diff --git a/marked/Rel-16/23_series/23008/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/23_series/23008/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4cfcda8a5483d8b6d5378376f9b900346c7e5e94 --- /dev/null +++ b/marked/Rel-16/23_series/23008/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a28c5a02aedf0faa3dbdf20cc4420f44966731538e257a56eb33a0b22ccc34a +size 9611 diff --git a/marked/Rel-16/23_series/23008/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/23_series/23008/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97fb31911e5cf2d06bea253d472462edb5b2948f --- /dev/null +++ b/marked/Rel-16/23_series/23008/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6be812790af7886d16972e3e23cce17baea9e7517d7b8f45438c015919fa0b5a +size 5625 diff --git a/marked/Rel-16/23_series/23008/raw.md b/marked/Rel-16/23_series/23008/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..70729d6c5097db068fa35a880a33af465738856a --- /dev/null +++ b/marked/Rel-16/23_series/23008/raw.md @@ -0,0 +1,6638 @@ + + +# 3GPP TS 23.008 V16.3.0 (2020-06) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Organization of subscriber data; (Release 16)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5G" text are three green curved lines of increasing size, representing signal waves. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. The "P" is larger and has a red signal wave icon at its base. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +# --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTETM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword..... | 15 | +| 0 Scope..... | 16 | +| 0.1 References..... | 16 | +| 0.2 Abbreviations..... | 20 | +| 1 Introduction..... | 21 | +| 1.1 Definition..... | 21 | +| 1.2 Storage facilities..... | 21 | +| 1.3 Subscriber data in other functional units..... | 22 | +| 1.4 Subscriber data in WLAN-IW functional units..... | 22 | +| 2 Definition of subscriber data for CS and PS domain..... | 23 | +| 2.1 Data related to subscription, identification and numbering..... | 23 | +| 2.1.1 Data defining the subscription profile..... | 23 | +| 2.1.1.1 International Mobile Subscriber Identity (IMSI)..... | 23 | +| 2.1.1.2 Network Access Mode (NAM)..... | 23 | +| 2.1.1.3 IMSI Unauthenticated indicator..... | 23 | +| 2.1.2 Mobile Station International ISDN Number (MSISDN)..... | 23 | +| 2.1.3 MSISDNs for multnumbering option..... | 23 | +| 2.1.3.1 The Basic MSISDN indicator..... | 23 | +| 2.1.3.2 The MSISDN-Alert indicator..... | 24 | +| 2.1.4 Temporary mobile subscriber identity (TMSI)..... | 24 | +| 2.1.5 Packet-Temporary Mobile Subscriber Identity (P-TMSI)..... | 24 | +| 2.1.6 Temporary Link Layer Identifier (TLLI)..... | 24 | +| 2.1.7 Random TLLI..... | 24 | +| 2.1.8 Local Mobile Station Identity (LMSI)..... | 24 | +| 2.1.9 International Mobile Equipment Identity (IMEI)..... | 24 | +| 2.1.10 External Identifier Set..... | 24 | +| 2.1.11 UE radio capability ID..... | 24 | +| 2.2 Data related to Mobile Station types..... | 25 | +| 2.2.1 Mobile Station Category..... | 25 | +| 2.2.2 LMU Identifier (GSM only)..... | 25 | +| 2.2.3 International Mobile Equipment Identity and Software Version (IMEISV)..... | 25 | +| 2.3 Data related to authentication and ciphering..... | 25 | +| 2.3.1 Random Number (RAND), Signed Response (SRES) and Ciphering Key (Kc)..... | 25 | +| 2.3.2 Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key(IK) and Authentication Token(AUTN), KASME..... | 25 | +| 2.3.3 The Ciphering Key Sequence Number (CKSN)..... | 26 | +| 2.3.4 The Key Set Identifier (KSI)..... | 26 | +| 2.3.5 Selected Ciphering Algorithm..... | 26 | +| 2.3.6 Current Kc..... | 26 | +| 2.3.7 P-TMSI Signature..... | 26 | +| 2.3.8 Access Network Identity (ANID)..... | 26 | +| 2.3.9 Key Status..... | 26 | +| 2.4 Data related to roaming..... | 27 | +| 2.4.1 Mobile Station Roaming Number (MSRN)..... | 27 | +| 2.4.2 Location Area Identification (LAI)..... | 27 | +| 2.4.3 Routing Area Identification (RAI)..... | 27 | +| 2.4.4 Void..... | 27 | +| 2.4.5 VLR number..... | 27 | +| 2.4.6 MSC number..... | 27 | +| 2.4.7 HLR number..... | 27 | +| 2.4.8 GSN number..... | 27 | +| 2.4.8.0 General..... | 27 | +| 2.4.8.1 SGSN number..... | 28 | +| 2.4.8.2 GGSN number..... | 28 | +| 2.4.8.3 IWF number..... | 28 | + +| | | | +|-----------|----------------------------------------------------------------|----| +| 2.4.9 | MLC number..... | 28 | +| 2.4.9.1 | SMLC number (GSM only)..... | 28 | +| 2.4.9.2 | GMLC number..... | 28 | +| 2.4.10 | Subscription restriction..... | 28 | +| 2.4.11 | Regional Subscription Information..... | 29 | +| 2.4.11.1 | RSZI lists..... | 29 | +| 2.4.11.2 | Zone Code List..... | 29 | +| 2.4.12 | MSC area restricted flag..... | 29 | +| 2.4.13 | LA not allowed flag..... | 29 | +| 2.4.14 | SGSN area restricted flag..... | 29 | +| 2.4.14a | RA not allowed flag..... | 30 | +| 2.4.14b | TA not allowed flag..... | 30 | +| 2.4.15 | Service restriction data induced by roaming..... | 30 | +| 2.4.15.1 | ODB-induced barring data..... | 31 | +| 2.4.15.2 | Roaming restriction due to unsupported feature..... | 31 | +| 2.4.15.3 | Roaming restricted in the SGSN due to unsupported feature..... | 31 | +| 2.4.15.3a | Roaming restricted in the MME due to unsupported feature..... | 31 | +| 2.4.16 | Cell Global ID or Service Area ID..... | 31 | +| 2.4.16A | E-UTRAN Cell Global ID..... | 32 | +| 2.4.16B | NR Cell Global Identity (NCGI)..... | 32 | +| 2.4.17 | Localised Service Area Information..... | 32 | +| 2.4.17.1 | LSA Identity..... | 32 | +| 2.4.17.2 | LSA Priority..... | 32 | +| 2.4.17.2A | LSA Preferential Access Indicator..... | 32 | +| 2.4.17.2B | LSA Active Mode Support Indicator..... | 32 | +| 2.4.17.3 | LSA Only Access Indicator..... | 32 | +| 2.4.17.4 | LSA Active Mode Indicator..... | 33 | +| 2.4.17.5 | VPLMN Identifier..... | 33 | +| 2.4.18 | Access Restriction Data..... | 33 | +| 2.4.19 | Selected CN operator ID..... | 33 | +| 2.4.20 | IP-SM-GW number..... | 34 | +| 2.4.20A | IP-SM-GW Diameter Identity..... | 34 | +| 2.4.21 | Paging Area..... | 34 | +| 2.4.22 | Closed Subscriber Group Information..... | 34 | +| 2.4.23 | Service Centre Address..... | 35 | +| 2.4.24 | Subscribed Periodic LAU Timer..... | 35 | +| 2.4.25 | CSS number..... | 35 | +| 2.4.26 | VPLMN Closed Subscriber Group Information..... | 35 | +| 2.4.27 | IAB-Operation Allowed indication..... | 35 | +| 2.5 | Data related to basic services..... | 35 | +| 2.5.1 | Provision of bearer service..... | 35 | +| 2.5.2 | Provision of teleservice..... | 36 | +| 2.5.3 | Bearer capability allocation..... | 36 | +| 2.5.4 | Transfer of SM option..... | 36 | +| 2.6 | Data related to supplementary services..... | 36 | +| 2.7 | Mobile station status data..... | 36 | +| 2.7.1 | IMSI detached flag..... | 36 | +| 2.7.2 | Mobile station Not Reachable for GPRS (MNRG)..... | 37 | +| 2.7.3 | Mobility Management State..... | 37 | +| 2.7.4 | Restoration flags..... | 37 | +| 2.7.4.1 | Confirmed by Radio Contact indicator..... | 37 | +| 2.7.4.2 | Subscriber Data Confirmed by HLR/HSS indicator..... | 37 | +| 2.7.4.3 | Location Information Confirmed in HLR/HSS indicator..... | 37 | +| 2.7.4.4 | Check SS indicator..... | 37 | +| 2.7.4.5 | VLR-Reliable indicator..... | 37 | +| 2.7.5 | MS purged for non-GPRS flag..... | 38 | +| 2.7.6 | MS purged for GPRS/UE purged in SGSN flag..... | 38 | +| 2.7.6A | UE purged in MME flag..... | 38 | +| 2.7.7 | Mobile station Not Reachable via MSC Reason (MNRR-MSC)..... | 38 | +| 2.7.7A | Mobile station Not Reachable via SGSN Reason (MNRR-SGSN)..... | 38 | +| 2.7.8 | Subscriber data dormant..... | 38 | + +| | | | +|----------|---------------------------------------------------------------------|----| +| 2.7.8A | Cancel Location received..... | 38 | +| 2.7.9 | Data related to UE reachability procedures..... | 39 | +| 2.7.9.1 | URRP-MME..... | 39 | +| 2.7.9.2 | URRP-SGSN..... | 39 | +| 2.8 | Data related to Operator Determined Barring..... | 39 | +| 2.8.1 | Subscriber status..... | 39 | +| 2.8.2 | Operator Determined Barring general data..... | 39 | +| 2.8.2.1 | Barring of outgoing calls..... | 39 | +| 2.8.2.2 | Barring of incoming calls..... | 40 | +| 2.8.2.3 | Barring of roaming..... | 40 | +| 2.8.2.4 | Barring of premium rate calls..... | 40 | +| 2.8.2.5 | Barring of supplementary services management..... | 40 | +| 2.8.2.6 | Barring of registration of call forwarding..... | 40 | +| 2.8.2.7 | Barring of invocation of call transfer..... | 41 | +| 2.8.2.8 | Barring of Packet Oriented Services..... | 41 | +| 2.8.3 | Operator Determined Barring PLMN-specific data..... | 41 | +| 2.8.4 | Notification to CSE flag..... | 41 | +| 2.8.5 | gsmSCF address list..... | 42 | +| 2.9 | Data related to handover..... | 42 | +| 2.9.1 | Handover Number..... | 42 | +| 2.10 | Data related to short message support..... | 42 | +| 2.10.1 | Messages Waiting Data (MWD)..... | 42 | +| 2.10.2 | Mobile Station Not Reachable Flag (MNRF)..... | 42 | +| 2.10.3 | Memory Capacity Exceeded Flag (MCEF)..... | 42 | +| 2.10.4 | Mobile station Not Reachable for GPRS (MNRG)..... | 42 | +| 2.10.4A | UE Not Reachable via IP-SM-GW Flag (UNRI)..... | 42 | +| 2.10.5 | Mobile station Not Reachable via MSC Reason (MNRR- MSC)..... | 42 | +| 2.10.5A | Mobile station Not Reachable via SGSN Reason (MNRR-SGSN)..... | 42 | +| 2.10.5B | UE Not Reachable via IP-SM-GW Reason (UNRR)..... | 42 | +| 2.10.6 | MME Number for MT SMS..... | 43 | +| 2.10.7 | PS and SMS Only..... | 43 | +| 2.10.8 | SMS In SGSN Allowed..... | 43 | +| 2.11 | Data related to subscriber trace..... | 43 | +| 2.11.1 | Trace Reference..... | 43 | +| 2.11.2 | Trace Type..... | 43 | +| 2.11.3 | Operations Systems Identity..... | 43 | +| 2.11.4 | HLR Trace Type..... | 43 | +| 2.11.5 | MAP Error On Trace..... | 43 | +| 2.11.6 | Trace Activated in VLR..... | 43 | +| 2.11.7 | Trace Activated in SGSN..... | 44 | +| 2.11.8 | Foreign Subscriber Registered in VLR..... | 44 | +| 2.11.9 | Trace Reference 2..... | 44 | +| 2.11.10 | Trace depth..... | 44 | +| 2.11.11 | List of NE types to trace..... | 44 | +| 2.11.12 | Triggering events..... | 44 | +| 2.11.13 | List of interfaces to trace..... | 44 | +| 2.11.14 | IP address of Trace Collection Entity..... | 44 | +| 2.11.15 | MDT-Configuration..... | 44 | +| 2.11.16 | MDT User Consent..... | 45 | +| 2.12 | Data related to the support of voice group and broadcast calls..... | 45 | +| 2.12.1 | VGCS Group Membership List..... | 45 | +| 2.12.2 | VBS Group Membership List..... | 45 | +| 2.12.2.1 | Broadcast Call Initiation Allowed List..... | 45 | +| 2.13 | Data related to PS NAM..... | 45 | +| 2.13.1 | PDP Type..... | 45 | +| 2.13.2 | PDP Address..... | 46 | +| 2.13.3 | NSAPI..... | 46 | +| 2.13.4 | Packet Data Protocol (PDP) State..... | 46 | +| 2.13.5 | New SGSN Address..... | 46 | +| 2.13.6 | Access Point Name (APN)..... | 46 | +| 2.13.7 | GGSN Address in Use..... | 46 | + +| | | | +|----------|-----------------------------------------------------|----| +| 2.13.8 | VPLMN Address Allowed..... | 46 | +| 2.13.9 | Dynamic Address..... | 46 | +| 2.13.10 | SGSN Address..... | 46 | +| 2.13.11 | GGSN-list..... | 47 | +| 2.13.12 | Quality of Service Subscribed..... | 47 | +| 2.13.13 | Quality of Service Requested..... | 47 | +| 2.13.14 | Quality of Service Negotiated..... | 47 | +| 2.13.15 | SND..... | 47 | +| 2.13.16 | SNU..... | 47 | +| 2.13.17 | DRX Parameters..... | 47 | +| 2.13.18 | Compression..... | 47 | +| 2.13.19 | Non-GPRS Alert Flag (NGAF)..... | 48 | +| 2.13.20 | Classmark..... | 48 | +| 2.13.21 | Tunnel Endpoint Identifier (TEID)..... | 48 | +| 2.13.22 | Radio Priority..... | 48 | +| 2.13.23 | Radio Priority SMS..... | 48 | +| 2.13.24 | PDP Context Identifier..... | 48 | +| 2.13.25 | PDP Context Charging Characteristics..... | 48 | +| 2.13.26 | MME name..... | 48 | +| 2.13.27 | VLR name..... | 49 | +| 2.13.28 | Non-EPS Alert Flag (NEAF)..... | 49 | +| 2.13.29 | UE level APN-OI-Replacement..... | 49 | +| 2.13.30 | Subscribed UE-AMBR..... | 49 | +| 2.13.30A | Used UE-AMBR..... | 49 | +| 2.13.31 | APN-Configuration-Profile..... | 49 | +| 2.13.32 | Subscribed APN-AMBR..... | 49 | +| 2.13.32A | Used APN-AMBR..... | 50 | +| 2.13.33 | Subscribed-RAT-Frequency-Selection-Priority-ID..... | 50 | +| 2.13.34 | GUTI..... | 50 | +| 2.13.35 | ME Identity..... | 50 | +| 2.13.36 | Selected NAS Algorithm..... | 50 | +| 2.13.37 | Selected AS Algorithm..... | 50 | +| 2.13.38 | Context Identifier..... | 50 | +| 2.13.39 | PDN Address..... | 50 | +| 2.13.40 | VPLMN Address Allowed..... | 50 | +| 2.13.41 | PDN GW identity..... | 50 | +| 2.13.42 | Tracking Area List..... | 50 | +| 2.13.43 | APN Restriction..... | 51 | +| 2.13.44 | APN in use..... | 51 | +| 2.13.45 | TAI..... | 51 | +| 2.13.46 | E-UTRAN Cell Identity Age..... | 51 | +| 2.13.47 | MME F-TEID for S11 (Control Plane)..... | 51 | +| 2.13.48 | MME UE SIAP ID..... | 51 | +| 2.13.49 | S-GW F-TEID for S11 (Control Plane)..... | 51 | +| 2.13.50 | S4-SGSN F-TEID for S4 (Control plane)..... | 51 | +| 2.13.51 | S4-SGSN F-TEID for S4 (User plane)..... | 51 | +| 2.13.52 | S-GW F-TEID for S5/S8 (control plane)..... | 51 | +| 2.13.53 | S-GW F-TEID for S1-U..... | 51 | +| 2.13.54 | S-GW F-TEID for S5/S8 (user plane)..... | 52 | +| 2.13.55 | eNodeB Address..... | 52 | +| 2.13.56 | eNodeB UE SIAP ID..... | 52 | +| 2.13.57 | eNodeB F-TEID for S1-U..... | 52 | +| 2.13.58 | E-UTRAN/UTRAN Key Set flag..... | 52 | +| 2.13.59 | Selected CN operator id..... | 52 | +| 2.13.60 | UE Radio Access Capability..... | 52 | +| 2.13.61 | UE Network Capability..... | 52 | +| 2.13.62 | Location Change Report..... | 52 | +| 2.13.63 | UE Specific DRX Parameters..... | 52 | +| 2.13.64 | PDN-GW F-TEID for S5/S8 (user plane)..... | 53 | +| 2.13.65 | PDN GW F-TEID for S5/S8 (control plane)..... | 53 | +| 2.13.66 | EPS Bearer ID..... | 53 | + +| | | | +|-----------|--------------------------------------------------|----| +| 2.13.67 | EPS Bearer QoS..... | 53 | +| 2.13.67A | EPS Subscribed QoS Profile..... | 53 | +| 2.13.68 | UL TFT..... | 53 | +| 2.13.69 | DL TFT..... | 53 | +| 2.13.70 | Charging Id..... | 53 | +| 2.13.71 | EPS PDN Connection Charging Characteristics..... | 54 | +| 2.13.72 | Default bearer..... | 54 | +| 2.13.73 | Void..... | 54 | +| 2.13.74 | Void..... | 54 | +| 2.13.75 | RAT Type (Access Type)..... | 54 | +| 2.13.76 | S101 HRPD access node IP address..... | 54 | +| 2.13.77 | S103 Forwarding Address..... | 54 | +| 2.13.78 | S103 GRE key(s)..... | 54 | +| 2.13.79 | Permanent User Identity..... | 54 | +| 2.13.80 | Mobility Capabilities..... | 54 | +| 2.13.81 | MAG IP address..... | 54 | +| 2.13.82 | Visited Network Identifier..... | 55 | +| 2.13.83 | EAP payload..... | 55 | +| 2.13.84 | Void..... | 55 | +| 2.13.85 | Void..... | 55 | +| 2.13.86 | MIP Subscriber profile..... | 55 | +| 2.13.87 | Uplink S5 GRE Key..... | 55 | +| 2.13.88 | Downlink S5 GRE Key..... | 55 | +| 2.13.89 | Uplink S8 GRE Key..... | 55 | +| 2.13.90 | Downlink S8 GRE Key..... | 55 | +| 2.13.91 | S2a GRE Keys..... | 55 | +| 2.13.92 | S2b GRE Keys..... | 55 | +| 2.13.93 | Mobile Node Identifier..... | 55 | +| 2.13.94 | IPv4 Default Router Address..... | 56 | +| 2.13.95 | Link-local address..... | 56 | +| 2.13.96 | Non 3GPP User Data..... | 56 | +| 2.13.97 | 3GPP AAA Server Identity..... | 56 | +| 2.13.98 | Selected IP mobility mode..... | 56 | +| 2.13.99 | Diameter Server Identity of HSS..... | 56 | +| 2.13.100 | SGSN name..... | 56 | +| 2.13.101 | S-GW F-TEID for S12..... | 56 | +| 2.13.102 | RNC F-TEID for S12..... | 56 | +| 2.13.103 | MME F-TEID for S3..... | 56 | +| 2.13.104 | S4-SGSN F-TEID for S3..... | 57 | +| 2.13.105 | PDN GW Allocation Type..... | 57 | +| 2.13.106 | S-GW F-TEID for S4 (control plane)..... | 57 | +| 2.13.107 | S-GW F-TEID for S4 (user plane)..... | 57 | +| 2.13.108 | RAT-Frequency-Selection-Priority-ID in Use..... | 57 | +| 2.13.109 | APN level APN-OI-Replacement..... | 57 | +| 2.13.110 | Unauthenticated IMSI..... | 57 | +| 2.13.111 | PDN Connection ID..... | 57 | +| 2.13.114 | SIPTO Permission..... | 58 | +| 2.13.114A | SIPTO Local Network Permission..... | 58 | +| 2.13.115 | Subscribed Periodic RAU/TAU Timer..... | 58 | +| 2.13.116 | ePDG F-TEID for S2b (control plane)..... | 58 | +| 2.13.117 | ePDG F-TEID for S2b (user plane)..... | 58 | +| 2.13.118 | PGW F-TEID for S2b (control plane)..... | 58 | +| 2.13.119 | PGW F-TEID for S2b (user plane)..... | 58 | +| 2.13.120 | MPS CS Priority..... | 58 | +| 2.13.121 | MPS EPS Priority..... | 59 | +| 2.13.122 | LIPA Permission..... | 59 | +| 2.13.123 | LIPA Allowed VPLMN List..... | 59 | +| 2.13.124 | VPLMN LIPA Allowed..... | 59 | +| 2.13.125 | Relay Node Indicator..... | 59 | +| 2.13.126 | Restricted RAT Types..... | 59 | +| 2.13.127 | Higher bitrates than 16Mbps flag..... | 60 | + +| | | | +|------------|---------------------------------------------------------------------------------------------------------------------------|----| +| 2.13.128 | Void..... | 60 | +| 2.13.129 | UE Local IP Address..... | 60 | +| 2.13.130 | UE UDP Port Number..... | 60 | +| 2.13.131 | H(e)NB Local IP Address..... | 60 | +| 2.13.132 | H(e)NB UDP Port Number..... | 60 | +| 2.13.133 | Diameter Server Identity of CSS..... | 60 | +| 2.13.134 | MME/S4 SGSN Identifier..... | 60 | +| 2.13.135 | SGW node name..... | 60 | +| 2.13.136 | Co-located GGSN-PGW FQDN..... | 60 | +| 2.13.137 | GERAN Cell Identity Age..... | 60 | +| 2.13.138 | UTRAN Service Area Identity Age..... | 61 | +| 2.13.139 | Default APN for Trusted WLAN..... | 61 | +| 2.13.140 | Access Information for Trusted WLAN..... | 61 | +| 2.13.141 | Homogeneous Support of IMS Voice over PS Sessions..... | 61 | +| 2.13.142 | Signalling Priority Indication..... | 61 | +| 2.13.143 | Restoration Priority..... | 61 | +| 2.13.144 | Void..... | 61 | +| 2.13.145 | Presence Reporting Area Action..... | 61 | +| 2.13.146 | WLAN offloadability..... | 61 | +| 2.13.147 | CN Assistance Information..... | 62 | +| 2.13.147.1 | General..... | 62 | +| 2.13.147.2 | Expected UE Activity Behaviour..... | 62 | +| 2.13.147.3 | Expected HO Interval..... | 62 | +| 2.13.148 | Active Time Value for PSM..... | 62 | +| 2.13.149 | Origination Time Stamp..... | 62 | +| 2.13.150 | DL Data Buffer Expiration Time..... | 62 | +| 2.13.151 | DL Buffering Suggested Packet Count..... | 62 | +| 2.13.152 | Notify-on-available-after-DDN-failure flag..... | 62 | +| 2.13.153 | IMSI Group Identifier List..... | 63 | +| 2.13.154 | UE Usage Type..... | 63 | +| 2.13.155 | Emergency Indication..... | 63 | +| 2.13.156 | Remote UE Contexts..... | 63 | +| 2.13.157 | Extended Idle Mode DRX parameters..... | 63 | +| 2.13.158 | Delay Tolerant Connection Indication..... | 63 | +| 2.13.159 | Pending Network Initiated PDN Connection Signalling Indication..... | 63 | +| 2.13.160 | UE Radio Capability for Paging information..... | 63 | +| 2.13.161 | Information on Recommended Cells and ENBs for Paging..... | 63 | +| 2.13.162 | Paging Attempt Count..... | 64 | +| 2.13.163 | User Plane Integrity Protection Indicator..... | 64 | +| 2.13.164 | Non-IP-PDN-Type-Indicator..... | 64 | +| 2.13.165 | Non-IP-Data-Delivery-Mechanism..... | 64 | +| 2.13.166 | SCEF-ID..... | 64 | +| 2.13.167 | PDN Type..... | 64 | +| 2.13.168 | PDN-Connection-Restricted flag..... | 64 | +| 2.13.169 | Preferred-Data-Mode..... | 64 | +| 2.13.170 | IOV_updates counter..... | 65 | +| 2.13.171 | Emergency Info..... | 65 | +| 2.13.172 | Dedicated Core Network Identifier..... | 65 | +| 2.13.173 | Acknowledgements Of Downlink NAS Data PDUs flag..... | 65 | +| 2.13.174 | Service Gap Time..... | 65 | +| 2.13.175 | Subscribed Additional RRM Policy Index..... | 65 | +| 2.13.176 | Additional RRM Policy Index in Use..... | 65 | +| 2.13.177 | Ethernet-PDN-Type-Indicator..... | 65 | +| 2.14 | Data related to CAMEL..... | 65 | +| 2.14.1 | Subscriber Data stored in HLR..... | 65 | +| 2.14.1.1 | Originating CAMEL Subscription Information (O-CSI)..... | 65 | +| 2.14.1.2 | Terminating CAMEL Subscription Information (T-CSI) and VMSC Terminating CAMEL
Subscription Information (VT-CSI));..... | 66 | +| 2.14.1.3 | Location information/Subscriber state interrogation..... | 67 | +| 2.14.1.4 | USSD CAMEL subscription information(U-CSI)..... | 67 | +| 2.14.1.5 | Supplementary Service invocation notification(SS-CSI)..... | 67 | + +| | | | +|-----------|-------------------------------------------------------------------------------------------|----| +| 2.14.1.6 | Translation Information flag (TIF-CSI)..... | 67 | +| 2.14.1.7 | Mobility Management event notification (M-CSI)..... | 68 | +| 2.14.1.8 | Mobile Originated Short Message Service CAMEL Subscription Information (MO-SMS-CSI)..... | 68 | +| 2.14.1.9 | Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI)..... | 69 | +| 2.14.1.10 | GPRS CAMEL Subscription Information (GPRS-CSI)..... | 69 | +| 2.14.1.11 | Dialled service CAMEL Subscription Information (D-CSI)..... | 70 | +| 2.14.1.12 | Mobility Management for GPRS event notification (MG-CSI)..... | 70 | +| 2.14.2 | Other Data stored in the HLR..... | 71 | +| 2.14.2.1 | Negotiated CAMEL Capability Handling..... | 71 | +| 2.14.2.2 | Supported CAMEL Phases..... | 71 | +| 2.14.2.2A | Offered CAMEL4 CSIs..... | 71 | +| 2.14.2.3 | UG-CSI..... | 72 | +| 2.14.2.4 | gsmSCF address for CSI..... | 72 | +| 2.14.3 | Subscriber data stored in VLR..... | 72 | +| 2.14.3.1 | Originating CAMEL Subscription Information (O-CSI)..... | 72 | +| 2.14.3.2 | VMSC Terminating CAMEL Subscription Information (VT-CSI)..... | 72 | +| 2.14.3.3 | Supplementary Service invocation notification(SS-CSI)..... | 73 | +| 2.14.3.4 | Mobility Management event notification (M-CSI)..... | 73 | +| 2.14.3.5 | Mobile Originating Short Message Service CAMEL Subscription Information (MO-SMS-CSI)..... | 74 | +| 2.14.3.6 | Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI)..... | 74 | +| 2.14.3.7 | Dialled service CAMEL Subscription Information (D-CSI)..... | 75 | +| 2.14.3.8 | Translation Information flag (TIF-CSI)..... | 75 | +| 2.14.4 | Data stored in SGSN..... | 75 | +| 2.14.4.1 | Mobile Originating Short Message Service CAMEL Subscription Information (MO-SMS-CSI)..... | 75 | +| 2.14.4.2 | Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI)..... | 76 | +| 2.14.4.3 | GPRS CAMEL Subscription Information (GPRS-CSI)..... | 77 | +| 2.14.4.4 | Mobility Management for GPRS event notification (MG-CSI)..... | 77 | +| 2.15 | Data related to IST..... | 77 | +| 2.15.1 | IST Alert Timer..... | 77 | +| 2.16 | Data related to Location Services..... | 78 | +| 2.16.1 | Subscriber Data stored in HLR..... | 78 | +| 2.16.1.1 | Privacy Exception List..... | 78 | +| 2.16.1.2 | GMLC Numbers..... | 78 | +| 2.16.1.3 | MO-LR List..... | 78 | +| 2.16.1.4 | Service Types..... | 78 | +| 2.16.2 | Data stored in GMLC..... | 78 | +| 2.16.3 | Data stored in SMLC (GSM only)..... | 78 | +| 2.16.4 | Data stored in LMU (GSM only)..... | 78 | +| 2.16.5 | Data stored in the MSC (GSM only)..... | 78 | +| 2.16.6 | Data stored in the BSC (GSM only)..... | 78 | +| 2.16.7 | Subscriber Data stored in HSS..... | 79 | +| 2.16.7.1 | List of Broadcast Location Assistance Data Types..... | 79 | +| 2.17 | Data related to Super-Charger..... | 79 | +| 2.17.1 | Age Indicator..... | 79 | +| 2.18 | Data related to bearer service priority..... | 79 | +| 2.18.1 | CS Allocation/Retention priority..... | 79 | +| 2.19 | Data related to charging..... | 79 | +| 2.19.1 | Subscribed Charging Characteristics..... | 79 | +| 2.20 | Data related to IMS Centralized Service..... | 79 | +| 2.20.1 | ICS Indicator..... | 79 | +| 2.21 | Data related to SRVCC..... | 79 | +| 2.21.1 | STN-SR..... | 79 | +| 2.21.1.1 | General..... | 79 | +| 2.21.1.2 | STN-SR in EPS or GPRS..... | 80 | +| 2.21.1.3 | STN-SR in 5GS..... | 80 | +| 2.21.2 | UE SRVCC Capability..... | 80 | +| 2.21.2.1 | General..... | 80 | +| 2.21.2.2 | UE SRVCC Capability in EPS..... | 80 | +| 2.21.2.3 | UE SRVCC Capability in 5GS..... | 80 | +| 2.21.3 | Subscribed vSRVCC..... | 80 | +| 2.21.4 | CS to PS SRVCC Allowed..... | 80 | + +| | | | +|---------|---------------------------------------------------------------|----| +| 2.22 | Data related to MBMS..... | 80 | +| 2.22.1 | MBMS GW F-TEID for Sm (Control Plane)..... | 80 | +| 2.22.2 | MBMS GW F-TEID for Sn (Control Plane)..... | 80 | +| 2.22.3 | Temporary Mobile Group Identity..... | 81 | +| 2.22.4 | MBMS Flow Identifier..... | 81 | +| 2.22.5 | MBMS IP Multicast Distribution..... | 81 | +| 2.22.6 | MBMS Service Area..... | 81 | +| 2.22.7 | MME F-TEID for Sm (Control Plane)..... | 81 | +| 2.22.8 | SGSN F-TEID for Sn (Control Plane)..... | 81 | +| 2.22.9 | SGSN F-TEID for Sn (User Plane)..... | 81 | +| 2.22.10 | MBMS session identifier..... | 81 | +| 2.22.11 | MBMS session duration..... | 81 | +| 2.22.12 | QoS parameters..... | 81 | +| 2.22.13 | MBMS Time to Data Transfer..... | 81 | +| 2.22.14 | MBMS Data Transfer Start..... | 82 | +| 2.22.15 | List of downstream nodes..... | 82 | +| 2.22.16 | MBMS Session Re-establishment Indication..... | 82 | +| 2.22.17 | GCS AS Address..... | 82 | +| 2.22.18 | MB2-U Port Number..... | 82 | +| 2.22.19 | MBMS Start Time..... | 82 | +| 2.22.20 | TMGI Expiration Time..... | 82 | +| 2.22.21 | MBMS Alternative IP Multicast Distribution..... | 82 | +| 2.22.22 | MBMS Cell List..... | 82 | +| 2.23 | Data related to Cellular IoT Control Plane Optimizations..... | 82 | +| 2.23.1 | Robust Header Compression Context..... | 82 | +| 2.23.2 | Void..... | 83 | +| 2.23.3 | MME F-TEID for S11 (User Plane)..... | 83 | +| 2.23.4 | S-GW F-TEID for S11(User Plane)..... | 83 | +| 2.23.5 | Serving-PLMN-Rate-Control..... | 83 | +| 2.23.6 | APN-Rate-Control..... | 83 | +| 2.23.7 | Not Reachable for NIDD Flag..... | 83 | +| 2.23.8 | NIDD Authorization..... | 83 | +| 2.24 | Data related to ERP..... | 83 | +| 2.24.1 | General..... | 83 | +| 2.24.2 | ERP-Authorization..... | 83 | +| 2.24.3 | ERP Keying Material..... | 84 | +| 2.24.4 | ERP Realm..... | 84 | +| 2.25 | Data related to the support of 5GS..... | 84 | +| 2.25.1 | SUPI..... | 84 | +| 2.25.2 | GPSI..... | 84 | +| 2.25.3 | Internal Group ID-list..... | 84 | +| 2.25.4 | Subscribed NSSAI..... | 84 | +| 2.25.5 | Default S-NSSAI..... | 84 | +| 2.25.6 | 5G QoS Parameters..... | 84 | +| 2.25.7 | Forbidden area..... | 85 | +| 2.25.8 | Service Area Restriction..... | 85 | +| 2.25.9 | RFSP Index..... | 85 | +| 2.25.10 | Priority Service..... | 85 | +| 2.25.11 | DNN Info..... | 85 | +| 2.25.12 | DNN Configuration..... | 85 | +| 2.25.13 | Steering of Roaming Information..... | 85 | +| 2.25.14 | SMS supported Data..... | 85 | +| 2.25.15 | SMSF Registrations..... | 85 | +| 2.25.16 | SMS subscribed..... | 86 | +| 2.25.17 | SMS barring..... | 86 | +| 2.25.18 | SMS Roaming..... | 86 | +| 2.25.19 | Core Network Type Restriction..... | 86 | +| 2.25.20 | LADN Information..... | 86 | +| 2.25.21 | Subscribed Periodic Registration Timer..... | 86 | +| 2.25.22 | PEI..... | 86 | +| 2.25.23 | 5G GUTI..... | 86 | + +| | | | +|---------|-----------------------------------------------------------------------------------------------------------------------------|----| +| 2.25.24 | PLMN Identifier..... | 87 | +| 2.25.25 | PDU Session..... | 87 | +| 2.25.26 | Trace Data..... | 87 | +| 2.25.27 | Mobile Initiated Connection Only (MICO) mode..... | 87 | +| 2.25.28 | UE purged in AMF flag..... | 87 | +| 2.25.29 | GUAMI..... | 87 | +| 2.25.30 | RAND, AUTN, XRES, CK', IK'..... | 87 | +| 2.25.31 | RAND, AUTN, XRES*..... | 87 | +| 2.25.32 | RAND, AUTN, HXRES*..... | 88 | +| 2.25.33 | Kausf..... | 88 | +| 2.25.34 | Kseaf..... | 88 | +| 2.25.35 | AuthenticationMethod..... | 88 | +| 2.25.36 | PermanentKey..... | 88 | +| 2.25.37 | SequenceNumber..... | 88 | +| 2.25.38 | AuthenticationManagementField..... | 88 | +| 2.25.39 | VectorAlgorithm..... | 88 | +| 2.25.40 | Milenage..... | 88 | +| 2.25.41 | Tuak..... | 89 | +| 2.25.42 | Opc..... | 89 | +| 2.25.43 | Topc..... | 89 | +| 2.25.44 | Authentication Status..... | 89 | +| 2.25.45 | SoR-XMAC-I UE ..... | 89 | +| 2.25.46 | Shared Data Ids..... | 89 | +| 2.25.47 | Access Restriction Data..... | 89 | +| 2.25.48 | IAB-Operation Allowed indication..... | 90 | +| 2.25.49 | UE radio capability ID..... | 90 | +| 2.25.50 | RG Level Wireline Access Characteristics..... | 90 | +| 2.25.51 | RG-TMBR..... | 90 | +| 3 | Definition of data for IP Multimedia domain..... | 90 | +| 3.1 | Data related to subscription, identification and numbering..... | 91 | +| 3.1.1 | Private User Identity..... | 91 | +| 3.1.2 | Public User Identities..... | 91 | +| 3.1.2A | Private Service Identity..... | 91 | +| 3.1.2B | Public Service Identity..... | 91 | +| 3.1.3 | Barring indication..... | 91 | +| 3.1.4 | List of authorized visited network identifiers..... | 91 | +| 3.1.5 | Services related to Unregistered State..... | 91 | +| 3.1.6 | Implicitly Registered Public User Identity Sets..... | 92 | +| 3.1.7 | Default Public User Identity indicator..... | 92 | +| 3.1.8 | PSI Activation State..... | 92 | +| 3.1.9 | Display Name..... | 92 | +| 3.1.10 | Alias Public User Identity Sets..... | 92 | +| 3.1.11 | Loose-Route Indication..... | 92 | +| 3.1.12 | Service Priority Level..... | 93 | +| 3.1.13 | Extended Priority..... | 93 | +| 3.1.14 | Reference Location Information..... | 93 | +| 3.1.15 | Privileged-Sender Indication..... | 93 | +| 3.2 | Data related to registration..... | 93 | +| 3.2.1 | Registration Status..... | 93 | +| 3.2.2 | S-CSCF Name..... | 93 | +| 3.2.2A | AS Name..... | 94 | +| 3.2.3 | Diameter Client Identity of S-CSCF..... | 94 | +| 3.2.4 | Diameter Server Identity of HSS..... | 94 | +| 3.2.5 | UE Not Reachable via IP-SM-GW Flag (UNRI)..... | 94 | +| 3.2.6 | UE Not Reachable via IP-SM-GW Reason (UNRR)..... | 94 | +| 3.2.7 | S-CSCF Restoration Information..... | 94 | +| 3.2.8 | Maximum Number Of Allowed Simultaneous Registrations..... | 94 | +| 3.3 | Data related to authentication and ciphering..... | 95 | +| 3.3.1 | Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key (IK) and Authentication Token (AUTN)..... | 95 | +| 3.3.2 | Data related to SIP Digest Authentication..... | 95 | + +| | | | +|----------|-------------------------------------------------------------------------------|-----| +| 3.3.2.1 | Digest Nonce..... | 95 | +| 3.3.2.2 | Digest HA1..... | 95 | +| 3.3.2.3 | Digest Nextnonce..... | 95 | +| 3.3.2.4 | Void..... | 95 | +| 3.3.2.5 | Authentication Pending Flag..... | 95 | +| 3.3.1 | Data related to NASS Bundled Authentication..... | 95 | +| 3.3.3.1 | Line Identifier List..... | 95 | +| 3.4 | Data related S-CSCF selection information..... | 96 | +| 3.4.1 | Server Capabilities..... | 96 | +| 3.4.2 | S-CSCF Reassignment Pending Flag..... | 96 | +| 3.5 | Data related to Application and service triggers..... | 96 | +| 3.5.1 | Void..... | 96 | +| 3.5.2 | Initial Filter Criteria..... | 96 | +| 3.5.3 | Application Server Information..... | 96 | +| 3.5.4 | Service Indication..... | 96 | +| 3.5.5 | Shared iFC Set Identifier..... | 96 | +| 3.5.6 | Transparent Data..... | 96 | +| 3.5.7 | Application Server Identity List..... | 97 | +| 3.6 | Data related to Core Network Services Authorization..... | 97 | +| 3.6.1 | Subscribed Media Profile Identifier..... | 97 | +| 3.6.2 | List of Subscribed IMS Communication Service Identifiers..... | 97 | +| 3.7 | Data related to Charging..... | 97 | +| 3.7.1 | Primary Event Charging Function Name..... | 97 | +| 3.7.2 | Secondary Event Charging Function Name..... | 97 | +| 3.7.3 | Primary Charging Collection Function Name..... | 98 | +| 3.7.4 | Secondary Charging Collection Function Name..... | 98 | +| 3.8 | Data related to CAMEL Support of IMS Services..... | 98 | +| 3.8.1 | Originating IP Multimedia CAMEL Subscription Information (O-IM-CSI)..... | 98 | +| 3.8.2 | Terminating IP Multimedia CAMEL Subscription Information (VT-IM-CSI)..... | 99 | +| 3.8.3 | Dialled Services IP Multimedia CAMEL Subscription Information (D-IM-CSI)..... | 100 | +| 3.8.4 | gsmSCF address for IM CSI..... | 100 | +| 3.8.5 | IM-SSF address for IM CSI..... | 100 | +| 3.9 | Data related to IMS Service Level Trace..... | 100 | +| 3.9.1 | IMS Service Level Trace Information..... | 100 | +| 3.10 | Data related to Generic Authentication Architecture..... | 100 | +| 3.10.1 | GAA Service Type..... | 101 | +| 3.10.2 | GAA Service Identifier..... | 101 | +| 3.10.3 | GBA User Security Settings..... | 101 | +| 3.10.4 | User Security Setting..... | 101 | +| 3.10.5 | User Public Identity..... | 101 | +| 3.10.6 | GAA Authorization flag..... | 101 | +| 3.10.7 | Bootstrapping Transaction Identifier..... | 101 | +| 3.10.8 | Key Lifetime..... | 102 | +| 3.10.9 | UICC Security Type..... | 102 | +| 3.10.10 | NAF Group..... | 102 | +| 3.10.11 | NAF Group Identity..... | 102 | +| 3.10.12 | NAF Address..... | 102 | +| 3.10.13 | Key Expirytime..... | 102 | +| 3.10.14 | Bootstrapping Info Creation Time..... | 102 | +| 3.10.15 | Diameter Server Identity of HSS..... | 102 | +| 3.11 | Definition of subscriber data I-WLAN domain..... | 103 | +| 3.11.1 | Data related to subscription, identification and numbering..... | 103 | +| 3.11.1.1 | IMSI..... | 103 | +| 3.11.1.2 | Mobile Subscriber ISDN Number (MSISDN)..... | 103 | +| 3.11.1.3 | W-APN..... | 103 | +| 3.11.1.4 | List of authorized visited network identifiers..... | 103 | +| 3.11.1.5 | 3GPP AAA Proxy Name..... | 103 | +| 3.11.1.6 | 3GPP AAA Server Name..... | 103 | +| 3.11.1.7 | Serving PDG List..... | 103 | +| 3.11.1.8 | Serving WAG..... | 103 | +| 3.11.1.9 | WLAN UE Local IP Address..... | 103 | + +| | | | +|------------|-----------------------------------------------------------------------------------------------------------------------------|-----| +| 3.11.1.10 | WLAN UE Remote IP Address..... | 104 | +| 3.11.2 | Data related to registration..... | 104 | +| 3.11.2.1 | User Status..... | 104 | +| 3.11.2.2 | Emergency Access Flag..... | 104 | +| 3.11.2.3 | Diameter Server Identity of HSS..... | 104 | +| 3.11.3 | Data related to authentication and ciphering..... | 104 | +| 3.11.3.1 | Random Number (RAND), Signed Response (SRES) and Ciphering Key (Kc)..... | 104 | +| 3.11.3.2 | Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key (IK) and Authentication Token (AUTN)..... | 104 | +| 3.11.3.3 | Master Key (MK)..... | 105 | +| 3.11.3.4 | Transient EAP Keys (TEKs)..... | 105 | +| 3.11.3.5 | Master Session Key (MSK)..... | 105 | +| 3.11.4 | Data related to session..... | 105 | +| 3.11.4.1 | Session Identifier..... | 105 | +| 3.11.4.2 | Session-Timeout..... | 105 | +| 3.11.5 | Operator Determined Barring general data..... | 105 | +| 3.11.5.1 | W-APN Authorised List..... | 105 | +| 3.11.5.1.1 | W-APN Identifier List..... | 105 | +| 3.11.5.1.2 | W-APN Barring Type List..... | 105 | +| 3.11.5.1.3 | W-APN Charging Data List..... | 105 | +| 3.11.5.1.4 | Static WLAN UE Remote IP Address List..... | 106 | +| 3.11.5.1.5 | Maximum Number of Accesses List..... | 106 | +| 3.11.5.1.6 | Access Number List..... | 106 | +| 3.11.5.2 | Access Dependence Flag..... | 106 | +| 3.11.5.3 | I-WLAN Access Type..... | 106 | +| 3.11.5.4 | WLAN Direct IP Access..... | 106 | +| 3.11.6 | QoS general data..... | 106 | +| 3.11.6.1 | Max Subscribed Bandwidth..... | 106 | +| 3.11.6.2 | Routing Policy..... | 106 | +| 3.11.6.3 | Subscribed 3GPP WLAN QoS Profile..... | 106 | +| 3.11.6.4 | Authorized 3GPP WLAN QoS Profile..... | 106 | +| 3.11.7 | Data related to Charging..... | 107 | +| 3.11.7.1 | Charging Data..... | 107 | +| 3.11.7.1.1 | Charging Characteristics..... | 107 | +| 3.11.7.2 | Primary OCS Charging Function Name..... | 107 | +| 3.11.7.3 | Secondary OCS Charging Function Name..... | 107 | +| 3.11.7.4 | Primary Charging Collection Function Name..... | 107 | +| 3.11.7.5 | Secondary Charging Collection Function Name..... | 107 | +| 3.11.7.6 | WLAN Session Identifier..... | 107 | +| 3.11.7.7 | PDG Charging Identifier..... | 107 | +| 3.12 | Data related to Access Network Discovery and Selection Function (ANDSF)..... | 107 | +| 3.12.1 | General..... | 107 | +| 3.12.2 | Policy Information..... | 108 | +| 3.12.3 | Discovery Information..... | 108 | +| 3.12.4 | UE Location..... | 108 | +| 3.13 | Proximity Services (ProSe)..... | 108 | +| 3.13.1 | General..... | 108 | +| 3.13.2 | ProSe Subscription data..... | 108 | +| 3.13.2.1 | ProSe-Permission..... | 108 | +| 3.13.2.2 | PLMN-Allowed-ProSe..... | 109 | +| 3.13.3 | Application layer user ID..... | 109 | +| 3.13.4 | EPC ProSe User ID..... | 109 | +| 3.13.5 | ProSe Application ID..... | 109 | +| 3.13.6 | ProSe Application Code..... | 109 | +| 3.13.7 | Discovery Filter..... | 109 | +| 3.13.7.1 | Filter ID..... | 109 | +| 3.13.7.2 | ProSe Application Code..... | 109 | +| 3.13.7.3 | ProSe Application Mask..... | 109 | +| 3.13.7.4 | TTLTimer T4002..... | 109 | +| 3.13.8 | ProSe Function Identity..... | 109 | +| 3.13.9 | ProSe Metadata Index Mask..... | 110 | + +| | | | +|-----------|---------------------------------------------------------------------------------|-----| +| 3.13.10 | PC5-tech..... | 110 | +| 3.14 | Architecture Enhancements for Service Exposure (AESE)..... | 110 | +| 3.14.1 | General..... | 110 | +| 3.14.2 | SCEF-Reference-ID..... | 110 | +| 3.14.3 | SCEF-ID..... | 110 | +| 3.14.4 | Monitoring-Type..... | 110 | +| 3.14.5 | Maximum-Number-of-Reports..... | 110 | +| 3.14.6 | UE-Reachability-Configuration..... | 110 | +| 3.14.7 | Monitoring-Duration..... | 111 | +| 3.14.8 | Maximum-Detection-Time..... | 111 | +| 3.14.9 | Reachability-Type..... | 111 | +| 3.14.10 | Maximum-Latency..... | 111 | +| 3.14.11 | Maximum-Response-Time..... | 111 | +| 3.14.12 | MONTE-Location-Type..... | 111 | +| 3.14.13 | Accuracy..... | 111 | +| 3.14.14 | Association-Type..... | 112 | +| 3.14.15 | Charged-Party..... | 112 | +| 3.14.16 | Remaining-number-of-reports..... | 112 | +| 3.14.17 | Communication Pattern set..... | 112 | +| 3.14.17.1 | Periodic-Communication-Indicator..... | 112 | +| 3.14.17.2 | Communication-Duration-Time..... | 112 | +| 3.14.17.3 | Periodic-Time..... | 112 | +| 3.14.17.4 | Scheduled-Communication-Time..... | 112 | +| 3.14.17.5 | Stationary-Indication..... | 112 | +| 3.14.17.6 | Validity-Time..... | 113 | +| 3.14.18 | AESE-Subscription-Data..... | 113 | +| 3.14.19 | SCEF-Realm..... | 113 | +| 3.14.20 | External Identifier for Monitoring Event Configuration..... | 113 | +| 3.14.21 | External Group Identifier..... | 113 | +| 3.15 | Data related to WebRTC..... | 113 | +| 3.15.1 | Allowed WAF and/or WWSF Identity List..... | 113 | +| 3.16 | V2X Service (V2X)..... | 114 | +| 3.16.1 | General..... | 114 | +| 3.16.2 | V2X Subscription data for the network scheduled LTE sidelink communication..... | 114 | +| 3.16.2.1 | V2X-Permission..... | 114 | +| 3.16.2.2 | UE-PC5-AMBR..... | 114 | +| 3.16.2.3 | V2X-PC5-Allowed-PLMN..... | 114 | +| 3.16.3 | V2X Authorization data..... | 114 | +| 3.16.3.1 | V2X-Permission-in-VPLMN..... | 114 | +| 3.16.3.2 | V2X-Application-Server..... | 114 | +| 3.16.3.3 | PC5-RAT-Type..... | 114 | +| 3.16.4 | V2X Control Function Identity..... | 114 | +| 3.16.5 | V2X Subscription data for the network scheduled NR sidelink communication..... | 115 | +| 3.16.5.1 | V2X-Permission..... | 115 | +| 3.16.5.2 | UE-PC5-AMBR..... | 115 | +| 3.16.5.3 | V2X-PC5-Allowed-PLMN..... | 115 | +| 3.16.5.4 | UE-PC5-QoS..... | 115 | +| 4 | Summary of data stored in location registers..... | 115 | +| 5 | Accessing subscriber or PSI data..... | 115 | +| 5.1 | CS Network Access Mode Data Storage..... | 118 | +| 5.2 | PS Network Access Mode Storage (GPRS)..... | 120 | +| 5.2A | PS Network Access Mode Storage (EPS)..... | 123 | +| 5.2B | PS Network Access Mode Data (5GS)..... | 130 | +| 5.3 | IP Multimedia Service Data Storage..... | 132 | +| 5.4 | Generic Authentication Architecture Service Data Storage..... | 133 | +| 5.5 | I-WLAN Service Data Storage..... | 133 | +| 5.6 | MBMS Storage (EPS)..... | 135 | +| 5.7 | VPLMN Autonomous CSG Roaming Service Data Storage..... | 135 | +| 5.8 | Proximity Services (ProSe) Data Storage..... | 136 | +| 5.9 | Architecture Enhancements for Service Exposure storage (AESE)..... | 136 | + +5.10 Data related to Cellular IoT Control Plane Optimizations..... 137 +5.11 V2X Service (V2X) Data Storage..... 138 +**Annex A (informative): Old Change history..... 139** +**Annex B (informative): Change history..... 146** + +## Foreword + +This Technical Specification has been produced by the 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. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +--- + +## 0 Scope + +The present document provides details concerning information to be stored in the different entities storing data within a 3GPP network concerning mobile subscriber. A list of entities storing subscriber data is provided in clause 1. + +Clause 2 contains all details concerning the definition of the parameters, often given by reference to other specifications, and where the parameter is to be stored. + +Table 1 in clause 3 gives a summary overview and clause 4 identifies the reference information required for accessing the information. + +In this specification, if there is no specific indication, the following principles apply: + +- "SGSN" refers to an SGSN which may support the Gn and Gp interfaces or the S4 interface or both. +- "S4-SGSN" refers to an SGSN which only supports the S4 interface. +- "Gn/Gp-SGSN" refers to an SGSN which only supports the Gn and Gp interfaces. + +## 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)". +- [3] Void +- [4] Void +- [5] 3GPP TS 23.003: "Numbering, addressing and identification". +- [6] 3GPP TS 23.007: "Restoration procedures". +- [7] 3GPP TS 23.009: "Handover procedures". +- [8] 3GPP TS 23.012: "Location Management Procedures". +- [9] 3GPP TS 23.015: "Technical realization of Operator Determined Barring (ODB)". +- [10] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)". + +- [11] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service description; Stage 1". +- [12] 3GPP TS 23.067: "Enhanced Multi-Level Precedence and Preemption service (EMLPP); Stage 2". +- [13] Void +- [14] 3GPP TS 23.081: "Line identification supplementary services; Stage 2". +- [15] Void +- [16] Void +- [17] Void +- [18] 3GPP TS 23.085: "Closed User Group (CUG) Supplementary Service; Stage 2". +- [19] Void +- [20] Void +- [21] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service Description; Stage 2". +- [22] Void +- [23] Void +- [24] Void +- [25] 3GPP TS 23.135: "Multicall supplementary service; Stage 2" +- [26] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [27] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [28] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". +- [29] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface". +- [30] 3GPP TS 42.032: "Digital cellular telecommunications system (Phase 2+); Immediate Service Termination (IST) Service description - Stage 1". +- [31] 3GPP TS 43.020: "Digital cellular telecommunications system (Phase 2+); Security-related network functions". +- [32] 3GPP TS 43.035: "Digital cellular telecommunications system (Phase 2+); Immediate Service Termination (IST); Stage 2". +- [33] 3GPP TS 43.068: "Digital cellular telecommunications system (Phase 2+); Voice Group Call Service (VGCS); Stage 2". +- [34] 3GPP TS 43.069: "Digital cellular telecommunications system (Phase 2+); Voice Broadcast Service (VBS); Stage 2". +- [35] 3GPP TS 23.071: "Location Services (LCS); Functional Description; Stage 2". +- [36] GSM 12.03: "Digital cellular telecommunications system (Phase 2+) (GSM); Security management". +- [37] 3GPP TS 52.008: "GSM Subscriber and equipment trace". +- [38] ITU-T Recommendation Q.763: "Signalling System No. 7 - ISDN User Part formats and codes". +- [39] ANSI T1.113: "Signalling System No7 (SS7); Integrated Services Digital Network (ISDN) User Part" + +- [40] 3GPP TS 32.250: "Telecommunication Management; Charging management; Circuit Switched (CS) domain charging". +- [41] 3GPP TS 32.251: "Telecommunication Management; Charging management; Packet Switched (PS) domain charging". +- [42] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [43] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx interfaces; Signalling flows and message contents". +- [44] 3GPP TS 29.229: "Cx and Dx Interfaces based on the Diameter protocol; Protocol details". +- [45] IETF RFC 3261: "SIP: Session Initiation Protocol". +- [46] IETF RFC 2396: "Uniform Resource Identifiers (URI): Generic Syntax". +- [47] Void +- [48] IETF RFC 4282: "The Network Access Identifier". +- [49] 3GPP TS 33.203: "3G security; Access security for IP-based services". +- [50] 3GPP TS 23.002: "Network Architecture". +- [51] IETF RFC 3588: "Diameter Base Protocol". +- [52] 3GPP TS 33.102: "3G Security; Security Architecture". +- [53] 3GPP TS 23.218: "IP Multimedia (IM) session handling; IM call model; Stage 2". +- [54] 3GPP TS 29.328: "IP Multimedia Subsystem (IMS) Sh interface signalling flows and message contents". +- [55] Void +- [56] 3GPP TS 23.271: "Location Services (LCS); Functional description; Stage 2". +- [57] 3GPP TS 23.221: "Architectural requirements ". +- [58] 3GPP TS 33.220: "Generic Authentication Architecture (GAA); Generic bootstrapping architecture". +- [59] 3GPP TS 29.109: "Zh and Zn Interfaces based on the Diameter protocol; Protocol details". +- [60] IETF RFC 3548: "The Base16, Base32, and Base64 Data Encodings". +- [61] 3GPP TS 23.251: "Network Sharing; Architecture and Functional Description". +- [62] 3GPP TS 23.234, Release 12: "3GPP System to WLAN Interworking System Description, Stage 2". +- [63] 3GPP TS 29.234, Release 11: "3GPP system to Wireless Local Area Network (WLAN), Stage 3". +- [64] 3GPP TS 32.422: "Subscriber and equipment trace: Trace control and configuration management". +- [65] 3GPP TS 32.421: "Subscriber and equipment trace: Trace concepts and requirements". +- [66] 3GPP TS 32.252, Release 11: "Telecommunication management; Charging management; Wireless Local Area Network (WLAN) charging". +- [67] 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging applications". +- [68] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP – stage 3" +- [69] IETF RFC 2617: "HTTP Authentication: Basic and Digest Access Authentication". +- [70] 3GPP TS 23.018: "Basic call handling; Technical realization". + +- [71] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services" +- [72] Void +- [73] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture" +- [74] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access" +- [75] 3GPP TS 29.274: "Evolved GPRS Tunneling Protocol for Control Plane" +- [76] 3GPP TS 32.298: "Telecommunication Management; Charging Management; Charging Data Record (CDR) parameter classification." +- [77] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses " +- [78] 3GPP TS 29.273: "3GPP EPS AAA Interfaces" +- [79] 3GPP TS 29.275: "Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunneling protocols" +- [80] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC), Stage 2" +- [81] 3GPP TS 29.272: "MME Related Interfaces Based on Diameter Protocol" +- [82] 3GPP TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3" +- [83] 3GPP TS 29.305: "InterWorking Function (IWF) between MAP based and Diameter based interfaces" +- [84] 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched (PS) domain charging" +- [85] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description; Stage 2". +- [86] 3GPP TS 24.312: "Access Network Discovery and Selection Function (ANDSF) Management Object (MO)". +- [87] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2". +- [88] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [89] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions". +- [90] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points". +- [91] 3GPP TS 23.139: "3GPP System-Fixed Broadband Access Network Interworking; Stage 2". +- [92] 3GPP TS 33.234, Release 12: "WLAN Interworking Security". +- [93] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture ". +- [94] Void +- [95] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE\_LTE); stage 2". +- [96] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [97] 3GPP TS 36.323: "Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) Specification". +- [98] 3GPP TS 23.303: "Proximity-based services (ProSe); stage 2". + +- [99] 3GPP TS 29.344: "Proximity-services (ProSe) Function to Home Subscriber Server (HSS) aspects; Stage 3". +- [100] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3". +- [101] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network; (E-UTRAN); S1 Application Protocol (S1AP)". +- [102] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [103] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications". +- [104] IETF RFC 4995: "The ROBust Header Compression (ROHC) Framework". +- [105] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [106] 3GPP TS 29.128: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) interfaces for interworking with packet data networks and applications ". +- [107] 3GPP TS 23.285: "Architecture enhancements for V2X services; Stage 2". +- [108] 3GPP TS 29.388: "V2X Control Function to V2X Control Function to Home Subscriber Server (HSS) aspects (V4)". +- [109] 3GPP TS 29.389: "Inter-V2X Control Function Signalling aspects (V6); Stage 3". +- [110] IETF RFC 6696: "EAP Extensions for the EAP Re-authentication Protocol (ERP)". +- [111] 3GPP TS 24.323: "3GPP IP Multimedia Subsystem (IMS) service level tracing management object (MO)". +- [112] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [113] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".. +- [114] 3GPP TS 29.503: "5G System; Unified Data Management Services" +- [115] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2". +- [116] 3GPP TS 33.501: "Security Architecture and Procedures for 5G System". +- [117] 3GPP TS 35.206: "An example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 2: Algorithm specification". +- [118] 3GPP TS 35.231: "A second example algorithm set for the 3GPP authentication and key generation functions f1, f1\*, f2, f3, f4, f5 and f5\*; Document 1: Algorithm specification ". +- [119] 3GPP TS 29.505: "5G System; Usage of the Unified Data Repository services for Subscription Data ". +- [120] 3GPP TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)". +- [121] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2". + +## 0.2 Abbreviations + +For the purposes of the present document, the abbreviations listed in 3GPP TR 21.905 [1] apply. + +| | | +|------|-------------------------| +| NCGI | NR Cell Global Identity | +| NR | New Radio | +| RG | Residential Gateway | + +# 1 Introduction + +## 1.1 Definition + +The term subscriber data is used to designate all information associated with a subscription which is required for service provisions, identification, authentication, routing, call handling, GPRS mode transmission, charging, subscriber tracing, operation and maintenance purposes. Some subscriber data are referred to as permanent subscriber data, i.e. they can only be changed by administration means. Other data are temporary subscriber data which may change as a result of normal operation of the system. + +Unless shown to be conditional, all data items are considered to be mandatory. + +## 1.2 Storage facilities + +This specification considers subscriber data stored by the following types of network functions: + +- Home subscriber server (HSS) which contains all permanent subscriber data and all relevant temporary subscriber data to support the call control and session management entities of the different Domains and Subsystems. +- Home location register (HLR) which contains all permanent subscriber data and all relevant temporary subscriber data for all mobile subscribers permanently registered in the HLR for CS and PS Domains. + +NOTE 0: according to 3GPP TS 23.002 [50] HLR is a subset of the HSS functionality. + +- CSG subscriber server (CSS) which contains Closed Subscriber Group information data for inbound roaming UEs to enable VPLMN autonomous CSG roaming in CS and PS domains. +- Visitor location register (VLR) which contains all subscriber data required for call handling and other purposes for mobile subscribers currently located in the area controlled by the VLR. +- Serving GPRS Support Node (SGSN) which contains all subscriber data required for GPRS mode transmission and other purposes for mobile subscribers currently located in the area controlled by the SGSN. +- Gateway GPRS Support Node (GGSN) which contains all subscriber data required for GPRS mode transmission for mobile subscribers using any service provided by the GGSN. +- Mobility Management Entity (MME) which contains all subscriber data required for EPS mode transmission and other purposes for mobile subscribers currently located in the area controlled by the MME. +- Serving GW (S-GW) which contains all subscriber data required for EPS mode transmission for mobile subscribers currently served by the S-GW. +- PDN GW (P-GW) which contains all subscriber data required for EPS mode transmission for mobile subscribers using any service provided by the P-GW. +- ePDG which contains all subscriber data required for EPS mode transmission for mobile subscribers currently served by the ePDG via a non 3GPP access. +- Gateway Mobile Location Center (GMLC) which contains all subscriber data required for external clients of the Location Services (LCS). +- In GSM, Serving Mobile Location Center (SMLC) which contains all LMU data required to manage location measurements in LMUs. + +NOTE 1: A type A LMU is a network entity that shares many of the attributes of an MS including subscription data in the HLR and identification using an IMSI. + +- Serving Call Session Control Function (S-CSCF) which handles the session states in the IP Multimedia (IM) Subsystem. Further definition of the S-CSCF is provided in 3GPP 23.228 [42]. + +- SUPL (Secure User Plane Location) Location Platform (SLP) provides user location information to the ProSe Function. Further information is provided in 3GPP TS 23.303 [98]. +- ProSe Function is the logical function that is used for network related actions required for Proximity services more details are provided in 3GPP TS 23.303 [98]. +- ProSe Application Server stores EPC ProSe User IDs and ProSe Function IDs and performs the mapping of Application Layer User IDs and EPC ProSe User IDs (see 3GPP TS 23.303 [98]). +- V2X Control Function is the logical function that is used for network related actions required for V2X services more details are provided in 3GPP TS 23.285 [107]. +- UDM, AMF, SMF, SMSF, AUSF and NEF in 5G System (see 3GPP TS 23.501 [112] and 3GPP TS 23.502 [113]). + +NOTE 2: Whether a node stores data for later usage in the UDR (externally) is not reflected, the description only reflects that the node holds data logically. Whether storage of data is performed internally or externally is out of scope of this specification. + +In addition, subscriber data may also be stored in the following functional unit: + +- Group Call Register (GCR) which contains all data required for configuration, set-up and handling of voice group and voice broadcast calls. This encompasses subscribers identities (mobile as well as fixed network) who are nominated as dispatchers for one or several groups within the area controlled by the GCR. + +NOTE 3: The data stored in the GCR is not strictly "subscriber data". Description of GCR data is therefore out of scope of this specification and is covered in the corresponding specifications for enhanced Multi Level Precedence and Pre-emption Service (eMLPP), Voice Group Call Service (VGCS) and Voice Broadcast Service (VBS) instead (3GPP TS 23.067 [12], 3GPP TS 43.068 [33] and 3GPP TS 43.069 [34]). + +NOTE 4: The MME, SGSN and ePDG Emergency Configuration Data, which are applied for all emergency bearer services, are not subscriber data and therefore out of the scope of this specification. See 3GPP TS 23.401 [74], 3GPP TS 23.060 [21] and 3GPP TS 23.402 [77]. + +## 1.3 Subscriber data in other functional units + +The individual Subscriber Authentication Key Ki defined in 3GPP TS 43.020 [31] is stored in the Authentication Centre (AuC); it is also stored in the SIM and therefore available in the MS. Version numbers of algorithms A3 and A8 may also be stored in the AuC. + +Bootstrapping Server Function (BSF) handles subscriber's bootstrapping information after bootstrapping procedure in Generic Authentication Architecture (GAA) system. A bootstrapping procedure creates security association between an UE and a BSF. Using the stored user's bootstrapping information and the security association the BSF can provide security services to network application functions (NAF) contacted by the UE. Functions of the BSF are defined in 3GPP TS 33.220 [58] and 3GPP TS 29.109 [59]. + +NOTE: It is for further study whether or not other types of functional units containing mobile subscriber parameters are to be included in this specification. Such units could include encryption key distribution centres, maintenance centres, etc. + +## 1.4 Subscriber data in WLAN-IW functional units + +This specification considers subscriber data stored in the following types of functional unit for I-WLAN: + +- 3GPP AAA Server which contains all subscriber data necessary to maintain WLAN Direct IP Access and WLAN 3GPP IP Access. +- 3GPP AAA Proxy which contains subscriber data necessary to perform AAA proxy functionality in the VPLMN and to provide charging inter operator settlement functionality. +- Packet Data Gateway (PDG) which contains all subscriber data necessary to manage WLAN 3GPP IP Access tunnels. + +- WLAN Access Gateway (WAG) which contains all subscriber data necessary to manage a per user firewall between the WLAN-AN and PLMN and to perform per tunnel charging. + +--- + +## 2 Definition of subscriber data for CS and PS domain + +### 2.1 Data related to subscription, identification and numbering + +#### 2.1.1 Data defining the subscription profile + +##### 2.1.1.1 International Mobile Subscriber Identity (IMSI) + +International Mobile Subscriber Identity (IMSI) is defined in 3GPP TS 23.003 [5]. + +IMSI is permanent subscriber data. IMSI is stored in HLR, HSS, CSS, VLR, SGSN, S4-SGSN, GGSN, MME, S-GW, P-GW, ePDG, SCEF and SMLC. For Anonymous Access, IMSI is not used in SGSN nor in GGSN. The IMSI serves as the root of the subscriber data pseudo-tree. + +For emergency attached UEs without IMSI (e.g; UICClassless UE) or with an unauthenticated IMSI, IMEI is used instead of IMSI to identify the UE. + +##### 2.1.1.2 Network Access Mode (NAM) + +The Network Access Mode (NAM) defines if the subscriber is registered to get access to the CS domain (non-GPRS/EPS), to the PS domain (GPRS/EPS) or to both domains using 3GPP access networks. NAM describes the first level of the subscriber data pseudo-tree below the IMSI root. It is permanent subscriber data stored in the HSS/HLR and the SGSN with the Gs interface option, and the MME with the SGs interface option. + +##### 2.1.1.3 IMSI Unauthenticated indicator + +For an emergency attached UE with an unauthenticated IMSI, the IMSI Unauthenticated indicator is set to reflect that the IMSI is unauthenticated. See 3GPP TS 23.401 [74], 3GPP TS 23.060 [21] and 3GPP TS 23.402 [77]. + +The IMSI Unauthenticated indicator is a temporary subscriber data stored in the MME, S-GW, P-GW, SGSN, S4-SGSN, GGSN and ePDG. + +#### 2.1.2 Mobile Station International ISDN Number (MSISDN) + +Mobile Station ISDN Number (MSISDN) is defined in 3GPP TS 23.003 [5]. + +The MSISDN is permanent subscriber data and is conditionally stored in HLR, VLR, SGSN, GGSN, HSS, MME, S-GW, P-GW, SCEF, 3GPP AAA Server and ePDG (for GTP-based S2b only), and is optionally stored in CSS. If the multinumbering option applies, the MSISDN stored in the VLR and in the Gn/Gp-SGSN is the Basic MSISDN, see clause 2.1.3.1. + +#### 2.1.3 MSISDNs for multinumbering option + +If the HPLMN allocates different MSISDNs for different Basic Services (see 3GPP TS 29.007 [28]), these numbers are conditionally stored as permanent data in the HLR. + +##### 2.1.3.1 The Basic MSISDN indicator + +The Basic MSISDN is defined in 3GPP TS 23.012 [8]. The Basic MSISDN indicator marks the MSISDN to be used as Basic MSISDN. + +It is permanent subscriber data stored conditionally in the HLR. + +### 2.1.3.2 The MSISDN-Alert indicator + +The MSISDN-Alert is defined in 3GPP TS 23.040 [10]. The MSISDN-Alert indicator marks the MSISDN to be used as MSISDN-Alert. + +It is permanent subscriber data stored conditionally in the HLR. + +### 2.1.4 Temporary mobile subscriber identity (TMSI) + +Temporary mobile subscriber identity (TMSI) is defined in 3GPP TS 23.003 [5]. + +The TMSI is temporary subscriber data and is conditionally stored in the VLR. + +### 2.1.5 Packet-Temporary Mobile Subscriber Identity (P-TMSI) + +Packet-Temporary Mobile Subscriber Identity (P-TMSI) is defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 23.060 [11]. P-TMSI is accompanied by the P-TMSI Signature, see clause 2.3.7. + +The P-TMSI is temporary subscriber data and is conditionally stored in the SGSN. + +### 2.1.6 Temporary Link Layer Identifier (TLLI) + +Temporary Link Layer Identifier (TLLI) is defined in 3GPP TS 23.003 [5]. It is derived from the P-TMSI by the MS and occurs in the variants Local TLLI and Foreign TLLI. The TLLI is temporary subscriber data and is conditionally stored in the SGSN. For use of TLLI see 3GPP TS 23.060 [11]. + +### 2.1.7 Random TLLI + +Random TLLI is chosen randomly by the MS. It is defined in 3GPP TS 23.003 [5]. Random TLLI is short living temporary subscriber data and is conditionally stored in the SGSN. For use of Random TLLI see 3GPP TS 23.060 [11]. + +A Random TLLI may be used if no valid P-TMSI is available. + +### 2.1.8 Local Mobile Station Identity (LMSI) + +Local Mobile Station Identity (LMSI) is defined in 3GPP TS 23.003 [5]. The LMSI is temporary subscriber data. The LMSI may be stored in the VLR; if it is received in the HLR it must be stored there. + +### 2.1.9 International Mobile Equipment Identity (IMEI) + +International Mobile Equipment Identity (IMEI) is defined in 3GPP TS 23.003 [5]. The IMEI is temporary subscriber data and is conditionally stored in the HSS, SGSN, S4-SGSN, GGSN, MME, SGW, PGW, ePDG and 3GPP AAA Server. + +### 2.1.10 External Identifier Set + +The External Identifier set contains one or more External Identifier as defined in 3GPP TS 23.003 [5]. + +Any one of the External Identifier from the IMSI's External Identifier Set shall uniquely identify a single subscriber (IMSI). + +The External Identifier Set is permanent subscriber data and is stored in the HSS and conditionally in the SCEF. + +### 2.1.11 UE radio capability ID + +The UE radio capability ID is defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 23.401 [74]. + +The UE radio capability ID is temporary subscriber data and is conditionally stored in the MME. + +## 2.2 Data related to Mobile Station types + +### 2.2.1 Mobile Station Category + +Mobile Station Category has a structure identical to that of "Calling Party's Category" defined in ISUP (ITU-T Recommendation Q.763 [38]). + +The following values of category shall be supported: + +- ordinary subscriber. + +The category is assigned per IMSI. + +Mobile Station Category is permanent subscriber data and is stored in HLR and VLR. + +### 2.2.2 LMU Identifier (GSM only) + +The LMU identifier is part of the subscriber data for a Type A LMU, when associated with an NSS based SMLC, and serves to distinguish a Type A LMU from a normal MS. + +### 2.2.3 International Mobile Equipment Identity and Software Version (IMEISV) + +International Mobile Equipment Identity and Software Version (IMEISV) is defined in 3GPP TS 23.003 [5]. The IMEISV is temporary subscriber data and is conditionally stored in the VLR, SGSN, HLR, S4-SGSN, GGSN, MME, SGW, PGW, ePDG and 3GPP AAA Server. + +## 2.3 Data related to authentication and ciphering + +### 2.3.1 Random Number (RAND), Signed Response (SRES) and Ciphering Key (Kc) + +Random Number (RAND), Signed Response (SRES) and Ciphering Key (Kc) form a triplet vector used for authentication and encryption as defined in 3GPP TS 43.020 [31]. + +For GSM users, triplet vectors are calculated in the 2G AuC and provided to the 2G HLR (see GSM 12.03 [36]), and for UMTS users triplet vectors are derived from quintuplet vectors in the 3G HLR or 3G VLR, if needed (see 3GPP TS 33.102 [52]). + +A set of up to 5 triplet values are sent from the 2G HLR to the VLR and the SGSN on request. These data are temporary subscriber data conditionally stored in the VLR and the SGSN. + +### 2.3.2 Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key (IK) and Authentication Token (AUTN), KASME + +Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key (IK) and Authentication Token (AUTN) form a quintuplet vector used for user authentication, data confidentiality and data integrity as defined in 3GPP TS 33.102 [52]. + +Random Challenge (RAND), Expected Response (XRES), Key for Access Security Management Entity (KASME) and Authentication Token (AUTN) form an EPS vector used for user authentication, data confidentiality and data integrity as defined in 3GPP TS 33.401 [73]. + +When both HLR and VLR or SGSN are 3G, a set of quintuplet vectors are calculated in the AuC, and up to 5 quintuplets are sent from the HLR to the VLR and to the SGSN on request (see 3GPP TS 29.002 [27]). These data are temporary subscriber data conditionally stored in the HLR, the VLR and the SGSN. + +When the HLR is 2G and the VLR or SGSN are 3G, quintuplet vectors are derived by the 3G VLR or SGSN from the received triplet vectors from the HLR, if needed (see 3GPP TS 33.102 [52]). + +### 2.3.3 The Ciphering Key Sequence Number (CKSN) + +The Ciphering Key Sequence Number (CKSN) is used to ensure GSM authentication information ( $K_c$ ) consistency between the MS and the VLR and between the MS and the SGSN. + +CKSN and its handling are defined in 3GPP TS 24.008 [26] and 3GPP TS 43.020 [31]. It is a temporary subscriber data and is stored in the VLR and in the SGSN. + +### 2.3.4 The Key Set Identifier (KSI) + +The Key Set Identifier (KSI) is used to ensure UMTS authentication information (CK and IK) consistency between the MS and the VLR and between the MS and the SGSN. + +For EPS the Key Set Identifier (KSI also noted $KSI_{ASME}$ ) is used to ensure EPS authentication information ( $K_{ASME}$ ) consistency between the MS and the MME. + +KSI and its handling are defined in UMTS TS 24.008 [26] and UMTS TS 33.102 [52]. It is temporary subscriber data and is stored in the VLR and the SGSN. + +$KSI_{ASME}$ and its handling are defined in 3GPP TS 23.401[74]. It is temporary subscriber data and is stored in the MME. + +### 2.3.5 Selected Ciphering Algorithm + +Selected Ciphering Algorithm is defined in 3GPP TS 23.060 [21]. + +Selected Ciphering Algorithm is temporary subscriber data stored in the SGSN. + +### 2.3.6 Current $K_c$ + +Current $K_c$ is defined in 3GPP TS 43.020 [31]. + +Current $K_c$ is temporary subscriber data stored in the SGSN. + +### 2.3.7 P-TMSI Signature + +P-TMSI Signature is defined in TSs 3GPP TS 23.003 [5] and 3GPP TS 23.060 [21]. It is used for identification checking purposes. + +P-TMSI Signature is temporary subscriber data and is conditionally stored in the SGSN. + +### 2.3.8 Access Network Identity (ANID) + +Access Network Identity is defined in TSs 3GPP TS 24.302 [82] and 3GPP TS 29.273 [78]. + +ANID is temporary subscriber data stored in HSS and 3GPP AAA server. + +### 2.3.9 Key Status + +Key Status is defined in 3GPP TS 25.413 [120]. + +Key Status is temporary subscriber data stored in VLR and SGSN. + +## 2.4 Data related to roaming + +### 2.4.1 Mobile Station Roaming Number (MSRN) + +Mobile Station Roaming Number (MSRN) is defined in 3GPP TS 23.003 [5]. + +NOTE: There may be more than one MSRN simultaneously per IMSI. + +The MSRN is short-lived temporary subscriber data stored in the VLR. + +### 2.4.2 Location Area Identification (LAI) + +Location Area Identification (LAI) is defined in 3GPP TS 23.003 [5]. + +The LAI is temporary subscriber data and is stored in the VLR. + +### 2.4.3 Routing Area Identification (RAI) + +Routing Area Identification (RAI) is defined in 3GPP TS 23.003 [5]. + +The RAI is temporary subscriber data and is stored in the SGSN. + +### 2.4.4 Void + +### 2.4.5 VLR number + +VLR number is defined in 3GPP TS 23.003 [5]. + +The VLR number is temporary subscriber data and is stored in the HLR. Absence of the VLR number in HLR indicates that the mobile station is deregistered for non-GPRS or the subscriber has not a non-GPRS subscription in the HLR. The VLR number is stored in the SGSN with the Gs interface option. For usage of the VLR number in SGSN, please refer to 3GPP TS 23.060 [21]. + +The VLR number is temporary subscriber data and is stored in the CSS. Absence of the VLR number in the CSS indicates that no subsequent update of the CSG subscription information is needed at the VLR upon CSG subscription change. + +### 2.4.6 MSC number + +MSC number is defined in 3GPP TS 23.003 [5]. + +The MSC number is temporary subscriber data and is stored in the HLR and conditionally in the VLR. For absence of the MSC number in the HLR, the remarks on VLR number apply accordingly, see clause 2.4.5. + +### 2.4.7 HLR number + +HLR number is defined in 3GPP TS 23.003 [5]. + +The HLR number may be stored in the VLR and Gn/Gp-SGSN. It is received as a mandatory parameter in the updating location accepted message. This data may be needed to retrieve subscribers to be restored after HLR reset. + +The HLR number is temporary subscriber data and may optionally be stored in the VLR and Gn/Gp-SGSN. + +### 2.4.8 GSN number + +#### 2.4.8.0 General + +GSN number occurs as SGSN number and as GGSN number. + +#### 2.4.8.1 SGSN number + +SGSN number is the SS7 address of the SGSN . It is defined in 3GPP TS 23.003 [5]. + +The SGSN number is temporary subscriber data and is stored in the HLR for a GPRS subscription. It is conditionally stored in the VLR if the Gs interface is installed. Absence of the SGSN number in the HLR indicates that the mobile station is deregistered for GPRS or the subscriber has no GPRS subscription in the HLR. Absence of the SGSN number in the VLR indicates that there is no association between the VLR and the SGSN for this MS. The SGSN number is to be distinguished from the SGSN address described in clause 2.13.10. + +The SGSN number is temporary subscriber data and is stored in the CSS. Absence of the SGSN number in the CSS indicates that no subsequent update of the CSG subscription information is needed at the SGSN upon CSG subscription change. + +#### 2.4.8.2 GGSN number + +GGSN number is the SS7 address of the GGSN .It is defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 23.060 [21]. It is contained in the GGSN-list stored in the HLR and does not appear as separate subscriber data. Cf. clause 2.13.11. + +#### 2.4.8.3 IWF number + +IWF number is the SS7 address of the IWF. It has the same format as a "VLR number" or "SGSN number" which are defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 29.305 [83]. + +### 2.4.9 MLC number + +The MLC number occurs as an SMLC number and as a GMLC number. + +#### 2.4.9.1 SMLC number (GSM only) + +The SMLC number is the E.164 address of an NSS based SMLC. + +The SMLC number is permanent data that may be stored in an MSC in association with either a set of IMSIs belonging to LMUs controlled by the SMLC or a set of cell identifiers belonging to the geographic area served by the SMLC. + +#### 2.4.9.2 GMLC number + +The GMLC number is the E.164 address of the GMLC. One or more GMLC numbers may be stored in the MS subscriber data in the HLR and downloaded to the VLR and SGSN. These GMLC numbers identify the GMLCs for the particular MS from which a location request for this MS may be confined for particular LCS clients. + +### 2.4.10 Subscription restriction + +Subscription restriction is a parameter indicating whether or not certain restrictions apply to the subscription. The parameter takes either of the following values (see also GSM 02.13 [36]): + +- accessible area for service; +- all GSM PLMNs; +- one national and all foreign GSM PLMNs; +- regionally restricted (part of a GSM PLMN in one country); +- regionally restricted plus all other GSM PLMNs. + +The HLR/HSS associates location updating information with subscription restriction. It deregisters the MS if the PLMN is not allowed and sets: + +- the MSC area restricted flag if the MSC area is not allowed, see clause 2.4.12; + +- SGSN area restricted flag if the SGSN area is not allowed, see clause 2.4.14. + +Handling of Regionally Restricted Subscription is defined in clause 2.4.11. By operator agreement, regional restriction in parts of different GSM PLMNs is also possible. + +The subscription restriction is permanent subscriber data and is stored in the HLR. + +## 2.4.11 Regional Subscription Information + +If a mobile subscriber has a regional subscription, the HLR/HSS shall store a list of up to ten Regional Subscription Zone Identities (RSZIs) per Network Destination Code (NDC) of the PLMN involved. The structure of RSZI is defined in 3GPP TS 23.003 [5]; since it is composed of the PLMN identification (CC NDC) and the Zone Code it is sufficient to store the Zone Code List per CC NDC. + +On updating the MME, VLR or the SGSN, the HLR/HSS identifies the VPLMN and NDC given by the VLR or SGSN number or VPLMN-Id and transfers the pertaining Zone Code List to the VLR or SGSN or MME. The VLR or SGSN or MME derives from the Zone Code List the allowed and not allowed MSC or SGSN or MME areas and location areas; it sets the "LA not allowed flag" should the target LAI of the mobile station be excluded, and it informs the HLR/HSS should the MSC or SGSN or MME area be excluded. Signalling of cause value "location area not allowed" towards the mobile station is defined in TSs 3GPP TS 29.002 [27] and 3GPP TS 24.008 [26]. + +### 2.4.11.1 RSZI lists + +The RSZI lists are permanent subscriber data stored conditionally in the HLR/HSS. + +### 2.4.11.2 Zone Code List + +The VLR and the SGSN and the MME shall store as permanent and conditional subscriber data at least those Zone Codes by which they are affected. + +## 2.4.12 MSC area restricted flag + +MSC area restricted flag is a parameter which can take either of the following values: + +- MSC area restricted; +- MSC area not restricted. + +The parameter is set in the HLR during updating of the VLR. Handling of unsupported services and information received from the VLR based on national roaming or regionally restricted subscription (clause 2.4.11) determine its value. The parameter contributes to the "MS Not Reachable" state for handling of terminating traffic in the HLR. The default value is "MSC area not restricted". + +The MSC area restricted flag is temporary subscriber data and is contained in the HLR. + +## 2.4.13 LA not allowed flag + +The LA not allowed flag is set in the VLR depending on National Roaming, Regionally Restricted Subscription and Roaming Restriction Due To Unsupported Feature, see 3GPP TS 29.002. It is applied to restrict service on a location area basis. + +The LA not allowed flag is temporary subscriber data stored in the VLR. + +## 2.4.14 SGSN area restricted flag + +SGSN area restricted flag is a parameter which can take either of the following values: + +- SGSN area restricted; +- SGSN area not restricted. + +The parameter is set in the HLR during updating of the SGSN. Handling of unsupported services and information received from the SGSN based on national roaming or regionally restricted subscription (clause 2.4.11) determine its value. The parameter contributes to the "MS Not Reachable" state for handling of terminating traffic in the HLR. The default value is "SGSN area not restricted". + +The SGSN area restricted flag is temporary subscriber data and is contained in the HLR. + +#### 2.4.14a RA not allowed flag + +The RA not allowed flag is set in the SGSN depending on National Roaming, Regionally Restricted Subscription and Roaming Restricted in the SGSN Due To Unsupported Feature, see 3GPP TS 29.002. It is applied to restrict service on a routing area basis. + +The RA not allowed flag is temporary subscriber data stored in the SGSN. + +#### 2.4.14b TA not allowed flag + +The TA not allowed flag is set in the MME depending on National Roaming, Regionally Restricted Subscription and Roaming Restricted in the MME Due To Unsupported Feature, see 3GPP TS 29.272[81]. It is applied to restrict service on a tracking area basis. + +The TA not allowed flag is temporary subscriber data stored in the MME. + +#### 2.4.15 Service restriction data induced by roaming + +If in the course of roaming or at updating of the VLR or SGSN or MME the HLR/HSS is informed that the VLR or SGSN or MME does not support certain sensitive services or features, or, the HLR/HSS is informed in data request that the VLR or the SGSN or the MME supports only specific services, features or phases which do not correspond to subscribed services, features or phases, the HLR/HSS takes appropriate measures to restrict service for the mobile station in that VLR or SGSN or MME by setting and sending network induced replacing services such as available services, features or phases, barring programs or the roaming restriction for the MSC or SGSN or MME area. + +These network-induced data have to be kept separate in the HLR, and where possible as discussed below in the VLR, from the permanent subscriber data of the call barring supplementary services, from the barring related data that can be modified by the subscriber or from the permanent regional subscription data. + +These network-induced data have to be kept separate in the HLR/HSS, and where possible as discussed below in the SGSN and MME, from the permanent regional subscription data. + +The network induced data take precedence over the subscriber data of the user where they are in conflict. If, in the course of roaming, restrictions caused by a service are lifted, the original subscriber data have to be re-installed both in HLR, in SGSN, in MME and in VLR when applicable, regarding any remaining restrictions due to other service replacements. + +All network-induced restriction data are temporary subscriber data. + +For ODB, 3GPP TS 23.015 [9] recommends mainly barring programs to replace this feature. The replacing barring data are conditionally stored in the HLR and VLR. In the VLR they cannot be distinguished from the permanent supplementary services data with the available signalling means, and no additional storage is needed. Interrogation shall reflect in both HLR and VLR the valid setting of the replacing temporary data; to prevent interference with Subscriber Controlled Input and to inform the customer on the restriction, the "control of barring services" subscription option is also temporarily set to the value "by the service provider". + +CUG is also replaced by Outgoing Call Barring as described in 3GPP TS 23.085 [18]. + +Roaming restriction in the MSC area due to unsupported features is used to replace AoCC, see 3GPP TS 23.086, and Zone Codes for regional subscription, see clause 2.4.11 and 3GPP TS 29.002. A flag in the HLR and the VLR, see clause 2.4.15.2, collects the sources of network-induced roaming restriction which are also kept separate by the HLR. + +Roaming restriction in the SGSN area due to unsupported features is used to replace Zone Codes for regional subscription, see clause 2.4.11 and 3GPP TS 29.002. A flag in the HLR and the SGSN, see clause 2.4.15.3, collects the sources of network-induced roaming restriction which are also kept separate by the HLR. + +Roaming restriction in the MME area due to unsupported features is used to replace Zone Codes for regional subscription, see clause 2.4.11 and 3GPP TS 29.272[81]. A flag in the HSS and the MME, see clause 2.4.15.3a, collects the sources of network-induced roaming restriction which are also kept separate by the HSS. + +#### 2.4.15.1 ODB-induced barring data + +ODB-induced barring data are temporary data stored conditionally in the HLR; they include the necessary replacing barring programs for outgoing and incoming calls depending on the ODB profile. The subscription option "control of barring services" is set to "by the service provider". The corresponding barring supplementary services for outgoing calls are set by the HLR and sent to the VLR. + +#### 2.4.15.2 Roaming restriction due to unsupported feature + +Roaming restriction due to unsupported feature is a parameter which indicates that one or several services or features are not supported by the MSC, resulting in roaming restriction in the MSC area. It can take either of the following values: + +- roaming restricted; +- roaming not restricted. + +The parameter governs the "LA not allowed flag" in the VLR (see clause 2.4.13) and the "MSC area restricted flag" in the HLR (see clause 2.4.12); see also 3GPP TS 29.002. + +The flag "roaming restriction due to unsupported feature" is temporary subscriber data stored in the VLR and in the HLR. + +#### 2.4.15.3 Roaming restricted in the SGSN due to unsupported feature + +Roaming restricted in the SGSN due to unsupported feature is a parameter which indicates that one or several services or features are not supported by the SGSN, resulting in roaming restriction in the SGSN area. It can take either of the following values: + +- roaming restricted; +- roaming not restricted. + +The parameter governs the "RA not allowed flag" in the SGSN (see clause 2.4.14a) and the "SGSN area restricted flag" in the HLR (see clause 2.4.14); see also 3GPP TS 29.002. + +The flag "roaming restricted in the SGSN due to unsupported feature" is temporary subscriber data stored in the SGSN and in the HLR. + +#### 2.4.15.3a Roaming restricted in the MME due to unsupported feature + +Roaming restricted in the MME due to unsupported feature is a parameter which indicates that one or several services or features are not supported by the MME, resulting in roaming restriction in the MME area. It can take either of the following values: + +- roaming restricted; +- roaming not restricted. + +The parameter governs the "TA not allowed flag" in the MME (see clause 2.4.14b). + +The flag "roaming restricted in the MME due to unsupported feature" is temporary subscriber data stored in the MME and in the HSS. + +### 2.4.16 Cell Global ID or Service Area ID + +The Cell Global ID or Service Area ID indicates the cell global identity of the cell in GSM (see 3GPP TS 23.003 [5]) or the service area identification of the service area in UMTS (see 3GPP TS 23.003 [5]) in which the MS is currently in + +radio contact or in which the MS was last in radio contact. The VLR and SGSN shall update the stored Cell Global ID or Service Area ID at establishment of every radio connection. + +The cell ID is temporary subscriber data stored in the VLR and SGSN. It is conditional data, the VLR and SGSN shall store it whenever the subscriber data is marked as confirmed by radio contact. + +The Cell Global ID or Service Area ID is temporary subscriber data stored in SGSN and GGSN/PDN-GW. + +## 2.4.16A E-UTRAN Cell Global ID + +The E-UTRAN Cell Global ID indicates the cell global identity of the cell in EPS (see 3GPP TS 23.003 [5]) in which the MS is currently in radio contact or in which the MS was last in radio contact. + +The E-UTRAN Cell Global ID is temporary subscriber data stored in MME, PDN-GW and, when received via the SGs interface, in the VLR. + +## 2.4.16B NR Cell Global Identity (NCGI) + +The NR Cell Global Identity indicates the cell global identity of the cell in 5GS (see 3GPP TS 23.003 [5]) in which the UE is currently in radio contact or in which the UE was last in radio contact. + +The NR Cell Global Identity is temporary subscriber data stored in AMF, SMF. + +## 2.4.17 Localised Service Area Information + +If a mobile subscriber has a localised service area subscription, the HLR shall store a list of up to 20 Localised Service Area Identities (LSA IDs) per PLMN. The structure of LSA ID is defined in 3GPP TS 23.003 [5]. + +On updating the VLR or the Gn/Gp-SGSN, the HLR identifies the VPLMN given by the VLR or SGSN number and transfers the applicable LSA ID List to the VLR or Gn/Gp-SGSN. The VLR or Gn/Gp-SGSN derives from the LSA ID List the allowed LSA(s), priority of each LSA, the preferential access indicator, the active mode support indicator and active mode indication and the "LSA only access" indicator. + +### 2.4.17.1 LSA Identity + +LSA Identity (LSA ID) is defined in 3GPP TS 23.003 [5]. The element uniquely identifies a LSA. + +### 2.4.17.2 LSA Priority + +Localised Service Area Priority (LSA Priority) is defined in GSM 08.08. The LSA Priority is permanent subscriber data stored conditionally in the HLR. + +### 2.4.17.2A LSA Preferential Access Indicator + +The Localised Service Area Preferential Access Indicator defines if the subscriber shall be favoured in cells belonging to the LSA at resource allocation compared to other subscribers. The LSA Preferential Access Indicator is permanent subscriber data stored conditionally in the HLR. + +### 2.4.17.2B LSA Active Mode Support Indicator + +The Localised Service Area Active Mode Support Indicator defines if cells belonging to the LSA shall be favoured for the subscriber compared to other cells at resource allocation. The LSA Active Mode Indicator is permanent subscriber data stored conditionally in the HLR. + +### 2.4.17.3 LSA Only Access Indicator + +The LSA Only Access Indicator defines if the subscriber is only allowed within its subscribed LSAs. The LSA Only Access Indicator is permanent subscriber data stored conditionally in the HLR. + +#### 2.4.17.4 LSA Active Mode Indicator + +The Localised Service Area Active Mode Indicator defines if the LSA Identity of the cell in which the MS is currently in radio contact with shall be indicated to the subscriber in active mode. The LSA Active Mode Indicator is permanent subscriber data stored conditionally in the HLR. + +#### 2.4.17.5 VPLMN Identifier + +The VPLMN Identifier identifies the VPLMN in which an LSA Identity is applicable. This identifier is not applicable to Universal LSA IDs as defined in 3GPP TS 23.003 [5]. The VPLMN identifier is permanent subscriber data stored conditionally in the HLR. + +### 2.4.18 Access Restriction Data + +The use of this data is described in 3GPP TS 23.221 [57] and in 3GPP TS 23.401 [74] clauses 4.3.28, 4.3.2a and 4.3.30. + +The Access Restriction Data is permanent subscriber data and is conditionally stored per PLMN in the HLR/HSS, the VLR, the SGSN and the MME. + +The parameter takes either of the following values: + +- GERAN not allowed, the subscriber shall not be allowed to access the network in GERAN radio access. Valid for Idle and Connected mode; +- UTRAN not allowed, the subscriber shall not be allowed to access the network in LA/RAs using a UTRAN radio access. Valid for Idle and Connected mode; +- E-UTRAN not allowed, the subscriber shall not be allowed to access the network in TAs using a E-UTRAN radio access. Valid for Idle and Connected mode; +- GAN not allowed, the subscriber shall not be allowed to access the network via GAN; +- I-HSPA-Evolution not allowed, the subscriber shall not be allowed to access the network in LA/RAs using I-HSPA-Evolution radio access. Valid for Idle and Connected mode; +- HO-To-Non-3GPP-Access not allowed, the subscriber is not allowed to get EPS services that require handover support between 3GPP and non-3GPP accesses; +- NB-IoT not allowed, the subscriber shall not be allowed to access the network in TAs using a NB-IoT radio access. Valid for Idle and Connected mode; +- Enhanced Coverage not allowed, the subscriber shall not be allowed to use enhanced coverage; +- NR as secondary RAT not allowed, the subscriber shall not be allowed to access the network using NR radio access as secondary RAT. Valid for Idle and Connected mode; +- Unlicensed Spectrum as secondary RAT not allowed, the subscriber shall not be allowed to access the network using unlicensed spectrum in the form of LAA, LWA/LWIP or NR in unlicensed bands as secondary RAT. Valid for Idle and Connected mode. + +Only the access restriction for WB-E-UTRAN and NB-IoT may include a different value per PLMN. + +The use of this parameter for LA/RA/TA update procedures is described in 3GPP TS 23.012 [8], 3GPP TS 23.060 [21], and 3GPP TS 23.401 [74]. + +### 2.4.19 Selected CN operator ID + +The selected CN operator ID indicates which core network operator Network Sharing supporting UEs have chosen in a shared network. The use of this data is described in 3GPP TS 23.251 [61]. And this data is identified by a PLMN ID (MCC+MNC) as described in 3GPP TS 23.003 [5]. + +The selected CN operator ID is temporary subscriber data stored conditionally in the VLR and the SGSN in a shared network for non-GPRS and GPRS services respectively. + +This data is also stored in VLR for GPRS services if the Gs interface is installed. + +## 2.4.20 IP-SM-GW number + +The IP-SM-GW number is the E.164 address of the IP-SM-GW. + +The IP-SM-GW number indicates the address of the external IP-SM-GW that is registered for a subscriber to be used for delivering mobile terminated short messages. The IP-SM-GW number is temporary subscriber data and is stored conditionally in the HLR. The absence of the IP-SM-GW number in the HLR indicates that no external IP-SM-GW is registered; in this case an IP-SM-GW number pre-configured in the HLR can be used as an alternative route for delivering mobile terminated short messages. + +## 2.4.20A IP-SM-GW Diameter Identity + +The IP-SM-GW Diameter Identity indicates the Diameter Name and Realm of the external IP-SM-GW that is registered for a subscriber to be used for delivering mobile terminated short messages via Diameter. The IP-SM-GW Diameter Identity is temporary subscriber data and is stored conditionally in the HSS. + +## 2.4.21 Paging Area + +As an option, and for paging optimization purpose, the VLR may control Paging Areas. A Paging Area is a list of up to 5 Location Areas. The structure of the Location Area is specified in 3GPP TS 29.002 [27]. The Paging Area is temporary data stored in the VLR and in the HLR. + +The use of this data is described in TS 23.012 [8] and in TS 23.018 [70]. + +## 2.4.22 Closed Subscriber Group Information + +If a mobile subscriber has a Closed Subscriber Group (CSG) subscription, the HLR/HSS shall store Closed Subscriber Group Information which is a list of up to 50 CSG-Ids per PLMN and for each CSG-Id optionally an associated expiration date which indicates the point in time when the subscription to the CSG-Id expires and optionally corresponding APNs which can be accessed via Local IP access from this CSG identified by the CSG-Id; an absent expiration date indicates unlimited subscription; an expired expiration date may indicate that removal of the CSG-Id from the UE (e.g. by OMA DM or OTA update) is pending. The structure of CSG-Id is defined in 3GPP TS 23.003 [5]. + +On updating the VLR or the SGSN or MME, the HSS/HLR identifies and stores the VPLMN and the list of equivalent PLMNs provided by the VLR, SGSN or MME, and transfers the applicable CSG-Ids, expiration dates and the APNs allowed for LIPA (if present) to the VLR or SGSN or MME. + +If an applicable (i.e. applicable for the current serving PLMN) CSG-Id is added to the Closed Subscriber Group Information in the subscriber data in the HLR/HSS, or an expiration date for an applicable CSG-Id is changed (added, modified or removed), or the APNs allowed for LIPA for an applicable CSG-Id is changed (added, modified or removed), then the HLR/HSS shall transfer applicable CSG-Ids, expiration dates, and APNs allowed for LIPA to the VLR or SGSN or MME. + +NOTE 1: The APNs allowed for LIPA information are not applicable to the VLR. + +When a CSG-Id expires, or the expiration date is changed (added or modified) to an expired date, the CSG-Id should be removed from the UE (e.g. by OMA DM or OTA update). After successful removal of the CSG-Id from the UE, the HLR/HSS should delete the CSG-Id and, if applicable, update the VLR or SGSN or MME. The two operations may not be correlated in the sense that they may be performed independently by different systems. The temporal relationship between the two operations is out scope of this specification and therefore depends on the operator policy. + +If the subscription is terminated by other means than expiry, then CSG-Ids that are not expired should not be removed at the HLR/HSS; rather the expiration date may be modified to an expired date. + +CSG-Ids that are expired should not be removed from the HLR/HSS before being removed from the UE. + +NOTE 2: In the VLR or SGSN or MME an expired CSG-Id subscription indicates that the UE is not allowed service in the CSG. However, since the CSG-Id removal from the UE is pending, the UE may still camp on that CSG and therefore the UE may still be paged in the CSG. + +Closed Subscriber Group Information is permanent subscriber data and is conditionally stored in HLR/HSS, VLR, SGSN, and MME. + +## 2.4.23 Service Centre Address + +The Service Centre Address, specified in the 3GPP TS 29.002 [27], represents the address of a Short Message Service Centre. + +It is permanent subscriber data and is stored conditionally in the HLR/HSS and the IP-SM-GW (AS). + +## 2.4.24 Subscribed Periodic LAU Timer + +The Subscribed Periodic LAU Timer value (see 3GPP TS 23.012 [8]) is permanent data conditionally stored in the HLR and VLR. The use of this data is described in 3GPP TS 23.012 [8]. + +## 2.4.25 CSS number + +CSS number is the international ISDN number of the CSS. It is defined in 3GPP TS 23.003 [5]. + +The CSS number is temporary subscriber data and is conditionally stored in the VLR and Gn/Gp-SGSN. + +## 2.4.26 VPLMN Closed Subscriber Group Information + +If the VPLMN supports VPLMN Autonomous CSG Roaming by providing CSG membership to the roaming subscriber, the CSS shall store Closed Subscriber Group Information which is a list of up to 50 CSG-Ids in the VPLMN and for each CSG-Id optionally an associated expiration date which indicates the point in time when the subscription to the CSG-Id expires; an absent expiration date indicates unlimited subscription. The structure of CSG-Id is defined in 3GPP TS 23.003 [5]. + +NOTE 1: The HPLMN enables Autonomous CSG Roaming in the VPLMN via Service Level Agreement. + +When a CSG-Id expires, or the expiration date is changed (added or modified) to an expired date, the CSG-Id may be removed from the CSS and the VLR or SGSN or MME based on implementation. + +NOTE 2: In the VLR or SGSN or MME an expired CSG-Id subscription indicates that the UE is not allowed service in the CSG. However, since the CSG-Id removal from the UE is pending, the UE may still camp on that CSG and therefore the UE may still be paged in the CSG. + +If the subscription is terminated by other means than expiry, then CSG-Ids that are not expired should not be removed at the CSS; rather the expiration date may be modified to an expired date and then be updated by the CSS to the VLR or SGSN or MME. + +VPLMN Closed Subscriber Group Information as described in 3GPP TS 29.002 [27] and 3GPP TS 29.272 [81] is permanent subscriber data and is conditionally stored in CSS, VLR, SGSN, and MME. + +## 2.4.27 IAB-Operation Allowed indication + +The IAB-Operation Allowed indication defines if the subscriber is allowed for IAB node operation as specified in 3GPP TS 23.401 [74]. + +The IAB-Operation Allowed indication is permanent subscriber data and is conditionally stored in the HSS and the MME. + +# 2.5 Data related to basic services + +## 2.5.1 Provision of bearer service + +Provision of bearer service is a parameter identifying whether a bearer service is provisioned to the mobile subscriber or not. This provision can be achieved through subscription of the mobile subscriber or the bearer service can be generally + +available. The parameter "provision of bearer service" must be set for the bearer service defined in 3GPP TS 22.002 [2] for which a subscription is required. + +Provision of bearer service is permanent subscriber data and is stored in the HLR and VLR. + +## 2.5.2 Provision of teleservice + +Provision of teleservice is a parameter identifying whether a teleservice is provisioned to the mobile subscriber or not. This provision can be achieved through subscription of the mobile subscriber or the teleservice can be generally available. The parameter "provision of teleservice" must be set for the teleservices defined in GSM 02.03 [36] for which a subscription is required. + +Provision of teleservice is permanent subscriber data and is stored in the HLR, Gn/Gp-SGSN and VLR. + +## 2.5.3 Bearer capability allocation + +Bearer capability allocation is a parameter stored against each ISDN number in the case when the Home PLMN allocates one directory number per teleservice and bearer service. In this case it is used to permit the establishment of the correct bearer capability on the connection to the MS. (See 3GPP TS 29.007 [28]). The bearer capability allocation is not required when the Home PLMN only allocates one directory number per subscriber for all bearer services and teleservices. It is permanent data stored conditionally in the 3GPP TS 23.020 [31]. + +## 2.5.4 Transfer of SM option + +Transfer of SM option is a parameter indicating which path should be used for transfer of Terminating Short Message when GPRS is not supported by the GMSC. Two options are possible: + +- transfer of SM via the MSC when GPRS is not supported in the GMSC: this option is used to indicate that SM shall always be sent via the MSC when the GMSC does not support the GPRS functionality; +- transfer of SM via the Gn/Gp-SGSN when GPRS is not supported in the GMSC: this option is used to indicate that SM shall always be sent via the Gn/Gp-SGSN when the GMSC does not support the GPRS functionality. + +Transfer of SM option is permanent subscriber data stored in HLR for a GPRS subscription. + +The data has an interim nature since in the final solution, the decision on SM Transfer is taken in the SMS-GMSC. + +## 2.6 Data related to supplementary services + +Subscriber data related to supplementary services are contained in the 3GPP TS 23.08x and 3GPP TS 23.09x series of Technical Specifications, that is 3GPP TS 23.081 [14] and following describing the network functionality of supplementary services. Additionally, subscriber data related to the Multicall (MC) supplementary service are contained in 3GPP TS 23.135 [25]. + +There is no data type which is mandatory for all supplementary services; note that the provision status is mandatory for all supplementary services except CUG, 3GPP TS 23.085 [18]. All other data are conditional depending on the provision. + +## 2.7 Mobile station status data + +### 2.7.1 IMSI detached flag + +IMSI detached flag is a parameter indicating that the MS is in the IMSI detached state, i.e. the subscriber is no longer reachable. For definition and handling see 3GPP TS 23.012 [8] and 3GPP TS 29.002 [27]. The parameter takes the following values: + +- IMSI detached; +- IMSI attached. + +The parameter is temporary subscriber data and is stored conditionally in the VLR. + +## 2.7.2 Mobile station Not Reachable for GPRS (MNRG) + +In HLR, MNRG indicates whether the MS is marked as GPRS detached or GPRS not reachable in the Gn/Gp-SGSN and possibly in the GGSN. The reason why the MS is GPRS not reachable is indicated in the Mobile Not Reachable via SGSN Reason (MNRR-SGSN). + +In Gn/Gp-SGSN, MNRG indicates whether activity from the MS shall be reported to the HLR. + +In GGSN, MNRG indicates whether the MS is marked as GPRS detached in the Gn/Gp-SGSN. + +MNRG is described in 3GPP TS 23.060 [21]. It is temporary subscriber data stored in the HLR, in the Gn/Gp-SGSN and in the GGSN. + +## 2.7.3 Mobility Management State + +The Mobility Management State indicates the GPRS state of the MS. It takes one of three possible values: + +1. READY: The MS is GPRS attached and its location is known at Cell Identity level. +2. STANDBY: The MS is GPRS attached and its location is known at Routing Area level. +3. IDLE: The MS is not GPRS attached. + +The parameter is described in 3GPP TS 23.060 [21]. It is temporary subscriber data stored in the SGSN. + +## 2.7.4 Restoration flags + +In the case of SGSN, MME, VLR or HLR failure, location register data have to be restored as described in 3GPP TS 23.007 [6] and 3GPP TS 29.002 [27]. The following flags are used for this purpose. + +### 2.7.4.1 Confirmed by Radio Contact indicator + +Confirmed by Radio Contact indicator is a restoration indicator defined in 3GPP TS 23.007 [6]. + +It is temporary subscriber data, stored in the VLR. + +### 2.7.4.2 Subscriber Data Confirmed by HLR/HSS indicator + +Subscriber Data Confirmed by HLR/HSS indicator is a restoration indicator defined in 3GPP TS 23.007 [6]. + +It is temporary subscriber data, stored in the VLR, in the SGSN and in the MME. + +### 2.7.4.3 Location Information Confirmed in HLR/HSS indicator + +Location Information Confirmed in HLR/HSS indicator is a restoration indicator defined in 3GPP TS 23.007 [6]. + +It is temporary subscriber data, stored in the VLR and in the SGSN and in the MME. + +### 2.7.4.4 Check SS indicator + +Check SS indicator is a restoration indicator defined in 3GPP TS 23.007 [6]. + +It is temporary subscriber data and is stored in the HLR. + +### 2.7.4.5 VLR-Reliable indicator + +VLR-Reliable indicator is a restoration indicator defined in 3GPP TS 23.007 [6]. + +It is temporary subscriber data and is stored in the SGSN and in the MME. + +## 2.7.5 MS purged for non-GPRS flag + +MS purged for non-GPRS flag is set in the HLR per IMSI record in order to indicate that the subscriber data for the MS concerned have been purged in the VLR. The parameter takes the following values: + +- MS purged; +- MS not purged. + +The default value is "MS not purged". The parameter is temporary subscriber data, stored in the HLR. + +## 2.7.6 MS purged for GPRS/UE purged in SGSN flag + +MS purged for GPRS/UE purged in SGSN flag is set in the HLR/HSS per IMSI record in order to indicate that the subscriber data for the MS/UE concerned have been purged in the SGSN. The parameter takes the following values: + +- MS purged for GPRS/UE purged in SGSN; +- MS not purged for GPRS/UE not purged in SGSN. + +The default value is "MS not purged for GPRS"/"UE not purged in SGSN". The parameter is temporary subscriber data, stored in the HLR/HSS for a PS subscription. + +## 2.7.6A UE purged in MME flag + +UE purged in MME flag is set in the HSS per IMSI record in order to indicate that the subscriber data for the UE concerned have been purged in the MME. The parameter shall take the following values: + +- UE purged in MME; +- UE not purged in MME. + +The default value is "UE not purged in MME". The parameter is temporary subscriber data, stored in the HSS for a PS subscription. + +## 2.7.7 Mobile station Not Reachable via MSC Reason (MNRR-MSC) + +Mobile station Not Reachable via MSC Reason (MNRR-MSC) for SMS is defined in 3GPP TS 23.040 [10]. The MNRR-MSC is temporary subscriber data. It is conditionally stored in the HLR. + +## 2.7.7A Mobile station Not Reachable via SGSN Reason (MNRR-SGSN) + +Mobile station Not Reachable via SGSN Reason (MNRR-SGSN) for SMS is defined in 3GPP TS 23.040 [10]. The MNRR-SGSN is temporary subscriber data. It is conditionally stored in the HLR. + +## 2.7.8 Subscriber data dormant + +Subscriber data dormant is set in the VLR per IMSI record in order to indicate that the subscriber data belong to a subscriber that has moved outside the VLR area (see 3GPP TS 23.012 [8]). The parameter takes the following values: + +- Subscriber data dormant; +- Subscriber data not dormant. + +The parameter is temporary subscriber data and is stored in the VLR. + +## 2.7.8A Cancel Location received + +Cancel Location received is set by a VLR supporting the MT roaming retry feature per IMSI record to indicate that a Cancel Location message has been received from the HLR. This is used to determine whether to trigger MT roaming + +retry upon receipt of an incoming call, see clause 7.3.2.1 of 3GPP TS 23.018 [5a]. The parameter takes the following values: true or false. + +The parameter is temporary subscriber data and is stored in the VLR. + +## 2.7.9 Data related to UE reachability procedures + +### 2.7.9.1 URRP-MME + +The UE Reachability Request Parameter for the MME (URRP-MME) indicates that UE activity notification from MME has been requested by the HSS. For definition and handling of the data see 3GPP TS 23.401 [74]. + +URRP-MME is temporary subscriber data conditionally stored in the MME and in the HSS. + +### 2.7.9.2 URRP-SGSN + +The UE Reachability Request Parameter for the SGSN (URRP-SGSN) indicates that UE activity notification from SGSN has been requested by the HSS. For definition and handling of the data see 3GPP TS 23.060 [21]. + +URRP-SGSN is temporary subscriber data conditionally stored in the SGSN and in the HSS. + +### 2.7.9.3 Service-related Entity list + +This information element is a list of service related entities (i.e. gsmSCF address list or AS Identity list, see the definition of gsmSCF address list in chapter 2.14.2.4 and the definition of AS Identity list in chapter 3.5.7) which have subscribed to a notification of UE reachability (e.g. IP-SM-GW ) + +Service-related Entity list is temporary subscriber data stored in the HSS. + +## 2.8 Data related to Operator Determined Barring + +### 2.8.1 Subscriber status + +Subscriber status is a flag which indicates whether the subscriber is subject to operator determined barring. + +It is permanent subscriber data, and is conditionally stored in the HLR/HSS, the SGSN, the MME and the VLR. + +### 2.8.2 Operator Determined Barring general data + +#### 2.8.2.1 Barring of outgoing calls + +Barring of outgoing calls indicates which one of the following categories of operator determined barring of outgoing calls applies to the subscriber: + +- No barring of outgoing calls; +- Barring of all outgoing calls; +- Barring of all outgoing international calls; +- Barring of all outgoing international calls except those directed to the home PLMN country; +- Barring of all outgoing inter-zonal calls; +- Barring of all outgoing inter-zonal calls except those directed to the home PLMN country; +- Barring of all outgoing international calls except those directed to the home PLMN country AND barring of all outgoing inter-zonal calls. + +It is permanent data, and is stored conditionally in the HLR/HSS, the SGSN and the VLR. + +### 2.8.2.2 Barring of incoming calls + +Barring of incoming calls indicates which one of the following categories of operator determined barring of incoming calls applies to the subscriber: + +- No barring of incoming calls; +- Barring of all incoming calls; +- Barring of all incoming calls when roaming outside the home PLMN country; +- Barring of all incoming calls when roaming outside the zone of the home PLMN country. + +It is permanent data, and is stored conditionally in the HLR. + +### 2.8.2.3 Barring of roaming + +Barring of roaming indicates which one of the following categories of operator determined barring of roaming applies to the subscriber: + +- No barring of roaming; +- Barring of roaming outside the home PLMN; +- Barring of roaming outside the home PLMN country. + +It is permanent data, and is stored conditionally in the HLR/HSS for non-GPRS, GPRS subscription and EPS subscription. + +### 2.8.2.4 Barring of premium rate calls + +Barring of premium rate calls indicates which one of the following categories of operator determined barring of premium rate calls applies to the subscriber: + +- No barring of premium rate calls; +- Barring of premium rate (information) calls; +- Barring of premium rate (entertainment) calls; +- Barring of premium rate (information) calls and premium rate (entertainment) calls. + +It is permanent subscriber data, and is stored conditionally in the HLR and the VLR. + +### 2.8.2.5 Barring of supplementary services management + +Barring of supplementary services management is a flag which indicates whether the subscriber is subject to operator determined barring of supplementary services management. + +It is permanent subscriber data, and is stored conditionally in the HLR and the VLR. + +### 2.8.2.6 Barring of registration of call forwarding + +Barring of registration of call forwarding indicates which one of the following categories of operator determined barring of registration of call forwarding applies to the subscriber: + +- Barring of registration of any forwarded-to number; +- Barring of registration of any international forwarded-to number; +- Barring of registration of any international forwarded-to number except a number within the HPLMN country; +- Barring of registration of any inter-zonal forwarded-to number; +- Barring of registration of any inter-zonal forwarded-to number except a number within the HPLMN country. + +It is permanent subscriber data, and is stored conditionally in the HLR. + +### 2.8.2.7 Barring of invocation of call transfer + +Barring of invocation of call transfer indicates which of the following categories of operator determined barring of invocation of call transfer applies to the subscriber: + +One of: + +- Barring of invocation of any call transfer; +- Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber; +- Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at international rates; +- Barring of invocation of call transfer where at least one of the two calls is a call charged to the served subscriber at inter-zonal rates; + +and independently: + +- Barring of invocation of call transfer where both calls are calls charged to the served subscriber; + +and independently: + +- Barring of invocation of call transfer when there is an existing transferred call for the served subscriber in the same MSC/VLR. + +It is permanent subscriber data, and is stored conditionally in the HLR and the VLR. + +### 2.8.2.8 Barring of Packet Oriented Services + +Barring of Packet Oriented Services indicates which one of the following categories of operator determined barring of Packet Oriented Services applies to the subscriber: + +- Barring of all Packet Oriented Services; +- Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN; +- Barring of Packet Oriented Services from access points that are within the roamed to VPLMN. + +It is permanent subscriber data, and is stored conditionally in the HLR/HSS, the SGSN and MME. + +## 2.8.3 Operator Determined Barring PLMN-specific data + +Operator determined barring PLMN-specific data indicates which of the following categories of operator specific barring, in any combination, applies to the subscriber: + +- Operator specific barring (type 1); +- Operator specific barring (type 2); +- Operator specific barring (type 3); +- Operator specific barring (type 4). + +It is permanent subscriber data. It is stored conditionally in the HLR/HSS, the SGSN and in the VLR when the subscriber is registered in the home PLMN. + +## 2.8.4 Notification to CSE flag + +This information element indicates whether the change of ODB data shall trigger Notification on Change of Subscriber Data or not. + +## 2.8.5 gsmSCF address list + +This information element contains the list of gsmSCF addresses to which Notification on Change of Subscriber Data is to be sent. + +## 2.9 Data related to handover + +### 2.9.1 Handover Number + +Handover Number is defined in 3GPP TS 23.003 [5] and its use is specified in 3GPP TS 23.009 [7]. + +The Handover Number is short-lived subscriber data and is stored in the VLR. + +## 2.10 Data related to short message support + +### 2.10.1 Messages Waiting Data (MWD) + +Messages Waiting Data (MWD) is defined in 3GPP TS 23.040 [10]. + +The MWD is temporary subscriber data, and is conditionally stored in the HLR. + +### 2.10.2 Mobile Station Not Reachable Flag (MNRF) + +Mobile Station Not Reachable Flag (MNRF) is defined in 3GPP TS 23.040 [10]. + +The MNRF is temporary data. It is stored in the VLR, MME and conditionally stored in the HLR. + +### 2.10.3 Memory Capacity Exceeded Flag (MCEF) + +Memory Capacity Exceeded Flag (MCEF) is defined in 3GPP TS 23.040 [10]. + +The MCEF is temporary subscriber data and is conditionally stored in the HLR. + +### 2.10.4 Mobile station Not Reachable for GPRS (MNRG) + +For MNRG see clause 2.7.2. + +### 2.10.4A UE Not Reachable via IP-SM-GW Flag (UNRI) + +For UNRI see clause 3.2.5. + +### 2.10.5 Mobile station Not Reachable via MSC Reason (MNRR-MSC) + +For MNRR-MSC see clause 2.7.7. + +### 2.10.5A Mobile station Not Reachable via SGSN Reason (MNRR-SGSN) + +For MNRR-SGSN see clause 2.7.7A. + +### 2.10.5B UE Not Reachable via IP-SM-GW Reason (UNRR) + +For UNRR see clause 3.2.6. + +## 2.10.6 MME Number for MT SMS + +MME number for MT SMS is the E.164 address for the MME that supports SMS in MME. It is defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 29.272 [81]. + +The MME number for MT SMS is temporary subscriber data and is stored in the HSS when the MME was registered as an MSC for MT SMS. + +## 2.10.7 PS and SMS Only + +This parameter indicates that the subscription is for PS Only, and permits CS service access only for SMS. + +This parameter is permanent subscriber data and is conditionally stored in the HSS and SGSN. + +## 2.10.8 SMS In SGSN Allowed + +This parameter indicates that the SMS in SGSN feature is allowed for the user. + +This parameter is permanent subscriber data and is conditionally stored in the HSS and SGSN. + +## 2.11 Data related to subscriber trace + +### 2.11.1 Trace Reference + +The Trace Reference is defined in 3GPP TS 52.008 [37]. + +The Trace Reference is permanent subscriber data and is conditionally stored in the HLR and VLR. + +### 2.11.2 Trace Type + +The Trace Type is defined in 3GPP TS 52.008 [37]. + +The Trace Type is permanent subscriber data and is conditionally stored in the HLR and VLR. + +### 2.11.3 Operations Systems Identity + +The Operations Systems Identity is defined in 3GPP TS 52.008 [37]. + +The Operations Systems Identity is permanent subscriber data and is conditionally stored in the HLR and VLR. + +### 2.11.4 HLR Trace Type + +The HLR Trace Type is defined in 3GPP TS 52.008 [37]. + +The HLR Trace Type is permanent subscriber data and is conditionally stored in the HLR. + +### 2.11.5 MAP Error On Trace + +The MAP Error On Trace is defined in 3GPP TS 52.008 [37]. + +The MAP Error On Trace is temporary subscriber data and is conditionally stored in the HLR. + +### 2.11.6 Trace Activated in VLR + +The Trace Activated in VLR flag is defined in 3GPP TS 52.008 [37]. + +The Trace Activated in VLR flag is temporary subscriber data and is conditionally stored in the HLR and VLR. + +## 2.11.7 Trace Activated in SGSN + +The Trace Activated in SGSN flag is defined in 3GPP TS 52.008 [37]. + +The Trace Activated in SGSN flag is temporary subscriber data and is conditionally stored in the HLR and SGSN. + +## 2.11.8 Foreign Subscriber Registered in VLR + +The Foreign Subscriber Registered in VLR flag is handled by operation and maintenance means in the VLR and is defined in 3GPP TS 52.008 [37]. + +The Foreign Subscriber Registered in VLR flag is permanent subscriber data and is conditionally stored in the VLR. + +## 2.11.9 Trace Reference 2 + +Trace reference 2 is defined in 3GPP TS 32.421 [65] and in 3GPP TS 32.422 [64]. + +The Trace Reference 2 is permanent subscriber data and is conditionally stored in the HSS/HLR, VLR, SGSN, MME, SGW, PGW and 3GPP AAA Server. + +## 2.11.10 Trace depth + +The Trace depth is defined in 3GPP TS 32.422 [64]. + +The Trace depth is permanent subscriber data and is conditionally stored in the HSS/HLR, VLR, SGSN, MME, SGW, PGW and 3GPP AAA Server. + +## 2.11.11 List of NE types to trace + +The List of NE types to trace is defined in 3GPP TS 32.422 [64]. + +The List of NE types to trace is permanent subscriber data and is conditionally stored in the HSS/HLR, VLR, SGSN, MME and 3GPP AAA Server. + +## 2.11.12 Triggering events + +The Triggering event is defined in 3GPP TS 32.422 [64]. + +The Triggering event is permanent subscriber data and is conditionally stored in the HSS/HLR, VLR, SGSN, MME, SGW, PGW and 3GPP AAA Server. + +## 2.11.13 List of interfaces to trace + +The List of interfaces to trace is defined in 3GPP TS 32.422 [64]. + +The List of interfaces to trace is permanent subscriber data and is conditionally stored in the HSS/HLR, VLR, SGSN, MME, SGW, PGW and 3GPP AAA Server. + +## 2.11.14 IP address of Trace Collection Entity + +The IP address of Trace Collection Entity is defined in 3GPP TS 32.422 [64]. + +The IP address of Trace Collection Entity is permanent subscriber data and is conditionally stored in the HSS/HLR, VLR, SGSN, MME, SGW, PGW and 3GPP AAA Server. + +## 2.11.15 MDT-Configuration + +The MDT-Configuration is defined in 3GPP TS 32.422 [64]. It contains: + +Job type + +Area Scope + +List of measurements + +Reporting Trigger + +Report Interval + +Report Amount + +Event Threshold RSRP + +Event Threshold RSRQ + +Logging Interval + +Logging Duration + +The MDT-Configuration is permanent subscriber data and is conditionally stored in the HSS/HLR, VLR, SGSN, and MME. + +## 2.11.16 MDT User Consent + +The MDT User Consent parameter indicates whether the user has given his consent for MDT activation. For details see 3GPP TS 32.422 [64]. + +The MDT User Consent is permanent subscriber data and is conditionally stored in the HSS/HLR, VLR, SGSN, and MME. + +## 2.12 Data related to the support of voice group and broadcast calls + +### 2.12.1 VGCS Group Membership List + +VGCS Group Membership List and its special condition of storage in VLR is defined in 3GPP TS 43.068 [33]. + +The VGCS Group Membership List is permanent subscriber data. It is stored conditionally in HLR and in the VLR. + +### 2.12.2 VBS Group Membership List + +VBS Group Membership List and its special condition of storage in VLR is defined in 3GPP TS 43.069 [34]. + +The VBS Group Membership List is permanent subscriber data. It is stored conditionally in HLR and in the VLR. + +#### 2.12.2.1 Broadcast Call Initiation Allowed List + +The Broadcast Call Initiation Allowed List and its special condition of storage in VLR is defined in 3GPP TS 43.069[34]. + +It is permanent subscriber data. It is stored conditionally in HLR and in the VLR. + +## 2.13 Data related to PS NAM + +The data listed in this clause pertain to the Network Access Mode "PS " and have no counterpart for CS. + +### 2.13.1 PDP Type + +PDP Type is defined in 3GPP TS 23.060 [21]. It indicates which type of protocol is used by the MS for a certain service, e.g. IP and X.25. + +PDP Type is permanent subscriber data and conditionally stored in HLR, SGSN and GGSN. + +### 2.13.2 PDP Address + +PDP Address is defined in 3GPP TS 23.060 [21]. It holds the address of the MS for a certain service, e.g. an IP address. If dynamic addressing is allowed, PDP Address is empty in the HLR, and, before the PDP context is activated, empty in the SGSN. + +PDP Address is permanent subscriber data and conditionally stored in HLR, SGSN and GGSN. + +### 2.13.3 NSAPI + +NSAPI is defined in 3GPP TS 23.060 [21]. It holds the index of the PDP Context. + +NSAPI is temporary subscriber data and conditionally stored in SGSN and GGSN. + +### 2.13.4 Packet Data Protocol (PDP) State + +PDP State is defined in 3GPP TS 23.060 [21]. The PDP State is either ACTIVE or INACTIVE. + +PDP State is temporary subscriber data and conditionally stored in SGSN. + +### 2.13.5 New SGSN Address + +New SGSN Address is defined in 3GPP TS 23.060 [21]. It is the IP-address of the new SGSN, to which N-PDUs should be forwarded from the old SGSN after an inter-SGSN routing update. + +New SGSN Address is temporary subscriber data and conditionally stored in SGSN. + +### 2.13.6 Access Point Name (APN) + +Access Point Name (APN) is defined in 3GPP TS 23.003 [5] and 3GPP TS 23.060 [21] and 3GPP TS 23.401[74]. The APN field in the HLR/HSS contains either only an APN Network Identifier (i.e. an APN without APN Operator Identifier) or the wild card value (defined in 3GPP TS 23.003 [5]). APN is permanent subscriber data conditionally stored in HLR/HSS, in GGSN, SGSN, MME, S-GW, PDN and SCEF. + +### 2.13.7 GGSN Address in Use + +GGSN Address in Use is defined in 3GPP TS 23.060 [21]. It is the IP address of the GGSN currently used by a certain PDP Address of the MS. + +GGSN Address is temporary subscriber data and conditionally stored in Gn/Gp-SGSN. + +### 2.13.8 VPLMN Address Allowed + +VPLMN Address Allowed is defined in 3GPP TS 23.060 [21]. It specifies per VPLMN whether the MS is allowed to use a dynamic address allocated in the VPLMN. + +VPLMN Address Allowed is permanent subscriber data and conditionally stored in HLR and SGSN. + +## 2.13.9 Dynamic Address + +Dynamic Address is defined in 3GPP TS 23.060 [21]. It indicates whether the address of the MS is dynamic. + +Dynamic Address is temporary subscriber data conditionally stored in GGSN. + +## 2.13.10 SGSN Address + +SGSN Address is defined in 3GPP TS 23.003 [5]. It is the IP Address of the SGSN currently serving the MS. + +SGSN Address is temporary subscriber data stored in HLR and stored conditionally in GGSN. A pendant is the SGSN number, cf clause 2.4.8. + +## 2.13.11 GGSN-list + +GGSN-list is defined in 3GPP TS 23.060 [21]. It defines the GGSNs to be contacted when activity from the MS is detected and MNRG is set. It contains the GGSN number and optionally the GGSN IP address. + +GGSN-list is temporary subscriber data stored in the HLR. + +## 2.13.12 Quality of Service Subscribed + +Quality of Service Subscribed is defined in 3GPP TS 23.060 [21]. It specifies the quality of service subscribed for a certain PDP context. + +Quality of Service Subscribed is permanent subscriber data and conditionally stored in HLR and SGSN. + +## 2.13.13 Quality of Service Requested + +Quality of Service Requested is defined in 3GPP TS 23.060 [21]. It specifies the quality of service requested for a certain PDP context. + +Quality of Service Requested is temporary subscriber data and conditionally stored in Gn/Gp-SGSN. + +## 2.13.14 Quality of Service Negotiated + +Quality of Service Negotiated is defined in 3GPP TS 23.060 [21]. It specifies the quality of service for a certain PDP context, negotiated between the MS and the SGSN, and then the GGSN. + +Quality of Service Negotiated is temporary subscriber data and conditionally stored in Gn/Gp-SGSN and GGSN. + +## 2.13.15 SND + +SND is defined in 3GPP TS 23.060 [21]. It is the GPRS Tunnelling Protocol sequence number of the next downlink N-PDU. + +SND is temporary subscriber data conditionally stored in Gn/Gp-SGSN and GGSN. + +## 2.13.16 SNU + +SNU is defined in 3GPP TS 23.060 [21]. It is the GPRS Tunnelling Protocol sequence number of the next uplink N-PDU. + +SNU is temporary subscriber data and conditionally stored in SGSN and GGSN. + +## 2.13.17 DRX Parameters + +DRX Parameters is defined in 3GPP TS 23.060 [21]. + +DRX Parameters is temporary subscriber data stored in SGSN. + +## 2.13.18 Compression + +Compression is defined in 3GPP TS 23.060 [21]. There is one set of negotiated compression parameters per QoS priority level. + +Compression is temporary subscriber data conditionally stored in the SGSN. + +## 2.13.19 Non-GPRS Alert Flag (NGAF) + +Non-GPRS Alert Flag (NGAF) is defined in 3GPP TS 23.060 [21]. It indicates whether activity from the MS shall be reported to the MSC/VLR. + +NGAF is temporary subscriber data and is conditionally stored in the SGSN if the Gs interface is installed. + +## 2.13.20 Classmark + +MS Classmark is defined in 3GPP TS 24.008 [26]. + +Classmark is temporary subscriber data stored in the SGSN. + +## 2.13.21 Tunnel Endpoint Identifier (TEID) + +Tunnel Endpoint Identifier is defined in 3GPP TS 29.060 [29]. TEID is temporary subscriber data conditionally stored in SGSN and GGSN. + +## 2.13.22 Radio Priority + +Radio Priority is defined in 3GPP TS 23.060 [21]. It indicates the RLC/MAC radio priority level for uplink user data transmission for a certain PDP context. + +Radio Priority is temporary subscriber data and conditionally stored in SGSN. + +## 2.13.23 Radio Priority SMS + +Radio Priority SMS is defined in 3GPP TS 23.060 [21]. It indicates the RLC/MAC radio priority level for uplink SMS transmission. + +Radio Priority SMS is temporary subscriber data and conditionally stored in SGSN. + +## 2.13.24 PDP Context Identifier + +PDP Context Identifier is defined in 3GPP TS 23.060 [21]. It identifies uniquely each PDP context. + +PDP Context Identifier is permanent subscriber data and conditionally stored in HLR and Gn/Gp-SGSN. + +## 2.13.25 PDP Context Charging Characteristics + +PDP Context Charging Characteristics is defined in 3GPP TS 32.251 [41]. It indicates the charging type to be applied to the PDP context. + +PDP Context Charging Characteristics is permanent subscriber data and conditionally stored in HLR, SGSN and GGSN. + +## 2.13.26 MME name + +MME name is defined in 3GPP TS 23.003 [5]. + +The MME name is temporary subscriber data and is stored in the HSS. Absence of the MME name in HSS indicates that the UE is not registered for EPS via 3GPP E-UTRAN access. The MME name is conditionally stored in the VLR for MMEs for which the SGs interface is supported. + +The MME name is temporary subscriber data and is stored in the CSS. Absence of the MME name in the CSS indicates that no subsequent update of the CSG subscription information is needed at the MME upon CSG subscription change. + +## 2.13.27 VLR name + +The VLR name is conditionally stored in the MME for VLRs for which the SGs interface is supported. Absence of the VLR name in MME indicates that there is no association between MME and VLR. + +## 2.13.28 Non-EPS Alert Flag (NEAF) + +Non-EPS Alert Flag (NEAF) indicates whether activity from the UE shall be reported to the VLR. + +NEAF is temporary subscriber data and is conditionally stored in the MME for which the SGs interface is supported. + +## 2.13.29 UE level APN-OI-Replacement + +UE level APN-OI-Replacement (see 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]) is permanent data conditionally stored in the HSS and MME/SGSN. + +## 2.13.30 Subscribed UE-AMBR + +Subscribed UE-AMBR indicates the UE-AMBR for the uplink/downlink provided by the HSS to the MME/SGSN over the S6a/S6d/Gr interface for all non-GBR Bearers according to the subscription of the user. + +Subscribed UE-AMBR (see 3GPP TS 23.401[74], 3GPP TS 23.060 [21] and 3GPP TS 23.501 [112]) is permanent data stored in HSS, SGSN, MME, UDM and AMF. + +## 2.13.30A Used UE-AMBR + +Used UE-AMBR indicates the UE-AMBR that is calculated by the MME/SGSN as the sum of the Used/Authorized APN-AMBRs of all active APNs up to the value of the Subscribed UE-AMBR. + +Used UE-AMBR (see 3GPP TS 23.401[74] and 3GPP TS 23.060 [21]) is temporary data stored in MME and SGSN. + +## 2.13.31 APN-Configuration-Profile + +The APN-Configuration-Profile contains a Context-Identifier identifying the default APN-Configuration, optionally an additional Context-Identifier identifying another default APN-Configuration for those subscriptions having APNs with both, IP-based and Non-IP PDN types, and a list of APN-Configurations, each identified by a Context-Identifier. For detailed content see 3GPP TS 29.272[81] and 3GPP TS 29.273 [78]. + +The default APN configuration (default APN) for IP-based PDN types and the default APN for Non-IP PDN type are permanent data. + +The list of APN-Configuration is permanent data stored in HSS, MME, S4-SGSN, ePDG and AAA-server with the following exceptions: + +- PDN GW identity for the active IP-based PDN connections; stored in HSS if the user has non-3GPP subscription and the PDN connection is applicable to both 3GPP and non-3GPP accesses. For static PDN GW allocation, the PDN GW identity is also permanent data. +- APN-Specific-Data optionally stored as part of the APN context for the wildcard APN. + +## 2.13.32 Subscribed APN-AMBR + +Subscribed APN-AMBR indicates the APN-AMBR for the uplink/downlink provided by the HSS to the MME/SGSN over the S6a/S6d/Gr interface for all non-GBR Bearers according to the subscription of the user. + +Subscribed APN-AMBR is part of each APN configuration (see 3GPP TS 29.272[81] and 3GPP TS 29.273[78]) and part of each PDP-Context (see 3GPP TS 29.002 [27]) and is permanent data stored in HSS, 3GPP AAA Server, MME, SGSN, GGSN, P-GW and ePDG(for GTP-based S2b only). + +## 2.13.32A Used APN-AMBR + +Used (Authorized) APN-AMBR indicates the APN-AMBR for the uplink/downlink authorized by the PCRF/PGW for all non-GBR bearers related with the same APN. + +Used APN-AMBR is temporary data stored in MME, SGSN, GGSN and P-GW for each active APN (see 3GPP TS 23.401[74], 3GPP TS 23.060 [21] and 3GPP TS 23.402 [77]). + +## 2.13.33 Subscribed-RAT-Frequency-Selection-Priority-ID + +The Subscribed-RFSP-ID (see 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]) is permanent data conditionally stored in HSS, S4-SGSN, Gn/Gp-SGSN and MME. + +## 2.13.34 GUTI + +The GUTI (see 3GPP TS 23.003 [5]) is temporary data conditionally stored in MME. + +## 2.13.35 ME Identity + +The ME Identity is temporary data and contains the IMEISV see clause 2.2.3. + +## 2.13.36 Selected NAS Algorithm + +Selected NAS security algorithm sent by MME to UE (see 3GPP TS 23.401 [74]) and is temporary data stored in MME + +## 2.13.37 Selected AS Algorithm + +Selected AS security algorithms are defined in 3GPP TS 23.401 [74] and is temporary subscriber data stored in the MME. + +## 2.13.38 Context Identifier + +Index of the PDN subscription context (see 3GPP TS 23.401 [74]) is permanent data stored in HSS and MME. + +## 2.13.39 PDN Address + +Indicates subscribed IPv4 address and/or IPv6 prefix is temporary data stored in S-GW, PDN-GW, MME, ePDG and 3GPP AAA Server, and is permanent data in HSS (static address allocation based on subscriber profile in HSS; see 3GPP TS 23.401 [74]). + +## 2.13.40 VPLMN Address Allowed + +VPLMN Address Allowed specifies per VPLMN whether for this APN the UE is allowed to use the PDN GW in the domain of the HPLMN only, or additionally the PDN GW in the domain of the VPLMN (see 3GPP TS 23.401 [74]). It is permanent data stored in HSS, and temporary data in MME, ePDG and 3GPP AAA Server. + +### 2.13.41 PDN GW identity + +PDN GW identity is the identity of the PDN GW used for this APN. The PDN GW identity may be an FQDN or an IP address. The PDN GW identity is permanent data in HSS when static assignment is used and temporary data in HSS when dynamic assignment is used. It is temporary data in MME, S4-SGSN, ePDG and 3GPP AAA Server. + +### 2.13.42 Tracking Area List + +Tracking area list contains the current list of tracking areas (see 3GPP TS 23.401 [74]) and is temporary data stored in MME. + +### 2.13.43 APN Restriction + +APN Restriction is defined in 3GPP TS 23.060 [21] for GPRS and in 3GPP TS 23.401 [74] for EPS. It is temporary data stored in MME, SGSN and S-GW and contains the maximum restriction for each PDP context/EPS Bearer Context. + +### 2.13.44 APN in use + +APN in use contains the APN (see 2.13.6) currently in use (see 3GPP TS 23.401 [74], 3GPP TS 23.060 [21] and 3GPP TS 23.402 [77]) and it is temporary data stored in S4-SGSN, MME, S-GW, ePDG and PDN-GW. + +### 2.13.45 TAI + +TAI of the TA in which the last Tracking Area Update was initiated and is temporary data stored in MME, AMF and SMF and, when received via the SGs interface, in the VLR it contains the TAI of the last received E-UTRAN Cell Global ID. + +### 2.13.46 E-UTRAN Cell Identity Age + +E-UTRAN Cell Identity Age contains time elapsed since the last E-UTRAN Cell Global Identity was acquired (see 3GPP TS 23.401 [74]) and is temporary data stored in MME and, when received via the SGs interface, in the VLR. + +### 2.13.47 MME F-TEID for S11 (Control Plane) + +F-TEID for S11 is defined in 3GPP TS 29.274 [75]. MME F-TEID for S11 is temporary data conditionally stored in MME and S-GW. + +### 2.13.48 MME UE S1AP ID + +"MME UE S1AP ID" is the Unique identity of the UE within MME (see 3GPP TS 23.401 [74]) and is temporary data stored in MME. + +### 2.13.49 S-GW F-TEID for S11 (Control Plane) + +F-TEID for S11 is defined in 3GPP TS 29.274[75]. S-GW F-TEID for S11 is temporary data conditionally stored in MME and S-GW. + +### 2.13.50 S4-SGSN F-TEID for S4 (Control plane) + +F-TEID for S4 is defined in 3GPP TS 29.274[75]. S4-SGSN F-TEID for S4 is temporary data conditionally stored in S-GW and S4-SGSN. + +### 2.13.51 S4-SGSN F-TEID for S4 (User plane) + +F-TEID for S4 is defined in 3GPP TS 29.274[75]. S4-SGSN F-TEID for S4 is temporary data conditionally stored in S-GW and S4-SGSN. + +### 2.13.52 S-GW F-TEID for S5/S8 (control plane) + +F-TEID for S5/S8(control plane) is defined in 3GPP TS 29.274[75]. S-GW F-TEID for S5/S8(control plane) is temporary data conditionally stored in PDN-GW and S-GW. + +### 2.13.53 S-GW F-TEID for S1-U + +F-TEID for S1-U is defined in 3GPP TS 29.274[75]. S-GW F-TEID for S1-U is temporary data conditionally stored in eNodeB and S-GW. + +### 2.13.54 S-GW F-TEID for S5/S8 (user plane) + +F-TEID for S5/S8 (user plane) is defined in 3GPP TS 29.274[75]. S-GW F-TEID for S5/S8 (user plane) is temporary data conditionally stored in PDN-GW and S-GW. + +### 2.13.55 eNodeB Address + +The eNodeB Address identifies the IP address of the eNodeB currently used for control plane signalling (see 3GPP TS 23.401 [74]) and is temporary data stored in MME. + +### 2.13.56 eNodeB UE S1AP ID + +The "eNodeB UE S1AP ID " is the Unique identity of the UE within eNodeB (see 3GPP TS 23.401 [74]) and is temporary data stored in MME. + +### 2.13.57 eNodeB F-TEID for S1-U + +F-TEID for S1-U is defined in 3GPP TS 29.274[75]. The eNodeB F-TEID for S1-U is temporary data conditionally stored in eNodeB, S-GW and MME. + +### 2.13.58 E-UTRAN/UTRAN Key Set flag + +The "E-UTRAN/UTRAN Key Set flag" indicates whether the UE is using security keys derived from UTRAN or E-UTRAN security association (see 3GPP TS 23.401 [74]). E-UTRAN/UTRAN Key Set flag is temporary data conditionally stored in MME. + +### 2.13.59 Selected CN operator id + +Selected CN operator id contains the selected core network operator identity (to support network sharing as defined in TS 23.251 [61]). Selected CN operator id is temporary data conditionally stored in MME. + +### 2.13.60 UE Radio Access Capability + +UE Radio Access Capability (see 3GPP TS 23.401 [74]) is temporary data conditionally stored in MME. + +NOTE: The actual size of UE Radio Access Capability depends on the features and bands supported by the UE and the eNodeB as specified in 3GPP TS 36.331[96]. Its size is constrained by the message size limits on the interfaces the information is conveyed (e.g. the maximum S1-AP SCTP packet size of 65535 bytes). + +The MME shall store the UE Radio Access Capability Information received from the eNodeB without any truncation. + +## 2.13.61 UE Network Capability + +UE network capabilities (see 3GPP TS 23.401 [74]) including security algorithms and key derivation functions which shall be supported by the UE. UE Network Capability is temporary data conditionally stored in MME. + +## 2.13.62 Location Change Report + +Location Change Report indicates the requirement to communicate Cell or TAI to the PDN GW with this EPS bearer Context (see 3GPP TS 23.401 [74]) and is temporary data stored in MME and S4-SGSN. + +## 2.13.63 UE Specific DRX Parameters + +UE specific DRX parameters for A/Gb mode, Iu mode and S1-mode (see 3GPP TS 23.401[74]). UE specific DRX parameters are temporary data conditionally stored in MME. + +## 2.13.64 PDN-GW F-TEID for S5/S8 (user plane) + +F-TEID for S5/S8 (user plane) is defined in 3GPP TS 29.274[75]. PDN-GW F-TEID for S5/S8 (user plane) is temporary data conditionally stored in PDN-GW, MME, S4-SGSN and S-GW for each EPS Bearer within the PDN connection see 3GPP TS 23.401[74] and 3GPP TS 23.060 [21]. + +## 2.13.65 PDN GW F-TEID for S5/S8 (control plane) + +F-TEID for S5/S8 (control plane) is defined in 3GPP TS 29.274[75]. PDN-GW F-TEID for S5/S8 (control plane) is temporary data conditionally stored in PDN-GW, MME, S4-SGSN and S-GW. + +## 2.13.66 EPS Bearer ID + +An EPS bearer identity uniquely identifies an EPS bearer for one UE accessing via E-UTRAN, UTRAN, GERAN or an S2b bearer for one UE accessing via non-3GPP access with GTP on S2b. It also uniquely identifies an EPS bearer for a T6a connection to an SCEF. + +EPS Bearer ID is temporary data stored in MME, S4 SGSN, S-GW, ePDG(for GTP-based S2b only) and PDN-GW for each EPS Bearer or S2b bearer within the PDN connection see 3GPP TS 23.401[74], 3GPP TS 23.060 [21] and 3GPP TS 23.402 [77]. + +When EPS Bearer ID identifies a T6a connection, EPS Bearer ID is temporary data stored in the MME and in the SCEF, see 3GPP TS 29.128 [106]. + +## 2.13.67 EPS Bearer QoS + +EPS Bearer QoS contains QCI and ARP and optionally: GBR and MBR in case of GBR bearer. ARP contains a priority level, the preemption capability and the preemption vulnerability. EPS Bearer QoS is temporary data stored in MME, S4 SGSN, S-GW, ePDG(for GTP-based S2b only) and PDN-GW for each EPS Bearer within the PDN connection; see 3GPP TS 23.401 [74] , 3GPP TS 23.060 [21] and 3GPP TS 23.402 [77]. + +## 2.13.67A EPS Subscribed QoS Profile + +EPS Subscribed QoS Profile contains QoS parameters (QCI and ARP) for the EPS default bearer of an APN, and it is permanent data stored in HSS, MME and S4-SGSN. + +The QCI values allowed for the EPS Subscribed QoS Profile shall be only those associated to non-GBR bearers. + +## 2.13.68 UL TFT + +Uplink Traffic Flow Template for each EPS Bearer or S2b bearer within the PDN connection see 3GPP TS 23.401[74] and 3GPP TS 23.402 [77], and is temporary data stored in S-GW (for PMIP-based S5/S8 only), PDN-GW and ePDG (for GTP-based S2b only). + +## 2.13.69 DL TFT + +Downlink Traffic Flow Template for each EPS Bearer or S2b bearer within the PDN connection see 3GPP TS 23.401[74] and 3GPP TS 23.402 [77], and is temporary data stored in S-GW (for PMIP-based S5/S8 only) and PDN-GW. + +## 2.13.70 Charging Id + +Charging Id is defined in 3GPP TS 32.298[76] and temporary data conditionally stored in PDN-GW and S-GW for each EPS Bearer within the PDN connection see 3GPP TS 23.401[74]. + +## 2.13.71 EPS PDN Connection Charging Characteristics + +EPS PDN Connection Charging Characteristics are defined in 3GPP TS 32.251[84] as permanent subscriber data conditionally stored in the HSS, 3GPP AAA Server and temporary data conditionally stored in MME, S-GW, ePDG and PDN-GW for each PDN connection see 3GPP TS 23.401[74] and 3GPP TS 23.402 [77]. + +## 2.13.72 Default bearer + +Default bearer Identifies the EPS Bearer Id of the default bearer within the given PDN connection (see 3GPP TS 23.401[74] , 3GPP TS 23.060 [21] and 3GPP TS 23.402 [77] ) and is temporary data stored in MME , S4 SGSN, S-GW, ePDG (for GTP-based S2b only) and PGW. + +## 2.13.73 Void + +## 2.13.74 Void + +## 2.13.75 RAT Type (Access Type) + +RAT Type (radio access technology, access type) contains the current RAT type of the Last known access system. RAT Type is temporary data conditionally stored in HSS, 3GPP AAA Server, S4-SGSN, MME, S-GW, PDN-GW and ePDG. + +The parameter takes the values as defined for RAT-Type AVP in the 3GPP TS 29.212 [90]. + +## 2.13.76 S101 HRPD access node IP address + +S101 HRPD access node IP address contains the IP address of the HRPD AN used for the S101 tunnel for a UE (see 3GPP TS 23.402) and is temporary data stored conditionally in the MME. + +## 2.13.77 S103 Forwarding Address + +S103 Forwarding Address contains the HSGW IP address used for data forwarding to the HRPD access over S103 interface (see 3GPP TS 23.402) and is temporary data stored conditionally in the MME. + +## 2.13.78 S103 GRE key(s) + +GRE Key(s) used for the data forwarding tunnel to the HSGW - one per UE-PDN connection and is Temporary data conditionally stored S-GW. + +## 2.13.79 Permanent User Identity + +Permanent user identity is defined in 3GPP TS 23.003[5] and is permanent data mandatory stored in HSS, 3GPP AAA-server, 3GPP AAA-server proxy, PDN-GW S-GW and ePDG. + +## 2.13.80 Mobility Capabilities + +Mobility Capabilities is defined in 3GPP TS 29.273 [78] and is temporary data conditionally stored in ePDG, PDN-GW and 3GPP-AAA-server. + +## 2.13.81 MAG IP address + +MAG IP address is defined in 3GPP TS 29.273 [78] and is temporary data conditionally stored in 3GPP-AAA-server. + +## 2.13.82 Visited Network Identifier + +Visited Network Identifier is defined in 3GPP TS 29.273 [78] and is temporary data conditionally stored in 3GPP-AAA-server. + +## 2.13.83 EAP payload + +EAP payload is defined in 3GPP TS 29.273 [78]. and is temporary data conditionally stored in 3GPP-AAA-server. + +## 2.13.84 Void + +## 2.13.85 Void + +## 2.13.86 MIP Subscriber profile + +MIP Subscriber profile is defined in 3GPP TS 29.273 [78] and is temporary data conditionally stored in AAA-server and Trusted Non-3GPP or ePDG. + +## 2.13.87 Uplink S5 GRE Key + +Uplink traffic of a given PDN connection sent over PMIP-based S5 is encapsulated with the uplink S5 GRE key (see 3GPP TS 29.275[79]) and is temporary data stored in MME, SGW and PDN-GW. + +## 2.13.88 Downlink S5 GRE Key + +Downlink traffic of a given PDN connection sent over PMIP-based S5 is encapsulated with the downlink S5 GRE key (see 3GPP TS 29.275[79]) and is temporary data stored in SGW and PDN-GW. + +## 2.13.89 Uplink S8 GRE Key + +Uplink traffic of a given PDN connection sent over PMIP-based S8 is encapsulated with the S5/S8 uplink GRE key (see 3GPP TS 29.275[79]) and is temporary data stored in MME, SGW and PDN-GW. + +## 2.13.90 Downlink S8 GRE Key + +Downlink traffic of a given PDN connection sent over PMIP-based S8 is encapsulated with the S5/S8 uplink GRE key (see 3GPP TS 29.275[79]) and is temporary data stored in SGW and PDN-GW. + +## 2.13.91 S2a GRE Keys + +Traffic of a given PDN connection sent over PMIP-based S2a is encapsulated with the per-direction (uplink or downlink) S2a GRE key (see 3GPP TS 29.275[79]) and is temporary data stored in the Trusted non-3GPP Access' MAG, and SGW (S2a chained with S8) or PDN-GW (unchained S2a). + +## 2.13.92 S2b GRE Keys + +Traffic of a given PDN connection sent over PMIP-based S2b is encapsulated with the per-direction (uplink or downlink) S2b GRE key (see 3GPP TS 29.275[79]) and is temporary data stored in the ePDG, and SGW (S2b chained with S8) or PDN-GW (unchained S2b). + +## 2.13.93 Mobile Node Identifier + +Mobile Node Identifier is defined in 3GPP TS 29.275[79] and is temporary data stored in SGW and PDN-GW. + +For emergency attached UEs without IMSI (e.g. UICless UE) or with an unauthenticated IMSI, the Mobile Node Identifier is derived from the UE IMEI to identify the UE. + +## 2.13.94 IPv4 Default Router Address + +IPv4 Default Router Address (see 3GPP TS 29.275[79]) is temporary data stored in SGW and PDN-GW. + +## 2.13.95 Link-local address + +Link-local address (see 3GPP TS 29.275[79]) is temporary data stored in SGW and PDN-GW. + +## 2.13.96 Non 3GPP User Data + +Non 3GPP User Data (see 3GPP TS 29.273 [78]) is permanent data conditionally stored in HSS. The Non 3GPP User Data (or a subset of it) is stored as temporary data also in the 3GPP AAA Server, Trusted Non-3GPP access network and ePDG. A further subset, the APN context for the served PDN connection is stored in the PDN GW as temporary data. + +## 2.13.97 3GPP AAA Server Identity + +The 3GPP AAA Server Identity is the Diameter identity of the 3GPP AAA server defined in 3GPP TS 29.273 [78] and is temporary data stored in the HSS, PDN GW, Trusted Non-3GPP access network and ePDG. Absence of the 3GPP AAA Server Identity in the HSS indicates that the UE is not registered for EPS via non 3GPP access. + +## 2.13.98 Selected IP mobility mode + +IP mobility mode is defined in 3GPP TS 24.302 [82] and is temporary data conditionally stored in the 3GPP AAA Server, Trusted Non-3GPP access network and ePDG. + +## 2.13.99 Diameter Server Identity of HSS + +The Diameter Server Identity of HSS identifies the HSS storing the EPS related data of a user. The format of the Diameter Server Identity is the Diameter Identity defined in IETF RFC 3588 [51]. + +The Diameter Server Identity of the HSS is temporary data and is conditionally stored in MME, S4-SGSN and 3GPP AAA Server. + +## 2.13.100 SGSN name + +SGSN name is defined in 3GPP TS 23.003 [5]. + +The SGSN name is temporary subscriber data and is stored in the HSS, if S6d interface is supported. + +The SGSN name is temporary subscriber data and is stored in the CSS, if S7d interface is supported. Absence of the SGSN name in the CSS indicates that no subsequent update of the CSG subscription information is needed at the SGSN upon CSG subscription change. + +### 2.13.101 S-GW F-TEID for S12 + +F-TEID for S12 is defined in 3GPP TS 29.274[75]. S-GW F-TEID for S12 is temporary data conditionally stored in RNC and S-GW. + +### 2.13.102 RNC F-TEID for S12 + +F-TEID for S12 is defined in 3GPP TS 29.274[75]. RNC F-TEID for S12 is temporary data conditionally stored in RNC, S-GW and S4-SGSN. + +### 2.13.103 MME F-TEID for S3 + +F-TEID for S3 is defined in 3GPP TS 29.274[75]. MME F-TEID for S3 is temporary data conditionally stored in S4-SGSN and MME. + +### 2.13.104 S4-SGSN F-TEID for S3 + +F-TEID for S3 is defined in 3GPP TS 29.274[75]. S4-SGSN F-TEID for S3 is temporary data conditionally stored in S4-SGSN and MME. + +### 2.13.105 PDN GW Allocation Type + +PDN GW Allocation Type specifies if the PDN has been statically provisioned for a certain APN, or if it can be dynamically selected by the MME. It is permanent data stored in HSS, and temporary data stored in MME. + +### 2.13.106 S-GW F-TEID for S4 (control plane) + +F-TEID for S4 (control plane) is defined in 3GPP TS 29.274[75]. S-GW F-TEID for S4 (control plane) is temporary data conditionally stored in S4-SGSN and S-GW. + +### 2.13.107 S-GW F-TEID for S4 (user plane) + +F-TEID for S4 (user plane) is defined in 3GPP TS 29.274[75]. S-GW F-TEID for S4 (user plane) is temporary data conditionally stored in S4-SGSN and S-GW. + +### 2.13.108 RAT-Frequency-Selection-Priority-ID in Use + +The RFSP-ID in Use (see 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]) is temporary data conditionally stored in S4-SGSN, Gn/Gp-SGSN and MME. + +### 2.13.109 APN level APN-OI-Replacement + +APN level APN-OI-Replacement (see 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]) is permanent data conditionally stored in the HSS and MME/SGSN. + +APN level APN-OI-Replacement has the same role as UE level APN-OI-Replacement. + +If both the APN level APN-OI-Replacement and UE level APN-OI-Replacement are present, the APN level APN-OI-Replacement has a higher priority than UE level APN-OI-Replacement. + +### 2.13.110 Unauthenticated IMSI + +For an emergency attached UE with an unauthenticated IMSI, the Unauthenticated IMSI is temporary data stored in SGW and the PDN-GW. See 3GPP TS 29.275 [79]. + +### 2.13.111 PDN Connection ID + +PDN Connection ID (see 3GPP TS 29.275[79]) is used to uniquely identify a PDN Connection over PMIP based interface if multiple PDN Connections to the same APN is supported. PDN Connection ID is temporary data and is conditionally stored in SGW, PDN-GW, trusted-non-3GPP access or ePDG if both MAG and LMA support multiple PDN connection to the same APN. + +### 2.13.112 MS Network Capability + +MS network capabilities (see 3GPP TS 23.060 [21]) including security algorithms and capabilities which shall be supported by the MS. MS Network Capability is temporary data conditionally stored in MME and SGSN. + +### 2.13.113 Voice Domain Preference and UE's Usage Setting + +Voice domain preference and UE's usage setting (see 3GPP TS 24.008 [26]) provides the network with the UE's usage setting and the voice domain preference. The network uses the UE's usage setting and the voice domain preference to select the RFSP index in use as specified in 3GPP TS 23.401 [74]. Voice domain preference and UE's usage setting is temporary data conditionally stored in MME and SGSN. + +### 2.13.114 SIPTO Permission + +SIPTO Permission indicates whether the traffic associated with a particular APN is allowed or not for SIPTO above RAN, as defined in 3GPP TS 23.060 [21], 3GPP TS 23.401 [74] and 3GPP TS 23.402 [77]. + +The SIPTO Permission for the wild card APN shall apply to any APN that is not explicitly present in the subscription data. + +SIPTO Permission is permanent data and is conditionally stored in the HSS, MME, SGSN, 3GPP AAA Server and Trusted Non-3GPP access network (eHRPD). + +### 2.13.114A SIPTO Local Network Permission + +SIPTO Local Network Permission indicates whether the traffic associated with a particular APN is allowed or not for SIPTO at the Local Network, as defined in 3GPP TS 23.060 [21] and 3GPP TS 23.401 [74]. + +The SIPTO Local Network Permission for the wild card APN shall apply to any APN that is not explicitly present in the subscription data. + +SIPTO Local Network Permission is permanent data and is conditionally stored in the HSS, MME and SGSN. + +### 2.13.115 Subscribed Periodic RAU/TAU Timer + +The Subscribed Periodic RAU/TAU Timer (see 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]) is permanent data conditionally stored in the HLR/HSS, MME and SGSN. + +### 2.13.116 ePDG F-TEID for S2b (control plane) + +F-TEID for S2b (control plane) is defined in 3GPP TS 29.274[75]. ePDG F-TEID for S2b (control plane) is temporary data conditionally stored in ePDG (for GTP-based S2b only) and PGW. + +### 2.13.117 ePDG F-TEID for S2b (user plane) + +F-TEID for S2b (user plane) is defined in 3GPP TS 29.274[75]. ePDG F-TEID for S2b (user plane) is temporary data conditionally stored in ePDG (for GTP-based S2b only) and PGW. + +### 2.13.118 PGW F-TEID for S2b (control plane) + +F-TEID for S2b (control plane) is defined in 3GPP TS 29.274[75]. PGW F-TEID for S2b (control plane) is temporary data conditionally stored in ePDG (for GTP-based S2b only) and PGW. + +### 2.13.119 PGW F-TEID for S2b (user plane) + +F-TEID for S2b (user plane) is defined in 3GPP TS 29.274[75]. PGW F-TEID for S2b (user plane) is temporary data conditionally stored in ePDG (for GTP-based S2b only) and PGW. + +### 2.13.120 MPS CS Priority + +MPS CS Priority indicates that the UE is subscribed to the eMLPP in the CS domain, as defined in 3GPP TS 23.401 [74]. + +MPS CS Priority is permanent data and is conditionally stored in the MME. + +NOTE: The MME gets the MPS CS Priority information from the HLR/HSS, which derives this information from the eMLPP Subscription Data as defined in the 3GPP TS 29.002 [27]. + +### 2.13.121 MPS EPS Priority + +MPS EPS Priority indicates that the UE is subscribed to the MPS in the EPS domain, as defined in 3GPP TS 23.401 [74]. + +MPS EPS Priority is permanent data and is conditionally stored in the HLR/HSS and MME. + +### 2.13.122 LIPA Permission + +LIPA Permission indicates whether the corresponding APN is allowed to be accessed via Local IP Access, as defined in 3GPP TS 23.060 [21] and 3GPP TS 23.401 [74]. + +The LIPA Permission for a Wildcard APN applies to any APN that is not explicitly present in the subscription data. + +LIPA Permission is permanent data and is conditionally stored in the HLR/HSS, MME and SGSN. + +### 2.13.123 LIPA Allowed VPLMN List + +LIPA Allowed VPLMN List indicates the PLMNs where the UE is allowed to use LIPA, it is permanent data and is conditionally stored in the HLR/HSS. + +### 2.13.124 VPLMN LIPA Allowed + +VPLMN LIPA Allowed indicates whether the UE is allowed to use LIPA in the PLMN where the UE is attached, as defined in the 3GPP TS 23.060 [21] and the 3GPP TS 23.401 [74]. + +VPLMN LIPA Allowed is permanent data and is conditionally stored in the MME and the SGSN. + +### 2.13.125 Relay Node Indicator + +Relay Node Indicator indicates whether the subscriber is a Relay Node (see 3GPP TS 36.300 [88]). + +Relay Node Indicator is permanent data and is conditionally stored in the HLR/HSS and MME. + +### 2.13.126 Restricted RAT Types + +Restricted RAT Types contains the RAT types that are disallowed for a user when accessing EPS service from non-3GPP accesses. + +Restricted RAT Types is permanent subscriber data and is conditionally stored in the HLR/HSS, 3GPP AAA Server, UDM and AMF. + +The parameter takes either of the following values: + +- WLAN not allowed, the subscriber shall not be allowed to access the network using WLAN radio access. Valid for Idle and Connected mode; +- CDMA2000\_1X not allowed, the subscriber shall not be allowed to access the network using CDMA2000\_1X radio access. Valid for Idle and Connected mode; +- HRPD not allowed, the subscriber shall not be allowed to access the network using HRPD radio access. Valid for Idle and Connected mode; +- UMB not allowed, the subscriber shall not be allowed to access the network using UMB radio access. Valid for Idle and Connected mode; +- EHPRD not allowed, the subscriber shall not be allowed to access the network using EHPRD radio access. Valid for Idle and Connected mode. + +## 2.13.127 Higher bitrates than 16Mbps flag + +Higher bitrates than 16Mbps flag (see 3GPP TS 23.060 [21]) is temporary data conditionally stored in Gn/Gp-SGSN or S4-SGSN. + +## 2.13.128 Void + +## 2.13.129 UE Local IP Address + +UE Local IP Address is defined in 3GPP TS 23.139 [91]. UE Local IP Address is temporary data conditionally stored in the ePDG. + +## 2.13.130 UE UDP Port Number + +UE UDP Port Number is defined in 3GPP TS 23.139 [91]. UE UDP Port Number is temporary data conditionally stored in the ePDG. + +## 2.13.131 H(e)NB Local IP Address + +H(e)NB Local IP Address is defined in 3GPP TS 23.139 [91]. H(e)NB Local IP Address is temporary data conditionally stored in the MME, S4-SGSN, and P-GW. + +## 2.13.132 H(e)NB UDP Port Number + +H(e)NB UDP Port Number is defined in 3GPP TS 23.139 [91]. H(e)NB UDP Port Number is temporary data conditionally stored in the MME, S4-SGSN, and P-GW. + +## 2.13.133 Diameter Server Identity of CSS + +The Diameter Server Identity of CSS identifies the CSS storing the VPLMN CSG Roaming subscription related data of a user. The format of the Diameter Server Identity is the Diameter Identity defined in IETF RFC 3588 [51]. + +The Diameter Server Identity of the CSS is temporary data and is conditionally stored in MME and S4-SGSN. + +## 2.13.134 MME/S4 SGSN Identifier + +MME/S4-SGSN Identifier is defined in 3GPP TS 29.274 [75]. MME/S4 SGSN Identifier is temporary data conditionally stored in the SGW and PGW. + +## 2.13.135 SGW node name + +SGW node name is defined in 3GPP TS 29.274 [75]. SGW node name is temporary data conditionally stored in the MME/S4 SGSN. + +## 2.13.136 Co-located GGSN-PGW FQDN + +Co-located GGSN-PGW FQDN is defined in 3GPP TS 29.060 [29]. Co-located GGSN-PGW FQDN is temporary data conditionally stored in the MME/S4 SGSN/Gn/Gp SGSN. + +## 2.13.137 GERAN Cell Identity Age + +GERAN Cell Identity Age contains time elapsed since the last GERAN Cell Global Identity was acquired (see 3GPP TS 23.060 [21]) and is temporary data stored in SGSN. + +## 2.13.138 UTRAN Service Area Identity Age + +UTRAN Service Area Identity Age contains time elapsed since the last UTRAN Service Area Identity Age was acquired (see 3GPP TS 23.060 [21]) and is temporary data stored in SGSN. + +## 2.13.139 Default APN for Trusted WLAN + +The Default APN for Trusted WLAN identifies the subscriber's default APN to be used for Trusted WLAN access to EPC over S2a in the Transparent single-connection mode. For detailed content see 3GPP TS 29.273 [78]. + +The Default APN for Trusted WLAN is permanent data conditionally stored in the HSS and 3GPP AAA Server. + +## 2.13.140 Access Information for Trusted WLAN + +The list of Access Information for Trusted WLAN contains information about the allowed access methods (i.e. EPC access and/or non-seamless WLAN offload) for a subscriber connecting via a trusted WLAN. For detailed content see 3GPP TS 29.273 [78]. + +The list of Access Information for Trusted WLAN is permanent data conditionally stored in the HSS and 3GPP AAA Server. + +## 2.13.141 Homogeneous Support of IMS Voice over PS Sessions + +Homogeneous Support of IMS Voice over PS Sessions (see 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]) is temporary data stored in the HSS/HLR, SGSN and MME. + +## 2.13.142 Signalling Priority Indication + +Signalling Priority Indication indicates that the UE signalled low access priority when the UE established the PDN connection or PDP context, as defined in 3GPP TS 23.401[74] and 3GPP TS 23.060 [21]. + +Signalling Priority Indication is temporary data conditionally stored in Gn/Gp-SGSN, S4-SGSN, MME, GGSN, SGW or PGW. + +## 2.13.143 Restoration Priority + +Restoration Priority is defined in 3GPP TS 23.007 [6]. It indicates the relative priority of a user's PDN connection among PDN connections to the same APN when restoring PDN connections affected by an SGW or PGW failure/restart. + +Restoration Priority is permanent subscriber data conditionally stored in the HSS, MME and S4-SGSN. + +## 2.13.144 Void + +## 2.13.145 Presence Reporting Area Action + +Presence Reporting Area Action is defined in in 3GPP TS 23.060 [21] and in 3GPP TS 23.401 [74]. It denotes whether the MME/SGSN is requested to report changes of UE presence in Presence Reporting Area, and include the Presence Reporting Area Identifier, and the list of Presence Reporting Area elements if provided by the PGW. + +Presence Reporting Area Action is temporary data conditionally stored in the MME, S4-SGSN and PGW. + +## 2.13.146 WLAN offloadability + +The WLAN offloadability information is a bitmask which indicates whether the traffic associated with the APN is allowed to be offloaded to WLAN from UTRAN or E-UTRAN. For detailed content see 3GPP TS 29.272 [81]. + +WLAN offloadability is permanent data and conditionally stored in HSS, MME, S4-SGSN. + +## 2.13.147 CN Assistance Information + +### 2.13.147.1 General + +CN Assistance Information is a set of parameters which are calculated in the MME for the Core Network assisted eNodeB parameters tuning (see 3GPP TS 23.401 [74]); these parameters aid the eNodeB to minimize the UE state transitions and achieve optimum network behaviour. + +### 2.13.147.2 Expected UE Activity Behaviour + +The Expected UE Activity Behaviour (see 3GPP TS 36.413 [101]) indicates the expected pattern of the UE's changes between ECM-CONNECTED and ECM-IDLE states. + +Expected UE Activity Behaviour is temporary subscriber data and is conditionally stored in the MME. + +### 2.13.147.3 Expected HO Interval + +The Expected HO Interval (see 3GPP TS 36.413 [101]) indicates the expected time interval between inter-eNB handovers of the UE. + +Expected HO Interval is temporary subscriber data and is conditionally stored in the MME. + +## 2.13.148 Active Time Value for PSM + +Active Time Value for PSM is defined in 3GPP TS 23.401[74] and 3GPP TS 23.060 [21]. Active Time Value for PSM is temporary data conditionally stored in MME, S4-SGSN and Gn/Gp-SGSN. + +## 2.13.149 Origination Time Stamp + +The Origination Time Stamp indicates the time at which an entity originates a request. This is used for detecting and handling requests which collide with an existing session context. See 3GPP TS 29.274 [75]. + +The Origination Time Stamp is temporary data conditionally stored in PGW, 3GPP AAA Server and PCRF. + +## 2.13.150 DL Data Buffer Expiration Time + +DL Data Buffer Expiration Time is defined in 3GPP TS 23.060 [21] and 3GPP TS 23.401 [74]. It indicates the time until the SGW buffers DL data, for a UE that is transiently not reachable due to power saving functions, when the MME or SGSN has requested extended buffering at the SGW. + +DL Data Buffer Expiration Time is temporary data conditionally stored in the MME, SGSN and SGW. + +## 2.13.151 DL Buffering Suggested Packet Count + +DL Buffering Suggested Packet Count is defined in 3GPP TS 23.060 [21] and 3GPP TS 23.401 [74]. It indicates the number of downlink packets the MME or SGSN suggests the SGW to store, for a UE that is transiently not reachable due to power saving functions, when the MME or SGSN requests extended buffering at the SGW. + +DL Buffering Suggested Packet Count is permanent data conditionally stored in the HSS/HLR, MME, and the SGSN. + +NOTE: The number of downlink packets the SGW decides to buffer is an implementation choice of the SGW, which can be dependent on the DL Buffering Suggested Packet Count. + +## 2.13.152 Notify-on-available-after-DDN-failure flag + +The Notify-on-available-after-DDN-failure flag is defined in 3GPP TS 23.682 [102]. + +The Notify-on-available-after-DDN-failure flag is temporary data conditionally stored in the MME and S4-SGSN. + +## 2.13.153 IMSI Group Identifier List + +IMSI Group Identifier (IMSI-Group-Id) is defined in 3GPP TS 23.003 [5]. + +A list of IMSI Group Identifier may be stored within the subscription data for a subscriber. + +The IMSI Group Identifier List is permanent subscriber data conditionally stored in HSS, SGSN, MME, UDM and AMF. + +## 2.13.154 UE Usage Type + +The UE Usage Type indicates the usage characteristics of the UE for use with Dedicated Core Networks (DCN); it is subscription information that enables the UE to be served by a specific DCN (i.e., one or more MME/SGSN and optionally one or more SGW/PGW/PCRF), as described in 3GPP TS 23.401 [74]. + +UE Usage Type is permanent data and conditionally stored in HSS, MME, SGSN, UDM and AMF. + +## 2.13.155 Emergency Indication + +The Emergency Indication information indicates a UE request to establish a PDN connection for emergency services. See 3GPP TS 24.302 [82] and 3GPP TS 29.273 [78]. + +Emergency Indication is temporary data conditionally stored in the ePDG, 3GPP AAA Server and 3GPP AAA Proxy. + +## 2.13.156 Remote UE Contexts + +Remote UE Contexts is defined in 3GPP TS 29.274 [21]. Remote UE Contexts is temporary data conditionally stored in MME, SGW and PGW. + +## 2.13.157 Extended Idle Mode DRX parameters + +The Extended Idle Mode DRX parameters is defined in 3GPP TS 23.401 [74]. + +The Extended Idle Mode DRX parameters is temporary data conditionally stored in the MME and SGSN. + +The Extended Idle Mode DRX cycle length (a part of the Extended Idle Mode DRX parameters) is permanent data stored in HSS. + +## 2.13.158 Delay Tolerant Connection Indication + +Delay Tolerant Connection Indication is defined in the 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]. Delay Tolerant Connection Indication is permanent data conditionally stored in MME, S4-SGSN, Gn/Gp-SGSN, PGW and GGSN. + +## 2.13.159 Pending Network Initiated PDN Connection Signalling Indication + +Pending Network Initiated PDN Connection Signalling Indication is defined in the 3GPP TS 23.401 [74] and 3GPP TS 23.060 [21]. Pending Network Initiated PDN Connection Signalling Indication is temporary data conditionally stored in MME, S4-SGSN and Gn/Gp-SGSN. + +## 2.13.160 UE Radio Capability for Paging information + +UE Radio Capability for Paging information is defined in the clause 5.11.4 of 3GPP TS 23.401 [74]. UE Radio Capability for Paging information is temporary data conditionally stored in MME. + +## 2.13.161 Information on Recommended Cells and ENBs for Paging + +Information on Recommended Cells and ENBs for Paging is defined in 3GPP TS 23.401 [74]. + +Information on Recommended Cells and ENBs for Paging is temporary data conditionally stored in the MME. + +## 2.13.162 Paging Attempt Count + +Paging Attempt Count is defined in 3GPP TS 23.401 [74]. + +Paging Attempt Count is temporary data conditionally stored in the MME. + +## 2.13.163 User Plane Integrity Protection Indicator + +User Plane Integrity Protection Indicator is defined in 3GPP TS 43.020 [31]. + +User Plane Integrity Protection Indicator is permanent data conditionally stored in the HSS and SGSN. + +## 2.13.164 Non-IP-PDN-Type-Indicator + +Non-IP-PDN-Type-Indicator is defined in 3GPP TS 29.272 [81]. It indicates whether the PDN type of the corresponding APN is Non-IP. + +Non-IP-PDN-Type-Indicator is permanent subscriber data conditionally stored in the HSS and MME. + +## 2.13.165 Non-IP-Data-Delivery-Mechanism + +Non-IP-Data-Delivery-Mechanism is defined in 3GPP TS 29.272 [81]. It indicates the mechanism to be used for Non-IP Data Delivery over a certain APN. + +The parameter takes either of the following values: + +- SGi-Based-Data-Delivery; +- SCEF-Based-Data-Delivery. + +Non-IP-Data-Delivery-Mechanism is permanent subscriber data conditionally stored in the HSS and MME. + +## 2.13.166 SCEF-ID + +SCEF-ID is defined in 3GPP TS 29.272 [81]. It indicates the identity (FQDN) of the SCEF to be used for Non-IP Data Delivery over a certain APN, when the selected data delivery mechanism is SCEF-based. + +SCEF-ID is permanent subscriber data conditionally stored in the HSS and MME. + +## 2.13.167 PDN Type + +PDN Type is defined in 3GPP TS 29.274 [81]. It indicates whether the PDN type is IPv4, IPv6, IPv4v6, Non-IP, or Ethernet. + +PDN Type is permanent subscriber data conditionally stored in the HSS, S4-SGSN, MME, SGW and PGW. + +NOTE: The S4-SGSN doesn't support Ethernet PDN type. + +## 2.13.168 PDN-Connection-Restricted flag + +The PDN-Connection-Restricted flag is defined in 3GPP TS 29.272 [81]. It indicates whether a registration without a PDN connection is enforced for this user when applicable. + +The PDN-Connection-Restricted flag is permanent subscriber data conditionally stored in the HSS and MME. + +## 2.13.169 Preferred-Data-Mode + +Preferred-Data-Mode is defined in 3GPP TS 29.272 [81]. It indicates, for an SGi PDN connection, whether it is preferred to transmit the user's traffic associated to the APN over the User Plane or the Control Plane. + +Preferred-Data-Mode is permanent subscriber data conditionally stored in the HSS and MME. + +## 2.13.170 IOV\_updates counter + +IOV\_updates counter is defined in the 3GPP TS 29.060 [29]. IOV\_updates counter is temporary data conditionally stored in a Gn/Gp-SGSN and S4-SGSN. + +## 2.13.171 Emergency Info + +Emergency Info is defined in 3GPP TS 29.272 [81]. It contains the identity of the PGW dynamically allocated for emergency services. + +Emergency Info is temporary subscriber data conditionally stored in the HSS, 3GPP AAA Server, MME and ePDG. + +## 2.13.172 Dedicated Core Network Identifier + +Dedicated Core Network Identifier is defined in the 3GPP TS 23.003 [5]. Dedicated Core Network Identifier is temporary data conditionally stored in a Gn/Gp-SGSN, S4-SGSN and MME. + +## 2.13.173 Acknowledgements Of Downlink NAS Data PDUs flag + +The Acknowledgement Of Downlink NAS Data PDUs flag is defined in 3GPP TS 29.272 [81]. It indicates whether acknowledgement of downlink NAS data PDUs for Control Plane CIoT Optimization is disabled for the UE. + +The Acknowledgement Of Downlink NAS Data PDUs flag is permanent subscriber data conditionally stored in the HSS and MME. + +## 2.13.174 Service Gap Time + +The Service Gap Time is defined in 3GPP TS 29.272 [81]. It indicates the minimum number of seconds during which the UE shall stay in ECM-IDLE mode, after leaving the ECM-CONNECTED mode, before being allowed to send a subsequent connection request to enter ECM-CONNECTED mode again. + +The Service Gap Time is permanent subscriber data conditionally stored in the HSS and MME. + +## 2.13.175 Subscribed Additional RRM Policy Index + +The Subscribed Additional RRM Policy Index (see 3GPP TS 23.401 [74]) is permanent data conditionally stored in HSS and MME. + +## 2.13.176 Additional RRM Policy Index in Use + +The Additional RRM Policy Index in Use (see 3GPP TS 23.401 [74]) is temporary data conditionally stored in MME. + +## 2.13.177 Ethernet-PDN-Type-Indicator + +Ethernet-PDN-Type-Indicator is defined in 3GPP TS 29.272 [81]. It indicates whether the PDN type of the corresponding APN is Ethernet. + +Ethernet-PDN-Type-Indicator is permanent subscriber data conditionally stored in the HSS and MME. + +# 2.14 Data related to CAMEL + +## 2.14.1 Subscriber Data stored in HLR + +### 2.14.1.1 Originating CAMEL Subscription Information (O-CSI) + +This data defines the contents of the Originating CAMEL subscription information used to interwork with the gsmSCF for MO and MF call. It consists of: + +- A TDP list. The TDP list is a list of TDP descriptions. Each TDP description contains the following elements: + 1. DP Value. The DP value identifies the DP in the MO State Model where service triggering may take place. For O-CSI, the allowed DP value are *DP Collected\_info*, *DP Route\_Select\_Failure*. + 2. A gsmSCF address. It is the gsmSCF address ( E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey. + 3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each TDP. + 4. A default Call Handling. The default call handling indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey. + 5. DP criteria. The DP criteria indicates on which criteria the gsmSSF shall access the gsmSCF. DP criteria is associated to each TDP. + +| TDP | Triggering Criteria (see note) | ServiceKey | gsmSCF address | Default Call Handling | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|----------------|--------------------------|---------------------------| +| DP Collected_ Info | No Criterion
Number criteria
Basic service code criteria
Call type criteria | One ServiceKey | One E.164 gsmSCF address | One Default call handling | +| DP Route_Select_ Failure | No criterion
Cause value criteria | One ServiceKey | One E.164 gsmSCF address | One Default call handling | +| NOTE: One or more TDP criteria shall be applicable. All applicable triggering criteria must be satisfied before the dialogue is established with the gsmSCF. | | | | | + +- CAMEL capability handling. It gives the CAMEL phase associated to the O-CSI (CAMEL phase 1, phase 2, phase 3, or phase 4). + +- The CSI state. The CSI state indicates whether the O-CSI is active or not. +- The notification flag, the notification flag indicates whether changes of the O-CSI shall trigger Notification on Change of Subscriber Data. + +### 2.14.1.2 Terminating CAMEL Subscription Information (T-CSI) and VMSC Terminating CAMEL Subscription Information (VT-CSI)); + +This data defines the contents of the terminating CAMEL subscription information used to interwork with the gsmSCF for MT call. It consists of: + +- A TDP list. The TDP list is a list of TDP descriptions. Each TDP description contains the following elements: + 1. DP Value. The DP value identifies the DP in the MT State Model where service triggering may take place. For T-CSI, the allowed DP value are DP Terminating\_Attempt\_Authorised, DP T\_Busy, DP T\_No\_Answer. + 2. A gsmSCF address. It is the gsmSCF address (E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey. + 3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each TDP. + 4. A default Call Handling. The default call handling indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey. + 5. DP criteria. The DP criteria indicates on which criteria the gsmSSF shall access the gsmSCF. DP criteria is associated to each TDP. + +| TDP | Triggering Criteria
(see note) | ServiceKey | gsmSCF
address | Default Call
Handling | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|--------------------|--------------------------------|----------------------------------| +| DP Terminating_
Attempt_Authorised | No Criterion
Basic service criteria | One serviceKey | One E.164
gsmSCF
address | One Default call
handling | +| DP T_Busy | No criterion
Cause value criteria | One serviceKey | One E.164
gsmSCF
address | One Default call
handling | +| DP T_No_Answer | No criterion
Cause value criteria | One
service Key | One E.164
gsmSCF
address | One Default call
handling | +| NOTE: One or more TDP criteria shall be applicable. All applicable triggering criteria must be satisfied before the dialogue is established with the gsmSCF. | | | | | + +- CAMEL capability handling. It gives the CAMEL phase associated to the T-CSI/VT-CSI (CAMEL phase1, phase2, or phase3, or phase4). +- The CSI state indicates whether the T-CSI/VT-CSI is active or not. +- Notification flag. The notification flag indicates whether the change of the T-CSI/VT-CSI shall trigger Notification on Change of Subscriber data. + +### 2.14.1.3 Location information/Subscriber state interrogation. + +This data item indicates whether or not the HLR shall send the location information and state of the called subscriber, as available, when a GMSC requests routing information for an MT call. + +### 2.14.1.4 USSD CAMEL subscription information(U-CSI) + +This data is used on USSD request receipt from the MS. It consists of a list of: + +- a service code: the service code defines a specific application in the gsmSCF; + +- a gsmSCFaddress: it is the gsmSCF address (E.164 number) where the USSD application is treated for this subscriber. + +#### 2.14.1.5 Supplementary Service invocation notification(SS-CSI) + +This data is used to notify the gsmSCF about Supplementary service invocation. It consists of: + +- notification criterion, which may be a list of Supplementary Service(s). The possible Supplementary Services are: ECT, CD or MPTY, CCBS; +- a gsmSCFaddress: it is the gsmSCF address (E.164 number) where the notification of the Supplementary Service invocation is treated for this subscriber; +- CSI state, indicates whether the SS-CSI is active or not; +- notification flag: it indicates whether the change of the SS-CSI shall trigger Notification on Change of Subscriber data. + +#### 2.14.1.6 Translation Information flag (TIF-CSI) + +- TIF-CSI flag is used to indicate that the HLR shall not attempt to perform any actions on the FTN (translation, prohibited FTN checks, call barring checks) at the registration procedure. +- Notification flag. The notification flag indicates whether the change of TIF-CSI flag shall trigger Notification on Change of Subscriber data. + +#### 2.14.1.7 Mobility Management event notification (M-CSI) + +This data indicates which Mobility Management events shall be reported to the gsmSCF. It consists of: + +- gsmSCF address: this is the address of the gsmSCF where the Mobility Management event notification shall be sent to. The gsmSCF address is in E.164 format. +- ServiceKey: the serviceKey is included in the notification to the gsmSCF and indicates to the gsmSCF which Service Logic shall be applied. +- Mobility Management Triggers: these triggers define which Mobility Managements events shall be reported to the gsmSCF. The mobility managements triggers may contain one or any combination of the following elements: + - Location update in the same VLR service area; + - Location update to another VLR service area; + - IMSI attach; + - MS initiated IMSI detach (explicit detach); + - Network initiated IMSI detach (implicit detach). +- The CSI state, indicates whether the M-CSI is active or not. +- Notification flag. The notification flag indicates whether the change of M-CSI shall trigger Notification on Change of Subscriber data. + +#### 2.14.1.8 Mobile Originated Short Message Service CAMEL Subscription Information (MO-SMS-CSI) + +This data defines the contents of the MO SMS CAMEL subscription information. The MO SMS CAMEL Subscription Information is used for the following interworking: + +- Interworking between gsmSCF and gsmSSF, for CAMEL control of circuit switched MO SMS; +- Interworking between gsmSCF and gprsSSF, for CAMEL control of packet switched MO SMS. + +MO-SMS-CSI consists of the following data items: + +- TDP List. The TDP list is a list of SMS TDP descriptions. Each TDP description contains the following elements: + 1. DP Value. The DP value identifies the DP in the MO SMS State Model where service triggering may take place. +For MO-SMS-CSI, the only allowed DP value is *SMS\_Collected\_Info*. + 2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MO SMS CAMEL Service associated with this TDP, is located for this subscriber. + 3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied. + 4. Default SMS handling. The default SMS handling indicates whether the MO SMS submission request shall be rejected or continued in the case of error in the dialogue between the gsmSSF and gsmSCF or between the gprsSSF and gsmSCF; +- CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MO SMS service. The CAMEL Capability Handling for MO-SMS-CSI shall have the value CAMEL phase 3. +- CSI state: indicates whether the MO-SMS-CSI is active or not. +- Notification flag indicates whether the change of the SMS-CSI shall trigger Notification on change of subscriber Data or not. + +#### 2.14.1.9 Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI) + +This data defines the contents of the mobile terminating short message service CAMEL subscription information. The MT-SMS-CSI CAMEL Subscription Information is used for the following interworking: + +- Interworking between gsmSCF and gsmSSF, for CAMEL control of circuit switched MT SMS; +- Interworking between gsmSCF and gprsSSF, for CAMEL control of packet switched MT SMS. + +MT-SMS-CSI consists of the following data items: + +- TDP List. The TDP list is a list of MT SMS TDP descriptions. Each TDP description contains the following elements: + 1. DP Value. The DP value identifies the DP in the MT SMS State Model where service triggering may take place. +For MT-SMS-CSI, the only allowed DP value is DP SMS-Delivery-Request + 2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MT SMS CAMEL Service associated with this TDP, is located for this subscriber. + 3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied. + 4. Default SMS handling. The default SMS handling indicates whether the MT SMS delivery request shall be rejected or continued in the case of error in the dialogue between the gsmSSF and gsmSCF or between the gprsSSF and gsmSCF. + 5. DP criterion. The DP criterion indicates on which criterion the gsmSSF shall access the gsmSCF. A DP criterion is associated with each TDP. For MT-SMS the DP criterion is the TDPU type. The criterion may be absent. + +| TDP | Triggering Criterion | ServiceKey | gsmSCF address | Default SMS Handling | +|-------------------------|-----------------------------|-------------------|--------------------------|-----------------------------| +| DP SMS-Delivery Request | TDPU type | One serviceKey | One E.164 gsmSCF address | One Default SMS handling | + +- CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MT SMS service. The CAMEL Capability Handling for MT-SMS-CSI shall have the value CAMEL phase 4. +- CSI state: indicates whether the MT-SMS-CSI is active or not. +- Notification flag indicates whether the change of the MT-SMS-CSI shall trigger Notification on change of subscriber Data or not. + +#### 2.14.1.10 GPRS CAMEL Subscription Information (GPRS-CSI) + +This data defines the contents of the GPRS CAMEL subscription information. The GPRS CAMEL Subscription Information is used for the interworking between gsmSCF and gprsSSF, for CAMEL control of packet switch call. + +GPRS-CSI consists of the following data items: + +- TDP List. The TDP list is a list of GPRS TDP descriptions. Each TDP description contains the following elements: + 1. DP Value. The DP value identifies the DP in the GPRS State Model where service triggering may take place. + 2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the GPRS CAMEL Service associated with this TDP, is located for this subscriber. + 3. Service Key. The service key identifies to the gsmSCF the service logic that shall be applied. + 4. Default GPRS handling. The default GPRS handling indicates whether the GPRS submission request shall be rejected or continued in the case of error in the dialogue between the gprsSSF and gsmSCF. +- CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the GPRS service. The CAMEL Capability Handling for GPRS-CSI shall have the value CAMEL phase 3. +- The CSI state indicates whether the GPRS-CSI is active or not. +- The notification flag indicates whether the change of the GPRS-CSI shall trigger Notification on change of subscriber Data or not. + +#### 2.14.1.11 Dialled service CAMEL Subscription Information (D-CSI) + +This data defines the contents of the dialled service CAMEL subscription information used to interwork with the gsmSCF for MO and MF call. It is applicable at TDP Analysed Info. It consists of: + +- DP Criteria list. This consists of 1 to 10 entries. Each entry shall contain the following items: + 1. DP Criterion. It indicates when the gsmSSF shall request gsmSCF for instructions. It is a destination number. + 2. A gsmSCF address. It is the gsmSCF address (E.164 number) where this Subscribed Dialled CAMEL service is treated for the subscriber. A gsmSCF address is associated to each DP Criterion. + 3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each DP Criterion. + 4. A default Call Handling. It indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each DP Criterion. +- CAMEL capability handling. It indicates the CAMEL phase associated to the D-CSI (CAMEL phase3, or Camel phase4 shall be indicated). +- CSI state: indicates whether the D-CSI is active or not. +- Notification Flag. It indicates whether the change of the D-CSI shall trigger the Notification on Change of Subscriber Data. + +## 2.14.1.12 Mobility Management for GPRS event notification (MG-CSI) + +This data indicates which Mobility Management for GPRS subscriber events shall be reported to the gsmSCF. It consists of: + +- gsmSCF address: this is the address of the gsmSCF where the Mobility Management event notification shall be sent to. The gsmSCF address is in E.164 format. +- Service Key: the service key is included in the notification to the gsmSCF and indicates to the gsmSCF which Service Logic shall be applied. +- Mobility Management Triggers: these triggers define which Mobility Managements events shall be reported to the gsmSCF. The mobility management triggers may contain one or any combination of the following elements: + - Routeing area update of MS to a different SGSN service area; + - Routeing area update of MS within the same SGSN service area; + - GPRS attach (e.g. MS switched on, successful routeing area update after network initiated detach); + - MS-initiated GPRS detach (e.g. MS switched off); + - Network-initiated transfer to the "not reachable for paging" state (the network has not received a periodic routeing area update from the MS and assumes that the MS is unreachable). +- The CSI state indicates whether the MG-CSI is active or not. +- Notification flag. The notification flag indicates whether the change of MG-CSI shall trigger Notification on Change of Subscriber data. + +## 2.14.2 Other Data stored in the HLR + +### 2.14.2.1 Negotiated CAMEL Capability Handling + +The HLR shall have a set of *negotiated CAMEL Capability Handling* variables. Each CSI that may be downloaded to the VLR or to the SGSN shall have a negotiated CAMEL Capability Handling (CCH) variable associated with it. + +The negotiated CCH variable for a CSI indicates what CAMEL Phase is indicated in that CSI in the VLR or SGSN. + +When the negotiated CCH variable has a value NULL, it indicates that the given CSI has not been downloaded to the VLR or SGSN. + +The following table shows the *negotiated CAMEL Capability Handling* variables. + +| Variable name | Associated CSI | CSI stored in | Allowable values for negotiated CCH | +|------------------------------------------------------|----------------|---------------|-------------------------------------| +| O-CSI Negotiated CAMEL Capability Handling | O-CSI | VLR | NULL, 1, 2, 3, 4 | +| D-CSI Negotiated CAMEL Capability Handling | D-CSI | VLR | NULL, 3, 4 | +| SS-CSI Negotiated CAMEL Capability Handling | SS-CSI | VLR | NULL, 2 | +| VT-CSI Negotiated CAMEL Capability Handling | VT-CSI | VLR | NULL, 3, 4 | +| MO-SMS-CSI VLR Negotiated CAMEL Capability Handling | MO-SMS-CSI | VLR | NULL, 3 | +| MT-SMS-CSI VLR Negotiated CAMEL Capability Handling | MT-SMS-CSI | VLR | NULL, 4 | +| M-CSI Negotiated CAMEL Capability Handling | M-CSI | VLR | NULL, 3 | +| MG-CSI Negotiated CAMEL Capability Handling | MG-CSI | SGSN | NULL, 4 | +| MO-SMS-CSI SGSN Negotiated CAMEL Capability Handling | MO-SMS-CSI | SGSN | NULL, 3 | +| MT-SMS-CSI SGSN Negotiated CAMEL Capability Handling | MT-SMS-CSI | SGSN | NULL, 4 | +| GPRS-CSI Negotiated CAMEL Capability Handling | GPRS-CSI | SGSN | NULL, 3 | + +There is no *negotiated CAMEL Capability Handling* variable associated with TIF-CSI. + +The HLR does not store a *Negotiated CAMEL Capability Handling* for CSIs that are sent to the GMSC, since a subscriber is not permanently registered in a GMSC. + +## 2.14.2.2 Supported CAMEL Phases + +The HLR shall store the supported CAMEL Phases of the VLR where the subscriber is currently registered and the SGSN where the subscriber is currently attached. + +The following variables are required: + +- VLR Supported CAMEL Phases +- SGSN Supported CAMEL Phases + +The HLR does not store the Supported CAMEL Phases of the GMSC, since a subscriber is not permanently registered at a GMSC. + +## 2.14.2.2A Offered CAMEL4 CSIs + +The HLR shall store the offered CAMEL4 CSIs of the VLR where the subscriber is currently registered and the SGSN where the subscriber is currently attached. + +The following variables are required: + +- VLR Offered CAMEL4 CSIs +- SGSN Offered CAMEL4 CSIs + +The HLR does not store the Offered CAMEL4 CSIs of the GMSC, since a subscriber is not permanently registered at a GMSC. + +## 2.14.2.3 UG-CSI + +The USSD general CAMEL service(UG-CSI) is also stored in the HLR. This data is used on USSD request receipt from the MS. It consists of a list of: + +- a service code. The service code defines a specific application in the gsmSCF; +- a gsmSCFaddress. It is the gsmSCF address (E.164 number) where the USSD application is treated for this subscriber. + +## 2.14.2.4 gsmSCF address for CSI + +This information element contains the list of gsmSCF address (E.164 address) to which Notification on Change of Subscriber Data is to be sent. + +# 2.14.3 Subscriber data stored in VLR + +## 2.14.3.1 Originating CAMEL Subscription Information (O-CSI) + +The Originating CAMEL Subscription Information (O-CSI) are stored in the VLR. + +This data defines the contents of the originating CAMEL subscription information used to interwork with the gsmSCF for MO and CF calls. It consists of: + +- A TDP list: The TDP list is a list of TDP descriptions. Each TDP description contains the following elements: + 1. DP Value. The DP value identifies the DP in the MO State Model where service triggering may take place. For O-CSI, the allowed DP value are *DP Collected\_info*, *DP Route\_Select\_Failure*. + 2. A gsmSCF address. It is the gsmSCF address (E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey. + +3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic.. A serviceKey is associated to each TDP. + 4. A default Call Handling. The default call handling indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey. + 5. DP criteria: The DP criteria indicates on which criteria the gsmSSF shall access the gsmSCF. DP criteria is associated to each TDP. +- CAMEL capability handling. It gives the CAMEL phase associated to the O-CSI (CAMEL phase1, or phase2, phase3, or phase4). + +### 2.14.3.2 VMSC Terminating CAMEL Subscription Information (VT-CSI) + +This data defines the contents of the visited terminating CAMEL subscription information used by the VMSC to interwork with the gsmSCF for an MT call. It consists of: + +- A TDP list. The TDP list is a list of TDP descriptions. Each TDP description contains the following elements: + 1. DP Value. The DP value identifies the DP in the MT State Model where service triggering may take place. For VT-CSI, the allowed DP value are *DP Terminating Attempt Authorised*, *DP T\_Busy*, *DP T\_No\_Answer*. + 2. A gsmSCF address. It is the gsmSCF address (E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey. + 3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each TDP. + 4. A default Call Handling. The default call handling indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey. + 5. DP criteria: The DP criteria indicates on which criteria the gsmSSF shall access the gsmSCF. +- CAMEL capability handling. It gives the CAMEL phase associated to the VT-CSI. It is set to CAMEL phase3 or phase4. + +### 2.14.3.3 Supplementary Service invocation notification(SS-CSI) + +This data is used to notify the gsmSCF about Supplementary Service invocation. It consists of : + +- a notification criterion, which may be ECT, CD or MPTY +- a gsmSCFaddress. It is the gsmSCF address (E.164 number) where the notification of the Supplementary service invocation is treated for this subscriber. + +### 2.14.3.4 Mobility Management event notification (M-CSI) + +This data indicates which Mobility Management events shall be reported to the gsmSCF. It consists of: + +- gsmSCF address : This is the address of the gsmSCF where the Mobility Management event notification shall be sent to. The gsmSCF address must be in E.164 format. +- ServiceKey: The serviceKey is included in the notification to the gsmSCF and indicates to the gsmSCF which Service Logic shall be applied. +- Mobility Management Triggers. These triggers define which Mobility Managements events shall be reported to the gsmSCF. The mobility managements triggers may contain one or any combination of the following elements: + - Location update in the same VLR service area; + - Location update to another VLR service area; + - IMSI attach; + +- MS initiated IMSI detach (explicit detach); +- Network initiated IMSI detach (implicit detach). + +### 2.14.3.5 Mobile Originating Short Message Service CAMEL Subscription Information (MO-SMS-CSI) + +This data defines the contents of the MO SMS CAMEL subscription information used for the interworking between gsmSCF and gsmSSF, for CAMEL control of circuit switched MO SMS. + +MO-SMS-CSI consists of the following data items: + +- TDP List. The TDP list is a list of SMS TDP descriptions. Each TDP description contains the following elements: + 1. DP Value. The DP value identifies the DP in the MO SMS State Model where service triggering may take place. +For MO-SMS-CSI, the only allowed DP value is *SMS\_Collected\_Info*. + 2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF. + 3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied. + 4. Default SMS handling. The default SMS handling indicates whether the MO SMS submission request shall be rejected or continued in the case of error in the dialogue between the gsmSSF and gsmSCF or between the gprsSSF and gsmSCF; +- CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MO SMS service. +The CAMEL Capability Handling for MO-SMS-CSI shall have the value CAMEL phase 3. + +### 2.14.3.6 Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI) + +This data defines the contents of the mobile terminating short message service CAMEL subscription information. The MT-SMS-CSI CAMEL Subscription Information is used for interworking between gsmSCF and gsmSSF, for CAMEL control of circuit switched MT SMS. + +MT-SMS-CSI consists of the following data items: + +- TDP List. The TDP list is a list of MT SMS TDP descriptions. Each TDP description contains the following elements: + 1. DP Value. The DP value identifies the DP in the MT SMS State Model where service triggering may take place. +For MT-SMS-CSI, the only allowed DP value is SMS-Delivery-Request + 2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MT SMS CAMEL Service associated with this TDP, is located for this subscriber. + 3. Service Key. The service key identifies to the gsmSCF the service logic that shall be applied. + 4. Default SMS handling. The default SMS handling indicates whether the MT SMS delivery request shall be rejected or continued in the case of error in the dialogue between the gsmSSF and gsmSCF or between the gprsSSF and gsmSCF + 5. DP criterion. The DP criterion indicates on which criterion the gsmSSF shall access the gsmSCF. A DP criterion is associated with each TDP. For MT-SMS the DP criterion is the TDPU type. The criterion may be absent. + +| TDP | Triggering Criterion | ServiceKey | gsmSCF address | Default SMS Handling | +|-------------------------|-----------------------------|-------------------|--------------------------|-----------------------------| +| DP SMS-Delivery Request | TDPU type | One serviceKey | One E.164 gsmSCF address | One Default SMS handling | + +- CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MT SMS service. The CAMEL Capability Handling for MT-SMS-CSI shall have the value CAMEL phase 4. + +### 2.14.3.7 Dialled service CAMEL Subscription Information (D-CSI) + +This data defines the contents of the dialled service CAMEL subscription information used to interwork with the gsmSCF for MO and MF call. It is applicable at TDP Analysed Info. It consists of: + +- DP Criteria list, this consists of 1 to 10 entries containing : DP Criterion: It indicates when the gsmSSF shall request gsmSCF for instructions. + 1. A gsmSCF address. It is the gsmSCF address (E.164 number) where this Subscribed Dialled CAMEL service is treated for the subscriber. A gsmSCF address is associated to each DP Criterion. + 2. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each DP Criterion. + 3. A default Call Handling. It indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. A default Call Handling is associated to each DP Criterion. +- CAMEL capability handling. It indicates the CAMEL phase associated to the D-CSI (CAMEL phase3 or CAMEL phase4 shall be indicated). + +### 2.14.3.8 Translation Information flag (TIF-CSI) + +This flag is used to indicate that the VLR shall not attempt to perform any actions on the deflected to number (DTN). + +## 2.14.4 Data stored in SGSN + +### 2.14.4.1 Mobile Originating Short Message Service CAMEL Subscription Information (MO-SMS-CSI) + +This data defines the contents of the MO SMS CAMEL subscription information. The MO-SMS-CSI in SGSN is used for the Interworking between SGSN and gsmSCF, for CAMEL control of packet switched MO SMS. + +MO-SMS-CSI consists of the following data items: + +- TDP List. The TDP list is a list of SMS TDP descriptions. Each TDP description contains the following elements: + 1. DP Value. The DP value identifies the DP in the MO SMS State Model where service triggering may take place. +For MO-SMS-CSI, the only allowed DP value is *SMS\_Collected\_Info*. + 2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MO SMS CAMEL Service associated with this TDP, is located for this subscriber. + 3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied. + 4. Default SMS handling. The default SMS handling indicates whether the MO SMS submission request shall be rejected or continued in the case of error in the dialogue between the gprsSSF and gsmSCF. +- CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MO SMS service. +The CAMEL Capability Handling for MO-SMS-CSI in SGSN shall have the value CAMEL phase 3. + +#### 2.14.4.2 Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI) + +This data defines the contents of the mobile terminating short message service CAMEL subscription information. The MT-SMS-CSI CAMEL Subscription Information is used for the Interworking between gsmSCF and gprsSSF, for CAMEL control of packet switched MT SMS. + +MT-SMS-CSI consists of the following data items: + +- TDP List. The TDP list is a list of MT SMS TDP descriptions. Each TDP description contains the following elements: + 1. DP Value. The DP value identifies the DP in the MT SMS State Model where service triggering may take place. +For MT-SMS-CSI, the only allowed DP value is *SMS-Delivery-Request* + 2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the MT SMS CAMEL Service associated with this TDP, is located for this subscriber. + 3. ServiceKey. The serviceKey identifies to the gsmSCF the service logic that shall be applied. + 4. Default SMS handling. The default SMS handling indicates whether the MT SMS delivery request shall be rejected or continued in the case of error in the dialogue between the gprsSSF and gsmSCF. + 5. DP criterion. The DP criterion indicates on which criterion the gsmSSF shall access the gsmSCF. A DP criterion is associated with each TDP. For MT-SMS the DP criterion is the TDPU type. The criterion may be absent. + +| TDP | Triggering Criterion | ServiceKey | gsmSCF address | Default SMS Handling | +|-------------------------|-----------------------------|-------------------|--------------------------|-----------------------------| +| DP SMS-Delivery Request | TDPU type | One serviceKey | One E.164 gsmSCF address | One Default SMS handling | + +- CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the MT SMS service. The CAMEL Capability Handling for MT-SMS-CSI shall have the value CAMEL phase 4. + +### 2.14.4.3 GPRS CAMEL Subscription Information (GPRS-CSI) + +This data defines the contents of the GPRS CAMEL subscription information. The GPRS CAMEL Subscription Information is used for the interworking between gsmSCF and gprsSSF, for CAMEL control of packet switch call. + +The GPRS-CSI consists of the following data items: + +- TDP List. The TDP list is a list of GPRS TDP descriptions. Each TDP description contains the following elements: + 1. DP Value. The DP value identifies the DP in the GPRS State Model where service triggering may take place. + 2. gsmSCF Address. The gsmSCF address is the address (E.164 number) of the gsmSCF where the GPRS CAMEL Service associated with this TDP, is located for this subscriber. + 3. Service Key. The service key identifies to the gsmSCF the service logic that shall be applied. + 4. Default GPRS handling. The default GPRS handling indicates whether the GPRS submission request shall be rejected or continued in the case of error in the dialogue between the gprsSSF and gsmSCF. +- CAMEL Capability Handling. CAMEL Capability Handling indicates the CAMEL Phase that is required for the GPRS service. The CAMEL Capability Handling for GPRS-CSI in SGSN shall have the value CAMEL phase 3. + +### 2.14.4.4 Mobility Management for GPRS event notification (MG-CSI) + +This data indicates which Mobility Management for GPRS events shall be reported to the gsmSCF. It consists of: + +- gsmSCF address : This is the address of the gsmSCF where the Mobility Management for GPRS event notification shall be sent to. The gsmSCF address must be in E.164 format. +- Service Key: The service key is included in the notification to the gsmSCF and indicates to the gsmSCF which Service Logic shall be applied. +- Mobility Management Triggers. These triggers define which Mobility Management events shall be reported to the gsmSCF. The mobility management triggers may contain one or any combination of the following elements: + - Routeing area update of MS to a different SGSN service area; + - Routeing area update of MS within the same SGSN service area; + - GPRS attach (e.g. MS switched on, successful routeing area update after network initiated detach); + - MS-initiated GPRS detach (e.g. MS switched off); + - Network-initiated transfer to the "not reachable for paging" state (the network has not received a periodic routeing area update from the MS and assumes that the MS is unreachable). + +## 2.15 Data related to IST + +### 2.15.1 IST Alert Timer + +The IST Alert Timer indicates the timer value that the VMSC and the GMSC shall use to inform the HLR about each of the call activities that an IST non-CAMEL subscriber performs. + +This parameter is only sent to the VLRs which support the non-CAMEL IST functionality. + +## 2.16 Data related to Location Services + +### 2.16.1 Subscriber Data stored in HLR + +#### 2.16.1.1 Privacy Exception List + +This data contains the privacy classes for any target MS that identify the LCS clients permitted to locate the MS. For a detailed definition of this data, refer to 3GPP TS 23.271 [56]. + +#### 2.16.1.2 GMLC Numbers + +This data contains the GMLC addresses for an MS subscriber. These addresses may be used to verify that a location request from specific LCS clients is authorized for the target MS. + +#### 2.16.1.3 MO-LR List + +This data contains the classes of MO-LR that are permitted for the MS subscriber. For a detailed definition of this data, refer to 3GPP TS 23.271 [56]. + +#### 2.16.1.4 Service Types + +This data contains the privacy settings for any target MS that identify the permitted service types for LCS clients requesting positioning of the MS. For a detailed definition of this data, refer to 3GPP TS 23.271 [56]. + +### 2.16.2 Data stored in GMLC + +The GMLC stores data related to LCS clients. Refer to 3GPP TS 23.271 [56] for a detailed description. + +### 2.16.3 Data stored in SMLC (GSM only) + +The SMLC stores data related to associated Type A and Type B LMUs from which location measurements may be received. Refer to GSM 23.271 [56] for a detailed description. + +### 2.16.4 Data stored in LMU (GSM only) + +The LMU stores data related to its LCS measurement and O&M capabilities and may store data related to LCS measurements and O&M reports that it is required to provide to its controlling SMLC. The nature and content of this data is not defined in GSM. + +### 2.16.5 Data stored in the MSC (GSM only) + +In order to support routing of connectionless LCS messages to an SMLC or a Type B LMU, the MSC may store permanent routing data for an SMLC or a Type B LMU in association with a specific location area identifier or location area identifier plus cell identifier. + +### 2.16.6 Data stored in the BSC (GSM only) + +In order to support routing of connectionless LCS messages to an SMLC or a Type B LMU, the BSC may store permanent routing data for an SMLC or a Type B LMU in association with a specific location area identifier or location area identifier plus cell identifier. + +## 2.16.7 Subscriber Data stored in HSS + +### 2.16.7.1 List of Broadcast Location Assistance Data Types + +This data contains information used to determine which ciphering key data should be provided to the UE if requested by the UE, when location assistance data is broadcast in E-UTRAN using ciphering. For a detailed definition of this data, refer to 3GPP TS 23.271 [56]. + +## 2.17 Data related to Super-Charger + +### 2.17.1 Age Indicator + +This data indicates the age of the subscription data provided by the HLR, e.g. the date and time at which the subscriber data was last modified in the HLR. + +## 2.18 Data related to bearer service priority + +### 2.18.1 CS Allocation/Retention priority + +The Circuit Switched ( CS ) Allocation/Retention priority corresponds to the allocation/retention priority which is defined in 3GPP TS 23.107 [93]. It specifies the relative importance compared to other UMTS bearers for allocation and retention of the UMTS bearer in the CS domain. + +The parameter is permanent subscriber data and is conditionally stored in the HLR and VLR. + +## 2.19 Data related to charging + +### 2.19.1 Subscribed Charging Characteristics + +Subscribed Charging Characteristics are specified in 3GPP TS 32.251[84], for example whether the subscriber is a normal, prepaid, flat rate and/or hot billing subscriber. + +Subscribed Charging Characteristics is permanent subscriber data and conditionally stored in HSS/HLR, SGSN, MME and ePDG (for GTP-based S2b only) (see 3GPP TS 23.060 [21], 3GPP TS 23.401 [74] and 3GPP TS 29.273[78]). + +## 2.20 Data related to IMS Centralized Service + +### 2.20.1 ICS Indicator + +The ICS Indicator specifies whether or not the subscriber is an ICS user (see 3GPP TS 23.292 [71]). + +The ICS Indicator is permanent subscriber data and is conditionally stored in the HSS, MME, VLR and SGSN. + +NOTE: The value of ICS Indicator is unique for a given subscriber, for both CS and PS, so its value is the same when sent by the HSS/HLR to the MME/SGSN/VLR over the different interfaces. + +## 2.21 Data related to SRVCC + +### 2.21.1 STN-SR + +#### 2.21.1.1 General + +The STN-SR identifies the Session Transfer Number for SRVCC or 5G-SRVCC (see 3GPP TS 23.003 [5]). + +The STN-SR is temporary data and is conditionally stored in the UDM, HSS, AMF, MME and SGSN (see 3GPP TS 23.216 [80]). + +### 2.21.1.2 STN-SR in EPS or GPRS + +The existence or absence of a STN-SR data in the HSS indicates that the user is SRVCC subscribed or not SRVCC subscribed. This information on SRVCC subscription is independent of the STN-SR value. The creation or deletion of the STN-SR data in the HSS is ensured by provisioning. + +NOTE: Backward compatibility cases (e.g. Pre-Release 10 AS) can still require provisioning of the STN-SR. + +### 2.21.1.3 STN-SR in 5GS + +The existence or absence of a STN-SR data in the UDM indicates that the user is 5G-SRVCC subscribed or not 5G-SRVCC subscribed. This information on SRVCC subscription is independent of the STN-SR value. The creation or deletion of the STN-SR data in the UDM is ensured by provisioning. + +## 2.21.2 UE SRVCC Capability + +### 2.21.2.1 General + +This information element indicates the SRVCC capability of the UE and is described in 3GPP TS 23.237 [87]. + +### 2.21.2.2 UE SRVCC Capability in EPS + +The UE SRVCC Capability is temporary data conditionally stored in the HSS, MME and SGSN. + +### 2.21.2.3 UE SRVCC Capability in 5GS + +The UE 5G SRVCC Capability is temporary data conditionally stored in the UDM and AMF. + +## 2.21.3 Subscribed vSRVCC + +The Subscribed vSRVCC is permanent data and is conditionally stored in the HSS and MME (see 3GPP TS 23.216 [80]). The Subscribed vSRVCC indicates that the user is subscribed to the Single Radio Video Call Continuity (vSRVCC) or not. + +## 2.21.4 CS to PS SRVCC Allowed + +The CS to PS SRVCC Allowed indicator is permanent data and is conditionally stored in the HSS and VLR (see 3GPP TS 23.216 [80]). The CS to PS SRVCC Allowed indicator indicates per PLMN whether the user is allowed to have CS to PS Single Radio Voice Call Continuity or not. + +## 2.22 Data related to MBMS + +### 2.22.1 MBMS GW F-TEID for Sm (Control Plane) + +The MBMS GW F-TEID for Sm (Control Plane) is defined in 3GPP TS 29.274 [75]. MBMS GW F-TEID for Sm (control plane) is temporary data conditionally stored in MBMS GW and MME. + +### 2.22.2 MBMS GW F-TEID for Sn (Control Plane) + +The MBMS GW F-TEID for Sn (Control Plane) is defined in 3GPP TS 29.274 [75]. MBMS GW F-TEID for Sn (control plane) is temporary data conditionally stored in MBMS GW and SGSN. + +### 2.22.3 Temporary Mobile Group Identity + +Temporary Mobile Group Identity (TMGI) (see 3GPP TS 23.246 [85]) is permanent data stored in MBMS GW, MME, SGSN and BM-SC. + +### 2.22.4 MBMS Flow Identifier + +The MBMS Flow Identifier is defined in 3GPP TS 23.246 [85]. MBMS Flow Identifier is permanent data conditionally stored in MBMS GW, MME, SGSN and BM-SC. + +### 2.22.5 MBMS IP Multicast Distribution + +The MBMS IP Multicast Distribution is defined in 3GPP TS 29.274 [75]. MBMS IP Multicast Distribution is temporary data conditionally stored in MBMS GW, MME and SGSN. + +### 2.22.6 MBMS Service Area + +The MBMS Service Area is defined in 3GPP TS 23.246 [85]. MBMS Service Area is permanent data conditionally stored in MBMS GW, MME, SGSN and BM-SC. + +### 2.22.7 MME F-TEID for Sm (Control Plane) + +The MME F-TEID for Sm (Control Plane) is defined in 3GPP TS 29.274 [75]. This is temporary data conditionally stored in MBMS GW and MME. + +### 2.22.8 SGSN F-TEID for Sn (Control Plane) + +The SGSN F-TEID for Sn (Control Plane) is defined in 3GPP TS 29.274 [75]. This is temporary data conditionally stored in MBMS GW and S4-SGSN. + +### 2.22.9 SGSN F-TEID for Sn (User Plane) + +The SGSN F-TEID for Sn (User Plane) is defined in 3GPP TS 23.246 [85]. This is temporary data stored in MBMS GW and S4-SGSN. + +### 2.22.10 MBMS session identifier + +The MBMS Session identifier is defined in 3GPP TS 23.246 [85]. This is permanent data conditionally stored in MBMS GW, MME, SGSN and BM-SC. + +### 2.22.11 MBMS session duration + +MBMS session duration is defined in 3GPP TS 23.246 [85]. This is permanent data conditionally stored in MBMS GW, MME, SGSN and BM-SC. + +### 2.22.12 QoS parameters + +QoS parameters is defined in 3GPP TS 23.246 [85]. QoS is permanent data conditionally stored in MBMS GW, MME, SGSN and BM-SC. + +### 2.22.13 MBMS Time to Data Transfer + +The MBMS Time to Data Transfer is defined in 3GPP TS 23.246 [85]. This is permanent data conditionally stored in MBMS GW, MME, SGSN and BM-SC. + +## 2.22.14 MBMS Data Transfer Start + +The MBMS Data Transfer Start is defined in 3GPP TS 23.246 [85]. This is permanent data conditionally stored in MBMS GW, MME and BM-SC. + +## 2.22.15 List of downstream nodes + +The List of downstream nodes is defined in 3GPP TS 23.246 [85]. This is temporary data stored in MBMS GW, MME, SGSN and BM-SC. + +## 2.22.16 MBMS Session Re-establishment Indication + +The MBMS Session Re-establishment Indication is defined in 3GPP TS 23.007 [6]. This is temporary data conditionally stored in MME, SGSN, MBMS GW and BM-SC. + +## 2.22.17 GCS AS Address + +The GCS AS Address is defined in 3GPP TS 23.468 [95]. It is used to address the AS over the MB2-C reference point. This is temporary data stored in BM-SC. + +## 2.22.18 MB2-U Port Number + +The MB2-U Port Number is defined in 3GPP TS 23.468 [95]. It is used by the BM-SC to receive data related to one MBMS bearer from a GCS AS over the MB2-U reference point. This is temporary data stored in BM-SC. + +## 2.22.19 MBMS Start Time + +The MBMS Start Time is defined in 3GPP TS 23.468 [95]. This is temporary data stored in BM-SC. + +## 2.22.20 TMGI Expiration Time + +The TMGI Expiration Time is defined in 3GPP TS 23.468 [95]. This is temporary data stored in BM-SC. + +## 2.22.21 MBMS Alternative IP Multicast Distribution + +The MBMS Alternative IP Multicast Distribution is defined in 3GPP TS 29.274 [75]. The MBMS Alternative IP Multicast Distribution is temporary data conditionally stored in MBMS GW and MME. + +## 2.22.22 MBMS Cell List + +The MBMS Cell List is defined in 3GPP TS 23.246 [85]. The MBMS Cell List is permanent data conditionally stored in the BM-SC, MBMS GW and MME. + +# 2.23 Data related to Cellular IoT Control Plane Optimizations + +## 2.23.1 Robust Header Compression Context + +The Robust Header Compression Configuration and Context contains the ROHC configuration and context used between the UE and the MME for the small data transferred over control plane. It is defined in IETF RFC 4995 [104]. The contents of the ROHC configuration and the ROHC context are specified in 3GPP TS 24.301 [105]. It is a temporary data conditionally stored in the MME. + +### 2.23.2 Void + +### 2.23.3 MME F-TEID for S11 (User Plane) + +F-TEID for S11 is defined in 3GPP TS 29.274 [75]. + +MME F-TEID for S11 is temporary data conditionally stored in MME and S-GW. + +### 2.23.4 S-GW F-TEID for S11(User Plane) + +F-TEID for S11 is defined in 3GPP TS 29.274 [75]. + +S-GW F-TEID for S11 is temporary data conditionally stored in MME and S-GW. + +### 2.23.5 Serving-PLMN-Rate-Control + +The Serving-PLMN-Rate-Control contains the rate control information requested for CIoT in the serving PLMN. It is defined in 3GPP TS 23.682 [102] and 3GPP TS 29.128 [106]. It is permanent data conditionally stored in the MME, SGW, PGW and SCEF. + +### 2.23.6 APN-Rate-Control + +The APN-Rate-Control contains the rate control information per APN allowed for CIoT from the home operator. It is defined in 3GPP TS 23.682 [102] and 3GPP TS 29.128 [106]. It is permanent data conditionally stored in the SCEF and PGW. + +### 2.23.7 Not Reachable for NIDD Flag + +The Not Reachable for NIDD Flag is defined in 3GPP TS 29.128 [106]. It indicates that Non-IP Data has been attempted to be delivered by one or more SCEF(s) to a UE that is temporarily not reachable due to a power saving function (e.g. extended idle mode DRX or UE Power Saving Mode) and that the corresponding SCEF(s) need to be notified when the UE is reachable or about to become reachable. + +The Not Reachable for NIDD Flag (together with the list of SCEF(s)) is temporary data conditionally stored in the MME. + +### 2.23.8 NIDD Authorization + +The NIDD Authorization contains whether the UE is authorized for MT/MO NIDD for a given APN, and the time period when this authorization is valid. It is permanent data conditionally stored in the HSS and SCEF. + +## 2.24 Data related to ERP + +### 2.24.1 General + +Following clauses describe the data that are defined on a per user basis and are related to EAP-Reauthentication Protocol (ERP). + +### 2.24.2 ERP-Authorization + +ERP-Authorization is defined in 3GPP TS 29.273 [78]. + +ERP-Authorization is used to indicate if a user is authorized to use ERP. + +ERP-Authorization is permanent data conditionally stored in the HSS and the 3GPP AAA Server. + +### 2.24.3 ERP Keying Material + +ERP Keying Material is composed of rMSK and eventually rMSK Lifetime. + +rMSK and rMSK Lifetime are defined in IETF RFC 6696 [110]. + +ERP Keying Material is temporary data conditionally stored in the 3GPP AAA Server or the 3GPP AAA Proxy. + +### 2.24.4 ERP Realm + +ERP-Realm is defined in 3GPP TS 29.273 [78]. + +ERP-Realm is used to identify the realm in which is located the ER server that will serve the user. + +ERP-Realm is permanent data conditionally stored in the 3GPP AAA Server or the 3GPP AAA Proxy. + +## 2.25 Data related to the support of 5GS + +### 2.25.1 SUPI + +The Subscription Permanent Identifier (SUPI) is defined in clause 2.2A of 3GPP TS 23.003 [5]. + +SUPI is permanent data conditionally stored in the UDM, AMF, SMF, SMSF and NEF. + +### 2.25.2 GPSI + +The Generic Public Subscription Identifier (GPSI) shall contain either an External Id (see clause 19.7.2 of 3GPP TS 23.003 [5]) or an MSISDN (see clause 3.3 of 3GPP TS 23.003 [5]). Multiple identifiers may be assigned to a user. + +GPSI is permanent data conditionally stored in the UDM, AMF, SMF and NEF. + +### 2.25.3 Internal Group ID-list + +Internal Group ID-list is a list of the subscribed internal group(s) that the UE belongs to. + +Internal Group ID is permanent data conditionally stored in the UDM, AMF and SMF. + +### 2.25.4 Subscribed NSSAI + +The Subscribed NSSAI (Network Slice Selection Assistance Information) represents the set of S-NSSAI(s) for a SUPI. + +The NSSAI is permanent data conditionally stored in UDM, AMF and SMF. + +### 2.25.5 Default S-NSSAI + +The default S-NSSAI (Network Slice Selection Assistance Information) represents the default S-Nssai for a SUPI. + +The default S-NSSAI is permanent data conditionally stored in UDM and AMF. + +### 2.25.6 5G QoS Parameters + +5G QoS Parameters (see 3GPP TS 23.501 [112]) are permanent data conditionally stored in UDM and SMF. + +## 2.25.7 Forbidden area + +Forbidden area defines areas in which the subscriber is not permitted to initiate any communication with the network (see 3GPP TS 23.501 [112] and 3GPP TS 23.316 [120]). + +Forbidden area is permanent data conditionally stored in UDM and AMF. + +## 2.25.8 Service Area Restriction + +Service Area Restriction indicates either Allowed areas in which the UE is permitted to initiate communication with the network, or Non-allowed areas in which the UE and the network are not allowed to initiate Service Request or SM signalling to obtain user services. (see 3GPP TS 23.501 [112]) and 3GPP TS 23.316 [120]). + +Service Area Restriction is permanent data conditionally stored in UDM and AMF. + +## 2.25.9 RFSP Index + +RAT/Frequency Selection Priority Index (RFSP Index), an index to a specific RRM configuration as defined in 3GPP TS 23.501 [112]. + +RFSP Index is permanent data and is conditionally stored in the UDM and AMF. + +## 2.25.10 Priority Service + +Priority indicates that the UE is subscribed to the MPS or MCX in the 5GS domain, as defined in 3GPP TS 23.501 [112] and 3GPP TS 23.379 [115]. + +Priority service is permanent data and is conditionally stored in the UDM and AMF. + +## 2.25.11 DNN Info + +Data Network Name Information (DNN Info) contains the DNN and optionally the default DNN indicator and LBO roaming allowed for the DNN see 3GPP TS 29.503 [114]. + +DNN Info is permanent data and is conditionally stored in the UDM and SMF. + +## 2.25.12 DNN Configuration + +Data Network Name Configuration (DNN Configuration) contains the DNN, pduSessionTypes, SSC modes, 5G QoS parameters, sessionAMBR, 3gppChargingCharacteristics, static IP Address and acsInfo see 3GPP TS 29.503 [114]. + +DNN Configuration is permanent data and is conditionally stored in the UDM and SMF. + +## 2.25.13 Steering of Roaming Information + +Steering of roaming information (see 3GPP TS 29.503 [114]) contains e.g. the preferred PLMN/AccessTechnologies. + +Steering of roaming information is temporary data and is conditionally stored in the UDM, AMF and AUSF. + +## 2.25.14 SMS supported Data + +SMS supported Data (see 3GPP TS 29.503 [114]) contains the supported SMS service delivery options of the UE. + +SMS supported Data is temporary data and is conditionally stored in the UDM, AMF and SMSF. + +## 2.25.15 SMSF Registrations + +SMSF Registrations (see 3GPP TS 29.503 [114]) contains the SMSF address registered for SMS service. + +SMSF Registration is temporary data and is conditionally stored in the UDM, AMF and SMSF. + +## 2.25.16 SMS subscribed + +SMS subscribed (see 3GPP TS 29.503 [114]) indicates if the subscriber has subscription for: + +- MT SMS service +- MO SMS service. + +SMS subscribed is permanent data and is mandatory stored in the UDM and SMSF. + +## 2.25.17 SMS barring + +SMS barring indicates if the subscriber has barrings for: + +- Barring of all incoming calls for MT-SMS +- Barring of incoming calls for MT-SMS when roaming outside the Home Public Land Mobile Network (PLMN) country +- Barring of all outgoing calls for MO-SMS +- Barring of outgoing calls for MO-SMS when roaming outside the Home Public Land Mobile Network (PLMN) country. + +SMS barring is permanent data and is conditionally stored in the UDM and SMSF. + +## 2.25.18 SMS Roaming + +The SMS Roaming (see 3GPP TS 29.503 [114]) if the subscriber is restriction for MT and MO SMS services when roaming. + +The SMS Roaming is permanent data and is conditionally stored in the UDM, AMF and SMSF. + +## 2.25.19 Core Network Type Restriction + +Core Network Type Restriction defines the types of Core Networks that are disallowed for a UE. + +Core Network Type Restriction is permanent data and is conditionally stored in the UDM and AMF. + +## 2.25.20 LADN Information + +LADN (Local Area Data Network) information (i.e. LADN service area information and LADN DNN) list of DNNs with LADN indication. + +LADN Information is permanent data and is conditionally stored in the UDM and AMF. + +## 2.25.21 Subscribed Periodic Registration Timer + +Subscribed periodic registration timer (see 3GPP TS 23.502 [113]) is permanent data conditionally stored in UDM and AMF. + +## 2.25.22 PEI + +The PEI (see 3GPP TS 23.502 [113] and 3GPP TS 23.316 [120]) is temporary data conditionally stored in UDM, AMF and SMF. + +## 2.25.23 5G GUTI + +The 5G GUTI (see 3GPP TS 23.003 [5]) is temporary data conditionally stored in AMF. + +## 2.25.24 PLMN Identifier + +The PLMN Identifier identifies the VPLMN in which the subscriber is serving or allowed to serve. The PLMN identifier is permanent subscriber data stored conditionally in the UDM, AMF, SMF and SMSF. + +## 2.25.25 PDU Session + +The PDU session (see 3GPP TS 29.503 [114]) is the association between the UE and a Data Network that provides a PDU connectivity service. + +The PDU session is temporary data conditionally stored in the UDM, AMF and SMF. + +## 2.25.26 Trace Data + +The Trace Data (see 3GPP TS 32.422 [64]) is the association between the UE and a Data Network that provides a PDU connectivity service. + +The Trace Data is permanent data conditionally stored in the UDM, AMF and SMF. + +## 2.25.27 Mobile Initiated Connection Only (MICO) mode + +The Mobile Initiated Connection Only (MICO) mode (see 3GPP TS 23.501 [112]) provides the information if MICO mode is allowed. + +The Mobile Initiated Connection Only (MICO) mode is permanent data conditionally stored in the UDM and AMF. + +## 2.25.28 UE purged in AMF flag + +UE purged in AMF flag is set in the UDM per IMSI record in order to indicate that the subscriber data for the UE concerned have been purged in the AMF. The parameter shall take the following values: + +- UE purged in AMF; +- UE not purged in AMF. + +The default value is "UE not purged in AMF". The parameter is temporary subscriber data, stored in the UDM. + +## 2.25.29 GUAMI + +The GUAMI (Globally Unique AMF Identifier) (see 3GPP TS 23.501 [112]) of the serving AMF. + +The GUAMI is temporary data conditionally stored in the UDM, SMF and AMF. + +## 2.25.30 RAND, AUTN, XRES, CK', IK' + +Random Challenge (RAND), Authentication Token (AUTN), Expected Response (XRES), Cipher Key prime (CK') and (IK') form a quintuplet vector for user authentication based on EAP-AKA' as defined in clause 6.1.3.1 of 3GPP TS 33.501 [116]. + +This quintuplet is provided by the UDM to the AUSF. + +## 2.25.31 RAND, AUTN, XRES\* + +Random Challenge (RAND), Authentication Token (AUTN) and Expected Response prime (XRES\*) form a triplet for user authentication based on 5G AKA as defined in clause 6.1.3.2.0 of 3GPP TS 33.501 [116]. + +This triplet is provided by the UDM to the AUSF. The Expected Response prime (XRES\*) is used in particular during the confirmation phase by the AUSF. + +## 2.25.32 RAND, AUTN, HXRES\* + +Random Challenge (RAND), Authentication Token (AUTN) and H-Expected Response prime (HXRES\*) form a triplet for user authentication based on 5G AKA as defined in clause 6.1.3.2.0 of 3GPP TS 33.501 [116]. + +This triplet is provided by the AUSF to the AMF. + +## 2.25.33 Kausf + +The Kausf is defined in 3GPP TS 33.501 [116]. It is a key either provided by the UDM if 5G-AKA is selected as authentication method or derived at the AUSF if EAP-AKA' is selected. + +NOTE: For 5G-AKA, the Kausf is provided along with RAND, AUTN and XRES\*. + +The Kausf is temporary data conditionally stored at the AUSF. + +## 2.25.34 Kseaf + +The Kseaf is defined in 3GPP TS 33.501 [116]. It is a key provided by the AUSF to the AMF acting as an SEAF. + +NOTE: For 5G-AKA, the Kseaf is provided if confirmation from AUSF is successful. + +## 2.25.35 AuthenticationMethod + +The AuthenticationMethod is described in 3GPP TS 33.501 [116]. + +The AuthenticationMethod is permanent data mandatory stored at the UDM. + +## 2.25.36 PermanentKey + +The PermanentKey is described in 3GPP TS 33.501 [116]. The permanent key shall be stored encrypted. + +The PermanentKey is permanent data conditionally stored at the UDM. + +## 2.25.37 SequenceNumber + +The SequenceNumber is described in 3GPP TS 33.102 [52]. + +The SequenceNumber is temporary data conditionally stored at the UDM. + +## 2.25.38 AuthenticationManagementField + +The AuthenticationManagementField is described in 3GPP TS 33.501 [116]. + +The AuthenticationManagementField is permanent data conditionally stored at the UDM. + +## 2.25.39 VectorAlgorithm + +The VectorAlgorithm the algorithm used for the generation of authentication vectors see 3GPP TS 29.505 [119]. + +The VectorAlgorithm is permanent data conditionally stored at the UDM. + +## 2.25.40 Milenage + +The Milenage described in 3GPP TS 35.206 [117]. + +The Milenage is permanent data conditionaly stored at the UDM. + +## 2.25.41 Tuak + +The Tuak described in 3GPP TS 35.231 [118]. + +The Tuak is permanent data conditionaly stored at the UDM. + +## 2.25.42 Opc + +The Opc described in 3GPP TS 35.205 [117]. + +The Opc is permanent data conditionaly stored at the UDM. + +## 2.25.43 Topc + +The Topc described in 3GPP TS 35.231 [118]. + +The Topc is permanent data conditionaly stored at the UDM. + +## 2.25.44 Authentication Status + +The authentication status of the UE contains authentication result, timestamp, and the serving network name. + +The Authentication Status is temporary data conditionaly stored at the UDM. + +## 2.25.45 SoR-XMAC-IUE + +The SoR-XMAC-IUE of the UE contains the expected SoR-XMAC-IUE as specified in 3GPP TS 33.501 [116]. + +The SoR-XMAC-IUE is temporary data conditionaly stored at the UDM. + +## 2.25.46 Shared Data Ids + +The Shared Data Id is defined in 3GPP TS 29.503 [114]. + +Shared Data Ids are permanent data and are conditionally stored in the UDM, AMF, SMSF and SMF. + +## 2.25.47 Access Restriction Data + +The use of this data is described in 3GPP TS 23.501 [112] clause 5.3.4.1.1. + +The Access Restriction Data is permanent subscriber data and is conditionally stored per PLMN in the UDM and the AMF. + +The parameter takes either of the following values: + +- NR not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR radio access. Valid for Idle and Connected mode; +- NR not allowed as secondary RAT, the subscriber shall not be allowed to access the network using NR radio access as secondary RAT. Valid for Connected mode; + +NOTE: As specified in clause 4.11.1.2.1 of 3GPP TS 23.502 [113], this restriction can also be applied when attached to EPC depending on operator policy, and in this case AMF will send this information to MME during handover from 5GC to EPC in order to allow MME to make appropriate handling, e.g. SGW selection based on access restriction, or whether or not to allocate resources for secondary RAT during inter RAT handover. + +- NR in unlicensed bands not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using NR radio access in unlicensed bands. Valid for Idle and Connected mode; + +- NR in unlicensed bands not allowed as secondary RAT, the subscriber shall not be allowed to access the network using NR radio access in unlicensed bands as secondary RAT. Valid for Connected mode; +- E-UTRA not allowed as primary RAT, the subscriber shall not be allowed to access the network in TAs using E-UTRA radio access. Valid for Idle and Connected mode; +- E-UTRA not allowed as secondary RAT, the subscriber shall not be allowed to access the network using E-UTRA radio access as secondary RAT. Valid for Connected mode; +- E-UTRA in unlicensed bands not allowed as secondary RAT, the subscriber shall not be allowed to access the network using E-UTRA radio access in unlicensed bands as secondary RAT. Valid for Connected mode; +- NB-IoT not allowed, the subscriber shall not be allowed to access the network in TAs using NB-IoT radio access. Valid for Idle and Connected mode; +- LTE-M not allowed, the subscriber shall not be allowed to access the network in TAs using LTE-M radio access. Valid for Idle and Connected mode. + +Only the access restriction for WB-E-UTRA and NB-IoT may include a different value per PLMN. + +The use of this parameter for TA update procedures is described in 3GPP TS 23.501 [112]. + +## 2.25.48 IAB-Operation Allowed indication + +The IAB-Operation Allowed indication defines if the subscriber is allowed for IAB node operation as specified in 3GPP TS 23.501 [112]. + +The IAB-Operation Allowed indication is permanent subscriber data and is conditionally stored in the UDM and the AMF. + +## 2.25.49 UE radio capability ID + +The UE radio capability ID is defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 23.501 [112]. + +The UE radio capability ID is temporary subscriber data and is conditionally stored in the AMF. + +## 2.25.50 RG Level Wireline Access Characteristics + +RG Level Wireline Access Characteristics (see 3GPP TS 23.316 [120]) are permanent data conditionally stored in UDM and AMF. + +## 2.25.51 RG-TMBR + +RG-TMBR (see 3GPP TS 23.316 [120]) are permanent data conditionally stored in UDM and AMF. + +## 2.25.52 List of 5GS Broadcast Location Assistance Data Types + +This data contains information used to determine which ciphering key data should be provided to the UE if requested by the UE, when location assistance data is broadcast in NG-RAN using ciphering. For a detailed definition of this data, refer to 3GPP TS 23.273 [121]. + +The list of 5GS Broadcast Location Assistance Data Types is permanent subscriber data and is conditionally stored in the UDM and the AMF. + +--- + +# 3 Definition of data for IP Multimedia domain + +This clause describes the IMS data for IMS subscribers and PSI users. + +## 3.1 Data related to subscription, identification and numbering + +### 3.1.1 Private User Identity + +The Private User Identity is applicable to IMS subscribers only. The Private User Identity is in the form of a Network Access Identifier (NAI), which is defined in IETF RFC 4282 [48]. + +If the GAA bootstrapping is based on authentication data from the IM domain, the corresponding Private User Identity from the IM domain (IMPI) is used as it is. If the GAA bootstrapping is based on the authentication data from the CS/PS domain, a Private User Identity is derived from user's IMSI according 3GPP TS 23.003 [5] is used. + +The Private User Identity is permanent subscriber data and is stored in HSS and in S-CSCF. + +### 3.1.2 Public User Identities + +The Public User Identities of an IMS subscriber contain one or several instances of Public User Identity or Wildcarded Public User Identity, which are defined in 3GPP TS 23.003 [5]. + +The Public User Identities are permanent subscriber data and are stored in HSS, S-CSCF and BSF. + +#### 3.1.2A Private Service Identity + +The Private Service Identity is applicable to a PSI user and is similar to a private user identity in the form of a Network Access Identifier (NAI), which is defined in IETF RFC 4282 [48]. The Private Service Identity is operator defined. + +The Private Service Identity is permanent data and is stored in HSS and S-CSCF. + +#### 3.1.2B Public Service Identity + +The Public Service Identity hosted by an application server may match either to a distinct PSI or a wildcarded PSI that is stored in the HSS. The PSI is defined in 3GPP TS 23.003 [5]. + +The relationship between Wildcarded Public Service Identities and Private Service Identities is one-to-one. + +A Public Service Identity (distinct PSI or Wildcarded PSI) cannot be shared by more than one Private Service Identity. + +The Public Service Identity is permanent data and is stored in HSS and S-CSCF. + +### 3.1.3 Barring indication + +Flag associated to each Public User Identity to indicate that the identity is barred from any IMS communication. A Public User Identity that is barred is allowed to register with the IMS. + +The Barring indication is permanent subscriber data and is stored in the HSS and in the S-CSCF. + +### 3.1.4 List of authorized visited network identifiers + +The list of authorized visited network identifiers is associated with the Public User Identity to indicate which visited network identifiers are allowed for roaming. If the Public User Identity is part of a set of implicitly registered Public User Identities, the list of authorized visited network identifiers shall be the same for the whole set. + +The list of authorized visited network identifiers is permanent subscriber data and is stored in the HSS. This list can be a linear list of visited network identifiers or a compound list of network identifier types e.g. home PLMN or home country; however the exact structure of the list is an implementation option. + +### 3.1.5 Services related to Unregistered State + +The Services related to Unregistered State is a parameter associated to each Public User Identity and Public Service Identity and it indicates whether the identity has services related to unregistered state or not. For a Public Service Identity the parameter shall always be set to value indicating that the identity has services related to unregistered state. + +The Services related to Unregistered State is permanent subscriber data stored in the HSS. + +### 3.1.6 Implicitly Registered Public User Identity Sets + +The Implicitly Registered Public User Identity Set contains one or several instances of Public User Identity of an IMS subscriber, and is defined in 3GPP TS 29.228 [43] following the described concept in 3GPP TS 23.228 [42]. Several Implicitly Registered Public User Identity Sets can be configured for a given user. Each Public User Identity shall be included in no more than one Implicitly Registered Public User Identity Set. + +The Implicitly Registered Public User Identity Sets are permanent subscriber data and are conditionally stored in HSS and in S-CSCF. + +### 3.1.7 Default Public User Identity indicator + +The Default Public User Identity indicator marks the Public User Identity to be used as default Public User Identity in each Implicitly Registered Public User Identity Set, and is defined in 3GPP TS 29.228 [43]. There shall be one Default Public User Identity per Implicitly Registered Public User Identity Set. + +The Default Public User Identity indicator is permanent subscriber data and is conditionally stored in the HSS. + +### 3.1.8 PSI Activation State + +The PSI Activation State is specific for Public Service Identities and is defined in 3GPP TS 29.328 [54]. + +The PSI Activation State indicator for distinct PSIs is temporary subscriber data and is stored in the HSS. The PSI Activation State indicator for wildcarded PSIs is permanent subscriber data and is stored in the HSS. A wildcarded PSI or a distinct PSI that matches a wildcarded PSI shall not be activated/deactivated via the Sh interface. + +### 3.1.9 Display Name + +The Display Name is a string associated with a Public Identity + +The Display Name is permanent subscriber data and is conditionally stored in the HSS and in the S-CSCF. + +### 3.1.10 Alias Public User Identity Sets + +The Alias Public User Identity Set contains two or more Public User Identities of an IMS subscriber, and these Public User Identities in the set are aliases of each other and their treatment is identical. Several Alias Public User Identity Sets can be configured for a given user. Each Public User Identity shall be included in no more than one Alias Public User Identity Set. All the Public User Identities in every Alias Public User Identity Set shall be included in the same Implicitly Registered Public User Identity Set, and shall be linked to the same Service Profile and share the same service data for each and every service, but there can be more than one Alias Public User Identity Set per Implicitly Registered Public User Identity Set and Service Profile. + +The Alias Public User Identity Sets are permanent subscriber data and are conditionally stored in the HSS and in the S-CSCF. + +### 3.1.11 Loose-Route Indication + +The Loose-Route Indication indicates if the loose-route mechanism is required for all the Public User Identities belonging to a Private User Identity. It is defined in 3GPP TS 29.228 [43] following the described concept in 3GPP TS 24.229 [68]. + +The Loose-Route Indication shall have the same value for all the Private Identities of the IMS subscription if at least one Public User Identity is shared by the multiple Private Identities; otherwise, each Private User Identity may have a different Loose-Route Indication value. + +The Loose-Route Indication is permanent subscriber data and is conditionally stored in the HSS and in the S-CSCF. + +### 3.1.12 Service Priority Level + +The Service Priority Level indicates the Priority Level allowed for the Public Identity. It is defined in 3GPP TS 29.228 [43] following the described concept in 3GPP TS 24.229 [68]. + +The Service Priority Level is permanent subscriber data and is conditionally stored in the HSS and the S-CSCF. + +### 3.1.13 Extended Priority + +The Extended Priority provides priority information for the Public Identity. It provides support for more than one subscribed namespaces in an operator's network, as included in priority mechanisms described in 3GPP TS 24.229 [68] and it is defined in 3GPP TS 29.228 [43]. + +The Extended Priority is permanent subscriber data and is conditionally stored in the HSS and the S-CSCF. + +### 3.1.14 Reference Location Information + +The Reference Location Information contains the reference location for the Private User Identity (e.g. line identification in the case of fixed line access). It is defined in 3GPP TS 29.228 [43] following the described concept in 3GPP TS 23.167 [89]. + +The Reference Location Information is permanent subscriber data and is conditionally stored in the HSS and the S-CSCF. + +### 3.1.15 Privileged-Sender Indication + +The Privileged-Sender Indication indicates if the corresponding Private User Identity shall be considered a privileged sender. It is defined in 3GPP TS 29.228 [43] following the described concept in 3GPP TS 24.229 [68]. + +If for an IMS subscription at least one Public User Identity is shared by more than one Private Identity, then all these Private Identities shall have the same value for the Privileged-Sender Indication; otherwise, each Private User Identity may have a different Privileged-Sender Indication value. + +The Privileged-Sender Indication is permanent subscriber data and is conditionally stored in the HSS and in the S-CSCF. + +### 3.1.16 Additional MSISDN (A-MSISDN) + +An Additional MSISDN (A-MSISDN) is an MSISDN optionally assigned in addition to the already assigned MSISDN(s) to a user with PS subscription. For the definition of A-MSISDN see 3GPP TS 23.003 [5]. + +It is a permanent subscriber data stored in the HSS/HLR. It is temporarily stored in the MME, SGSN and AS. + +## 3.2 Data related to registration + +### 3.2.1 Registration Status + +The Registration Status, specified in 3GPP TS 29.228 [43], contains the status of registration of a Public User Identity or a Public Service Identity (i.e. registered, not registered, unregistered). A Public Service Identity shall have only the registration status not registered or unregistered. + +The Registration Status is temporary subscriber data and is stored in HSS. + +### 3.2.2 S-CSCF Name + +For an IMS subscriber, the S-CSCF Name identifies the S-CSCF allocated to the IMS subscriber when the subscriber is registered to IP Multimedia Services. It is used during mobile terminated sessions set-up and re-registrations. + +For a Public Service Identity the S-CSCF Name identifies the S-CSCF allocated to the PSI for basic IMS routing. It is used during terminated call set-up for a PSI user. + +The S-CSCF Name shall be in the form of a SIP URL as defined in IETF RFC 3261 [45] and RFC 2396 [46]. + +For an IMS subscriber and PSI user, the S-CSCF Name is temporary data and is stored in HSS. + +### 3.2.2A AS Name + +For a PSI user the AS Name identifies the application server hosting the Public Service Identity and is used for direct routing of a Public Service Identity. + +The AS Name shall be in the form of a SIP URL as defined in IETF RFC 3261 [45] and RFC 2396 [46]. + +The AS Name is permanent data and is stored in the HSS. + +### 3.2.3 Diameter Client Identity of S-CSCF + +The Diameter Client Identity of the S-CSCF identifies the Diameter client in the S-CSCF when the IMS subscriber is registered to IP Multimedia Services or a PSI user has an assigned S-CSCF. It is used in requests sent by the HSS to the S-CSCF. The format of the Diameter Client Identity is the Diameter Identity defined in IETF RFC 3588 [51]. + +The Diameter Client Identity of the S-CSCF is temporary data and is stored in HSS. + +### 3.2.4 Diameter Server Identity of HSS + +The Diameter Server Identity of HSS identifies the Diameter Server in the HSS when the IMS subscriber is registered to IP Multimedia Services or the identity of HSS holding the IMS data of a PSI user. It is used in requests sent by the S-CSCF to the HSS. The format of the Diameter Server Identity is the Diameter Identity defined in IETF RFC 3588 [51]. + +For an IMS subscriber and PSI user, the Diameter Server Identity of the HSS is temporary data and is stored in S-CSCF. + +### 3.2.5 UE Not Reachable via IP-SM-GW Flag (UNRI) + +The UNRI is temporary subscriber data stored in the HLR/HSS and in the IP-SM-GW (AS). It indicates whether the UE is marked not reachable for short message delivery via the IMS. + +### 3.2.6 UE Not Reachable via IP-SM-GW Reason (UNRR) + +The UNRR is temporary subscriber data stored in the HLR/HSS. It indicates the reason why MT short message delivery failed at the IP-SM-GW. + +### 3.2.7 S-CSCF Restoration Information + +The S-CSCF Restoration Information, specified in 3GPP TS 29.228 [43], contains information for the S-CSCF to restore services for the user, including the list of SIP Proxies in the Path header, the Contact information and the UE's subscription information. + +The S-CSCF Restoration Information is temporary subscriber data and is stored in the HSS and S-CSCF. + +### 3.2.8 Maximum Number Of Allowed Simultaneous Registrations + +The Maximum Number Of Allowed Simultaneous Registrations per public user identity is specified in 3GPP TS 29.228 [43]. + +It is permanent subscriber data and is stored in the HSS and S-CSCF. + +### 3.3 Data related to authentication and ciphering + +The Data related to authentication and ciphering are applicable to IMS subscribers only. + +#### 3.3.1 Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key (IK) and Authentication Token (AUTN) + +For contents of Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key (IK) and Authentication Token (AUTN) see clause 2.3.2. + +A set of quintuplet vectors are calculated in the HSS, and sent from the HSS to the S-CSCF (see 3GPP TS 29.228 [43]). + +These data are temporary subscriber data conditionally stored in the HSS and in the S-CSCF. + +#### 3.3.2 Data related to SIP Digest Authentication + +##### 3.3.2.1 Digest Nonce + +The Digest Nonce is a random (non-predictable) value selected by the S-CSCF (see 3GPP TS 29.228 [43]) and used by the client to calculate the authentication response (see IETF RFC 2617 [69]). + +The Digest Nonce is temporary subscriber data and is stored in the S-CSCF. + +##### 3.3.2.2 Digest HA1 + +Digest HA1 is the value calculated as defined in IETF RFC 2617 [69]. It is calculated by the HSS and used by the S-CSCF to create the Expected Response (see 3.3.2.14). It is also used to create the Response-Auth (see 3.3.2.15) after a successful authentication verification has occurred. + +HA1 is permanent subscriber data and is stored in the HSS and the S-CSCF. + +##### 3.3.2.3 Digest Nextnonce + +Nextnonce is the nonce the server wishes the client to use for a future authentication response (see IETF RFC 2617 [69]). + +Digest Nextnonce is temporary subscriber data and is stored in the S-CSCF. + +##### 3.3.2.4 Void + +##### 3.3.2.5 Authentication Pending Flag + +The Authentication Pending flag, described in 3GPP TS 29.228 [43], indicates that the authentication of a Public User Identity - Private User Identity pair is pending and waiting for confirmation. + +The Authentication Pending Flag is temporary data and is stored in the HSS. + +#### 3.3.1 Data related to NASS Bundled Authentication + +##### 3.3.3.1 Line Identifier List + +Line Identifier List contains a list of fixed broadband access line identifiers associated to the user and used by the S-CSCF to authenticate the user. + +Line Identifier List is permanent subscriber data and is stored in HSS and the S-CSCF. + +## 3.4 Data related S-CSCF selection information + +### 3.4.1 Server Capabilities + +The Server Capabilities contains information to assist the I-CSCF in the selection of a S-CSCF for an IMS subscriber or a PSI user. For definition and handling of the data see 3GPP TS 29.228 [43] and 3GPP TS 29.229 [44]. + +The Server Capabilities information is permanent data and is stored in HSS. + +### 3.4.2 S-CSCF Reassignment Pending Flag + +The S-CSCF Reassignment Pending Flag, described in 3GPP TS 29.228 [43] indicates that the subscription can be reassigned to a new S-CSCF (i.e. the current S-CSCF is not responding). + +The S-CSCF Reassignment Pending Flag is temporary data and is stored in the HSS. + +## 3.5 Data related to Application and service triggers + +For definition and handling of these data see 3GPP TS 23.218 [53]. + +### 3.5.1 Void + +### 3.5.2 Initial Filter Criteria + +A set of Initial Filter Criteria are stored for each user, for each application or service that the user request may invoke. The relevant service points of interest are defined in 3GPP TS 23.218 [53] clause 5.2. + +Each set of filter criteria includes the Application Server Address, AS priority, Default Handling, Subscribed Media, Trigger Points and Optional Service Information. + +For a PSI that is routed according to the basic IMS routing principles, Initial Filter criteria is mandatory in order to route towards the AS hosting the PSI. + +### 3.5.3 Application Server Information + +The HSS may store Application Server specific information for each user. This information may include Service Key, Trigger Points, and Service Scripts etc. (see 3GPP TS 23.218 [53] clause 9.3.1) + +### 3.5.4 Service Indication + +The Service Indication, associated with a public user identity, identifies exactly one set of service related transparent data (see 3GPP TS 29.328 [54]), which is stored in an HSS in an operator network. It is defined in 3GPP TS 29.328 [54]. + +The Service Indication is permanent subscriber data and is stored in the HSS and one or more ASs. + +### 3.5.5 Shared iFC Set Identifier + +Shared iFC Set Identifier identify sets of Initial Filter Criteria that may be shared by more than one IMS subscriber or PSI user. The translation from a Shared iFC Set Identifier to the set of initial Filter Criteria is performed in the S-CSCF based on operator configuration. + +The Shared iFC Set Identifier are permanent data stored in the HSS and in the S-CSCF. + +### 3.5.6 Transparent Data + +The Transparent Data is information stored in the HSS by the AS per Service Indication and Public User Identity or Public Service Identity (Repository Data). It is defined in 3GPP TS 29.328 [54]. If the Public Service Identity matches a Wildcarded Public Service Identity, the transparent data shall be stored per Wildcarded PSI, and not for each specific Public Service Identity matching that Wildcarded PSI. Transparent Data for Wildcarded Public User Identities shall also be stored per Wildcarded Public User Identity, and not for each identity matching that Wildcarded Public User Identity. Transparent data for an Alias Public User Identity Set shall be stored and shared by each and every Public User Identity within the same Public User Identity Set. + +The Transparent Data is temporary subscriber data and is stored in the HSS and one or more ASs. + +### 3.5.7 Application Server Identity List + +The Application Server Identity List is stored in the HSS per Public User Identity or Public Service Identity and per requested user data (data-reference) for a given expiration time. It identifies the application servers which subscribed to notifications of the user data updates and need to be notified when the data subscribed changes. + +Application Server Identity List is temporary data and is stored in the HSS. + +## 3.6 Data related to Core Network Services Authorization + +### 3.6.1 Subscribed Media Profile Identifier + +The Subscribed Media Profile Identifier identifies a set of session description parameters that the IMS subscriber or PSI user is authorized to request. The translation from the Profile Identifier to the set of subscribed media is performed in the S-CSCF based on operator configuration. + +The Subscribed Media Profile Identifier is permanent data stored in the HSS and in the S-CSCF. + +### 3.6.2 List of Subscribed IMS Communication Service Identifiers + +The list of subscribed IMS Communication Service Identifiers is associated with the IMS Public Identity and identifies the list of IMS communication services that the subscriber is authorized to use as specified in 3GPP TS 23.228 [42]. The syntax of the IMS Communication Service Identifier is defined in 3GPP TS 24.229 [68]. The usage of IMS Communication Service Identifier for policing the allowed IMS communication service is performed in the S-CSCF and in the AS based on operator configuration. + +The List of Subscribed IMS Communication Service Identifiers is permanent data stored in the HSS and conditionally in the S-CSCF and AS. + +## 3.7 Data related to Charging + +The following charging function names shall be common to the entire IMS Subscription i.e. the same set of charging function names shall be returned for all the identities inside the same IMS Subscription. + +### 3.7.1 Primary Event Charging Function Name + +The Primary Event Charging Function Name identifies the primary Online Charging Function, which performs on-line charging. The format is specified in 3GPP TS 29.229 [44]. + +The Primary Event Charging Function Name is permanent data stored in the HSS and in the S-CSCF. + +### 3.7.2 Secondary Event Charging Function Name + +The Secondary Event Charging Function Name identifies the secondary Online Charging Function, which performs on-line charging. The format is specified in 3GPP TS 29.229 [44]. + +The Secondary Event Charging Function Name is permanent data stored in the HSS and in the S-CSCF. + +### 3.7.3 Primary Charging Collection Function Name + +The Primary Charging Collection Function Name identifies the primary Charging Data Function, which provides off-line charging support for IMS subscribers and PSIs. The format is specified in 3GPP TS 29.229 [44]. + +The Primary Charging Collection Function Name is permanent data stored in the HSS and in the S-CSCF. + +### 3.7.4 Secondary Charging Collection Function Name + +The Secondary Charging Collection Function Name identifies the secondary Charging Data Function, which provides off-line charging support for IMS subscribers and PSIs. The format is specified in 3GPP TS 29.229 [44]. + +The Secondary Charging Collection Function Name is permanent data stored in the HSS and in the S-CSCF. + +## 3.8 Data related to CAMEL Support of IMS Services + +The Data related to CAMEL Support of IMS Services are applicable to IMS subscribers only. + +### 3.8.1 Originating IP Multimedia CAMEL Subscription Information (O-IM-CSI) + +This data defines the contents of the Originating IP Multimedia CAMEL subscription information used to interwork with the gsmSCF for originating IP multimedia sessions. It consists of: + +- A TDP list. The TDP list is a list of TDP descriptions. Each TDP description contains the following elements: + 1. DP Value. The DP value identifies the DP in the O-IM-BCSM where service triggering may take place. For O-IM-CSI, the allowed DP values are *DP Collected\_info*, *DP Route\_Select\_Failure*. + 2. A gsmSCF address. It is the gsmSCF address (E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey. + 3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each TDP. + 4. A default Call Handling. The default call handling indicates whether the IP Multimedia session shall be released or continued as requested in case of error in the IM-SSF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey. + 5. DP criteria. The DP criteria indicates on which criteria the IM-SSF shall access the gsmSCF. DP criteria is associated to each TDP. + +| TDP | Triggering Criteria (*) | ServiceKey | gsmSCF address | Default Call Handling | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|----------------|--------------------------|---------------------------| +| DP Collected_ Info | No Criterion
Number criteria | One ServiceKey | One E.164 gsmSCF address | One Default call handling | +| DP Route_Select_ Failure | No criterion
Cause value criteria | One ServiceKey | One E.164 gsmSCF address | One Default call handling | +| NOTE: One or more TDP criteria shall be applicable. All applicable triggering criteria must be satisfied before the dialogue is established with the gsmSCF. | | | | | + +- CAMEL capability handling. It gives the CAMEL phase associated to the O-IM-CSI (phase 4). +- The CSI state. The CSI state indicates whether the O-IM-CSI is active or not. The CSI state is not sent to the IM-SSF. +- The notification flag, the notification flag indicates whether changes of the O-IM-CSI shall trigger Notification on Change of Subscriber Data towards the gsmSCF and IM-SSF. The notification flag is not sent to the IM-SSF. + +### 3.8.2 Terminating IP Multimedia CAMEL Subscription Information (VT-IM-CSI) + +This data defines the contents of the terminating IP Multimedia CAMEL subscription information used to interwork with the gsmSCF for terminating IP multimedia sessions. It consists of: + +- A TDP list. The TDP list is a list of TDP descriptions. Each TDP description contains the following elements: + 1. DP Value. The DP value identifies the DP in the T-IM-BCSM where service triggering may take place. For VT-IM-CSI, the allowed DP values are *DP Terminating\_Attempt\_Authorised*, *DP T\_Busy*, *DP T\_No\_Answer*. + 2. A gsmSCF address. It is the gsmSCF address (E.164 number) where the CAMEL service is treated for the subscriber. A gsmSCF address is associated to each serviceKey. + 3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each TDP. + 4. A default Call Handling. The default call handling indicates whether the IP Multimedia session shall be released or continued as requested in case of error in the IM-SFF to gsmSCF dialogue. A default Call Handling is associated to each serviceKey. + 5. DP criteria. The DP criteria indicates on which criteria the IM-SSF shall access the gsmSCF. DP criteria is associated to each TDP. + +| TDP | Triggering Criteria (*) | ServiceKey | gsmSCF address | Default Call Handling | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|-----------------|--------------------------|---------------------------| +| DP Terminating_Attempt_Authorised | No Criterion | One serviceKey | One E.164 gsmSCF address | One Default call handling | +| DP T_Busy | No criterion
Cause value criteria | One serviceKey | One E.164 gsmSCF address | One Default call handling | +| DP T_No_Answer | No criterion
Cause value criteria | One service Key | One E.164 gsmSCF address | One Default call handling | +| NOTE: One or more TDP criteria shall be applicable. All applicable triggering criteria must be satisfied before the dialogue is established with the gsmSCF. | | | | | + +- CAMEL capability handling. It gives the CAMEL phase associated to the VT-IM-CSI (CAMEL phase 4). +- The CSI state indicates whether the VT-IM-CSI is active or not. The CSI state is not sent to the IM-SSF. +- Notification flag. The notification flag indicates whether the change of the VT-IM-CSI shall trigger Notification on Change of Subscriber data towards the gsmSCF and IM-SSF. The notification flag is not sent to the IM-SSF. + +### 3.8.3 Dialled Services IP Multimedia CAMEL Subscription Information (D-IM-CSI) + +This data defines the contents of the dialled service CAMEL subscription information used to interwork with the gsmSCF for originating and forwarded IP Multimedia sessions. It is applicable at TDP Analysed Info. It consists of: + +- DP Criteria list. This consists of 1 to 10 entries. Each entry shall contain the following items: + 1. DP Criterion. It indicates when the IM-SSF shall request gsmSCF for instructions. It is a destination number. + 2. A gsmSCF address. It is the gsmSCF address (E.164 number) where this Subscribed Dialled CAMEL service is treated for the subscriber. A gsmSCF address is associated to each DP Criterion. + 3. A serviceKey. The serviceKey identifies to the gsmSCF the service logic. A serviceKey is associated to each DP Criterion. + 4. A default Call Handling. It indicates whether the IP Multimedia session shall be released or continued as requested in case of error in the IM-SSF to gsmSCF dialogue. A default Call Handling is associated to each DP Criterion. +- CAMEL capability handling. It indicates the CAMEL phase associated to the D-IM-CSI (CAMEL phase 4). +- CSI state: indicates whether the D-IM-CSI is active or not. The CSI state is not sent to the IM-SSF. +- Notification Flag. It indicates whether the change of the D-IM-CSI shall trigger the Notification on Change of Subscriber Data towards the gsmSCF and IM-SSF. The notification flag is not sent to the IM-SSF. + +### 3.8.4 gsmSCF address for IM CSI + +This information element contains the list of gsmSCF address (E.164 address) to which Notification on Change of Subscriber Data is to be sent. + +### 3.8.5 IM-SSF address for IM CSI + +This information element contains the IM-SSF address to which Notification on Change of Subscriber Data is to be sent. The IM-SSF address is entered in the HSS/HLR at UE registration and is deleted when the HSS/HLR initiates or is notified of the UE deregistration. + +## 3.9 Data related to IMS Service Level Trace + +### 3.9.1 IMS Service Level Trace Information + +The IMS Service Level Trace Information is utilised by the S-CSCF and the Application Server to enable service level tracing within the IMS Core Network. The content of the IMS Service Level Trace Information is defined in the management object specified in 3GPP TS 24.323 [111]. + +The IMS Service Level Trace Information is temporary subscriber data and is stored in the HSS, S-CSCF and Application Server. + +## 3.10 Data related to Generic Authentication Architecture + +The Generic Authentication Architecture (GAA) is independent from CS/PS and IM domains, but it requires a subscription in the HSS for every its users at least in one of the domains for generation of authentication vectors. The need for a GAA specific subscription data in the HSS for GAA specific user identities and/or authorization controls is GAA application dependent. At the same time, GAA shall not be considered as a separate domain in the same sense as the notion of a "domain" is considered for CS and PS. + +The Generic Authentication Architecture is defined in 3GPP TS 33.220 [58] and 3GPP TS 29.109 [59]. For data related to GAA, see also the definition of Private User Identity in chapter 3.1.1. + +### 3.10.1 GAA Service Type + +The GAA Service Type is an enumerated integer, which is defined in 3GPP TS 29.109 [58]. + +The GAA Service Type is permanent subscriber data and is stored in the HSS, BSF and NAF. + +### 3.10.2 GAA Service Identifier + +The GAA Service Identifier (GSID) is an integer, which uniquely identifies a GAA Service. For example a set of NAFs belonging to a certain GAA Service Type and owned or managed by a certain operator may provide the same operator specific service and they may use the same GAA Service Identifier to identify their services to BSF. The owner of the user's home HSS may define different GAA Authorization flags and allowed Private User Identities for each GAA Service Identifiers separately. + +The GAA Service Identifier is permanent subscriber data and is stored in the HSS, BSF and NAF. + +### 3.10.3 GBA User Security Settings + +The GBA User Security Settings (GUSS) is identified by a Private User Identity. The GBA User Security Settings contains optional BSF control information (i.e., UICC Security Type and optional Key Lifetime) and a set of User Security Setting (USS). + +The GBA User Security Settings is permanent subscriber data and is stored in the HSS, and the BSF. + +### 3.10.4 User Security Setting + +The User Security Setting (USS) is unique identified by a combination of Private User Identifiers (IMPI) and GAA Service Identifiers (GSID). The User Security Setting contains a list of allowed public identities for the service and possible authorization flags. No duplicates are allowed. + +The User Security Setting is permanent subscriber data and is stored in the HSS, BSF and NAF. + +### 3.10.5 User Public Identity + +The User Public Identity (UID) is a freely defined string that can be used as user's public identity in a GAA application. A list of allowed User Public Identities is stored for each GAA Service Subscription. A User Public Identity may be connected to several GAA Service Subscription. + +The User Public Identity is permanent subscriber data and is stored in the HSS, BSF and NAF. + +### 3.10.6 GAA Authorization flag + +The GAA Authorization flag is a GAA Service type specific integer code, which authorizes a defined security operation in the GAA service. A list of allowed operations is stored for each GAA Service Subscription. + +The values of the authorization flags for each application type using them are listed in TS 29.109 [59] + +The Authorization Flag is permanent subscriber data and is stored in the HSS, BSF and NAF. + +### 3.10.7 Bootstrapping Transaction Identifier + +The Bootstrapping Transaction Identifier (B-TID) identifies the security association between a BSF and a UE after a bootstrapping procedure in GAA. According [57] the B-TID value shall be also generated in format of NAI by taking the base64 encoded RAND value [60] and the BSF server name, i.e. base64 encoded (RAND)@BSF\_servers\_domain\_name. + +The Bootstrapping Transaction Identifier is temporary subscriber data and is stored in the BSF and NAF. + +### 3.10.8 Key Lifetime + +Key Lifetime is an integer which defines the length of the validity period of bootstrapping information in BSF in seconds. + +The Key Lifetime is permanent subscriber data and is stored in the HSS, and the BSF. + +### 3.10.9 UICC Security Type + +The UICC Security Type indicates the allocation of security procedure inside a User Equipment i.e. are security applications executed entirely inside mobile equipment or also in UICC . + +The values of UICC Security Type are defined in TS 29.109 [59] + +The UICC Security Type is permanent subscriber data and is stored in the HSS and BSF. + +### 3.10.10 NAF Group + +The NAF Group contains one or more NAF Address elements (cf. clause 3.9.12) defining the NAFs that belong to the NAF Group. The NAF Group is identified by NAF Group Identity (cf. clause 3.9.11). + +NOTE: The grouping of NAFs is done in each home network separately, i.e. one NAF contacting BSFs in different home networks belongs to different groups in every home network. + +The NAF Group Setting is permanent subscriber data and is stored in the BSF. + +### 3.10.11 NAF Group Identity + +The NAF Group Identity is a freely defined string that the home operator can uses as a name of a group of NAFs. + +The NAF Group Identity is permanent subscriber data and is stored in the HSS and BSF. + +### 3.10.12 NAF Address + +The NAF Address is a freely defined string that can be used identify one or more NAFs. The NAF Address may contain a fully qualified domain identifying a single NAF. The NAF Address may also contain a domain name with wildcards "\*" and it can be used to identity multiple NAFs. + +The NAF Address is permanent subscriber data and is stored in the BSF. + +### 3.10.13 Key Expirytime + +Key Expirytime is an integer which defines the expiry time of bootstrapping information in BSF in seconds according to Diameter Time format as specified in IETF RFC 3588[51]. + +The Key Expirytime is temporary subscriber data and is stored in the BSF and NAF. + +### 3.10.14 Boostrapping Info Creation Time + +Boostrapping Info Creation Time is an integer which defines the point of time when the corresponding boostrapping information is created in BSF in seconds according. + +### 3.10.15 Diameter Server Identity of HSS + +The Diameter Server Identity of HSS identifies the HSS storing the GAA specific subscription data for a subscriber. It is used in requests send by the BSF to the HSS. The format of the Diameter Server Identity is the Diameter Identity defined in IETF RFC 3588 [51]. + +The Diameter Server Identity of the HSS is temporary data and is stored in BSF. + +## 3.11 Definition of subscriber data I-WLAN domain + +NOTE: The WLAN Network Selection and WLAN/3GPP Radio Interworking features supersede the I-WLAN feature from Rel-12 onwards, therefore all I-WLAN subscriber data specified in the present Clause are no longer maintained. + +### 3.11.1 Data related to subscription, identification and numbering + +#### 3.11.1.1 IMSI + +The International Mobile Subscriber Identity (IMSI) is defined in 3GPP TS 23.003 [5]. The IMSI serves as the root of the subscriber data pseudo-tree. + +#### 3.11.1.2 Mobile Subscriber ISDN Number (MSISDN) + +Mobile Subscriber ISDN Number (MSISDN) is defined in 3GPP TS 23.003 [5]. One MSISDN is used for WLAN-IW subscription. If the multnumbering option applies, the MSISDN used is the Basic MSISDN (see clause 2.1.3 for more information on MSISDNs for multnumbering option). + +#### 3.11.1.3 W-APN + +The WLAN Access Point Name (W-APN) is defined in 3GPP TS 23.003 [5]. This parameter identifies a data network and a point of interconnection to that network (Packet Data Gateway). + +#### 3.11.1.4 List of authorized visited network identifiers + +The list of authorized visited network identifiers field indicates which 3GPP visited network identifiers are allowed for roaming. + +This list can be a linear list of visited network identifiers or a compound list of network identifier types e.g. home PLMN or home country; however the exact structure of the list is an implementation option. + +#### 3.11.1.5 3GPP AAA Proxy Name + +The 3GPP AAA Proxy Name, specified in 3GPP TS 29.234 [63], defines the Diameter or RADIUS Identity of the 3GPP AAA Proxy node. + +#### 3.11.1.6 3GPP AAA Server Name + +The 3GPP AAA Server Name, specified in 3GPP TS 29.234 [63], defines the Diameter or RADIUS Identity of the 3GPP AAA Server node. + +#### 3.11.1.7 Serving PDG List + +The Serving PDG List field contains the addresses of the PDGs to which the WLAN UE is connected. + +#### 3.11.1.8 Serving WAG + +The Serving WAG field contains the WAG address information obtained through the successful user authentication procedure. + +#### 3.11.1.9 WLAN UE Local IP Address + +The WLAN UE Local IP Address field, specified in 3GPP TS 23.234 [62], represents the IPv4/IPv6 address of the WLAN UE in the WLAN AN. It is an address used to deliver the packet to a WLAN UE in a WLAN AN. + +### 3.11.1.10 WLAN UE Remote IP Address + +The WLAN UE Remote IP Address field, specified in 3GPP TS 23.234 [62], represents the IPv4/IPv6 address of the WLAN UE in the network which the WLAN UE is accessing. It is an address used in the data packet encapsulated by the WLAN UE-initiated tunnel and is the source address used by applications in the WLAN UE. The WLAN UE Remote IP address is per W-APN, see clause 3.11.5.1.4. + +## 3.11.2 Data related to registration + +### 3.11.2.1 User Status + +The User Status field identifies the registration status of the I-WLAN User. The User Status shall be either REGISTERED, in which case there is an associated Serving 3GPP AAA Server Name stored at the HSS, or NOT\_REGISTERED, in which case there may or may not be a 3GPP AAA Server Name stored. + +### 3.11.2.2 Emergency Access Flag + +The Emergency Access flag is specified in 3GPP TS 29.234 [63]. It enables operators to control the access to I-WLAN for emergency purposes. The parameter takes either of the following values: + +- Access is for emergency purposes. +- Access is not for emergency purposes. + +The flag is set in the 3GPP AAA Server if the WLAN Direct IP access is indicated to be for emergency purposes. + +### 3.11.2.3 Diameter Server Identity of HSS + +The Diameter Server Identity of HSS identifies the identity of HSS storing the I-WLAN specific subscription data for a subscriber. It is used in requests sent by the 3GPP AAA Server to the HSS. The format of the Diameter Server Identity is the Diameter Identity defined in IETF RFC 3588 [51]. + +The Diameter Server Identity of the HSS is temporary data and is stored in 3GPP AAA Server. + +## 3.11.3 Data related to authentication and ciphering + +### 3.11.3.1 Random Number (RAND), Signed Response (SRES) and Ciphering Key (Kc) + +Random Number (RAND), Signed Response (SRES) and Ciphering Key (Kc) fields form a triplet vector used for authentication and encryption as defined in 3GPP TS 43.020 [31]. + +In I-WLAN for SIM based users, triplet vectors are calculated in the 2G AuC and provided to the 2G HLR/HSS (see GSM 12.03 [36]). For USIM based users, triplet vectors are derived from quintuplet vectors in the 3G HLR/HSS if needed (see 3GPP TS 33.102 [52]). + +A set of up to 5 triplet values are sent from the 2G HLR/HSS to the 3GPP AAA Server upon request. These data are temporary subscriber data stored in the 3GPP AAA Server. + +### 3.11.3.2 Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key (IK) and Authentication Token (AUTN) + +Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key (IK) and Authentication Token (AUTN) fields form a quintuplet vector used for user authentication, data confidentiality and data integrity as defined in 3GPP TS 33.102 [52]. + +In I-WLAN, a set of quintuplet vectors are calculated in the AuC, and up to 5 quintuplets are sent from the HLR/HSS to the 3GPP AAA Server upon request (see 3GPP TS 29.002 [27]). + +These data are temporary subscriber data stored in the HSS and 3GPP AAA Server. + +### 3.11.3.3 Master Key (MK) + +The Master Key (MK) field is defined in 3GPP TS 33.234 [92]. It enables keys to be derived. + +### 3.11.3.4 Transient EAP Keys (TEKs) + +The Transient EAP Keys (TEKs) field is defined in 3GPP TS 33.234 [92] and are used to protect the EAP packets. + +### 3.11.3.5 Master Session Key (MSK) + +The Master Session Key (MSK) field is defined in 3GPP TS 33.234 [92] and is used to obtain the key material required for the link layer confidentiality mechanism and IPsec confidentiality mechanism. + +## 3.11.4 Data related to session + +### 3.11.4.1 Session Identifier + +The Session Identifier field, specified in 3GPP TS 29.234 [63], indicates a unique Diameter signalling session specific to the user. + +### 3.11.4.2 Session-Timeout + +The Session-Timeout field, specified in 3GPP TS 29.234 [63], indicates the maximum period for a session measured in seconds. It is used for re-authentication purposes. If this field does not appear, the WLAN AN shall apply default time intervals. + +## 3.11.5 Operator Determined Barring general data + +### 3.11.5.1 W-APN Authorised List + +The W-APN Authorised field is specified in 3GPP TS 29.234 [63]. It contains authorization information for each W-APN. This parameter indicates the list of allowed W-APNs, the environment where the access is allowed and optionally the charging data specific for that W-APN and the Static IP address. + +#### 3.11.5.1.1 W-APN Identifier List + +See clause 3.11.1.3. + +#### 3.11.5.1.2 W-APN Barring Type List + +The W-APN Barring Type field is specified in 3GPP TS 29.234 [63]. It indicates the subscriber access type to the home and visited network's services. The parameter takes either of the following values: + +- Allow access to this W-APN regardless of whether the subscriber is located in a VPLMN or in the HPLMN; +- Prohibit access to this W-APN within the HPLMN when the subscriber is located in a VPLMN; +- Prohibit access to this W-APN within the VPLMN when the subscriber is located in a VPLMN; +- Prohibit access to this W-APN within the HPLMN when the subscriber is located in the HPLMN; +- Prohibit access to public Internet through any W-APN regardless of whether the subscriber is located in a VPLMN or in the HPLMN. + +#### 3.11.5.1.3 W-APN Charging Data List + +The W-APN Charging Data field is specified in 3GPP TS 29.234 [63]. When this parameter is present, it supersedes the general charging information to be applied for the subscriber. See clause 3.11.7. + +#### 3.11.5.1.4 Static WLAN UE Remote IP Address List + +WLAN UE IP Address field identifies the IPv4/IPv6 address that the operator has statically assigned to the WLAN UE. See clause 3.11.1.10. + +#### 3.11.5.1.5 Maximum Number of Accesses List + +The Maximum Number of Accesses is specified in 3GPP TS 29.234[63]. It enables operators to specify the maximum number of concurrent accesses per W-APN. + +#### 3.11.5.1.6 Access Number List + +Access Number is an integer counter kept at the 3GPP AAA Server per W-APN. + +#### 3.11.5.2 Access Dependence Flag + +The Access Dependence Flag is specified in 3GPP TS 29.234 [63]. It enables operators to authenticate a subscriber accessing the I-WLAN by WLAN 3GPP IP Access independently of a previous WLAN Direct IP Access. The parameter takes either of the following values: + +- Allow access to WLAN 3GPP IP Access independently of a previous WLAN Direct IP Access. +- Prohibit access to WLAN 3GPP IP Access independently of a previous WLAN Direct IP Access. + +#### 3.11.5.3 I-WLAN Access Type + +The I-WLAN Access Type field is specified in 3GPP TS 29.234 [63]. It indicates the types of access the subscriber has used to access to the IWLAN. The parameter takes either of the following values: + +- WLAN 3GPP IP Access; +- WLAN Direct IP Access. + +#### 3.11.5.4 WLAN Direct IP Access + +WLAN Direct IP Access (see 3GPP TS 29.234 [63]) is permanent data conditionally stored in HSS. It indicates whether the user is allowed to have WLAN direct IP access to external IP networks from the WLAN Access Network. The WLAN Direct IP Access is stored as temporary data also in the 3GPP AAA Server. + +### 3.11.6 QoS general data + +#### 3.11.6.1 Max Subscribed Bandwidth + +The Max Subscribed Bandwidth field, specified in 3GPP TS 29.234 [63], indicates the Max subscribed bandwidth. + +#### 3.11.6.2 Routing Policy + +The Routing Policy field, specified in 3GPP TS 29.234 [63], defines a packet filter for an IP flow. + +#### 3.11.6.3 Subscribed 3GPP WLAN QoS Profile + +The Subscribed 3GPP WLAN QoS Profile field, specified in 3GPP TS 29.234 [63], defines a subscribed 3GPP WLAN QoS profile per W-APN. + +#### 3.11.6.4 Authorized 3GPP WLAN QoS Profile + +The Authorized 3GPP WLAN QoS Profile field, specified in 3GPP TS 29.234 [63], defines the authorized 3GPP WLAN QoS profile per W-APN for a user. + +## 3.11.7 Data related to Charging + +### 3.11.7.1 Charging Data + +The Charging Data field identifies the Charging Characteristics plus the Charging Nodes to be applied per user for all W-APNs or per user for individual W-APNs. + +#### 3.11.7.1.1 Charging Characteristics + +Charging Characteristics field is defined in 3GPP TS 32.252 [66]. It indicates the charging type to be applied to the user tunnel. + +### 3.11.7.2 Primary OCS Charging Function Name + +The Primary OCS Charging Function Name field identifies the Primary OCS Function node that performs on-line based charging. The format is specified in 3GPP TS 29.234 [63]. + +### 3.11.7.3 Secondary OCS Charging Function Name + +The Secondary OCS Charging Function Name field identifies the Secondary OCS Charging Function node that performs on-line based charging. The format is specified in 3GPP TS 29.234 [63]. + +### 3.11.7.4 Primary Charging Collection Function Name + +The Primary Charging Collection Function Name field identifies the primary Charging Collection Function node that provides off-line charging support for the IMS subscribers. The format is specified in 3GPP TS 29.234 [63]. + +### 3.11.7.5 Secondary Charging Collection Function Name + +The Secondary Charging Collection Function Name field identifies the secondary Charging Collection Function node that provides off-line charging support for the IMS subscribers. The format is specified in 3GPP TS 29.234 [63]. + +### 3.11.7.6 WLAN Session Identifier + +The WLAN Session Identifier is the identifier generated by 3GPP AAA Server and sent to PDG. Together with PDG Charging Identifier, it is used for correlating WLAN AN and PDG charging data. The format is specified in 3GPP TS 32.299 [67]. + +### 3.11.7.7 PDG Charging Identifier + +The PDG Charging Identifier is the identifier generated by PDG and sent to 3GPP AAA Server. Together with WLAN Session Identifier, it is used for correlating WLAN AN and PDG charging data. The format is specified in 3GPP TS 32.299 [67]. + +## 3.12 Data related to Access Network Discovery and Selection Function (ANDSF) + +### 3.12.1 General + +Following clauses describe the Data that is defined on per user basis and is related to Access Network Discovery and Selection Function (ANDSF). + +### 3.12.2 Policy Information + +This set contains a list of inter-system mobility policies. Each policy contains the following information while the corresponding coding is defined in 3GPP TS 24.312 [86]: + +- Rule Priority: indicates the priority of the correspondent intersystem mobility policy; +- Prioritized Access: a set of information providing lists of possible technologies the UE can access. The technologies are prioritized based on operator preferences. It is also possible to indicate an access technology as forbidden or as restricted; +- Validity Area and Time of the Day: these two sets of information indicate where and when the policy can be applied by the UE. Different ways to describe the area of validity of the policy are provided and described in 3GPP TS 24.312 [86]. There can be multiple policies valid (e.g. overlapping validity areas): in this case, the value of Rule Priority is used as discriminator; +- Roaming: it indicates if the policy is also valid if the UE is roaming. + +This set is permanent data conditionally stored in the ANDSF. + +### 3.12.3 Discovery Information + +This set contains the information regarding the access networks the UE can discover. + +It contains the following information while the corresponding coding is defined in 3GPP TS 24.312 [86]: + +- Access Network Type: indicates the type of the network for which discovery assistance information is provided; +- Access Network Area: describes the location where the access network indicated in the correspondent Access Network Type is expected to be available. Different ways to describe the area of validity of the policy are provided in 3GPP TS 24.312 [86]; +- Access Network Information Reference: is a pointer to a set containing the relevant information for the networks the UE can discover (e.g. SSIDs and correspondent channels in case of WLAN access). + +This set is permanent data conditionally stored in the ANDSF. + +### 3.12.4 UE Location + +This set provides information about the UE location, i.e. it is a way to indicate the position of the UE. This information can be used by ANDSF to limit the number of information sent to the UE. Different ways to describe the UE location are provided in 3GPP TS 24.312 [86]. + +This set is temporary data conditionally stored in the ANDSF. + +## 3.13 Proximity Services (ProSe) + +### 3.13.1 General + +Following clauses describe the data that are defined on per user basis and are related to Proximity Services (ProSe). + +### 3.13.2 ProSe Subscription data + +#### 3.13.2.1 ProSe-Permission + +The ProSe-permission is part of the ProSe Subscription data information and is specified in 3GPP TS 29.344 [99]. + +ProSe-permission is permanent data conditionally stored in HSS, MME and ProSe Function. + +### 3.13.2.2 PLMN-Allowed-ProSe + +The PLMN-Allowed-ProSe is part of the ProSe Subscription data and is specified in 3GPP TS 29.344 [99]. + +PLMN-Allowed-ProSe is permanent data conditionally stored in HSS, MME and ProSe Function. + +### 3.13.3 Application layer user ID + +The Application layer user ID is specified in 3GPP TS 23.303 [98]. + +Application layer user ID is permanent data conditionally stored in ProSe Function and ProSe Application Server. + +### 3.13.4 EPC ProSe User ID + +The EPC ProSe User user ID is specified in 3GPP TS 23.003 [5]. + +EPC ProSe User ID is temporary data conditionally stored in ProSe Function, ProSe Application Server + +### 3.13.5 ProSe Application ID + +The ProSe Application ID is specified in 3GPP TS 23.003 [5]. + +ProSe Application ID is permanent data conditionally stored in ProSe Function. + +### 3.13.6 ProSe Application Code + +The ProSe Application Code is specified in 3GPP TS 23.003 [5]. + +ProSe Application Code is temporary data conditionally stored in ProSe Function. + +### 3.13.7 Discovery Filter + +#### 3.13.7.1 Filter ID + +The Filter ID part of the Discovery Filter is specified in 3GPP TS 24.334 [100]. + +Filter ID is permanent data conditionally stored in ProSe Function. + +#### 3.13.7.2 ProSe Application Code + +The ProSe Application Code as part of the Discovery Filter is specified in 3GPP TS 23.003 [5]. + +ProSe Application Code is permanent data conditionally stored in ProSe Function. + +#### 3.13.7.3 ProSe Application Mask + +The ProSe Application Mask as part of the Discovery Filter is specified in 3GPP TS 24.334 [100]. + +ProSe Application Mask as part of the discovery filter is permanent data conditionally stored in ProSe Function. + +#### 3.13.7.4 TTLTimer T4002 + +The TTLTimer T4002 as part of the Discovery Filter is specified in 3GPP TS 24.334 [100]. + +The TTLTimer T4002 as part of the discovery filter is permanent data conditionally stored in ProSe Function. + +### 3.13.8 ProSe Function Identity + +ProSe Function Identity is specified in 3GPP TS 29.344 [99]. + +The ProSe Function Identity is temporary subscriber data and is conditionally stored in the HSS and in the ProSe Application Server. + +### 3.13.9 ProSe Metadata Index Mask + +The ProSe Metadata Index Mask indicates which part of the ProSe Application Code contains the metadata index. It is specified in 3GPP TS 24.334 [100]. + +ProSe Metadata Index Mask is permanent data conditionally stored in ProSe Function. + +### 3.13.10 PC5-tech + +The PC5-tech indicates the PC5 radio technology in order to enable co-ordination between the announcing and monitoring side. It is specified in 3GPP TS 24.334 [100]. + +PC5-tech is temporary data conditionally stored in ProSe Function. + +## 3.14 Architecture Enhancements for Service Exposure (AESE) + +### 3.14.1 General + +Following clauses describe the data that are defined on a per user basis and are related to Architecture Enhancements for Service Exposure (AESE). + +### 3.14.2 SCEF-Reference-ID + +SCEF-Reference-ID is defined in 3GPP TS 29.336 [103]. + +SCEF-Reference-ID is used to uniquely identify an event created by an SCEF. + +SCEF-Reference-ID is temporary data conditionally stored in the SCEF, HSS, MME and SGSN. + +### 3.14.3 SCEF-ID + +SCEF-ID is defined in 3GPP TS 29.336 [103]. + +SCEF-ID is used to uniquely identify an SCEF. + +SCEF-ID is permanent data conditionally stored in the SCEF, HSS, MME and SGSN. + +### 3.14.4 Monitoring-Type + +Monitoring-Type is defined in 3GPP TS 29.336 [103]. + +Monitoring-Type is used to identify type the event to be monitored. + +Monitoring-Type is permanent data conditionally stored in the SCEF, HSS, MME and SGSN. + +### 3.14.5 Maximum-Number-of-Reports + +Maximum-Number-of-Reports is defined in 3GPP TS 29.336 [103]. + +Maximum-Number-of-Reports is used to indicate the number of reports to be delivered to the SCEF. + +Maximum-Number-of-Reports is permanent data conditionally stored in the SCEF, HSS, MME and SGSN. + +### 3.14.6 UE-Reachability-Configuration + +UE-Reachability-Configuration number is defined in 3GPP TS 29.336 [103]. + +UE-Reachability-Configuration contain details for configuration for UE reachability. + +UE-Reachability-Configuration is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN. + +### 3.14.7 Monitoring-Duration + +Monitoring-Duration is defined in 3GPP TS 29.336 [103]. + +Monitoring-Duration indicates the time for which the SCEF request to perform the monitoring. + +Monitoring-Duration is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN. + +### 3.14.8 Maximum-Detection-Time + +Maximum-Detection-Time is defined in 3GPP TS 29.336 [103]. + +Maximum-Detection-Time contains the maximum number of time without any communication with the UE after which the SCEF is to be informed that the UE is considered to be unreachable. + +Maximum-Detection-Time is permanent data conditionaly stored in the SCEF and HSS. + +### 3.14.9 Reachability-Type + +Reachability-Type is defined in 3GPP TS 29.336 [103]. + +Reachability-Type indicates for which kind of reachability of the subscriber needs to be reported i.e. reachable for SMS or data. + +Reachability-Type is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN. + +### 3.14.10 Maximum-Latency + +Maximum Latency is defined in 3GPP TS 29.336 [103]. + +Maximum Latency contains the maximum acceptable delay time for downlink data transfer. + +Maximum Latency is permanent data conditionaly stored in the SCEFand HSS. + +### 3.14.11 Maximum-Response-Time + +Maximum Response Time is defined in 3GPP TS 29.336 [103]. + +Maximum Response Time contains the maximum time for which the UE stays reachable. + +Maximum Response Time is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN. + +### 3.14.12 MONTE-Location-Type + +MONTE-Location-Type is defined in 3GPP TS 29.336 [103]. + +MONTE-Location-Type indicates how actual the location information should be. + +Location-Type is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN. + +### 3.14.13 Accuracy + +Accuracy is defined in 3GPP TS 29.336 [103]. + +Accuracy is used to indicate in which form geographic location information has to be provided in the report. Accuracy is permanent data conditionaly stored in the SCEF, HSS, MME and SGSN. + +### 3.14.14 Association-Type + +Association-Type is defined in 3GPP TS 29.336 [103]. + +Association-Type indicates which kind (IMEI or SV) of change of the IMEI has to be reported. Association-Type is permanent data conditionally stored in the SCEF and HSS. + +### 3.14.15 Charged-Party + +Charged-Party is defined in 3GPP TS 32.299 [67]. + +Charged-Party holds the address (Public User ID: SIP URI, Tel URI, etc.) of the party to be charged. + +Charged-Party is permanent data conditionally stored in the SCEF, HSS, MME and SGSN. + +### 3.14.16 Remaining-number-of-reports + +Remaining number of reports is defined in 3GPP TS 29.336 [103]. + +Remaining number of reports holds the number of reports which are outstanding to be sent to the SCEF. Remaining number of reports is temporary data conditionally stored in the SCEF, HSS, MME and SGSN. + +### 3.14.17 Communication Pattern set + +#### 3.14.17.1 Periodic-Communication-Indicator + +Periodic-Communication-Indicator is defined in 3GPP TS 29.336 [103]. + +Periodic-Communication-Indicator provides information if the CP occurs periodically or on demand. + +Periodic-Communication-Indicator is permanent data conditionally stored in the SCEF, HSS and MME. + +#### 3.14.17.2 Communication-Duration-Time + +Communication-duration-time is defined in 3GPP TS 29.336 [103]. + +Communication-duration-time contains the time in seconds of the duration of the periodic communication. + +Communication-duration-time is permanent data conditionally stored in the SCEF, HSS and MME. + +#### 3.14.17.3 Periodic-Time + +Periodic-Time is defined in 3GPP TS 29.336 [103]. + +Periodic-Time contains the time in seconds of the interval for periodic communication. + +Periodic-Time is permanent data conditionally stored in the SCEF, HSS and MME. + +#### 3.14.17.4 Scheduled-Communication-Time + +Scheduled-Communication-Time is defined in 3GPP TS 29.336 [103]. + +Scheduled-Communication-Time contains start and end times and repetition during a week for periodic communication. + +Scheduled-Communication-Time is permanent data conditionally stored in the SCEF, HSS and MME. + +#### 3.14.17.5 Stationary-Indication + +Stationary-Indication is defined in 3GPP TS 29.336 [103]. + +Stationary-Indication contains the information if the subscriber is stationary or mobile. + +Stationary-Indication is permanent data conditionally stored in the SCEF, HSS and MME. + +### 3.14.17.6 Validity-Time + +Validity-Time is defined in 3GPP TS 29.336 [103]. + +Validity-Time provides the expiration time at which the CP sets shall be deleted. + +Validity-Time is permanent data conditionally stored in the SCEF, HSS and MME. + +### 3.14.18 AESE-Subscription-Data + +AESE-Subscription-Data contains details on subscription information of the allowed services such as: + +- allowed service (e.g. monitoring, CP set); +- allowed service types (e.g. allowed Monitoring events). + +AESE-Subscription-Data is permanent data conditionally stored in the HSS. + +### 3.14.19 SCEF-Realm + +SCEF-Realm is defined in 3GPP TS 29.272 [81]. + +SCEF-Realm is used to identify the realm of the SCEF. + +SCEF-Realm is permanent data conditionally stored in the SCEF, HSS, MME and SGSN. + +### 3.14.20 External Identifier for Monitoring Event Configuration + +The External Identifier for Monitoring Event Configuration contains an External Identifier as defined in 3GPP TS 23.003 [5] and identifies the External Identifier in the subscription that is associated to each Monitoring Event Configuration (MONTE) data instance. + +The External Identifier for each Monitoring Event Configuration is permanent subscriber data and is stored in the HSS and conditionally in the SCEF, MME and SGSN. + +### 3.14.21 External Group Identifier + +The External Group Identifier contains an External Group Identifier as defined in 3GPP TS 23.003 [5]. + +The External Group Identifier for Monitoring Event Configuration is permanent subscriber data and is stored in the HSS and conditionally in the SCEF. + +## 3.15 Data related to WebRTC + +### 3.15.1 Allowed WAF and/or WWSF Identity List + +An Allowed WAF or WWSF Identity identifies a WebRTC Authentication Function or WebRTC Web Server Function the subscription is allowed to use. See 3GPP TS 33.203 [49]. Multiple WAF or WWSF identities may be stored within the Allowed WAF and/or WWSF Identity List. + +The Allowed WAF and/or WWSF Identity List is permanent data stored in the HSS and in the S-CSCF. + +## 3.16 V2X Service (V2X) + +### 3.16.1 General + +Following clauses describe the data that are defined on per user basis and are related to V2X Service (V2X). + +### 3.16.2 V2X Subscription data for the network scheduled LTE sidelink communication + +#### 3.16.2.1 V2X-Permission + +The V2X-Permission is part of the V2X Subscription data information for the network scheduled LTE sidelink communication and is specified in 3GPP TS 29.272 [81]. + +V2X-Permission is permanent data conditionally stored in HSS and MME. + +#### 3.16.2.2 UE-PC5-AMBR + +The UE-PC5-AMBR is part of the V2X Subscription data information for the network scheduled LTE sidelink communication and is specified in 3GPP TS 29.272 [81]. + +UE-PC5-AMBR is permanent data conditionally stored in HSS and MME. + +#### 3.16.2.3 V2X-PC5-Allowed-PLMN + +The V2X-PC5-Allowed-PLMN is part of the V2X Subscription data and is specified in 3GPP TS 29.388 [108]. + +V2X-PC5-Allowed-PLMN is permanent data conditionally stored in HSS and V2X Control Function. + +### 3.16.3 V2X Authorization data + +#### 3.16.3.1 V2X-Permission-in-VPLMN + +The V2X-Permission-VPLMN is part of the V2X authorization data and is specified in 3GPP TS 29.389 [109]. + +V2X-Permission-in-VPLMN is permanent data conditionally stored in V2X Control Function. + +#### 3.16.3.2 V2X-Application-Server + +The V2X-Application-Server is part of the V2X authorization data and is specified in 3GPP TS 29.389 [109]. + +V2X-Application-Server is permanent data conditionally stored in V2X Control Function. + +#### 3.16.3.3 PC5-RAT-Type + +The PC5-RAT-Type is part of the V2X authorization data and is specified in 3GPP TS 29.389 [109]. + +PC5-RAT-Type is permanent data conditionally stored in HSS and V2X Control Function. + +### 3.16.4 V2X Control Function Identity + +V2X Function Identity is specified in 3GPP TS 29.388 [108]. + +The V2X Control Function Identity is temporary subscriber data and is conditionally stored in the HSS. + +### 3.16.5 V2X Subscription data for the network scheduled NR sidelink communication + +#### 3.16.5.1 V2X-Permission + +The V2X-Permission is part of the V2X Subscription data information for the network scheduled NR sidelink communication and is specified in 3GPP TS 29.272 [81]. + +V2X-Permission is permanent data conditionally stored in HSS and MME. + +#### 3.16.5.2 UE-PC5-AMBR + +The UE-PC5-AMBR is part of the V2X Subscription data information for the network scheduled NR sidelink communication and is specified in 3GPP TS 29.272 [81]. + +UE-PC5-AMBR is permanent data conditionally stored in HSS and MME. + +#### 3.16.5.3 V2X-PC5-Allowed-PLMN + +The V2X-PC5-Allowed-PLMN is part of the V2X Subscription data and is specified in 3GPP TS 29.388 [108]. + +V2X-PC5-Allowed-PLMN is permanent data conditionally stored in HSS and V2X Control Function. + +#### 3.16.5.4 UE-PC5-QoS + +The UE-PC5-QoS is part of the V2X Subscription data information for the network scheduled NR sidelink communication and is specified in 3GPP TS 29.272 [81]. + +UE-PC5-AMBR is permanent data conditionally stored in HSS and MME. + +--- + +## 4 Summary of data stored in location registers + +Table 5.1 gives an overview of data stored in location registers for non-GPRS Network Access Mode (CS). + +Table 5.2 shows the data stored in the location registers, in the Gn/Gp-SGSN and in the GGSN for GPRS Network Access Mode. + +Tables 5.2A-1 show the data stored in the location registers, in the SGSN, S4-SGSN, MME, S-GW, P-GW, ePDG, 3GPP AAA server and 3GPP AAA server Proxy for EPS Network Access Mode. + +Table 5.2B-1 show the data stored by the UDM, AMF, SMF, SMSF, AUSF and NEF in the 5G System. + +Table 5.3 gives an overview of data stored for IP Multimedia services. + +In the tables, M = mandatory means that this parameter is stored for all subscribers with subscription of the Network Access Mode as shown in the table heading and defining the table; and C = conditional means that the parameter is subject to some condition (e.g. subscription of teleservice or other services, reception of optional message or short-lived data). The type indication indicates whether the subscriber data is temporary (T) or permanent (P) data, where permanent data can be set and modified but by the operator, whereas the temporary data are set and changed automatically by network functions. + +--- + +## 5 Accessing subscriber or PSI data + +It shall be possible to retrieve or store subscriber data concerning a specific MS from the HSS by use of each of the following references: + +- International Mobile Subscriber Identity (IMSI); + +- Mobile Station ISDN Number (MSISDN). + +It shall be possible to retrieve CSG subscriber data concerning a specific roaming MS from the CSS by use of each of the following references: + +- International Mobile Subscriber Identity (IMSI). + +It may be possible to retrieve subscriber data concerning a specific roaming MS from the CSS by use of each of the following references: + +- Mobile Station ISDN Number (MSISDN). + +It shall be possible to retrieve or store subscriber IP Multimedia service data concerning a specific IMS subscription from the HSS by use of each of the following references: + +- Private User Identity; +- Public User Identity. + +It shall be possible to retrieve or store PSI IP Multimedia service data from the HSS by use of each of the following references: + +- Public Service Identity. + +It shall be possible to retrieve or store subscriber data concerning a specific MS from the VLR by use of each of the following references: + +- International Mobile Subscriber Identity (IMSI); +- Temporary Mobile Subscriber Identity (TMSI). + +It shall be possible to retrieve or store subscriber data concerning a specific MS from the SGSN by use of each of the following references: + +- International Mobile Subscriber Identity (IMSI); +- Packet Temporary Mobile Subscriber identity (P-TMSI); +- International Mobile Equipment Identity (IMEI) for emergency attached UEs without IMSI (e.g; UICClassless UE) or with an unauthenticated IMSI. + +It shall be possible to retrieve or store subscriber data concerning a specific MS from the GGSN by use of the following reference: + +- International Mobile Subscriber Identity (IMSI); +- International Mobile Equipment Identity (IMEI) for emergency attached UEs without IMSI (e.g; UICClassless UE) or with an unauthenticated IMSI. + +It shall be possible to retrieve or store subscriber data concerning a specific MS from the MME by use of each of the following references: + +- International Mobile Subscriber Identity (IMSI); +- Globally Unique Temporary Identity (GUTI); +- International Mobile Equipment Identity (IMEI) for emergency attached UEs without IMSI (e.g; UICClassless UE) or with an unauthenticated IMSI. + +It shall be possible to retrieve or store subscriber data concerning a specific MS from the S-GW and P-GW by use of the following reference: + +- International Mobile Subscriber Identity (IMSI); +- International Mobile Equipment Identity (IMEI) for emergency attached UEs without IMSI (e.g; UICClassless UE) or with an unauthenticated IMSI. + +It shall be possible to retrieve or store subscriber data concerning a specific MS from the 3GPP AAA Server by use of each of the following references: + +- International Mobile Subscriber Identity (IMSI); +- Mobile Subscriber ISDN Number (MSISDN). +- International Mobile Equipment Identity (IMEI) for emergency attached UEs without IMSI (e.g: UICClassless UE) or with an unauthenticated IMSI. + +It shall be possible to retrieve or store subscriber data concerning a specific MS from the 3GPP AAA Proxy by use of the following reference: + +- Mobile Subscriber ISDN Number (MSISDN). + +It shall be possible to retrieve or store subscriber data concerning a specific MS from the WAG by use of the following reference: + +- Mobile Subscriber ISDN Number (MSISDN). + +It shall be possible to retrieve or store subscriber data concerning a specific MS from the PDG by use of each of the following references: + +- International Mobile Subscriber Identity (IMSI); +- Mobile Subscriber ISDN Number (MSISDN). +- International Mobile Equipment Identity (IMEI) for emergency attached UEs without IMSI (e.g: UICClassless UE) or with an unauthenticated IMSI. + +NOTE: See clause 4 for explanation of M, C, T and P in table 5.1, table 5.2, table 5.2A-1, table 5.2A-2, table 5.2A-3, table 5.2B-1 and table 5.3. + +## 5.1 CS Network Access Mode Data Storage + +**Table 5.1: Overview of data stored for CS Network Access Mode** + +| PARAMETER | CLAUSE | HLR | VLR | TYPE | +|-------------------------------------------------|-----------|-----|-----|------| +| IMSI | 2.1.1.1 | M | M | P | +| Network Access Mode | 2.1.1.2 | M | - | P | +| International MS ISDN number | 2.1.2 | C | C | P | +| multinumbering MSISDNs | 2.1.3 | C | - | P | +| Basic MSISDN indicator | 2.1.3.1 | C | - | P | +| MSISDN-Alert indicator | 2.1.3.2 | C | - | P | +| TMSI | 2.1.4 | - | C | T | +| LMSI | 2.1.8 | C | C | T | +| Mobile Station Category | 2.2.1 | M | M | P | +| LMU Identifier | 2.2.2 | C | C | P | +| IMEISV | 2.2.3 | C | C | T | +| RAND, SRES and Kc | 2.3.1 | | C | T | +| RAND, XRES, CK, IK and AUTN | 2.3.2 | M | C | T | +| Ciphering Key Sequence Number | 2.3.3 | - | M | T | +| Key Set Identifier (KSI) | 2.3.4 | - | M | T | +| Key Status | 2.3.9 | - | C | T | +| MSRN | 2.4.1 | - | C | T | +| Location Area Identity | 2.4.2 | - | M | T | +| VLR number | 2.4.5 | M | - | T | +| MSC number | 2.4.6 | M | C | T | +| HLR number | 2.4.7 | - | C | T | +| Subscription restriction | 2.4.10 | C | - | P | +| RSZI lists | 2.4.11.1 | C | - | P | +| Zone Code List | 2.4.11.2 | - | C | P | +| MSC area restricted flag | 2.4.12 | M | - | T | +| LA not allowed flag | 2.4.13 | - | M | T | +| ODB-induced barring data | 2.4.15.1 | C | - | T | +| Roaming restriction due to unsupported feature | 2.4.15.2 | M | M | T | +| Cell Global ID or Service Area ID | 2.4.16 | - | C | T | +| LSA Identity | 2.4.17.1 | C | C | P | +| LSA Priority | 2.4.17.2 | C | C | P | +| LSA Preferential Access Indicator | 2.4.17.2A | C | C | P | +| LSA Active Mode Support Indicator | 2.4.17.2B | C | C | P | +| LSA Only Access Indicator | 2.4.17.3 | C | C | P | +| LSA Active Mode Indicator | 2.4.17.4 | C | C | P | +| VPLMN Identifier | 2.4.17.5 | C | - | P | +| Access Restriction Data | 2.4.18 | C | C | P | +| Selected CN operator ID | 2.4.19 | - | C | T | +| IP-SM-GW number | 2.4.20 | C | - | T | +| IP-SM-GW Diameter Identity | 2.4.20A | C | - | T | +| Paging area | 2.4.21 | C | C | T | +| Closed Subscriber Group Information | 2.4.22 | C | C | P | +| Service Centre Address | 2.4.23 | C | - | P | +| Subscribed Periodic LAU Timer | 2.4.24 | C | C | P | +| Provision of bearer service | 2.5.1 | M | M | P | +| Provision of teleservice | 2.5.2 | M | M | P | +| BC allocation | 2.5.3 | C | C | P | +| IMSI detached flag | 2.7.1 | - | C | T | +| Confirmed by Radio Contact indicator | 2.7.4.1 | - | M | T | +| Subscriber Data Confirmed by HLR indicator | 2.7.4.2 | - | M | T | +| Location Information Confirmed in HLR indicator | 2.7.4.3 | - | M | T | +| Check SS indicator | 2.7.4.4 | M | - | T | +| MS purged for non-GPRS flag | 2.7.5 | M | - | T | +| MNRR-MSC | 2.7.7 | C | - | T | +| Subscriber data dormant | 2.7.8 | - | C | T | +| Cancel Location received | 2.7.8A | - | C | T | +| Subscriber status | 2.8.1 | C | C | P | +| Barring of outgoing calls | 2.8.2.1 | C | C | P | +| Barring of incoming calls | 2.8.2.2 | C | - | P | +| Barring of roaming | 2.8.2.3 | C | - | P | +| Barring of premium rate calls | 2.8.2.4 | C | C | P | +| Barring of supplementary service management | 2.8.2.5 | C | C | P | +| Barring of registration of call forwarding | 2.8.2.6 | C | - | P | +| Barring of invocation of call transfer | 2.8.2.7 | C | C | P | + +| PARAMETER | CLAUSE | HLR | VLR | TYPE | +|------------------------------------------------------------------|-------------------|-----|-----|------| +| Operator determined barring PLMN-specific data | 2.8.3 | C | C | P | +| Notification to CSE flag for ODB | 2.8.4 | C | - | T | +| gsmSCF address list for ODB | 2.8.5 | C | - | P | +| Handover Number | 2.9.1 | - | C | T | +| Messages Waiting Data | 2.10.1 | C | - | T | +| Mobile Station Not Reachable Flag | 2.10.2 | C | M | T | +| Memory Capacity Exceeded Flag | 2.10.3 | C | - | T | +| Trace Reference | 2.11.1 | C | C | P | +| Trace Type | 2.11.2 | C | C | P | +| Operations Systems Identity | 2.11.3 | C | C | P | +| HLR Trace Type | 2.11.4 | C | - | P | +| MAP Error On Trace | 2.11.5 | C | - | T | +| Trace Activated in VLR | 2.11.6 | C | C | T | +| Foreign Subscriber Registered in VLR | 2.11.7 | - | C | P | +| Trace Reference 2 | 2.11.9 | C | C | P | +| Trace depth | 2.11.10 | C | C | P | +| List of NE types to trace | 2.11.11 | C | C | P | +| Triggering events | 2.11.12 | C | C | P | +| List of interfaces to trace | 2.11.13 | C | C | P | +| IP address of Trace Collection Entity | 2.11.14 | C | C | P | +| MDT-Configuration | 2.11.15 | C | C | P | +| MDT User Consent | 2.11.16 | C | C | P | +| VGCS Group Membership List | 2.12.1 | C | C | P | +| VBS Group Membership List | 2.12.2 | C | C | P | +| Broadcast Call Initiation Allowed List | 2.12.2.1 | C | C | P | +| Originating CAMEL Subscription Information (O-CSI) | 2.14.1.1/3.1 | C | C | P | +| Terminating CAMEL Subscription Information (T-CSI) | 2.14.1.2 | C | - | P | +| VMSC Terminating CAMEL Subscription Information (VT-CSI) | 2.14.1.2/3.2 | C | C | P | +| Location Information/Subscriber state Information | 2.14.1.3 | C | - | P | +| USSD CAMEL subscription information(U-CSI) | 2.14.1.4 | C | - | P | +| SS invocation notification (SS-CSI) | 2.14.1.5/3.2 | C | C | P | +| Translation information flag(TIF-CSI) | 2.14.1.6/3.6 | C | C | P | +| Dialled service CAMEL Subscription Information (D-CSI) | 2.14.1.11/3.7 | C | C | P | +| USSD General CAMEL service information (UG-CSI) | 2.14.2.4 | C | - | P | +| O-CSI Negotiated CAMEL Capability Handling | 2.14.2.1 | C | - | T | +| SS-CSI Negotiated CAMEL Capability Handling | 2.14.2.1 | C | - | T | +| VT-CSI Negotiated CAMEL Capability Handling | 2.14.2.1 | C | - | T | +| Short Message Service CAMEL Subscription Information(MO-SMS-CSI) | 2.14.1.8/2.14.3.5 | C | C | P | +| Short Message Service CAMEL Subscription Information(MT-SMS-CSI) | 2.14.1.9/2.14.3.6 | C | C | P | +| MO-SMS-CSI VLR Negotiated CAMEL Capability Handling | 2.14.2.1 | C | - | T | +| MT-SMS-CSI VLR Negotiated CAMEL Capability Handling | 2.14.2.1 | C | - | P | +| M-CSI Negotiated CAMEL Capability Handling | 2.14.2.1 | C | - | T | +| VLR Supported CAMEL Phases | 2.14.2.3 | C | - | T | +| GsmSCF address for CSI | 2.14.2.4 | C | - | P | +| VLR Offered CAMEL4 CSIs | 2.14.2.2A | C | - | T | +| IST Alert Timer | 2.15.1 | C | C | P | +| Privacy Exception List | 2.16.1.1 | C | C | P | +| GMLC Numbers | 2.16.1.2 | C | C | P | +| MO-LR List | 2.16.1.3 | C | C | P | +| Service Types | 2.16.1.4 | C | C | P | +| Age Indicator | 2.17.1 | C | C | T | +| CS Allocation/Retention priority | 2.18.1 | C | C | P | +| ICS Indicator | 2.20.1 | C | C | P | +| CS to PS SRVCC Allowed | 2.21.4 | C | C | P | + +## 5.2 PS Network Access Mode Storage (GPRS) + +**Table 5.2: Overview of data used for PS Network Access Mode (GPRS)** + +| PARAMETER | Clause | HLR | VLR | Gn/Gp-SGSN | GGSN | TYPE | +|-----------------------------------------------------------|-----------|-----|---------|------------|------|------| +| IMSI | 2.1.1.1 | M | M | C | C | P | +| Network Access Mode | 2.1.1.2 | M | - | C note1 | - | P | +| IMSI Unauthenticated indicator | 2.1.1.3 | - | - | C | C | T | +| International MS ISDN number | 2.1.2 | C | C | C | C | P | +| multinumbering MSISDNs | 2.1.3 | C | - | - | - | P | +| Basic MSISDN indicator | 2.1.3.1 | C | - | - | - | P | +| MSISDN-Alert indicator | 2.1.3.2 | C | - | - | - | P | +| P-TMSI | 2.1.5 | - | - | C | - | T | +| TLLI | 2.1.6 | - | - | C | - | T | +| Random TLLI | 2.1.7 | - | - | C | - | T | +| IMEI | 2.1.9 | - | - | C | C | T | +| External Identifier Set | 2.1.10 | C | - | - | - | P | +| IMEISV | 2.2.3 | C | - | C | C | T | +| RAND/SRES and Kc | 2.3.1 | - | - | C | - | T | +| RAND, XRES, CK, IK, AUTN | 2.3.2 | M | - | C | - | T | +| Ciphering Key Sequence Number | 2.3.3 | - | - | M | - | T | +| Key Set Identifier (KSI) | 2.3.4 | - | - | M | - | T | +| Selected Ciphering Algorithm | 2.3.5 | - | - | M | - | T | +| Current Kc | 2.3.6 | - | - | M | - | T | +| P-TMSI Signature | 2.3.7 | - | - | C | - | T | +| Key Status | 2.3.9 | - | - | C | - | T | +| Routing Area Identity | 2.4.3 | - | - | M | - | T | +| VLR Number | 2.4.5 | M | - | C note2 | - | T | +| SGSN Number | 2.4.8.1 | M | C note2 | - | - | T | +| GGSN Number | 2.4.8.2 | M | - | - | - | P | +| RSZI Lists | 2.4.11.1 | C | - | - | - | P | +| Zone Code List | 2.4.11.2 | - | - | C | - | P | +| RA not allowed flag | 2.4.14a | - | - | M | - | T | +| SGSN area restricted flag | 2.4.14 | M | - | - | - | T | +| Roaming Restricted in the SGSN due to unsupported feature | 2.4.15.3 | M | - | M | - | T | +| Cell Global ID or Service Area ID | 2.4.16 | - | - | C | C | T | +| LSA Identity | 2.4.17.1 | C | C | C | - | P | +| LSA Priority | 2.4.17.2 | C | C | C | - | P | +| LSA Preferential Access Indicator | 2.4.17.2A | C | C | C | - | P | +| LSA Active Mode Support Indicator | 2.4.17.2B | C | C | C | - | P | +| LSA Only Access Indicator | 2.4.17.3 | C | C | C | - | P | +| LSA Active Mode Indicator | 2.4.17.4 | C | C | C | - | P | +| VPLMN Identifier | 2.4.17.5 | C | - | - | - | P | +| Access Restriction Data | 2.4.18 | C | - | C | - | P | +| IP-SM-GW number | 2.4.20 | C | - | - | - | T | +| IP-SM-GW Diameter Identity | 2.4.20A | C | - | - | - | T | +| Closed Subscriber Group Information | 2.4.22 | C | C | C | - | P | +| Service Centre Address | 2.4.23 | C | - | - | - | P | +| Provision of teleservice | 2.5.2 | C | - | C | - | P | +| Transfer of SM option | 2.5.4 | M | - | - | - | P | +| MNRG | 2.7.2 | M | - | M | M | T | +| MM State | 2.7.3 | - | - | M | - | T | +| Subscriber Data Confirmed by HLR Indicator | 2.7.4.2 | - | - | M | - | T | +| Location Info Confirmed by HLR Indicator | 2.7.4.3 | - | - | M | - | T | +| VLR-Reliable Indicator | 2.7.4.5 | - | - | C note1 | - | T | +| MS purged for GPRS flag | 2.7.6 | M | - | - | - | T | +| MNRR-SGSN | 2.7.7A | C | - | - | - | T | +| Subscriber Status | 2.8.1 | C | - | C | - | P | +| Barring of outgoing calls | 2.8.2.1 | C | - | - | - | P | +| Barring of roaming | 2.8.2.3 | C | - | - | - | P | +| Barring of Packet Oriented Services | 2.8.2.8 | C | - | C | - | P | +| ODB PLMN-specific data | 2.8.3 | C | - | C | - | P | +| Notification to CSE flag for ODB | 2.8.4 | C | - | - | - | T | +| gsmSCF address list for ODB | 2.8.5 | C | - | - | - | P | +| Trace Activated in SGSN | 2.11.7 | C | - | C | - | P | +| Trace Reference 2 | 2.11.9 | C | - | C | C | P | +| Trace depth | 2.11.10 | C | - | C | C | P | + +| | | | | | | | +|----------------------------------------------------------------|--------------------|---|---|---------|---|-----| +| List of NE types to trace | 2.11.11 | C | - | C | C | P | +| Triggering events | 2.11.12 | C | - | C | C | P | +| List of interfaces to trace | 2.11.13 | C | - | C | C | P | +| MDT-Configuration | 2.11.15 | C | C | C | - | P | +| PDP Type | 2.13.1 | C | - | C | M | P | +| PDP Address | 2.13.2 | C | - | C | M | P | +| NSAPI | 2.13.3 | - | - | C | C | T | +| PDP State | 2.13.4 | - | - | C | - | T | +| New SGSN Address | 2.13.5 | - | - | C | - | T | +| Access Point Name | 2.13.6 | C | - | C | C | P/T | +| GGSN Address in Use | 2.13.7 | - | - | C | - | T | +| VPLMN Address Allowed | 2.13.8 | C | - | C | - | P | +| Dynamic Address | 2.13.9 | - | - | - | C | T | +| SGSN Address | 2.13.10 | - | - | - | M | T | +| GGSN-list | 2.13.11 | M | - | - | - | T | +| Quality of Service Subscribed | 2.13.12 | C | - | C | - | P | +| Quality of Service Requested | 2.13.13 | - | - | C | - | T | +| Quality of Service Negotiated | 2.13.14 | - | - | C | M | T | +| SND | 2.13.15 | - | - | C | C | T | +| SNU | 2.13.16 | - | - | C | C | T | +| DRX Parameters | 2.13.17 | - | - | M | - | T | +| Compression | 2.13.18 | - | - | C | - | T | +| NGAF | 2.13.19 | - | - | C note2 | - | T | +| Classmark | 2.13.20 | - | - | M | - | T | +| TEID | 2.13.21 | - | - | C | C | T | +| Radio Priority | 2.13.22 | - | - | C | - | T | +| Radio Priority SMS | 2.13.23 | - | - | C | - | T | +| PDP Context Identifier | 2.13.24 | C | - | C | - | T | +| PDP Context Charging Characteristics | 2.13.25 | C | - | C | C | P | +| UE level APN-OI-Replacement | 2.13.29 | C | - | C | - | P | +| Subscribed UE-AMBR | 2.13.30 | C | - | C | - | P | +| Used UE-AMBR | 2.13.30A | - | - | C | - | T | +| Subscribed APN-AMBR | 2.13.32 | C | - | C | C | P | +| Used APN-AMBR | 2.13.32A | - | - | C | C | T | +| Subscribed-RFSP-ID | 2.13.33 | C | - | C | - | P | +| APN Restriction | 2.13.43 | - | - | C | C | P | +| RFSP-ID in Use | 2.13.108 | - | - | C | - | T | +| APN level APN-OI-Replacement | 2.13.109 | C | - | C | - | P | +| SIPTO Permission | 2.13.114 | C | - | C | - | P | +| SIPTO Local Network Permission | 2.13.114A | C | - | C | - | P | +| Subscribed Periodic RAU/TAU Timer | 2.13.115 | C | - | C | - | P | +| LIPA Permission | 2.13.122 | C | - | C | - | P | +| LIPA Allowed VPLMN List | 2.13.123 | C | - | - | - | P | +| VPLMN LIPA Allowed | 2.13.124 | - | - | C | - | P | +| Higher bitrates than 16Mbps flag | 2.13.127 | - | - | C | - | T | +| Co-located GGSN-PGW FQDN | 2.13.136 | - | - | C | - | T | +| GERAN Cell Identity Age | 2.13.137 | - | - | C | - | T | +| UTRAN Service Area Identity Age | 2.13.138 | - | - | C | - | T | +| Homogeneous Support of IMS Voice over PS Sessions | 2.13.141 | C | - | C | - | T | +| Signalling Priority Indication | 2.13.142 | - | - | C | C | T | +| Active Time Value for PSM | 2.13.148 | - | - | C | - | T | +| DL Data Buffer Expiration Time | 2.13.150 | - | - | C | - | T | +| DL Buffering Suggested Packet Count | 2.13.151 | C | - | C | - | P | +| IMSI-Group Identifier List | 2.13.153 | C | - | C | - | P | +| UE Usage Type | 2.13.154 | C | - | C | - | P | +| Extended idle mode DRX parameters | 2.13.157 | - | - | C | - | T | +| Delay Tolerant Connection Indication | 2.13.158 | - | - | C | C | P | +| Pending Network Initiated PDN Connection Signalling Indication | 2.13.159 | - | - | C | - | T | +| User Plane Integrity Protection Indicator | 2.13.163 | C | - | C | - | P | +| IOV_updates counter | 2.13.170 | - | - | C | - | T | +| Dedicated Core Network Identifier | 2.13.172 | - | - | C | - | T | +| GPRS CAMEL Subscription Information (GPRS-CSI) | 2.14.1.10/2.14.4.4 | C | - | C | - | C | + +| | | | | | | | +|---------------------------------------------------------------------|--------------------|---|---|---|---|---| +| MO Short Message Service CAMEL Subscription Information(MO-SMS-CSI) | 2.14.1.8/2.14.4.1 | C | - | C | - | C | +| MT Short Message Service CAMEL Subscription Information(MT-SMS-CSI) | 2.14.1.9/2.14.4.2. | C | - | C | - | C | +| MO-SMS-CSI SGSN Negotiated CAMEL Capability Handling | 2.14.2.1 | C | - | - | - | P | +| MT-SMS-CSI SGSN Negotiated CAMEL Capability Handling | 2.14.2.1 | C | - | - | - | P | +| Mobility Management for GPRS event notification (MG-CSI) | 2.14.1.12/2.14.4.4 | C | - | C | - | C | +| MG-CSI Negotiated CAMEL Capability Handling | 2.14.2.1 | C | - | - | - | P | +| GPRS-CSI Negotiated CAMEL Capability Handling | 2.14.2.1 | C | - | - | - | T | +| SGSN Supported CAMEL Phases | 2.14.2.3 | C | - | - | - | T | +| SGSN Offered CAMEL4 CSIs | 2.14.2.2A | C | - | - | - | T | +| GsmSCF address for CSI | 2.14.2.4 | C | - | - | - | P | +| Age Indicator | 2.16.1 | C | - | C | - | T | +| Privacy Exception List | 2.16.1.1 | C | - | C | - | P | +| GMLC Numbers | 2.16.1.2 | C | - | C | - | P | +| MO-LR List | 2.16.1.3 | C | - | C | - | P | +| Service Types | 2.16.1.4 | C | - | C | - | P | +| Subscribed Charging Characteristics | 2.19.1 | C | - | C | C | P | +| ICS Indicator | 2.20.1 | C | C | C | - | P | +| STN-SR | 2.21.1 | C | - | C | - | T | +| Additional MSISDN | 3.1.16 | C | - | C | - | P | + +The HLR column indicates only GPRS related use, i.e. if the HLR uses a parameter in non-GPRS Network Access Mode but not in GPRS Network Access Mode, it is not mentioned in this table 5.2. + +NOTE 1: This parameter is relevant in the SGSN only when the Gs interface is installed. + +NOTE 2: The VLR column is applicable if Gs interface is installed. It only indicates GPRS related data to be stored and is only relevant to GPRS subscribers registered in VLR. + +For special condition of storage see in clause 2. See clause 4 for explanation of M, C, T and P in table 5.2. + +## 5.2A PS Network Access Mode Storage (EPS) + +**Table 5.2A-1: Overview of data used for PS Network Access Mode (EPS 3GPP access)** + +| PARAMETER | Clause | HSS | VLR
(see
note3) | S4-
SGSN | MME | S-GW | PDN-
GW | TYPE | +|--------------------------------------------------------------|-----------|-----|-----------------------|------------------|-------------------------|------|------------|------| +| IMSI | 2.1.1.1 | M | C | C | C | C | C | P | +| Network Access Mode | 2.1.1.2 | M | - | - | C
(see
note
1) | - | - | P | +| IMSI Unauthenticated indicator | 2.1.1.3 | - | - | C | C | C | C | T | +| International MS ISDN number | 2.1.2 | C | - | C | C | C | C | P | +| P-TMSI | 2.1.5 | - | - | C | - | - | - | T | +| TLLI | 2.1.6 | - | - | C | - | - | - | T | +| Random TLLI | 2.1.7 | - | - | C | - | - | - | T | +| IMEI | 2.1.9 | C | - | C | C | C | C | T | +| External Identifier Set | 2.1.10 | C | - | - | - | - | - | P | +| UE radio capability ID | 2.1.11 | - | - | - | C | - | - | T | +| IMEISV | 2.2.3 | C | - | C | C | C | C | T | +| RAND/SRES and Kc | 2.3.1 | - | - | C | - | - | - | T | +| RAND, XRES, CK, IK, AUTN | 2.3.2 | M | - | C | C | - | - | T | +| RAND, XRES, KASME, AUTN | 2.3.2 | M | - | - | C | - | - | T | +| Ciphering Key Sequence Number | 2.3.3 | C | - | M | - | - | - | T | +| Key Set Identifier (KSI) | 2.3.4 | - | - | M | - | - | - | T | +| KSI ASME | 2.3.4 | - | - | - | M | - | - | T | +| Selected Ciphering Algorithm | 2.3.5 | - | - | M | - | - | - | T | +| Current Kc | 2.3.6 | - | - | M | - | - | - | T | +| P-TMSI Signature | 2.3.7 | - | - | C | - | - | - | T | +| Key Status | 2.3.9 | - | - | C | - | - | - | T | +| Routing Area Identity | 2.4.3 | - | - | M | - | - | - | T | +| IWF number | 2.4.8.3 | C | - | - | - | - | - | T | +| RSZI Lists | 2.4.11.1 | C | - | - | - | - | - | P | +| Zone Code List | 2.4.11.2 | - | - | C | C | - | - | P | +| SGSN area restricted Flag | 2.4.14 | M | - | - | - | - | - | T | +| RA not allowed flag | 2.4.14a | - | - | M | - | - | - | T | +| TA not allowed flag | 2.4.14b | - | - | - | M | - | - | T | +| Roaming Restricted in the SGSN
due to unsupported feature | 2.4.15.3 | M | - | M | - | - | - | T | +| Roaming Restricted in the MME
due to unsupported feature | 2.4.15.3a | M | - | - | M | - | - | T | +| Cell Global Identity or Service
Area ID | 2.4.16 | - | - | C | C | - | C | T | +| E-UTRAN Cell Global ID | 2.4.16A | - | C (see
note 2) | - | C | - | C | T | +| Access Restriction Data | 2.4.18 | C | - | C | C | - | - | P | +| Closed Subscriber Group
Information | 2.4.22 | C | C | C | C | - | - | P | +| IAB-Operation Allowed | 2.4.27 | C | - | - | C | - | - | P | +| Confirmed by Radio Contact
indicator | 2.7.4.1 | - | C | - | - | - | - | T | +| Subscriber Data Confirmed by
HLR/HSS Indicator | 2.7.4.2 | - | - | M | M | - | - | T | +| Location Info Confirmed by
HLR/HSS Indicator | 2.7.4.3 | - | - | M | M | - | - | T | +| VLR-Reliable Indicator | 2.7.4.5 | - | - | C(see
note 5) | C
(see
note
2) | - | - | T | +| UE purged in SGSN flag | 2.7.6 | M | - | - | - | - | - | T | +| UE purged in MME flag | 2.7.6A | M | - | - | - | - | - | T | +| URRP-MME | 2.7.9.1 | C | - | - | C | - | - | T | +| URRP-SGSN | 2.7.9.2 | C | - | C | - | - | - | T | +| Subscriber Status | 2.8.1 | C | - | C | C | - | - | P | +| Barring of outgoing calls | 2.8.2.1 | C | - | C | - | - | - | P | +| Barring of roaming | 2.8.2.3 | C | - | - | - | - | - | P | +| Barring of Packet Oriented
Services | 2.8.2.8 | C | - | C | C | - | - | P | +| ODB PLMN-specific data | 2.8.3 | C | - | C | - | - | - | P | + +| PARAMETER | Clause | HSS | VLR
(see note3) | S4-SGSN | MME | S-GW | PDN-GW | TYPE | +|---------------------------------------|----------|-----|--------------------|-------------------|-------------------|------|--------|--------------------| +| PS and SMS Only | 2.10.7 | C | - | C | - | - | - | P | +| SMS in SGSN Allowed | 2.10.8 | C | - | C | - | - | - | P | +| Trace Activated in SGSN | 2.11.7 | C | - | C | - | - | - | P | +| Trace Reference 2 | 2.11.9 | C | C | C | C | C | C | P | +| Trace depth | 2.11.10 | C | C | C | C | C | C | P | +| List of NE types to trace | 2.11.11 | C | C | C | C | - | - | P | +| Triggering events | 2.11.12 | C | C | C | C | C | C | P | +| List of interfaces to trace | 2.11.13 | C | C | C | C | C | C | P | +| IP address of trace collection entity | 2.11.14 | C | C | C | C | C | C | P | +| MDT-Configuration | 2.11.15 | C | C | C | C | - | - | P | +| MDT User Consent | 2.11.16 | C | C | C | C | - | - | P | +| Access Point Name (APN). | 2.13.6 | M | - | M | M | M | M | P | +| MME name | 2.13.26 | M | C | - | - | - | - | T | +| VLR name | 2.13.27 | - | - | - | C
(see note 2) | - | - | T | +| NEAF | 2.13.28 | - | - | - | C
(see note 2) | - | - | T | +| UE level APN-OI-Replacement | 2.13.29 | C | - | - | C | - | - | P | +| Subscribed UE-AMBR | 2.13.30 | M | - | M | M | - | - | P | +| Used UE-AMBR | 2.13.30A | - | - | C | C | - | - | T | +| APN-Configuration-Profile | 2.13.31 | M | - | M | M | - | - | P | +| Subscribed APN-AMBR | 2.13.32 | M | - | M | M | M | - | P | +| Used APN-AMBR | 2.13.32A | - | - | C | C | - | C | T | +| Subscribed-RFSP-ID | 2.13.33 | C | - | - | C | - | - | P | +| GUTI | 2.13.34 | - | - | - | C | - | - | T | +| ME identity (IMEISV) | 2.13.35 | C | - | C | C | C | C | T | +| Selected NAS Algorithm | 2.13.36 | - | - | - | M | - | - | T | +| Selected AS Algorithm | 2.13.37 | - | - | - | M | - | - | T | +| Context Identifier | 2.13.38 | M | - | M | M | M | M | P | +| PDN Address | 2.13.39 | C | - | C | C | C | C | P/T
(see note4) | +| VPLMN Address Allowed | 2.13.40 | M | - | M | M | - | - | P | +| PDN GW identity | 2.13.41 | C | - | C
(see note 6) | C
(see note 6) | - | - | P/T
(see note4) | +| Tracking Area List | 2.13.42 | - | - | - | M | - | - | T | +| APN Restriction | 2.13.43 | - | - | C | C | C | C | P | +| APN in use | 2.13.44 | - | - | M | M | M | M | T | +| TAI | 2.13.45 | - | C (see note 2) | - | M | - | - | T | +| E-UTRAN Cell Identity Age | 2.13.46 | - | C (see note 2) | - | C | - | - | T | +| MME F-TEID for S11 (control plane) | 2.13.47 | - | - | - | C | C | - | T | +| MME UE S1AP ID | 2.13.48 | - | - | - | C | - | - | T | +| S-GW F-TEID for S11 (control plane) | 2.13.49 | - | - | - | C | C | - | T | +| S4-SGSN F-TEID for S4 (control plane) | 2.13.50 | - | - | C | - | - | - | T | +| S4-SGSN F-TEID for S4 (User plane) | 2.13.51 | - | - | C | - | - | - | T | +| S-GW F-TEID for S5/S8 (control plane) | 2.13.52 | - | - | - | C | C | C | T | +| S-GW F-TEID for S1-U | 2.13.53 | - | - | - | C | C | - | T | +| S-GW F-TEID for S5/S8 (user plane) | 2.13.54 | - | - | - | - | C | C | T | + +| PARAMETER | Clause | HSS | VLR
(see
note3) | S4-
SGSN | MME | S-GW | PDN-
GW | TYPE | +|---------------------------------------------------|-----------|-----|-----------------------|----------------------|----------------------|------|------------|------| +| eNodeB Address | 2.13.55 | - | - | - | C | - | - | T | +| eNodeB UE S1AP ID | 2.13.56 | - | - | - | C | - | - | T | +| eNodeB F-TEID for S1-U | 2.13.57 | - | - | - | C | C | - | T | +| E-UTRAN/UTRAN Key Set flag | 2.13.58 | - | - | - | C | - | - | T | +| Selected CN operator id | 2.13.59 | - | - | - | C | - | - | T | +| UE Radio Access Capability | 2.13.60 | - | - | - | C | - | - | T | +| Location Change Report Required | 2.13.62 | - | - | C | C | - | - | T | +| UE specific DRX parameters | 2.13.63 | - | - | - | C | - | - | T | +| PDN GW F-TEID for S5/S8
(user plane) | 2.13.64 | - | - | C | C | C | C | T | +| PDN GW F-TEID for S5/S8
(control plane) | 2.13.65 | - | - | C | C | C | C | T | +| EPS Bearer ID | 2.13.66 | - | - | C | C | C | C | T | +| EPS Bearer QoS | 2.13.67 | - | - | C | C | C | C | T | +| EPS Subscribed QoS Profile | 2.13.67A | M | - | M | M | - | - | P | +| UL TFT | 2.13.68 | - | - | - | C | C | C | T | +| DL TFT | 2.13.69 | - | - | - | C | C | C | T | +| Charging Id | 2.13.70 | - | - | C | - | C | C | T | +| EPS PDN Connection Charging
Characteristics | 2.13.71 | C | - | C | C | C | C | P | +| Default bearer | 2.13.72 | - | - | - | C | C | C | T | +| URRP-MME | 2.13.73 | C | - | - | C | - | - | T | +| RAT Type (Access Type) | 2.13.75 | C | - | C | C | C | C | T | +| Diameter Server Identity of the
HSS | 2.13.99 | - | - | C | C | - | - | T | +| SGSN name | 2.13.100 | M | - | - | - | - | - | T | +| S-GW F-TEID for S12 | 2.13.101 | - | - | - | - | C | - | T | +| RNC F-TEID for S12 | 2.13.102 | - | - | C | - | C | - | T | +| MME F-TEID for S3 | 2.13.103 | - | - | C | C | - | - | T | +| S4-SGSN F-TEID for S3 | 2.13.104 | - | - | C | C | - | - | T | +| PDN GW Allocation Type | 2.13.105 | M | - | - | M | - | - | P | +| S-GW F-TEID for S4 (control
plane) | 2.13.106 | - | - | C | - | C | - | T | +| S-GW F-TEID for S4 (user plane) | 2.13.107 | - | - | C | - | C | - | T | +| RFSP-ID in Use | 2.13.108 | - | - | C | C | - | - | T | +| APN level APN-OI-Replacement | 2.13.109 | C | - | C | C | - | - | P | +| PDN Connection ID | 2.13.111 | - | - | - | - | C | C | T | +| MS Network Capability | 2.13.112 | - | - | C | C | - | - | T | +| Voice Domain Preference and
UE's Usage Setting | 2.13.113 | - | - | C | C | - | - | T | +| SIPTO Permission | 2.13.114 | C | - | C | C | - | - | P | +| SIPTO Local Network Permission | 2.13.114A | C | - | C | C | - | - | P | +| Subscribed Periodic RAU/TAU
Timer | 2.13.115 | C | - | C | C | - | - | P | +| MPS CS Priority | 2.13.120 | - | - | - | C | - | - | P | +| MPS EPS Priority | 2.13.121 | C | - | - | C | - | - | P | +| LIPA Permission | 2.13.122 | C | - | C | C | - | - | P | +| LIPA Allowed VPLMN List | 2.13.123 | C | - | - | - | - | - | P | +| VPLMN LIPA Allowed | 2.13.124 | - | - | C | C | - | - | P | +| Relay Node Indicator | 2.13.125 | C | - | - | C | - | - | P | +| Higher bitrates than 16Mbps flag | 2.13.127 | - | - | C | - | - | - | T | +| H(e)NB Local IP Address | 2.13.131 | - | - | C | C | - | C | T | +| H(e)NB UDP Port Number | 2.13.132 | - | - | C | C | - | C | T | +| MME/S4 SGSN Identifier | 2.13.134 | - | - | - | - | C | C | T | +| SGW node name | 2.13.135 | - | - | C | C | - | - | T | +| Co-located GGSN-PGW FQDN | 2.13.136 | - | - | C
(see
note 6) | C
(see
note 6) | - | - | T | +| GERAN Cell Identity Age | 2.13.137 | - | - | C | - | - | - | T | +| UTRAN Service Area Identity Age | 2.13.138 | - | - | C | - | - | - | T | + +| PARAMETER | Clause | HSS | VLR
(see
note3) | S4-
SGSN | MME | S-GW | PDN-
GW | TYPE | +|----------------------------------------------------------------|-------------|-----|-----------------------|-------------|-----|------|------------|------------------------| +| Homogeneous Support of IMS Voice over PS Sessions | 2.13.14.1 | C | - | C | C | - | - | T | +| Signalling Priority Indication | 2.13.14.2 | - | - | C | C | C | C | T | +| Restoration Priority | 2.13.14.3 | C | - | C | C | - | - | P | +| Presence Reporting Area Action | 2.13.14.5 | - | - | C | C | - | C | T | +| WLAN offloadability | 2.13.14.6 | C | - | C | C | - | - | P | +| Expected UE Activity Behaviour | 2.13.14.7.2 | - | - | - | C | - | - | T | +| Expected HO Interval | 2.13.14.7.3 | - | - | - | C | - | - | T | +| Active Time Value for PSM | 2.13.14.8 | - | - | C | C | - | - | T | +| Origination Time Stamp | 2.13.14.9 | - | - | - | - | - | C | T | +| DL Data Buffer Expiration Time | 2.13.15.0 | - | - | C | C | C | - | T | +| DL Buffering Suggested Packet Count | 2.13.15.1 | C | - | C | C | - | - | P | +| Notify-on-available-after-DDN-failure flag | 2.13.15.2 | - | - | C | C | - | - | T | +| IMSI-Group Identifier List | 2.13.15.3 | C | - | C | C | - | - | P | +| UE Usage Type | 2.13.15.4 | C | - | C | C | - | - | P | +| Remote UE Contexts | 2.13.15.6 | - | - | - | C | C | C | T | +| Extended idle mode DRX parameters | 2.13.15.7 | C | - | C | C | - | - | P/T
(see
note 7) | +| Delay Tolerant Connection Indication | 2.13.15.8 | - | - | C | C | - | C | P | +| Pending Network Initiated PDN Connection Signalling Indication | 2.13.15.9 | - | - | C | C | - | - | T | +| UE Radio Capability for Paging information | 2.13.16.0 | - | - | - | C | - | - | T | +| Information on Recommended Cells and ENBs for Paging | 2.13.16.1 | - | - | - | C | - | - | T | +| Paging Attempt Count | 2.13.16.2 | - | - | - | C | - | - | T | +| User Plane Integrity Protection Indicator | 2.13.16.3 | C | - | C | - | - | - | P | +| Non-IP-PDN-Type-Indicator | 2.13.16.4 | C | - | - | C | - | - | P | +| Non-IP-Data-Delivery-Mechanism | 2.13.16.5 | C | - | - | C | - | - | P | +| SCEF-ID | 2.13.16.6 | C | - | - | C | - | - | P | +| PDN Type | 2.13.16.7 | C | - | C | C | C | C | P | +| PDN-Connection-Restricted flag | 2.13.16.8 | C | - | - | C | - | - | P | +| Preferred-Data-Mode | 2.13.16.9 | C | - | - | C | - | - | P | +| IOV_updates counter | 2.13.17.0 | - | - | C | - | - | - | T | +| Dedicated Core Network Identifier | 2.13.17.2 | - | - | C | C | - | - | T | +| Service Gap Time | 2.13.17.4 | C | - | - | C | - | - | P | +| Subscribed Additional RRM Policy Index | 2.13.17.5 | C | - | - | C | - | - | P | +| Additional RRM Policy Index in use | 2.13.17.6 | - | - | - | C | - | - | T | +| Ethernet-PDN-Type-Indicator | 2.13.17.7 | C | - | - | C | - | - | P | +| Privacy Exception List | 2.16.1.1 | C | - | C | - | - | - | P | +| GMLC Numbers | 2.16.1.2 | C | - | C | - | - | - | P | +| MO-LR List | 2.16.1.3 | C | - | C | - | - | - | P | +| Service Types | 2.16.1.4 | C | - | C | - | - | - | P | +| Broadcast Location Assistance Data Types | 2.16.7.1 | C | - | - | C | - | - | P | +| Subscribed Charging Characteristics | 2.19.1 | C | - | C | C | - | - | P | +| ICS Indicator | 2.20.1 | C | C | C | C | - | - | P | +| STN-SR | 2.21.1 | C | - | C | C | - | - | T | +| UE SRVCC Capability | 2.21.2 | C | - | C | C | - | - | T | +| Subscribed vSRVCC | 2.21.3 | C | - | - | C | - | - | P | +| Additional MSISDN | 3.1.16 | C | - | C | C | - | - | P | + +NOTE 1: This parameter is relevant in the MME only when the SGs interface is installed. + +NOTE 2: Only is applicable if SGs interface is installed. It only indicates EPS related data to be stored and is only relevant to EPS subscribers registered in VLR. + +NOTE 3: The VLR column is applicable if SGs/Sv interface is installed. It only indicates EPS related + +| PARAMETER | Clause | HSS | VLR
(see
note3) | S4-
SGSN | MME | S-GW | PDN-
GW | TYPE | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----------------------|-------------|-----|------|------------|------| +| | data to be stored and is only relevant to EPS subscribers registered in VLR. | | | | | | | | +| NOTE 4: | If Static IP address allocation provisioned in the subscriber profile in the HSS is chosen, PDN address is permanent data. | | | | | | | | +| NOTE 5: | Only is applicable if Gs interface is installed. It only indicates EPS related data to be stored and is only relevant to EPS subscribers registered in VLR. | | | | | | | | +| NOTE 6: | The MME/S4 SGSN stores either the PDN GW identity or the Co-located GGSN-PGW FQDN since they are identical information. | | | | | | | | +| NOTE 7: | The eDRX cycle length may be stored in HSS as a subscribed parameter, and in that case, it is permanent data. | | | | | | | | + +For special condition of storage see in clause 2. See clause 4 for explanation of M, C, T and P in table 5.2A-1. + +**Table 5.2A-2: Overview of data used for PS Network Access Mode (EPS non 3GPP access)** + +| PARAMETER | Clause | HSS | MME | S-GW | PDN-GW | ePDG | 3GPP AAA server | 3GPP AAA server Proxy | TYPE | +|---------------------------------------------|----------|-----|-----|------|--------|------|-----------------|-----------------------|----------------| +| IMSI | 2.1.1.1 | M | C | C | C | C | - | - | P | +| IMSI Unauthenticated indicator | 2.1.1.3 | - | C | C | C | C | - | - | T | +| International MS ISDN number | 2.1.2 | C | C | C | C | C | C | - | P | +| IMEI | 2.1.9 | C | - | - | C | C | C | - | T | +| RAND, XRES, CK, IK, AUTN | 2.3.2 | M | - | - | - | - | M | - | T | +| RAND, XRES, KASME, AUTN | 2.3.2 | M | - | - | - | - | M | - | T | +| Access Network Identity | 2.3.8 | C | - | - | - | - | C | - | T | +| Trace Reference 2 | 2.11.9 | C | - | - | C | - | C | - | P | +| Trace depth | 2.11.10 | C | - | - | C | - | C | - | P | +| List of NE types to trace | 2.11.11 | C | - | - | - | - | C | - | P | +| Triggering events | 2.11.12 | C | - | - | C | - | C | - | P | +| List of interfaces to trace | 2.11.13 | C | - | - | C | - | C | - | P | +| IP address of Trace Collection Entity | 2.11.14 | C | - | - | C | - | C | - | P | +| APN-Configuration-Profile | 2.13.31 | M | - | - | C | C | C | - | T | +| Subscribed APN-AMBR | 2.13.32 | M | - | - | C | C | C | - | P | +| Used APN-AMBR | 2.13.32A | - | - | - | C | - | - | - | T | +| ME Identity (IMEISV) | 2.13.35 | C | - | - | C | C | C | - | T | +| PDN Address | 2.13.39 | C | - | C | C | C | C | - | T/P (see Note) | +| VPLMN Address Allowed | 2.13.40 | M | C | - | - | C | C | - | P | +| PDN GW identity | 2.13.41 | M | C | - | - | C | C | - | P | +| APN in use | 2.13.44 | - | - | - | C | C | - | - | T | +| EPS Bearer ID | 2.13.66 | - | - | - | C | C | - | - | T | +| EPS Bearer QoS | 2.13.67 | - | - | - | C | C | - | - | T | +| EPS PDN Connection Charging Characteristics | 2.13.71 | C | - | - | C | C | C | - | P | +| RAT Type (Access Type) | 2.13.75 | C | - | C | C | C | C | - | T | +| Permanent User Identity | 2.13.79 | M | - | M | M | M | M | - | P | +| Mobility Capabilities | 2.13.80 | - | - | - | M | C | C | - | T | +| MAG IP address | 2.13.81 | - | - | - | - | - | C | - | T | +| Visited Network Identifier | 2.13.82 | C | - | - | C | C | C | - | T | +| EAP payload | 2.13.83 | - | - | - | - | - | C | - | P | +| MIP Subscriber profile | 2.13.86 | M | - | - | M | - | - | - | P | +| Uplink S5 GRE Key | 2.13.87 | - | C | C | C | - | - | - | T | +| Downlink S5 GRE Key | 2.13.88 | - | - | C | C | - | - | - | T | +| Uplink S8 GRE Key | 2.13.89 | - | C | C | C | - | - | - | T | +| Downlink S8 GRE Key | 2.13.90 | - | - | C | C | - | - | - | T | +| S2a GRE Keys | 2.13.91 | - | - | C | C | - | - | - | T | +| S2b GRE Keys | 2.13.92 | - | - | C | C | C | - | - | T | +| Mobile Node Identifier | 2.13.93 | - | - | C | C | - | - | - | T | +| IPv4 Default Router Address | 2.13.94 | - | - | C | C | - | - | - | T | +| Link-local address | 2.13.95 | - | - | C | C | - | - | - | T | +| Non 3GPP User Data | 2.13.96 | C | - | - | - | C | C | - | | +| 3GPP AAA Server Identity | 2.13.97 | C | - | - | C | C | - | - | T | +| Selected IP mobility mode | 2.13.98 | - | - | - | C | C | C | - | T | +| Diameter Server Identity of HSS | 2.13.99 | - | C | - | - | - | C | - | T | +| Unauthenticated IMSI | 2.13.110 | - | - | C | C | - | - | - | T | +| PDN Connection ID | 2.13.111 | - | - | C | C | C | - | - | T | +| SIPTO Permission | 2.13.114 | C | - | - | - | - | C | - | P | +| ePDG F-TEID for S2b (control plane) | 2.13.116 | - | - | - | C | C | - | - | T | +| ePDG F-TEID for S2b (user plane) | 2.13.117 | - | - | - | C | C | - | - | T | +| PGW F-TEID for S2b (control plane) | 2.13.118 | - | - | - | C | C | - | - | T | +| PGW F-TEID for S2b (user plane) | 2.13.119 | - | - | - | C | C | - | - | T | +| Restricted RAT Types | 2.13.126 | C | - | - | - | - | C | - | P | +| UE Local IP Address | 2.13.129 | - | - | - | - | C | - | - | T | +| UE UDP Port Number | 2.13.130 | - | - | - | - | C | - | - | T | +| Default APN for Trusted WLAN | 2.13.139 | C | - | - | - | - | C | - | P | + +| PARAMETER | Clause | HSS | MME | S-GW | PDN-GW | ePDG | 3GPP AAA server | 3GPP AAA server Proxy | TYPE | +|-------------------------------------|----------|-----|-----|------|--------|------|-----------------|-----------------------|------| +| Access Information for Trusted WLAN | 2.13.140 | C | - | - | - | - | C | - | P | +| Origination Time Stamp | 2.13.149 | - | - | - | C | - | C | - | T | +| Emergency Indication | 2.13.155 | - | - | - | - | C | C | C | T | +| Emergency Info | 2.13.171 | C | C | - | - | C | C | - | T | +| Subscribed Charging Characteristics | 2.19.1 | M | - | - | - | C | C | - | P | +| ERP-Authorization | 2.24.2 | C | - | - | - | - | C | - | P | +| ERP Keying Material | 2.24.3 | - | - | - | - | - | C | C | T | +| ERP-Realm | 2.24.4 | - | - | - | - | - | C | C | P | +| Master session Key | 3.11.3.5 | - | - | - | C | C | C | - | T | + +NOTE: If Static IP address allocation provisioned in the subscriber profile in the HSS is chosen, PDN address is permanent data. + +For special condition of storage see in clause 2. See clause 4 for explanation of M, C, T and P in table 5.2A-2. + +Table 5.2.A-3 contains additional parameter to be hold when optimised handover to 3GPP2 is supported. + +**Table 5.2A-3: Overview of data used for PS Network Access Mode (optimized handover to 3GPP2)** + +| PARAMETER | Clause | HSS | MME | S-GW | PDN-GW | ePDG | 3GPP AAA server | 3GPP AAA server Proxy | TYPE | +|-------------------------------------|---------|-----|-----|------|--------|------|-----------------|-----------------------|------| +| Access Restriction Data | 2.4.18 | C | C | - | - | - | - | - | P | +| Barring of Packet Oriented Services | 2.8.2.8 | C | C | - | - | - | - | - | P | +| RAT Type | 2.13.75 | C | - | - | - | - | - | - | T | +| S101 HRPD access node IP address | 2.13.76 | - | C | - | - | - | - | - | T | +| S103 Forwarding Address | 2.13.77 | - | C | C | - | - | - | - | T | +| S103 GRE key(s) | 2.13.78 | - | C | C | - | - | - | - | T | + +NOTE: A UE may be simultaneously attached to EPS and have simultaneously active PDN connections or IP flows via different access systems (3GPP access and a non 3GPP access). + +## 5.2B PS Network Access Mode Data (5GS) + +**Table 5.2B-1: Overview of data used for PS Network Access Mode (5GS)** + +| PARAMETER | Clause | UDM | AMF | SMF | SMSF | AUSF | NEF | | TYPE | +|------------------------------------------------------|----------|-----|-----|-----|------|------|-----|---|------| +| Subscribed UE-AMBR | 2.13.30 | C | C | - | - | - | - | - | P | +| TAI | 2.13.45 | - | C | C | - | - | - | - | T | +| Restricted RAT Types | 2.13.126 | C | C | - | - | - | - | - | P | +| IMSI Group Identifier List | 2.13.153 | C | C | - | - | - | - | - | P | +| UE Usage Type | 2.13.154 | C | C | - | - | - | - | - | P | +| STN-SR | 2.21.1 | C | C | - | - | - | - | - | T | +| UE 5G SRVCC Capability | 2.21.2 | C | C | - | - | - | - | - | T | +| SUPI | 2.25.1 | M | C | C | C | - | C | - | P | +| GPSI | 2.25.2 | M | C | C | - | - | C | - | P | +| Internal Group ID-list | 2.25.3 | C | C | C | - | - | - | - | P | +| Subscribed S-NSSAI | 2.25.4 | C | C | C | - | - | - | - | P | +| Default S-NSSAI | 2.25.5 | C | C | - | - | - | - | - | P | +| 5G QOS Parameter | 2.25.6 | C | - | C | - | - | - | - | P | +| Forbidden Area | 2.25.7 | C | C | - | - | - | - | - | P | +| Service Area Restriction | 2.25.8 | C | C | - | - | - | - | - | P | +| RFSP Index | 2.25.9 | C | C | - | - | - | - | - | P | +| Priority Service | 2.25.10 | C | C | - | - | - | - | - | P | +| DNN Info | 2.25.11 | C | - | C | - | - | - | - | P | +| DNN Configuration | 2.25.12 | C | - | C | - | - | - | - | P | +| Steering of Roaming Information | 2.25.13 | C | C | - | - | C | - | - | T | +| SMS supported Data | 2.25.14 | C | C | - | C | - | - | - | T | +| SMSF Registrations | 2.25.15 | C | C | - | M | - | - | - | P | +| SMS subscribed | 2.25.16 | M | - | - | C | - | - | - | P | +| SMS barring | 2.25.17 | M | - | - | C | - | - | - | P | +| SMS Roaming | 2.25.18 | C | C | - | C | - | - | - | P | +| Core Network Type Restriction | 2.25.19 | C | C | - | - | - | - | - | P | +| LADN Information | 2.25.20 | C | C | - | - | - | - | - | P | +| Subscribed periodic Registration timer | 2.25.21 | C | C | - | - | - | - | - | P | +| PEI | 2.25.22 | C | C | C | - | - | - | - | T | +| 5G GUTI | 2.25.23 | - | C | - | - | - | - | - | T | +| PLMN ID | 2.25.24 | C | C | C | C | - | - | - | P | +| PDU session | 2.25.25 | C | C | C | - | - | - | - | T | +| Trace Data | 2.25.26 | C | C | C | - | - | - | - | P | +| Mobile Initiated Connection Only (MICO) mode | 2.25.27 | C | C | - | - | - | - | - | P | +| UE purged in AMF flag | 2.25.28 | M | - | - | - | - | - | - | T | +| GUAMI | 2.25.29 | C | C | C | - | - | - | - | T | +| RAND, AUTN, XRES, CK', IK' | 2.25.30 | - | - | - | - | - | - | - | T | +| RAND, AUTN, XRES* | 2.25.31 | - | - | - | - | - | - | - | T | +| RAND, AUTN, HXRES* | 2.25.32 | - | - | - | - | - | - | - | T | +| Kausf | 2.25.33 | - | - | - | - | C | - | - | T | +| Kseaf | 2.25.34 | - | M | - | - | - | - | - | T | +| AuthenticationMethod | 2.25.35 | M | - | - | - | - | - | - | P | +| PermanentKey | 2.25.36 | C | - | - | - | - | - | - | P | +| SequenceNumber | 2.25.37 | C | - | - | - | - | - | - | T | +| AuthenticationManagementField | 2.25.38 | C | - | - | - | - | - | - | P | +| VectorAlgorithm | 2.25.39 | C | - | - | - | - | - | - | P | +| Milenage | 2.25.40 | C | - | - | - | - | - | - | P | +| Tuak | 2.25.41 | C | - | - | - | - | - | - | P | +| Opc | 2.25.42 | C | - | - | - | - | - | - | P | +| Topc | 2.25.43 | C | - | - | - | - | - | - | P | +| Authentication Status | 2.25.44 | C | - | - | - | - | - | - | T | +| SoR-XMAC-I UE | 2.25.45 | C | - | - | - | - | - | - | T | +| Shared Data Ids | 2.25.46 | C | C | C | C | - | - | - | P | +| Access Restriction Data | 2.25.47 | C | C | - | - | - | - | - | P | +| IAB-Operation Allowed | 2.25.48 | C | C | - | - | - | - | - | P | +| UE radio capability ID | 2.25.49 | - | C | - | - | - | - | - | T | +| RG Level Wireline Access Characteristics | 2.25.50 | C | C | - | - | - | - | - | P | +| RG-TMBR | 2.25.51 | C | C | - | - | - | - | - | P | +| List of 5GS Broadcast Location Assistance Data Types | 2.25.52 | C | C | - | - | - | - | - | P | + +NOTE: Where the node physically stores data and/or from where it retrieves data for usage (e.g. interactions with the UDR) are not reflected in this table. + +## 5.3 IP Multimedia Service Data Storage + +**Table 5.3: Overview of IMS subscriber data used for IP Multimedia services** + +| PARAMETER | Clause | HSS | S-CSCF | IM-SSF | AS | TYPE | +|------------------------------------------------------|---------|----------|--------|--------|----|------| +| Service Centre Address | 2.4.23 | C | - | - | C | P | +| Private User Identity | 3.1.1 | M | M | - | - | P | +| Public User Identity | 3.1.2 | M | M | - | - | P | +| Barring Indication | 3.1.3 | M | M | - | - | P | +| List of authorized visited network identifiers | 3.1.4 | M | - | - | - | P | +| Services related to Unregistered State | 3.1.5 | M | - | - | - | P | +| Implicitly registered Public User Identity sets | 3.1.6 | C | C | - | - | P | +| Default Public User Identity indicator | 3.1.7 | C | - | - | - | P | +| Display Name | 3.1.9 | C | C | - | - | P | +| Alias Public User Identities Set | 3.1.10 | C | C | - | - | P | +| Loose-Route Indication | 3.1.11 | C | C | - | - | P | +| Service Priority Level | 3.1.12 | C | C | - | - | P | +| Extended Priority | 3.1.13 | C | C | - | - | P | +| Reference Location Information | 3.1.14 | C | C | - | - | P | +| Privileged-Sender Indication | 3.1.15 | C | C | - | - | P | +| Additional MSISDN | 3.1.16 | C | - | - | C | P | +| Registration Status | 3.2.1 | M | - | - | - | T | +| S-CSCF Name | 3.2.2 | M | - | - | - | T | +| Diameter Client Identity of S-CSCF | 3.2.3 | M | - | - | - | T | +| Diameter Server Identity of HSS | 3.2.4 | - | M | - | C | T | +| UNRI | 3.2.5 | C | - | - | C | T | +| UNRR | 3.2.6 | C | - | - | - | T | +| S-CSCF Restoration Information | 3.2.7 | C | C | - | - | T | +| Maximum Number Of Allowed Simultaneous Registrations | 3.2.8 | C | C | - | - | P | +| RAND, XRES, CK, IK and AUTN | 3.3.1 | M | C | - | - | T | +| Digest Nonce | 3.3.2.1 | - | C | - | - | T | +| Digest HA1 | 3.3.2.2 | C | C | - | - | P | +| Digest Nextnonce | 3.3.2.3 | - | C | - | - | T | +| Authentication Pending Flag | 3.3.2.5 | C | - | - | - | T | +| Line Identifier List | 3.3.3.1 | C | C | - | - | P | +| Server Capabilities | 3.4.1 | C | - | - | - | P | +| S-CSCF Reassignment Pending Flag | 3.4.2 | C | - | - | - | T | +| Initial Filter Criteria | 3.5.2 | C | C | - | - | P | +| Application Server Information | 3.5.3 | C | C | - | - | P | +| Service Indication | 3.5.4 | M | - | - | M | P | +| Shared iFC Set Identifier | 3.5.5 | C | C | - | - | P | +| Transparent Data | 3.5.6 | C | - | - | C | T | +| Application Server Identity List | 3.5.7 | C | - | - | - | T | +| Subscribed Media Profile Identifier | 3.6.1 | C | C | - | - | P | +| List of Subscribed Communication Service Identifiers | 3.6.2 | M | C | - | C | P | +| Primary Event Charging Function Name | 3.7.1 | C Note 1 | C | - | - | P | +| Secondary Event Charging Function Name | 3.7.2 | C | C | - | - | P | +| Primary Charging Collection Function Name | 3.7.3 | C Note 1 | C | - | - | P | +| Secondary Charging Collection Function Name | 3.7.4 | C | C | - | - | P | +| O-IM-CSI | 3.8.1 | C | - | C | - | P | +| VT-IM-CSI | 3.8.2 | C | - | C | - | P | +| D-IM-CSI | 3.8.3 | C | - | C | - | P | +| GsmSCF address for IM CSI | 3.8.4 | C | - | - | - | P | +| IM-SSF address for IM CSI | 3.8.5 | C | - | - | - | T | +| IMS Service Level Trace Information | 3.9.1 | C | C | - | C | T | +| Allowed WAF and/or WWSF Identity List | 3.15.1 | C | C | - | - | P | + +Note 1: At least one of these Primary Charging Function Names shall be mandatorily provisioned in the HSS. + +**Table 5.3A: Overview of PSI user data used for IP Multimedia services** + +| PARAMETER | Clause | HSS | S-CSCF | IM-SSF | AS | TYPE | +|---------------------------------------------|--------|----------|--------|--------|----|------| +| Private Service Identity | 3.1.2A | M | M | - | - | P | +| Public Service Identity | 3.1.2B | M | M | - | M | P | +| Services related to Unregistered State | 3.1.5 | M | - | - | - | P | +| PSI Activation State | 3.1.8 | M | - | - | M | T | +| Display Name | 3.1.9 | C | C | - | - | P | +| Registration Status | 3.2.1 | M | - | - | - | T | +| S-CSCF Name | 3.2.2 | C | - | - | - | T | +| AS Name | 3.2.2A | C | - | - | - | P | +| Diameter Client Identity of S-CSCF | 3.2.3 | M | - | - | - | T | +| Diameter Server Identity of HSS | 3.2.4 | - | M | - | C | T | +| Server Capabilities | 3.4.1 | C | - | - | - | P | +| Initial Filter Criteria | 3.5.2 | C | C | - | - | P | +| Application Server Information | 3.5.3 | C | C | - | - | P | +| Service Indication | 3.5.4 | M | - | - | M | P | +| Shared iFC Set Identifier | 3.5.5 | C | C | - | - | P | +| Transparent Data | 3.5.6 | C | - | - | C | T | +| Subscribed Media Profile Identifier | 3.6.1 | C | C | - | - | P | +| Primary Event Charging Function Name | 3.7.1 | C Note 1 | C | - | - | P | +| Secondary Event Charging Function Name | 3.7.2 | C | C | - | - | P | +| Primary Charging Collection Function Name | 3.7.3 | C Note 1 | C | - | - | P | +| Secondary Charging Collection Function Name | 3.7.4 | C | C | - | - | P | + +Note 1: At least one of these Primary Charging Function Names shall be mandatorily provisioned in the HSS. + +## 5.4 Generic Authentication Architecture Service Data Storage + +**Table 5.4: Overview of data used for GAA services** + +| PARAMETER | Clause | HSS | BSF | NAF | TYPE | +|--------------------------------------|---------|-----|-----|-----|------| +| Private User Identity | 3.1.1 | M | M | C | P | +| GAA Service Type | 3.10.1 | M | M | M | P | +| GAA Service Identifier | 3.10.2 | M | M | M | P | +| GBA User Security Settings | 3.10.3 | M | M | - | P | +| User Security Setting | 3.10.4 | M | M | M | P | +| User Public Identity | 3.10.5 | M | M | M | P | +| GAA Authorization flag | 3.10.6 | C | C | C | P | +| Bootstrapping Transaction Identifier | 3.10.7 | - | M | M | T | +| Key Lifetime | 3.10.8 | C | M | - | P | +| UICC Security Setting | 3.10.9 | C | C | - | P | +| NAF Group | 3.10.10 | - | M | - | P | +| NAF Group Identity | 3.10.11 | C | M | - | P | +| NAF Address | 3.10.12 | - | M | - | P | +| Key Expirytime | 3.10.13 | - | M | M | T | +| Bootstrapping Info Creation Time | 3.10.14 | - | M | M | T | +| Diameter Server Identity of HSS | 3.10.15 | - | C | - | T | + +The possible user's GBA User Security Settings (GUSS) are stored in HSS with User Private Identifier (IMPI) as retrieval key. + +The bootstrapping procedure creates a bootstrapping information entity to the BSF with B-TID as retrieval key. + +## 5.5 I-WLAN Service Data Storage + +NOTE: The WLAN Network Selection and WLAN/3GPP Radio Interworking features supersede the I-WLAN feature from Rel-12 onwards, therefore all I-WLAN subscriber data specified in the present Clause are no longer maintained. + +**Table 5.5: Overview of data used for I-WLAN services** + +| PARAMETER | Clause | HSS | 3GPP AAA Server | 3GPP AAA Proxy | PDG | WAG | TYPE | +|------------------------------------------------|------------|----------|-----------------|----------------|-----|-----|------| +| IMSI | 3.11.1.1 | M | M | - | C | - | P | +| MSISDN | 3.11.1.2 | M | M | M | M | M | P | +| W-APN | 3.11.1.3 | C | C | C | C | - | T | +| List of authorized visited network identifiers | 3.11.1.4 | M | - | - | - | - | P | +| 3GPP AAA Proxy Name | 3.11.1.5 | C | C | C | C | C | T | +| 3GPP AAA Server Name | 3.11.1.6 | C | - | C | C | C | T | +| Serving PDG List | 3.11.1.7 | - | C | C | - | - | T | +| Serving WAG | 3.11.1.8 | - | C | C | - | - | T | +| WLAN UE Local IP address | 3.11.1.9 | - | - | - | C | C | T | +| WLAN UE Remote IP address | 3.11.1.10 | C | C | - | C | - | P | +| User Status | 3.11.2.1 | M | M | - | - | - | T | +| Emergency Access | 3.11.2.2 | - | M | - | - | - | T | +| Diameter Server Identity of HSS | 3.11.2.3 | - | C | - | - | - | T | +| RAND, SRES, Kc | 3.11.3.1 | - | C | - | - | - | T | +| RAND, XRES CK, IK, AUTN | 3.11.3.2 | M | C | - | - | - | T | +| Master Key (MK) | 3.11.3.3 | - | M | - | - | - | T | +| Transient EAP Keys (TEKs) | 3.11.3.4 | - | M | - | - | - | T | +| Master Session Key (MSK) | 3.11.3.5 | - | - | - | C | - | T | +| Session Identifier | 3.11.4.1 | - | M | C | C | - | T | +| Session-Timeout | 3.11.4.2 | - | C | - | - | - | P | +| W APN Identifier List | 3.11.5.1.1 | C | C | - | C | - | P | +| W-APN Barring Type List | 3.11.5.1.2 | C | C | - | - | - | P | +| W-APN Charging Data List | 3.11.5.1.3 | C | C | - | C | - | P | +| Static WLAN UE Remote IP Address List | 3.11.5.1.4 | C | C | - | C | - | P | +| Maximum-Number-Accesses List | 3.11.5.1.5 | C | C | - | - | - | P | +| Access-Number List | 3.11.5.1.6 | - | M | - | - | - | T | +| Access Dependence Flag | 3.11.5.2 | M | M | - | - | - | P | +| I-WLAN Access Type | 3.11.5.3 | M | M | - | - | - | T | +| WLAN Direct IP Access | 3.11.5.4 | C | C | - | - | - | P | +| Max Subscribed Bandwidth | 3.11.6.1 | C | C | - | C | - | P | +| Routing Policy | 3.11.6.2 | - | C | C | C | C | T | +| Subscribed 3GPP WLAN QoS Profile | 3.11.6.3 | C | C | - | - | - | P | +| Authorized 3GPP WLAN QoS Profile | 3.11.6.4 | - | C | - | C | - | T | +| Charging Characteristics | 3.11.7.1.1 | M | M | - | C | - | P | +| Primary OCS Charging Function Name | 3.11.7.2 | C Note 1 | C | - | C | - | P | +| Secondary OCS Charging Function Name | 3.11.7.3 | C | C | - | C | - | P | +| Primary Charging Collection Function Name | 3.11.7.4 | C Note 1 | C | - | C | - | P | +| Secondary Charging Collection Function Name | 3.11.7.5 | C | C | - | C | - | P | +| WLAN Session Identifier | 3.11.7.6 | - | M | C | C | - | T | +| PDG Session Identifier | 3.11.7.7 | - | C | C | M | - | T | + +Note 1: At least one of these Primary Charging Function Names shall be mandatorily provisioned in the HSS. + +## 5.6 MBMS Storage (EPS) + +Table 5.6-1: Overview of data used for MBMS (EPS) + +| PARAMETER | Clause | SGSN | MME | MBMS GW | BM-SC | TYPE | +|--------------------------------------------|---------|------|-----|---------|-------|------| +| MBMS GW F-TEID for Sm(Control Plane) | 2.22.1 | - | C | C | - | T | +| MBMS GW F-TEID for Sn(Control Plane) | 2.22.2 | C | - | C | - | T | +| Temporary Mobile Group Identity | 2.22.3 | C | C | C | C | P | +| MBMS Flow Identifier | 2.22.4 | C | C | C | C | P | +| MBMS IP Multicast Distribution | 2.22.5 | C | C | C | - | T | +| MBMS Service Area | 2.22.6 | C | C | C | C | P | +| MME F-TEID for Sm (Control Plane) | 2.22.7 | - | C | C | - | T | +| SGSN F-TEID for Sn (Control Plane) | 2.22.8 | C | - | C | - | T | +| SGSN F-TEID for Sn (User Plane) | 2.22.9 | C | - | C | - | T | +| MBMS session identifier | 2.22.10 | C | C | C | C | P | +| MBMS session duration | 2.22.11 | C | C | C | C | P | +| QoS parameters | 2.22.12 | C | C | C | C | P | +| MBMS Time to Data Transfer | 2.22.13 | C | C | C | C | P | +| MBMS Data Transfer Start | 2.22.14 | - | C | C | C | P | +| List of downstream nodes | 2.22.15 | C | C | C | C | T | +| MBMS Session Re-establishment Indication | 2.22.16 | C | C | C | C | T | +| GCS AS Address | 2.22.17 | - | - | - | C | T | +| MB2-U Port Number | 2.22.18 | - | - | - | C | T | +| MBMS Start Time | 2.22.19 | - | - | - | C | T | +| TMGI Expiration Time | 2.22.20 | - | - | - | C | T | +| MBMS Alternative IP Multicast Distribution | 2.22.21 | - | C | C | - | T | +| MBMS Cell List | 2.22.22 | - | C | C | C | P | + +## 5.7 VPLMN Autonomous CSG Roaming Service Data Storage + +Table 5.7-1: Overview of data used for VPLMN Autonomous CSG Roaming Service + +| PARAMETER | Clause | CSS | MME | S4-SGSN | Gn/Gp-SGSN | VLR | TYPE | +|-------------------------------------------|----------|-----|-----|---------|------------|-----|------| +| IMSI | 2.1.1.1 | M | C | C | M | M | P | +| International MS ISDN number | 2.1.2 | C | C | C | C | C | P | +| VLR Number | 2.4.5 | M | - | - | - | - | T | +| SGSN Number | 2.4.8.1 | M | - | - | - | - | T | +| CSS Number | 2.4.25 | - | - | - | C | C | T | +| VPLMN Closed Subscriber Group Information | 2.4.26 | C | C | C | C | C | P | +| MME Name | 2.13.26 | M | - | - | - | - | T | +| SGSN Name | 2.13.100 | M | - | - | - | - | T | +| Diameter Server Identity of CSS | 2.13.133 | - | C | C | - | - | T | + +## 5.8 Proximity Services (ProSe) Data Storage + +Table 5.8-1: Overview of data for Proximity Services + +| PARAMETER | Clause | HSS | SLP | MME | ProSe Function | ProSe Application Server | TYPE | +|---------------------------|----------|-----|-----|-----|----------------|--------------------------|------| +| IMSI | 2.1.1.1 | M | C | C | C | - | P | +| MSISDN | 2.1.2 | C | C | C | C | - | P | +| ProSe-Permission | 3.13.2.1 | C | - | C | C | - | P | +| PLMN-Allowed-ProSe | 3.13.2.2 | C | - | C | C | - | P | +| Application layer user ID | 3.13.3 | - | - | - | C | C | P | +| EPC ProSe User ID | 3.13.4 | - | - | - | C | C | T | +| ProSe Application ID | 3.13.5 | - | - | - | C | - | P | +| ProSe Application Code | 3.13.6 | - | - | - | C | - | T | +| Filter ID | 3.13.7.1 | - | - | - | C | - | P | +| ProSe Application Code | 3.13.7.2 | - | - | - | C | - | P | +| ProSe Application Mask | 3.13.7.3 | - | - | - | C | - | P | +| TTLTimer T4002 | 3.13.7.4 | - | - | - | C | - | P | +| ProSe Function Identity | 3.13.8 | C | - | - | - | C | T | +| ProSe Metadata Index Mask | 3.13.9 | - | - | - | C | - | P | +| PC5-tech | 3.13.10 | - | - | - | C | - | T | + +## 5.9 Architecture Enhancements for Service Exposure storage (AESE) + +Table 5.9-1: Overview of data used for AESE + +| PARAMETER | Clause | HSS | MME | SGSN | SCEF | TYPE | +|--------------------------------------------------------|-----------|-----|-----|------|------|------| +| International MS ISDN number | 2.1.2 | C | C | C | C | P | +| External Identifier Set | 2.1.10 | C | - | - | C | P | +| SCEF-Reference-ID | 3.14.2 | C | C | C | C | T | +| SCEF-ID | 3.14.3 | C | C | C | C | P | +| Monitoring-Type | 3.14.4 | C | C | C | C | P | +| Maximum-Number-of-Reports | 3.14.5 | C | C | C | C | P | +| UE-Reachability-Configuration | 3.14.6 | C | C | C | C | P | +| Monitoring-Duration | 3.14.7 | C | C | C | C | P | +| Maximum-Detection-Time | 3.14.8 | C | - | - | C | P | +| Reachability-Type | 3.14.9 | C | - | - | C | P | +| Maximum Latency | 3.14.10 | C | - | - | C | P | +| Maximum Response Time | 3.14.11 | C | C | C | C | P | +| MONTE-Location-Type | 3.14.12 | C | C | C | C | P | +| Accuracy | 3.14.13 | C | C | C | C | P | +| Association-Type | 3.14.14 | C | - | - | C | P | +| Charged-Party | 3.14.15 | C | C | C | C | P | +| Remaining number of reports | 3.14.16 | C | C | C | C | T | +| Periodic-Communication-Indicator | 3.14.17.1 | C | C | - | C | P | +| Communication-Duration-Time | 3.14.17.2 | C | C | - | C | P | +| Periodic-Time | 3.14.17.3 | C | C | - | C | P | +| Scheduled-Communication-Time | 3.14.17.4 | C | C | - | C | P | +| Stationary-Indication | 3.14.17.5 | C | C | - | C | P | +| Validity-Time | 3.14.17.6 | C | C | - | C | P | +| AESE-Subscription-Data | 3.14.18 | C | - | - | - | P | +| SCEF-Realm | 3.14.19 | C | C | C | C | P | +| External-Identifier for Monitoring Event Configuration | 3.14.20 | C | C | C | C | P | +| External Group Identifier | 3.14.21 | C | - | - | C | P | + +## 5.10 Data related to Cellular IoT Control Plane Optimizations + +Table 5.10-1: Overview of data used for CIoT + +| PARAMETER | Clause | HSS | MME | SGSN | SGW | PGW | SCEF | TYPE | +|------------------------------------------------|----------|-----|-----|------|-----|-----|------|------| +| IMSI | 2.1.1.1 | C | C | C | - | - | C | P | +| MSISDN | 2.1.2 | C | C | C | - | - | C | P | +| External Identifier set | 2.1.10 | C | - | - | - | - | C | P | +| Access Point Name | 2.13.6 | C | C | C | - | - | C | P | +| EPS Bearer Id | 2.13.66 | - | C | C | - | - | C | T | +| Acknowledgement-Of-Downlink-NAS-Data-PDUs flag | 2.13.173 | C | C | - | - | - | - | P | +| Robust Header Compression Context | 2.23.1 | - | C | - | - | - | - | T | +| MME F-TEID for S11 (user plane) | 2.23.3 | - | C | - | C | - | - | T | +| S-GW F-TEID for S11 (userplane) | 2.23.4 | - | C | - | C | - | - | T | +| Serving-PLMN-Rate-Control | 2.23.5 | - | C | - | C | C | C | P | +| APN-Rate-Control | 2.23.6 | - | - | - | - | C | C | P | +| Not Reachable for NIDD Flag | 2.23.7 | - | C | C | - | - | - | T | +| NIDD Authorization | 2.23.8 | C | - | - | - | - | C | P | +| SCEF-ID | 3.14.3 | C | C | C | - | - | C | P | +| SCEF-Realm | 3.14.19 | C | C | C | - | - | C | P | + +## 5.11 V2X Service (V2X) Data Storage + +Table 5.11-1: Overview of data for V2X Service + +| PARAMETER | Clause | HSS | SLP | MME | V2X Control Function | TYPE | +|-------------------------------|----------|-----|-----|-----|----------------------|------| +| IMSI | 2.1.1.1 | M | C | C | C | P | +| MSISDN | 2.1.2 | C | C | C | C | P | +| V2X-Permission | 3.16.2.1 | C | - | C | - | P | +| UE-PC5-AMBR | 3.16.2.2 | C | - | C | - | P | +| V2X-PC5-Allowed-PLMN | 3.16.2.3 | C | - | - | C | P | +| V2X-Permission-in-VPLMN | 3.16.3.1 | - | - | - | C | P | +| V2X-Application-Server | 3.16.3.2 | - | - | - | C | P | +| PC5-RAT-Type | 3.16.3.3 | C | - | - | C | P | +| V2X Control Function Identity | 3.16.4 | C | - | - | - | T | +| V2X-Permission | 3.16.5.1 | C | - | C | - | P | +| UE-PC5-AMBR | 3.16.5.2 | C | - | C | - | P | +| V2X-PC5-Allowed-PLMN | 3.16.5.3 | C | - | - | C | P | +| UE-PC5-QoS | 3.16.5.4 | C | - | C | - | P | + +--- + +## Annex A (informative): Old Change history + +| Change history | | | | | | | +|----------------|-----------|---------|-------|---------|-------------|-------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| Apr 1999 | GSM 03.08 | 7.0.0 | | | | Transferred to 3GPP CN1 | +| CN#03 | 23.008 | | | R99 | 3.0.0 | Approved at CN#03 | +| CN#05 | 23.008 | 3.0.0 | 002r1 | R99 | 3.1.0 | Approved at CN#05 | +| CN#06 | 23.008 | 3.1.0 | 003r1 | R99 | 3.2.0 | Introduction of the Super-Charger Concept in TS 23.008 | +| CN#06 | 23.008 | 3.1.0 | 004r3 | R99 | 3.2.0 | Authentication Enhancements | +| CN#06 | 23.008 | 3.1.0 | 009 | R99 | 3.2.0 | Authentication Enhancements | +| CN#06 | 23.008 | 3.1.0 | 010r2 | R99 | 3.2.0 | Combined CR on 23.008 | +| CN#06 | 23.008 | 3.1.0 | 011 | R99 | 3.2.0 | Organization of Subscriber Data for LCS | +| CN#07 | 23.008 | 3.2.0 | 012r2 | R99 | 3.3.0 | Introduction of 'Notification to CSE flag' to the operator determined barring data | +| CN#07 | 23.008 | 3.2.0 | 013 | R99 | 3.3.0 | Correction of LSA Information | +| CN#07 | 23.008 | 3.2.0 | 014r2 | R99 | 3.3.0 | The addition of priority information to subscriber data | +| CN#07 | 23.008 | 3.2.0 | 015r1 | R99 | 3.3.0 | Introduction of Multicall | +| CN#07 | 23.008 | 3.2.0 | 016r1 | R99 | 3.3.0 | Parallel handling of multiple PDP contexts | +| CN#07 | 23.008 | 3.2.0 | 019r1 | R99 | 3.3.0 | Introduction of Service Area Identification | +| CN#07 | 23.008 | 3.2.0 | 020r1 | R99 | 3.3.0 | Addition of gsmSCF address list to CSI | +| CN#07 | 23.008 | 3.2.0 | 023r1 | R99 | 3.3.0 | Combined CR on 23.008 | +| CN#07 | 23.008 | 3.2.0 | 024 | R99 | 3.3.0 | Adding D-CSI to table with Negotiated CAMEL Capability Handling variables | +| CN#07 | 23.008 | 3.2.0 | 025 | R99 | 3.3.0 | Addition of PDP Context Identifier | +| CN#08 | 23.008 | 3.3.0 | 017 | R99 | 3.4.0 | Addition of subscribed charging characteristics information | +| CN#08 | 23.008 | 3.3.0 | 026r2 | R99 | 3.4.0 | Editorial changes on 23.008 draft version 3.2.0 | +| CN#08 | 23.008 | 3.3.0 | 027 | R99 | 3.4.0 | Clarifications on GSM vs. UMTS specific parts | +| CN#08 | 23.008 | 3.3.0 | 029 | R99 | 3.4.0 | Addition of charging characteristics per PDP context | +| CN#09 | 23.008 | 3.4.0 | 030 | R99 | 3.5.0 | Deletion of "Barring of roaming" stored in SGSN | +| CN#09 | 23.008 | 3.4.0 | 031 | R99 | 3.5.0 | Corrections of the description of BC allocation for VLR (Release 99) | +| CN#11 | 23.008 | 3.5.0 | | Rel-4 | 4.0.0 | Version updated from R99 to Rel-4 after CN#11 | +| CN#11 | 23.008 | 3.5.0 | 032r1 | Rel-4 | 4.0.0 | Declare barring data for ODB PS | +| CN#11 | 23.008 | 3.5.0 | 033r2 | Rel-4 | 4.0.0 | Addition of LCS related subscriber data for PS domain | +| CN#12 | 23.008 | 4.0.0 | 035r3 | Rel-4 | 4.1.0 | Correction of references | +| CN#12 | 23.008 | 4.0.0 | 037 | Rel-4 | 4.1.0 | Supported CAMEL Phases in VLR is temporary | +| CN#15 | 23.008 | 4.1.0 | 038r5 | Rel-5 | 5.0.0 | Addition of multimedia information elements | +| CN#15 | 23.008 | 4.1.0 | 039r1 | Rel-5 | 5.0.0 | Collective CRs against 23.008 for CAMEL phase4 | +| CN#16 | 23.008 | 5.0.0 | 041r2 | Rel-5 | 5.1.0 | Filter Criteria Modifications | +| CN#16 | 23.008 | 5.0.0 | 043 | Rel-5 | 5.1.0 | Correction to TS 23.008 | +| CN#16 | 23.008 | 5.0.0 | 044 | Rel-5 | 5.1.0 | Correction of the DP criteria table for T-CSI and VT-CSI on the Rel05 collective CR | +| CN#16 | 23.008 | 5.0.0 | 045r1 | Rel-5 | 5.1.0 | Splitting of CAMEL phase 4 | +| CN#16 | 23.008 | 5.0.0 | 047r1 | Rel-5 | 5.1.0 | Addition of Service Indication | +| CN#16 | 23.008 | 5.0.0 | 048r1 | Rel-5 | 5.1.0 | CR on the charging function address format | +| CN#16 | 23.008 | 5.0.0 | 051 | Rel-5 | 5.1.0 | Correction of errors introduced with the taken into account CAMEL phase 4 | +| CN#16 | 23.008 | 5.0.0 | 052r1 | Rel-5 | 5.1.0 | LCS: Service Type and Codeword | +| CN#16 | 23.008 | 5.0.0 | 053 | Rel-5 | 5.1.0 | Alignment of 23.008 | +| CN#17 | 23.008 | 5.1.0 | 054r1 | Rel-5 | 5.2.0 | The Organisation of CAMEL IMS Data | +| CN#17 | 23.008 | 5.1.0 | 056r1 | Rel-5 | 5.2.0 | Handling of partial implementations of CAMEL phase 4 | +| CN#17 | 23.008 | 5.1.0 | 057 | Rel-5 | 5.2.0 | Wrong Camel capability handling for the O-CSI, T-CSI, VT-CSI and D-CSI | +| CN#18 | 23.008 | 5.2.0 | 058 | Rel-5 | 5.3.0 | Addition of Barring Indication of multimedia public identities | + +| Change history | | | | | | | +|----------------|--------|---------|--------|---------|-------------|----------------------------------------------------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| CN#18 | 23.008 | 5.2.0 | 060 | Rel-5 | 5.3.0 | Deleting codeword related information | +| CN#18 | 23.008 | 5.2.0 | 061r1 | Rel-5 | 5.3.0 | Correction to the form of public user identity | +| CN#19 | 23.008 | 5.3.0 | 065r1 | Rel-5 | 5.4.0 | Clarification of IMPU barring handling | +| CN#19 | 23.008 | 5.3.0 | 067r1 | Rel-5 | 5.4.0 | Definition of the Subscribed Media Profile Identifier | +| CN#20 | 23.008 | 5.4.0 | 068 | Rel-5 | 5.5.0 | Storage of UESBI in the VLR and SGSN | +| CN#20 | 23.008 | 5.4.0 | 121 | Rel-5 | 5.5.0 | Distinction between Roaming Restriction Due To Unsupported Feature and Roaming Restricted in the SGSN Due To Unsupported Feature | +| CN#21 | 23.008 | 5.5.0 | 122r2 | Rel-5 | 5.6.0 | Addition of a list of authorized visited network identifiers | +| CN#22 | 23.008 | 5.6.0 | 126 | Rel-5 | 5.7.0 | Registration status | +| CN#22 | 23.008 | 5.6.0 | 128r1 | Rel-5 | 5.7.0 | Correct table of IMS elements | +| CN#22 | 23.008 | 5.7.0 | 127r4 | Rel-6 | 6.0.0 | Services related to unregistered state | +| CN#23 | 23.008 | 6.0.0 | 129 | Rel-6 | 6.1.0 | Inclusion of Access_Restriction_Data parameter | +| CN#24 | 23.008 | 6.1.0 | 130r4 | Rel-6 | 6.2.0 | Add IMEISV to 'data stored in the HLR' due to ADD function | +| CN#25 | 23.008 | 6.2.0 | 133r3 | Rel-6 | 6.3.0 | GAA Domain Data Structure | +| CN#26 | 23.008 | 6.3.0 | 135r1 | Rel-6 | 6.4.0 | Inclusion of selected CN operator ID parameter | +| CN#26 | 23.008 | 6.3.0 | 136 | Rel-6 | 6.4.0 | Optimization of User Profile Download | +| CN#26 | 23.008 | 6.3.0 | 137 | Rel-6 | 6.4.0 | Subscribed Media Profile Identifier | +| CN#26 | 23.008 | 6.3.0 | 138r1 | Rel-6 | 6.4.0 | Domain independent GAA | +| CN#26 | 23.008 | 6.3.0 | 140 | Rel-6 | 6.4.0 | Correction to authorization flag definition | +| CN#26 | 23.008 | 6.3.0 | 141 | Rel-6 | 6.4.0 | Introduction of NAF groups | +| CN#26 | 23.008 | 6.3.0 | 142r1 | Rel-6 | 6.4.0 | WLAN-IW data handling: additions to 23.008 | +| CN#27 | 23.008 | 6.4.0 | 134r4 | Rel-6 | 6.5.0 | Adding trace control and configuration parameters to subscriber data in HSS | +| CN#27 | 23.008 | 6.4.0 | 143r1 | Rel-6 | 6.5.0 | Add reference to Implicitly registered Public User Identities set definition | +| CT#28 | 23.008 | 6.5.0 | 148 | Rel-6 | 6.6.0 | Change the temporary flag of the MSISDN for GPRS | +| CT#28 | 23.008 | 6.5.0 | 0150 | Rel-6 | 6.6.0 | Removal of implied link between MS and IMS subscription | +| CT#28 | 23.008 | 6.5.0 | 0146r2 | Rel-6 | 6.6.0 | Corrections on WLAN UE Remote IP Address | +| CT#28 | 23.008 | 6.5.0 | 0147r1 | Rel-6 | 6.6.0 | Default Public User Identity per Implicit Registration Set | +| CT#28 | 23.008 | 6.5.0 | 0145r2 | Rel-6 | 6.6.0 | Corrections on Serving WAG | +| CT#28 | 23.008 | 6.5.0 | 0151r1 | Rel-6 | 6.6.0 | Addition of Maximum-Number-Accesses AVP and Number-Accesses Data types | +| CT#28 | 23.008 | 6.5.0 | 0144r4 | Rel-6 | 6.6.0 | Public Service Identity | +| CT#28 | 23.008 | 6.6.0 | 152r2 | Rel-6 | 6.7.0 | Correction on I-WLAN Service Data Storage table | +| CT#28 | 23.008 | 6.6.0 | 153 | Rel-6 | 6.7.0 | Correction to handling of Maximum-Number-Accesses description | +| CT#28 | 23.008 | 6.6.0 | 154R2 | Rel-6 | 6.7.0 | PSI routing | +| CT#28 | 23.008 | 6.6.0 | 155r1 | Rel-6 | 6.7.0 | Update to GAA time data items | +| CT#28 | 23.008 | 6.6.0 | 156r1 | Rel-6 | 6.7.0 | PSI Activation | +| CT#28 | 23.008 | 6.6.0 | 157r1 | Rel-6 | 6.7.0 | Removing references to Diameter draft | +| CT#28 | 23.008 | 6.6.0 | 159r1 | Rel-6 | 6.7.0 | IMSI handling at the PDG | +| CT#28 | 23.008 | 6.6.0 | 160 | Rel-6 | 6.7.0 | Change of reference from Release 5 to Release 6 | +| CT#28 | 23.008 | 6.6.0 | 161 | Rel-6 | 6.7.0 | Association of the Charging Information with the IMS Subscription | +| CT#28 | 23.008 | 6.6.0 | 162 | Rel-6 | 6.7.0 | Charging-Information Correction | +| CT#30 | 23.008 | 6.7.0 | 0163r1 | Rel-6 | 6.8.0 | Incorrect References | +| CT#30 | 23.008 | 6.7.0 | 0164r1 | Rel-6 | 6.8.0 | Correction on I-WLAN Service Data Storage table | +| CT#30 | 23.008 | 6.7.0 | 0165r2 | Rel-6 | 6.8.0 | Updating the table of I-WLAN Data Storage | +| CT#30 | 23.008 | 6.8.0 | | Rel-7 | 7.0.0 | Rel-7 version was created because of ETSI TISPAN references. | + +| Change history | | | | | | | +|----------------|--------|---------|------------------------------------------------------------------|---------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| CT#31 | 23.008 | 7.0.0 | 0169r1 | Rel-7 | 7.1.0 | Correction to the Max Requested Bandwidth in I-WLAN data storage | +| CT#32 | 23.008 | 7.1.0 | 0172r2 | Rel-7 | 7.2.0 | Roaming handling with implicitly registered Public User IDs | +| CT#33 | 23.008 | 7.2.0 | 0179r1 | Rel-7 | 7.3.0 | Correction of the handling of transparent data | +| CT#33 | 23.008 | 7.2.0 | 0176r2 | Rel-7 | 7.3.0 | Storage of the Display Name in the IM Core Network Subsystem | +| CT#34 | 23.008 | 7.3.0 | 0170r4
0181r1
0183r1
0187r1
0190r1
0194
0195r1 | Rel-7 | 7.4.0 | Support of SMS over IP networks
Activation Status of a PSI
Charging identifier storage
User Status valid values
Definition of Wildcarded PSIs
Clarification of the definition of the Service Indication
Addition of Emergency Access Flag to I-WLAN User data | +| CT#35 | 23.008 | 7.4.0 | 0196r1
0198r2
0199r2
0201
0205r1 | Rel-7 | 7.5.0 | Subscriber data for Operator Determined Barring
Correction of user data
QoS parameter storage in I-WLAN entities
MNRR correction
Network Access Identifier Update | +| CT#36 | 23.008 | 7.5.0 | 0200r1
0206
0207r2
0209 | Rel-7 | 7.6.0 | Addition of UNRI
Mobile Termination whilst the MS is moving to another MSC
Definition of the List of Subscribed IMS Communication Service Identifiers
Negotiated CAMEL Capability Handling for M-CSI and SS-CSI | +| CT#37 | 23.008 | 7.6.0 | 0210
0211r1
0213r1 | Rel-7 | 7.7.0 | Mandatory Charging Data in the HSS
Repository Data for Alias Public User Identities
Repository Data for Wildcarded PSIs | +| CT#38 | 23.008 | 7.7.0 | 0220 | Rel-7 | 7.8.0 | Addition of Alias Public User Identities | +| CT#38 | 23.008 | 7.8.0 | 0214r5 | Rel-8 | 8.0.0 | Updates to 23.008 for Digest | +| CT#39 | 23.008 | 8.0.0 | 0222r2
0223r1
0226 | Rel-8 | 8.1.0 | Update for Supporting NASS-Bundled-Authentication
PSI clarification
Wildcarded Public User Identities | +| CT#40 | 23.008 | 8.1.0 | 0221r1 | Rel-8 | 8.2.0 | Paging optimization with A/lu flex | +| CT#41 | 23.008 | 8.2.0 | 0229
0230r1
0232 | Rel-8 | 8.3.0 | Addition of IMS Centralized Service subscription information
Support of "Loose-Route" indication from HSS
Add S-CSCF Restoration Information as One Subscriber Data | +| CT#42 | 23.008 | 8.3.0 | 0234r1
0233r4
0236
0238r2 | Rel-8 | 8.4.0 | Introduction of new subscriber related data for CS fallback
Closed Subscriber Group
Support for IMS Service Level Trace
EPS related Subscriber Data | +| CT#43 | 23.008 | 8.4.0 | 0245r1
0239r3
0244 | Rel-8 | 8.5.0 | AliasesRepositoryData removal
Correction and alignments with interface specifications
EPS Subscription Data | +| CT#44 | 23.008 | 8.5.0 | 0248r2
0249
0251r3 | Rel-8 | 8.6.0 | Loose Route Indication
Parameters storage related to ISR
User data related to UE reachability notification procedure | +| CT#45 | 23.008 | 8.6.0 | 0252r1
0254r1
0256r1 | Rel-8 | 8.7.0 | Subscribed and EPS PDN Connection Charging Characteristics
HSS Data Corrections
SA2 alignment in 23.008 | + +| Change history | | | | | | | +|----------------|--------|---------|--------|---------|-------------|----------------------------------------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| | | | 0258r1 | | | Correction on some ODB parameters description | +| | | | 0259r3 | | | Removal of URRD | +| CT#45 | 23.008 | 8.7.0 | 0253r1 | Rel-9 | 9.0.0 | Managing membership of CSG users | +| | | | 0257r1 | | | Subscriber Data for MBMS in EPS | +| CT#46 | 23.008 | 9.0.0 | 0260r2 | Rel-9 | 9.1.0 | Information storage for IMS emergency call over GRPS and EPS | +| | | | 0262r1 | | | Correction on AMBR | +| | | | 0263r3 | | | APN level APN-OI replacement | +| | | | 0266r1 | | | ICS-Flag | +| | | | 0265r1 | | | Information Storage correction | +| | | | 0268r2 | | | RFSP alignment in 23.008 | +| | | | 0274 | | | Information storage for IMS emergency call over EPS non 3GPP access | +| | | | 0280 | | | Corrections to "eNB F-TEID for S1-U" | +| | | | 0285r2 | | | S4-SGSN and Gn/Gp-SGSN | +| | | | 0287r2 | | | PDN Connection Id | +| CT#47 | 23.008 | 9.1.0 | 0292r1 | Rel-9 | 9.2.0 | Priority service information stored in HSS | +| | | | 0288r2 | | | ANDSF Subscription Data | +| CT#48 | 23.008 | 9.2.0 | 0304r1 | Rel-9 | 9.3.0 | Update of IETF Reference | +| | | | 0296r3 | | | Missing IMS information related to AS identities | +| | | | 0298r1 | | | HPLMN ODB | +| | | | 0299 | | | Information storage for UE's usage setting and voice capability | +| | | | 0302r1 | | | URRP for SGSN | +| CT#49 | 23.008 | 9.3.0 | 0309 | Rel-9 | 9.4.0 | S-CSCF re-assignment pending flag | +| CT#49 | 23.008 | 9.4.0 | 0305r1 | Rel-10 | 10.0.0 | SIPTO Permission Indicator | +| CT#50 | 23.008 | 10.0.0 | 0313r2 | Rel-10 | 10.1.0 | Subscriber's data for MAPCON | +| | | | 0322r2 | | | Missing Restoration flags for Gs/SGs interface | +| | | | 0328r1 | | | Addition of UE Purge Flag | +| | | | 0326r1 | | | Periodic TAU/RAU timer in HSS subscription | +| | | | 0325r5 | | | Enhanced SRVCC Subscriber Data | +| | | | 0318r2 | | | Definition of Alias Public User Identities | +| | | | 0316r1 | | | Clarification on SIPTO Permission for Wildcard APN | +| | | | 0315r2 | | | Non-3GPP data storage for S2b-GTP | +| | | | 0312r1 | | | Addition of MPS Priority as Subscriber Data | +| | | | 0311r1 | | | Addition of LIPA permission as Subscriber Data | +| | | | 0317r2 | | | Addition of Service-related Entity Information elements to the Subscriber Data and removal of duplicated information | +| CT#51 | 23.008 | 10.1.0 | 0330r2 | Rel-10 | 10.2.0 | Minimization of Drive Tests (MDT) | +| | | | 0333r2 | | | Subscription Data for Relay Node | +| | | | 0334 | | | New Extended Priority data | +| | | | 0335 | | | MT Roaming Retry and Super Charger | +| | | | 0337r1 | | | STN-SR and SRVCC subscription | +| CT#52 | 23.008 | 10.2.0 | 0338r1 | Rel-10 | 10.3.0 | MDT user consent | +| | | | 0340r1 | | | Addition of SC Address as Subscriber Data | +| | | | 0341r1 | | | Periodic LAU timer in HSS subscription | +| CT#52 | 23.008 | 10.3.0 | 0336r2 | Rel-11 | 11.0.0 | Definition of Referece Location as Subscriber Data | +| CT#53 | 23.008 | 11.0.0 | 0351r1 | Rel-11 | 11.1.0 | VPLMN Address Allowed data defined per VPLMN | +| | | | 0345r1 | | | Privileged sender | +| | | | 0347r1 | | | Add vSRVCC updates for subscriber data | +| | | | 0354r1 | | | Addition of AMBR for GPRS | +| CT#54 | 23.008 | 11.1.0 | 0355r2 | Rel-11 | 11.2.0 | Correction on Definition of RAT Type | + +| Change history | | | | | | | +|----------------|--------|---------|--------|---------|-------------|--------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| CT#55 | 23.008 | 11.2.0 | 0360r1 | Rel-11 | 11.3.0 | Information storage on the Higher bitrates than 16Mbps flag and the Max MBR/APN-AMBR | +| | | | 0363r2 | | | Subscriber data for BBAI | +| CT#56 | 23.008 | 11.3.0 | 0361r2 | Rel-11 | 11.4.0 | Maximum Number of simultaneous registrations | +| | | | 0364r1 | | | New IEs for H(e)NB case in BBAI | +| | | | 0362r7 | | | Update of subscriber data with the PS additional number | +| | | | 0365r3 | | | SMS in MME/SGSN | +| | | | 0346r9 | | | CSS information storage | +| | | | 0366r1 | | | Information Storage of the MME/SGSN ID in the PGW | +| | | | 0367r1 | | | Information Storage of the SGW node name/ Co-located GGSN-PGW FQDN | +| | | | 0368r1 | | | External Identifier | +| | | | 0369 | | | Information Storage of the CGI/SAI age | +| | | | 0370r1 | | | User's subscription data for WLAN access to EPC | +| CT#57 | 23.008 | 11.4.0 | 0375r1 | Rel-11 | 11.5.0 | PS only subscription w/o MSISDN | +| | | | 0376r1 | | | Information storage of Homogeneous Support of IMS Voice over PS Sessions | +| | | | 0377 | | | Data for I-WLAN service | +| | | | 0378r1 | | | Uniform terminology | +| | | | 0379 | | | Reference corrections | +| | | | 0380r1 | | | Storage of last known cell identity in GGSN/PDN-GW | +| | | | 0381r1 | | | Reference list correction to align with the corrected TS 29.212 title | +| CT#58 | 23.008 | 11.5.0 | 0384 | Rel-11 | 11.6.0 | SIPTO support for eHRPD | +| | | | 0393r1 | | | Trace info stored in SGW/PGW | +| | | | 0382r1 | | | Storage of the Signalling Priority Indication | +| | | | 0385 | | | Key Status for UMTS | +| | | | 0386 | | | Closed Subscriber Group Information for Inter-PLMN handover to a CSG cell | +| | | | 0389r1 | | | Trace Info in CS data storage | +| | | | 0387 | | | Removal of Maximum MBR/APN-AMBR | +| | | | 0388r1 | | | PS only subscription without MSISDN | +| CT#59 | 23.008 | 11.6.0 | 0398r1 | Rel-11 | 11.7.0 | EPS Subscribed QoS Profile | +| CT#60 | 23.008 | 11.7.0 | 0403r2 | Rel-11 | 11.8.0 | Storing of eCGI within the VLR | +| | | | 0401 | | | Restoration Priority during SGW and PGW restoration procedures | +| CT#60 | 23.008 | 11.8.0 | 0402r1 | Rel-12 | 12.0.0 | SIPTO permission for Local Network enhancements | +| | | | 0399 | | | MBMS data storage | +| 06-2013 | 23.008 | 12.0.0 | | Rel-12 | 12.0.1 | Clause 5 empty cell in tables corrected with "-". | +| CT#61 | 23.008 | 12.0.1 | 0404r1 | Rel-12 | 12.1.0 | MBMS Session Re-establishment Indication | +| | | | 0405r1 | | | Clarification of Aggregate Maximum Bit Rate (AMBR) terms | +| CT#63 | 23.008 | 12.1.0 | 0407r2 | Rel-12 | 12.2.0 | Storage of RAN assistance data in MME | +| CT#64 | 23.008 | 12.2.0 | 0410r1 | Rel-12 | 12.3.0 | CS to PS SRVCC | +| | | | 0412r1 | | | IP-SM-GW address handling clarification | +| | | | 0408r1 | | | Presence Reporting Area Action | +| | | | 0413r1 | | | Consistency of ICS Indicator | +| CT#65 | 23.008 | 12.3.0 | 0420r1 | Rel-12 | 12.4.0 | RAN assistant information storage in MME | +| | | | 0421r2 | | | WLAN offloadability | +| | | | 0422r1 | | | Adding data related to the MB2 Interface for GCSE | +| | | | 0423 | | | Storing of MME/S4 SGSN identifier in SGW | + +| Change history | | | | | | | +|----------------|--------|---------|--------|---------|-------------|------------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| CT#66 | 23.008 | 12.4.0 | 0424r1 | Rel-12 | 12.5.0 | Storage of eNodeB FTEID for S1U at MME and RNC FTEID for S12 at S4-SGSN | +| | | | 0425 | | | Default APN for Trusted WLAN | +| | | | 0426r1 | | | WLAN offloadability indication stored in S4-SGSN | +| | | | 0427r4 | | | UE Radio Access Capability | +| | | | 0429r4 | | | ProSe parameter storage | +| | | | 0430r1 | | | CN-Assisted Parameters | +| | | | 0431r1 | | | Correction on the scope | +| | | | 0432r2 | | | Restricted RAT Types | +| | | | 0433r1 | | | I-WLAN maintenance | +| CT#67 | 23.008 | 12.5.0 | 0439r1 | Rel-12 | 12.6.0 | Missing PS-and-SMS-Only subscription parameter | +| CT#67 | 23.008 | 12.6.0 | 0437r1 | Rel-13 | 13.0.0 | Storage of MBMS Alternative IP Multicast Distribution Address by MBMS GW and MME | +| CT#68 | 23.008 | 13.0.0 | 0441 | Rel-13 | 13.1.0 | Network Access Mode | +| | | | 0444r3 | | | Storage of access restriction data per PLMN | +| | | | 0449 | | | Remove S2a GRE Keys from ePDG | +| | | | 0442r1 | | | Storage of IMEI for WLAN access | +| | | | 0448r1 | | | IP-SM-GW registration with Diameter | +| CT#69 | 23.008 | 13.1.0 | 0458r1 | Rel-13 | 13.2.0 | Storage of Active Timer for PSM | +| | | | 0450 | | | Storage of Origination Time Stamp parameter | +| | | | 0451r1 | | | Storage of new parameters for extended buffering at the SGW | +| | | | 0452 | | | Storage of new parameter for the "Availability after DDN Failure" monitoring mechanism | +| | | | 0453r1 | | | ProSe Function identifier | +| | | | 0454r2 | | | Storage of IMSI-Group Identifier List | +| | | | 0455r1 | | | Addition of "UE Usage Type" to Subscriber Data | +| | | | 0459r2 | | | Storage of data for monitoring | +| | | | 0460r1 | | | Emergency PDN connection over untrusted WLAN access | +| CT#70 | 23.008 | 13.2.0 | 0461 | Rel-13 | 13.3.0 | Storage of MBMS Cell List | +| | | | 0462r2 | | | Storage information of ProSe-Metadata-Index-Mask | +| | | | 0471r1 | | | The storage of a list of remote UEs | +| | | | 0463r3 | | | Storage of CP parameters | +| | | | 0464r1 | | | Storage of Extended idle mode DRX parameters | +| | | | 0469r2 | | | Storage of DTCI and PNSI | +| | | | 466r1 | | | The storage of UE Radio Capability for Paging Information | +| | | | 0468r1 | | | Allowed WAF and/or WWSF Identities | +| | | | 0472r1 | | | Parameters for paging optimisations | +| | | | 0473r2 | | | Remove the storage of DL Buffering | +| | | | | | | Suggested Packet Count in SGW | +| CT#71 | 23.008 | 13.3.0 | 0483r1 | Rel-13 | 13.4.0 | IP-SW-GW number format | +| | | | 0476r1 | | | User Plane Integrity Protection Indicator | +| | | | 0477r1 | | | Clarification on usage of P and T needs | +| | | | 0489r2 | | | Subscription for allowed services | +| | | | 0484r1 | | | Handover to Non-3GPP Access Not Allowed | +| | | | 0486r1 | | | Addition of NB-IoT radio access type to the Access-Restriction-Dat-Type for Cellular IoT | +| | | | | | | | +| | | | | | | | + +--- + +## Annex B (informative): Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-------|-----------|------|-----|--------------------------------------------------------------------------------------------------------------------|--------| +| 2016-06 | CT#72 | CP-160212 | 0495 | 1 | Correct the storage of Used UE-AMBR | 13.5.0 | +| 2016-06 | CT#72 | CP-160228 | 0490 | 2 | NIDD authorisation update | 13.5.0 | +| 2016-06 | CT#72 | CP-160228 | 0491 | 1 | Add S11-U MME F-TEID and S11-U SGW F-TEID into TS23.008 | 13.5.0 | +| 2016-06 | CT#72 | CP-160228 | 0492 | 1 | PDN type Storage | 13.5.0 | +| 2016-06 | CT#72 | CP-160228 | 0498 | 2 | Address editor's note on ROHC config and security context for small data over control plane | 13.5.0 | +| 2016-06 | CT#72 | CP-160228 | 0499 | 1 | Serving PLMN rate control | 13.5.0 | +| 2016-06 | CT#72 | CP-160228 | 0500 | 1 | APN Rate Control | 13.5.0 | +| 2016-06 | CT#72 | CP-160228 | 0501 | 2 | Not Reachable for NIDD flag | 13.5.0 | +| 2016-06 | CT#72 | CP-160225 | 0496 | 1 | SCEF Realm | 13.5.0 | +| 2016-06 | CT#72 | CP-160237 | 0502 | 1 | Correction on A-MSISDN | 13.5.0 | +| 2016-09 | CT#73 | CP-160572 | 0503 | 1 | PDN-Connection-Restricted flag | 13.6.0 | +| 2016-09 | CT#73 | CP-160423 | 0504 | - | Preferred Data Mode for an SGi PDN connection | 13.6.0 | +| 2016-12 | CT#74 | CP-160660 | 0506 | 1 | Correction on data used for AESE | 13.7.0 | +| 2016-12 | CT#74 | CP-160652 | 0510 | 1 | The storage of IOV_updates counter | 13.7.0 | +| 2016-12 | CT#74 | CP-160679 | 0507 | 1 | IMSI unauthenticated indicator | 14.0.0 | +| 2016-12 | CT#74 | CP-160679 | 0511 | 1 | Handover of Emergency PDN connection between LTE and WLAN | 14.0.0 | +| 2016-12 | CT#74 | CP-160677 | 0509 | 1 | Storage of DCN ID for eDECOR | 14.0.0 | +| 2016-12 | CT#74 | CP-160680 | 0512 | 1 | Storage of Non-IP related data in SGSN | 14.0.0 | +| 2017-03 | CT#75 | CP-170025 | 0521 | - | MPS Priority additions to tabular summary | 14.1.0 | +| 2017-03 | CT#75 | CP-170039 | 0513 | 1 | Enhanced Coverage | 14.1.0 | +| 2017-03 | CT#75 | CP-170043 | 0517 | 1 | Storage of V2X Parameters | 14.1.0 | +| 2017-03 | CT#75 | CP-170049 | 0518 | 2 | Add ERP related data | 14.1.0 | +| 2017-03 | CT#75 | CP-170038 | 0519 | 1 | Subscription parameters for eDRX | 14.1.0 | +| 2017-06 | CT#76 | CP-171016 | 0523 | 1 | Explicit References to IWLan specifications | 14.2.0 | +| 2017-06 | CT#76 | CP-171021 | 0525 | 2 | Correction to description of PDN-Connection-Restricted flag | 14.2.0 | +| 2017-06 | CT#76 | CP-171029 | 0526 | 2 | External-Identifier for Monitoring Event Configuration and External Group Identifier | 14.2.0 | +| 2017-06 | CT#76 | CP-171034 | 0527 | 1 | IMS Trace (ISAT) Reference Updates | 14.2.0 | +| 2017-06 | CT#76 | CP-171043 | 0530 | - | Clarification of APN-Configuration-Profile for non-IP APNs | 15.0.0 | +| 2017-09 | CT#77 | CP-172027 | 0532 | 1 | Access Restriction for NR | 15.1.0 | +| 2017-09 | CT#77 | CP-172018 | 0533 | 1 | Acknowledgements of downlink NAS data PDUs | 15.1.0 | +| 2017-12 | CT#78 | CP-173012 | 0539 | - | Discontinuation of TS 32.252 (I-WLAN Charging) | 15.2.0 | +| 2017-12 | CT#78 | CP-173030 | 0540 | - | NIDD Authorization Subscription Data | 15.2.0 | +| 2017-12 | CT#78 | CP-173035 | 0541 | 1 | Access restriction to unlicensed spectrum as secondary RAT | 15.2.0 | +| 2017-12 | CT#78 | CP-173032 | 0542 | 1 | Storage of PC5-tech for WLAN based ProSe Direct Discovery | 15.2.0 | +| 2018-03 | CT#79 | CP-180026 | 0549 | 1 | Introducing NCGI | 15.3.0 | +| 2018-03 | CT#79 | CP-180026 | 0555 | 2 | Subscriber Data for 5GS | 15.3.0 | +| 2018-03 | CT#79 | CP-180022 | 0556 | 1 | "Service Gap Time" Subscription Data | 15.3.0 | +| 2018-06 | CT#80 | CP-181132 | 0557 | 1 | Storage of data interactions with the UDR | 15.4.0 | +| 2018-06 | CT#80 | CP-181124 | 0558 | - | Storage of subscription data for ciphering keys in HSS to support broadcast of ciphered assistance data in E-UTRAN | 15.4.0 | +| 2018-09 | CT#81 | CP-182084 | 0560 | 6 | Storage information for 5GS | 15.5.0 | +| 2018-09 | CT#81 | CP-182084 | 0564 | 2 | Data related to authentication, ciphering and keying for 5GS | 15.5.0 | +| 2018-09 | CT#81 | CP-182067 | 0562 | 1 | Correction of the UE radio Access Capability size | 15.5.0 | +| 2018-09 | CT#81 | CP-182075 | 0563 | - | External Identifier | 15.5.0 | +| 2018-12 | CT#82 | CP-183082 | 0565 | 1 | Note on additional NFs | 15.6.0 | +| 2018-12 | CT#82 | CP-183082 | 0566 | 1 | Kseaf is no longer transmitted with AV in 5G AKA | 15.6.0 | +| 2018-12 | CT#82 | CP-183082 | 0567 | 1 | Storage of Authentication Subscription data | 15.6.0 | +| 2018-12 | CT#82 | CP-183082 | 0568 | 1 | Storage of Authentication Status | 15.6.0 | +| 2018-12 | CT#82 | CP-183082 | 0569 | 1 | Storage of Authentication Data for steering of roaming | 15.6.0 | +| 2018-12 | CT#82 | CP-183082 | 0570 | 1 | Shared Data Ids for 5G | 15.6.0 | +| 2019-03 | CT#83 | CP-190032 | 0571 | 1 | Correction on referenced clause | 15.7.0 | +| 2019-09 | CT#85 | CP-192126 | 0572 | 2 | Additional RRM Policy Index | 16.0.0 | +| 2019-09 | CT#85 | CP-192126 | 0573 | 1 | Ethernet PDN type in EPS | 16.0.0 | +| 2019-12 | CT#86 | CP-193036 | 0574 | 1 | Adding support for subscription-based access | 16.1.0 | + +| | | | | | | | +|---------|--------|-----------|------|---|-------------------------------------------------------------------------|--------| +| | | | | | restriction in 5GS | | +| 2020-03 | CT#87e | CP-200022 | 0575 | 2 | Introduce support for 5G SRVCC in PS Network Access Mode Data (5GS) | 16.2.0 | +| 2020-03 | CT#87e | CP-200027 | 0576 | 1 | Addition of IAB-Operation Allowed indication to subscriber data | 16.2.0 | +| 2020-03 | CT#87e | CP-200048 | 0577 | - | Correction on subscription based access restriction in unlicensed bands | 16.2.0 | +| 2020-03 | CT#87e | CP-200021 | 0578 | 2 | Addition of UE radio capability ID to subscriber data | 16.2.0 | +| 2020-06 | CT#88e | CP-201071 | 0579 | 1 | Support of inter-RAT HO from NR SA to EN-DC | 16.3.0 | +| 2020-06 | CT#88e | CP-201049 | 0580 | - | Subscription data for NR V2X | 16.3.0 | +| 2020-06 | CT#88e | CP-201048 | 0581 | - | Subscriber data for wireline access devices | 16.3.0 | +| 2020-06 | CT#88e | CP-201032 | 0582 | - | Adding 5GS Broadcast Location Assistance subscriber data | 16.3.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23090/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23090/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69f284069efedf44ad9d8b7bcc250890a3650fc3 --- /dev/null +++ b/marked/Rel-16/23_series/23090/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f6a76210ea8a88aedd5ac765717c4a7d0ff5ce0148fd56c2dcc9e2dff62197d +size 103361 diff --git a/marked/Rel-16/23_series/23090/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23090/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b45444ddc236f93fc6db9dd4f063f69083f88a5d --- /dev/null +++ b/marked/Rel-16/23_series/23090/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa7ce98654e017cbac71e76dfe2075bc954d38b163d341cbc997bf6ea1c01aad +size 82553 diff --git a/marked/Rel-16/23_series/23090/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23090/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efbebfbf64477b1d1aa74d0beee98fac290a35ab --- /dev/null +++ b/marked/Rel-16/23_series/23090/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acb796d1f4a40940d26a7f1cef4f9d9685ae356903fed21d9874dcd6a5336117 +size 80360 diff --git a/marked/Rel-16/23_series/23090/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23090/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcdbd17cd0cbd4e3bdac1d343468b04af80c974b --- /dev/null +++ b/marked/Rel-16/23_series/23090/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fe32b8d0df92ca2cf0cc7965d9f6282f26d03c5504711a647cfbbb9393f46e8 +size 115357 diff --git a/marked/Rel-16/23_series/23090/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23090/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c72384db6721245a8db0943c8b10ad9688faf7c8 --- /dev/null +++ b/marked/Rel-16/23_series/23090/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9429ef9bd76d13d14d6d856abdfc214d3575d4fe0d7f4cc986b093507e191a30 +size 122922 diff --git a/marked/Rel-16/23_series/23090/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23090/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91b69467de80140bb0d36f6a8a2f78c076e25681 --- /dev/null +++ b/marked/Rel-16/23_series/23090/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bfed0423f79f702e27fc421ee41364ff0568ae67148dfc48ef9e9cb03d725218 +size 140918 diff --git a/marked/Rel-16/23_series/23090/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/23_series/23090/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c198f1ff7f741826c1cb84c3be83127fc382efd7 --- /dev/null +++ b/marked/Rel-16/23_series/23090/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:191dafff22815b47f8a7db0966edbd0b4c2c732a536b6900b5b8b7928519ed3d +size 103810 diff --git a/marked/Rel-16/23_series/23090/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23090/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7217ded26e398041ca92a144a5d0cd67e92eb978 --- /dev/null +++ b/marked/Rel-16/23_series/23090/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d0dc04b4a1813a9b9716b28670ae2f023fa6bb754af039339a65663d6719fa0 +size 91829 diff --git a/marked/Rel-16/23_series/23090/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23090/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b51ca7e5f03368e1a494da27f7dc0287a3ab09d --- /dev/null +++ b/marked/Rel-16/23_series/23090/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d42ab2a72cdb034e8cc7cc276c2352e4e983fd9f3e9823d2e0f203a81377f34 +size 98925 diff --git a/marked/Rel-16/23_series/23090/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/23_series/23090/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cc7e273034d38462e563918d9496ab6b4c50c11 --- /dev/null +++ b/marked/Rel-16/23_series/23090/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3581ceefabaea661c3067eab0fd847c41471ddb503606e50d85ec516f1c96ddf +size 71214 diff --git a/marked/Rel-16/23_series/23090/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23090/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce5b3beab5f7572991b6b1f50f1c0ad1365fa60a --- /dev/null +++ b/marked/Rel-16/23_series/23090/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe5cd6c06b7deebc1fdc47586fef97b0f0066bdbeb54cfaee5778d6ba76285df +size 133860 diff --git a/marked/Rel-16/23_series/23090/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/23_series/23090/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8bd9f4cbd6f5fd1e2387b145eb13a519646e9690 --- /dev/null +++ b/marked/Rel-16/23_series/23090/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea4f8eb0860bf6180ed686551cea2a2d68374836dd9f76af404d0b10eec9cd8e +size 73912 diff --git a/marked/Rel-16/23_series/23090/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23090/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8045dee51c8489c3edb70ec5e32c58bd5a1ea279 --- /dev/null +++ b/marked/Rel-16/23_series/23090/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:334e94c43bd0d9eff7515c3a577be4434869ba7acbcaac79c2d195ac2893955a +size 62355 diff --git a/marked/Rel-16/23_series/23090/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/23_series/23090/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0740157a3a8f31fe99bbb3939c51430b5928636e --- /dev/null +++ b/marked/Rel-16/23_series/23090/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2188491f8d2fac49118e9333e1524ce83dfdfc15b16d0ff3298d02004907382 +size 98540 diff --git a/marked/Rel-16/23_series/23090/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23090/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e76dadd932b00ff1f4dba48f6ee95a3982e6159 --- /dev/null +++ b/marked/Rel-16/23_series/23090/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:586f153d1d3c675e7b98cabb62153a3ee05073346c3a4a4dc80b9c3e767cfba2 +size 126907 diff --git a/marked/Rel-16/23_series/23090/ca5566458a134032dd860e88fdaa0d2b_img.jpg b/marked/Rel-16/23_series/23090/ca5566458a134032dd860e88fdaa0d2b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5cc208fe5a7a8671c097abc01ea7ce52ce4a424 --- /dev/null +++ b/marked/Rel-16/23_series/23090/ca5566458a134032dd860e88fdaa0d2b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb8e3170589d344f768af070f0f0623e9622a7f1a16aeacd3d9f1dd69f7c7b54 +size 38244 diff --git a/marked/Rel-16/23_series/23090/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23090/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11f5f162ec5c1a5d15ca770c83a9c5c64b17b238 --- /dev/null +++ b/marked/Rel-16/23_series/23090/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:348560f8920e6c90ff212dc2b2d5f1b76063790e4b7335ca4db402d8f6de1a4c +size 93668 diff --git a/marked/Rel-16/23_series/23090/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23090/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11c92b982f8a9486a9bf09c75485d74541327202 --- /dev/null +++ b/marked/Rel-16/23_series/23090/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d60f782d3e638832e0195a7d4065b0ae3b2ebd7f887fc232a344345658cbd9bf +size 132760 diff --git a/marked/Rel-16/23_series/23090/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/23_series/23090/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a6d319c78d9caaa6fae32390308619f262012fb --- /dev/null +++ b/marked/Rel-16/23_series/23090/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5666fbaca71d00a1cc4ebcfc12e83225e63c89b394852daedad3976c51c441a +size 121261 diff --git a/marked/Rel-16/23_series/23090/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23090/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f915b2fe6b05cb84083a9025707e5d6257f0231a --- /dev/null +++ b/marked/Rel-16/23_series/23090/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b49327e051091c7fdc5386595f78b4298a5b49f99753cca5f544b8bf60df79d +size 71474 diff --git a/marked/Rel-16/23_series/23090/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23090/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8fa3647da7eb6e005991adffe01483076ff8dae --- /dev/null +++ b/marked/Rel-16/23_series/23090/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07713c9f46662d900f57c4072b12f570b31baa357edfea16f79a8edea0b9e3d6 +size 82006 diff --git a/marked/Rel-16/23_series/23090/raw.md b/marked/Rel-16/23_series/23090/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..c33641cc691c0f4ddfd0aa6716bb0da4c05e8658 --- /dev/null +++ b/marked/Rel-16/23_series/23090/raw.md @@ -0,0 +1,1214 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Abbreviations ..... | 6 | +| 4 Cross phase compatibility ..... | 6 | +| 5 Network initiated unstructured supplementary service..... | 6 | +| 5.1 Handling of network initiated USSD ..... | 6 | +| 5.2 Functions and information flows..... | 6 | +| 5.2.1 Invoking unstructured SS operation from the HLR ..... | 6 | +| 5.2.2 Invoking unstructured SS operation from the VLR ..... | 7 | +| 5.2.3 Invoking unstructured SS operation from the MSC ..... | 7 | +| 5.2.4 Forwarding USSD operations..... | 7 | +| 5.2.5 Handling of unstructured SS operation at the MS..... | 8 | +| 5.3 Information stored in the HLR..... | 15 | +| 5.4 Information stored in the VLR..... | 15 | +| 5.5 Handover ..... | 15 | +| 5.6 Cross-phase compatibility ..... | 16 | +| 6 Mobile initiated unstructured supplementary service data ..... | 16 | +| 6.1 Handling of mobile initiated USSD ..... | 16 | +| 6.2 Functions and information flows..... | 16 | +| 6.2.1 Handling of USSD request at MS ..... | 16 | +| 6.2.2 Handling of USSD request at MSC..... | 17 | +| 6.2.3 Handling of USSD request at VLR ..... | 17 | +| 6.2.4 Handling of USSD request at HLR ..... | 17 | +| 6.2.5 Processing the USSD request ..... | 17 | +| 6.3 Information stored in the HLR..... | 30 | +| 6.4 Information stored in the VLR..... | 31 | +| 6.5 Handover ..... | 31 | +| 6.6 Cross-phase compatibility ..... | 31 | +| Annex A (informative): Change history..... | 32 | + +# --- Foreword + +This Technical Specification has been produced by the 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. + +# 1 Scope + +The present document gives the stage 2 description of Unstructured Supplementary Service Data (USSD). + +The unstructured supplementary service data (USSD) mechanism allows the Mobile Station (MS) user and a PLMN operator defined application to communicate in a way which is transparent to the MS and to intermediate network entities. The mechanism allows development of PLMN specific supplementary services. The following diagram shows how handling of USSD is carried out, independently of the applications. + +![Diagram illustrating the handling of USSD across network entities: USER, MS, MSC, VLR, and HLR. The USER is connected to the MS. The MS contains an MMI and a USSD Handler. The MSC, VLR, and HLR each contain Applications and a USSD Handler. A horizontal line connects the USSD Handler in the MS to the USSD Handler in the MSC, which is then connected to the USSD Handler in the VLR, which is finally connected to the USSD Handler in the HLR.](ca5566458a134032dd860e88fdaa0d2b_img.jpg) + +``` +graph LR; USER[USER] --- MS[MS]; subgraph MS; MMI[MMI] --- USSD_H[USSD Handler]; end; subgraph MSC; Apps1[Applications] --- USSD_H1[USSD Handler]; end; subgraph VLR; Apps2[Applications] --- USSD_H2[USSD Handler]; end; subgraph HLR; Apps3[Applications] --- USSD_H3[USSD Handler]; end; USSD_H --- USSD_H1 --- USSD_H2 --- USSD_H3; +``` + +Diagram illustrating the handling of USSD across network entities: USER, MS, MSC, VLR, and HLR. The USER is connected to the MS. The MS contains an MMI and a USSD Handler. The MSC, VLR, and HLR each contain Applications and a USSD Handler. A horizontal line connects the USSD Handler in the MS to the USSD Handler in the MSC, which is then connected to the USSD Handler in the VLR, which is finally connected to the USSD Handler in the HLR. + +**Figure 1.1: Handling of USSD** + +The present document defines the requirements for handling USSD at the MS and network entities. It does not include specification of particular applications, nor does it specify how a particular application is selected. Where more than one application exists at a network entity, routing of messages to the correct application is carried out by the USSD handler. The MMI for USSD is specified in TS 22.030 and TS 22.090. The alphabet indicator and the data coding scheme are defined in TS 23.038. + +USSD may be initiated by the MS user, or by the network in the following ways: + +- Network initiated USSD (clause 1); +- Mobile initiated USSD (clause 2). + +# 2 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 22.030: "Man-Machine Interface (MMI) of the User Equipment (UE)". +- [3] 3GPP TS 22.090: "Unstructured Supplementary Service Data (USSD) - Stage 1". +- [4] 3GPP TS 23.038: "Alphabets and language-specific information". + +# --- 3 Abbreviations + +In addition to those below, abbreviations used in the present document are listed in TR 21.905 [1]. + +| | | +|------|-----------------------------------------| +| AI | Application Initiated | +| MI | Mobile Initiated | +| USSD | Unstructured Supplementary Service Data | + +# --- 4 Cross phase compatibility + +The Phase 1 series of GSM specifications defined the signalling protocol which may be used, but they did not specify the operation of USSD as a service. + +The main body of the present document assumes that the MS and all network entities comply with this phase of USSD. In order to minimize any possible problems between a Phase 1 implementation of USSD and this phase, subclauses 5.6 and 6.6 define the additional requirements for when one or more entity complies with the Phase 1 USSD specification for network initiated and mobile initiated USSD respectively. + +# --- 5 Network initiated unstructured supplementary service + +## 5.1 Handling of network initiated USSD + +The network (MSC, VLR or HLR) can at any time send a USSD operation towards an MS. This operation may be either a request (asking the MS to provide information) or a notification (requiring no information in the response from the MS). No prior provision of USSD is required, although provision of services which make use of USSD may be required. All USSD requests, notifications and responses (except responses to notifications) contain the USSD string, an alphabet indicator and language indicator. + +## 5.2 Functions and information flows + +The following text describes the handling of network initiated USSD. Diagrammatic representations are as follows: + +| | | +|------------|-----------------------------------------------------------| +| Figure 5.1 | SDL for USSD invocation (HLR, VLR, MSC); | +| Figure 5.2 | SDL for forwarding of USSD operations (VLR, MSC); | +| Figure 5.3 | SDL for MS; | +| Figure 5.4 | Information flow for successful single USSD request; | +| Figure 5.5 | Information flow for successful single USSD notification; | +| Figure 5.6 | Information flow for successful multiple USSD requests; | +| Figure 5.7 | Information flow for failed USSD request. | + +### 5.2.1 Invoking unstructured SS operation from the HLR + +When an application in the HLR is to send a USSD request or notification to an MS, it shall set up a transaction to the VLR where the subscriber is currently registered and send the operation to the VLR. It shall then await a response. The HLR is responsible for controlling the transaction, and shall therefore normally release the transaction when it receives a response from the VLR. The HLR may also release the transaction before receiving a response if necessary (e.g. if an application timer expires). + +If an application in the HLR needs to send further operations to the same MS as part of the same application, it may continue to use the same transaction until all operations are completed (see figure 5.6). If a different transaction is to be used for a subsequent operation, the HLR shall release the first transaction before starting the next. + +If the VLR releases the transaction at any time (e.g. due to user clearing), the HLR shall inform the application and terminate the USSD operation. + +See subclause 5.2.4 for forwarding of an HLR invoked operation by the VLR and MSC. + +### 5.2.2 Invoking unstructured SS operation from the VLR + +When an application in the VLR is to send a USSD request or notification to an MS, it shall set up a transaction to the MSC where the subscriber is currently registered and send the operation to the MSC. It shall then await a response. The VLR is responsible for controlling the transaction, and shall therefore normally release the transaction when it receives a response from the MSC. The VLR may also release the transaction before receiving a response if necessary (e.g. if an application timer expires). + +If an application in the VLR needs to send further operations to the same MS as part of the same application, it may continue to use the same transaction until all operations are completed. If a different transaction is to be used for a subsequent operation, the VLR shall release the first transaction before starting the next. + +See subclause 5.2.4 for forwarding of a VLR invoked operation by the MSC. + +If the MSC releases the transaction at any time (e.g. due to the user clearing), the VLR shall inform the application and terminate the USSD operation. + +### 5.2.3 Invoking unstructured SS operation from the MSC + +When an application in the MSC is to send a USSD request or notification to an MS, it shall set up a transaction to the MS where the subscriber is currently registered and send the operation to the MS. It shall then await a response. The MSC is responsible for controlling the transaction, and shall therefore normally release the transaction when it receives a response from the MS. The MSC may also release the transaction before receiving a response if necessary (e.g. if an application timer expires). + +If an application in the MSC needs to send further operations to the same MS as part of the same application, it may continue to use the same transaction until all operations are completed. If a different transaction is to be used for a subsequent operation, the VLR shall release the first transaction before starting the next. + +If the MS releases the transaction at any time (e.g. due to the user clearing), the MSC shall inform the application and terminate the USSD operation. + +NOTE: MSC invoked USSD is only likely to be used for call related operations, where the application is controlling a call to or from the MS. + +### 5.2.4 Forwarding USSD operations + +The VLR may any time receive a USSD operation from the HLR. If the subscriber can be contacted, the VLR shall set up a transaction to the MSC and forward the operation unchanged. Any further information exchange between the HLR and MSC shall be transparent to the VLR. When one transaction is released, the VLR shall release the other. + +The MSC may at any time receive an USSD operation from the VLR. If the subscriber can be contacted, the MSC shall set up a transaction to the MS and forward the operation unchanged. Any further information exchange between the VLR and MS shall be transparent to the MSC. When one transaction is released, the MSC shall release the other. + +### 5.2.5 Handling of unstructured SS operation at the MS + +The MS may at any time receive a USSD operation (request or notification) from the MSC. + +If the MS receives a USSD transaction while another USSD transaction (network or mobile initiated) or a non-call related supplementary service transaction is in progress, the MS shall reject the new transaction. + +If the MS receives a USSD operation when it is in a state where the MMI required is not possible (e.g. during dialling) it shall reject the operation. + +If the MS does not support the alphabet indicated in the USSD operation, it shall inform the network. + +If the MS is in a state where it can handle the operation, it shall process the operation as follows: + +- The MS shall analyse the data coding scheme and decides whether the USSD operation is MMI mode or application mode. See 3GPP TS 22. 030 [2] for details of codes. + +If the data coding scheme corresponds to the MMI mode : + +- For a USSD request, the MS shall display the text provided and await user input. If the user enters a response, the MS shall return the response to the MSC, maintaining the transaction. If the user requests release of the transaction, the MS shall release the transaction. +- For a USSD notification, the MS shall display the text provided and send back a response. + +If the data coding schemes corresponds to the application mode : + +- For a USSD request, the MS shall pass the message to the application addressed in the ME, SIM or TE, and await application response . If the application responds, the MS shall pass the response to the MSC, maintaining the transaction. If the application releases the transaction, the MS shall release the transaction. +- For a USSD notification, the MS shall pass the message to the application addressed in the ME, SIM or TE, and send back a response. + +After sending the response to a USSD operation, the MS shall wait for the network to release the transaction. If, while awaiting this release, the MS receives any further USSD operations, it shall process them in the normal way. + +![State transition diagram for Process USSD_NI1. It shows two main entry points: 'USSD notify' and 'USSD request'. Both lead to 'MS reachable' decision diamonds. If 'no', they lead to 'RELEASE (error)' and then 'idle'. If 'yes', they lead to 'USSD notify' and 'USSD request' respectively, which then merge into 'NW wait user response'. From 'NW wait user response', four paths emerge: 'error' (leading to 'error' and then 'wait for application'), 'USSD response' (leading to 'USSD response' and then 'wait for application'), 'release' (leading to 'release' and then 'idle'), and 'release' (leading to 'release' and then 'idle'). From 'wait for application', four paths emerge: 'USSD notify' (leading to 'USSD notify' and then 'NW wait user response'), 'USSD request' (leading to 'USSD request' and then 'NW wait user response'), 'release' (leading to 'release' and then 'idle'), and 'release' (leading to 'release' and then 'idle').](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +**Process USSD\_NI1** + +390\_51(1) + +**INPUTS AND OUTPUTS** + +Source/destination of messages shown to/from the right is the application. + +Source/destination of messages shown to/from the left depends on the entity being described, as follows: + +| Entity | To/From | +|--------|---------| +| HLR | VLR | +| VLR | MSC | +| MSC | MS | + +State transition diagram for Process USSD\_NI1. It shows two main entry points: 'USSD notify' and 'USSD request'. Both lead to 'MS reachable' decision diamonds. If 'no', they lead to 'RELEASE (error)' and then 'idle'. If 'yes', they lead to 'USSD notify' and 'USSD request' respectively, which then merge into 'NW wait user response'. From 'NW wait user response', four paths emerge: 'error' (leading to 'error' and then 'wait for application'), 'USSD response' (leading to 'USSD response' and then 'wait for application'), 'release' (leading to 'release' and then 'idle'), and 'release' (leading to 'release' and then 'idle'). From 'wait for application', four paths emerge: 'USSD notify' (leading to 'USSD notify' and then 'NW wait user response'), 'USSD request' (leading to 'USSD request' and then 'NW wait user response'), 'release' (leading to 'release' and then 'idle'), and 'release' (leading to 'release' and then 'idle'). + +**Figure 5.1: Network initiated USSD invoked at HLR, VLR or MSC** + +![State transition diagram for Process USSD_NI2. The diagram shows the flow of USSD messages between a network entity (VLR or MSC) and a mobile station (MS). It starts in an 'idle' state. From 'idle', a 'USSD notify' or 'USSD request' can be received. Each leads to an 'MS reachable' decision. If 'no', a 'RELEASE (error)' is sent and the state returns to 'idle'. If 'yes', the message is forwarded ('USSD notify' or 'USSD request') to a 'forwarding wait user' state. From 'forwarding wait user', four responses are possible: 'error', 'USSD response', 'release', or 'release'. 'error' leads to an 'error' state and back to 'idle'. 'USSD response' leads to a 'USSD response' state and then to 'forwarding wait application'. 'release' leads to a 'release' state and then to 'idle'. 'forwarding wait application' leads to four states: 'USSD notify', 'USSD request', 'release', or 'release'. 'USSD notify' and 'USSD request' lead to their respective states and then back to 'forwarding wait user'. 'release' leads to a 'release' state and then to 'idle'.](e6df2733626a85205c1db682e6259c46_img.jpg) + +**Process USSD\_NI2** + +390\_52(1) + +**INPUTS AND OUTPUTS** + +Source/destination of messages depends on the entity being described, as follows: + +| Entity | Left | Right | +|--------|------|-------| +| VLR | MSC | HLR | +| MSC | MS | VLR | + +``` +stateDiagram-v2 + [*] --> idle + idle --> USSD_notify_in {USSD notify} + idle --> USSD_request_in {USSD request} + USSD_notify_in --> MS_reachable_notify {MS reachable} + USSD_request_in --> MS_reachable_request {MS reachable} + MS_reachable_notify -- no --> RELEASE_error_notify [RELEASE (error)] + MS_reachable_notify -- yes --> USSD_notify_out {USSD notify} + MS_reachable_request -- no --> RELEASE_error_request [RELEASE (error)] + MS_reachable_request -- yes --> USSD_request_out {USSD request} + RELEASE_error_notify --> idle + RELEASE_error_request --> idle + USSD_notify_out --> forwarding_wait_user {forwarding wait user} + USSD_request_out --> forwarding_wait_user + forwarding_wait_user --> error_in {error} + forwarding_wait_user --> USSD_response_out {USSD response} + forwarding_wait_user --> release_out1 {release} + forwarding_wait_user --> release_out2 {release} + error_in --> error_out {error} + error_out --> idle + USSD_response_out --> USSD_response_in {USSD response} + USSD_response_in --> forwarding_wait_application {forwarding wait application} + release_out1 --> release_in1 {release} + release_out2 --> release_in2 {release} + release_in1 --> idle + release_in2 --> idle + forwarding_wait_application --> USSD_notify_out2 {USSD notify} + forwarding_wait_application --> USSD_request_out2 {USSD request} + forwarding_wait_application --> release_out3 {release} + forwarding_wait_application --> release_out4 {release} + USSD_notify_out2 --> USSD_notify_in2 {USSD notify} + USSD_request_out2 --> USSD_request_in2 {USSD request} + USSD_notify_in2 --> forwarding_wait_user + USSD_request_in2 --> forwarding_wait_user + release_out3 --> release_in3 {release} + release_out4 --> release_in4 {release} + release_in3 --> idle + release_in4 --> idle +``` + +State transition diagram for Process USSD\_NI2. The diagram shows the flow of USSD messages between a network entity (VLR or MSC) and a mobile station (MS). It starts in an 'idle' state. From 'idle', a 'USSD notify' or 'USSD request' can be received. Each leads to an 'MS reachable' decision. If 'no', a 'RELEASE (error)' is sent and the state returns to 'idle'. If 'yes', the message is forwarded ('USSD notify' or 'USSD request') to a 'forwarding wait user' state. From 'forwarding wait user', four responses are possible: 'error', 'USSD response', 'release', or 'release'. 'error' leads to an 'error' state and back to 'idle'. 'USSD response' leads to a 'USSD response' state and then to 'forwarding wait application'. 'release' leads to a 'release' state and then to 'idle'. 'forwarding wait application' leads to four states: 'USSD notify', 'USSD request', 'release', or 'release'. 'USSD notify' and 'USSD request' lead to their respective states and then back to 'forwarding wait user'. 'release' leads to a 'release' state and then to 'idle'. + +Figure 5.2: Network initiated USSD forwarding at VLR or MSC + +![SDL Flowchart for Process USSD_NI3: Network initiated USSD at MS.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +**Process USSD\_NI3** 390\_53(1) + +INPUTS AND OUTPUTS + +Source/destination of messages shown to/from the left is the MS MMI. + +Source/destination of messages shown to/from the right is the network. + +**Detailed Diagram Description:** + The flowchart describes the **Process USSD\_NI3** starting from an **idle** state. + Two main branches originate from the network side: + + +- Branch 1 (USSD notify):** Leads to checks for 'alphabet supported' (no -> connector 1), 'valid state' (no -> connector 1), and 'Mode = MMI mode'. + - If 'Mode = MMI mode' is yes: It sends 'USSD notify' to MS MMI, then 'USSD notify' to the network, and ends at connector 1. + - If 'Mode = MMI mode' is no: It checks 'Mode = application mode?'. If yes, it goes to an **error** state and then **wait network action**. If no, it goes to connector 3. +- Branch 2 (USSD request):** Leads to checks for 'alphabet supported' (no -> connector 2) and 'valid state' (no -> connector 2). + - If 'Mode = MMI mode' is yes: It sends 'USSD request' to MS MMI, enters state **MS wait user response**, receives 'USSD response' from MMI, sends 'USSD response' to network, enters **wait network action**, and finally sends/receives 'USSD notify'/'USSD request' before ending at connector 1 or 2. + - If 'Mode = MMI mode' is no: It checks 'Mode = application mode?'. If yes, it sends 'USSD request' to the application (note: 'Send to the application in the MS'), enters **MS wait application response**, and handles various 'release' signals before returning to **idle**. + + Connectors 1 and 2 return the process to the **idle** state. Connector 3 leads to a 'USSD notify' output to the MMI. + +SDL Flowchart for Process USSD\_NI3: Network initiated USSD at MS. + +Figure 5.3: Network initiated USSD at MS + +![Sequence diagram showing information flow for USSD request (Single Operation) between MS, MSC, VLR, and HLR.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +The diagram illustrates the information flow for a USSD request (Single Operation) across four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence is divided into three initiation scenarios: + +- HLR initiated:** + - The HLR sends a **USSD request** to the VLR. + - The VLR forwards the **USSD request** to the MSC. + - The MSC sends a **USSD request** to the MS. + - The MS returns a **USSD response** to the MSC. + - The MSC forwards the **USSD response** to the VLR. + - The VLR sends a **Release** message to the HLR. + - The HLR sends a **Release** message to the MSC. + - The MSC sends a **Release** message to the MS. +- VLR initiated:** + - The VLR sends a **USSD request** to the MSC. + - The MSC sends a **USSD request** to the MS. + - The MS returns a **USSD response** to the MSC. + - The MSC forwards the **USSD response** to the VLR. + - The VLR sends a **Release** message to the MSC. + - The MSC sends a **Release** message to the MS. +- MSC initiated:** + - The MSC sends a **USSD request** to the MS. + - The MS returns a **USSD response** to the MSC. + - The MSC sends a **Release** message to the MS. + +Sequence diagram showing information flow for USSD request (Single Operation) between MS, MSC, VLR, and HLR. + +Figure 5.4: Information flow for USSD request (Single Operation) + +![Sequence diagram showing information flow for USSD notification (Single Operation) between MS, MSC, VLR, and HLR.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + + Note left of MS: HLR initiated + HLR->>VLR: USSD notify + VLR->>MSC: USSD notify + MSC->>MS: USSD notify + MS->>MSC: USSD response + MSC->>VLR: USSD response + VLR->>HLR: USSD response + MSC->>VLR: Release + VLR->>MS: Release + + Note left of MS: VLR initiated + VLR->>MSC: USSD notify + MSC->>MS: USSD notify + MS->>MSC: USSD response + MSC->>VLR: USSD response + MSC->>VLR: Release + VLR->>MS: Release + + Note left of MS: MSC initiated + MSC->>MS: USSD notify + MS->>MSC: USSD response + MSC->>MS: Release +``` + +The diagram illustrates the information flow for a USSD notification (Single Operation) across four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). It is divided into three sections based on the initiator: HLR initiated, VLR initiated, and MSC initiated. In the HLR initiated section, the HLR sends a USSD notify to the VLR, which then forwards it to the MSC and then to the MS. The MS sends a USSD response back to the MSC, which is then forwarded by the MSC to the VLR and finally to the HLR. A Release message is sent from the MSC to the VLR, which then forwards it to the MS. In the VLR initiated section, the VLR sends a USSD notify to the MSC, which then forwards it to the MS. The MS sends a USSD response back to the MSC, which is then forwarded by the MSC to the VLR. A Release message is sent from the MSC to the VLR, which then forwards it to the MS. In the MSC initiated section, the MSC sends a USSD notify to the MS. The MS sends a USSD response back to the MSC. A Release message is sent from the MSC to the MS. + +Sequence diagram showing information flow for USSD notification (Single Operation) between MS, MSC, VLR, and HLR. + +Figure 5.5: Information flow for USSD notification (Single Operation) + +![Sequence diagram showing information flow for HLR initiated USSD request between MS, MSC, VLR, and HLR.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The diagram is a sequence diagram with four lifelines: MS, MSC, VLR, and HLR. The interaction consists of two identical USSD request-response cycles, separated by a vertical ellipsis. In the first cycle, the HLR sends a 'USSD request' to the VLR, which then forwards it to the MSC. The MSC sends a 'USSD request' to the MS. The MS responds with a 'USSD response' to the MSC, which is then forwarded by the MSC to the VLR, and finally by the VLR to the HLR. The HLR sends a 'Release' message to the VLR, which is forwarded by the VLR to the MSC, and finally by the MSC to the MS. The second cycle follows the same pattern. The 'Release' message is the last message in the sequence. + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: First USSD Request + HLR->>VLR: USSD request + VLR->>MSC: USSD request + MSC->>MS: USSD request + MS-->>MSC: USSD response + MSC-->>VLR: USSD response + VLR-->>HLR: USSD response + HLR->>VLR: Release + VLR-->>MSC: Release + MSC-->>MS: Release + Note right of HLR: Second USSD Request + HLR->>VLR: USSD request + VLR->>MSC: USSD request + MSC->>MS: USSD request + MS-->>MSC: USSD response + MSC-->>VLR: USSD response + VLR-->>HLR: USSD response + HLR->>VLR: Release + VLR-->>MSC: Release + MSC-->>MS: Release +``` + +Sequence diagram showing information flow for HLR initiated USSD request between MS, MSC, VLR, and HLR. + +**Figure 5.6: Information flow for HLR initiated USSD request (Multiple Operation On Same Transaction)** + +![Sequence diagram showing information flow for a failed USSD request between MS, MSC, VLR, and HLR.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + + Note left of MS: VLR cannot contact subscriber + Note left of MSC: MSC cannot contact subscriber + Note left of MS: Error detected at MS + Note left of MS: MS clears transaction + + HLR->>VLR: USSD request + VLR-->>HLR: Error + MSC->>VLR: USSD request + VLR-->>HLR: Error + MSC-->>VLR: Error + MSC->>VLR: USSD request + VLR-->>HLR: Error + MSC-->>VLR: Error + MSC->>VLR: USSD request + VLR-->>HLR: Error + MSC-->>VLR: Error + MSC->>VLR: USSD request + VLR-->>HLR: Release + MSC-->>VLR: Release + MSC->>MS: USSD request + MS-->>MSC: Error + MSC-->>MS: Release + +``` + +The sequence diagram illustrates the information flow for a failed USSD request. It involves four lifelines: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The process starts with the HLR sending a USSD request to the VLR, which returns an error. The MSC then sends a USSD request to the VLR, which again returns an error. The MSC receives an error from the VLR and sends another USSD request to the VLR, which returns an error. The MSC receives another error from the VLR and sends a USSD request to the VLR, which returns a release message. The MSC receives the release message from the VLR and sends a USSD request to the MS, which returns an error. The MSC receives the error from the MS and sends a release message to the MS. The diagram also includes notes indicating that the VLR cannot contact the subscriber, the MSC cannot contact the subscriber, an error is detected at the MS, and the MS clears the transaction. + +Sequence diagram showing information flow for a failed USSD request between MS, MSC, VLR, and HLR. + +Figure 5.7: Information flow for failed USSD request + +## 5.3 Information stored in the HLR + +The HLR shall not store any information specific to the use of USSD, although information may be stored for services which are offered by USSD applications. + +## 5.4 Information stored in the VLR + +The VLR shall not store any information specific to the use of USSD, although information may be stored for services which are offered by USSD applications. + +## 5.5 Handover + +Handover will have no impact on the operation of this service. + +## 5.6 Cross-phase compatibility + +Network initiated USSD shall not be permitted if the MS or any network entity involved in the operation is of Phase 1. If, when setting up a transaction, a network entity discovers that the other end is of Phase 1, it shall reject the request and release the transaction being set up. + +# --- 6 Mobile initiated unstructured supplementary service data + +## 6.1 Handling of mobile initiated USSD + +A MS can at any time initiate a USSD request to the network. No prior provision of the service is required, although provisioning of services which make use of USSD may be required. All USSD messages (requests and responses), contain the USSD string, an alphabet indicator and language indicator. + +## 6.2 Functions and information flows + +The following text describes the handling of mobile network initiated USSD. Diagrammatic representations are as follows: + +- Figure 6.1 SDL, request from user at MS; +- Figure 6.2 SDL, request from MS at MSC; +- Figure 6.3 SDL, request from application at MSC; +- Figure 6.4 SDL, request from MSC at VLR; +- Figure 6.5 SDL, request from application at VLR; +- Figure 6.6 SDL, request from VLR at HLR; +- Figure 6.7 Information flow, no further information required; +- Figure 6.8 Information flow, further information required; +- Figure 6.9 Information flow for failed USSD request. + +### 6.2.1 Handling of USSD request at MS + +When the user or the application in the MS makes a request which the MS determines is to make use of USSD, the MS shall set up a transaction to the network, send the request to the MSC and await a response. When the MS receives the response, it shall display the information contained to the user or relay the message to the application in the MS. + +While awaiting the response, the MS may receive a network initiated USSD request or notification on the same transaction. If this occurs, the MS shall process that operation (see section 1) and continue to await the response to the mobile initiated request. + +If, when the MS determines that a user request is to make use of USSD, the MS is already involved in a USSD or a non-call related supplementary service transaction, the MS shall reject the request. + +### 6.2.2 Handling of USSD request at MSC + +When an MSC receives a USSD request containing an HPLMN service code, it shall set up a transaction to the VLR and forward the request unchanged. If this forwarding fails, an error shall be returned to the MS. The MSC shall be transparent to any further requests or responses (in either direction) for that transaction, passing them between the MS and VLR without taking any action. When one transaction is released (MS-MSC or MSC-VLR), the MSC shall release the other. + +If an HPLMN service code is not included, the MSC shall process the request locally (see section 6.2.5). + +If the MSC does not support the alphabet used in a USSD request, it shall set up a transaction to the VLR and forward the request unchanged, in the same way as when a HPLMN service code is received. + +### 6.2.3 Handling of USSD request at VLR + +When a VLR receives a USSD request containing an HPLMN service code and the user is not in the HPLMN, it shall set up a transaction to the HLR and forward the request unchanged. If this forwarding fails, an error shall be returned to the MS. The VLR shall be transparent to any further requests or responses (in either direction) for that transaction, passing them between the MSC and HLR without taking any action. When one transaction is released (MSC-VLR or VLR-HLR), the VLR shall release the other. + +If an HPLMN service code is not included, or the user is in the HPLMN, the VLR shall process the request locally (see subclause 6.2.5). + +If the VLR does not support the alphabet used in a USSD request, it shall set up a transaction to the HLR and forward the request unchanged, in the same way as when a HPLMN service code is received and the user is not in the HPLMN. + +### 6.2.4 Handling of USSD request at HLR + +An HLR shall always process a USSD request locally (see subclause 6.2.5). + +If the HLR does not support the alphabet used in a USSD request, it shall inform the MS and release the transaction. + +### 6.2.5 Processing the USSD request + +When a network entity is to process a USSD request locally, the request shall be handled by an appropriate application. The location, nature and contents of USSD applications is, by definition, service provider and network operator dependent, but may include: + +- Setting up or releasing signalling and/or speech channels; +- Passing the request to another network entity (unchanged or changed); +- Passing a different USSD request to another network entity; +and/or +- Requesting further information from the MS (one or more times). + +Upon completion of handling the request, the network entity shall respond to the request and release the transaction. + +![State transition diagram for Mobile Initiated USSD (USSD_MI1). The process starts at 'idle', receives a 'USSD request' from the application/user, enters 'wait network response', then branches into 'USSD response' (idle), 'USSD notify' (wait network response), 'USSD request' (MI wait user response), 'release' (idle), or 'error' (idle). The 'MI wait user response' state further branches into 'USSD response' (wait network response), 'release' (idle), or 'error' (idle).](4356776ca004ecba5d599667a155d7d4_img.jpg) + +Process USSD\_MI1 390\_61(1) + +``` +stateDiagram-v2 + [*] --> idle + note left of USSD_request: Sent by the application or entered by the user + idle --> USSD_request + USSD_request --> USSD_request + USSD_request --> wait_network_response + state "wait network response" as wait_network_response + wait_network_response --> USSD_response + wait_network_response --> USSD_notify + wait_network_response --> USSD_request + wait_network_response --> release + wait_network_response --> release + wait_network_response --> error + USSD_response --> USSD_response + USSD_response --> idle + USSD_notify --> USSD_notify + USSD_notify --> USSD_response + USSD_notify --> wait_network_response + USSD_request --> USSD_request + USSD_request --> MI_wait_user_response + MI_wait_user_response --> USSD_response + MI_wait_user_response --> release + MI_wait_user_response --> release + MI_wait_user_response --> error + USSD_response --> USSD_response + USSD_response --> wait_network_response + release --> release + release --> idle + release --> release + release --> error + error --> error + error --> idle +``` + +**INPUTS AND OUTPUTS** + +Source/destination of messages shown to/from the left is the MS MMI or the application in the MS. + +Source/destination of messages shown to/from the right is the MSC. + +State transition diagram for Mobile Initiated USSD (USSD\_MI1). The process starts at 'idle', receives a 'USSD request' from the application/user, enters 'wait network response', then branches into 'USSD response' (idle), 'USSD notify' (wait network response), 'USSD request' (MI wait user response), 'release' (idle), or 'error' (idle). The 'MI wait user response' state further branches into 'USSD response' (wait network response), 'release' (idle), or 'error' (idle). + +Figure 6.1: Mobile initiated USSD at MS + +![Flowchart for Process USSD_MI2. It starts with 'idle', followed by 'USSD request'. A decision 'alphabet supported' has a 'no' path leading to 'MI wait VLR response' and a 'yes' path to 'HPLMN service code'. 'HPLMN service code' has a 'no' path to 'USSD request (appl)' and a 'yes' path to 'USSD request (VLR)'. 'USSD request (VLR)' leads to 'MI wait VLR response' and 'USSD request (appl)' leads to 'MSC application processing'.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Process USSD\_MI2 + +390\_621(3) + +**INPUTS AND OUTPUTS** + +Source/destination of messages shown to/from the left is the MS. + +Source/destination of messages shown to/from the right is either the VLR or the application (as indicated). + +``` +graph TD; idle([idle]) --> UR{USSD request}; UR --> AS{alphabet supported}; AS -- no --> MV[MI wait VLR response]; AS -- yes --> HSC{HPLMN service code}; HSC -- no --> UA{USSD request (appl)}; HSC -- yes --> UV{USSD request (VLR)}; UV --> MV; UA --> MP[MSC application processing]; +``` + +Flowchart for Process USSD\_MI2. It starts with 'idle', followed by 'USSD request'. A decision 'alphabet supported' has a 'no' path leading to 'MI wait VLR response' and a 'yes' path to 'HPLMN service code'. 'HPLMN service code' has a 'no' path to 'USSD request (appl)' and a 'yes' path to 'USSD request (VLR)'. 'USSD request (VLR)' leads to 'MI wait VLR response' and 'USSD request (appl)' leads to 'MSC application processing'. + +Figure 6.2 (sheet 1 of 3): Mobile initiated USSD at MSC + +![State transition diagram for Process USSD_MI2. The diagram shows two main state transition paths starting from 'MI wait VLR response'. The first path leads to 'USSD response (VLR)' and then to 'idle'. The second path leads to 'MI wait user response (for VLR)', which then branches into 'USSD response', 'release', 'release (VLR)', and 'error'. 'USSD response' leads to 'USSD response (VLR)' and then to 'MI wait VLR response'. 'release' and 'release (VLR)' both lead to 'idle'. 'error' leads to 'error (VLR)' and then to 'MI wait VLR response'.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +Process USSD\_MI2 + +390\_622(3) + +``` +stateDiagram-v2 + [*] --> MI_wait_VLR_response : MI wait VLR response + MI_wait_VLR_response --> USSD_response_VLR_1 : USSD response (VLR) + MI_wait_VLR_response --> USSD_request_VLR : USSD request (VLR) + MI_wait_VLR_response --> USSD_notify_VLR : USSD notify (VLR) + MI_wait_VLR_response --> release_1 : release + MI_wait_VLR_response --> release_VLR_1 : release (VLR) + MI_wait_VLR_response --> error_VLR_1 : error (VLR) + + USSD_response_VLR_1 --> USSD_response : USSD response + USSD_response --> idle_1 : idle + + USSD_request_VLR --> USSD_request : USSD request + USSD_notify_VLR --> USSD_notify : USSD notify + USSD_request --> MI_wait_user_response : MI wait user response (for VLR) + USSD_notify --> MI_wait_user_response + + release_1 --> release_VLR : release (VLR) + release_VLR_1 --> release_2 : release + error_VLR_1 --> error : error + release_VLR --> idle_2 : idle + release_2 --> idle_2 + error --> error_VLR : error (VLR) + error_VLR --> MI_wait_VLR_response_2 : MI wait VLR response + + MI_wait_user_response --> USSD_response_2 : USSD response + MI_wait_user_response --> release_3 : release + MI_wait_user_response --> release_VLR_2 : release (VLR) + MI_wait_user_response --> error_2 : error + + USSD_response_2 --> USSD_response_VLR_2 : USSD response (VLR) + USSD_response_VLR_2 --> MI_wait_VLR_response_2 + + release_3 --> release_VLR_3 : release (VLR) + release_VLR_3 --> release_4 : release + release_4 --> idle_2 + + error_2 --> error_VLR_2 : error (VLR) + error_VLR_2 --> MI_wait_VLR_response_2 +``` + +State transition diagram for Process USSD\_MI2. The diagram shows two main state transition paths starting from 'MI wait VLR response'. The first path leads to 'USSD response (VLR)' and then to 'idle'. The second path leads to 'MI wait user response (for VLR)', which then branches into 'USSD response', 'release', 'release (VLR)', and 'error'. 'USSD response' leads to 'USSD response (VLR)' and then to 'MI wait VLR response'. 'release' and 'release (VLR)' both lead to 'idle'. 'error' leads to 'error (VLR)' and then to 'MI wait VLR response'. + +Figure 6.2 (sheet 2 of 3): Mobile initiated USSD at MSC + +![State transition diagram for Process USSD_MI2. The diagram shows transitions between states: MSC application processing, USSD response, USSD request, USSD notify, release, release (application), error, error (application), idle, and MSC wait user response (for application). Transitions are labeled with messages like 'USSD response (application)', 'USSD request (application)', 'USSD notify (application)', 'release', 'release (application)', and 'error (application)'. The diagram is divided into two main sections by a horizontal line, with the top section showing initial transitions and the bottom section showing transitions from the 'MSC wait user response' state.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +Process USSD\_MI2 390\_623(3) + +``` +stateDiagram-v2 + [*] --> MSC_application_processing : MSC application processing + MSC_application_processing --> USSD_response_application : USSD response (application) + MSC_application_processing --> USSD_request_application : USSD request (application) + MSC_application_processing --> USSD_notify_application : USSD notify (application) + MSC_application_processing --> release : release + MSC_application_processing --> release_application : release (application) + MSC_application_processing --> error_application : error (application) + + USSD_response_application --> USSD_response : USSD response + USSD_response --> idle : idle + + USSD_request_application --> USSD_request : USSD request + USSD_notify_application --> USSD_notify : USSD notify + release_application --> release_application_state : release (application) + release_application_state --> MSC_wait_user_response : MSC wait user response (for application) + release --> release_state : release + error_application --> error : error + error --> idle : idle + + MSC_wait_user_response --> USSD_response_state : USSD response + MSC_wait_user_response --> release_state : release + MSC_wait_user_response --> release_application_state : release (application) + MSC_wait_user_response --> error_state : error + + USSD_response_state --> USSD_response_application : USSD response (application) + USSD_response_application --> MSC_application_processing : MSC application processing + + release_state --> release_application_state : release (application) + release_application_state --> idle : idle + + error_state --> error_application : error (application) + error_application --> MSC_application_processing : MSC application processing +``` + +State transition diagram for Process USSD\_MI2. The diagram shows transitions between states: MSC application processing, USSD response, USSD request, USSD notify, release, release (application), error, error (application), idle, and MSC wait user response (for application). Transitions are labeled with messages like 'USSD response (application)', 'USSD request (application)', 'USSD notify (application)', 'release', 'release (application)', and 'error (application)'. The diagram is divided into two main sections by a horizontal line, with the top section showing initial transitions and the bottom section showing transitions from the 'MSC wait user response' state. + +Figure 6.2 (sheet 3 of 3): Mobile initiated USSD at MSC + +![State transition diagram for Process USSD_AI1. The diagram shows the flow of USSD messages between an application and a VLR. It starts at an 'idle' state, receives a 'USSD request (application)', sends a 'USSD request (VLR)', and enters an 'AI wait VLR response' state. From there, it branches into several possible message exchanges: 1) 'USSD request (VLR)' to 'USSD request (application)' leading to 'AI wait application response (for VLR)'; 2) 'USSD notify (VLR)' to 'USSD notify (application)'; 3) 'USSD response (VLR)' to 'USSD response (application)' leading to 'idle'; 4) 'release (application)' to 'release (VLR)'; 5) 'release (VLR)' to 'release (application)'; 6) 'error (VLR)' to 'error (application)'. From 'AI wait application response (for VLR)', it branches into: 1) 'USSD response (application)' to 'USSD response (VLR)' leading to 'AI wait VLR response'; 2) 'error (application)' to 'error (VLR)'; 3) 'release (application)' to 'release (VLR)' leading to 'idle'; 4) 'release (VLR)' to 'release (application)'. A note on the right explains message directions and the use of 'USSD request'.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Process USSD\_AI1 390\_63(1) + +``` +stateDiagram-v2 + [*] --> idle + idle --> USSD_request_application : USSD request (application) + USSD_request_application --> USSD_request_VLR : USSD request (VLR) + USSD_request_VLR --> AI_wait_VLR_response : AI wait VLR response + AI_wait_VLR_response --> USSD_request_VLR : USSD request (VLR) + AI_wait_VLR_response --> USSD_notify_VLR : USSD notify (VLR) + AI_wait_VLR_response --> USSD_response_VLR : USSD response (VLR) + AI_wait_VLR_response --> release_application : release (application) + AI_wait_VLR_response --> release_VLR : release (VLR) + AI_wait_VLR_response --> error_VLR : error (VLR) + USSD_request_VLR --> USSD_request_application : USSD request (application) + USSD_notify_VLR --> USSD_notify_application : USSD notify (application) + USSD_response_VLR --> USSD_response_application : USSD response (application) + release_application --> release_VLR : release (VLR) + release_VLR --> release_application : release (application) + error_VLR --> error_application : error (application) + USSD_request_application --> AI_wait_application_response : AI wait application response (for VLR) + USSD_response_application --> USSD_response_VLR : USSD response (VLR) + error_application --> error_VLR : error (VLR) + release_application --> release_VLR : release (VLR) + release_VLR --> release_application : release (application) + AI_wait_application_response --> USSD_response_application : USSD response (application) + AI_wait_application_response --> error_application : error (application) + AI_wait_application_response --> release_application : release (application) + AI_wait_application_response --> release_VLR : release (VLR) + USSD_response_VLR --> AI_wait_VLR_response : AI wait VLR response + release_VLR --> idle : release (VLR) + error_VLR --> idle : error (VLR) +``` + +**INPUTS AND OUTPUTS** + +For consistency with other SDL diagrams, all messages are shown to/from the right, for either the VLR or the application (as indicated). + +USSD request from application is used when an application receives a request from a MS and passes on the request (changed or unchanged) or generates a new request. + +State transition diagram for Process USSD\_AI1. The diagram shows the flow of USSD messages between an application and a VLR. It starts at an 'idle' state, receives a 'USSD request (application)', sends a 'USSD request (VLR)', and enters an 'AI wait VLR response' state. From there, it branches into several possible message exchanges: 1) 'USSD request (VLR)' to 'USSD request (application)' leading to 'AI wait application response (for VLR)'; 2) 'USSD notify (VLR)' to 'USSD notify (application)'; 3) 'USSD response (VLR)' to 'USSD response (application)' leading to 'idle'; 4) 'release (application)' to 'release (VLR)'; 5) 'release (VLR)' to 'release (application)'; 6) 'error (VLR)' to 'error (application)'. From 'AI wait application response (for VLR)', it branches into: 1) 'USSD response (application)' to 'USSD response (VLR)' leading to 'AI wait VLR response'; 2) 'error (application)' to 'error (VLR)'; 3) 'release (application)' to 'release (VLR)' leading to 'idle'; 4) 'release (VLR)' to 'release (application)'. A note on the right explains message directions and the use of 'USSD request'. + +Figure 6.3: Application initiated USSD at MSC + +![Flowchart for Process USSD_MI3. It starts with an 'idle' state, followed by a 'USSD request' from the MSC. A decision 'alphabet supported' follows. If 'no', it goes to 'MI wait HLR response'. If 'yes', it goes to another decision 'HPLMN service code'. If 'no', it goes to 'USSD request (application)' then 'VLR application processing'. If 'yes', it goes to 'USSD request (HLR)' then 'MI wait HLR response'.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Process USSD\_MI3 + +390\_641(3) + +**INPUTS AND OUTPUTS** + +Source/destination of messages shown to/from the left is the MSC. + +Source/destination of messages shown to/from the right is either the HLR or the application (as indicated). + +``` +graph TD; idle([idle]) --> UR{USSD request}; UR --> AS{alphabet supported}; AS -- no --> MIW[MI wait HLR response]; AS -- yes --> HSC{HPLMN service code}; HSC -- no --> UA{USSD request (application)}; HSC -- yes --> UH{USSD request (HLR)}; UA --> VAP[VLR application processing]; UH --> MIW; +``` + +Flowchart for Process USSD\_MI3. It starts with an 'idle' state, followed by a 'USSD request' from the MSC. A decision 'alphabet supported' follows. If 'no', it goes to 'MI wait HLR response'. If 'yes', it goes to another decision 'HPLMN service code'. If 'no', it goes to 'USSD request (application)' then 'VLR application processing'. If 'yes', it goes to 'USSD request (HLR)' then 'MI wait HLR response'. + +Figure 6.4 (sheet 1 of 3): Mobile initiated USSD at VLR + +![State transition diagram for Process USSD_MI3. The diagram shows various states and transitions for a mobile initiated USSD process at a VLR. States include 'MI wait HLR response', 'USSD response (HLR)', 'USSD request (HLR)', 'USSD notify (HLR)', 'release', 'error (HLR)', 'idle', and 'MI wait user response (for HLR)'. Transitions are labeled with message names like 'USSD response', 'USSD request', 'USSD notify', 'release (HLR)', 'release', and 'error'.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +Process USSD\_MI3 390\_642(3) + +``` +stateDiagram-v2 + [*] --> MI_wait_HLR_response : MI wait HLR response + MI_wait_HLR_response --> USSD_response_HLR : USSD response (HLR) + MI_wait_HLR_response --> USSD_request_HLR : USSD request (HLR) + MI_wait_HLR_response --> USSD_notify_HLR : USSD notify (HLR) + MI_wait_HLR_response --> release : release + MI_wait_HLR_response --> release_HLR : release (HLR) + MI_wait_HLR_response --> error_HLR : error (HLR) + + USSD_response_HLR --> USSD_response : USSD response + USSD_response --> idle : idle + + USSD_request_HLR --> USSD_request : USSD request + USSD_notify_HLR --> USSD_notify : USSD notify + USSD_request --> MI_wait_user_response : MI wait user response (for HLR) + USSD_notify --> MI_wait_user_response + + release --> release_HLR : release (HLR) + release_HLR --> idle : idle + + release_HLR --> release : release + release --> idle : idle + + error_HLR --> error : error + error --> MI_wait_HLR_response : MI wait HLR response + + MI_wait_user_response --> USSD_response : USSD response + MI_wait_user_response --> release : release + MI_wait_user_response --> release_HLR : release (HLR) + MI_wait_user_response --> error : error + + USSD_response --> USSD_response_HLR : USSD response (HLR) + USSD_response_HLR --> MI_wait_HLR_response : MI wait HLR response + + release --> release_HLR : release (HLR) + release_HLR --> idle : idle + + release_HLR --> release : release + release --> idle : idle + + error --> error_HLR : error (HLR) + error_HLR --> MI_wait_HLR_response : MI wait HLR response +``` + +State transition diagram for Process USSD\_MI3. The diagram shows various states and transitions for a mobile initiated USSD process at a VLR. States include 'MI wait HLR response', 'USSD response (HLR)', 'USSD request (HLR)', 'USSD notify (HLR)', 'release', 'error (HLR)', 'idle', and 'MI wait user response (for HLR)'. Transitions are labeled with message names like 'USSD response', 'USSD request', 'USSD notify', 'release (HLR)', 'release', and 'error'. + +Figure 6.4 (sheet 2 of 3): Mobile initiated USSD at VLR + +![State transition diagram for Process USSD_MI3. The diagram shows transitions between states like 'VLR application processing', 'idle', and 'VLR wait user response (for application)' based on events like 'USSD response (application)', 'USSD request (application)', 'USSD notify (application)', 'release', 'release (application)', and 'error (application)'.](26d664119ad25250780f554633444e54_img.jpg) + +Process USSD\_MI3 390\_643(3) + +``` +stateDiagram-v2 + [*] --> VLR_application_processing : VLR application processing + VLR_application_processing --> USSD_response_application : USSD response (application) + VLR_application_processing --> USSD_request_application : USSD request (application) + VLR_application_processing --> USSD_notify_application : USSD notify (application) + VLR_application_processing --> release : release + VLR_application_processing --> release_application : release (application) + VLR_application_processing --> error_application : error (application) + + USSD_response_application --> USSD_response : USSD response + USSD_response --> idle : idle + + USSD_request_application --> USSD_request : USSD request + USSD_notify_application --> USSD_notify : USSD notify + release --> release_application : release (application) + release_application --> release : release + error_application --> error : error + + USSD_request --> VLR_wait_user_response : VLR wait user response (for application) + USSD_notify --> VLR_wait_user_response + release_application --> idle : idle + release --> idle + error --> idle + + VLR_wait_user_response --> USSD_response : USSD response + VLR_wait_user_response --> release : release + VLR_wait_user_response --> release_application : release (application) + VLR_wait_user_response --> error : error + + USSD_response --> USSD_response_application : USSD response (application) + release --> release_application : release (application) + release_application --> release : release + error --> error_application : error (application) + + USSD_response_application --> VLR_application_processing : VLR application processing + release_application --> idle : idle + error_application --> VLR_application_processing : VLR application processing +``` + +State transition diagram for Process USSD\_MI3. The diagram shows transitions between states like 'VLR application processing', 'idle', and 'VLR wait user response (for application)' based on events like 'USSD response (application)', 'USSD request (application)', 'USSD notify (application)', 'release', 'release (application)', and 'error (application)'. + +Figure 6.4 (sheet 3 of 3): Mobile initiated USSD at VLR + +![State transition diagram for Process USSD_AI2. It shows states 'idle' and 'AI wait HLR response'. Transitions include 'USSD request (application)', 'USSD request (HLR)', 'USSD notify (HLR)', 'USSD response (HLR)', 'release (application)', and 'error (HLR)'. The diagram is divided into two main sections by a horizontal line. The top section starts with 'idle' -> 'USSD request (application)' -> 'USSD request (HLR)' -> 'AI wait HLR response'. From 'AI wait HLR response', there are six outgoing transitions: 'USSD request (HLR)' -> 'USSD request (application)' -> 'AI wait application response (for HLR)'; 'USSD notify (HLR)' -> 'USSD notify (application)' -> 'idle'; 'USSD response (HLR)' -> 'USSD response (application)' -> 'idle'; 'release (application)' -> 'release (HLR)' -> 'idle'; 'release (HLR)' -> 'release (application)' -> 'idle'; and 'error (HLR)' -> 'error (application)' -> 'idle'. The bottom section starts with 'AI wait application response (for HLR)' -> 'USSD response (application)' -> 'USSD response (HLR)' -> 'AI wait HLR response'; 'error (application)' -> 'error (HLR)' -> 'AI wait HLR response'; 'release (application)' -> 'release (HLR)' -> 'idle'; and 'release (HLR)' -> 'release (application)' -> 'idle'.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +**Process USSD\_AI2** 390\_65(1) + +**INPUTS AND OUTPUTS** + +For consistency with other SDL diagrams, all messages are shown to/from the right, for either the HLR or the application (as indicated). + +USSD request from application is used when an application receives a request from a MS and passes on the request (changed or unchanged) or generates a new request. + +``` +stateDiagram-v2 + [*] --> idle + idle --> USSD_request_application : USSD request (application) + USSD_request_application --> USSD_request_HLR : USSD request (HLR) + USSD_request_HLR --> AI_wait_HLR_response : AI wait HLR response + + state "AI wait HLR response" as AI_wait_HLR_response + AI_wait_HLR_response --> USSD_request_HLR_2 : USSD request (HLR) + USSD_request_HLR_2 --> USSD_request_application_2 : USSD request (application) + USSD_request_application_2 --> AI_wait_application_response : AI wait application response (for HLR) + + AI_wait_HLR_response --> USSD_notify_HLR : USSD notify (HLR) + USSD_notify_HLR --> USSD_notify_application : USSD notify (application) + USSD_notify_application --> idle_2 : idle + + AI_wait_HLR_response --> USSD_response_HLR : USSD response (HLR) + USSD_response_HLR --> USSD_response_application : USSD response (application) + USSD_response_application --> idle_3 : idle + + AI_wait_HLR_response --> release_application : release (application) + release_application --> release_HLR : release (HLR) + release_HLR --> idle_4 : idle + + AI_wait_HLR_response --> release_HLR_2 : release (HLR) + release_HLR_2 --> release_application_2 : release (application) + release_application_2 --> idle_5 : idle + + AI_wait_HLR_response --> error_HLR : error (HLR) + error_HLR --> error_application : error (application) + error_application --> idle_6 : idle + + AI_wait_application_response : AI wait application response (for HLR) + AI_wait_application_response --> USSD_response_application_3 : USSD response (application) + USSD_response_application_3 --> USSD_response_HLR_3 : USSD response (HLR) + USSD_response_HLR_3 --> AI_wait_HLR_response_2 : AI wait HLR response + + AI_wait_application_response --> error_application_3 : error (application) + error_application_3 --> error_HLR_3 : error (HLR) + error_HLR_3 --> AI_wait_HLR_response_2 : AI wait HLR response + + AI_wait_application_response --> release_application_3 : release (application) + release_application_3 --> release_HLR_3 : release (HLR) + release_HLR_3 --> idle_7 : idle + + AI_wait_application_response --> release_HLR_4 : release (HLR) + release_HLR_4 --> release_application_4 : release (application) + release_application_4 --> idle_8 : idle +``` + +State transition diagram for Process USSD\_AI2. It shows states 'idle' and 'AI wait HLR response'. Transitions include 'USSD request (application)', 'USSD request (HLR)', 'USSD notify (HLR)', 'USSD response (HLR)', 'release (application)', and 'error (HLR)'. The diagram is divided into two main sections by a horizontal line. The top section starts with 'idle' -> 'USSD request (application)' -> 'USSD request (HLR)' -> 'AI wait HLR response'. From 'AI wait HLR response', there are six outgoing transitions: 'USSD request (HLR)' -> 'USSD request (application)' -> 'AI wait application response (for HLR)'; 'USSD notify (HLR)' -> 'USSD notify (application)' -> 'idle'; 'USSD response (HLR)' -> 'USSD response (application)' -> 'idle'; 'release (application)' -> 'release (HLR)' -> 'idle'; 'release (HLR)' -> 'release (application)' -> 'idle'; and 'error (HLR)' -> 'error (application)' -> 'idle'. The bottom section starts with 'AI wait application response (for HLR)' -> 'USSD response (application)' -> 'USSD response (HLR)' -> 'AI wait HLR response'; 'error (application)' -> 'error (HLR)' -> 'AI wait HLR response'; 'release (application)' -> 'release (HLR)' -> 'idle'; and 'release (HLR)' -> 'release (application)' -> 'idle'. + +Figure 6.5: Application initiated USSD at VLR + +![State transition diagram for Process USSD_MI4. The process starts at 'idle', receives a 'USSD request' from the VLR, checks if the alphabet is supported. If 'no', it sends an 'error' to the application and returns to 'idle'. If 'yes', it sends a 'USSD request' to the application and enters 'HLR application processing'. From there, it branches into two main paths. The first path involves 'USSD request', 'USSD notify', 'USSD response', 'release', and 'error' messages between the VLR and application, leading to 'HLR wait user response' and then back to 'HLR application processing'. The second path involves 'USSD response', 'error', 'release', and 'release' messages between the application and VLR, leading back to 'idle'.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +Process USSD\_MI4 + +390\_66(1) + +``` +stateDiagram-v2 + [*] --> idle + idle --> USSD_request_VLR: USSD request + USSD_request_VLR --> alphabet_supported{alphabet supported} + alphabet_supported --> error_app: error + error_app --> idle + alphabet_supported --> USSD_request_app: USSD request + USSD_request_app --> HLR_app_processing: HLR application processing + + state "HLR application processing" as HLR_app_processing + HLR_app_processing --> USSD_request_VLR + HLR_app_processing --> USSD_notify_app + HLR_app_processing --> USSD_response_VLR + HLR_app_processing --> release_app + HLR_app_processing --> release_VLR + HLR_app_processing --> error_app + + USSD_request_VLR --> USSD_request_app + USSD_notify_app --> USSD_notify_VLR + USSD_response_VLR --> USSD_response_app + release_app --> release_VLR + release_VLR --> release_app + error_app --> error_VLR + + USSD_request_app --> HLR_wait_user_response: HLR wait user response + USSD_notify_VLR --> idle + USSD_response_app --> HLR_app_processing + release_VLR --> idle + release_app --> release_VLR + error_VLR --> idle + + HLR_wait_user_response --> USSD_response_VLR + HLR_wait_user_response --> error_app + HLR_wait_user_response --> release_app + HLR_wait_user_response --> release_VLR + + USSD_response_VLR --> USSD_response_app + error_app --> error_VLR + release_app --> release_VLR + release_VLR --> release_app + + USSD_response_app --> HLR_app_processing + error_VLR --> idle + release_VLR --> idle +``` + +idle + +USSD request + +alphabet supported + +no + +yes + +error + +USSD request + +HLR application processing + +USSD request + +USSD notify + +USSD response + +release + +release + +error + +USSD request + +USSD notify + +USSD response + +release + +release + +error + +HLR wait user response + +idle + +USSD response + +error + +release + +release + +USSD response + +error + +release + +release + +HLR application processing + +idle + +INPUTS AND OUTPUTS + +Source/destination of messages shown to/from the left is the VLR. + +Source/destination of messages shown to/from the right is the application. + +State transition diagram for Process USSD\_MI4. The process starts at 'idle', receives a 'USSD request' from the VLR, checks if the alphabet is supported. If 'no', it sends an 'error' to the application and returns to 'idle'. If 'yes', it sends a 'USSD request' to the application and enters 'HLR application processing'. From there, it branches into two main paths. The first path involves 'USSD request', 'USSD notify', 'USSD response', 'release', and 'error' messages between the VLR and application, leading to 'HLR wait user response' and then back to 'HLR application processing'. The second path involves 'USSD response', 'error', 'release', and 'release' messages between the application and VLR, leading back to 'idle'. + +Figure 6.6: Mobile initiated USSD at HLR + +![Sequence diagram showing information flow for mobile initiated USSD Request. Lifelines: MS, MSC, VLR, HLR. The diagram shows three scenarios: 'Request handled by MSC', 'Request handled by VLR', and 'Request handled by HLR'. In each scenario, the MS sends a USSD request to the MSC. The MSC then either responds (OR1:N) or forwards it to the VLR (OR1:Y). The VLR then either responds (OR2:N) or forwards it to the HLR (OR2:Y). The HLR responds to the VLR, which in turn responds to the MSC, which finally responds to the MS.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + + Note left of MS: Request handled by MSC + MS->>MSC: USSD request + MSC-->>MS: USSD response OR1:N + + Note left of MS: Request handled by VLR + MS->>MSC: USSD request + MSC-->>MS: USSD response OR1:Y + MSC->>VLR: USSD request + VLR-->>MSC: USSD response OR2:N + VLR-->>MS: USSD response + + Note left of MS: Request handled by HLR + MS->>MSC: USSD request + MSC-->>MS: USSD response OR1:Y + MSC->>VLR: USSD request + VLR-->>MSC: USSD response OR2:Y + VLR->>HLR: USSD request + HLR-->>VLR: USSD response + HLR-->>MSC: USSD response + HLR-->>MS: USSD response +``` + +Sequence diagram showing information flow for mobile initiated USSD Request. Lifelines: MS, MSC, VLR, HLR. The diagram shows three scenarios: 'Request handled by MSC', 'Request handled by VLR', and 'Request handled by HLR'. In each scenario, the MS sends a USSD request to the MSC. The MSC then either responds (OR1:N) or forwards it to the VLR (OR1:Y). The VLR then either responds (OR2:N) or forwards it to the HLR (OR2:Y). The HLR responds to the VLR, which in turn responds to the MSC, which finally responds to the MS. + +NOTE: OR1: HPLMN service code Y: Yes +OR2: HPLMN service code and user not in HPLMN N: No + +Note that the application at the MSC/VLR may pass the request on to another network entity. This is not shown here. + +**Figure 6.7: Information flow for mobile initiated USSD Request (No further information requested)** + +![Sequence diagram showing information flow for mobile initiated USSD Request Handled by HLR, further information requested. Lifelines: MS, MSC, VLR, HLR. The diagram shows a sequence of USSD requests and responses between the entities.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + + MS->>MSC: USSD request + MSC->>VLR: USSD request + VLR->>HLR: USSD request + HLR-->>VLR: USSD request + VLR-->>MSC: USSD request + MSC-->>MS: USSD request + MS->>MSC: USSD response + MSC->>VLR: USSD response + VLR->>HLR: USSD response + + Note over MS,HLR: ... + + HLR->>VLR: USSD request + VLR->>MSC: USSD request + MSC->>MS: USSD request + MS->>MSC: USSD response + MSC->>VLR: USSD response + VLR->>HLR: USSD response + HLR-->>VLR: USSD response + VLR-->>MSC: USSD response + MSC-->>MS: USSD response + +``` + +Sequence diagram showing information flow for mobile initiated USSD Request Handled by HLR, further information requested. Lifelines: MS, MSC, VLR, HLR. The diagram shows a sequence of USSD requests and responses between the entities. + +NOTE: Note that this call flow only shows one example to illustrate the possible scenarios. See the SDL diagrams for a complete description. + +**Figure 6.8: Information flow for mobile initiated USSD Request Handled by HLR, further information requested** + +![Sequence diagram showing information flow for mobile initiated failed USSD Request between MS, MSC, VLR, and HLR.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + + Note left of MS: Error detected at MSC + MS->>MSC: USSD request + MSC-->>MS: Error + + Note left of MS: Error detected at VLR + MS->>MSC: USSD request + MSC->>VLR: USSD request + VLR-->>MSC: Error + MSC-->>MS: Error + + Note left of MS: Error detected at HLR + MS->>MSC: USSD request + MSC->>VLR: USSD request + VLR->>HLR: USSD request + HLR-->>VLR: Error + VLR-->>MSC: Error + MSC-->>MS: Error + + Note left of MS: MS clears transaction before response received + MS->>MSC: USSD request + MSC->>VLR: USSD request + VLR->>HLR: USSD request + MS->>MSC: Release + MSC->>VLR: Release + VLR->>HLR: Release +``` + +The diagram illustrates the interaction between a Mobile Station (MS), Mobile Switching Center (MSC), Visitor Location Register (VLR), and Home Location Register (HLR) for a failed USSD request. It shows four scenarios: 1) Error detected at MSC: MS sends a USSD request to MSC, which immediately responds with an Error. 2) Error detected at VLR: MS sends a USSD request to MSC, which forwards it to VLR; VLR responds with an Error to MSC, which then forwards it to MS. 3) Error detected at HLR: MS sends a USSD request to MSC, which forwards it to VLR, which then forwards it to HLR; HLR responds with an Error to VLR, which forwards it to MSC, which then forwards it to MS. 4) MS clears transaction before response received: MS sends a USSD request to MSC, which forwards it to VLR, which then forwards it to HLR; before any error is received, MS sends a Release message to MSC, which forwards it to VLR, which then forwards it to HLR. + +Sequence diagram showing information flow for mobile initiated failed USSD Request between MS, MSC, VLR, and HLR. + +NOTE: This call flow only shows a limited number of examples to illustrate the possible scenarios. See the SDL diagrams for a complete description. + +**Figure 6.9: Information flow for mobile initiated failed USSD Request** + +## 6.3 Information stored in the HLR + +The HLR shall not store any information specific to the use of USSD, although information may be stored for services which are offered by USSD applications. + +## 6.4 Information stored in the VLR + +The VLR shall not store any information specific to the use of USSD, although information may be stored for services which are offered by USSD applications. + +## 6.5 Handover + +Handover will have no impact on the operation of this service. + +## 6.6 Cross-phase compatibility + +If, when a Phase 2 MS sends a mobile initiated USSD request, any network entity is of Phase 1, the request will be rejected. If it is possible to encode the content of the USSD request using the Phase 1 protocol, the MS shall repeat the request, using the Phase 1 protocol. + +A Mobile initiated USSD request from a Phase 1 MS uses the Phase 1 protocol. On receipt of such a request, the application shall also use the Phase 1 protocol when sending the response. + +A Phase 2 network shall not send network initiated requests or notifications during a mobile initiated USSD request if the MS or any network entity involved in the operation is of Phase 1. + +# Annex A (informative): Change history + +| TSG CN# | Spec | CR | Rev | Phase | Cat | New Ver | Subject/Comment | +|----------|-----------|------|-----|--------|-----|---------|--------------------------------| +| Apr 1999 | GSM 03.90 | | | R97 | | | Transferred to 3GPP CN1 | +| CN#03 | 23.090 | | | R99 | | 3.0.0 | Approved at CN#03 | +| CN#06 | 23.090 | 001 | 1 | R99 | | 3.1.0 | USSD enhancement | +| CN#09 | 23.090 | 002 | 1 | R99 | F | 3.2.0 | SDL refresh | +| CN#11 | 23.090 | | | Rel-4 | | 4.0.0 | Release 4 after CN#11 | +| CN#16 | 23.090 | | | Rel-5 | | 5.0.0 | Release 5 after CN#16 | +| CN#26 | 23.090 | | | Rel-6 | | 6.0.0 | Release 6 after CN#26 | +| CT#30 | 23.090 | 0003 | 1 | Rel-6 | F | 6.1.0 | Incorrect References | +| CT#36 | 23.090 | | | Rel-7 | | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.090 | | | Rel-8 | | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#42 | 23.090 | - | - | Rel-9 | | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 23.090 | - | - | Rel-10 | | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | 23.090 | - | - | Rel-11 | | 11.0.0 | Update to Rel-11 version (MCC) | +| 2014-09 | 23.090 | - | - | Rel-12 | | 12.0.0 | Update to Rel-12 version (MCC) | +| 2015-12 | 23.090 | - | - | Rel-13 | | 13.0.0 | Update to Rel-13 version (MCC) | +| 2017-03 | 23.090 | - | - | Rel-14 | | 14.0.0 | Update to Rel-14 version (MCC) | +| 2018-06 | 23.090 | - | - | Rel-15 | - | 15.0.0 | Update to Rel-15 version (MCC) | +| 2020-07 | 23.090 | - | - | Rel-16 | - | 16.0.0 | Update to Rel-16 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23091/2f58bcce74146d4d983070d93be12291_img.jpg b/marked/Rel-16/23_series/23091/2f58bcce74146d4d983070d93be12291_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d98e1c320f41831f4df9eee16ed901df4bde7d1 --- /dev/null +++ b/marked/Rel-16/23_series/23091/2f58bcce74146d4d983070d93be12291_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:940a88c15de88be78b7236a34f8e826308a7ca158478c06e248283aac2706ced +size 45672 diff --git a/marked/Rel-16/23_series/23091/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/marked/Rel-16/23_series/23091/5e92d9e8e9ce204e405bff2367f88176_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c937c563f40c50dee193477f053d92dc7bd3d07e --- /dev/null +++ b/marked/Rel-16/23_series/23091/5e92d9e8e9ce204e405bff2367f88176_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6624ce27088c785f32042e2aa1626441a4deae6132dcc2b9559b86bae73739e8 +size 91958 diff --git a/marked/Rel-16/23_series/23091/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/23_series/23091/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5711fa99f5990e9a8fcca14c4b95b2a2e42b5291 --- /dev/null +++ b/marked/Rel-16/23_series/23091/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e86886f691479c61787e1e2916e4dfcacf807cfcf9a668fe0b5276a5f24b83cb +size 119042 diff --git a/marked/Rel-16/23_series/23091/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23091/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d73da7fe623a19c64d63878f2eb0e714bb8ae2d --- /dev/null +++ b/marked/Rel-16/23_series/23091/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa3e9ab5b2492e3eacad7524b218832c11df7e9b5356c6aa0667597d03a6df99 +size 40473 diff --git a/marked/Rel-16/23_series/23097/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/23_series/23097/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..720644a695931c937568b60f6596675172b9a5c7 --- /dev/null +++ b/marked/Rel-16/23_series/23097/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b72b87d9153ad09bd2f1e420b78ee338d5ce1fd81fcdc57c2c8f238b3a68e79 +size 105514 diff --git a/marked/Rel-16/23_series/23097/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg b/marked/Rel-16/23_series/23097/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da38cca74ab95d41d80ea9a66483caa309b93f74 --- /dev/null +++ b/marked/Rel-16/23_series/23097/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a6530aec4674c3d4f6e53841ebf8582f7aa7b038e6173b073b3b62d4bf2359d +size 40224 diff --git a/marked/Rel-16/23_series/23097/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/23_series/23097/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c21ed7ba0bb6f4a74ac4e45fc59a2d0f194ba966 --- /dev/null +++ b/marked/Rel-16/23_series/23097/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a8d8072eecd14a90002786c5ac36c058ff762ca8c7c63ba0d663406e90adaea +size 99831 diff --git a/marked/Rel-16/23_series/23097/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/23_series/23097/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f646437fb828e89c9c4ac30995e6bfc52f0ff636 --- /dev/null +++ b/marked/Rel-16/23_series/23097/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d9984a5db52d5f9347ef28bf766311bc168d16217e744bd25a1f03b0610eeff +size 98223 diff --git a/marked/Rel-16/23_series/23097/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23097/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7a49363ef527cc34654371ec4b4c51f9f2928d1 --- /dev/null +++ b/marked/Rel-16/23_series/23097/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8c509a6949ffefc7250d97ae1aa9f28a70c0274359e034473ffb6dc432af0aa +size 109850 diff --git a/marked/Rel-16/23_series/23097/212c50c4e3d043c989037a01e13c1a98_img.jpg b/marked/Rel-16/23_series/23097/212c50c4e3d043c989037a01e13c1a98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0471a4630413e730c349e08a7a4e3cfb2c4e29a9 --- /dev/null +++ b/marked/Rel-16/23_series/23097/212c50c4e3d043c989037a01e13c1a98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee5595dc2f79d6585085d29f81fb088664998c1edea99a205423a8952be7a6f7 +size 44712 diff --git a/marked/Rel-16/23_series/23097/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23097/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6449a1de2beb0d60a9b07116f52b4eb35898ede0 --- /dev/null +++ b/marked/Rel-16/23_series/23097/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed83433cf26013331c4892934ace1f4d59cdd6b05cbb58e94473b792b3625da7 +size 117466 diff --git a/marked/Rel-16/23_series/23097/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23097/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..92b5d93921e389c5d0dee1819bc7718e724f9159 --- /dev/null +++ b/marked/Rel-16/23_series/23097/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49c3d3cc7e1293097d4886fa03a3a9d4656841fb08799566053e10144ef14922 +size 99267 diff --git a/marked/Rel-16/23_series/23097/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/23_series/23097/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2064ab22433e491641d5b6fb6c90deb48faf346b --- /dev/null +++ b/marked/Rel-16/23_series/23097/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb7bc2d5da0c4e39b91f34d3803954998d4778652a8345d433a0671792bc9153 +size 99683 diff --git a/marked/Rel-16/23_series/23097/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23097/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31c558aa42317efd70928e93ab803be800034f5a --- /dev/null +++ b/marked/Rel-16/23_series/23097/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fe081cd93a4be27b189c7d66e2974de38d0b592bb9c1b1789e661bc7cd71e26 +size 74877 diff --git a/marked/Rel-16/23_series/23097/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/23_series/23097/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5742b235694e475b2e9872779b916dffee6f91b3 --- /dev/null +++ b/marked/Rel-16/23_series/23097/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d322c4cab6c86dcfa10df9a345817052b7fcf0fd034bd32a9a61cf0784bc4b5 +size 89025 diff --git a/marked/Rel-16/23_series/23097/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/23_series/23097/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b14adbf81bf2c1a0eb700e69fb998d48729d7aa --- /dev/null +++ b/marked/Rel-16/23_series/23097/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59111da7a989232381aec187503842a5839e367c4a24e0ae0ac2811b5f9b604a +size 92045 diff --git a/marked/Rel-16/23_series/23097/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-16/23_series/23097/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d4df0f3ee50716983929c06e0604efc98bb4378 --- /dev/null +++ b/marked/Rel-16/23_series/23097/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d98f5a99b877084e71d69e3fd1b6e225ff83f24ac39d52f172352fe7cd33605 +size 104925 diff --git a/marked/Rel-16/23_series/23097/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23097/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdfe973c6bd6e0c69de97720c0c5db8952b00014 --- /dev/null +++ b/marked/Rel-16/23_series/23097/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24307e30675b6ab60970250a446cefec9101f234ce0a10ff9f2814d17dd736aa +size 128631 diff --git a/marked/Rel-16/23_series/23097/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-16/23_series/23097/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07d75cb565029a4704ee494dc060901aaba0276a --- /dev/null +++ b/marked/Rel-16/23_series/23097/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:251ce995c5d038e24784e9443b4e7f5cd500dc2a0042a26fd1deeceee2c7a3a0 +size 75695 diff --git a/marked/Rel-16/23_series/23097/552328a9daaf3bc0069424b500025880_img.jpg b/marked/Rel-16/23_series/23097/552328a9daaf3bc0069424b500025880_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09e4bf1ea96f42950e5f30ed0748fb922c6dd8db --- /dev/null +++ b/marked/Rel-16/23_series/23097/552328a9daaf3bc0069424b500025880_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d8c996fa3132e889d103e5873982108de0ef47c5982fe5837ee182f1ddfad85 +size 115393 diff --git a/marked/Rel-16/23_series/23097/5793a44ffdadd039928e2f9fe6daae06_img.jpg b/marked/Rel-16/23_series/23097/5793a44ffdadd039928e2f9fe6daae06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c6a92433489b51cffe92fd23902db20f3576d18 --- /dev/null +++ b/marked/Rel-16/23_series/23097/5793a44ffdadd039928e2f9fe6daae06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97ac0fc2d164cc2ff6f29b4be164d8219e7acad6ab3da664737d39b2392c0c46 +size 95081 diff --git a/marked/Rel-16/23_series/23097/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23097/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..73ec0550e035a1b80f2ce2131a78972bfe45125e --- /dev/null +++ b/marked/Rel-16/23_series/23097/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c71aed5777a4a51fe5796d13a781f76202b31e2858e66a84dcc9ea310a11f0a0 +size 60504 diff --git a/marked/Rel-16/23_series/23097/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-16/23_series/23097/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b7628de60f8afa3c0b2383a188ea9213af567af --- /dev/null +++ b/marked/Rel-16/23_series/23097/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4974593ab9449a088c54f5d371f4c6ff353a3b48a517184127fe0a0f07531d0a +size 85603 diff --git a/marked/Rel-16/23_series/23097/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/23_series/23097/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3bff7d82ede7bfbbb524edda6a4829c01a74246 --- /dev/null +++ b/marked/Rel-16/23_series/23097/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a63b98256982d8f7407414690ba7bdf3f3dc5eb8745f558af07f67f3f25aedfd +size 76347 diff --git a/marked/Rel-16/23_series/23097/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/23_series/23097/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..482d743317bfaf76749b7da31284573a0e199673 --- /dev/null +++ b/marked/Rel-16/23_series/23097/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56afcc3dd742657e72ac9c5f6e1928be72a50e827029d780ff500f5ca1f894d2 +size 98309 diff --git a/marked/Rel-16/23_series/23097/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/23_series/23097/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c59f0209c57b2da00c8ccc33073115cf653da20b --- /dev/null +++ b/marked/Rel-16/23_series/23097/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5a5880a1ec2241619ee5a993e566e1e939a2b69907a8d5ec547ec136c127471 +size 74479 diff --git a/marked/Rel-16/23_series/23097/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/23_series/23097/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7ffe460a794e333c9982fb44525bf0fe155eb53 --- /dev/null +++ b/marked/Rel-16/23_series/23097/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd6f47eee99da77a645b995e9cd9fe196725f9c38096c0fb662167bab5ea4f2f +size 71015 diff --git a/marked/Rel-16/23_series/23097/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23097/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15098d0af8e0a4c58ec1e3e8751732ab49fe88da --- /dev/null +++ b/marked/Rel-16/23_series/23097/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b08df94d49b3d844d7d57d462ed23bdc1b009c82549c4eff765683e74fd80a13 +size 112083 diff --git a/marked/Rel-16/23_series/23097/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/23_series/23097/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d69a04ecd44b374684d96edca21db6ee7db97f1b --- /dev/null +++ b/marked/Rel-16/23_series/23097/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a706b3263812b6d0587806a5b767be071919b37587878709a799714fe35e66c0 +size 89888 diff --git a/marked/Rel-16/23_series/23097/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23097/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..baa30afcb2f843ef87a941cc20d8538e7e9e2d32 --- /dev/null +++ b/marked/Rel-16/23_series/23097/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:863af5ff330a1e3cf322909a82d35965b12d98f37d561c03b9647965e0d8c717 +size 89324 diff --git a/marked/Rel-16/23_series/23097/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-16/23_series/23097/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..189a15b344f737cfa2b12531f5b7bdf4aee7f7b1 --- /dev/null +++ b/marked/Rel-16/23_series/23097/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d573269d1a9ffc4c682e0199117fec453b0cc564656d8d3f6df10adbd1c47eac +size 119595 diff --git a/marked/Rel-16/23_series/23097/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/23_series/23097/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be3804040ca020f0ad2923c846834869073cc22a --- /dev/null +++ b/marked/Rel-16/23_series/23097/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:139af0fdb36c71b80010f944d2012c480f527bb6aaf384e374e4495a49c8a95b +size 88843 diff --git a/marked/Rel-16/23_series/23097/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/23_series/23097/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7099cbf32986efa05c10718199ceb05cf54fd06d --- /dev/null +++ b/marked/Rel-16/23_series/23097/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:219fc8153881ee92fa5bfbd51381ee14f4035f092396a87bd744b9068de95503 +size 102810 diff --git a/marked/Rel-16/23_series/23097/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23097/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bef577e1c36af846ed927b1bf52ddd86521130d1 --- /dev/null +++ b/marked/Rel-16/23_series/23097/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b88e646f05e88b785340783f01df22115a0bc8e48053ef44cd49ce39d6b9172 +size 116020 diff --git a/marked/Rel-16/23_series/23097/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/23_series/23097/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..800510fece5e4ab732a9da3bccad6a76f5ddddad --- /dev/null +++ b/marked/Rel-16/23_series/23097/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2815e5732a98940d7cd8cf62cc7b1125caaf76851111ff6b87e77f6fe90a1b2b +size 74854 diff --git a/marked/Rel-16/23_series/23097/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23097/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5bba72794bdac88287d5a07a8441dd4f7ca07c34 --- /dev/null +++ b/marked/Rel-16/23_series/23097/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f40f1b8ec1f81a39dd73545e3c57b79f47e2b1d55ad99de061446626ce296f3f +size 78949 diff --git a/marked/Rel-16/23_series/23097/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-16/23_series/23097/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34bc07e00a30afb8760ca9262111ada92b654ce7 --- /dev/null +++ b/marked/Rel-16/23_series/23097/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f20956694d73db69326c677d05fb3dafe18646271a454352c11b66a86998d8f +size 70096 diff --git a/marked/Rel-16/23_series/23097/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23097/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bb8fd53836360c741e3788c166fe5c7cc9d59c1 --- /dev/null +++ b/marked/Rel-16/23_series/23097/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28ee56ade6f09f7bf6f3ce4b846de2ac8a65a02ef8880e254ec2238994bfe34c +size 90594 diff --git a/marked/Rel-16/23_series/23097/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/23_series/23097/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0da11dfafbc4259411598a6d40c4b0bac4baa51d --- /dev/null +++ b/marked/Rel-16/23_series/23097/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9e230e100fc1cc3eefc1d224797528c0232ceaaa9d6ec9464431b26767746f9 +size 89809 diff --git a/marked/Rel-16/23_series/23097/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/23_series/23097/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5a7ab24597bf2fa85bb2439426f09d095e17b3c --- /dev/null +++ b/marked/Rel-16/23_series/23097/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2943cb6b10e4718214e5c1f1317c7aa821e1447f651265d539b2c3d88102b97b +size 109702 diff --git a/marked/Rel-16/23_series/23097/b774dfc5023e15e9c352b97ca25a56d4_img.jpg b/marked/Rel-16/23_series/23097/b774dfc5023e15e9c352b97ca25a56d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4615d45ff4290ee9384864a35923e85ac3c86d1 --- /dev/null +++ b/marked/Rel-16/23_series/23097/b774dfc5023e15e9c352b97ca25a56d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae0adc14fee2df03d95be0be93b14daa38c661b9923c06d009f4769254806709 +size 41915 diff --git a/marked/Rel-16/23_series/23097/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-16/23_series/23097/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2be01d7f3bf0b0a5ab8c0850aa4bcc6e67c9d14 --- /dev/null +++ b/marked/Rel-16/23_series/23097/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2a5b0412e48691ce022cc5c762a297a5082141842467a9574a9fbf5d37bde58 +size 88218 diff --git a/marked/Rel-16/23_series/23097/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/23_series/23097/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5c3259237608de2a6145460417fae3c870a4a29 --- /dev/null +++ b/marked/Rel-16/23_series/23097/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f16c4297a5a496e864d7a13e9249a7339835335705bdb4b20622b0c648b617b7 +size 87554 diff --git a/marked/Rel-16/23_series/23097/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/Rel-16/23_series/23097/cab0834804fb031b43865554cc8d06ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..558decfceb293ba5ca489c970f7b729984aa8fdf --- /dev/null +++ b/marked/Rel-16/23_series/23097/cab0834804fb031b43865554cc8d06ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c813af5df27daa484b2948aa0321f853d86e5ae5758cd9939693e8c31a43532 +size 62440 diff --git a/marked/Rel-16/23_series/23097/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg b/marked/Rel-16/23_series/23097/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ca03d5743a35ba488e50c650638042bcc819ff9 --- /dev/null +++ b/marked/Rel-16/23_series/23097/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:978f88360e82452de33e352200df9ac57f6c6dec6aa40637e697c06747a4200c +size 67597 diff --git a/marked/Rel-16/23_series/23097/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23097/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8abfb45429be50ab89c7961c5356ed60b5288706 --- /dev/null +++ b/marked/Rel-16/23_series/23097/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06e56adf201ee568668f98a7932a5f45e9afd0050922017f8a06daafe5df8b5b +size 108446 diff --git a/marked/Rel-16/23_series/23097/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/23_series/23097/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cff6819367bc1aee643a758a01ffde2457b32dae --- /dev/null +++ b/marked/Rel-16/23_series/23097/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bf743500beb0d7a22effe012d0ab95438746573d149cdb139ccbbfadcba5a42 +size 114292 diff --git a/marked/Rel-16/23_series/23097/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23097/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7a1b94fc29fe0a33bf27f4e5e825f2df045e880 --- /dev/null +++ b/marked/Rel-16/23_series/23097/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ccaa75fb0bb0842870c85750edb0d691b921ff79ea8ef675ee0a0e6a5a6c87b2 +size 86952 diff --git a/marked/Rel-16/23_series/23097/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg b/marked/Rel-16/23_series/23097/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63616528bf7b811a9f6bdaf20567a7bac99b2566 --- /dev/null +++ b/marked/Rel-16/23_series/23097/efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd47b984ff86773f4da555335b9fd72e2e7c7ac12eeabfa2fd98fe7c62e79459 +size 51502 diff --git a/marked/Rel-16/23_series/23097/raw.md b/marked/Rel-16/23_series/23097/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..266aca4a7bab02d32537e414f8427f041a94437a --- /dev/null +++ b/marked/Rel-16/23_series/23097/raw.md @@ -0,0 +1,1745 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 Features needed to support MSP Phase 2 ..... | 7 | +| 5 Additional Information stored in network entities ..... | 8 | +| 5.1 Data stored in the HLR..... | 8 | +| 5.2 Data stored in the VLR..... | 8 | +| 6 Additional procedures in network entities ..... | 8 | +| 6.1 OCB_flag ..... | 8 | +| 6.2 ODB flags..... | 9 | +| 6.3 HOLD_flag..... | 9 | +| 6.4 CW_flag ..... | 9 | +| 6.5 MPTY_flag..... | 9 | +| 6.6 ECT_flag..... | 9 | +| 6.7 CCBS_flag ..... | 10 | +| 6.8 CLIR_flag..... | 10 | +| 7 Description of Multiple Subscriber Profile..... | 10 | +| 7.1 Overview ..... | 10 | +| 7.2 Registration of a Profile ..... | 10 | +| 7.3 Interrogation ..... | 12 | +| 7.4 Call Handling for an MSP subscriber ..... | 15 | +| 7.4.1 Mobile Originating (MO) call handling ..... | 15 | +| 7.4.2 Mobile Terminating (MT) call handling ..... | 15 | +| 7.5 Functions and Information Flows ..... | 15 | +| 7.5.1 MO call handling in the gsmSCF ..... | 15 | +| 7.5.1.1 Process MO_MSP_Call_gsmSCF ..... | 15 | +| 7.5.1.2 Procedure Set_Calling_Profile_gsmSCF..... | 15 | +| 7.5.1.3 Procedure Send_FCI_gsmSCF ..... | 15 | +| 7.5.2 MT call handling in the gsmSCF..... | 22 | +| 7.5.2.1 Process MT_MSP_Call_gsmSCF..... | 22 | +| 7.5.3 SS handling in the gsmSCF..... | 27 | +| 7.5.3.1 Procedure Check_CLIR_gsmSCF ..... | 27 | +| 7.5.3.2 Procedure Forwarded_MSP_Call_gsmSCF ..... | 27 | +| 7.5.3.3 Procedure Check_CFU_gsmSCF ..... | 27 | +| 7.5.3.4 Procedure Check_Early_CF_gsmSCF..... | 27 | +| 7.5.3.5 Procedure Check_Late_CF_gsmSCF ..... | 27 | +| 7.5.3.6 Procedure Check_CFNRy_gsmSCF..... | 27 | +| 7.5.3.7 Procedure Check_CFB_gsmSCF..... | 27 | +| 7.5.3.8 Procedure Check_CFNRc_gsmSCF..... | 27 | +| 7.5.3.9 Procedure Check_CW_gsmSCF..... | 27 | +| 7.5.3.10 Procedure Check_HOLD_gsmSCF..... | 27 | +| 7.5.3.11 Procedure Check_MPTY_gsmSCF..... | 27 | +| 7.5.3.12 Procedure Check_ACM_gsmSCF ..... | 27 | +| 7.5.3.13 Process AoC_MSP_gsmSCF ..... | 27 | +| 7.5.3.14 Procedure AoCI_gsmSCF..... | 27 | +| 7.5.3.15 Procedure AoCC_gsmSCF ..... | 28 | +| 7.5.3.16 Procedure Outgoing_Barring_Check_gsmSCF ..... | 28 | +| 7.5.3.17 Procedure Incoming_Barring_Check_gsmSCF..... | 28 | +| 7.5.3.18 Procedure Check_ECT_gsmSCF..... | 28 | +| 7.5.3.19 Procedure Check_CCBS_gsmSCF..... | 28 | +| 7.5.4 Information flows ..... | 47 | +| 7.6 SMS handling..... | 50 | + +| | | | +|-------------------------------|-------------------------------------------------------------------------|-----------| +| 7.7 | Call Independent SS handling..... | 52 | +| 7.8 | Interaction with Supplementary Services..... | 52 | +| 7.8.1 | Line Identification services ..... | 52 | +| 7.8.1.1 | CLIP..... | 52 | +| 7.8.1.2 | CLIR ..... | 52 | +| 7.8.1.3 | COLP ..... | 52 | +| 7.8.1.4 | COLR..... | 52 | +| 7.8.2 | Call Hold (HOLD)..... | 52 | +| 7.8.3 | Call Waiting (CW) ..... | 53 | +| 7.8.4 | Call Forwarding..... | 53 | +| 7.8.5 | Multi Party Service (MPTY)..... | 53 | +| 7.8.6 | Closed User Group (CUG) ..... | 53 | +| 7.8.7 | Advice of Charge (AoC) ..... | 53 | +| 7.8.8 | Call Barring ..... | 54 | +| 7.8.9 | Explicit Call Transfer (ECT)..... | 54 | +| 7.8.10 | Completion of Calls to Busy Subscriber (CCBS) ..... | 54 | +| 7.8.11 | enhanced Multi-Level Precedence and Pre-emption (eMLPP) ..... | 54 | +| 7.8.12 | User-to-User Signalling (UUS) ..... | 55 | +| 7.8.13 | Call Deflection (CD) ..... | 55 | +| 7.9 | Interaction with other services ..... | 55 | +| 7.9.1 | The Multi-Numbering Scheme..... | 55 | +| 7.9.2 | The Short Message Service ..... | 55 | +| 7.9.3 | Interactions with CAMEL ..... | 55 | +| 7.9.4 | Interactions with OR..... | 55 | +| 7.9.5 | Operator Determined Barring..... | 55 | +| 7.9.6 | Roaming Restrictions ..... | 56 | +| 7.10 | Data stored in the gsmSCF..... | 57 | +| 7.11 | Equivalent services implemented by the gsmSCF ..... | 58 | +| 7.11.1 | Call Forwarding..... | 58 | +| 7.11.1.1 | Call Forward Unconditional ..... | 60 | +| 7.11.1.2 | Call Forward on Busy..... | 61 | +| 7.11.1.3 | Call Forward on No Reply..... | 61 | +| 7.11.1.4 | Call Forward on Not Reachable..... | 62 | +| 7.11.1.5 | Early CFNRc..... | 62 | +| 7.11.1.6 | Late CFNRc ..... | 63 | +| 7.11.2 | Call Barring ..... | 63 | +| 7.11.3 | Operator Determined Barring (ODB)..... | 64 | +| 7.11.4 | Advice of Charge (AoC) ..... | 64 | +| 7.12 | Exceptional Procedures..... | 64 | +| 7.12.1 | Roaming into a network not supporting CAMEL Phase 3..... | 64 | +| 7.12.2 | Roaming into a network not supporting CAMEL Phase 2..... | 65 | +| 7.12.2.1 | Actions required on Location Update..... | 65 | +| 7.12.2.2 | MO call handling ..... | 65 | +| 7.12.2.3 | MT call handling..... | 65 | +| 7.12.2.4 | MO short message handling ..... | 65 | +| 7.12.3 | Lack of availability of the Network Indication of Alerting feature..... | 65 | +| Annex A (informative): | Provision and Withdrawal of MSP..... | 66 | +| A.1 | Provision of MSP ..... | 66 | +| A.2 | Withdrawal of MSP ..... | 66 | +| Annex B (informative): | Change history..... | 67 | + +# --- Foreword + +The present document has been produced by the 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. + +# --- 1 Scope + +The present document specifies the stage 2 description of the Multiple Subscriber Profile (MSP) Supplementary Service Phase 2. MSP Phase 2 is implemented using CAMEL Phase 3. + +# --- 2 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 22.030: " Man Machine Interface (MMI) of the Mobile Station (MS)". +- [3] 3GPP TS 22.097: " Multiple Subscriber Profile (MSP) Service Description – Stage 1". +- [4] 3GPP TS 23.008: "Organisation of subscriber data". +- [5] 3GPP TS 23.015: "Technical realization of Operator Determined Barring (ODB)". +- [6] 3GPP TS 23.018: "Basic Call Handling – Technical Realization". +- [7] 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP) – Stage 2". +- [8] 3GPP TS 23.072: "Call Deflection (CD); Stage 2". +- [9] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) – Phase 3; Stage 2". +- [10] 3GPP TS 23.079: "Support of Optimal Routeing (SOR); Technical Realisation". +- [11] 3GPP TS 23.081: "Line identification supplementary services – Stage 2". +- [12] 3GPP TS 23.082: "Call Forwarding (CF) supplementary services – Stage 2". +- [13] 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services – Stage 2". +- [14] 3GPP TS 23.084: "Multi Party (MPTY) supplementary services – Stage 2". +- [15] 3GPP TS 23.085: "Closed User Group (CUG) supplementary services – Stage 2". +- [16] 3GPP TS 23.086: "Advice of Charge (AoC) supplementary services – Stage 2". +- [17] 3GPP TS 23.087: "User-to-User (UUS) Supplementary Service; Stage 2". +- [18] 3GPP TS 23.088: "Call Barring (CB) supplementary services – Stage 2". +- [19] 3GPP TS 23.090: "Unstructured Supplementary Service Data (USSD) – Stage 2". +- [20] 3GPP TS 23.091: "Explicit Call Transfer (ECT) supplementary service – Stage 2". +- [21] 3GPP TS 23.093: "Technical Realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2". +- [22] 3GPP TS 24.086: "Advice of Charge (AoC) supplementary services – Stage 3". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purpose of this specification, the following terms and definitions apply: + +**Default Profile:** profile used when the MSP subscriber roams to a non-supporting network. + +**MSP Subscriber:** the subscriber provisioned with the MSP service + +**Profile Identity:** numerical identity (between 1 and 4) of the profile + +**Profile Status:** specifies if the profile is the registered profile and/or the default profile + +**Registered Profile:** profile used for all MO calls and short messages if a profile has not been explicitly selected + +## 3.2 Abbreviations + +The abbreviations used in this specification are listed in 3G TR21.905. + +For the purpose of this specification, the following abbreviations apply: + +| | | +|------|---------------------------------------------------------------------| +| CD | The Call Deflection supplementary service | +| MSP | The Multiple Subscriber Profile supplementary service | +| UUS | The User-to-User Signalling supplementary service | +| SII2 | The Service Interaction Indicators Two parameter (see 3G TS 23.078) | + +# --- 4 Features needed to support MSP Phase 2 + +CAMEL Phase 3 is a pre-requisite for MSP Phase 2. + +The following CAMEL Phase 3 features are used for MSP Phase 2: + +- SII2; +- MO SMS interaction; +- T-BCSM in the VMSC; +- SS-CSI Invocation Notification for CCBS; +- Any Time Modification; +- CUG Handling. + +The following CAMEL Phase 2 features are used for MSP Phase 2: + +- Network Indication of Alerting pattern; +- Event detection points; +- USSD Interaction; +- Control of Call Duration; +- SS-CSI Invocation Notification for CD; +- Furnish Charging Information. + +# --- 5 Additional Information stored in network entities + +## 5.1 Data stored in the HLR + +The HLR contains all the common data (the data valid for all profiles) and some data specific to the default profile. + +The data stored in the HLR are defined in 3G TS 23.008. The elements specifically used for MSP are: + +- list of MSISDNs and associated Bearer Capabilities for each profile; +- default profile (associated with the Basic MSISDN); +- capabilities of VLR (support of CAMEL Phase 2 and 3); +- supplementary services (per BSG) provisioned per subscriber (CW, CH, MPTY,...); +- Call Barring Data (see subclause 7.6.8: Call Barring); +- ODB Data (see subclause 7.7.5: Operator Determined Barring); +- HOLD Data (see subclause 7.8.2: Call Hold); +- ECT Data (see subclause 7.8.9: Explicit Call Transfer); +- MPTY Data (see subclause 7.8.5: Multi Party); +- CCBS Data (see subclause 7.8.10: Completion of Calls to Busy Subscriber); +- CW Data (see subclause 7.8.3: Call Waiting); +- CLIR Data (see subclause 7.8.1.2); +- CAMEL data including the MSP service key, O-CSI, T-CSI, VT-CSI, UG-CSI, SS-CSI and Location information / Subscriber state Interrogation. + +## 5.2 Data stored in the VLR + +The data stored in a VLR are defined in 3G TS 23.008. MSP has no impact on the VLR. + +# --- 6 Additional procedures in network entities + +## 6.1 OCB\_flag + +The OCB\_flag shall be set in the HLR if Call Barrings are provided in the gsmSCF. + +If the OCB\_flag is set then: + +- when the subscriber roams to a VLR which supports CAMEL Phase 2 or later, the HLR shall not send any outgoing call barring supplementary services data to the VLR; +- when the subscriber roams to a VLR which does not support CAMEL Phase 2 or later, the HLR shall send to the VLR outgoing call barring supplementary services data as stored in the HLR; +- the subscriber shall not be allowed to alter the Call Barring data in the HLR. + +## 6.2 ODB flags + +The ODB flag for the relevant category shall be set in the HLR if ODB is provisioned in the gsmSCF for that category. + +If the ODB flag is set for that category, then: + +when the subscriber roams to a VLR which supports CAMEL Phase 2 or later, the HLR shall not send any ODB data for that category to the VLR; + +when the subscriber roams to a VLR which does not support CAMEL Phase 2 or later, the HLR shall send to the VLR ODB data for that category as stored in the HLR. + +## 6.3 HOLD\_flag + +The HOLD\_flag shall be set in the HLR if the subscriber data for the HOLD SS are controlled by the gsmSCF. + +If the HOLD\_flag is set, then: + +- when the subscriber roams to a VLR which supports CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the HOLD SS as Active and Operative; +- when the subscriber roams to a VLR which does not support CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the HOLD SS as stored in the HLR. + +## 6.4 CW\_flag + +The CW\_flag shall be set in the HLR if the subscriber data for the CW SS are controlled by the gsmSCF. + +If the CW\_flag is set, then: + +- when the subscriber roams to a VLR which supports CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the CW SS as Active and Operative; +- when the subscriber roams to a VLR which does not support CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the CW SS as stored in the HLR; +- the subscriber shall not be allowed to alter the CW data in the HLR. + +## 6.5 MPTY\_flag + +The MPTY\_flag shall be set in the HLR if the subscriber data for the MPTY SS are controlled by the gsmSCF. + +If the MPTY\_flag is set, then: + +- when the subscriber roams to a VLR which supports CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the MPTY SS as Active and Operative; +- when the subscriber roams to a VLR which does not support CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the MPTY SS as stored in the HLR. + +## 6.6 ECT\_flag + +The ECT\_flag shall be set in the HLR if the subscriber data for the ECT SS are controlled by the gsmSCF. + +If the ECT\_flag is set, then: + +- when the subscriber roams to a VLR which supports CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the ECT SS as Active and Operative; +- when the subscriber roams to a VLR which does not support CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the ECT SS as stored in the HLR. + +## 6.7 CCBS\_flag + +The CCBS\_flag shall be set in the HLR if the subscriber data for the CCBS SS are controlled by the gsmSCF. + +If the CCBS\_flag is set, then: + +- when the subscriber roams to a VLR which supports CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the CCBS SS as Active and Operative; +- when the subscriber roams to a VLR which does not support CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the CCBS SS as stored in the HLR; + +- the subscriber shall not be allowed to alter the CCBS data in the HLR. + +## 6.8 CLIR\_flag + +The CLIR\_flag shall be set in the HLR if the subscriber data for the CLIR SS are controlled by the gsmSCF. + +If the CLIR\_flag is set, then: + +- when the subscriber roams to a VLR which supports CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state of the CLIR SS as Active and Operative, and the presentation mode as "temporary (presentation allowed)"; +- when the subscriber roams to a VLR which does not support CAMEL Phase 3 or later, the HLR shall send to the VLR the activation state and presentation mode for the CLIR SS as stored in the HLR; +- the subscriber shall not be allowed to alter the CLIR data in the HLR. + +# --- 7 Description of Multiple Subscriber Profile + +## 7.1 Overview + +The MSP service allows the served subscriber to have several profiles, to distinguish between different telecommunication service requirements (e.g. business and home). This is described in 3G TS 22.097. Subscriber data specific to MSP is stored in the HLR and the gsmSCF. + +## 7.2 Registration of a Profile + +Registration of a profile allows the subscriber to register a provisioned profile to be used for mobile originated calls and activities. The request to register a profile shall contain the MSP code and the profile identity and will be sent to the gsmSCF using USSD, see 3G TS 23.078 and 3G TS 23.090. The registered profile is stored in the gsmSCF. In response to a successful registration request, the gsmSCF shall return a positive acknowledgement, including the identity of the registered profile, using USSD. + +The registration process in the gsmSCF is shown in figure 2. The information flow for successfully registering a profile is shown in figure 1. + +![Sequence diagram showing the Registration Process: information flow between MS, MSC, VLR, HLR, and gsmSCF.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + participant gsmSCF + + MS->>MSC: USSD Request (MSP code, Profile ID) + MSC->>VLR: USSD Request (MSP code, Profile ID) + VLR->>HLR: Process USS Request (MSP code, Profile ID) + HLR->>gsmSCF: Process USS Request (MSP code, Profile ID) + gsmSCF-->>HLR: Process USS Request ack (Profile ID) + HLR-->>VLR: Process USS Request ack (Profile ID) + VLR-->>MSC: USSD Response (Profile ID) + MSC-->>MS: USSD Response (Profile ID) +``` + +The diagram illustrates the information flow during a registration process involving five entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), HLR (Home Location Register), and gsmSCF (gsm Service Control Function). The sequence of messages is as follows: 1. MS sends a USSD Request (MSP code, Profile ID) to MSC. 2. MSC forwards the USSD Request (MSP code, Profile ID) to VLR. 3. VLR sends a Process USS Request (MSP code, Profile ID) to HLR. 4. HLR sends a Process USS Request (MSP code, Profile ID) to gsmSCF. 5. gsmSCF returns a Process USS Request ack (Profile ID) to HLR. 6. HLR returns a Process USS Request ack (Profile ID) to VLR. 7. VLR returns a USSD Response (Profile ID) to MSC. 8. MSC returns a USSD Response (Profile ID) to MS. + +Sequence diagram showing the Registration Process: information flow between MS, MSC, VLR, HLR, and gsmSCF. + +Figure 1: Registration Process: information flow + +![Flowchart for Process Register_MSP_gsmSCF](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +**Process Register\_MSP\_gsmSCF** **Reg\_MSP\_G\_1(1)** + +A process in the gsmSCF to register a profile. + +Signals to/from the left are to/from the HLR + +``` +graph TD; Idle1([Idle]) --> USSD{Process USS Request (MSP code, Profile ID)}; USSD --> MSP{MSP provisioned?}; MSP -- Yes --> Profile{Profile provisioned?}; MSP -- No --> Error1[Error := MSP not provisioned]; Profile -- Yes --> Reg[Registered profile := Profile ID]; Profile -- No --> Error2[Error := Profile not provisioned]; Reg --> Ack1{Process USS Request ack (Profile ID)}; Error1 --> Ack2{Process USS Request ack (Error)}; Error2 --> Ack2; Ack1 --> Idle2([Idle]); Ack2 --> Idle2; +``` + +The flowchart illustrates the process for registering an MSP profile in the gsmSCF. It begins with an 'Idle' state, followed by a 'Process USS Request' with 'MSP code' and 'Profile ID'. A decision diamond 'MSP provisioned?' follows. If 'No', an error 'Error := MSP not provisioned' is set, leading to 'Process USS Request ack (Error)'. If 'Yes', another decision diamond 'Profile provisioned?' follows. If 'No', an error 'Error := Profile not provisioned' is set, also leading to 'Process USS Request ack (Error)'. If 'Yes', 'Registered profile := Profile ID' is set, leading to 'Process USS Request ack (Profile ID)'. Both 'Process USS Request ack' paths lead to a final 'Idle' state. + +Flowchart for Process Register\_MSP\_gsmSCF + +**Figure 2: Process Register\_MSP\_gsmSCF** + +## 7.3 Interrogation + +The MS can interrogate MSP, using USSD, to identify which profiles are provisioned and which of the provisioned profiles is the currently registered profile. The interrogate MSP operation shall contain the MSP code and will be sent to the gsmSCF using USSD. In response to a successful interrogation request, the gsmSCF shall return the profile identity and profile status for each provisioned profile. If the MSP service is not provisioned then the gsmSCF shall return the service status indicating not provisioned. + +The interrogation process is shown in figure 4. The information flow for interrogation of MSP is shown in figure 3. + +![Sequence diagram showing information flow for interrogating MSP between MS, MSC, VLR, HLR, and gsmSCF.](cab0834804fb031b43865554cc8d06ab_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + participant gsmSCF + Note left of MS: + MS->>MSC: USSD Request (MSP code) + MSC->>VLR: USSD Request (MSP code) + VLR->>HLR: Process USS Request (MSP code) + HLR->>gsmSCF: Process USS Request (MSP code) + gsmSCF-->>HLR: Process USS Request ack (MSP info) + HLR-->>VLR: Process USS Request ack (MSP info) + VLR-->>MSC: USSD Response (MSP info) + MSC-->>MS: USSD Response (MSP info) +``` + +The diagram illustrates the information flow for interrogating an MSP. It involves five lifelines: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), HLR (Home Location Register), and gsmSCF (gsm Service Control Function). The sequence of messages is as follows: 1. MS sends a 'USSD Request (MSP code)' to MSC. 2. MSC sends a 'USSD Request (MSP code)' to VLR. 3. VLR sends a 'Process USS Request (MSP code)' to HLR. 4. HLR sends a 'Process USS Request (MSP code)' to gsmSCF. 5. gsmSCF returns a 'Process USS Request ack (MSP info)' to HLR. 6. HLR returns a 'Process USS Request ack (MSP info)' to VLR. 7. VLR returns a 'USSD Response (MSP info)' to MSC. 8. MSC returns a 'USSD Response (MSP info)' to MS. Each lifeline has a solid vertical line and a rectangular activation bar at the bottom. + +Sequence diagram showing information flow for interrogating MSP between MS, MSC, VLR, HLR, and gsmSCF. + +Figure 3: Interrogating MSP: information flow + +![Flowchart for Process Interrogate_MSP_gsmSCF. It starts at 'Idle', goes to 'Process USS Request (MSP code)', then checks 'MSP provisioned?'. If 'Yes', it calculates 'MSP info' and sends 'Process USS Request ack (MSP info)'. If 'No', it sets 'Error := MSP not provisioned' and sends 'Process USS Request ack (Error)'. Both acks lead back to 'Idle'. Notes indicate this is a gsmSCF process and signals are to/from the HLR.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +### Process Interrogate\_MSP\_gsmSCF + +Int\_MSP\_G\_1(1) + +``` +graph TD; Idle1([Idle]) --> Request{Process USS Request (MSP code)}; Request --> Provisioned{MSP provisioned?}; Provisioned -- Yes --> Info["MSP info := (Default profile ID, Registered profile ID, Other provisioned profiles)"]; Info --> AckYes{Process USS Request ack (MSP info)}; Provisioned -- No --> Error["Error := MSP not provisioned"]; Error --> AckNo{Process USS Request ack (Error)}; AckYes --> Idle2([Idle]); AckNo --> Idle2; +``` + +A process in the gsmSCF to interrogate MSP. + +Signals to/from the left are to/from the HLR + +Flowchart for Process Interrogate\_MSP\_gsmSCF. It starts at 'Idle', goes to 'Process USS Request (MSP code)', then checks 'MSP provisioned?'. If 'Yes', it calculates 'MSP info' and sends 'Process USS Request ack (MSP info)'. If 'No', it sets 'Error := MSP not provisioned' and sends 'Process USS Request ack (Error)'. Both acks lead back to 'Idle'. Notes indicate this is a gsmSCF process and signals are to/from the HLR. + +Figure 4: Process Interrogate\_MSP\_gsmSCF + +## 7.4 Call Handling for an MSP subscriber + +The procedure for handling MSP calls can be divided into two areas: mobile originating call handling and mobile terminating call handling. + +### 7.4.1 Mobile Originating (MO) call handling + +The served subscriber may use the registered profile or explicitly select a provisioned profile to set up an MO call. If the profile is explicitly selected, the selection information will be included in the called party BCD number and transported to the gsmSCF. If the gsmSCF recognises that a profile has not been explicitly selected (there is no profile selection information in the called party BCD number) then the registered profile is used. The MMI for explicitly selecting a profile is defined in 3G TS 22.030. + +The information flow for an MO call is shown in figure 28. + +When the gsmSCF receives an Initial\_DP message containing MO call parameters from the gsmSSF, the process MO\_MSP\_Call\_gsmSCF will be invoked, see figure 5. All other call handling is described in 3G TS 23.018 and 3G TS 23.078. + +### 7.4.2 Mobile Terminating (MT) call handling + +The profile used for an MT call to the served subscriber is determined by the called MSISDN. + +The information flow for an MT call is shown in figure 29. + +When the gsmSCF receives an Initial\_DP message containing MT call parameters from the gsmSSF, the process MT\_MSP\_Call\_gsmSCF will be invoked, see figure 8. All other call handling is described in 3G TS 23.018 and 3G TS 23.078. + +## 7.5 Functions and Information Flows + +### 7.5.1 MO call handling in the gsmSCF + +#### 7.5.1.1 Process MO\_MSP\_Call\_gsmSCF + +Handles an MO call for an MSP subscriber. See figure 5. + +#### 7.5.1.2 Procedure Set\_Calling\_Profile\_gsmSCF + +Sets the correct parameters for the calling profile. See figure 6. + +#### 7.5.1.3 Procedure Send\_FCI\_gsmSCF + +Sends a Furnish Charging Information message to the gsmSSF. See figure 7. + +![Flowchart for Process MO_MSP_Call_gsmSCF](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +**Process MO\_MSP\_Call\_gsmSCF** **MO\_MCG\_1(4)** + +A process in the gsmSCF to handle an MO call for an MSP subscriber. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; Idle1([Idle]) --> InitDP{Initial_DP (MO Parameters)}; InitDP --> ForwardedCall{Forwarded Call?}; ForwardedCall -- Yes --> ForwardedMSP[Forwarded_MSP_Call_gsmSCF]; ForwardedMSP --> Idle2([Idle]); ForwardedCall -- No --> SetProfile[Set Calling Profile_gsmSCF]; SetProfile --> ResponseMsg{Response_msg = Release?}; ResponseMsg -- Yes --> ReleaseCall{Release Call (Cause)}; ResponseMsg -- No --> OutgoingBarring[Outgoing_Barring_Check_gsmSCF]; OutgoingBarring --> ResultPass1{Result = Pass?}; ResultPass1 -- No --> ReleaseCall; ResultPass1 -- Yes --> CheckACM[Check_ACM_gsmSCF]; CheckACM --> ResultPass2{Result = Pass?}; ResultPass2 -- No --> ReleaseCall; ResultPass2 -- Yes --> SendFCI[Send_FCI_gsmSCF]; SendFCI --> Connector1((1)); ReleaseCall --> Idle3([Idle]); +``` + +The flowchart illustrates the process for handling an MO call for an MSP subscriber. It begins with an 'Idle' state, followed by 'Initial\_DP (MO Parameters)'. A decision 'Forwarded Call?' follows. If 'Yes', it proceeds to 'Forwarded\_MSP\_Call\_gsmSCF' and returns to 'Idle'. If 'No', it proceeds to 'Set Calling Profile\_gsmSCF'. A decision 'Response\_msg = Release?' follows. If 'Yes', it proceeds to 'Release Call (Cause)' and returns to 'Idle'. If 'No', it proceeds to 'Outgoing\_Barring\_Check\_gsmSCF'. A decision 'Result = Pass?' follows. If 'No', it proceeds to 'Release Call (Cause)' and returns to 'Idle'. If 'Yes', it proceeds to 'Check\_ACM\_gsmSCF'. Another decision 'Result = Pass?' follows. If 'No', it proceeds to 'Release Call (Cause)' and returns to 'Idle'. If 'Yes', it proceeds to 'Send\_FCI\_gsmSCF' and then to connector '1'. + +Flowchart for Process MO\_MSP\_Call\_gsmSCF + +**Figure 5a: Process MO\_MSP\_Call\_gsmSCF (sheet 1 of 4)** + +![Flowchart for Process MO_MSP_Call_gsmSCF. It starts at connector 1, goes to 'Request Report BCSM Event' (which contains O_Answer as EDP-R and O_Disconnect as EDP-N), then sequentially checks CLIR, CW, HOLD, MPTY, ECT, and CCBS using gsmSCF functions, and ends at connector 2.](8307f6b04df072c9332f9987e034272c_img.jpg) + +**Process MO\_MSP\_Call\_gsmSCF** **MO\_MCG\_2(4)** + +A process in the gsmSCF to handle an MO call for an MSP subscriber. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; 1((1)) --> R[Request Report BCSM Event]; R --> C1[Check_CLIR_gsmSCF]; C1 --> C2[Check_CW_gsmSCF]; C2 --> C3[Check_HOLD_gsmSCF]; C3 --> C4[Check_MPTY_gsmSCF]; C4 --> C5[Check_ECT_gsmSCF]; C5 --> C6[Check_CCBS_gsmSCF]; C6 --> 2((2)); +``` + +Contains: +O\_Answer as EDP-R +O\_Disconnect as EDP-N + +Flowchart for Process MO\_MSP\_Call\_gsmSCF. It starts at connector 1, goes to 'Request Report BCSM Event' (which contains O\_Answer as EDP-R and O\_Disconnect as EDP-N), then sequentially checks CLIR, CW, HOLD, MPTY, ECT, and CCBS using gsmSCF functions, and ends at connector 2. + +**Figure 5b: Process MO\_MSP\_Call\_gsmSCF (sheet 2 of 4)** + +![Flowchart for Process MO_MSP_Call_gsmSCF. It starts at connector 2, checks if SII2 is True. If Yes, it goes to Connect. If No, it checks if Response_msg = Connect. If Yes, it goes to Connect. If No, it goes to Continue. Both Continue and Connect lead to Wait_for_Event_Report. From there, it branches into three paths: 1) Event BCSM (Notify and Continue) leading to Idle (labeled O_Disconnect); 2) Event BCSM (Interrupted) leading to connector 3; 3) SS Invocation Notification (CCBS request) leading to Wait_for_CCBS_Setup, then SS Invocation Notification (CCBS call setup), Store CCBS call information, Cancel All, and finally Idle (labeled O_Answer).](4356776ca004ecba5d599667a155d7d4_img.jpg) + +### Process MO\_MSP\_Call\_gsmSCF + +MO\_MCG\_3(4) + +A process in the gsmSCF to handle an MO call for an MSP subscriber. + +Signals to/from the left are to/from the gsmSSF. Signals to/from the right are to/from the HLR. + +Connect may contain Destination Routing Address, Generic Number and SII2 + +``` +graph TD; 2((2)) --> SII2{SII2 = True?}; SII2 -- Yes --> Connect{{Connect}}; SII2 -- No --> Response{Response_msg = Connect?}; Response -- Yes --> Connect; Response -- No --> Continue{{Continue}}; Continue --> Wait[Wait_for_Event_Report]; Connect --> Wait; Wait --> Event1{{Event BCSM (Notify and Continue)}}; Wait --> Event2{{Event BCSM (Interrupted)}}; Wait --> Event3{{SS Invocation Notification (CCBS request)}}; Event1 --> Idle1([Idle]); Event2 --> 3((3)); Event3 --> WaitCCBS[Wait_for_CCBS_Setup]; WaitCCBS --> Event4{{SS Invocation Notification (CCBS call setup)}}; Event4 --> Store[Store CCBS call information]; Store --> Cancel{{Cancel All}}; Cancel --> Idle2([Idle]); +``` + +This will be O\_Disconnect + +This will be O\_Answer + +Flowchart for Process MO\_MSP\_Call\_gsmSCF. It starts at connector 2, checks if SII2 is True. If Yes, it goes to Connect. If No, it checks if Response\_msg = Connect. If Yes, it goes to Connect. If No, it goes to Continue. Both Continue and Connect lead to Wait\_for\_Event\_Report. From there, it branches into three paths: 1) Event BCSM (Notify and Continue) leading to Idle (labeled O\_Disconnect); 2) Event BCSM (Interrupted) leading to connector 3; 3) SS Invocation Notification (CCBS request) leading to Wait\_for\_CCBS\_Setup, then SS Invocation Notification (CCBS call setup), Store CCBS call information, Cancel All, and finally Idle (labeled O\_Answer). + +Figure 5c: Process MO\_MSP\_Call\_gsmSCF (sheet 3 of 4) + +![State transition diagram for Process MO_MSP_Call_gsmSCF. The diagram shows a sequence of states and transitions: 3 (initial state) -> Start AoC (Call Information) -> Wait_for_AoC_ack -> AoC ack -> Request Report BCSM Event (O_Disconnect) -> Continue -> Ongoing_call. From Ongoing_call, there are two possible transitions: Event BCSM (labeled 'This will be O_Disconnect') leading to Call ended, and Release call (Cause) leading to Release call (Cause). Both Call ended and Release call (Cause) lead to Idle.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +### Process MO\_MSP\_Call\_gsmSCF + +MO\_MCG\_4(4) + +A process in the gsmSCF to handle an MO call for an MSP subscriber. + +Signals to/from the left are to/from the gsmSSF. Signals to/from the right are to/from the process AoC\_MSP\_gsmSCF. + +``` +stateDiagram-v2 + [*] --> Start_AoC : 3 + Start_AoC --> Wait_for_AoC_ack + Wait_for_AoC_ack --> AoC_ack + AoC_ack --> Request_Report_BCSM_Event : Request Report BCSM Event (O_Disconnect) + Request_Report_BCSM_Event --> Continue + Continue --> Ongoing_call + state "Ongoing_call" as Ongoing_call + Ongoing_call --> Event_BCSM : Event BCSM + Ongoing_call --> Release_call_Cause_1 : Release call (Cause) + Note left of Event_BCSM : This will be O_Disconnect + Event_BCSM --> Call_ended : Call ended + Release_call_Cause_1 --> Release_call_Cause_2 : Release call (Cause) + Call_ended --> Idle + Release_call_Cause_2 --> Idle +``` + +State transition diagram for Process MO\_MSP\_Call\_gsmSCF. The diagram shows a sequence of states and transitions: 3 (initial state) -> Start AoC (Call Information) -> Wait\_for\_AoC\_ack -> AoC ack -> Request Report BCSM Event (O\_Disconnect) -> Continue -> Ongoing\_call. From Ongoing\_call, there are two possible transitions: Event BCSM (labeled 'This will be O\_Disconnect') leading to Call ended, and Release call (Cause) leading to Release call (Cause). Both Call ended and Release call (Cause) lead to Idle. + +Figure 5d: Process MO\_MSP\_Call\_gsmSCF (sheet 4 of 4) + +![Flowchart for Procedure Set_Calling_Profile_gsmSCF](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +### Procedure Set\_Calling\_Profile\_gsmSCF + +SCPG\_1(1) + +A procedure in the gsmSCF to set the correct parameters for the calling profile. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; Start([ ]) --> Decision1{Is profile explicitly selected in Called Party Number}; Decision1 -- No --> Process1[Calling profile := Registered profile]; Decision1 -- Yes --> Process2[Calling profile := Selected profile]; Process1 --> Decision2{Calling profile = Default profile?}; Process2 --> Process3[Destination Routing Address := Called Party Number without explicit profile selection]; Process3 --> Decision3{Calling profile = Default profile?}; Decision2 -- Yes --> Response1[Response_msg := Continue]; Decision2 -- No --> Process4[Set Additional Calling Party Number to MSISDN of Calling profile]; Decision3 -- No --> Process4; Decision3 -- Yes --> Response2[Response_msg := Connect]; Process4 --> Response2; Response1 --> End(( )); Response2 --> End; +``` + +The flowchart illustrates the procedure for setting the calling profile in the gsmSCF. It begins with a start symbol leading to a decision: "Is profile explicitly selected in Called Party Number". If "No", the calling profile is set to the "Registered profile". If "Yes", the calling profile is set to the "Selected profile". Both paths lead to a decision: "Calling profile = Default profile?". If "Yes", the response message is "Continue". If "No", the procedure sets the "Additional Calling Party Number to MSISDN of Calling profile". This path then leads to a second decision: "Calling profile = Default profile?". If "No", it loops back to the "Set Additional Calling Party Number" process. If "Yes", the response message is "Connect". Both "Continue" and "Connect" response messages lead to the end symbol. + +Flowchart for Procedure Set\_Calling\_Profile\_gsmSCF + +Figure 6: Procedure Set\_Calling\_Profile\_gsmSCF + +![Flowchart for Procedure Send_FCI_gsmSCF](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +**Procedure Send\_FCI\_gsmSCF** **SFCIG\_1(1)** + +A procedure in the gsmSCF to send a Furnish Charging Information message. + +Signals to/from the left are to/from the gsmSSF. + +``` + +graph TD + Start([ ]) --> Step1[Set data for Furnish Charging Information] + Step1 --> Step2{{Furnish +Charging +Information +(Profile ID)}} + Step2 --> End((X)) + +``` + +The flowchart illustrates the procedure 'Send\_FCI\_gsmSCF'. It begins with a start symbol (an oval with a vertical line), followed by a process block 'Set data for Furnish Charging Information'. This leads to an output signal block (a polygon with a pointed left side) containing 'Furnish Charging Information (Profile ID)'. The flowchart ends with an end symbol (a circle with an 'X'). + +Flowchart for Procedure Send\_FCI\_gsmSCF + +**Figure 7: Procedure Send\_FCI\_gsmSCF** + +### 7.5.2 MT call handling in the gsmSCF + +#### 7.5.2.1 Process MT\_MSP\_Call\_gsmSCF + +Handles an MT call for an MSP subscriber. See figure 8. + +![Flowchart for Process MT_MSP_Call_gsmSCF. The process starts at 'Idle', receives 'Initial_DP (MT parameters)', sets the called profile, checks CFU, then checks incoming barring, then checks ACM. If any check fails, it returns to 'Idle'. If all checks pass, it proceeds to connector '1'.](5793a44ffdadd039928e2f9fe6daae06_img.jpg) + +**Process MT\_MSP\_Call\_gsmSCF** **MT\_MCG\_1(5)** + +A process in the gsmSCF to handle an MT call for an MSP subscriber. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; Idle1([Idle]) --> Initial_DP[/Initial_DP (MT parameters)/]; Initial_DP --> Set_Profile[Set Called profile according to called MSISDN]; Set_Profile --> Check_CFU[Check_CFU_gsmSCF]; Check_CFU --> Result_Continue{Result = Continue?}; Result_Continue -- No --> Idle2([Idle]); Result_Continue -- Yes --> Incoming_Barring[Incoming_Barring_Check_gsmSCF]; Incoming_Barring --> Result_Pass1{Result = Pass?}; Result_Pass1 -- No --> Idle2; Result_Pass1 -- Yes --> Check_ACM[Check_ACM_gsmSCF]; Check_ACM --> Result_Pass2{Result = Pass?}; Result_Pass2 -- No --> Idle2; Result_Pass2 -- Yes --> One((1)); +``` + +Flowchart for Process MT\_MSP\_Call\_gsmSCF. The process starts at 'Idle', receives 'Initial\_DP (MT parameters)', sets the called profile, checks CFU, then checks incoming barring, then checks ACM. If any check fails, it returns to 'Idle'. If all checks pass, it proceeds to connector '1'. + +Figure 8a: Process MT\_MSP\_Call\_gsmSCF (sheet 1 of 5) + +![Flowchart for Process MT_MSP_Call_gsmSCF. It starts at connector 1, proceeds to Check_Early_CF_gsmSCF, then Send_FCI_gsmSCF. A decision diamond 'Result = Continue?' follows. If 'No', it goes to an 'Idle' state. If 'Yes', it proceeds through a series of checks: Check_Late_CF_gsmSCF, Check_CW_gsmSCF, Check_HOLD_gsmSCF, Check_MPTY_gsmSCF, Check_ECT_gsmSCF, and Check_CCBS_gsmSCF, ending at connector 2.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +**Process MT\_MSP\_Call\_gsmSCF** **MT\_MCG\_2(5)** + +A process in the gsmSCF to handle an MT call for an MSP subscriber. + +``` +graph TD; 1((1)) --> A[Check_Early_CF_gsmSCF]; A --> B[Send_FCI_gsmSCF]; B --> C{Result = Continue?}; C -- No --> D([Idle]); C -- Yes --> E[Check_Late_CF_gsmSCF]; E --> F[Check_CW_gsmSCF]; F --> G[Check_HOLD_gsmSCF]; G --> H[Check_MPTY_gsmSCF]; H --> I[Check_ECT_gsmSCF]; I --> J[Check_CCBS_gsmSCF]; J --> K((2)); +``` + +Flowchart for Process MT\_MSP\_Call\_gsmSCF. It starts at connector 1, proceeds to Check\_Early\_CF\_gsmSCF, then Send\_FCI\_gsmSCF. A decision diamond 'Result = Continue?' follows. If 'No', it goes to an 'Idle' state. If 'Yes', it proceeds through a series of checks: Check\_Late\_CF\_gsmSCF, Check\_CW\_gsmSCF, Check\_HOLD\_gsmSCF, Check\_MPTY\_gsmSCF, Check\_ECT\_gsmSCF, and Check\_CCBS\_gsmSCF, ending at connector 2. + +**Figure 8b: Process MT\_MSP\_Call\_gsmSCF (sheet 2 of 5)** + +![Flowchart for Process MT_MSP_Call_gsmSCF. It starts at connector '2', goes to 'Check_CD_gsmSCF', then to a decision 'Does Called profile require specific Alerting Pattern?'. If 'Yes', it goes to 'Set Alerting Pattern'. If 'No', it goes to 'SI2 = True?'. Both 'Set Alerting Pattern' and 'SI2 = True?' (if 'Yes') lead to 'Connect'. 'SI2 = True?' (if 'No') leads to 'Continue'. Both 'Continue' and 'Connect' lead to 'Wait_For_Event_Report'. A note indicates 'Connect' contains SI2 and/or Alerting pattern if applicable.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +**Process MT\_MSP\_Call\_gsmSCF** **MT\_MCG\_3(5)** + +A process in the gsmSCF to handle an MT call for an MSP subscriber. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; Start((2)) --> Check[Check_CD_gsmSCF]; Check --> Decision1{Does Called profile require specific Alerting Pattern?}; Decision1 -- Yes --> Set[Set Alerting Pattern]; Decision1 -- No --> Decision2{SI2 = True?}; Set --> Connect{{Connect}}; Decision2 -- Yes --> Connect; Decision2 -- No --> Continue{{Continue}}; Continue --> Wait([Wait_For_Event_Report]); Connect --> Wait; Note1[Contains SI2 and/or Alerting pattern if applicable] -.-> Connect; +``` + +Flowchart for Process MT\_MSP\_Call\_gsmSCF. It starts at connector '2', goes to 'Check\_CD\_gsmSCF', then to a decision 'Does Called profile require specific Alerting Pattern?'. If 'Yes', it goes to 'Set Alerting Pattern'. If 'No', it goes to 'SI2 = True?'. Both 'Set Alerting Pattern' and 'SI2 = True?' (if 'Yes') lead to 'Connect'. 'SI2 = True?' (if 'No') leads to 'Continue'. Both 'Continue' and 'Connect' lead to 'Wait\_For\_Event\_Report'. A note indicates 'Connect' contains SI2 and/or Alerting pattern if applicable. + +Figure 8c: Process MT\_MSP\_Call\_gsmSCF (sheet 3 of 5) + +![Flowchart for Process MT_MSP_Call_gsmSCF. It starts with 'Wait_For_Event_Report', leading to 'Event BCSM (Notify and Continue)' and 'Event BCSM (Interrupted)'. The 'Notify and Continue' path leads to 'Cancel all' and 'Idle'. The 'Interrupted' path leads to a series of decision diamonds: 'Event = T_Answer?', 'Event = T_No_Answer?', 'Cause = Busy?', and 'Result = Continue?'. It also includes process blocks 'Check_CFNRY_gsmSCF', 'Check_CFNRC_gsmSCF', and 'Check_CFB_gsmSCF', and signal labels 'T_Abandon, T_Busy or T_No_Answer' and 'T_Answer, T_Busy or T_No_Answer'. The process ends at 'Idle' or connector '3'.](26d664119ad25250780f554633444e54_img.jpg) + +### Process MT\_MSP\_Call\_gsmSCF + +MT\_MCG\_4(5) + +A process in the gsmSCF to handle an MT call for an MSP subscriber. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; Start([Wait_For_Event_Report]) --> Event1{{Event BCSM (Notify and Continue)}}; Start --> Event2{{Event BCSM (Interrupted)}}; Event1 --> Cancel{Cancel all}; Cancel --> Idle1([Idle]); Event2 --> T_Answer{Event = T_Answer?}; T_Answer -- Yes --> 3((3)); T_Answer -- No --> T_No_Answer{Event = T_No_Answer?}; T_No_Answer -- Yes --> Check_CFNRY[Check_CFNRY_gsmSCF]; T_No_Answer -- No --> Cause_Busy{Cause = Busy?}; Cause_Busy -- Yes --> Check_CFB[Check_CFB_gsmSCF]; Cause_Busy -- No --> Check_CFNRC[Check_CFNRC_gsmSCF]; Check_CFNRY --> Join(( )); Check_CFNRC --> Join; Check_CFB --> Join; Join --> Result_Continue{Result = Continue?}; Result_Continue -- Yes --> Continue{Continue}; Continue --> Idle2([Idle]); Result_Continue -- No --> Idle2; Event1 -.-> T_Abandon[T_Abandon, T_Busy or T_No_Answer]; Event2 -.-> T_Answer_Signal[T_Answer, T_Busy or T_No_Answer]; +``` + +Flowchart for Process MT\_MSP\_Call\_gsmSCF. It starts with 'Wait\_For\_Event\_Report', leading to 'Event BCSM (Notify and Continue)' and 'Event BCSM (Interrupted)'. The 'Notify and Continue' path leads to 'Cancel all' and 'Idle'. The 'Interrupted' path leads to a series of decision diamonds: 'Event = T\_Answer?', 'Event = T\_No\_Answer?', 'Cause = Busy?', and 'Result = Continue?'. It also includes process blocks 'Check\_CFNRY\_gsmSCF', 'Check\_CFNRC\_gsmSCF', and 'Check\_CFB\_gsmSCF', and signal labels 'T\_Abandon, T\_Busy or T\_No\_Answer' and 'T\_Answer, T\_Busy or T\_No\_Answer'. The process ends at 'Idle' or connector '3'. + +Figure 8d: Process MT\_MSP\_Call\_gsmSCF (sheet 4 of 5) + +![Flowchart for Process MT_MSP_Call_gsmSCF. The process starts at connector '3', proceeds to 'Start AoC (Call Information)', then 'Wait_for_AoC_ack', 'AoC ack', 'Continue', and 'Ongoing_Call'. From 'Ongoing_Call', it branches to 'Release call (Cause)' (left) and 'Event BCSM (Notify and Continue)' (right). 'Event BCSM' leads to 'Call ended' and then 'Idle', with a note 'This will be T_Disconnect'. 'Release call (Cause)' leads to another 'Release call (Cause)' block, which then leads to 'Idle'. A separate vertical flow on the right shows 'Wait_For_Event_Report', 'SS Notification Invocation (CD)' (From MSC), 'Store CD call information', 'Cancel All', and 'Idle'.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +### Process MT\_MSP\_Call\_gsmSCF + +MT\_MCG\_5(5) + +A process in the gsmSCF to handle an MT call for an MSP subscriber. + +Signals to/from the left are to/from the gsmSSF. Signals to/from the right are to/from the process AoC\_MSP\_gsmSCF unless stated otherwise. + +``` +graph TD; 3((3)) --> StartAoC[Start AoC (Call Information)]; StartAoC --> WaitAoCack[Wait_for_AoC_ack]; WaitAoCack --> AoCack[AoC ack]; AoCack --> Continue[Continue]; Continue --> OngoingCall[Ongoing_Call]; OngoingCall --> ReleaseCall1[Release call (Cause)]; OngoingCall --> EventBCSM[Event BCSM (Notify and Continue)]; EventBCSM --> CallEnded[Call ended]; CallEnded --> Idle1[Idle]; ReleaseCall1 --> ReleaseCall2[Release call (Cause)]; ReleaseCall2 --> Idle2[Idle]; Note1[This will be T_Disconnect] -.-> EventBCSM; WaitForEventReport[Wait_For_Event_Report] --> SSNotification[SS Notification Invocation (CD)]; SSNotification --> StoreCD[Store CD call information]; StoreCD --> CancelAll[Cancel All]; CancelAll --> Idle3[Idle]; FromMSC[From MSC] -.-> SSNotification; +``` + +Flowchart for Process MT\_MSP\_Call\_gsmSCF. The process starts at connector '3', proceeds to 'Start AoC (Call Information)', then 'Wait\_for\_AoC\_ack', 'AoC ack', 'Continue', and 'Ongoing\_Call'. From 'Ongoing\_Call', it branches to 'Release call (Cause)' (left) and 'Event BCSM (Notify and Continue)' (right). 'Event BCSM' leads to 'Call ended' and then 'Idle', with a note 'This will be T\_Disconnect'. 'Release call (Cause)' leads to another 'Release call (Cause)' block, which then leads to 'Idle'. A separate vertical flow on the right shows 'Wait\_For\_Event\_Report', 'SS Notification Invocation (CD)' (From MSC), 'Store CD call information', 'Cancel All', and 'Idle'. + +Figure 8e: Process MT\_MSP\_Call\_gsmSCF (sheet 5 of 5) + +### 7.5.3 SS handling in the gsmSCF + +#### 7.5.3.1 Procedure Check\_CLIR\_gsmSCF + +Checks whether the CLI Presentation Indicator shall be set to Presentation Restricted. See figure 9. + +#### 7.5.3.2 Procedure Forwarded\_MSP\_Call\_gsmSCF + +Sets the parameters for a forwarded or deflected call. See figure 10. + +#### 7.5.3.3 Procedure Check\_CFU\_gsmSCF + +Applies CFU to the MT Call if Active and Operative for the Called profile. See figure 11. + +#### 7.5.3.4 Procedure Check\_Early\_CF\_gsmSCF + +Checks whether any early Call Forwarding apply to the Called profile. See figure 12 + +#### 7.5.3.5 Procedure Check\_Late\_CF\_gsmSCF + +Arms the detection points required for the provisioned late Call Forwardings on the Called profile. See figure 13. + +#### 7.5.3.6 Procedure Check\_CFNRy\_gsmSCF + +Applies CFNRy to the MT call if Active and Operative for the Called profile. See figure 14. + +#### 7.5.3.7 Procedure Check\_CFB\_gsmSCF + +Applies CFB to the MT call if Active and Operative for the Called profile. See figure 15. + +#### 7.5.3.8 Procedure Check\_CFNRc\_gsmSCF + +Applies CFNRc to the MT call if Active and Operative for the Called profile. See figure 16. + +#### 7.5.3.9 Procedure Check\_CW\_gsmSCF + +Checks whether CW is allowed during the current call. See figure 17. + +#### 7.5.3.10 Procedure Check\_HOLD\_gsmSCF + +Checks whether a HOLD request shall be accepted or rejected during the ongoing call. See figure 18. + +#### 7.5.3.11 Procedure Check\_MPTY\_gsmSCF + +Checks whether an MPTY request shall be accepted or rejected during the ongoing call. See figure 19. + +#### 7.5.3.12 Procedure Check\_ACM\_gsmSCF + +Ensures that ACMmax is not exceeded for the profile in use. See figure 20. + +#### 7.5.3.13 Process AoC\_MSP\_gsmSCF + +Applies AoC per profile. See figure 21. + +#### 7.5.3.14 Procedure AoCI\_gsmSCF + +Applies AoCI per profile. See figure 22. + +#### 7.5.3.15 Procedure AoCC\_gsmSCF + +Applies AoCC per profile. See figure 23. + +#### 7.5.3.16 Procedure Outgoing\_Barring\_Check\_gsmSCF + +Checks the outgoing call barrings for an MSP subscriber. See figure 24. + +#### 7.5.3.17 Procedure Incoming\_Barring\_Check\_gsmSCF + +Checks the incoming barrings for the Called profile. See figure 25. + +#### 7.5.3.18 Procedure Check\_ECT\_gsmSCF + +Checks whether an ECT request shall be accepted or rejected during the ongoing call. See figure 26. + +#### 7.5.3.19 Procedure Check\_CCBS\_gsmSCF + +Checks whether a CCBS request can be planted by/against the MSP subscriber. See figure 27. + +![Flowchart for Procedure Check_CLIR_gsmSCF](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +### Procedure Check\_CLIR\_gsmSCF + +C\_CLIR\_G\_1(1) + +A procedure in the gsmSCF to set the CLI Presentation Indicator. + +``` +graph TD; Start([ ]) --> Q1{CLIR provisioned per profile?}; Q1 -- No --> End1(( )); Q1 -- Yes --> Q2{CLIR set to "Restricted" for calling profile?}; Q2 -- No --> End1; Q2 -- Yes --> P1[Calling Party Restriction Indicator := Presentation Restricted]; P1 --> P2[SII2 := True]; P2 --> End2(( )); P2 -.-> InSII2[In SII2]; +``` + +The flowchart illustrates the procedure Check\_CLIR\_gsmSCF. It begins with a start symbol (oval with vertical line) leading to a decision diamond: "CLIR provisioned per profile?". If the answer is "No", the flow proceeds to an end symbol (circle with X). If the answer is "Yes", it proceeds to another decision diamond: "CLIR set to 'Restricted' for calling profile?". If the answer is "No", the flow proceeds to the same end symbol. If the answer is "Yes", it proceeds to a process block: "Calling Party Restriction Indicator := Presentation Restricted". This is followed by another process block: "SII2 := True". From this block, the flow proceeds to a second end symbol (circle with X). A dashed box labeled "In SII2" is connected to the "SII2 := True" block. + +Flowchart for Procedure Check\_CLIR\_gsmSCF + +Figure 9: Procedure Check\_CLIR\_gsmSCF + +![Flowchart for Procedure Forwarded_MSP_Call_gsmSCF. It starts with a connector, followed by two decision diamonds: 'Call Forwarding provisioned per subscriber?' and 'CD provisioned per subscriber?'. If either is 'Yes', it goes to 'Continue'. If both are 'No', it goes to 'Retrieve stored CD Call Information'. Then a decision 'Call Deflection A&O for Calling Profile?'. If 'Yes', it goes to 'Send_FCI_gsmSCF'. Then a decision 'Calling Profile = Default Profile?'. If 'Yes', it goes to 'Continue'. If 'No', it goes to 'Set Additional Calling Party Number to MSISDN of Calling Profile'. From there, it goes to 'Connect (Generic Number)'. If 'Call Deflection A&O for Calling Profile?' was 'No', it goes to 'Set Cause' then 'Release Call (Cause)'. All three paths ('Continue', 'Connect', 'Release') lead to a merge connector.](dd5771673aececa53d42ece89218299d_img.jpg) + +### Procedure Forwarded\_MSP\_Call\_gsmSCF + +FWD\_MCG\_1(1) + +A procedure in the gsmSCF to set the correct parameters for a forwarded or deflected call. + +``` +graph TD; Start([ ]) --> D1{Call Forwarding provisioned per subscriber?}; D1 -- Yes --> Continue{Continue}; D1 -- No --> D2{CD provisioned per subscriber?}; D2 -- Yes --> Continue; D2 -- No --> P1[Retrieve stored CD Call Information]; P1 --> D3{Call Deflection A&O for Calling Profile?}; D3 -- Yes --> P2[Send_FCI_gsmSCF]; P2 --> D4{Calling Profile = Default Profile?}; D4 -- Yes --> Continue; D4 -- No --> P3[Set Additional Calling Party Number to MSISDN of Calling Profile]; P3 --> C{Connect (Generic Number)}; D3 -- No --> P4[Set Cause]; P4 --> R{Release Call (Cause)}; R --> Merge(( )); C --> Merge; Continue --> Merge; +``` + +Flowchart for Procedure Forwarded\_MSP\_Call\_gsmSCF. It starts with a connector, followed by two decision diamonds: 'Call Forwarding provisioned per subscriber?' and 'CD provisioned per subscriber?'. If either is 'Yes', it goes to 'Continue'. If both are 'No', it goes to 'Retrieve stored CD Call Information'. Then a decision 'Call Deflection A&O for Calling Profile?'. If 'Yes', it goes to 'Send\_FCI\_gsmSCF'. Then a decision 'Calling Profile = Default Profile?'. If 'Yes', it goes to 'Continue'. If 'No', it goes to 'Set Additional Calling Party Number to MSISDN of Calling Profile'. From there, it goes to 'Connect (Generic Number)'. If 'Call Deflection A&O for Calling Profile?' was 'No', it goes to 'Set Cause' then 'Release Call (Cause)'. All three paths ('Continue', 'Connect', 'Release') lead to a merge connector. + +Figure 10: Procedure Forwarded\_MSP\_Call\_gsmSCF + +![Flowchart for Procedure Check_CFU_gsmSCF](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +### Procedure Check\_CFU\_gsmSCF + +C\_CFU\_G\_1(1) + +A procedure in the gsmSCF to apply CFU to the MT call if Active and Operative for the Called profile. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; Start([Start]) --> D1{CFU provisioned per profile?}; D1 -- No --> R1[Result := Continue]; D1 -- Yes --> D2{CFU A&O for Called profile?}; D2 -- No --> R1; D2 -- Yes --> P1[Set CFU data]; P1 --> P2[Outgoing_Barring_Check_gsmSCF]; P2 --> D3{Result = Pass?}; D3 -- No --> R3[Result := Release]; D3 -- Yes --> R2[Result := Forward]; R1 --> J(( )); R2 --> C1{Connect (FTN, Original Called Party ID, Redirecting Info)}; C1 --> J; R3 --> C2{Release Call (Cause)}; C2 --> J; +``` + +The flowchart illustrates the 'Check\_CFU\_gsmSCF' procedure. It begins with a start connector, leading to a decision 'CFU provisioned per profile?'. If 'No', the result is 'Continue'. If 'Yes', it proceeds to 'CFU A&O for Called profile?'. If 'No', the result is 'Continue'. If 'Yes', it proceeds to 'Set CFU data', then 'Outgoing\_Barring\_Check\_gsmSCF'. From there, it checks 'Result = Pass?'. If 'No', the result is 'Release'. If 'Yes', the result is 'Forward'. The 'Continue' result leads directly to the exit connector. The 'Forward' result leads to 'Connect (FTN, Original Called Party ID, Redirecting Info)', which then leads to the exit connector. The 'Release' result leads to 'Release Call (Cause)', which then leads to the exit connector. + +Flowchart for Procedure Check\_CFU\_gsmSCF + +Figure 11: Procedure Check\_CFU\_gsmSCF + +![Flowchart for Procedure Check_Early_CF_gsmSCF. It starts with a connector, then checks if the subscriber state is not reachable. If yes, it goes to Check_CFNRC_gsmSCF. If no, it checks if the subscriber state is busy. If yes, it goes to Check_CFB_gsmSCF. If no, it checks if the subscriber state is CAMEL busy. If yes, it goes to Check_CFB_gsmSCF. If no, it sets the result to Continue and goes to a connector. Both Check_CFB_gsmSCF and Check_CFNRC_gsmSCF lead to a 'Result = Continue?' decision. If Yes, it goes to a common 'Result := Release' block. If No, it goes to 'Result := Forward' and then to a connector. The 'Result := Release' block leads to 'Set Cause' and then to 'Release Call (Cause)' and finally to a connector.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +### Procedure Check\_Early\_CF\_gsmSCF + +CECFG\_1(1) + +A procedure in the gsmSCF to check if any early Call Forwardings apply to the called profile. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; Start([ ]) --> D1{Subscriber State = Not Reachable?}; D1 -- Yes --> P2[Check_CFNRC_gsmSCF]; D1 -- No --> D2{Subscriber State = Busy?}; D2 -- Yes --> P1[Check_CFB_gsmSCF]; D2 -- No --> D3{Subscriber State = CAMEL busy?}; D3 -- Yes --> P1; D3 -- No --> P3[Result := Continue]; P3 --> C1(( )); P1 --> D4{Result = Continue?}; P2 --> D5{Result = Continue?}; D4 -- Yes --> P4[Result := Release]; D4 -- No --> P5[Result := Forward]; P5 --> C2(( )); D5 -- Yes --> P4; D5 -- No --> P6[Result := Forward]; P6 --> C3(( )); P4 --> P7[Set Cause]; P7 --> P8[/Release Call (Cause)/]; P8 --> C4(( )); +``` + +Flowchart for Procedure Check\_Early\_CF\_gsmSCF. It starts with a connector, then checks if the subscriber state is not reachable. If yes, it goes to Check\_CFNRC\_gsmSCF. If no, it checks if the subscriber state is busy. If yes, it goes to Check\_CFB\_gsmSCF. If no, it checks if the subscriber state is CAMEL busy. If yes, it goes to Check\_CFB\_gsmSCF. If no, it sets the result to Continue and goes to a connector. Both Check\_CFB\_gsmSCF and Check\_CFNRC\_gsmSCF lead to a 'Result = Continue?' decision. If Yes, it goes to a common 'Result := Release' block. If No, it goes to 'Result := Forward' and then to a connector. The 'Result := Release' block leads to 'Set Cause' and then to 'Release Call (Cause)' and finally to a connector. + +Figure 12: Procedure Check\_Early\_CF\_gsmSCF + +![Flowchart for Procedure Check_Late_CF_gsmSCF](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +**Procedure Check\_Late\_CF\_gsmSCF** CLCFG\_1(1) + +A procedure in the gsmSCF to arm the detection points required for the provisioned late Call Forwardings on the Called profile. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; Start([ ]) --> Init["Arm_DP_List := (T_Answer as EDP-R, T_Abandon as EDP-N)"]; Init --> D1{CFB A&O For Called profile?}; D1 -- No --> D2{CFNRc A&O for Called profile?}; D1 -- Yes --> A1["Add T_Busy to Arm_DP_List as EDP-R"]; D2 -- Yes --> A1; D2 -- No --> A2["Add T_Busy to Arm_DP_List as EDP-N"]; A1 --> D3{CFNRy A&O for Called profile?}; A2 --> D3; D3 -- Yes --> A3["Add T_No_Answer to Arm_DP_List as EDP-R"]; D3 -- No --> A4["Add T_No_Answer to Arm_DP_List as EDP-N"]; A3 --> R1{{Request Report BCSM_Event (Arm_DP_List)}}; A4 --> R1; R1 --> End((X)) +``` + +The flowchart illustrates the procedure for checking late call forwarding (CF) settings. It begins with an initialization of the Arm\_DP\_List containing T\_Answer as EDP-R and T\_Abandon as EDP-N. It then enters a loop of decision diamonds: 'CFB A&O For Called profile?', 'CFNRc A&O for Called profile?', and 'CFNRy A&O for Called profile?'. Depending on the 'Yes' or 'No' outcomes, specific detection points (T\_Busy or T\_No\_Answer) are added to the Arm\_DP\_List as either EDP-R or EDP-N. All paths converge to a 'Request Report BCSM\_Event (Arm\_DP\_List)' block, which leads to the end of the procedure. + +Flowchart for Procedure Check\_Late\_CF\_gsmSCF + +Figure 13: Procedure Check\_Late\_CF\_gsmSCF + +![Flowchart for Procedure Check_CFNRy_gsmSCF](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +### Procedure Check\_CFNRy\_gsmSCF + +C\_CFNRy\_G\_1(1) + +A procedure in the gsmSCF to apply CFNRy to the MT call if Active and Operative for the Called profile. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; Start([Start]) --> Decision1{CFNRy A&O for Called profile?}; Decision1 -- No --> ResultContinue[Result := Continue]; Decision1 -- Yes --> SetData[Set CFNRy data]; SetData --> OutgoingBarring[Outgoing_Barring_Check_gsmSCF]; OutgoingBarring --> Decision2{Result = Pass?}; Decision2 -- No --> ResultRelease[Result := Release]; Decision2 -- Yes --> ResultForward[Result := Forward]; ResultContinue --> Connect{Connect (FTN, Original Called Party ID, Redirecting Info)}; ResultForward --> Connect; ResultRelease --> ReleaseCall{Release Call (Cause)}; Connect --> End((X)); ReleaseCall --> End +``` + +The flowchart illustrates the procedure for checking and applying CFNRy (Call Forwarding Not Reachable) in the gsmSCF. It begins with a start symbol leading to a decision diamond: 'CFNRy A&O for Called profile?'. If 'No', the result is 'Continue'. If 'Yes', it proceeds to 'Set CFNRy data', then to a double-bordered rectangle 'Outgoing\_Barring\_Check\_gsmSCF'. A second decision diamond asks 'Result = Pass?'. If 'No', the result is 'Release'. If 'Yes', the result is 'Forward'. Both 'Continue' and 'Forward' results lead to a 'Connect' diamond containing '(FTN, Original Called Party ID, Redirecting Info)'. The 'Release' result leads to a 'Release Call (Cause)' diamond. All three paths converge at a final circle with an 'X' symbol. + +Flowchart for Procedure Check\_CFNRy\_gsmSCF + +Figure 14: Procedure Check\_CFNRy\_gsmSCF + +![Flowchart for Procedure Check_CFB_gsmSCF](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +### Procedure Check\_CFB\_gsmSCF + +C\_CFB\_G\_1(1) + +A procedure in the gsmSCF to apply CFB to the MT call if Active and Operative for the Called profile. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; Start([ ]) --> Decision1{CFB A&O for Called profile?}; Decision1 -- No --> ResultContinue[Result := Continue]; Decision1 -- Yes --> SetCFB[Set CFB data]; SetCFB --> OutgoingBarring[Outgoing_Barring_Check_gsmSCF]; OutgoingBarring --> Decision2{Result = Pass?}; Decision2 -- No --> ResultRelease[Result := Release]; Decision2 -- Yes --> ResultForward[Result := Forward]; ResultContinue --> Connect{Connect (FTN, Original Called Party ID, Redirecting Info)}; ResultForward --> Connect; ResultRelease --> ReleaseCall{Release Call (Cause)}; Connect --> End((X)); ReleaseCall --> End +``` + +The flowchart illustrates the 'Procedure Check\_CFB\_gsmSCF'. It begins with a start symbol leading to a decision diamond: 'CFB A&O for Called profile?'. If 'No', it proceeds to 'Result := Continue'. If 'Yes', it proceeds to 'Set CFB data', then to a double-bordered process box 'Outgoing\_Barring\_Check\_gsmSCF'. From there, it reaches a decision diamond: 'Result = Pass?'. If 'No', it proceeds to 'Result := Release'. If 'Yes', it proceeds to 'Result := Forward'. Both 'Result := Continue' and 'Result := Forward' lead to a decision diamond: 'Connect (FTN, Original Called Party ID, Redirecting Info)'. 'Result := Release' leads to a decision diamond: 'Release Call (Cause)'. All three decision diamonds lead to a common end symbol (a circle with an X). + +Flowchart for Procedure Check\_CFB\_gsmSCF + +Figure 15: Procedure Check\_CFB\_gsmSCF + +![Flowchart for Procedure Check_CFNRc_gsmSCF](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +### Procedure Check\_CFNRc\_gsmSCF + +C\_CFNRc\_G\_1(1) + +A procedure in the gsmSCF to apply CFNRc to the MT call if Active and Operative for the Called profile. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; Start([ ]) --> Decision1{CFNRc A&O for Called profile?}; Decision1 -- No --> ResultContinue[Result := Continue]; Decision1 -- Yes --> SetData[Set CFNRc data]; SetData --> OutgoingCheck[Outgoing_Barring_Check_gsmSCF]; OutgoingCheck --> Decision2{Result = Pass?}; Decision2 -- No --> ResultRelease[Result := Release]; Decision2 -- Yes --> ResultForward[Result := Forward]; ResultContinue --> Connect{Connect (FTN, Original Called Party ID, Redirecting Info)}; ResultForward --> Connect; ResultRelease --> ReleaseCall{Release Call (Cause)}; Connect --> End(( )); ReleaseCall --> End +``` + +The flowchart illustrates the procedure for checking and applying CFNRc (Call Forwarding Number Restriction) in a gsmSCF. It begins with a start symbol leading to a decision diamond: 'CFNRc A&O for Called profile?'. If 'No', the result is 'Continue', leading to a 'Connect' diamond. If 'Yes', it proceeds to 'Set CFNRc data', then to a double-bordered rectangle 'Outgoing\_Barring\_Check\_gsmSCF'. From there, a decision diamond 'Result = Pass?' is reached. If 'No', the result is 'Release', leading to a 'Release Call (Cause)' diamond. If 'Yes', the result is 'Forward', leading to the 'Connect' diamond. Both 'Connect' and 'Release Call (Cause)' diamonds lead to a common end symbol (circle with an X). + +Flowchart for Procedure Check\_CFNRc\_gsmSCF + +Figure 16: Procedure Check\_CFNRc\_gsmSCF + +![Flowchart for Procedure Check_CW_gsmSCF. It starts with an oval connector, followed by a decision diamond 'CW provisioned per profile?'. If 'No', it goes to an exit connector. If 'Yes', it goes to another decision diamond 'CW A&O for current profile?'. If 'Yes', it goes to the same exit connector. If 'No', it goes to a process box 'CW Treatment Indicator := CW Not Allowed', which is also labeled 'In SII2'. This is followed by a process box 'SII2 := True', and finally an exit connector.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +**Procedure Check\_CW\_gsmSCF** **C\_CW\_G\_1(1)** + +A procedure in the gsmSCF to check if CW is provisioned for the current profile. + +``` +graph TD; Start([ ]) --> D1{CW provisioned per profile?}; D1 -- No --> Exit1(( )); D1 -- Yes --> D2{CW A&O for current profile?}; D2 -- Yes --> Exit1; D2 -- No --> P1[CW Treatment Indicator := CW Not Allowed]; P1 --> P2[SII2 := True]; P2 --> Exit2(( )); +``` + +Flowchart for Procedure Check\_CW\_gsmSCF. It starts with an oval connector, followed by a decision diamond 'CW provisioned per profile?'. If 'No', it goes to an exit connector. If 'Yes', it goes to another decision diamond 'CW A&O for current profile?'. If 'Yes', it goes to the same exit connector. If 'No', it goes to a process box 'CW Treatment Indicator := CW Not Allowed', which is also labeled 'In SII2'. This is followed by a process box 'SII2 := True', and finally an exit connector. + +**Figure 17: Procedure Check\_CW\_gsmSCF** + +![Flowchart for Procedure Check_HOLD_gsmSCF. It starts with a start symbol, followed by a decision 'HOLD provisioned per profile?'. If 'No', it goes to an exit symbol. If 'Yes', it goes to another decision 'HOLD A&O for current profile?'. If 'Yes', it goes to the same exit symbol. If 'No', it goes to a process block 'HOLD Treatment Indicator := Reject HOLD Request', which is also labeled 'In SII2'. This is followed by a process block 'SII2 := True', and finally an exit symbol.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +### Procedure Check\_HOLD\_gsmSCF + +C\_HOLD\_G\_1(1) + +A procedure in the gsmSCF to check if HOLD is provisioned for the current profile. + +``` +graph TD; Start([ ]) --> D1{HOLD provisioned per profile?}; D1 -- No --> Exit1(( )); D1 -- Yes --> D2{HOLD A&O for current profile?}; D2 -- Yes --> Exit1; D2 -- No --> P1[HOLD Treatment Indicator := Reject HOLD Request]; P1 --> P2[SII2 := True]; P2 --> Exit2(( )); InSII2[In SII2] -.-> P1 +``` + +Flowchart for Procedure Check\_HOLD\_gsmSCF. It starts with a start symbol, followed by a decision 'HOLD provisioned per profile?'. If 'No', it goes to an exit symbol. If 'Yes', it goes to another decision 'HOLD A&O for current profile?'. If 'Yes', it goes to the same exit symbol. If 'No', it goes to a process block 'HOLD Treatment Indicator := Reject HOLD Request', which is also labeled 'In SII2'. This is followed by a process block 'SII2 := True', and finally an exit symbol. + +Figure 18: Procedure Check\_HOLD\_gsmSCF + +![Flowchart for Procedure Check_MPTY_gsmSCF. It starts with an oval connector, followed by a decision 'MPTY provisioned per profile?'. If 'No', it goes to an exit connector. If 'Yes', it goes to another decision 'MPTY A&O for Current profile?'. If 'Yes', it goes to the same exit connector. If 'No', it goes to a process block 'Conference Treatment Indicator := Reject Conference Request' (with an 'In SII2' label), then to 'SII2 := True', and finally to an exit connector.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +Procedure Check\_MPTY\_gsmSCF C\_MPTY\_G\_1(1) + +A procedure in the gsmSCF to check if MPTY is provisioned for the current profile. + +``` +graph TD; Start([ ]) --> D1{MPTY provisioned per profile?}; D1 -- No --> Exit1(( )); D1 -- Yes --> D2{MPTY A&O for Current profile?}; D2 -- Yes --> Exit1; D2 -- No --> P1[Conference Treatment Indicator := Reject Conference Request]; P1 --> P2[SII2 := True]; P2 --> Exit2(( )); InSII2[In SII2] -.-> P1 +``` + +Flowchart for Procedure Check\_MPTY\_gsmSCF. It starts with an oval connector, followed by a decision 'MPTY provisioned per profile?'. If 'No', it goes to an exit connector. If 'Yes', it goes to another decision 'MPTY A&O for Current profile?'. If 'Yes', it goes to the same exit connector. If 'No', it goes to a process block 'Conference Treatment Indicator := Reject Conference Request' (with an 'In SII2' label), then to 'SII2 := True', and finally to an exit connector. + +Figure 19: Procedure Check\_MPTY\_gsmSCF + +![Flowchart for Procedure Check_ACM_gsmSCF. It starts with a connector, followed by three decision diamonds: 'AoCC A&O for current profile?', 'Call chargeable to MSP subscriber?', and 'ACM >= ACMmax?'. If 'No' to any, it goes to 'Result := Pass'. If 'Yes' to all, it goes to 'Result := Fail', 'Set Cause', and 'Release Call (Cause)'.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +### Procedure Check\_ACM\_gsmSCF + +C\_ACM\_G\_1(1) + +A procedure in the gsmSCF to ensure that ACMmax is not exceeded for the profile in use. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; Start([ ]) --> D1{AoCC A&O for current profile?}; D1 -- No --> Pass[Result := Pass]; D1 -- Yes --> D2{Call chargeable to MSP subscriber?}; D2 -- No --> Pass; D2 -- Yes --> D3{ACM >= ACMmax?}; D3 -- No --> Pass; D3 -- Yes --> Fail[Result := Fail]; Fail --> SetCause[Set Cause]; SetCause --> ReleaseCall{Release Call (Cause)}; ReleaseCall --> End(( )); Pass --> End; +``` + +Flowchart for Procedure Check\_ACM\_gsmSCF. It starts with a connector, followed by three decision diamonds: 'AoCC A&O for current profile?', 'Call chargeable to MSP subscriber?', and 'ACM >= ACMmax?'. If 'No' to any, it goes to 'Result := Pass'. If 'Yes' to all, it goes to 'Result := Fail', 'Set Cause', and 'Release Call (Cause)'. + +Figure 20: Procedure Check\_ACM\_gsmSCF + +![Flowchart for Process AoC_MSP_gsmSCF](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +**Process AoC\_MSP\_gsmSCF** **AoC\_MG\_1(1)** + +A process in the gsmSCF to apply AoC per profile. + +Signals to/from the left are to/from the process MO\_MSP\_Call\_gsmSCF or the process MT\_MSP\_Call\_gsmSCF. + +``` +graph TD; Idle1([Idle]) --> StartAoC[/Start AoC (Call Information)/]; StartAoC --> Decision1{AoCI A&O for profile?}; Decision1 -- Yes --> AoCI_gsmSCF[|AoCI_gsmSCF|]; Decision1 -- No --> Decision2{AoCC A&O for profile?}; Decision2 -- Yes --> AoCC_gsmSCF[|AoCC_gsmSCF|]; Decision2 -- No --> AoC_ack{AoC ack}; AoCI_gsmSCF --> Merge(( )); AoCC_gsmSCF --> Merge; AoC_ack --> Merge; Merge --> Idle2([Idle]); +``` + +The flowchart illustrates the process flow for AoC\_MSP\_gsmSCF. It begins with an 'Idle' state, followed by 'Start AoC (Call Information)'. A decision point 'AoCI A&O for profile?' follows. If 'Yes', it proceeds to 'AoCI\_gsmSCF'. If 'No', it proceeds to another decision point 'AoCC A&O for profile?'. If 'Yes', it proceeds to 'AoCC\_gsmSCF'. If 'No', it proceeds to 'AoC ack'. All three paths ('AoCI\_gsmSCF', 'AoCC\_gsmSCF', and 'AoC ack') converge to a merge point, which then leads to the final 'Idle' state. + +Flowchart for Process AoC\_MSP\_gsmSCF + +**Figure 21: Process AoC\_MSP\_gsmSCF** + +![Flowchart for Procedure AoCI_gsmSCF](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +**Procedure AoCI\_gsmSCF** **AoCI\_G\_1(1)** + +A procedure in the gsmSCF to apply AoCI per profile. + +Signals to/from the right are to/from the process MO\_MSP\_Call\_gsmSCF or the process MT\_MSP\_Call\_gsmSCF. + +``` +graph TD; Start([Start]) --> Step1[Start charge calculations]; Step1 --> Decision{AoC ack}; Decision --> Step2(AoCI_active); Step2 --> Step3[/Call ended/]; Step3 --> Step4[Stop charging calculations]; Step4 --> End((X)); +``` + +The flowchart illustrates the procedure AoCI\_gsmSCF. It begins with a start symbol (oval), followed by a process block 'Start charge calculations'. This leads to a decision diamond 'AoC ack'. If the decision is positive, it proceeds to a data symbol (double circle) 'AoCI\_active'. This is followed by an input/output symbol (parallelogram) 'Call ended'. The next step is a process block 'Stop charging calculations', which finally leads to an end symbol (circle with an X). + +Flowchart for Procedure AoCI\_gsmSCF + +**Figure 22: Procedure AoCI\_gsmSCF** + +![Flowchart for Procedure AoCC_gsmSCF. The flow starts with a connector symbol, followed by 'Start charge calculations', 'AoC ack', and 'AoCC_active'. A decision point 'ACM >= ACMmax' follows. If true, it goes to 'Set Cause' and 'Release call (Cause)'. If false, it goes to 'Call ended' and 'Stop charging calculations'. Both paths end at connector symbols.](8269648391c59363ea61243864a2adf7_img.jpg) + +**Procedure AoCC\_gsmSCF** **AoCC\_G\_1(1)** + +A procedure in the gsmSCF to apply AoCC per profile. + +Signals to/from the left are to/from the process MO\_MSP\_Call\_gsmSCF or the process MT\_MSP\_Call\_gsmSCF. Signals from the right are internal. + +``` +graph TD; Start([ ]) --> StartCalc[Start charge calculations]; StartCalc --> AoCack{AoC ack}; AoCack --> AoCCactive([AoCC_active]); AoCCactive --> Decision{ACM >= ACMmax}; Decision -- True --> SetCause[Set Cause]; SetCause --> ReleaseCall{Release call (Cause)}; ReleaseCall --> End1([X]); Decision -- False --> CallEnded{Call ended}; CallEnded --> StopCalc[Stop charging calculations]; StopCalc --> End2([X]); +``` + +Flowchart for Procedure AoCC\_gsmSCF. The flow starts with a connector symbol, followed by 'Start charge calculations', 'AoC ack', and 'AoCC\_active'. A decision point 'ACM >= ACMmax' follows. If true, it goes to 'Set Cause' and 'Release call (Cause)'. If false, it goes to 'Call ended' and 'Stop charging calculations'. Both paths end at connector symbols. + +**Figure 23: Procedure AoCC\_gsmSCF** + +![Flowchart for Procedure Outgoing_Barring_Check_gsmSCF. It starts with an oval connector, followed by four decision diamonds: ODB applicable to current profile?, BAOC applicable to current profile?, BOIC-exHC applicable to current profile?, and BOIC applicable to current profile?. If any 'Yes' is found, it goes to 'Set Cause' and then 'Result := Fail'. If all are 'No', it goes to 'Result := Pass' and then to a circle connector.](32ff77da4286b58c4778033acaa10836_img.jpg) + +### Procedure Outgoing\_Barring\_Check\_gsmSCF + +OBCG\_1(1) + +A procedure in the gsmSCF to check the outgoing call barrings for an MSP subscriber. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; Start([ ]) --> D1{ODB applicable to current profile?}; D1 -- Yes --> SC[Set Cause]; D1 -- No --> D2{BAOC applicable to current profile?}; D2 -- Yes --> SC; D2 -- No --> D3{BOIC-exHC applicable to current profile?}; D3 -- Yes --> SC; D3 -- No --> D4{BOIC applicable to current profile?}; D4 -- Yes --> SC; D4 -- No --> RP[Result := Pass]; RP --> End(( )); SC --> RF[Result := Fail]; RF --> End +``` + +Flowchart for Procedure Outgoing\_Barring\_Check\_gsmSCF. It starts with an oval connector, followed by four decision diamonds: ODB applicable to current profile?, BAOC applicable to current profile?, BOIC-exHC applicable to current profile?, and BOIC applicable to current profile?. If any 'Yes' is found, it goes to 'Set Cause' and then 'Result := Fail'. If all are 'No', it goes to 'Result := Pass' and then to a circle connector. + +Figure 24: Procedure Outgoing\_Barring\_Check\_gsmSCF + +![Flowchart for Procedure Incoming_Barring_Check_gsmSCF. It starts with an oval connector, followed by three decision diamonds: 'ODB applicable to Called profile?', 'BAIC applicable to Called profile?', and 'BIC-roam applicable to Called profile?'. If any 'Yes' is returned, it goes to 'Set Cause' -> 'Result := Fail' -> 'Release Call (Cause)'. If all are 'No', it goes to 'Result := Pass'. Both paths lead to a circle connector with an X.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +### Procedure Incoming\_Barring\_Check\_gsmSCF + +IBCG\_1(1) + +A procedure in the gsmSCF to check the incoming barrings for the called profile. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; Start([ ]) --> D1{ODB applicable to Called profile?}; D1 -- Yes --> SC[Set Cause]; D1 -- No --> D2{BAIC applicable to Called profile?}; D2 -- Yes --> SC; D2 -- No --> D3{BIC-roam applicable to Called profile?}; D3 -- Yes --> SC; D3 -- No --> RP[Result := Pass]; SC --> RF[Result := Fail]; RF --> RC{{Release Call (Cause)}}; RP --> End((X)); RC --> End +``` + +Flowchart for Procedure Incoming\_Barring\_Check\_gsmSCF. It starts with an oval connector, followed by three decision diamonds: 'ODB applicable to Called profile?', 'BAIC applicable to Called profile?', and 'BIC-roam applicable to Called profile?'. If any 'Yes' is returned, it goes to 'Set Cause' -> 'Result := Fail' -> 'Release Call (Cause)'. If all are 'No', it goes to 'Result := Pass'. Both paths lead to a circle connector with an X. + +Figure 25: Procedure Incoming\_Barring\_Check\_gsmSCF + +![Flowchart for Procedure Check_ECT_gsmSCF](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +### Procedure Check\_ECT\_gsmSCF + +C\_ECT\_G\_1(1) + +A procedure in the gsmSCF to check if ECT is provisioned for the current profile. + +``` +graph TD; Start([ ]) --> D1{ECT provisioned per profile?}; D1 -- No --> Join(( )); D1 -- Yes --> D2{ECT A&O for current profile?}; D2 -- Yes --> Join; D2 -- No --> P1[ECT Treatment Indicator := Reject ECT Request]; P1 --> P2[SII2 := True]; P2 --> End(( )); +``` + +The flowchart illustrates the 'Procedure Check\_ECT\_gsmSCF'. It begins with an oval connector symbol. The first decision diamond asks 'ECT provisioned per profile?'. If the answer is 'No', the flow proceeds to a circular connector symbol. If the answer is 'Yes', it proceeds to the second decision diamond, 'ECT A&O for current profile?'. If the answer to this second decision is 'Yes', the flow proceeds to the same circular connector symbol. If the answer is 'No', the flow proceeds to a rectangular process block labeled 'ECT Treatment Indicator := Reject ECT Request'. This block is preceded by a dashed box labeled 'In SII2'. Following this process block is another rectangular process block labeled 'SII2 := True'. Finally, the flow proceeds to a circular connector symbol. + +Flowchart for Procedure Check\_ECT\_gsmSCF + +Figure 26: Procedure Check\_ECT\_gsmSCF + +![Flowchart for Procedure Check_CCBS_gsmSCF. It starts with a connector, then checks if CCBS is provisioned per profile. If No, it goes to an exit connector. If Yes, it checks if it's a MO call. If No, it checks if the called profile can be a CCBS target. If Yes, it sets SII2 := True and exits. If No, it sets Call Completion Treatment Indicator := Reject Call Completion Service Request and exits. If Yes to MO call, it checks if the calling profile can plant CCBS. If Yes, it exits. If No, it sets Call Completion Treatment Indicator := Reject Call Completion Service Request and exits.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +**Procedure Check\_CCBS\_gsmSCF** **C\_CCBS\_G\_1(1)** + +A procedure in the gsmSCF to check if CCBS is provisioned for the current profile. + +``` +graph TD; Start([ ]) --> D1{CCBS provisioned per profile?}; D1 -- No --> Exit1(( )); D1 -- Yes --> D2{MO call?}; D2 -- No --> D3{Called profile can be a CCBS target?}; D2 -- Yes --> D4{Calling profile can plant CCBS?}; D4 -- Yes --> Exit1; D4 -- No --> P1[Call Completion Treatment Indicator := Reject Call Completion Service Request]; P1 --> Exit1; D3 -- Yes --> P2[SII2 := True]; P2 --> Exit2(( )); D3 -- No --> Exit1; +``` + +Flowchart for Procedure Check\_CCBS\_gsmSCF. It starts with a connector, then checks if CCBS is provisioned per profile. If No, it goes to an exit connector. If Yes, it checks if it's a MO call. If No, it checks if the called profile can be a CCBS target. If Yes, it sets SII2 := True and exits. If No, it sets Call Completion Treatment Indicator := Reject Call Completion Service Request and exits. If Yes to MO call, it checks if the calling profile can plant CCBS. If Yes, it exits. If No, it sets Call Completion Treatment Indicator := Reject Call Completion Service Request and exits. + +**Figure 27: Procedure Check\_CCBS\_gsmSCF** + +### 7.5.4 Information flows + +The information flow for a successful MO call by an MSP subscriber is shown in figure 28. + +The information flow for a successful MT call to an MSP subscriber is shown in figure 29. + +![Sequence diagram showing information flow for a successful MO call between MS, MSC, VLR, gsmSSF, gsmSCF, and Destination Network.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant gsmSSF + participant gsmSCF + participant DN as Destination Network + + MS->>MSC: Setup + MSC->>VLR: SIFOC + VLR->>MSC: Complete call (O-CS1) + MSC->>MS: Call proceeding + MSC->>gsmSSF: Invoke gsmSSF + gsmSSF->>MSC: gsmSSF invoked + MSC->>gsmSSF: DP_Collected_Info + gsmSSF->>gsmSCF: Initial_DP (MO parameters) + gsmSCF->>gsmSSF: Furnish Charging Information (Profile ID) + gsmSCF->>MSC: Continue / Connect (Generic Number, SII2) + MSC->>MS: Progress + MSC->>VLR: SIFOC + VLR->>MSC: Complete call + MSC->>DN: Initial Address Message +``` + +The sequence diagram illustrates the information flow for a successful MO call. It begins with the MS sending a 'Setup' message to the MSC. The MSC responds with 'SIFOC' to the VLR, which in turn sends 'Complete call (O-CS1)' back to the MSC. The MSC then sends 'Call proceeding' to the MS. Next, the MSC sends 'Invoke gsmSSF' to the gsmSSF, which responds with 'gsmSSF invoked'. The MSC then sends 'DP\_Collected\_Info' to the gsmSSF, which in turn sends 'Initial\_DP (MO parameters)' to the gsmSCF. The gsmSCF responds with 'Furnish Charging Information (Profile ID)' to the gsmSSF, which then sends 'Continue / Connect (Generic Number, SII2)' to the MSC. The MSC sends 'Progress' to the MS. Finally, the MSC sends 'SIFOC' to the VLR, which sends 'Complete call' back to the MSC, and the MSC sends 'Initial Address Message' to the Destination Network. + +Sequence diagram showing information flow for a successful MO call between MS, MSC, VLR, gsmSSF, gsmSCF, and Destination Network. + +Figure 28: Information flow for a successful MO call + +![Sequence diagram showing information flow for a successful MT call to a profile with no active call forwarding. Lifelines: GMSC, HLR, gsmSSF, gsmSCF, VLR, Terminating MSC. The process involves routing info exchange, subscriber info lookup, gsmSSF invocation, and final routing to the terminating MSC.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +``` + +sequenceDiagram + participant GMSC + participant HLR + participant gsmSSF + participant gsmSCF + participant VLR + participant Terminating MSC + + GMSC->>HLR: Send Routing Info + HLR->>VLR: Provide Subscriber Info + VLR->>Terminating MSC: Obtain Subscriber Info + Terminating MSC-->>VLR: Obtain Subscriber Info ack + VLR->>gsmSCF: Provide Subscriber Info ack + gsmSCF-->>HLR: + HLR-->>GMSC: Send Routing Info ack (T-CSI) + GMSC->>gsmSSF: Invoke gsmSSF + gsmSSF-->>HLR: gsmSSF invoked + HLR-->>GMSC: DP_Termination_Attempt_Authorised + gsmSSF->>gsmSCF: Initial DP (MT parameters) + gsmSCF-->>gsmSSF: Furnish Charging Information (Profile ID) + gsmSCF-->>gsmSSF: Continue / Connect (Alerting Pattern, SII2) + gsmSSF-->>GMSC: Continue / Connect (Alerting Pattern, SII2) + GMSC->>HLR: Send Routing Info (Suppress T-CSI, Alerting Pattern) + HLR->>VLR: Provide Roaming Number (Alerting Pattern) + VLR->>gsmSCF: Provide Roaming Number ack + gsmSCF-->>HLR: + HLR-->>GMSC: Send Routing Info ack (MSRN) + GMSC->>Terminating MSC: Initial Address Message + +``` + +Sequence diagram showing information flow for a successful MT call to a profile with no active call forwarding. Lifelines: GMSC, HLR, gsmSSF, gsmSCF, VLR, Terminating MSC. The process involves routing info exchange, subscriber info lookup, gsmSSF invocation, and final routing to the terminating MSC. + +**Figure 29: Information flow for a successful MT call to a profile that has no Call Forwardings Active and Operative in the gsmSCF** + +NOTE: For information flows to a profile that has Call Forwarding services Active and Operative in the gsmSCF, see subclause 7.11.1: Call Forwarding. + +## 7.6 SMS handling + +MSP Phase 2 does not apply to MT short messages. The MSP subscriber will receive MT short messages but no profile indication will be given. + +When the gsmSCF receives an Initial SMS Event message from the gsmSSF, the process MO\_MSP\_SMS\_gsmSCF will be invoked, see figure 30. + +![Flowchart for Process MO_MSP_SMS_gsmSCF (sheet 1 of 2). The process starts at 'Idle', receives an 'Initial SMS Event', then checks if a profile is explicitly selected. If 'Yes', it sets the SMS sender to the selected profile and removes the profile ID. If 'No', it sets the SMS sender to the registered profile. Both paths lead to a decision 'SMS sender = Default profile?'. If 'Yes', it sends a 'Response_msg := Continue'. If 'No', it sets the calling party number and then sends a 'Response_msg := Connect'. Both response messages lead to connector '1'.](552328a9daaf3bc0069424b500025880_img.jpg) + +**Process MO\_MSP\_SMS\_gsmSCF** **MO\_MSG\_1(2)** + +A process in the gsmSCF to handle an MO short message for an MSP subscriber. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; Idle([Idle]) --> Event{{Initial SMS Event}}; Event --> Decision1{Is profile explicitly selected in Destination Subscriber address?}; Decision1 -- Yes --> Sender1[SMS sender := Selected profile]; Decision1 -- No --> Sender2[SMS sender := Registered profile]; Sender1 --> RemoveID[Remove Profile ID from Destination Subscriber Address]; RemoveID --> Decision2{SMS sender = Default profile?}; Sender2 --> Decision2; Decision2 -- Yes --> Response1[Response_msg := Continue]; Decision2 -- No --> CallingParty[Set Calling Party Number to MSISDN of SMS sender]; CallingParty --> Response2[Response_msg := Connect]; Response1 --> Connector((1)); Response2 --> Connector; +``` + +Flowchart for Process MO\_MSP\_SMS\_gsmSCF (sheet 1 of 2). The process starts at 'Idle', receives an 'Initial SMS Event', then checks if a profile is explicitly selected. If 'Yes', it sets the SMS sender to the selected profile and removes the profile ID. If 'No', it sets the SMS sender to the registered profile. Both paths lead to a decision 'SMS sender = Default profile?'. If 'Yes', it sends a 'Response\_msg := Continue'. If 'No', it sets the calling party number and then sends a 'Response\_msg := Connect'. Both response messages lead to connector '1'. + +Figure 30a: Process MO\_MSP\_SMS\_gsmSCF (sheet 1 of 2) + +![Flowchart for Process MO_MSP_SMS_gsmSCF. It starts at a circle labeled '1', goes to a process box 'Outgoing_Barring_Check_gsmSCF', then to a decision diamond 'Result = Pass?'. If 'No', it goes to 'Release SMS (Cause)'. If 'Yes', it goes to a process box 'Furnish SMS Charging Information (Profile ID)', then to a decision diamond 'Response_msg = Connect?'. If 'No', it goes to 'Continue SMS'. If 'Yes', it goes to 'Connect SMS'. All three paths ('Release SMS', 'Continue SMS', and 'Connect SMS') lead to a final oval labeled 'Idle'. A note next to 'Connect SMS' states: 'Contains Calling Party Number and/or Destination Subscriber Address'.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +**Process MO\_MSP\_SMS\_gsmSCF** **MO\_MSG\_2(2)** + +A process in the gsmSCF to handle an MO short message for an MSP subscriber. + +Signals to/from the left are to/from the gsmSSF. + +``` +graph TD; Start((1)) --> Process1[Outgoing_Barring_Check_gsmSCF]; Process1 --> Decision1{Result = Pass?}; Decision1 -- No --> ReleaseSMS{{Release SMS (Cause)}}; Decision1 -- Yes --> Process2{{Furnish SMS Charging Information (Profile ID)}}; Process2 --> Decision2{Response_msg = Connect?}; Decision2 -- No --> ContinueSMS{{Continue SMS}}; Decision2 -- Yes --> ConnectSMS{{Connect SMS}}; Note[Contains Calling Party Number and/or Destination Subscriber Address] -.-> ConnectSMS; ReleaseSMS --> Idle([Idle]); ContinueSMS --> Idle; ConnectSMS --> Idle; +``` + +Flowchart for Process MO\_MSP\_SMS\_gsmSCF. It starts at a circle labeled '1', goes to a process box 'Outgoing\_Barring\_Check\_gsmSCF', then to a decision diamond 'Result = Pass?'. If 'No', it goes to 'Release SMS (Cause)'. If 'Yes', it goes to a process box 'Furnish SMS Charging Information (Profile ID)', then to a decision diamond 'Response\_msg = Connect?'. If 'No', it goes to 'Continue SMS'. If 'Yes', it goes to 'Connect SMS'. All three paths ('Release SMS', 'Continue SMS', and 'Connect SMS') lead to a final oval labeled 'Idle'. A note next to 'Connect SMS' states: 'Contains Calling Party Number and/or Destination Subscriber Address'. + +**Figure 30b: Process MO\_MSP\_SMS\_gsmSCF (sheet 2 of 2)** + +## 7.7 Call Independent SS handling + +Supplementary Services provisioned per subscriber will be handled in the usual way. + +Supplementary Services provisioned per profile will be controlled using USSD, sent via the VLR and HLR to the gsmSCF. + +If Call Barring is provisioned per profile, if the outgoing call barring data for the default profile is changed, the HLR shall be informed using Any Time Modification. On receipt of an Any Time Modification message from the gsmSCF for a subscriber with the OCB\_flag set, the HLR will modify the stored Call Barring information for the default profile in accordance with the information in the Any Time Modification message. + +## 7.8 Interaction with Supplementary Services + +### 7.8.1 Line Identification services + +#### 7.8.1.1 CLIP + +No interaction. + +#### 7.8.1.2 CLIR + +CLIR can be provisioned per subscriber or per profile. + +If CLIR is provisioned per subscriber and CLIR is active, it will be active for all profiles. Data for the CLIR Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. CLIR will function as specified in 3G TS 23.081 and will not distinguish between MSP and non-MSP subscribers. + +If CLIR is provisioned per profile then the CLIR\_flag shall be set in the HLR (see subclause 6.8: CLIR\_flag) and the CLIR subscription information for the default profile shall be stored in the HLR in the usual manner. For an MO call, if the CLIR subscription information for the Calling profile indicates that the CLI shall be restricted, the gsmSCF shall set the Calling Party Presentation Indicator to Presentation Restricted in the SII2 parameter. + +#### 7.8.1.3 COLP + +No interaction. + +#### 7.8.1.4 COLR + +No interaction. + +### 7.8.2 Call Hold (HOLD) + +Call Hold can be provisioned per subscriber or per profile. + +If Call Hold is provisioned per subscriber and Call Hold is active, it will be active for all profiles. Data for the Call Hold Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. Call Hold will function as specified in 3G TS 23.083 and will not distinguish between MSP and non-MSP subscribers. + +If Call Hold is provisioned per profile then the HOLD\_flag shall be set in the HLR (see subclause 6.3: HOLD\_flag). On receipt of an Initial\_DP message for an MO or MT call, the gsmSCF will check the subscription information for the profile in use for that call. If HOLD is not active and operative, then the SII2 will be included in the Connect message with the HOLD Treatment Indicator set to Reject HOLD Request. + +### 7.8.3 Call Waiting (CW) + +Call Waiting can be provisioned per subscriber or per profile. + +If Call Waiting is provisioned per subscriber and Call Waiting is active, it will be active for all profiles. Data for the Call Waiting Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. Call Waiting will function as specified in 3G TS 23.083 and will not distinguish between MSP and non-MSP subscribers. + +If Call Waiting is provisioned per profile then the CW\_flag shall be set in the HLR (see subclause 6.4: CW\_flag). On receipt of an Initial\_DP message for an MO or MT call, the gsmSCF will check the subscription information for the profile in use for that call. If Call Waiting is not active and operative, then the SII2 will be included in the Connect message with the CW Treatment Indicator set to CW Not Allowed. The subscriber shall be able to modify CW information per profile by making contact with the gsmSCF using USSD. However, the subscriber shall not be able to modify CW data for the default profile. + +### 7.8.4 Call Forwarding + +The Call Forwarding Supplementary Services, described in 3G TS 23.082, can only be provisioned per subscriber. However, services equivalent to the Call Forwarding Supplementary Services, implemented in the gsmSCF, will be available to the MSP subscriber per profile. This is described in subclause 7.11.1: Call Forwarding. + +If the Call Forwarding Supplementary Services are provisioned per subscriber, then Call Forwarding will function as specified in 3G TS 23.082 and will not distinguish between MSP and non-MSP subscribers. + +NOTE 1: If Call Forwarding is provisioned per subscriber in the HLR then Call Forwarding should not be provisioned per profile in the gsmSCF, as this may cause unpredictable behaviour. + +NOTE 2: If Call Forwarding is provisioned per subscriber in the HLR then Call Deflection should not be provisioned per profile in the gsmSCF, as this may cause unpredictable behaviour. + +### 7.8.5 Multi Party Service (MPTY) + +The Multi Party Supplementary Service can be provisioned per subscriber or per profile. + +If MPTY is provisioned per subscriber and MPTY is active, it will be active for all profiles. Data for the MPTY Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. MPTY will function as specified in 3G TS 23.084 and will not distinguish between MSP and non-MSP subscribers. + +If MPTY is provisioned per profile then the MPTY\_flag shall be set in the HLR (see subclause 6.5: MPTY\_flag). On receipt of an Initial\_DP message for an MO or MT call, the gsmSCF will check the subscription information for the profile in use for that call. If MPTY is not active and operative, then the SII2 will be included in the Connect message with the Conference Treatment Indicator set to Reject Conference Request. + +### 7.8.6 Closed User Group (CUG) + +The Closed User Group Supplementary Service can be provisioned per subscriber or per profile. + +If CUG is provisioned per subscriber and CUG is active, it will be active for all profiles. Data for the CUG Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. CUG will function as specified in 3G TS 23.085 and will not distinguish between MSP and non-MSP subscribers. The interaction between CAMEL and CUG is defined in 3G TS 23.078. + +CUG provisioning per profile is supported by CAMEL Phase 3 and is FFS. + +### 7.8.7 Advice of Charge (AoC) + +The Advice of Charge Supplementary Service can be provisioned per subscriber. However, services equivalent to the Advice of Charge supplementary services, implemented in the gsmSCF, will be available to the MSP subscriber per profile. This is described in subclause 7.11.4: Advice of Charge (AoC). Signalling on the access interface will be as specified in 3G TS 24.086. + +If AoC is active, it will be active for all profiles. Data for the AoC Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. AoC will function as specified in 3G TS 23.086 and will not distinguish between MSP and non-MSP subscribers. + +### 7.8.8 Call Barring + +The Call Barring Supplementary Services, described in 3G TS 23.088, can only be provisioned per subscriber. However, services equivalent to the Call Barring Supplementary Services, implemented in the gsmSCF, can be provided to the MSP subscriber per profile. This is described in subclause 7.11.2: Call Barring. This requires the OCB\_flag mechanism described in section subclause 6.1: OCB\_flag. + +### 7.8.9 Explicit Call Transfer (ECT) + +The Explicit Call Transfer supplementary service can be provisioned per subscriber or per profile. + +If ECT is provisioned per subscriber and ECT is active, it will be active for all profiles. Data for the ECT Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. ECT will function as specified in 3G TS 23.091 and will not distinguish between MSP and non-MSP subscribers. + +If ECT is provisioned per profile then the ECT\_flag shall be set in the HLR (see subclause 6.6: ECT\_flag). On receipt of an Initial\_DP message for an MO or MT call, the gsmSCF will check the subscription information for the profile in use for that call leg. If ECT is not active and operative, then the SII2 will be included in the Connect message with the ECT Treatment Indicator set to Reject ECT Request. + +### 7.8.10 Completion of Calls to Busy Subscriber (CCBS) + +CCBS can be provisioned per subscriber or per profile. + +If CCBS is provisioned per subscriber and CCBS is active, it will be active over all profiles. Data for the CCBS Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. + +If CCBS is provisioned per profile then the CCBS\_flag shall be set in the HLR (see subclause 6.7: CCBS\_flag). + +On receipt of an Initial\_DP message for an MO call, the gsmSCF will check the subscription information for the calling profile. If CCBS is not active and operative, then the SII2 will be included in the Connect message with the Call Completion Treatment Indicator set to Call Completion Not Allowed. + +On receipt of an Initial\_DP message for an MT call, the gsmSCF will check the subscription information for the called profile. If CCBS is not active and operative, then the SII2 will be included in the Connect message with the Call Completion Treatment Indicator sent to Call Completion not allowed. + +The subscriber shall be able to modify CCBS information per profile by making contact with the gsmSCF using USSD. However, the subscriber shall not be able to modify CCBS data for the default profile. + +If a CFU-equivalent service is activated while there are queue entries in MS-B's target queue, HLR-B will not know about this activation and will process these queue entries as normal. As a consequence, the CCBS calls related to these queue entries will be forwarded to the new destination. CCBS activation is not possible if this forwarded call meets NDUB. This results in expiry of recall timer T9 and deletion of the queue entry from MS-B's target queue. For further details on the interaction between CCBS and CAMEL, refer to 3G TS 23.093. + +The same applies to Incoming Call Barring-equivalent services which are activated while there are queue entries in MS-B's target queue. + +An MSP subscriber will have CCBS set in the SS-CSI. The gsmSCF will be informed of CCBS Request and CCBS Setup messages for the MSP subscriber. This allows the service logic in the gsmSCF to assign the correct profile to the CCBS call. + +### 7.8.11 enhanced Multi-Level Precedence and Pre-emption (eMLPP) + +eMLPP will be provisioned per subscriber. If eMLPP is active, it will be active for all profiles. Data for the eMLPP Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. eMLPP will function as specified in 3G TS 23.067 and will not distinguish between MSP and non-MSP subscribers. + +### 7.8.12 User-to-User Signalling (UUS) + +The User-to-User Supplementary Service will be provisioned per subscriber. If UUS is active, it will be active for all profiles. Data for the UUS Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual manner. UUS will function as specified in 3G TS 23.087 and will not distinguish between MSP and non-MSP subscribers. + +### 7.8.13 Call Deflection (CD) + +The Call Deflection Supplementary Service will be provisioned per subscriber. If CD is active, it will be active for all profiles. Data for the CD Supplementary Service will be stored in the HLR, and if appropriate in the VLR, in the usual + +manner. CD will function as specified in 3G TS 23.072 and will not distinguish between MSP and non-MSP subscribers. + +When the MSP subscriber deflects an MT call, it triggers an interrogation of the gsmSCF for an MO Call. Using the call reference number, the gsmSCF can recognise that there is an ongoing dialogue for the MT call, and can then retrieve the profile to apply for the deflected call. + +This gives the gsmSCF the opportunity to reject the call deflection per profile, providing the MSP subscriber is in a supporting network. + +NOTE: Call Deflection should not be provisioned per profile if Call Forwardings are provisioned per subscriber in the HLR as unpredictable behaviour may occur. + +## 7.9 Interaction with other services + +### 7.9.1 The Multi-Numbering Scheme + +If the MSP subscriber has different MSISDNs allocated for different Basic Services, all MSISDNs and associated Basic Services will be stored in the HLR. Each MSISDN and associated Basic Services will also be stored in the gsmSCF with associated profile ID. + +### 7.9.2 The Short Message Service + +Mobile terminated short messages can be received on any profile although the profile will not be indicated to the user. + +It shall be possible to select a profile for mobile originated short messages. If a profile is explicitly selected, the MO short message will be sent by and charged to the selected profile. If a profile is not explicitly selected, the MO short message will be sent by and charged to the registered profile. + +### 7.9.3 Interactions with CAMEL + +An MSP subscriber will, by definition, have a CAMEL subscription. + +If other CAMEL services are designed in such a way that an MSP subscriber can use them, they will be available to the MSP subscriber. It is a network option to design CAMEL services that interact with MSP. + +### 7.9.4 Interactions with OR + +The GMSC in the Interrogating PLMN (IPLMN) needs to support CAMEL Phase 2 capability if the called subscriber is an MSP subscriber. + +If an interrogation request is received for an MSP subscriber from a GMSC in the IPLMN that does not support the CAMEL Phase 2 capability, the HLR shall return an OR not allowed negative response (see 3G TS 23.079) to the GMSC. This will force the call to be routed to a GMSC supporting CAMEL Phase 2 capability in the HPLMN. + +### 7.9.5 Operator Determined Barring + +ODB, as described in 3G TS 23.015, can only be provisioned per subscriber. + +A service, implemented in the gsmSCF equivalent to the ODB service will be available for an MSP subscriber per profile. This is described in subclause 7.11.3: Operator Determined Barring (ODB); it requires the mechanism described in subclause 6.2: ODB flags.. + +Outgoing ODB for the default profile will be stored in the HLR for use when the subscriber roams into a non-supporting network, see subclause 7.11.3: Roaming into a network not supporting CAMEL Phase 2 for further details. + +### 7.9.6 Roaming Restrictions + +Roaming Restrictions will apply per subscriber. Data for the Roaming Restrictions will be stored in the HLR in the usual manner. + +## 7.10 Data stored in the gsmSCF + +The gsmSCF contains all the data needed to control the MSP service. These data can be divided into the common data (the data valid for all profiles) and the profile specific data. + +![Diagram showing the data stored in the gsmSCF, divided into Common Data and Profile Specific Data. Common Data includes IMSI, Category, Registered profile, and Default profile. Profile Specific Data includes Profile ID, MSISDNs and associated Basic Services, Alerting Pattern (For Incoming calls), Call Forwarding data, Call Barring Data, CLIR data, HOLD data, CW data, MPTY data, ECT data, CCBS data, and ODB Data.](cc6f9dbfc36aa5821d9749ca84861f93_img.jpg) + +Common Data + +- IMSI +- Category +- Registered profile +- Default profile + +Profile Specific Data + +- Profile ID +- MSISDNs and associated Basic Services +- Alerting Pattern (For Incoming calls) +- Call Forwarding data +- Call Barring Data +- CLIR data +- HOLD data +- CW data +- MPTY data +- ECT data +- CCBS data +- ODB Data + +``` +graph TD; subgraph CommonData [Common Data]; IMSI[IMSI]; Category[Category]; RegisteredProfile[Registered profile]; DefaultProfile[Default profile]; end; subgraph ProfileSpecificData [Profile Specific Data]; ProfileID[Profile ID]; MSISDNs[MSISDNs and associated Basic Services]; AlertingPattern["Alerting Pattern (For Incoming calls)"]; CallForwarding[Call Forwarding data]; CallBarring[Call Barring Data]; CLIR[CLIR data]; HOLD[HOLD data]; CW[CW data]; MPTY[MPTY data]; ECT[ECT data]; CCBS[CCBS data]; ODB[ODB Data]; end; +``` + +Diagram showing the data stored in the gsmSCF, divided into Common Data and Profile Specific Data. Common Data includes IMSI, Category, Registered profile, and Default profile. Profile Specific Data includes Profile ID, MSISDNs and associated Basic Services, Alerting Pattern (For Incoming calls), Call Forwarding data, Call Barring Data, CLIR data, HOLD data, CW data, MPTY data, ECT data, CCBS data, and ODB Data. + +## 7.11 Equivalent services implemented by the gsmSCF + +### 7.11.1 Call Forwarding + +Call Forwarding services will be provided in the gsmSCF per profile. An MT call to an MSP subscriber will be subject to the provided call forwardings for the called profile. + +The Call Forwarding services, implemented by the gsmSCF, should operate in the same way as the Call Forwarding Supplementary Services. The MSP subscriber should have control over the call forwarding data (Registration, Erasure, Activation, Deactivation, and Interrogation). The method for controlling this data is a network option. + +![Sequence diagram showing information flow for a successful MT call to a profile with some Call Forwardings Active and Operative. Lifelines: GMSC, HLR, gsmSSF, gsmSCF, VLR, Terminating MSC.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` + +sequenceDiagram + participant GMSC + participant HLR + participant gsmSSF + participant gsmSCF + participant VLR + participant Terminating MSC + + Note left of GMSC: + GMSC->>HLR: Send Routing Info + HLR->>VLR: Provide Subscriber Info + VLR->>Terminating MSC: Obtain Subscriber Info + Terminating MSC-->>VLR: Obtain Subscriber Info ack + VLR-->>HLR: Provide Subscriber Info ack + HLR-->>GMSC: Send Routing Info ack (T-CSI) + GMSC->>gsmSSF: Invoke gsmSSF + gsmSSF-->>GMSC: gsmSSF invoked + GMSC->>gsmSCF: DP_Termination_Attempt_Authorized + gsmSCF->>gsmSSF: Initial_DP (MT parameters) + gsmSSF-->>gsmSCF: Furnish Charging Information (Profile ID) + gsmSCF->>gsmSSF: Request_Report_BCSM_Event (see Note) + gsmSSF-->>gsmSCF: Continue / Connect (Alerting Pattern, SII2) + gsmSCF-->>GMSC: Continue / Connect (Alerting Pattern, SII2) + GMSC->>HLR: Send Routing Info (Alerting Pattern) + HLR->>VLR: Provide Roaming Number (Alerting Pattern) + VLR-->>HLR: Provide Roaming Number ack (MSRN) + HLR-->>GMSC: Send Routing Info ack (MSRN) + GMSC->>Terminating MSC: Initial Address Message + +``` + +Sequence diagram showing information flow for a successful MT call to a profile with some Call Forwardings Active and Operative. Lifelines: GMSC, HLR, gsmSSF, gsmSCF, VLR, Terminating MSC. + +**Figure 31: Information flow for a successful MT call to a profile with some Call Forwardings Active and Operative** + +NOTE: Request\_Report\_BCSM\_Event will contain the list Arm\_DP\_List (see figure 1). This list will contain the following elements: + T\_Answer EDP-N + T\_Abandon EDP-N + T\_Busy EDP-N (Unless CFB and/or CFNRc are A&O for the called profile, in which case EDP-R) + T\_No\_Answer EDP-N (Unless CFNRy is A&O for the called profile, in which case EDP-R) + +#### 7.11.1.1 Call Forward Unconditional + +![Sequence diagram for Call Forward Unconditional (CFU) showing interactions between GMSC, gsmSSF, and gsmSCF.](03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg) + +``` +sequenceDiagram + participant GMSC + participant gsmSSF + participant gsmSCF + Note left of GMSC: + GMSC->>gsmSSF: Invoke gsmSSF (T-CSI) + gsmSSF-->>GMSC: gsmSSF Invoked + GMSC->>gsmSSF: DP_Termination_Attempt_Authorized + gsmSSF->>gsmSCF: Initial_DP (MT parameters) + gsmSCF-->>gsmSSF: Furnish Charging Information (Profile ID) + gsmSCF-->>gsmSSF: Connect (FTN) + gsmSSF-->>GMSC: Connect (FTN) +``` + +Sequence diagram for Call Forward Unconditional (CFU) showing interactions between GMSC, gsmSSF, and gsmSCF. + +Figure 32: Information flow for an MT call to a profile with CFU active and operative in the gsmSCF + +#### 7.11.1.2 Call Forward on Busy + +![Sequence diagram for Call Forward on Busy (CFB) showing interactions between GMSC, gsmSSF, gsmSCF, and MSC.](b774dfc5023e15e9c352b97ca25a56d4_img.jpg) + +``` +sequenceDiagram + participant GMSC + participant gsmSSF + participant gsmSCF + participant MSC + Note left of GMSC: + GMSC->>MSC: Initial Address Message + MSC-->>GMSC: Release (Busy) + GMSC->>gsmSSF: DP_T_Busy + gsmSSF->>gsmSCF: Event Report BCSM (interrupted) + gsmSCF-->>gsmSSF: Connect (FTN) + gsmSSF-->>GMSC: Connect (FTN) +``` + +Sequence diagram for Call Forward on Busy (CFB) showing interactions between GMSC, gsmSSF, gsmSCF, and MSC. + +Figure 33: Information flow for an MT call to a profile with CFB active and operative in the gsmSCF, where the called subscriber is NDUB or UDUB + +#### 7.11.1.3 Call Forward on No Reply + +![Sequence diagram showing the information flow for an MT call to a profile with CFNRy active and operative in the gsmSCF, where the called party does not answer. The diagram involves four lifelines: GMSC, gsmSSF, gsmSCF, and MSC. The sequence starts with an Initial Address Message from GMSC to MSC. MSC responds with an Address Complete Message to GMSC. GMSC starts a timer (TNRy Expired). When the timer expires, GMSC sends a Release message to MSC. GMSC then sends a DP_T_No_Answer message to gsmSSF. gsmSSF sends an Event Report BCSM (interrupted) to gsmSCF. gsmSCF sends a Connect (FTN) message to gsmSSF. gsmSSF sends a Connect (FTN) message to GMSC.](efbdfb3d9d5a7a7782ef29e131f9f280_img.jpg) + +``` + +sequenceDiagram + participant GMSC + participant gsmSSF + participant gsmSCF + participant MSC + Note left of GMSC: TNRy Expired + GMSC->>MSC: Initial Address Message + MSC-->>GMSC: Address Complete Message + Note left of GMSC: TNRy Expired + GMSC->>MSC: Release + GMSC->>gsmSSF: DP_T_No_Answer + gsmSSF->>gsmSCF: Event Report BCSM (interrupted) + gsmSCF->>gsmSSF: Connect (FTN) + gsmSSF->>GMSC: Connect (FTN) + +``` + +Sequence diagram showing the information flow for an MT call to a profile with CFNRy active and operative in the gsmSCF, where the called party does not answer. The diagram involves four lifelines: GMSC, gsmSSF, gsmSCF, and MSC. The sequence starts with an Initial Address Message from GMSC to MSC. MSC responds with an Address Complete Message to GMSC. GMSC starts a timer (TNRy Expired). When the timer expires, GMSC sends a Release message to MSC. GMSC then sends a DP\_T\_No\_Answer message to gsmSSF. gsmSSF sends an Event Report BCSM (interrupted) to gsmSCF. gsmSCF sends a Connect (FTN) message to gsmSSF. gsmSSF sends a Connect (FTN) message to GMSC. + +**Figure 34: Information flow for an MT call to a profile with CFNRy active and operative in the gsmSCF, where the called party does not answer** + +NOTE: The timer TNRy is started in the GMSC after the Address Complete Message has been received from the destination exchange. If this timer expires before an Answer message is received from the destination exchange, a release message is sent to the destination exchange and the detection point T\_No\_Answer is reached. This is specified in 3G TS 23.018 and 3G TS 23.078. + +#### 7.11.1.4 Call Forward on Not Reachable + +#### 7.11.1.5 Early CFNRc + +Early Call Forwarding on Not Reachable will apply if the gsmSCF receives the parameter "subscriber state" set as Not Reachable. Due to the presence of the Location information / Subscriber state Interrogation parameter in the CAMEL data, stored in the HLR, the HLR sends a Provide Subscriber Information message to the VLR. This determines if the subscriber state is Not Reachable. + +![Sequence diagram showing information flow for an MT call. Lifelines: GMSC, HLR, gsmSSF, gsmSCF, VLR, Destination MSC. The sequence involves routing information exchange, subscriber info lookup, gsmSSF invocation, and call setup parameters.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +``` + +sequenceDiagram + participant GMSC + participant HLR + participant gsmSSF + participant gsmSCF + participant VLR + participant DMSC as Destination MSC + + Note left of GMSC: MT call setup + GMSC->>HLR: Send Routing Information + HLR->>VLR: Provide Subscriber Info + VLR->>DMSC: Obtain Subscriber Info + DMSC-->>VLR: Obtain Subscriber Info ack (Network Determined Not Reachable) + VLR-->>HLR: Provide Subscriber Info ack (Network Determined Not Reachable) + HLR-->>GMSC: Routing Information ack (Network Determined Not Reachable) + GMSC->>gsmSSF: Invoke gsmSSF (T-CS) + gsmSSF-->>GMSC: gsmSSF Invoked + GMSC->>gsmSSF: DP_Termination_Attempt_Authorized + gsmSSF->>gsmSCF: Initial_DP (MT parameters) + gsmSCF-->>gsmSSF: Furnish Charging Information (Profile ID) + gsmSCF-->>gsmSSF: Connect (FTN) + gsmSSF-->>GMSC: Connect (FTN) + +``` + +Sequence diagram showing information flow for an MT call. Lifelines: GMSC, HLR, gsmSSF, gsmSCF, VLR, Destination MSC. The sequence involves routing information exchange, subscriber info lookup, gsmSSF invocation, and call setup parameters. + +Figure 35: Information flow for an MT call to a profile with CFNRc active and operative in the gsmSCF, where early CFNRc is invoked + +#### 7.11.1.6 Late CFNRc + +![Sequence diagram showing information flow for an MT call to a profile with CFNRc active and operative in the gsmSCF, where late CFNRc is invoked. The diagram involves four entities: GMSC, gsmSSF, gsmSCF, and MSC. The sequence of messages is: 1. GMSC sends an Initial Address Message to MSC. 2. MSC sends a Release (Not Reachable / Other (any other cause except 'Busy')) message back to GMSC. 3. GMSC sends a DP_T_Busy (Release Cause) message to gsmSSF. 4. gsmSSF sends an Event Report BCSM (interrupted) message to gsmSCF. 5. gsmSCF sends a Connect (FTN) message to gsmSSF. 6. gsmSSF sends a Connect (FTN) message to GMSC.](212c50c4e3d043c989037a01e13c1a98_img.jpg) + +``` + +sequenceDiagram + participant GMSC + participant gsmSSF + participant gsmSCF + participant MSC + Note left of GMSC: + GMSC->>MSC: Initial Address Message + MSC-->>GMSC: Release (Not Reachable / Other (any other cause except "Busy")) + GMSC->>gsmSSF: DP_T_Busy (Release Cause) + gsmSSF->>gsmSCF: Event Report BCSM (interrupted) + gsmSCF->>gsmSSF: Connect (FTN) + gsmSSF->>GMSC: Connect (FTN) + +``` + +Sequence diagram showing information flow for an MT call to a profile with CFNRc active and operative in the gsmSCF, where late CFNRc is invoked. The diagram involves four entities: GMSC, gsmSSF, gsmSCF, and MSC. The sequence of messages is: 1. GMSC sends an Initial Address Message to MSC. 2. MSC sends a Release (Not Reachable / Other (any other cause except 'Busy')) message back to GMSC. 3. GMSC sends a DP\_T\_Busy (Release Cause) message to gsmSSF. 4. gsmSSF sends an Event Report BCSM (interrupted) message to gsmSCF. 5. gsmSCF sends a Connect (FTN) message to gsmSSF. 6. gsmSSF sends a Connect (FTN) message to GMSC. + +**Figure 36: Information flow for an MT call to a profile with CFNRc active and operative in the gsmSCF, where late CFNRc is invoked** + +### 7.11.2 Call Barring + +Call Barring services can be provided by the gsmSCF per profile. An MO call made by an MSP subscriber will be subject to the outgoing call barrings provided for the Calling profile. An MT call to an MSP subscriber will be subject to the incoming call barrings provided for the Called profile. If an MT call to an MSP subscriber is forwarded, the forwarded call will be subject to the outgoing call barrings provided for the Called profile. + +The Call Barring services available per profile are: + +- Barring of all outgoing calls (BAOC); +- Barring of outgoing international calls (BOIC); +- Barring of outgoing international calls except those directed to the home PLMN country (BOIC-exHC); +- Barring of all incoming calls (BAIC); +- Barring of incoming calls when roaming outside the home PLMN country (BIC-roam). + +The Call Barring services, implemented by the gsmSCF, should operate in the same way as the Call Barring Supplementary Services. The MSP subscriber should have control over the call barring data (Registration, Erasure, Activation, Deactivation, and Interrogation). The method for controlling this data is a network option. + +If the MSP subscriber changes the Outgoing Call Barrings for the default profile by contacting the gsmSCF, the gsmSCF will change the barrings stored in the gsmSCF and inform the HLR using ATM to change the barrings stored in the HLR. The Call Barring Supplementary Services may require a password before Call Barring data can be changed. For the Call Barring Services implemented in the gsmSCF, use of a password is a network option. + +The operator should ensure that if the equivalent call barring service is provided then: + +- the OCB\_flag is set in the HLR (See subclause 6.1:OCB\_flag); +- if an equivalent outgoing call barring service is in a "Provisioned and Active" state in the gsmSCF for the default profile, that outgoing call barring supplementary service will be in a "Provisioned and Active" state in the HLR; +- if an equivalent outgoing call barring service is in a "Not Active" state in the gsmSCF for the default profile, that outgoing call barring supplementary service will be in a "Not Provisioned" state in the HLR; +- incoming Call Barrings shall not be provisioned in the HLR; + +NOTE: Barrings will not apply to MT short messages. + +### 7.11.3 Operator Determined Barring (ODB) + +Operator Determined Barring will be available per profile in the gsmSCF for the following categories: + +- Barring of outgoing calls; +- Barring of incoming calls; +- Barring of roaming; +- Barring of outgoing Premium Rate Calls; +- Barring specific to the home PLMN; +- Barring of registration of call forwarding; +- Barring of invocation of call transfer. + +However, if zone related barring is implemented in the gsmSCF, the appropriate data will be needed in the gsmSCF as well as the HLR. For barring of incoming calls when roaming outside the zone of the home country, the gsmSCF will need to use Any Time Interrogation to establish the location of the called party. + +Management of ODB data is operator specific. + +The operator should ensure that if the equivalent ODB service for an ODB category is provided then: + +- the ODB flag for the correct category is set in the HLR (See subclause 6.2: ODB flags); +- the ODB data for that category for the default profile is duplicated in the HLR. + +NOTE: Barring of incoming calls in the gsmSCF will not disallow MO or MT short messages. + +### 7.11.4 Advice of Charge (AoC) + +Advice of Charge is available per profile in the gsmSCF. This is detailed in the SDL diagrams in Section 7.5: Functions and Information flows. + +## 7.12 Exceptional Procedures + +### 7.12.1 Roaming into a network not supporting CAMEL Phase 3 + +When roaming into a network not supporting CAMEL Phase 3, only the functionality of MSP Phase 1 will be available to an MSP subscriber. + +The default profile subscription information shall apply to all supplementary services, excluding Call Forwarding and Call Barring, provisioned per profile. + +### 7.12.2 Roaming into a network not supporting CAMEL Phase 2 + +This subclause details MSP specific handling for roaming into a network not supporting CAMEL Phase 2. Other handling for this scenario is described in 3G TS 23.078. + +#### 7.12.2.1 Actions required on Location Update + +The HLR will send the outgoing call barring data and outgoing ODB data, specific to the default profile, to the VLR. + +#### 7.12.2.2 MO call handling + +When an MSP subscriber roams into a network not supporting CAMEL Phase 2, the default profile will be used for all outgoing traffic. + +#### 7.12.2.3 MT call handling + +MT calls to any profile will be received by the subscriber (subject to call forwardings and call barrings provided in the gsmSCF on the called profile), although no indication of the called profile will be received. + +The HLR will not allow OR, this means that for MT calls, the GMSC will always support CAMEL Phase 2, allowing the gsmSCF to invoke appropriate Call Forwardings and Call Barrings. + +#### 7.12.2.4 MO short message handling + +MO short messages will be sent from and charged to the default profile. + +### 7.12.3 Lack of availability of the Network Indication of Alerting feature + +If an MSP subscriber roams into a network not supporting the Network Indication of Alerting feature, or is using an MS that does not support the Network indication of Alerting feature, then the subscriber will still receive all MT calls, but no indication of the called profile will be given. + +# --- Annex A (informative): Provision and Withdrawal of MSP + +## A.1 Provision of MSP + +MSP will be provisioned by prior arrangement with the service provider. + +For an existing subscriber converting to an MSP subscriber, all profile specific data will be stored in the gsmSCF and removed from the HLR, and MSP will be provisioned in the HLR. + +For a new subscriber provisioned with the MSP service, all profile specific data will be stored in the gsmSCF and MSP will be provisioned in the HLR. + +Data specific to the Default Profile will be stored in both the HLR and the gsmSCF. + +## --- A.2 Withdrawal of MSP + +MSP will be withdrawn when there is only one profile remaining. In this event, the subscriber data will be stored in the HLR and removed from the gsmSCF, and the HLR will remove all MSP markings. The subscriber will then be treated as a normal subscriber. + +# Annex B (informative): Change history + +| TSG SA# | Spec | CR | | New Version | Subject/Comment | +|----------|-----------|-----|---------|-------------|----------------------------------------| +| Jun 1999 | GSM 03.97 | | | | Transferred to 3GPP CN | +| CN#04 | 23.097 | | | 3.0.0 | | +| CN#05 | 23.097 | 001 | | 3.0.1 | Various editorial corrections | +| CN#06 | 23.097 | 002 | R99 | 3.1.0 | Inclusion of MSP Phase 2 functionality | +| CN#06 | 23.097 | 003 | R99 | 3.1.0 | Interaction MSP and CF | +| CN#07 | 23.097 | 004 | R99 | 3.1.1 | Minor editorial corrections | +| CN#11 | 23.097 | | Rel-4 | 4.0.0 | Upgrade to Rel-4 | +| CN#16 | 23.097 | | Rel-5 | 5.0.0 | Release 5 after CN#16 | +| CN#26 | 23.097 | | Rel-6 | 6.0.0 | Release 6 after CN#26 | +| CT#36 | 23.097 | | Rel-7 | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.097 | | Rel-8 | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 23.097 | - | Rel-9 | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 23.097 | - | Rel-10 | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | 23.097 | - | Rel-11 | 11.0.0 | Update to Rel-11 version (MCC) | +| 2014-09 | 23.097 | - | Rel-12 | 12.0.0 | Update to Rel-12 version (MCC) | +| 2015-12 | 23.097 | - | Rel-13 | 13.0.0 | Update to Rel-13 version (MCC) | +| 2017-03 | 23.097 | - | Rel-14 | 14.0.0 | Update to Rel-14 version (MCC) | +| 2018-06 | 23.097 | - | Rel-15 | 15.0.0 | Update to Rel-15 version (MCC) | +| 2020-07 | 23.097 | - | Rel-16 | 16.0.0 | Update to Rel-16 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23110/4636adff5682a064f0ae5f13a1d464a6_img.jpg b/marked/Rel-16/23_series/23110/4636adff5682a064f0ae5f13a1d464a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b0282d8ebbbbe4b13f2bda5e9fbd079417f3e31 --- /dev/null +++ b/marked/Rel-16/23_series/23110/4636adff5682a064f0ae5f13a1d464a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af0445d0a90572a7a9c623e49cf7e6ccc851085297fc51fb0f495be1dc5716b2 +size 64528 diff --git a/marked/Rel-16/23_series/23110/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23110/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ea14f5a7411c9093623c375cfbc2470a918e940 --- /dev/null +++ b/marked/Rel-16/23_series/23110/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5af8804e2719ccf076aaa312f38b6a65016220ffc206e3acbb66d18a87f44e61 +size 30986 diff --git a/marked/Rel-16/23_series/23110/raw.md b/marked/Rel-16/23_series/23110/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..fa051eb119a707fc17fbb9ee3c62d2fe7ec7a7ce --- /dev/null +++ b/marked/Rel-16/23_series/23110/raw.md @@ -0,0 +1,1015 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 Basic Assumptions..... | 7 | +| 4.1 Boundaries of the Access Stratum ..... | 7 | +| 4.2 Main design guidelines..... | 7 | +| 5 Functions location inside/outside Access Stratum..... | 8 | +| 5.1 Call Control..... | 9 | +| 5.2 (Connection) Bearer Control..... | 9 | +| 5.3 Supplementary Services (CLIP, CF etc.) ..... | 10 | +| 5.4 Location Management..... | 10 | +| 5.5 Attach/ Detach..... | 10 | +| 5.6 Resource management..... | 10 | +| 5.7 Handover..... | 10 | +| 5.7.1 Handover - outside Access Stratum ..... | 10 | +| 5.7.2 Handover - inside Access Stratum ..... | 10 | +| 5.7.3 Handover scenarios supported by the Iu interface..... | 10 | +| 5.7.3.1 Classification A..... | 10 | +| 5.7.3.2 Classification B..... | 11 | +| 5.7.3.3 Classification C..... | 11 | +| 5.7.3.4 Classification D..... | 12 | +| 5.8 Macrodiversity ..... | 12 | +| 5.9 Encryption ..... | 12 | +| 5.10 Authentication of Subscriber..... | 12 | +| 5.11 (Non source dependent coding) Compression ..... | 12 | +| 5.12 Source (e.g. voice or video) Coding..... | 12 | +| 5.13 Radio Channel Coding ..... | 12 | +| 5.14 UE Location Identification..... | 13 | +| 5.15 Charging..... | 13 | +| 6 Access Stratum services..... | 13 | +| 6.1 Service Access Points (SAPs)..... | 14 | +| 6.1.1 General Control SAPs ..... | 15 | +| 6.1.2 Notification SAPs..... | 15 | +| 6.1.3 Dedicated Control SAPs..... | 15 | +| 6.2 Operations ..... | 15 | +| 6.2.1 General ..... | 15 | +| 6.2.2 Common operations..... | 16 | +| 6.2.2.1 General Control SAP ..... | 16 | +| 6.2.2.1.1 Information broadcast ..... | 16 | +| 6.2.2.2 Notification SAPs ..... | 16 | +| 6.2.2.2.1 Paging Request, IF side..... | 17 | +| 6.2.2.2.2 Notification Broadcast Request, IF side..... | 17 | +| 6.2.2.2.3 Notification Indication, UE side..... | 17 | +| 6.2.2.3 Dedicated Control SAPs ..... | 17 | +| 6.2.2.3.1 UE Side Initiated Connection Establishment..... | 18 | +| 6.2.2.3.2 Connection Release..... | 19 | +| 6.2.2.3.3 Information Transfer ..... | 19 | +| 6.2.2.3.4 IF Side Initiated Radio Access Bearer Establishment..... | 20 | +| 6.2.2.3.4.1 IF Side Initiated Radio Access Bearer Establishment Request, IF Side ..... | 21 | +| 6.2.2.3.4.2 IF Side Initiated Radio Access Bearer Establishment Indication, UE Side ..... | 21 | +| 6.2.2.3.4.3 IF Side Initiated Radio Access Bearer Establishment Response, UE Side ..... | 21 | +| 6.2.2.3.4.4 IF Side Initiated Radio Access Bearer Establishment Confirm, IF Side..... | 21 | + +| | | | +|------------------------|------------------------------------------------------------------------|----| +| 6.2.2.3.5 | IF Side Initiated Radio Access Bearer Release..... | 21 | +| 6.2.2.3.5.1 | IF Side Initiated Radio Access Bearer Release Request, IF Side..... | 21 | +| 6.2.2.3.5.2 | IF Side Initiated Radio Access Bearer Release Indication, UE Side..... | 22 | +| 6.2.3 | IF side only operations ..... | 22 | +| 6.2.3.1 | Dedicated control SAPs ..... | 22 | +| 6.2.3.1.1 | Position update indication ..... | 22 | +| 6.2.3.1.2 | Connection loss indication ..... | 22 | +| 6.2.3.1.3 | Streamlining required indication ..... | 22 | +| 6.2.3.1.4 | Branch establishment request..... | 22 | +| 6.2.3.1.5 | Branch establishment confirm..... | 22 | +| 6.2.3.1.6 | UE location information request ..... | 23 | +| 6.2.3.1.7 | UE location information confirm ..... | 23 | +| 6.2.4 | UE side only operations..... | 23 | +| 6.2.4.1 | Dedicated control SAPs ..... | 23 | +| 6.2.4.1.1 | Connection loss indication ..... | 23 | +| 6.3 | Parameters structure ..... | 23 | +| 6.3.1 | Local ..... | 23 | +| 6.3.2 | Bit string ..... | 23 | +| 6.3.3 | Enumerated..... | 24 | +| 6.3.4 | Geographical description..... | 24 | +| 6.3.5 | QoS ..... | 24 | +| 6.3.6 | Route..... | 24 | +| 6.3.7 | Transaction identifier..... | 24 | +| 6.3.8 | Transaction list ..... | 24 | +| 6.3.9 | Transmission mode..... | 24 | +| 6.3.10 | AN/CN Point List ..... | 24 | +| 6.3.11 | Localisation ..... | 24 | +| Annex A (informative): | Change history..... | 25 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 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. + +# --- 1 Scope + +The present document specifies the services provided by the Access Stratum to the rest of the system. The adopted architecture is given by TS 23.101 [2]. + +The present document describes the main functions visible at the boundary between the Access Stratum and the rest of the system, it describes in general terms the information flows, both control and user data, over this boundary and relevant for the Access Stratum. + +The present document is the basis of the detailed specifications of the protocols which rule the information flows, both control and user data, between the Access Stratum and the parts of UMTS outside the Access Stratum, and of the detailed specifications of the UTRAN. These detailed specifications are to be found in other Technical Specifications. + +# --- 2 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 TS 22.101: "Universal Mobile Telecommunications System (UMTS): Service aspects; Service principles". +- [2] 3GPP TS 23.101: "Universal Mobile Telecommunications System (UMTS): General UMTS Architecture". +- [3] 3GPP TS 23.105: "Universal Mobile Telecommunications System (UMTS): Network Principles". +- [4] ITU-T Recommendation X.210 (November 1993): "Information Technology - Open Systems Interconnection - Basic Reference Model: Conventions for the Definition of OSI Services". +- [5] 3GPP TS 23.107: "QoS Concept and Architecture". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TS 23.101 [2] and the following apply. + +**Access Stratum:** defined in TS 23.101 [2]. + +**Access Network:** defined in TS 23.101 [2]. + +**Edge-Node:** core network node which is connected to the URAN at a particular instance. + +**URAN:** defined in [TBD]. + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|----|----------------| +| AN | Access Network | +| AS | Access Stratum | +| CC | Call Control | + +| | | +|-------|--------------------------------------------| +| DC | Dedicated Control SAP | +| CN | Core Network | +| FFS | For Further Study | +| GC | General Control (SAP) | +| GPRS | General Packet Radio Service | +| GSM | Global System for Mobile communications | +| HPLMN | Home Public Land Mobile Network | +| IF | Infrastructure | +| ME | Mobile Equipment | +| MM | Mobility Management | +| MS | Mobile Station | +| NAS | Non Access Stratum | +| Nt | Notification (SAP) | +| PDN | Packet Data Network | +| PTM | Point to Multipoint | +| RAN | Radio Access Network | +| SAP | Service Access Point | +| SAPI | Service Access Point Identifier [???] | +| SIM | Subscriber Identity Module | +| SMS | Short Message Service | +| SS | Supplementary Services | +| TBD | To Be Defined | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunications System | +| URAN | UMTS Radio Access Network | +| USIM | UMTS Subscriber Identity Module | +| USSD | Unstructured Supplementary Service Data | +| UTRA | UMTS Terrestrial Radio Access | +| UTRAN | UMTS Terrestrial Radio Access Network | +| VBS | Voice Broadcast Service | +| VGCS | Voice Group Call Service | +| VPLMN | Visited Public Land Mobile Network | + +# 4 Basic Assumptions + +## 4.1 Boundaries of the Access Stratum + +The Access Stratum (AS) is defined in TS 23.101 [2]. It consists of a functional grouping which includes all the layers embedded in the URAN; and part of the layers in the User Equipment (UE) and the infrastructure (IF); i.e. the edge-node. Its boundary is the frontier between the layers which are independent of the access technique and the ones which are dependent on it. This frontier is located in the UE (mobile boundary) and in an edge-node (fixed boundary). There is a direct or "transparent" dialogue (i.e. not interpreted by the AS) between the UE and the edge-node for the Non-Access Stratum layers. + +## 4.2 Main design guidelines + +- 1) The Access Stratum contains all access specific functionality, e.g. all mode specific functionality in case of the UTRAN. +- 2) Reconfiguration of the AN, or changes in the AN domain functionality shall have minimal impact on Core Network functions, and vice-versa. +- 3) A given Access Network (e.g., the UTRAN) may provide access to different type of Core Networks via the Iu reference point. +- 4) The services, access signalling, mobility and subscriber management specific to each Core Network are completely outside the Access Stratum, and are transferred transparently by the Access Stratum. +- 5) The Access Stratum provides flexible radio access bearers characterised by parameters describing the type of information and QoS transported over the radio interface (i.e. not the actual radio resources). Some radio access bearers may be asymmetric, i.e., have different parameters on uplink and downlink. + +- 6) There are radio access bearers for both connection oriented packet-switched services, connectionless (store-and-forward) services, and circuit-switched traffic. +- 7) Parameters for connection-oriented radio access bearers may change during connection (bandwidth on demand, quality management). +- 8) Whether a terminal can be registered and have connections to several Core Networks simultaneously (i.e., over different instances of Iu) is FFS. +- 9) The Access Stratum can provide several parallel and independent radio access bearers to one user equipment each with its own characteristics. +- 10) Multimedia is handled outside the Access Stratum by multiplexing several streams onto one radio access bearer or by requesting several parallel radio access bearers. In the latter case, the possibly needed synchronisation is handled outside the Access Stratum. +- 11) Connection of a user equipment to several URAN at a time has to be studied. +- 12) Handover and if applied macrodiversity within one Access Network is handled within the Access Stratum. +- 13) Handover between two Access Networks (e.g., two UTRANs, or between UTRAN and GSM BSS) may use support from the Core Network. +- 14) The Access Stratum should hide all access -specific parameters, e.g., location data provided to the Core Networks should be independent from the actual configuration of the Access Network. +- 15) The user equipment can be connected to different AN/CN points via a single Access Network. The Access Stratum should be able to provide a flexible routing to the appropriate AN/CN point. + +# 5 Functions location inside/outside Access Stratum + +Following table shows the functional split between Access Stratum and the rest of the system. + +**Table 1: Functions inside/outside the Access Stratum** + +| LOCATION
\ FUNCTION | Outside the Access Stratum | Inside the Access Stratum | +|--------------------------------------|----------------------------|-----------------------------------| +| Call set up/release | yes | no | +| (Connection) Bearer Set-Up Release | CN bearer [tbd] | Radio Access Bearer [tbd] | +| Supplementary Services | yes | no | +| Location management | yes (IWF/CN related) | yes (Radio related) | +| Attach/ Detach | yes | FFS, Contr expected | +| Resource Management | yes (for NAS resource) | yes (for AS resource incl. radio) | +| Handover | yes* | yes | +| Macrodiversity [ffs] | yes* | yes | +| Encryption | yes | yes** | +| Authentication | yes | no | +| compression (non source dependent) | yes | yes | +| source dependent coding | yes | no | +| radio channel coding (could be many) | no | yes (could be many) | +| UE location identification | may be supported | yes | +| Charging | yes | no | + +NOTE \*: Optionally execution. In some CNs, it may not be present but not full service will be supported (e.g. limited to RLL type of service). +NOTE \*\*: Contributions expected to clarify the role between encryption and subscriber data. + +## 5.1 Call Control + +This Functionality is placed in the NAS, since it manipulates the call state machine. An example is termination of Q.931 message and sending of ISUP. + +Not part of AS. NAS specific signalling messages, e.g. Q.931, Q.2931 and ISUP. + +## 5.2 (Connection) Bearer Control + +It is distinguished between the bearers used in the NAS and the common bearer used in the AS (radio access bearer). + +Basic principles for radio access bearers are: + +- 1) Radio access bearers provide information transport between the non-access stratum parts of the infrastructure side (i.e. the edge node) and the user equipment side. Radio access bearers shall support real time as well as non real time user traffic. +- 2) Radio access bearers must be flexible enough to support different traffic types, activity levels, throughput rates, transfer delays and bit error rates. Attributes allowing efficient use of radio resources are crucial. +- 3) Efficient mapping from the traffic attributes used by non-UMTS applications, given by dominating external network technologies, to the attributes of the radio access bearer layer of the access stratum is essential. Complexity in mapping procedures should be avoided. +- 4) Definitions of traffic attributes and traffic management for radio access bearers shall be consistent with the predominant networking technology on the market (e.g. N-ISDN and IP networks for UMTS phase 1). As networking technologies emerge, adapted radio access bearer attributes and types shall gradually be added. +- 5) Radio access bearer definitions must allow for straightforward and efficient traffic management and resource handling of the radio resources in the access stratum. + +This procedure is part of the NAS. Example are 13.0 kbit/s (for GSM speech) and 2B+D (for ISDN BRI). + +The protocols required in AS to provide a radio access bearer should be able to describe both packet switch and circuit switch types of connections. + +## 5.3 Supplementary Services (CLIP, CF etc.) + +Supplementary services are part of the NAS, since they manipulate the Call state machine. + +Supplementary services are not part of AS since they manipulate the call state machine. + +## 5.4 Location Management + +"Location Updating Management" and "Paging" is an existing example of Location Management. + +Location Management may be supported in the NAS. + +Radio related Location Management may be part of the AS. + +## 5.5 Attach/ Detach + +If the Attach/ Detach procedures are supported in the NAS they use CN specific identifiers to mark the attached/detached subscriber. As an example in GSM, the attach/detach procedure is performed on the IMSI flag, and therefore it is a NAS functionality. + +Attach/Detach may be performed in the AS using the URAN unique identifiers. This is FFS. + +## 5.6 Resource management + +This function allocates resources for a given information stream, as to allow to convey it with a given QoS. This information stream may support either signalling data (CC, MM, ...) or user data. + +Both circuit switched and packet access are supported, offering both connection oriented and connectionless services. + +The AS resource management is transparent for the NAS and vice versa. + +## 5.7 Handover + +### 5.7.1 Handover - outside Access Stratum + +Handover may be a NAS functionality, but it can not be expected that all CNs will support handover therefore the IWF may take care of any required handover functionality. The AN may leave certain parameters, e.g. the address to a new IWF/CN-AN connection point, to which the IWF/CN may switch if it has the capabilities. + +### 5.7.2 Handover - inside Access Stratum + +Handover is performed in the AS, to hide all radio specific details from the NAS. + +### 5.7.3 Handover scenarios supported by the Iu interface + +The following clauses describe which functions will be supported by the Iu interface. Some functions have no impact on the Iu interface and therefore will be supported de-facto, nevertheless they are explicitly mentioned for completeness of the scenarios. + +#### 5.7.3.1 Classification A + +Classification A describes the way the handover is prepared: + +- HO A1: the network has informed the target cell before the MS changes cell; +- HO A2: the network has not informed the target cell before the MS changes cell; +- HO A3: the mobile has informed the target cell before it leaves the source cell. + +HO A1 is typical of the existing handover in GSM. + +HO A2 reflects the call re-establishment in GSM, mobile directed handovers in general, or even GPRS to some extent (although the GPRS vocabulary is different). + +HO A1, HO A2 and HO A3 shall be supported by the service primitives of the Iu interface. + +#### 5.7.3.2 Classification B + +Classification B describes the way the decision to initiate a handover is taken: + +- HO B1: decision is taken by the terminal; +- HO B2: decision is taken by the network. + +When the network takes the decision, it can be either in the RAN (HO B2a), or in the CN (probably based on information provided by the RAN and/or the MS) (HO B2b). + +In order to keep the radio independence from the CN, it would be desirable that the decision be taken only in the RAN. This means that a communication mechanism is needed between URANs, that interface being logically different from the Iu interface. + +HO B1 and HO B2 shall be supported by the service primitives of the Iu interface. + +NOTE 1: FFS: For HO B2 cases, handover initiation/decisions shall be taken by the source URAN. + +NOTE 2: FFS: There is a URAN to URAN signalling mechanism transparent to the CN. A standardised protocol will be implemented across that interface to allow handover decisions by the URAN in HO B2 cases. + +#### 5.7.3.3 Classification C + +Classification C concerns the kind of handover performed: + +- 1) intra-cell handover; +- 2) intra-URAN handover; + +- 3) inter-URAN handover (without change of CN access point); +- 4) intra-CN handover with same URAN type; +- 5) intra-CN handover with different URAN type; +- 6) inter-CN handover with same URAN type and same CN type; +- 7) inter-CN handover with different URAN type and same CN type; +- 8) inter-CN handover with same URAN type and different CN type; +- 9) inter-CN handover with different URAN type and different CN type; +- 10)inter-CN handover without change of URAN. + +The type of URAN type should be relatively transparent to the Iu interface. + +Regarding handovers across multiple CN, it is proposed that this is supported (and this is already possible with GSM). + +C1 to C7 scenarios shall be supported by the service primitives of the Iu interface. + +NOTE: FFS: scenarios C8 to C10 shall be supported by the service primitives of the Iu interface. + +#### 5.7.3.4 Classification D + +Regarding how a handover is performed, there is the possibility to either have the notion of anchor point, or not to have it. Example is circuit switched GSM, using anchor points, and GPRS, not using that notion. + +Furthermore, the notion of anchor point may be handled differently for the signalling plane and the transmission plane. + +The notion of anchor point shall be supported by the service primitives of the Iu interface. + +NOTE 1: FFS: the notion of transmission plane anchor point is supported by the service primitives of the Iu interface. + +NOTE 2: FFS: the notion of signalling plane anchor point is supported by the service primitives of the Iu interface. + +NOTE 3: FFS: the anchor points for the signalling plane and transmission plane need not necessarily be the same or even exist simultaneously. The flexibility should be left in UMTS by the Iu service principles. + +## 5.8 Macrodiversity + +(if needed, dependent of the choice of multiple access technology) + +Not all IWF/CNs will support macrodiversity. + +Macrodiversity may be supported in the AS, dependent on the choice of multiple access technology. + +## 5.9 Encryption + +The NAS may support encryption to protect the transmitted data. + +The AS needs to support encryption to prevent from eavesdropping at the radio interface. + +## 5.10 Authentication of Subscriber + +Subscriber data is stored in the NAS and therefore authentication should be considered a NAS functionality. + +NAS data is not stored in the URAN, and subscriber authentication can therefore not be a URAN functionality. + +## 5.11 (Non source dependent coding) Compression + +NAS may support compression. + +The AS should support compression to optimise usage of radio resources. + +## 5.12 Source (e.g. voice or video) Coding + +Source coding is different dependent on IWF/CN and is therefore a NAS functionality. + +## 5.13 Radio Channel Coding + +Radio Channel coding is needed due to the radio interface and could therefore be considered a radio functionality. Radio Channel coding is not a NAS functionality. + +Radio Channel coding is supported by URAN. + +## 5.14 UE Location Identification + +The UE location identification may be supported by the UE and/or the access network side of the AS; i.e., URAN; e.g., as defined in the GSM LCS (Location Services) specifications or by some other means. The UE location identification is provided to identify the likely location of specific UEs. This is meant to be used for charging, location-based services, lawful interception, emergency calls, etc., as well as the positioning services. + +When location identification is supported by URAN, the following apply: + +URAN obtains 'Area ID' and/or geographic co-ordinates with uncertainty parameters for identification of the likely location of UE, to be sent to the NAS entity side of the CN (i.e., edge node) 'Area ID' represents either a radio access cell/sector or a geographic area. 'Area ID' is coded in the same format as Cell Global Identification (CGI), for compatibility to GSM. + +Location information is categorised to two levels of accuracy. The Basic Level of information is what URAN obtains without extra signalling with the UE. The advanced level is obtained through extra signalling for positioning. Both levels can be used for both, Positioning services and other applications. + +Location information is always at least obtained from URAN by the appropriate edge node(s) at the activation of a Call/PDP Context. Mechanism to make it possible to obtain the location information at the release of a Call/PDP Context should be specified. Location information sent to the edge node at other occasions is on the basis of asynchronous requests from the edge node to URAN. An edge node can request URAN to send the location information with the two types of requests, Type 1 (Direct request) where URAN sends location information only once at the request and Type 2 (Event request) where URAN sends location information at each specified event (e.g. Cell Update) requested by the edge node. + +## 5.15 Charging + +The functions related to charging are not part of the AS. These functions are mainly: + +- charging information generation; +- charging processing. + +# --- 6 Access Stratum services + +The modelling of the services follow the basic principles as set by ITU-T Recommendation X.210 [4]. In this recommendation the following figure is given as an example for peer-to-peer connection-mode services. + +![Figure 1: Example of a peer-to-peer connection-mode service. The diagram shows two Service Users, A and B, interacting with an OSI-Service-Provider. Service User A sends a 'Request (requestor.submit)' to the provider and receives a 'Confirm (requestor.deliver)'. Service User B sends an 'Indication (acceptor.deliver)' to the provider and receives a 'Response (acceptor.submit)'. The diagram is labeled TISO2530-94/d03.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Figure 1: Example of a peer-to-peer connection-mode service. The diagram shows two Service Users, A and B, interacting with an OSI-Service-Provider. Service User A sends a 'Request (requestor.submit)' to the provider and receives a 'Confirm (requestor.deliver)'. Service User B sends an 'Indication (acceptor.deliver)' to the provider and receives a 'Response (acceptor.submit)'. The diagram is labeled TISO2530-94/d03. + +**Figure 1: Example of a peer-to-peer connection-mode service [4]** + +For connectionless-mode services the basic primitives are "request" and "indication". + +## 6.1 Service Access Points (SAPs) + +The SAPs offered by the Access Stratum (AS) to the rest of the system (Non Access Stratum: NAS) are reflected in the following figure. + +![Figure 2: Service Access Points (SAPs) offered by the Access Stratum (AS). The diagram is divided into two sides: User Equipment Side and Infrastructure Side. On the User Equipment Side, a UE contains NAS, AS, and UE-Uu layers. The AS offers three SAPs (GC, Nt, DC) to the NAS and three SAPs (GC, Nt, DC) to the UE-Uu. The UE-Uu layer is labeled 'Uu Svc: e.g., RRC'. On the Infrastructure Side, an Edge node contains NAS, AS, and CN-Iu layers. The AS offers three SAPs (GC, Nt, DC) to the NAS and three SAPs (GC, Nt, DC) to the CN-Iu. The CN-Iu layer is labeled 'Iu Svc: e.g., RANAP'. In the center, a RAN contains RNC Functions, IF-Uu, and RAN-Iu layers. The RNC Functions layer offers three SAPs (GC, Nt, DC) to the IF-Uu and three SAPs (GC, Nt, DC) to the RAN-Iu. The IF-Uu layer is labeled 'Uu Svc: e.g., RRC' and the RAN-Iu layer is labeled 'Iu Svc: e.g., RANAP'. A legend at the bottom left shows a diamond symbol labeled 'SAPs'.](4636adff5682a064f0ae5f13a1d464a6_img.jpg) + +Figure 2: Service Access Points (SAPs) offered by the Access Stratum (AS). The diagram is divided into two sides: User Equipment Side and Infrastructure Side. On the User Equipment Side, a UE contains NAS, AS, and UE-Uu layers. The AS offers three SAPs (GC, Nt, DC) to the NAS and three SAPs (GC, Nt, DC) to the UE-Uu. The UE-Uu layer is labeled 'Uu Svc: e.g., RRC'. On the Infrastructure Side, an Edge node contains NAS, AS, and CN-Iu layers. The AS offers three SAPs (GC, Nt, DC) to the NAS and three SAPs (GC, Nt, DC) to the CN-Iu. The CN-Iu layer is labeled 'Iu Svc: e.g., RANAP'. In the center, a RAN contains RNC Functions, IF-Uu, and RAN-Iu layers. The RNC Functions layer offers three SAPs (GC, Nt, DC) to the IF-Uu and three SAPs (GC, Nt, DC) to the RAN-Iu. The IF-Uu layer is labeled 'Uu Svc: e.g., RRC' and the RAN-Iu layer is labeled 'Iu Svc: e.g., RANAP'. A legend at the bottom left shows a diamond symbol labeled 'SAPs'. + +**Figure 2: Service Access Points (SAPs) offered by the Access Stratum (AS)** + +For the time being, the SAPs offered by the AS are symmetric, i.e. the same SAPs are offered on the infrastructure side (CN-AS) and on the user equipment side (UE-AS). These SAPs are: + +- GC: General Control (see 6.1.1 for a general presentation and 6.2.2.1 for a detailed information). +- Nt: Notification (see 6.1.2 for a general presentation and 6.2.2.2 for a detailed information). +- DC: Dedicated Control (see 6.1.3 for a general presentation and 6.2.2.3 for a detailed information). + +NOTE: Broadcast and Multicast services can not be described using the services and functions defined so far in the present document. The nature of Broadcast and Multicast services, like Cell Broadcast Service (CBS), is very different from other specified services. The following model characteristics are missing to fulfil the CBS requirements, namely: + +1. CBS uses two segments with different QoS requirements to deliver CB messages to the UE: + - 1a. From Cell Broadcast Centre (CBC) to RNC, a SAP is required where for instance, 1 second turnaround time, interactive class, with a reliable transport is required. + - 1b. From RNC to UE, a SAP is required where for instance, a maximum delay of 10 seconds and a background class is required. +2. Because of (item 1), the service primitives used by each of the segments may also be different; i.e., the related SAPs to those primitives may differ in the two segments and a combination of GC, Nt, and DC SAPs requires study. +3. CBS traffic is asymmetric in nature. The communication flow is only in one direction from the CBC to the UE. There is no uplink channel needed and the UE can not initiate a communication or request specific information. + +At least two changes are envisaged and thus detailed contributions are expected: + +- i. Introduce a new SAP type. +- ii. Mapping example between the two communication segments. + +Figure 2 shows also, as an example, some details of the AS architecture. The details are out of the scope of this document and are further specified in the 25-series. + +This model does not exclude, nor imply, which protocol is specified between the UE-AS entity and the CN-AS entity. These protocols are 'transparent' for the AN, but participate in the service provided by the AS. + +### 6.1.1 General Control SAPs + +These SAPs are used to enable the Core Network to provide information and to give commands that do not relate to specific users or specific [sessions] (group calls, conference). There is typically one General Control SAP per AN/CN connection point. On the UE side, a possible model is to consider that there is a single General Control SAP in an MS. + +### 6.1.2 Notification SAPs + +These SAPs are used to broadcast data to identified Users. The typical use is for initiating paging in the AN. There is typically one Notification SAP per AN/CN connection point. On the UE side, a possible model is to consider that there is a single Notification SAP (a Paging SAP) in an MS. + +### 6.1.3 Dedicated Control SAPs + +These SAPs are used to establish, release connections with specific User Equipment, and to exchange information related to these connections. A connection is a relationship between temporary contexts respectively in the AN and in the CN. The context in the AN is initiated at the establishment of the connection, and erased when the connection is released. Several types of connections are identified, such as point connection (single user) and group connections. + +There are typically a great number of Dedicated Control SAPs per AN/CN connection point. SAPs are identified by a SAPI at the AS boundary. During the lifetime of a connection, the connection can be identified unambiguously by the SAPI of the associated SAP, and the SAPI is used as a reference in the exchanges at the AS boundary on the infrastructure side. + +A SAPI is used as a connection identifier allocated unambiguously to each connection during its lifetime, and used in the exchanges at the AS boundary on the infrastructure side. + +On the UE side, a possible modelling is to consider that there is a single dedicated control SAP in an MS. + +NOTE 1: On the UE side, an open issue is whether simultaneous services from distinct ANs can be provided to an MS. Settling this issue may lead to a different model, for instance with the possibility to have several Dedicated Control SAPs, one per AN with which an active context exists. Another issue, visible when analysing Point-to-Multipoint services in GSM, is the SAP modelling for those PTM services. + +NOTE 2: The model is limited in this version to the cases where all the activity between a User Equipment and the infrastructure pertains to the same subscriber. Extension to cases with several subscriber sharing a User Equipment requires further study. + +## 6.2 Operations + +### 6.2.1 General + +The operations are described both for the AS boundary on the Infrastructure side and on the User Equipment side. The description of the operations on the Infrastructure side is given with sufficient details to develop on this basis a concrete control protocol at the AN/CN inter-connection. The description of the operations on the User Equipment side may be used [to be discussed] for developing a concrete API, allowing an open modular design of the User Equipment software. + +The operations are described in three clauses, one for operations that involve both the IF side and the UE side, one for operations local to the IF and finally one for operations local to the UE side. In each clauses, operations are sorted per SAP category. + +Request and confirm primitives are always toward the Access Stratum. Indication and response primitives are always from the Access Stratum. + +### 6.2.2 Common operations + +#### 6.2.2.1 General Control SAP + +##### 6.2.2.1.1 Information broadcast + +This operation consists in the broadcast from IF toward User Equipment of some information in some geographical area. This information is to be used by the User Equipment for instance to choose among access points or to be taken into account during initial access. The information can also be destined to an application. + +NOTE: This concerns only information to be broadcasted on behalf of Non Access Strata. Other information may be broadcasted for the internal use of the Access Stratum. + +###### 6.2.2.1.1.1 Information broadcast request, IF side + +The parameters are: + +| | | +|--------------------------|------------------------------------------------------------------| +| Category | enumerated (access point selection, initial access, application) | +| Geographical area | geographical area | +| Information to broadcast | bit string | + +The size of the information to broadcast is not bound by this description, but may be constrained by the access system. + +The geographical area is used by the AN to determine which access points are concerned. The rules are not specified in the external specification of the AS, but must exist and must be consistent with other translations between geographical descriptions and access points (e.g., in the connection establishment). + +The category is used by the AN to determine priority and more generally the parameters governing information repetition over time. + +NOTE: The category field could be enhanced, e.g., to allow a more precise control of priorities and repetitions. + +###### 6.2.2.1.1.2 Information Broadcast Indication, UE Side + +The parameters are: + +| | | +|------------------------|------------| +| Access point reference | local | +| Broadcast information | bit string | + +The access point reference identifies the point on the access boundary (e.g., the cell) where the information was received. + +NOTE: The access point reference is a local reference, to be used in other primitives at the AS/NAS boundary in the same UE. + +#### 6.2.2.2 Notification SAPs + +Notification operations consists of sending information to a dedicated user/terminal, or a group of users/terminals over a defined geographic area. + +Typically the request is forwarded to the user/terminal on a broadcast resource. If the AN knows of an existing signalling relation to the user/terminal, the information might be sent through the existing relation, according to Access Stratum specifications. + +##### 6.2.2.2.1 Paging Request, IF side + +The parameters are the following: + +| | | +|--------------------------------------|----------------------------| +| User/Terminal Identity | pageable identity | +| Geographical area where to broadcast | geographical area | +| Paging resource parameters | paging resource parameters | +| Information to send | bit string | + +The user/terminal identity is provided to determine if a signalling relation with the user/terminal exists. The geographical area indicates the area in which the Core Network knows the User/Terminal(s) to be. + +The size of the information to send is not bound by this description, but may be constrained by the access system. + +The paging resource parameters are used to determine which paging resource to be used when several are available. The organisation of paging resources is known in advance by the User Equipment, and are used by the User Equipment to choose the paging resources to listen to. The exact use of the paging resource parameters is specified as part of Access Stratum specifications. + +NOTE: This function is typically used for paging, i.e., to trigger an access from the User/Terminal. However, this is not relevant to the Access Stratum, and other uses can be envisaged without impacting the Access Stratum. The action required from the MS, if any, is indicated, implicitly or explicitly, in the information to send, the content of which being part of the Non Access Strata specifications and not of the Access Stratum specifications. + +##### 6.2.2.2.2 Notification Broadcast Request, IF side + +The parameters are the following: + +| | | +|--------------------------------------|----------------------------| +| Geographical area where to broadcast | geographical area | +| Notification resource parameters | paging resource parameters | +| Information to broadcast | bit string | + +The size of the information to broadcast is not bound by this description, but may be constrained by the access system. + +The paging resource parameters are used to determine which paging resource to be used when several are available. The organisation of paging resources is known in advance by the User Equipment, and are used by the User Equipment to choose the paging resources to listen to. The exact use of the paging resource parameters is specified as part of Access Stratum specifications. + +NOTE: This operation is used typically to inform all MSs of some starting or on-going activities, such as group calls. + +##### 6.2.2.2.3 Notification Indication, UE side + +Parameters + +| | | +|------------------------|------------| +| Access point reference | local | +| Broadcast information | bit string | + +NOTE: This primitive applies both for a paging sent on broadcast resources and for the reception of an information broadcast to many users. + +#### 6.2.2.3 Dedicated Control SAPs + +Dedicated Control operations are done within the scope of a connection, embodied by corresponding SAPs on the UE and IF sides. This scope is determined by local references (respectively on the UE side and on the IF side). All operations contain such a local reference, and, at a given AN/CN interconnection point, all operations with the same local reference from the establishment event to the release event pertain to the same connection. The correspondence between Dedicated Control SAPs on the UE and IF side is dynamic, and established through the connection establishment operations. + +The local connection references have only a local scope, and their values do not necessarily have any predictable relationship with the corresponding reference local to the other side, or with a reference used over some interface to multiplex the messages pertaining to the connection with messages pertaining to other connections. + +##### 6.2.2.3.1 UE Side Initiated Connection Establishment + +This operation consists in the establishment of a new connection at the initiative of NAS on the User Equipment side. + +###### 6.2.2.3.1.1 UE Side Initiated Connection Establishment Request, UE side + +Parameters + +| | | +|----------------------------|--------------------| +| Local connection reference | local | +| Routing parameters | routing parameters | +| Initial message | bit string | + +The routing parameters are to be used by the AS on the Infrastructure side to choose the AN/CN connection point through which the connection is to be established. + +The initial message is to be forwarded to the non-access strata. The size of the initial message should not be constrained by the access system. + +###### 6.2.2.3.1.2 UE Side Initiated Connection Establishment Indication, IF side + +Parameters + +| | | +|----------------------------|-------------------| +| Local connection reference | local | +| Initial message | bit string | +| Localisation data | localisation data | + +The localisation data indicate the knowledge the AN has of the localisation of the initiating User Equipment. It includes typically a geographical area and some accuracy indication. + +###### 6.2.2.3.1.3 UE Side Initiated Connection Establishment Confirm, IF Side + +Parameters + +| | | +|----------------------------|------------------------------------------| +| Local connection reference | local | +| Status | enumerated (terminated by NAS, going on) | +| Initial answer | bit string | + +The NAS can choose not to pursue the connection (status = terminated by NAS). Reasons can be that the information provided by the User Equipment did not require more than a single message answer (e.g., store-and-forward service), or some exception conditions prevented the CN to pursue the connection. + +The initial answer is to be provided to the requesting part in the non-access strata. + +###### 6.2.2.3.1.4 UE Side Initiated Connection Establishment Response, UE side + +Parameters + +| | | +|----------------------------|------------------------------------------------------------| +| Local connection reference | local | +| Status | enumerated (terminated by NAS, terminated by AS, going on) | +| Initial answer | bit string | + +The initial answer is not provided in the case the status is 'terminated by AS'. The status 'going on' and 'terminated by NAS' indicates that the initial message was delivered to the NAS; on the other hand, the status 'terminated by AS' can happen whether or not the initial message was delivered to the NAS. + +##### 6.2.2.3.2 Connection Release + +This operation is the termination of a connection, at the request of non-access strata on the Infrastructure side. The use of this operation may lead to the non-completion of other previously started operations in the same connection (e.g., transparent data transfer). + +###### 6.2.2.3.2.1 IF Initiated Connection Release Request, IF Side + +Parameter + +| | | +|----------------------------|-------| +| Local connection reference | local | +|----------------------------|-------| + +###### 6.2.2.3.2.2 IF Initiated Connection Release Indication UE side + +Parameter + +| | | +|----------------------------|-------| +| Local connection reference | local | +|----------------------------|-------| + +##### 6.2.2.3.3 Information Transfer + +These operations allow the transfer of messages between Non-Access Strata elements on each side of the access interface. + +The service is essentially that of a transport layer, with multiplexing, and possibly guarantee of order and correct transmission (transmission difficulties lead to connection loss), including the effect of user movements. The operation caters only for transmission from AS boundary to access boundary. Upper layers of protocol are typically added for addressing and routing beyond this boundary. + +Several independent streams can exist simultaneously on the same connection, as distinguished by a routing and transaction identifiers. Message order is guaranteed, if applicable, on a stream basis. Routing identifiers are typically used to indicate originator and destination (e.g., USIM to Home, ME to Serving, and also distinctions such as GSM between MM and CC for instance...). Transaction identifiers are used to distinguish streams with the same originator and destination. Messages can be sent within a transaction or not. Transactions are explicitly set up and released, either in-band (i.e., together with information transfer) or out-band. Transaction identifiers have only a local significance. + +NOTE 1: There is a difficulty behind the message order. In some cases it may be important to keep message order in a combination of streams, e.g., within a route, or even involving two routes. The model presented so far is too simple to cope with such cases. + +A quality of service indication is present in sending requests. This covers such aspects as message order, effect on other on-going traffic (e.g., speech pre-emption), delay. A finite number of quality of service classes will be identified, and the one to apply to a message indicated. + +With each transaction is associated a default quality of service, established at transaction establishment or by a subsequent modification request. + +A transmission mode indication is present in reception indications. This gives information from the Access Stratum on the aspects of the transmission related to service quality of service (e.g., speech has been pre-empted). + +NOTE 2: This covers circuit data transport, including cases where each message is very small (down to 1 bit or other information quantum). Obviously, in such cases these primitives are a model not to be followed in implementations. + +###### 6.2.2.3.3.1 Data Transfer Request, IF Side + +###### Parameters + +| | | +|-------------------------------|----------------------------------------------| +| Local connection reference | local | +| Route | route | +| Transaction identification | local | +| Transaction management | enumerated (single, first, subsequent, last) | +| Quality of Service indication | QoS | +| Message | bit string | + +The transaction management field indicates if the message is independent from transactions (single), is the first of the transaction and hence initialises the transaction (first), is the last of the transaction and hence releases the transaction (last), or is in the middle of a transaction. + +The primitive can be used with an empty message for transaction management alone (value 'single' is then meaningless). + +###### 6.2.2.3.3.2 Data Transfer Indication, UE Side + +###### Parameters + +| | | +|------------------------------|----------------------------------------------| +| Local connection reference | local | +| Route | route | +| Transaction identification | local | +| Transaction management | enumerated (single, first, subsequent, last) | +| Transmission mode indication | transmission mode | +| Message | bit string | + +###### 6.2.2.3.3.3 Data Transfer Request, UE Side + +###### Parameters + +| | | +|-------------------------------|----------------------------------------------| +| Local connection reference | local | +| Route | route | +| Transaction identification | local | +| Transaction management | enumerated (single, first, subsequent, last) | +| Quality of Service indication | QoS | +| Message | bit string | + +###### 6.2.2.3.3.4 Data Transfer Indication, IF Side + +###### Parameters + +| | | +|------------------------------|----------------------------------------------| +| Local connection reference | local | +| Route | route | +| Transaction identification | local | +| Transaction management | enumerated (single, first, subsequent, last) | +| Transmission mode indication | transmission mode | +| Message | bit string | + +##### 6.2.2.3.4 IF Side Initiated Radio Access Bearer Establishment + +These operations allow the transfer of control messages for radio access bearer establishment between non-access strata elements on each side of the access interface. The operations pertain to the connection identified by the local connection reference parameter. The operations allow the IF side to initialise a radio access bearer. The operation also implies a request to the AS to allocate transmission resources to the radio access bearer. + +A radio access bearer identification uniquely identifies the radio access bearer. It is used in all primitives that pertain to the radio access bearer. It also serves as the binding to a NAS call. + +The Iu bearer identification identifies the Iu connection. + +A quality of service request specifies the bearer characteristics that apply to the radio access bearer. + +###### 6.2.2.3.4.1 IF Side Initiated Radio Access Bearer Establishment Request, IF Side + +Parameters + +| | | +|------------------------------------|------------| +| Local connection reference | local | +| Radio access bearer identification | bit string | +| Iu bearer identification | bit string | +| Quality of Service request | QoS | + +###### 6.2.2.3.4.2 IF Side Initiated Radio Access Bearer Establishment Indication, UE Side + +Parameters + +| | | +|------------------------------------|------------| +| Local connection reference | local | +| Radio access bearer identification | bit string | +| Iu bearer identification | bit string | + +###### 6.2.2.3.4.3 IF Side Initiated Radio Access Bearer Establishment Response, UE Side + +Parameters + +| | | +|------------------------------------|------------------------------------------| +| Local connection reference | local | +| Radio access bearer identification | bit string | +| Status | enumerated (terminated by NAS, going on) | + +###### 6.2.2.3.4.4 IF Side Initiated Radio Access Bearer Establishment Confirm, IF Side + +Parameters + +| | | +|------------------------------------|------------------------------------------------------------| +| Local connection reference | local | +| Radio access bearer identification | bit string | +| Status | enumerated (terminated by NAS, terminated by AS, going on) | + +##### 6.2.2.3.5 IF Side Initiated Radio Access Bearer Release + +These operations allow the transfer of radio access bearer release messages between non-access strata elements on each side of the access interface. The operations pertain to the connection identified by the local connection reference parameter. The operations allow IF side to release a radio access bearer. + +NOTE: A radio access bearer release procedure is normally initiated by the IF side. Abnormal cases such as termination by the AS are FFS. + +###### 6.2.2.3.5.1 IF Side Initiated Radio Access Bearer Release Request, IF Side + +###### Parameters + +| | | +|------------------------------------|------------| +| Local connection reference | local | +| Radio access bearer identification | bit string | + +###### 6.2.2.3.5.2 IF Side Initiated Radio Access Bearer Release Indication, UE Side + +###### Parameters + +| | | +|------------------------------------|------------| +| Local connection reference | local | +| Radio access bearer identification | bit string | + +### 6.2.3 IF side only operations + +#### 6.2.3.1 Dedicated control SAPs + +##### 6.2.3.1.1 Position update indication + +###### Parameters + +| | | +|----------------------------|----------| +| Local connection reference | local | +| Position | position | + +##### 6.2.3.1.2 Connection loss indication + +###### Parameters + +| | | +|----------------------------|-------| +| Local connection reference | local | +|----------------------------|-------| + +##### 6.2.3.1.3 Streamlining required indication + +This operation is used by the AS to indicate that the connection runs the risk to be aborted unless a streamlining is done. + +###### Parameters + +| | | +|-------------------------------------------|------------------| +| Local connection reference | local | +| Proposed list of alternative AN/CN points | AN/CN point list | + +##### 6.2.3.1.4 Branch establishment request + +This operation establishes a new branch supporting dedicated mode transport for a given UE. + +###### Parameters + +| | | +|----------------------------|------------------| +| Local connection reference | local | +| Transaction list | transaction list | + +The transaction list describes the transactions for which the establishment prior the first transmission of data is required. + +##### 6.2.3.1.5 Branch establishment confirm + +This indicates that the branch is successfully established up to the UE and can then be used for transmission. As a result, the NAS may decide to remove the old branch. + +Parameters + +| | | +|----------------------------|-------| +| Local connection reference | local | +|----------------------------|-------| + +##### 6.2.3.1.6 UE location information request + +This operation is sent from the NAS entity inside the CN (i.e. edge node) to the access network side of AS (i.e. URAN) to request the location information of a specific UE. + +Parameters: + +| | | +|----------------------------|---------------------------------| +| Local connection reference | local | +| Level of accuracy | basic level or advanced level | +| Type of request | direct request or event request | +| Event | conditions to send information | + +The level of accuracy describes the granularity required on the UE location information, either basic or advanced. The type of request describes whether the request is to get the current UE location or to get the location when some conditions specified by event are satisfied. + +##### 6.2.3.1.7 UE location information confirm + +This operation is sent in response to the UE location information request operation. + +Parameters: + +| | | +|----------------------------|-------------------------------------------------| +| Local connection reference | local | +| Area ID | UE location information in terms of CGI format | +| Geographic coordinates | UE location information in terms of coordinates | +| Event | conditions met | + +The Area ID is to be formatted in accordance with the CGI (Cell Global Identity). The geographic co-ordinates represents the physical co-ordinates on the earth and uncertainty parameters. + +[To be completed] + +### 6.2.4 UE side only operations + +#### 6.2.4.1 Dedicated control SAPs + +##### 6.2.4.1.1 Connection loss indication + +Parameters + +| | | +|----------------------------|-------| +| Local connection reference | local | +|----------------------------|-------| + +[To be completed] + +## 6.3 Parameters structure + +### 6.3.1 Local + +The structure is not relevant in the scope of this document, and can be decided on an implementation basis. + +### 6.3.2 Bit string + +A finite ordered sequence of bit values. + +### 6.3.3 Enumerated + +The parameter can take one value out of a list explicitly given. + +### 6.3.4 Geographical description + +TBI + +### 6.3.5 QoS + +This clause describes the radio access bearer (RAB) by referencing a list of attributes related to the QoS. The radio access bearers are divided into two categories: + +- Restricted radio access bearers; +- Unrestricted radio access bearers. + +An unrestricted radio access bearer is meant for data requiring bit sequence integrity (e.g., N-ISDN data transport), whereas a restricted radio access bearer contains a description of the nature of the information (e.g., encoded voice). For a restricted radio access bearer, the characteristics are implicitly given. + +The characterisation of a radio access bearer is made by using a set of attributes. A radio access bearer attribute is a specific characteristic that distinguishes it from other radio access bearer services. Refer to TS 23.107 [5] for a list of these QoS attributes. Particular values are also indicated in that specification for different services. + +In order to describe the desired radio access bearer service, QoS attributes are defined at the SAP. Note that it is not necessary, nor meaningful to support all possible combinations of parameter settings. + +NOTE: In case of an unrestricted radio access bearer, for every SDU provided at the SAP, bit sequence integrity should be maintained. + +### 6.3.6 Route + +TBI + +### 6.3.7 Transaction identifier + +Local. + +### 6.3.8 Transaction list + +A list of transactions, each described by a transaction identifier (local) and by QoS parameters. + +### 6.3.9 Transmission mode + +TBI + +### 6.3.10 AN/CN Point List + +TBI + +### 6.3.11 Localisation + +TBI + +# --- Annex A (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|----------|----|-----|--------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2004-12 | SA#26 | | | | Created version 6.0.0 | 5.0.0 | 6.0.0 | +| 2007-06 | SP-36 | - | - | - | Updated to Rel-7 version (MCC) | 6.0.0 | 7.0.0 | +| 2008-12 | SP-42 | - | - | - | Updated to Rel-8 version (MCC) | 7.0.0 | 8.0.0 | +| 2009-12 | SP-46 | - | - | - | Updated to Rel-9 version (MCC) | 8.0.0 | 9.0.0 | +| 2011-03 | SP-51 | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | SP-65 | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2015-12 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | - | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 | +| 2018-06 | SP-80 | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | SP-88E | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23116/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/Rel-16/23_series/23116/07b17a620c75522d53916a11e12d1bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7c24b81142a694eb54c1d4605a098aee65e1ea7 --- /dev/null +++ b/marked/Rel-16/23_series/23116/07b17a620c75522d53916a11e12d1bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b19720bf9d5a2887cce4713e2d304ce4a7c39159f835f83fb9e5c3fe3baeac7 +size 74202 diff --git a/marked/Rel-16/23_series/23116/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/Rel-16/23_series/23116/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbfb4fbe1320d6883fc492f141fdf82160e3c20d --- /dev/null +++ b/marked/Rel-16/23_series/23116/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b375a81517a372947c070671428a56387a4b5d9cd3bb7f1019a34f8139b521d +size 45406 diff --git a/marked/Rel-16/23_series/23116/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23116/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b153b28247bbc6978ea2bb98b1fa992b9ffb3ee --- /dev/null +++ b/marked/Rel-16/23_series/23116/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a7dc7e1c7b0e995be2cc7760cc6cd331c7e44228bda6aa7740b1838d4ecc051 +size 99561 diff --git a/marked/Rel-16/23_series/23116/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/marked/Rel-16/23_series/23116/1b5a812c8aa20fd5cba28e97001d32de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9019c4558d811a4cfb0bddcbf2270dc8b9d399e6 --- /dev/null +++ b/marked/Rel-16/23_series/23116/1b5a812c8aa20fd5cba28e97001d32de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:395df4ccf6804559b009946d38628070dec9d2665e7b087518065651f29ca3dc +size 43075 diff --git a/marked/Rel-16/23_series/23116/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/Rel-16/23_series/23116/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6b30d1b08deeb2bd7dc413a5028300464c77cc2 --- /dev/null +++ b/marked/Rel-16/23_series/23116/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8726d0bb3ce966016cd1269683d4c1e9ab98d22dab7dede216fca060ccfb93b4 +size 46526 diff --git a/marked/Rel-16/23_series/23116/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/Rel-16/23_series/23116/43837b056625d3d6ce615e4c02f163bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0c2ac2edaee7b9a3f422bc81448ac1fbb91fd64 --- /dev/null +++ b/marked/Rel-16/23_series/23116/43837b056625d3d6ce615e4c02f163bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74170c1e03871b862fee92d5764e9a899153c805a46b6832e8ace72551ad1313 +size 29360 diff --git a/marked/Rel-16/23_series/23116/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg b/marked/Rel-16/23_series/23116/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee8c64b2d1145b71bcd9a51df25d3bfd70c4ebe0 --- /dev/null +++ b/marked/Rel-16/23_series/23116/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c216dacc3c1fd303b7683f2786c893d235e904c1a395bef934f1366bf4393e40 +size 52972 diff --git a/marked/Rel-16/23_series/23116/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/Rel-16/23_series/23116/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d1efe212267f2371a64bc026d01298a8b6de3cc --- /dev/null +++ b/marked/Rel-16/23_series/23116/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6baba14daa2bf7f7fcf3a1f4013e574d9d9ea0510c42f2b0f915c88f7c3330b2 +size 24084 diff --git a/marked/Rel-16/23_series/23116/a734898ce18e972938949637c32a34f4_img.jpg b/marked/Rel-16/23_series/23116/a734898ce18e972938949637c32a34f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fd31ebf89f44c12189a7640cc887bdd7ba6ba6f --- /dev/null +++ b/marked/Rel-16/23_series/23116/a734898ce18e972938949637c32a34f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94f7a5f8ea1523ad97e0fa48c8fb0558296726ee6b81bac7f364ab9fa4f71ffd +size 33538 diff --git a/marked/Rel-16/23_series/23116/b28af4985cdef1e519e3aaf26561dcb3_img.jpg b/marked/Rel-16/23_series/23116/b28af4985cdef1e519e3aaf26561dcb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5b60522941698a5a64e91f29239cbe8c905c7d3 --- /dev/null +++ b/marked/Rel-16/23_series/23116/b28af4985cdef1e519e3aaf26561dcb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd9cc9d83193d90e48aa1d869a13b89f143bf7fead8d04811886912a93eefab3 +size 75582 diff --git a/marked/Rel-16/23_series/23116/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg b/marked/Rel-16/23_series/23116/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9058ae896c775a5e1071bcdc68f56e01d6a7edb --- /dev/null +++ b/marked/Rel-16/23_series/23116/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ad06087f0f755096a62fd79330944ad3f35f64ef77930837fd64fedc0505cc5 +size 55635 diff --git a/marked/Rel-16/23_series/23116/raw.md b/marked/Rel-16/23_series/23116/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..43d3b7a9b3d19e3fd1c15c7061a0c71603485a25 --- /dev/null +++ b/marked/Rel-16/23_series/23116/raw.md @@ -0,0 +1,682 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Abbreviations ..... | 6 | +| 4 Information flows..... | 6 | +| 4.1 Location Updating in a Super-Charged Network..... | 6 | +| 4.1.1 CS-domain Location Updating in a serving network entity that does not have subscription data..... | 6 | +| 4.1.2 CS-domain Location Updating in a network entity that has retained subscription data ..... | 7 | +| 4.1.3 PS-domain Location Updating in a network entity that does not have subscription data ..... | 8 | +| 4.1.4 PS-domain Location Updating in a network entity that has retained subscription data..... | 9 | +| 5 Functional behaviour..... | 11 | +| 5.1 Subscriber Settings..... | 11 | +| 5.2 Data Consistency..... | 11 | +| 5.2.1 Modification of subscription data..... | 11 | +| 5.2.2 Location Updating ..... | 11 | +| 5.2.2.1 Detailed Procedure in the serving network entity..... | 11 | +| 5.2.2.2 Detailed Procedure in the HLR..... | 13 | +| 5.2.3 Cancel Location..... | 15 | +| 5.2.3.0 General..... | 15 | +| 5.2.3.1 Detailed procedures in the serving network entity ..... | 15 | +| 5.2.3.2 Detailed procedures in the HLR ..... | 15 | +| 5.2.4 Purge MS..... | 16 | +| 5.2.4.1 CS-domain restoration procedures..... | 19 | +| 5.2.4.2 Mobile Terminating Short Message Service ..... | 22 | +| 5.3 Subscriber Deactivation ..... | 23 | +| 5.4 TMSI Management ..... | 23 | +| 5.5 Database Management ..... | 23 | +| 5.5.1 Utilisation of a larger database ..... | 23 | +| 5.5.2 Periodic Audit..... | 23 | +| 5.5.3 Dynamic Subscription Data Deletion..... | 24 | +| 5.6 Enhanced User Identity Confidentiality ..... | 24 | +| 5.7 Exception procedure..... | 24 | +| 6 Contents of the messages ..... | 25 | +| 6.1 Update Location ..... | 25 | +| 6.2 Update Location ack..... | 25 | +| 6.3 Update GPRS Location ..... | 25 | +| 6.4 Update GPRS Location ack..... | 26 | +| 6.5 Insert Subscriber Data ..... | 26 | +| 6.6 Insert Subscriber Data ack..... | 26 | +| Annex A (informative): Change History..... | 27 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 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. + +# --- 1 Scope + +The present document specifies the stage 2 description of the Super-Charger that provides a mechanism to reduce the signalling traffic associated with mobility. + +# --- 2 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 TS 21.905: "3G Vocabulary". +- [2] 3GPP TR 23.912: "Technical Report on Super-Charger". +- [3] 3GPP TS 23.007: "Restoration Procedures". +- [4] 3GPP TS 23.008: "Organisation of Subscriber Data". +- [5] 3GPP TS 23.012: "Location Management Procedures". +- [6] 3GPP TS 23.016: "Subscriber Data Management: Stage 2". +- [7] 3GPP TS 23.040: "Technical Realisation of the Short Message Service (SMS); Point-To-Point (PP)". +- [8] 3GPP TS 23.060: "General Packet Radio Service; Stage 2". +- [9] 3GPP TS 29.002: "Mobile Application Part (MAP)". +- [10] 3GPP TS 23.018: "Basic call handling; Technical realization". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document the following terms and definitions apply. + +Procedure Calls to stage 2. + +| | | +|---------------------------------|------------------------------------------------------------------------------------------------------------| +| Super-Charged Network: | UMTS network in which the Super-Charger mechanism is being used to optimise mobility management signalling | +| Network Entity: | either an MSC/VLR, SGSN or UMSC | +| Serving Network Entity: | network entity to which the mobile station is attached | +| Previous Network Entity: | network entity to which the mobile station was attached prior to the serving network entity | + +## 3.2 Abbreviations + +Abbreviations used in the present document are listed in GSM 01.04. + +# 4 Information flows + +In a Super-Charged network subscription data is retained by the previous network entity when the subscriber roams to a new network entity. + +When a subscriber performs location updating in a Super-Charged network the HLR shall only cancel the subscription information at the previous network entity if it does not support the Super-Charger functionality except in the conditions described in section 5.2.3.0. If the network entity to which the subscriber has roamed has retained subscription data from a previous visit then the HLR shall only send subscription data to the network entity if the retained subscription data is not consistent with the data stored by the HLR. If the HLR does not send subscription data to the serving network entity it shall treat the retained subscription data as valid. + +## 4.1 Location Updating in a Super-Charged Network + +### 4.1.1 CS-domain Location Updating in a serving network entity that does not have subscription data + +When a Super-Charged network entity receives a request to perform a location update for a subscriber for whom there is no record, the network entity shall initiate the location updating procedures as described in 3GPP TS 23.012. + +The Super-Charged HLR shall determine whether the previous network entity supports the Super-Charger functionality: + +- if the previous network entity does not support the Super-Charger functionality then the HLR shall respond to the location updating request as described in 3GPP TS 23.012; +- if the previous network entity supports the Super-Charger functionality then the HLR shall respond to the location updating request as described in 3GPP TS 23.012 but shall not cancel the location information at the previous network entity except in the conditions described in section 5.2.3.0. + +![Sequence diagram showing information flow for an inter-node location update in a Super-Charged network. The diagram involves five lifelines: MS, RNC, Serving Network Entity, Previous Network Entity, and HLR. The sequence starts with the MS sending a 'Location Update Request' to the RNC, which then forwards it to the Serving Network Entity. The Serving Network Entity sends a 'Send ID Req.' to the Previous Network Entity, which responds with 'Send ID Res.'. Next, the Serving Network Entity sends an 'Update Location Req.' to the HLR. The HLR then sends a 'Cancel Location' message to the Previous Network Entity, which responds with 'Cancel Location Res.'. This pair of messages is labeled 'Note 1'. The HLR then sends an 'Insert Subscriber Data' message to the Serving Network Entity, which responds with 'Insert Subscriber Data Res.'. Finally, the HLR sends an 'Update Location Res.' to the Serving Network Entity, which then sends a 'Location Update Confirm' back to the MS via the RNC.](43fec6623ab9cb223a9ff74e2d2a4402_img.jpg) + +``` + +sequenceDiagram + participant MS + participant RNC + participant Serving Network Entity + participant Previous Network Entity + participant HLR + + MS->>RNC: Location Update Request + RNC->>Serving Network Entity: + Serving Network Entity->>Previous Network Entity: Send ID Req. + Previous Network Entity-->>Serving Network Entity: Send ID Res. + Serving Network Entity->>HLR: Update Location Req. + Note right of HLR: Note 1 + HLR->>Previous Network Entity: Cancel Location + Previous Network Entity-->>HLR: Cancel Location Res. + HLR->>Serving Network Entity: Insert Subscriber Data + Serving Network Entity-->>HLR: Insert Subscriber Data Res. + HLR->>Serving Network Entity: Update Location Res. + Serving Network Entity->>RNC: + RNC->>MS: Location Update Confirm + +``` + +Sequence diagram showing information flow for an inter-node location update in a Super-Charged network. The diagram involves five lifelines: MS, RNC, Serving Network Entity, Previous Network Entity, and HLR. The sequence starts with the MS sending a 'Location Update Request' to the RNC, which then forwards it to the Serving Network Entity. The Serving Network Entity sends a 'Send ID Req.' to the Previous Network Entity, which responds with 'Send ID Res.'. Next, the Serving Network Entity sends an 'Update Location Req.' to the HLR. The HLR then sends a 'Cancel Location' message to the Previous Network Entity, which responds with 'Cancel Location Res.'. This pair of messages is labeled 'Note 1'. The HLR then sends an 'Insert Subscriber Data' message to the Serving Network Entity, which responds with 'Insert Subscriber Data Res.'. Finally, the HLR sends an 'Update Location Res.' to the Serving Network Entity, which then sends a 'Location Update Confirm' back to the MS via the RNC. + +**Figure 1: Information flow for an inter-node location update in a Super-Charged network for the case when the serving network entity does not have subscription data for the requesting mobile station** + +Note 1: If the previous network entity supports the Super-Charger features the HLR shall not cancel the location information at the previous network entity unless the Inform Previous Network Entity is included in the Update Location message, except in the conditions described in section 5.2.3.0. + +### 4.1.2 CS-domain Location Updating in a network entity that has retained subscription data + +When a Super-Charged network entity receives a request to perform a location update for a subscriber for whom subscription data has been retained, the network entity shall initiate the location updating procedures as described in 3GPP TS 23.012. + +The Super-Charged HLR shall determine whether the previous network entity supports the Super-Charger functionality: + +- if the previous network entity does not support the Super-Charger functionality then the HLR shall cancel the location information at the previous network entity as described in 3GPP TS 23.012. +- if the previous network entity supports the Super-Charger functionality then the HLR shall not cancel the location information at the previous network entity except in the conditions described in section 5.2.3.0. + +The Super-Charged HLR shall determine whether the subscription data retained by the serving network entity is consistent with the subscription data stored in the HLR: + +- if the subscription data is consistent then the HLR shall not send subscription data to the serving network entity as part of the location updating; +- if the subscription data is not consistent then the HLR shall respond to the location updating request as described in 3GPP TS 23.012. + +![Sequence diagram showing information flow for an inter-node location update. Lifelines: MS, RNC, Serving Network Entity, Previous Network Entity, HLR. The process starts with a Location Update Request from MS to Serving Network Entity. The Serving Network Entity sends a Send ID Req. to Previous Network Entity, which responds with Send ID Res. Next, the Serving Network Entity sends an Update Location Request to HLR. The HLR sends a Cancel Location Req. to Previous Network Entity, which responds with Cancel Location Res. (Note 1). Then, the HLR sends an Insert Subscriber Data Req. to Serving Network Entity, which responds with Insert Subscriber Data Res. (Note 2). Finally, the HLR sends an Update Location Res. to Serving Network Entity, which then sends a Location update confirm to MS.](ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg) + +``` + +sequenceDiagram + participant MS + participant RNC + participant Serving Network Entity + participant Previous Network Entity + participant HLR + + MS->>Serving Network Entity: Location Update Request + Serving Network Entity->>Previous Network Entity: Send ID Req. + Previous Network Entity-->>Serving Network Entity: Send ID Res. + Serving Network Entity->>HLR: Update Location Request + HLR->>Previous Network Entity: Cancel Location Req. + Previous Network Entity-->>HLR: Cancel Location Res. Note 1 + HLR->>Serving Network Entity: Insert Subscriber Data Req. + Serving Network Entity-->>HLR: Insert Subscriber Data Res. Note 2 + HLR->>Serving Network Entity: Update Location Res. + Serving Network Entity->>MS: Location update confirm + +``` + +Sequence diagram showing information flow for an inter-node location update. Lifelines: MS, RNC, Serving Network Entity, Previous Network Entity, HLR. The process starts with a Location Update Request from MS to Serving Network Entity. The Serving Network Entity sends a Send ID Req. to Previous Network Entity, which responds with Send ID Res. Next, the Serving Network Entity sends an Update Location Request to HLR. The HLR sends a Cancel Location Req. to Previous Network Entity, which responds with Cancel Location Res. (Note 1). Then, the HLR sends an Insert Subscriber Data Req. to Serving Network Entity, which responds with Insert Subscriber Data Res. (Note 2). Finally, the HLR sends an Update Location Res. to Serving Network Entity, which then sends a Location update confirm to MS. + +**Figure 2: Information flow for an inter-node location update in a Super-Charged network for the case when the serving network entity has retained subscription data for the requesting mobile station** + +Note 1: If the previous network entity supports the Super-Charger features the HLR shall not cancel the location information at the previous network entity unless the Inform Previous Network Entity is included in the Update Location message, except in the conditions described in section 5.2.3.0. + +Note 2: If the subscription data retained by serving network entity is consistent with the subscription data stored by the HLR, the HLR shall not send subscription data. + +### 4.1.3 PS-domain Location Updating in a network entity that does not have subscription data + +When a Super-Charged network entity receives a request to perform a routeing area update or attach for a subscriber for whom there is no record, the network entity shall initiate the location updating procedures as described in 3GPP TS 23.012. + +The Super-Charged HLR shall determine whether the previous network entity supports the Super-Charger functionality: + +- if the previous network entity does not support the Super-Charger functionality then the HLR shall respond to the location updating request as described in 3GPP TS 23.012; +- if the previous network entity supports the Super-Charger functionality then the HLR shall respond to the location updating request as described in 3GPP TS 23.012 but shall not cancel the location information at the previous network entity. + +![Sequence diagram showing information flow for an inter-node routeing area update or attach in a Super-Charged network. Lifelines: MS, RNC, Serving Network Entity, Previous Network Entity, HLR. The process involves an initial request from MS to Serving Network Entity, identification exchange between Serving Network Entity and Previous Network Entity (Note 1), a PDP context update step (Note 2), a location update request from Serving Network Entity to HLR, a cancel location exchange between HLR and Previous Network Entity (Note 3), subscriber data insertion from HLR to Serving Network Entity, and final accept/complete messages from Serving Network Entity to MS.](07b17a620c75522d53916a11e12d1bff_img.jpg) + +``` + +sequenceDiagram + participant MS + participant RNC + participant Serving Network Entity + participant Previous Network Entity + participant HLR + + MS->>Serving Network Entity: Attach or RA Update request + Note over Serving Network Entity, Previous Network Entity: Note 1 + Serving Network Entity->>Previous Network Entity: Identification Req. + Previous Network Entity-->>Serving Network Entity: Identification Res. + rect rgb(255, 255, 255) + Note over MS, HLR: Update PDP Contexts (Note 2) + end + Serving Network Entity->>HLR: Update Location Req. + Note over Previous Network Entity, HLR: Note 3 + HLR->>Previous Network Entity: Cancel Location + Previous Network Entity-->>HLR: Cancel Location Res. + HLR->>Serving Network Entity: Insert Subscriber Data + Serving Network Entity-->>HLR: Insert Subscriber Data Res. + HLR->>Serving Network Entity: Update Location Res. + Serving Network Entity->>MS: Attach or RA update accept + MS->>Serving Network Entity: Attach or RA update Complete + +``` + +Sequence diagram showing information flow for an inter-node routeing area update or attach in a Super-Charged network. Lifelines: MS, RNC, Serving Network Entity, Previous Network Entity, HLR. The process involves an initial request from MS to Serving Network Entity, identification exchange between Serving Network Entity and Previous Network Entity (Note 1), a PDP context update step (Note 2), a location update request from Serving Network Entity to HLR, a cancel location exchange between HLR and Previous Network Entity (Note 3), subscriber data insertion from HLR to Serving Network Entity, and final accept/complete messages from Serving Network Entity to MS. + +**Figure 3: Information flow for an inter-node routeing area update or attach in a Super-Charged network for the case when the serving network entity does not have subscription data for the requesting mobile station** + +Note 1: This procedure is optionally performed as part of the Attach procedures, see 3GPP TS 23.060. + +Note 2: This procedure is used to update PDP contexts during a routeing area update when there is a one or more PDP Contexts established, see 3GPP TS 23.060. + +Note 3: If the previous network entity supports the Super-Charger features the HLR shall not cancel the location information at the previous network entity unless the Inform Previous Network Entity is included in the Update Location message. + +### 4.1.4 PS-domain Location Updating in a network entity that has retained subscription data + +When a Super-Charged network entity receives a request to perform a routeing area update or attach for a subscriber for whom subscription data has been retained, the network entity shall initiate the location updating procedures as described in 3GPP TS 23.012. + +The Super-Charged HLR shall determine whether the previous network entity supports the Super-Charger functionality: + +- if the previous network entity does not support the Super-Charger functionality then the HLR shall cancel the location information as described in 3GPP TS 23.012; +- if the previous network entity supports the Super-Charger functionality then the HLR shall not cancel the location information. + +The Super-Charged HLR shall determine whether the subscription data retained by the serving network entity is consistent with the subscription data stored in the HLR: + +- if the subscription data is consistent then the HLR shall not send subscription data to the serving network entity as part of the location updating procedures; +- if the subscription data is not consistent then the HLR shall respond to the location updating request as described in 3GPP TS 23.012. + +![Sequence diagram showing information flow for an inter-node routeing area update or attach in a Super-Charged network. Lifelines: MS, RNC, Serving Network Entity, Previous Network Entity, HLR. The process involves Identification Req./Res. (Note 1), Update PDP Contexts (Note 2), Update Location Req., Cancel Location (Note 3), Insert Subscriber Data (Note 4), and final Accept/Complete messages.](b28af4985cdef1e519e3aaf26561dcb3_img.jpg) + +``` + +sequenceDiagram + participant MS + participant RNC + participant SNE as Serving Network Entity + participant PNE as Previous Network Entity + participant HLR + + MS->>SNE: Attach or RA Update request + rect rgb(255, 255, 255) + Note right of SNE: Note 1 + SNE->>PNE: Identification Req. + PNE-->>SNE: Identification Res. + end + Note over MS,HLR: Update PDP Contexts (Note 2) + SNE->>HLR: Update Location Req. + rect rgb(255, 255, 255) + Note right of PNE: Note 3 + HLR->>PNE: Cancel Location + PNE-->>HLR: Cancel Location Res. + end + rect rgb(255, 255, 255) + Note right of SNE: Note 4 + HLR->>SNE: Insert Subscriber Data + SNE-->>HLR: Insert Subscriber Data Res. + end + HLR->>SNE: Update Location Res. + SNE->>MS: Attach or RA update accept + MS->>SNE: Attach or RA update Complete + +``` + +Sequence diagram showing information flow for an inter-node routeing area update or attach in a Super-Charged network. Lifelines: MS, RNC, Serving Network Entity, Previous Network Entity, HLR. The process involves Identification Req./Res. (Note 1), Update PDP Contexts (Note 2), Update Location Req., Cancel Location (Note 3), Insert Subscriber Data (Note 4), and final Accept/Complete messages. + +**Figure 4: Information flow for an inter-node routeing area update or attach in a Super-Charged network for the case when the serving network entity has retained subscription data for the requesting mobile station** + +Note 1: This procedure is optionally performed as part of the Attach procedures, see 3GPP TS 23.060. + +Note 2: This procedure is used to update PDP contexts during a routeing area update when there is a one or more PDP Contexts established, see 3GPP TS 23.060. + +Note 3: If the previous network entity supports the Super-Charger features the HLR shall not cancel the location information at the previous network entity unless the Inform Previous Network Entity is included in the Update Location message. + +Note 4: If the subscription data retained by serving network entity is consistent with the subscription data stored by the HLR, the HLR shall not send subscription data. + +# 5 Functional behaviour + +This clause describes the implementation of Super-Charger feature. This mechanism can reduce the signalling traffic associated with mobility, provided the HLR and serving network entity (i.e. MSC/VLR, SGSN, and UMSC) support the Super-Charger functionality. + +## 5.1 Subscriber Settings + +The Super-Charger feature requires a mechanism using which the HLR can determine whether the subscription data retained by the serving network entity is valid. In this specification this parameter shall be referred to as the age indicator. The format of the age indicator is implementation specific since it shall be defined and used by the HPLMN. The HLR shall store the age indicator and an indication as to whether the previous network entity supported the Super-Charger functionality on a per subscriber basis. + +The serving network entity shall store the age indicator provided by the HLR and an indication as to whether the HLR supports the Super-Charger functionality on a per subscriber basis. + +## 5.2 Data Consistency + +In a Super-Charged Network, subscription data may be retained by a number of network entities. Each Super-Charged network entity provided with subscription data will retain this information when the subscriber roams to a different network entity. + +### 5.2.1 Modification of subscription data + +If the subscription data is changed in the HLR the copy of the data in each of the network entities will become outdated. To ensure data consistency: + +- the HLR shall update the age indicator to reflect the change in the subscription data; +- the subscription data in the serving network entity shall be updated as described in 3GPP TS 23.012. The subscription data provided to the serving network entity shall include the new age indicator. + +### 5.2.2 Location Updating + +The location updating procedures shall be initiated according to 3GPP TS 23.012. + +#### 5.2.2.1 Detailed Procedure in the serving network entity + +If the serving network entity has retained subscription data, it shall provide the age indicator as part of the location updating procedure. + +If the serving entity has retained subscription data and does not receive subscription data as part of a successful location updating procedure, the serving entity shall treat the retained subscription data as valid and indicate successful completion of the location updating procedure towards the mobile station. + +If the serving entity has retained subscription data then subscription data received as part of a successful location updating procedure shall be treated as described in 3GPP TS 23.012. + +The procedure Check\_User\_Error\_In\_Serving\_Network\_Entity is defined for the case when the serving entity has retained subscription data but receives a negative response to the location update procedure. In this case, the serving entity shall not treat the retained subscription data as valid. If the negative response indicates "Unknown Subscriber" or "Roaming Not Allowed" the serving network entity shall delete the retained subscription data. + +##### Procedure Check\_User\_Error\_In\_Serving\_Network\_Entity + +1(1) + +Figure 5: Procedure in a Super-Charged serving network entity to determine whether retained subscription data shall be deleted following the receipt of a negative response to the location updating procedure. + +![Flowchart for Procedure Check_User_Error_In_Serving_Network_Entity](08441fa90c5fd11994626f662ac13f19_img.jpg) + +``` +graph TD; Start([ ]) --> Entity{Super-Charged Serving Network Entity}; Entity -- no --> Join(( )); Entity -- yes --> Retained{Subscription Data Retained?}; Retained -- no --> Join; Retained -- yes --> Unknown{Error: Unknown subscriber?}; Unknown -- yes --> Delete[Delete Subscription Data]; Unknown -- no --> Roaming{Error: Roaming Not Allowed?}; Roaming -- yes --> Delete; Roaming -- no --> End(( )); Delete --> End; +``` + +The flowchart illustrates the procedure for checking user errors in a Super-Charged serving network entity. It begins with a start symbol leading to the 'Super-Charged Serving Network Entity' process. A decision point follows: if 'no', the flow ends at a connector symbol; if 'yes', it proceeds to 'Subscription Data Retained?'. If 'no', it ends at the connector; if 'yes', it proceeds to 'Error: Unknown subscriber?'. If 'yes', it goes to 'Delete Subscription Data'; if 'no', it proceeds to 'Error: Roaming Not Allowed?'. If 'yes', it goes to 'Delete Subscription Data'; if 'no', it ends at the connector. The 'Delete Subscription Data' process leads to the connector. + +Flowchart for Procedure Check\_User\_Error\_In\_Serving\_Network\_Entity + +Figure 5: Procedure Check\_User\_Error\_In\_Serving\_Network\_Entity + +#### 5.2.2.2 Detailed Procedure in the HLR + +The procedure Super\_Charged\_Location\_Updating\_HLR determines when a Super-Charged HLR shall send subscription data to the requesting network entity. + +If the serving network entity indicates support for Super-Charger and includes the age indicator, the HLR shall use the age indicator to determine whether the subscription data retained by the serving network entity is valid i.e. the same as the subscription data stored in the HLR: + +- If the subscription data retained by serving network entity is invalid, then the HLR shall send subscriber data to the requesting entity including an indication of support for the Super-Charger functionality and the age indicator. +- If the subscription data retained by the serving network entity is valid, then the HLR shall not send subscription data to the requesting entity. + +If the serving network entity indicates support for Super-Charger but includes a request for subscription data, the HLR shall send subscriber data to the requesting entity including an indication of support for the Super-Charger functionality and the age indicator. + +If the serving network entity does not indicate support for Super-Charger the HLR shall send subscriber data to the requesting entity. + +##### Procedure Super\_Charged\_Location\_Updating\_HLR + +1(1) + +Figure 6: The procedure Super\_Charged\_Location\_Updating\_HLR determines when a Super-Charged HLR shall send subscription data to the requesting network entity. + +![Flowchart for Procedure Super_Charged_Location_Updating_HLR. It starts with a Super-Charged HLR check, followed by three decision diamonds: 'Serving Network Entity Supports Super-Charger?', 'Send subscriber data?', and 'Subscriber data valid?'. It ends with 'Result:=Pass' or 'Result:=Fail' leading to a connector symbol.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) + +``` + +graph TD + Start([ ]) --> HLR{Super-Charged +HLR} + HLR -- yes --> SNESSC{Serving Network +Entity Supports +Super-Charger?} + HLR -- no --> Fail[Result:=Fail] + SNESSC -- yes --> SSD{Send subscriber +data?} + SNESSC -- no --> Fail + SSD -- no --> SDV{Subscriber data +valid?} + SSD -- yes --> Fail + SDV -- yes --> Pass[Result:=Pass] + SDV -- no --> Fail + Pass --> End((X)) + Fail --> End + +``` + +Flowchart for Procedure Super\_Charged\_Location\_Updating\_HLR. It starts with a Super-Charged HLR check, followed by three decision diamonds: 'Serving Network Entity Supports Super-Charger?', 'Send subscriber data?', and 'Subscriber data valid?'. It ends with 'Result:=Pass' or 'Result:=Fail' leading to a connector symbol. + +**Figure 6: Procedure Super\_Charger\_Location\_Updating\_HLR** + +### 5.2.3 Cancel Location + +#### 5.2.3.0 General + +The cancel location procedures are normally not used within and between Super-Charged networks as part of the location update procedure, as described 3GPP TS 23.012. However, Super-Charged networks shall support the cancel location procedure to provide interworking for location update procedures with GSM & UMTS networks that do not support the Super-Charger functionality. The cancel location procedure shall also be used within a Super-Charged network as a notification when there is a need to inform the previous network entity that the connections for the subscriber can be released, due to the fact that the MS has moved to another network entity. Subscription data should still be kept in the previous network entities that support Super-Charger. + +The mechanisms used to determine which network entities the cancel location message shall be sent to are outside the scope of this specification. However, it is recommended that the HLR store an indication if the serving network entity supports the Super-Charger functionality. It is also recommended that an HLR supporting the Super-Charger functionality have mechanisms to decide when a notification as described above needs to be sent against previous network entity or not. Without such mechanisms, Cancel Location shall always be sent. The mechanisms are triggered by the indication received from serving network entity during location update procedure saying that previous network entity must be notified. These mechanisms are triggered when there is a risk data inconsistency between nodes in the network, and are detailed in 3GPP TS 23.912. + +An HLR supporting the mobile terminating roaming forwarding feature (see 3GPP TS 23.018 [10]) shall always send a MAP Cancel Location message to the old VLR upon receipt of the MAP Update Location from the new VLR. This shall also apply if the HLR and the old VLR support Super-Charger, regardless of whether the new VLR indicates or not during the location update procedure that the previous network entity must be notified. + +An HLR supporting the mobile terminating roaming retry feature (see 3GPP TS 23.018 [10]) shall always send a MAP Cancel Location message to the old VLR upon receipt of the MAP Update Location from the new VLR. This shall also apply if the HLR and the old VLR support Super-Charger, regardless of whether the new VLR indicates or not during the location update procedure that the previous network entity must be notified. + +#### 5.2.3.1 Detailed procedures in the serving network entity + +A Super-Charged serving network entity shall be capable of receiving a cancel location message as described in 3GPP TS 23.012. + +#### 5.2.3.2 Detailed procedures in the HLR + +The procedure Super\_Charged\_Cancel\_Location\_HLR determines to whether a Super-Charged HLR shall send the cancel location message to the previous network entity during location updating as described in 3GPP TS 23.012. + +If the previous network entity does support the Super-Charger functionality, the HLR shall not send the cancel location message during location updating except in the conditions described in section 5.2.3.0. This is indicated by the "Result:= Pass" exit in Figure 7. + +![Flowchart for Procedure Super_Charged_Cancel_Location_HLR](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +**Procedure Super\_Charged\_Cancel\_Location\_HLR** 1(1) + +Figure 7: The procedure Super\_Charged\_Cancel\_Location\_HLR determines whether a Super-Charged HLR shall send the cancel location message to the previous network entity during location updating. + +``` +graph TD; Start([ ]) --> HLR_Super{Super-Charged HLR}; HLR_Super -- yes --> HLR_Supports_MT{HLR supports MT Roaming Forwarding ?}; HLR_Supports_MT -- yes --> Fail[Result:= Fail]; HLR_Supports_MT -- no --> HLR_Supports_MT_Retry{HLR supports MT Roaming Retry ?}; HLR_Supports_MT_Retry -- yes --> Fail; HLR_Supports_MT_Retry -- no --> Inform{Inform Previous Network Entity?}; Inform -- yes --> Fail; Inform -- no --> Previous_Supports{Previous Network Entity Supports Super-Charger?}; Previous_Supports -- no --> Fail; Previous_Supports -- yes --> Pass[Result:= Pass]; Pass --> End(( )); Fail --> End; +``` + +The flowchart illustrates the procedure for a Super-Charged HLR to determine whether to send a cancel location message. It begins with an oval connector, leading to a decision diamond 'Super-Charged HLR'. If 'yes', it proceeds to 'HLR supports MT Roaming Forwarding ?'. If 'yes', it goes to 'Result:= Fail'; if 'no', it proceeds to 'HLR supports MT Roaming Retry ?'. If 'yes', it goes to 'Result:= Fail'; if 'no', it proceeds to 'Inform Previous Network Entity?'. If 'yes', it goes to 'Result:= Fail'; if 'no', it proceeds to 'Previous Network Entity Supports Super-Charger?'. If 'no', it goes to 'Result:= Fail'; if 'yes', it proceeds to 'Result:= Pass'. Both 'Result:= Pass' and 'Result:= Fail' lead to a circular connector with an 'X'. + +Flowchart for Procedure Super\_Charged\_Cancel\_Location\_HLR + +**Figure 7: Procedure Super\_Charged\_Cancel\_Location\_HLR** + +### 5.2.4 Purge MS + +In a Super-Charged network, the subscriber record for an MS may be deleted by database management procedure to free up capacity in the network entity to accept new subscribers as described in subclause 5.5. + +The procedure Purge\_MS\_in\_Serving\_Network\_Entity determines whether a Super-Charged Serving Network Entity shall send the purge MS message to the HLR when deleting inactive subscription data. + +If the HLR does not support the Super-Charger functionality, the deletion of inactive subscription data shall initiate the purge MS procedure as described in 3GPP TS 23.012. This is indicated by the "Result:= Fail" exit in Figure 8. + +For the CS-domain, the restoration procedures for Super-Charged network entities shall be modified to minimize the number of unnecessary mobile terminated call and short message attempts. + +For the PS-domain, any attempt to establish a network-requested PDP context to a network entity that has no record for the subscriber shall proceed as described in 3GPP TS 23.060. + +In addition, the Mobile Terminating Short Message Service is modified to minimize the number of unnecessary mobile terminated calls and short message attempts. + +#### Procedure Purge\_MS\_In\_Serving\_Network\_Entity + +1(1) + +Figure 8: The procedure Purge\_MS\_in\_Serving\_Network\_Entity determines whether a Super-Charged Serving Network Entity shall send the purge MS message to the HLR when deleting inactive subscription data. + +![Flowchart for Procedure Purge_MS_In_Serving_Network_Entity](43837b056625d3d6ce615e4c02f163bb_img.jpg) + +``` +graph TD; Start([ ]) --> SC[Super-Charged Serving Network Entity]; SC -- yes --> HLR{HLR supports Super-Charger?}; SC -- no --> End(( )); HLR -- yes --> Pass[Result:= Pass]; HLR -- no --> Fail[Result:= Fail]; Pass --> End; Fail --> End; +``` + +The flowchart illustrates the procedure for purging MS in a serving network entity. It begins with a start symbol (oval) leading to a process block labeled 'Super-Charged Serving Network Entity'. From this block, a 'yes' path leads to a decision diamond 'HLR supports Super-Charger?'. A 'no' path from the 'Super-Charged Serving Network Entity' block leads directly to an end symbol (circle with an X). From the decision diamond, a 'yes' path leads to a process block 'Result:= Pass', and a 'no' path leads to a process block 'Result:= Fail'. Both 'Result:= Pass' and 'Result:= Fail' blocks lead to the same end symbol (circle with an X). + +Flowchart for Procedure Purge\_MS\_In\_Serving\_Network\_Entity + +Figure 8: Procedure Purge\_MS\_In\_Serving\_Network\_Entity + +#### 5.2.4.1 CS-domain restoration procedures + +Upon receipt of a request for a roaming number, if there is no subscriber data record in the recipient network entity the network entity shall distinguish two cases: + +- the subscriber data record was lost due to network entity restart; +- the subscriber data record was removed by the Super-Charger database management function described in subclause 5.5. + +If the subscriber data record was lost due to a network entity restart the restoration procedure as described in 3GPP TS 29.002 shall be initiated. + +The procedure Check\_Reason\_In\_Serving\_Network\_Entity determines whether the subscriber data was removed by the Super-Charger database management function and whether the network entity shall return the Purged MS diagnostic information to the HLR. + +The procedure Super\_Charged\_SRI\_Error\_HLR determines whether the HLR shall mark its data for the MS as purged and maps the Purged\_MS diagnostic information to indicate that the IMSI is detached, in the send routeing information response. Consequently any request for routeing information for a mobile terminated call or a mobile terminated short message shall be treated as if the MS is not reachable. + +The means by which the network entity distinguishes the two cases is implementation dependent and therefore outside the scope of this specification. + +##### Procedure Check\_Reason\_In\_Serving\_Network\_Entity + +1(1) + +Figure 9: The procedure Check\_Reason\_In\_Serving\_Network\_Entity determines whether the subscriber data was removed by the Super-Charger database management function and sets the Purged MS diagnostic information, if required. + +![Flowchart for Procedure Check_Reason_In_Serving_Network_Entity](a734898ce18e972938949637c32a34f4_img.jpg) + +``` +graph TD; Start([ ]) --> Entity{Super-Charged Serving Network Entity}; Entity -- yes --> Decision{IMSI Purged by Super-Charger?}; Entity -- no --> NotPurged[Result:= Not Purged]; Decision -- yes --> NegativeResponse[Set negative response: Purged MS]; NegativeResponse --> Purged[Result:= Purged]; Decision -- no --> NotPurged; Purged --> End((X)); NotPurged --> End; +``` + +The flowchart illustrates the procedure Check\_Reason\_In\_Serving\_Network\_Entity. It begins with a start symbol (oval with vertical line), leading to a process block labeled 'Super-Charged Serving Network Entity'. From this block, a 'yes' path leads to a decision diamond 'IMSI Purged by Super-Charger?'. A 'no' path from the 'Super-Charged Serving Network Entity' block leads to a process block 'Result:= Not Purged'. From the decision diamond, a 'yes' path leads to a process block 'Set negative response: Purged MS', which then leads to a process block 'Result:= Purged'. A 'no' path from the decision diamond leads to the 'Result:= Not Purged' block. Both 'Result:= Purged' and 'Result:= Not Purged' blocks lead to a common exit symbol (circle with X). + +Flowchart for Procedure Check\_Reason\_In\_Serving\_Network\_Entity + +Figure 9: Procedure Check\_Reason\_In\_Serving\_Network\_Entity + +##### Procedure Super\_Charged\_SRI\_Error\_HLR + +1(1) + +Figure 10: The procedure Super\_Charged\_SRI\_Error\_HLR determines whether the HLR shall mark its data for the MS as purged and maps the Purged\_MS diagnostic information to indicate that the IMSI is detached, in the send routing information response. + +![Flowchart for Procedure Super_Charged_SRI_Error_HLR](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +``` +graph TD; Start([ ]) --> Decision1{Super-Charged HLR}; Decision1 -- no --> End(( )); Decision1 -- yes --> Decision2{Absent Subscriber Error: Purged MS?}; Decision2 -- no --> End; Decision2 -- yes --> Process1[Set MS Purged Flag]; Process1 --> Process2[ ]; Process2 --> End; Process2 --> Note[Set negative response Absent Subscriber: IMSI Detach]; Note --> Process2; Process2 --> Process3[Result:= Purged]; Process3 --> End; Process3 --> Process4[Result:= Not Purged]; Process4 --> End; +``` + +The flowchart illustrates the procedure Super\_Charged\_SRI\_Error\_HLR. It begins with an oval connector symbol, leading to a decision diamond labeled 'Super-Charged HLR'. If the answer is 'no', the flow proceeds directly to a circle connector symbol at the bottom. If the answer is 'yes', it proceeds to another decision diamond labeled 'Absent Subscriber Error: Purged MS?'. If this second decision is 'no', the flow proceeds to the circle connector symbol. If the answer is 'yes', it proceeds to a rectangular process block labeled 'Set MS Purged Flag'. This is followed by an empty rectangular process block. From this empty block, the flow proceeds to the circle connector symbol, and also to a note box labeled 'Set negative response Absent Subscriber: IMSI Detach', which loops back to the empty process block. The empty process block then leads to a rectangular process block labeled 'Result:= Purged'. This block leads to the circle connector symbol and also to another rectangular process block labeled 'Result:= Not Purged', which finally leads to the circle connector symbol. + +Flowchart for Procedure Super\_Charged\_SRI\_Error\_HLR + +Figure 10: Procedure Super\_Charged\_SRI\_Error\_HLR + +#### 5.2.4.2 Mobile Terminating Short Message Service + +The procedure Check\_Absent\_SubscriberSM\_In\_HLR determines whether the HLR shall mark its data for the MS as purged based on the content of the absent subscriber SM diagnostic information (See 3GPP TS 23.040), if received from the SMS-GMSC, following a Mobile Terminating Short Message delivery attempt. + +##### Procedure Check\_Absent\_SubscriberSM\_In\_HLR + +1(1) + +Figure 11: The procedure Check\_Absent\_SubscriberSM\_In\_HLR determines whether the HLR shall mark its data for the MS as purged and based on the outcome of a MT-SMS delivery attempt. + +![Flowchart for Procedure Check_Absent_SubscriberSM_In_HLR](75e4b78ee25f885d73120e3066a5253e_img.jpg) + +``` +graph TD; Start([ ]) --> HLR{Super-Charged HLR}; HLR -- yes --> Decision{Absent Subscriber SM Error Purged MS?}; HLR -- no --> End(( )); Decision -- yes --> Process[Set MS Purged Flag]; Decision -- no --> End; Process --> End; +``` + +The flowchart illustrates the procedure 'Check\_Absent\_SubscriberSM\_In\_HLR'. It begins with a start symbol (oval with a vertical line), leading to a decision diamond labeled 'Super-Charged HLR'. If the answer is 'yes', it proceeds to another decision diamond labeled 'Absent Subscriber SM Error Purged MS?'. If the answer to this second decision is 'yes', it proceeds to a process box labeled 'Set MS Purged Flag'. If the answer to either decision is 'no', it proceeds directly to the end symbol (circle with an 'X'). + +Flowchart for Procedure Check\_Absent\_SubscriberSM\_In\_HLR + +Figure 11: Procedure Check\_Absent\_SubscriberSM\_In\_HLR + +## 5.3 Subscriber Deactivation + +When a subscriber is deactivated, the cancel location message is sent to the serving network entity and the subscription data shall be deleted in the HLR. + +Subsequently, when the subscriber attempts to register in a network entity that has data for the subscriber, the HLR will return an error of 'Unknown Subscriber' and the subscription data in the network entity shall be deleted as described in subclause 5.2.2.1. + +## 5.4 TMSI Management + +In a Super-Charged network, if the cancel location or purge MS procedures are not performed the TMSI and P-TMSI values shall be de-allocated by another mechanism to avoid double allocation of temporary identifiers. + +If the send identification procedure as described in 3GPP TS 29.002 is used, the previous network entity may use this to explicitly de-allocate the temporary identifier assigned to that subscriber. + +In the event that the send identification procedure is not perform or not used as an explicit de-allocation trigger, it is recommended that an alternative mechanism is available to de-allocate temporary identifiers. The chosen mechanism is an implementation detail. De-allocation of TMSI and P-TMSI values may be achieved by a system of supervision timers or as part of the database management function, see subclause 5.5. However, other mechanisms may be used to avoid double allocation. + +## 5.5 Database Management + +In a Super-Charged network subscription data shall not be deleted in the previous network entity. The subscription data shall be retained using spare capacity available in the network entity. This results in a continuous growth of the database size. If not managed properly, the network entity will eventually become full and unable to handle newly arrived MSs. A strategy to manage the capacity of Super-Charged network entities is required. + +The database management scheme shall be an implementation option and so outside the scope of this specification. Example mechanisms are: + +- Utilisation of a larger database. +- Periodic audit scheme. +- Implementation of a strategy to make room for new users by removing old subscriber information from the associated database. + +### 5.5.1 Utilisation of a larger database + +The implementation of larger databases may be used to limit the need for other mechanisms to ensure that sufficient database capacity is available to service new subscribers. However, the need for an alternative mechanism such as Periodic Audits and Dynamic Subscription Data Deletion is not removed. + +Implementing larger databases such that subscription data is retained for an increased number of subscribers can increase the benefit from a Super-Charged network. However, the optimal database capacity will be network specific. + +The implementation of a larger database is not a requirement for this feature. + +### 5.5.2 Periodic Audit + +This scheme periodical removes inactive subscription data from the VLR and SGSN databases. The volume of subscription data deleted should be based on an estimation of the growth of the database size during the audit cycle. + +The criterion for removal of the subscriber is outside the scope of this specification. Circuit Switched and Packet Service activity of the subscriber should be checked before any deletion. + +### 5.5.3 Dynamic Subscription Data Deletion + +This scheme allows the run-time removal of subscription if the associated database is full. In this case, the oldest subscription data is deleted to make room for the newly arrived subscriber. This mechanism may be used in conjunction with the other scheme detailed above or as the only method by which to create available capacity within a database. + +The criterion for removal of the subscriber is outside the scope of this specification. Circuit Switched and Packet Service activity of the subscriber should be checked before any deletion. + +## 5.6 Enhanced User Identity Confidentiality + +If an MS configured to support Enhanced User Identity Confidentiality updates location at a serving network entity which has retained subscriber data from a previous visit, the normal procedure of Enhanced User Identity Confidentiality as defined in 3GPP TS 23.018 shall apply. + +The serving network entity shall replace the TEMSI stored in the subscriber data by the TEMSI received from the UIDN as a result of the Send IMSI operation. + +## 5.7 Exception procedure + +A Super-Charged network entity shall inform the HLR about the support of the Super-Charger functionality whenever a subscriber roams on to that network entity. This information shall be included in the update location message sent to the HLR. The HLR shall use this information to determine the most appropriate action. + +If the HLR does not support the Super-Charger functionality the HLR shall ignore this information and proceed according to 3GPP TS 29.002. + +If the serving network entity does not support the Super-Charger functionality the serving network entity shall ignore information relating to the Super-Charger feature and proceed according to 3GPP TS 29.002. + +# 6 Contents of the messages + +This clause contains detailed description of the messages shown in Section 5 of the specification. + +## 6.1 Update Location + +The contents of this message are specified in 3GPP TS 29.002. In the case when the originating entity supports the Super-Charger functionality, the following Super-Charger specific information is defined: + +| Information element name | Required | Description | +|---------------------------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Super-Charger Supported In Serving Network Entity | C | When included, this parameter indicates that the originating entity supports the Super-Charger functionality. In addition, this parameter shall indicate either that subscription data is required or the date and time of the last known subscriber data modification. | +| Inform Previous Network Entity | C | When included, this parameter indicates that the previous network entity needs to be informed about the update location.
The parameter shall be included if:
  • - Send Identification has not been sent to the previous network entity or
  • - the MTRF Supported flag is included in the Update Location message.
| + +## 6.2 Update Location ack + +The contents of this message are specified in 3GPP TS 29.002. + +## 6.3 Update GPRS Location + +The contents of this message are specified in 3GPP TS 29.002. In the case when the originating entity supports the Super-Charger functionality, the following Super-Charger specific information is defined: + +| Information element name | Required | Description | +|---------------------------------------------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Super-Charger Supported In Serving Network Entity | C | When included, this parameter indicates that the originating entity supports the Super-Charger functionality. In addition, this parameter shall indicate either that subscription data is required or the date and time of the last known subscriber data modification. | +| Inform Previous Network Entity | C | When included, this parameter indicates that the previous network entity needs to be informed about the update location.
The parameter shall be included only if SGSN Context Request has not been sent to the previous network entity. | + +## 6.4 Update GPRS Location ack + +The contents of this message are specified in 3GPP TS 29.002. + +## 6.5 Insert Subscriber Data + +The contents of this message are specified in 3GPP TS 29.002. In the case when the originating entity supports the Super-Charger functionality, the following Super-Charger specific information is defined: + +| Information element name | Required | Description | +|--------------------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Super-Charger Supported In HLR | C | When included, this parameter indicates that the originating entity supports the Super-Charger functionality. In addition, this parameter is used by the HLR to indicate the age of the subscription data stored in the HLR. | + +## 6.6 Insert Subscriber Data ack + +The contents of this message are specified in 3GPP TS 29.002. + +# Annex A (informative): Change History + +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|-----------|--------|-----------|------|-----|-------------------------------------------------------------------------------|--------| +| Mar 2000 | CN#07 | | | | Approved by TSG CN#07 | 3.0.0 | +| Mar 2001 | CN#11 | | | | Release 4 after CN#11 | 4.0.0 | +| Jun 2001 | CN#12 | NP-010299 | 002 | 3 | Essential drawbacks on services due to introduction of Super-Charger function | 4.1.0 | +| Dec. 2001 | CN#14 | NP-010617 | 004 | 1 | Clarification of methodology for maintaining data consistency in Supercharger | 4.2.0 | +| Jun 2002 | CN#16 | | | | Release 5 after CN#16 | 5.0.0 | +| Dec 2004 | CN#26 | | | | Release 6 after CN#26 | 6.0.0 | +| Jun 2006 | CT#32 | CP-060312 | 0014 | 1 | Correction for Usage of Cancel Location for Supercharger | 7.0.0 | +| Dec 2008 | CT#42 | | | | Upgraded unchanged from Rel-7 | 8.0.0 | +| 2009-12 | - | - | - | - | Update to Rel-9 version (MCC) | 9.0.0 | +| 2011-03 | CT#51 | CP-110068 | 0015 | 1 | MT Roaming Retry and Super Charger | 10.0.0 | +| 2011-03 | CT#51 | CP-110068 | 0016 | 1 | Mobile Terminating Roaming Forwarding | 10.0.0 | +| 2011-09 | CT#53 | CP-110575 | 0017 | 2 | MTRF and Super Charger interactions | 10.1.0 | +| 2012-09 | CT#57 | | | | Update to Rel-11 version (MCC) | 11.0.0 | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 12.0.0 | +| 2015-12 | CT#70 | | | | Update to Rel-13 version (MCC) | 13.0.0 | +| 2017-03 | CT#75 | - | - | - | Update to Rel-14 version (MCC) | 14.0.0 | +| 2018-06 | CT#80 | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-07 | CT#88e | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23119/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/23_series/23119/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..638cd8e2eea4037bb0c5ba62e38097ee2b6d78fd --- /dev/null +++ b/marked/Rel-16/23_series/23119/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6faf2c149df3bcd2760fa7b14abe501aa4bca04edbd03d78edb6b9c761dc8f7d +size 124269 diff --git a/marked/Rel-16/23_series/23119/036ceaf207a7b289ca76e160892eb724_img.jpg b/marked/Rel-16/23_series/23119/036ceaf207a7b289ca76e160892eb724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..779ffe0b0aab0fed895e9b5f700f1aaaae26792f --- /dev/null +++ b/marked/Rel-16/23_series/23119/036ceaf207a7b289ca76e160892eb724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e103c6a094798fda8111a2eacbbe261e7deb4791e8ee73ffa46213c7bc752c7 +size 111109 diff --git a/marked/Rel-16/23_series/23119/0856d34939157228ac3a54a59882fb10_img.jpg b/marked/Rel-16/23_series/23119/0856d34939157228ac3a54a59882fb10_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91bd18281de5ec07b4f3f46668d80c3ec03671ff --- /dev/null +++ b/marked/Rel-16/23_series/23119/0856d34939157228ac3a54a59882fb10_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8bcdc6bab9b0709b2ee09e7cd6395b12c5612433ee8c5a7822262ecf416fca3 +size 24706 diff --git a/marked/Rel-16/23_series/23119/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-16/23_series/23119/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c3d32ea27d6be84c75de991cf194f0cb3aa2d0e --- /dev/null +++ b/marked/Rel-16/23_series/23119/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a8818e7e524b29b1354e8b8fb3ad02705488037dfa13b4efe417c99057e880e +size 108591 diff --git a/marked/Rel-16/23_series/23119/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-16/23_series/23119/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15a85211e99e8967ee803882b04b97ada8d7907e --- /dev/null +++ b/marked/Rel-16/23_series/23119/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:942f9e1037e28c96750c31dd10bad9c87ab45b3df23f185afd5b970999a07355 +size 77675 diff --git a/marked/Rel-16/23_series/23119/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-16/23_series/23119/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3475c9429e2f6816bdde16afea48044ceba6f002 --- /dev/null +++ b/marked/Rel-16/23_series/23119/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d32d2886a764a1fcfa912eec9e5183f9e541864afec20bd5e6dddd902a32911 +size 141244 diff --git a/marked/Rel-16/23_series/23119/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/marked/Rel-16/23_series/23119/0c80c383f76034e117adf5e5eaadaaf3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d1b8d5b61a79968865f1128251f3512f184f14c --- /dev/null +++ b/marked/Rel-16/23_series/23119/0c80c383f76034e117adf5e5eaadaaf3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b1f628d56f1e92a53ab1577af77768fc1525c58973c5a7c1c78a6e9196916f5 +size 108108 diff --git a/marked/Rel-16/23_series/23119/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-16/23_series/23119/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..94e447079aedd2905ccb124a8e4e6c6ae29404f6 --- /dev/null +++ b/marked/Rel-16/23_series/23119/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3800f6860748436a0d1de646493e55ce8527750c1d616ae38e0e8287cc1f797f +size 63590 diff --git a/marked/Rel-16/23_series/23119/0ee9d674085524d589646a6c3fb21ec3_img.jpg b/marked/Rel-16/23_series/23119/0ee9d674085524d589646a6c3fb21ec3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c65be9a35ebc374bcec17d061b6cbaafa46e74bc --- /dev/null +++ b/marked/Rel-16/23_series/23119/0ee9d674085524d589646a6c3fb21ec3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f46105eb1b160b682c0126d9a0a8518bd8707e7f69cb905fd6ed7505c460520 +size 38462 diff --git a/marked/Rel-16/23_series/23119/0f26e70157bd4c45f825795cdcd20fbd_img.jpg b/marked/Rel-16/23_series/23119/0f26e70157bd4c45f825795cdcd20fbd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee01c5615cb0a76312ebe232cd9a9a61233403e4 --- /dev/null +++ b/marked/Rel-16/23_series/23119/0f26e70157bd4c45f825795cdcd20fbd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74e58f8bef1a45b111e5189cc54de31e7474db9e90383920a0634deda981408f +size 106493 diff --git a/marked/Rel-16/23_series/23119/1033dc9fde75540d224c907681b1b7aa_img.jpg b/marked/Rel-16/23_series/23119/1033dc9fde75540d224c907681b1b7aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..406c5e59be795ec085ff775dc0bcbeea374a0c06 --- /dev/null +++ b/marked/Rel-16/23_series/23119/1033dc9fde75540d224c907681b1b7aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3dd24a6400e0551d802fc4ca4cad05def6b36a67b2039a83f5cb3deaceed3365 +size 126353 diff --git a/marked/Rel-16/23_series/23119/10737843d428d439ee47ad580036c875_img.jpg b/marked/Rel-16/23_series/23119/10737843d428d439ee47ad580036c875_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8fd18f0fcf3d60236c4bd887285c38286fb5359 --- /dev/null +++ b/marked/Rel-16/23_series/23119/10737843d428d439ee47ad580036c875_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:969000bddfedc679f9a06e95de9b511379a0ec5db81f4cfd42a7e408d604b998 +size 54259 diff --git a/marked/Rel-16/23_series/23119/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-16/23_series/23119/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d3a06a3a60820b55760d11667d017e73bdad3d7 --- /dev/null +++ b/marked/Rel-16/23_series/23119/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:040b8a7dbf3f10a209be239587f3c7c5bb575f9d02d2db7e71fc923b301038e3 +size 29148 diff --git a/marked/Rel-16/23_series/23119/1399c76ef88f22b70d05ed3f781d3c48_img.jpg b/marked/Rel-16/23_series/23119/1399c76ef88f22b70d05ed3f781d3c48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9ccd219cb73fa613eca8400aec97445932cf1c5 --- /dev/null +++ b/marked/Rel-16/23_series/23119/1399c76ef88f22b70d05ed3f781d3c48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3007d0cfe471dd85a2a3b016054ad7c6348986b1e63c4ca6e7ca83e10c0f5084 +size 118961 diff --git a/marked/Rel-16/23_series/23119/17f0cf80b9c38adb460d4ca836960da7_img.jpg b/marked/Rel-16/23_series/23119/17f0cf80b9c38adb460d4ca836960da7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c6514bae73b063e7250024e6714fa848d42b32a --- /dev/null +++ b/marked/Rel-16/23_series/23119/17f0cf80b9c38adb460d4ca836960da7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12343ebbda1a6db5dea743a5e55384b8d6b789e081841083f71b1a19f60bb167 +size 120190 diff --git a/marked/Rel-16/23_series/23119/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/Rel-16/23_series/23119/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..149340eff12b63b4474f7b5983663edc562ebd0b --- /dev/null +++ b/marked/Rel-16/23_series/23119/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a24cc18fa8ed752122a68c6a47e25fec23e4bca3e989845e135399959ff12ea +size 73223 diff --git a/marked/Rel-16/23_series/23119/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/23_series/23119/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d5e89cea33217e8135f1cf9cd5decf4f1da45b5 --- /dev/null +++ b/marked/Rel-16/23_series/23119/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:274ceb6b04b62798900d6698aa456e977f7ecbd88e1a3dd436d1dca04e028f31 +size 147804 diff --git a/marked/Rel-16/23_series/23119/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/marked/Rel-16/23_series/23119/18bb06865e2dada3656ea3d57f290f7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1f6967899d05a2502a5e6756604969733d46de6 --- /dev/null +++ b/marked/Rel-16/23_series/23119/18bb06865e2dada3656ea3d57f290f7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3f12bc1307e3445724f1d75b82c606eab4f12a5b669bab72ec0e3ae38f3a3cf +size 93100 diff --git a/marked/Rel-16/23_series/23119/1e8c50ad4fca7f315a407347dd5091cc_img.jpg b/marked/Rel-16/23_series/23119/1e8c50ad4fca7f315a407347dd5091cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ecced16e80b717778be2234e3bb0b5a9c022ecf --- /dev/null +++ b/marked/Rel-16/23_series/23119/1e8c50ad4fca7f315a407347dd5091cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f976c214a3d752955805e69c3097ce9651381ae833e055ff05d8e1915d50567 +size 100867 diff --git a/marked/Rel-16/23_series/23119/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/Rel-16/23_series/23119/1eadbbe42cfcac5c0023577110aec5e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c12f1732c2adda9164a287387129a5e13769e172 --- /dev/null +++ b/marked/Rel-16/23_series/23119/1eadbbe42cfcac5c0023577110aec5e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:457b718906e7e391deb7c8803932f55490b5778402d27630b543a586c9413b57 +size 62746 diff --git a/marked/Rel-16/23_series/23119/236f674770a03c918c0375a74fe950db_img.jpg b/marked/Rel-16/23_series/23119/236f674770a03c918c0375a74fe950db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75add0618fa235f9a622a45d2760c905754466e7 --- /dev/null +++ b/marked/Rel-16/23_series/23119/236f674770a03c918c0375a74fe950db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fb5d09ed4055aa67ff83d8aa6fc56a5bf3f6df3e609d8626a7378b7e15ec623 +size 25754 diff --git a/marked/Rel-16/23_series/23119/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg b/marked/Rel-16/23_series/23119/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f57fadd8c676edf74183ec7bc8c1c76abd11f951 --- /dev/null +++ b/marked/Rel-16/23_series/23119/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a777cbe8909c53a7fb6c66ed1a5498978e1af81bcd2d859790f594f70b64ad0 +size 28615 diff --git a/marked/Rel-16/23_series/23119/28085f681b9fff76a53c5b8b32338ee1_img.jpg b/marked/Rel-16/23_series/23119/28085f681b9fff76a53c5b8b32338ee1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ac3eac262305f2e533940db2e97279e3dbed033 --- /dev/null +++ b/marked/Rel-16/23_series/23119/28085f681b9fff76a53c5b8b32338ee1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79691648789a8bca92352efebf641baaf3ebe7310af22af74f2f21f535863751 +size 92000 diff --git a/marked/Rel-16/23_series/23119/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-16/23_series/23119/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..065acdcad34af81b83dde9dc4d72a1d6a5c90a66 --- /dev/null +++ b/marked/Rel-16/23_series/23119/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dfa602de67a68a4a7a7ddaecdd4f844cc6b27865150f1588aca708124b028d3e +size 114223 diff --git a/marked/Rel-16/23_series/23119/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/23_series/23119/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e6229f8b35f1d5b5c5f9240ce1f2f5ae827a09f --- /dev/null +++ b/marked/Rel-16/23_series/23119/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:83ab2c7515a882c3cb8895e225394419571ba51c5236b5ccea53098695b49763 +size 110780 diff --git a/marked/Rel-16/23_series/23119/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/23_series/23119/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a346cc25ecfeeab51eb9cc8d8c7503555b25e07d --- /dev/null +++ b/marked/Rel-16/23_series/23119/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf97c290e84af495107cd0b5cdd03173d7d5055a4aa4c850830de878b09806aa +size 143024 diff --git a/marked/Rel-16/23_series/23119/34d7353cac3d344f71ad82bd1eda40d1_img.jpg b/marked/Rel-16/23_series/23119/34d7353cac3d344f71ad82bd1eda40d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..127331d22aa1998ce25354858f05fa4e186960cc --- /dev/null +++ b/marked/Rel-16/23_series/23119/34d7353cac3d344f71ad82bd1eda40d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc7920e0654e6f1f09ba9634d92c826a2c963008563eb424662d1db1fdacd330 +size 17291 diff --git a/marked/Rel-16/23_series/23119/372876d8c5ee065bc744b175be0a6c1f_img.jpg b/marked/Rel-16/23_series/23119/372876d8c5ee065bc744b175be0a6c1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f914360ce5dfeed8080f9b7772e429bb5d9e6389 --- /dev/null +++ b/marked/Rel-16/23_series/23119/372876d8c5ee065bc744b175be0a6c1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6f36c8b02c94195f18bc50add5c52c34ef8c4f496f4682d5ac48da225b42499 +size 23966 diff --git a/marked/Rel-16/23_series/23119/3b00a61116faef21d3a6009fd350b46a_img.jpg b/marked/Rel-16/23_series/23119/3b00a61116faef21d3a6009fd350b46a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f078fdd6e6d0d56e90ab541d821808109a20d79b --- /dev/null +++ b/marked/Rel-16/23_series/23119/3b00a61116faef21d3a6009fd350b46a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf0c0d923c0e31c10fc427bf3731594a4c58bf897c63e9a33647a08a19ab475b +size 26156 diff --git a/marked/Rel-16/23_series/23119/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg b/marked/Rel-16/23_series/23119/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ced02ed0d05a3ee7d6b1c88a4285d40a518fa7fa --- /dev/null +++ b/marked/Rel-16/23_series/23119/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5996bb95d62233b4f281a4ab68a430f0d97fefd540d455cda4dd456b0b491a4 +size 51852 diff --git a/marked/Rel-16/23_series/23119/3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg b/marked/Rel-16/23_series/23119/3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4ac1afd7b62915ea2b1813e125e9a6007cd7f39 --- /dev/null +++ b/marked/Rel-16/23_series/23119/3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ec44473c4b53267dd6f326607bdd212cf86e9f12799420a5d7bbb8ec25538c0 +size 93239 diff --git a/marked/Rel-16/23_series/23119/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-16/23_series/23119/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e37984fd3689fa4b9b2be3fc45a8f0d369886a12 --- /dev/null +++ b/marked/Rel-16/23_series/23119/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0de0129be1f7801adffe751817219bd072f45cd4d9f398431e8baf6bbe0a273b +size 151903 diff --git a/marked/Rel-16/23_series/23119/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23119/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dfc68646a7bd9d4df1673713e3663aab52d0142a --- /dev/null +++ b/marked/Rel-16/23_series/23119/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41d81413d995df814921ff42a9256c651fbbdde53d46df6960d455c380451761 +size 142743 diff --git a/marked/Rel-16/23_series/23119/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg b/marked/Rel-16/23_series/23119/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77b4c296af264a0220580f1bba297b267f4e8d83 --- /dev/null +++ b/marked/Rel-16/23_series/23119/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9371ac1a1b8257826bc1665021a9356bc2ebe5b648045f840130c4764d62dee3 +size 29826 diff --git a/marked/Rel-16/23_series/23119/4806f9f95fff13a30d6523bd6ffeac63_img.jpg b/marked/Rel-16/23_series/23119/4806f9f95fff13a30d6523bd6ffeac63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff0f9c40cc51e6696d76de933dbc70f39a611b3f --- /dev/null +++ b/marked/Rel-16/23_series/23119/4806f9f95fff13a30d6523bd6ffeac63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a820f742cad1fd4cdf5f36343d9f0564b9f7a8408b731941425af50fe0b3e1f6 +size 151495 diff --git a/marked/Rel-16/23_series/23119/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Rel-16/23_series/23119/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5249fc743bfe9afd9da15d92d0f0973a60529b5f --- /dev/null +++ b/marked/Rel-16/23_series/23119/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62d51bdbc8ef64dc32b7e6d8af5bc82fddfb70415d04d237fe2bccc212c57057 +size 143040 diff --git a/marked/Rel-16/23_series/23119/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-16/23_series/23119/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6258cce3413567222c04c46d735c8110aa1fa38 --- /dev/null +++ b/marked/Rel-16/23_series/23119/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1db24807387936cd1ffcbd5279b7d705f382f98a1270c897b04ebcfebbc9cf5 +size 92673 diff --git a/marked/Rel-16/23_series/23119/56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg b/marked/Rel-16/23_series/23119/56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0481e47d8644ee19f6c981dd7658fe1f53b98809 --- /dev/null +++ b/marked/Rel-16/23_series/23119/56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d3fe09a714275b5e23f05c47585620e285fe3b148ba42ca04f17192b90a3bec +size 61601 diff --git a/marked/Rel-16/23_series/23119/57134800ac3a97b6212b27b93aa196ac_img.jpg b/marked/Rel-16/23_series/23119/57134800ac3a97b6212b27b93aa196ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..670b3987ed557dcaacb149e91ef85e58912a2f9b --- /dev/null +++ b/marked/Rel-16/23_series/23119/57134800ac3a97b6212b27b93aa196ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b415fef79de073fabd7c8478025e18994bb8ac24a08b0c8b4d910657c3c09ae +size 76643 diff --git a/marked/Rel-16/23_series/23119/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/Rel-16/23_series/23119/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5913499c65f24520cb09382c20ca2d1190128360 --- /dev/null +++ b/marked/Rel-16/23_series/23119/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b78819c59bc8745665a633ff4e4cc27ad1da64d95c1ec46371d75b088a89004c +size 127909 diff --git a/marked/Rel-16/23_series/23119/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg b/marked/Rel-16/23_series/23119/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb5f72912b3c04e3e95cd86f6e3c832e8e9c43c7 --- /dev/null +++ b/marked/Rel-16/23_series/23119/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:629c7afad90092874fbc2dedb96e75b38cc4155a77f0e2c98d2e700ba48e6e53 +size 22887 diff --git a/marked/Rel-16/23_series/23119/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-16/23_series/23119/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..955895f6b59210c33bd10d3f6b81f1a946f6bb40 --- /dev/null +++ b/marked/Rel-16/23_series/23119/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eba83c8f24b3f59c176a3c0ad246ef8e5b8004360c5b6dae73d1e8ccd0d7e95f +size 127968 diff --git a/marked/Rel-16/23_series/23119/64bec4cd45e47e1976245711f702aca2_img.jpg b/marked/Rel-16/23_series/23119/64bec4cd45e47e1976245711f702aca2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed1aae646651c18f62f4e5baa4ecddcc9d055b31 --- /dev/null +++ b/marked/Rel-16/23_series/23119/64bec4cd45e47e1976245711f702aca2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bd0dc2228ca382eebbb295c4746b32e3128210760c488ff334d659cccff74b8 +size 99612 diff --git a/marked/Rel-16/23_series/23119/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-16/23_series/23119/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76a32e838da684b2ade99c0858b49d969ab3ee6d --- /dev/null +++ b/marked/Rel-16/23_series/23119/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00a2a626d98308e242f06f8c4fe38adc4d27220323de25a775793438b8bb1e17 +size 124121 diff --git a/marked/Rel-16/23_series/23119/6922d65f6e8904f01264141d85dd51d5_img.jpg b/marked/Rel-16/23_series/23119/6922d65f6e8904f01264141d85dd51d5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cff791be9e1e5ba1b50ed248460a2374e26fc3b --- /dev/null +++ b/marked/Rel-16/23_series/23119/6922d65f6e8904f01264141d85dd51d5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81c9091ddc0248c5edb12ee873e63d978c6192961d3757d537b3122f9aa27844 +size 18917 diff --git a/marked/Rel-16/23_series/23119/6ba310120ebcd99661c4ee1c58a1586c_img.jpg b/marked/Rel-16/23_series/23119/6ba310120ebcd99661c4ee1c58a1586c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7902fa5cb21be8b14cc799580f5c6c8b522ef397 --- /dev/null +++ b/marked/Rel-16/23_series/23119/6ba310120ebcd99661c4ee1c58a1586c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d26f9484cf2c1677eb48c81a480995c5bd081d428d55fc15fb6388b8bd69781 +size 28544 diff --git a/marked/Rel-16/23_series/23119/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/Rel-16/23_series/23119/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..715d621e066a967c06e56fe06362d787cfc6f008 --- /dev/null +++ b/marked/Rel-16/23_series/23119/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11cf75a16cfd19db31b07dd6d6b81fe16aef74a6f8acffc7c1f1fe30914adcdd +size 52283 diff --git a/marked/Rel-16/23_series/23119/74e409e1548dd2606c4de9bdfe9806e4_img.jpg b/marked/Rel-16/23_series/23119/74e409e1548dd2606c4de9bdfe9806e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6721dbbfed172edc2dfd4116d9b591fe5786fd2c --- /dev/null +++ b/marked/Rel-16/23_series/23119/74e409e1548dd2606c4de9bdfe9806e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f4c426859af8664aa52898ef628362a4d41644d14dba3db3724720787b161a7 +size 92850 diff --git a/marked/Rel-16/23_series/23119/7818b1bd115c04ee738bcf90f51d945b_img.jpg b/marked/Rel-16/23_series/23119/7818b1bd115c04ee738bcf90f51d945b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0387acc71c4a200e539097833fcb1df4afea240a --- /dev/null +++ b/marked/Rel-16/23_series/23119/7818b1bd115c04ee738bcf90f51d945b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73cf41d95b32d4c3866411216fdcc95cb7755d72005b2f201b86d401b8f1aa66 +size 92548 diff --git a/marked/Rel-16/23_series/23119/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/23_series/23119/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8b9c23cc8e282b5b3519f8ea36957dcf73ff8e78 --- /dev/null +++ b/marked/Rel-16/23_series/23119/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89353cecaee2d9bcad7df4d895fdb83faa190fc858c66e7e3b8b6b3218e9abc9 +size 118804 diff --git a/marked/Rel-16/23_series/23119/796d2e601722450d6456085e0a801e1e_img.jpg b/marked/Rel-16/23_series/23119/796d2e601722450d6456085e0a801e1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..483602a8868052c79fcb1d811b74740dba13073f --- /dev/null +++ b/marked/Rel-16/23_series/23119/796d2e601722450d6456085e0a801e1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:305d5b681ccd6e0769994a455b4bf39bb01c209f13aeb05792e98da4666fb846 +size 52590 diff --git a/marked/Rel-16/23_series/23119/79aaab5889060cf8264226764a109cdb_img.jpg b/marked/Rel-16/23_series/23119/79aaab5889060cf8264226764a109cdb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fe7c0788374a40d8c01d8869ca90b968328d7fb --- /dev/null +++ b/marked/Rel-16/23_series/23119/79aaab5889060cf8264226764a109cdb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30201b891bcd6bd86039a3f9e06e6a2359da1a1d6992cc9b3b6bdf05c8e2e62d +size 65143 diff --git a/marked/Rel-16/23_series/23119/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/23_series/23119/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6648f912d85d7d672c27ace0c725912276c93915 --- /dev/null +++ b/marked/Rel-16/23_series/23119/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4b7a61620b28a391c58e8a761c5e6a9547db35c9aae3c52b4d8d08b0cad723a +size 131758 diff --git a/marked/Rel-16/23_series/23119/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/marked/Rel-16/23_series/23119/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0d3c9583610183b69f238de800766f8d2284a35 --- /dev/null +++ b/marked/Rel-16/23_series/23119/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba87978d86930a47c59748b519bcd4bd1474f9aedfa32117e6867abf22debfed +size 40843 diff --git a/marked/Rel-16/23_series/23119/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/23_series/23119/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..446456eaf9f6034146dc6dd919e125a16b3f03d5 --- /dev/null +++ b/marked/Rel-16/23_series/23119/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4d8b1b4e90890f8e7ca08f6b21f17022509a3acccec994c4198bbd70cc9d27f +size 75959 diff --git a/marked/Rel-16/23_series/23119/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23119/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56689935e611dee79b7350bcb8f653cc5a725dcc --- /dev/null +++ b/marked/Rel-16/23_series/23119/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd948c4ce161ec0b5bf9b29e55b8caafb96fc02e8dc00884855212a7e163c995 +size 46495 diff --git a/marked/Rel-16/23_series/23119/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23119/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5108fee0037fdc3c39bc3d320667799996cec2be --- /dev/null +++ b/marked/Rel-16/23_series/23119/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09c349411d3b436d5443d99b817daea01217dcaff1fe6a95a85dd05448900402 +size 159252 diff --git a/marked/Rel-16/23_series/23119/83c2ebae8819e9cdca7eb157a13ee26a_img.jpg b/marked/Rel-16/23_series/23119/83c2ebae8819e9cdca7eb157a13ee26a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d8b83727a1646ca9aadde2f844a91352946025b --- /dev/null +++ b/marked/Rel-16/23_series/23119/83c2ebae8819e9cdca7eb157a13ee26a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cff9f1d5d9a8dfea166c6814498dfc4efce4013588c9d92fceb79c43d413de00 +size 68458 diff --git a/marked/Rel-16/23_series/23119/8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg b/marked/Rel-16/23_series/23119/8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33d5010a5a3f58cbbbe37496bdd4d937c1feb47c --- /dev/null +++ b/marked/Rel-16/23_series/23119/8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8936bd70c1724fe89e3004c382f5933464676fe09ec25907013bcdae221fdae9 +size 44730 diff --git a/marked/Rel-16/23_series/23119/8edfc370769207831f060f44d2281084_img.jpg b/marked/Rel-16/23_series/23119/8edfc370769207831f060f44d2281084_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b70a140e8fa14c68aab91a8490488265708d4908 --- /dev/null +++ b/marked/Rel-16/23_series/23119/8edfc370769207831f060f44d2281084_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:850c2224e582c3de247025206a3061c38b596b718e40201c1fd272bac0f136aa +size 110368 diff --git a/marked/Rel-16/23_series/23119/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/23_series/23119/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01d12866fa378aa46c8a1e56a6a5eb1be8032b0f --- /dev/null +++ b/marked/Rel-16/23_series/23119/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e57f755886989f6596093ed5d5aeae24d758d9bd88ba8be8318c1162d5bce199 +size 154572 diff --git a/marked/Rel-16/23_series/23119/921458d4fc1b778c2450592ac9745b48_img.jpg b/marked/Rel-16/23_series/23119/921458d4fc1b778c2450592ac9745b48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8225323884003537f2721ee47587dc13972da45e --- /dev/null +++ b/marked/Rel-16/23_series/23119/921458d4fc1b778c2450592ac9745b48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b5bafa7de7a70cdbfc28adb909287be511e81ac31a25a2e794b05b64d68267c +size 24432 diff --git a/marked/Rel-16/23_series/23119/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/23_series/23119/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b72dde3048f2a29f3a91676bffe40c14f84ac8d9 --- /dev/null +++ b/marked/Rel-16/23_series/23119/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e47e2b95e896d1ee5c307241e2d6a5855ea229c139bbcd86d914ae90f3da3d1f +size 29356 diff --git a/marked/Rel-16/23_series/23119/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/marked/Rel-16/23_series/23119/933ecd14c858bf3fc919222d8e357bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7864deb0cc1fd11957df4c41187c4a443e2e23b --- /dev/null +++ b/marked/Rel-16/23_series/23119/933ecd14c858bf3fc919222d8e357bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12eacfa395c04b0f2f78060237c6823d7e89b0e2202a891852e830172df30cdc +size 88861 diff --git a/marked/Rel-16/23_series/23119/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/Rel-16/23_series/23119/99bae07626f60f9ede10e2e387ef7051_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..235ff30202c3739a09a0a3a2dbc334c011e2bf10 --- /dev/null +++ b/marked/Rel-16/23_series/23119/99bae07626f60f9ede10e2e387ef7051_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de35adc54b3bd77a9723655c8bc929c6dfe6331819a5ce8fb05515f7dd3c0bc4 +size 56229 diff --git a/marked/Rel-16/23_series/23119/9bafc60bf378685e5e246c3ffad7b792_img.jpg b/marked/Rel-16/23_series/23119/9bafc60bf378685e5e246c3ffad7b792_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..525211048cc9af38a4396adba597832eb2bda7e7 --- /dev/null +++ b/marked/Rel-16/23_series/23119/9bafc60bf378685e5e246c3ffad7b792_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9129d1b393f9418a54edbc8483abed6dddba6189f5cdeea4d147911d2096de27 +size 27913 diff --git a/marked/Rel-16/23_series/23119/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/23_series/23119/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c41106108945817f02667e516f9bcf6dc039dbbc --- /dev/null +++ b/marked/Rel-16/23_series/23119/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4cca7c7297068e5390bbc9d346066f526b4d2e119e632ed995956e08f1a7951 +size 118549 diff --git a/marked/Rel-16/23_series/23119/9c45844d796e85ae05505870a54e4eb4_img.jpg b/marked/Rel-16/23_series/23119/9c45844d796e85ae05505870a54e4eb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3720b6954b8fbb1efeb20867ccbf3dd6519911b3 --- /dev/null +++ b/marked/Rel-16/23_series/23119/9c45844d796e85ae05505870a54e4eb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e5f7a43d385fbc522c526b60741f8e5e3806731e1b4fadfb6f16dc9274a7379 +size 140003 diff --git a/marked/Rel-16/23_series/23119/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/23_series/23119/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d86d7a126da74303b78383bda99d8350c9d391c0 --- /dev/null +++ b/marked/Rel-16/23_series/23119/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14638eaca6732d97bf2b46054a0543cd9b0650a9ca76aaabeef2152895112c15 +size 140639 diff --git a/marked/Rel-16/23_series/23119/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-16/23_series/23119/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a293e7fded63edf831e882944d0ee66634d3065b --- /dev/null +++ b/marked/Rel-16/23_series/23119/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3cf8fb0fc90e0e7583883a53db9e3bd2249bd1f4019bbf0c46f2ff7b4d3ac195 +size 64845 diff --git a/marked/Rel-16/23_series/23119/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/23_series/23119/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bb8489b48b2f74ec9529b9a5d261c6c1f41724f --- /dev/null +++ b/marked/Rel-16/23_series/23119/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cefe9c0969961b7cc9720a01c188d8ba28277b43f244ca439aaff5ab96815d15 +size 117761 diff --git a/marked/Rel-16/23_series/23119/a320e67b369bfde4a5fa360b100da55c_img.jpg b/marked/Rel-16/23_series/23119/a320e67b369bfde4a5fa360b100da55c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09c51f519594c42cf6e5b29f630181e6c2750e38 --- /dev/null +++ b/marked/Rel-16/23_series/23119/a320e67b369bfde4a5fa360b100da55c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad8c89e092632f51875de1c11415893d9284e635c8bbe47e3a890a67b708b6a4 +size 74922 diff --git a/marked/Rel-16/23_series/23119/a3d6b1f562612dbd5a5d7c4ce91999d1_img.jpg b/marked/Rel-16/23_series/23119/a3d6b1f562612dbd5a5d7c4ce91999d1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f6cd6357f33107bbe7c2e8c404e456408431406 --- /dev/null +++ b/marked/Rel-16/23_series/23119/a3d6b1f562612dbd5a5d7c4ce91999d1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11fbf570a86c43e2b05651bc930f2342403d274e6bda65eee8446a6761e3cc59 +size 29679 diff --git a/marked/Rel-16/23_series/23119/a471382fa73185ead4f9b83e3e64ee96_img.jpg b/marked/Rel-16/23_series/23119/a471382fa73185ead4f9b83e3e64ee96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c341bae07b548a47b061c661ffff75ea016dc5c --- /dev/null +++ b/marked/Rel-16/23_series/23119/a471382fa73185ead4f9b83e3e64ee96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbae59d056bcc06f87fa1d12e0187f7c0095ab5fe19fa62775dbde9c66dbedb3 +size 83872 diff --git a/marked/Rel-16/23_series/23119/a5404b7275b06497eecf9b5883604753_img.jpg b/marked/Rel-16/23_series/23119/a5404b7275b06497eecf9b5883604753_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ad4b1650f8eaac39d104071dfa5c5fb0d1cf007 --- /dev/null +++ b/marked/Rel-16/23_series/23119/a5404b7275b06497eecf9b5883604753_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e344f1f3f7f3970ef7ba3c02cc740b4eb35d5f511268426c851294ad47f3004 +size 136205 diff --git a/marked/Rel-16/23_series/23119/a634891d16b60b21df90a35c2af72c67_img.jpg b/marked/Rel-16/23_series/23119/a634891d16b60b21df90a35c2af72c67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f35e2d58d188eb7dac1b63ee7e743ac04abc687 --- /dev/null +++ b/marked/Rel-16/23_series/23119/a634891d16b60b21df90a35c2af72c67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:869d5c84653de7e314f236684fd21046870aa412dedbdcdbbe9130b730f8b070 +size 83368 diff --git a/marked/Rel-16/23_series/23119/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/marked/Rel-16/23_series/23119/a7450c80e88ad3f6ca1427ad84020998_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d5e97ad75868a554dc58844583c03229e049b7d --- /dev/null +++ b/marked/Rel-16/23_series/23119/a7450c80e88ad3f6ca1427ad84020998_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7c05daa74d5d7c1d3439fff9bb5485201afdbb37f7496cf0ddbe3b4a4d82280 +size 94642 diff --git a/marked/Rel-16/23_series/23119/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Rel-16/23_series/23119/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b4e0601a09270c8700b70a231390dc45626b4bf --- /dev/null +++ b/marked/Rel-16/23_series/23119/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea561de93b35cf0e47982c22317ba6512fc92fd2667f553422d191a6daecf62c +size 39913 diff --git a/marked/Rel-16/23_series/23119/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Rel-16/23_series/23119/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf0aa71a5c3ad6f05af599c6952599c44dcad4a2 --- /dev/null +++ b/marked/Rel-16/23_series/23119/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:427edea58196d23100342658cbaf8382ab61f68881d2b8e604ddc7c7cfc6865a +size 94936 diff --git a/marked/Rel-16/23_series/23119/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/23_series/23119/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c51f746e2da684f51fb7716418b286bf13c14be3 --- /dev/null +++ b/marked/Rel-16/23_series/23119/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52875103bf7c02e0aa00cfd8c0b53cffb104aaea6a49601e94dc239053c1a4c0 +size 127960 diff --git a/marked/Rel-16/23_series/23119/af2da9ea326af3b375c6fea82bd0b77d_img.jpg b/marked/Rel-16/23_series/23119/af2da9ea326af3b375c6fea82bd0b77d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77196411d9d0fd7c8e79387d3fc44948da5499ed --- /dev/null +++ b/marked/Rel-16/23_series/23119/af2da9ea326af3b375c6fea82bd0b77d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d3fd42f69bb1fc290afb0d8477b657294b585ac6c36b6d09f6400098fc6d5c0 +size 20684 diff --git a/marked/Rel-16/23_series/23119/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/marked/Rel-16/23_series/23119/b51423b6c049f5b5fcde42e50b58f18b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be554e5bb8da5cbc4e4a339aa487a8273fa69992 --- /dev/null +++ b/marked/Rel-16/23_series/23119/b51423b6c049f5b5fcde42e50b58f18b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37e5cdcb4aef3b37c9c7d04fd305b6192c1ec0fbeb98014121e083662e2393da +size 76757 diff --git a/marked/Rel-16/23_series/23119/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Rel-16/23_series/23119/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f15ef703d1b4a0360d6d6581eaf5f606309419e --- /dev/null +++ b/marked/Rel-16/23_series/23119/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:601b581134d1f4b4346d1cb7458da4a353617a77bda2bf452476d302ee47feca +size 58384 diff --git a/marked/Rel-16/23_series/23119/b87818c8505328b198d035761bbc3f2d_img.jpg b/marked/Rel-16/23_series/23119/b87818c8505328b198d035761bbc3f2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..211f9bef44a4d0995a8ae21e20b4390cd4044510 --- /dev/null +++ b/marked/Rel-16/23_series/23119/b87818c8505328b198d035761bbc3f2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:affdcc5970e240c9b5d1af3bf7b15de1bc12e2f8c0b474b8642cdf2f86b57a1e +size 71700 diff --git a/marked/Rel-16/23_series/23119/b904ac2472cab80892d1e783e6230d6e_img.jpg b/marked/Rel-16/23_series/23119/b904ac2472cab80892d1e783e6230d6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ce5a28aa0caae956867edfc1cf15285576e8cb4 --- /dev/null +++ b/marked/Rel-16/23_series/23119/b904ac2472cab80892d1e783e6230d6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ce03aae97aa55bd98eb32a30e2f512263bc654017917a1c7838eb54b9619e69 +size 68432 diff --git a/marked/Rel-16/23_series/23119/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg b/marked/Rel-16/23_series/23119/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f95f9bdd23d4e26ad1e68181ce01915172b5ca3e --- /dev/null +++ b/marked/Rel-16/23_series/23119/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00471364b13aea3b3f88c5ecd57efa40ff5bc4dd380d2d22816bfdd72605ac6c +size 125215 diff --git a/marked/Rel-16/23_series/23119/bb3063a33c89b248574f64b6d8dfc404_img.jpg b/marked/Rel-16/23_series/23119/bb3063a33c89b248574f64b6d8dfc404_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2136af9a229234d619cb68091fc5470978bb93d3 --- /dev/null +++ b/marked/Rel-16/23_series/23119/bb3063a33c89b248574f64b6d8dfc404_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b7242c62d36bbe3d8c2f642c6d0a292eb654bf21fd4e141d881d7a5c956c334 +size 52552 diff --git a/marked/Rel-16/23_series/23119/bbddeb46a8bee133d49003273fcfc8dd_img.jpg b/marked/Rel-16/23_series/23119/bbddeb46a8bee133d49003273fcfc8dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90451f3b741a223c6b9986c3e2b956ac4ac49345 --- /dev/null +++ b/marked/Rel-16/23_series/23119/bbddeb46a8bee133d49003273fcfc8dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:548052b9e19393087f91e3e83550f00ac00f62bd9c29646316e735b62094c748 +size 21668 diff --git a/marked/Rel-16/23_series/23119/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Rel-16/23_series/23119/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff52cb572b8582115e1ab802c53537e77ac139fd --- /dev/null +++ b/marked/Rel-16/23_series/23119/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f5099bd0189af484aab70858b623a303bab7d069cfcebb29ceb63eee674eaf7 +size 135368 diff --git a/marked/Rel-16/23_series/23119/c0ca823603794512478906b302176bca_img.jpg b/marked/Rel-16/23_series/23119/c0ca823603794512478906b302176bca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b64a17d49fc41556283de708541ffe96e9f60637 --- /dev/null +++ b/marked/Rel-16/23_series/23119/c0ca823603794512478906b302176bca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57f0c3af0fd43faf3294bca3aa9dfec4a9ee59b3eca2eaf43420ff7e8e87ad32 +size 75724 diff --git a/marked/Rel-16/23_series/23119/c419b566d720267c499087add1506018_img.jpg b/marked/Rel-16/23_series/23119/c419b566d720267c499087add1506018_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4d8d91027888a8bb16f0bae307e4fd4375c80657 --- /dev/null +++ b/marked/Rel-16/23_series/23119/c419b566d720267c499087add1506018_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:671a159c3bdebef425663cedfc865f9c46208dbc22f06ebe9c546d8f9ad35ca0 +size 68413 diff --git a/marked/Rel-16/23_series/23119/c4e30d3e93833e47634647ab593db2ff_img.jpg b/marked/Rel-16/23_series/23119/c4e30d3e93833e47634647ab593db2ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98166b0ffc589c08dc83a4a3df6aa29279ba8dfc --- /dev/null +++ b/marked/Rel-16/23_series/23119/c4e30d3e93833e47634647ab593db2ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e6e0ac244596810a9abf7a704050f24583864e81a32d473eed662dd0529fd41 +size 44779 diff --git a/marked/Rel-16/23_series/23119/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg b/marked/Rel-16/23_series/23119/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc1059f69f8694dca08dce14dadcf98ccebcf0a5 --- /dev/null +++ b/marked/Rel-16/23_series/23119/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7ede9dcef1d42e3e43abf9cab20c61b102087a281136e71913316b1f36d48be +size 29182 diff --git a/marked/Rel-16/23_series/23119/d2417b04116c354deccb25d98a84a0fb_img.jpg b/marked/Rel-16/23_series/23119/d2417b04116c354deccb25d98a84a0fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98ad70f1f91922c1967e1fb0b62dfd9f3b7c94ee --- /dev/null +++ b/marked/Rel-16/23_series/23119/d2417b04116c354deccb25d98a84a0fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a8e60cf696696b298fe6a3d39eca094a705cc4589022770f29fd6855b7cf15b +size 57123 diff --git a/marked/Rel-16/23_series/23119/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/23_series/23119/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b4ea9ed836bc6a5b3067cfdf54eafedf92c5555 --- /dev/null +++ b/marked/Rel-16/23_series/23119/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aaa022e5f8e6ccd00d41fa940fc22e0c2e94dc46f792943b9fc624336dab6e82 +size 66196 diff --git a/marked/Rel-16/23_series/23119/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/Rel-16/23_series/23119/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..839f48c532786a759dcb28a88f113a5853e7b11f --- /dev/null +++ b/marked/Rel-16/23_series/23119/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db90d830011c86d4e205012d1b628319e068facc670cd055bb86abf7751150fd +size 153008 diff --git a/marked/Rel-16/23_series/23119/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Rel-16/23_series/23119/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..789db544700934111a25b399947e6a0c8cb46bb2 --- /dev/null +++ b/marked/Rel-16/23_series/23119/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4611e116d514531973d1f944de5e87d1f94a5c8d89e3cd44035e3d3ec461f01 +size 46013 diff --git a/marked/Rel-16/23_series/23119/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg b/marked/Rel-16/23_series/23119/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75274172241ab319cb36ec8b1f255f6fd1e016ac --- /dev/null +++ b/marked/Rel-16/23_series/23119/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d54ea746c142cb82421989e43bf5f62dfb0b9e24cd080546e99d8ce0786c13c +size 96092 diff --git a/marked/Rel-16/23_series/23119/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23119/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae0798367797ab677aeb9274ab18fb84ff8e6a49 --- /dev/null +++ b/marked/Rel-16/23_series/23119/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:986e4d2db3a9b940c8ad50f9e58c48716a3983ecab70fb7a187164e293524c81 +size 162507 diff --git a/marked/Rel-16/23_series/23119/e18841eb4a995df8354a793459e12fd0_img.jpg b/marked/Rel-16/23_series/23119/e18841eb4a995df8354a793459e12fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c98cd9abaa6d176b2bc276f4fd534b388024b251 --- /dev/null +++ b/marked/Rel-16/23_series/23119/e18841eb4a995df8354a793459e12fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de0a1dce50c33ad2442d56d347f60e53d665590cd1821de16e741d407596cdc2 +size 24402 diff --git a/marked/Rel-16/23_series/23119/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-16/23_series/23119/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e44cdeb356f2d104bbd8235d0269a267c456ed99 --- /dev/null +++ b/marked/Rel-16/23_series/23119/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18a6fe5f881aa772d0aac1ca5fa354ef74e5bf4d71cf70634c4bec9e2e3deb32 +size 37001 diff --git a/marked/Rel-16/23_series/23119/e60c2d24a97a2855d98671d27ea43d0f_img.jpg b/marked/Rel-16/23_series/23119/e60c2d24a97a2855d98671d27ea43d0f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b9f209107b7528862eafd0c4339ba92bb818bddd --- /dev/null +++ b/marked/Rel-16/23_series/23119/e60c2d24a97a2855d98671d27ea43d0f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0560090bc2133507bd744c80a6ddac4865975313c2cb334cf364f3317d06dca0 +size 54472 diff --git a/marked/Rel-16/23_series/23119/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-16/23_series/23119/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cca4dc13d9f2e9a2c1fb336e682175fdbb0d9c0b --- /dev/null +++ b/marked/Rel-16/23_series/23119/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:feef64abd97988497486d9189e4c70f7ac337d10475d58a8e511353d54e85cc0 +size 117209 diff --git a/marked/Rel-16/23_series/23119/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-16/23_series/23119/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1df32851fef0daf02142fa7c780611b95f243b18 --- /dev/null +++ b/marked/Rel-16/23_series/23119/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c547cfd1db0bb5c81f1057fe9adb2d90ff72d01c6297db0530642d07b693c57 +size 88176 diff --git a/marked/Rel-16/23_series/23119/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23119/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa68a917f55c62b78c6dcddd79cca7a5ba24fe58 --- /dev/null +++ b/marked/Rel-16/23_series/23119/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:125649a0474b79f6a6eda6bbc10c2561dd60cc69b1b65c1b4c43b65f1ada4ee6 +size 146837 diff --git a/marked/Rel-16/23_series/23119/ef0faba51289e3a364ba51e5ef4d1a43_img.jpg b/marked/Rel-16/23_series/23119/ef0faba51289e3a364ba51e5ef4d1a43_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5526e00977af5388b9a36afba053a33c4485b1b7 --- /dev/null +++ b/marked/Rel-16/23_series/23119/ef0faba51289e3a364ba51e5ef4d1a43_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e8ea636a8cf39bd8568d6af9021438f0a8ee9a575ffde16582bc96faab0f7e7 +size 75824 diff --git a/marked/Rel-16/23_series/23119/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-16/23_series/23119/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44fcc942ddd78bb7d1606c2792048a09cab281c6 --- /dev/null +++ b/marked/Rel-16/23_series/23119/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3e379f4e41310d247dccbd49afd7d9f0cb4e0f491eb5b33f9ef74bef141514e +size 105882 diff --git a/marked/Rel-16/23_series/23119/ff1a293f8118c0f00dbfeb0ab843d6e6_img.jpg b/marked/Rel-16/23_series/23119/ff1a293f8118c0f00dbfeb0ab843d6e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce5b099e2034a7c55cf959ed8c4e16b1149dda9d --- /dev/null +++ b/marked/Rel-16/23_series/23119/ff1a293f8118c0f00dbfeb0ab843d6e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f98551382f8c4ba03327d4f9525056f78b693f8daaf21ff709488c4fcb703edb +size 83915 diff --git a/marked/Rel-16/23_series/23119/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/marked/Rel-16/23_series/23119/ffe0fef452a0ae9a20253c319c54e13c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff56051e9b95e1a922126fe2c12c1bfcc416bf0d --- /dev/null +++ b/marked/Rel-16/23_series/23119/ffe0fef452a0ae9a20253c319c54e13c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a835c110ca11310cec36573110a0dd7f5e51fbd5576dd77bd030f2939d41129f +size 57117 diff --git a/marked/Rel-16/23_series/23119/raw.md b/marked/Rel-16/23_series/23119/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..997ba5e2d2acfbef7879cc88724b6684ae0d76c7 --- /dev/null +++ b/marked/Rel-16/23_series/23119/raw.md @@ -0,0 +1,4556 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 Introduction..... | 8 | +| 5 Roaming Scenario ..... | 8 | +| 5.1 Relationship between GLR and HLR..... | 8 | +| 5.2 Relationship between GLR and VLR..... | 9 | +| 5.3 Roaming to VPLMN with GLR from HPLMN without GLR ..... | 9 | +| 5.4 Intra-VPLMN with GLR roaming..... | 10 | +| 5.5 Inter-VPLMNs with GLR Roaming..... | 10 | +| 5.6 Roaming to VPLMN without GLR from VPLMN with GLR ..... | 11 | +| 6 Logical Network Model..... | 11 | +| 6.1 GLR..... | 12 | +| 6.2 Intermediate MSC ..... | 12 | +| 6.3 Intermediate GSN..... | 12 | +| 6.4 Gate Node..... | 12 | +| 7 Functional Description..... | 13 | +| 7.1 Logical Functions..... | 13 | +| 7.1.1 Message Relay Function..... | 13 | +| 7.1.2 Address Conversion Function ..... | 13 | +| 7.1.3 Subscriber Information Caching Function ..... | 13 | +| 7.1.4 Subscriber Information Cancellation Function ..... | 13 | +| 7.1.5 HLR emulation Function..... | 14 | +| 7.1.6 Location Updating Screening Function..... | 14 | +| 7.1.7 Routeing Information Providing Function ..... | 14 | +| 7.1.8 Regional Restriction and Unsupported Services handling Function ..... | 14 | +| 7.1.9 Super Charger function..... | 14 | +| 7.2 Circuit Switched Service..... | 14 | +| 7.2.1 Location Management Procedures ..... | 14 | +| 7.2.1.1 Location Updating Procedure ..... | 14 | +| 7.2.1.1.1 First Location Updating Procedure ..... | 15 | +| 7.2.1.1.2 Second and further Location Updating Procedure ..... | 16 | +| 7.2.1.1.3 Functional requirements of GLR..... | 16 | +| 7.2.1.2 Cancel Location Procedure ..... | 29 | +| 7.2.1.2.1 Functional requirements of GLR..... | 30 | +| 7.2.1.3 Handling of unsupported service ..... | 33 | +| 7.2.2 Retrieval of routeing information procedure ..... | 34 | +| 7.2.2.1 Information flow for retrieval of routeing information for an MT call ..... | 35 | +| 7.2.2.2 Functional requirements of network entities ..... | 35 | +| 7.2.2.2.1 Functional requirements of GLR..... | 36 | +| 7.2.2.3 Contents of messages (HLR-GLR, GLR-VLR) ..... | 41 | +| 7.2.3 Authentication Information Retrieval procedure ARRI ..... | 41 | +| 7.2.4 Subscriber Data management procedure ..... | 41 | +| 7.2.4.1 Insert Subscriber Data Procedure ..... | 41 | +| 7.2.4.2 Delete Subscriber Data Procedure ..... | 42 | +| 7.2.5 Supplementary services procedures..... | 43 | +| 7.3 Packet Switched Service ..... | 43 | +| 7.3.1 GPRS Attach Procedure ..... | 44 | +| 7.3.1.1 New SGSN served by GLR, old SGSN served by HLR ..... | 44 | +| 7.3.1.2 New SGSN and old SGSN served by the same GLR ..... | 46 | + +| | | | +|-----------|--------------------------------------------------------------------------------|-----| +| 7.3.1.3 | New SGSN served by the GLR, and old SGSN served by the other GLR..... | 47 | +| 7.3.1.4 | New SGSN served by HLR, old SGSN served by GLR ..... | 49 | +| 7.3.1.5 | Functional requirements of GLR ..... | 50 | +| 7.3.1.5.1 | Process Update_GPRS_Location_GLR ..... | 50 | +| 7.3.1.5.2 | Process Subscriber_Present_GPRS_GLR..... | 58 | +| 7.3.1.5.3 | Procedure Insert_Subscriber_Data_GPRS_Initiated_GLR..... | 59 | +| 7.3.1.5.4 | Process Cancel_GPRS_Location_Initiated_GLR ..... | 60 | +| 7.3.2 | Detach procedure..... | 61 | +| 7.3.2.1 | HLR-Initiated Detach Procedure ..... | 61 | +| 7.3.2.2 | Functional requirements of GLR ..... | 61 | +| 7.3.2.2.1 | Process Cancel_GPRS_Location_GLR ..... | 61 | +| 7.3.3 | Authentication of Subscriber..... | 63 | +| 7.3.4 | Inter SGSN Routeing Area Update Procedure ..... | 63 | +| 7.3.5 | Subscriber Management Procedures ..... | 66 | +| 7.3.5.1 | Insert Subscriber Data Procedure ..... | 66 | +| 7.3.5.2 | Delete Subscriber Data Procedure ..... | 67 | +| 7.3.6 | PDP Context Activation Procedure ..... | 67 | +| 7.3.6.1 | Successful Network-Requested PDP Context Activation Procedure with GLR ..... | 67 | +| 7.3.6.2 | Unsuccessful Network-Requested PDP Context Activation Procedure with GLR ..... | 68 | +| 7.4 | Purge MS Procedure..... | 70 | +| 7.4.1 | Functional requirements of GLR..... | 71 | +| 7.4.1.1 | Process Purge_MS_GLR ..... | 71 | +| 7.5 | Regional Restriction Procedure..... | 74 | +| 7.6 | Recovery and Restoration ..... | 75 | +| 7.6.1 | GLR Failure..... | 76 | +| 7.6.2 | HLR Failure..... | 77 | +| 7.6.2.1 | Suppression of Intra-PLMN signalling..... | 79 | +| 7.6.2.1.1 | Usage of the HLR id List (Tool 1)..... | 79 | +| 7.6.2.1.2 | Multiple GLR number allocation (Tool 2)..... | 79 | +| 7.6.3 | VLR Failure..... | 80 | +| 7.6.4 | SGSN Failure..... | 81 | +| 7.6.5 | Functional requirements of GLR..... | 82 | +| 7.6.5.1 | Process Restore_Data_GLR ..... | 82 | +| 7.7 | Short Message Service ..... | 90 | +| 7.7.1 | Scope ..... | 90 | +| 7.7.2 | Definitions ..... | 90 | +| 7.7.3 | Services and service elements ..... | 91 | +| 7.7.3.1 | Short Message Service elements..... | 91 | +| 7.7.3.1.1 | Messages-Waiting..... | 91 | +| 7.7.3.1.2 | Alert-SC ..... | 92 | +| 7.7.3.2 | Unsuccessful short message TPDU transfer SC -> MS..... | 92 | +| 7.7.4 | Network architecture ..... | 92 | +| 7.7.4.1 | Basic network structure ..... | 92 | +| 7.7.5 | Node functionality related to SM MT ..... | 93 | +| 7.7.5.1 | General ..... | 93 | +| 7.7.5.2 | Functionality of the GLR..... | 93 | +| 7.7.5.3 | Functionality of the IM-MSC ..... | 93 | +| 7.7.6 | Protocols and protocol architecture..... | 94 | +| 7.7.6.1 | Service provided by the SM-RL ..... | 94 | +| 7.7.6.1.1 | General ..... | 94 | +| 7.7.6.1.2 | Protocol element repertoire at SM-RL..... | 94 | +| 7.7.7 | Fundamental procedures within the point-to-point SMS ..... | 94 | +| 7.7.7.1 | Short message mobile terminated..... | 94 | +| 7.7.7.2 | Functional requirements of GLR ..... | 103 | +| 7.7.7.2.1 | Process Obtain_MSC_Number_GLR ..... | 103 | +| 7.7.7.2.2 | Process Inform_SM_Delivery_Failure_GLR ..... | 105 | +| 7.7.7.2.3 | Procedure Check_Absent_SubscriberSM_In_GLR ..... | 107 | +| 7.7.7.3 | Alert transfer ..... | 108 | +| 7.8 | Subscriber and Equipment Trace ..... | 110 | +| 7.9 | Impact of GLR on CAMEL ..... | 110 | + +| | | | +|------------------------|----------------------------------------------------------------------------------------------------|-----| +| 7.9.1 | The VLR supports CAMEL Phase 2 onwards ..... | 110 | +| 7.9.2 | The VLR supports CAMEL Phase 1 or has no CAMEL Support..... | 111 | +| 7.10 | Interaction with CCBS ..... | 111 | +| 7.10.1 | Two possible treatments for interaction with CCBS..... | 111 | +| 7.10.2 | The functionality in the GLR ..... | 111 | +| 7.10.2.1 | Functional requirements of GLR ..... | 113 | +| 7.10.2.1.1 | Process Set_reporting_GLR..... | 113 | +| 7.10.2.1.2 | Process Status report GLR ..... | 115 | +| 7.10.2.1.3 | Process Remote_User_Free_GLR..... | 116 | +| 7.10.2.1.4 | Procedure CCBS_status_report_GLR..... | 117 | +| 7.10.2.1.5 | Procedure CCBS_start_report_GLR ..... | 118 | +| 7.11 | Location Service..... | 119 | +| 7.11.1 | Mobile Terminating Location Request..... | 119 | +| 7.11.1.1 | Circuit Switched Mobile Terminating Location Request (CS-MT-LR)..... | 119 | +| 7.11.1.1.1 | Location Preparation Procedure ..... | 119 | +| 7.11.1.1.2 | Positioning Measurement Establishment Procedure ..... | 120 | +| 7.11.1.1.3 | Location Calculation and Release Procedure..... | 120 | +| 7.11.1.2 | MT-LR for a previously obtained location estimate..... | 120 | +| 7.11.1.3 | Network Induced Location Request (NI-LR) ..... | 121 | +| 7.11.1.4 | Network Induced Location Request (NI-LR) from a Serving RNC for a target UE in dedicated mode..... | 121 | +| 7.11.2 | Mobile Originating Location Request..... | 121 | +| 7.11.2.1 | Mobile Originating Location Request, Circuit Switched (CS-MO-LR)..... | 121 | +| 7.12 | IST of non-CAMEL implementation ..... | 121 | +| 7.13 | The interaction with Super-Charger..... | 121 | +| 7.13.1 | First Location Updating Procedure in the Super-Charged network ..... | 121 | +| 7.13.2 | Second and further Location Updating Procedure in the Super-Charged networks..... | 123 | +| 7.13.3 | Cancel Location Procedure in the Super-Charged networks..... | 123 | +| 7.13.4 | Functional requirement for the GLR ..... | 124 | +| 7.13.4.1 | Procedure Super_Charged_Cancel_Location_GLR ..... | 124 | +| 7.13.4.2 | Procedure Super_Charged_Location_Updating_GLR ..... | 126 | +| 8 | The subscriber information stored in the GLR ..... | 127 | +| 8.1 | Information for HLR emulation ..... | 127 | +| 8.2 | Information for address and identity conversion..... | 127 | +| 8.3 | Information for Location updating Screening..... | 127 | +| 8.4 | Information for support of Super-Charger functionality ..... | 128 | +| 8.5 | Other Information..... | 128 | +| 8.6 | IMSI Record in the GLR..... | 129 | +| Annex A (informative): | Change history..... | 131 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 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. + +# --- 1 Scope + +The present document gives the stage 2 description of the Gateway Location Register (GLR) within the UMTS Core Network as a means of reducing the amount of MAP signalling traffic associated with location management carried over inter-PLMN links for roaming users. + +The present document will be restricted of the case where the GLR supports one VPLMN only. + +# --- 2 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 TS 22.003: "Teleservices Supported by a GSM Public Land Mobile Network (PLMN)". +- [2] 3GPP TS 23.007: "Restore procedure". +- [3] 3GPP TS 23.012: "Location management". +- [4] 3GPP TS 23.018: "Basic call handling". +- [5] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS); Point-to-Point (PP)". +- [6] 3GPP TS 23.060: "General Packet Radio Service; Service description; Stage 2". +- [7] 3GPP TS 23.171: "Location Services (LCS); Functional Description; Stage 2". +- [8] 3GPP TS 23.093: "Technical realization of Completion of Calls to Busy Subscriber (CCBS) - Stage 2". +- [9] 3GPP TS 23.116: "Super-Charger Technical Realisation; Stage 2". +- [10] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [11] 3GPP TS 29.120: "Mobile Application Part (MAP) specification for GLR". +- [12] 3GPP TS 33.102: "3G Security". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**Gateway Location Register:** this entity handles location management of roaming subscriber in visited network without involving HLR + +**Intermediate GSN:** this entity is used as serving GSN towards home network and relay some PDU notification messages between serving GSN and Gateway GSN + +**Intermediate MSC:** this entity is used as serving MSC towards home network and relay some messages between serving MSC and home network + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|----------------------------------------| +| CCBS | Completion of Calls to Busy Subscriber | +| GLR | Gateway Location Register | +| GPRS | General Packet Radio Service | +| IM-GSN | Intermediate GSN | +| IM-MSC | Intermediate MSC | +| SGSN | Serving GPRS Support Node | + +# --- 4 Introduction + +UMTS will build on the success of GSM and is likely to become even more widespread. UMTS/ IMT-2000 networks based on GSM evolution are planned for Europe, Japan, USA and Korea. Coupled with steadily increasing rates of international travel for business and leisure, this means a significant increase in the number of roaming users needing to be supported. This will lead to an increase of the signalling traffic on "short-haul" and "long-haul" international links. + +The GLR (Gateway Location Register) is a node between the VLR and/or SGSN and the HLR, which may be used to optimise the location updating and the handling of subscriber profile data across network boundaries. When a subscriber is roaming the GLR plays the role of the HLR towards the VLR and SGSN in the visited network and the role of the VLR and SGSN towards the HLR in the home network. + +The GLR is an optional entity within the VPLMN. The network architecture where the presence of a GLR within a UMTS PLMN is not visible to either a second generation HPLMN (i.e. GSM release 98 or earlier) or a 3G HPLMN (i.e. GSM Release 99 or later). + +# --- 5 Roaming Scenario + +Figure 1 shows that the GLR is deployed at the edge of visited network. It contains roamer's subscriber profile and location information, and handles mobility management within the visited network. + +The subscriber information is downloaded from HLR to GLR at the first location update procedure under the GLR. Using the information, GLR handles *Update Location* message from VLR as if it is the HLR of the subscriber at second and further location updating procedures. GLR enables the procedure invisible from the home network so that this hierarchical location management can reduce the inter-network signalling for the location management. + +The GLR keeps the information until receiving *Cancel Location* message from HLR. + +## 5.1 Relationship between GLR and HLR + +A GLR interacts with multiple HLRs, which will be located in different PLMNs. The relationship between the GLR and the HLR is the same as that between the VLR and the HLR. + +The implication of supporting multiple HPLMNs is that the GLR will need to store a large amount of profile data. + +## 5.2 Relationship between GLR and VLR + +A GLR interacts with multiple VLRs. For the purposes of this Technical Specification, the GLR supports only one VPLMN. The support of multiple VPLMNs by the GLR is outside the scope of this Technical Specification. + +However, it is an assumption of this specification that the proposed GLR architecture must not prevent future expansion to support multiple VPLMNs. + +![Figure 5.2/1: Possible Location of GLR. Network diagram showing three HPLMNs (A, B, C) at the top, each with an HLR. These connect to two VPLMNs (a, b) below. Each VPLMN contains one GLR and two VLR/SGSN units. Lines show connectivity from HLRs to GLRs, and from GLRs to their respective VLR/SGSNs.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +Figure 5.2/1: Possible Location of GLR. Network diagram showing three HPLMNs (A, B, C) at the top, each with an HLR. These connect to two VPLMNs (a, b) below. Each VPLMN contains one GLR and two VLR/SGSN units. Lines show connectivity from HLRs to GLRs, and from GLRs to their respective VLR/SGSNs. + +Figure 5.2/1: Possible Location of GLR + +## 5.3 Roaming to VPLMN with GLR from HPLMN without GLR + +Figure 5.3/1 shows the roaming scenario in case of a subscriber roaming to a new VPLMN with the GLR. + +![Figure 5.3/1: Roaming to VPLMN with the GLR from HPLMN without the GLR. Diagram showing MS-a at the bottom connecting to a VLR/SGSN in VPLMN a. A thin arrow labeled 'Location Update' goes from MS-a to VLR/SGSN, then to GLR, then to HLR in HPLMN A. A thick arrow labeled 'Subscriber Data' returns from HLR A to GLR, then to VLR/SGSN. Other network elements (HPLMN B, C and VPLMN b) are shown as background context.](99bae07626f60f9ede10e2e387ef7051_img.jpg) + +➡ Subscriber Data + +➞ : Location Update + +MS-a + +Figure 5.3/1: Roaming to VPLMN with the GLR from HPLMN without the GLR. Diagram showing MS-a at the bottom connecting to a VLR/SGSN in VPLMN a. A thin arrow labeled 'Location Update' goes from MS-a to VLR/SGSN, then to GLR, then to HLR in HPLMN A. A thick arrow labeled 'Subscriber Data' returns from HLR A to GLR, then to VLR/SGSN. Other network elements (HPLMN B, C and VPLMN b) are shown as background context. + +Figure 5.3/1: Roaming to VPLMN with the GLR from HPLMN without the GLR + +## 5.4 Intra-VPLMN with GLR roaming + +In this case, the second and further location updating procedure is handled within the VPLMN. No location management message is sent to the HPLMN. + +![Diagram of Intra-VPLMN with GLR roaming showing three HPLMNs (A, B, C) connected to two VPLMNs (a, b). VPLMN a contains a GLR and two VLR/SGSN units. MS-a is shown moving from one VLR/SGSN to another within VPLMN a. Arrows indicate Subscriber Data, Location Update, and Cancel Location messages.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +The diagram illustrates Intra-VPLMN with GLR roaming. At the top, three Home PLMNs (HPLMN A, B, and C) are shown, each containing an HLR. These HLRs are connected to two Visited PLMNs (VPLMN a and b). VPLMN a contains a Gateway RNC (GLR) and two VLR/SGSN units. VPLMN b also contains a GLR and two VLR/SGSN units. MS-a is shown moving from one VLR/SGSN to another within VPLMN a. The legend indicates: + + +- Subscriber Data**: Solid thick arrow from HLR to GLR. +- Location Update**: Solid thin arrow from VLR/SGSN to GLR. +- Cancel Location**: Dotted thin arrow from GLR to VLR/SGSN. + + A dashed box represents the old VLR/SGSN, and a solid box represents the new VLR/SGSN. + +Diagram of Intra-VPLMN with GLR roaming showing three HPLMNs (A, B, C) connected to two VPLMNs (a, b). VPLMN a contains a GLR and two VLR/SGSN units. MS-a is shown moving from one VLR/SGSN to another within VPLMN a. Arrows indicate Subscriber Data, Location Update, and Cancel Location messages. + +Figure 5.4/1: Intra-VPLMN with GLR roaming + +## 5.5 Inter-VPLMNs with GLR Roaming + +This roaming case is similar to the case of roaming from HPLMN to VPLMN. The first location update procedure is handled by HLR and VLR via GLR of a new VPLMN. + +![Diagram of Inter-VPLMN with GLR roaming showing three HPLMNs (A, B, C) connected to two VPLMNs (a, b). MS-a is shown moving from HPLMN A to VPLMN b. Arrows indicate Subscriber Data, Location Update, and Cancel Location messages.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +The diagram illustrates Inter-VPLMN with GLR roaming. At the top, three Home PLMNs (HPLMN A, B, and C) are shown, each containing an HLR. These HLRs are connected to two Visited PLMNs (VPLMN a and b). VPLMN a contains a Gateway RNC (GLR) and two VLR/SGSN units. VPLMN b also contains a GLR and two VLR/SGSN units. MS-a is shown moving from HPLMN A to VPLMN b. The legend indicates: + + +- Subscriber Data**: Solid thick arrow from HLR to GLR. +- Location Update**: Solid thin arrow from VLR/SGSN to GLR. +- Cancel Location**: Dotted thin arrow from GLR to VLR/SGSN. + + A dashed box represents the old VLR/SGSN, and a solid box represents the new VLR/SGSN. + +Diagram of Inter-VPLMN with GLR roaming showing three HPLMNs (A, B, C) connected to two VPLMNs (a, b). MS-a is shown moving from HPLMN A to VPLMN b. Arrows indicate Subscriber Data, Location Update, and Cancel Location messages. + +Figure 5.5/1: Inter-VPLMN with GLR roaming + +## 5.6 Roaming to VPLMN without GLR from VPLMN with GLR + +In this case the cancel location procedure is handled by HLR and VLR via GLR of old VPLMN. + +![Diagram showing roaming from VPLMN with GLR to VPLMN without GLR. It includes HPLMN A, B, C with HLRs; VPLMN a, b with GLRs and VLR/SGSNs; and VPLMN c without a GLR. Arrows show Subscriber Data, Location Update, and Cancel Location flows between these elements and MS-a.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +The diagram illustrates the network architecture for roaming. At the top, three Home PLMNs (HPLMN A, B, and C) each contain an HLR. Below them, three Visited PLMNs (VPLMN a, b, and c) are shown. VPLMN a and b each contain a GLR and two VLR/SGSN units. VPLMN c does not contain a GLR and has two VLR/SGSN units. A mobile station (MS-a) is shown in VPLMN c. + Legend: + - Solid thick arrow: Subscriber Data + - Solid thin arrow: Location Update + - Dashed thin arrow: Cancel Location + Flows: + - Subscriber Data: From HLRs to GLRs and VLR/SGSNs. + - Location Update: From MS-a in VPLMN c to its VLR/SGSN, then to GLR in VPLMN b, then to HLR in HPLMN C. + - Cancel Location: From HLR in HPLMN C to GLR in VPLMN b, then to VLR/SGSN in VPLMN b, then to VLR/SGSN in VPLMN c. + +Diagram showing roaming from VPLMN with GLR to VPLMN without GLR. It includes HPLMN A, B, C with HLRs; VPLMN a, b with GLRs and VLR/SGSNs; and VPLMN c without a GLR. Arrows show Subscriber Data, Location Update, and Cancel Location flows between these elements and MS-a. + +**Figure 5.6/1: Roaming to VPLMN without GLR from VPLMN with GLR** + +# 6 Logical Network Model + +The GLR is logically located between HLR and VLR as an optional node to optimise inter-network signalling for location management. The overall GLR concept is achieved by the GLR itself, Intermediate-MSC (IM-MSC) and Intermediate-GSN (IM-GSN). The logical network model is shown in figure 6/1. + +![Logical Network Model diagram showing SGSN, VLR/MSC, IM-GSN, GLR, IM-MSC, GGSN, HLR, and Gate node connected within an Other PLMN oval. Legend distinguishes between Signalling Interface (dotted) and Signalling and Data Transfer Interface (solid).](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) + +The logical network model shows the following components and interfaces: + - SGSN and VLR/MSC are at the top. + - SGSN connects to IM-GSN (solid line) and GLR (dotted line). + - VLR/MSC connects to IM-MSC (solid line) and GLR (dotted line). + - IM-GSN connects to GLR (dotted line) and GGSN (solid line). + - IM-MSC connects to GLR (dotted line) and Gate node (solid line). + - All four components (GGSN, HLR, Gate node, and GLR) are located within an oval labeled 'Other PLMN'. + - Inside the oval: GGSN, HLR, and Gate node are connected to GLR via dotted lines. + Legend: + - Dotted line: Signalling Interface + - Solid line: Signalling and Data Transfer Interface + +Logical Network Model diagram showing SGSN, VLR/MSC, IM-GSN, GLR, IM-MSC, GGSN, HLR, and Gate node connected within an Other PLMN oval. Legend distinguishes between Signalling Interface (dotted) and Signalling and Data Transfer Interface (solid). + +**Figure 6/1: GLR Network Model** + +## 6.1 GLR + +The GLR is pseudo-HLR located in visited network. The roamer's information is stored in it and handles location management of it within the network. Presence of GLR is invisible from home network therefore interface between + +HLR and GLR is same as one of HLR and VLR. Also, the interface between the VLR and GLR is the same as the one between the VLR and the HLR. + +The GLR is a logical node and acts as a VLR for MAP signalling (e.g. PRN) from the HPLMN point of view. The GLR acts as a HLR for MAP signalling (e.g. Register SS) from the VPLMN point of view. + +The GLR also acts as an SGSN for MAP signalling only (e.g. ISD) from the HPLMN point of view. This is because MAP operations such as ISD must be terminated at the GLR for the purpose of subscriber data caching. + +The GLR shall terminate all TC dialogues and start new dialogues towards the HLR or the VLR. The GLR shall generate SCCP address of the HLR (i.e. E.214 MGT) from IMSI. + +## 6.2 Intermediate MSC + +The Intermediate MSC (IM-MSC) is the logical node, which represent MSCs in the visited network. Some service features use the MSC Number stored in the HLR directly to deliver message from a certain node in home network (e.g. SMS-GMSC) to serving MSC in visited network. In such case, the message is firstly distributed to representative MSC (i.e., IM-MSC) and it relays it to actual serving MSC interrogating routing information to GLR. + +- The Intermediate MSC (IM-MSC) is a logical node and represents the VMSC in the GLR equipped VPLMN. +- The IM-MSC acts as the VMSC for the HPLMN in the same way that the GLR acts as a VLR for HPLMN. The IM-MSC terminates MAP signalling from the HPLMN towards the VMSC and forwards the signal to the actual VMSC. +- The IM-MSC has an address interrogation function with which it is able to obtain the actual VMSC Number from the GLR. +- The IM-MSC is implemented in the same physical node as the one in which the GLR is implemented. +- The GLR alters the VMSC Number to the IM-MSC Number within an Update Location message. +- The IM-MSC Number is the E.164 Number assigned to the IM-MSC. +- The interrogation function of the IM-MSC is similar to that in the SMS-GMSC. + +## 6.3 Intermediate GSN + +The Intermediate GSN (IM-GSN) is a logical node and represents the SGSN for some GTP signalling termination in a GLR equipped VPLMN. + +The IM-GSN acts as an SGSN for **only some GTP signalling messages** (i.e. PDU\_Notification request/response, PDU\_Notification\_reject request/response) from the HPLMN. The IM-GSN terminates these GTP signalling messages from the HPLMN towards SGSN and forwards the signal to the actual SGSN. The IM-GSN has an address interrogation function with which it is able to request the actual SGSN address from the GLR. + +Apart from the case described above (i.e. PDU\_Notification request/response, PDU\_Notification\_reject request/response), all other GTP signalling should be handled directly between the SGSN and the GGSN. + +NOTE: **MAP signalling** towards the SGSN is **NOT** terminated at the IM-GSN. Instead it is terminated at the GLR. + +## 6.4 Gate Node + +The Gate Node represents a GMSC, GMLC or SMS-GMSC. + +# --- 7 Functional Description + +## 7.1 Logical Functions + +This subclause gives the logical functions performed within the GLR. + +### 7.1.1 Message Relay Function + +This function is used for the exchange of MAP operation between HLR and VLR/SGSN via GLR. When a message is received from VLR or SGSN, the GLR identifies the relevant HLR using appropriate logic, and vice versa. + +### 7.1.2 Address Conversion Function + +The Address Conversion function in the GLR is performed when the GLR receives the Update Location message from the VLR or the Update GPRS Location message from the SGSN, and the HLR updating is required. The GLR will convert visited node addresses as follows: + +- VLR Number converts to the GLR Number. +- MSC Number converts to the IM- MSC Number. +- SGSN Number converts to the GLR Number. +- SGSN Address converts to the IM-GSN Address. + +The converted numbers are sent to the HLR with the Update Location message or Update GPRS message. The HLR stores these addresses as the location information. The HLR uses the GLR Number as the destination address of the messages to VLR and SGSN (e.g., Insert Subscriber Data) and the messages are actually routed to the GLR. The IM- MSC Number is sent to e.g., the SMS-GMSC with a Send Routing Info for Short Message ack message as a destination address to the MSC and the SMS-GMSC uses the IM- MSC Number as the destination address of a Forward Short Message. The IM-GSN Address is sent to the GGSN with Send Routing Info for GPRS ack message and used as the destination address of PDU Notification message. + +According to this scheme, the actual visited node addresses would be stored only in the GLR. The GLR can hide second and further UL messages towards the HLR. Consequently inter-PLMN signalling will be reduced. + +The address conversion function in the GLR is performed also when the GLR receives any messages that include the HLR Number from the HLR. The GLR will modify the HLR Number as follows. + +- HLR Number converts to the GLR Number. + +The GLR Number is sent to the VLR or SGSN with the same message received from HLR. The VLR or SGSN stores the GLR Number as the HLR number. + +### 7.1.3 Subscriber Information Caching Function + +This function is to store the subscriber's information, which is obtained from HLR during location updating procedure. When the HLR send *Insert Subscriber Data* message to VLR and/or SGSN via GLR for the location update, the subscriber information is also stored in the GLR and kept until it receives *Cancel Location* message from HLR. The stored information is used for HLR emulation Function. + +### 7.1.4 Subscriber Information Cancellation Function + +This function is to delete subscriber information stored in GLR and also in VLR and SGSN as requested from HLR or from Location Updating Screening Function in the GLR. + +### 7.1.5 HLR emulation Function + +This function is to handle the location management procedure only within the visited network. When it is decided that the request of location update can be handled at the GLR without involving HLR by Location Updating Screening Function, this function is invoked and GLR acts like the HLR of the subscriber. + +### 7.1.6 Location Updating Screening Function + +This function is used to judge, whether requested location updating is necessary to be indicated to HLR or not. When the GLR has the IMSI record, the GLR may not indicate the location updating to HLR and HLR emulation function is invoked. However, even though the GLR stores the IMSI record, the update location has to be indicated to HLR in some cases. The detail procedures of the cases are shown below. + +### 7.1.7 Routeing Information Providing Function + +This function is used to provide routeing information to the Intermediate MSC and the Intermediate GSN. + +An Address Interrogation function is located within the IM- MSC, IM-GSN and GLR. The IM- MSC, IM-GSN and GLR need the actual visited node address when they need to forward messages to the actual visited node. The IM- MSC and IM-GSN interrogate the GLR to obtain these actual visited node addresses. The GLR holds the actual visited node address internally. + +### 7.1.8 Regional Restriction and Unsupported Services handling Function + +This function is used to handle the regional restriction indication or unsupported service indication in Insert Subscriber Data ack message. When the GLR receives the indication, the GLR initiates the location updating procedure toward the HLR. And later, when the user returns to an MSC/SGSN area that is not restricted due to regional subscription or an area that supports the services subscribed, the GLR identifies the need to notify the HLR of the return. Therefore the location updating procedure is initiated toward the HLR for this handling. + +### 7.1.9 Super Charger function + +This function is used handle the location management procedure from the serving node (i.e. VLR or SGSN) which supports the Super-Charger features. This is basically the same as the Super-Charged HLR. (Refer to 3G TS 23.116 [9]) Followings are supplementary explanation for the GLR behaviour as Super-Charged HLR: + +- When the subscription data is updated by insert subscriber data procedure from the HLR, the GLR shall update the age indicator to reflect the change of the subscription data and sends the subscription data to the serving node identified by the GLR. + +If the GLR receives location registration request from the Super-Charged serving node and has no subscription data for the user, whatever the content of the age indicator in the request is, when the GLR receives the subscription data from the HLR, it relays the data to the serving node. + +## 7.2 Circuit Switched Service + +### 7.2.1 Location Management Procedures + +[Editor's Note: This section may be modified after the finalising of restructuring of 3G TS 23.012 [3] and section 19 of 3G TS 29.002 [10].] + +#### 7.2.1.1 Location Updating Procedure + +In case of first location updating procedure in the network that introduces the GLR, this procedure is handled by HLR and VLR via GLR. For the second and further location updating, HLR is no longer involved with the procedure. The distinction of those two cases is controlled by GLR so that HLR and VLR is not necessary to be conscious of the difference. + +##### 7.2.1.1.1 First Location Updating Procedure + +The first location updating procedure in a network is illustrated in figure 7.2/1. Each step is explained in the following list. + +![Sequence diagram of the First Location Updating Procedure in the Network. The diagram shows interactions between a VLR and GLR in the Visited NW, and an HLR in the Home NW. The sequence of messages is: 1. Update Location (VLR to GLR), 1. Update Location (GLR to HLR), 2. Insert Subscriber Data (HLR to GLR), 2. Insert Subscriber Data (GLR to VLR), 2. Insert Subscriber Data ack (VLR to GLR), 2. Insert Subscriber Data ack (GLR to HLR), 3. Update Location ack (HLR to GLR), 3. Update Location ack (GLR to VLR).](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` +sequenceDiagram + participant VLR + participant GLR + participant HLR + Note over VLR, GLR: Visited NW + Note over HLR: Home NW + VLR->>GLR: 1. Update Location + GLR->>HLR: 1. Update Location + HLR->>GLR: 2. Insert Subscriber Data + GLR->>VLR: 2. Insert Subscriber Data + VLR->>GLR: 2. Insert Subscriber Data ack + GLR->>HLR: 2. Insert Subscriber Data ack + HLR->>GLR: 3. Update Location ack + GLR->>VLR: 3. Update Location ack +``` + +Sequence diagram of the First Location Updating Procedure in the Network. The diagram shows interactions between a VLR and GLR in the Visited NW, and an HLR in the Home NW. The sequence of messages is: 1. Update Location (VLR to GLR), 1. Update Location (GLR to HLR), 2. Insert Subscriber Data (HLR to GLR), 2. Insert Subscriber Data (GLR to VLR), 2. Insert Subscriber Data ack (VLR to GLR), 2. Insert Subscriber Data ack (GLR to HLR), 3. Update Location ack (HLR to GLR), 3. Update Location ack (GLR to VLR). + +**Figure 7.2/1: First Location Updating Procedure in the Network** + +###### Procedure: + +- 1) When the GLR receives an *Update Location* message from a VLR and does not hold the subscriber's information for the user (i.e. at first location updating to the GLR), the GLR: + - stores the VLR Number and serving MSC Number included in the received message, and + - sends an *Update Location* message to the HLR with the GLR Number as *VLR Number*, and IM-MSC Number as *MSC Number*. +- 2) The HLR stores the GLR Number and IM-MSC Number from received message as respectively VLR Number and serving MSC Number. Thereafter the HLR initiates insert subscriber data procedure and cancel location procedure. When the GLR receives *Insert Subscriber Data* message from the HLR, the GLR stores the subscriber's information in the message and transport it to the VLR. +- 3) After these procedures, the HLR replies to an *Update Location* message from the GLR and the GLR transports the response to the VLR. + +##### 7.2.1.1.2 Second and further Location Updating Procedure + +The second and further location updating procedure in the network is illustrated in figure 7.2/2. Each step is explained in the following list. + +![Sequence diagram illustrating the Second and further Location Updating Procedure. The diagram shows interactions between VLR_OLD, VLR_NEW, GLR (all under Visited NW) and HLR (under Home NW).](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +``` + +sequenceDiagram + participant VLR_NEW + participant GLR + participant HLR + Note left of VLR_NEW: Visited NW + Note right of HLR: Home NW + VLR_NEW->>GLR: 1. Update Location + GLR->>VLR_OLD: 2. Cancel Location + VLR_OLD->>GLR: 2. Cancel Location ack + GLR->>VLR_NEW: 3. Insert Subscriber Data + VLR_NEW->>GLR: 3. Insert Subscriber Data ack + GLR->>VLR_NEW: 4. Update Location ack + +``` + +Sequence diagram illustrating the Second and further Location Updating Procedure. The diagram shows interactions between VLR\_OLD, VLR\_NEW, GLR (all under Visited NW) and HLR (under Home NW). + +**Figure 7.2/2: Second and further Location Updating Procedure in the Network** + +###### Procedure: + +- 1) When the GLR receives an *Update Location* message from newly visited VLR and holds the subscriber information for the user (i.e. at second or further location updating to the GLR), the GLR stores the new VLR Number and new serving MSC Number included in the received message. +- 2) Thereafter the GLR initiates insert subscriber data procedure and cancel location procedure. +- 3) After these procedures, the GLR replies to an *Update Location* message from the VLR. + +##### 7.2.1.1.3 Functional requirements of GLR + +###### 7.2.1.1.3.1 Process Update\_Location\_GLR + +Figure 7.2/3 shows SDL chart for Process Update\_Location\_GLR. + +Sheet1: the test "HLR update required?" takes the "yes" exit the GLR checks some flags (ex. CCBS mon. flag) to perform the "Location Updating Screening Function (see to section 7.1.6)" and if it is needed to update location information to the HLR. + +Sheet1: CCBS\_Status\_Report\_GLR procedure is called only if Alternative 2 for CCBS is performed in GLR. + +Sheet2: after the GLR sends an Update Location message to the HLR, the GLR receives the response with: + +- an Insert Subscriber Data message handled by the procedure Insert\_Subscriber\_Data\_GLR. +- a Forward Check SS indication message. This message will be relayed to the VLR without any change of the current state. +- an Update Location ack message. If the GLR receives this message, this indicates that updating has been successfully completed. The GLR sets the "(Location and Subscriber information) LSIC by HLR" indicator to "Confirmed". The GLR send an Update Location ack message to the VLR. +- an Update Location negative response message. If the GLR receives this message, this indicates that updating has been unsuccessfully completed. The GLR sets the "(Location and Subscriber information) LSIC by HLR" indicator to "False". The GLR sends an Update Location negative to the VLR. + +Sheet1: process Cancel\_Location\_Initiated\_GLR is specified in subclause 7.2.1.2.1.2. + +Sheet5: CCBS\_Start\_Report\_GLR procedure is called only if Alternative 2 for CCBS performed in GLR. + +![Flowchart for Process Update_Location_GLR. It starts with an Idle state, followed by an Update Location request. A 'Check Parameter' step is performed, referencing TS 23.018. A decision 'Result=Pass' follows. If 'No', it goes to 'Set negative response: Unknown Subscriber' and then 'Update Location negative response' to Idle. If 'Yes', it checks 'subscriber known in GLR'. If 'No', it goes to 'Set GLR Number as VLR Number', 'Set IM-MSC Number as MSC Number', 'Update Location', and 'Wait_For_Data'. If 'Yes', it checks 'Network access mode = GPRS only'. If 'Yes', it goes to 'Set negative response: Unknown Subscriber'. If 'No', it checks 'HLR update required?'. If 'Yes', it goes to 'Set GLR Number as VLR Number'. If 'No', it checks 'New VLR?'. If 'Yes', it goes to 'Super_Charged_Cancel_Location_GLR', then 'Result=Pass?'. If 'Yes', it goes to 'CCBS_status_report_GLR' and then connector '1'. If 'No', it goes to 'Cancel_Location_Initiated_GLR' and then connector '1'. If 'No' for 'New VLR?', it goes to 'Set GLR Number as VLR Number'.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +### Process Update\_Location\_GLR + +1(7) + +Process in the GLR to handle an Update Location request and trigger the correct application process + +Signales to/from the left are to/from the VLR +Signales to/from the right are to/from the HLR + +``` +graph TD; Start([Idle]) --> UL{Update Location}; UL --> CP[Check Parameter]; CP --- TS[See TS 23.018]; CP --> RP{Result=Pass}; RP -- No --> SNR[Set negative response: Unknown Subscriber]; SNR --> ULNR{Update Location negative response}; ULNR --> Idle1([Idle]); RP -- Yes --> SK{subscriber known in GLR}; SK -- No --> SG[Set GLR Number as VLR Number]; SK -- Yes --> NAM{Network access mode = GPRS only}; NAM -- Yes --> SNR; NAM -- No --> HU{HLR update required?}; HU -- Yes --> SG; HU -- No --> NV{New VLR?}; NV -- Yes --> SC[Super_Charged_Cancel_Location_GLR]; SC --> RP2{Result=Pass?}; RP2 -- Yes --> CS[CCBS_status_report_GLR]; CS --> C1((1)); RP2 -- No --> CL[Cancel_Location_Initiated_GLR]; CL --> C1; NV -- No --> SG; SG --> SIM[Set IM-MSC Number as MSC Number]; SIM --> UL2{Update Location}; UL2 --> WFD[Wait_For_Data]; +``` + +Flowchart for Process Update\_Location\_GLR. It starts with an Idle state, followed by an Update Location request. A 'Check Parameter' step is performed, referencing TS 23.018. A decision 'Result=Pass' follows. If 'No', it goes to 'Set negative response: Unknown Subscriber' and then 'Update Location negative response' to Idle. If 'Yes', it checks 'subscriber known in GLR'. If 'No', it goes to 'Set GLR Number as VLR Number', 'Set IM-MSC Number as MSC Number', 'Update Location', and 'Wait\_For\_Data'. If 'Yes', it checks 'Network access mode = GPRS only'. If 'Yes', it goes to 'Set negative response: Unknown Subscriber'. If 'No', it checks 'HLR update required?'. If 'Yes', it goes to 'Set GLR Number as VLR Number'. If 'No', it checks 'New VLR?'. If 'Yes', it goes to 'Super\_Charged\_Cancel\_Location\_GLR', then 'Result=Pass?'. If 'Yes', it goes to 'CCBS\_status\_report\_GLR' and then connector '1'. If 'No', it goes to 'Cancel\_Location\_Initiated\_GLR' and then connector '1'. If 'No' for 'New VLR?', it goes to 'Set GLR Number as VLR Number'. + +Figure 7.2/3(1): Process Update\_Location\_GLR + +![](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +### Process Update\_Location\_GLR + +2(7) + +Process in the GLR to handle an Update Location request and trigger the correct application process + +Signales to/from the left are to/from the VLR + Signales to/from the right are to/from the HLR + + + +``` + + graph TD + Wait_For_Data([Wait_For_Data]) + + %% Branch 1 + Wait_For_Data --> ISD_In[/Insert Subscriber Data/] + ISD_In --> ISD_GLR[Insert_Subscriber_Data_GLR] + ISD_GLR --> Wait_HLR_VLR([Wait_For_Data_from_HLR_and_ISD_ack_from_VLR]) + + %% Branch 2 + Wait_For_Data --> FCSS_In[/Forward Check SS indication/] + FCSS_In --> FCSS_Out[["Forward Check SS indicator"]] + FCSS_Out --> Wait_For_Data + + %% Branch 3 + Wait_For_Data --> UL_Ack_In[/Update Location ack/] + UL_Ack_In --> Res_Pass[Result:=Pass] + Res_Pass --> LSIC_Conf["LSIC by HLR :=Confirmed"] + LSIC_Conf --> Set_GLR["Set GLR Number as HLR Number"] + Set_GLR --> UL_Ack_Out[["Update Location ack"]] + UL_Ack_Out --> Idle1([Idle]) + + %% Branch 4 + Wait_For_Data --> UL_Neg_In[/Update Location negative response/] + UL_Neg_In --> Fail_Case{Failure Case?} + + Fail_Case -- Roaming Not Allowed --> Res_Roam[Result:= Roaming Not Allowed] + Fail_Case -- Unknown Subscriber --> Res_Unk[Result:= Unknown Subscriber] + Fail_Case -- Procedure Error --> Res_Err[Result:= Procedure Error] + + Res_Roam --> Del_Sub1[Delete Subscriber Data] + Res_Unk --> Del_Sub2[Delete Subscriber Data] + + Del_Sub1 --> LSIC_False + Del_Sub2 --> LSIC_False + Res_Err --> LSIC_False["LSIC by HLR :=False"] + + LSIC_False --> UL_Neg_Out[["Update Location negative response"]] + UL_Neg_Out --> Idle2([Idle]) + + %% Branch 5 + Wait_For_Data --> Abort_In[/Abort/] + Abort_In --> Abort_Out[["Abort"]] + Abort_Out --> Idle3([Idle]) + +``` + +**Figure 7.2/3(2): Process Update\_Location\_GLR** + +![Flowchart for Process Update_Location_GLR. It starts with 'Wait_For_Data_from_HLR_and_ISD_ack_from_VLR'. It branches into five paths: 1) Insert Subscriber Data -> Insert_Subscriber_Data_GLR -> Wait_For_Data_from_HLR_and_ISD_ack_from_VLR. 2) Forward Check SS indication -> Forward Check SS indicator -> Wait_For_Data_from_HLR_and_ISD_ack_from_VLR. 3) Update Location ack -> Result:=Pass -> LSIC by HLR :=Confirmed -> Set GLR Number as HLR Number -> Update Location ack -> Idle. 4) Update Location negative response -> Failure Case? -> (Roaming Not Allowed: Result:=Roaming Not Allowed -> Delete Subscriber Data) or (Unknown Subscriber: Result:=Unknown Subscriber -> Delete Subscriber Data) or (Procedure Error: Result:=Procedure Error) -> LSIC by HLR :=False -> Update Location negative response -> Idle. 5) Abort -> Abort -> Idle.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +### Process Update\_Location\_GLR + +3(7) + +Process in the GLR to handle an Update Location request and trigger the correct application process + +Signales to/from the left are to/from the VLR +Signales to/from the right are to/from the HLR + +``` +graph TD; Start([Wait_For_Data_from_HLR_and_ISD_ack_from_VLR]) --> Branch1[Insert Subscriber Data]; Start --> Branch2[Forward Check SS indication]; Start --> Branch3[Update Location ack]; Start --> Branch4[Update Location negative response]; Start --> Branch5[Abort]; Branch1 --> Step1[Insert_Subscriber_Data_GLR]; Step1 --> End1([Wait_For_Data_from_HLR_and_ISD_ack_from_VLR]); Branch2 --> Step2[Forward Check SS indicator]; Step2 --> End2([Wait_For_Data_from_HLR_and_ISD_ack_from_VLR]); Branch3 --> Step3[Result:=Pass]; Step3 --> Step4[LSIC by HLR :=Confirmed]; Step4 --> Step5[Set GLR Number as HLR Number]; Step5 --> Step6[Update Location ack]; Step6 --> End3([Idle]); Branch4 --> Decision1{Failure Case?}; Decision1 -- Roaming Not Allowed --> Step7[Result:=Roaming Not Allowed]; Decision1 -- Unknown Subscriber --> Step8[Result:=Unknown Subscriber]; Decision1 -- Procedure Error --> Step9[Result:=Procedure Error]; Step7 --> Step10[Delete Subscriber Data]; Step8 --> Step11[Delete Subscriber Data]; Step9 --> Step12[LSIC by HLR :=False]; Step10 --> Step12; Step11 --> Step12; Step12 --> Step13[Update Location negative response]; Step13 --> End4([Idle]); Branch5 --> Step14[Abort]; Step14 --> End5([Idle]); +``` + +Flowchart for Process Update\_Location\_GLR. It starts with 'Wait\_For\_Data\_from\_HLR\_and\_ISD\_ack\_from\_VLR'. It branches into five paths: 1) Insert Subscriber Data -> Insert\_Subscriber\_Data\_GLR -> Wait\_For\_Data\_from\_HLR\_and\_ISD\_ack\_from\_VLR. 2) Forward Check SS indication -> Forward Check SS indicator -> Wait\_For\_Data\_from\_HLR\_and\_ISD\_ack\_from\_VLR. 3) Update Location ack -> Result:=Pass -> LSIC by HLR :=Confirmed -> Set GLR Number as HLR Number -> Update Location ack -> Idle. 4) Update Location negative response -> Failure Case? -> (Roaming Not Allowed: Result:=Roaming Not Allowed -> Delete Subscriber Data) or (Unknown Subscriber: Result:=Unknown Subscriber -> Delete Subscriber Data) or (Procedure Error: Result:=Procedure Error) -> LSIC by HLR :=False -> Update Location negative response -> Idle. 5) Abort -> Abort -> Idle. + +Figure 7.2/3(3): Process Update\_Location\_GLR + +![Flowchart for Process Update_Location_GLR. The process starts with a 'Wait_For_Data_from_HLR_and_ISD_ack_from_VLR' state. It then branches to 'Insert Subscriber Data ack' and 'Insert Subscriber Data negative response'. The 'ack' path leads to a decision 'All received feature & service supported?'. If 'Yes', it goes to 'Update Subscriber Data'. If 'No', it goes to 'Update subscriber data for supported features' and 'set parameters for unsupported features'. Both lead to a decision 'MSC area restricted by regional subscription?'. If 'Yes', it goes to 'Set MSC area restricted'. Both 'No' and 'Set MSC area restricted' lead to 'Insert Subscriber Data ack', which returns to the initial 'Wait' state. The 'negative response' path leads to 'Insert Subscriber Data negative response' and then back to the initial 'Wait' state.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +### Process Update\_Location\_GLR + +4(7) + +Process in the GLR to handle an Update Location request and trigger the correct application process + +Signals to/from the left are to/from the VLR +Signals to/from the right are to/from the HLR + +``` +graph TD; Start((Wait_For_Data_from_HLR_and_ISD_ack_from_VLR)) --> InsertAck{Insert Subscriber Data ack}; Start --> InsertNeg{Insert Subscriber Data negative response}; InsertAck --> AllSupported{All received feature & service supported?}; AllSupported -- Yes --> UpdateSub[Update Subscriber Data]; AllSupported -- No --> UpdateSubData[Update subscriber data for supported features]; UpdateSubData --> SetParams[set parameters for unsupported features]; UpdateSub --> MSCRestricted{MSC area restricted by regional subscription?}; SetParams --> MSCRestricted; MSCRestricted -- Yes --> SetMSC[Set MSC area restricted]; MSCRestricted -- No --> InsertSubAck{Insert Subscriber Data ack}; SetMSC --> InsertSubAck; InsertSubAck --> Start; InsertNeg --> InsertSubNeg[Insert Subscriber Data negative response]; InsertSubNeg --> Start; +``` + +Flowchart for Process Update\_Location\_GLR. The process starts with a 'Wait\_For\_Data\_from\_HLR\_and\_ISD\_ack\_from\_VLR' state. It then branches to 'Insert Subscriber Data ack' and 'Insert Subscriber Data negative response'. The 'ack' path leads to a decision 'All received feature & service supported?'. If 'Yes', it goes to 'Update Subscriber Data'. If 'No', it goes to 'Update subscriber data for supported features' and 'set parameters for unsupported features'. Both lead to a decision 'MSC area restricted by regional subscription?'. If 'Yes', it goes to 'Set MSC area restricted'. Both 'No' and 'Set MSC area restricted' lead to 'Insert Subscriber Data ack', which returns to the initial 'Wait' state. The 'negative response' path leads to 'Insert Subscriber Data negative response' and then back to the initial 'Wait' state. + +Figure 7.2/3(4): Process Update\_Location\_GLR + +![Flowchart for Process Update_Location_GLR. The process starts at connector 1, leading to Super_Charged_Location_Updating_GLR. A decision 'Result = Pass?' follows. If 'Yes', it goes to 'Update Location ack' and then 'Idle'. If 'No', it goes to 'ISD_GLR'. From 'ISD_GLR', a decision 'Result = Pass?' follows. If 'Yes', it checks 'MSC Area Restricted? OR Roaming Restricted Due to Unsupported Feature?'. If 'Yes', it goes to 'Idle'. If 'No', it goes to 'Subscriber_Present_GLR'. From 'Subscriber_Present_GLR', a decision 'Check_SS_Required?' follows. If 'True', it goes to 'Forward CheckSS Indication' and then 'Check_SS_Required := False'. If 'False', it proceeds to a decision 'Changed supported services?'. If 'Yes', it goes to 'Set GLR Number as VLR Number', then 'Set IM-MSC Number as MSC Number', then 'Update Location', and finally 'Wait_For_information'. If 'No', it goes to a decision 'Changed MSC area restricted'. If 'Yes', it goes to 'Changed MSC area restricted'. If 'No', it goes to 'Update Location ack', then 'CCBS_start_report_GLR', and finally 'Idle'. From the second 'Result = Pass?' after 'ISD_GLR', if 'No', it goes to 'Result = Aborted?'. If 'Yes', it goes to 'Idle'. If 'No', it goes to 'Update Location negative response' and then 'Idle'.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +**Process Update\_Location\_GLR** 5(7) + +Process in the GLR to handle an Update Location request and trigger the correct application process + +Signales to/from the left are to/from the VLR +Signales to/from the right are to/from the HLR + +``` + +graph TD + 1((1)) --> Super_Charged_Location_Updating_GLR[Super_Charged_Location_Updating_GLR] + Super_Charged_Location_Updating_GLR --> Result_Pass_1{Result = Pass?} + Result_Pass_1 -- Yes --> Update_Location_ack_1[Update Location ack] + Update_Location_ack_1 --> Idle_1([Idle]) + Result_Pass_1 -- No --> ISD_GLR[ISD_GLR] + ISD_GLR --> Result_Pass_2{Result = Pass?} + Result_Pass_2 -- Yes --> MSC_Area_Restricted{MSC Area Restricted? +OR +Roaming Restricted Due to Unsupported Feature?} + MSC_Area_Restricted -- Yes --> Idle_2([Idle]) + MSC_Area_Restricted -- No --> Subscriber_Present_GLR[Subscriber_Present_GLR] + Subscriber_Present_GLR --> Check_SS_Required{Check_SS_Required?} + Check_SS_Required -- True --> Forward_CheckSS_Indication[Forward CheckSS Indication] + Forward_CheckSS_Indication --> Check_SS_Required_False[Check_SS_Required := False] + Check_SS_Required -- False --> Changed_supported_services{Changed supported services?} + Changed_supported_services -- Yes --> Set_GLR_Number[Set GLR Number as VLR Number] + Set_GLR_Number --> Set_IM_MSC_Number[Set IM-MSC Number as MSC Number] + Set_IM_MSC_Number --> Update_Location[Update Location] + Update_Location --> Wait_For_information([Wait_For_information]) + Changed_supported_services -- No --> Changed_MSC_area_restricted{Changed MSC area restricted?} + Changed_MSC_area_restricted -- Yes --> Changed_MSC_area_restricted_text[Changed MSC area restricted] + Changed_MSC_area_restricted -- No --> Update_Location_ack_2[Update Location ack] + Update_Location_ack_2 --> CCBS_start_report_GLR[CCBS_start_report_GLR] + CCBS_start_report_GLR --> Idle_3([Idle]) + Result_Pass_2 -- No --> Result_Aborted{Result = Aborted?} + Result_Aborted -- Yes --> Idle_4([Idle]) + Result_Aborted -- No --> Update_Location_negative_response[Update Location negative response] + Update_Location_negative_response --> Idle_5([Idle]) + +``` + +Flowchart for Process Update\_Location\_GLR. The process starts at connector 1, leading to Super\_Charged\_Location\_Updating\_GLR. A decision 'Result = Pass?' follows. If 'Yes', it goes to 'Update Location ack' and then 'Idle'. If 'No', it goes to 'ISD\_GLR'. From 'ISD\_GLR', a decision 'Result = Pass?' follows. If 'Yes', it checks 'MSC Area Restricted? OR Roaming Restricted Due to Unsupported Feature?'. If 'Yes', it goes to 'Idle'. If 'No', it goes to 'Subscriber\_Present\_GLR'. From 'Subscriber\_Present\_GLR', a decision 'Check\_SS\_Required?' follows. If 'True', it goes to 'Forward CheckSS Indication' and then 'Check\_SS\_Required := False'. If 'False', it proceeds to a decision 'Changed supported services?'. If 'Yes', it goes to 'Set GLR Number as VLR Number', then 'Set IM-MSC Number as MSC Number', then 'Update Location', and finally 'Wait\_For\_information'. If 'No', it goes to a decision 'Changed MSC area restricted'. If 'Yes', it goes to 'Changed MSC area restricted'. If 'No', it goes to 'Update Location ack', then 'CCBS\_start\_report\_GLR', and finally 'Idle'. From the second 'Result = Pass?' after 'ISD\_GLR', if 'No', it goes to 'Result = Aborted?'. If 'Yes', it goes to 'Idle'. If 'No', it goes to 'Update Location negative response' and then 'Idle'. + +Figure 7.2/3(5): Process Update\_Location\_GLR + +![Flowchart for Process Update_Location_GLR. It starts with 'Wait_For_Information' and branches into five main paths: 1. Insert Subscriber Data (leads to connector 2); 2. Forward Check SS indication (leads to 'Forward Check SS indication' decision, then 'Wait_For_information', then 'LSIC by HLR :=True', 'Set GLR Number as HLR Number', 'Update Location ack', and 'Idle'); 3. Update Location ack (leads to 'Result:= Pass', then 'LSIC by HLR :=True', 'Set GLR Number as HLR Number', 'Update Location ack', and 'Idle'); 4. Update Location negative response (leads to 'Failure case?' decision); 5. Abort (leads to 'Abort' decision and 'Idle'). The 'Failure case?' decision branches into 'Roaming not Allowed' (Result:= Roaming Not Allowed, Delete Subscriber Data), 'Unknown Subscriber' (Result:= Unknown Subscriber, Delete Subscriber Data), and 'Procedure Error' (Result:= Procedure Error). All three failure paths lead to 'LSIC by HLR :=False', 'Update Location negative response', and 'Idle'.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +### Process Update\_Location\_GLR + +6(7) + +Process in the GLR to handle an Update Location request and trigger the correct application process + +Signales to/from the left are to/from the VLR +Signales to/from the right are to/from the HLR + +``` +graph TD; Start([Wait_For_Information]) --> Insert[Insert Subscriber Data]; Insert --> C2((2)); Start --> FCSI{Forward Check SS indication}; FCSI --> WFI([Wait_For_information]); WFI --> LSIC_T[LSIC by HLR :=True]; LSIC_T --> SetGLR[Set GLR Number as HLR Number]; SetGLR --> ULA1[Update Location ack]; ULA1 --> Idle1([Idle]); Start --> ULA2{Update Location ack}; ULA2 --> ResPass[Result:= Pass]; ResPass --> LSIC_T; Start --> ULNR{Update Location negative response}; ULNR --> FC{Failure case?}; FC -- Roaming not Allowed --> ResR[Result:= Roaming Not Allowed]; ResR --> DelR[Delete Subscriber Data]; FC -- Unknown Subscriber --> ResU[Result:= Unknown Subscriber]; ResU --> DelU[Delete Subscriber Data]; FC -- Procedure Error --> ResP[Result:= Procedure Error]; DelR --> LSIC_F[LSIC by HLR :=False]; DelU --> LSIC_F; ResP --> LSIC_F; LSIC_F --> ULNR2{Update Location negative response}; ULNR2 --> Idle2([Idle]); Start --> Abort1{Abort}; Abort1 --> Idle3([Idle]); +``` + +Flowchart for Process Update\_Location\_GLR. It starts with 'Wait\_For\_Information' and branches into five main paths: 1. Insert Subscriber Data (leads to connector 2); 2. Forward Check SS indication (leads to 'Forward Check SS indication' decision, then 'Wait\_For\_information', then 'LSIC by HLR :=True', 'Set GLR Number as HLR Number', 'Update Location ack', and 'Idle'); 3. Update Location ack (leads to 'Result:= Pass', then 'LSIC by HLR :=True', 'Set GLR Number as HLR Number', 'Update Location ack', and 'Idle'); 4. Update Location negative response (leads to 'Failure case?' decision); 5. Abort (leads to 'Abort' decision and 'Idle'). The 'Failure case?' decision branches into 'Roaming not Allowed' (Result:= Roaming Not Allowed, Delete Subscriber Data), 'Unknown Subscriber' (Result:= Unknown Subscriber, Delete Subscriber Data), and 'Procedure Error' (Result:= Procedure Error). All three failure paths lead to 'LSIC by HLR :=False', 'Update Location negative response', and 'Idle'. + +Figure 7.2/3(6): Process Update\_Location\_GLR + +![Flowchart for Process Update_Location_GLR. It starts with connector '2', followed by 'Check Parameter' (referencing TS 23.018). A decision 'Result= Pass?' leads to 'Subscriber known?'. If 'No' at either decision, it goes to 'Insert Subscriber Data negative response' and then 'Idle'. If 'Yes' to 'Subscriber known?', it checks 'All received features & services supported?'. If 'No', it performs 'Update Subscriber Data for supported features' and 'Set parameters for unsupported features'. If 'Yes', it performs 'Update Subscriber Data'. Both paths lead to a decision 'MSC area restricted by regional subscription?'. If 'Yes', it performs 'Set MSC area restricted'. All paths lead to 'Insert Subscriber Data ack' and finally 'Wait_For_Information'.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +### Process Update\_Location\_GLR + +7(7) + +Process in the GLR to handle an Update Location request and trigger the correct application process + +Signales to/from the left are to/from the VLR +Signales to/from the right are to/from the HLR + +``` + +graph TD + Start((2)) --> CP[Check Parameter] + CP --- TS[See TS 23.018] + CP --> RP{Result= +Pass?} + RP -- No --> ISDN[Insert Subscriber +Data negative +response] + RP -- Yes --> SK{Subscriber +known?} + SK -- No --> ISDN + ISDN --> Idle([Idle]) + SK -- Yes --> AS{All received +features & services +supported?} + AS -- Yes --> USD[Update +Subscriber +Data] + AS -- No --> USDF[Update Subscriber +Data for +supported features] + USDF --> SP[Set parameters +for unsupported +features] + USD --> MAR{MSC area +restricted by +regional subscription?} + SP --> MAR + MAR -- No --> ISDA[Insert Subscriber +Data ack] + MAR -- Yes --> SMAR[Set MSC area +restricted] + SMAR --> ISDA + ISDA --> WFI([Wait_For_ +Information]) + +``` + +Flowchart for Process Update\_Location\_GLR. It starts with connector '2', followed by 'Check Parameter' (referencing TS 23.018). A decision 'Result= Pass?' leads to 'Subscriber known?'. If 'No' at either decision, it goes to 'Insert Subscriber Data negative response' and then 'Idle'. If 'Yes' to 'Subscriber known?', it checks 'All received features & services supported?'. If 'No', it performs 'Update Subscriber Data for supported features' and 'Set parameters for unsupported features'. If 'Yes', it performs 'Update Subscriber Data'. Both paths lead to a decision 'MSC area restricted by regional subscription?'. If 'Yes', it performs 'Set MSC area restricted'. All paths lead to 'Insert Subscriber Data ack' and finally 'Wait\_For\_Information'. + +Figure 7.2/3(7): Process Update\_Location\_GLR + +###### 7.2.1.1.3.2 Process Subscriber\_Present\_GLR + +Figure 7.2/4 shows SDL chart for Process Subscriber\_Present\_GLR. + +![SDL chart for Process Subscriber_Present_GLR. It starts with an initial state, leading to a decision diamond 'MNRF Set?'. If 'Yes', it goes to a process box 'Subscriber_Present_GLR_AS_VLR', which is linked to a note 'See TS 29.120 Section 25.4'. If 'No', it bypasses the process box. Both paths lead to a merge point and then to a final state (crossed circle).](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +**Process Subscriber\_Present\_GLR** 1(1) + +Process in the GLR Application to perform actions required for short message alerting + +``` +stateDiagram-v2 + [*] --> MNRF_Set{MNRF Set?} + MNRF_Set --> Subscriber_Present_GLR_AS_VLR[Subscriber_Present_GLR_AS_VLR] : Yes + MNRF_Set --> MergePoint : No + Subscriber_Present_GLR_AS_VLR --> MergePoint + MergePoint --> [*] +``` + +SDL chart for Process Subscriber\_Present\_GLR. It starts with an initial state, leading to a decision diamond 'MNRF Set?'. If 'Yes', it goes to a process box 'Subscriber\_Present\_GLR\_AS\_VLR', which is linked to a note 'See TS 29.120 Section 25.4'. If 'No', it bypasses the process box. Both paths lead to a merge point and then to a final state (crossed circle). + +Figure 7.2/4: Process Subscriber\_Present\_GLR + +###### 7.2.1.1.3.3 Procedure Insert\_Subscriber\_Data\_GLR + +Figure 7.2/5 shows SDL chart for Procedure Insert\_Subscriber\_Data\_GLR. This procedure is initiated by receiving Insert Subscriber Data from the HLR. This procedure is used by Process Update\_Location\_GLR and Process Update\_GPRS\_Location\_GLR. + +![SDL diagram for Procedure Insert_Subscriber_Data_GLR](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +**Procedure Insert\_Subscriber\_Data\_GLR** 1(1) + +Procedure to receive and store subscriber data in the GLR + +``` +graph TD; Start([ ]) --> Check[Check Parameter]; Check --- Note1[See TS 23.018]; Check --> Result{Result=Pass?}; Result -- No --> Negative[Insert Subscriber Data negative response]; Result -- Yes --> Known{Subscriber known?}; Known -- No --> Negative; Known -- Yes --> Store[Store Subscriber Data]; Store --> Insert{Insert Subscriber Data}; Insert --> End(( )); Negative --> End2(( )); +``` + +The diagram is a State Transition Diagram (STD) for the procedure 'Insert\_Subscriber\_Data\_GLR'. It begins with an initial state (oval with two vertical lines). The first transition is to a state 'Check Parameter', which is associated with a note 'See TS 23.018'. From 'Check Parameter', the flow goes to a decision diamond 'Result=Pass?'. If 'No', it proceeds to a state 'Insert Subscriber Data negative response'. If 'Yes', it proceeds to another decision diamond 'Subscriber known?'. If 'No', it also proceeds to 'Insert Subscriber Data negative response'. If 'Yes', it proceeds to a state 'Store Subscriber Data', which then leads to a transition diamond 'Insert Subscriber Data'. Both 'Insert Subscriber Data' and 'Insert Subscriber Data negative response' lead to final states (circles with an 'X'). + +Signals to/from the left are to/from the VLR/SGSN +Signals to/from the right are to/from the HLR + +SDL diagram for Procedure Insert\_Subscriber\_Data\_GLR + +Figure 7.2/5: Procedure Insert\_Subscriber\_Data\_GLR + +###### 7.2.1.1.3.4 + +###### Procedure Insert\_Subscriber\_Data\_Initiated\_GLR + +Figure 7.2/6 shows SDL chart for Procedure Insert\_Subscriber\_Data\_Initiated\_GLR. This procedure is initiated if HLR update is not required. + +![SDL chart for Procedure Insert_Subscriber_Data_Initiated_GLR](088921fa3f5a44c8551815122517eefd_img.jpg) + +**Procedure Insert\_Subscriber\_Data\_Initiated\_GLR** 1(2) + +Procedure in the GLR Application for handling the insertion of subscriber data into the VLR + +Signals to/from the left are to/from the VLR + +``` +stateDiagram-v2 + [*] --> Insert Subscriber Data + Insert Subscriber Data --> Count:=1 + Count:=1 --> More Data To Send? + More Data To Send? -- Yes --> Insert Subscriber Data + More Data To Send? -- No --> Wait_For_ISD_Ack + Insert Subscriber Data --> Count:=Count+1 + Count:=Count+1 --> More Data To Send? + Wait_For_ISD_Ack --> Insert Subscriber Data ack + Wait_For_ISD_Ack --> Abort + Wait_For_ISD_Ack --> Insert Subscriber Data negative response + Insert Subscriber Data ack --> Count:=Count-1 + Count:=Count-1 --> [*] + Abort --> Result:=Aborted + Result:=Aborted --> [*] + Insert Subscriber Data negative response --> Set Negative Response System Failure + Set Negative Response System Failure --> Result:=Fail + Result:=Fail --> [*] +``` + +The diagram is an SDL chart for the procedure 'Insert\_Subscriber\_Data\_Initiated\_GLR'. It begins with an initial state leading to an input state 'Insert Subscriber Data', followed by an action 'Count:=1'. A transition with a circle containing the number '2' leads to a decision state 'More Data To Send?'. If 'Yes', it goes to an input state 'Insert Subscriber Data' followed by an action 'Count:=Count+1', which loops back to the decision. If 'No', it goes to an output state 'Wait\_For\_ISD\_Ack'. From this output state, three transitions lead to: 1) an output state 'Insert Subscriber Data ack' followed by an action 'Count:=Count-1' and a circle containing the number '1'; 2) an output state 'Abort' followed by an action 'Result:=Aborted' and a circle with an 'X'; 3) an output state 'Insert Subscriber Data negative response' followed by an action 'Set Negative Response System Failure', an action 'Result:=Fail', and a circle with an 'X'. + +SDL chart for Procedure Insert\_Subscriber\_Data\_Initiated\_GLR + +Figure7.2/6(1): Procedure Insert\_Subscriber\_Data\_Initiated\_GLR + +![Flowchart for Procedure Insert_Subscriber_Data_Initiated_GLR. It starts at connector 1, checks for unsupported services, handles them (ignore, replace, or critical), checks MSC area restrictions, and ends at connector 2.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +### Procedure Insert\_Subscriber\_Data\_Initiated\_GLR + +2(2) + +Procedure in the GLR Application for handling the insertion of subscriber data into the VLR + +Signals to/from the left are to/from the VLR + +``` +graph TD; 1((1)) --> D1{Any services not supported in VLR?}; D1 -- No --> D4{MSC Area Restricted?}; D1 -- Yes --> D2{Ignore Unsupported Service?}; D2 -- No --> D3{Replace Service in VLR?}; D2 -- Yes --> D4; D3 -- No --> D5{Unsupported Service Critical?}; D3 -- Yes --> P1[Replace Service]; D5 -- No --> P2[GLR Internal Action]; D5 -- Yes --> P3[Roaming Restricted Due To Unsupported Feature=True; MSC Area Restricted=True]; P1 --> 2((2)); P3 --> 2; P2 --> D4; D4 -- Yes --> P4[Set MSC Area Restricted]; D4 -- No --> D6{Count>0?}; P4 --> D6; D6 -- Yes --> P5[Wait_For_ISD_Ack]; D6 -- No --> P6[Result := Pass]; P5 --> 2; P6 --> 2; +``` + +The flowchart illustrates the procedure for inserting subscriber data initiated by the GLR. It begins at connector 1 and enters a loop to handle unsupported services. If any services are not supported in the VLR, it checks if they should be ignored. If not ignored, it checks if the service should be replaced. If replacement is not done, it checks if the service is critical. For critical services, a roaming restriction is applied. For non-critical unsupported services, a GLR internal action is performed. After handling unsupported services, it checks if the MSC area is restricted. If not, it checks a count. If the count is greater than zero, it waits for an ISD Ack. If the count is zero or the MSC area is restricted, it sets the MSC area restricted and then checks the count. Finally, it either passes the result or waits for an ISD Ack before reaching connector 2. + +Flowchart for Procedure Insert\_Subscriber\_Data\_Initiated\_GLR. It starts at connector 1, checks for unsupported services, handles them (ignore, replace, or critical), checks MSC area restrictions, and ends at connector 2. + +Figure7.2/6(2): Procedure Insert\_Subscriber\_Data\_Initiated\_GLR + +#### 7.2.1.2 Cancel Location Procedure + +The cancel location procedure in the network when MS leave the network is illustrated in figure 7.2/7. Each step is explained in the following list. + +![Sequence diagram of the Cancel Location Procedure in the Network. The diagram shows interactions between VLR_OLD, GLR, HLR, and VLR_NEW across Visited NW and Home NW domains.](6ca05954842b17f14dfd52f26b9d43d2_img.jpg) + +``` +sequenceDiagram + participant VLR_OLD as VLR_OLD + participant GLR as GLR + participant HLR as HLR + participant VLR_NEW as VLR_NEW + + Note left of VLR_OLD: Visited NW + Note right of VLR_NEW: Home NW + + VLR_NEW->>HLR: 1. Update Location + HLR->>GLR: 2. Cancel Location + GLR->>VLR_OLD: 2. Cancel Location + VLR_OLD->>GLR: 2. Cancel Location ack + GLR->>HLR: 2. Cancel Location ack + HLR->>VLR_NEW: 3. Insert Subscriber Data + VLR_NEW->>HLR: 3. Insert Subscriber Data ack + HLR->>VLR_NEW: 4. Update Location ack +``` + +Sequence diagram of the Cancel Location Procedure in the Network. The diagram shows interactions between VLR\_OLD, GLR, HLR, and VLR\_NEW across Visited NW and Home NW domains. + +**Figure 7.2/7: Cancel Location Procedure in the Network** + +##### Procedure: + +- 1) When the HLR receives an *Update Location* message from newly visited VLR after the MS left the network with the GLR, the HLR initiates cancel location procedure to the GLR. +- 2) The GLR receives a *Cancel Location* message from the HLR and transport to the previously visited VLR. When the GLR receives the response, the GLR transports it to the HLR and delete the roamer's subscriber profile and location information. +- 3) The HLR initiates insert subscriber data procedure to the newly visited VLR. +- 4) After the procedure, the HLR returns the response of an *Update Location* message to the newly visited VLR. + +##### 7.2.1.2.1 Functional requirements of GLR + +###### 7.2.1.2.1.1 Process Cancel\_Location\_GLR + +Figure 7.2/8 shows SDL chart for Process Cancel\_Location\_GLR. This process is initiated from the HLR. + +![Flowchart for Process Cancel_Location_GLR. The process starts at an 'Idle' state, receives a 'Cancel Location' signal, checks parameters (referencing TS 23.018), and then evaluates if the result passes. If it passes, it sends a 'Super_Charged_Cancel_Location_GLR' signal and checks the result again. If this second check passes, it sends a 'Cancel Location ack' and deletes subscriber data, returning to 'Idle'. If either check fails, it sends a 'Cancel Location negative response' and returns to 'Idle'. If the second check fails, it enters a 'Wait_For_Response' state and then handles either an acknowledgement or a negative response.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +### Process Cancel\_Location\_GLR + +1(1) + +``` +graph TD; Start([Idle]) --> CL{Cancel Location}; CL --> CP[Check Parameter]; CP --- Note1[See TS 23.018]; CP --> RP{Result=Pass?}; RP -- No --> CLR{Cancel Location negative response}; CLR --> Idle1([Idle]); RP -- Yes --> SC[Super_Charged_Cancel_Location_GLR]; SC --> RP2{Result=Pass?}; RP2 -- No --> CL2{Cancel Location}; CL2 --> WFR([Wait_For_Response]); WFR --> CLA{Cancel Location ack}; WFR --> CNR{Cancel Location negative response}; CLA --> DSD[Delete Subscriber data]; DSD --> CLA2{Cancel Location ack}; CNR --> CNR2{Cancel Location negative response}; CLA2 --> Idle2([Idle]); CNR2 --> Idle2; +``` + +Process in the GLR application to initiate cancellation of location registration in a VLR + +Signals to/from the left are to/from the VLR +Signals to/from the right are to/from the HLR + +Flowchart for Process Cancel\_Location\_GLR. The process starts at an 'Idle' state, receives a 'Cancel Location' signal, checks parameters (referencing TS 23.018), and then evaluates if the result passes. If it passes, it sends a 'Super\_Charged\_Cancel\_Location\_GLR' signal and checks the result again. If this second check passes, it sends a 'Cancel Location ack' and deletes subscriber data, returning to 'Idle'. If either check fails, it sends a 'Cancel Location negative response' and returns to 'Idle'. If the second check fails, it enters a 'Wait\_For\_Response' state and then handles either an acknowledgement or a negative response. + +Figure 7.2/8: Process Cancel\_Location\_GLR + +###### 7.2.1.2.1.2 Process Cancel\_Location\_Initiated\_GLR + +Figure 7.2/9 shows SDL chart for Process Cancel\_Location\_Initiated\_GLR. This process is initiated if HLR update is not required. + +![SDL chart for Process Cancel_Location_Initiated_GLR](933ecd14c858bf3fc919222d8e357bc8_img.jpg) + +**Process Cancel\_Location\_Initiated\_GLR** 1(1) + +Process in the GLR application to initiate cancellation of location registration in a VLR + +Signals to/from the left are to/from the VLR + +``` +stateDiagram-v2 + [*] --> Cancel_Location + Cancel_Location --> Wait_For_CL_Response + state "Cancel Location ack" as Cancel_Location_ack + state "Abort" as Abort + state "Cancel Location negative response" as Cancel_Location_negative_response + state "Repeat Location Cancellation?" as Repeat_Location_Cancellation + state "Wait for time expiry" as Wait_for_time_expiry + Wait_For_CL_Response --> Cancel_Location_ack + Wait_For_CL_Response --> Abort + Wait_For_CL_Response --> Cancel_Location_negative_response + Cancel_Location_ack --> [*] + Abort --> Cancel_Location_negative_response + Cancel_Location_negative_response --> Repeat_Location_Cancellation + Repeat_Location_Cancellation -- Yes --> Wait_for_time_expiry + Repeat_Location_Cancellation -- No --> [*] + Wait_for_time_expiry --> Cancel_Location +``` + +The diagram is an SDL chart titled "Process Cancel\_Location\_Initiated\_GLR". It begins with an initial state (oval) leading to a transition "Cancel Location" (diamond). This leads to a state "Wait\_For\_CL\_Response" (double oval). From this state, three transitions are possible: "Cancel Location ack" (trapezoid), "Abort" (trapezoid), and "Cancel Location negative response" (trapezoid). The "Cancel Location ack" transition leads to a final state (cross). The "Abort" transition leads to the "Cancel Location negative response" transition. The "Cancel Location negative response" transition leads to a decision state "Repeat Location Cancellation?" (diamond). If "Yes", it leads to a state "Wait for time expiry" (rectangle), which then loops back to the "Cancel Location" transition. If "No", it leads to a final state (cross). + +SDL chart for Process Cancel\_Location\_Initiated\_GLR + +Figure 7.2/9: Process Cancel\_Location\_Initiated\_GLR + +#### 7.2.1.3 Handling of unsupported service + +The procedure can be used to handle the case where the VLR does not support the full set of services required by the user. + +See figure 7.2/10. When the GLR receives the **Insert Subscriber Data Acknowledge** message indicating "Service Not Supported", it initiates the location updating procedure toward the HLR. The HLR takes some appropriate reaction (e.g. initiates service substitution or roaming restriction etc.) and determines whether to accept the location updating request or not for the user. The HLR generates a new profile (i.e. the profile after service substitution), which must be forwarded by the GLR to the VLR. The GLR must also maintain a copy of the actual service profile for the subscriber (i.e. the profile before service substitution). + +The GLR will have to perform some transaction level processing on message 3 (i.e. **Insert Subscriber Data ack**) from the VLR. Subsequently, when the GLR sends message 6 (i.e. **Insert Subscriber Data ack**) to the HLR, the message format will have to match that of message 5 (**Insert Subscriber Data**) from the HLR. + +![Sequence diagram showing message flow between VLR, GLR, and HLR for handling unsupported services.](b904ac2472cab80892d1e783e6230d6e_img.jpg) + +``` + +sequenceDiagram + participant VLR + participant GLR + participant HLR + Note over VLR, GLR: Visited NW + Note over HLR: Home NW + VLR->>GLR: 1. Update Location + GLR->>VLR: 2. Insert Subscriber Data + Note left of VLR: Can't Support +The Full Set of +Subscribed +Services + VLR->>GLR: 3. Insert Subscriber Data ack +(Service Not Supported) + Note right of GLR: Identifies unsupported and +Decides to initiate UL + GLR->>HLR: 4. Update Location + HLR->>GLR: 5. Insert Subscriber Data + GLR->>HLR: 6. Insert Subscriber Data ack +(Service Not Supported) + Note right of HLR: Some appropriate +action + HLR->>GLR: 7. Update Location ack OR +Update Location error + GLR->>VLR: 8. Update Location ack OR +Update Location error + +``` + +The diagram illustrates the signaling sequence between the VLR, GLR, and HLR. The VLR and GLR are within the Visited Network (NW), while the HLR is in the Home NW. The sequence starts with an Update Location from VLR to GLR. After Insert Subscriber Data exchange, the VLR indicates it cannot support the full set of services. The GLR then initiates an Update Location to the HLR. The HLR performs an appropriate action and returns either an Update Location ack or error, which is forwarded back to the VLR. + +Sequence diagram showing message flow between VLR, GLR, and HLR for handling unsupported services. + +**Figure 7.2/10: MS Arrives at a VLR That Cannot Handle all Services** + +When the user roams from a VLR area with restricted service support into a VLR area where the VLR can support the full set of subscribed services, the GLR must: + +- Identify that the new VLR can support the actual service profile required by the HLR, i.e. the profile before service substitution. +- notify the HLR to take the appropriate reaction to restore services. Therefore, the GLR initiates the location updating procedure towards the HLR. (refer to figure 7.2/11 in the case of circuit switched mode). + +The GLR will have to perform some transaction level processing on message 3 (i.e. Insert Subscriber Data ack) from the VLR. Subsequently, when the GLR sends message 6 (i.e. Insert Subscriber Data ack) to the HLR, the message format will have to match that of message 5 (Insert Subscriber Data) from the HLR. + +![Sequence diagram showing the procedure for unsupported service handling when a mobile station (MS) arrives at a VLR that handles all services. The diagram involves three entities: VLR and GLR in the Visited NW, and HLR in the Home NW. The sequence starts with a note: 'The Procedure for Unsupported Service handling was initiated On location updating in the previously visited VLR'. The steps are: 1. Update Location (VLR to GLR), 2. Insert Subscriber Data (GLR to VLR), 3. Insert Subscriber Data ack (VLR to GLR) with a note 'Can Support The Full Set of Subscribed Services', 4. Update Location (GLR to HLR), 5. Insert Subscriber Data (HLR to GLR), 6. Insert Subscriber Data ack (GLR to HLR) with a note 'Some appropriate action', 7. Update Location ack (HLR to GLR), and 8. Update Location (GLR to VLR). A note between steps 3 and 4 indicates the GLR 'Identifies the full set of subscribed service supported and Decides to...'.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) + +``` + +sequenceDiagram + participant VLR + participant GLR + participant HLR + Note right of GLR: The Procedure for Unsupported Service handling was initiated +On location updating in the previously visited VLR + VLR->>GLR: 1. Update Location + GLR->>VLR: 2. Insert Subscriber Data + Note left of VLR: Can Support +The Full Set of +Subscribed +Services + VLR->>GLR: 3. Insert Subscriber Data ack + Note right of GLR: Identifies the full set of +subscribed service +supported and Decides to... + GLR->>HLR: 4. Update Location + HLR->>GLR: 5. Insert Subscriber Data + GLR->>HLR: 6. Insert Subscriber Data ack + Note right of HLR: Some appropriate +action + HLR->>GLR: 7. Update Location ack + GLR->>VLR: 8. Update Location + +``` + +Sequence diagram showing the procedure for unsupported service handling when a mobile station (MS) arrives at a VLR that handles all services. The diagram involves three entities: VLR and GLR in the Visited NW, and HLR in the Home NW. The sequence starts with a note: 'The Procedure for Unsupported Service handling was initiated On location updating in the previously visited VLR'. The steps are: 1. Update Location (VLR to GLR), 2. Insert Subscriber Data (GLR to VLR), 3. Insert Subscriber Data ack (VLR to GLR) with a note 'Can Support The Full Set of Subscribed Services', 4. Update Location (GLR to HLR), 5. Insert Subscriber Data (HLR to GLR), 6. Insert Subscriber Data ack (GLR to HLR) with a note 'Some appropriate action', 7. Update Location ack (HLR to GLR), and 8. Update Location (GLR to VLR). A note between steps 3 and 4 indicates the GLR 'Identifies the full set of subscribed service supported and Decides to...'. + +Figure 7.2/11: MS Arrives at a VLR That Handles all Services + +### 7.2.2 Retrieval of routing information procedure + +In 3G TS 23.018 [4](Basic Call Handling) specification, the description for the basic call handling about MO and MT is stated. + +Only the retrieval of routing information for an MT call is related with the GLR. + +Therefore, this specification states the retrieval of routing information for an MT call. + +#### 7.2.2.1 Information flow for retrieval of routing information for an MT call + +The information flow for retrieval of routing information for an MT call is shown in figure 7.2/12. Solid lines show ISUP signalling between the originating exchange and GMSCB, and between GMSCB and VMSCB; signalling over the MAP interfaces between GMSCB and HLRB and between HLRB and VLRB is shown by chain lines. + +![Sequence diagram showing information flow for retrieval of routing information for a basic mobile terminated call. The diagram shows five entities: GMSC, HLRB, GLRB, VLRB, and VMSCB. The flow starts with an IAM message to GMSC. GMSC sends an SRI to HLRB. HLRB sends a PRN to GLRB. GLRB sends a PRN to VLRB. VLRB returns a PRN ack to GLRB. GLRB returns a PRN ack to HLRB. HLRB returns an SRI ack to GMSC. Finally, GMSC sends an IAM message to VMSCB.](0ee9d674085524d589646a6c3fb21ec3_img.jpg) + +``` + +sequenceDiagram + participant GMSC + participant HLRB + participant GLRB + participant VLRB + participant VMSCB + + Note left of GMSC: IAM + GMSC-->>HLRB: SRI + HLRB-->>GLRB: PRN + GLRB-->>VLRB: PRN + VLRB-->>GLRB: PRN ack + GLRB-->>HLRB: PRN ack + HLRB-->>GMSC: SRI ack + GMSC->>VMSCB: IAM + +``` + +Sequence diagram showing information flow for retrieval of routing information for a basic mobile terminated call. The diagram shows five entities: GMSC, HLRB, GLRB, VLRB, and VMSCB. The flow starts with an IAM message to GMSC. GMSC sends an SRI to HLRB. HLRB sends a PRN to GLRB. GLRB sends a PRN to VLRB. VLRB returns a PRN ack to GLRB. GLRB returns a PRN ack to HLRB. HLRB returns an SRI ack to GMSC. Finally, GMSC sends an IAM message to VMSCB. + +**Figure 7.2/12: Information flow for retrieval of routing information for a basic mobile terminated call** + +When GMSCB receives an IAM, it analyses the called party address. If GMSCB can derive an HLR address from the B party address, it sends a request for routing information (SRI) to HLRB. HLRB sends a request for a roaming number (PRN) to VLRB via GLRB. VLRB returns the roaming number in the PRN ack via GLR, and HLRB relays the roaming number to GMSCB in the SRI ack. GMSCB constructs an IAM using the roaming number, and sends it to VMSCB. + +If the VLRB supports the Super-Charger features, when the VLRB receives a request for a roaming number (PRN) and has no subscriber data for the user, it checks whether the subscriber data record was removed by the Super-Charger database management function or not. (See 3G TS 23.116 [9]) If the subscriber data was removed by the Super-Charger feature, the VLRB shall return the cause information set to Purged MS to the GLR by sending PRN negative response. When the GLR receives this information, it deletes the subscriber data for the user and relays the message to the HLR. + +#### 7.2.2.2 Functional requirements of network entities + +The text in this clause is a supplement to the definition in the SDL diagrams; it does not duplicate the information in the SDL diagrams. + +The entities described in this clause interwork with other entities over the D interfaces, used to interwork between the VLR & HLR. + +The protocol used over the D interfaces is MAP, which is specified in 3G TS 29.002 [10]. + +For the purposes of this specification, the protocol used over telephony signalling interfaces is ISUP, which is specified in ETS 300 356-1 [27]; other telephony signalling systems may be used instead. + +The SDL diagrams in this clause show the handling for a number of optional features and services. If the handling consists only of a call to a procedure specific to the feature or service, the procedure call is omitted if the entity does not support an optional feature or service. If the handling consists of more than a call to a procedure specific to the feature or service, the text associated with each SDL diagram specifies the handling that applies if the entity does not support an optional feature or service. + +##### 7.2.2.2.1 Functional requirements of GLR + +###### 7.2.2.2.1.1 Process PRN\_GLR + +Figure 7.2/13 shows SDL chart for Process PRN\_GLR. + +Sheet1: the GLR receives a PRN message from the HLR. + +Sheet1: after the GLR transfers the VLR Number, the GLR relays a PRN message to the VLR. + +Sheet1: the GLR waits a PRN response and receives a PRN ack message or a PRN negative response message from the VLR. + +Sheet1: after the GLR transfers the HLR Number, the GLR relays a PRN ack message or a PRN negative response message to the HLR. + +Figure 7.2/14 shows SDL chart for Procedure Super\_Charged\_PRN\_Error\_GLR. + +![State transition diagram for Process PRN_GLR. The process starts at an Idle state, receives a Provide Roaming Number from the HLR, sets the GLR Number as MSC number, provides the Roaming Number to the VLR, and then waits for a response. It then branches based on the response from the VLR: an ack leads to another Idle state via the HLR, while a negative response leads to a Super_Charged PRN_Error_GLR state and then to an Idle state.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +### Process PRN\_GLR + +1(1) + +Process in the GLR to handle a request for a roaming number + +Signals to/from the left are to/from the HLR: signals to/from the right are to/from the VLR. + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> PRN_from_HLR: Provide Roaming Number from HLR + PRN_from_HLR --> Set_MSC: Set GLR Number as MSC number + Set_MSC --> PRN_to_VLR: Provide Roaming Number to VLR + PRN_to_VLR --> Wait: Wait for Provide Roaming Number response + state "Wait for Provide Roaming Number response" as Wait + Wait --> PRN_ack_from_VLR: Provide Roaming Number ack from VLR + Wait --> PRN_neg_response_from_VLR: Provide Roaming Number negative response from VLR + PRN_ack_from_VLR --> PRN_ack_to_HLR: Provide Roaming Number ack to HLR + PRN_ack_to_HLR --> Idle2: Idle + PRN_neg_response_from_VLR --> PRN_neg_response_to_HLR: Provide Roaming Number negative response to HLR + PRN_neg_response_to_HLR --> Super_Charged: Super_Charged PRN_Error_GLR + Super_Charged --> Idle3: Idle +``` + +State transition diagram for Process PRN\_GLR. The process starts at an Idle state, receives a Provide Roaming Number from the HLR, sets the GLR Number as MSC number, provides the Roaming Number to the VLR, and then waits for a response. It then branches based on the response from the VLR: an ack leads to another Idle state via the HLR, while a negative response leads to a Super\_Charged PRN\_Error\_GLR state and then to an Idle state. + +Figure 7.2/13: Process PRN\_GLR + +###### Procedure Super\_Charged\_PRN\_Error\_GLR + +1(1) + +The procedure Super\_Charged\_PRN\_Error\_GLR determines whether the GLR shall delete its data for the MS based on the outcome of a Provide Roaming Number + +![Flowchart for Procedure Super_Charged_PRN_Error_GLR](5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg) + +``` +graph TD; Start([ ]) --> Decision1{Super-Charged GLR}; Decision1 -- Yes --> Decision2{Absent Subscriber Error: Purged MS?}; Decision1 -- No --> End(( )); Decision2 -- Yes --> Process[Delete Subscriber Data]; Decision2 -- No --> End; Process --> End; +``` + +The flowchart illustrates the procedure Super\_Charged\_PRN\_Error\_GLR. It begins with a start symbol (oval with a vertical line), leading to a decision diamond labeled 'Super-Charged GLR'. If the answer is 'Yes', it proceeds to another decision diamond labeled 'Absent Subscriber Error: Purged MS?'. If the answer to this second decision is 'Yes', it proceeds to a process box labeled 'Delete Subscriber Data'. If the answer to either decision is 'No', or after the 'Delete Subscriber Data' process, it proceeds to an end symbol (circle with an 'X'). + +Flowchart for Procedure Super\_Charged\_PRN\_Error\_GLR + +Figure7.2/14: Procedure Super\_Charged\_PRN\_Error\_GLR + +###### 7.2.2.2.1.2 Process PSI\_GLR + +Figure 7.2/15 shows SDL chart for Process PSI\_GLR. + +Sheet1: the GLR receives a PSI message from the HLR. + +Sheet1: after the GLR transfers the VLR Number, the GLR relays a PSI message to the VLR. + +Sheet1: the GLR waits a PSI response and receives a PSI ack message or a PSI negative response message from the VLR. + +Sheet1: after the GLR transfers the HLR Number, the GLR relays a PSI ack message or a PSI negative response message to the HLR. + +![State transition diagram for Process PSI_GLR. The process starts at an initial state, goes to Idle, receives 'Provide Subscriber Info' from HLR, sends 'Provide Subscriber Info' to VLR, and then waits for a response. The response can be an 'Info ack' from VLR, leading to 'Set GLR Number as VLR Number' and then sending an 'Info ack' to HLR, or an 'Info negative response' from VLR, leading to sending an 'Info negative response' to HLR. Both final states return to Idle.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +### Process PSI\_GLR + +1(1) + +Process in the GLR to handle a request from the HLR for subscriber information + +Signals to/from the left are to/from the HLR: signals to/from the right are to/from the VLR. + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> ProvideSubscriberInfo_HLR : from HLR + ProvideSubscriberInfo_HLR --> ProvideSubscriberInfo_VLR : to VLR + ProvideSubscriberInfo_VLR --> WaitResponse : Wait for Provide Subscriber Info response + state "Wait for Provide Subscriber Info response" as WaitResponse + WaitResponse --> ProvideSubscriberInfo_ack_VLR : from VLR + WaitResponse --> ProvideSubscriberInfo_negative_response_VLR : from VLR + ProvideSubscriberInfo_ack_VLR --> SetGLRNumber : Set GLR Number as VLR Number + SetGLRNumber --> ProvideSubscriberInfo_ack_HLR : to HLR + ProvideSubscriberInfo_ack_HLR --> Idle + ProvideSubscriberInfo_negative_response_VLR --> ProvideSubscriberInfo_negative_response_HLR : to HLR + ProvideSubscriberInfo_negative_response_HLR --> Idle +``` + +State transition diagram for Process PSI\_GLR. The process starts at an initial state, goes to Idle, receives 'Provide Subscriber Info' from HLR, sends 'Provide Subscriber Info' to VLR, and then waits for a response. The response can be an 'Info ack' from VLR, leading to 'Set GLR Number as VLR Number' and then sending an 'Info ack' to HLR, or an 'Info negative response' from VLR, leading to sending an 'Info negative response' to HLR. Both final states return to Idle. + +Figure 7.2/15: Process PSI\_GLR + +#### 7.2.2.3 Contents of messages (HLR-GLR, GLR-VLR) + +There is no different between the contents of the following messages sent between HLR and VLR and the contents of the following messages sent between HLR and GLR, GLR and VLR. The same contents are sent from the HLR to VLR via the GLR. See 3G TS 23.018 [4]. + +- Provide Roaming Number. +- Provide Roaming Number ack. +- Provide Roaming Number negative response. +- Provide Subscriber Info. +- Provide Subscriber Info ack. +- Provide Subscriber Info negative response. + +### 7.2.3 Authentication Information Retrieval procedure ARRI + +The Authentication Information Retrieval procedure is illustrated in figure 7.2/16. Each step is explained in the following list. + +![Sequence diagram for Authentication Information Retrieval procedure ARRI. The diagram shows four steps: 1. VLR sends 'Send Authentication Info' to GLR; 2. GLR sends 'Send Authentication Info' to HLR; 3. HLR sends 'Send Authentication Info ack' to GLR; 4. GLR sends 'Send Authentication Info ack' to VLR. The VLR and GLR are grouped under 'Visited NW', and the HLR is under 'Home NW'.](4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg) + +``` + +sequenceDiagram + participant VLR + participant GLR + participant HLR + Note over VLR, GLR: Visited NW + Note over HLR: Home NW + VLR->>GLR: 1. Send Authentication Info + GLR->>HLR: 2. Send Authentication Info + HLR-->>GLR: 3. Send Authentication Info ack + GLR-->>VLR: 4. Send Authentication Info ack + +``` + +Sequence diagram for Authentication Information Retrieval procedure ARRI. The diagram shows four steps: 1. VLR sends 'Send Authentication Info' to GLR; 2. GLR sends 'Send Authentication Info' to HLR; 3. HLR sends 'Send Authentication Info ack' to GLR; 4. GLR sends 'Send Authentication Info ack' to VLR. The VLR and GLR are grouped under 'Visited NW', and the HLR is under 'Home NW'. + +**Figure 7.2/16: Send Authentication Info** + +#### Procedure: + +1. When the VLR receives a service indication concerning a location registration, call set-up, operation on a supplementary service to initiate authentication. The VLR sends a *Send Authentication Info* message to the GLR in order to retrieve the authentication information. +2. The GLR transfers the received message to the HLR. +3. When the GLR receives the response with authentication information for the user from the HLR, it transports to the VLR. +4. The VLR receives the authentication information of user by the response of *Send Authentication Info* message. + +### 7.2.4 Subscriber Data management procedure + +#### 7.2.4.1 Insert Subscriber Data Procedure + +The Insert Subscriber Data procedure is illustrated in figure 7.2/17. Each step is explained in the following list. + +![Sequence diagram for Insert Subscriber Data procedure](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +A sequence diagram illustrating the 'Insert Subscriber Data' procedure. It features three lifelines: VLR and GLR under the heading 'Visited NW', and HLR under the heading 'Home NW'. The sequence of messages is as follows: 1. An arrow labeled '1. Insert Subscriber Data' points from the HLR to the GLR. 2. An arrow labeled '2. Insert Subscriber Data' points from the GLR to the VLR. 3. An arrow labeled '3. Insert Subscriber Data ack' points from the VLR to the GLR. 4. An arrow labeled '4. Insert Subscriber Data ack' points from the GLR to the HLR. + +Sequence diagram for Insert Subscriber Data procedure + +**Figure 7.2/17: Insert Subscriber Data** + +##### **Procedure:** + +1. The HLR sends *Insert Subscriber Data* message to the GLR in order to update with the certain subscriber data. +2. The GLR updates the subscriber data and transfer the received message to the VLR. +3. The GLR receives the response from the VLR. The response may indicate regional restriction or unsupported services. The detail procedures are described in subclause 7.5. +4. The GLR transfers the received message to the HLR. + +#### **7.2.4.2 Delete Subscriber Data Procedure** + +The Delete Subscriber Data procedure is used by an HLR to remove certain subscriber data from a VLR and a SGSN if the subscription of one or more supplementary services or basic services is withdrawn. Note that this service is not used in case of erasure or deactivation of supplementary services. And the Delete Subscriber Data procedure is illustrated in figure 7.2/18. Each step is explained in the following list. + +![Sequence diagram for Delete Subscriber Data procedure](23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg) + +A sequence diagram illustrating the 'Delete Subscriber Data' procedure. It features three lifelines: VLR and GLR under the heading 'Visited NW', and HLR under the heading 'Home NW'. The sequence of messages is as follows: 1. An arrow labeled '1. Delete Subscriber Data' points from the HLR to the GLR. 2. An arrow labeled '2. Delete Subscriber Data' points from the GLR to the VLR. 3. An arrow labeled '3. Delete Subscriber Data ack' points from the VLR to the GLR. 4. An arrow labeled '4. Delete Subscriber Data ack' points from the GLR to the HLR. + +Sequence diagram for Delete Subscriber Data procedure + +**Figure 7.2/18: Delete Subscriber Data** + +##### **Procedure:** + +1. The HLR sends a *Delete Subscriber Data* message to the GLR in order to remove with the certain subscriber data. + +2. The GLR deletes the subscriber data indicated and transfers the received message to the VLR. +3. The GLR receives a *Delete Subscriber Data* ack message from the VLR. +4. The GLR transfers the received message to the HLR. + +### 7.2.5 Supplementary services procedures + +Activation, deactivation, registration, erasure, and interrogation are the procedures involving the interface between the VLR and the HLR related to the control of state of the supplementary services. Also Registration of password and use of password are the procedures involving the interface. Additionally, Unstructured SS Data service and CCBS includes the procedure involving the interface. If the GLR is located between the HLR and the VLR, the GLR relays the messages between HLR and VLR of the procedures transparently. + +The registration procedure involving the GLR is described in figure 7.2/19 as a typical case. The following procedures are the similar to the registration procedure. Each step is explained in the following list. + +![Sequence diagram for Register SS procedure involving VLR, GLR, and HLR.](3b00a61116faef21d3a6009fd350b46a_img.jpg) + +``` +sequenceDiagram + participant VLR + participant GLR + participant HLR + Note over VLR, GLR: Visited NW + Note over HLR: Home NW + VLR->>GLR: 1. Register SS + GLR->>HLR: 2. Register SS + HLR-->>GLR: 3. Register SS ack + GLR-->>VLR: 4. Register SS ack +``` + +The diagram illustrates the 'Register SS' procedure. It features three vertical lifelines: VLR, GLR, and HLR. The VLR and GLR are grouped under a bracket labeled 'Visited NW', while the HLR is under a bracket labeled 'Home NW'. The sequence of messages is as follows: 1. A solid arrow labeled '1. Register SS' points from the VLR to the GLR. 2. A solid arrow labeled '2. Register SS' points from the GLR to the HLR. 3. A dashed arrow labeled '3. Register SS ack' points from the HLR back to the GLR. 4. A dashed arrow labeled '4. Register SS ack' points from the GLR back to the VLR. + +Sequence diagram for Register SS procedure involving VLR, GLR, and HLR. + +**Figure 7.2/19: Register SS** + +#### Procedure: + +1. When the VLR receives a service indication of registration of SS data, such as a Forwarded-to-Number, the VLR sends a Register SS message. +2. The GLR transfers the received message to the HLR. +3. The GLR receives the acknowledgement from the HLR. +4. The GLR transfers the received message to the VLR. + +## 7.3 Packet Switched Service + +This subclause describes the GPRS procedures involving GLR except Short Message Service, Recovery and Restoration. The procedures for Short Message Service of GPRS are described in the subclause "Short Message Service." The procedures for Recovery and Restoration of GPRS are described in the subclause "Recovery and Restoration." + +### 7.3.1 GPRS Attach Procedure + +Three cases are described in this section: + +- The new SGSN is within a VPLMN served by the GLR. The old SGSN interfaces to the HLR directly. +- The new SGSN and old SGSN are within a VPLMN served by the same GLR. + +- The new SGSN is within a VPLMN served by the GLR. The old SGSN is within a different VPLMN served by the GLR. +- The new SGSN interfaces to the HLR directly. The old SGSN is within a VPLMN served by the GLR. + +#### 7.3.1.1 New SGSN served by GLR, old SGSN served by HLR + +![Sequence diagram of GPRS Attach Procedure involving GLR. Lifelines: MS, BSS, new SGSN, old SGSN, GGSN, EIR, GLR, HLR. The diagram shows the interaction between these entities during an attach procedure where the new SGSN is under the GLR and the old SGSN interfaces directly with the HLR.](0c80c383f76034e117adf5e5eaadaaf3_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant new_SGSN as new SGSN + participant old_SGSN as old SGSN + participant GGSN + participant EIR + participant GLR + participant HLR + + MS->>new_SGSN: 1. Attach Request + new_SGSN->>old_SGSN: 2. Identification Request + old_SGSN-->>new_SGSN: 2. Identification Response + new_SGSN->>MS: 3. Identity Request + MS-->>new_SGSN: 3. Identity Response + new_SGSN->>MS: 4. Authentication + new_SGSN->>EIR: 5. IMEI Check + new_SGSN->>GLR: 6a. Update Location + GLR->>HLR: 6a. Update Location + HLR->>old_SGSN: 6b. Cancel Location + old_SGSN-->>HLR: 6c. Cancel Location Ack + HLR->>GLR: 6d. Insert Subscriber Data + GLR->>new_SGSN: 6d. Insert Subscriber Data + new_SGSN-->>GLR: 6e. Insert Subscriber Data Ack + GLR->>HLR: 6e. Insert Subscriber Data Ack + HLR->>GLR: 6f. Update Location Ack + GLR->>new_SGSN: 6f. Update Location Ack + new_SGSN->>MS: 8. Attach Accept + MS-->>new_SGSN: 9. Attach Complete + +``` + +Sequence diagram of GPRS Attach Procedure involving GLR. Lifelines: MS, BSS, new SGSN, old SGSN, GGSN, EIR, GLR, HLR. The diagram shows the interaction between these entities during an attach procedure where the new SGSN is under the GLR and the old SGSN interfaces directly with the HLR. + +**Figure 7.3/1: GPRS Attach Procedure involving GLR (new SGSN is under the GLR. Old SGSN interfaces the HLR directly)** + +- to 5) These steps are the same as the steps not involving GLR. See TS 23.060 [6]. +- If the SGSN number has changed since the GPRS detach, or if it is the very first attach, then the SGSN informs the HLR via GLR: + - The SGSN sends an Update Location (SGSN Number, SGSN Address, and IMSI) to the GLR. Then the GLR sends an Update Location (GLR Number, IM-GSN address, IMSI) to the HLR, if the GLR does have the IMSI record. Note that, GLR Number and IM-GSN address should respectively be set in SGSN Number parameter and SGSN address parameters. + - The HLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with Cancellation Type set to Update Procedure. + - The old SGSN acknowledges with Cancel Location Ack (IMSI). If there are any ongoing procedures for that MS, the old SGSN shall wait until these procedures are finished before removing the MM and PDP contexts. + - The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the GLR. The GLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN. + +- e) The new SGSN validates the MS's presence in the (new) RA. If due to regional subscription restrictions the MS is not allowed to attach in the RA, the SGSN rejects the Attach Request with an appropriate cause, and may return an Insert Subscriber Data Ack (IMSI, SGSN Area Restricted) message to the GLR. Then, the GLR set the SGSN area restricted flag "true" and transfers the SGSN area restricted indication to the HLR within the Insert Subscriber Data Ack message. Note that some modification at the application level might be needed here to maintain compatibility with the message format of (6d). If subscription checking fails for other reasons, the SGSN rejects the Attach Request with an appropriate cause and returns an Insert Subscriber Data Ack (IMSI, Cause) message to the GLR, which the GLR transfers to the HLR within the Insert Subscriber Data Ack message. Note that some modification at the application level might be needed here to maintain compatibility with the message format of (6d). If all checks are successful then the SGSN constructs an MM context for the MS and returns an Insert Subscriber Data Ack (IMSI) message to the GLR, which the GLR transfers to the HLR. +- f) The HLR acknowledges the Update Location message by sending an Update Location Ack to the GLR and the GLR send it to the SGSN after the cancelling of old MM context and insertion of new MM context are finished. If the Update Location is rejected by the HLR, the SGSN rejects the Attach Request from the MS with an appropriate cause. +- 8) and 9) These steps are the same as the steps not involving GLR. See TS 23.060 [6]. + +If the Attach Request cannot be accepted, the SGSN returns an Attach Reject (IMSI, Cause) message to the MS. + +#### 7.3.1.2 New SGSN and old SGSN served by the same GLR + +![Sequence diagram of GPRS Attach Procedure involving GLR (new SGSN and old SGSN are under in the same GLR).](1e8c50ad4fca7f315a407347dd5091cc_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant new_SGSN as new SGSN + participant old_SGSN as old SGSN + participant GGSN + participant EIR + participant GLR + participant HLR + + MS->>new_SGSN: 1. Attach Request + new_SGSN->>old_SGSN: 2. Identification Request + old_SGSN-->>new_SGSN: 2. Identification Response + new_SGSN-->>MS: 3. Identity Request + MS-->>new_SGSN: 3. Identity Response + new_SGSN<->MS: 4. Authentication + new_SGSN<->EIR: 5. IMEI Check + new_SGSN->>GLR: 6a. Update Location + GLR->>old_SGSN: 6b. Cancel Location + old_SGSN-->>GLR: 6c. Cancel Location Ack + GLR<->HLR: 6d. Insert Subscriber Data + GLR->>HLR: 6e. Insert Subscriber Data Ack + GLR-->>new_SGSN: 6f. Update Location Ack + new_SGSN-->>MS: 8. Attach Accept + MS-->>new_SGSN: 9. Attach Complete + +``` + +Sequence diagram of GPRS Attach Procedure involving GLR (new SGSN and old SGSN are under in the same GLR). + +**Figure 7.3/2: GPRS Attach Procedure involving GLR (new SGSN and old SGSN are under in the same GLR)** + +- 1) to 5) These steps are the same as the steps not involving GLR. See TS 23.060 [6]. + +- 6) If the SGSN number has changed since the GPRS detach, or if it is the very first attach, then the SGSN informs the GLR: + - a) The SGSN sends an Update Location (SGSN Number, SGSN Address, and IMSI) to the GLR. If the GLR has the IMSI record, the GLR does not send an Update Location message to the HLR. + - b) The GLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with Cancellation Type set to Update Procedure. + - c) The old SGSN acknowledges with Cancel Location Ack (IMSI). If there are any ongoing procedures for that MS, the old SGSN shall wait until these procedures are finished before removing the MM and PDP contexts. + - d) The GLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN. + - e) The new SGSN validates the MS's presence in the (new) RA. If due to regional subscription restrictions the MS is not allowed to attach in the RA, the SGSN rejects the Attach Request with an appropriate cause, and may return an Insert Subscriber Data Ack (IMSI, SGSN Area Restricted) message to the GLR. If the SGSN area restricted flag is set "false" in the GLR, the GLR sets the flag "true" and sends an Update Location (GLR Number, IM-GSN address, IMSI) to the HLR. Subclause 7.5 describes the detail procedure. Note that, GLR Number and IM-GSN address should respectively be set in SGSN Number parameter and SGSN address parameters. If subscription checking fails for other reasons, the SGSN rejects the Attach Request with an appropriate cause and returns an Insert Subscriber Data Ack (IMSI, Cause) message to the GLR. If all checks are successful then the SGSN constructs an MM context for the MS and returns an Insert Subscriber Data Ack (IMSI) message to the GLR. + - f) The GLR acknowledges the Update Location message by sending an Update Location Ack to the SGSN after the cancelling of old MM context and insertion of new MM context are finished. If the Update Location is rejected by the GLR, the SGSN rejects the Attach Request from the MS with an appropriate cause. +- 8) and 9) These steps are the same as the steps not involving GLR. See TS 23.060 [6]. + +If the Attach Request cannot be accepted, the SGSN returns an Attach Reject (IMSI, Cause) message to the MS. + +#### 7.3.1.3 New SGSN served by the GLR, and old SGSN served by the other GLR + +![Sequence diagram of GPRS Attach Procedure involving GLR. Lifelines: MS, BSS, new SGSN, old SGSN, GGSN, EIR, new GLR, old GLR, HLR. The sequence shows the interaction between these entities during an attach process where the new SGSN is under a different GLR than the old SGSN.](036ceaf207a7b289ca76e160892eb724_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant new_SGSN as new SGSN + participant old_SGSN as old SGSN + participant GGSN + participant EIR + participant new_GLR as new GLR + participant old_GLR as old GLR + participant HLR + + Note left of MS: 1. Attach Request + MS->>new_SGSN: 1. Attach Request + Note right of new_SGSN: 2. Identification Request + new_SGSN->>old_SGSN: 2. Identification Request + Note right of old_SGSN: 2. Identification Response + old_SGSN-->>new_SGSN: 2. Identification Response + Note left of new_SGSN: 3. Identity Request + new_SGSN-->>MS: 3. Identity Request + Note left of MS: 3. Identity Response + MS->>new_SGSN: 3. Identity Response + Note left of new_SGSN: 4. Authentication + new_SGSN-->>MS: 4. Authentication + Note left of MS: 5. IMEI Check + MS->>new_SGSN: 5. IMEI Check + Note right of new_SGSN: 6a. Update Location + new_SGSN->>new_GLR: 6a. Update Location + Note right of new_GLR: 6b. Cancel Location + new_GLR->>HLR: 6b. Cancel Location + Note right of HLR: 6c. Cancel Location Ack + HLR-->>old_GLR: 6c. Cancel Location Ack + Note right of old_GLR: 6d. Insert Subscriber Data + old_GLR->>old_SGSN: 6d. Insert Subscriber Data + Note right of old_SGSN: 6e. Insert Subscriber Data Ack + old_SGSN-->>old_GLR: 6e. Insert Subscriber Data Ack + Note right of old_GLR: 6f. Update Location Ack + old_GLR-->>new_GLR: 6f. Update Location Ack + Note right of new_GLR: 8. Attach Accept + new_GLR-->>new_SGSN: 8. Attach Accept + Note left of new_SGSN: 9. Attach Complete + new_SGSN->>BSS: 9. Attach Complete + BSS->>MS: 9. Attach Complete + +``` + +Sequence diagram of GPRS Attach Procedure involving GLR. Lifelines: MS, BSS, new SGSN, old SGSN, GGSN, EIR, new GLR, old GLR, HLR. The sequence shows the interaction between these entities during an attach process where the new SGSN is under a different GLR than the old SGSN. + +**Figure 7.3/3: GPRS Attach Procedure involving GLR (new SGSN and old SGSN are under in the different GLR)** + +- 1) to 5) These steps are the same as the steps not involving GLR. See TS 23.060 [6]. +- 6) If the SGSN number has changed since the GPRS detach, or if it is the very first attach, then the SGSN informs the HLR via GLR: + - a) The SGSN sends an Update Location (SGSN Number, SGSN Address, and IMSI) to the GLR. Then the GLR sends an Update Location (GLR Number, IM-GSN address, IMSI) to the HLR if the GLR does not have the IMSI record. Note that, GLR Number and IM-GSN address should respectively be set in SGSN Number parameter and SGSN address parameters in the actual MAP operation. + - b) The HLR sends Cancel Location (IMSI, Cancellation Type) to the old GLR with Cancellation Type set to Update Procedure. Then the GLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with Cancellation Type set to Update Procedure. + - c) The old SGSN acknowledges with Cancel Location Ack (IMSI). If there are any ongoing procedures for that MS, the old SGSN shall wait until these procedures are finished before removing the MM and PDP contexts. + - d) The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the GLR. The GLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN. + +- e) The new SGSN validates the MS's presence in the (new) RA. If due to regional subscription restrictions the MS is not allowed to attach in the RA, the SGSN rejects the Attach Request with an appropriate cause, and may return an Insert Subscriber Data Ack (IMSI, SGSN Area Restricted) message to the GLR. The GLR sets the SGSN area restricted flag "true" and transfers the SGSN area restricted indication to the HLR within the Insert Subscriber Data Ack message. Note that some modification at the application level might be needed here to maintain compatibility with the message format of (6d). If subscription checking fails for other reasons, the SGSN rejects the Attach Request with an appropriate cause and returns an Insert Subscriber Data Ack (IMSI, Cause) message to the GLR, which the GLR transfers to the HLR within the Insert Subscriber Data Ack message. Note that some modification at the application level might be needed here to maintain compatibility with the message format of (6d). If all checks are successful then the SGSN constructs an MM context for the MS and returns an Insert Subscriber Data Ack (IMSI) message to the GLR, which the GLR transfers to the HLR. +- f) The HLR acknowledges the Update Location message by sending an Update Location Ack to the GLR and the GLR send it to the SGSN after the cancelling of old MM context and insertion of new MM context are finished. If the Update Location is rejected by the HLR, the SGSN rejects the Attach Request from the MS with an appropriate cause. +- 8) and 9) These steps are the same as the steps not involving GLR. See TS 23.060 [6]. + +If the Attach Request cannot be accepted, the SGSN returns an Attach Reject (IMSI, Cause) message to the MS. + +#### 7.3.1.4 New SGSN served by HLR, old SGSN served by GLR + +![Sequence diagram of GPRS Attach Procedure involving GLR. Lifelines: MS, BSS, new SGSN, old SGSN, GGSN, EIR, GLR, HLR. The diagram shows the interaction between these entities during an attach procedure where the new SGSN interfaces directly with the HLR, and the old SGSN is under the GLR.](0f26e70157bd4c45f825795cdcd20fbd_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant new_SGSN as new SGSN + participant old_SGSN as old SGSN + participant GGSN + participant EIR + participant GLR + participant HLR + + Note left of MS: 1. Attach Request + MS->>new_SGSN: 1. Attach Request + Note right of new_SGSN: 2. Identification Request + new_SGSN->>old_SGSN: 2. Identification Request + Note right of old_SGSN: 2. Identification Response + old_SGSN-->>new_SGSN: 2. Identification Response + Note left of new_SGSN: 3. Identity Request + new_SGSN-->>MS: 3. Identity Request + Note left of MS: 3. Identity Response + MS-->>new_SGSN: 3. Identity Response + Note left of new_SGSN: 4. Authentication + new_SGSN-->>MS: 4. Authentication + Note left of MS: 5. IMEI Check + MS-->>new_SGSN: 5. IMEI Check + Note right of new_SGSN: 6a. Update Location + new_SGSN->>HLR: 6a. Update Location + Note right of HLR: 6b. Cancel Location + HLR-->>old_SGSN: 6b. Cancel Location + Note right of old_SGSN: 6c. Cancel Location Ack + old_SGSN-->>GLR: 6c. Cancel Location Ack + Note right of GLR: 6d. Insert Subscriber Data + GLR-->>new_SGSN: 6d. Insert Subscriber Data + Note right of new_SGSN: 6e. Insert Subscriber Data Ack + new_SGSN-->>HLR: 6e. Insert Subscriber Data Ack + Note right of HLR: 6f. Update Location Ack + HLR-->>new_SGSN: 6f. Update Location Ack + Note left of new_SGSN: 8. Attach Accept + new_SGSN-->>MS: 8. Attach Accept + Note left of MS: 9. Attach Complete + MS-->>new_SGSN: 9. Attach Complete + +``` + +Sequence diagram of GPRS Attach Procedure involving GLR. Lifelines: MS, BSS, new SGSN, old SGSN, GGSN, EIR, GLR, HLR. The diagram shows the interaction between these entities during an attach procedure where the new SGSN interfaces directly with the HLR, and the old SGSN is under the GLR. + +Figure 7.3/4: GPRS Attach Procedure involving GLR (new SGSN interfaces the HLR directly. Old SGSN is under the GLR) + +- 1) to 5) These steps are the same as the steps not involving GLR. See TS 23.060 [6]. +- 6) If the SGSN number has changed since the GPRS detach, or if it is the very first attach, then the SGSN informs the HLR: + - a) The SGSN sends an Update Location (SGSN Number, SGSN Address, and IMSI) to the HLR. + - b) The HLR sends Cancel Location (IMSI, Cancellation Type) to the old GLR, then the GLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with Cancellation Type set to Update Procedure. + - c) The old SGSN acknowledges with Cancel Location Ack (IMSI) via the GLR. If there are any ongoing procedures for that MS, the old SGSN shall wait until these procedures are finished before removing the MM and PDP contexts. + - d) The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN. + - e) The new SGSN validates the MS's presence in the (new) RA. If due to regional subscription restrictions the MS is not allowed to attach in the RA, the SGSN rejects the Attach Request with an appropriate cause, and may return an Insert Subscriber Data Ack (IMSI, SGSN Area Restricted) message to the HLR. If subscription checking fails for other reasons, the SGSN rejects the Attach Request with an appropriate cause and returns an Insert Subscriber Data Ack (IMSI, Cause) message to the HLR. If all checks are successful then the SGSN constructs an MM context for the MS and returns an Insert Subscriber Data Ack (IMSI) message to the HLR. + - f) The HLR acknowledges the Update Location message by sending an Update Location Ack to the SGSN after the cancelling of old MM context and insertion of new MM context are finished. If the Update Location is rejected by the HLR, the SGSN rejects the Attach Request from the MS with an appropriate cause. +- 8) and 9) These steps are the same as the steps not involving GLR. See TS 23.060 [6]. + +If the Attach Request cannot be accepted, the SGSN returns an Attach Reject (IMSI, Cause) message to the MS. + +#### 7.3.1.5 Functional requirements of GLR + +##### 7.3.1.5.1 Process Update\_GPRS\_Location\_GLR + +Figure 7.3/5 shows SDL chart for Process Update\_GPRS\_Location\_GLR. + +Sheet1: the test "HLR update required?" takes the "yes" exit the GLR checks some flags to perform the "Location Updating Screening Function (see to section 7.1.6)" and if it is needed to update location information to the HLR. + +Sheet2: after the GLR sends an Update GPRS Location message to the HLR, the GLR receives the response with: + +- an Insert Subscriber Data message, handled by the procedure Insert\_Subscriber\_Data\_GLR shown in subclause 7.2.1; +- an Update GPRS Location ack message. If the GLR receives this message, this indicates that updating has been successfully completed. The GLR sets the "(Location and Subscriber information) LSIC by HLR" indicator to "Confirmed". The GLR send an Update GPRS Location ack message to the SGSN; +- an Update GPRS Location negative response message. If the GLR receives this message, this indicates that updating has been unsuccessfully completed. The GLR sets the "(Location and Subscriber information) LSIC by HLR" indicator to "False". The GLR sends an Update GPRS Location negative to the SGSN. + +Sheet3: process Cancel\_GPRS\_Location\_Initiated\_GLR is specified in subclause 7.3.1.5.4. + +![Flowchart for Process Update_GPRS_Location_GLR. The process starts at an 'Idle' state, receives an 'Update GPRS Location' request, checks parameters (referencing TS 23.018), and then evaluates if the result passes. If it passes, it checks if the subscriber is known in the GLR. If not known, it sets a negative response and returns to 'Idle'. If known, it checks the network access mode. If not GPRS, it sets a negative response and returns to 'Idle'. If GPRS, it checks if an HLR update is required. If yes, it sets the GLR number as the SGSN number, sets the IM-GSN address, updates the location, and waits for data. If no HLR update is required, it checks if it's a new SGSN. If yes, it super-charges and cancels the location in the GLR, then checks the result. If that result passes, it cancels the GPRS location initiated by the GLR and proceeds to connector 1. If no new SGSN, it proceeds to connector 1. If the initial parameter check fails, it proceeds directly to connector 1.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +### Process Update\_GPRS\_Location\_GLR + +1(7) + +Process in the GLR to handle an Update GPRS Location request and trigger the correct application process + +Signales to/from the left are to/from the SGSN +Signales to/from the right are to/from the HLR + +``` +graph TD; Start([Idle]) --> Request{{Update GPRS Location}}; Request --> Check[Check Parameter]; Check -.-> Note1[See TS 23.018]; Check --> ResultPass{Result= Pass}; ResultPass -- No --> Connector1((1)); ResultPass -- Yes --> SubscriberKnown{subscriber known in GLR}; SubscriberKnown -- No --> NegativeResponse[Set negative response: Unknown Subscriber]; NegativeResponse --> UpdateNeg[Update GPRS Location negative response]; UpdateNeg --> Idle([Idle]); SubscriberKnown -- Yes --> NetworkAccess{Network access mode = GPRS}; NetworkAccess -- No --> NegativeResponse; NetworkAccess -- Yes --> HLRUpdate{HLR update required?}; HLRUpdate -- Yes --> SetGLR[Set GLR Number as SGSN Number]; SetGLR --> SetIM[Set IM-GSN address as SGSN address]; SetIM --> UpdateLoc[Update Location]; UpdateLoc --> WaitData([Wait_For_Data]); HLRUpdate -- No --> NewSGSN{New SGSN?}; NewSGSN -- Yes --> SuperCharge[Super_Charged_Cancel_Location_GLR]; SuperCharge --> ResultPass2{Result = pass?}; ResultPass2 -- No --> CancelGPRS[Cancel_GPRS_Location_Initiated_GLR]; CancelGPRS --> Connector1; ResultPass2 -- Yes --> CancelGPRS; NewSGSN -- No --> Connector1; +``` + +Flowchart for Process Update\_GPRS\_Location\_GLR. The process starts at an 'Idle' state, receives an 'Update GPRS Location' request, checks parameters (referencing TS 23.018), and then evaluates if the result passes. If it passes, it checks if the subscriber is known in the GLR. If not known, it sets a negative response and returns to 'Idle'. If known, it checks the network access mode. If not GPRS, it sets a negative response and returns to 'Idle'. If GPRS, it checks if an HLR update is required. If yes, it sets the GLR number as the SGSN number, sets the IM-GSN address, updates the location, and waits for data. If no HLR update is required, it checks if it's a new SGSN. If yes, it super-charges and cancels the location in the GLR, then checks the result. If that result passes, it cancels the GPRS location initiated by the GLR and proceeds to connector 1. If no new SGSN, it proceeds to connector 1. If the initial parameter check fails, it proceeds directly to connector 1. + +Figure7.3/5(1): Process Update\_GPRS\_Location\_GLR + +![Flowchart for Process Update_GPRS_Location_GLR. It starts with 'Wait_For_Data' and branches into four main paths: 'Insert Subscriber Data', 'Update GPRS Location ack', 'Update GPRS Location negative response', and 'Abort'. The 'Update GPRS Location ack' path leads to 'Result:=Pass', 'LSIC by HLR :=Confirmed', 'Set GLR Number as HLR Number', 'Update Location ack', and 'Idle'. The 'Update GPRS Location negative response' path leads to a 'Failure Case?' decision. If 'Roaming Not Allowed', 'Result:= Roaming Not Allowed', 'Delete Subscriber Data', 'LSIC by HLR :=False', 'Update GPRS Location negative response', and 'Idle'. If 'Unknown Subscriber', 'Result:= Unknown Subscriber', 'Delete Subscriber Data', 'LSIC by HLR :=False', 'Update GPRS Location negative response', and 'Idle'. If 'Procedure Error', 'Result:= Procedure Error', 'LSIC by HLR :=False', 'Update GPRS Location negative response', and 'Idle'. The 'Insert Subscriber Data' path leads to 'Insert_Subscriber_Data_GLR', 'Wait_For_Data_from_HLR_and_ISD_ack_from_SGSN', and 'Idle'. The 'Abort' path leads to 'Abort' and 'Idle'.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +### Process Update\_GPRS\_Location\_GLR 2(7) + +Process in the GLR to handle an Update GPRS Location request and trigger the correct application process + +Signals to/from the left are to/from the SGSN +Signals to/from the right are to/from the HLR + +``` +graph TD; Start([Wait_For_Data]) --> InsertData{Insert Subscriber Data}; Start --> UpdateAck{Update GPRS Location ack}; Start --> UpdateNeg{Update GPRS Location negative response}; Start --> Abort1{Abort}; InsertData --> InsertSub[Insert_Subscriber_Data_GLR]; InsertSub --> WaitForDataHLR[Wait_For_Data_from_HLR_and_ISD_ack_from_SGSN]; WaitForDataHLR --> Idle1([Idle]); UpdateAck --> ResultPass[Result:=Pass]; ResultPass --> LSICConfirmed[LSIC by HLR :=Confirmed]; LSICConfirmed --> SetGLR[Set GLR Number as HLR Number]; SetGLR --> UpdateLocAck{Update Location ack}; UpdateLocAck --> Idle2([Idle]); UpdateNeg --> FailureCase{Failure Case?}; FailureCase -- Roaming Not Allowed --> ResultRoaming[Result:= Roaming Not Allowed]; ResultRoaming --> DeleteData1[Delete Subscriber Data]; FailureCase -- Unknown Subscriber --> ResultUnknown[Result:= Unknown Subscriber]; ResultUnknown --> DeleteData2[Delete Subscriber Data]; FailureCase -- Procedure Error --> ResultError[Result:= Procedure Error]; DeleteData1 --> LSICFalse[LSIC by HLR :=False]; DeleteData2 --> LSICFalse; ResultError --> LSICFalse; LSICFalse --> UpdateNegNeg{Update GPRS Location negative response}; UpdateNegNeg --> Idle3([Idle]); Abort1 --> Abort2{Abort}; Abort2 --> Idle4([Idle]); +``` + +Flowchart for Process Update\_GPRS\_Location\_GLR. It starts with 'Wait\_For\_Data' and branches into four main paths: 'Insert Subscriber Data', 'Update GPRS Location ack', 'Update GPRS Location negative response', and 'Abort'. The 'Update GPRS Location ack' path leads to 'Result:=Pass', 'LSIC by HLR :=Confirmed', 'Set GLR Number as HLR Number', 'Update Location ack', and 'Idle'. The 'Update GPRS Location negative response' path leads to a 'Failure Case?' decision. If 'Roaming Not Allowed', 'Result:= Roaming Not Allowed', 'Delete Subscriber Data', 'LSIC by HLR :=False', 'Update GPRS Location negative response', and 'Idle'. If 'Unknown Subscriber', 'Result:= Unknown Subscriber', 'Delete Subscriber Data', 'LSIC by HLR :=False', 'Update GPRS Location negative response', and 'Idle'. If 'Procedure Error', 'Result:= Procedure Error', 'LSIC by HLR :=False', 'Update GPRS Location negative response', and 'Idle'. The 'Insert Subscriber Data' path leads to 'Insert\_Subscriber\_Data\_GLR', 'Wait\_For\_Data\_from\_HLR\_and\_ISD\_ack\_from\_SGSN', and 'Idle'. The 'Abort' path leads to 'Abort' and 'Idle'. + +Figure7.3/5(2): Process Update\_GPRS\_Location\_GLR + +![Flowchart for Process Update_GPRS_Location_GLR. It starts with an 'Insert Subscriber Data' message from the left, followed by 'Insert_Subscriber_Data_GLR' and 'Wait_For_Data_from_HLR_and_ISD_ack_from_SGSN'. The process then sends an 'Update GPRS Location ack' to the left, receiving 'Result:=Pass' and 'LSIC by HLR :=Confirmed'. It then 'Set GLR Number as HLR_Number' and sends another 'Update Location ack' to the left, ending in 'Idle'. Alternatively, it can receive an 'Update GPRS Location negative response' from the left, leading to a 'Failure Case?' decision. The 'Failure Case?' decision has three branches: 'Roaming Not Allowed' (Result:= Roaming Not Allowed, Delete Subscriber Data), 'Unknown Subscriber' (Result:= Unknown Subscriber, Delete Subscriber Data), and 'Procedure Error' (Result:= Procedure Error). All three branches lead to 'LSIC by HLR :=False', then 'Update GPRS Location negative response' to the left, and finally 'Idle'. An 'Abort' message from the left leads to an 'Abort' state and then 'Idle'.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +### Process Update\_GPRS\_Location\_GLR 3(7) + +Process in the GLR to handle an Update GPRS Location request and trigger the correct application process + +Wait\_For\_Data\_from\_HLR\_and\_ISD\_ack\_from\_SGSN + +Signales to/from the left are to/from the SGSN +Signales to/from the right are to/from the HLR + +``` +graph TD; Start(( )) --> InsertData[Insert Subscriber Data]; InsertData --> InsertSub[Insert_Subscriber_Data_GLR]; InsertSub --> WaitForData((Wait_For_Data_from_HLR_and_ISD_ack_from_SGSN)); WaitForData --> UpdateAck1[Update GPRS Location ack]; UpdateAck1 --> ResultPass[Result:=Pass]; ResultPass --> LSICConfirmed[LSIC by HLR :=Confirmed]; LSICConfirmed --> SetGLR[Set GLR Number as HLR_Number]; SetGLR --> UpdateLocAck[Update Location ack]; UpdateLocAck --> Idle1((Idle)); UpdateLocAck --> NegativeResponse[Update GPRS Location negative response]; NegativeResponse --> FailureCase{Failure Case?}; FailureCase -- Roaming Not Allowed --> ResultRoaming[Result:= Roaming Not Allowed]; ResultRoaming --> DeleteData1[Delete Subscriber Data]; FailureCase -- Unknown Subscriber --> ResultUnknown[Result:= Unknown Subscriber]; ResultUnknown --> DeleteData2[Delete Subscriber Data]; FailureCase -- Procedure Error --> ResultError[Result:= Procedure Error]; DeleteData1 --> LSICFalse[LSIC by HLR :=False]; DeleteData2 --> LSICFalse; ResultError --> LSICFalse; LSICFalse --> NegativeResponse2[Update GPRS Location negative response]; NegativeResponse2 --> Idle2((Idle)); Abort1[Abort] --> Abort2[Abort]; Abort2 --> Idle3((Idle)); +``` + +Flowchart for Process Update\_GPRS\_Location\_GLR. It starts with an 'Insert Subscriber Data' message from the left, followed by 'Insert\_Subscriber\_Data\_GLR' and 'Wait\_For\_Data\_from\_HLR\_and\_ISD\_ack\_from\_SGSN'. The process then sends an 'Update GPRS Location ack' to the left, receiving 'Result:=Pass' and 'LSIC by HLR :=Confirmed'. It then 'Set GLR Number as HLR\_Number' and sends another 'Update Location ack' to the left, ending in 'Idle'. Alternatively, it can receive an 'Update GPRS Location negative response' from the left, leading to a 'Failure Case?' decision. The 'Failure Case?' decision has three branches: 'Roaming Not Allowed' (Result:= Roaming Not Allowed, Delete Subscriber Data), 'Unknown Subscriber' (Result:= Unknown Subscriber, Delete Subscriber Data), and 'Procedure Error' (Result:= Procedure Error). All three branches lead to 'LSIC by HLR :=False', then 'Update GPRS Location negative response' to the left, and finally 'Idle'. An 'Abort' message from the left leads to an 'Abort' state and then 'Idle'. + +Figure7.3/5(3): Process Update\_GPRS\_Location\_GLR + +![Flowchart for Process Update_GPRS_Location_GLR. It starts with a 'Wait_For_Data_from_HLR_and_ISD_ack_from_SGSN' state, leading to a decision between 'Insert Subscriber Data ack' and 'Insert Subscriber Data negative response'. The 'ack' path leads to 'Update Subscriber Data' and then a decision 'SGSN area restricted by regional subscription?'. If 'Yes', it goes to 'Set SGSN area restricted' before reaching 'Insert Subscriber Data ack' and the final wait state. If 'No', it goes directly to 'Insert Subscriber Data ack' and the final wait state. The 'negative response' path leads to 'Insert Subscriber Data negative response' and then to a 'Wait_For_Data_from_HLR_and_ISD_ack_from_SGSN' state.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +### Process Update\_GPRS\_Location\_GLR 4(7) + +Process in the GLR to handle an Update GPRS Location request and trigger the correct application process + +Signals to/from the left are to/from the SGSN +Signals to/from the right are to/from the HLR + +``` +graph TD; Start((Wait_For_Data_from_HLR_and_ISD_ack_from_SGSN)) --> Decision1{ }; Decision1 --> Ack1{{Insert Subscriber Data ack}}; Decision1 --> Neg1{{Insert Subscriber Data negative response}}; Ack1 --> Update[Update Subscriber Data]; Update --> Decision2{SGSN area restricted by regional subscription?}; Decision2 -- Yes --> Set[Set SGSN area restricted]; Set --> Ack2{{Insert Subscriber Data ack}}; Decision2 -- No --> Ack2; Ack2 --> End((Wait_For_Data_from_HLR_and_ISD_ack_from_SGSN)); Neg1 --> Neg2{{Insert Subscriber Data negative response}}; Neg2 --> End2((Wait_For_Data_from_HLR_and_ISD_ack_from_SGSN)); +``` + +Flowchart for Process Update\_GPRS\_Location\_GLR. It starts with a 'Wait\_For\_Data\_from\_HLR\_and\_ISD\_ack\_from\_SGSN' state, leading to a decision between 'Insert Subscriber Data ack' and 'Insert Subscriber Data negative response'. The 'ack' path leads to 'Update Subscriber Data' and then a decision 'SGSN area restricted by regional subscription?'. If 'Yes', it goes to 'Set SGSN area restricted' before reaching 'Insert Subscriber Data ack' and the final wait state. If 'No', it goes directly to 'Insert Subscriber Data ack' and the final wait state. The 'negative response' path leads to 'Insert Subscriber Data negative response' and then to a 'Wait\_For\_Data\_from\_HLR\_and\_ISD\_ack\_from\_SGSN' state. + +Figure7.3/5(4): Process Update\_GPRS\_Location\_GLR + +![Flowchart for Process Update_GPRS_Location_GLR. It starts with connector '1', followed by 'Super_Charged_Location_Updating_GLR' process. A decision 'Result = pass?' follows. If 'No', it goes to 'ISD_GLR' process, then another 'Result = Pass?' decision. If 'Yes', it checks 'SGSN Area Restricted?'. If 'No', it goes to 'Subscriber_Present_GPRS_GLR' process, then 'Changed SGSN area restricted' decision. If 'Yes', it goes to 'Update GPRS Location ack' then 'Idle'. If 'No', it goes to 'Set GLR Number as SGSN Number', 'Set IM-GSN address as SGSN address', 'Update GPRS Location', and 'Wait_For_information'. If 'Result = Pass?' is 'No', it checks 'Result = Aborted?'. If 'Yes', it goes to 'Idle'. If 'No', it goes to 'Update GPRS Location negative response' then 'Idle'. If 'Result = pass?' is 'Yes', it goes to 'Update GPRS Location' then 'Idle'.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +### Process Update\_GPRS\_Location\_GLR + +5(7) + +Process in the GLR to handle an Update GPRS Location request and trigger the correct application process + +Signales to/from the left are to/from the SGSN +Signales to/from the right are to/from the HLR + +``` +graph TD; 1((1)) --> P1[Super_Charged_Location_Updating_GLR]; P1 --> D1{Result = pass?}; D1 -- No --> P2[ISD_GLR]; P2 --> D2{Result = Pass?}; D2 -- Yes --> D3{SGSN Area Restricted?}; D3 -- No --> P3[Subscriber_Present_GPRS_GLR]; P3 --> D4{Changed SGSN area restricted}; D4 -- Yes --> P4[Set GLR Number as SGSN Number]; P4 --> P5[Set IM-GSN address as SGSN address]; P5 --> P6[Update GPRS Location]; P6 --> P7[Wait_For_information]; D4 -- No --> P8[Update GPRS Location ack]; P8 --> E1([Idle]); D2 -- No --> D5{Result = Aborted?}; D5 -- Yes --> E2([Idle]); D5 -- No --> P9[Update GPRS Location negative response]; P9 --> E3([Idle]); D1 -- Yes --> P10[Update GPRS Location]; P10 --> E4([Idle]); +``` + +Flowchart for Process Update\_GPRS\_Location\_GLR. It starts with connector '1', followed by 'Super\_Charged\_Location\_Updating\_GLR' process. A decision 'Result = pass?' follows. If 'No', it goes to 'ISD\_GLR' process, then another 'Result = Pass?' decision. If 'Yes', it checks 'SGSN Area Restricted?'. If 'No', it goes to 'Subscriber\_Present\_GPRS\_GLR' process, then 'Changed SGSN area restricted' decision. If 'Yes', it goes to 'Update GPRS Location ack' then 'Idle'. If 'No', it goes to 'Set GLR Number as SGSN Number', 'Set IM-GSN address as SGSN address', 'Update GPRS Location', and 'Wait\_For\_information'. If 'Result = Pass?' is 'No', it checks 'Result = Aborted?'. If 'Yes', it goes to 'Idle'. If 'No', it goes to 'Update GPRS Location negative response' then 'Idle'. If 'Result = pass?' is 'Yes', it goes to 'Update GPRS Location' then 'Idle'. + +Figure7.3/5(5): Process Update\_GPRS\_Location\_GLR + +![Flowchart for Process Update_GPRS_Location_GLR. It starts with 'Wait_For_Information' and branches into four main paths: 'Insert Subscriber Data' (leading to connector '2'), 'Update GPRS Location ack' (leading to 'Result:= Pass', 'LSIC by HLR :=True', 'Set GLR Number as HLR Number', 'Update GPRS Location ack', and 'Idle'), 'Update GPRS Location negative response' (leading to 'Failure case?' decision), and 'Abort' (leading to 'Abort' and 'Idle'). The 'Failure case?' decision leads to three sub-paths: 'Roaming not Allowed' (Result:= Roaming Not Allowed, Delete Subscriber Data), 'Unknown Subscriber' (Result:= Unknown Subscriber, Delete Subscriber Data), and 'Procedure Error' (Result:= Procedure Error). All three failure paths converge to 'LSIC by HLR :=False', 'Update Location negative response', and 'Idle'.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +### Process Update\_GPRS\_Location\_GLR + +6(7) + +Process in the GLR to handle an Update GPRS Location request and trigger the correct application process + +Signales to/from the left are to/from the VLR +Signales to/from the right are to/from the HLR + +``` +graph TD; Start([Wait_For_Information]) --> InsertData[/Insert Subscriber Data/]; Start --> UpdateAck[/Update GPRS Location ack/]; Start --> UpdateNegResp[/Update GPRS Location negative response/]; Start --> Abort[/Abort/]; InsertData --> C2((2)); UpdateAck --> ResPass[Result:= Pass]; ResPass --> LSICTrue[LSIC by HLR :=True]; LSICTrue --> SetGLR[Set GLR Number as HLR Number]; SetGLR --> UpdateAck2[/Update GPRS Location ack/]; UpdateAck2 --> Idle1([Idle]); UpdateNegResp --> FailureCase{Failure case?}; FailureCase -- Roaming not Allowed --> ResRoam[Result:= Roaming Not Allowed]; ResRoam --> DelSub1[Delete Subscriber Data]; FailureCase -- Unknown Subscriber --> ResUnknown[Result:= Unknown Subscriber]; ResUnknown --> DelSub2[Delete Subscriber Data]; FailureCase -- Procedure Error --> ResError[Result:= Procedure Error]; DelSub1 --> LSICFalse[LSIC by HLR :=False]; DelSub2 --> LSICFalse; ResError --> LSICFalse; LSICFalse --> UpdateNegResp2[/Update Location negative response/]; UpdateNegResp2 --> Idle2([Idle]); Abort --> Abort2[/Abort/]; Abort2 --> Idle3([Idle]); +``` + +Flowchart for Process Update\_GPRS\_Location\_GLR. It starts with 'Wait\_For\_Information' and branches into four main paths: 'Insert Subscriber Data' (leading to connector '2'), 'Update GPRS Location ack' (leading to 'Result:= Pass', 'LSIC by HLR :=True', 'Set GLR Number as HLR Number', 'Update GPRS Location ack', and 'Idle'), 'Update GPRS Location negative response' (leading to 'Failure case?' decision), and 'Abort' (leading to 'Abort' and 'Idle'). The 'Failure case?' decision leads to three sub-paths: 'Roaming not Allowed' (Result:= Roaming Not Allowed, Delete Subscriber Data), 'Unknown Subscriber' (Result:= Unknown Subscriber, Delete Subscriber Data), and 'Procedure Error' (Result:= Procedure Error). All three failure paths converge to 'LSIC by HLR :=False', 'Update Location negative response', and 'Idle'. + +Figure7.3/5(6): Process Update\_GPRS\_Location\_GLR + +![Flowchart for Process Update_GPRS_Location_GLR. It starts with connector '2', followed by 'Check Parameter' (note: See TS 23.018). A decision 'Result= Pass?' follows. If 'No', it goes to 'Insert Subscriber Data negative response' and then 'Idle'. If 'Yes', it goes to 'Subscriber known?'. If 'No', it goes to 'Idle'. If 'Yes', it goes to 'Update Subscriber Data'. Next is a decision 'SGSN area restricted by regional subscription?'. If 'Yes', it goes to 'Set SGSN area restricted' and then to 'Insert Subscriber Data ack'. If 'No', it goes directly to 'Insert Subscriber Data ack'. Finally, it goes to 'Wait_For_Information'.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +### Process Update\_GPRS\_Location\_GLR + +7(7) + +Process in the GLR to handle an Update GPRS Location request and trigger the correct application process + +Signals to/from the left are to/from the SGSN +Signals to/from the right are to/from the HLR + +``` +graph TD; 2((2)) --> Check[Check Parameter]; Note1[See TS 23.018] -.-> Check; Check --> Result{Result= Pass?}; Result -- No --> InsertNeg[Insert Subscriber Data negative response]; InsertNeg --> Idle1([Idle]); Result -- Yes --> Known{Subscriber known?}; Known -- No --> Idle1; Known -- Yes --> Update[Update Subscriber Data]; Update --> Restricted{SGSN area restricted by regional subscription?}; Note2[SGSN area restricted by regional subscription?] -.-> Restricted; Restricted -- Yes --> SetRestricted[Set SGSN area restricted]; SetRestricted --> InsertAck[Insert Subscriber Data ack]; Restricted -- No --> InsertAck; InsertAck --> Wait[Wait_For_Information]; +``` + +Flowchart for Process Update\_GPRS\_Location\_GLR. It starts with connector '2', followed by 'Check Parameter' (note: See TS 23.018). A decision 'Result= Pass?' follows. If 'No', it goes to 'Insert Subscriber Data negative response' and then 'Idle'. If 'Yes', it goes to 'Subscriber known?'. If 'No', it goes to 'Idle'. If 'Yes', it goes to 'Update Subscriber Data'. Next is a decision 'SGSN area restricted by regional subscription?'. If 'Yes', it goes to 'Set SGSN area restricted' and then to 'Insert Subscriber Data ack'. If 'No', it goes directly to 'Insert Subscriber Data ack'. Finally, it goes to 'Wait\_For\_Information'. + +Figure7.3/5(7): Process Update\_GPRS\_Location\_GLR + +##### 7.3.1.5.2 Process Subscriber\_Present\_GPRS\_GLR + +Figure 7.3/6 shows SDL chart for Process Subscriber\_Present\_GPRS\_GLR. + +![SDL diagram for Process Subscriber_Present_GPRS_GLR. It starts with an initial state (oval), leading to a decision diamond ''. The 'Yes' path leads to a process box 'Subscriber_Present_GLR_AS_SGSN', which is linked to a note 'See TS 29.120 Section 25.4'. The 'No' path bypasses this process. Both paths converge to a merge point (vertical line with a horizontal tick), which then leads to a final state (crossed circle).](c419b566d720267c499087add1506018_img.jpg) + +**Process Subscriber\_Present\_GPRS\_GLR** 1(1) + +Process in the GLR Application to perform actions required for short message alerting + +``` +graph TD; Start([ ]) --> Decision{}; Decision -- Yes --> Process[Subscriber_Present_GLR_AS_SGSN]; Process --- Note[See TS 29.120 Section 25.4]; Decision -- No --> Merge(( )); Process --> Merge; Merge --> End((X)); +``` + +SDL diagram for Process Subscriber\_Present\_GPRS\_GLR. It starts with an initial state (oval), leading to a decision diamond ''. The 'Yes' path leads to a process box 'Subscriber\_Present\_GLR\_AS\_SGSN', which is linked to a note 'See TS 29.120 Section 25.4'. The 'No' path bypasses this process. Both paths converge to a merge point (vertical line with a horizontal tick), which then leads to a final state (crossed circle). + +**Figure 7.3/6: Process Subscriber\_Present\_GPRS\_GLR** + +##### 7.3.1.5.3 Procedure Insert\_Subscriber\_Data\_GPRS\_Initiated\_GLR + +Figure 7.3/7 shows SDL chart for Procedure Insert\_Subscriber\_Data\_GPRS\_Initiated\_GLR. This procedure is initiated if HLR update is not required. + +![SDL chart for Procedure Insert_Subscriber_Data_GPRS_Initiated_GLR](1033dc9fde75540d224c907681b1b7aa_img.jpg) + +**Procedure Insert\_Subscriber\_Data\_GPRS\_Initiated\_GLR** 1(1) + +The diagram is an SDL chart for the procedure 'Insert\_Subscriber\_Data\_GPRS\_Initiated\_GLR'. It starts with an initial state leading to a transition 'Insert Subscriber Data'. This is followed by an action 'Count:=1'. A decision diamond 'More Data To Send?' follows. If 'Yes', it goes to transition 'Insert Subscriber Data' and action 'Count:= Count+1', then loops back to the decision. If 'No', it goes to state 'Wait\_For\_ISD\_Ack'. From this state, three transitions are possible: 'Insert Subscriber Data ack' (leading to action 'Count:= Count-1' and decision 'SGSN Area Restricted?'), 'Abort' (leading to action 'Result:= Aborted' and final state), and 'Insert Subscriber Data negative response' (leading to action 'Set Negative Response System Failure' and action 'Result:= Fail', then final state). The 'SGSN Area Restricted?' decision has a 'Yes' path to action 'Set SGSN Area Restricted' and a 'No' path to decision 'Count>0?'. The 'Set SGSN Area Restricted' action loops back to the 'Count>0?' decision. The 'Count>0?' decision has a 'Yes' path to state 'Wait\_For\_ISD\_Ack' and a 'No' path to action 'Result:= Pass' and final state. Two notes are present: 'Procedure in the GLR Application for handling the insertion of subscriber data into the SGSN' and 'Signals to/from the left are to/from the VLR'. + +``` + +stateDiagram-v2 + [*] --> Start + Start --> Insert_Subscriber_Data_Out + Insert_Subscriber_Data_Out --> Count_Init + Count_Init --> More_Data_Decision + + More_Data_Decision --> Insert_Subscriber_Data_Loop : Yes + Insert_Subscriber_Data_Loop --> Count_Inc + Count_Inc --> More_Data_Decision + + More_Data_Decision --> Wait_For_ISD_Ack : No + + Wait_For_ISD_Ack --> Insert_Subscriber_Data_Ack_In + Wait_For_ISD_Ack --> Abort_In + Wait_For_ISD_Ack --> Insert_Subscriber_Data_Neg_In + + Insert_Subscriber_Data_Ack_In --> Count_Dec + Count_Dec --> SGSN_Restricted_Decision + + SGSN_Restricted_Decision --> Set_SGSN_Restricted : Yes + Set_SGSN_Restricted --> Count_Check_Decision + SGSN_Restricted_Decision --> Count_Check_Decision : No + + Count_Check_Decision --> Wait_For_ISD_Ack : Yes + Count_Check_Decision --> Result_Pass : No + Result_Pass --> End_Success + + Abort_In --> Result_Aborted + Result_Aborted --> End_Abort + + Insert_Subscriber_Data_Neg_In --> Set_Neg_Response + Set_Neg_Response --> Result_Fail + Result_Fail --> End_Fail + + state " " as Start + state "Insert Subscriber Data" as Insert_Subscriber_Data_Out + state "Count:=1" as Count_Init + state "More Data To Send?" as More_Data_Decision + state "Insert Subscriber Data" as Insert_Subscriber_Data_Loop + state "Count:= Count+1" as Count_Inc + state "Wait_For_ISD_Ack" as Wait_For_ISD_Ack + state "Insert Subscriber Data ack" as Insert_Subscriber_Data_Ack_In + state "Count:= Count-1" as Count_Dec + state "SGSN Area Restricted?" as SGSN_Restricted_Decision + state "Set SGSN Area Restricted" as Set_SGSN_Restricted + state "Count>0?" as Count_Check_Decision + state "Result := Pass" as Result_Pass + state "Abort" as Abort_In + state "Result:= Aborted" as Result_Aborted + state "Insert Subscriber Data negative response" as Insert_Subscriber_Data_Neg_In + state "Set Negative Response System Failure" as Set_Neg_Response + state "Result:= Fail" as Result_Fail + state " " as End_Success + state " " as End_Abort + state " " as End_Fail + +``` + +SDL chart for Procedure Insert\_Subscriber\_Data\_GPRS\_Initiated\_GLR + +Figure 7.3/7: Procedure Insert\_Subscriber\_Data\_GPRS\_Initiated\_GLR + +##### 7.3.1.5.4 Process Cancel\_GPRS\_Location\_Initiated\_GLR + +Figure 7.3/8 shows SDL chart for Process Cancel\_GPRS\_Location\_Initiated\_GLR. This procedure is initiated if HLR update is not required. + +![SDL chart for Process Cancel_GPRS_Location_Initiated_GLR](28085f681b9fff76a53c5b8b32338ee1_img.jpg) + +### Process Cancel\_GPRS\_Location\_Initiated\_GLR 1(1) + +Process in the GLR application to initiate cancellation of location registration in a SGSN + +Signals to/from the left are to/from the SGSN + +``` +stateDiagram-v2 + [*] --> CancelLocation + state "Cancel Location" as CancelLocation + state "Wait_For_CL_Response" as Wait_For_CL_Response + state "Cancel Location ack" as CancelLocation_ack + state "Abort" as Abort + state "Cancel Location negative response" as CancelLocation_negative_response + state "Repeat Location Cancellation?" as RepeatLocationCancellation + state "Wait for time expiry" as Wait_for_time_expiry + + CancelLocation --> Wait_For_CL_Response + Wait_For_CL_Response --> CancelLocation_ack + Wait_For_CL_Response --> Abort + Wait_For_CL_Response --> CancelLocation_negative_response + CancelLocation_ack --> [*] + Abort --> CancelLocation_negative_response + CancelLocation_negative_response --> RepeatLocationCancellation + RepeatLocationCancellation -- Yes --> Wait_for_time_expiry + RepeatLocationCancellation -- No --> [*] + Wait_for_time_expiry --> CancelLocation +``` + +The diagram is an SDL chart titled "Process Cancel\_GPRS\_Location\_Initiated\_GLR". It begins with an initial state leading to a transition labeled "Cancel Location". This transition leads to a state labeled "Wait\_For\_CL\_Response". From this state, three possible transitions emerge: "Cancel Location ack" (which leads to an end state marked with an 'X'), "Abort" (which leads to the "Cancel Location negative response" transition), and "Cancel Location negative response" (which leads to a decision state labeled "Repeat Location Cancellation?"). From the "Repeat Location Cancellation?" decision, a "Yes" transition leads to a state labeled "Wait for time expiry", which then loops back to the "Cancel Location" transition. A "No" transition from the decision leads to an end state marked with an 'X'. + +SDL chart for Process Cancel\_GPRS\_Location\_Initiated\_GLR + +Figure 7.3/8: Process Cancel\_GPRS\_Location\_Initiated\_GLR + +### 7.3.2 Detach procedure + +#### 7.3.2.1 HLR-Initiated Detach Procedure + +The HLR-Initiated Detach procedure is initiated by the HLR. The HLR uses this procedure for operator-determined purposes to request the removal of a subscriber's MM and PDP contexts at the SGSN. The HLR-Initiated Detach Procedure is illustrated in Figure 7.3/9. Each step is explained in the following list. + +![Sequence diagram of the HLR-Initiated GPRS Detach Procedure. Lifelines: MS, BSS, SGSN, GGSN, GLR, HLR, MSC/VLR. The sequence starts with the HLR sending a '1. Cancel Location' message to the SGSN via the GLR. The SGSN then sends a '2. Detach Request' to the MS. The SGSN sends a '3. Delete PDP Context Request' to the GGSN, which responds with '3. Delete PDP Context Response'. The SGSN sends a '4. GPRS Detach Indication' to the MSC/VLR. The MS sends a '5. Detach Accept' to the SGSN. Finally, the SGSN sends a '6. Cancel Location Ack' to the HLR via the GLR.](3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant SGSN + participant GGSN + participant GLR + participant HLR + participant MSC/VLR + + HLR->>GLR: 1. Cancel Location + GLR->>SGSN: 1. Cancel Location + SGSN->>MS: 2. Detach Request + SGSN->>GGSN: 3. Delete PDP Context Request + GGSN-->>SGSN: 3. Delete PDP Context Response + SGSN->>MSC/VLR: 4. GPRS Detach Indication + MS->>SGSN: 5. Detach Accept + SGSN->>GLR: 6. Cancel Location Ack + GLR->>HLR: 6. Cancel Location Ack + +``` + +Sequence diagram of the HLR-Initiated GPRS Detach Procedure. Lifelines: MS, BSS, SGSN, GGSN, GLR, HLR, MSC/VLR. The sequence starts with the HLR sending a '1. Cancel Location' message to the SGSN via the GLR. The SGSN then sends a '2. Detach Request' to the MS. The SGSN sends a '3. Delete PDP Context Request' to the GGSN, which responds with '3. Delete PDP Context Response'. The SGSN sends a '4. GPRS Detach Indication' to the MSC/VLR. The MS sends a '5. Detach Accept' to the SGSN. Finally, the SGSN sends a '6. Cancel Location Ack' to the HLR via the GLR. + +Figure 7.3/9: HLR-Initiated GPRS Detach Procedure + +- 1) If the HLR wants to request the immediate deletion of a subscriber's MM and PDP contexts from the SGSN, the HLR shall send a Cancel Location (IMSI, Cancellation Type) message to the SGSN via GLR with Cancellation Type set to Subscription Withdrawn. +- 2) The SGSN informs the MS that it has been detached by sending Detach Request (Detach Type) to the MS. Detach Type shall indicate that the MS is not requested to make a new attach and PDP context activation. +- 3) The active PDP contexts in the GGSNs regarding this particular MS are deactivated by the SGSN sending Delete PDP Context Request (TID) messages to the GGSNs. The GGSNs acknowledge with Delete PDP Context Response (TID) messages. +- 4) If the MS was both IMSI- and GPRS-attached, the SGSN sends a GPRS Detach Indication (IMSI) message to the VLR. The VLR removes the association with the SGSN and handles paging and location updating without going via the SGSN. +- 5) The MS sends a Detach Accept message to the SGSN any time after step 2. +- 6) The SGSN shall confirm the deletion of the MM and PDP contexts with a Cancel Location Ack (IMSI) message via GLR. + +#### 7.3.2.2 Functional requirements of GLR + +##### 7.3.2.2.1 Process Cancel\_GPRS\_Location\_GLR + +Figure 7.2/10 shows SDL chart for Process Cancel\_GPRS\_Location\_GLR. This process is initiated from the HLR. + +![Flowchart for Process Cancel_GPRS_Location_GLR](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +### Process Cancel\_GPRS\_Location\_GLR + +1(1) + +Process in the GLR application to initiate cancellation of location registration in a SGSN + +Signals to/from the left are to/from the SGSN +Signals to/from the right are to/from the HLR + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> CancelLoc1[/Cancel Location/]; CancelLoc1 --> CheckParam[Check Parameter]; CheckParam --> Note1[See TS 23.018]; CheckParam --> ResultPass{Result= Pass?}; ResultPass -- No --> CancelNeg1[/Cancel Location negative response/]; CancelNeg1 --> Idle2([Idle]); ResultPass -- Yes --> SuperCharger[Super_Charger Cancel_Location_GLR]; SuperCharger --> ResultPass2{Result = pass?}; ResultPass2 -- No --> CancelLoc2[/Cancel Location/]; CancelLoc2 --> WaitForResponse([Wait_For_Response]); WaitForResponse --> CancelLocAck1[/Cancel Location ack/]; WaitForResponse --> CancelNeg2[/Cancel Location negative response/]; CancelLocAck1 --> DeleteData[Delete subscriber data]; DeleteData --> CancelLocAck2[/Cancel Location ack/]; CancelLocAck2 --> Idle3([Idle]); CancelNeg2 --> CancelNeg3[/Cancel Location negative response/]; CancelNeg3 --> Idle3; +``` + +The flowchart illustrates the 'Process Cancel\_GPRS\_Location\_GLR' sequence. It begins with an oval start symbol leading to an 'Idle' state (oval). A 'Cancel Location' message (chevron) is sent from the left. The process then enters a 'Check Parameter' block (double rectangle), which references 'See TS 23.018'. A decision diamond 'Result= Pass?' follows. If 'No', a 'Cancel Location negative response' message (chevron) is sent to the right, returning to an 'Idle' state. If 'Yes', the process enters a 'Super\_Charger Cancel\_Location\_GLR' block (double rectangle). A second decision diamond 'Result = pass?' follows. If 'No', a 'Cancel Location' message (chevron) is sent from the left, followed by a 'Wait\_For\_Response' state (oval). From there, a 'Cancel Location ack' message (chevron) is received from the left, leading to 'Delete subscriber data' (rectangle), then a 'Cancel Location ack' message (chevron) is sent to the right, and finally an 'Idle' state (oval) is reached. A 'Cancel Location negative response' message (chevron) is also received from the right during the wait phase, leading directly to the final 'Idle' state. If 'Result = pass?' is 'yes', the flow bypasses the 'Cancel Location' message and goes directly to the 'Delete subscriber data' block. + +Flowchart for Process Cancel\_GPRS\_Location\_GLR + +Figure 7.3/10: Process Cancel\_GPRS\_Location\_GLR + +### 7.3.3 Authentication of Subscriber + +Authentication procedures already defined in GSM shall be used, with the distinction that the procedures are executed from the SGSN. Additionally, the authentication procedure performs the selection of the ciphering algorithm and the synchronisation for the start of ciphering. Authentication triplets are stored in the SGSN. The MSC/VLR shall not authenticate the MS via the SGSN upon IMSI attach, nor location update, but may authenticate the MS during CS connection establishment. Security-related network functions are described in TS 33.102 [12]. + +The Authentication procedure is illustrated in Figure 7.3/11. Each step is explained in the following list. + +![Sequence diagram of the Authentication Procedure. Lifelines: MS, BSS, SGSN, GLR, HLR. The sequence starts with the SGSN sending '1. Send Authentication Info' to the GLR, which then forwards it to the HLR. The HLR responds with '1. Send Authentication Info Ack' back to the GLR, which then passes it to the SGSN. The SGSN then sends '2. Authentication Request' to the MS via the BSS. The MS responds with '2. Authentication Response' back to the SGSN via the BSS.](cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg) + +``` +sequenceDiagram + participant MS + participant BSS + participant SGSN + participant GLR + participant HLR + Note left of MS: n + SGSN->>GLR: 1. Send Authentication Info + GLR->>HLR: 1. Send Authentication Info + HLR-->>GLR: 1. Send Authentication Info Ack + GLR-->>SGSN: 1. Send Authentication Info Ack + SGSN->>BSS: 2. Authentication Request + BSS->>MS: 2. Authentication Request + MS-->>BSS: 2. Authentication Response + BSS-->>SGSN: 2. Authentication Response +``` + +Sequence diagram of the Authentication Procedure. Lifelines: MS, BSS, SGSN, GLR, HLR. The sequence starts with the SGSN sending '1. Send Authentication Info' to the GLR, which then forwards it to the HLR. The HLR responds with '1. Send Authentication Info Ack' back to the GLR, which then passes it to the SGSN. The SGSN then sends '2. Authentication Request' to the MS via the BSS. The MS responds with '2. Authentication Response' back to the SGSN via the BSS. + +**Figure 7.3/11: Authentication Procedure** + +- 1) If the SGSN does not have previously stored authentication triplets, a Send Authentication Info (IMSI) is sent to the GLR, which the GLR sends to the HLR without modification at the application layer. The HLR responds with Send Authentication Info Ack (Authentication Triplets). Each Authentication Triplet includes RAND, SRES and Kc. +- 2) The SGSN sends Authentication Request (RAND, CKSN, and Ciphering Algorithm). The MS responds with Authentication Response (SRES). + +The MS starts ciphering after sending the Authentication Response message. The SGSN starts ciphering when a valid Authentication Response is received from the MS. + +### 7.3.4 Inter SGSN Routeing Area Update Procedure + +[Editor's note] This procedure may be replaced with inter SGSN SRNS relocation procedure. + +[Editor's note] This procedure may not need to be detailed, because the part of this procedure between SGSN and HLR is the same as the part of Attach procedure. + +The Inter SGSN Routeing Area Update procedure is illustrated in Figure 7.3/12. Each step is explained in the following list. + +![Sequence diagram of Inter SGSN Routing Area Update Procedure. Lifelines: MS, BSS, new SGSN, old SGSN, GGSN, GLR, HLR. The procedure involves 12 numbered steps: 1. MS to new SGSN: Routing Area Update Request; 2. new SGSN to old SGSN: SGSN Context Request; 3. Security Functions (dashed line between new SGSN and HLR); 4. new SGSN to old SGSN: SGSN Context Acknowledge; 5. old SGSN to new SGSN: Forward Packets; 6. new SGSN to GGSN: Update PDP Context Request; 6. GGSN to new SGSN: Update PDP Context Response; 7. new SGSN to GLR: Update Location; 8. GLR to old SGSN: Cancel Location; 8. old SGSN to GLR: Cancel Location Ack; 9. new SGSN to GLR: Insert Subscriber Data; 9. GLR to new SGSN: Insert Subscriber Data Ack; 10. new SGSN to old SGSN: Update Location Ack; 11. new SGSN to MS: Routing Area Update Accept; 12. new SGSN to BSS: Routing Area Update Complete.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSS + participant new_SGSN as new SGSN + participant old_SGSN as old SGSN + participant GGSN + participant GLR + participant HLR + + Note left of MS: 1. Routing Area Update Request + MS->>new_SGSN: 1. Routing Area Update Request + Note right of new_SGSN: 2. SGSN Context Request + new_SGSN->>old_SGSN: 2. SGSN Context Request + Note right of old_SGSN: 2. SGSN Context Response + old_SGSN-->>new_SGSN: 2. SGSN Context Response + Note left of new_SGSN: 3. Security Functions + new_SGSN-->>HLR: 3. Security Functions + Note right of HLR: 4. SGSN Context Acknowledge + HLR-->>new_SGSN: 4. SGSN Context Acknowledge + Note right of old_SGSN: 5. Forward Packets + old_SGSN-->>new_SGSN: 5. Forward Packets + Note right of new_SGSN: 6. Update PDP Context Request + new_SGSN->>GGSN: 6. Update PDP Context Request + Note right of GGSN: 6. Update PDP Context Response + GGSN-->>new_SGSN: 6. Update PDP Context Response + Note right of new_SGSN: 7. Update Location + new_SGSN->>GLR: 7. Update Location + Note right of GLR: 8. Cancel Location + GLR->>old_SGSN: 8. Cancel Location + Note right of old_SGSN: 8. Cancel Location Ack + old_SGSN-->>GLR: 8. Cancel Location Ack + Note right of new_SGSN: 9. Insert Subscriber Data + new_SGSN->>GLR: 9. Insert Subscriber Data + Note right of GLR: 9. Insert Subscriber Data Ack + GLR-->>new_SGSN: 9. Insert Subscriber Data Ack + Note right of new_SGSN: 10. Update Location Ack + new_SGSN-->>old_SGSN: 10. Update Location Ack + Note left of MS: 11. Routing Area Update Accept + new_SGSN-->>MS: 11. Routing Area Update Accept + Note right of new_SGSN: 12. Routing Area Update Complete + new_SGSN->>BSS: 12. Routing Area Update Complete + +``` + +Sequence diagram of Inter SGSN Routing Area Update Procedure. Lifelines: MS, BSS, new SGSN, old SGSN, GGSN, GLR, HLR. The procedure involves 12 numbered steps: 1. MS to new SGSN: Routing Area Update Request; 2. new SGSN to old SGSN: SGSN Context Request; 3. Security Functions (dashed line between new SGSN and HLR); 4. new SGSN to old SGSN: SGSN Context Acknowledge; 5. old SGSN to new SGSN: Forward Packets; 6. new SGSN to GGSN: Update PDP Context Request; 6. GGSN to new SGSN: Update PDP Context Response; 7. new SGSN to GLR: Update Location; 8. GLR to old SGSN: Cancel Location; 8. old SGSN to GLR: Cancel Location Ack; 9. new SGSN to GLR: Insert Subscriber Data; 9. GLR to new SGSN: Insert Subscriber Data Ack; 10. new SGSN to old SGSN: Update Location Ack; 11. new SGSN to MS: Routing Area Update Accept; 12. new SGSN to BSS: Routing Area Update Complete. + +**Figure 7.3/12: Inter SGSN Routing Area Update Procedure** + +- 1) The MS sends a Routing Area Update Request (old RAI, old P-TMSI Signature, and Update Type) to the new SGSN. Update Type shall indicate RA update or periodic RA update. The BSS shall add the Cell Global Identity including the RAC and LAC of the cell where the message was received before passing the message to the SGSN. +- 2) The new SGSN sends SGSN Context Request (old RAI, TLLI, old P-TMSI Signature, and New SGSN Address) to the old SGSN to get the MM and PDP contexts for the MS. The old SGSN validates the old P-TMSI Signature and responds with an appropriate error cause if it does not match the value stored in the old SGSN. This should initiate the security functions in the new SGSN. If the security functions authenticate the MS correctly, the new SGSN shall send an SGSN Context Request (old RAI, TLLI, MS Validated, and New SGSN Address) message to the old SGSN. MS Validated indicates that the new SGSN has authenticated the MS. If the old P-TMSI Signature was valid or if the new SGSN indicates that it has authenticated the MS, the old SGSN responds with SGSN Context Response (MM Context, PDP Contexts, and LLC Ack). If the MS is not known in the old SGSN, the old SGSN responds with an appropriate error cause. The old SGSN stores New SGSN Address, to allow the old SGSN to forward data packets to the new SGSN. LLC Ack contains the acknowledgements for each LLC connection used by the MS. Each PDP Context includes the GTP sequence number for the next downlink N-PDU to be sent to the MS and the GTP sequence number for the next uplink N-PDU to be tunnelled to the GGSN. The old SGSN starts a timer and stops the transmission of N-PDUs to the MS. +- 3) Security functions may be executed. These procedures are defined in subclause "Security Function". Ciphering mode shall be set if ciphering is supported. + +- 4) The new SGSN sends an SGSN Context Acknowledge message to the old SGSN. This informs the old SGSN that the new SGSN is ready to receive data packets belonging to the activated PDP contexts. The old SGSN marks in its context that the MSC/VLR association and the information in the GGSNs and the GLR are invalid. This triggers the MSC/VLR, the GGSNs, and the GLR to be updated if the MS initiates a routeing area update procedure back to the old SGSN before completing the ongoing routeing area update procedure. If the security functions do not authenticate the MS correctly, then the routing area update shall be rejected, and the new SGSN shall send a reject indication to the old SGSN. The old SGSN shall continue as if the SGSN Context Request was never received. +- 5) The old SGSN duplicates the buffered N-PDUs and starts tunnelling them to the new SGSN. Additional N-PDUs received from the GGSN before the timer described in step 2 expires are also duplicated and tunnelled to the new SGSN. N-PDUs that were already sent to the MS in acknowledged mode and that are not yet acknowledged by the MS are tunnelled together with the number of the LLC frame that transferred the last segment of the N-PDU. No N-PDUs shall be forwarded to the new SGSN after expiry of the timer described in step 2. +- 6) The new SGSN sends Update PDP Context Request (new SGSN Address, TID, and QoS Negotiated) to the GGSNs concerned. The GGSNs update their PDP context fields and return Update PDP Context Response (TID). +- 7) The new SGSN informs the GLR of the change of SGSN by sending Update Location (SGSN Number, SGSN Address, and IMSI) to the GLR. +- 8) The GLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with Cancellation Type set to Update Procedure. If the timer described in step 2 is not running, then the old SGSN removes the MM and PDP contexts. Otherwise, the contexts are removed only when the timer expires. This allows the old SGSN to complete the forwarding of N-PDUs. It also ensures that the MM and PDP contexts are kept in the old SGSN in case the MS initiates another inter SGSN routeing area update before completing the ongoing routeing area update to the new SGSN. The old SGSN acknowledges with Cancel Location Ack (IMSI). +- 9) The GLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN. The new SGSN validates the MS's presence in the (new) RA. If due to regional subscription restrictions the MS is not allowed to be attached in the RA, the SGSN rejects the Routeing Area Update Request with an appropriate cause, and may return an Insert Subscriber Data Ack (IMSI, SGSN Area Restricted) message to the GLR. If all checks are successful then the SGSN constructs an MM context for the MS and returns an Insert Subscriber Data Ack (IMSI) message to the GLR. +- 10) The GLR acknowledges the Update Location by sending Update Location Ack (IMSI) to the new SGSN. +- 11) The new SGSN validates the MS's presence in the new RA. If due to roaming restrictions the MS is not allowed to be attached in the SGSN, or if subscription checking fails, then the new SGSN rejects the routeing area update with an appropriate cause. If all checks are successful then the new SGSN constructs MM and PDP contexts for the MS. A logical link is established between the new SGSN and the MS. The new SGSN responds to the MS with Routeing Area Update Accept (P-TMSI, LLC Ack, and P-TMSI Signature). LLC Ack contains the acknowledgements for each LLC connection used by the MS, thereby confirming all mobile-originated N-PDUs successfully transferred before the start of the update procedure. +- 12) The MS acknowledges the new P-TMSI with a Routeing Area Update Complete (P-TMSI, LLC Ack). LLC Ack contains the acknowledgements for each LLC connection used by the MS, thereby confirming all mobile-terminated N-PDUs successfully transferred before the start of the update procedure. If LLC Ack confirms reception of N-PDUs that were forwarded from the old SGSN, then these N-PDUs shall be discarded by the new SGSN. LLC and SNDCP in the MS are reset. + +In the case of a rejected routeing area update operation, due to regional subscription or roaming restrictions, the new SGSN shall not construct an MM context. A reject shall be returned to the MS with an appropriate cause. The MS shall not re-attempt a routeing area update to that RA. The RAI value shall be deleted when the MS is powered-up. + +If the SGSN is unable to update the PDP context in one or more GGSNs, then the SGSN shall deactivate the corresponding PDP contexts as described in subclause "PDP Context Deactivation Initiated by SGSN Procedure". This shall not cause the SGSN to reject the routeing area update. + +If the timer described in step 2 expires and no Cancel Location (IMSI) was received from the GLR, then the old SGSN shall stop forwarding N-PDUs to the new SGSN. + +If the routeing area update procedure fails a maximum allowable number of times, or if the SGSN returns a Routeing Area Update Reject (Cause) message, the MS shall enter IDLE state. + +### 7.3.5 Subscriber Management Procedures + +Whenever the GPRS subscription data is changed for a GPRS subscriber in the HLR, and the changes affect the GPRS subscription data stored in the SGSN, then the SGSN node shall be informed about these changes by means of the following procedures: + +- Insert Subscriber Data procedure, used to add or modify GPRS subscription data in the SGSN; or +- Delete Subscriber Data procedure, used to remove GPRS subscription data in the SGSN. + +#### 7.3.5.1 Insert Subscriber Data Procedure + +In addition to the insertion and modification of general GPRS subscription data for a GPRS subscriber, see TS 29.002 [10], the HLR may request the insertion or modification of one or several new or existing PDP contexts in the SGSN. + +The Insert Subscriber Data procedure is illustrated in Figure 7.3/13. Each step is explained in the following list. + +![Sequence diagram for Insert Subscriber Data Procedure showing interactions between SGSN, GLR, and HLR.](921458d4fc1b778c2450592ac9745b48_img.jpg) + +``` + +sequenceDiagram + participant HLR + participant GLR + participant SGSN + Note left of HLR: 1. Insert Subscriber Data + HLR->>GLR: 1. Insert Subscriber Data + Note left of GLR: 1. Insert Subscriber Data + GLR->>SGSN: 1. Insert Subscriber Data + Note left of SGSN: 2. Insert Subscriber Data Ack + SGSN->>GLR: 2. Insert Subscriber Data Ack + Note left of GLR: 2. Insert Subscriber Data Ack + GLR->>HLR: 2. Insert Subscriber Data Ack + +``` + +Sequence diagram for Insert Subscriber Data Procedure showing interactions between SGSN, GLR, and HLR. + +**Figure 7.3/13: Insert Subscriber Data Procedure** + +- 1) The HLR sends an Insert Subscriber Data (IMSI, GPRS Subscription Data) message to the GLR. The GLR updates its GPRS subscription data and sends an Insert Subscriber Data (IMSI, GPRS Subscription Data) message to the SGSN. +- 2) The SGSN updates its GPRS subscription data and acknowledges the Insert Subscriber Data message by returning an Insert Subscriber Data Ack (IMSI) message. The GLR receives the ack message, then it sends the Insert Subscriber Data Ack (IMSI) message to the HLR. For each PDP context that is included in GPRS Subscription Data the SGSN shall check whether it is a new, an active, or an inactive PDP context: + - For a new or inactive PDP context, no further action is required except storage in the SGSN. + - For an active PDP context, the SGSN shall in addition compare the new QoS Subscribed with QoS Negotiated and shall, if necessary, initiate a PDP Context Modification procedure as described in subclause "Modification Procedures". Furthermore, if VPLMN Address Allowed is changed, the SGSN shall, if necessary (e.g., if the PDP context is currently routed via a GGSN in the VPLMN and VPLMN Address Allowed is changed to not allowed), initiate a PDP Context Deactivation procedure as explained in subclause "Deactivation Procedures". + +#### 7.3.5.2 Delete Subscriber Data Procedure + +In addition to the deletion of general GPRS subscription data for a GPRS subscriber, see TS 29.002 [10], the HLR may request the deletion of one or several PDP contexts from the SGSN. + +The Delete Subscriber Data procedure is illustrated in Figure 7.3/14. Each step is explained in the following list. + +![Sequence diagram for Delete Subscriber Data Procedure showing interactions between SGSN, GLR, and HLR.](0856d34939157228ac3a54a59882fb10_img.jpg) + +``` + +sequenceDiagram + participant HLR + participant GLR + participant SGSN + Note left of HLR: 1. Delete Subscriber Data + HLR->>GLR: 1. Delete Subscriber Data + Note left of GLR: 1. Delete Subscriber Data + GLR->>SGSN: 1. Delete Subscriber Data + Note left of SGSN: 2. Delete Subscriber Data Ack + SGSN->>GLR: 2. Delete Subscriber Data Ack + Note left of GLR: 2. Delete Subscriber Data Ack + GLR->>HLR: 2. Delete Subscriber Data Ack + +``` + +Sequence diagram for Delete Subscriber Data Procedure showing interactions between SGSN, GLR, and HLR. + +**Figure 7.3/14: Delete Subscriber Data Procedure** + +- 1) The HLR sends a Delete Subscriber Data (IMSI, PDP Context Identifiers List) message to the GLR. The GLR deletes its PDP Context indicated and sends an Insert Subscriber Data (IMSI, PDP Context Identifiers List) message to the SGSN. +- 2) The SGSN acknowledges the Delete Subscriber Data message by returning a Delete Subscriber Data Ack (IMSI) message. For each PDP context identifier included in PDP Context Identifiers List, the SGSN shall check whether it belongs to an active or an inactive PDP context: + - For an inactive PDP context no further action is required except deletion of the PDP context. + - For an active PDP context, the SGSN shall initiate the PDP Context Deactivation Initiated by SGSN procedure as explained in subclause "Deactivation Procedures" before the PDP context is deleted. + +### 7.3.6 PDP Context Activation Procedure + +#### 7.3.6.1 Successful Network-Requested PDP Context Activation Procedure with GLR + +The Successful Network-Requested PDP Context Activation procedure is illustrated in Figure 7.3/15. Each step is explained in the following list. + +![Sequence diagram illustrating the Successful Network-Requested PDP Context Activation Procedure with GLR. The diagram shows interactions between MS, SGSN, GLR, IM-GSN, HLR, and GGSN.](83c2ebae8819e9cdca7eb157a13ee26a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant SGSN + participant GLR + participant IM-GSN + participant HLR + participant GGSN + + Note right of GGSN: 1. PDP PDU + GGSN->>HLR: 2. Send Routeing Info for GPRS + HLR-->>GGSN: 2. Send Routeing Info for GPRS Ack + GGSN->>IM-GSN: 3. PDU Notification Request + IM-GSN->>GLR: 3. Send Routeing Info for GPRS + GLR-->>IM-GSN: 3. Send Routeing Info for GPRS Ack + IM-GSN->>SGSN: 3. PDU Notification Request + SGSN-->>IM-GSN: 3. PDU Notification Response + IM-GSN->>GGSN: 3. PDU Notification Response + SGSN->>MS: 4. Request PDP Context Activation + GGSN->>MS: 5. PDP Context Activation procedure + +``` + +Sequence diagram illustrating the Successful Network-Requested PDP Context Activation Procedure with GLR. The diagram shows interactions between MS, SGSN, GLR, IM-GSN, HLR, and GGSN. + +**Figure 7.3/15: Successful Network-Requested PDP Context Activation Procedure** + +- 1) When receiving a PDP PDU the GGSN determines if the Network-Requested PDP Context Activation procedure has to be initiated. The GGSN may store subsequent PDUs received for the same PDP address. +- 2) The GGSN may send a Send Routeing Information for GPRS (IMSI) message to the HLR. If the HLR determines that the request can be served, it returns a Send Routeing Information for GPRS Ack (IMSI, SGSN Address, Mobile Station Not Reachable Reason) message to the GGSN. The SGSN Address parameter includes actually the value of the IM-GSN Address. The Mobile Station Not Reachable Reason parameter is included if the MNRG flag is set in the HLR. The Mobile Station Not Reachable Reason parameter indicates the reason for the setting of the MNRG flag as stored in the MNRR record (see TS 23.040 [5]). If the MNRR record indicates a reason other than 'No Paging Response', the HLR shall include the GGSN number in the GGSN-list of the subscriber. + - If the HLR determines that the request cannot be served (e.g., IMSI unknown in HLR), the HLR shall send a Send Routeing Information for GPRS Ack (IMSI, MAP Error Cause) message. Map Error Cause indicates the reason for the negative response. +- 3) If the SGSN address is present and either Mobile Station Not Reachable Reason is not present or Mobile Station Not Reachable Reason indicates 'No Paging Response', the GGSN shall send a PDU Notification Request (IMSI, PDP Type, PDP Address) message to the IM-GSN indicated by the HLR. Otherwise, the GGSN shall set the + +MNRG flag for that MS. The IM-GSN sends a Send Routeing Information for GPRS (IMSI) message to the GLR. If the GLR determines that the request can be served, it returns a Send Routeing Information for GPRS Ack (IMSI, SGSN Address, Mobile Station Not Reachable Reason) message to the IM-GSN. If the SGSN address is present and either Mobile Station Not Reachable Reason is not present or Mobile Station Not Reachable Reason indicates 'No Paging Response', the IM-GSN shall send a PDU Notification Request (IMSI, PDP Type, PDP Address) message to the SGSN indicated by the GLR. The SGSN returns a PDU Notification Response (Cause) message to the GGSN via the IM-GSN in order to acknowledge that it shall request the MS to activate the PDP context indicated with PDP Address. + +- 4) The SGSN sends a Request PDP Context Activation (TI, PDP Type, and PDP Address) message to request the MS to activate the indicated PDP context. +- 5) The PDP context is activated with the PDP Context Activation procedure (see subclause "PDP Context Activation Procedure" in 3G TS 23.060 [6]). + +#### 7.3.6.2 Unsuccessful Network-Requested PDP Context Activation Procedure with GLR + +If the PDP context requested by the GGSN cannot be established, the SGSN sends a PDU Notification Response (Cause) or a PDU Notification Reject Request (IMSI, PDP Type, PDP Address, Cause) message to the GGSN depending on whether the context activation fails before or after the SGSN has sent a Request PDP Context Activation message to the MS. Cause indicates the reason why the PDP context could not be established: + +- 'IMSI Not Known'. The SGSN has no MM context for that IMSI (Cause in PDU Notification Response). +- 'MS GPRS Detached'. The MM state of the MS is IDLE (Cause in PDU Notification Response). +- 'MS Not GPRS Responding'. The MS is GPRS-attached to the SGSN but the MS does not respond. This may be due to: + - the lack of a response to a GPRS Paging Request; + - an Abnormal RLC condition, or + - no Activate PDP Context Request message received within a certain time after the Request PDP Context Activation message was delivered to the MS (Cause in PDU Notification Reject Request). +- 'MS Refuses'. The MS refuses explicitly the network-requested PDP context (Cause in PDU Notification Reject Request). + +When receiving the PDU Notification Response or the PDU Notification Reject Request message the GGSN may reject or discard the PDP PDU depending on the PDP type. + +After an unsuccessful Network-Requested PDP Context Activation procedure the network may perform some actions to prevent unnecessary enquires to the HLR. The actions taken depend on the cause of the delivery failure. + +- If the MS is not reachable or if the MS refuses the PDP PDU (Cause value 'MS Not GPRS Responding' or 'MS Refuses'), then the SGSN shall not change the setting of MNRG for this MS. The GGSN may refuse any PDP PDU for that PDP address during a certain period. The GGSN may store the SGSN address during a certain period and send subsequent PDU Notification Request messages to that SGSN via IM-GSN. +- If the MS is GPRS-detached or if the IMSI is not known in the SGSN (Cause value 'MS GPRS Detached' or 'IMSI Not Known'), then the SGSN, the GGSN, and the HLR may perform the Protection and Mobile User Activity procedures. + +The Protection procedure is illustrated in Figure 7.3/16. Each step is explained in the following list. + +![Sequence diagram illustrating the Protection Procedure between SGSN, GLR, IM-GSN, HLR, and GGSN.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +``` + +sequenceDiagram + participant SGSN + participant GLR + participant IM-GSN + participant HLR + participant GGSN + + Note left of SGSN: 1. PDU Notification Response + SGSN->>IM-GSN: 1. PDU Notification Response + IM-GSN->>GGSN: 1. PDU Notification Response + Note left of SGSN: 2. PDU Notification Reject Request + SGSN->>IM-GSN: 2. PDU Notification Reject Request + IM-GSN->>GGSN: 2. PDU Notification Reject Request + Note left of GGSN: 2. PDU Notification Reject Response + GGSN->>IM-GSN: 2. PDU Notification Reject Response + IM-GSN->>SGSN: 2. PDU Notification Reject Response + Note left of GLR: 3. Send Routeing Info for GPRS + GLR->>IM-GSN: 3. Send Routeing Info for GPRS + IM-GSN->>GLR: 3. Send Routeing Info for GPRS Ack + Note left of GLR: 4. Failure Report + GLR->>IM-GSN: 4. Failure Report + IM-GSN->>GLR: 4. Failure Report Ack + Note left of HLR: 3. Send Routeing Info for GPRS + HLR->>GGSN: 3. Send Routeing Info for GPRS + GGSN->>HLR: 3. Send Routeing Info for GPRS Ack + Note left of HLR: 4. Failure Report + HLR->>GGSN: 4. Failure Report + GGSN->>HLR: 4. Failure Report Ack + +``` + +Sequence diagram illustrating the Protection Procedure between SGSN, GLR, IM-GSN, HLR, and GGSN. + +**Figure 7.3/16: Protection Procedure** + +- 1) If the MM context of the mobile is IDLE or if the SGSN has no information about that user, the SGSN returns a PDU Notification Response (Cause) message to the GGSN via IM-GSN with Cause equal to 'MS GPRS Detached' or 'IMSI Not Known', otherwise the Cause shall be 'Activation Proceeds'. If the Cause is 'MS GPRS Detached' or 'IMSI Not Known' and if the SGSN has an MM context for that user, the SGSN sets MNRG to indicate the need to report to the HLR when the next contact with that MS is performed. +- 2) If the MS does not respond or refuses the activation request, the SGSN sends a PDU Notification Reject Request (IMSI, PDP Type, PDP Address, Cause) message to the GGSN via IM-GSN with Cause equal to 'MS Not GPRS Responding' or 'MS Refuses'. The GGSN returns a PDU Notification Reject Response message to the SGSN via IM-GSN. +- 3) If Cause equals 'IMSI Not Known' the IM-GSN may send a Send Routeing Information for GPRS (IMSI) message to the GLR before sending the PDU Notification response to GGSN. The GLR returns a Send Routeing Information for GPRS Ack (IMSI, SGSN Address, and Cause) message to the IM-GSN indicating the address of the SGSN that currently serves the MS. If SGSN Address is different from the one previously stored by the IM-GSN, then steps 3, 4, and 5 in Figure 6 are followed. +If Cause equals 'IMSI Not Known' the GGSN may send a Send Routeing Information for GPRS (IMSI) message to the HLR. The HLR returns a Send Routeing Information for GPRS Ack (IMSI, SGSN Address, Cause) message to the GGSN (Note that the SGSN Address parameter includes actually the value of the IM-GSN Address.) indicating the address of the IM-GSN that currently serves the MS. If IM-GSN Address is different from the one previously stored by the GGSN, then steps 3, 4, and 5 in Figure 6 are followed. +- 4) If SGSN Address is the same as the one previously stored in the IM-GSN or if the Cause value returned in step 1 equals 'MS GPRS Detached', then the IM-GSN sets MNRG for that PDP address and sends a Failure Report (IMSI) message to the GLR to request MNRG to be set in the GLR. The GLR sets (if not already set) MNRG for the IMSI. Note that GLR does not store IM-GSN address and IM-GSN address to report to when activity from that IMSI is detected, and IM-GSN forgets the SGSN address after receiving PDU notification response or sending PDU notification reject response. +If IM-GSN Address is the same as the one previously stored in the GGSN, or if the Cause value returned in step 1 equals 'MS GPRS Detached', then the GGSN sets MNRG for that PDP address and sends a Failure Report (IMSI, GGSN Number, GGSN Address) message to the HLR to request MNRG to be set in the HLR. The HLR sets (if not already set) MNRG for the IMSI and adds GGSN Number and GGSN Address to the list of GGSNs to report to when activity from that IMSI is detected. GGSN Number is either the number of the GGSN, or, if a protocol converting GSN is used as an intermediate node, the number of the protocol-converting GSN. GGSN Address is an optional parameter that shall be included if a protocol-converting GSN is used. + +The Mobile User Activity procedure is illustrated in Figure 7.3/17. Each step is explained in the following list. + +![Sequence diagram for Mobile User Activity Procedure. Lifelines: MS, SGSN, GLR, HLR, GGSN. The sequence starts with an Attach Request from MS to SGSN. SGSN then sends '2a. Ready for SM' to GLR, which forwards it to HLR. SGSN also sends '2b. Update Location' to GLR, which forwards it to HLR. HLR sends '2c. Ready for SM' to GLR, which forwards it to SGSN. Finally, HLR sends '3. Note MS GPRS Present' to GGSN.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` + +sequenceDiagram + participant MS + participant SGSN + participant GLR + participant HLR + participant GGSN + Note left of MS: 1. Attach Request + MS->>SGSN: 1. Attach Request + Note right of SGSN: 2a. Ready for SM + SGSN->>GLR: 2a. Ready for SM + Note right of GLR: 2a. Ready for SM + GLR->>HLR: 2a. Ready for SM + Note right of SGSN: 2b. Update Location + SGSN->>GLR: 2b. Update Location + Note right of GLR: 2b. Update Location + GLR->>HLR: 2b. Update Location + Note right of GLR: 2c. Ready for SM + GLR->>SGSN: 2c. Ready for SM + Note right of HLR: 3. Note MS GPRS Present + HLR->>GGSN: 3. Note MS GPRS Present + +``` + +Sequence diagram for Mobile User Activity Procedure. Lifelines: MS, SGSN, GLR, HLR, GGSN. The sequence starts with an Attach Request from MS to SGSN. SGSN then sends '2a. Ready for SM' to GLR, which forwards it to HLR. SGSN also sends '2b. Update Location' to GLR, which forwards it to HLR. HLR sends '2c. Ready for SM' to GLR, which forwards it to SGSN. Finally, HLR sends '3. Note MS GPRS Present' to GGSN. + +**Figure 7.3/17: Mobile User Activity Procedure** + +- 1) The SGSN receives an indication that an MS is reachable, e.g., an Attach Request message from the MS. +- 2a) If the SGSN contains an MM context of the MS and MNRG for that MS is set, the SGSN shall send a Ready for SM (IMSI, MS Reachable) message to the GLR and clears MNRG for that MS. The GLR sends it without modification at the application level to HLR and clears MNRG for that MS. +- 2b) If the SGSN does not keep the MM context of the MS, the SGSN shall send an Update Location message (see subclause "Attach Function") to the GLR. If the GLR does not keep the MM context of the MS, the SGSN shall send an Update Location message (see subclause "Attach Function") to the HLR. +- 2c) If the GLR contains an MM context of the MS and MNRG for that MS is set, the SGSN shall send a Ready for SM (IMSI, MS Reachable) message to the HLR and clears MNRG for that MS. +- 3) When the HLR receives the Ready for SM message or the Update Location message for an MS that has MNRG set, it clears MNRG for that MS and sends a Note MS GPRS Present (IMSI, SGSN Address) message to all the GGSNs in the list of the subscriber. (The Ready for SM message also triggers the SMS alert procedure as described in subclause "Unsuccessful Mobile-terminated SMS Transfer".) SGSN Address contains the address of the IM-GSN that currently serves the MS. Upon reception of Note MS Present, each GGSN shall clear MNRG. + +## 7.4 Purge MS Procedure + +This Purge MS procedure is used to cause the HLR to mark its data for an MS so that any request for routing information for a mobile terminated call, a mobile terminated short message or Network-requested PDP context activation will be treated as if the MS is not reachable. It is invoked when the subscriber record for the MS is to be deleted in the VLR or SGSN, either by MMI interaction or automatically, e.g. because the MS has been inactive for several days. This procedure is illustrated in figure 7.4/1. Each step is explained in the following list. + +![Sequence diagram for Purge MS procedure. Lifelines: VLR or SGSN, GLR, HLR. The sequence starts with a Purge MS message from VLR or SGSN to GLR. GLR then sends a Purge MS message to HLR. HLR sends a Purge MS ack back to GLR. Finally, GLR sends a Purge MS ack back to VLR or SGSN.](236f674770a03c918c0375a74fe950db_img.jpg) + +``` + +sequenceDiagram + participant VLR_SGSN as VLR or SGSN + participant GLR + participant HLR + Note left of VLR_SGSN: 1. Purge MS + VLR_SGSN->>GLR: 1. Purge MS + Note right of GLR: 2. Purge MS + GLR->>HLR: 2. Purge MS + Note right of HLR: 3. Purge MS ack + HLR->>GLR: 3. Purge MS ack + Note right of GLR: 4. Purge MS ack + GLR->>VLR_SGSN: 4. Purge MS ack + +``` + +Sequence diagram for Purge MS procedure. Lifelines: VLR or SGSN, GLR, HLR. The sequence starts with a Purge MS message from VLR or SGSN to GLR. GLR then sends a Purge MS message to HLR. HLR sends a Purge MS ack back to GLR. Finally, GLR sends a Purge MS ack back to VLR or SGSN. + +**Figure 7.4/1: Purge MS procedure** + +#### Procedure: + +- 1) The serving node, i.e., the VLR or the SGSN, sends a Purge MS message to the GLR. + +- 2) When the GLR receives the Purge MS message from the serving node, it checks whether the subscriber is registered. If the subscriber is not registered, the GLR may report an error to the O&M interface, and sends back a negative response to the serving node. If the subscriber is registered, the GLR checks whether the purging notification came from the serving node where the MS was last registered. + - If the serving node that sent the purge MS request is the registered serving node, the GLR transports the received message to the HLR. + - If the serving node that sent the purge MS request is not the registered serving node, the GLR sends a purge MS ack to the serving node indicating that the TMSI or P-TMSI shall not be frozen. +- 3) When the GLR receives the response from the HLR, the GLR deletes the subscriber data and transports the received message to the serving node. +- 4) The serving node receives the Purge MS ack message indicating successful outcome of the procedure. + +### 7.4.1 Functional requirements of GLR + +#### 7.4.1.1 Process Purge\_MS\_GLR + +Figure 7.4/2 shows SDL chart for Process Purge\_MS\_GLR. + +![Flowchart for Process Purge_MS_GLR. The process starts at an 'Idle' state, receives a 'Purge MS' signal from a VLR or SGSN, checks parameters according to TS 23.018, and then evaluates if the subscriber is registered and if the purge indication came from the registered serving node. Depending on these checks, it either sets the GLR number as an SGSN or VLR number, sends a 'Purge MS' signal, and waits for a response, or it sends a negative response and returns to the 'Idle' state.](5e9af8986a5845504f251d3079da8078_img.jpg) + +### Process Purge\_MS\_GLR + +1(2) + +GLR application process for Purge MS. + +Signals from/to left are from/to VLR or SGSN. Signals from/to right are from/to HLR. + +``` +graph TD; Start([Idle]) --> PurgeMS{Purge MS}; PurgeMS --- P1[from VLR or SGSN]; PurgeMS --> CheckParam[Check Parameter]; CheckParam --- P2[See TS 23.018]; CheckParam --> ResultPass{Result= Pass?}; ResultPass -- No --> End([Idle]); ResultPass -- Yes --> SubReg{Subscriber registered?}; SubReg -- No --> NegResp[Set negative response := Subscriber unknown.]; SubReg -- Yes --> FromNode{Purge MS indication came from the registered serving node}; FromNode -- No --> Ack{Purge MS ack}; FromNode -- Yes --> FromVLR{Purge MS from VLR?}; FromVLR -- No --> SetSGSN[Set GLR Number as SGSN Number]; FromVLR -- Yes --> SetVLR[Set GLR Number as VLR Number]; SetSGSN --> PurgeMSOut{Purge MS}; SetVLR --> PurgeMSOut; PurgeMSOut --> WaitForResp([Wait_For_Response]); PurgeMSOut --> End; NegResp --> NegRespOut{Purge MS negative response}; NegRespOut --> End; Ack --> NoFlag[Don't set Flag Freeze IMSI or P-TMSI]; NoFlag --> End; +``` + +Flowchart for Process Purge\_MS\_GLR. The process starts at an 'Idle' state, receives a 'Purge MS' signal from a VLR or SGSN, checks parameters according to TS 23.018, and then evaluates if the subscriber is registered and if the purge indication came from the registered serving node. Depending on these checks, it either sets the GLR number as an SGSN or VLR number, sends a 'Purge MS' signal, and waits for a response, or it sends a negative response and returns to the 'Idle' state. + +Figure 7.4/2(1): Process Purge\_MS\_GLR + +![Flowchart for Process Purge_MS_GLR](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +### Process Purge\_MS\_GLR + +2(2) + +GLR application process for Purge MS. + +Signals from/to left are from/to VLR or SGSN. +Signals from/to right are from/to HLR. + +``` +graph TD; Start([Wait_For_Response]) --> PurgeMSack1[Purge MS ack]; Start --> PurgeMSneg[Purge MS negative response]; PurgeMSack1 --> Decision{Purge MS from VLR?}; Decision -- No --> DeletePS[delete subscriber data for PS]; Decision -- Yes --> DeleteCS[delete subscriber data for CS]; DeletePS --> PurgeMSack2[Purge MS ack]; DeleteCS --> PurgeMSack2; PurgeMSack2 --> SendHLR[Send as it is received from the HLR.]; PurgeMSneg --> Abort{Abort}; SendHLR --> Idle([Idle]); Abort --> Idle; +``` + +The flowchart illustrates the 'Process Purge\_MS\_GLR' starting from a 'Wait\_For\_Response' state. It branches into two potential incoming signals: 'Purge MS ack' and 'Purge MS negative response'. The 'Purge MS ack' path leads to a decision 'Purge MS from VLR?'. If 'No', it proceeds to 'delete subscriber data for PS'. If 'Yes', it proceeds to 'delete subscriber data for CS'. Both deletion paths lead to a 'Purge MS ack' state, which then leads to 'Send as it is received from the HLR.'. The 'Purge MS negative response' path leads to an 'Abort' state. Both the 'Send as it is received from the HLR.' and 'Abort' states lead to the final 'Idle' state. + +Flowchart for Process Purge\_MS\_GLR + +Figure 7.4/2(2): Process Purge\_MS\_GLR + +## 7.5 Regional Restriction Procedure + +In the case that GLR is introduced, during second and subsequent location updating, there is no interaction between the GLR and the HLR. However, the regional restriction service needs the location updating procedure towards the HLR. + +The GLR stores the Zone Code List sent by the HLR in the Insert Subscriber Data message. On the location updates the GLR sends its stored Zone Code list to the VLR and/or SGSN (refer to figure 7.2/10). The GLR stores also the MSC area restricted flag and/or the SGSN are restricted flag. These flags are set "False" if the location updating procedure executed successfully. + +When the GLR receives the Insert Subscriber Data Acknowledge message indicating "MSC area restricted" or "SGSN area restricted" and the MSC area restricted flag or the SGSN area restricted flag is set as "False", the GLR initiates the location updating procedure toward the HLR. In addition, the GLR sets the MSC area restricted flag or the SGSN area restricted flag "True". Also, the HLR sets the MSC area restricted flag or the SGSN area restricted flag "True", and the location updating for the IMSI is rejected. These flags contribute to the "MS Not Reachable" state for handling of terminating traffic (i.e. mobile terminated call and mobile terminated SMS and so on) in the HLR. + +![Sequence diagram of the Regional Restriction Procedure (MS Enters a restricted Area). The diagram shows interactions between old VLR/old SGSN, new VLR/new SGSN, GLR, and HLR. It is divided into 'First Location Updating' and 'Second and Further Location Updating' phases. In the first phase, the new VLR sends an Update Location to the GLR, which forwards it to the HLR. The HLR responds with Insert Subscriber Data (Zone Code List) to the GLR, which stores it and then sends it to the new VLR. In the second phase, the new VLR sends an Update Location to the GLR. The GLR responds with Insert Subscriber Data (Zone Code List). The new VLR becomes 'Aware of whole new MSC area restricted'. The GLR then sends an Insert Subscriber Data ack (MSC area restricted) to the new VLR. The GLR then 'Identifies restricted and Decides to initiate UL', sending an Update Location to the HLR. The HLR responds with Insert Subscriber Data, which the GLR acknowledges. The HLR then sets 'the MSC area restricted flag' and sends an Update Location ack or Update GPRS Location ack (Rejected) to the GLR, which in turn sends a rejected ack to the new VLR.](1399c76ef88f22b70d05ed3f781d3c48_img.jpg) + +``` + +sequenceDiagram + participant old_VLR as old VLR/old SGSN + participant new_VLR as new VLR/new SGSN + participant GLR + participant HLR + + Note left of old_VLR: First Location Updating + new_VLR->>GLR: 1. Update Location or Update GPRS Location + GLR->>HLR: 2. Update Location or Update GPRS Location + HLR->>GLR: 3. Insert Subscriber Data (Zone Code List) + Note right of GLR: Store Zone Code List + GLR->>new_VLR: 4. Insert Subscriber Data (Zone Code List) + + Note left of old_VLR: Second and Further Location Updating + new_VLR->>GLR: 5. Update Location or Update GPRS Location + GLR->>new_VLR: 6. Insert Subscriber Data (Zone Code List) + Note right of new_VLR: Aware of whole new MSC area restricted + new_VLR->>GLR: 7. Insert Subscriber Data ack (MSC area restricted) + Note right of GLR: Identifies restricted and Decides to initiate UL + GLR->>HLR: 8. Update Location or Update GPRS Location + HLR->>GLR: 9. Insert Subscriber Data + GLR->>HLR: 10. Insert Subscriber Data ack (MSC area restricted) + Note right of HLR: "the MSC area restricted flag" is set + HLR->>GLR: 11. Update Location ack or Update GPRS Location ack (Rejected) + GLR->>new_VLR: 12. Update Location ack or Update GPRS Location ack (Rejected) + +``` + +Sequence diagram of the Regional Restriction Procedure (MS Enters a restricted Area). The diagram shows interactions between old VLR/old SGSN, new VLR/new SGSN, GLR, and HLR. It is divided into 'First Location Updating' and 'Second and Further Location Updating' phases. In the first phase, the new VLR sends an Update Location to the GLR, which forwards it to the HLR. The HLR responds with Insert Subscriber Data (Zone Code List) to the GLR, which stores it and then sends it to the new VLR. In the second phase, the new VLR sends an Update Location to the GLR. The GLR responds with Insert Subscriber Data (Zone Code List). The new VLR becomes 'Aware of whole new MSC area restricted'. The GLR then sends an Insert Subscriber Data ack (MSC area restricted) to the new VLR. The GLR then 'Identifies restricted and Decides to initiate UL', sending an Update Location to the HLR. The HLR responds with Insert Subscriber Data, which the GLR acknowledges. The HLR then sets 'the MSC area restricted flag' and sends an Update Location ack or Update GPRS Location ack (Rejected) to the GLR, which in turn sends a rejected ack to the new VLR. + +Figure 7.5/1: Regional Restriction Procedure (MS Enters a restricted Area) + +When the GLR receives the Insert Subscriber Data Acknowledge message indicating "MSC area restricted" or "SGSN area restricted" and the MSC area restricted flag or the SGSN area restricted flag is set as "True", The GLR reject the location updating procedure for the IMSI. No interaction with the HLR is needed. + +When the user returns to an MSC area that is not restricted due to regional subscription (see figure 7.2/11), i.e., when the GLR receives the Insert Subscriber Data Acknowledge message NOT indicating "MSC area restricted" or "SGSN area restricted" and the MSC area restricted flag or the SGSN area restricted flag is set as "True", the GLR initiates the location updating procedure toward the HLR. + +![Sequence diagram of the Regional Restriction Procedure (MS leaves the restricted area).](a634891d16b60b21df90a35c2af72c67_img.jpg) + +The diagram illustrates the sequence of messages for the Regional Restriction Procedure when a mobile station (MS) leaves a restricted area. It involves four main entities: VLROLD, VLRNEW, GLR, and HLR, grouped into Visited NW and Home NW. + +**Sequence of Messages:** + +- 1. Update Location:** VLRNEW sends a message to GLR. +- 2. Insert Subscriber Data (Zone Code List):** GLR sends a message to VLRNEW. A note indicates VLRNEW is "Aware of Not whole new MSC area restricted". +- 3. Insert Subscriber Data ack:** VLRNEW sends a message to GLR. A note indicates GLR "Identifies No more restricted and Decides to initiate UL". +- 4. Update Location:** GLR sends a message to HLR. +- 5. Insert Subscriber Data:** HLR sends a message to GLR. +- 6. Insert Subscriber Data ack:** GLR sends a message to HLR. A note indicates "the MSC area restricted flag" is cleared. +- 7. Update Location ack:** HLR sends a message to GLR. +- 8. Update Location ack:** GLR sends a message to VLRNEW. + +**Initial Context:** A box at the top states: "The Regional Restriction Procedure was initiated on location updating In the previously visited VLR". + +Sequence diagram of the Regional Restriction Procedure (MS leaves the restricted area). + +Figure 7.5/2: Regional Restriction Procedure (MS leaves the restricted area) + +## 7.6 Recovery and Restoration + +The recovery and restoration procedures are intended to maintain service if inconsistencies in databases occur and at lost or invalid database information. "Invalid" in this context means that the database entry cannot be regarded as reliable. + +### 7.6.1 GLR Failure + +A consequence of GLR restart is that an Update Location has to be performed for all roaming subscribers within the VPLMN. + +The GLR will keep a part of the IMSI record in non-volatile memory by periodical backup. If the IMSI record in main memory is lost or broken by restart, it is retrieved from non-volatile backup memory as in HLR. This backup data would contain enough information to send "Provide Roaming Number" message to the VLR when it is requested by the HLR. The data which shall be stored in backed-up would be "VLR number", "SGSN number", "IMSI". + +In case of GLR restart, it sends "Reset" message including the GLR number as the HLR number to VLR/SGSN where one or more of its mobile terminals are registered to prompt location updating attempt from VLR/SGSN. On receiving the location updating request, the GLR relays it to the HLR to restore its location and subscriber data. The restoration trigger can be the normal location updating from mobile terminal, call origination and call termination and so on. + +The assumption in the case of terminating call in circuit switched service is that GLR would have VLR number in non-volatile memory so that it could know the exact VLR mobile terminal registered. If GLR loses VLR number or has only old VLR number, it loses the opportunity to restore its data at the timing of terminating call. This situation is the same as the case of HLR that loses VLR number after restart. + +Also in this case, GLR shall have an indicator representing restart of GLR. This indicator is set "Not Confirmed" when GLR restarts, and kept the status until subscriber profile is successfully downloaded from HLR. This shall be triggered by radio contact of the mobile terminal. + +The restoration indicator is called the "Location and Subscriber information Confirmed by HLR" (LSIC) and defined as follows: + +If the LSIC is set to "Not confirmed," the GLR send Update Location message to HLR. + +"Location and Subscriber information confirmed by HLR" is set to "Not Confirmed" at any of following events: + +- The GLR receives an "Update Location" request for an MS for which the GLR has no IMSI records. +- The GLR receives a "Reset" message from the HLR with which the MS is registered. +- The GLR detects the restart of itself and the IMSI record does not seem to be guaranteed (e.g. data retrieved from backup non-volatile memory). + +"Location and Subscriber information confirmed by HLR" is set to "Confirmed" at any of following events: + +- The GLR successfully performs an "Update Location" to the HLR. + +The recovery procedure of GLR Failure is illustrated in Figure 7.6/1. Each step is explained in the following list. + +![Sequence diagram illustrating the recovery of the GLR. The diagram shows three lifelines: VLR or SGSN, GLR, and HLR. The GLR initiates a 'Restart' (indicated by a starburst). The sequence of messages is: 1. Reset (GLR to VLR or SGSN); 2. Update Location or Restore Data (VLR or SGSN to GLR); 3. Insert Subscriber Data (GLR to HLR); 3. Insert Subscriber Data ack (HLR to GLR); 3. Insert Subscriber Data ack (GLR to VLR or SGSN); 4. Update Location ack or Restore Data ack (HLR to GLR); 4. Update Location ack or Restore Data ack (GLR to VLR or SGSN). A note indicates that the VLR/SGSN receives a Mobile Originated Activity/Location Updating Request or Mobile Terminated Request after the Reset message.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +``` + +sequenceDiagram + participant VLR or SGSN + participant GLR + participant HLR + Note right of GLR: Restart + GLR->>VLR or SGSN: 1. Reset + Note over VLR or SGSN: The VLR/SGSN received Mobile Originated Activity/Location Updating Request or Mobile Terminated Request + VLR or SGSN->>GLR: 2. Update Location or Restore Data + GLR->>HLR: 3. Insert Subscriber Data + HLR->>GLR: 3. Insert Subscriber Data ack + GLR->>VLR or SGSN: 3. Insert Subscriber Data ack + HLR->>GLR: 4. Update Location ack or Restore Data ack + GLR->>VLR or SGSN: 4. Update Location ack or Restore Data ack + +``` + +Sequence diagram illustrating the recovery of the GLR. The diagram shows three lifelines: VLR or SGSN, GLR, and HLR. The GLR initiates a 'Restart' (indicated by a starburst). The sequence of messages is: 1. Reset (GLR to VLR or SGSN); 2. Update Location or Restore Data (VLR or SGSN to GLR); 3. Insert Subscriber Data (GLR to HLR); 3. Insert Subscriber Data ack (HLR to GLR); 3. Insert Subscriber Data ack (GLR to VLR or SGSN); 4. Update Location ack or Restore Data ack (HLR to GLR); 4. Update Location ack or Restore Data ack (GLR to VLR or SGSN). A note indicates that the VLR/SGSN receives a Mobile Originated Activity/Location Updating Request or Mobile Terminated Request after the Reset message. + +**Figure 7.6/1: Recovery of the GLR** + +#### Procedure: + +1. After restart of the GLR it sets the "LSIC" "not confirmed" and sends the *Reset* message to the VLR and/or SGSN. The VLR sets the indicator "Location Information Confirmed in HLR" of affected user "not confirmed" and waits for access from/to the user. +2. After identifying access from the user and successful authentication the VLR or SGSN sends *Update Location* message to the GLR. After identifying access to the user and successful authentication the VLR or SGSN sends *Restore data* message to the GLR. If the GLR identifies the "LSIC" set in "Not Confirmed", it relays the message to the HLR. +3. When the HLR receives the *Update Location* or *Restore Data* message from the GLR, it initiates insert subscriber procedure. During the procedure the GLR relay messages. +4. After the insert subscriber procedure, the HLR returns *Update Location ack* or *Restore Data ack* message to the VLR via the GLR. When the VLR and the GLR receives the message, each indicator in both nodes is set "confirmed". + +### 7.6.2 HLR Failure + +In the case of HLR restart when the GLR receives a reset message from a HLR, it marks all subscriber records for which the HLR number matches the HLR number received in the reset message. This indicates that when the MS next makes radio contact the GLR needs to initiate a location registration procedure to the HLR. If the HLR included an HLR-ID list in the reset message, then only those subscriber records for which the leading digits of the IMSI match one of the HLR-IDs in the HLR-ID list will be marked. + +Then the GLR sends a *RESET* message, which includes the GLR number as the HLR number and HLR-ID list if the GLR received it from the HLR, to the serving node (i.e. VLR or SGSN). The receiving serving node may use the HLR number or HLR-ID list (if present) to identify the affected users. In the case that the serving node uses the HLR number, it regards the users as affected, whose subscriber record stores the number as HLR number equal to the received GLR number. On the other hand in the case that the serving node uses the HLR-ID list, it regards the users as affected, whose IMSI has the leading digits equal to one of HLR-IDs. After that when the affected user accesses the network, the serving node initiates a location registration procedure to the GLR. When the GLR receives an *Update Location* message from the serving node and identifies that the subscriber record in the GLR is marked as needing to notify the HLR when the MS makes radio contact then the GLR sends the *Update Location* message to the HLR. + +The recovery procedure of HLR Failure is illustrated in Figure 7.6/2. Each step is explained in the following list. + +![Sequence diagram illustrating the recovery procedure of HLR Failure. The diagram shows interactions between a Visited Network (Visited NW) containing a VLR and a GLR, and a Home Network (Home NW) containing an HLR. The process starts with an HLR Restart. The GLR sends a Reset message to the HLR. The HLR responds with a Reset message to the GLR. The GLR marks subscriber records for affected users. When a VLR receives a Mobile Originated Activity/Location Updating Request or Mobile Terminated Request, it sends an Update Location message to the GLR. The GLR identifies the registration as coming from an affected user and sends an Update Location message to the HLR. The HLR responds with Insert Subscriber Data, which the GLR forwards to the VLR. The VLR responds with Insert Subscriber Data ack, which the GLR forwards to the HLR. The HLR then sends Forward Check SS ind to the GLR, which is forwarded to the VLR (optional for CS domain). Finally, the HLR sends Update Location ack to the GLR, which is forwarded to the VLR.](17f0cf80b9c38adb460d4ca836960da7_img.jpg) + +``` + +sequenceDiagram + participant VLR + participant GLR + participant HLR + Note right of HLR: Restart + HLR->>GLR: 1. Reset (HLR No, HLR id List(*)) + Note right of GLR: Mark subscriber records for all affected users + GLR->>VLR: 2. Reset (GLR No, HLR id List(*)) + Note right of VLR: The VLR received Mobile Originated Activity/Location Updating Request Or Mobile Terminated Request + VLR->>GLR: 3. Update Location + Note right of GLR: Identify this registration comes from affected user + GLR->>HLR: 3. Update Location + HLR->>GLR: 4. Insert Subscriber Data + GLR->>VLR: 4. Insert Subscriber Data + VLR->>GLR: 4. Insert Subscriber Data ack + GLR->>HLR: 4. Insert Subscriber Data ack + Note right of HLR: Optional for CS domain + HLR->>GLR: 5. Forward Check SS ind + GLR->>VLR: 5. Forward Check SS ind + HLR->>GLR: 6. Update Location ack + GLR->>VLR: 6. Update Location ack + +``` + +(\*) This parameter is optionally provided by HLR + +Sequence diagram illustrating the recovery procedure of HLR Failure. The diagram shows interactions between a Visited Network (Visited NW) containing a VLR and a GLR, and a Home Network (Home NW) containing an HLR. The process starts with an HLR Restart. The GLR sends a Reset message to the HLR. The HLR responds with a Reset message to the GLR. The GLR marks subscriber records for affected users. When a VLR receives a Mobile Originated Activity/Location Updating Request or Mobile Terminated Request, it sends an Update Location message to the GLR. The GLR identifies the registration as coming from an affected user and sends an Update Location message to the HLR. The HLR responds with Insert Subscriber Data, which the GLR forwards to the VLR. The VLR responds with Insert Subscriber Data ack, which the GLR forwards to the HLR. The HLR then sends Forward Check SS ind to the GLR, which is forwarded to the VLR (optional for CS domain). Finally, the HLR sends Update Location ack to the GLR, which is forwarded to the VLR. + +**Figure 7.6/2: Recovery procedure of HLR Failure** + +#### **Procedure:** + +1. When the HLR restart occurs and the GLR receives a *RESET* message, the GLR identifies affected users by received HLR number and sets the indicator ("LSIC") "not confirmed" for the users. If the HLR included an HLR-ID list in the reset message, then only those subscriber records for which the leading digits of the IMSI match one of the HLR-IDs in the HLR-ID list will be marked. +2. The GLR sends reset messages to the serving node where the affected users are roaming. The reset message includes the GLR number as HLR number and HLR-ID list if the GLR receives it from the HLR. Receiving serving node may regard the users as affected by HLR number or HLR-ID list (if present). + +3. When the affected user accesses the network, the serving node initiates an update location procedure to the GLR. If the GLR identifies that the indicator ("LSIC") set to "not confirmed" for the user, it relays the message to the HLR. +4. When the HLR receives the *Update Location* message, it initiates the insert subscriber data procedure. During the procedure the GLR relays the messages between the serving node and HLR transparently. +5. If the HLR implements Forward Check SS indication, it sends the *Forward Check SS ind* message to the GLR and the GLR relays the message to the VLR. (implemented only for CS domain). +6. When the serving node receives the *Update Location ack* message, the restoration procedure is completed. + +#### 7.6.2.1 Suppression of Intra-PLMN signalling + +During the HLR restoration procedure involving the GLR, the GLR notifies the GLR number as the HLR number to the serving node in a *Reset* message. Therefore, in case the serving node does not use the HLR-ID list (i.e. the case that HLR did not send the HLR-ID list to the serving node via GLR or the case that the serving node does not support the usage of the HLR-ID list), the serving node regards all users accommodated into the GLR as affected. This leads to the unnecessary location updates for the restoration of the users not from the restarting HLR. To suppress this unnecessary signalling within VPLMN some mechanism as shown in following subsections may be used. + +##### 7.6.2.1.1 Usage of the HLR id List (Tool 1) + +In this tool the GLR generates HLR-ID list, which is composed of MCC+MNC, by translating the CC and NDC of the HLR and sends it to the serving node in the *Reset* message. On receiving the HLR-ID list the serving node may or may not use this. If the serving node uses the HLR-ID list and identifies HPLMN where the restarting HLR exists, no unnecessary signaling traffic for the users from the other PLMNs occurs. + +##### 7.6.2.1.2 Multiple GLR number allocation (Tool 2) + +In this tool the GLR has multiple GLR numbers corresponding to each HLR. The numbers, which can be routed to the GLR, are allocated as multiple GLR numbers. The correspondence between HLR numbers and GLR numbers is statistically kept in the non-volatile memory. See Figure 7.6/3. + +![Diagram illustrating Multiple GLR number allocation. It shows HLR#1, HLR#2, HLR#3, ..., HLR#n connected to a central GLR box. The GLR box contains multiple GLR numbers: #A, #B, #C. Arrows labeled 'Reset #1', 'Reset #A', and 'Reset #A' point from the GLR to VLR#1 and VLR#2. A table on the left shows the correspondence between HLR# and GLR#.](c4e30d3e93833e47634647ab593db2ff_img.jpg) + +| HLR# | GLR# | +|------|------| +| #1 | #A | +| #2 | #B | +| #3 | #C | + +Diagram illustrating Multiple GLR number allocation. It shows HLR#1, HLR#2, HLR#3, ..., HLR#n connected to a central GLR box. The GLR box contains multiple GLR numbers: #A, #B, #C. Arrows labeled 'Reset #1', 'Reset #A', and 'Reset #A' point from the GLR to VLR#1 and VLR#2. A table on the left shows the correspondence between HLR# and GLR#. + +Figure 7.6/3: Multiple GLR number allocation + +Possible scenarios for GLR number allocation are as follows. + +In this tool, if one GLR number is allocated for one HLR and VPLMN has the roaming agreements with many PLMNs, many GLR numbers are needed. + +As possible variation of scenario, a GLR number may be assigned to a group of HLRs. This group can be grouped by, for instance, country code or network destination code and so on. If one GLR number is assigned for many HLRs, the occupied address space is small, however the unnecessary signalling traffic for the users not associated to restarting HLR increases. On the other hand, if one GLR number is assigned for few HLRs, the unnecessary signalling traffic is small, however the occupied address space is larger. + +How many HLRs are grouped is operator dependent. + +### 7.6.3 VLR Failure + +In the case of VLR restart, the VLR retrieves subscriber data from the GLR to recover its database. The required capability of the GLR to support this procedure is the same as that of the HLR in the case of VLR restart without GLR. The procedure is described in 3G TS 23.007 [2]. + +Basically, data recovery is achieved through the restore procedure requested from the VLR in the case of mobile terminating call, or normal location updating in the case where there is radio contact (for example on location updating and call originating from the user). + +The restoration procedure of VLR Failure is illustrated in Figure 7.6/4 and 7.6/5. Each step is explained in the following list. + +![Sequence diagram illustrating the restoration of the VLR by Mobile Terminated call. The diagram shows interactions between the VLR, GLR, and HLR across Visited NW and Home NW domains. The VLR initiates the process with a 'Restart' event, followed by a 'Provide Roaming Number' request to the HLR via the GLR. The HLR responds with 'Provide Roaming Number ack' to the GLR, which is then relayed to the VLR. The VLR then sends a 'Restore Data' request to the GLR. The GLR initiates an 'Insert Subscriber Data' procedure with the HLR, receives the 'Insert Subscriber Data ack' from the HLR via the GLR, and finally sends a 'Restore Data ack' to the VLR.](bb3063a33c89b248574f64b6d8dfc404_img.jpg) + +``` + +sequenceDiagram + participant VLR + participant GLR + participant HLR + Note left of VLR: Restart + VLR->>GLR: 1. Provide Roaming Number + GLR->>HLR: 1. Provide Roaming Number + HLR-->>GLR: 1. Provide Roaming Number ack + GLR-->>VLR: 1. Provide Roaming Number ack + VLR->>GLR: 2. Restore Data + GLR->>HLR: 3. Insert Subscriber Data + HLR-->>GLR: 3. Insert Subscriber Data ack + GLR-->>VLR: 4. Restore Data ack + +``` + +Sequence diagram illustrating the restoration of the VLR by Mobile Terminated call. The diagram shows interactions between the VLR, GLR, and HLR across Visited NW and Home NW domains. The VLR initiates the process with a 'Restart' event, followed by a 'Provide Roaming Number' request to the HLR via the GLR. The HLR responds with 'Provide Roaming Number ack' to the GLR, which is then relayed to the VLR. The VLR then sends a 'Restore Data' request to the GLR. The GLR initiates an 'Insert Subscriber Data' procedure with the HLR, receives the 'Insert Subscriber Data ack' from the HLR via the GLR, and finally sends a 'Restore Data ack' to the VLR. + +**Figure 7.6/4: Restoration of the VLR by Mobile Terminated call** + +#### Procedure: + +- 1) When the VLR receives *Provide Roaming Number* message, it identifies that no IMSI record exists and creates a skeleton IMSI record and returns the *Provide Roaming Number ack* message with MSRN to the HLR via the GLR. The GLR only relays these messages. +- 2) The VLR also sends the *Restore Data* message to the GLR when it identifies that no IMSI record exists in order to recover subscriber record for the IMSI. +- 3) The GLR that receives the message initiates insert subscriber procedure to the VLR. +- 4) The recovery of IMSI record in the VLR is completed after it receives *Restore Data ack* message. + +![Sequence diagram illustrating the restoration of the VLR by Mobile Originated activity and Update Location. The diagram shows interactions between MSC, VLR, and GLR within a Visited NW. It is divided into two cases: MO case and UL case. In the MO case, the VLR receives a Mobile Originated Activity Request, identifies an unidentified subscriber, and returns an error. The user then initiates an Update Location Area request. In the UL case, the user initiates an Update Location Area request directly. Both cases lead to an Authentication phase. After authentication, the VLR sends an Update Location message to the GLR, which responds with Insert Subscriber Data and Insert Subscriber Data ack. Finally, the GLR sends an Update Location ack to the VLR, and the VLR sends an Update Location Area ack to the MSC.](18bb06865e2dada3656ea3d57f290f7f_img.jpg) + +``` + +sequenceDiagram + participant MSC + participant VLR + participant GLR + Note over MSC, VLR, GLR: Visited NW + + Note left of MSC: MO case + MSC->>VLR: Mobile Originated Activity Request + VLR-->>MSC: Error: Unidentified Subscriber + Note left of MSC: UL case + MSC->>VLR: 1. Update Location Area + Note over MSC, VLR, GLR: Authentication + VLR->>GLR: 2. Update Location + GLR-->>VLR: 3. Insert Subscriber Data + VLR-->>GLR: 3. Insert Subscriber Data ack + GLR-->>VLR: 4. Update Location ack + VLR-->>MSC: 5. Update Location Area ack + +``` + +Sequence diagram illustrating the restoration of the VLR by Mobile Originated activity and Update Location. The diagram shows interactions between MSC, VLR, and GLR within a Visited NW. It is divided into two cases: MO case and UL case. In the MO case, the VLR receives a Mobile Originated Activity Request, identifies an unidentified subscriber, and returns an error. The user then initiates an Update Location Area request. In the UL case, the user initiates an Update Location Area request directly. Both cases lead to an Authentication phase. After authentication, the VLR sends an Update Location message to the GLR, which responds with Insert Subscriber Data and Insert Subscriber Data ack. Finally, the GLR sends an Update Location ack to the VLR, and the VLR sends an Update Location Area ack to the MSC. + +**Figure 7.6/5: Restoration of the VLR by Mobile Originated activity and Update Location** + +#### Procedure: + +- 1) (Mobile Originated case). + +When the VLR receives MO activity request and identifies that no IMSI record exists, it returns negative response with cause (Unidentified Subscriber). The user who receives the negative response initiates update location procedure and then the VLR creates a skeleton IMSI record. + +(Update Location case). + +When the user initiates location update procedure and the VLR identifies that no IMSI record exists, the VLR creates a skeleton IMSI record. + +- 2) After successful authentication the VLR sends *Update Location* message to the GLR. +- 3) When the GLR receives the *Update Location* message from the VLR, it initiates insert subscriber procedure normally. +- 4) After insert subscriber procedure completed the GLR sends *Update Location ack* message to the VLR. +- 5) When the VLR receives the *Update Location ack* message, it confirms the registration for the user. At this time the recovery of IMSI record in the VLR is completed. + +### 7.6.4 SGSN Failure + +After an SGSN restart, the SGSN deletes all MM and PDP contexts affected by the restart. When GGSN detects the SGSN restarted by polling function (echo request and response), it shall delete all PDP contexts associated to the SGSN. After that during restoration procedure the SGSN initiates location update procedure. However the GLR does not need to know that the SGSN restart and it only proceeds usual location procedure. + +The restoration procedure of SGSN Failure is illustrated in Figure 7.6/6. Each step is explained in the following list. + +![Sequence diagram illustrating the restoration of the SGSN. The diagram shows interactions between MS, SGSN, GLR, and GGSN. The SGSN undergoes a 'Restart' (indicated by a starburst). The sequence of messages is: 1. RESET (SGSN to MS), 2. Attach Request (MS to SGSN), 3. Identifies No MM context (SGSN internal), 4. Update GPRS Location (SGSN to GLR), 5. Insert Subscriber Data (GLR to SGSN), 6. Insert Subscriber Data ack (SGSN to GLR), 7. Update GPRS Location ack (GLR to SGSN), 8. Attach Request ack (SGSN to MS). A final bar indicates 'Re-Initiate PDP Context Activation procedures' across all entities.](b87818c8505328b198d035761bbc3f2d_img.jpg) + +``` + +sequenceDiagram + participant MS + participant SGSN + participant GLR + participant GGSN + + Note right of SGSN: Restart + SGSN->>MS: 1. RESET + MS->>SGSN: 2. Attach Request + Note right of SGSN: Identifies No MM context + SGSN->>GLR: 2. Update GPRS Location + GLR->>SGSN: 3. Insert Subscriber Data + SGSN->>GLR: 3. Insert Subscriber Data ack + GLR->>SGSN: 4. Update GPRS Location ack + SGSN->>MS: 5. Attach Request ack + Note over MS, SGSN, GLR, GGSN: Re-Initiate PDP Context Activation procedures + +``` + +Sequence diagram illustrating the restoration of the SGSN. The diagram shows interactions between MS, SGSN, GLR, and GGSN. The SGSN undergoes a 'Restart' (indicated by a starburst). The sequence of messages is: 1. RESET (SGSN to MS), 2. Attach Request (MS to SGSN), 3. Identifies No MM context (SGSN internal), 4. Update GPRS Location (SGSN to GLR), 5. Insert Subscriber Data (GLR to SGSN), 6. Insert Subscriber Data ack (SGSN to GLR), 7. Update GPRS Location ack (GLR to SGSN), 8. Attach Request ack (SGSN to MS). A final bar indicates 'Re-Initiate PDP Context Activation procedures' across all entities. + +**Figure 7.6/6: Restoration of the SGSN** + +#### Procedure: + +1. After the SGSN restart, it may broadcast a *Reset* message within SGSN area. This causes the MS to reinitiate Attach and Activate PDP context procedures. +2. When the SGSN receives Attach Request message and identifies no MM context for the MS, it initiates update location procedure. +3. The GLR initiates insert subscriber data procedure as normal update location procedure. +4. When the SGSN receives the *Update GPRS Location ack* message from the GLR, it returns the *Attach Request ack* message to the MS. +5. The MS which receives the message re-initiates Activate PDP context procedures, if needed. + +### 7.6.5 Functional requirements of GLR + +#### 7.6.5.1 Process Restore\_Data\_GLR + +Figure 7.6/7 shows SDL chart for Process Restore\_Data\_GLR. + +![Flowchart for Process Restore_Data_GLR. It starts with an Idle state, followed by a Restore Data input. A Check Parameter step is performed (referencing TS 23.018). A decision 'Result=Pass' follows. If 'No', it leads to 'Set negative response: Unknown Subscriber' and then 'Update Location negative response' back to Idle. If 'Yes', it checks if the 'subscriber known in GLR'. If 'No', it goes to 'Set GLR Number as VLR Number'. If 'Yes', it checks if 'HLR update required?'. If 'Yes', it goes to 'Set GLR Number as VLR Number'. If 'No', it goes to connector '1'. The 'Set GLR Number as VLR Number' step is followed by 'Set IM-MSC Number as MSC Number', 'Restore data', and 'Wait_For_Data'.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +### Process Restore\_Data\_GLR + +1(7) + +Process in the GLR to handle an Restore Data request and trigger the correct application process + +Signals to/from the left are to/from the VLR +Signals to/from the right are to/from the HLR + +``` +graph TD; Start([Idle]) --> Input[/Restore Data/]; Input --> Check[Check Parameter]; Check -.-> Note1[See TS 23.018]; Check --> Result{Result=Pass}; Result -- No --> Neg[Set negative response: Unknown Subscriber]; Neg --> Update{Update Location negative response}; Update --> Idle2([Idle]); Result -- Yes --> Known{subscriber known in GLR}; Known -- No --> SetGLR[Set GLR Number as VLR Number]; Known -- Yes --> HLR{HLR update required?}; HLR -- Yes --> SetGLR; HLR -- No --> Connector1((1)); SetGLR --> SetIM[Set IM-MSC Number as MSC Number]; SetIM --> Restore[/Restore data/]; Restore --> Wait([Wait_For_Data]); +``` + +Flowchart for Process Restore\_Data\_GLR. It starts with an Idle state, followed by a Restore Data input. A Check Parameter step is performed (referencing TS 23.018). A decision 'Result=Pass' follows. If 'No', it leads to 'Set negative response: Unknown Subscriber' and then 'Update Location negative response' back to Idle. If 'Yes', it checks if the 'subscriber known in GLR'. If 'No', it goes to 'Set GLR Number as VLR Number'. If 'Yes', it checks if 'HLR update required?'. If 'Yes', it goes to 'Set GLR Number as VLR Number'. If 'No', it goes to connector '1'. The 'Set GLR Number as VLR Number' step is followed by 'Set IM-MSC Number as MSC Number', 'Restore data', and 'Wait\_For\_Data'. + +Figure 7.6/7(1): Process Restore\_Data\_GLR + +![State transition diagram for Process Restore_Data_GLR. It starts with 'Wait_For_Data' and branches into four main paths: 'Insert Subscriber Data', 'Restore data ack', 'Restore data negative response', and 'Abort'. The 'Insert Subscriber Data' path leads to 'Idle' via 'MNRF set?' and 'Set MS_Not_Reachable'. The 'Restore data ack' path leads to 'Idle' via 'Result:=Pass', 'LSIC by HLR :=Confirmed', 'Set GLR Number as HLR Number', and 'MNRF set?'. The 'Restore data negative response' path leads to 'Idle' via 'Failure Case?' and 'LSIC by HLR :=False'. The 'Abort' path leads to 'Idle' via 'Abort'.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +### Process Restore\_Data\_GLR + +2(7) + +Process in the GLR to handle an Restore Data request and trigger the correct application process + +Signals to/from the left are to/from the VLR +Signals to/from the right are to/from the HLR + +``` +stateDiagram-v2 + [*] --> Wait_For_Data + state "Insert Subscriber Data" as Insert_Subscriber_Data + state "Restore data ack" as Restore_data_ack + state "Restore data negative response" as Restore_data_negative_response + state "Abort" as Abort + + Wait_For_Data --> Insert_Subscriber_Data + Wait_For_Data --> Restore_data_ack + Wait_For_Data --> Restore_data_negative_response + Wait_For_Data --> Abort + + Insert_Subscriber_Data --> Insert_Subscriber_Data_GLR + state "Insert Subscriber Data_GLR" as Insert_Subscriber_Data_GLR + Insert_Subscriber_Data_GLR --> Wait_For_Data_from_HLR_and_ISD_ack_from_VLR + state "Wait_For_Data_from_HLR_and_ISD_ack_from_VLR" as Wait_For_Data_from_HLR_and_ISD_ack_from_VLR + Wait_For_Data_from_HLR_and_ISD_ack_from_VLR --> MNRF_set_1{MNRF set?} + state "MNRF set?" as MNRF_set_1 + MNRF_set_1 -- yes --> Set_MS_Not_Reachable + state "Set MS_Not_Reachable" as Set_MS_Not_Reachable + Set_MS_Not_Reachable --> Restore_data_ack + MNRF_set_1 -- No --> Restore_data_ack + + Restore_data_ack --> Result_Pass + state "Result:=Pass" as Result_Pass + Result_Pass --> LSIC_HLR_Confirmed + state "LSIC by HLR :=Confirmed" as LSIC_HLR_Confirmed + LSIC_HLR_Confirmed --> Set_GLR_Number + state "Set GLR Number as HLR Number" as Set_GLR_Number + Set_GLR_Number --> MNRF_set_2{MNRF set?} + state "MNRF set?" as MNRF_set_2 + MNRF_set_2 -- yes --> Restore_data_ack + MNRF_set_2 -- No --> Restore_data_ack + + Restore_data_negative_response --> Failure_Case{Failure Case?} + state "Failure Case?" as Failure_Case + Failure_Case -- Roaming Not Allowed --> Result_Roaming_Not_Allowed + state "Result:= Roaming Not Allowed" as Result_Roaming_Not_Allowed + Result_Roaming_Not_Allowed --> Delete_Subscriber_Data_1 + state "Delete Subscriber Data" as Delete_Subscriber_Data_1 + Failure_Case -- Unknown Subscriber --> Result_Unknown_Subscriber + state "Result:= Unknown Subscriber" as Result_Unknown_Subscriber + Result_Unknown_Subscriber --> Delete_Subscriber_Data_2 + state "Delete Subscriber Data" as Delete_Subscriber_Data_2 + Failure_Case -- Procedure Error --> Result_Procedure_Error + state "Result:= Procedure Error" as Result_Procedure_Error + Delete_Subscriber_Data_1 --> LSIC_HLR_False + Delete_Subscriber_Data_2 --> LSIC_HLR_False + Result_Procedure_Error --> LSIC_HLR_False + state "LSIC by HLR :=False" as LSIC_HLR_False + LSIC_HLR_False --> Restore_Data_negative_response_2{Restore Data negative response} + state "Restore Data negative response" as Restore_Data_negative_response_2 + Restore_Data_negative_response_2 --> Idle_1([Idle]) + + Abort --> Abort_2{Abort} + state "Abort" as Abort_2 + Abort_2 --> Idle_2([Idle]) +``` + +State transition diagram for Process Restore\_Data\_GLR. It starts with 'Wait\_For\_Data' and branches into four main paths: 'Insert Subscriber Data', 'Restore data ack', 'Restore data negative response', and 'Abort'. The 'Insert Subscriber Data' path leads to 'Idle' via 'MNRF set?' and 'Set MS\_Not\_Reachable'. The 'Restore data ack' path leads to 'Idle' via 'Result:=Pass', 'LSIC by HLR :=Confirmed', 'Set GLR Number as HLR Number', and 'MNRF set?'. The 'Restore data negative response' path leads to 'Idle' via 'Failure Case?' and 'LSIC by HLR :=False'. The 'Abort' path leads to 'Idle' via 'Abort'. + +Figure 7.6/7(2): Process Restore\_Data\_GLR + +![State transition diagram for Process Restore_Data_GLR. It starts with a wait state for HLR and VLR signals. From there, it branches into four main paths: 1) Insert Subscriber Data, which leads to a success path (Result:=Pass, LSIC:=Confirmed, Set GLR Number, MNRF set? yes, Set MS_Not_Reachable, Restore data ack, Idle); 2) Restore data ack, which leads to a success path (Result:=Pass, LSIC:=Confirmed, Set GLR Number, MNRF set? No, Restore data ack, Idle); 3) Restore Data negative response, which leads to a failure case analysis (Failure Case? Roaming Not Allowed, Unknown Subscriber, Procedure Error); 4) Abort, which leads directly to Idle. The failure cases for Roaming Not Allowed and Unknown Subscriber both lead to Delete Subscriber Data, then LSIC:=False, Restore Data negative response, and Idle. The Procedure Error case leads directly to Result:=Procedure Error and then Idle.](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) + +### Process Restore\_Data\_GLR + +3(7) + +Process in the GLR to handle an Restore Data request and trigger the correct application process + +Signals to/from the left are to/from the VLR +Signals to/from the right are to/from the HLR + +``` +stateDiagram-v2 + [*] --> Wait_For_Data_from_HLR_and_ISD_ack_from_VLR + state "Wait_For_Data_from_HLR_and_ISD_ack_from_VLR" as Wait_For_Data_from_HLR_and_ISD_ack_from_VLR + state "Insert Subscriber Data" as Insert_Subscriber_Data + state "Restore data ack" as Restore_data_ack + state "Restore Data negative response" as Restore_Data_negative_response + state "Abort" as Abort + + Wait_For_Data_from_HLR_and_ISD_ack_from_VLR --> Insert_Subscriber_Data + Wait_For_Data_from_HLR_and_ISD_ack_from_VLR --> Restore_data_ack + Wait_For_Data_from_HLR_and_ISD_ack_from_VLR --> Restore_Data_negative_response + Wait_For_Data_from_HLR_and_ISD_ack_from_VLR --> Abort + + Insert_Subscriber_Data --> Insert_Subscriber_Data_GLR + state "Insert Subscriber Data_GLR" as Insert_Subscriber_Data_GLR + Insert_Subscriber_Data_GLR --> Wait_For_Data_from_HLR_and_ISD_ack_from_VLR + Wait_For_Data_from_HLR_and_ISD_ack_from_VLR --> Result_Pass_1[Result:=Pass] + Result_Pass_1 --> LSIC_Confirmed_1[LSIC by HLR :=Confirmed] + LSIC_Confirmed_1 --> Set_GLR_Number[Set GLR Number as HLR Number] + Set_GLR_Number --> MNRF_set_1{MNRF set?} + MNRF_set_1 -- yes --> Set_MS_Not_Reachable[Set MS_Not_Reachable] + Set_MS_Not_Reachable --> Restore_data_ack_1{Restore data ack} + MNRF_set_1 -- No --> Restore_data_ack_1 + Restore_data_ack_1 --> Idle_1([Idle]) + + Restore_data_ack --> Result_Pass_2[Result:=Pass] + Result_Pass_2 --> LSIC_Confirmed_2[LSIC by HLR :=Confirmed] + LSIC_Confirmed_2 --> Set_GLR_Number_2[Set GLR Number as HLR Number] + Set_GLR_Number_2 --> MNRF_set_2{MNRF set?} + MNRF_set_2 -- No --> Restore_data_ack_2{Restore data ack} + Restore_data_ack_2 --> Idle_2([Idle]) + + Restore_Data_negative_response --> Failure_Case{Failure Case?} + Failure_Case -- Roaming Not Allowed --> Result_Roaming[Result:= Roaming Not Allowed] + Result_Roaming --> Delete_Subscriber_Data_1[Delete Subscriber Data] + Failure_Case -- Unknown Subscriber --> Result_Unknown[Result:= Unknown Subscriber] + Result_Unknown --> Delete_Subscriber_Data_2[Delete Subscriber Data] + Failure_Case -- Procedure Error --> Result_Procedure[Result:= Procedure Error] + Delete_Subscriber_Data_1 --> LSIC_False[LSIC by HLR :=False] + Delete_Subscriber_Data_2 --> LSIC_False + LSIC_False --> Restore_Data_negative_response_2{Restore Data negative response} + Restore_Data_negative_response_2 --> Idle_3([Idle]) + Result_Procedure --> Idle_4([Idle]) + + Abort --> Abort_2{Abort} + Abort_2 --> Idle_5([Idle]) +``` + +State transition diagram for Process Restore\_Data\_GLR. It starts with a wait state for HLR and VLR signals. From there, it branches into four main paths: 1) Insert Subscriber Data, which leads to a success path (Result:=Pass, LSIC:=Confirmed, Set GLR Number, MNRF set? yes, Set MS\_Not\_Reachable, Restore data ack, Idle); 2) Restore data ack, which leads to a success path (Result:=Pass, LSIC:=Confirmed, Set GLR Number, MNRF set? No, Restore data ack, Idle); 3) Restore Data negative response, which leads to a failure case analysis (Failure Case? Roaming Not Allowed, Unknown Subscriber, Procedure Error); 4) Abort, which leads directly to Idle. The failure cases for Roaming Not Allowed and Unknown Subscriber both lead to Delete Subscriber Data, then LSIC:=False, Restore Data negative response, and Idle. The Procedure Error case leads directly to Result:=Procedure Error and then Idle. + +Figure 7.6/7(3): Process Restore\_Data\_GLR + +![Flowchart for Process Restore_Data_GLR. It starts with a 'Wait_For_Data_from_HLR_and_ISD_ack_from_VLR' state, leading to 'Insert Subscriber Data ack'. A decision 'All received feature & service supported?' follows. If 'Yes', it goes to 'Update Seubscriber Data' (typo in image). If 'No', it goes to 'Update subscriber data for supported features' and 'set parameters for unsupported features'. Both lead to a second decision 'MSC area restricted by regional subscription?'. If 'Yes', it goes to 'Set MSC area restricted'. Both 'Yes' and 'No' lead to 'Insert Subscriber Data ack', which then leads to another 'Wait_For_Data_from_HLR_and_ISD_ack_from_VLR' state. A separate path from the first wait state leads to 'Insert Subscriber Data negative response', which leads to another 'Insert Subscriber Data negative response', which then leads to the second 'Wait_For_Data_from_HLR_and_ISD_ack_from_VLR' state.](c07e21a8d65991db04263322f859c94f_img.jpg) + +### Process Restore\_Data\_GLR + +4(7) + +Process in the GLR to handle an Restore Data request and trigger the correct application process + +Signals to/from the left are to/from the VLR +Signals to/from the right are to/from the HLR + +``` +graph TD; Start1((Wait_For_Data_from_HLR_and_ISD_ack_from_VLR)) --> InsertAck1{{Insert Subscriber Data ack}}; InsertAck1 --> Decision1{All received feature & service supported?}; Decision1 -- Yes --> UpdateData[Update Seubscriber Data]; Decision1 -- No --> UpdateSub[Update subscriber data for supported features]; UpdateSub --> SetParams[set parameters for unsupported features]; SetParams --> Decision2{MSC area restricted by regional subscription?}; UpdateData --> Decision2; Decision2 -- Yes --> SetMSC[Set MSC area restricted]; Decision2 -- No --> InsertAck2{{Insert Subscriber Data ack}}; SetMSC --> InsertAck2; InsertAck2 --> Start2((Wait_For_Data_from_HLR_and_ISD_ack_from_VLR)); Start1 --> InsertNeg1{{Insert Subscriber Data negative response}}; InsertNeg1 --> InsertNeg2{{Insert Subscriber Data negative response}}; InsertNeg2 --> Start2; +``` + +Flowchart for Process Restore\_Data\_GLR. It starts with a 'Wait\_For\_Data\_from\_HLR\_and\_ISD\_ack\_from\_VLR' state, leading to 'Insert Subscriber Data ack'. A decision 'All received feature & service supported?' follows. If 'Yes', it goes to 'Update Seubscriber Data' (typo in image). If 'No', it goes to 'Update subscriber data for supported features' and 'set parameters for unsupported features'. Both lead to a second decision 'MSC area restricted by regional subscription?'. If 'Yes', it goes to 'Set MSC area restricted'. Both 'Yes' and 'No' lead to 'Insert Subscriber Data ack', which then leads to another 'Wait\_For\_Data\_from\_HLR\_and\_ISD\_ack\_from\_VLR' state. A separate path from the first wait state leads to 'Insert Subscriber Data negative response', which leads to another 'Insert Subscriber Data negative response', which then leads to the second 'Wait\_For\_Data\_from\_HLR\_and\_ISD\_ack\_from\_VLR' state. + +Figure 7.6/7(4): Process Restore\_Data\_GLR + +![Flowchart for Process Restore_Data_GLR. It starts with a connector '1' leading to 'ISD_GLR'. A decision 'Result = Pass?' follows. If 'No', it checks 'Result = Aborted?'. If 'Yes', it goes to 'Idle'. If 'No', it sends 'Restore Data negative response' and goes to 'Idle'. If 'Yes' from 'Result = Pass?', it checks 'MSC Area Restricted? OR Roaming Restricted Due to Unsupported Feature?'. If 'No', it sends 'Subscriber Present_GLR'. A decision 'Changed supported services?' follows. If 'Yes', it checks 'Changed MSC area restricted'. If 'Yes', it goes to 'Set GLR Number as VLR Number'. If 'No', it checks 'MNRF set?'. If 'yes', it goes to 'Set MS_Not_Reachable'. If 'No', it goes to 'Restore data ack'. From 'Set MS_Not_Reachable', it goes to 'Restore data ack'. From 'Set GLR Number as VLR Number', it goes to 'Set IM-MSC Number as MSC Number', then 'Restore Data', then 'Wait_For_information'. From 'Restore data ack', it goes to 'Idle'.](9c45844d796e85ae05505870a54e4eb4_img.jpg) + +### Process Restore\_Data\_GLR + +5(7) + +Process in the GLR to handle an Restore Data request and trigger the correct application process + +Signales to/from the left are to/from the VLR +Signales to/from the right are to/from the HLR + +``` +graph TD + 1((1)) --> ISD_GLR[ISD_GLR] + ISD_GLR --> Result_Pass{Result = Pass?} + Result_Pass -- No --> Result_Aborted{Result = Aborted?} + Result_Aborted -- Yes --> Idle1([Idle]) + Result_Aborted -- No --> Restore_Neg[Restore Data negative response] + Restore_Neg --> Idle2([Idle]) + Result_Pass -- Yes --> MSC_Restricted{MSC Area Restricted? +OR +Roaming Restricted Due to +Unsupported Feature?} + MSC_Restricted -- No --> Sub_Pres[Subscriber Present_GLR] + Sub_Pres --> Changed_Services{Changed supported services?} + Changed_Services -- Yes --> Changed_MSC{Changed MSC area restricted} + Changed_MSC -- Yes --> Set_GLR[Set GLR Number as VLR Number] + Changed_MSC -- No --> MNRF{MNRF set?} + MNRF -- yes --> Set_MS[Set MS_Not_Reachable] + MNRF -- No --> Restore_Ack[Restore data ack] + Set_MS --> Restore_Ack + Set_GLR --> Set_IM[Set IM-MSC Number as MSC Number] + Set_IM --> Restore_Data[Restore Data] + Restore_Data --> Wait_For[Wait_For_information] + Wait_For --> Restore_Ack + Restore_Ack --> Idle3([Idle]) +``` + +Flowchart for Process Restore\_Data\_GLR. It starts with a connector '1' leading to 'ISD\_GLR'. A decision 'Result = Pass?' follows. If 'No', it checks 'Result = Aborted?'. If 'Yes', it goes to 'Idle'. If 'No', it sends 'Restore Data negative response' and goes to 'Idle'. If 'Yes' from 'Result = Pass?', it checks 'MSC Area Restricted? OR Roaming Restricted Due to Unsupported Feature?'. If 'No', it sends 'Subscriber Present\_GLR'. A decision 'Changed supported services?' follows. If 'Yes', it checks 'Changed MSC area restricted'. If 'Yes', it goes to 'Set GLR Number as VLR Number'. If 'No', it checks 'MNRF set?'. If 'yes', it goes to 'Set MS\_Not\_Reachable'. If 'No', it goes to 'Restore data ack'. From 'Set MS\_Not\_Reachable', it goes to 'Restore data ack'. From 'Set GLR Number as VLR Number', it goes to 'Set IM-MSC Number as MSC Number', then 'Restore Data', then 'Wait\_For\_information'. From 'Restore data ack', it goes to 'Idle'. + +Figure 7.6/7(5): Process Restore\_Data\_GLR + +![Flowchart for Process Restore_Data_GLR. It starts with 'Wait_For_Information' and branches into four main paths: 'Insert Subscriber Data', 'Restore data ack', 'Restore data negative response', and 'Abort'.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +### Process Restore\_Data\_GLR + +6(7) + +Process in the GLR to handle an Restore Data request and trigger the correct application process + +Signales to/from the left are to/from the VLR +Signales to/from the right are to/from the HLR + +``` + +graph TD + Wait([Wait_For_Information]) + + %% Branch 1 + Wait --> Insert[/Insert Subscriber Data/] + Insert --> C2((2)) + + %% Branch 2 + Wait --> AckIn[/Restore data ack/] + AckIn --> ResPass[Result:= Pass] + ResPass --> LSIC_T[LSIC by HLR :=True] + LSIC_T --> SetGLR[Set GLR Number as HLR Number] + SetGLR --> MNRF{MNRF set?} + MNRF -- yes --> SetMS[Set MS_Not_Reachable] + MNRF -- No --> AckOut[/Restore data ack/] + SetMS --> AckOut + AckOut --> Idle1([Idle]) + + %% Branch 3 + Wait --> NegIn[/Restore data negative response/] + NegIn --> Failure{Failure case?} + Failure -- Roaming not Allowed --> ResRoam[Result:= Roaming Not Allowed] + ResRoam --> DelRoam[Delete Subscriber Data] + Failure -- Unknown Subscriber --> ResUnk[Result:= Unknown Subscriber] + ResUnk --> DelUnk[Delete Subscriber Data] + Failure -- Procedure Error --> ResErr[Result:= Procedure Error] + + DelRoam --> LSIC_F[LSIC by HLR :=False] + DelUnk --> LSIC_F + ResErr --> LSIC_F + + LSIC_F --> NegOut[/Restore data negative response/] + NegOut --> Idle2([Idle]) + + %% Branch 4 + Wait --> AbortIn[/Abort/] + AbortIn --> AbortAct[Abort] + AbortAct --> Idle3([Idle]) + +``` + +Flowchart for Process Restore\_Data\_GLR. It starts with 'Wait\_For\_Information' and branches into four main paths: 'Insert Subscriber Data', 'Restore data ack', 'Restore data negative response', and 'Abort'. + +**Figure 7.6/7(6): Process Restore\_Data\_GLR** + +![Flowchart for Process Restore_Data_GLR. It starts at connector 2, checks parameters (referencing TS 23.018), checks if the result passed, if the subscriber is known, if all features are supported, and if the MSC area is restricted. Depending on these checks, it either updates subscriber data, sets parameters for unsupported features, sets the MSC area as restricted, sends a negative response, or sends an acknowledgment and waits for information.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +### Process Restore\_Data\_GLR + +7(7) + +Process in the GLR to handle an Restore Data request and trigger the correct application process + +Signales to/from the left are to/from the VLR +Signales to/from the right are to/from the HLR + +``` +graph TD; Start((2)) --> Check[Check Parameter]; Check --- Note1[See TS 23.018]; Check --> Result{Result= Pass?}; Result -- No --> InsertNeg[Insert Subscriber Data negative response]; InsertNeg --> Idle([Idle]); Result -- Yes --> Known{Subscriber known?}; Known -- No --> InsertNeg; Known -- Yes --> AllSupported{All received features & services supported?}; AllSupported -- No --> UpdateData[Update Subscriber Data for supported features]; AllSupported -- Yes --> UpdateData; UpdateData --> SetParams[Set parameters for unsupported features]; SetParams --> MSCRestricted{MSC area restricted by regional subscription?}; MSCRestricted -- Yes --> SetMSC[Set MSC area restricted]; SetMSC --> InsertAck[Insert Subscriber Data ack]; MSCRestricted -- No --> InsertAck; InsertAck --> WaitForInfo([Wait_For_Information]); +``` + +Flowchart for Process Restore\_Data\_GLR. It starts at connector 2, checks parameters (referencing TS 23.018), checks if the result passed, if the subscriber is known, if all features are supported, and if the MSC area is restricted. Depending on these checks, it either updates subscriber data, sets parameters for unsupported features, sets the MSC area as restricted, sends a negative response, or sends an acknowledgment and waits for information. + +Figure 7.6/7(7): Process Restore\_Data\_GLR + +## 7.7 Short Message Service + +The Short Message Mobile Terminated is realised by MAP signalling between SMS-GMSC and the visited node (i.e. MSC or SGSN). Signalling address is the E.164 MSC Number or the E.164 SGSN Number. Since in the case of GLR introduction address conversion (see subclause 7.1.2) is performed some mechanism is needed to restore the actual visited node address from the converted one generated by the GLR. In principle that restoration is performed by the GLR itself. + +### 7.7.1 Scope + +This subclause describes only SM MT with GLR under the following condition: + +- The recipient MS in the visited PLMN with the GLR is roamed into the PLMN from other PLMN. + +Since SM MT in the case that is not applied to the above condition and SM MO have no relation to the introduction of the GLR those cases are not treated in this subclause and just refer to 3G TS 23.040 [5]. This subclause defines: + +- the services and service elements (with regard to the GLR introduction); +- the network architecture (with regard to the GLR introduction); +- the IM-MSC functionality (with regard to the SMS); +- the GLR functionality (with regard to the SMS); +- the protocols and protocol layering (with regard to the GLR introduction); + +for the Teleservices 22, as specified in the 3G TS 22.003 [1]. + +### 7.7.2 Definitions + +This clause only provides definitions specific to the GLR introduction. Other definitions regarding SMS are provided in 3G TS 23.040 [5]. + +**Intermediate- MSC (IM-MSC):** The Intermediate MSC is an exchange which performs address interrogation to the GLR and relays the SMS to the MSC in the case of SM MT. + +**Mobile-Station-Not-Reachable-Flag (MNRF):** The part of the MWI to be stored in the VLR and the HLR. It shall be stored also in the GLR. MNRF is a Boolean parameter indicating if the address list of MWD contains one or more entries because an attempt to deliver a short message to an MS has failed with a cause of Absent Subscriber. + +**Mobile-station-Not-Reachable-for-GPRS (MNRG):** The part of the MWI to be stored in the SGSN and the HLR. It shall be stored also in the GLR. MNRG is a Boolean parameter indicating if the address list of MWD contains one or more entries because an attempt to deliver a short message to an MS has failed with a cause of Absent Subscriber. + +**More-Messages-To-Send (MMS):** The GLR shall keep a MAP dialogue open between the SMS-GMSC and the GLR and between the GLR and the SGSN where there are more messages to send. The IM-MSC shall keep a MAP dialogue open between the SMS-GMSC and the IM-MSC and between the IM-MSC and the MSC. + +**Gateway Location Register (GLR):** The Gateway Location Register is an exchange that relays the SMS MT from SMS-GMSC to the SGSN. The GLR shall have interrogation function to forward the SM MT to the correct MSC or the SGSN. + +### 7.7.3 Services and service elements + +#### 7.7.3.1 Short Message Service elements + +##### 7.7.3.1.1 Messages-Waiting + +Refer to 3G TS 23.040 [5] for the definition of the Message-Waiting service element. + +The GLR shall have only the MNRF and the MNRG for the Message-Waiting. The GLR does not have other datum for the Message-Waiting service element. + +Setting the MNRF and the MNRG is mandatory in the GLR as in the VLR/SGSN. When the MS has been detected as becoming active, the VLR or the SGSN shall: + +- send the "MS Reachable" message (see subclause 7.7.7) to the HLR via the GLR, and then +- clear MNRF in the VLR or the MNRG in SGSN (see 3G TS 23.040 [5]). + +When the GLR receives the "MS Reachable" message it is mandatory for the GLR to relay the "MS Reachable" message to the HLR and then clear MNRF or MNRG in the GLR. + +The MNRG and MNRF in the GLR are updated in the following way: + +- 1a) When a mobile terminated short message delivery fails due to the MS being temporarily absent (i.e. either IMSI DETACH flag is set or there is no response from the MS to a paging request via the MSC), the MNRF is set (if it is not already set). +- 1b) When a mobile terminated short message delivery fails due to the MS being temporarily absent (i.e. either GPRS DETACH flag is set or there is no response from the MS to a paging request via the SGSN), the MNRG is set (if it is not already set). +- 1c) When a mobile terminated short message delivery fails due to the MS memory capacity via the MSC being exceeded, the MNRF is cleared. +- 1d) When a mobile terminated short message delivery fails due to the MS memory capacity via the SGSN being exceeded, the MNRG is cleared. +- 2a) When either the HLR or VLR detects that the MS (with a non-empty MWD and the MCEF clear in the HLR and the MNRF set in the VLR) has recovered operation (e.g. has responded to a paging request over MSC), the HLR directly, or on request of the VLR or of the GLR, will invoke operations to alert the SCs within the MWD (see subclause 7.7.3.1.2 and subclause 7.7.7). Once the Alert SC operations have been invoked, the MNRF is cleared in the VLR and the GLR. +- 2b) When either the HLR or SGSN detects that the MS (with a non-empty MWD and the MCEF clear in the HLR and the MNRG set in the SGSN) has recovered operation (e.g. has responded to a paging request via the SGSN), the HLR directly or on request of the SGSN or the GLR will invoke operations to alert the SCs within the MWD (see subclause 7.7.3.1.2 and subclause 7.7.7). Once the Alert SC operations have been invoked, the MNRG is cleared in the SGSN and the GLR. +- 2c) When the HLR receives (via the MSC, the VLR and the GLR) a notification that the MS (with a non-empty MWD and the MCEF set in the HLR) has memory capacity available to receive one or more short messages, the HLR will invoke operations to alert the SCs within the MWD (see subclause 7.7.3.1.2 and subclause 7.7.7). Once the Alert SC operations have been invoked, the MNRF is cleared in the VLR and the GLR. +- 2d) When the HLR receives (via the SGSN and the GLR) a notification that the MS (with a non-empty MWD and the MCEF set in the HLR) has memory capacity available to receive one or more short messages, the HLR will invoke operations to alert the SCs within the MWD (see subclause 7.7.3.1.2 and subclause 7.7.7). Once the Alert SC operations have been invoked, the MNRG is cleared in the SGSN and the GLR. + +##### 7.7.3.1.2 Alert-SC + +Considering the Alert-SC service element, when the GLR receives the Update Location or the Update GPRS Location from the VLR or the SGSN if and only if the MNRF or the MNRG is set in the GLR the GLR shall send "MS Reachable" message (see clause 7.7.7) to the HLR. That enables the HLR to initiate Alert-SC. + +#### 7.7.3.2 Unsuccessful short message TPDU transfer SC -> MS + +Some error(s) may occur in the IM-MSC or the GLR (see subclauses 7.7.5 and 7.7.7). + +### 7.7.4 Network architecture + +#### 7.7.4.1 Basic network structure + +The exchange of messages between an MS and an SME involves the entities shown in figure 7.7/1. + +The basic network structure of the SM MT with GLR is depicted in figure 7.7/2. + +![Figure 7.7/1: Entities involved in the provision of SM MT with GLR. This diagram shows a sequence of entities: SME, SC, SMS-GMSC, IM-MSC/GLR, MSC/SGSN, and MS. A dashed line connects SME and SC. A solid line connects SC to SMS-GMSC. A vertical line separates the first two entities (SME and SC) from the rest, with an arrow pointing from SC to the SMS-GMSC. Below this line, text indicates 'Outside the scope of the 3GPP Specifications' for SME and SC, and 'Inside the scope of the 3GPP Specifications' for the remaining entities. Solid lines connect SMS-GMSC to IM-MSC/GLR, IM-MSC/GLR to MSC/SGSN, and MSC/SGSN to MS.](bbddeb46a8bee133d49003273fcfc8dd_img.jpg) + +Figure 7.7/1: Entities involved in the provision of SM MT with GLR. This diagram shows a sequence of entities: SME, SC, SMS-GMSC, IM-MSC/GLR, MSC/SGSN, and MS. A dashed line connects SME and SC. A solid line connects SC to SMS-GMSC. A vertical line separates the first two entities (SME and SC) from the rest, with an arrow pointing from SC to the SMS-GMSC. Below this line, text indicates 'Outside the scope of the 3GPP Specifications' for SME and SC, and 'Inside the scope of the 3GPP Specifications' for the remaining entities. Solid lines connect SMS-GMSC to IM-MSC/GLR, IM-MSC/GLR to MSC/SGSN, and MSC/SGSN to MS. + +**Figure 7.7/1: Entities involved in the provision of SM MT with GLR** + +The links of figure 7.7/2 support the SM MT with GLR in the following way: + +- the operations performed on links 1, 2, 3 and 4 is described in 3G TS 29.002 [10]; +- interface E is internal interface in one physical node. Procedure in the IM-MSC, the GLR and between them regarding interface 5 is described in 3G TS 29.002 [10]. + +![Figure 7.7/2: The main network structure serving as a basis for the SM MT with GLR. This diagram shows entities: SC, SMS-GMSC, IM-MSC, MSC/VL, MS, GLR, and SGSN. SC is connected to SMS-GMSC by a double-headed arrow. SMS-GMSC is connected to IM-MSC by a double-headed arrow labeled '1'. IM-MSC is connected to MSC/VL by a double-headed arrow labeled '3'. MSC/VL is connected to MS by a double-headed arrow. IM-MSC is connected to GLR by a double-headed arrow labeled '5'. GLR is connected to SGSN by a double-headed arrow labeled '4'. SGSN is connected to MS by a double-headed arrow. There is also a double-headed arrow labeled '2' between SMS-GMSC and GLR.](af2da9ea326af3b375c6fea82bd0b77d_img.jpg) + +Figure 7.7/2: The main network structure serving as a basis for the SM MT with GLR. This diagram shows entities: SC, SMS-GMSC, IM-MSC, MSC/VL, MS, GLR, and SGSN. SC is connected to SMS-GMSC by a double-headed arrow. SMS-GMSC is connected to IM-MSC by a double-headed arrow labeled '1'. IM-MSC is connected to MSC/VL by a double-headed arrow labeled '3'. MSC/VL is connected to MS by a double-headed arrow. IM-MSC is connected to GLR by a double-headed arrow labeled '5'. GLR is connected to SGSN by a double-headed arrow labeled '4'. SGSN is connected to MS by a double-headed arrow. There is also a double-headed arrow labeled '2' between SMS-GMSC and GLR. + +**Figure 7.7/2: The main network structure serving as a basis for the SM MT with GLR** + +### 7.7.5 Node functionality related to SM MT + +#### 7.7.5.1 General + +In the case of the GLR introduction as an option for the visited network operator, the existing functionality of the GSM entities regarding SMS MT (i.e. SMS-GMSC, MSC, VLR, SGSN and HLR) shall not be needed to modify. + +#### 7.7.5.2 Functionality of the GLR + +When receiving a short message TPDU from the SMS-GMSC ("forwardShortMessage", see subclause 7.7.7.1), the GLR is responsible for the following operations: + +- reception of the short message TPDU; + +if errors are detected by the GLR: + +- returning the appropriate error information to the SMS-GMSC in a failure report (negative outcome of "forwardShortMessage" see clauses 7.7.7.1); + +if no errors are detected by the GLR: + +- retrieve the SGSN Number from the identity of the recipient MS; +- transferring the short message to the SGSN. + +When a delivery report is received by the GLR: + +- relaying the delivery report (positive outcome of "forwardShortMessage" see subclause 7.7.7.1) to the SMS-GMSC. + +When a failure report is received by the GLR: + +- relaying the failure report (negative outcome of "forwardShortMessage" see subclause 7.7.7.1) to the SMS-GMSC. + +When receiving "ReadyForSM" from the MSC or the SGSN: + +if errors are detected by the GLR: + +- returning the appropriate error information to the MSC or the SGSN in a failure report (negative outcome of "ReadyForSM", see subclause 7.7.7.3); + +if no errors are detected by the GLR: + +- relaying the "ReadyForSM" to the HLR (see subclause 7.7.7.3). + +#### 7.7.5.3 Functionality of the IM-MSC + +When receiving a short message TPDU from the SMS-GMSC ("forwardShortMessage", see subclause 7.7.7.1), the IM-MSC is responsible for the following operations: + +- reception of the short message TPDU; +- retrieving information from the GLR ("ObtainMSCNumber", see subclause 7.7.7.1); MSC Number and, when appropriate, error information; + +if errors are indicated by the GLR: + +- returning the appropriate error information to the SMS-GMSC in a failure report (negative outcome of "forwardShortMessage" see clauses 7.7.7.1); + +if no errors are indicated by the GLR: + +- relaying the "forwardShortMessage" to the MSC is indicated by the retrieved MSC Number. + +When a delivery report is received by the IM-MSC: + +- relaying the delivery report (positive outcome of "forwardShortMessage" see subclause 7.7.7.1) to the SMS-GMSC. + +When a failure report is received by the IM-MSC: + +- relaying the failure report (negative outcome of "forwardShortMessage" see subclause 7.7.7.1) to the SMS-GMSC. + +### 7.7.6 Protocols and protocol architecture + +SM-RL shall be terminated at the GLR and the IM-MSC, since the GLR and the IM-MSC shall be able to retrieve the actual visited node address (i.e. the MSC Number or the SGSN Number) from the recipient MS identity. The protocol layers of the SMS are structured as shown in figure 7.7/3. + +![Figure 7.7/3: Protocol layer overview for the SM MT with GLR. The diagram shows five entities: SC, SMS-GMSC, IM-SC/GLR, MSC/SGSN, and MS. Each entity has a stack of protocol layers. SC and MS have SM-AL, SM-TL, SM-RL, and SM-LL. SMS-GMSC, IM-SC/GLR, and MSC/SGSN have SM-RL and SM-LL. Arrows indicate connections: SM-AL and SM-TL connect SC and MS directly. SM-RL connects SC to SMS-GMSC, SMS-GMSC to IM-SC/GLR, IM-SC/GLR to MSC/SGSN, and MSC/SGSN to MS. SM-LL connects SC to SMS-GMSC, SMS-GMSC to IM-SC/GLR, IM-SC/GLR to MSC/SGSN, and MSC/SGSN to MS.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +Figure 7.7/3: Protocol layer overview for the SM MT with GLR. The diagram shows five entities: SC, SMS-GMSC, IM-SC/GLR, MSC/SGSN, and MS. Each entity has a stack of protocol layers. SC and MS have SM-AL, SM-TL, SM-RL, and SM-LL. SMS-GMSC, IM-SC/GLR, and MSC/SGSN have SM-RL and SM-LL. Arrows indicate connections: SM-AL and SM-TL connect SC and MS directly. SM-RL connects SC to SMS-GMSC, SMS-GMSC to IM-SC/GLR, IM-SC/GLR to MSC/SGSN, and MSC/SGSN to MS. SM-LL connects SC to SMS-GMSC, SMS-GMSC to IM-SC/GLR, IM-SC/GLR to MSC/SGSN, and MSC/SGSN to MS. + +**Figure 7.7/3: Protocol layer overview for the SM MT with GLR** + +#### 7.7.6.1 Service provided by the SM-RL + +##### 7.7.6.1.1 General + +SM-RL messages and its information elements are the same as in the network without the GLR. + +##### 7.7.6.1.2 Protocol element repertoire at SM-RL + +Protocol element repertoire at SM-RL is the same as in the network without the GLR. Refer to 3G TS 23.040 [5] for the presence (i.e. mandatory, optional or not present) of each information element by replacing the term in the following manner. + +- SMS-GMSC <-> IM-SC or IM-SC <-> MSC : MSC <-> MSC. +- SMS-GMSC <-> GLR or GLR <-> SGSN : MSC <-> SGSN. + +### 7.7.7 Fundamental procedures within the point-to-point SMS + +This subclause provides the procedures specific to the GLR introduction. + +#### 7.7.7.1 Short message mobile terminated + +The entities involved in this procedure are depicted in figure 7.7/4. + +![Figure 7.7/4: Interface involved in the short message mobile terminated procedure with GLR. The diagram shows the flow of a short message from the SC (Service Center) through the SMS-GMSC. The SMS-GMSC has two possible paths: one through the GLR to the SGSN to the MS, and another through the IM-SC to the MSC to the MS. The SMS-GMSC is also connected to the HLR. The MSC is connected to the VLR.](6922d65f6e8904f01264141d85dd51d5_img.jpg) + +Figure 7.7/4: Interface involved in the short message mobile terminated procedure with GLR. The diagram shows the flow of a short message from the SC (Service Center) through the SMS-GMSC. The SMS-GMSC has two possible paths: one through the GLR to the SGSN to the MS, and another through the IM-SC to the MSC to the MS. The SMS-GMSC is also connected to the HLR. The MSC is connected to the VLR. + +**Figure 7.7/4: Interface involved in the short message mobile terminated procedure with GLR** + +**NOTE:** The GLR and the IM-SC shall not be visible to the other entities. Especially the SMS-GMSC shall regard the GLR and the IM-SC as the SGSN and the MSC respectively. Further the SGSN and MSC shall regard the GLR and the IM-SC as the SMS-GMSC. + +In figures 7.7/5, sequence diagrams are shown for the following basic situations of short message mobile terminated transfer attempt: + +- Successful short message transfer via the MSC;...a). +- Successful short message transfer via the SGSN;...b). +- Short message transfer attempt failing due to error at the MSC;...c). +- Short message transfer attempt failing due to error at the SGSN;...d). +- Short message transfer attempt failing due to error at the IM-MSC;...e). +- Short message transfer attempt failing due to error at the IM-MSC/GLR;...f). +- Short message transfer attempt failing due to error at the GLR;...g). +- Short message transfer attempt failing over the SGSN as the first path and succeeding over the MSC as the second path;...h). +- Short message transfer attempt failing over the SGSN as the first path and over the MSC as the second path;...I). + +![Sequence diagram for successful short message transfer attempt via the MSC. Lifelines: SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The process involves routing information lookup, message forwarding through IM-MSC and MSC, and delivery reports back to the sender.](79aaab5889060cf8264226764a109cdb_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant IM-MSC + participant GLR + participant MSC + participant VLR + participant SGSN + participant MS + + Note left of SC: Operation invocation or message transfer + SC->>SMS-GMSC: Message Transfer + Note right of SMS-GMSC: Successful operation invocation or message transfer including report + SMS-GMSC->>HLR: SendRoutingInfoForShortMsg + HLR-->>SMS-GMSC: + Note right of SMS-GMSC: Successful operation invocation or message transfer including report + SMS-GMSC->>IM-MSC: 1a. ForwardShortMessage + Note right of IM-MSC: Successful operation invocation or message transfer including report + IM-MSC->>GLR: 2. ObtainMSCNumber + GLR-->>IM-MSC: + Note right of IM-MSC: Successful operation invocation or message transfer including report + IM-MSC->>MSC: 3a. ForwardShortMessage + Note right of MSC: Successful operation invocation or message transfer including report + MSC->>VLR: SendInfoForMT-SMS + VLR-->>MSC: + Note right of MSC: Successful operation invocation or message transfer including report + MSC->>MS: Message Transfer + Note right of MS: Successful operation invocation or message transfer including report + MS-->>MSC: 3b. Delivery report + Note right of MSC: Successful operation invocation or message transfer including report + MSC-->>IM-MSC: 1b. Delivery report + Note right of IM-MSC: Successful operation invocation or message transfer including report + IM-MSC->>SMS-GMSC: SM-Delivery ReportStatus + Note right of SMS-GMSC: Successful operation invocation or message transfer including report + SMS-GMSC-->>SC: Delivery report + Note right of SC: Successful operation invocation or message transfer including report + +``` + +Sequence diagram for successful short message transfer attempt via the MSC. Lifelines: SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The process involves routing information lookup, message forwarding through IM-MSC and MSC, and delivery reports back to the sender. + +**Figure 7.7/5a): Successful short message transfer attempt via the MSC** + +![Sequence diagram showing a successful short message transfer attempt via the SGSN. Lifelines: SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The process involves Message Transfer, SendRoutingInfoForShortMsg, 1a. ForwordShortMessage, 3a. ForwordShortMessage, Message Transfer to MS, 3b. Delivery report, 1b. Delivery report, SM-Delivery ReportStatus, and final Delivery report. A legend at the bottom distinguishes between 'Operation invocation or message transfer' (solid line) and 'Successful operation invocation or message transfer including report' (double line).](d2417b04116c354deccb25d98a84a0fb_img.jpg) + +``` +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant IM-MSC + participant GLR + participant MSC + participant VLR + participant SGSN + participant MS + + Note left of SC: Message Transfer + SC->>SMS-GMSC: Message Transfer + SMS-GMSC->>HLR: SendRoutingInfoForShortMsg + HLR-->>SMS-GMSC: 1a. ForwordShortMessage + SMS-GMSC->>GLR: 1a. ForwordShortMessage + GLR->>MSC: 3a. ForwordShortMessage + MSC->>VLR: 3a. ForwordShortMessage + VLR->>SGSN: 3a. ForwordShortMessage + SGSN->>MS: Message Transfer + MS-->>SGSN: 3b. Delivery report + SGSN->>GLR: 3b. Delivery report + GLR-->>IM-MSC: 1b. Delivery report + IM-MSC-->>SMS-GMSC: 1b. Delivery report + SMS-GMSC->>HLR: SM-Delivery ReportStatus + HLR-->>SMS-GMSC: SM-Delivery ReportStatus + SMS-GMSC->>SC: Delivery report +``` + +Legend: + +- Operation invocation or message transfer +- ⇔ Successful operation invocation or message transfer including report + +Sequence diagram showing a successful short message transfer attempt via the SGSN. Lifelines: SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The process involves Message Transfer, SendRoutingInfoForShortMsg, 1a. ForwordShortMessage, 3a. ForwordShortMessage, Message Transfer to MS, 3b. Delivery report, 1b. Delivery report, SM-Delivery ReportStatus, and final Delivery report. A legend at the bottom distinguishes between 'Operation invocation or message transfer' (solid line) and 'Successful operation invocation or message transfer including report' (double line). + +**Figure 7.7/5b): Successful short message transfer attempt via the SGSN** + +![Sequence diagram showing short message transfer attempt failing due to error at the MSC. Lifelines: SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The diagram shows a 'Message Transfer' from SC to SMS-GMSC, followed by 'SendRoutingInfoForShortMsg' between SMS-GMSC and HLR. SMS-GMSC sends '1a. ForwordShortMessage' to IM-MSC. IM-MSC sends '2. ObtainMSCNumber' to GLR. GLR sends '3a. ForwordShortMessage' to MSC. MSC sends '3c. Failure report' back to IM-MSC. IM-MSC sends '4. InformSMDeliveryFailure' to GLR. IM-MSC also sends '1c. Failure report' back to SMS-GMSC. SMS-GMSC sends 'SM-DeliveryReportStatus' to HLR. Finally, SC receives a 'Failure report' from SMS-GMSC.](18003425d0e8638dde4acc9c5c468c5c_img.jpg) + +``` +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant IM-MSC + participant GLR + participant MSC + participant VLR + participant SGSN + participant MS + + Note left of SC: Message Transfer + SC->>SMS-GMSC: Message Transfer + SMS-GMSC->>HLR: SendRoutingInfoForShortMsg + SMS-GMSC->>IM-MSC: 1a. ForwordShortMessage + IM-MSC->>GLR: 2. ObtainMSCNumber + GLR->>MSC: 3a. ForwordShortMessage + MSC-->>IM-MSC: 3c. Failure report + IM-MSC->>GLR: 4. InformSMDeliveryFailure + IM-MSC-->>SMS-GMSC: 1c. Failure report + SMS-GMSC->>HLR: SM-DeliveryReportStatus + SMS-GMSC-->>SC: Failure report +``` + +Legend: + +- Operation invocation or message transfer +- ↔ Successful operation invocation or message transfer including report +- .-> Error report +- .-> Unsuccessful operation invocation or message transfer including report (or with missing confirmation) + +Sequence diagram showing short message transfer attempt failing due to error at the MSC. Lifelines: SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The diagram shows a 'Message Transfer' from SC to SMS-GMSC, followed by 'SendRoutingInfoForShortMsg' between SMS-GMSC and HLR. SMS-GMSC sends '1a. ForwordShortMessage' to IM-MSC. IM-MSC sends '2. ObtainMSCNumber' to GLR. GLR sends '3a. ForwordShortMessage' to MSC. MSC sends '3c. Failure report' back to IM-MSC. IM-MSC sends '4. InformSMDeliveryFailure' to GLR. IM-MSC also sends '1c. Failure report' back to SMS-GMSC. SMS-GMSC sends 'SM-DeliveryReportStatus' to HLR. Finally, SC receives a 'Failure report' from SMS-GMSC. + +**Figure 7.7/5c): Short message transfer attempt failing due to error at the MSC** + +![Sequence diagram for short message transfer failing due to error at the SGSN. Lifelines: SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The sequence shows Message Transfer, SendRoutingInfoForShortMsg, 1a. ForwordShortMessage, 3a. ForwordShortMessage, 3c. Failure report, 1c. Failure report, SM-Delivery ReportStatus, and Failure report messages with a legend for arrow types. Solid arrow Solid double-headed arrow Dashed arrow Dashed double-headed arrow](0dfdff10c725fe9c332b07ade9d23a5e_img.jpg) + +Legend: + +- Operation invocation or message transfer +- Successful operation invocation or message transfer including report +- Error report +- Unsuccessful operation invocation or message transfer including report (or with missing confirmation) + +Sequence diagram for short message transfer failing due to error at the SGSN. Lifelines: SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The sequence shows Message Transfer, SendRoutingInfoForShortMsg, 1a. ForwordShortMessage, 3a. ForwordShortMessage, 3c. Failure report, 1c. Failure report, SM-Delivery ReportStatus, and Failure report messages with a legend for arrow types. Solid arrow Solid double-headed arrow Dashed arrow Dashed double-headed arrow + +**Figure 7.7/5d): Short message transfer attempt failing due to error at the SGSN** + +![Sequence diagram for short message transfer failing due to error at the IM-MSC. Lifelines: SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The sequence shows Message Transfer, SendRoutingInfoForShortMsg, 1a. ForwordShortMessage, 1c. Failure report, SM-Delivery ReportStatus, and Failure report messages with a legend for arrow types. Solid arrow Solid double-headed arrow Dashed arrow Dashed double-headed arrow](796d2e601722450d6456085e0a801e1e_img.jpg) + +Legend: + +- Operation invocation or message transfer +- Successful operation invocation or message transfer including report +- Error report +- Unsuccessful operation invocation or message transfer including report (or with missing confirmation) + +Sequence diagram for short message transfer failing due to error at the IM-MSC. Lifelines: SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The sequence shows Message Transfer, SendRoutingInfoForShortMsg, 1a. ForwordShortMessage, 1c. Failure report, SM-Delivery ReportStatus, and Failure report messages with a legend for arrow types. Solid arrow Solid double-headed arrow Dashed arrow Dashed double-headed arrow + +**Figure 7.7/5e): Short message transfer attempt failing due to error at the IM-MSC** + +![Sequence diagram for short message transfer failing at IM-MSC/GLR. Lifelines: SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The process involves Message Transfer, SendRoutingInfoForShortMsg, 1a. ForwardShortMessage, 2. ObtainMSCNumber, 1c. Failure report, SM-DeliveryReportStatus, and Failure report. A legend at the bottom defines the arrow types: solid for operation invocation, solid with double head for successful operation, dashed for error report, and dashed with double head for unsuccessful operation.](ffe0fef452a0ae9a20253c319c54e13c_img.jpg) + +Sequence diagram illustrating a short message transfer attempt failing due to an error at the IM-MSC/GLR. The lifelines involved are SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, and MS. + +The sequence of messages is as follows: + +- SC sends a **Message Transfer** (solid arrow) to SMS-GMSC. +- SMS-GMSC sends a **SendRoutingInfoForShortMsg** (solid double-headed arrow) to HLR. +- HLR sends a **1a. ForwardShortMessage** (solid arrow) to IM-MSC. +- IM-MSC sends a **2. ObtainMSCNumber** (dashed double-headed arrow) to GLR. +- GLR sends a **1c. Failure report** (dashed arrow) to IM-MSC. +- IM-MSC sends a **SM-DeliveryReportStatus** (solid double-headed arrow) to HLR. +- HLR sends a **Failure report** (dashed double-headed arrow) to SMS-GMSC. +- SMS-GMSC sends a **Failure report** (dashed double-headed arrow) to SC. + +Legend: + +- Solid arrow: Operation invocation or message transfer +- Solid arrow with double head: Successful operation invocation or message transfer including report +- Dashed arrow: Error report +- Dashed arrow with double head: Unsuccessful operation invocation or message transfer including report (or with missing confirmation) + +Sequence diagram for short message transfer failing at IM-MSC/GLR. Lifelines: SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The process involves Message Transfer, SendRoutingInfoForShortMsg, 1a. ForwardShortMessage, 2. ObtainMSCNumber, 1c. Failure report, SM-DeliveryReportStatus, and Failure report. A legend at the bottom defines the arrow types: solid for operation invocation, solid with double head for successful operation, dashed for error report, and dashed with double head for unsuccessful operation. + +**Figure 7.7/5f): Short message transfer attempt failing due to error at the IM-MSC/GLR** + +![Sequence diagram for short message transfer failing at GLR. Lifelines: SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The process involves Message Transfer, SendRoutingInfoForShortMsg, 1a. ForwardShortMessage, 1c. Failure report, SM-DeliveryReportStatus, and Failure report. A legend at the bottom defines the arrow types: solid for operation invocation, solid with double head for successful operation, dashed for error report, and dashed with double head for unsuccessful operation.](e60c2d24a97a2855d98671d27ea43d0f_img.jpg) + +Sequence diagram illustrating a short message transfer attempt failing due to an error at the GLR. The lifelines involved are SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, and MS. + +The sequence of messages is as follows: + +- SC sends a **Message Transfer** (solid arrow) to SMS-GMSC. +- SMS-GMSC sends a **SendRoutingInfoForShortMsg** (solid double-headed arrow) to HLR. +- HLR sends a **1a. ForwardShortMessage** (solid arrow) to GLR. +- GLR sends a **1c. Failure report** (dashed arrow) to SMS-GMSC. +- SMS-GMSC sends a **SM-DeliveryReportStatus** (solid double-headed arrow) to HLR. +- HLR sends a **Failure report** (dashed double-headed arrow) to SC. + +Legend: + +- Solid arrow: Operation invocation or message transfer +- Solid arrow with double head: Successful operation invocation or message transfer including report +- Dashed arrow: Error report +- Dashed arrow with double head: Unsuccessful operation invocation or message transfer including report (or with missing confirmation) + +Sequence diagram for short message transfer failing at GLR. Lifelines: SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The process involves Message Transfer, SendRoutingInfoForShortMsg, 1a. ForwardShortMessage, 1c. Failure report, SM-DeliveryReportStatus, and Failure report. A legend at the bottom defines the arrow types: solid for operation invocation, solid with double head for successful operation, dashed for error report, and dashed with double head for unsuccessful operation. + +**Figure 7.7/5g): Short message transfer attempt failing due to error at the GLR** + +![Sequence diagram showing short message transfer between SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, and MS. The diagram illustrates a failure over the SGSN path and success over the MSC path.](a963ca41bde1669b18a4b783616f228b_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant IM-MSC + participant GLR + participant MSC + participant VLR + participant SGSN + participant MS + + Note left of SC: Message Transfer + SC->>SMS-GMSC: Message Transfer + SMS-GMSC->>HLR: SendRoutingInfoForShortMsg + HLR-->>SMS-GMSC: 1a. ForwordShortMessage + SMS-GMSC->>GLR: 1a. ForwordShortMessage + GLR->>MSC: 3a. ForwordShortMessage + MSC-->>SGSN: 3c. Failure report + SGSN-->>GLR: 1c. Failure report + GLR-->>SMS-GMSC: 1c. Failure report + SMS-GMSC->>IM-MSC: 1a. ForwordShortMessage + IM-MSC->>GLR: 2. ObtainMSCNumber + GLR-->>IM-MSC: 3a. ForwordShortMessage + IM-MSC->>MSC: 3a. ForwordShortMessage + MSC->>VLR: SendInfoFor-MT-SMS + VLR-->>MSC: Message Transfer + MSC->>MS: Message Transfer + MS-->>MSC: 3c. Delivery report + MSC-->>IM-MSC: 1c. Delivery report + IM-MSC-->>SMS-GMSC: SM-DeliveryReportStatus + SMS-GMSC-->>SC: Delivery report + + Note right of SC: + Note right of SC: Operation invocation or message transfer + Note right of SC: Successful operation invocation or message transfer including report + Note right of SC: Error report + Note right of SC: Unsuccessful operation invocation or message transfer including report (or with missing confirmation) + +``` + +Sequence diagram showing short message transfer between SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, and MS. The diagram illustrates a failure over the SGSN path and success over the MSC path. + +**Figure 7.7/5h): Short message transfer attempt failing over the SGSN as the first path and succeeding over the MSC as the second path** + +![Sequence diagram for Short message transfer attempt failing over the SGSN as the first path and over the MSC as the second path. The diagram shows interactions between SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, and MS. The process involves Message Transfer, SendRoutingInfoForShortMsg, ForwardShortMessage (1a), ObtainMSCNumber (2), and various Failure reports (1c, 3c, 4).](de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg) + +The sequence diagram illustrates the interaction for a short message transfer attempt that fails. The lifelines are SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, and MS. + +- Message Transfer:** SC sends a message transfer to SMS-GMSC. +- SendRoutingInfoForShortMsg:** SMS-GMSC sends a routing information request to HLR. +- 1a. ForwardShortMessage:** HLR sends the short message to GLR. +- 3a. ForwardShortMessage:** GLR sends the short message to SGSN. +- 3c. Failure report:** SGSN sends a failure report back to GLR. +- 1c. Failure report:** GLR sends a failure report back to SMS-GMSC. +- 1a. ForwardShortMessage:** SMS-GMSC retransmits the short message to IM-MSC. +- 2. ObtainMSCNumber:** IM-MSC sends a request to GLR to obtain the MSC number. +- 3a. ForwardShortMessage:** IM-MSC sends the short message to MSC. +- SendInfoFor-MT-SMS:** MSC sends information for message transfer to VLR. +- 3c. Failure report:** VLR sends a failure report back to IM-MSC. +- 4. InformSMDeliveryFailure:** IM-MSC sends a delivery failure indication to GLR. +- 1c. Failure report:** GLR sends another failure report back to SMS-GMSC. +- SM-Delivery ReportStatus:** SMS-GMSC sends a delivery report status to HLR. +- Failure report:** SMS-GMSC sends a final failure report back to SC. + +**Legend:** + +- Solid line with arrow: Operation invocation or message transfer +- Solid line with double arrow: Successful operation invocation or message transfer including report +- Dashed line with arrow: Error report +- Dashed line with double arrow: Unsuccessful operation invocation or message transfer including report (or with missing confirmation) + +Sequence diagram for Short message transfer attempt failing over the SGSN as the first path and over the MSC as the second path. The diagram shows interactions between SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, and MS. The process involves Message Transfer, SendRoutingInfoForShortMsg, ForwardShortMessage (1a), ObtainMSCNumber (2), and various Failure reports (1c, 3c, 4). + +**Figure 7.7/5i): Short message transfer attempt failing over the SGSN as the first path and over the MSC as the second path** + +Operation 1: Message transfer SMS-GMSC -> GLR or IM-MSC. + +This operation is used to transfer a short message from an SMS-GMSC to a GLR or IM-MSC. + +The operation consists of: + +- the transfer of a message containing the TPDU from the SMS-GMSC to the GLR or IM-MSC (see "1a. ForwardShortMessage" in figure 7.7.5), and +- the return of either a "Failure report" (see 1c. in figure 7.7.5) or a "Delivery report" (see 1b. in figure 7.7.5). + +"Failure report" is returned to the SMS-GMSC when the GLR or IM-MSC has received indication from another entity (MSC, SGSN) or when an error has occurred in the GLR or IM-MSC the procedure was unsuccessful. The error indications which the GLR or IM-MSC may receive from the MSC, SGSN, VLR or MS enable the GLR or IM-MSC to return one of the error indications given in Table 23.040/1 back to the SMS-GMSC. + +Note that the SMS-GMSC shall regard the GLR as a SGSN and the IM-MSC a MSC and it is not aware the GLR and the IM-MSC as individual entities. + +Operation 2: ObtainMSCNumber. + +When the IM-MSC receives "1a. ForwardShortMessage" from an SMS-GMSC, the IM-MSC interrogates the GLR internally and obtains the E.164 number of the MSC at which the MS is currently located. + +Operation 3: forwardShortMessage. + +The operation provides a means for the GLR or IM-MSC to transfer a short message to the MSC or to the SGSN respectively at which the MS is currently located. + +The operation works in tandem with the forwarding of the short message from the MSC or from the SGSN to the MS. Thus, the outcome of the operation comprises either success, i.e. that the message has been delivered to the MS; or a failure that may be caused by several reasons, e.g. failure in the transfer IM-MSC -> MSC or GLR -> SGSN, MS being detached, or no paging response. + +Note that the MSC and the SGSN shall not be aware of existence of the GLR and the IM-MSC. + +Operation 4: InformSMDeliveryFailure. + +When the IM-MSC receives "3c. FailureReport" with absent subscriber cause, IM-MSC informs it to the GLR. The GLR checks if the reason of absent subscriber is due to the purged MS in the serving node (i.e. MSC or SGSN). If so, the GLR deletes the subscriber data for the user. Otherwise the GLR sets MNRF. + +When the GLR receives "3c. FailureReport" with absent subscriber cause, the GLR checks if the reason of absent subscriber is due to the purged MS in the serving node (i.e. MSC or SGSN). If so, the GLR deletes the subscriber data for the user. Otherwise the GLR sets MNRG. + +#### 7.7.7.2 Functional requirements of GLR + +##### 7.7.7.2.1 Process Obtain\_MSC\_Number\_GLR + +Figure 7.7/6 shows the SDL chart for Process Obtain\_MSC\_Number\_GLR. + +![SDL Flowchart for Process Obtain_MSC_Number_GLR](c0ca823603794512478906b302176bca_img.jpg) + +### Process Obtain\_MSC\_Number\_GLR + +1(1) + +GLR application process +for Obtain MSC Number + +Signals from/to the left +are to/from the IM-MSC + +``` + +graph TD + Start([ ]) --> Idle1(Idle) + Idle1 --> In1[/Obtain MSC +Number/] + In1 --> Dec1{Subscriber known +in GLR?} + Dec1 -- Yes --> Out1[\Obtain MSC +Number ack/] + Dec1 -- No --> Out2[\Obtain MSC +Number negative +response/] + Out1 --> Idle2(Idle) + Out2 --> Idle3(Idle) + +``` + +The diagram shows the SDL process for obtaining an MSC number in a GLR (Gateway Location Register). It starts from an initial state, enters an 'Idle' state, and waits for an 'Obtain MSC Number' input signal. Upon receiving the signal, it checks if the subscriber is known in the GLR. If yes, it sends an 'Obtain MSC Number ack' output signal and returns to the 'Idle' state. If the subscriber is not known, it sends an 'Obtain MSC Number negative response' output signal and returns to the 'Idle' state. All signals are exchanged with the IM-MSC on the left. + +SDL Flowchart for Process Obtain\_MSC\_Number\_GLR + +**Figure 7.7/6: Process Obtain\_MSC\_Number\_GLR** + +##### 7.7.7.2.2 Process Inform\_SM\_Delivery\_Failure\_GLR + +Figure 7.7/7 shows the SDL chart for Process Inform\_SM\_Delivery\_Failure\_GLR. + +![SDL chart for Process Inform_SM_Delivery_Failure_GLR](a320e67b369bfde4a5fa360b100da55c_img.jpg) + +**Process Inform\_SM\_Delivery\_Failure\_GLR** 1(1) + +GLR application process +for Inform SM Delivery Failure + +Signals to/from the left +are to/from IM-MSC + +``` +stateDiagram-v2 + [*] --> Idle1 : Idle + Idle1 --> InformSM : Inform SM Delivery Failure + InformSM --> setMNRF : set MNRF + setMNRF --> CheckAbsent : Check Absent SSubscriberSM_In_GLR + CheckAbsent --> Idle2 : Idle +``` + +The diagram is an SDL chart for the process 'Inform\_SM\_Delivery\_Failure\_GLR'. It begins with an initial state leading to an 'Idle' state. A transition labeled 'Inform SM Delivery Failure' leads to a 'set MNRF' state. From 'set MNRF', a transition labeled 'Check Absent SSubscriberSM\_In\_GLR' leads to another 'Idle' state. Two callouts are present: one on the top left indicating that the GLR application process is for 'Inform SM Delivery Failure', and one on the top right indicating that signals to/from the left are to/from the 'IM-MSC'. + +SDL chart for Process Inform\_SM\_Delivery\_Failure\_GLR + +Figure 7.7/7: Process Inform\_SM\_Delivery\_Failure\_GLR + +##### 7.7.7.2.3 Procedure Check\_Absent\_SubscriberSM\_In\_GLR + +Figure 7.7/8 shows the SDL chart for Procedure Check\_Absent\_SubscriberSM\_In\_GLR. + +![SDL chart for Procedure Check_Absent_SubscriberSM_In_GLR](ff1a293f8118c0f00dbfeb0ab843d6e6_img.jpg) + +**Procedure Check\_Absent\_SubscriberSM\_In\_GLR** 1(1) + +The procedure Check\_Absent\_SubscriberSM\_In\_GLR determines whether the GLR shall delete its data for the MS based on the outcome of a MT-SMS delivery attempt for PS domain + +``` + +graph TD + Start([ ]) --> SuperCharged{Super-Charged +GLR} + SuperCharged -- no --> End((X)) + SuperCharged -- yes --> Absent{Absent +Subscriber SM Error +Purged MS?} + Absent -- no --> End + Absent -- yes --> Delete[Delete +Subscriber Data] + Delete --> End + +``` + +The diagram is an SDL chart for the procedure 'Check\_Absent\_SubscriberSM\_In\_GLR'. It begins with a start symbol, leading to a decision diamond labeled 'Super-Charged GLR'. A 'no' branch leads to the end symbol (a circle with an 'X'). A 'yes' branch leads to a second decision diamond labeled 'Absent Subscriber SM Error Purged MS?'. From this second diamond, a 'no' branch leads to the end symbol, and a 'yes' branch leads to a process box 'Delete Subscriber Data', which then terminates at the end symbol. + +SDL chart for Procedure Check\_Absent\_SubscriberSM\_In\_GLR + +Figure 7.7/8: Procedure Check\_Absent\_SubscriberSM\_In\_GLR + +#### 7.7.7.3 Alert transfer + +The entities involved in this procedure are depicted in figure 7.7/9. + +![Figure 7.7/9: Interfaces involved in the Alert procedure with GLR. This block diagram shows the network architecture. On the left, an SC (Service Centre) is connected to an SMS-IWMSC. The SMS-IWMSC is connected to an HLR. The HLR is connected to a GLR. The GLR is connected to a VLR. The VLR is connected to an MSC. The MSC is connected to an MS (Mobile Station). Additionally, the GLR is connected to an SGSN, which is also connected to the MS.](34d7353cac3d344f71ad82bd1eda40d1_img.jpg) + +Figure 7.7/9: Interfaces involved in the Alert procedure with GLR. This block diagram shows the network architecture. On the left, an SC (Service Centre) is connected to an SMS-IWMSC. The SMS-IWMSC is connected to an HLR. The HLR is connected to a GLR. The GLR is connected to a VLR. The VLR is connected to an MSC. The MSC is connected to an MS (Mobile Station). Additionally, the GLR is connected to an SGSN, which is also connected to the MS. + +**Figure 7.7/9: Interfaces involved in the Alert procedure with GLR** + +NOTE: The GLR shall not be visible to the other entities. Especially the HLR shall regard the GLR as the VLR or the SGSN. Further the SGSN and the VLR shall regard the GLR as the HLR. + +This procedure consists of the operations shown in figure 7.7/10. + +Regarding the GLR introduction, the following four cases are distinguished: + +- the MS becomes reachable when the MNRF is set in the VLR (figure 7.7/10a); +- the MS becomes reachable when the MNRF is set in the SGSN (figure 7.7/10b); +- the MS performs Location Update when the MNRF is not set in the VLR (figure 7.7/10c); +- the MS performs Routing Area Update when the MNRF is not set in the SGSN (figure 7.7/10d). + +The operations between HLR and GLR are equivalent for HLR to those between HLR and VLR or between HLR and SGSN. The operations between GLR and SGSN are equivalent for SGSN to those between HLR and SGSN. The operations between GLR and VLR are equivalent for VLR to those between HLR and VLR. + +The procedures in HLR, VLR and SGSN regarding the operations are the same as in the network without GLR. The procedures regarding the operations in GLR and IM-MSC are defined in 3G TS 29.002 [10]. + +![Figure 7.7/10a: Sequence diagram of the alert procedure. The lifelines are SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, and MS. The sequence of messages is: 1. MSC sends 'ReadyForSM' to GLR. 2. GLR sends 'ReadyForSM' to HLR. 3. HLR sends 'alertServiceCentre' to SMS-GMSC. 4. SMS-GMSC sends 'ServiceCentreAler' to SC.](372876d8c5ee065bc744b175be0a6c1f_img.jpg) + +Figure 7.7/10a: Sequence diagram of the alert procedure. The lifelines are SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, and MS. The sequence of messages is: 1. MSC sends 'ReadyForSM' to GLR. 2. GLR sends 'ReadyForSM' to HLR. 3. HLR sends 'alertServiceCentre' to SMS-GMSC. 4. SMS-GMSC sends 'ServiceCentreAler' to SC. + +**Figure 7.7/10a: The alert procedure when the MS becomes reachable, MNRF is set** + +![Sequence diagram for Figure 7.7/10b: The alert procedure when the MS becomes reachable, MNRG is set. Lifelines: SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The sequence starts with MSC sending ReadyForSM to GLR, which then sends ReadyForSM to HLR. HLR sends alertServiceCentre to SMS-GMSC, which sends ServiceCentreAler to SC.](e18841eb4a995df8354a793459e12fd0_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HLR + participant IM-MSC + participant GLR + participant MSC + participant VLR + participant SGSN + participant MS + MSC->>GLR: ReadyForSM + GLR->>HLR: ReadyForSM + HLR->>SMS-GMSC: alertServiceCentre + SMS-GMSC->>SC: ServiceCentreAler + +``` + +Sequence diagram for Figure 7.7/10b: The alert procedure when the MS becomes reachable, MNRG is set. Lifelines: SC, SMS-GMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The sequence starts with MSC sending ReadyForSM to GLR, which then sends ReadyForSM to HLR. HLR sends alertServiceCentre to SMS-GMSC, which sends ServiceCentreAler to SC. + +**Figure 7.7/10b: The alert procedure when the MS becomes reachable, MNRG is set** + +![Sequence diagram for Figure 7.7/10c: The alert procedure when the GLR receives UpdateLocation, MNRF or MNRG is set. Lifelines: SC, SMS-IWMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The sequence starts with MS sending LA Update to SGSN, which sends UpdateLocation to VLR, which sends UpdateLocation to GLR. GLR then sends ReadyForSM to HLR. HLR sends alertServiceCentre to SMS-IWMSC, which sends ServiceCentreAler to SC.](9bafc60bf378685e5e246c3ffad7b792_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-IWMSC + participant HLR + participant IM-MSC + participant GLR + participant MSC + participant VLR + participant SGSN + participant MS + MS->>SGSN: LA Update + SGSN->>VLR: UpdateLocation + VLR->>GLR: UpdateLocation + GLR->>HLR: ReadyForSM + HLR->>SMS-IWMSC: alertServiceCentre + SMS-IWMSC->>SC: ServiceCentreAler + +``` + +Sequence diagram for Figure 7.7/10c: The alert procedure when the GLR receives UpdateLocation, MNRF or MNRG is set. Lifelines: SC, SMS-IWMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The sequence starts with MS sending LA Update to SGSN, which sends UpdateLocation to VLR, which sends UpdateLocation to GLR. GLR then sends ReadyForSM to HLR. HLR sends alertServiceCentre to SMS-IWMSC, which sends ServiceCentreAler to SC. + +**Figure 7.7/10c: The alert procedure when the GLR receives UpdateLocation, MNRF or MNRG is set** + +![Sequence diagram for Figure 7.7/10d: The alert procedure when the GLR receives UpdateGprsLocation, MNRF or MNRG is set. Lifelines: SC, SMS-IWMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The sequence starts with MS sending RA Update to SGSN, which sends UpdateGprsLocation to GLR. GLR then sends 5. ReadyForSM to HLR. HLR sends alertServiceCentre to SMS-IWMSC, which sends ServiceCentreAler to SC.](6ba310120ebcd99661c4ee1c58a1586c_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-IWMSC + participant HLR + participant IM-MSC + participant GLR + participant MSC + participant VLR + participant SGSN + participant MS + MS->>SGSN: RA Update + SGSN->>GLR: UpdateGprsLocation + GLR->>HLR: 5. ReadyForSM + HLR->>SMS-IWMSC: alertServiceCentre + SMS-IWMSC->>SC: ServiceCentreAler + +``` + +Sequence diagram for Figure 7.7/10d: The alert procedure when the GLR receives UpdateGprsLocation, MNRF or MNRG is set. Lifelines: SC, SMS-IWMSC, HLR, IM-MSC, GLR, MSC, VLR, SGSN, MS. The sequence starts with MS sending RA Update to SGSN, which sends UpdateGprsLocation to GLR. GLR then sends 5. ReadyForSM to HLR. HLR sends alertServiceCentre to SMS-IWMSC, which sends ServiceCentreAler to SC. + +**Figure 7.7/10d: The alert procedure when the GLR receives UpdateGprsLocation, MNRF or MNRG is set** + +Operation 5: ReadyForSM (invoked by UpdateLocation or UpdateGprsLocation). + +When the GLR receives UpdateLocation (see 7.7/10c) or UpdateGprsLocation (see 7.7/10d) the GLR shall invoke ReadyForSM to the HLR if and only if MNRF or MNRG is set. Note that if the GLR in which the MNRG is set receives Update Location the GLR shall invoke ReadyForSM also in that case. The converse case is also the case. + +## 7.8 Subscriber and Equipment Trace + +3G TS29.002 [10] states that subscriber and equipment trace is only available for subscribers within their HPLMN area. If the HLR receives a trace request for a subscriber, and the HLR detects that the subscriber is not in the HPLMN, then the HLR does not forward the trace request to the VPLMN. The trace request never reaches the GLR. Therefore it is concluded that the GLR has no impact on subscriber and equipment trace. + +## 7.9 Impact of GLR on CAMEL + +### 7.9.1 The VLR supports CAMEL Phase 2 onwards + +When the GLR receives the MAP\_UPDATE\_LOCATION request message from the subscriber, the GLR checks that the CAMEL supported phase it previously received for that subscriber matches the CAMEL supported phase carried by MAP\_UPDATE\_LOCATION request message. If a difference is detected, the GLR relays the MAP\_UPDATE\_LOCATION request message to the HLR in order to obtain the proper CAMEL subscription information that corresponds to the current VLR. Refer to figure 7.9.1/1. + +In order to perform this scenario, the CAMEL supported phase information needs to be added to the 'IMSI record in GLR' table. + +It is possible that all the VLRs within a VPLMN do not support the same phase of CAMEL. This could happen in the case of an incremental upgrade of these VLRs within the VPLMN. In this case, it is possible that the HLR may receive frequent changes of the CAMEL supported phase information in the MAP\_UPDATE\_LOCATION request message from the GLR. The effect is that the HLR would perceive the GLR as a VLR that changes its CAMEL supported phase. + +Other CAMEL related messages between HLR and VLR, e.g. Provide Subscriber Info, Provide Subscriber Info ack are always relayed transparently from the HLR to the VLR or vice versa. + +![Sequence diagram illustrating CAMEL Subscription Information flow between MS, VLR, GLR, and HLR.](a471382fa73185ead4f9b83e3e64ee96_img.jpg) + +``` + +sequenceDiagram + participant MS + participant VLR + participant GLR + participant HLR + + Note right of GLR: Compare the CAMEL Supported phase between that held in the GLR and newly received in the MAP_LU. If difference is detected, relay MAP_UL to HLR. + Note left of GLR: Store the received CAMEL Supported phase information in GLR + + MS->>VLR: Location update req. + VLR->>GLR: Update Location VLR number + GLR->>HLR: Update Location GLR number + HLR->>GLR: Insert Sub. Data CAMEL sub. Info. + GLR->>VLR: Insert Sub. Data CAMEL sub. Info. + VLR->>GLR: Insert Sub. Data ack + GLR->>HLR: Insert Sub. Data ack + HLR->>GLR: Update Location + GLR->>VLR: Update Location + VLR->>MS: Location update conf. + +``` + +The sequence diagram shows the interaction between four entities: MS (Mobile Station), VLR (Visitor Location Register), GLR (Gateway Location Register), and HLR (Home Location Register). The process begins with the MS sending a 'Location update req.' to the VLR. The VLR then sends an 'Update Location' message with its VLR number to the GLR. The GLR performs an internal check (indicated by a note: 'Compare the CAMEL Supported phase between that held in the GLR and newly received in the MAP\_LU. If difference is detected, relay MAP\_UL to HLR.') and also stores the received CAMEL Supported phase information (indicated by another note: 'Store the received CAMEL Supported phase information in GLR'). The GLR then sends an 'Update Location' message with its GLR number to the HLR. The HLR responds with 'Insert Sub. Data' containing CAMEL subscription information. This information is relayed by the GLR to the VLR. The VLR sends an 'Insert Sub. Data ack' to the GLR, which is then relayed by the GLR to the HLR. Finally, the HLR sends an 'Update Location' message to the GLR, which is relayed by the GLR to the VLR, which in turn sends a 'Location update conf.' message back to the MS. + +Sequence diagram illustrating CAMEL Subscription Information flow between MS, VLR, GLR, and HLR. + +Figure 7.9/1: CAMEL Subscription Information + +### 7.9.2 The VLR supports CAMEL Phase 1 or has no CAMEL Support + +If the Location Update Request message received by the GLR contains no indication that the VLR supports CAMEL, then this shows to the GLR that the VLR: + +- **either** has no support for CAMEL. +- **or** supports CAMEL Phase 1. + +The GLR will interpret this situation to mean that there is no CAMEL support within the VLR. Therefore the GLR will treat this as a case of an unsupported service (see subclause 7.2.1.4). This will lead to an update location procedure being initiated between the GLR and HLR, causing the HLR to activate its service substitution rules. + +Note the following description of a current GSM network, i.e. where there is no GLR between the HLR and VLR. When the HLR receives a Location Update request with no indication of CAMEL support, then the HLR will attempt to request CAMEL Phase 1 support in the ISD message. If the ISD is accepted by the VLR, then support for CAMEL Phase 1 is indicated. If the ISD is rejected, then no support for CAMEL Phase 1 is indicated. + +## 7.10 Interaction with CCBS + +### 7.10.1 Two possible treatments for interaction with CCBS + +In order to treat CCBS function in the GLR, There may be two possible treatments applied. When a subscriber is monitored (either as being a target or being the initiator of CCBS request), and roams to visited network which contains the GLR, the GLR manages monitoring state of subscriber. + +If monitoring is ongoing when the GLR receives a Location Update request from the new VLR, the GLR can take one of the following actions: + +- (Alternative 1): Relay the Location Update request to the HLR to inform the appropriate CCBS processes in the HLR, or +- (Alternative 2): Send a StatusReport MAP operation, indicating "Idle" to the HLR, handle the Location Update request locally in the GLR, and start monitoring on the new VLR, by sending a SetReportingState MAP operation to the new VLR. + +Should the SetReportingState response from the new VLR indicate "Not reachable" or "Not Idle", then the GLR will send this status information in a StatusReport towards the HLR. + +The alternative 1 has the advantage that the GLR monitoring functionality is straightforward, but implies unnecessary MAP LU traffics. + +The alternative 2 has the advantage that MAP LU traffic is saved, but implies monitoring logic to be available in the GLR. + +Both options imply that the GLR needs to keep track of subscribers being monitored. + +### 7.10.2 The functionality in the GLR + +The CCBS Monitoring Flag is used in the GLR to judge whether requested location updating is necessary to be indicated to HLR or not. The figure 7.10/1 and figure 7.10/2 show how to handle a Location Update request signal referring with the CCBS Monitoring Flag in the GLR by using the alternative 1 treatment, the alternative 2 treatment respectively. These figures only indicate how a Location Update request signal is treated in the GLR. Refer to the 3G TS 23.093 [8] for a more detail treatment about the CCBS service. + +Other CCBS related MAP operations, e.g. RegisterCC-entry, EraseCC-Entry and RemoteUserFree are always relayed transparently from the HLR to the VLR or vice versa. + +![Sequence diagram showing Update Location request signal handling for CCBS in the GLR (Alternative 1).](ba676d18b6a00f27c5bfaec9eeec20be_img.jpg) + +The sequence diagram illustrates the interaction between the MS (Mobile Station), MSC1/VLR1, MSC2/VLR2, GLR (GPRS Location Register), and HLR (Home Location Register) for CCBS (Call Completion on Busy Subscriber) in the GLR. The diagram is divided into two main parts based on the MS status. + +**Part 1: MS Idle to Busy** + +- The MS is initially **Idle**. It sends an **Update Location** message to MSC1/VLR1. +- MSC1/VLR1 sends a **Subsequent Location Update in GLR area** message to the GLR. +- The GLR initiates an **Insert subscriber data process** with the HLR. +- The HLR responds with **Location Update ack.** to the GLR. +- The GLR sends a **Start reporting** message to the HLR. A callout indicates **CCBS mon. Flag = off as default value**. +- The HLR responds with **Start reporting ack.** to the GLR. +- The GLR sends a **Start reporting** message to MSC1/VLR1. A callout indicates **CCBS mon. Flag = on**. +- MSC1/VLR1 responds with **Start reporting ack.** to the GLR. +- The MS status changes to **Busy**. + +**Part 2: MS Idle to Busy (Due to CCBS call)** + +- The MS is initially **Idle**. It sends an **Update Location** message to MSC2/VLR2. +- MSC2/VLR2 sends a **Location Update** message to the GLR. +- The GLR initiates an **Insert subscriber data process** with the HLR. +- The HLR responds with **Location Update ack.** to the GLR. +- The GLR sends a **Location Update ack.** message to MSC2/VLR2. +- The MS status changes to **Busy**. A callout indicates this is **Due to CCBS call**. +- The MS sends a **Stop reporting** message to MSC2/VLR2. +- MSC2/VLR2 sends a **Stop reporting** message to the GLR. A callout indicates **CCBS mon. Flag = off**. +- The GLR sends a **Stop reporting** message to the HLR. +- The HLR responds with **Stop reporting ack.** to the GLR. +- The GLR responds with **Stop reporting ack.** to MSC2/VLR2. + +Sequence diagram showing Update Location request signal handling for CCBS in the GLR (Alternative 1). + +Figure 7.10/1: Update Location request signal handling for CCBS in the GLR (Alternative 1) + +![Sequence diagram for Update Location request signal handling for CCBS in the GLR (Alternative 2).](a5404b7275b06497eecf9b5883604753_img.jpg) + +The sequence diagram illustrates the interaction between the MS (Mobile Station), MSC1/VLR1, MSC2/VLR2, GLR (GPRS Location Register), and HLR (Home Location Register) for CCBS in the GLR (Alternative 2). + +**Sequence of Events:** + +- MS Status:** The MS starts in an **Idle** state. +- Update Location:** The MS sends an **Update Location** message to MSC1/VLR1. +- Subsequent Location Update in GLR area:** MSC1/VLR1 sends this message to the GLR. +- Insert subscriber data process:** The GLR initiates this process with MSC1/VLR1. +- Location Update ack.:** MSC1/VLR1 sends this to the GLR. +- Start reporting:** The GLR sends this to MSC1/VLR1. +- CCBS mon. Flag = off as default value:** A note indicates the default value for the CCBS monitoring flag. +- Start reporting ack.:** MSC1/VLR1 sends this to the GLR. +- Update Location:** The MS sends another **Update Location** message, this time to MSC2/VLR2. +- Location Update:** MSC2/VLR2 sends this to the GLR. +- Launch Status report message:** The GLR sends this to MSC2/VLR2. +- Status report (Idle):** MSC2/VLR2 sends this to the HLR. +- Insert subscriber data process:** The GLR initiates this process with MSC2/VLR2. +- Location Update ack.:** MSC2/VLR2 sends this to the GLR. +- Start reporting:** The GLR sends this to MSC2/VLR2. +- Start reporting ack.:** MSC2/VLR2 sends this to the GLR. +- Due to CCBS call:** A note indicates the MS status changes to **Busy** due to a CCBS call. +- Stop reporting:** The GLR sends this to MSC2/VLR2. +- CCBS mon. Flag = :** A note indicates the CCBS monitoring flag value. +- Stop reporting ack.:** MSC2/VLR2 sends this to the GLR. +- Stop reporting:** The GLR sends this to MSC1/VLR1. +- Stop reporting ack.:** MSC1/VLR1 sends this to the GLR. + +Sequence diagram for Update Location request signal handling for CCBS in the GLR (Alternative 2). + +**Figure 7.10/2: Update Location request signal handling for CCBS in the GLR (Alternative 2)** + +#### 7.10.2.1 Functional requirements of GLR + +The Alternative 1 introduced in this section for Update Location request signal handling for CCBS in the GLR is illustrated in the section 7.2.1 Location Management Procedures as one possible alternative. + +##### 7.10.2.1.1 Process Set\_reporting\_GLR + +Figure 7.10/3 shows the SDL chart for Process Set\_reporting\_GLR. + +![Flowchart for Process Set_reporting_GLR. The process starts at an Idle state, sets the HLR, checks parameters (referencing TS), and then checks if the result passes. If it passes, it sets the CCBS flag, copies data from the Set HLR, sets the VLR, and waits for a response. If it fails, it goes to an Abort state. Upon receiving a response, it copies the response, sets the HLR response, and returns to Idle. If no response is received, it copies data from the Set VLR, sets the HLR, and returns to Idle.](a7450c80e88ad3f6ca1427ad84020998_img.jpg) + +### Process 1(1) + +Process in the to file set + +Signals to/from the are to/from the Signals to/from the are to/from the + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> SetHLR[/Set HLR/]; SetHLR --> CheckParam[Check Paramete]; CheckParam --> SeeTS[See TS]; CheckParam --> Result{Result: pass}; Result -- Yes --> SetCCBS[Set CCBS flag]; SetCCBS --> CopySetHLR[Copy from Set HLR]; CopySetHLR --> SetVLR[/Set VLR/]; SetVLR --> WaitForResp[Wait_For Respons]; WaitForResp --> SetVLR2[/Set VLR/]; WaitForResp --> Abort1[/Abort/]; WaitForResp --> SetVLRResp[/Set VLR respons/]; SetVLR2 --> CopySetVLR[Copy from Set VLR]; CopySetVLR --> SetHLR2[/Set HLR/]; SetHLR2 --> Abort2[/Abort/]; SetHLR2 --> Idle2([Idle]); Abort1 --> Abort2; SetVLRResp --> CopyResp[Copy respons]; CopyResp --> SetHLRResp[/Set HLR respons/]; SetHLRResp --> Idle2; Result -- No --> SetHLRResp; +``` + +Flowchart for Process Set\_reporting\_GLR. The process starts at an Idle state, sets the HLR, checks parameters (referencing TS), and then checks if the result passes. If it passes, it sets the CCBS flag, copies data from the Set HLR, sets the VLR, and waits for a response. If it fails, it goes to an Abort state. Upon receiving a response, it copies the response, sets the HLR response, and returns to Idle. If no response is received, it copies data from the Set VLR, sets the HLR, and returns to Idle. + +Figure 7.10/3: Process Set\_reporting\_GLR + +##### 7.10.2.1.2 Process Status report GLR + +Figure 7.10/4 shows the SDL chart for Process Status\_report\_GLR. + +![SDL chart for Process Status_report_GLR. The process starts at an initial state, goes to Idle, receives a Status report from VLR, checks parameters (referencing TS 23.018), and then checks if the result passes. If it passes, it copies information and sends a Status report to HLR, then waits for a response. The response can be an HLR ack (leading to copying information and sending a VLR ack), an Abort, or a negative response (leading to copying the negative response and sending a VLR negative response). All three outcomes lead to the Idle state. If the initial parameter check fails, it goes directly to the Idle state.](64bec4cd45e47e1976245711f702aca2_img.jpg) + +### Process Status\_report\_GLR + +1(1) + +Process in the GLR to handle Status report + +Signals to/from the left are to/from the VLR +Signals to/from the right are to/from the HLR + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Status_report_VLR : Status report VLR + Status_report_VLR --> Check_Parameter : Check Parameter (See TS 23.018) + Check_Parameter --> Result_pass{Result= pass?} + Result_pass -- No --> Idle + Result_pass -- Yes --> Copy_info_VLR : Copy information from Status report VLR + Copy_info_VLR --> Status_report_HLR : Status report HLR + Status_report_HLR --> Wait_For_Response : Wait_For_Response + state "Status report HLR ack" as Status_report_HLR_ack + state "Abort" as Abort + state "Status report HLR negative response" as Status_report_HLR_neg_resp + Wait_For_Response --> Status_report_HLR_ack + Wait_For_Response --> Abort + Wait_For_Response --> Status_report_HLR_neg_resp + Status_report_HLR_ack --> Copy_info_HLR_ack : Copy information from Status report HLR ack + Copy_info_HLR_ack --> Status_report_VLR_ack : Status report VLR ack + Status_report_VLR_ack --> Idle + Abort --> Abort + Status_report_HLR_neg_resp --> Copy_neg_resp : Copy negative response + Copy_neg_resp --> Status_report_VLR_neg_resp : Status report VLR negative response + Status_report_VLR_neg_resp --> Idle +``` + +SDL chart for Process Status\_report\_GLR. The process starts at an initial state, goes to Idle, receives a Status report from VLR, checks parameters (referencing TS 23.018), and then checks if the result passes. If it passes, it copies information and sends a Status report to HLR, then waits for a response. The response can be an HLR ack (leading to copying information and sending a VLR ack), an Abort, or a negative response (leading to copying the negative response and sending a VLR negative response). All three outcomes lead to the Idle state. If the initial parameter check fails, it goes directly to the Idle state. + +Figure 7.10/4: Process Status\_report\_GLR + +##### 7.10.2.1.3 Process Remote\_User\_Free\_GLR + +Figure 7.10/5 shows the SDL chart for Process Remote\_User\_Free\_GLR. + +![SDL chart for Process Remote_User_Free_GLR. The process starts at an initial state, goes to Idle, then sends RUF HLR. It checks parameters (referencing TS 23.018). If the result passes, it copies information from RUF HLR, sends RUF VLR, and waits for a response. If the result does not pass, it goes directly to the final Idle state. Upon receiving a response, it either acknowledges (RUF VLR ack, then RUF HLR ack) or handles a negative response (copy negative response, then RUF HLR negative response). Both paths lead to the final Idle state. Abort states are also shown as transitions.](8edfc370769207831f060f44d2281084_img.jpg) + +**Process** 1(1) + +Process in the GLR to handle Remote User Free + +Signals to/from the left are to/from the VLR +Signals to/from the right are to/from the HLR + +``` +stateDiagram-v2 + [*] --> Idle1[Idle] + Idle1 --> RUF_HLR[RUF HLR] + RUF_HLR --> Check_Parameter[Check Parameter] + Check_Parameter --> See_TS_23.018[See TS 23.018] + Check_Parameter --> Result_Pass{Result:= pass?} + Result_Pass -- No --> Idle2[Idle] + Result_Pass -- Yes --> Copy_Info[Copy information from RUF HLR] + Copy_Info --> RUF_VLR[RUF VLR] + RUF_VLR --> Wait_For_Response[Wait_For_Response] + Wait_For_Response --> RUF_VLR_ack[RUF VLR ack] + Wait_For_Response --> Abort1[Abort] + Wait_For_Response --> RUF_VLR_neg_response[RUF VLR negative response] + RUF_VLR_ack --> Copy_Ack[Copy information from RUF VLR ack] + Copy_Ack --> RUF_HLR_ack[RUF HLR ack] + RUF_HLR_ack --> Idle2 + RUF_VLR_neg_response --> Copy_Neg_Response[Copy negative response] + Copy_Neg_Response --> RUF_HLR_neg_response[RUF HLR negative response] + RUF_HLR_neg_response --> Idle2 + Abort1 --> Abort2[Abort] + Abort2 --> Idle2 +``` + +SDL chart for Process Remote\_User\_Free\_GLR. The process starts at an initial state, goes to Idle, then sends RUF HLR. It checks parameters (referencing TS 23.018). If the result passes, it copies information from RUF HLR, sends RUF VLR, and waits for a response. If the result does not pass, it goes directly to the final Idle state. Upon receiving a response, it either acknowledges (RUF VLR ack, then RUF HLR ack) or handles a negative response (copy negative response, then RUF HLR negative response). Both paths lead to the final Idle state. Abort states are also shown as transitions. + +Figure 7.10/5: Process Remote\_User\_Free\_GLR + +##### 7.10.2.1.4 Procedure CCBS\_status\_report\_GLR + +Figure 7.10/6 shows the SDL chart for Procedure CCBS\_status\_report\_GLR. + +![SDL chart for Procedure CCBS_status_report_GLR. The process starts with an initial state, followed by a decision 'CCBS mon flag on?'. If 'No', it ends. If 'Yes', it proceeds to 'Set subscriber status = idle', then 'Status report HLR', then 'Wait_For_Response'. From 'Wait_For_Response', there are three possible outcomes: 'Status report HLR ack', 'Status report HLR negative response', and 'Abort', each leading to an end state.](57134800ac3a97b6212b27b93aa196ac_img.jpg) + +**Procedure CCBS\_status\_report\_GLR** 1(1) + +Procedure to send status report in GLR + +Signals to/from the right are to/from the HLR + +``` +stateDiagram-v2 + [*] --> Decision{CCBS mon flag on?} + Decision -- No --> [*] + Decision -- Yes --> SetStatus[Set subscriber status = idle] + SetStatus --> StatusReport[Status report HLR] + StatusReport --> WaitResponse([Wait_For_Response]) + WaitResponse --> Ack{Status report HLR ack} + WaitResponse --> NegativeResponse{Status report HLR negative response} + WaitResponse --> Abort{Abort} + Ack --> [*] + NegativeResponse --> [*] + Abort --> [*] +``` + +SDL chart for Procedure CCBS\_status\_report\_GLR. The process starts with an initial state, followed by a decision 'CCBS mon flag on?'. If 'No', it ends. If 'Yes', it proceeds to 'Set subscriber status = idle', then 'Status report HLR', then 'Wait\_For\_Response'. From 'Wait\_For\_Response', there are three possible outcomes: 'Status report HLR ack', 'Status report HLR negative response', and 'Abort', each leading to an end state. + +**Figure 7.10/6: Procedure CCBS\_Status\_Report\_GLR** + +##### 7.10.2.1.5 Procedure CCBS\_start\_report\_GLR + +Figure 7.10/7 shows the SDL chart for Procedure CCBS\_start\_report\_GLR + +![SDL chart for Procedure CCBS_start_report_GLR](ef0faba51289e3a364ba51e5ef4d1a43_img.jpg) + +**Procedure CCBS\_start\_report\_GLR** 1(1) + +The diagram is an SDL chart for the procedure CCBS\_start\_report\_GLR. It begins with a start symbol (oval with a vertical line), leading to a decision diamond labeled "CCBS mon flag on?". If the answer is "No", the flow ends at a circle with an 'X'. If the answer is "Yes", the flow proceeds to a process box labeled "set start reporting", followed by a transition box labeled "Set reporting VLR". This leads to a state box labeled "Wait\_For\_Response". From this state, three possible transitions are shown: "Set reporting VLR ack", "Set reporting VLR negative response", and "Abort". Each of these transitions leads to a circle with an 'X', representing an end state. There are two callout boxes: one on the top left stating "Procedure to send CCBS start report in GLR" and one on the top right stating "Signals to/from the right are to/from the VLR". + +``` +graph TD; Start([ ]) --> Decision{CCBS mon flag on?}; Decision -- No --> End1((X)); Decision -- Yes --> Process[set start reporting]; Process --> Transition[Set reporting VLR]; Transition --> State[Wait_For_Response]; State --> Transition1[Set reporting VLR ack]; State --> Transition2[Set reporting VLR negative response]; State --> Transition3[Abort]; Transition1 --> End2((X)); Transition2 --> End3((X)); Transition3 --> End4((X)); +``` + +SDL chart for Procedure CCBS\_start\_report\_GLR + +Figure 7.10/7: Procedure CCBS\_Start\_Report\_GLR + +## 7.11 Location Service + +This section is based on that in 3G TS 23.171 [7]. + +### 7.11.1 Mobile Terminating Location Request + +#### 7.11.1.1 Circuit Switched Mobile Terminating Location Request (CS-MT-LR) + +![Sequence diagram for Circuit Switched Mobile Terminating Location Request (CS-MT-LR). The diagram shows the interaction between Client, GMLC, HLR, IM-MSC, GLR, 3G-VMSC, SRNC, and MS. The process involves a service request, routing information exchange, subscriber location provision, and final location reporting.](3f2ccb513ccdda4c3e19aea59f7f6215_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC + participant HLR + participant IM-MSC + participant GLR + participant 3G-VMSC + participant SRNC + participant MS + + Note left of Client: 1. LCS Service Request + Client->>GMLC: 1. LCS Service Request + GMLC->>HLR: 2. MAP Send Routing Info for LCS + HLR-->>GMLC: 3. MAP Send Routing Info for LCS ack. + GMLC->>IM-MSC: 4. MAP Provide Subscriber Location + Note right of IM-MSC: 2') + IM-MSC->>GLR: 2') MAP Send Routing Info for LCS + GLR-->>IM-MSC: 3') MAP Send Routing Info for LCS ack. + IM-MSC->>3G-VMSC: 4') MAP Provide Subscriber Location + Note right of 3G-VMSC: 5. MS Paging, Authentication, Ciphering + 3G-VMSC->>MS: 5. MS Paging, Authentication, Ciphering + Note right of 3G-VMSC: [6. LCS Location Notification Invoke?] + 3G-VMSC->>MS: [6. LCS Location Notification Invoke?] + Note right of 3G-VMSC: [7. LCS Location Notification Return Result?] + 3G-VMSC->>MS: [7. LCS Location Notification Return Result?] + Note right of 3G-VMSC: 8. RANAP Location Reporting Control + 3G-VMSC->>SRNC: 8. RANAP Location Reporting Control + Note right of SRNC: 9. Messages for individual positioning methods + SRNC->>3G-VMSC: 10. RANAP Location Report + Note right of IM-MSC: 11') + IM-MSC->>GLR: 11') MAP Provide Subscriber Location ack. + GLR-->>IM-MSC: 11. MAP Provide Subscriber Location ack. + IM-MSC->>GMLC: 11. MAP Provide Subscriber Location ack. + GMLC->>Client: 12. LCS Service Response + +``` + +Sequence diagram for Circuit Switched Mobile Terminating Location Request (CS-MT-LR). The diagram shows the interaction between Client, GMLC, HLR, IM-MSC, GLR, 3G-VMSC, SRNC, and MS. The process involves a service request, routing information exchange, subscriber location provision, and final location reporting. + +Figure 7.11/1: General Network Positioning for a MT-LR + +##### 7.11.1.1.1 Location Preparation Procedure + +1) and 2) Same as the steps not involving GLR. See 3G TS 23.171 [7]. + +3) The HLR returns the current 3G-VMSC address that includes actually IM-MSC address. The other action is the same as the step not involving GLR. See 3G TS 23.171 [7]. + +4) The GMLC sends a MAP\_PROVIDE\_SUBSCRIBER\_LOCATION message to the IM-MSC indicated by the HLR. The other action is the same as the step not involving GLR. See 3G TS 23.171 [7]. + +2') If the IM-MSC already knows the VMSC location for the particular IMSI (e.g. from a previous location request), this step and step 3' may be skipped. Otherwise, the IM-MSC sends a MAP\_SEND\_ROUTING\_INFO\_FOR\_LCS message to the GLR of the target MS to be located with the IMSI of this MS. + +3') The GLR returns the current VMSC address and whichever of the IMSI and MSISDN was not provided in step (2') for the particular MS. + +- 4') The IM-MSC sends a MAP\_PROVIDE\_SUBSCRIBER\_LOCATION message to the VMSC indicated by the GLR. + 5) to 8) Same as the steps not involving GLR. See 3G TS 23.171 [7]. + +##### 7.11.1.1.2 Positioning Measurement Establishment Procedure + +- 9) Same as the step not involving GLR. See 3G TS 23.171 [7]. + +##### 7.11.1.1.3 Location Calculation and Release Procedure + +- 10) Same as the step not involving GLR. See 3G TS 23.171 [7]. + 11') The VMSC returns the location estimate and its age to the IM-MSC. The other action is the same as the step not involving GLR. See 3G TS 23.171 [7]. + 11) The IM-MSC receives the location estimate and its age, then sends them to the GMLC. + 12) Same as the step not involving GLR. See 3G TS 23.171 [7]. + +#### 7.11.1.2 MT-LR for a previously obtained location estimate + +![Sequence diagram for MT-LR for a previously obtained location estimate. The diagram shows interactions between Client, GMLC, HLR, SRNC, 3G-VMSC, and UE. The Client sends an LCS Service Request to the GMLC. The GMLC sends a MAP Send Routing Info for LCS to the HLR, which returns a MAP Send Routing Info for LCS ack. The GMLC then sends a MAP Provide Subscriber Location to the SRNC. The SRNC sends a MAP Send Routing Info for LCS to the HLR, which returns a MAP Send Routing Info for LCS ack. The SRNC then sends a MAP Provide Subscriber Location to the 3G-VMSC, which returns a MAP Provide Subscriber Location ack. Finally, the SRNC sends a MAP Provide Subscriber Location ack to the GMLC, which sends an LCS Service Response to the Client.](56468323fb2f5ff6f0a8bf9bf1f691e8_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC + participant HLR1 as HLR + participant SRNC1 as SRNC + participant HLR2 as HLR + participant VMSC as 3G-VMSC + participant SRNC2 as SRNC + participant UE + + Client->>GMLC: 1. LCS Service Request + GMLC->>HLR1: 2. MAP Send Routing Info for LCS + HLR1-->>GMLC: 3. MAP Send Routing Info for LCS ack. + GMLC->>SRNC1: 4. MAP Provide Subscriber Location + SRNC1->>HLR2: 2'. MAP Send Routing Info for LCS + HLR2-->>SRNC1: 3'. MAP Send Routing Info for LCS ack. + SRNC1->>VMSC: 4'. MAP Provide Subscriber Location + VMSC-->>SRNC1: 5'. MAP Provide Subscriber Location ack. + SRNC1-->>GMLC: 5. MAP Provide Subscriber Location ack. + GMLC-->>Client: 6. LCS Service Response + +``` + +Sequence diagram for MT-LR for a previously obtained location estimate. The diagram shows interactions between Client, GMLC, HLR, SRNC, 3G-VMSC, and UE. The Client sends an LCS Service Request to the GMLC. The GMLC sends a MAP Send Routing Info for LCS to the HLR, which returns a MAP Send Routing Info for LCS ack. The GMLC then sends a MAP Provide Subscriber Location to the SRNC. The SRNC sends a MAP Send Routing Info for LCS to the HLR, which returns a MAP Send Routing Info for LCS ack. The SRNC then sends a MAP Provide Subscriber Location to the 3G-VMSC, which returns a MAP Provide Subscriber Location ack. Finally, the SRNC sends a MAP Provide Subscriber Location ack to the GMLC, which sends an LCS Service Response to the Client. + +**Figure 7.11/2: MT-LR for a previously obtained location estimate** + +- (1) to (4) Same as the step not involving GLR. See 3G TS 23.171 [7]. + (2') to (3') Same as step 2' for an MT-LR. + (4') Same as step 4' for an MT-LR. The message sent to the 3G-VMSC requests either an initial location or current or last known location with "no delay". + (5') Same as step 11 for an MT-LR. + (5) Same as step 11 for an MT-LR. + (6) Same as the step not involving GLR. See 3G TS 23.171 [7]. + +#### 7.11.1.3 Network Induced Location Request (NI-LR) + +This procedure is the same as the procedure not involving GLR. See 3G TS 23.171 [7]. + +#### 7.11.1.4 Network Induced Location Request (NI-LR) from a Serving RNC for a target UE in dedicated mode + +This procedure is not related to GLR. + +### 7.11.2 Mobile Originating Location Request + +#### 7.11.2.1 Mobile Originating Location Request, Circuit Switched (CS-MO-LR) + +This procedure is the same as the procedure not involving GLR. See 3G TS 23.171 [7]. + +## 7.12 IST of non-CAMEL implementation + +If the GLR supports IST, when the GLR receives an Update Location request that indicates that the MSC/VLR supports IST, it relays the indication to the HLR. If not, the GLR may ignore the indication. When the GLR receives an IST Alert Request from the MSC, it relays the message to the HLR. The HLR sends an IST Alert Response to the GLR, and then the GLR relays the message to the MSC. + +When the IM-MSC receives an IST Command Request from the HLR, it retrieves the location information, i.e., MSC Number, from the GLR and sends the message to the MSC. Then the IM-MSC receives the response from the MSC and sends the response to the HLR. + +## 7.13 The interaction with Super-Charger + +Following sub-clauses show the location updating procedures in the case that the serving nodes in the network with the GLR support the Super-Charger functionality. + +### 7.13.1 First Location Updating Procedure in the Super-Charged network + +The first location updating procedure in a Super-Charged network is illustrated in figure 7.13/1. Each step is explained in the following list. + +![Sequence diagram illustrating the First Location Updating Procedure in the case that visited NW supports the Super-Charger features. The diagram shows interactions between VLR/SGSN, GLR, and HLR across Visited NW and Home NW domains.](10737843d428d439ee47ad580036c875_img.jpg) + +``` + +sequenceDiagram + participant VLR/SGSN + participant GLR + participant HLR + Note over VLR/SGSN, GLR: Visited NW + Note over HLR: Home NW + + VLR/SGSN->>GLR: 1. Update Location or Update GPRS Location + GLR->>HLR: 1. Update Location or Update GPRS Location + HLR->>GLR: 2. Insert Subscriber Data + GLR->>VLR/SGSN: 2. Insert Subscriber Data + VLR/SGSN->>GLR: 2. Insert Subscriber Data ack + GLR->>HLR: 2. Insert Subscriber Data ack + HLR->>GLR: 3. Update Location ack or Update GPRS Location ack + GLR->>VLR/SGSN: 3. Update Location ack or Update GPRS Location ack + +``` + +Sequence diagram illustrating the First Location Updating Procedure in the case that visited NW supports the Super-Charger features. The diagram shows interactions between VLR/SGSN, GLR, and HLR across Visited NW and Home NW domains. + +**Figure 7.13/1: First Location Updating Procedure in the case that visited NW supports the Super-Charger features** + +#### Procedure: + +- 1) When the GLR receives an *Update Location* or *Update GPRS Location* message from a serving node (i.e., VLR or SGSN) and does not hold the subscriber's information for the user (ex. at the first location updating to the + +GLR), it relays the message without age indicator (if age indicator is received from the serving node, the GLR deletes it) to the HLR. + +- 2) The HLR stores the address and number of serving node. Thereafter the HLR initiates insert subscriber data procedure and cancel location procedure (only if both the HLR and previous serving node support the Super-Charger features). When the GLR receives *Insert Subscriber Data* message from the HLR, the GLR creates an age indicator and stores the subscriber's information in the message and transports it to the serving node with the age indicator. +- 3) After these procedures, the HLR replies to an *Update Location* or *Update GPRS Location* message from the GLR and the GLR transports the response to the serving node. + +### 7.13.2 Second and further Location Updating Procedure in the Super-Charged networks + +The second and further location updating procedure in a Super-Charged network is illustrated in figure 7.13/2. Each step is explained in the following list. + +![Sequence diagram of the Second and further Location Updating Procedure in the case that visited NW supports the Super-Charger features. The diagram shows interactions between VLR/SGSN OLD, VLR/SGSN NEW, GLR, and HLR. The GLR receives an Update Location or Update GPRS Location message from the VLR/SGSN NEW. It then initiates a Cancel Location procedure with the VLR/SGSN OLD (Note1) and an Insert Subscriber Data procedure with the HLR (Note2). Finally, the HLR sends an Update Location ack or Update GPRS Location ack to the GLR, which then relays it to the VLR/SGSN NEW.](74e409e1548dd2606c4de9bdfe9806e4_img.jpg) + +``` + +sequenceDiagram + participant VLR_OLD as VLR/SGSN OLD + participant VLR_NEW as VLR/SGSN NEW + participant GLR + participant HLR + + Note left of VLR_NEW: Visited NW + Note right of HLR: Home NW + + VLR_NEW->>GLR: 1. Update Location or Update GPRS Location + Note right of GLR: Note1: This procedure is initiated only when the serving node doesn't support SC feature + GLR->>VLR_OLD: 2. Cancel Location + VLR_OLD-->>GLR: 2. Cancel Location ack + Note right of GLR: Note2: This procedure is initiated only if the serving node requests the subscriber data or the subscriber data in the serving node is not consistent with that in the GLR + GLR->>HLR: 3. Insert Subscriber Data + HLR-->>GLR: 3. Insert Subscriber Data ack + HLR->>GLR: 4. Update Location ack Update GPRS Location ack + GLR-->>VLR_NEW: 4. Update Location ack Update GPRS Location ack + +``` + +Sequence diagram of the Second and further Location Updating Procedure in the case that visited NW supports the Super-Charger features. The diagram shows interactions between VLR/SGSN OLD, VLR/SGSN NEW, GLR, and HLR. The GLR receives an Update Location or Update GPRS Location message from the VLR/SGSN NEW. It then initiates a Cancel Location procedure with the VLR/SGSN OLD (Note1) and an Insert Subscriber Data procedure with the HLR (Note2). Finally, the HLR sends an Update Location ack or Update GPRS Location ack to the GLR, which then relays it to the VLR/SGSN NEW. + +**Figure 7.13/2: Second and further Location Updating Procedure in the case that visited NW supports the Super-Charger features** + +#### Procedure: + +- 1) When the GLR receives an *Update Location* or *Update GPRS Location* message with an age indicator from newly visited serving node (i.e. VLR or GSN) and holds the subscriber information for the user (i.e. at second or further location updating to the GLR), it stores the address and number of newly visited serving node included in the received message. +- 2) The GLR does not initiate cancel location procedure if the previous node supports the Super-Charger features. +- 3) When the age indicator from the serving node indicates the serving node does not request the subscription data, the GLR checks if the subscription data retained in serving node is consistent with that stored in the GLR. If so, + +the GLR shall not send subscription data to the newly visited serving node. Otherwise the GLR initiates the insert subscriber procedure to the serving node. + +- 4) After these procedures, the GLR replies to an *Update Location* or *Update GPRS Location* message from the serving node. + +### 7.13.3 Cancel Location Procedure in the Super-Charged networks + +The cancel location procedure in a Super-Charged network when MS leave the network is illustrated in figure 7.13/3. Each step is explained in the following list. + +![Sequence diagram for Cancel Location Procedure in Super-Charged networks. The diagram shows interactions between Visited NW (VLR/SGSN OLD and GLR) and Home NW (HLR).](8b5a2bf5517051acf8bcc2587bcb73a1_img.jpg) + +``` + +sequenceDiagram + participant HLR as HLR + participant GLR as GLR + participant VLR as VLR/SGSN OLD + + Note right of HLR: Note + HLR->>GLR: 1. Cancel Location + Note right of GLR: Note + GLR->>VLR: 2. Cancel Location + Note right of VLR: Note + VLR-->>GLR: 2. Cancel Location ack + Note right of GLR: Note + GLR->>HLR: 3. Cancel Location ack + +``` + +Note: This procedure is initiated only when the serving node doesn't support SC feature + +Sequence diagram for Cancel Location Procedure in Super-Charged networks. The diagram shows interactions between Visited NW (VLR/SGSN OLD and GLR) and Home NW (HLR). + +**Figure 7.13/3: Cancel Location Procedure in the case that visited NW supports the Super-Charger features** + +#### Procedure: + +- 1) When the GLR receives a *Cancel Location* message from the HLR, it checks whether the serving node supports the Super-Charger features or not. +- 2) If the serving node does not support the Super-Charger features, the GLR initiates a cancel location procedure to the serving node. +- 3) When the GLR receives the response of the *Cancel Location* message, it responds to the HLR by sending the *Cancel Location ack* message. + +### 7.13.4 Functional requirement for the GLR + +#### 7.13.4.1 Procedure Super\_Charged\_Cancel\_Location\_GLR + +Figure 7.13/4 shows SDL chart for Procedure Super\_Charged\_Cancel\_Location\_GLR. + +##### Procedure Super\_Charged\_Cancel\_Location\_GLR + +1(1) + +The procedure Super\_Charged\_Cancel\_Location\_GLR determines whether a Super-Charged GLR shall send the cancel location message to the previous network entity. + +![Flowchart for Procedure Super_Charged_Cancel_Location_GLR](a3d6b1f562612dbd5a5d7c4ce91999d1_img.jpg) + +``` +graph TD; Start([ ]) --> GLR{Super-Charged GLR}; GLR -- yes --> Decision{Previous Network Entity Supports Super-Charger?}; GLR -- no --> Fail[Result:= Fail]; Decision -- yes --> Pass[Result:= Pass]; Decision -- no --> Fail; Pass --> End(( )); Fail --> End +``` + +The flowchart illustrates the procedure Super\_Charged\_Cancel\_Location\_GLR. It begins with a start symbol (a circle with a vertical line), leading to a decision node labeled 'Super-Charged GLR'. From this node, a 'yes' path leads down to another decision node labeled 'Previous Network Entity Supports Super-Charger?'. A 'no' path from the first node leads to the right and then down to a 'Result:= Fail' box. From the second decision node, a 'yes' path leads down to a 'Result:= Pass' box, and a 'no' path leads to the right and then down to the same 'Result:= Fail' box. Both 'Result:= Pass' and 'Result:= Fail' boxes lead to a common horizontal line that connects to an end symbol (a circle with an 'X'). + +Flowchart for Procedure Super\_Charged\_Cancel\_Location\_GLR + +Figure 7.13/4: Procedure Super\_Charged\_Cancel\_Location\_GLR + +#### 7.13.4.2 Procedure Super\_Charged\_Location\_Updating\_GLR + +Figure 7.13/5 shows SDL chart for Procedure Super\_Charged\_Location\_Updating\_GLR. + +![SDL chart for Procedure Super_Charged_Location_Updating_GLR. The flow starts with a start symbol, followed by a state 'Super-Charged GLR'. It then enters a loop of three decision diamonds: 'Serving Network Entity Supports Super-Charger?', 'Send subscriber data?', and 'Subscriber data valid?'. If any decision is 'no', it leads to 'Result:=Fail'. If all are 'yes', it leads to 'Result:=Pass'. Both results lead to an end symbol.](7818b1bd115c04ee738bcf90f51d945b_img.jpg) + +**Procedure Super\_Charged\_Location\_Updating\_GLR** 1(1) + +The procedure Super\_Charged\_Location\_Updating\_GLR determines whether a Super-Charged GLR shall send subscription data to the requesting network entity. + +``` +graph TD; Start([ ]) --> State1[Super-Charged GLR]; State1 --> Decision1{Serving Network Entity Supports Super-Charger?}; Decision1 -- no --> ResultFail[Result:=Fail]; Decision1 -- yes --> Decision2{Send subscriber data?}; Decision2 -- no --> ResultFail; Decision2 -- yes --> Decision3{Subscriber data valid?}; Decision3 -- no --> ResultFail; Decision3 -- yes --> ResultPass[Result:=Pass]; ResultPass --> End(( )); ResultFail --> End; +``` + +SDL chart for Procedure Super\_Charged\_Location\_Updating\_GLR. The flow starts with a start symbol, followed by a state 'Super-Charged GLR'. It then enters a loop of three decision diamonds: 'Serving Network Entity Supports Super-Charger?', 'Send subscriber data?', and 'Subscriber data valid?'. If any decision is 'no', it leads to 'Result:=Fail'. If all are 'yes', it leads to 'Result:=Pass'. Both results lead to an end symbol. + +**Figure 7.13/5: Procedure Super\_Charged\_Location\_Updating\_GLR** + +# --- 8 The subscriber information stored in the GLR + +The subscriber information stored in the GLR can be categorised in the following types. + +## 8.1 Information for HLR emulation + +The GLR retrieves this kind of subscriber information mainly from Insert Subscriber Data message received from the HLR and stores it. Then this message is transported to the VLR transparently. + +This type of information is for example: + +- IMSI. +- International MS ISDN number. +- PDP Type. + +## 8.2 Information for address and identity conversion + +On location updating the VLR or SGSN sends Update Location message to the GLR and notifies its VLR number and MSC number or SGSN number and SGSN address by the message. On the first updating in the newly visited network, the GLR relays Update Location message to the HLR setting. + +- The GLR number as the VLR number(E.164 address). +- The IM\_MSC number as the MSC number(E.164 address). +- The GLR number as the SGSN number(E.164 address). +- The IM-GSN address as the SGSN address(IP address). + +The GLR keeps the association of these numbers and addresses and updates it on the second and further updating. And when the GLR receives and stores the HLR number in Update Location ack message form the HLR, it relays the message to the VLR setting. + +- The GLR number as the HLR number (E. 164 address). +- Identity Conversion. + +On location updating the VLR creates and allocates the LMSI number (denote LMSIv) for the user and sends it to the GLR in Update Location message. When the GLR receives the message, it creates and allocates another LMSI number (denote LMSIg) and associates LMSIg with received LMSIv. The GLR notifies LMSIg to the HLR sending Update Location message. This method can speed up the search for subscriber data in the GLR when the GLR receives some message from the HLR. + +## 8.3 Information for Location updating Screening + +This information is used for the GLR to judge whether requested location updating is necessary to be indicated to HLR or not. Following are information categorized in this type. + +MNRF, MNRG. + +- CCBS Monitoring Flag. +- MSC area restricted flag. +- SGSN area restricted flag. +- Location and Subscriber information Confirmed by HLR indicator (LSIC). + +Subclause 7.7 shows the procedure for SMS alerting in the network with the GLR. In the procedure Mobile station Not Reachable Flag (MNRF) and Mobile station Not Reachable for GPRS (MNRG) are needed. + +The CCBS Monitoring Flag is set when the user in the GLR area is CCBS monitored by the VLR. As one option, while it is set, the Update Location message is relayed to the HLR to inform the appropriate CCBS process in the HLR. More detailed procedures for the CCBS are included in section 7.10. + +MSC area restricted flag and SGSN area restricted flag are needed for regional restriction service. See section 7.5 for more detailed procedures. + +LSIC is used for restart procedures. Section 7.6.3 includes more detailed description for the usage of this indicator. + +## 8.4 Information for support of Super-Charger functionality + +This information is used for the GLR to behave as the HLR supporting the Super-Charger functionality towards the serving node (i.e. VLR or SGSN) which also supports Super-Charger functionality. Following is information categorised in this type. + +- Age indicator for CS. +- Age indicator for PS. + +## 8.5 Other Information + +The GLR has Service Substitution Induced Flag list. This information show which service is replaced by service substitution. See section 7.2.1.3 for more detail on the handling of unsupported services. + +## 8.6 IMSI Record in the GLR + +**Table 8.5/1: Subscriber Information stored in the GLR** + +| PARAMETER | PRESENCE | CATEGORY (*1) | NOTE | +|----------------------------------------------------------------|----------|---------------|------| +| IMSI | M | A | | +| Network Access Mode | C | A | | +| International MS ISDN number | M | A | | +| LMSI allocated by VLR | C | B | | +| LMSI allocated by GLR | C | B | | +| Mobile Station Category | M | A | | +| LMU Identifier | C | A | | +| VLR number | M | B | | +| MSC number | M | B | | +| HLR number | C | B | | +| Zone Code List | C | A | | +| Roaming restriction due to unsupported feature | C | A | | +| MSC area restricted flag | M | C | | +| LSA Identity | C | A | | +| LSA Priority | C | A | | +| LSA Only Access Indicator | C | A | | +| LSA Active Mode Indicator | C | A | | +| Provision of bearer service | M | A | | +| Provision of teleservice | M | A | | +| BC allocation | C | A | | +| Subscriber status | C | A | | +| Barring of outgoing calls | C | A | | +| Barring of premium rate calls | C | A | | +| Barring of supplementary service management | C | A | | +| Barring of invocation of call transfer | C | A | | +| Mobile Station Not Reachable Flag | M | C | | +| VGCS Group Membership List | C | A | | +| VBS Group Membership List | C | A | | +| Broadcast Call Initiation Allowed List | C | A | | +| Originating CAMEL Subscription Information | C | A | | +| SS invocation notification (SS-CSI) | C | A | | +| CCBS Monitoring Flag | C | C | | +| Location and Subscriber information Confirmed by HLR indicator | M | C | | +| CAMEL Supported phases information | C | C | | +| Service Substitution Induced Flag list | C | E | | +| Forwarding information List | C | A | | +| Call barring information List | C | A | | +| CUG information List | C | A | | +| SS-Data List | C | A | | +| EMLPP Subscription | C | A | | +| North American Equal Access preferred Carrier Id List | C | A | | +| Privacy Exception List | C | A | | +| Home GMLC Numbers | C | A | | +| IST Alert Timer | C | A | | +| Age indicator for CS | C | D | | +| Packet Specific Data | | | | +| SGSN number | M | B | | +| Roaming Restriction in the SGSN due to unsupported feature | M | A | | +| SGSN area restricted flag | M | C | | +| MNRG | M | C | | +| PDP Type | C | A | | +| PDP Address | C | A | | +| SGSN address | M | B | | +| Access Point Name | C | A | | +| VPLMN Address Allowed | C | A | | +| Quality of Service Subscribed | C | A | | +| Age indicator for PS | C | D | | + +(\*1) A: Information for HLR emulation. + +B: Information for address and identity conversion. + +C: Information for Location updating Screening. + +D: Information for support of Super-Charger functionality. + +E: Others. + +# Annex A (informative): Change history + +| Document history | | | +|-------------------------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| V0.1.0 | Aug 1999 | The first draft. | +| V0.2.0 | Sep 1999 | Addition of section 7.10 and some editorial corrections. | +| V0.3.0 | Oct 1999 | Addition of section 7.5.2, modification of section 7.2.1.3 and section 7.2.2, and, some editorial corrections. | +| V0.4.0 | Nov 1999 | Moved, modified and merged Purge MS descriptions from section 7.3.1.3 and 7.3.3 to section 7.4. Deleted section 7.10 Location Service and remove LCS related data from table 8.5/1. Corrected some editing errors. | +| V0.5.0 | Nov 1999 | Modified section 2 References. Deleted one sentence from section 4. Corrected minor editing errors in section 5.3 and section 8.5. Restored section 7.11 Location Services and LCS related data to table 8.5/1. | +| V1.0.0 | Feb 2000 | Agreed by CN2B, Milan | +| V2.0.0 | Mar 2000 | Submitted for approval to TSG CN#07 | +| V3.0.0 | March 2000 | Approved by CN#07 | +| V4.0.0 | March 2001 | Release 4 after CN#11 | +| V5.0.0 | June 2002 | Release 5 after CN#16 | +| V6.0.0 | Dec 2004 | Release 6 after CN#26 | +| V7.0.0 | June 2007 | Upgraded unchanged from Rel-6 after CT#36 | +| V8.0.0 | Dec 2008 | Upgraded unchanged from Rel-7 after CT#42 | +| V9.0.0 | Dec 2009 | Update to Rel-9 version (MCC) | +| V10.0.0 | Mar 2011 | Update to Rel-10 version (MCC) | +| V11.0.0 | Sep 2012 | Update to Rel-11 version (MCC) | +| V12.0.0 | Sep 2014 | Update to Rel-12 version (MCC) | +| V13.0.0 | Dec 2015 | Update to Rel-13 version (MCC) | +| V14.0.0 | Mar 2017 | Update to Rel-14 version (MCC) | +| V15.0.0 | Jun 2018 | Update to Rel-15 version (MCC) | +| V16.0.0 | July 2020 | Update to Rel-16 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23142/21c78ed8eb23eb76d4a2c9edbe5626bb_img.jpg b/marked/Rel-16/23_series/23142/21c78ed8eb23eb76d4a2c9edbe5626bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7babcfd1ddbee816695005095f34478f5b65e79f --- /dev/null +++ b/marked/Rel-16/23_series/23142/21c78ed8eb23eb76d4a2c9edbe5626bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:413ea6a7c35e5ea782b38e647d101b8f5211160eaabff6285c4364709c5f706d +size 45132 diff --git a/marked/Rel-16/23_series/23142/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23142/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf523d93ab07fc0b40a602104427b3ff59158361 --- /dev/null +++ b/marked/Rel-16/23_series/23142/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:043268dc5f1ed4dd338d95c04c93a3a0a563e46dd37535f14f308bf3f2a35b6c +size 88747 diff --git a/marked/Rel-16/23_series/23142/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/Rel-16/23_series/23142/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bd91bee40a823d80e8f1fd5f031c4f24b0311aa --- /dev/null +++ b/marked/Rel-16/23_series/23142/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0838377ebf8fc7ba3bc86c19aa8fb2dde3e75bef9135829926ac717ec318a1e +size 92418 diff --git a/marked/Rel-16/23_series/23142/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23142/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e933485e0fad0a4b011e1fb4cf1cd77293e4e01 --- /dev/null +++ b/marked/Rel-16/23_series/23142/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5dea67639cfd19ac1c52cba984ce30ab1bfe01102de9f0451679f477b5204a5 +size 138758 diff --git a/marked/Rel-16/23_series/23142/5a24ac755b962fd5f0183f13de0726de_img.jpg b/marked/Rel-16/23_series/23142/5a24ac755b962fd5f0183f13de0726de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9394bc8ee0052c410343df83a5b6bd962fd805c3 --- /dev/null +++ b/marked/Rel-16/23_series/23142/5a24ac755b962fd5f0183f13de0726de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a90c2152565a0c899f07571fed4fec199c2e57b2644d4a0d3881fb6d77ca9825 +size 48913 diff --git a/marked/Rel-16/23_series/23142/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/marked/Rel-16/23_series/23142/73dff6b45b2b9ffd384bab3235f869af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e857415de22c3dfbc7c553703ef20bf4718fc863 --- /dev/null +++ b/marked/Rel-16/23_series/23142/73dff6b45b2b9ffd384bab3235f869af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a32a68bf1fd56e9107f0fe15bc72e18669b31d1eb51b1c7e6e45511a52fc5b42 +size 96773 diff --git a/marked/Rel-16/23_series/23142/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/Rel-16/23_series/23142/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e148a462e274ad92b7b53c8ec6806105767b561 --- /dev/null +++ b/marked/Rel-16/23_series/23142/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57a278d4d275eb6406c33ac85c93f54c5b3f2a66d74733e7a69976d1029cd16e +size 91878 diff --git a/marked/Rel-16/23_series/23142/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/23_series/23142/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..adcf5f2aeba9a6c325657eec1895e29c197cce55 --- /dev/null +++ b/marked/Rel-16/23_series/23142/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29d685ef0ae006e8dc94d544d345946e4bef1340fd3efcd9b8db9d94d80afc71 +size 67771 diff --git a/marked/Rel-16/23_series/23142/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23142/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd0d475dbbbaecb3152ed22ac75d4b1eb23ce6aa --- /dev/null +++ b/marked/Rel-16/23_series/23142/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22f7625598d55515a77f8d1e54e946322a36d366750ab814cf0d9b0a8997d791 +size 98806 diff --git a/marked/Rel-16/23_series/23142/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23142/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d01975c1c68102faa06c1dd124311c0fd7fc41e1 --- /dev/null +++ b/marked/Rel-16/23_series/23142/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89fcffdd08c499c6c7dfd6ef4b27ff8772a88a17015c34c3f622c33e052c64c6 +size 117451 diff --git a/marked/Rel-16/23_series/23142/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23142/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84ce7e77fb2d6620c097f34cbcd7b112145a383d --- /dev/null +++ b/marked/Rel-16/23_series/23142/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98b8676a83dd23665e2fd2a94612d0d38aa67ee3a1c14efccc8b8f36818d3adb +size 103255 diff --git a/marked/Rel-16/23_series/23142/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/Rel-16/23_series/23142/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c1ebce8720448b7e6ad9d43e1453ca3be55bf9e --- /dev/null +++ b/marked/Rel-16/23_series/23142/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4f53e7f1d4d8fac7c3c26990709708840d5b425b651c104fd369557375b0cce +size 102873 diff --git a/marked/Rel-16/23_series/23142/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23142/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8d3dab3f782fdc15dadec581344a4fa60aec1d6 --- /dev/null +++ b/marked/Rel-16/23_series/23142/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6fffaba82e7ccbee6f7ca6c9f27a61f658078a2340b9c899c69da6fe37cc5d7 +size 108324 diff --git a/marked/Rel-16/23_series/23142/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Rel-16/23_series/23142/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7f0a6519f13666cd4f1116a48605a3fdd1d7344 --- /dev/null +++ b/marked/Rel-16/23_series/23142/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ecce0bb44d333d4feef32453023d9147ff7bf7944763da38f5d789d16cd2839 +size 85532 diff --git a/marked/Rel-16/23_series/23142/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-16/23_series/23142/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7215c0bba1d16b9920dc63fcc03728da65b4412 --- /dev/null +++ b/marked/Rel-16/23_series/23142/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c36b2019e3279e6de093bd6d47181cdc5bf2485a269f6b60961cc559095acfb +size 78126 diff --git a/marked/Rel-16/23_series/23142/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23142/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a6e41ae755c2e3bf13d636fd6fb9cab5d67ad55 --- /dev/null +++ b/marked/Rel-16/23_series/23142/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d545f067e11311382fa32bacd8479d3715eef1a5447f98387fc04e5b8706ad97 +size 126222 diff --git a/marked/Rel-16/23_series/23142/raw.md b/marked/Rel-16/23_series/23142/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..964474a1fdd97781d3724d4884de3f13c888d663 --- /dev/null +++ b/marked/Rel-16/23_series/23142/raw.md @@ -0,0 +1,1023 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions..... | 5 | +| 3.1 Definitions..... | 5 | +| 4 VAS-SMS service requirements ..... | 6 | +| 4.1 General description of VAS-SMS service requirements..... | 6 | +| 4.2 Operational requirements ..... | 7 | +| 4.2.1 VAS-SMS Provision/withdrawal ..... | 7 | +| 4.2.1.1 General..... | 7 | +| 4.2.1.2 Requirements on the originating network side ..... | 7 | +| 4.2.1.3 Requirements on the terminating network side ..... | 7 | +| 5 Architecture and Interface..... | 7 | +| 5.1 Architectural requirements ..... | 7 | +| 5.2 Reference model..... | 7 | +| 5.2.1 Logical network architecture ..... | 7 | +| 5.2.2 Functional entities ..... | 8 | +| 5.2.2.1 VAS AS (VAS SMS Application Server) ..... | 8 | +| 5.2.2.2 SMS node..... | 8 | +| 5.2.2.3 Service Portal Function (SPF) ..... | 8 | +| 5.2.2.4 Billing and Charging Function (BCF) ..... | 8 | +| 5.2.3 Interfaces ..... | 8 | +| 6 VAS-SMS service provisioning, activation & deactivation, configuration..... | 9 | +| 6.1 Activation/deactivation..... | 9 | +| 6.2 Configuration..... | 9 | +| 7 VAS-SMS signalling procedure..... | 10 | +| 7.0 General Signalling Procedure..... | 10 | +| 7.0.1 Originating Signalling flows ..... | 10 | +| 7.0.2 Terminating signalling flows..... | 12 | +| 7.1 Short Message forwarding ..... | 14 | +| 7.2 Short Message forwarding multiple subscriptions ..... | 15 | +| 7.3 Short Message filtering ..... | 17 | +| 7.4 Short Message receipt ..... | 18 | +| 7.5 Short Message network storage..... | 20 | +| 7.6 Short Message to multiple destinations..... | 22 | +| 7.7 Short Message Virtual Private Network (VPN)..... | 23 | +| 7.8 Short Message auto reply ..... | 23 | +| 7.9 Short Message personal signature..... | 25 | +| 7.10 Short Message deferred delivery..... | 25 | +| 8 Interaction with other features ..... | 25 | +| 8.1 Interaction with barring services..... | 25 | +| 8.2 Interaction with multiple Short Message transfer ..... | 25 | +| 8.3 Interaction with SMS COMPRESSION ..... | 25 | +| 8.4 Interaction with Enhanced Messaging Service ..... | 25 | +| 8.5 Interaction with SM delivery report ..... | 26 | +| 8.6 Interaction with charging ..... | 26 | +| 8.7 Interaction between VAS-SMS services..... | 26 | +| 9 Interworking with other networks..... | 26 | +| Annex A: Change history ..... | 27 | + +# --- Foreword + +This Technical Specification has been produced by the 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. + +# --- 1 Scope + +The present document describes the stage 2 of the VAS4SMS (Value Added Service for SMS). It includes: + +- The logic architecture; +- The logic elements functionality; +- The signaling flows; +- The interaction with other features. + +The service requirements of VAS4SMS are specified in 3GPP TS 22.142 [2]. + +The functionality and mechanism of SMS Service is defined in 3GPP TS 23.040 [4]. + +# --- 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.142: "Value Added Services (VAS) for Short Message Service (SMS) requirements ". +- [3] 3GPP TS 22.041: "Operator Determined Barring (ODB)". +- [4] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)". +- [5] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access". + +# --- 3 Definitions + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [x] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [x]. + +**Loop prevention indication:** a indication set by VAS AS which indicates that a VAS service has been applied to generate this new message, e.g. message receipt, auto reply or message forwarding service. This indication is used by recipients VAS AS to check before also generating a new message to prevent loops. + +**Message transfer:** this term is used for SM transfer between MS and SMS Node. + +**Delivery report:** this term is used to deliver the status report of original SM between MS and SMS Node.. + +**VAS check:** this term is used for the SMS Node to inquire the VAS AS if the VAS of user has activated. + +**VAS check response:** this term is used for the VAS AS to reply the result of VAS check. + +**Submit short message:** this term is used for the VAS AS to submit a new message to the SMS Node. + +**Submit short message response:** this term is used for the SMS Node to acknowledge the submit short message from the VAS AS. + +**VAS delivery report:** this term is used for the SMS Node to deliver status report of the short message from the VAS AS. + +**VAS submittal report:** this term is used for the VAS AS to submit a general status report of the short message which generated by the VAS AS based on VAS delivery report. + +**Relay short message:** this term is used to transfer the short message between SMS Nodes. + +**Delivery status notification:** this term is used to deliver VAS submittal report between SMS Nodes. + +NOTE: Relay short message and Delivery status notification are functionally equivalent to Message transfer and Delivery report respectively. Different naming is used to allow different mapping in stage 3 protocols + +# --- 4 VAS-SMS service requirements + +## 4.1 General description of VAS-SMS service requirements + +As defined in 3GPP TS 22.142[2], the VAS4SMS is an operator specific service by which an operator enables the subscriber to experience some value-added service features for SMS. + +VAS4SMS features that were defined in stage 1 include: + +- 1) Short Message Forwarding +- 2) Short Message Forwarding Multiple Subscriptions +- 3) Short Message Filtering +- 4) Short Message Receipt +- 5) Short Message Network Storage +- 6) Short Message to Multiple Destinations +- 7) Short Message Virtual Private Network (VPN) +- 8) Short Message Auto Reply +- 9) Short Message Personal Signature +- 10) Short Message Deferred Delivery + +VAS4SMS should not negatively affect the normal SMS communication between calling and called parties. + +The service subscriber is able to subscribe to the VAS4SMS service, activate (or de-activate) the service, and update the settings, e.g., to change by configure the personalized service related information. The personalized service information can consist of message signature, the forwarding destination address and message contents for auto reply, etc. + +The VAS4SMS subscriber is able to refine the VAS4SMS behaviour with configured rules, e.g. time, the identity of the calling party, the SMS forwarding service is able to act according to the rules. + +VAS4SMS is either a terminating network or originating network service. That is, VAS4SMS can be used by the calling and called subscribers. + +In general, services offered by the sender's VAS4SMS occur prior to the SMS delivering to the recipient's operation. + +## 4.2 Operational requirements + +### 4.2.1 VAS-SMS Provision/withdrawal + +#### 4.2.1.1 General + +The VAS4SMS may be provided after prior arrangement with the service provider. + +The VAS4SMS may be provided/withdrawn upon the subscriber's request or for administrative reasons. + +#### 4.2.1.2 Requirements on the originating network side + +A VAS4SMS application server in the originating network is required to be under the control of the SMS-SC that is serving a calling subscriber who has activated VAS4SMS. + +#### 4.2.1.3 Requirements on the terminating network side + +A VAS4SMS application server in the terminating network is required to be under the control of the SMS-Route that is serving a called subscriber who has activated VAS4SMS. + +# 5 Architecture and Interface + +## 5.1 Architectural requirements + +The network architecture defined for VAS SMS should have less impact on pre-Rel 8 realization of short message service. The VAS SMS solution shall be able to be deployed independently of the pre-Rel 8 services. VAS SMS shall not break pre-Rel 8 services. + +## 5.2 Reference model + +### 5.2.1 Logical network architecture + +![Figure 5.2.1.1 Logical network architecture for VAS4SMS. The diagram shows two PLMNs, PLMN A and PLMN B, separated by a dashed vertical line. In PLMN A, a VAS AS is connected to an SPF and a BCF via Rf-d and Rf-c interfaces respectively. The VAS AS is also connected to an SMS Node via an Rf-a interface. The SMS Node is connected to an MS A and an HLR/HSS/UDM. In PLMN B, a similar VAS AS is connected to an SPF and a BCF via Rf-d and Rf-c interfaces. The VAS AS is connected to an SMS Node via an Rf-a interface. The SMS Node is connected to an MS B and the HLR/HSS/UDM. The HLR/HSS/UDM is connected to both SMS Nodes via an Rf-b interface. The Rf-a interface is a double-headed arrow, while the Rf-b interface is a single-headed arrow pointing from the HLR/HSS/UDM towards the SMS Nodes.](21c78ed8eb23eb76d4a2c9edbe5626bb_img.jpg) + +Figure 5.2.1.1 Logical network architecture for VAS4SMS. The diagram shows two PLMNs, PLMN A and PLMN B, separated by a dashed vertical line. In PLMN A, a VAS AS is connected to an SPF and a BCF via Rf-d and Rf-c interfaces respectively. The VAS AS is also connected to an SMS Node via an Rf-a interface. The SMS Node is connected to an MS A and an HLR/HSS/UDM. In PLMN B, a similar VAS AS is connected to an SPF and a BCF via Rf-d and Rf-c interfaces. The VAS AS is connected to an SMS Node via an Rf-a interface. The SMS Node is connected to an MS B and the HLR/HSS/UDM. The HLR/HSS/UDM is connected to both SMS Nodes via an Rf-b interface. The Rf-a interface is a double-headed arrow, while the Rf-b interface is a single-headed arrow pointing from the HLR/HSS/UDM towards the SMS Nodes. + +**Figure 5.2.1.1 Logical network architecture for VAS4SMS** + +NOTE: Other SMS related elements (MSC/SGSN etc.) behavior is according to 3GPP TS 23.040[4]. + +### 5.2.2 Functional entities + +The main functional entities involved in the VAS SMS services provisioning depicted in figure 5.2.1.1 are described as follows. + +#### 5.2.2.1 VAS AS (VAS SMS Application Server) + +The VAS AS is an entity in user's HPLMN of which the main requirement with respect to handling of the VAS4SMS messages is the necessary service logic handling. + +The VAS AS informs the SMS Node whether or not it takes over the handling of a short message. The VAS AS will use a SMS Node for delivery of new or modified messages. + +The VAS AS informs the SMS Node about the outcome of its short message handling. + +VAS AS may receive the delivery report of the VAS4SMS messages generated by it from SMS Node + +If the delivery of SMS is failed, VAS AS may re-send/resubmit the VAS4SMS messages for several times, subject to operator's configuration + +#### 5.2.2.2 SMS node + +SMS Node may be the integration of standard SMS Functional elements defined in 3GPP TS 23.040[4] depending on HPLMN (MO or MT): SMS-IWMSC, SMS-GMSC, SMS-SC or SMS Router. + +Besides standard SMS functionalities described in TS 23.040 [4] the SMS Node may support: + +- storage of the user subscription indication for the VAS4SMS +- triggering a short message to VAS AS, if a user has VAS4SMS subscription +- receiving a short message from VAS AS which is generated based on a previously triggered short message +- submitting a short message which comes from VAS AS to the PLMN +- receiving a report from PLMN and forwarding it to VAS AS +- receiving a report from VAS AS + +In case the communication between the SMS Node and VAS AS fails, the SMS Node proceeds as if the user hasn't subscribed the VAS4SMS. + +#### 5.2.2.3 Service Portal Function (SPF) + +The SPF provides the means to VAS SMS subscription, activation & deactivation, configuration. The detailed information for these operations is described in section 6. After a user subscribing a VAS4SMS, the portal should support the capability to synchronize the user setting information to VAS AS. + +#### 5.2.2.4 Billing and Charging Function (BCF) + +BCF plays the role of receiving the call detail record (CDR) information from the VAS AS. + +The other function entities in figure 5.2.1.1 shall follow 3GPP TS 23.040[4], which is outside the scope of this specification. + +### 5.2.3 Interfaces + +As illustrated in figure 5.2.1.1, following interfaces are defined: + +- **Rf-a:** Rf-a is the interface between VAS AS and SMS Node. The VAS AS shall be able to influence and impact the SMS procedure on behalf of the services and it uses Rf-a interface to communicate with SMS Node. The SMS Node shall decide whether the information related to an incoming SMS is needed to send to the VAS AS and VAS AS shall make the SMS Node aware of any resulting activity. Rf-a shall also support to transfer the delivery result between VAS AS and SMS Node. +- **Rf-b:** Rf-b is the interface between two SMS Nodes. The Rf-b interface is used for message transferring between two PLMNs. +- **Rf-c:** Rf-c is the interface between VAS AS and Charging and Billing Function (BCF). The Rf-c is used for the VAS AS to transfer the CDR information to the BCF. + +- **Rf-d:** Rf-d is the interface between VAS AS and Service Portal Function (SPF). Rf-d is used to synchronize the user setting and subscription information from SPF to VAS AS + +# 6 VAS-SMS service provisioning, activation & deactivation, configuration + +## 6.1 Activation/deactivation + +The VAS-SMS service is activated at provisioning and deactivated at withdrawal. + +A subscriber can subscribe all the VAS-SMS service features as a whole or make the subscription to every feature separately, which is subject to operator's policy. When a VAS-SMS service is activated, a subscriber can specify some configuration for each subscribed service feature, such as the destination address which short messages shall be forwarded to. + +After a subscriber has activated their VAS-SMS service, all short messages related to him shall be handled according to his service configuration. + +## 6.2 Configuration + +Different methods may be provided for configuration of VAS-SMS service, e.g. such as short message, IVR and etc. It is out of the scope of this document to specify the configuration procedure itself. + +# 7 VAS-SMS signalling procedure + +## 7.0 General Signalling Procedure + +### 7.0.1 Originating Signalling flows + +![Sequence diagram showing the general short message submittal procedure without active originating VAS. The diagram involves three entities: MS (Mobile Station), SMS Node A, and VAS AS (VAS Application Server). The sequence of messages is: 1. MS sends a 'Message transfer' to SMS Node A. 2. SMS Node A sends a 'VAS check (originating VAS checking)' to VAS AS. 3. VAS AS responds with a 'VAS check response (no active originating VAS)' to SMS Node A. 4. SMS Node A then sends a 'Relay short message' to VAS AS. 5. VAS AS sends a 'Delivery report' back to SMS Node A. 6. Finally, SMS Node A sends a 'Status report' back to the MS via a dashed line.](5a24ac755b962fd5f0183f13de0726de_img.jpg) + +``` +sequenceDiagram + participant MS + participant SMS Node A + participant VAS AS + Note left of MS: MS successfully sends the short message to the SMS Node A via the originating user's serving node (e.g. MSC, SGSN, MME, SMSF, AMF). See 3GPP TS 23.040 [4] for details. + MS->>SMS Node A: 1. Message transfer + SMS Node A->>VAS AS: 2. VAS check (originating VAS checking) + VAS AS-->>SMS Node A: 3. VAS check response (no active originating VAS) + SMS Node A->>VAS AS: 4. Relay short message + VAS AS-->>SMS Node A: 5. Delivery report + SMS Node A-->>MS: 6. Status report +``` + +Sequence diagram showing the general short message submittal procedure without active originating VAS. The diagram involves three entities: MS (Mobile Station), SMS Node A, and VAS AS (VAS Application Server). The sequence of messages is: 1. MS sends a 'Message transfer' to SMS Node A. 2. SMS Node A sends a 'VAS check (originating VAS checking)' to VAS AS. 3. VAS AS responds with a 'VAS check response (no active originating VAS)' to SMS Node A. 4. SMS Node A then sends a 'Relay short message' to VAS AS. 5. VAS AS sends a 'Delivery report' back to SMS Node A. 6. Finally, SMS Node A sends a 'Status report' back to the MS via a dashed line. + +**Figure 7.0.1-1 General Short Message submittal procedures without active originating VAS** + +1. MS successfully sends the short message to the SMS Node A via the originating user's serving node (e.g. MSC, SGSN, MME, SMSF, AMF). See 3GPP TS 23.040 [4] for details. + +2. After checking that the originating user has subscribed VAS, the SMS Node A interacts with the VAS AS to interrogate whether the VAS of the originating user is active by sending an inquiring message including the message content received in step 1. In that case the SMS Node shall save the original short message. + +3. The VAS AS indicates to the SMS Node A that there is no active originating VAS for the originating user. + +4. The SMS Node A transfers the original short message to the termination side. +5. The termination side responds the delivery report to SMS Node A to notify that the short message has been delivered successfully. In this case the SMS Node A deletes the original short message which was saved in step 2. +6. The SMS Node A send the status report to the MS, which is optional depending on user's request. + +![Sequence diagram illustrating the General Short Message submittal procedures with active originating VAS. The diagram shows interactions between MS, SMS Node A, and VAS AS.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +``` + +sequenceDiagram + participant MS + participant SMS Node A + participant VAS AS + Note right of VAS AS: Termination side + MS->>SMS Node A: 1. Message transfer + SMS Node A->>VAS AS: 2. VAS check (originating VAS checking) + VAS AS-->>SMS Node A: 3. VAS check response (active originating VAS) + SMS Node A->>VAS AS: 4. Submit short message + VAS AS-->>SMS Node A: 5. Submit short message response + SMS Node A->>Termination side: 6. Relay short message + Termination side-->>SMS Node A: 7. Delivery status notification + SMS Node A->>VAS AS: 8. VAS delivery report + VAS AS-->>SMS Node A: 9. VAS submittal report (general) + SMS Node A-->>MS: 10. Status report + +``` + +Sequence diagram illustrating the General Short Message submittal procedures with active originating VAS. The diagram shows interactions between MS, SMS Node A, and VAS AS. + +**Figure 7.0.1-2 General Short Message submittal procedures with active originating VAS** + +1. MS successfully sends the short message to the SMS Node A via the originating user's serving node (e.g. MSC, SGSN, MME, AMF, SMF). See 3GPP TS 23.040 [4] for details. + 2. After checking that the originating user has subscribed VAS, the SMS Node A interacts with the VAS AS to interrogate whether originating VAS is active by sending an inquiring message including the message content received in step 1. In that case the SMS Node A shall save the original short message. + 3. The VAS AS indicates to the SMS Node A that originating VAS is active. + 4. The VAS AS performs originating VAS for the original user and generates a new short message by modifying the message content if necessary and submits the new short message to SMS Node A for transferring. +- NOTE: It is assumed that after this step VAS AS A has executed the service logic for all originating services. +5. The SMS Node A sends a Submit short message response message to the Originating VAS AS. + 6. The SMS Node A shall not check for VAS services for messages that are submitted by a VAS AS. The SMS Node A successfully transfer the new short message to the termination side. + 7. The termination side sends the delivery status notification to SMS Node A to notify the new short message has been delivered successfully. + 8. The SMS Node A transfers the delivery status notification as the VAS delivery report to the originating VAS AS. + 9. The originating VAS AS generates a general delivery report based on the report which received in step 8 and sends it to the SMS Node A. The SMS Node removes the original short message which was saved in step 2 when it receives the VAS submittal report from the VAS AS. + +10. The SMS Node A delivers the status report to originating MS, which is optional depending on originating user's request. + +### 7.0.2 Terminating signalling flows + +![Sequence diagram showing the general short message delivery procedure without active terminating VAS. The diagram involves four lifelines: SMS Node A, SMS Node B, VAS AS B, and MS B. The sequence of messages is: 1. Relay short message from SMS Node A to SMS Node B; 2. A decision box at SMS Node B indicating it judges whether to interrogate the HLR; 3. VAS check (terminating VAS checking) from SMS Node B to VAS AS B; 4. VAS check response (no active terminating VAS) from VAS AS B to SMS Node B; 5. Message transfer from SMS Node B to MS B; 6. Delivery Report from MS B to SMS Node B; 7. Delivery status notification from SMS Node B to SMS Node A.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +``` +sequenceDiagram + participant SMS Node A + participant SMS Node B + participant VAS AS B + participant MS B + Note right of SMS Node B: 2. Depend on the deployment, SMS Node B judges whether should interrogate the called party HLR first before relay the short message + SMS Node A->>SMS Node B: 1. Relay short message + SMS Node B->>VAS AS B: 3. VAS check (terminating VAS checking) + VAS AS B-->>SMS Node B: 4. VAS check response (no active terminating VAS) + SMS Node B->>MS B: 5. Message transfer + MS B-->>SMS Node B: 6. Delivery Report + SMS Node B-->>SMS Node A: 7. Delivery status notification +``` + +Sequence diagram showing the general short message delivery procedure without active terminating VAS. The diagram involves four lifelines: SMS Node A, SMS Node B, VAS AS B, and MS B. The sequence of messages is: 1. Relay short message from SMS Node A to SMS Node B; 2. A decision box at SMS Node B indicating it judges whether to interrogate the HLR; 3. VAS check (terminating VAS checking) from SMS Node B to VAS AS B; 4. VAS check response (no active terminating VAS) from VAS AS B to SMS Node B; 5. Message transfer from SMS Node B to MS B; 6. Delivery Report from MS B to SMS Node B; 7. Delivery status notification from SMS Node B to SMS Node A. + +**Figure 7.0.2-1 General Short Message delivery procedures without active terminating VAS** + +1-2. SMS Node B receives the relayed short message from the originating side and responds by sending an acknowledge message. See 3GPP TS 23.040 [4] for details. + +3. After checking that the terminating user has subscribed VAS, the SMS Node B interacts with the VAS AS B to interrogate whether terminating VAS is active by sending an inquiring message including the short message content received in step 1. In that case the SMS Node B shall save the short message. + +4. The VAS AS B indicates to the SMS Node B that there is no active terminating VAS for the terminating user. + +5-6. The SMS Node B successfully transfers the short message to the terminating MS B and receives the Delivery Report message (see 3GPP TS 23.040 [4] for details). In this case the SMS Node B removes the short message which was saved in step 3. + +7. The SMS Node B notifies the originating side of the delivery status. + +![Sequence diagram showing General Short Message delivery procedures with active terminating VAS. Lifelines: SMS Node A, SMS Node B, VAS AS B, MS B. The process involves relaying a short message, VAS checking, message transfer, and delivery reports.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +sequenceDiagram + participant SMS Node A + participant SMS Node B + participant VAS AS B + participant MS B + + Note right of SMS Node B: 2. Depend on the deployment, SMS Node B judges whether should interrogate the called party HLR first before relay the short message + + SMS Node A->>SMS Node B: 1. Relay short message + SMS Node B->>VAS AS B: 3. VAS check (terminating VAS checking) + VAS AS B-->>SMS Node B: 4. VAS check response (active terminating VAS) + VAS AS B->>SMS Node B: 5. Submit short message + SMS Node B-->>VAS AS B: 6. Submit short message response + SMS Node B->>MS B: 7. Message transfer + MS B-->>SMS Node B: 8. Delivery Report + SMS Node B->>VAS AS B: 9. VAS delivery report + VAS AS B-->>SMS Node B: 10. VAS submittal report (terminating) + SMS Node B-->>SMS Node A: 11. Delivery status notification + +``` + +Sequence diagram showing General Short Message delivery procedures with active terminating VAS. Lifelines: SMS Node A, SMS Node B, VAS AS B, MS B. The process involves relaying a short message, VAS checking, message transfer, and delivery reports. + +**Figure 7.0.2-2 General Short Message delivery procedures with active terminating VAS** + +1-2. SMS Node B receives the relayed short message from the originating side and responds by sending an acknowledge message. See 3GPP TS 23.040 [4] for details. + +3. After checking that the terminating user has subscribed VAS, the SMS Node B interacts with the VAS AS B to interrogate whether terminating VAS is active by sending an inquiring message including the short message content received in step 1. In that case the SMS Node B shall save the short message. + +4. The VAS AS B indicates to the SMS Node B that there is active terminating VAS for the terminating user. + +5. The VAS AS B performs terminating VAS and generates a new short message by modifying the received short message content if necessary and submits the new short message to SMS Node B for transferring. + +NOTE 1: It is assumed that after this step VAS AS B has executed the service logic for all terminating services. + +6. The SMS Node B sends a response message to the VAS AS B. + +7-8. The SMS Node B shall not check for VAS services for messages that are submitted by a VAS AS B. The SMS Node B delivers the short message to the MS and receives the ACK messages (see 3GPP TS 23.040 [4] for details). + +9. The SMS Node B transfers the delivery report to the VAS AS B. + +10. The VAS AS B generates a delivery report of the short message for the originating user based on the report received in step 9 and sends to SMS Node B. + +11. The SMS Node B notifies the originating side of the delivery status. In that case the SMS Node B removes the short message which was saved in step 3. + +NOTE 2: Depending on the stage 3 protocol used, for VAS services where step 11 exceeds the allowed response time, a report of delivery status may be returned after step 4. This does not inform SMS Node A of the actual delivery outcome. Depending on the capabilities of the stage 3 protocol PLMN A may request a separate delivery report to be informed of the final delivery status. + +## 7.1 Short Message forwarding + +The short message forwarding shall be a service feature only active for terminating user. The signaling procedure in originating side network shall not be affected for whether the message forwarding is active or not. + +The figures in this section describe the following possible scenarios when short message forwarding is active: + +- a short message is forwarded to an address which is specified by terminating user other than called number. +- a short message is not forwarded subject to terminating user's configuration + +![Sequence diagram showing the terminating signaling flow for short message forwarding. The diagram involves five lifelines: SMS Node A, SMS Node B, VAS AS B, MS B, and MS C. The process starts with SMS Node A sending a 'Relay short message' to SMS Node B. SMS Node B then performs a decision based on deployment (interrogating HLR). Next, SMS Node B sends a 'VAS check (terminating VAS checking)' to VAS AS B, which responds with 'VAS check response (active terminating VAS)'. VAS AS B then performs message forwarding service logic and decides to forward the SM to MS C. SMS Node B sends a 'Submit short message' to VAS AS B, which responds with 'Submit short message response'. VAS AS B then performs 'Message transfer' to MS C, which sends a 'Delivery Report' back to VAS AS B. VAS AS B sends a 'VAS delivery report' to SMS Node B, which in turn sends a 'VAS sbmittal report (terminating)' back to VAS AS B. Finally, SMS Node B sends a 'Delivery status notification' back to SMS Node A.](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) + +``` + +sequenceDiagram + participant SMS Node A + participant SMS Node B + participant VAS AS B + participant MS B + participant MS C + + Note right of SMS Node B: 2. Depend on the deployment, SMS Node B judges whether should interrogate the called party HLR first before relay the short message + + SMS Node A->>SMS Node B: 1. Relay short message + SMS Node B->>VAS AS B: 3. VAS check (terminating VAS checking) + VAS AS B-->>SMS Node B: 4. VAS check response (active terminating VAS) + Note right of VAS AS B: 5. Perform message forwarding service logic and decide the SM shall be forwarded to MS C + SMS Node B->>VAS AS B: 6. Submit short message + VAS AS B-->>SMS Node B: 7. Submit short message response + VAS AS B->>MS C: 8. Message transfer + MS C-->>VAS AS B: 9. Delivery Report + VAS AS B->>SMS Node B: 10. VAS delivery report + SMS Node B-->>VAS AS B: 11. VAS sbmittal report (terminating) + SMS Node B-->>SMS Node A: 12. Delivery status notification + +``` + +Sequence diagram showing the terminating signaling flow for short message forwarding. The diagram involves five lifelines: SMS Node A, SMS Node B, VAS AS B, MS B, and MS C. The process starts with SMS Node A sending a 'Relay short message' to SMS Node B. SMS Node B then performs a decision based on deployment (interrogating HLR). Next, SMS Node B sends a 'VAS check (terminating VAS checking)' to VAS AS B, which responds with 'VAS check response (active terminating VAS)'. VAS AS B then performs message forwarding service logic and decides to forward the SM to MS C. SMS Node B sends a 'Submit short message' to VAS AS B, which responds with 'Submit short message response'. VAS AS B then performs 'Message transfer' to MS C, which sends a 'Delivery Report' back to VAS AS B. VAS AS B sends a 'VAS delivery report' to SMS Node B, which in turn sends a 'VAS sbmittal report (terminating)' back to VAS AS B. Finally, SMS Node B sends a 'Delivery status notification' back to SMS Node A. + +**Figure 7.1-1 Terminating signaling flow - Short Message is forwarded** + +NOTE1: The content of the VAS4SMS message in operation 5 is the same as the original SMS, only the destination address shall be changed to forwarded-to number. + +1-4. See general flow described in the previous chapter 7.0. The VAS AS B checks that a terminating user has activated short message network forwarding service and indicates to the SMS Node B there is terminating VAS active. + +5. According to user B's preferences, the VAS AS B decides the message needs to be forwarded to MS C. The VAS AS B takes a loop check for original SM. If there is a loop prevention indication set in the SM, the VAS AS B shall not apply short message forwarding service and do not go to following steps. + +6-10. The VAS AS B delivers the original short message to the MS C after including a loop prevention indication. + +11. The VAS AS B generates a report of the short message and sends it to SMS Node B. + +12. The SMS Node B notifies the originating side of the delivery status. + +![Sequence diagram showing terminating signaling flow where the short message is not forwarded. Lifelines: SMS Node A, SMS Node B, VAS AS B, MS B. The process involves relaying the message, VAS checking, deciding not to forward, submitting the message directly to the MS, and then reporting the delivery status back to the originating node.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant SMS Node A + participant SMS Node B + participant VAS AS B + participant MS B + Note right of SMS Node B: 2. Depend on the deployment, SMS Node B judges whether should interrogate the called party HLR first before relay the short message + SMS Node A->>SMS Node B: 1. Relay short message + SMS Node B->>VAS AS B: 3. VAS check (terminating VAS checking) + VAS AS B-->>SMS Node B: 4. VAS check response (active terminating VAS) + Note right of VAS AS B: 5. Perform message forwarding service logic and decide the destination not need to be changed + VAS AS B->>SMS Node B: 6. Submit short message + SMS Node B-->>VAS AS B: 7. Submit short message response + VAS AS B->>MS B: 8. Message transfer + MS B-->>VAS AS B: 9. Delivery Report + VAS AS B-->>SMS Node B: 10. VAS delivery report + SMS Node B-->>VAS AS B: 11. VAS submittal VAS report (terminating) + SMS Node B-->>SMS Node A: 12. Delivery status notification + +``` + +Sequence diagram showing terminating signaling flow where the short message is not forwarded. Lifelines: SMS Node A, SMS Node B, VAS AS B, MS B. The process involves relaying the message, VAS checking, deciding not to forward, submitting the message directly to the MS, and then reporting the delivery status back to the originating node. + +**Figure 7.1-2 Terminating signaling flow - Short Message is not forwarded** + +NOTE2: The VAS4SMS message in operation 5 is the same as the original SM. + +1-4. See general flow described in the previous chapter 7.0. The VAS AS B checks that a terminating user has activated short message forwarding service and indicates to the SMS Node B there is terminating VAS active. + +5. According to user B's preferences, the VAS AS B decides the message needs not to be forwarded. + +6-10. The VAS AS B delivers the original short message to the terminating user. See general flow described in the previous chapter 7.0. + +11. The VAS AS B generates a report of the short message and sends it to SMS Node B. + +12. The SMS Node B notifies the originating side of the delivery status. + +## 7.2 Short Message forwarding multiple subscriptions + +Short Message Forwarding Multiple Subscriptions is applicable for the terminating user. In this case, the VAS AS checks that the terminating user has activated the Short Message Forwarding Multiple Subscriptions service and shall send the original short message to multiple receivers based on the subscription information. The procedure of Short Message Forwarding Multiple Subscriptions described in the following figure 7.2-1. + +![Sequence diagram illustrating the Short Message forwarding to multiple subscriptions procedure. The diagram shows interactions between Receiving MS-1, Receiving MS-n, SMS Node A, SMS Node B, and VAS AS B. The process involves relaying a short message, performing VAS checks, submitting messages to multiple subscriptions, and returning delivery reports.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant MS1 as Receiving MS-1 + participant MSn as Receiving MS-n + participant SNA as SMS Node A + participant SNB as SMS Node B + participant VASB as VAS AS B + + Note right of VASB: 4. Perform SM forwarding to multiple subscriptions service + + SNA->>SNB: 1. Relay Short Message + SNB->>VASB: 2. VAS check (originating VAS checking) + VASB-->>SNB: 3. VAS check response (active originating VAS) + Note right of VASB: 4. Perform SM forwarding to multiple subscriptions service + VASB->>SNB: 5. Submit short message (MS-1) + SNB-->>VASB: 6. Submit short message response(MS-1) + Note right of SNB: ..... + VASB->>SNB: 7. Submit short message (MS-n) + SNB-->>VASB: 8. Submit short message response(MS-n) + SNB->>MS1: 9. Message transfer (MS-1) + Note right of SNB: ..... + SNB-->>VASB: 10. VAS delivery report (MS-1) + Note right of SNB: ..... + SNB->>MSn: 11. Message transfer (MS-n) + SNB-->>VASB: 12. VAS delivery report (MS-n) + VASB-->>SNB: 13. VAS submittal report (general) + SNB-->>SNA: 14. Delivery status notification + + Note left of MS1: + -->> : Message transfer + -->> : Successful message transfer including report + +``` + +Sequence diagram illustrating the Short Message forwarding to multiple subscriptions procedure. The diagram shows interactions between Receiving MS-1, Receiving MS-n, SMS Node A, SMS Node B, and VAS AS B. The process involves relaying a short message, performing VAS checks, submitting messages to multiple subscriptions, and returning delivery reports. + +**Figure 7.2-1 Short Message forwarding to multiple subscriptions procedure** + +1.-3. The short message is transferred from the originating user to terminating sides' SMS Node B. After checking out that the terminating user has subscribed VAS, the SMS Node B interacts with the VAS AS to interrogate whether the VAS of the terminating user is active by sending an inquiring message including the message content received in step 1. In that case the SMS Node shall save the original short message. + +4. The VAS AS performs the short message forwarding to multiple subscriptions service and generates new short messages based on the original short message for each subscription. + +5-6. The SMS Node B receives a short message to MS-1 and sends the Submit short message response to the VAS AS B. + +7-8. The SMS Node B receives a short message to MS-n and sends the Submit short message response to the VAS AS B. + +9-10. The SMS node B delivers the short message to MS-1 and relay the delivery report received from MS-1 to the VAS AS. These steps can happen at any time after step 6. + +11-12. The SMS node B delivers the short message to MS-n and relay the delivery report received from MS-n to the VAS AS. These steps can happen at any time after step 6. There is no sequence requirement of sending short message for SMS Node, i.e. the SMS Node can send the short message in parallel. + +13. The VAS AS generates a general delivery report based on all the delivery reports it receives and sends it to SMS Node B. + +14. The SMS Node B notifies the originating side of the delivery status. + +## 7.3 Short Message filtering + +The short message filtering shall be a service feature only active for terminating user. The signaling procedure in originating side network shall not be affected for whether the message filtering is active or not. + +The figures in this section describe the following possible scenarios when short message filtering is active: + +- a short message is filtered subject to terminating user's configuration, such as a terminating user would not like to receive the message coming from a certain user. +- a short message is not filtered subject to terminating user's configuration. + +![Sequence diagram showing the terminating signaling flow for a short message that is filtered. The diagram involves four lifelines: SMS Node A, SMS Node B, VAS AS B, and MS B. The flow starts with SMS Node A sending a 'Relay short message' to SMS Node B. SMS Node B then performs a local decision (step 2). Next, SMS Node B sends a 'VAS check (terminating VAS checking)' to VAS AS B. VAS AS B responds with 'VAS check response (active terminating VAS)'. VAS AS B then performs filtering logic (step 5) and sends a 'VAS submittal report (terminating)' to SMS Node B. Finally, SMS Node B sends a 'Delivery status notification' back to SMS Node A. A legend at the bottom indicates that a single-headed arrow represents 'Message transfer' and a double-headed arrow represents 'Successful message transfer including report'.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +``` + +sequenceDiagram + participant SMS Node A + participant SMS Node B + participant VAS AS B + participant MS B + + Note right of SMS Node B: 2. Depend on the deployment, SMS Node B judges whether should interrogate the called party HLR first before relay the short message + Note right of VAS AS B: 5. Perform the filtering service logic and decide the SM to MS B shall be filtered + + SMS Node A->>SMS Node B: 1. Relay short message + SMS Node B->>VAS AS B: 3. VAS check (terminating VAS checking) + VAS AS B-->>SMS Node B: 4. VAS check response (active terminating VAS) + VAS AS B-->>SMS Node B: 6. VAS submittal report (terminating) + SMS Node B-->>SMS Node A: 7. Delivery status notification + +``` + +Legend: + +- Message transfer +- ⇔ Successful message transfer including report + +Sequence diagram showing the terminating signaling flow for a short message that is filtered. The diagram involves four lifelines: SMS Node A, SMS Node B, VAS AS B, and MS B. The flow starts with SMS Node A sending a 'Relay short message' to SMS Node B. SMS Node B then performs a local decision (step 2). Next, SMS Node B sends a 'VAS check (terminating VAS checking)' to VAS AS B. VAS AS B responds with 'VAS check response (active terminating VAS)'. VAS AS B then performs filtering logic (step 5) and sends a 'VAS submittal report (terminating)' to SMS Node B. Finally, SMS Node B sends a 'Delivery status notification' back to SMS Node A. A legend at the bottom indicates that a single-headed arrow represents 'Message transfer' and a double-headed arrow represents 'Successful message transfer including report'. + +**Figure 7.3-1 Terminating signaling flow - Short Message is filtered** + +NOTE 1: In step 6, whether the delivery result is failure or success is subject to operator's configuration + +NOTE 2: Appropriate failure codes for the status notification have to be selected carefully to avoid the unnecessary retries. + +- 1-4. See general flow described in the previous chapter 7.0. The VAS AS B checks that a terminating user has activated short message filtering service and indicates to the SMS Node B there is terminating VAS active. +5. According to user B's preferences, the VAS AS B decides the message needs to be filtered. +6. The VAS AS B generates a report of the short message and sends it to SMS Node B. The delivery result in report is based on the configuration of user B or operator. +7. The SMS Node B notifies the originating side of the delivery status. + +![Sequence diagram showing the terminating signaling flow for a short message that is not filtered. The diagram involves four lifelines: SMS Node A, SMS Node B, VAS AS B, and MS B. The process starts with SMS Node A sending a 'Relay short message' to SMS Node B. SMS Node B then performs a decision (step 2) about whether to interrogate the HLR. Next, SMS Node B sends a 'VAS check (terminating VAS checking)' to VAS AS B, which responds with 'VAS check response (active terminating VAS)'. VAS AS B then performs filtering logic (step 5) and decides not to filter the message. SMS Node B then sends a 'Submit short message' to VAS AS B, which responds with 'Submit short message response'. VAS AS B then performs 'Message transfer' to MS B, receives a 'Delivery Report' from MS B, sends a 'VAS delivery report' to SMS Node B, and finally sends a 'VAS submittal report (terminating)' to SMS Node B. SMS Node B then sends a 'Delivery status notification' back to SMS Node A.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant SMS Node A + participant SMS Node B + participant VAS AS B + participant MS B + + Note right of SMS Node B: 2. Depend on the deployment, SMS Node B judges whether should interrogate the called party HLR first before relay the short message + + Note right of VAS AS B: 5. Perform the filtering service logic and decide the SM to MS B shall not be filtered + + SMS Node A->>SMS Node B: 1. Relay short message + SMS Node B->>VAS AS B: 3. VAS check (terminating VAS checking) + VAS AS B-->>SMS Node B: 4. VAS check response (active terminating VAS) + SMS Node B->>VAS AS B: 7. Submit short message + VAS AS B-->>SMS Node B: 8. Submit short message response + VAS AS B->>MS B: 9. Message transfer + MS B-->>VAS AS B: 10. Delivery Report + VAS AS B->>SMS Node B: 11. VAS delivery report + VAS AS B-->>SMS Node B: 12. VAS submittal report (terminating) + SMS Node B-->>SMS Node A: 13. Delivery status notification + +``` + +Sequence diagram showing the terminating signaling flow for a short message that is not filtered. The diagram involves four lifelines: SMS Node A, SMS Node B, VAS AS B, and MS B. The process starts with SMS Node A sending a 'Relay short message' to SMS Node B. SMS Node B then performs a decision (step 2) about whether to interrogate the HLR. Next, SMS Node B sends a 'VAS check (terminating VAS checking)' to VAS AS B, which responds with 'VAS check response (active terminating VAS)'. VAS AS B then performs filtering logic (step 5) and decides not to filter the message. SMS Node B then sends a 'Submit short message' to VAS AS B, which responds with 'Submit short message response'. VAS AS B then performs 'Message transfer' to MS B, receives a 'Delivery Report' from MS B, sends a 'VAS delivery report' to SMS Node B, and finally sends a 'VAS submittal report (terminating)' to SMS Node B. SMS Node B then sends a 'Delivery status notification' back to SMS Node A. + +**Figure 7.3-2 Terminating signaling flow - Short Message is not filtered** + +NOTE: The VAS4SMS message in step 5 is the same as the original SM. + +1-4. See general flow described in the previous chapter 7.0. The VAS AS B checks that a terminating user has activated short message filtering service and indicates to the SMS Node B there is terminating VAS active. + +5. According to user B's preferences, the VAS AS B decides the message needs not to be filtered. + +6-10. The VAS AS B delivers the original short message to the terminating user. See general flow described in the previous chapter 7.0. + +12. The VAS AS B generates a report of the short message and sends it to SMS Node B. + +13. The SMS Node B notifies the originating side of the delivery status. + +## 7.4 Short Message receipt + +Short Message Receipt is a terminating VAS. The procedure of the short message receipt refers to the general flow for VAS SMS described in the sub-clause 7.0.2. The VAS AS checks that the terminating user has activated the Short Message Receipt service and generates a new short message as the receipt of original message. + +![Sequence diagram of Short Message receipt procedure. Lifelines: SMS Node A, SMS Node B, VAS AS B, MS B. The process involves VAS checking, message transfer, receipt generation, and delivery status notification.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant SMS Node A + participant SMS Node B + participant VAS AS B + participant MS B + + Note right of SMS Node B: 2. Depend on the deployment, SMS Node B judges whether should interrogate the called party HLR first before relay the short message + + SMS Node A->>SMS Node B: 1. Relay short message + SMS Node B->>VAS AS B: 3. VAS check (terminating VAS checking) + VAS AS B-->>SMS Node B: 4. VAS check response (active terminating VAS) + Note right of VAS AS B: 5. Perform the short message receipt service logic including loop prevention check and decide a receipt is need + VAS AS B->>SMS Node B: 6. Submit short message (original SM) + SMS Node B-->>VAS AS B: 7. Submit short message response + VAS AS B->>MS B: 8. Message transfer + VAS AS B-->>SMS Node B: 9. VAS delivery report (original SM) + Note right of VAS AS B: 10. generate a receipt for original SM with loop prevention indication set + VAS AS B->>SMS Node B: 11. Submit short message (message receipt) + SMS Node B-->>VAS AS B: 12. Submit short message response + VAS AS B-->>SMS Node B: 14. VAS delivery report (message receipt) + VAS AS B-->>SMS Node B: 15. VAS submittal report (terminating) + SMS Node B-->>SMS Node A: 16. Delivery status notification + + Note left of SMS Node A: + Note left of SMS Node A: Message transfer + Note left of SMS Node A: Successful message transfer including report + +``` + +Sequence diagram of Short Message receipt procedure. Lifelines: SMS Node A, SMS Node B, VAS AS B, MS B. The process involves VAS checking, message transfer, receipt generation, and delivery status notification. + +**Figure 7.4-1 Short Message receipt procedure** + +1-4. See general flow described in the previous chapter 7.0. The VAS AS B checks that a terminating user has activated short message receipt service and indicates to the SMS Node B there is terminating VAS active. + +5. According to user B's preferences, the VAS AS B decides a message receipt is needed and shall be sent to user A. The VAS AS B takes a loop check for original SM. If there is a loop prevention indication set in the SM, the VAS AS B shall not apply short message receipt service and do not go to following steps. + +6-9. The VAS AS B delivers the original short message to the terminating user. See general flow described in the previous chapter 7.0. + +10. The VAS AS B generates a receipt short message, based on the report received in step 9 and terminating user's preferences. The receipt message shall include a loop prevention indication that indicating it is a message generated for message receipt service of user B. + +11-14. The VAS AS B delivers the message receipt to the originating user. See general flow described in the previous chapter 7.0. + +15. The VAS AS B generates a report of the short message and sends it to SMS Node B. + +16. The SMS Node B notifies the originating side of the delivery status. + +## 7.5 Short Message network storage + +The short message storage can be active to both originating and terminating user. + +![Sequence diagram showing the originating signaling flow for Short Message storage. The diagram involves three main entities: MS (Mobile Station), SMS Node A, and VAS AS (VAS Application Server). The sequence of messages is as follows: 1. MS sends 'Message transfer' to SMS Node A. 2. SMS Node A sends 'VAS check (originating VAS checking)' to VAS AS. 3. VAS AS sends 'VAS check response (active originating VAS)' back to SMS Node A. 4. VAS AS performs internal logic: 'Perform the message storage service logic and decide the SM shall be stored'. 5. VAS AS sends 'Submit short message' to SMS Node A. 6. SMS Node A sends 'Submit short message response' to VAS AS. 7. SMS Node A sends 'Relay short message' to the destination. 8. The destination sends 'Delivery status notification' to SMS Node A. 9. SMS Node A sends 'VAS delivery report' to VAS AS. 10. VAS AS performs internal logic: 'Store the SM and relevant information based on user's preference'. 11. VAS AS sends 'VAS submittal report (general)' to SMS Node A. 12. SMS Node A sends a dashed 'Status report' back to MS.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +``` + +sequenceDiagram + participant MS + participant SMS Node A + participant VAS AS + Note right of VAS AS: 4.Perform the message storage service logic and decide the SM shall be stored + Note right of VAS AS: 10. Store the SM and relevant information based on user's preference + MS->>SMS Node A: 1. Message transfer + SMS Node A->>VAS AS: 2. VAS check (originating VAS checking) + VAS AS-->>SMS Node A: 3. VAS check response (active originating VAS) + VAS AS->>SMS Node A: 5. Submit short message + SMS Node A-->>VAS AS: 6. Submit short message response + SMS Node A->>Destination: 7. Relay short message + Destination-->>SMS Node A: 8. Delivery status notification + SMS Node A->>VAS AS: 9. VAS delivery report + VAS AS->>SMS Node A: 11. VAS submittal report (general) + SMS Node A-->>MS: 12. Status report + +``` + +Sequence diagram showing the originating signaling flow for Short Message storage. The diagram involves three main entities: MS (Mobile Station), SMS Node A, and VAS AS (VAS Application Server). The sequence of messages is as follows: 1. MS sends 'Message transfer' to SMS Node A. 2. SMS Node A sends 'VAS check (originating VAS checking)' to VAS AS. 3. VAS AS sends 'VAS check response (active originating VAS)' back to SMS Node A. 4. VAS AS performs internal logic: 'Perform the message storage service logic and decide the SM shall be stored'. 5. VAS AS sends 'Submit short message' to SMS Node A. 6. SMS Node A sends 'Submit short message response' to VAS AS. 7. SMS Node A sends 'Relay short message' to the destination. 8. The destination sends 'Delivery status notification' to SMS Node A. 9. SMS Node A sends 'VAS delivery report' to VAS AS. 10. VAS AS performs internal logic: 'Store the SM and relevant information based on user's preference'. 11. VAS AS sends 'VAS submittal report (general)' to SMS Node A. 12. SMS Node A sends a dashed 'Status report' back to MS. + +**Figure 7.5-1 Originating signaling flow - Short Message storage** + +NOTE: The VAS4SMS message in operation 4 is the same as the original SM. + +1-3. See general flow described in the previous chapter 7.0. The VAS AS A checks that a originating user has activated short message network storage service and indicates to the SMS Node A there is originating VAS active. + +4. The VAS AS A decides that the original SMS shall be stored based on originating user's preferences. + +5-9. The VAS AS A delivers the original short message to the terminating user. See general flow described in the previous chapter 7.0. + +10. VAS AS A stores the original SMS and relevant information for originating user. + +11. The VAS AS A generates a delivery report for the original short message based on the report which received in step 9 and sends to SMS Node A. + +12. The SMS Node A sends the status report to UE, which is optional depending on user's request. + +![Sequence diagram illustrating the interaction between SMS Node A, SMS Node B, VAS AS B, and MS B for short message delivery and VAS processing.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +sequenceDiagram + participant SMS Node A + participant SMS Node B + participant VAS AS B + participant MS B + + SMS Node A->>SMS Node B: 1. Relay short message + Note over SMS Node B: 2. Depend on the deployment, SMS Node B judges whether should +interrogate the called party HLR first +before relay the short message + SMS Node B->>VAS AS B: 3. VAS check (terminating VAS checking) + VAS AS B-->>SMS Node B: 4. VAS check response (active terminating VAS) + Note over VAS AS B: 5. Perform the message storage +service logic and +decide the SM shall be stored + VAS AS B->>SMS Node B: 6. Submit short message + SMS Node B-->>VAS AS B: 7. Submit short message response + VAS AS B->>MS B: 8. Message transfer + VAS AS B->>SMS Node B: 9. VAS delivery report + Note over VAS AS B: 10. Store the SM and relevant +information based on user's +preference + VAS AS B-->>SMS Node B: 11. VAS submittal report (terminating) + SMS Node B->>SMS Node A: 12. Delivery status notification + +``` + +—> Message transfer +<——> Successful message transfer including report + +Sequence diagram illustrating the interaction between SMS Node A, SMS Node B, VAS AS B, and MS B for short message delivery and VAS processing. + +**Figure 7.5-2 Terminating signaling flow - Short Message storage** + +NOTE 1: The VAS4SMS message in operation 5 is the same as the original SM. + +NOTE 2: Depending on the stage 3 protocol used, for VAS services where step 12 exceeds the allowed response time, a report of delivery status may be returned after step 4. This does not inform SMS Node A of the actual delivery outcome. Depending on the capabilities of the stage 3 protocol PLMN A may request a separate delivery report to be informed of the final delivery status. + +1-4. See general flow described in the previous chapter 7.0. The VAS AS B checks that a terminating user has activated short message network storage service and indicates to the SMS Node B that the terminating VAS is active. + +5. The VAS AS B decides that the original SMS shall be stored based on terminating user's preferences. + +6-9. The VAS AS B delivers the original short message to the terminating user. See general flow described in the previous chapter 7.0. + +10. The VAS AS B stores the SMS and relevant information for terminating user. + +11. The VAS AS B generates a report of the short message and sends it to SMS Node B. + +12. The SMS Node B notifies the originating side of the delivery status. + +## 7.6 Short Message to multiple destinations + +In order to support short message to multiple destinations service it is needed for one user to establish a SMS group which is identified by a unique identifier in the VAS AS firstly. The SMS Group ID shall be allocated by VAS AS uniquely and be known by all the members of the SMS group. A SMS group also can be deleted by creator. There may be many ways to manage a SMS group, i.e. create or delete or query a SMS group which is out of the scope of this specification. + +When the SMS group is established, every group member can send the short message to all other members in this group by setting the destination to the unique identifier of the SMS group. The procedure of sending message to multiple destinations is described in the following figure 7.6-1. + +![Sequence diagram illustrating the Short Message to multiple destinations service procedure. The diagram shows interactions between Receiving MS-1, Receiving MS-n, Sending MS, SMS Node A, and VAS AS. The process involves message transfer, VAS checks, and individual message submissions to multiple recipients.](73dff6b45b2b9ffd384bab3235f869af_img.jpg) + +``` + +sequenceDiagram + participant Sending MS + participant SMS Node A + participant VAS AS + participant Receiving MS-1 + participant Receiving MS-n + + Note right of VAS AS: 4. Perform SM to multiple destinations VAS + + Sending MS->>SMS Node A: 1. Message transfer (SMS Group ID) + SMS Node A->>VAS AS: 2. VAS check (originating VAS checking) + VAS AS-->>SMS Node A: 3. VAS check response (active originating VAS) + VAS AS->>SMS Node A: 5. Submit short message (MS-1) + SMS Node A-->>VAS AS: 6. Submit short message response + SMS Node A->>Receiving MS-1: 7. Message transfer (MS-1) + Receiving MS-1->>SMS Node A: 8. Delivery report (MS-1) + SMS Node A->>VAS AS: 9. VAS delivery report (MS-1) + Note right of SMS Node A: ..... + SMS Node A->>VAS AS: 10. Submit short message (MS-n) + VAS AS-->>SMS Node A: 11. Submit short message response + SMS Node A->>Receiving MS-n: 12. Message transfer (MS-n) + Receiving MS-n->>SMS Node A: 13. Delivery report (MS-n) + SMS Node A->>VAS AS: 14. VAS delivery report (MS-n) + VAS AS->>SMS Node A: 15. VAS submittal report (general) + SMS Node A-->>Sending MS: 16. Status report + +``` + +Sequence diagram illustrating the Short Message to multiple destinations service procedure. The diagram shows interactions between Receiving MS-1, Receiving MS-n, Sending MS, SMS Node A, and VAS AS. The process involves message transfer, VAS checks, and individual message submissions to multiple recipients. + +**Figure 7.6-1 Short Message to multiple destinations service procedure** + +1.-3. These steps are identical to step 1 to 3 of the general message flow described in sub-clause 7.0. SMS Group ID shall be included in the short message and identified by recipient address. + +4. The VAS AS performs a short message to multiple destinations service and generates new short messages with the same content as the original short message. + +5.-14. The VAS AS separately submits the short message to the SMS Node A with different destination address. These destinations should be all other recipients within the SMS group. There is no sequence requirement of sending short message for VAS AS, i.e. the VAS AS can send the short message in parallel. The SMS Node A receives a delivery report from each receiving MS and relays it to the VAS AS. The VAS AS generates a general delivery report based on the results of the delivery reports from each recipient. + +15.-16. The general delivery report is sent from VAS AS to SMS Node A and transferred to the sending MS by SMS Node if possible. + +## 7.7 Short Message Virtual Private Network (VPN) + +The originating user and the terminating user are in the same VPN and support sending messages to local numbers in the VPN. The local number may be a short number which is bound to mobile number. The mapping table with local number to mobile number shall be stored in the VAS AS. The VAS AS receiving a checking message from SMS Node checks that the originating user activating VPN service, then replace local number by terminating user's mobile number. + +![Sequence diagram of Short Message Virtual Private Network (VPN) procedure](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +``` +sequenceDiagram + participant MS + participant SMS Node A + participant VAS AS + Note right of VAS AS: 4. Replace local number by its mobile number + MS->>SMS Node A: 1. Message transfer (Local number) + SMS Node A->>VAS AS: 2. VAS check (originating VAS checking) + VAS AS-->>SMS Node A: 3. VAS check response (active originating VAS) + Note right of VAS AS: 4. Replace local number by its mobile number + VAS AS->>SMS Node A: 5. Submit short message + SMS Node A-->>VAS AS: 6. Submit short message response + VAS AS->>SMS Node A: 7. Relay short message + SMS Node A-->>VAS AS: 8. Delivery status notification + VAS AS->>SMS Node A: 9. VAS delivery report + SMS Node A-->>VAS AS: 10. VAS submittal report (general) + SMS Node A-->>MS: 11. Status report +``` + +The diagram illustrates the interaction between three entities: MS (Mobile Station), SMS Node A, and VAS AS (Value Added Service Application Server). The sequence of messages is as follows: 1. MS sends a 'Message transfer (Local number)' to SMS Node A. 2. SMS Node A sends a 'VAS check (originating VAS checking)' to VAS AS. 3. VAS AS responds with 'VAS check response (active originating VAS)'. 4. A note indicates that the VAS AS 'Replaces local number by its mobile number'. 5. VAS AS sends 'Submit short message' to SMS Node A. 6. SMS Node A responds with 'Submit short message response'. 7. VAS AS sends 'Relay short message' to SMS Node A. 8. SMS Node A sends 'Delivery status notification' to VAS AS. 9. VAS AS sends 'VAS delivery report' to SMS Node A. 10. SMS Node A sends 'VAS submittal report (general)' to VAS AS. 11. SMS Node A sends a 'Status report' back to MS via a dashed line. + +Sequence diagram of Short Message Virtual Private Network (VPN) procedure + +Figure 7.7-1 Short Message Virtual Private Network procedure + +1. The SMS Node A receives a short message to local number from MS and need ask the VAS AS to check whether the originating user has activated VAS. +- 2.-3. The VAS AS checks that the originating user has activated VPN service and the destination is a local number. The VAS AS indicates the SMS Node there is active originating VAS for originating user. +4. The VAS AS replaces the local number by its mobile number and continues according to the general procedure described in sub-clause 7.0 step 4 and following. + +## 7.8 Short Message auto reply + +Short Message Auto Reply is a terminating VAS. The procedure of the short message auto reply refers to the general flow for VAS SMS described in the previous sub-clause 7.0. The VAS AS checks that the terminating user has activated the Short Message Auto Reply service and generates an auto reply short message which contents have been defined in advance, then deliver it to the originating user. + +![Sequence diagram illustrating the Short Message auto reply procedure. Lifelines: SMS Node A, SMS Node B, VAS AS B, and MS B. The process involves relaying a short message, checking for VAS, generating an auto-reply if applicable, and then delivering both the auto-reply and the original message with associated reports.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` + +sequenceDiagram + participant SMS Node A + participant SMS Node B + participant VAS AS B + participant MS B + + Note right of SMS Node B: 2. Depend on the deployment, SMS Node B judges whether should interrogate the called party HLR first before relay the short message + + SMS Node A->>SMS Node B: 1. Relay short message + SMS Node B->>VAS AS B: 3. VAS check (terminating VAS checking) + VAS AS B-->>SMS Node B: 4. VAS check response (active terminating VAS) + Note right of VAS AS B: 5. Generate auto reply short message + VAS AS B->>SMS Node B: 6. Submit short message (auto reply) + SMS Node B->>VAS AS B: 7. Submit short message response + VAS AS B->>SMS Node A: 8. Relay short message + SMS Node A->>SMS Node B: 9. Delivery report + VAS AS B->>SMS Node B: 10. VAS delivery report (auto reply) + VAS AS B->>SMS Node B: 11. Submit short message (original SM) + SMS Node B->>VAS AS B: 12. Submit short message response + VAS AS B->>MS B: 13. Message transfer + MS B->>VAS AS B: 14. Delivery report + VAS AS B->>SMS Node B: 15. VAS delivery report (original SM) + VAS AS B->>SMS Node B: 16. VAS submittal report (terminating) + SMS Node B->>SMS Node A: 17. Delivery status notification + +``` + +Sequence diagram illustrating the Short Message auto reply procedure. Lifelines: SMS Node A, SMS Node B, VAS AS B, and MS B. The process involves relaying a short message, checking for VAS, generating an auto-reply if applicable, and then delivering both the auto-reply and the original message with associated reports. + +**Figure 7.8-1 Short Message auto reply procedure** + +NOTE: There is no requirement of the sequence for which one of auto reply message or original SM should be sent firstly in the VAS AS, i.e. auto reply message can be sent before or after original SM. + +1.-4. See general flow described in the previous chapter 7.0. The VAS AS checks that a terminating user has activated short message auto reply service and indicates to the SMS Node B there is terminating VAS active. + +5. The VAS-AS B checks a loop prevention indication within the message. If the loop prevention indication is not set, then the VAS AS B generates an auto reply short message and set the loop prevention indication within the auto reply short message to indicate a spawned message. Otherwise an auto reply short message shall not be generated. The VAS AS B stores the original short message for next delivery. + +6.-7. The VAS AS B delivers a short message which is indicated as an auto reply message to the SMS Node B. + +8.-9. The auto reply short message is delivered to the originating user. See 3GPP TS 23.040[4] for details. + +10. The VAS AS B receives a delivery report for auto reply message delivery. + +11.-17. The VAS AS B continues to deliver the original short message to the terminating user. See general flow described in the previous chapter 7.0. + +## 7.9 Short Message personal signature + +Short Message Personal Signature service is applicable for the originating user. In this case, the VAS AS checks that the originating user has activated the Short Message Personal Signature service and shall append the user's personal signature to the short message. The Short Message Personal Signature procedure refers to the general procedure for VAS SMS which described in the previous chapter 7.0. + +Short message personal signature should be appended in the last concatenated message for a large message need to be separated into concatenated messages. + +## 7.10 Short Message deferred delivery + +Short Message Deferred Delivery service allows the user to set the short message delivery time. In this case the VAS AS checks that the originating user has activated the short message deferred delivery service. The VAS AS shall store the short message and set the timer to deferred delivery time. The short message should be sent when the timer times out. The deferred delivery time should be determined by the originating user. The service procedure refers to the general flow for VAS SMS which described in the previous chapter 7.0. + +NOTE 1: Short message deferred delivery time can be set in many ways by the originating user, e.g. via Ut interface. + +NOTE 2: Deferred delivery capability may be provide in SMS Node, however it is out of the scope of this specification. + +# --- 8 Interaction with other features + +## 8.1 Interaction with barring services + +Barring services described in 3GPP TS 23.040[4] are prior to VAS-SMS services. Any related VAS-SMS service to Operator Determined Barring (see 3GPP TS 22.041 [3]) is not applicable when Operator Determined Barring applies to the Short Message Service. For example, if an originating service for SMS is barred by ODB and a terminating service for SMS is not barred, all the related originating services for VAS-SMS service are also barred, but terminating services (e.g. SMS forwarding) for VAS-SMS are not impacted. + +## 8.2 Interaction with multiple Short Message transfer + +There is no direct conflict between the VAS-SMS service and the multiple short message transfer service described in 3GPP TS 23.040[4]. VAS-SMS services shall not impact the implementation of the multiple short message transfer service when the SMS-SC indicates to the SMS-GMSC that there are more messages to send for each message waiting in the service centre. + +## 8.3 Interaction with SMS COMPRESSION + +VAS-SMS services should be applicable for the SMS COMPRESSION described in 3GPP TS 23.040[4]. If the VAS-SMS service does not support SMS COMPRESSION (for example for VAS-SMS services that modify the content of a SM), then it shall guarantee the compressed SMS message delivery as normal. + +## 8.4 Interaction with Enhanced Messaging Service + +For the enhanced messaging service described in 3GPP TS 23.040[4], VAS-SMS services should be applicable. If the VAS-SMS service does not support the enhanced messaging service (for example for VAS-SMS services that modify the content of a SM), then it shall guarantee enhanced message delivery as normal. + +## 8.5 Interaction with SM delivery report + +If a Short Message Receipt service is applied the SMS Node shall not send SM delivery report message to the user. + +## 8.6 Interaction with charging + +VAS-SMS services are required to produce billing of extra fee (e.g. monthly based function fee). + +## 8.7 Interaction between VAS-SMS services + +VAS-SMS services should be classified by priority and triggered according to priority order based on operator's policy. + +# --- 9 Interworking with other networks + +The network architecture defined for VAS SMS is based on cellular networks. 3GPP TS 23.204 [5] specifies how to deliver SMS over generic 3GPP IP access. The theory of interworking with IP based network for VAS SMS is the same as normal SMS; refers to 3GPP TS 23.204 [5]. + +NOTE: Application of VAS services is triggered from either an SMS-SC or an SMS Router. As a consequence, for interworking in the originating side, both originating and terminating VAS services can be applied. For interworking in the terminating side the terminating VAS services can be applied subject to an SMS Node being involved in the message flow. + +# --- Annex A: Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|--------|-----------|----------|-----|-----------------------------------------|--------| +| 2009-12 | CT#46 | CP-090824 | | | 3GPP TS Presented for approval in CT#46 | 9.0.0 | +| 2009-12 | | | | | Editorial tidy-up | 9.0.1 | +| 2011-03 | - | - | - | - | Update to Rel-10 version (MCC) | 10.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 11.0.0 | +| 2014-09 | - | - | - | - | Update to Rel-12 version (MCC) | 12.0.0 | +| 2015-12 | | | | | Update to Rel-13 version (MCC) | 13.0.0 | +| 2017-03 | CT#75 | - | - | - | Update to Rel-14 version (MCC) | 14.0.0 | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2019-06 | CT#84 | CP-191058 | 000
1 | 1 | Addition of 5GS support | 15.1.0 | +| 2020-07 | CT#88e | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23202/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/Rel-16/23_series/23202/367926125450c2bc3f4bdca9d59a62ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8829e6dff0d0d3f9f3d742927bc37f92112e084 --- /dev/null +++ b/marked/Rel-16/23_series/23202/367926125450c2bc3f4bdca9d59a62ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a468816676b3554257068f295a24fabcfde261b0c4432282c8900ceba87c888 +size 59782 diff --git a/marked/Rel-16/23_series/23202/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg b/marked/Rel-16/23_series/23202/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d99b45ba46b17c563b313b975ba4e575d3fe63a7 --- /dev/null +++ b/marked/Rel-16/23_series/23202/49ee89a1d5852ab005dbbab6de09a8a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f8c5758558785e3a019e4def95e10a4fb17e499fb8f054da180902f204698b3 +size 89311 diff --git a/marked/Rel-16/23_series/23202/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/23_series/23202/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae5115e03a7896bf24c713a3335506b590d4ea56 --- /dev/null +++ b/marked/Rel-16/23_series/23202/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ab7e55263600381f30dba70cf8dc2fa2e671e3bbd7fd4a8c99f96b27f5cc9b6 +size 71038 diff --git a/marked/Rel-16/23_series/23202/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Rel-16/23_series/23202/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58d976dc5c53d5ae8026026deabc59af69ab7ea5 --- /dev/null +++ b/marked/Rel-16/23_series/23202/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c3458e76999f1d8fb8ef992407758b9dcde0a782db4a83ef17d4d298c137127 +size 69792 diff --git a/marked/Rel-16/23_series/23202/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Rel-16/23_series/23202/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe8d42f107ba64ff1dcbe16d087c2ce671837e7d --- /dev/null +++ b/marked/Rel-16/23_series/23202/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95da81d5516b3afb324b0602696c52e7bfaaab4e1dd5d1c144e90cc95c08209a +size 52257 diff --git a/marked/Rel-16/23_series/23202/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/23_series/23202/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29513619390dca69d1b2f84edf4a0450469b5490 --- /dev/null +++ b/marked/Rel-16/23_series/23202/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2da9deab2f7f1d0cce5f262525d258d6fe869b6a5455edf06582c846fef4ed60 +size 48664 diff --git a/marked/Rel-16/23_series/23202/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/23_series/23202/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49d596c631cfdbf1bf76f81786cc82644ab6cf33 --- /dev/null +++ b/marked/Rel-16/23_series/23202/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c081af0f3f097d0cc71101b10a9b1997e0b9245a1c7e5f4deb0895e477a2ab96 +size 62717 diff --git a/marked/Rel-16/23_series/23202/raw.md b/marked/Rel-16/23_series/23202/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..364fa101fccb0076e7d381345477336508e89fcb --- /dev/null +++ b/marked/Rel-16/23_series/23202/raw.md @@ -0,0 +1,345 @@ + + + + + + +# Contents + +| | | +|---------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 General..... | 6 | +| 4.1 Limited set of UTRAN Iu mode PLMN connection models ..... | 7 | +| 4.1.1 Transparent data ..... | 7 | +| 4.1.2 Non-transparent data ..... | 9 | +| 4.2 Limited set of GERAN Iu mode PLMN connection models ..... | 9 | +| 4.2.1 Transparent data ..... | 9 | +| 4.2.2 Non-transparent data ..... | 11 | +| 5 Bearer Capabilities for UMTS Data Services..... | 11 | +| 5.1 Bearer Capabilities for UMTS Data Services ..... | 12 | +| 5.1.1 Transparent Data ..... | 12 | +| 5.1.2 Non-Transparent Fax..... | 12 | +| 5.1.3 NT Data ..... | 12 | +| 5.1.4 Transparent Data for Support of Multimedia ..... | 12 | +| 5.2 BC-IE to RAB QoS Mapping..... | 13 | +| 6 Iu and Nb User Plane ..... | 14 | +| 6.1 NT services..... | 14 | +| 6.2 T services..... | 14 | +| 7 RLC..... | 14 | +| 8 Initial Synchronisation and resynchronisation..... | 14 | +| 9 Call Control..... | 14 | +| 10 Handover Issues ..... | 14 | +| 10.1 Signalling issues..... | 14 | +| 10.2 User Plane ..... | 14 | +| Annex A (informative): Change history..... | 15 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 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. + +# --- 1 Scope + +The present document provides an overview of the architecture and issues related to the provision of Circuit Switched Bearer Services in a 3G mobile network (UMTS) operating in UTRAN or GERAN Iu mode. Handover to GERAN A/Gb mode is also considered. + +NOTE: The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. + +# --- 2 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 TS 22.001: "Principles of circuit telecommunication services supported by a PLMN". +- [2] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [3] 3GPP TS 22.003: "Circuit Teleservices supported by a PLMN". +- [4] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)". +- [5] 3GPP TS 22.101: "Service principles". +- [6] 3GPP TS 22.105: "Services and service capabilities". +- [7] 3GPP TS 23.002: "Network architecture". +- [8] 3GPP TS 23.034: "High Speed Circuit Switched Data (HSCSD) -Stage 2". +- [9] 3GPP TS 23.101: "General UMTS architecture". +- [10] 3GPP TS 23.107: "Quality of Service (QoS), concept and architecture". +- [11] 3GPP TS 24.022: "Radio Link Protocol (RLP) for circuit switched bearer and teleservices ". +- [12] 3GPP TS 25.322: "Radio Link Control (RLC) protocol specification". +- [13] 3GPP TS 25.415: "UTRAN Iu Interface user plane protocols". +- [14] 3GPP TS 27.001: "General on Terminal Adaption Functions (TAF) for Mobile Station (MS)". +- [15] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". +- [16] ITU-T Recommendation V.90 (09/98): "A digital modem and analogue modem pair for use on the Public Switched Telephone Network (PSTN) at data signalling rates of up to 56 000 bit/s downstream and up to 33 600 bit/s upstream". +- [17] ITU-T Recommendation T.30 "Procedures for document facsimile transmission in the general switched telephone network". +- [18] 3GPP TS 44.021: "Rate adaption on the Mobile Station - Base Station System (MS - BSS) interface". +- [19] 3GPP TS 48.020: "Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface". + +- [20] ITU-T Recommendation I.366.1 (06/98): "Segmentation and Reassembly Service Specific Convergence Sublayer for the AAL type 2". +- [21] ITU-T Recommendation Q.2630.1 (12/99): "AAL type 2 signalling protocol (Capability Set 1)". +- [22] 3GPP TS 43.051: "GSM/EDGE Radio Access Network (GERAN) overall description, stage 2" +- [23] 3GPP TS 43.010: "GSM Public Land Mobile Network (PLMN) connection types" +- [24] 3GPP TS 29.415: "Core Network Nb Interface User Plane Protocols". +- [25] ITU-T Recommendation I.363.2: "B-ISDN ATM Adaptation Layer specification : Type 2 AAL". +- [26] ITU-T Recommendation I.460 (02/99): "Multiplexing, rate adaption and support of existing interfaces". +- [27] ITU-T Recommendation I.366.2: "AAL type 2 service specific convergence sublayer for narrow-band services". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +The term 'Mobile Station' (MS) in the present document is synonymous with the term 'User Equipment' (UE) as defined in 3GPP TR 21.905 [2]. + +For the purposes of the present document the following terms and definitions given in 3GPP TS 21.905 [2] and the following apply: + +**A/Gb mode:** indicates that the text applies only to a system or sub-system which operate in A/Gb mode of operation, i.e. with a functional division that is in accordance with the use of an A or a Gb interface between the radio access network and the core network + +**Iu mode:** indicates that the text applies only to a system or a sub-system which operates in Iu mode of operation, i.e. with a functional division that is in accordance with the use of an Iu-CS or Iu-PS interface between the radio access network and the core network + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TS 21.905 [2] and the following apply. + +| | | +|-------|--------------------------------| +| BC | Bearer Capability | +| CE | Connection Element | +| CT | Circuit | +| GBR | Guaranteed Bitrate | +| MBR | Maximum Bitrate | +| RA | Rate Adaptation Functions | +| RNL | Radio Network Layer | +| S/C | Split/Combine Function | +| WAIUR | Wanted Air Interface User Rate | + +# --- 4 General + +CS data services in UMTS are divided according to 3GPP TS 22.001 [1] into Bearer Services (3GPP TS 22.002 [4]) and end-to-end Teleservices (3GPP TS 22.003 [3]). These services are built on services provided by the Access Network. The Radio Access Bearer Services are invoked through the RNL-SAP provided by the Iu User Plane to the Non-access + +stratum on the Core Network side, and the corresponding SAP provided by the RLC to the Non-access stratum on the Terminal side. Figure 1 shows the service architecture. + +![Figure 1: Service architecture diagram showing the layers of services between a Terminal Equipment (TE) and a User Equipment (MT) through a Radio Access Network (RAN) and Core Network (CN) elements.](49ee89a1d5852ab005dbbab6de09a8a6_img.jpg) + +The diagram illustrates the service architecture across several layers: + +- Top Layer:** A single grey bar labeled "End-to-End Service" spanning across all components. +- Second Layer:** Below the End-to-End Service, consisting of three grey boxes: "TE/MT Local Bearer Service" (under TE and MT), "UMTS Bearer Service" (spanning RAN and CN Iu EDGE NODE), and "External Bearer Service" (under CN Gateway and TE). +- Third Layer:** Below the UMTS Bearer Service, containing two grey boxes: "Radio Access Bearer Service" (under RAN) and "CN Bearer Service" (under CN Iu EDGE NODE). +- Fourth Layer:** Below the third layer, containing three grey boxes: "Radio Bearer Service" (under RAN), "Iu Bearer Service" (under CN Iu EDGE NODE), and "Backbone Bearer Service" (under CN Gateway). +- Fifth Layer:** The bottom layer, containing two grey boxes: "Physical Radio Bearer Service" (under RAN) and "Physical Bearer Service" (under CN Iu EDGE NODE). + +Vertical lines connect the components across these layers, showing the flow of services from the TE/MT through the RAN and CN elements to the external network. + +Figure 1: Service architecture diagram showing the layers of services between a Terminal Equipment (TE) and a User Equipment (MT) through a Radio Access Network (RAN) and Core Network (CN) elements. + +Figure 1: Service architecture + +## 4.1 Limited set of UTRAN Iu mode PLMN connection models + +### 4.1.1 Transparent data + +Figure 2 shows the connection model for synchronous transparent CS data. In general all the user data bits are conveyed between the MT and the IWF as they are received from the TE. This implies that the RLC SDU/ Iu UP frame is transparent. + +Figure 3 shows the connection model for asynchronous transparent CS data. The rate adaptation function RA0 from 3GPP TS 44.021 [18] (adapted to the RLC SDU size) is used for converting between asynchronous data and a synchronous bit stream. End-to-end flow control is not applicable in UTRAN Iu mode, thus no status bits are conveyed over RAN/UTRAN (see 3GPP TS 27.001 [14]). + +![Figure 2: Connection model for Synchronous T CS data. This diagram shows the protocol stack for synchronous data transfer. On the left, a TE connects to an I/Fccct at the R I/F. The MT contains RLC, MAC, and CDMA layers. The RNC contains RLC, MAC, CDMA, ATM, and Iu UP layers. The MSC/IWF contains Iu UP, AAL2, ATM, and various user plane options like Modem Codec, ISDN TA, and No IWF. A dashed line labeled 'Transparent Synchronous Data' spans across the R I/F, MT, and RNC interfaces.](d0abac95583b52a3b35f74a215567334_img.jpg) + +Figure 2: Connection model for Synchronous T CS data. This diagram shows the protocol stack for synchronous data transfer. On the left, a TE connects to an I/Fccct at the R I/F. The MT contains RLC, MAC, and CDMA layers. The RNC contains RLC, MAC, CDMA, ATM, and Iu UP layers. The MSC/IWF contains Iu UP, AAL2, ATM, and various user plane options like Modem Codec, ISDN TA, and No IWF. A dashed line labeled 'Transparent Synchronous Data' spans across the R I/F, MT, and RNC interfaces. + +Figure 2: Connection model for Synchronous T CS data + +![Figure 3: Connection model for Asynchronous T CS data. This diagram shows the protocol stack for asynchronous data transfer. It is similar to Figure 2 but includes an RA0 layer in the MT and MSC/IWF. The MT stack is RA0, RLC, MAC, CDMA. The RNC stack is RLC, MAC, CDMA, ATM, Iu UP. The MSC/IWF stack is RA0, Iu UP, AAL2, ATM, and user plane options. A dashed line labeled 'Transparent Asynchronous Data' spans across the R I/F, MT, and RNC interfaces.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +Figure 3: Connection model for Asynchronous T CS data. This diagram shows the protocol stack for asynchronous data transfer. It is similar to Figure 2 but includes an RA0 layer in the MT and MSC/IWF. The MT stack is RA0, RLC, MAC, CDMA. The RNC stack is RLC, MAC, CDMA, ATM, Iu UP. The MSC/IWF stack is RA0, Iu UP, AAL2, ATM, and user plane options. A dashed line labeled 'Transparent Asynchronous Data' spans across the R I/F, MT, and RNC interfaces. + +Figure 3: Connection model for Asynchronous T CS data + +### 4.1.2 Non-transparent data + +Figure 4 shows the connection model for asynchronous non-transparent CS data. + +![Figure 4: Connection model for Asynchronous NT CS data. The diagram illustrates the protocol stack for non-transparent asynchronous data across three main interfaces: R I/F, Uu, and Iu. On the left, a TE (Terminal Equipment) connects to an I/Fccit at the R I/F. The MT (Mobile Terminal) at the R I/F contains L2R and RLP layers. Data flows from the MT through RLC, MAC, and CDMA layers to the RNC. At the Uu interface, the RNC contains RLC, MAC, and CDMA layers. Data then passes through the Iu interface, where the RNC contains Iu UP, AAL2, and ATM layers. The MSC/IWF at the Iu interface contains L2R, RLP, Iu UP, AAL2, and ATM layers. Finally, the data is sent to a Modem Codec and ISDN TA.](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +The diagram shows the connection model for asynchronous non-transparent CS data. It is divided into three main sections by vertical dashed lines representing interfaces: R I/F, Uu, and Iu. A horizontal dashed line at the top indicates the 'Non-transparent Asynchronous Data' path. On the left (TE side), data flows from the TE through an I/Fccit interface. The MT (Mobile Terminal) at the R I/F contains L2R and RLP layers. Data flows from the MT through RLC, MAC, and CDMA layers to the RNC. At the Uu interface, the RNC contains RLC, MAC, and CDMA layers. Data then passes through the Iu interface, where the RNC contains Iu UP, AAL2, and ATM layers. The MSC/IWF at the Iu interface contains L2R, RLP, Iu UP, AAL2, and ATM layers. Finally, the data is sent to a Modem Codec and ISDN TA. + +Figure 4: Connection model for Asynchronous NT CS data. The diagram illustrates the protocol stack for non-transparent asynchronous data across three main interfaces: R I/F, Uu, and Iu. On the left, a TE (Terminal Equipment) connects to an I/Fccit at the R I/F. The MT (Mobile Terminal) at the R I/F contains L2R and RLP layers. Data flows from the MT through RLC, MAC, and CDMA layers to the RNC. At the Uu interface, the RNC contains RLC, MAC, and CDMA layers. Data then passes through the Iu interface, where the RNC contains Iu UP, AAL2, and ATM layers. The MSC/IWF at the Iu interface contains L2R, RLP, Iu UP, AAL2, and ATM layers. Finally, the data is sent to a Modem Codec and ISDN TA. + +Figure 4: Connection model for Asynchronous NT CS data + +## 4.2 Limited set of GERAN Iu mode PLMN connection models + +This subclause gives an overall overview on the PLMN connection models for circuit switched data services in GERAN Iu mode. The stage 2 description is given in 3GPP TS 43.051 [22]. For details concerning the PLMN connection models refer to 3GPP TS 43.010 [23]. + +### 4.2.1 Transparent data + +Figure 5 shows the connection model for synchronous transparent CS data. In general all the user data bits are conveyed between the MT and the IWF as they are received from the TE. This implies that the RLC SDU/ Iu UP frame is transparent. + +Figure 6 shows the connection model for asynchronous transparent CS data. The rate adaptation function RA0 from 3GPP TS 44.021 [18] (adapted to the RLC SDU size) is used for converting between asynchronous data and a synchronous bit stream. End-to-end flow control is not applicable in GERAN Iu mode, thus no status bits are conveyed over RAN/GERAN (see 3GPP TS 27.001 [14]). + +![Figure 5: Connection model for Synchronous T CS data. This diagram shows the protocol stack for synchronous data transfer. It is divided into four main sections: TE (Terminal Equipment), MT (Mobile Terminal), BSS (Base Station System), and MSC/IWF (Mobile Switching Center/Interworking Function). The TE connects to the MT via the R I/F (Radio Interface). The MT contains a stack of layers: S/C (Switching Control), RA (Radio Access), RLC (Radio Link Control), MAC (Medium Access Control), and TDMA (Time Division Multiple Access). The BSS contains a similar stack: S/C, RA, RLC, MAC, and TDMA. The RLC layers in the MT and BSS are connected via the Um interface. The MAC layers in the BSS connect to the Iu interface via the Iu UP (User Plane) and AAL2 (ATM Adaptation Layer 2) layers. The Iu UP layers in the BSS and MSC/IWF are connected via the Iu interface. The MSC/IWF contains the Iu UP, AAL2, and ATM layers, which connect to external devices: Modem Codec, ISDN TA, and No IWF. A dashed line labeled 'Transparent Synchronous Data' spans across the top of the diagram, indicating the data path.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Figure 5: Connection model for Synchronous T CS data. This diagram shows the protocol stack for synchronous data transfer. It is divided into four main sections: TE (Terminal Equipment), MT (Mobile Terminal), BSS (Base Station System), and MSC/IWF (Mobile Switching Center/Interworking Function). The TE connects to the MT via the R I/F (Radio Interface). The MT contains a stack of layers: S/C (Switching Control), RA (Radio Access), RLC (Radio Link Control), MAC (Medium Access Control), and TDMA (Time Division Multiple Access). The BSS contains a similar stack: S/C, RA, RLC, MAC, and TDMA. The RLC layers in the MT and BSS are connected via the Um interface. The MAC layers in the BSS connect to the Iu interface via the Iu UP (User Plane) and AAL2 (ATM Adaptation Layer 2) layers. The Iu UP layers in the BSS and MSC/IWF are connected via the Iu interface. The MSC/IWF contains the Iu UP, AAL2, and ATM layers, which connect to external devices: Modem Codec, ISDN TA, and No IWF. A dashed line labeled 'Transparent Synchronous Data' spans across the top of the diagram, indicating the data path. + +Figure 5: Connection model for Synchronous T CS data + +![Figure 6: Connection model for Asynchronous T CS data. This diagram shows the protocol stack for asynchronous data transfer. It is divided into four main sections: TE (Terminal Equipment), MT (Mobile Terminal), BSS (Base Station System), and MSC/IWF (Mobile Switching Center/Interworking Function). The TE connects to the MT via the R I/F (Radio Interface). The MT contains a stack of layers: RA0 (Radio Access 0), S/C (Switching Control), RA (Radio Access), RLC (Radio Link Control), MAC (Medium Access Control), and TDMA (Time Division Multiple Access). The BSS contains a similar stack: S/C, RA, RLC, MAC, and TDMA. The RLC layers in the MT and BSS are connected via the Um interface. The MAC layers in the BSS connect to the Iu interface via the Iu UP (User Plane) and AAL2 (ATM Adaptation Layer 2) layers. The Iu UP layers in the BSS and MSC/IWF are connected via the Iu interface. The MSC/IWF contains the RA0, Iu UP, AAL2, and ATM layers, which connect to external devices: Modem Codec and ISDN TA. A dashed line labeled 'Transparent Asynchronous Data' spans across the top of the diagram, indicating the data path.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +Figure 6: Connection model for Asynchronous T CS data. This diagram shows the protocol stack for asynchronous data transfer. It is divided into four main sections: TE (Terminal Equipment), MT (Mobile Terminal), BSS (Base Station System), and MSC/IWF (Mobile Switching Center/Interworking Function). The TE connects to the MT via the R I/F (Radio Interface). The MT contains a stack of layers: RA0 (Radio Access 0), S/C (Switching Control), RA (Radio Access), RLC (Radio Link Control), MAC (Medium Access Control), and TDMA (Time Division Multiple Access). The BSS contains a similar stack: S/C, RA, RLC, MAC, and TDMA. The RLC layers in the MT and BSS are connected via the Um interface. The MAC layers in the BSS connect to the Iu interface via the Iu UP (User Plane) and AAL2 (ATM Adaptation Layer 2) layers. The Iu UP layers in the BSS and MSC/IWF are connected via the Iu interface. The MSC/IWF contains the RA0, Iu UP, AAL2, and ATM layers, which connect to external devices: Modem Codec and ISDN TA. A dashed line labeled 'Transparent Asynchronous Data' spans across the top of the diagram, indicating the data path. + +Figure 6: Connection model for Asynchronous T CS data + +### 4.2.2 Non-transparent data + +Figure 7 shows the connection model for asynchronous non-transparent CS data. + +![Figure 7: Connection model for Asynchronous NT CS data. The diagram illustrates the protocol stack for non-transparent asynchronous data across three main entities: TE (Terminal Equipment), MT (Mobile Terminal), BSS (Base Station System), and MSC/IWF (Mobile Switching Center/Interworking Function). The data flows from the TE through the MT's L2R and RLP layers, then through the BSS's S/C, RA, RLC, MAC, and TDMA layers. It then passes through the Iu interface (Iu UP, AAL2, ATM) to the MSC/IWF, where it is handled by the RLP layer and connected to a Modem Codec and ISDN TA. The R I/F interface is shown between the TE and MT, and the Um interface is between the MT and BSS.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +Figure 7: Connection model for Asynchronous NT CS data. The diagram illustrates the protocol stack for non-transparent asynchronous data across three main entities: TE (Terminal Equipment), MT (Mobile Terminal), BSS (Base Station System), and MSC/IWF (Mobile Switching Center/Interworking Function). The data flows from the TE through the MT's L2R and RLP layers, then through the BSS's S/C, RA, RLC, MAC, and TDMA layers. It then passes through the Iu interface (Iu UP, AAL2, ATM) to the MSC/IWF, where it is handled by the RLP layer and connected to a Modem Codec and ISDN TA. The R I/F interface is shown between the TE and MT, and the Um interface is between the MT and BSS. + +Figure 7: Connection model for Asynchronous NT CS data + +# 5 Bearer Capabilities for UMTS Data Services + +The UMTS bearer services are described by the PLMN BC-IE. Five services (or services categories) are currently distinguishable from the PLMN BC-IE in UTRAN Iu mode: + +- Speech. +- Transparent Data for support of Multimedia. +- Transparent Data. +- Non-transparent Fax. +- Non-transparent data. + +Four services (or services categories) are currently distinguishable from the PLMN BC-IE in GERAN Iu mode: + +- Speech. +- Transparent Data for support of Multimedia. +- Transparent Data. +- Non-transparent data. + +Speech is currently not in the scope of the present document. + +Each UMTS bearer service is supported by a Radio Access Bearers (RAB). The RABs in turn are described by the QoS parameters. There may be one or several RAB candidates for supporting a UMTS bearer service. The possible candidates are described by a mapping of the BC-IE to RAB QoS described in subclause 5.2. + +## 5.1 Bearer Capabilities for UMTS Data Services + +### 5.1.1 Transparent Data + +This service is distinguished by the following BC-IE parameters: + +- ITC = UDI or 3.1 kHz audio or Other ITC = RDI. +- CE = transparent. + +For this service the FNUR at the setup is restricted to: + +- 64 kbit/s, in case ITC = UDI. +- 56 kbit/s in case ITC = UDI or Other ITC = RDI. +- 28,8 kbit/s, in case ITC = 3,1 kHz audio. + +NOTE: ITU-T Recommendation V.90 [16] is not supported in transparent mode, because asymmetric user rates are not supported in transparent mode. + +### 5.1.2 Non-Transparent Fax + +This service is only applicable for UTRAN Iu mode. It is distinguished by the following BC-IE parameters: + +- ITC = Fax Group 3 (ITU-T Recommendation T.30 [17]). +- CE = non-transparent. + +WAIUR shall not be more than 28.8 kbit/s. The possible AIURs are limited to 14,4 kbit/s and 28,8 kbit/s. + +### 5.1.3 NT Data + +This service is distinguished by the following BC-IE parameters: + +- ITC = UDI or 3.1 kHz audio or Other ITC = RDI. +- CE = non-transparent. + +The possible AIURs in UTRAN Iu mode are limited to 14,4 kbit/s, 28,8 kbit/s and 57,6 kbit/s. For GERAN Iu mode the following AIURs are possible: 9,6 kbit/s, 14,4 kbit/s, 19,2 kbit/s, 28,8 kbit/s, 38,4 kbit/s, 43,2 kbit/s and 57,6 kbit/s. + +### 5.1.4 Transparent Data for Support of Multimedia + +This service is distinguished by the following BC-IE parameters: + +- ITC = UDI or 3.1 kHz audio or Other ITC = RDI. +- CE = transparent. +- Other rate adaptation = H.223 and H.245. + +For this service the FNUR at the setup is restricted to: + +- 64 kbit/s, in case ITC = UDI. +- 56 kbit/s in case Other ITC = RDI. +- 33,6 kbit/s, in case ITC = 3,1 kHz audio. +- 32 kbit/s, in case ITC = UDI. +- 28,8 kbit/s, in case ITC = 3,1 kHz audio. + +NOTE: Transmission rates 31.2 kbit/s and 28.8 kbit/s negotiated by the modems in a 3.1 kHz multimedia call may be used with a rate adaptation to 33.6 kbit/s between the UE and the IWF (see 3GPP TS 27.001 [14] and 3GPP TS 29.007 [15]). The negotiated values shall be provided by the MSC by way of a MODIFY message. + +## 5.2 BC-IE to RAB QoS Mapping + +Since UMTS bearer services are described by BC-IEs and RABs by QoS parameters, a mapping between the UMTS bearer services and the possible RABs that support them has to be specified. The QoS mapping is based on 3GPP TS 23.107 [10] and is specified in detail in 3GPP TS 27.001[14], annex B, subclause B.1.13. + +# --- 6 Iu and Nb User Plane + +## 6.1 NT services + +The Iu and NB User Plane for NT services is described in Clause 11a.2 of 3GPP TS 29.007 [15]. + +## 6.2 T services + +The Iu and NB User Plane for T services is described in Clause 11a.3 of 3GPP TS 29.007 [15]. + +# --- 7 RLC + +The RLC shall be used in transparent mode for T and NT services. + +# --- 8 Initial Synchronisation and resynchronisation + +The initial synchronisation and actions on loss of synchronisation are specified in 3GPP TS 27.001 [14] and 3GPP TS 29.007 [15]. + +# --- 9 Call Control + +BC-IE negotiation procedures and mapping to ISDN are specified in 3GPP TS 27.001 [14] and 3GPP TS 29.007 [15]. BC-IE parameter values shall be restricted as indicated in subclause 5.1. See also 3GPP TS 27.001 [14], annex B, table B.5a for further details on the validity of parameter values in A/Gb mode and Iu mode. + +# --- 10 Handover Issues + +## 10.1 Signalling issues + +The handling of signalling during handover is described in Clause 11.0 of 3GPP TS 29.007 [15]. + +## 10.2 User Plane + +The handling of the user plane during handover is described in clause 11 of 3GPP TS 29.007 [15]. + +# Annex A (informative): Change history + +| Change history | | | | | | | | +|-----------------------|--------------|-----------------|-----------|------------|-------------------------------------------------------------------------|-----------------------------------------|------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 12-2004 | CN#26 | NP-040607 | | | "Technical Report" changed to "Technical Specification" in the foreword | 1.0.1 | 6.0.0 | +| 03-2005 | CN#27 | NP-050110 | 1 | | References for Iu and Nb User Plane | 6.0.0 | 6.1.0 | +| 06-2007 | CT#36 | | | | Upgraded to Release 7 | 6.1.0 | 7.0.0 | +| 12-2008 | CT#42 | | | | Upgraded to v8.0.0 due to simple upgrade without no technical change | 7.0.0 | 8.0.0 | +| 12-2009 | CT#46 | | | | Automatic upgrade from previous Release | 8.0.0 | 9.0.0 | +| 09-2010 | CT#49 | CP-100549 | 2 | 1 | Correcting unspecific external reference | 9.0.0 | 9.1.0 | +| 03-2011 | CT#51 | | | | Automatic upgrade from previous Release version 9.1.0 | 9.1.0 | 10.0.0 | +| 03-2011 | CT#51 | | | | Correction of heading and numbering made by MCC | 10.0.0 | 10.0.1 | +| 09-2012 | CT#57 | | | | Automatic upgrade from previous Release version 10.0.1 | 10.0.1 | 11.0.0 | +| 10-2014 | | | | | Automatic upgrade from previous Release | 11.0.0 | 12.0.0 | +| 12-2015 | | | | | Automatic upgrade from previous Release | 12.0.0 | 13.0.0 | +| Change history | | | | | | | | +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | New | +| 2017-03 | CT#75 | | | | | Automatic upgrade from previous Release | 14.0.0 | +| 2018-06 | - | - | - | - | | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-06 | CT#88e | | | | | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23205/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/23_series/23205/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f01ef2b591a340a57a87763bb63e9e518a5bae2 --- /dev/null +++ b/marked/Rel-16/23_series/23205/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f2d830e90a871d1195ef2665e18c03775ab38bb6984a1456655c4b6d04e8407 +size 125365 diff --git a/marked/Rel-16/23_series/23205/01141eb99b707de5aead56f84afe3b1f_img.jpg b/marked/Rel-16/23_series/23205/01141eb99b707de5aead56f84afe3b1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78957bc3bdb9184f552e32c5235cbf5d7a555400 --- /dev/null +++ b/marked/Rel-16/23_series/23205/01141eb99b707de5aead56f84afe3b1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e003e98976f621f6e53016763fc16373d1ad984a3f5fd151189a8556ae17dcfb +size 17940 diff --git a/marked/Rel-16/23_series/23205/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg b/marked/Rel-16/23_series/23205/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b7c344a9b217a4ba1ca392e35eabaf4921ab24d --- /dev/null +++ b/marked/Rel-16/23_series/23205/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3653044bf000abe3901bcfa19cc1edee23e108ebc972b7c994c25bbf2b188197 +size 131633 diff --git a/marked/Rel-16/23_series/23205/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/23_series/23205/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bcd7e6198b626e3a5253fcac67a4b8c0aa1ac79 --- /dev/null +++ b/marked/Rel-16/23_series/23205/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b77e588dabf8c568a39eebe90103b38db407e8f4f849533d71831aea3c569585 +size 88006 diff --git a/marked/Rel-16/23_series/23205/070352b751dd0711b8ac6ddfa6df1d98_img.jpg b/marked/Rel-16/23_series/23205/070352b751dd0711b8ac6ddfa6df1d98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5836a7e212e63db2f223d4c86e2ea007794a284f --- /dev/null +++ b/marked/Rel-16/23_series/23205/070352b751dd0711b8ac6ddfa6df1d98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8631f57698957b29a1b183280e45b2e4e1cfae960a608cf598aac474f694b578 +size 95938 diff --git a/marked/Rel-16/23_series/23205/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-16/23_series/23205/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9833852015ad1dd45761e52da326de4bbc3a0fa --- /dev/null +++ b/marked/Rel-16/23_series/23205/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e63f9b708418adaba1ec7cb94f63a44be41872f1cbcc4afbb5d50fd70ae1e5e6 +size 72589 diff --git a/marked/Rel-16/23_series/23205/0b998e3ad8f9d104768642612605cb35_img.jpg b/marked/Rel-16/23_series/23205/0b998e3ad8f9d104768642612605cb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a52c3919e86dfc764dcd459a607612579b67938 --- /dev/null +++ b/marked/Rel-16/23_series/23205/0b998e3ad8f9d104768642612605cb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a420a2b54b9b12e0ee8647b61557ee19767e424e66c03859ba04462bced77e8f +size 101644 diff --git a/marked/Rel-16/23_series/23205/0f1767577a073167eb9628d72034e083_img.jpg b/marked/Rel-16/23_series/23205/0f1767577a073167eb9628d72034e083_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..059283295e6a9eac1111dbac6d4612c023303402 --- /dev/null +++ b/marked/Rel-16/23_series/23205/0f1767577a073167eb9628d72034e083_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fda3d24976f084e3df79757ed23da3d00ac57c2b9b0f98d4bf27a1bf80e9f12 +size 36519 diff --git a/marked/Rel-16/23_series/23205/10b0dda884baae493ad958422d11b552_img.jpg b/marked/Rel-16/23_series/23205/10b0dda884baae493ad958422d11b552_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca58978e3c7abb870913e2ba9201d2c0889325a0 --- /dev/null +++ b/marked/Rel-16/23_series/23205/10b0dda884baae493ad958422d11b552_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:609119a0b483699b9a7fcdfdb79ac2690737bfb8c1932404033faf0522beea07 +size 49190 diff --git a/marked/Rel-16/23_series/23205/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg b/marked/Rel-16/23_series/23205/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cb27219c0791a247e0cc4ba351fe2151d58a2fa --- /dev/null +++ b/marked/Rel-16/23_series/23205/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fea56793b2d02bc3bf5ba3f3c5e1a6bdc16f494871fbb094db4a212269bdca9 +size 115327 diff --git a/marked/Rel-16/23_series/23205/1520ac6ca40d678c53dca4ef6550963f_img.jpg b/marked/Rel-16/23_series/23205/1520ac6ca40d678c53dca4ef6550963f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d73ef461e191746fa86a78ddd31a565210f7572 --- /dev/null +++ b/marked/Rel-16/23_series/23205/1520ac6ca40d678c53dca4ef6550963f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcb891084819cad080f045c75393fa75580fe76df18cfbdfc0873c978db3e3e6 +size 15497 diff --git a/marked/Rel-16/23_series/23205/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/Rel-16/23_series/23205/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3de8de7f62fed4abfc110718e3326139a46b4a0 --- /dev/null +++ b/marked/Rel-16/23_series/23205/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18e594de2ec33bae0fd8d40fea29e2e467e17a1556800f9d328e818e90fb3890 +size 117280 diff --git a/marked/Rel-16/23_series/23205/187bba66c887c745c512add37a577c5e_img.jpg b/marked/Rel-16/23_series/23205/187bba66c887c745c512add37a577c5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43992f475ecaefb2454c74f5a8cfb83d82f5a1db --- /dev/null +++ b/marked/Rel-16/23_series/23205/187bba66c887c745c512add37a577c5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a76e72e95edee9d7e14873db59c20fe6d1353d992f168cecd45e00363a6978d6 +size 33919 diff --git a/marked/Rel-16/23_series/23205/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/marked/Rel-16/23_series/23205/18bb06865e2dada3656ea3d57f290f7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..729ae9bf6e53748d47b28bf9ee10d6efe1cb7aaf --- /dev/null +++ b/marked/Rel-16/23_series/23205/18bb06865e2dada3656ea3d57f290f7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:388dfc2f8f69811e29f20feb7c351962909f70515c7f0ec367f22951fc887cc6 +size 69953 diff --git a/marked/Rel-16/23_series/23205/18d7d8de298d79e7bc87af5217f11203_img.jpg b/marked/Rel-16/23_series/23205/18d7d8de298d79e7bc87af5217f11203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc5db12cc0860a87c87303a637c49ad26ea46027 --- /dev/null +++ b/marked/Rel-16/23_series/23205/18d7d8de298d79e7bc87af5217f11203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:713c166d54c66ce1b4728ab71a6ff5e3f7c279054554594cc90078a9976956b6 +size 96815 diff --git a/marked/Rel-16/23_series/23205/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23205/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b19e0433cc351b726cbe5d905a06a2d7c065f45 --- /dev/null +++ b/marked/Rel-16/23_series/23205/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3c35d7d058c6d5cd67a4f46f478de8cea29d9be2427802e8d1a93be2fbe7cf9 +size 89449 diff --git a/marked/Rel-16/23_series/23205/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg b/marked/Rel-16/23_series/23205/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a246c74b224fea10e5a8f6c17d7a168bea790977 --- /dev/null +++ b/marked/Rel-16/23_series/23205/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b6d8c71a18ffd02ce10b9a926a7fb0b6a076a3578f6254c6b99eedcf1da18b5 +size 24352 diff --git a/marked/Rel-16/23_series/23205/1b893df61c2b73b7a85e65fc1f58e203_img.jpg b/marked/Rel-16/23_series/23205/1b893df61c2b73b7a85e65fc1f58e203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb428299db04bbde301c09009716eb09aff70b2a --- /dev/null +++ b/marked/Rel-16/23_series/23205/1b893df61c2b73b7a85e65fc1f58e203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:756c7c9479d0c0f1dd17fd2f01a45198abf5cdb134367b90a1502facdc2d943d +size 61719 diff --git a/marked/Rel-16/23_series/23205/1b896a95bc9974ad01fac7ac6f541a96_img.jpg b/marked/Rel-16/23_series/23205/1b896a95bc9974ad01fac7ac6f541a96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53fcd89fb41abeb5b1bc9698b9b7da5410b9da19 --- /dev/null +++ b/marked/Rel-16/23_series/23205/1b896a95bc9974ad01fac7ac6f541a96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1020b74483ae82e2fdf19989b90272eaa3111b3fc1ad20fae7ce0a0505df2e76 +size 20157 diff --git a/marked/Rel-16/23_series/23205/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/marked/Rel-16/23_series/23205/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18146bbd5eca86648cb503dbf4cd5bd063269813 --- /dev/null +++ b/marked/Rel-16/23_series/23205/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ab6492be89dd4bd633b115e80422718e75241516f1f683331d878f0147f3394 +size 84121 diff --git a/marked/Rel-16/23_series/23205/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg b/marked/Rel-16/23_series/23205/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd44fc70655588bdc51a20d36bb67539fb7d7c61 --- /dev/null +++ b/marked/Rel-16/23_series/23205/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47eea742ab90fda4a89b266da6b3be5857e4c0300191ea52807f3e10f7cb203e +size 182470 diff --git a/marked/Rel-16/23_series/23205/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/marked/Rel-16/23_series/23205/1eadbbe42cfcac5c0023577110aec5e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f2d872e980a61c99c82f3371499bde016d06938 --- /dev/null +++ b/marked/Rel-16/23_series/23205/1eadbbe42cfcac5c0023577110aec5e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd1c667dead35567bf4b4b5e217fcfcd1939f657a1ae61a6bde653fe79470a4d +size 24153 diff --git a/marked/Rel-16/23_series/23205/212c50c4e3d043c989037a01e13c1a98_img.jpg b/marked/Rel-16/23_series/23205/212c50c4e3d043c989037a01e13c1a98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64e59b536f81f385b91231345ed8a763e6bf488d --- /dev/null +++ b/marked/Rel-16/23_series/23205/212c50c4e3d043c989037a01e13c1a98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49838f7a3d2383cdd549944220c8b3c327496bf0c28d97e808191b9638ed7782 +size 146493 diff --git a/marked/Rel-16/23_series/23205/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg b/marked/Rel-16/23_series/23205/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a7eb44908822cd9ff8451bc5239e7cccf5e991c --- /dev/null +++ b/marked/Rel-16/23_series/23205/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8dcade8727b80770d150658b719dba52b9a112e523dfb0cf351610a41fbea7f0 +size 10913 diff --git a/marked/Rel-16/23_series/23205/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg b/marked/Rel-16/23_series/23205/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd242014e4711319e2ef5e6e100641b41fa20139 --- /dev/null +++ b/marked/Rel-16/23_series/23205/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e2a6a4418e2e7084d2381cdac6dd903ac24efb2091ae33e8866498164d4ad5b +size 91246 diff --git a/marked/Rel-16/23_series/23205/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23205/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..971101ecd076d8575fd8c06c06add5a9686fbe58 --- /dev/null +++ b/marked/Rel-16/23_series/23205/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5520e97d73d51a2af5c78354cbd292d3e80cb41401dd91ff4d1c2ad143d5d49 +size 48904 diff --git a/marked/Rel-16/23_series/23205/288220dc8e18b23fc8f294cf1ca909b4_img.jpg b/marked/Rel-16/23_series/23205/288220dc8e18b23fc8f294cf1ca909b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..843b52503ad1a238ad8835c88cc3f87a1c5daf51 --- /dev/null +++ b/marked/Rel-16/23_series/23205/288220dc8e18b23fc8f294cf1ca909b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:026a3397f5797967eba60b551702edd9094b75fe7eccf606fa99a16c0ec2c0a4 +size 33478 diff --git a/marked/Rel-16/23_series/23205/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23205/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ab0764ad3c4a773ddb842821b0abe950b34ac86 --- /dev/null +++ b/marked/Rel-16/23_series/23205/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c758ea585800f3e38ef3b10d66c80a4b1745ffaa8d2c28032a1288d84df8b39b +size 72839 diff --git a/marked/Rel-16/23_series/23205/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-16/23_series/23205/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45033d576b7602a3ceddeeb8d7ec86d207b58475 --- /dev/null +++ b/marked/Rel-16/23_series/23205/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f745e2e1b27f89cc60285cf204aef9f520533a055549484e4bb55e1305cf938 +size 108373 diff --git a/marked/Rel-16/23_series/23205/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23205/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e7495d5df2987598e34863df3770eb64c64d1d8 --- /dev/null +++ b/marked/Rel-16/23_series/23205/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc8c644d5a204409aa0c77c8412b38323d12378db6af39d258292c160c9157e6 +size 74070 diff --git a/marked/Rel-16/23_series/23205/2b00743506f6a3bbd17af764162dc76d_img.jpg b/marked/Rel-16/23_series/23205/2b00743506f6a3bbd17af764162dc76d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6872f8c8b55e5e76fc9f0175072b4aa28e7b20ce --- /dev/null +++ b/marked/Rel-16/23_series/23205/2b00743506f6a3bbd17af764162dc76d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a49952fb462c80a70d5738e3c8e4168015ee3f7fbf53b3c1bafc82aee3d11143 +size 120565 diff --git a/marked/Rel-16/23_series/23205/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/Rel-16/23_series/23205/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06a180db55c330031d29717b2cb4bc36f3062be4 --- /dev/null +++ b/marked/Rel-16/23_series/23205/2f587210e4f97c32758c5972e2e83d20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4839356b303af7bec286dd92d16f6573ae4668dd8bb741044702374103feaffa +size 111943 diff --git a/marked/Rel-16/23_series/23205/3263a25e110201638bda790456af2909_img.jpg b/marked/Rel-16/23_series/23205/3263a25e110201638bda790456af2909_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f33d580e5649cd9e5a2f32294f371e1c962c7c9a --- /dev/null +++ b/marked/Rel-16/23_series/23205/3263a25e110201638bda790456af2909_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bc86bfc2e4fc33e4372962dfabba1e7b34ae9561259e67bf0bea1aa48cbcc90 +size 21879 diff --git a/marked/Rel-16/23_series/23205/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/23_series/23205/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..088b4183994f09fbe2234c186e12c32d48d4673b --- /dev/null +++ b/marked/Rel-16/23_series/23205/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6055e43b969a3212530ed49d5bac61977b76760eb37b80f63ea9b61512aa9cb +size 236199 diff --git a/marked/Rel-16/23_series/23205/32acdaad6c921e80fd17e42562858b80_img.jpg b/marked/Rel-16/23_series/23205/32acdaad6c921e80fd17e42562858b80_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2e220c901e663e4a8fc907b917a6e48df13917f --- /dev/null +++ b/marked/Rel-16/23_series/23205/32acdaad6c921e80fd17e42562858b80_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5c4f595b5786e35aea4014b269b74350b3b27db6d4b01ba9d293299d5f50e2a +size 20667 diff --git a/marked/Rel-16/23_series/23205/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/23_series/23205/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8e47bdee81e9d81117853833a70b79a9cd774d6 --- /dev/null +++ b/marked/Rel-16/23_series/23205/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c078afaa955d6cc9728660a16716e508fbaebd28081d09497ef860dcf262838 +size 58846 diff --git a/marked/Rel-16/23_series/23205/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg b/marked/Rel-16/23_series/23205/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b035f23e7f777a0cef7903d0b28f147fbdaa9b6 --- /dev/null +++ b/marked/Rel-16/23_series/23205/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8dc1f92c48496ae0fdcc043dcaabe2884bdbf7ffd8b6b7299de555176261d33 +size 128702 diff --git a/marked/Rel-16/23_series/23205/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/23_series/23205/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bd1d4007ed1314822cd0a5f2b3be6a84ad6897b --- /dev/null +++ b/marked/Rel-16/23_series/23205/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b37443ef3de3e2030cf97d85346a03098121d88d8d47af2ef73d5fba79720999 +size 46422 diff --git a/marked/Rel-16/23_series/23205/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-16/23_series/23205/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c890223c0b69d7ea37d5e1f4397e5cb14f98988 --- /dev/null +++ b/marked/Rel-16/23_series/23205/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ae02f9d4a6858d277de8698c0af85759cc563621a7d0078cc6963fef794bb59 +size 61717 diff --git a/marked/Rel-16/23_series/23205/356eb99ab9489bbd647223390a913903_img.jpg b/marked/Rel-16/23_series/23205/356eb99ab9489bbd647223390a913903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d834b0c5f1df35db7dc2bd53f03aac6ad978985 --- /dev/null +++ b/marked/Rel-16/23_series/23205/356eb99ab9489bbd647223390a913903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bb9f5cb8bfe87fbbd6f15a16238e7397754fdbdc083fce2142772f5eb381df2 +size 47825 diff --git a/marked/Rel-16/23_series/23205/376f80eb8a41369e87da63a0210d173e_img.jpg b/marked/Rel-16/23_series/23205/376f80eb8a41369e87da63a0210d173e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..361c3b17d65253852bdb19300c2b5b44e017e172 --- /dev/null +++ b/marked/Rel-16/23_series/23205/376f80eb8a41369e87da63a0210d173e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b9274e08c44819c7a44e964cc90220d03603dedc16037467f21eca62bbe1c5c0 +size 151592 diff --git a/marked/Rel-16/23_series/23205/38d82ffe820e339811b396206f40a201_img.jpg b/marked/Rel-16/23_series/23205/38d82ffe820e339811b396206f40a201_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf47157fdd407bbbdb5e01a7c66589c068fa00b8 --- /dev/null +++ b/marked/Rel-16/23_series/23205/38d82ffe820e339811b396206f40a201_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68c623157b96844be59476f6468f17e1564a9ec4176b4a9adc169eee3194d497 +size 134639 diff --git a/marked/Rel-16/23_series/23205/3922e505954d53f8864a44dc9ea664c6_img.jpg b/marked/Rel-16/23_series/23205/3922e505954d53f8864a44dc9ea664c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..522c56b6bfc714709264a2d41836cdb3ed260dab --- /dev/null +++ b/marked/Rel-16/23_series/23205/3922e505954d53f8864a44dc9ea664c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db10fa56f983d6792fd287c16f56be03df8f0b1cdb9f6522129dcade011229ec +size 97179 diff --git a/marked/Rel-16/23_series/23205/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/marked/Rel-16/23_series/23205/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e91e230af3a155937519a9502335c6ee6d0a840 --- /dev/null +++ b/marked/Rel-16/23_series/23205/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54e274df28d7a8833c8642154eb5ba5187bc8969517b0b8df2c4118f376ecef0 +size 22048 diff --git a/marked/Rel-16/23_series/23205/3e20f0289a1945c7c3894f51383d8e37_img.jpg b/marked/Rel-16/23_series/23205/3e20f0289a1945c7c3894f51383d8e37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..706d8fa75086e9aa7206a2d174650cdb6038c47c --- /dev/null +++ b/marked/Rel-16/23_series/23205/3e20f0289a1945c7c3894f51383d8e37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37478f266424e22726659724b305381b6ee77c23466eb5ee95a6d4cb57b828a0 +size 26873 diff --git a/marked/Rel-16/23_series/23205/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg b/marked/Rel-16/23_series/23205/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30fc60eb4cf5168dd36537fca1990015d43a44a2 --- /dev/null +++ b/marked/Rel-16/23_series/23205/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ecd9d061192c2638c941af17c7d672e00115cadb3bb8f6b06b7232f51af4f3e8 +size 55005 diff --git a/marked/Rel-16/23_series/23205/3ec35c497a0765a1a885c85f214b1bef_img.jpg b/marked/Rel-16/23_series/23205/3ec35c497a0765a1a885c85f214b1bef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..001a1514aadc59e5f71fa28890f1b682154a92d0 --- /dev/null +++ b/marked/Rel-16/23_series/23205/3ec35c497a0765a1a885c85f214b1bef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3be6da7e47dedf5acdd26fe0f223370a612c26e7c54c301aa5bfb3efb6ae2e98 +size 25471 diff --git a/marked/Rel-16/23_series/23205/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-16/23_series/23205/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bf420db64527f14dc7765eef49df718334db224 --- /dev/null +++ b/marked/Rel-16/23_series/23205/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d94c61ed7b30ac9464411982b2b868c9a6fcb85c186f5d1a42140907cf6a31f +size 55919 diff --git a/marked/Rel-16/23_series/23205/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23205/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa9982ff560ef16590803acbb9f6bcf4b5272146 --- /dev/null +++ b/marked/Rel-16/23_series/23205/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bfa55adbf39112d2a297401fcc23d2752543d56bad9cc68127b07a6fee567620 +size 95729 diff --git a/marked/Rel-16/23_series/23205/43ff52fe5a7c6990f4f0d5e0ca55d4b4_img.jpg b/marked/Rel-16/23_series/23205/43ff52fe5a7c6990f4f0d5e0ca55d4b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcb887210af5973381d31e0275c680ff91cf604f --- /dev/null +++ b/marked/Rel-16/23_series/23205/43ff52fe5a7c6990f4f0d5e0ca55d4b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:47c6345168dc23b73717d6e72bb8b4f8017b9ebf85a01113e182166cb28b541c +size 31381 diff --git a/marked/Rel-16/23_series/23205/44c649b1c110b4cd617810ae17342927_img.jpg b/marked/Rel-16/23_series/23205/44c649b1c110b4cd617810ae17342927_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea01b4cd801068a019e9e2adfbe7105a0912244d --- /dev/null +++ b/marked/Rel-16/23_series/23205/44c649b1c110b4cd617810ae17342927_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fca83ddcf78ae4a4df532fefac9b5feb02fb46e1f016d490dd18e540cbb74fa5 +size 49392 diff --git a/marked/Rel-16/23_series/23205/458fdbcb4015a4ee90bd84809afc4aac_img.jpg b/marked/Rel-16/23_series/23205/458fdbcb4015a4ee90bd84809afc4aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..592598da77af60b54fbb98276963f823b212d490 --- /dev/null +++ b/marked/Rel-16/23_series/23205/458fdbcb4015a4ee90bd84809afc4aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1583d762f39d8a1532b743f6ceb372568ffdd62dbabe816266d0845e204744e4 +size 37862 diff --git a/marked/Rel-16/23_series/23205/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Rel-16/23_series/23205/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2edf40ef115e1578d8b37ff02bb1343520f12011 --- /dev/null +++ b/marked/Rel-16/23_series/23205/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:729b6434e1f6a445c35f5ad30916a84764506e9a9f9a35688675502e231e1a24 +size 125515 diff --git a/marked/Rel-16/23_series/23205/508bc574df81fa8d3027a374f6d155fc_img.jpg b/marked/Rel-16/23_series/23205/508bc574df81fa8d3027a374f6d155fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..18d5ae43decefd0c0d0016776e2a362eac90ef66 --- /dev/null +++ b/marked/Rel-16/23_series/23205/508bc574df81fa8d3027a374f6d155fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51017acee9a3bfd89b7375bc5aaa63da05f2843658d8a4b90701f80a763504db +size 56689 diff --git a/marked/Rel-16/23_series/23205/536768a30136cd5c2d57f46c25d1d804_img.jpg b/marked/Rel-16/23_series/23205/536768a30136cd5c2d57f46c25d1d804_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55638e77ce487cbac5bd1a666aae7ca6608777a4 --- /dev/null +++ b/marked/Rel-16/23_series/23205/536768a30136cd5c2d57f46c25d1d804_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acc097180fd734ff49cc189750fb0872d035063860d04a4b730e25bedc0d3705 +size 176903 diff --git a/marked/Rel-16/23_series/23205/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-16/23_series/23205/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23cdad41a0aa38b4e96fb99ae239f3e88af85ff0 --- /dev/null +++ b/marked/Rel-16/23_series/23205/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:699f65c763e7ebb6fcc871728c0352cdf2dd7e18786064ce1731efcf1409192c +size 95080 diff --git a/marked/Rel-16/23_series/23205/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-16/23_series/23205/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4d804bea111bbf0482a7808092e7c0ffdb79515 --- /dev/null +++ b/marked/Rel-16/23_series/23205/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53d7d3d0669a2d751a3b59a555087c7639a1637bd4a44b35f2ba20b398b09b4b +size 17084 diff --git a/marked/Rel-16/23_series/23205/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg b/marked/Rel-16/23_series/23205/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..175b6a1e39b1201bc51af4a87ee3fc6dc5d0d362 --- /dev/null +++ b/marked/Rel-16/23_series/23205/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ca0c09743614702b513c5d645cd10efd2dd0febaf9e80310994a675dcad2ae6 +size 87790 diff --git a/marked/Rel-16/23_series/23205/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg b/marked/Rel-16/23_series/23205/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2354a4a81de39b08642d1915ff7f1c1af9d4aef --- /dev/null +++ b/marked/Rel-16/23_series/23205/5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1aff7221849ec33ca662796878a4264ed021c7b1af7730f7b4813eee05fb5929 +size 25647 diff --git a/marked/Rel-16/23_series/23205/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg b/marked/Rel-16/23_series/23205/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ce090bb30a91dfdce76371ef6081e0f66553416 --- /dev/null +++ b/marked/Rel-16/23_series/23205/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54978629336e553a617192817a811af35071825a9cc336a7618264b73a2c652b +size 154309 diff --git a/marked/Rel-16/23_series/23205/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-16/23_series/23205/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..348ac3a4ad7a033c0bbabc137f4e52d4ab5736f7 --- /dev/null +++ b/marked/Rel-16/23_series/23205/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc351ab7caf32e719630d89925f9fb60f21f218611a2ed8894551f372d2f7569 +size 57627 diff --git a/marked/Rel-16/23_series/23205/62ee64afa2d368d732de66628cf2c841_img.jpg b/marked/Rel-16/23_series/23205/62ee64afa2d368d732de66628cf2c841_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e6cd1132ccd081036a415f016bd10b3bbe2d069 --- /dev/null +++ b/marked/Rel-16/23_series/23205/62ee64afa2d368d732de66628cf2c841_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e715e87381f11843d8784bf00c716d714aa64cdaa0a37747220d70125f3bb3ae +size 21305 diff --git a/marked/Rel-16/23_series/23205/63a2519518616620ef0e53d98b923c05_img.jpg b/marked/Rel-16/23_series/23205/63a2519518616620ef0e53d98b923c05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cebb0ad55788f9f9265d695a8f9822b29ea568a3 --- /dev/null +++ b/marked/Rel-16/23_series/23205/63a2519518616620ef0e53d98b923c05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fff82242382ed66ba013801b710fa21739ebd86d31419a44de119eda08dd18a +size 16717 diff --git a/marked/Rel-16/23_series/23205/649f424fd35ea31f622163506a6148ed_img.jpg b/marked/Rel-16/23_series/23205/649f424fd35ea31f622163506a6148ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eacefc98d9d58aedb40b4d46a01aa2c9cb121c31 --- /dev/null +++ b/marked/Rel-16/23_series/23205/649f424fd35ea31f622163506a6148ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd30e1cd7cc36aa034d9fbf3b3d5b9bd47946b3c750f1aec28ee1da6a6e4f1d9 +size 43356 diff --git a/marked/Rel-16/23_series/23205/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-16/23_series/23205/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..334e1a5d8c5c07ac7ca0e2a66046a8ce2133d910 --- /dev/null +++ b/marked/Rel-16/23_series/23205/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f92493f79d2f5cecd800c8500a5715a1d01e08952a0f62d93893b39a5b008a7 +size 52586 diff --git a/marked/Rel-16/23_series/23205/67a1dd734d3de6e31754caf85d6fe77f_img.jpg b/marked/Rel-16/23_series/23205/67a1dd734d3de6e31754caf85d6fe77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c3d1bd65302101b27650d91d6eb9bc535bdcf68 --- /dev/null +++ b/marked/Rel-16/23_series/23205/67a1dd734d3de6e31754caf85d6fe77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a45b931287a929435cd80b3c76f5a7620dc6ba9fe992bc406072954b9be6518 +size 17076 diff --git a/marked/Rel-16/23_series/23205/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/marked/Rel-16/23_series/23205/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1b6ddf0d538dfd995d0ecb8926c0d0a87e10df6 --- /dev/null +++ b/marked/Rel-16/23_series/23205/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:518c367378bba234a3eacee4f47341a6c4593170d27a8206b0c384058c2fcd0c +size 17664 diff --git a/marked/Rel-16/23_series/23205/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-16/23_series/23205/694df81535f89c7bfb9ef0df6f130dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..856bac5bc1f1679382c138ca7dcb4d6ae06fe8a4 --- /dev/null +++ b/marked/Rel-16/23_series/23205/694df81535f89c7bfb9ef0df6f130dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:978fcfcf6ec546f9fabe22d4ba83f42300a49138431ad1506be0d27cab2a19bf +size 83465 diff --git a/marked/Rel-16/23_series/23205/6d6670b8e65d3ff8126e5ab9aeaffbd8_img.jpg b/marked/Rel-16/23_series/23205/6d6670b8e65d3ff8126e5ab9aeaffbd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..950c71645269b791715733466879f5025cbbe94d --- /dev/null +++ b/marked/Rel-16/23_series/23205/6d6670b8e65d3ff8126e5ab9aeaffbd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fd91aacc5ceea56a477268d59970ace0290cf15434b7ef776f20312a4ed570b +size 19720 diff --git a/marked/Rel-16/23_series/23205/6d67eee81b97a14e06a6fe57a95aff36_img.jpg b/marked/Rel-16/23_series/23205/6d67eee81b97a14e06a6fe57a95aff36_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d7d2e1e308c7e07825c3c2e58d3c5dc49937dd7 --- /dev/null +++ b/marked/Rel-16/23_series/23205/6d67eee81b97a14e06a6fe57a95aff36_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7992f2d44263315f0b55f5f452946b66de8c80c914e6e259bf6382a15093fd83 +size 81742 diff --git a/marked/Rel-16/23_series/23205/6e9d059430baba0c363e33749f68b107_img.jpg b/marked/Rel-16/23_series/23205/6e9d059430baba0c363e33749f68b107_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6aeba8dd18ac7553df689ca17ab753a735bd9dbf --- /dev/null +++ b/marked/Rel-16/23_series/23205/6e9d059430baba0c363e33749f68b107_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fac6bebbe32941ab6c3c7afb9cf220c614be42cc7d47f49233b2fc514f6a160 +size 97337 diff --git a/marked/Rel-16/23_series/23205/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg b/marked/Rel-16/23_series/23205/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9dc9fd7f003348935908dfb57e28f21c33e9ae10 --- /dev/null +++ b/marked/Rel-16/23_series/23205/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7995e04bbba7c7cf68b0b24cec7d31d0ed5aa8609c32d59cde0b88477a2b29e5 +size 51481 diff --git a/marked/Rel-16/23_series/23205/70a07cbdcf39ad922c4f80528f12bc46_img.jpg b/marked/Rel-16/23_series/23205/70a07cbdcf39ad922c4f80528f12bc46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6127162e89a8f5add83689bbb1b1799e24d5d2f4 --- /dev/null +++ b/marked/Rel-16/23_series/23205/70a07cbdcf39ad922c4f80528f12bc46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d56ec61b75783e980992de5fe0c92bc3a446c142e15f177ad9e6e2bf26ce9a4 +size 21215 diff --git a/marked/Rel-16/23_series/23205/7156cf400ef0e19f9d06a5d0549834a3_img.jpg b/marked/Rel-16/23_series/23205/7156cf400ef0e19f9d06a5d0549834a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b3804f16db6a924bfde3dc84c486981048e41dc8 --- /dev/null +++ b/marked/Rel-16/23_series/23205/7156cf400ef0e19f9d06a5d0549834a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2297223a9964104ae9935083e2ff55dfa8134f3b2435608122f4b48493795827 +size 21514 diff --git a/marked/Rel-16/23_series/23205/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-16/23_series/23205/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cf4e1a0e1be30a68f216985e236c5ae7218c7b0 --- /dev/null +++ b/marked/Rel-16/23_series/23205/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc25cba3ae5ee5c9246e13f014724a1de5ebf66697c8c7c5d6df12a00f766d63 +size 127966 diff --git a/marked/Rel-16/23_series/23205/72bc1a2b64dd6bac8285f560440c1218_img.jpg b/marked/Rel-16/23_series/23205/72bc1a2b64dd6bac8285f560440c1218_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b6a6eaf5a1640a7c12eb317a45d6ec589822b329 --- /dev/null +++ b/marked/Rel-16/23_series/23205/72bc1a2b64dd6bac8285f560440c1218_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73158b6985d2bc5b8b0ab542c0d608549b049f502be303e607448490b9693d2c +size 21008 diff --git a/marked/Rel-16/23_series/23205/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Rel-16/23_series/23205/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b057b529eed4d41c674e7c1f04224f41393e060d --- /dev/null +++ b/marked/Rel-16/23_series/23205/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33016b97eb2bd31c1f38e04ece18f78a915131ac266b8ec5eba0700ca9f071b3 +size 37884 diff --git a/marked/Rel-16/23_series/23205/77c78bfdbbee0e121808674b08fd7046_img.jpg b/marked/Rel-16/23_series/23205/77c78bfdbbee0e121808674b08fd7046_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a94213e9eeaef2905dab8b9da27415eee915604 --- /dev/null +++ b/marked/Rel-16/23_series/23205/77c78bfdbbee0e121808674b08fd7046_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f0c4733ba5f1401dbcaec4d0f4c4c0826b147c35d8a1dcdbdcee4774b6db63b +size 34731 diff --git a/marked/Rel-16/23_series/23205/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg b/marked/Rel-16/23_series/23205/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba3211dd35c2b809ece9c3bb22830e3f446c32d0 --- /dev/null +++ b/marked/Rel-16/23_series/23205/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:385f15f0fd3bd2f4116268e97f67ef17a3bbf1f7be882fcae5f69db358cb521d +size 57812 diff --git a/marked/Rel-16/23_series/23205/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/23_series/23205/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19949b38ef10db882d4fa53dcbe2a093a77c3409 --- /dev/null +++ b/marked/Rel-16/23_series/23205/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17ae617c8a5265926238a7b5dff72648e4dd6083d388c430b59248b4277680c9 +size 97795 diff --git a/marked/Rel-16/23_series/23205/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-16/23_series/23205/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b74d3ee4fb339a50ec5724cc7805e4029846ad63 --- /dev/null +++ b/marked/Rel-16/23_series/23205/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e2274e8aaa5389e463398c9ef495a8196335a8350ffc3d2ad8339ae0c1e2bfd6 +size 146032 diff --git a/marked/Rel-16/23_series/23205/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg b/marked/Rel-16/23_series/23205/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0345816debf8bd45b060627ebeec7c3fa5907e26 --- /dev/null +++ b/marked/Rel-16/23_series/23205/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c72755f158cd077aba18ea3b75704806522f0e243767bff58760296b7c7014dd +size 57237 diff --git a/marked/Rel-16/23_series/23205/820515db47ded68f5e0b625f4ec7d2c1_img.jpg b/marked/Rel-16/23_series/23205/820515db47ded68f5e0b625f4ec7d2c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e61284b5d7b4d1008fc29c55a1f77322dbda54fd --- /dev/null +++ b/marked/Rel-16/23_series/23205/820515db47ded68f5e0b625f4ec7d2c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d37388a34a33200a4e9f1be12682a2057029fa640ef92a3ff24986909a4cefc +size 23440 diff --git a/marked/Rel-16/23_series/23205/82b40cb8b2a5ac361973859400fa128a_img.jpg b/marked/Rel-16/23_series/23205/82b40cb8b2a5ac361973859400fa128a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3650ce8b1b323d25c8f89d9fcb2e45b1e430f69 --- /dev/null +++ b/marked/Rel-16/23_series/23205/82b40cb8b2a5ac361973859400fa128a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7c33d72bd57fa7ded0eebc8e269b6df338cec51a225a659dca8720c3de40d8d +size 22091 diff --git a/marked/Rel-16/23_series/23205/848073118eebfdbfdb9a60e3923fe0b3_img.jpg b/marked/Rel-16/23_series/23205/848073118eebfdbfdb9a60e3923fe0b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4bcf6bb59b0ba079fc6e897f39bd29001dee5880 --- /dev/null +++ b/marked/Rel-16/23_series/23205/848073118eebfdbfdb9a60e3923fe0b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99c6c044ff4f53de476a7e481533314bc39fee94a1bf3111aab25cc47acb9f29 +size 22082 diff --git a/marked/Rel-16/23_series/23205/868ef3e0abb37916a7af1e923995f329_img.jpg b/marked/Rel-16/23_series/23205/868ef3e0abb37916a7af1e923995f329_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdf6f55a7ac34baa7b64a320a68a7d8fd65aae40 --- /dev/null +++ b/marked/Rel-16/23_series/23205/868ef3e0abb37916a7af1e923995f329_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5f9d2fda4642b9591514d04dc45bc15590f672508f6a33e58bf8d91bdf7c7e8 +size 21016 diff --git a/marked/Rel-16/23_series/23205/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg b/marked/Rel-16/23_series/23205/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..705b638c31f1e74691fe78b9d7c5d8658eafb4ae --- /dev/null +++ b/marked/Rel-16/23_series/23205/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bf63a04afcb5230d668c04b8be3a2d36314ef4b23385eb6e7fc16b53a3f2574 +size 22149 diff --git a/marked/Rel-16/23_series/23205/86f61404a19a384d06a7b0b2c4e6937a_img.jpg b/marked/Rel-16/23_series/23205/86f61404a19a384d06a7b0b2c4e6937a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a33262b2d708037a6f67965831160a81dc322fc --- /dev/null +++ b/marked/Rel-16/23_series/23205/86f61404a19a384d06a7b0b2c4e6937a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3723e0252a8dea93ff94cccf71f8244d44243cdefc29413186deccdf974b7805 +size 21427 diff --git a/marked/Rel-16/23_series/23205/88b0f3f4393228e9ea4d6542aef7c399_img.jpg b/marked/Rel-16/23_series/23205/88b0f3f4393228e9ea4d6542aef7c399_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1ab91345e326bbdedced004004e80055eae7f7f --- /dev/null +++ b/marked/Rel-16/23_series/23205/88b0f3f4393228e9ea4d6542aef7c399_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be3b6facb446e5a02c3db305a94df5221d6c2e34eea0bc26884dea393db840c5 +size 21475 diff --git a/marked/Rel-16/23_series/23205/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-16/23_series/23205/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ab0a347caebfae0fbe23bb630d1d1468c941148 --- /dev/null +++ b/marked/Rel-16/23_series/23205/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:765e7f7be062ef469332a6c854cd164726f1944e65a785086957c00cb71b7f14 +size 631 diff --git a/marked/Rel-16/23_series/23205/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/23_series/23205/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e72c73d093d532cbbf976f3f836eb421e9b02d85 --- /dev/null +++ b/marked/Rel-16/23_series/23205/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d46a4795e775a6747e012d8c4a9323198d812485e696e18ca76f928fc15abeae +size 77071 diff --git a/marked/Rel-16/23_series/23205/8f8caebe58364416a2eda21039d8c7bf_img.jpg b/marked/Rel-16/23_series/23205/8f8caebe58364416a2eda21039d8c7bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1c3d3d585b182abb446e036dcf3cf6f2153faba --- /dev/null +++ b/marked/Rel-16/23_series/23205/8f8caebe58364416a2eda21039d8c7bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abbb475ce255ba86e6f24d5e83cfbde6fa72e0093227b7a5f577d32b1d05e978 +size 103035 diff --git a/marked/Rel-16/23_series/23205/907cc0e0bfee6288b926d1c38c232e5d_img.jpg b/marked/Rel-16/23_series/23205/907cc0e0bfee6288b926d1c38c232e5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5252f31628616fb1d3391608a234cc298e652717 --- /dev/null +++ b/marked/Rel-16/23_series/23205/907cc0e0bfee6288b926d1c38c232e5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d00618e4714d04cf5d632a8a19dec9f78763f81e81a24cc30ec7091f5739e5b +size 21466 diff --git a/marked/Rel-16/23_series/23205/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23205/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa5db730af1a64b2dccf0aebe4abc26725dd4323 --- /dev/null +++ b/marked/Rel-16/23_series/23205/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:343d4578fe8ac47cacf42a37b584c26d1195630fa9bfd85e7d1ee1d41365743f +size 87408 diff --git a/marked/Rel-16/23_series/23205/90ddf538ef276510e2b631f7b96654e6_img.jpg b/marked/Rel-16/23_series/23205/90ddf538ef276510e2b631f7b96654e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29e5aec44cce0dbf84012732a28db260e5c0bd93 --- /dev/null +++ b/marked/Rel-16/23_series/23205/90ddf538ef276510e2b631f7b96654e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:342c7cdfcb0134734c04c2e2611ea8e72138447f683d2d77764aa6da07aef38a +size 74709 diff --git a/marked/Rel-16/23_series/23205/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg b/marked/Rel-16/23_series/23205/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..32006730725cb5952f39f103a8fe183824219c84 --- /dev/null +++ b/marked/Rel-16/23_series/23205/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86dffc61af355f47689198f3f22ff61cec42cec8cc79bd8a939f22a28ac837fb +size 22192 diff --git a/marked/Rel-16/23_series/23205/92724c769da9d46b730fde1a6dccb023_img.jpg b/marked/Rel-16/23_series/23205/92724c769da9d46b730fde1a6dccb023_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42fb7d497e031e6f4a29c03a8acaabc5ea542a66 --- /dev/null +++ b/marked/Rel-16/23_series/23205/92724c769da9d46b730fde1a6dccb023_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c01e73360129c6a3a507b5810073d39df10806afb82ae9a5a712e8dd227f5279 +size 59321 diff --git a/marked/Rel-16/23_series/23205/977811d1c73b74f801be9f4c376694ca_img.jpg b/marked/Rel-16/23_series/23205/977811d1c73b74f801be9f4c376694ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1469d6ab3ed0dc80382efef0d483944f8d17d533 --- /dev/null +++ b/marked/Rel-16/23_series/23205/977811d1c73b74f801be9f4c376694ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76097d87c5c3111502c77d0ee11f84ee3a889a63954dea0ab00fc0d7b548d91a +size 43461 diff --git a/marked/Rel-16/23_series/23205/9b25cfd1657391070da4ca3e922b82b1_img.jpg b/marked/Rel-16/23_series/23205/9b25cfd1657391070da4ca3e922b82b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e1b7d95046f8e1953664526fd3cb112db787eb6 --- /dev/null +++ b/marked/Rel-16/23_series/23205/9b25cfd1657391070da4ca3e922b82b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:193c67b7768674873344b6ff54ce0e52c7fb6cac2b278efe441bca8e762a8777 +size 62399 diff --git a/marked/Rel-16/23_series/23205/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg b/marked/Rel-16/23_series/23205/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d54d6f2e9dfa5ae937babd8d1c0e058fb4ba9070 --- /dev/null +++ b/marked/Rel-16/23_series/23205/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b350e82753ff26958c89f0800e9a7d06fcb44c289dc24bcb957dee9b1e61b49 +size 69746 diff --git a/marked/Rel-16/23_series/23205/9b62a616c7a1097c5da57f001ab6dd64_img.jpg b/marked/Rel-16/23_series/23205/9b62a616c7a1097c5da57f001ab6dd64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6b5a3539c8eaa6cdb2ae10e3f25930a6ee1f2e8 --- /dev/null +++ b/marked/Rel-16/23_series/23205/9b62a616c7a1097c5da57f001ab6dd64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e9ea1cc00a1ca352f896011ac2e0e43959f232fe247726fa9bdaccb067f5bff +size 37347 diff --git a/marked/Rel-16/23_series/23205/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/23_series/23205/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd4b2bb19058ed3a2585ce624d5feb83560a5b7f --- /dev/null +++ b/marked/Rel-16/23_series/23205/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:118666d978a20b1ce436f1a5b6fa102aaa3a3c1797284666e5413e7e7d3e4344 +size 138619 diff --git a/marked/Rel-16/23_series/23205/9cb54072e43a6b6717eb16036a7640a2_img.jpg b/marked/Rel-16/23_series/23205/9cb54072e43a6b6717eb16036a7640a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac531952c24ec4d88bca8382dde04633ddbff544 --- /dev/null +++ b/marked/Rel-16/23_series/23205/9cb54072e43a6b6717eb16036a7640a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1b5c56d4db051b28420890a1dbdffcc7ddb182539dc5dfeecea61fe6d792531 +size 96728 diff --git a/marked/Rel-16/23_series/23205/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/marked/Rel-16/23_series/23205/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4c243112d4ab56875789ae99418f410d222ac50 --- /dev/null +++ b/marked/Rel-16/23_series/23205/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dda98977e52c862c2624fc28a02f6ee9cbebc711bdc2f69497a04149e383597d +size 42835 diff --git a/marked/Rel-16/23_series/23205/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/marked/Rel-16/23_series/23205/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..538f050319e4b477b4b7c04444aa6c394084f620 --- /dev/null +++ b/marked/Rel-16/23_series/23205/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8291df4ee2790bcd11cae65fb43ff05a1a5a82e836c47f8a964dc61c02f9bed4 +size 81095 diff --git a/marked/Rel-16/23_series/23205/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg b/marked/Rel-16/23_series/23205/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c650af6732f06033bb425abcf717c545114581f --- /dev/null +++ b/marked/Rel-16/23_series/23205/9e4f582a5d5f6742d1372956db0f8f0b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7986b9ba99b3c60b47f61c80ad343a4c8ce642dad33d3bbeda746e287eca660b +size 38864 diff --git a/marked/Rel-16/23_series/23205/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/23_series/23205/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b487de0b4b937f8b50e22fe58cdd3a3074ff6ef --- /dev/null +++ b/marked/Rel-16/23_series/23205/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3986ca2c6db599d79a3b6610aeeb39b0829a2fa4a997275aff5c8c1fbf384c19 +size 104447 diff --git a/marked/Rel-16/23_series/23205/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23205/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8dbdef3875b124a6833d33c66b0d13e56d13e2aa --- /dev/null +++ b/marked/Rel-16/23_series/23205/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c50dfdb11e5bafb442351831dc6f18662e77a2970c510ab1a4164d3fe43a29e6 +size 163972 diff --git a/marked/Rel-16/23_series/23205/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/23_series/23205/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88cc8cc4bc8904ffc4ef53d2888a02a4efc64159 --- /dev/null +++ b/marked/Rel-16/23_series/23205/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7c8100b2745ea50a50e6e9b24c4e4b318c903e45a9d0af608ea5e3593acf2a4 +size 57443 diff --git a/marked/Rel-16/23_series/23205/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Rel-16/23_series/23205/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..856a7007c913069ae5bedf64b8f77204710fba42 --- /dev/null +++ b/marked/Rel-16/23_series/23205/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:87d82a46035d5b6074b296876b3e686561b2302770fe5b54e2a683dbc1d4fb7e +size 170759 diff --git a/marked/Rel-16/23_series/23205/a2586540d49d5665489c8b5a273f86d3_img.jpg b/marked/Rel-16/23_series/23205/a2586540d49d5665489c8b5a273f86d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a31f23c5f583f73d7f2a4d467de4acca759eb2e3 --- /dev/null +++ b/marked/Rel-16/23_series/23205/a2586540d49d5665489c8b5a273f86d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27b337ec0e247529fc4a1b90ba4eebd9a1c81a51f78698b4c82744a60cbc77f1 +size 30948 diff --git a/marked/Rel-16/23_series/23205/a47713c2491e6ce619259ed2f196fd24_img.jpg b/marked/Rel-16/23_series/23205/a47713c2491e6ce619259ed2f196fd24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43eece7ec72a42f1870e8f7012bf98ecc9eca91f --- /dev/null +++ b/marked/Rel-16/23_series/23205/a47713c2491e6ce619259ed2f196fd24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:803661c7b7564b3b376cc6b93d1f94dec87744245f18af822906523262cd6fe4 +size 42080 diff --git a/marked/Rel-16/23_series/23205/a49d2de328d172709cd326a374415d6d_img.jpg b/marked/Rel-16/23_series/23205/a49d2de328d172709cd326a374415d6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e995faab912c170367bbf3014efd57c201c562b3 --- /dev/null +++ b/marked/Rel-16/23_series/23205/a49d2de328d172709cd326a374415d6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52f2a98efc978afcd7048c1e557b854ea0f5c056ddf2a442b9c1b076bbc7875f +size 33198 diff --git a/marked/Rel-16/23_series/23205/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/marked/Rel-16/23_series/23205/a7450c80e88ad3f6ca1427ad84020998_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6b539b4ae62147d92fa80683179aa57a594127b --- /dev/null +++ b/marked/Rel-16/23_series/23205/a7450c80e88ad3f6ca1427ad84020998_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49cd4d23570a3d5f4f6d5cc344faaeb8fe38d116d830a7fd160b7b427e1c7421 +size 35360 diff --git a/marked/Rel-16/23_series/23205/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Rel-16/23_series/23205/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9865d767adcb442f2ae9919050b3baa19ca8de7c --- /dev/null +++ b/marked/Rel-16/23_series/23205/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3649ca197798c561beb6793bb9d2fdc096a1b117c116a0a3fb6ae55d8e84ae92 +size 78011 diff --git a/marked/Rel-16/23_series/23205/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/23_series/23205/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce9658a631fd820372672403833e4714b227bbdb --- /dev/null +++ b/marked/Rel-16/23_series/23205/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d16482ba176a1cf8756181d261a2db52b8c0b6543400fd683769656c01a9faf1 +size 148651 diff --git a/marked/Rel-16/23_series/23205/aeb2a26a07219661191294dba528067a_img.jpg b/marked/Rel-16/23_series/23205/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66469d27fdf72ba064f643f7ff497b25fc52535b --- /dev/null +++ b/marked/Rel-16/23_series/23205/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c09e2b7fc346fb36c8f617a6df157a6067d615b510d1cd187a63ebb17ea5caf6 +size 22130 diff --git a/marked/Rel-16/23_series/23205/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/marked/Rel-16/23_series/23205/af6be343f0c0a8f155f965dcf337b8af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a01417d448e2c1ed668e50003c3e22a5d1d7f7e --- /dev/null +++ b/marked/Rel-16/23_series/23205/af6be343f0c0a8f155f965dcf337b8af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:988ebcb879f32293421b23a632050868da5db4c96352d9740cc5b0cc40b84765 +size 26015 diff --git a/marked/Rel-16/23_series/23205/b30e390cb591b39482fe7ecd4c4cd84b_img.jpg b/marked/Rel-16/23_series/23205/b30e390cb591b39482fe7ecd4c4cd84b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b4fa864bbe9767ad0ed4e42a90c7bdbe072f144 --- /dev/null +++ b/marked/Rel-16/23_series/23205/b30e390cb591b39482fe7ecd4c4cd84b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d48e1274cf15d1fcaf089a4a151008179812e83635c796db364ba7ed8cfa89e +size 116268 diff --git a/marked/Rel-16/23_series/23205/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/23_series/23205/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35dfa997aa6cbf48eb5d1f683c45ef5adc1e5963 --- /dev/null +++ b/marked/Rel-16/23_series/23205/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0704a76657fd35800250a60ece028a08df80c876334f19f37e70bd90566f8e28 +size 33218 diff --git a/marked/Rel-16/23_series/23205/b44f89b176c971c7dd264c07bfef2c2a_img.jpg b/marked/Rel-16/23_series/23205/b44f89b176c971c7dd264c07bfef2c2a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0b2b76b698f89e4dd3d4cbe781d4f11418f42aa --- /dev/null +++ b/marked/Rel-16/23_series/23205/b44f89b176c971c7dd264c07bfef2c2a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c76dbd555acc79d43898b2faad8db0fe43422eda29cc33ae768dc70268aa0a1b +size 28296 diff --git a/marked/Rel-16/23_series/23205/b4c825454b7a89b4d7744e4f45521174_img.jpg b/marked/Rel-16/23_series/23205/b4c825454b7a89b4d7744e4f45521174_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3347acc9f369a153e62b7413288ad245aa614c9b --- /dev/null +++ b/marked/Rel-16/23_series/23205/b4c825454b7a89b4d7744e4f45521174_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7994ae8ad0eeee55f3bd749d530ba023500f571df792980000a0d80e83b98a4a +size 70685 diff --git a/marked/Rel-16/23_series/23205/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/23_series/23205/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac99873ea92edd3fad34a1bf60bbb4b7289f7fe5 --- /dev/null +++ b/marked/Rel-16/23_series/23205/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6147ec1a9be5df93d5d7ab0a39ad54c7da68469edb36e907ca6c2dc604131c00 +size 81284 diff --git a/marked/Rel-16/23_series/23205/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-16/23_series/23205/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0e9cd55e9f2c1c83a0c1fc9196c4863d041027e --- /dev/null +++ b/marked/Rel-16/23_series/23205/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:098c1cfc154edba7a830d5bfe4b71d0413f5a73ef16335b5ac9e91c25c997ba5 +size 63674 diff --git a/marked/Rel-16/23_series/23205/c24b21874de17e073506dd8797e4e45a_img.jpg b/marked/Rel-16/23_series/23205/c24b21874de17e073506dd8797e4e45a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5036b48738486fbc2af1490af0f64d4aac857cbb --- /dev/null +++ b/marked/Rel-16/23_series/23205/c24b21874de17e073506dd8797e4e45a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3c86550372d47e9188437f4d12202a36a4d0326aaaa1be9e8bcca35c315fcd2 +size 27130 diff --git a/marked/Rel-16/23_series/23205/c649cad02e45d7d9a16f3f5bdb332219_img.jpg b/marked/Rel-16/23_series/23205/c649cad02e45d7d9a16f3f5bdb332219_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c68dbe3851c750f98d1ca7c64cb129b9a8317ccb --- /dev/null +++ b/marked/Rel-16/23_series/23205/c649cad02e45d7d9a16f3f5bdb332219_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:147cdedf1db5c82ca593db1b624c63a79dd57d06b05d959ac64559d6b0e5ff9c +size 111096 diff --git a/marked/Rel-16/23_series/23205/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/23_series/23205/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03fecf3ec817bdf0c8f0b89b243183ad591fcfd5 --- /dev/null +++ b/marked/Rel-16/23_series/23205/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3a033e0d4a95db5cb9dd24ec737a2715a95080e39e49bc410abeb6c7819c492 +size 91741 diff --git a/marked/Rel-16/23_series/23205/c9bcc9f954279dd8f99cdcb0f41fff4a_img.jpg b/marked/Rel-16/23_series/23205/c9bcc9f954279dd8f99cdcb0f41fff4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0689a0b0a82d93f72713b27a1ed177ed02fc9de --- /dev/null +++ b/marked/Rel-16/23_series/23205/c9bcc9f954279dd8f99cdcb0f41fff4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b9c00a1492527f2f92468373058a755b43f96b250c1711aa42ee99cd3723a2a +size 20456 diff --git a/marked/Rel-16/23_series/23205/cc7baa8e5118f4b42c01166637c738ea_img.jpg b/marked/Rel-16/23_series/23205/cc7baa8e5118f4b42c01166637c738ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42c7c6e6c2afbd3e6d0e8a5544862d105333a90f --- /dev/null +++ b/marked/Rel-16/23_series/23205/cc7baa8e5118f4b42c01166637c738ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ec19aaf6ca76c2a2c0ff629495a3917e4741f379580e4f763065db22e7d046a +size 86620 diff --git a/marked/Rel-16/23_series/23205/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/marked/Rel-16/23_series/23205/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..348adc03a4b3e9645694061ebe58abe30fe07d9f --- /dev/null +++ b/marked/Rel-16/23_series/23205/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e126b8ab3b8d6374360a1159933f20d02c9334d1f15479ffa9d991caa2c123aa +size 127549 diff --git a/marked/Rel-16/23_series/23205/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/23_series/23205/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cadd6696707980a6bc3a551cf6369a961e33456d --- /dev/null +++ b/marked/Rel-16/23_series/23205/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7674cac4c5937a809ac9d7e28389961c67edf8518d35c83f3641181bb8f78ab6 +size 36977 diff --git a/marked/Rel-16/23_series/23205/d2417b04116c354deccb25d98a84a0fb_img.jpg b/marked/Rel-16/23_series/23205/d2417b04116c354deccb25d98a84a0fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..178dc637660f3206e361116196cfb93c8c90973c --- /dev/null +++ b/marked/Rel-16/23_series/23205/d2417b04116c354deccb25d98a84a0fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6752f42b6cb52c6f51bf871464d7bdee030060e5792d925dc0c818a83b9db95 +size 69451 diff --git a/marked/Rel-16/23_series/23205/d244183a8ff3d94b0dcf30140f51020d_img.jpg b/marked/Rel-16/23_series/23205/d244183a8ff3d94b0dcf30140f51020d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6378ad8d0ddf04269bb169e5568bcab6317dd2b8 --- /dev/null +++ b/marked/Rel-16/23_series/23205/d244183a8ff3d94b0dcf30140f51020d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdb2d9002381f528b713fceeb3c839d0e0e168b4e8449eb0ea3b83fa16e8b8ee +size 22527 diff --git a/marked/Rel-16/23_series/23205/d79d33da852cb7bca3e87b400a15c3e8_img.jpg b/marked/Rel-16/23_series/23205/d79d33da852cb7bca3e87b400a15c3e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7995d3fa58bc8bd108ecbba86abda69b2023e7a --- /dev/null +++ b/marked/Rel-16/23_series/23205/d79d33da852cb7bca3e87b400a15c3e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74a79af6fc59984d3ac308d3f4fbc7780e60d07a4d85454386403248ed0d978d +size 63077 diff --git a/marked/Rel-16/23_series/23205/d9638e837004a4e09dbbc50b8aecbd5f_img.jpg b/marked/Rel-16/23_series/23205/d9638e837004a4e09dbbc50b8aecbd5f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d468843515405b786c7195b54d4cfee1354960d2 --- /dev/null +++ b/marked/Rel-16/23_series/23205/d9638e837004a4e09dbbc50b8aecbd5f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02cbaa1cacdcaaff1c871877ea74ddb87e667f5f879f119c722c841542df894a +size 107448 diff --git a/marked/Rel-16/23_series/23205/d9c0a780cd22626253dab4aa41699e2f_img.jpg b/marked/Rel-16/23_series/23205/d9c0a780cd22626253dab4aa41699e2f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5898da41d95884472f64d45ab69f2f1870e41621 --- /dev/null +++ b/marked/Rel-16/23_series/23205/d9c0a780cd22626253dab4aa41699e2f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdd00797b19c735308a45030dface1a897b92743f4bb1d23fac5132d730f5b59 +size 88411 diff --git a/marked/Rel-16/23_series/23205/d9d41a512d5ad50bad281dba2f0061b0_img.jpg b/marked/Rel-16/23_series/23205/d9d41a512d5ad50bad281dba2f0061b0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28a94cc4eae561dcbcc9a6130491b3fd4ccd7e7b --- /dev/null +++ b/marked/Rel-16/23_series/23205/d9d41a512d5ad50bad281dba2f0061b0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:856fbd7040fd76fbf1e7147b3e53014d60496995faffa40d877ab3b5f8494cc6 +size 16546 diff --git a/marked/Rel-16/23_series/23205/da85343976fdbb19f866d9ddbdad0eae_img.jpg b/marked/Rel-16/23_series/23205/da85343976fdbb19f866d9ddbdad0eae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e17dcbf65ccd650afdd0b114c6d2b0539e7c5928 --- /dev/null +++ b/marked/Rel-16/23_series/23205/da85343976fdbb19f866d9ddbdad0eae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a07470208b85d87f6b3861abd25a528520028f4712a3a434dc7993841318e7bc +size 156016 diff --git a/marked/Rel-16/23_series/23205/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/marked/Rel-16/23_series/23205/dbbc0baac7341cda76cc4f8355dce23f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a74b5a9634c507638aeee11e28ddba179e23085 --- /dev/null +++ b/marked/Rel-16/23_series/23205/dbbc0baac7341cda76cc4f8355dce23f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:935efc4b817aa59f6d7459c4e7bb82d1d8b4a35c2bc358d651ce1b0b9923fe90 +size 71066 diff --git a/marked/Rel-16/23_series/23205/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/Rel-16/23_series/23205/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd6f3438c66c0119d954baf13a1167d964b49e9d --- /dev/null +++ b/marked/Rel-16/23_series/23205/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfde8203f69d945eb0124ad38c6b70c28dd6e068d3f7001957c8e5b7fc13eb38 +size 79938 diff --git a/marked/Rel-16/23_series/23205/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23205/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad3b3584342432c17bd4505feb9c63db5518e040 --- /dev/null +++ b/marked/Rel-16/23_series/23205/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30225b1d1baff8c9bbeca621ebaf8f93ce68b1022cbb19745fcd515988c58adb +size 129379 diff --git a/marked/Rel-16/23_series/23205/ddcdc1712375261ba1d89165fdf12aa6_img.jpg b/marked/Rel-16/23_series/23205/ddcdc1712375261ba1d89165fdf12aa6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9088da85aa49e80c2d532ee208db5fac979eaa8 --- /dev/null +++ b/marked/Rel-16/23_series/23205/ddcdc1712375261ba1d89165fdf12aa6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2419eba68fcba148d7c2f57bded253f1ebed54bf0e9b61cf6fdfbfaa9d3f89ff +size 31453 diff --git a/marked/Rel-16/23_series/23205/ddee3e67e0dfc22e25188fa635a19558_img.jpg b/marked/Rel-16/23_series/23205/ddee3e67e0dfc22e25188fa635a19558_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6027cdad75f6f92ad158690831eb9a419f20d50a --- /dev/null +++ b/marked/Rel-16/23_series/23205/ddee3e67e0dfc22e25188fa635a19558_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7c85824553e73165d804e7aa6e59fd70d372952e1b00be49fd4f449822d43cc +size 55829 diff --git a/marked/Rel-16/23_series/23205/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg b/marked/Rel-16/23_series/23205/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e6201e0bf3cdac4b4affb20fae864330c49ce03 --- /dev/null +++ b/marked/Rel-16/23_series/23205/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f2265e0c3b8a1862612ed2f073a9d2ef2d76eaec1dbae926a4a3d0c4def4871 +size 122357 diff --git a/marked/Rel-16/23_series/23205/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/23_series/23205/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8b68f51ad6d9bd3fe87a8daac46c9a798ed6bb1 --- /dev/null +++ b/marked/Rel-16/23_series/23205/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:797dca735385ad59c6bbd1bcec678343181b6c4b4c4c9388a8dccb9010d635df +size 227794 diff --git a/marked/Rel-16/23_series/23205/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/marked/Rel-16/23_series/23205/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a21ecad11e38559a03f432e99e596cceb9c29659 --- /dev/null +++ b/marked/Rel-16/23_series/23205/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27bfe1a96208cdbb2091b6ecb4257a3bac7226e1d914aa811706adbb47c0bb9c +size 115488 diff --git a/marked/Rel-16/23_series/23205/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23205/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26d0e1964545c6c248148c14f54f2adf790319f3 --- /dev/null +++ b/marked/Rel-16/23_series/23205/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26984fc650b1bfd9d079d90f2b2d8706f14abbcf171ec91929bf23d0e7035cfe +size 72673 diff --git a/marked/Rel-16/23_series/23205/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-16/23_series/23205/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4af5026b83bc42da47ead9a51a08e62c702dd1d7 --- /dev/null +++ b/marked/Rel-16/23_series/23205/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c601d0101f666376aa9217f5e3994caae9c29170f13bac8d159b07bb84161554 +size 73641 diff --git a/marked/Rel-16/23_series/23205/e699312f10b7831b388e6c6a5e7032ee_img.jpg b/marked/Rel-16/23_series/23205/e699312f10b7831b388e6c6a5e7032ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5914881757f6d0607f2380d40d37ce63790d151 --- /dev/null +++ b/marked/Rel-16/23_series/23205/e699312f10b7831b388e6c6a5e7032ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8036c1043779448d8edbb7cde67f880161241cb592304e07bd8d44afde66c73 +size 25557 diff --git a/marked/Rel-16/23_series/23205/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-16/23_series/23205/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6d66ac8e4f82364f57c0c2c3f9e63ff947418b7 --- /dev/null +++ b/marked/Rel-16/23_series/23205/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:007fe01f0a5273e6564f5afd455d39eb7b0444840608d6b7077b98bb42ab8350 +size 46631 diff --git a/marked/Rel-16/23_series/23205/eabcb2f8b9acedb194571d5bc734b463_img.jpg b/marked/Rel-16/23_series/23205/eabcb2f8b9acedb194571d5bc734b463_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f37aef082fa9ea1876c41d91da1093c262f16220 --- /dev/null +++ b/marked/Rel-16/23_series/23205/eabcb2f8b9acedb194571d5bc734b463_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2c517cb666a9ce919b2bef19db9f560aa7097f3aa76e3a11d3fdf1793fe6dfe +size 100727 diff --git a/marked/Rel-16/23_series/23205/eb450c92214e8409c1e0f0846e30d876_img.jpg b/marked/Rel-16/23_series/23205/eb450c92214e8409c1e0f0846e30d876_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97e4119819faa0ff3cb69fb2d9f4b85d63a1a69d --- /dev/null +++ b/marked/Rel-16/23_series/23205/eb450c92214e8409c1e0f0846e30d876_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:791d7a87c4c1d01fc0857d12c0dfcbfbbf9d3ba7dd913b438ee8e0900884b13a +size 53742 diff --git a/marked/Rel-16/23_series/23205/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg b/marked/Rel-16/23_series/23205/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..007a0dd73120ceddfa375e92df71a94d52ac4f2b --- /dev/null +++ b/marked/Rel-16/23_series/23205/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13652eff2eb99acbe4d3c448dbb7125c65ebb135844bc2392383a1e46257afea +size 87303 diff --git a/marked/Rel-16/23_series/23205/f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg b/marked/Rel-16/23_series/23205/f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4fd2dc0a73cdd7f4900f8b700f07a05c6840bd2 --- /dev/null +++ b/marked/Rel-16/23_series/23205/f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23e922b7f83c47eeaef8d9dfd69947d335afc568c74fa3f7c10646eeba031303 +size 21429 diff --git a/marked/Rel-16/23_series/23205/f23879f003c58b57f690e2dc6c95816a_img.jpg b/marked/Rel-16/23_series/23205/f23879f003c58b57f690e2dc6c95816a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f90089a881db6ab8932fcc6c5b0cce12d0c9be0b --- /dev/null +++ b/marked/Rel-16/23_series/23205/f23879f003c58b57f690e2dc6c95816a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61499ebefda1e33b507c7a7ffa4ff477c916f0ffb1f94b498288db10a5e58324 +size 34766 diff --git a/marked/Rel-16/23_series/23205/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg b/marked/Rel-16/23_series/23205/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8aae858f033bffecaa22e504cb9131af28ee4130 --- /dev/null +++ b/marked/Rel-16/23_series/23205/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2acd2ba2a5e911d874e686cbbb9c7d0a14d1d6059348dd883a12c4bfbed6bc7f +size 92555 diff --git a/marked/Rel-16/23_series/23205/f89631cc38aa971e8d15cbffe28f1183_img.jpg b/marked/Rel-16/23_series/23205/f89631cc38aa971e8d15cbffe28f1183_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d55473392ea5006cb1e1fd73d3cbbdcc0a4607ca --- /dev/null +++ b/marked/Rel-16/23_series/23205/f89631cc38aa971e8d15cbffe28f1183_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:daf5a9c9e50541bf62e38532a9545fdcf3b912f32bd59bfd0863e9411f5661c2 +size 18569 diff --git a/marked/Rel-16/23_series/23205/f99313b06c15e9882079b773ce50a7b2_img.jpg b/marked/Rel-16/23_series/23205/f99313b06c15e9882079b773ce50a7b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9e1ebc2f59edb97724a171abc04e9b1d4cbd1f8 --- /dev/null +++ b/marked/Rel-16/23_series/23205/f99313b06c15e9882079b773ce50a7b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa712388a5882855dba1e87e865bb3afc08beab97a252fd425d5e69547d2958f +size 109256 diff --git a/marked/Rel-16/23_series/23205/fb73a07d61dc5c47709b9802b894d716_img.jpg b/marked/Rel-16/23_series/23205/fb73a07d61dc5c47709b9802b894d716_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2191adaa6752705cc93bd13d227847a48a77de4a --- /dev/null +++ b/marked/Rel-16/23_series/23205/fb73a07d61dc5c47709b9802b894d716_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d9f0713180e5f39c4af5df6fc019b089a52b87714d8d7aa164a12297e3bf589 +size 29656 diff --git a/marked/Rel-16/23_series/23205/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg b/marked/Rel-16/23_series/23205/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a6940991e2355a5ecec3524816828f77e90517e --- /dev/null +++ b/marked/Rel-16/23_series/23205/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a8c82efb90d783766b8374b3fd571b826a4f2fc5c48f1f24e20c573605021ca +size 41106 diff --git a/marked/Rel-16/23_series/23205/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-16/23_series/23205/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..077f74c6c6cdc1a77247875d19ba39b5062e96eb --- /dev/null +++ b/marked/Rel-16/23_series/23205/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee765d59ab00ad522ed64cae6bbc2f2027811819fea67b208ca063dbae0dacf7 +size 61170 diff --git a/marked/Rel-16/23_series/23205/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-16/23_series/23205/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0aa15f4534ffe24e3929354346efa56f81a0937 --- /dev/null +++ b/marked/Rel-16/23_series/23205/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e07530a43220c2a06538becf34f32995d03fbc8fa23e70d22858db45e287a761 +size 69746 diff --git a/marked/Rel-16/23_series/23205/fd76efce549d3713543bb5ed9b023c2e_img.jpg b/marked/Rel-16/23_series/23205/fd76efce549d3713543bb5ed9b023c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7f0ad50a0fbe35d37d3ff2918ae5016b6a1443b --- /dev/null +++ b/marked/Rel-16/23_series/23205/fd76efce549d3713543bb5ed9b023c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9924a84d17eaf8960ec00d3ad69e4231080b70433c9314f2ed3d4712a084273 +size 84064 diff --git a/marked/Rel-16/23_series/23205/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23205/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3ecfec84957d79dd97c44afa0c8490b916416e1 --- /dev/null +++ b/marked/Rel-16/23_series/23205/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d6d17bc2a252efcc9bdaa8df2f808e31f8a24943fdd419ad998b350ab6c0009 +size 62128 diff --git a/marked/Rel-16/23_series/23205/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Rel-16/23_series/23205/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90a5f81c998fadea84d522adb925c417b35f733a --- /dev/null +++ b/marked/Rel-16/23_series/23205/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af9ee2dba41ba3dddeff11466fcb3024962d0ed10c7c93eff2c4f7aabfd463e7 +size 109877 diff --git a/marked/Rel-16/23_series/23205/raw.md b/marked/Rel-16/23_series/23205/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d51ef039338f7eaec2a7c8616a73817cb61cb8e6 --- /dev/null +++ b/marked/Rel-16/23_series/23205/raw.md @@ -0,0 +1,9380 @@ +# Contents + +| | | +|------------------------------------------------------------------------|----| +| Foreword ..... | 15 | +| 1 Scope..... | 16 | +| 2 References..... | 16 | +| 3 Symbols and abbreviations ..... | 18 | +| 3.1 Symbols..... | 18 | +| 3.2 Abbreviations ..... | 18 | +| 3.3 Definitions..... | 19 | +| 4 Main Concepts ..... | 19 | +| 4.1 General ..... | 19 | +| 4.2 Bearer-Independent Call Control ..... | 19 | +| 4.3 H.248/MEGACO..... | 20 | +| 5 General Circuit Switched Core Network Domain Architecture ..... | 20 | +| 5.1 Logical Architecture..... | 20 | +| 5.1.1 CS Core Network Nodes ..... | 20 | +| 5.1.1.1 MSC Server..... | 20 | +| 5.1.1.2 GMSC Server..... | 20 | +| 5.1.1.3 Media Gateway..... | 20 | +| 5.1.2 CS Core Network Interfaces and Reference Points..... | 21 | +| 5.1.2.1 Mc Interface..... | 21 | +| 5.1.2.2 Nc Interface..... | 21 | +| 5.1.2.3 Nb Interface ..... | 21 | +| 5.2 Network Interworking..... | 21 | +| 5.2.1 Interworking on the Nc Reference Point..... | 21 | +| 5.2.2 Interworking on the Nb Reference Point..... | 21 | +| 6 Call Establishment ..... | 21 | +| 6.1 Basic Mobile Originating Call ..... | 21 | +| 6.1.1 Forward bearer establishment..... | 21 | +| 6.1.1.1 MGW selection..... | 21 | +| 6.1.1.2 Initial addressing..... | 22 | +| 6.1.1.3 Network side bearer establishment..... | 22 | +| 6.1.1.4 Access bearer assignment..... | 22 | +| 6.1.1.5 Framing protocol initialisation..... | 22 | +| 6.1.1.6 Confirmation of bearer establishment..... | 22 | +| 6.1.1.7 Through-Connection..... | 23 | +| 6.1.1.8 Interworking function ..... | 23 | +| 6.1.1.9 Codec handling ..... | 23 | +| 6.1.1.10 Voice Processing function ..... | 23 | +| 6.1.1.11 Failure handling in MSC server..... | 23 | +| 6.1.1.12 Example ..... | 23 | +| 6.1.2 Backward bearer establishment..... | 26 | +| 6.1.2.1 MGW selection..... | 26 | +| 6.1.2.2 Network side bearer establishment..... | 26 | +| 6.1.2.3 Initial addressing..... | 26 | +| 6.1.2.4 Access bearer assignment..... | 27 | +| 6.1.2.5 Framing protocol initialisation..... | 27 | +| 6.1.2.6 Confirmation of bearer establishment..... | 27 | +| 6.1.2.7 Through-Connection..... | 27 | +| 6.1.2.8 Interworking function ..... | 27 | +| 6.1.2.9 Codec handling ..... | 28 | +| 6.1.2.10 Voice Processing function ..... | 28 | +| 6.1.2.11 Failure handling in MSC server..... | 28 | +| 6.1.2.12 Example ..... | 28 | +| 6.1.3 Originating Call Establishment For Iu Interface on IP..... | 30 | +| 6.1.4 Forward bearer establishment with Trace Session Activation ..... | 31 | +| 6.1.4.1 Trace activation..... | 31 | + +| | | | +|------------|--------------------------------------------------------------|----| +| 6.1.4.2 | Example ..... | 32 | +| 6.1.5 | Originating Call Establishment for A interface over IP ..... | 34 | +| 6.2 | Basic Mobile Terminating Call..... | 35 | +| 6.2.1 | Forward bearer establishment..... | 35 | +| 6.2.1.1 | GMSC server ..... | 35 | +| 6.2.1.1.1 | MGW selection ..... | 35 | +| 6.2.1.1.2 | Initial addressing ..... | 36 | +| 6.2.1.1.3 | Outgoing side bearer establishment ..... | 36 | +| 6.2.1.1.4 | Incoming side bearer establishment ..... | 36 | +| 6.2.1.1.5 | Framing protocol initialisation ..... | 36 | +| 6.2.1.1.6 | Through-Connection ..... | 36 | +| 6.2.1.1.7 | Confirmation of bearer establishment..... | 36 | +| 6.2.1.1.8 | Voice Processing function..... | 37 | +| 6.2.1.1.9 | Failure handling in GMSC server ..... | 37 | +| 6.2.1.2 | MSC server ..... | 37 | +| 6.2.1.2.1 | Paging..... | 37 | +| 6.2.1.2.2 | Call setup..... | 37 | +| 6.2.1.2.3 | MGW selection ..... | 37 | +| 6.2.1.2.4 | Network side bearer establishment ..... | 37 | +| 6.2.1.2.5 | Access bearer assignment..... | 37 | +| 6.2.1.2.6 | Framing protocol initialisation ..... | 38 | +| 6.2.1.2.7 | Called party alerting ..... | 38 | +| 6.2.1.2.8 | Called party answer..... | 38 | +| 6.2.1.2.9 | Through-Connection ..... | 38 | +| 6.2.1.2.10 | Interworking function..... | 39 | +| 6.2.1.2.11 | Codec handling..... | 39 | +| 6.2.1.2.12 | Voice Processing function..... | 39 | +| 6.2.1.2.13 | Failure handling in MSC server ..... | 39 | +| 6.2.1.2.14 | Example..... | 39 | +| 6.2.2 | Backward bearer establishment..... | 42 | +| 6.2.2.1 | GMSC server ..... | 42 | +| 6.2.2.1.1 | MGW selection ..... | 42 | +| 6.2.2.1.2 | Outgoing side bearer establishment ..... | 42 | +| 6.2.2.1.3 | Initial addressing ..... | 42 | +| 6.2.2.1.4 | Incoming side bearer establishment ..... | 42 | +| 6.2.2.1.5 | Framing protocol initialisation ..... | 42 | +| 6.2.2.1.6 | Through-Connection ..... | 43 | +| 6.2.2.1.7 | Confirmation of bearer establishment..... | 43 | +| 6.2.2.1.8 | Voice Processing function..... | 43 | +| 6.2.2.1.9 | Failure handling in GMSC server ..... | 43 | +| 6.2.2.2 | MSC server ..... | 43 | +| 6.2.2.2.1 | Paging..... | 43 | +| 6.2.2.2.2 | Call setup..... | 43 | +| 6.2.2.2.3 | MGW selection ..... | 44 | +| 6.2.2.2.3 | Network side bearer establishment ..... | 44 | +| 6.2.2.2.4 | Access bearer assignment..... | 44 | +| 6.2.2.2.5 | Framing protocol initialisation ..... | 44 | +| 6.2.2.2.6 | Called party alerting ..... | 45 | +| 6.2.2.2.7 | Called party answer..... | 45 | +| 6.2.2.2.8 | Through-Connection ..... | 45 | +| 6.2.2.2.9 | Interworking function..... | 45 | +| 6.2.2.2.10 | Codec handling..... | 45 | +| 6.2.2.2.11 | Voice Processing function..... | 45 | +| 6.2.2.2.12 | Failure handling in MSC server ..... | 45 | +| 6.2.2.2.13 | Example..... | 45 | +| 6.2.3 | Terminating Call Establishment For Iu Interface on IP ..... | 49 | +| 6.2.4 | Terminating Call Establishment For A Interface over IP..... | 51 | +| 7 | Call Clearing ..... | 51 | +| 7.1 | Network Initiated..... | 52 | +| 7.1.1 | GMSC server ..... | 52 | +| 7.1.1.1 | Call clearing from the incoming side..... | 52 | + +| | | | +|-----------|------------------------------------------------------------------------|----| +| 7.1.1.2 | Call clearing to the outgoing side ..... | 52 | +| 7.1.2 | MSC server ..... | 52 | +| 7.1.2.1 | Call clearing from the network side ..... | 52 | +| 7.1.2.2 | Call clearing to the UE ..... | 52 | +| 7.1.2.3 | Example ..... | 53 | +| 7.2 | User Initiated ..... | 54 | +| 7.2.1 | Void ..... | 55 | +| 7.2.2 | MSC server ..... | 55 | +| 7.2.2.1 | all clearing from the UE ..... | 55 | +| 7.2.2.2 | Call clearing to the network side ..... | 55 | +| 7.2.2.3 | Example ..... | 55 | +| 7.3 | (G)MSC server Initiated ..... | 56 | +| 7.3.1 | GMSC server ..... | 56 | +| 7.3.1.1 | Call clearing to the destination side ..... | 56 | +| 7.3.1.2 | Call clearing to the originating side ..... | 56 | +| 7.3.2 | MSC server ..... | 57 | +| 7.3.2.1 | Call clearing to the UE ..... | 57 | +| 7.3.2.2 | Call clearing to the network side ..... | 57 | +| 7.3.2.3 | Example ..... | 57 | +| 7.4 | MGW Initiated ..... | 59 | +| 7.4.1 | GMSC server ..... | 59 | +| 7.4.1.1 | Bearer released on the destination side ..... | 59 | +| 7.4.1.2 | Bearer released on the originating side ..... | 59 | +| 7.4.2 | MSC server ..... | 59 | +| 7.4.2.1 | Bearer released on the access side ..... | 59 | +| 7.4.2.2 | Bearer released on the network side ..... | 59 | +| 7.4.2.3 | Example ..... | 59 | +| 7.5 | Call Clearing for Iu Interface on IP ..... | 61 | +| 8 | Handover/Relocation ..... | 63 | +| 8.1 | UMTS to UMTS ..... | 63 | +| 8.1.1 | Intra-MSC SRNS/SBSS Relocation ..... | 63 | +| 8.1.1.1 | Relocation Required ..... | 64 | +| 8.1.1.2 | Relocation Command/Relocation Detect ..... | 64 | +| 8.1.1.3 | Relocation Complete ..... | 64 | +| 8.1.1.4 | Interworking function ..... | 64 | +| 8.1.1.5 | Codec handling ..... | 64 | +| 8.1.1.6 | Voice Processing function ..... | 64 | +| 8.1.1.7 | Handling of multiple bearers (multicall) ..... | 64 | +| 8.1.1.8 | Failure Handling in MSC server ..... | 64 | +| 8.1.1.9 | Example ..... | 64 | +| 8.1.2 | Basic Inter-MSC SRNS/SBSS Relocation ..... | 67 | +| 8.1.2.1 | MSC-A/MGW-A ..... | 67 | +| 8.1.2.1.1 | Relocation Required ..... | 67 | +| 8.1.2.1.2 | Bearer establishment between MGW-A and MGW-B ..... | 67 | +| 8.1.2.1.3 | Relocation Command/Relocation Detect ..... | 67 | +| 8.1.2.1.4 | Relocation Complete ..... | 67 | +| 8.1.2.1.5 | Interworking function ..... | 67 | +| 8.1.2.1.6 | Codec handling ..... | 67 | +| 8.1.2.1.7 | Voice Processing function ..... | 67 | +| 8.1.2.1.8 | Handling of multiple bearers (multicall) ..... | 68 | +| 8.1.2.1.9 | Failure Handling in MSC server ..... | 68 | +| 8.1.2.2 | MSC-B/MGW-B ..... | 68 | +| 8.1.2.2.1 | MGW selection ..... | 68 | +| 8.1.2.2.2 | Bearer establishment towards RNC-B ..... | 68 | +| 8.1.2.2.3 | Bearer establishment between MGW-A and MGW-B ..... | 68 | +| 8.1.2.2.4 | Codec handling ..... | 68 | +| 8.1.2.2.5 | Voice Processing function ..... | 68 | +| 8.1.2.2.6 | Handling of multiple bearers (multicall) ..... | 68 | +| 8.1.2.2.7 | Failure Handling in MSC server ..... | 68 | +| 8.1.2.2.8 | Example ..... | 69 | +| 8.1.3 | Subsequent Inter-MSC SRNS/SBSS Relocation back to the Anchor MSC ..... | 71 | + +| | | | +|-----------|------------------------------------------------------------------------|----| +| 8.1.3.1 | MSC-A/MGW-A ..... | 71 | +| 8.1.3.1.1 | Relocation Request..... | 71 | +| 8.1.3.1.2 | Relocation Command/Relocation Detect..... | 71 | +| 8.1.3.1.3 | Relocation Complete..... | 72 | +| 8.1.3.1.4 | Interworking function..... | 72 | +| 8.1.3.1.5 | Codec handling..... | 72 | +| 8.1.3.1.6 | Voice Processing function..... | 72 | +| 8.1.3.1.7 | Handling of multiple bearers (multicall)..... | 72 | +| 8.1.3.1.8 | Failure Handling in MSC server ..... | 72 | +| 8.1.3.2 | MSC-B/MGW-B..... | 72 | +| 8.1.3.2.1 | Relocation Required..... | 72 | +| 8.1.3.2.2 | Relocation Complete..... | 72 | +| 8.1.3.2.3 | Release of bearer towards MGW-A..... | 72 | +| 8.1.3.2.4 | Handling of multiple bearers (multicall)..... | 73 | +| 8.1.3.2.5 | Example..... | 73 | +| 8.1.4 | Subsequent Inter- MSC SRNS/SBSS Relocation to a third MSC..... | 75 | +| 8.1.5 | SRNS/SBSS Relocation with Iu on IP ..... | 75 | +| 8.1.6 | Intra- MSC enhanced SRNS Relocation ..... | 76 | +| 8.1.6.1 | Introduction..... | 76 | +| 8.1.6.2 | Enhanced Relocation Complete Request..... | 76 | +| 8.1.6.3 | Enhanced Relocation Complete Confirm ..... | 77 | +| 8.1.6.4 | Interworking function ..... | 77 | +| 8.1.6.5 | Codec handling ..... | 77 | +| 8.1.6.6 | Voice Processing function ..... | 77 | +| 8.1.6.7 | Handling of multiple bearers (multicall) ..... | 77 | +| 8.1.6.8 | Failure Handling in MSC server..... | 77 | +| 8.1.6.9 | Example ..... | 77 | +| 8.1.7 | Intra- MSC enhanced SRNS Relocation with Iu on IP ..... | 79 | +| 8.2 | UMTS to GSM ..... | 80 | +| 8.2.1 | Intra- MSC UMTS to GSM Handover ..... | 80 | +| 8.2.1.1 | Relocation Required ..... | 80 | +| 8.2.1.2 | Handover Request Acknowledge..... | 81 | +| 8.2.1.3 | Relocation Command/Handover Detect ..... | 81 | +| 8.2.1.4 | Handover Complete ..... | 81 | +| 8.2.1.5 | Interworking function ..... | 81 | +| 8.2.1.6 | Voice Processing function ..... | 81 | +| 8.2.1.7 | Handling of multiple bearers (multicall) ..... | 81 | +| 8.2.1.8 | Failure Handling in MSC server..... | 81 | +| 8.2.1.9 | Example ..... | 81 | +| 8.2.1.10 | Intra- MSC UMTS to GSM Handover for A interface over IP ..... | 84 | +| 8.2.2 | Basic Inter- MSC UMTS to GSM Handover ..... | 85 | +| 8.2.2.1 | MSC-A/ MGW-A ..... | 85 | +| 8.2.2.1.1 | Bearer establishment between MGW-A and MGW-B ..... | 85 | +| 8.2.2.1.2 | Relocation Command/Handover Detect..... | 85 | +| 8.2.2.1.3 | Handover Complete..... | 86 | +| 8.2.2.1.4 | Interworking function..... | 86 | +| 8.2.2.1.5 | Voice Processing function..... | 86 | +| 8.2.2.1.6 | Handling of multiple bearers (multicall)..... | 86 | +| 8.2.2.1.7 | Failure Handling in MSC server ..... | 86 | +| 8.2.2.2 | MSC-B/MGW-B..... | 86 | +| 8.2.2.2.1 | MGW selection ..... | 86 | +| 8.2.2.2.2 | Bearer establishment towards BSC-B..... | 86 | +| 8.2.2.2.3 | Bearer establishment between MGW-A and MGW-B ..... | 86 | +| 8.2.2.2.4 | Voice Processing function..... | 86 | +| 8.2.2.2.5 | Failure Handling in MSC server ..... | 86 | +| 8.2.2.2.6 | Example..... | 87 | +| 8.2.2.3 | Basic Inter- MSC UMTS to GSM Handover for A Interface over IP ..... | 89 | +| 8.2.3 | Subsequent Inter- MSC UMTS to GSM Handover back to the Anchor MSC..... | 90 | +| 8.2.3.1 | MSC-A..... | 90 | +| 8.2.3.1.1 | Handover Request..... | 90 | +| 8.2.3.1.2 | Handover Request Acknowledge..... | 91 | +| 8.2.3.1.3 | Relocation Command/Handover Detect..... | 91 | + +| | | | +|-----------|-------------------------------------------------------------------------------------------------|-----| +| 8.2.3.1.4 | Handover Complete..... | 91 | +| 8.2.3.1.5 | Interworking function..... | 91 | +| 8.2.3.1.6 | Voice Processing function..... | 91 | +| 8.2.3.1.7 | Handling of multiple bearers (multicall)..... | 91 | +| 8.2.3.1.8 | Failure Handling in MSC server ..... | 91 | +| 8.2.3.2 | MSC-B ..... | 91 | +| 8.2.3.2.1 | Handover Complete..... | 91 | +| 8.2.3.2.2 | Release of bearer towards MGW-A ..... | 91 | +| 8.2.3.2.3 | Handling of multiple bearers (multicall)..... | 92 | +| 8.2.3.2.4 | Example..... | 92 | +| 8.2.3.3 | Subsequent Inter- MSC UMTS to GSM Handover back to the anchor MSC for A Interface over IP ..... | 94 | +| 8.2.4 | Subsequent Inter- MSC UMTS to GSM Handover to a third MSC..... | 95 | +| 8.3 | GSM to UMTS ..... | 95 | +| 8.3.1 | Intra- MSC GSM to UMTS Handover ..... | 96 | +| 8.3.1.1 | Handover Required ..... | 96 | +| 8.3.1.2 | Handover Command/Relocation Detect ..... | 96 | +| 8.3.1.3 | Relocation Complete..... | 96 | +| 8.3.1.4 | Interworking function ..... | 96 | +| 8.3.1.5 | Codec handling ..... | 96 | +| 8.3.1.6 | Voice Processing function ..... | 96 | +| 8.3.1.7 | Failure Handling in MSC server ..... | 96 | +| 8.3.1.8 | Example ..... | 96 | +| 8.3.2 | Basic Inter- MSC GSM to UMTS Handover ..... | 98 | +| 8.3.2.1 | MSC-A..... | 99 | +| 8.3.2.1.1 | Handover Required ..... | 99 | +| 8.3.2.1.2 | Bearer establishment between MGW-A and MGW-B ..... | 99 | +| 8.3.2.1.3 | Handover Command/Handover Detect ..... | 99 | +| 8.3.2.1.4 | Handover Complete..... | 99 | +| 8.3.2.1.5 | Interworking function..... | 99 | +| 8.3.2.1.6 | Codec handling..... | 99 | +| 8.3.2.1.7 | Voice Processing function..... | 99 | +| 8.3.2.1.8 | Failure Handling in MSC server ..... | 100 | +| 8.3.2.2 | MSC-B ..... | 100 | +| 8.3.2.2.1 | MGW selection ..... | 100 | +| 8.3.2.2.2 | Bearer establishment towards RNC-B ..... | 100 | +| 8.3.2.2.3 | Bearer establishment between MGW-A and MGW-B ..... | 100 | +| 8.3.2.2.4 | Codec handling..... | 100 | +| 8.3.2.2.5 | Voice Processing function..... | 100 | +| 8.3.2.2.6 | Failure Handling in MSC server ..... | 100 | +| 8.3.2.2.7 | Example..... | 101 | +| 8.3.3 | Subsequent Inter- MSC GSM to UMTS Handover back to the Anchor MSC..... | 103 | +| 8.3.3.1 | MSC-A..... | 103 | +| 8.3.3.1.1 | Handover Request ..... | 103 | +| 8.3.3.1.2 | Handover Command/Relocation Detect..... | 104 | +| 8.3.3.1.3 | Relocation Complete ..... | 104 | +| 8.3.3.1.4 | Interworking function..... | 104 | +| 8.3.3.1.5 | Codec handling..... | 104 | +| 8.3.3.1.6 | Voice Processing function..... | 104 | +| 8.3.3.1.7 | Failure Handling in MSC server ..... | 104 | +| 8.3.3.2 | MSC-B / MGW-B..... | 104 | +| 8.3.3.2.1 | Handover Required ..... | 104 | +| 8.3.3.2.2 | Handover Complete..... | 105 | +| 8.3.3.2.3 | Release of bearer towards MGW-A ..... | 105 | +| 8.3.3.2.4 | Example..... | 105 | +| 8.3.4 | Subsequent Inter- MSC GSM to UMTS Handover to a third MSC..... | 107 | +| 8.3.5 | GSM to UMTS Handover with Iu on IP ..... | 108 | +| 8.4 | GSM to GSM ..... | 109 | +| 8.4.1 | Intra- MSC Inter- BSS GSM to GSM Handover..... | 109 | +| 8.4.1.1 | Handover Required ..... | 109 | +| 8.4.1.2 | Handover Request Acknowledge..... | 110 | +| 8.4.1.3 | Handover Command/Handover Detect..... | 110 | + +| | | | +|-----------|---------------------------------------------------------------------------------------------|-----| +| 8.4.1.4 | Handover Complete ..... | 110 | +| 8.4.1.5 | Interworking function ..... | 110 | +| 8.4.1.6 | Voice Processing function ..... | 110 | +| 8.4.1.7 | Failure Handling in MSC server..... | 110 | +| 8.4.1.8 | Example ..... | 111 | +| 8.4.1.9 | Intra-MSC GSM to GSM Handover for A interface over IP..... | 113 | +| 8.4.2 | Basic Inter-MSC GSM to GSM Handover..... | 114 | +| 8.4.2.1 | MSC-A / MGW-A ..... | 114 | +| 8.4.2.1.1 | Bearer establishment between MGW-A and MGW-B ..... | 114 | +| 8.4.2.1.2 | Handover Command/Handover Detect ..... | 114 | +| 8.4.2.1.3 | Handover Complete..... | 115 | +| 8.4.2.1.4 | Interworking function..... | 115 | +| 8.4.2.1.5 | Voice Processing function..... | 115 | +| 8.4.2.1.6 | Failure Handling in MSC server ..... | 115 | +| 8.4.2.2 | MSC-B / MGW-B..... | 115 | +| 8.4.2.2.1 | MGW selection ..... | 115 | +| 8.4.2.2.2 | Bearer establishment towards BSC-B..... | 115 | +| 8.4.2.2.3 | Bearer establishment between MGW-A and MGW-B ..... | 115 | +| 8.4.2.2.4 | Voice Processing function..... | 115 | +| 8.4.2.2.5 | Failure Handling in MSC server ..... | 115 | +| 8.4.2.2.6 | Example..... | 115 | +| 8.4.2.3 | Basic Inter-MSC GSM to GSM Handover for A Interface over IP..... | 118 | +| 8.4.3 | Subsequent Inter-MSC GSM to GSM Handover back to the Anchor MSC ..... | 119 | +| 8.4.3.1 | MSC-A / MGW-A ..... | 119 | +| 8.4.3.1.1 | Handover Request Acknowledge..... | 119 | +| 8.4.3.1.2 | Handover Command/Handover Detect ..... | 120 | +| 8.4.3.1.3 | Handover Complete..... | 120 | +| 8.4.3.1.4 | Interworking function..... | 120 | +| 8.4.3.1.5 | Voice Processing function..... | 120 | +| 8.4.3.1.6 | Failure Handling in MSC server ..... | 120 | +| 8.4.3.2 | MSC-B/MGW-B..... | 120 | +| 8.4.3.2.1 | Handover Complete..... | 120 | +| 8.4.3.2.2 | Release of bearer towards MGW-A ..... | 120 | +| 8.4.3.2.3 | Example..... | 120 | +| 8.4.3.3 | Subsequent Inter-MSC GSM to GSM Handover back to the anchor MSC for A Interface over IP ... | 124 | +| 8.4.4 | Subsequent GSM to GSM Handover to a third MSC..... | 124 | +| 8.4.5 | BSS Internal Handover..... | 125 | +| 8.4.5.1 | Introduction..... | 125 | +| 8.4.5.2 | Internal Handover Required..... | 125 | +| 8.4.5.3 | Internal Handover Command/Handover Detect ..... | 125 | +| 8.4.5.4 | Handover Complete ..... | 125 | +| 8.4.5.5 | Interworking function ..... | 125 | +| 8.4.5.6 | Voice Processing function ..... | 125 | +| 8.4.5.7 | Failure Handling in MSC server..... | 125 | +| 8.4.5.8 | Example for a successful BSS Internal Handover..... | 126 | +| 8.5 | Handling of GSM Services after UMTS to GSM Handover ..... | 128 | +| 9 | Compatibility Issues..... | 128 | +| 9.1 | Interworking with GERAN (A i/f)..... | 128 | +| 9.1.1 | Introduction ..... | 128 | +| 9.1.2 | A interface over TDM ..... | 129 | +| 10 | General (G)MSC server-MGW Procedures..... | 129 | +| 10.1 | MGW Unavailable ..... | 129 | +| 10.2 | MGW Available ..... | 130 | +| 10.3 | MGW Recovery ..... | 132 | +| 10.4 | (G)MSC server Recovery..... | 133 | +| 10.4.1 | General ..... | 133 | +| 10.4.2 | (G)MSC Server Restoration ..... | 133 | +| 10.5 | MGW Re-register..... | 133 | +| 10.6 | MGW Re-registration Ordered by (G)MSC server..... | 134 | +| 10.7 | Removal from Service of a Physical Termination ..... | 134 | + +| | | | +|------------|----------------------------------------------------------------------|-----| +| 10.8 | Restoration to Service of a Physical Termination..... | 135 | +| 10.9 | Audit of MGW ..... | 135 | +| 10.9.1 | Audit of Value ..... | 135 | +| 10.9.2 | Audit of Capability ..... | 136 | +| 10.10 | MGW Capability Change..... | 136 | +| 10.11 | Void..... | 137 | +| 10.12 | (G)MSC Server Out of service..... | 137 | +| 10.13 | MGW Resource Congestion Handling - Activate..... | 137 | +| 10.14 | MGW Resource Congestion Handling -Indication ..... | 137 | +| 10.15 | Control association monitoring..... | 138 | +| 10.16 | Hanging termination detection ..... | 138 | +| 11 | Identities..... | 139 | +| 11.1 | Bearer Address and Binding Reference ..... | 139 | +| 11.2 | MGW-Id..... | 139 | +| 11.3 | (G)MSC server Address..... | 139 | +| 12 | Operational Aspects..... | 139 | +| 12.1 | Charging..... | 139 | +| 13 | Interactions with Other Services ..... | 139 | +| 13.1 | Enhanced Multi-Level Precedence and Pre-emption service (eMLPP)..... | 140 | +| 13.2 | Call Deflection Service ..... | 140 | +| 13.2.1 | MGW selection and incoming side bearer establishment ..... | 140 | +| 13.2.2 | IU/A-interface release..... | 140 | +| 13.2.3 | Notification to the Calling Subscriber ..... | 140 | +| 13.2.4 | Initial addressing ..... | 140 | +| 13.2.5 | Establishment of bearer towards the forwarded-to subscriber ..... | 140 | +| 13.2.6 | Failure handling in MSC server ..... | 140 | +| 13.2.7 | Example ..... | 140 | +| 13.3 | Line identification Services..... | 142 | +| 13.3.1 | Calling Line Identification Presentation (CLIP) ..... | 142 | +| 13.3.2 | Calling Line Identification Restriction (CLIR) ..... | 142 | +| 13.3.3 | Connected Line Identification Presentation (COLP)..... | 142 | +| 13.3.4 | Connected Line Identification Restriction (COLR) ..... | 142 | +| 13.4 | Call Forwarding Services ..... | 142 | +| 13.4.1 | Call Forwarding Unconditional (CFU) ..... | 142 | +| 13.4.1.1 | MGW selection..... | 142 | +| 13.4.1.2 | Incoming side bearer establishment..... | 142 | +| 13.4.1.3 | Notification to the Calling Subscriber ..... | 142 | +| 13.4.1.4 | Initial addressing..... | 142 | +| 13.4.1.5 | Establishment of bearer towards the forwarded-to subscriber..... | 143 | +| 13.4.1.6 | Confirmation of bearer establishment..... | 143 | +| 13.4.1.7 | Failure handling in GMSC server..... | 143 | +| 13.4.1.8 | Example ..... | 143 | +| 13.4.2 | Call Forwarding on mobile subscriber Busy (CFB)..... | 144 | +| 13.4.2.1 | Network Determined User Busy (NDUB)..... | 144 | +| 13.4.2.1.1 | MGW selection ..... | 144 | +| 13.4.2.1.2 | Incoming side bearer establishment..... | 144 | +| 13.4.2.1.3 | Notification to the calling subscriber ..... | 144 | +| 13.4.2.1.4 | Initial addressing ..... | 145 | +| 13.4.2.1.5 | Establishment of bearer towards the forwarded-to subscriber..... | 145 | +| 13.4.2.1.5 | Confirmation of bearer establishment..... | 145 | +| 13.4.2.1.6 | Failure handling in MSC server ..... | 145 | +| 13.4.2.1.7 | Example..... | 145 | +| 13.4.2.2 | User Determined User Busy (UDUB) ..... | 146 | +| 13.4.2.2.1 | MGW selection ..... | 146 | +| 13.4.2.2.2 | Incoming side bearer establishment..... | 147 | +| 13.4.2.2.3 | IU/A-interface release ..... | 147 | +| 13.4.2.2.4 | Notification to the Calling Subscriber..... | 147 | +| 13.4.2.2.5 | Initial addressing ..... | 147 | +| 13.4.2.2.6 | Establishment of bearer towards the forwarded-to subscriber..... | 147 | +| 13.4.2.2.7 | Confirmation of bearer establishment..... | 147 | + +| | | | +|-------------|--------------------------------------------------------------------------------|-----| +| 13.4.2.2.8 | Failure handling in MSC server ..... | 148 | +| 13.4.2.2.9 | Example..... | 148 | +| 13.4.3 | Call Forwarding on No Reply (CFNRy) ..... | 149 | +| 13.4.3.1 | MGW selection and incoming side bearer establishment..... | 149 | +| 13.4.3.2 | IU/A-interface release..... | 149 | +| 13.4.3.3 | Notification to the Calling Subscriber ..... | 149 | +| 13.4.3.4 | Initial addressing..... | 150 | +| 13.4.3.5 | Establishment of bearer towards the forwarded-to subscriber..... | 150 | +| 13.4.3.6 | Failure handling in MSC server..... | 150 | +| 13.4.3.7 | Example ..... | 150 | +| 13.4.4 | Call Forwarding on mobile subscriber Not Reachable (CFNRc)..... | 151 | +| 13.4.4.1 | Rerouting by HLR ..... | 151 | +| 13.4.4.2 | Rerouting by VLR ..... | 151 | +| 13.4.4.2.1 | MGW selection ..... | 152 | +| 13.4.4.2.2 | Incoming side bearer establishment..... | 152 | +| 13.4.4.2.3 | Notification to the calling subscriber ..... | 152 | +| 13.4.4.2.4 | Initial addressing ..... | 152 | +| 13.4.4.2.5 | Establishment of bearer towards the forwarded-to subscriber..... | 152 | +| 13.4.4.2.6 | Confirmation of bearer establishment ..... | 152 | +| 13.4.4.2.7 | Failure handling in MSC server ..... | 153 | +| 13.4.4.2.8 | Example..... | 153 | +| 13.5 | Call Waiting (CW) ..... | 154 | +| 13.5.1 | Call Confirmation of the waiting call ..... | 156 | +| 13.5.2 | Acceptance of the Waiting Call..... | 157 | +| 13.6 | Call Hold (CH)..... | 157 | +| 13.6.1 | Hold request..... | 157 | +| 13.6.2 | Retrieval request..... | 158 | +| 13.6.3 | Setting up another call ..... | 158 | +| 13.6.4 | Alternate from one call to the other..... | 158 | +| 13.6.5 | Disconnect ..... | 158 | +| 13.6.6 | Failure handling in MSC server ..... | 158 | +| 13.6.7 | Example 1 ..... | 158 | +| 13.6.8 | Example 2 ..... | 161 | +| 13.7 | Multiparty (MPTY)..... | 164 | +| 13.7.1 | Beginning the Multi Party call ..... | 164 | +| 13.7.2 | Managing an active Multi Party call ..... | 164 | +| 13.7.3 | Disconnect ..... | 165 | +| 13.7.4 | Failure handling in MSC server ..... | 165 | +| 13.7.5 | Example 1 – Multiparty call establishment..... | 165 | +| 13.7.6 | Example 2 – Private call establishment during multiparty call ..... | 168 | +| 13.8 | Closed User Group (CUG)..... | 169 | +| 13.9 | Advice of Charge (AoC)..... | 169 | +| 13.10 | User-to-User Signalling (UUS)..... | 169 | +| 13.11 | Call Barring Services ..... | 169 | +| 13.11.1 | Barring of outgoing calls ..... | 169 | +| 13.11.2 | Barring of incoming calls other than Anonymous Call Rejection..... | 169 | +| 13.11.3 | Anonymous Call Rejection (ACR)..... | 169 | +| 13.11.3.1 | General..... | 169 | +| 13.11.3.2 | Anonymous Call Rejection by the GMSC..... | 169 | +| 13.12 | Explicit Call Transfer (ECT)..... | 170 | +| 13.12.1 | Connection of remote parties..... | 170 | +| 13.12.2 | IU/A-interface release..... | 170 | +| 13.12.3 | Failure handling in MSC server ..... | 170 | +| 13.12.4 | Example ..... | 170 | +| 13.13 | Completion of Calls to Busy Subscriber (CCBS)..... | 172 | +| 13.13.1 | Clearing when tones/announcements are provided to the calling subscriber ..... | 172 | +| 13.13.2 | Network initiated mobile originated call ..... | 172 | +| 13.13.2.1 | Early Traffic Channel Assignment ..... | 173 | +| 13.13.2.1.1 | Example..... | 173 | +| 13.13.3 | CCBS Information conveyed by Call Signalling ..... | 174 | +| 13.14 | Multiple Subscriber Profile (MSP) ..... | 174 | +| 13.15 | Multicall ..... | 174 | + +| | | | +|------------|-------------------------------------------------------------------------------|-----| +| 13.15.1 | Mobile Originating ..... | 174 | +| 13.15.2 | Mobile Terminating..... | 174 | +| 13.16 | Calling Name Presentation (CNAP) ..... | 174 | +| 13.17 | Alternate Speech/Fax ..... | 174 | +| 13.18 | Modification of the Access Bearer..... | 175 | +| 13.18.1 | Modification of Bearer Characteristics..... | 175 | +| 13.18.1.1 | Iu mode ..... | 175 | +| 13.18.1.2 | A/Gb mode..... | 175 | +| 13.18.2 | IWF Protocol Change ..... | 175 | +| 13.19 | GSM Fax ..... | 175 | +| 13.20 | Voice group call service (VGCS), Voice broadcast service (VBS) ..... | 176 | +| 13.20.1 | Beginning the Voice group call..... | 176 | +| 13.20.2 | Talker change in Voice group call (1 channel model)..... | 176 | +| 13.20.3 | Disconnect ..... | 177 | +| 13.20.4 | Failure handling in MSC server ..... | 177 | +| 13.20.5 | Example ..... | 177 | +| 13.20.6 | Voice group call and voice broadcast services with AoIP ..... | 182 | +| 14 | Interactions with Other Network Features and Services..... | 184 | +| 14.1 | Customised Applications for Mobile network Enhanced Logic (CAMEL) ..... | 184 | +| 14.1.1 | Play Announcement/Send Tone ..... | 184 | +| 14.1.1.1 | Example of playing announcement by the gsmSRF ..... | 185 | +| 14.1.2 | User Interaction ..... | 185 | +| 14.1.2.1 | Play announcement..... | 185 | +| 14.1.2.2 | Detect DTMF tones ..... | 185 | +| 14.1.2.3 | Report DTMF tones ..... | 185 | +| 14.1.2.4 | Cancel prompt and collect user information..... | 185 | +| 14.1.3 | Call Party Handling (CPH)..... | 186 | +| 14.1.3.1 | Call Party Handling concepts ..... | 186 | +| 14.1.3.2 | Initiate Call Attempt procedure ..... | 186 | +| 14.1.3.2.1 | Example..... | 187 | +| 14.1.3.3 | Move Leg procedure..... | 188 | +| 14.1.3.4 | Split Leg procedure..... | 189 | +| 14.1.3.5 | CAMEL User interaction procedure..... | 190 | +| 14.1.3.6 | Failure handling in the MSC-S ..... | 191 | +| 14.2 | IST ..... | 191 | +| 14.3 | Operator Determined Barring (ODB) ..... | 191 | +| 14.3.1 | Barring of Outgoing Calls ..... | 191 | +| 14.3.2 | Barring of Incoming Calls ..... | 191 | +| 14.4 | DTMF..... | 192 | +| 14.4.1 | DTMF Tone Generation ..... | 192 | +| 14.4.1.1 | Inband DTMF Tone Generation ..... | 192 | +| 14.4.1.1.1 | Start DTMF ..... | 192 | +| 14.4.1.1.2 | Stop DTMF ..... | 192 | +| 14.4.1.1.3 | Example..... | 192 | +| 14.4.1.2 | Out-of-Band DTMF Tone Generation..... | 193 | +| 14.4.1.2.1 | Start DTMF ..... | 193 | +| 14.4.1.2.2 | Stop DTMF ..... | 193 | +| 14.4.1.2.3 | Example..... | 193 | +| 14.4.2 | DTMF Detection ..... | 194 | +| 14.4.2.1 | Inband DTMF Detection..... | 194 | +| 14.4.2.2 | Out-of-Band DTMF Detection ..... | 195 | +| 14.5 | OR ..... | 195 | +| 14.5.1 | Optimal routeing for basic mobile-to-mobile calls..... | 195 | +| 14.5.2 | Optimal routeing for conditional call forwarding; Early call forwarding ..... | 195 | +| 14.5.3 | Optimal routeing for conditional call forwarding; Late call forwarding..... | 195 | +| 14.5.3.1 | MSC server ..... | 195 | +| 14.5.3.1.1 | Resume Call Handling and clearing of connection to GMSC server..... | 195 | +| 14.5.3.1.2 | IU release..... | 195 | +| 14.5.3.2 | GMSC server ..... | 196 | +| 14.5.3.2.1 | Resume Call Handling and Clearing of Connection to visited MSC server ..... | 196 | +| 14.5.3.2.2 | MGW selection ..... | 196 | + +| | | | +|-------------|---------------------------------------------------------------------------------|-----| +| 14.5.3.2.3 | Incoming side bearer establishment ..... | 196 | +| 14.5.3.2.4 | Notification to the Calling Subscriber..... | 196 | +| 14.5.3.2.5 | Establishment of call and bearer towards the forwarded-to subscriber ..... | 196 | +| 14.5.3.2.6 | Example..... | 196 | +| 14.6 | Providing tones or announcements ..... | 200 | +| 14.6.1 | Preconditions when providing in-band information to the calling subscriber..... | 200 | +| 14.6.2 | Preconditions when providing in-band information to the called subscriber..... | 200 | +| 14.6.3 | Preconditions when providing in-band information to multiple subscribers ..... | 200 | +| 14.6.4 | Request to play an announcement/tone ..... | 200 | +| 14.6.5 | Stopping an announcement/tone..... | 200 | +| 14.6.6 | Announcement/tone completed ..... | 201 | +| 14.6.7 | Example 1 ..... | 201 | +| 14.6.8 | Example 2 ..... | 202 | +| 14.7 | Global Text Telephony..... | 203 | +| 14.8 | Emergency Calls ..... | 204 | +| 14.9 | Subscriber and equipment trace ..... | 204 | +| 14.10 | Customized Alerting Tone ..... | 204 | +| 14.10.1 | General ..... | 204 | +| 14.10.2 | Audio CAT ..... | 204 | +| 14.10.2.1 | Audio CAT Activated by the Calling Party..... | 204 | +| 14.10.2.2 | Audio CAT Activated by the Called Party ..... | 205 | +| 14.10.3 | Multimedia CAT ..... | 205 | +| 14.10.3.1 | Introduction..... | 205 | +| 14.10.3.2 | Multimedia CAT Activated by the Calling Party ..... | 205 | +| 14.10.3.3 | Multimedia CAT Activated by the Called Party ..... | 206 | +| 14.10.3.3.1 | Mobile originated multimedia call ..... | 206 | +| 14.10.3.3.2 | Mobile terminated multimedia call ..... | 206 | +| 14.10.3.3.3 | Example..... | 206 | +| 15 | Tunnelling ..... | 208 | +| 15.1 | Forward Bearer Establishment..... | 208 | +| 15.1.1 | Outgoing Side ..... | 208 | +| 15.1.1.1 | Tunnel Selection ..... | 208 | +| 15.1.1.2 | Initial addressing..... | 208 | +| 15.1.1.3 | Fast forward tunnelling..... | 208 | +| 15.1.1.4 | Delayed forward tunnelling ..... | 209 | +| 15.1.1.5 | Bearer control signalling transfer ..... | 209 | +| 15.1.2 | Incoming Side..... | 209 | +| 15.1.2.1 | Initial addressing..... | 209 | +| 15.1.2.2 | Tunnel Selection ..... | 209 | +| 15.1.2.3 | Fast forward tunnelling..... | 209 | +| 15.1.2.4 | Delayed forward tunnelling ..... | 210 | +| 15.1.2.5 | Bearer control signalling transfer ..... | 210 | +| 15.1.2.6 | Example ..... | 210 | +| 15.2 | Backward Bearer Establishment ..... | 211 | +| 15.2.1 | Outgoing Side ..... | 211 | +| 15.2.1.1 | Tunnel Selection ..... | 211 | +| 15.2.1.2 | Initial addressing..... | 212 | +| 15.2.1.3 | Fast forward tunnelling..... | 212 | +| 15.2.1.4 | Delayed backward tunnelling ..... | 212 | +| 15.2.1.5 | Bearer control signalling transfer ..... | 212 | +| 15.2.2 | Incoming Side..... | 212 | +| 15.2.2.1 | Initial addressing..... | 212 | +| 15.2.2.2 | Tunnel Selection ..... | 212 | +| 15.2.2.3 | Fast forward tunnelling..... | 212 | +| 15.2.2.4 | Delayed backward tunnelling ..... | 213 | +| 15.2.2.5 | Bearer control signalling transfer ..... | 213 | +| 15.2.2.6 | Example ..... | 213 | +| 16 | Messages/Procedures and their contents ..... | 215 | +| 16.1 | Messages between (G)MSC servers..... | 216 | +| 16.2 | Procedures between (G)MSC server and MGW ..... | 218 | + +| | | | +|---------|-----------------------------------------------------|-----| +| 16.2.1 | Change Flow Direction..... | 218 | +| 16.2.2 | Join Bearer Termination ..... | 219 | +| 16.2.3 | Isolate Bearer Termination ..... | 219 | +| 16.2.4 | Establish Bearer..... | 220 | +| 16.2.5 | Prepare Bearer ..... | 222 | +| 16.2.6 | Reserve Circuit..... | 224 | +| 16.2.7 | Change Through-Connection ..... | 225 | +| 16.2.8 | Activate Interworking Function ..... | 225 | +| 16.2.9 | Release Bearer ..... | 226 | +| 16.2.10 | Bearer Established ..... | 226 | +| 16.2.11 | Bearer Released ..... | 227 | +| 16.2.12 | Release Termination..... | 227 | +| 16.2.13 | Tunnel Information Up..... | 228 | +| 16.2.14 | Tunnel Information Down ..... | 228 | +| 16.2.15 | Send Tone ..... | 229 | +| 16.2.16 | Stop Tone..... | 229 | +| 16.2.17 | Play Announcement..... | 230 | +| 16.2.18 | Stop Announcement ..... | 230 | +| 16.2.19 | Announcement Completed ..... | 231 | +| 16.2.20 | Tone Completed ..... | 231 | +| 16.2.21 | Detect DTMF..... | 232 | +| 16.2.22 | Stop DTMF Detection ..... | 232 | +| 16.2.23 | Report DTMF ..... | 233 | +| 16.2.24 | Send DTMF ..... | 233 | +| 16.2.25 | Stop DTMF..... | 234 | +| 16.2.26 | MGW Out-of-Service/ Maintenance locking ..... | 234 | +| 16.2.27 | MGW Communication Up ..... | 235 | +| 16.2.28 | MGW Restoration ..... | 235 | +| 16.2.29 | MGW Register..... | 236 | +| 16.2.30 | MGW Re-register ..... | 237 | +| 16.2.31 | (G)MSC Server Ordered Re-register..... | 237 | +| 16.2.32 | (G)MSC Server Restoration ..... | 238 | +| 16.2.33 | (G)MSC Server Out of Service ..... | 238 | +| 16.2.34 | Termination Out-of-Service ..... | 239 | +| 16.2.35 | Termination Restoration..... | 239 | +| 16.2.36 | Audit Value ..... | 240 | +| 16.2.37 | Audit Capability ..... | 240 | +| 16.2.38 | Capability Update..... | 241 | +| 16.2.39 | Command Reject ..... | 241 | +| 16.2.40 | Activate Voice Processing Function ..... | 242 | +| 16.2.41 | Modify Bearer Characteristics..... | 243 | +| 16.2.42 | Protocol Negotiation Result ..... | 244 | +| 16.2.43 | MGW Resource Congestion Handling - Activate ..... | 244 | +| 16.2.44 | MGW Resource Congestion Handling - Indication ..... | 245 | +| 16.2.45 | Bearer Modification Support..... | 245 | +| 16.2.46 | CTM report..... | 246 | +| 16.2.47 | Prepare_IP_Transport..... | 247 | +| 16.2.48 | Modify IP Transport Address ..... | 248 | +| 16.2.49 | Emergency Call Indication ..... | 248 | +| 16.2.50 | Trace Activation ..... | 249 | +| 16.2.51 | Trace Deactivation..... | 249 | +| 16.2.52 | Trace Activation result notification..... | 250 | +| 16.2.53 | Continuity Check Tone..... | 250 | +| 16.2.54 | Continuity Check Verify ..... | 250 | +| 16.2.55 | Continuity Check Response ..... | 251 | +| 16.2.56 | Rate Change..... | 251 | +| 16.2.57 | Bearer Modified..... | 252 | +| 16.2.58 | Bearer Modification Failed..... | 252 | +| 16.2.59 | Termination heartbeat indication..... | 253 | +| 16.2.60 | Inactivity timeout activation..... | 253 | +| 16.2.61 | Inactivity timeout indication..... | 254 | +| 16.2.62 | Reserve RTP Connection Point ..... | 254 | + +| | | | +|------------------------|------------------------------------------------------------------------------------------------------------------|-----| +| 16.2.63 | Configure RTP Connection Point..... | 257 | +| 16.2.64 | Reserve and Configure RTP Connection Point ..... | 260 | +| 16.2.65 | Realm Availability Change - Activation ..... | 262 | +| 16.2.66 | Realm Availability Change - Indication..... | 264 | +| 16.2.67 | Media Inactivity Notification ..... | 264 | +| 17 | Bearer Redirect ..... | 264 | +| 17.1 | Example of use of Bearer Redirect with Call Forwarding on No Reply (CFNRy) ..... | 264 | +| 18 | (G)MSC MGW Tandeming ..... | 267 | +| 18.1 | Example of use of MSC MGW Tandeming during call setup to provide bearer access to specialised MGW resources..... | 267 | +| 19 | Timers for bearer independent CS core network ..... | 268 | +| 20 | Multiple IP Realms ..... | 268 | +| Annex A (informative): | Change History..... | 270 | + +--- + +## Foreword + +This Technical Specification has been produced by the 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. + +# 1 Scope + +The present document defines the stage 2 description for the bearer independent CS core network. The stage 2 shall cover the information flow between the GMSC server, MSC server and media gateways. Note that nothing in the present document shall preclude an implementation of a combined MSC Server and MGW. The present document shall show the CS core network termination of the Iu interface in order to cover the information flow stimulus to the core network and describe the interaction with the supplementary and value added services and capabilities. + +For the purposes of the present document, the protocol used over the Nc interface is an enhanced call control protocol supporting call bearer separation such as BICC (which is specified in [22]). The protocol used over the Mc interface is H.248 (which is specified in 3GPP TS 29.232 [6]). Existing specifications and recommendations shall not be repeated, as such the relevant specification shall be referred to. + +SIP-I based CS core network is further specified in 3GPP TS 23.231 [42]. + +Local Call Local Switch (LCLS) functionality is further specified in 3GPP TS 23.284 [45]. + +The present document is applicable only for ATM or IP transport in the CS core network. + +![Figure 1: CS core network logical architecture diagram. The diagram shows the logical architecture of a CS core network. At the top, UTRAN and GERAN are connected to the core network via Iu and A/Iu interfaces respectively. The core network consists of two MGW (Media Gateway) units and two server units: MSC server and GMSC server. The MGW units are connected to the PSTN/ Legacy/External network. The MSC server and GMSC server are connected to the MGW units via Mc and Nb interfaces. The MSC server is also connected to Applications & Services via CAP interfaces and to the HLR via D and C interfaces. The GMSC server is connected to the HLR via C and D interfaces. A legend at the bottom left indicates that dashed lines represent Signalling Interfaces and solid lines represent Signalling and Data Transfer Interfaces.](6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg) + +Figure 1: CS core network logical architecture diagram. The diagram shows the logical architecture of a CS core network. At the top, UTRAN and GERAN are connected to the core network via Iu and A/Iu interfaces respectively. The core network consists of two MGW (Media Gateway) units and two server units: MSC server and GMSC server. The MGW units are connected to the PSTN/ Legacy/External network. The MSC server and GMSC server are connected to the MGW units via Mc and Nb interfaces. The MSC server is also connected to Applications & Services via CAP interfaces and to the HLR via D and C interfaces. The GMSC server is connected to the HLR via C and D interfaces. A legend at the bottom left indicates that dashed lines represent Signalling Interfaces and solid lines represent Signalling and Data Transfer Interfaces. + +**Figure 1: CS core network logical architecture** + +The CAP interfaces and the interfaces towards the HLR are outside the scope of the present document. + +Details of Transcoder-Free Operation are outside the scope of the present document. Please see 3GPP TS 23.153 [3] for more information. + +The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced. + +# 2 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: "Vocabulary for 3GPP Specifications". + +- [2] 3GPP TS 23.002: "Network architecture". +- [3] 3GPP TS 23.153: "Out of Band Transcoder Control; Stage 2". +- [4] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [5] ITU-T Recommendation H.248: "Gateway control protocol". +- [6] 3GPP TS 29.232: "Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3". +- [7] 3GPP TS 29.415: " Core Network Nb Interface User Plane Protocols ". +- [8] 3GPP TS 23.009: "Handover procedures". +- [9] 3GPP TS 23.072: "Call Deflection Supplementary Service; Stage2". +- [10] 3GPP TS 23.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL); Stage 2". +- [11] 3GPP TS 23.079: "Support of Optimal Routeing (SOR); Technical Realization; Stage2". +- [12] 3GPP TS 23.082: "Call Forwarding (CF) Supplementary Services; Stage 2". +- [13] 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Services; Stage 2". +- [14] 3GPP TS 23.084: "MultiParty (MPTY) Supplementary Service; Stage 2". +- [15] 3GPP TS 23.091: "Explicit Call Transfer (ECT) Supplementary Service; Stage 2". +- [16] 3GPP TS 23.093: "Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2". +- [17] 3GPP TS 23.135: "Multicall supplementary service; Stage 2". +- [18] 3GPP TS 23.108: "Mobile radio interface layer 3 specification core network protocols; Stage 2". +- [19] 3GPP TS 42.032: "Immediate Service Termination (IST); Service description; Stage 1". +- [20] 3GPP TS 25.415: "UTRAN Iu interface user plane protocols". +- [21] 3GPP TS 29.414: "Core Network Nb data transport and transport signalling". +- [22] 3GPP TS 29.205: "Application of Q.1900 series to bearer independent circuit-switched core network architecture; Stage 3". +- [23] 3GPP TS 29.010: "Information Element Mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling Procedures and the Mobile Application Part (MAP)". +- [24] 3GPP TS 43.045: "Technical Realization Of Facsimile Group 3 service - Transparent". +- [25] 3GPP TS 23.146: "Technical realization of facsimile group 3 non-transparent". +- [26] 3GPP TS 25.413: "UTRAN Iu Interface RANAP signalling" +- [27] 3GPP TS 48.008: "Mobile Switching Centre – Base Station system (MSC – BSS) interface layer 3 Specification" +- [28] 3GPP TS 23.226: "Global Text Telephony (GTT); Stage 2" +- [29] 3GPP TS 43.051: "GSM/EDGE Radio Access Network (GERAN) overall description; Stage 2;" +- [30] 3GPP TS 25.412: "UTRAN Iu interface signalling transport". +- [31] 3GPP TS 25.410: "UTRAN Iu Interface: General Aspects and Principles". +- [32] 3GPP TS 25.414: "UTRAN Iu interface data transport and transport signalling". + +- [33] 3GPP TS 23.014: "Technical Specification Group Core Network; Support of Dual Tone Multi-Frequency (DTMF) signalling". +- [34] 3GPP TS 32.421: " Subscriber and equipment trace: Trace concepts and requirements". +- [35] 3GPP TS 32.422: "Subscriber and equipment trace: Trace control and configuration management". +- [36] 3GPP TS 32.423: "Subscriber and equipment trace: Trace data definition and management". +- [37] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". +- [38] 3GPP TS 23.172: "Technical Specification Group Core Network and Terminals;Technical realization of Circuit Switched (CS);multimedia service UDI/RDI fallback and service modification;Stage 2 +- [39] 3GPP TS 43.068: " Voice Group Call Service (VGCS)" +- [40] 3GPP TS 43.069: " Voice Broadcast Service (VBS)" +- [41] IETF RFC 2663: "IP Network Address Translator (NAT) Terminology and Considerations ". +- [42] 3GPP TS 23.231: "SIP-I based Circuit Switched Core Network ; Stage 2" +- [43] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [44] 3GPP TS 29.235: "Interworking between SIP-I based circuit-switched core network and other networks". +- [45] 3GPP TS 23.284: "Local Call Local Switch; Stage 2". +- [46] 3GPP TS 23.088: "Call Barring (CB) Supplementary Services; Stage 2". + +--- + +## 3 Symbols and abbreviations + +### 3.1 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|----|---------------------------------------------------------------------------------------------| +| Iu | Interface between the RNS and the core network. It is also considered as a reference point. | +| Mc | Interface between the server and the media gateway. | +| Nb | Interface between media gateways. | +| Nc | The NNI call control interface between (G)MSC servers. | + +### 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|---------------------------------| +| BCF | Bearer Control Function | +| BICC | Bearer Independent Call Control | +| CIC | Call Instance Code | +| CCF | Call Control Function | +| CS | Circuit Switched | +| GERAN | GSM/EDGE Radio Access Network | +| IAM | Initial Address Message | +| IETF | Internet Engineering Task Force | +| IP | Internet Protocol | +| IPv4 | Internet Protocol version 4 | +| IPv6 | Internet Protocol version 6 | +| LCLS | Local Call Local Switch | +| MGW | Media GateWay | +| MGC | Media Gateway Controller | + +| | | +|-------|-------------------------------------------| +| MSC-S | MSC Server | +| MTP2 | Message Transfer Part layer 2 | +| MTP3 | Message Transfer Part layer 3 | +| NNI | Network-Network interface | +| RAB | Radio Access Bearer | +| RANAP | Radio Access Network Application Protocol | +| SBSS | Serving Base Station System | +| SRNS | Serving Radio Network Subsystem | +| TCAP | Transaction Capabilities Application Part | +| TFO | Tandem Free Operation | +| TRAU | Transcoder and Rate Adapter Unit | +| TrFO | Transcoder Free Operation | +| UDP | User Datagram Protocol | +| UTRAN | UMTS Terrestrial Radio Access Network | + +### 3.3 Definitions + +**UE :** User equipment. This specification makes no distinction between MS (mobile station) and UE. + +**A/Gb mode:** mode of operation of the UE when connected to the Core Network via GERAN and the A and/or Gb interfaces. Throughout this specification the term GSM refers to GERAN A/Gb mode. + +**Iu mode:** mode of operation of the UE when connected to the Core Network via GERAN or UTRAN and the Iu interface. Throughout this specification the term UMTS refers to UTRAN or GERAN Iu mode. + +--- + +## 4 Main Concepts + +### 4.1 General + +The circuit switched core network enables the support of different transports (e.g. ATM or IP) in a bearer-independent fashion. For the ATM and IP transport, there is a strict separation between the call control level and the bearer control level. In the case of ATM or IP transport, the passage of compressed speech at variable bit rates is possible through the CS core network. + +The CS core network shall employ the MSC server, GMSC server and media gateways. The GMSC server and MSC server shall provide the call control and mobility management functions, and the media gateway shall provide the bearer control and transmission resource functions. The media gateway shall contain the stream manipulating functions. + +The GMSC server and MSC servers are connected to the media gateway via the Mc reference point. The MSC servers and GMSC servers are connected with the Nc reference point. There may be a number of call control transit nodes between the MSC server and GMSC server in the Nc reference point. The MGWs are connected with the Nb reference point. + +The users connected to the CS core network shall not be aware whether a MSC server – media gateway combination is used, or a monolithic MSC is used. + +### 4.2 Bearer-Independent Call Control + +The protocol used on the Nc interface shall be a call control protocol supporting IP and ATM transports in a bearer-independent manner for the ISDN service set, allowing the physical separation of the call control entities from the bearer control entities. + +An exception to this bearer independence concept is if Iu interface is on IP and the IP addresses are to be exchanged via call control plane signalling (known by the MSC due to configuration data). In this case the specific handling is described separately. + +Another exception to the bearer independence concept is the case of A interface user plane over IP (AoIP). In that case the IP addresses/UDP port numbers are to be exchanged via call control plane signalling. Specific handling is also described separately for this case. + +## 4.3 H.248/MEGACO + +H.248/MEGACO has been jointly developed within the ITU-T and the IETF, and supports a separation of call control entities from bearer control entities, and a separation of bearer control entities from transport entities. H.248 is used on the Mc interface between the (G)MSC servers and the media gateway. + +--- + +# 5 General Circuit Switched Core Network Domain Architecture + +## 5.1 Logical Architecture + +The overall CS core network logical architecture is shown in figure 1. + +### 5.1.1 CS Core Network Nodes + +#### 5.1.1.1 MSC Server + +The MSC server mainly comprises the call control and mobility control parts of a GSM/UMTS MSC as described in 3GPP TS 23.002 [2]. It is also integrated with a VLR to hold the mobile subscriber's service data and CAMEL related data. + +The MSC server terminates the user-network signalling (see 3GPP TS 24.008 [4]) and translates it into the signalling over the Nc interface. The MSC Server terminates the Iu control plane signalling and its transport bearer (see 3GPP TS 25.413 [26] and 3GPP TS 25.412 [30]). It also terminates the signalling over the Mc interface with the Media Gateway. + +The MSC server controls the parts of the call state model that pertain to connection control for media channels in an MGW. It also contains the "Call Control Function" in the BICC model. + +#### 5.1.1.2 GMSC Server + +The GMSC server mainly comprises the call control and mobility control parts of a GSM/UMTS GMSC as described in 3GPP TS 23.002 [2]. + +The GMSC server terminates the signalling over the Nc interface and the call control interfaces to the external networks. It also terminates the signalling over the Mc interface towards the Media Gateway. + +The GMSC server controls the parts of the call state model that pertain to connection control for media channels in an MGW. It also contains the "Call Control Function" in the BICC model. + +#### 5.1.1.3 Media Gateway + +The Media Gateway terminates the signalling over the Mc interface from the (G)MSC servers. The Media Gateway terminates the Iu transport network control plane signalling with its transport bearer (see 3GPP TS 25.410 [31] and 3GPP TS 25.414 [32]). The Media Gateway also terminates the Iu user plane protocol (see 3GPP TS 25.415 [20]). It also terminates the bearer control signalling and the transport bearer over the Nb interface (see 3GPP TS 29.414 [21] and 3GPP TS 29.415 [7]). + +The Media Gateway contains bearer terminations and media manipulation equipment (e.g. transcoders, echo cancellers, or tone senders). It may perform media conversion and framing protocol conversion. + +### 5.1.2 CS Core Network Interfaces and Reference Points + +#### 5.1.2.1 Mc Interface + +The Mc reference point in the present document considers the aspects of the interface between the (G)MSC server and the MGW. The H.248 protocol [5] together with 3GPP specific extensions/packages shall be used over the Mc interface. + +### 5.1.2.2 Nc Interface + +The Network-Network based call control is used over the Nc interface. Any suitable call control protocol may be used over the Nc interface (e.g. BICC). + +### 5.1.2.3 Nb Interface + +The bearer control signalling and transport are carried over the Nb interface. + +## 5.2 Network Interworking + +### 5.2.1 Interworking on the Nc Reference Point + +Interworking between the Nc reference point, call control protocols and ISUP is defined within the 3GPP stage 3 documentation for each protocol (or by references specified in stage 3 documentation [6]). + +### 5.2.2 Interworking on the Nb Reference Point + +The interworking is specified in 3GPP TS 29.415 [7] and 3GPP TS 29.414 [21]. + +--- + +## 6 Call Establishment + +NOTE1: All message sequence charts in this clause are examples. All valid call establishment message sequences can be derived from the example message sequences and associated message pre-conditions. + +NOTE2: The continuity indication in the IAM is not used to indicate that a continuity check will be performed on the current leg of the call, but it is used to indicate that a Continuity message can be expected as a result of a continuity check on a preceding ISUP circuit, or establishment of a preceding bearer connection. + +## 6.1 Basic Mobile Originating Call + +### 6.1.1 Forward bearer establishment + +The mobile originating call shall be established in accordance with 3GPP TS 23.108 [17]. The following clauses describe the additional requirements for the bearer independent CS core network. If out-of-band transcoder control is applied for a speech call, it shall be performed in accordance with 3GPP TS 23.153 [3]. + +#### 6.1.1.1 MGW selection + +The MSC server shall select an MGW for the bearer connection before it performs the access bearer assignment or the network side bearer establishment. This may happen either before sending the IAM or after receiving the Bearer Information message. In the latter case, the MGW selection may be based on a possibly received MGW-id from the succeeding node (bullet 1 or bullet 2 in figure 6.2). For GSM, if performing Service based handover (see 3GPP TS 48.008 [27]) the MSC Server may omit MGW selection at this time. + +#### 6.1.1.2 Initial addressing + +The MSC server shall indicate in the IAM that forward bearer establishment is to be used. If access bearer assignment has not been completed, the MSC server shall indicate that the Continuity message will follow. However, if late access bearer assignment (assignment after alerting or answer) is used the MSC server shall not indicate that the Continuity message will follow. The MSC server provides the bearer characteristics to the succeeding node in the IAM. If the MGW is selected at an earlier stage the MGW-id may also be provided in the IAM (bullet 1 in figure 6.2). + +#### 6.1.1.3 Network side bearer establishment + +The MSC server shall select bearer characteristics for the network side bearer connection before sending the IAM. After the succeeding node has provided a bearer address and a binding reference in the Bearer Information message the MSC server uses the Establish Bearer procedure to request the MGW to establish a bearer towards the destination MGW. The MSC server provides the MGW with the bearer address, the binding reference and the bearer characteristics (bullet 2 in figure 6.2). + +#### 6.1.1.4 Access bearer assignment + +The MSC server shall select bearer characteristics for the access bearer. + +For UMTS, before the MSC server starts the access bearer assignment, the MSC server requests the MGW to prepare for the access bearer establishment using the Prepare Bearer procedure. The MSC server requests the MGW to provide a bearer address and a binding reference, provides the MGW with the bearer characteristics and requests notification that the bearer can be modified. For speech calls, the MSC server shall provide the MGW with the speech coding information and conditionally GTT related information in accordance with 3GPP TS 23.226 [28] for the bearer. For a non-speech call the MSC server also provides the MGW with a PLMN Bearer Capability [4]. After the MGW has replied with the bearer address and the binding reference the MSC server requests access bearer assignment using the provided bearer address and binding reference (bullet 3 in figure 6.2) in accordance with 3GPP TS 25.413 [26]. The MSC shall only be notified by the MGW using Bearer Modification Support procedure if the existing link characteristics of the access bearer can be modified at a later stage, see subclause 13.18.1. + +For GERAN Iu mode the MSC Server receives the GERAN capabilities within the RANAP INITIAL UE MESSAGE, indicating the services (e.g. for CS speech services the supported codec types and, for an adaptive codec type, the supported codec modes (for definition see [27])), which will be available at the RAB establishment procedure. The MSC server shall take the indicated GERAN capabilities into account as well as the received MS capabilities when negotiating a service. Additionally, when requesting the access bearer assignment the MSC server shall indicate to the GERAN the selected service (e.g. selected codec type). The MSC server shall not set codec information in the NAS Synchronisation Indicator (see [4]). Instead it shall set codec information in the GERAN BSC container. + +For GSM, before the MSC server starts the access bearer assignment, the MSC server uses the Reserve Circuit procedure to seize a TDM circuit. For a non-speech call the MSC server also provides the MGW with a PLMN Bearer Capability [4] and a GSM channel coding. After the MGW has replied to the TDM circuit seizure, the MSC server requests access bearer assignment (bullet 4 in figure 6.2) in accordance with 3GPP TS 48.008 [27]. If performing Service based handover (see 3GPP TS 48.008 [27]) the MSC Server may omit to perform Reserve Circuit procedure. + +#### 6.1.1.5 Framing protocol initialisation + +In 3GPP CS CN speech and data shall be carried using the Iu/Nb User Plane Protocol. The specification for the Iu UP protocol is defined in [20] and the Nb UP Protocol in [7] and [21]. The Iu/Nb UP Protocol is established through the CN in a forward direction. This is established independently of the bearer establishment direction. The MGW derives the forward direction from information sent by the MSC server within the Establish Bearer and Prepare Bearer procedures [6]. + +#### 6.1.1.6 Confirmation of bearer establishment + +If the IAM which was sent to the succeeding node indicated that the Continuity message will follow, the MSC server sends the Continuity message when the access bearer assignment has been completed (bullet 5 in figure 6.2). + +#### 6.1.1.7 Through-Connection + +During any one of the Prepare Bearer, Reserve Circuit and Establish Bearer procedures, the MSC server will use the Change Through-Connection procedure to request the MGW to through-connect the bearer terminations so that the bearer will be backward through-connected (bullet 2, and bullet 3 or 4 in figure 6.2). + +For a multimedia call, the MSC may request the MGW to both-way through-connect the bearer using the Change Through-Connection procedure to generate a multimedia CAT (see subclause 14.10.3.1). + +Otherwise when MSC server receives the answer indication, it requests the MGW to both-way through-connect the bearer using the Change Through-Connection procedure (bullet 6 in figure 6.2). + +#### 6.1.1.8 Interworking function + +The MGW may use an interworking function that is based on the PLMN Bearer Capability [4] of the bearer termination. The activation of the possible interworking function in both bearer terminations will be requested by the MSC server at reception of the answer indication using the Activate Interworking Function procedure (bullet 6 in figure 6.2). + +#### 6.1.1.9 Codec handling + +The MGW may include a speech transcoder based upon the speech coding information provided to each bearer termination. + +#### 6.1.1.10 Voice Processing function + +A voice processing function located on the MGW may be used to achieve desired acoustic quality on the bearer terminations. The MSC server shall request the activation of voice processing functions in the bearer terminations. For non-speech calls, the MSC server has the ability to instruct the MGW to disable the voice processing functions (bullet 6 in figure 6.2). + +#### 6.1.1.11 Failure handling in MSC server + +If any procedure between the MSC server and the MGW has not completed successfully or the MSC server receives a Bearer Released procedure from the MGW, the call shall be cleared as described in clause 7.3, (G)MSC server initiated call clearing or in clause 7.4, MGW initiated call clearing. Alternatively, the MSC server may only release the resources in the MGW that caused the failure, possibly select a new MGW for the bearer connection and continue the call establishment using new resources in the selected MGW. + +#### 6.1.1.12 Example + +Figure 6.1 shows the network model for the mobile originating call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. The MSC server seizes one context with two bearer terminations in the MGW. The bearer termination T1 is used for the bearer towards the RNC/BSC and the bearer termination T2 is used for the bearer towards the succeeding MGW. + +![Figure 6.1: Basic Mobile Originating Call, Forward Bearer Establishment (network model). The diagram shows three main components: MSC-S (top), RNC/BSC (bottom left), and MGW (bottom center). The MSC-S is connected to the RNC/BSC by a dashed green line (call control signalling). The MSC-S is connected to the MGW by a solid blue line (bearer control signalling). The RNC/BSC is connected to the MGW by a dotted red line (bearer). The MGW has two bearer terminations, T1 and T2. T1 is connected to the RNC/BSC via the dotted red line. T2 is connected to the succeeding MGW via another dotted red line. The MGW is labeled 'CTX1' and 'MGW'.](86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg) + +``` +graph TD + MSC_S[MSC-S] + RNC_BSC[RNC/BSC] + MGW[MGW] + MSC_S -.-> RNC_BSC + MSC_S --- MGW + RNC_BSC -.-> MGW + subgraph MGW + T1[T1] + T2[T2] + CTX1[CTX1] + end + MGW -.-> Succeeding_MGW[Succeeding MGW] +``` + +Figure 6.1: Basic Mobile Originating Call, Forward Bearer Establishment (network model). The diagram shows three main components: MSC-S (top), RNC/BSC (bottom left), and MGW (bottom center). The MSC-S is connected to the RNC/BSC by a dashed green line (call control signalling). The MSC-S is connected to the MGW by a solid blue line (bearer control signalling). The RNC/BSC is connected to the MGW by a dotted red line (bearer). The MGW has two bearer terminations, T1 and T2. T1 is connected to the RNC/BSC via the dotted red line. T2 is connected to the succeeding MGW via another dotted red line. The MGW is labeled 'CTX1' and 'MGW'. + +**Figure 6.1: Basic Mobile Originating Call, Forward Bearer Establishment (network model)** + +Figure 6.2 shows the message sequence chart example for the mobile originating call. In the example the MSC server requests seizure of the network side bearer termination and establishment of the bearer when the Bearer Information message is received from the succeeding node. After the network side bearer termination is seized the MSC server requests seizure of the access side bearer termination. When the MSC server receives an answer indication, it shall requests the MGW to both-way through-connect the bearer terminations. The MSC shall also request the possible activation of the interworking function in both terminations and the possible activation of the voice processing functions for the bearer terminations. + +![Sequence diagram for Basic Mobile Originating Call, Forward Bearer Establishment. Lifelines: UE, RNC/BSC, MSC-S, MGW. The diagram shows the flow of messages for call setup and bearer establishment, with specific sections for UMTS and GSM.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +The sequence diagram illustrates the interaction between UE, RNC/BSC, MSC-S, and MGW for a Basic Mobile Originating Call. The process begins with the UE sending a SETUP message to the MSC-S, which responds with CALL PROCEEDING. The MSC-S then sends an Initial Address to the MGW, which returns Bearer Information. The diagram is divided into two main sections: UMTS and GSM, each with its own bearer establishment procedure. In the UMTS section, the MSC-S sends Context (\$) and Context (C1) to the MGW, which responds with ADD.request (\$) and ADD.reply (T2). The RNC/BSC then sends a RAB ASSIGNMENT REQ to the MSC-S, which triggers a 'Bearer Establishment and Iu UP Initialization' block. The MGW sends UP Init to the UE, which responds with UP Init Ack. In the GSM section, the MSC-S sends Context (C1) to the MGW, which responds with ADD.request (T1) and ADD.reply (T1). The RNC/BSC then sends an ASSIGNMENT REQUEST to the MSC-S, which responds with ASSIGNMENT COMPL. Finally, the MSC-S sends a Continuity message to the MGW. + +``` +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S + participant MGW + + Note left of UE: Error! No + Note right of MGW: Error! No text of specified style in + + UE->>MSC-S: SETUP + MSC-S-->>UE: CALL PROCEEDING + + Note right of MSC-S: 1 + MSC-S->>MGW: Initial Address + MGW-->>MSC-S: Bearer Information + + Note right of MSC-S: 2 + MSC-S->>MGW: Context ($) +Context (C1) + MGW-->>MSC-S: ADD.request ($) +ADD.reply (T2) + Note right of MGW: Bearer Establishment + Note right of MGW: Establish Bearer + Change Through-Connection + + Note right of RNC/BSC: UMTS: + Note right of MSC-S: 3 + MSC-S->>MGW: Context (C1) +Context (C1) + MGW-->>MSC-S: ADD.request ($) +ADD.reply (T1) + Note right of MGW: Prepare Bearer + Change Through-Connection + RNC/BSC->>MSC-S: RAB ASSIGNMENT REQ + Note right of RNC/BSC: Bearer Establishment and Iu UP Initialization + MGW->>UE: UP Init + UE-->>MGW: UP Init Ack + + Note right of RNC/BSC: GSM: + Note right of MSC-S: 4 + MSC-S->>MGW: Context (C1) +Context (C1) + MGW-->>MSC-S: ADD.request (T1) +ADD.reply (T1) + Note right of MGW: Reserve Circuit + Change Through-Connection + RNC/BSC->>MSC-S: ASSIGNMENT REQUEST + MSC-S-->>RNC/BSC: ASSIGNMENT COMPL + + Note right of MSC-S: 5 + MSC-S->>MGW: Continuity +``` + +Sequence diagram for Basic Mobile Originating Call, Forward Bearer Establishment. Lifelines: UE, RNC/BSC, MSC-S, MGW. The diagram shows the flow of messages for call setup and bearer establishment, with specific sections for UMTS and GSM. + +Figure 6.2/1: Basic Mobile Originating Call, Forward Bearer Establishment (message sequence chart) + +![Sequence diagram for Basic Mobile Originating Call, Forward Bearer Establishment. Lifelines: UE, RNC/BSC, MSC-S, MGW. The diagram shows the flow of messages for bearer establishment. 1. MGW sends 'Address Complete' to MSC-S. 2. MSC-S sends 'Answer' to RNC/BSC. 3. RNC/BSC sends 'ALERTING' to UE. 4. MSC-S sends 'Context (C1)' to RNC/BSC. 5. MSC-S sends 'MOD.request (T1)' to MGW. 6. MGW responds with 'Change Through-Connection + Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable)'. 7. MSC-S sends 'MOD.reply (T1)' to MGW. 8. MSC-S sends 'Context (C1)' to RNC/BSC. 9. MSC-S sends 'MOD.request (T2)' to MGW. 10. MGW responds with 'Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable)'. 11. MSC-S sends 'MOD.reply (T2)' to MGW. 12. MSC-S sends 'Context (C1)' to RNC/BSC. 13. MSC-S sends 'CONNECT' to RNC/BSC. 14. RNC/BSC sends 'CONNECT' to UE.](26d664119ad25250780f554633444e54_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S + participant MGW + + Note right of MGW: 6 + MGW->>MSC-S: Address Complete + MSC-S->>RNC/BSC: Answer + RNC/BSC->>UE: ALERTING + MSC-S->>RNC/BSC: Context (C1) + MSC-S->>MGW: MOD.request (T1) + MGW-->>MSC-S: Change Through-Connection + Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable) + MSC-S->>MGW: MOD.reply (T1) + MSC-S->>RNC/BSC: Context (C1) + MSC-S->>MGW: MOD.request (T2) + MGW-->>MSC-S: Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable) + MSC-S->>MGW: MOD.reply (T2) + MSC-S->>RNC/BSC: Context (C1) + MSC-S->>RNC/BSC: CONNECT + RNC/BSC->>UE: CONNECT + +``` + +Sequence diagram for Basic Mobile Originating Call, Forward Bearer Establishment. Lifelines: UE, RNC/BSC, MSC-S, MGW. The diagram shows the flow of messages for bearer establishment. 1. MGW sends 'Address Complete' to MSC-S. 2. MSC-S sends 'Answer' to RNC/BSC. 3. RNC/BSC sends 'ALERTING' to UE. 4. MSC-S sends 'Context (C1)' to RNC/BSC. 5. MSC-S sends 'MOD.request (T1)' to MGW. 6. MGW responds with 'Change Through-Connection + Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable)'. 7. MSC-S sends 'MOD.reply (T1)' to MGW. 8. MSC-S sends 'Context (C1)' to RNC/BSC. 9. MSC-S sends 'MOD.request (T2)' to MGW. 10. MGW responds with 'Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable)'. 11. MSC-S sends 'MOD.reply (T2)' to MGW. 12. MSC-S sends 'Context (C1)' to RNC/BSC. 13. MSC-S sends 'CONNECT' to RNC/BSC. 14. RNC/BSC sends 'CONNECT' to UE. + +**Figure 6.2/2: Basic Mobile Originating Call, Forward Bearer Establishment +(message sequence chart continue)** + +## 6.1.2 Backward bearer establishment + +The basic mobile originating call shall be established in accordance with 3GPP TS 23.108 [17]. The following clauses describe the additional requirements for the bearer independent CS core network. If out-of-band transcoder control is applied for a speech call, it shall be performed in accordance with 3GPP TS 23.153 [3]. + +### 6.1.2.1 MGW selection + +The MSC server shall select an MGW for the bearer connection before it performs the access bearer assignment or the network side bearer establishment. This happens before sending the IAM (bullet 1 or 2 in figure 6.4). For GSM, if performing Service based handover (see 3GPP TS 48.008 [27]) the MSC Server may omit MGW selection at this time. + +### 6.1.2.2 Network side bearer establishment + +The MSC server shall select bearer characteristics for the network side bearer connection before sending the IAM. The MSC server requests the MGW to prepare for the network side bearer establishment using the Prepare Bearer procedure. The MSC server requests the MGW to provide a bearer address and a binding reference, and provides the MGW with the bearer characteristics (bullet 3 in figure 6.4). After the MGW has replied with the bearer address and the binding reference, the MSC server sends the IAM to the succeeding node. + +### 6.1.2.3 Initial addressing + +The MSC server shall indicate in the IAM that backward bearer establishment is to be used. If access bearer assignment has not been completed, the MSC server shall indicate that the Continuity message will follow. However, if late access bearer assignment (assignment after alerting or answer) is used the MSC server shall not indicate that the Continuity message will follow. The MSC server provides the bearer characteristics, the bearer address and the binding reference to the succeeding node in the IAM. The MSC server may also provide the MGW-id in the IAM (bullet 4 in figure 6.4). + +### 6.1.2.4 Access bearer assignment + +The MSC server shall select bearer characteristics for the access bearer. + +For UMTS, before the MSC server starts the access bearer assignment, the MSC server requests the MGW to prepare for the access bearer establishment using the Prepare Bearer procedure. The MSC server requests the MGW to provide a bearer address and a binding reference, provides the MGW with the bearer characteristics and requests notification that the bearer can be modified. For speech calls, the MSC server shall provide the MGW with the speech coding information and conditionally GTT related information in accordance with 3GPP TS 23.226 [28] for the bearer. For a non-speech call the MSC server also provides the MGW with a PLMN Bearer Capability [4]. After the MGW has replied with the bearer address and the binding reference the MSC server requests access bearer assignment using the provided bearer address and binding reference (bullet 1 in figure 6.4) in accordance with 3GPP TS 25.413 [26]. The MSC shall only be notified by the MGW using the Bearer Modification Support procedure if the existing link characteristics of the access bearer can be modified at a later stage, see subclause 13.18.1. + +For GERAN Iu mode the MSC Server receives the GERAN capabilities within the RANAP INITIAL UE MESSAGE, indicating the services (e.g. for CS speech services the supported codec types and, for an adaptive codec type, the supported codec modes (for definition see [27])), which will be available at the RAB establishment procedure. The MSC server shall take the indicated GERAN capabilities into account as well as the received MS capabilities when negotiating a service. Additionally, when requesting the access bearer assignment the MSC server shall indicate to the GERAN the selected service (e.g. selected codec type). The MSC server shall not set codec information in the NAS Synchronisation Indicator (see [4]). Instead it shall set codec information in the GERAN BSC container. + +For GSM, before the MSC server starts the access bearer assignment, the MSC server uses the Reserve Circuit procedure to seize a TDM circuit. For a non-speech call the MSC server also provides the MGW with a PLMN Bearer Capability [4] and a GSM channel coding. After the MGW has replied the TDM circuit seizure the MSC server requests access bearer assignment (bullet 2 in figure 6.4) in accordance with 3GPP TS 48.008 [27]. If performing Service based handover (see 3GPP TS 48.008 [27]) the MSC Server may omit to perform Reserve Circuit procedure. + +### 6.1.2.5 Framing protocol initialisation + +In 3GPP CS CN speech and data shall be carried using the Iu/Nb User Plane Protocol. The specification for the Iu UP protocol is defined in [20] and the Nb UP Protocol in [7] and [21]. The Iu/Nb UP Protocol is established through the CN in a forward direction. This is established independently of the bearer establishment direction. The MGW derives the forward direction from information sent by the MSC server within the Establish Bearer and Prepare Bearer procedures [6]. + +### 6.1.2.6 Confirmation of bearer establishment + +If the IAM was sent to the succeeding node indicating that the Continuity message will follow, the MSC server sends the Continuity message when the access bearer assignment has been completed. + +### 6.1.2.7 Through-Connection + +During the Prepare Bearer or Reserve Circuit procedures, the MSC server will use the Change Through-Connection procedure to request the MGW to through-connect the bearer terminations so that the bearer will be backward through-connected (bullet 1 or 2, and bullet 3 in figure 6.4). + +For a multimedia call, the MSC may request the MGW to both-way through-connect the bearer using the Change Through-Connection procedure to generate a multimedia CAT (see subclause 14.10.1). + +Otherwise when the MSC server receives the answer indication, it requests the MGW to both-way through-connect the bearer using the Change Through-Connection procedure (bullet 5 in figure 6.4). + +### 6.1.2.8 Interworking function + +The MGW may use an interworking function that is based on the PLMN Bearer Capability [4] of the bearer termination. The activation of the possible interworking function in both bearer terminations will be requested by the MSC server at reception of the answer indication using the Activate Interworking Function procedure (bullet 5 in figure 6.4). + +### 6.1.2.9 Codec handling + +The MGW may include a speech transcoder based upon the speech coding information provided to each bearer termination. + +### 6.1.2.10 Voice Processing function + +A voice processing function located on the MGW may be used to achieve desired acoustic quality on the bearer terminations. The MSC server shall request the activation of the voice processing functions in the bearer terminations. For non-speech calls, the MSC server has the ability to instruct the MGW to disable the voice processing functions (bullet 5 in figure 6.4). + +### 6.1.2.11 Failure handling in MSC server + +If any procedure between the MSC server and the MGW has not completed successfully or the MSC server receives a Bearer Released procedure from the MGW, the call shall be cleared as described in clause 7.3, (G)MSC server initiated call clearing or in clause 7.4, MGW initiated call clearing. Alternatively, the MSC server may only release the resources in the MGW that caused the failure, possibly select a new MGW for the bearer connection and continue the call establishment using new resources in the selected MGW. + +### 6.1.2.12 Example + +Figure 6.3 shows the network model for the mobile originating call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. The MSC server seizes one context with two bearer terminations in the MGW. The bearer termination T1 is used for the bearer towards the RNC/BSC and the bearer termination T2 is used for the bearer towards the succeeding MGW. + +![Figure 6.3: Basic Mobile Originating Call, Backward Bearer Establishment (network model). The diagram shows three main components: MSC-S (top), RNC/BSC (bottom left), and MGW (bottom center). MSC-S is connected to RNC/BSC by a dashed green line (call control signalling). MSC-S is connected to MGW by a solid blue line (bearer control signalling). MGW has two bearer terminations, T1 and T2. T1 is connected to RNC/BSC by a dotted red line (bearer). T2 is connected to a dotted red line extending to the right (bearer towards succeeding MGW).](82b40cb8b2a5ac361973859400fa128a_img.jpg) + +Figure 6.3: Basic Mobile Originating Call, Backward Bearer Establishment (network model). The diagram shows three main components: MSC-S (top), RNC/BSC (bottom left), and MGW (bottom center). MSC-S is connected to RNC/BSC by a dashed green line (call control signalling). MSC-S is connected to MGW by a solid blue line (bearer control signalling). MGW has two bearer terminations, T1 and T2. T1 is connected to RNC/BSC by a dotted red line (bearer). T2 is connected to a dotted red line extending to the right (bearer towards succeeding MGW). + +**Figure 6.3: Basic Mobile Originating Call, Backward Bearer Establishment (network model)** + +Figure 6.4 shows the message sequence chart example for the mobile originating call. In the example the MSC server requests seizure of the access side bearer termination and network side bearer termination. As the access bearer assignment has been completed before the IAM, no Continuity message will be sent. When the MSC server receives an answer indication, it requests the MGW to both-way through-connect the bearer terminations. The MSC server, shall also request the possible activation of the interworking function in both bearer terminations. The MSC server shall request the possible activation of the voice processing functions for the bearer terminations. + +![Sequence diagram for Basic Mobile Originating Call, Backward Bearer Establishment. Lifelines: UE, RNC/BSC, MSC-S, MGW. The diagram shows the interaction between these components to establish a bearer for a call. It includes phases for UMTS and GSM, with specific messages like SETUP, CALL PROCEEDING, RAB ASSIGNMENT REQ, ADD.request, ADD.reply, ASSIGNMENT REQUEST, ASSIGNMENT COMPL, Initial Address, UP Init, and UP Init Ack. Key actions include 'Prepare Bearer + Change Through-Connection', 'Reserve Circuit + Change Through-Connection', and 'Prepare Bearer'.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S + participant MGW + + Note left of UE: Error! No + Note right of MGW: Error! No text of specified style in + + UE->>MSC-S: SETUP + MSC-S-->>UE: CALL PROCEEDING + + Note right of RNC/BSC: UMTS: + Note right of RNC/BSC: Context (C$) ① + MSC-S->>MGW: ADD.request ($) + Note right of MGW: Prepare Bearer + Change Through-Connection + MGW-->>MSC-S: ADD.reply (T1) + Note right of RNC/BSC: Context (C1) + RNC/BSC->>MSC-S: RAB ASSIGNMENT REQ + Note right of RNC/BSC: Bearer Establishment and Iu UP Initialization + MSC-S-->>RNC/BSC: RAB ASSIGNMENT COMPL + + Note right of RNC/BSC: GSM: + Note right of RNC/BSC: Context (C$) ② + MSC-S->>MGW: ADD.request (T1) + Note right of MGW: Reserve Circuit + Change Through-Connection + MGW-->>MSC-S: ADD.reply (T1) + Note right of RNC/BSC: Context (C1) + RNC/BSC->>MSC-S: ASSIGNMENT REQUEST + MSC-S-->>RNC/BSC: ASSIGNMENT COMPL + + Note right of RNC/BSC: Context (C1) ③ + MSC-S->>MGW: ADD.request ($) + Note right of MGW: Prepare Bearer + MGW-->>MSC-S: ADD.reply (T2) + Note right of RNC/BSC: Context (C1) + Note right of RNC/BSC: ④ + MSC-S->>MGW: Initial Address + Note right of MGW: Bearer Establishment + MGW->>UE: UP Init + UE-->>MGW: UP Init Ack + +``` + +Sequence diagram for Basic Mobile Originating Call, Backward Bearer Establishment. Lifelines: UE, RNC/BSC, MSC-S, MGW. The diagram shows the interaction between these components to establish a bearer for a call. It includes phases for UMTS and GSM, with specific messages like SETUP, CALL PROCEEDING, RAB ASSIGNMENT REQ, ADD.request, ADD.reply, ASSIGNMENT REQUEST, ASSIGNMENT COMPL, Initial Address, UP Init, and UP Init Ack. Key actions include 'Prepare Bearer + Change Through-Connection', 'Reserve Circuit + Change Through-Connection', and 'Prepare Bearer'. + +Figure 6.4/1: Basic Mobile Originating Call, Backward Bearer Establishment +(message sequence chart) + +![Sequence diagram for Basic Mobile Originating Call, Backward Bearer Establishment. Lifelines: UE, RNC/BSC, MSC-S, MGW. The diagram shows the flow of messages for call setup and bearer establishment. Messages include ALERTING, Address Complete, Answer, Context (C1) MOD.request (T1), Context (C1) MOD.reply (T1), Context (C1) MOD.request (T2), Context (C1) MOD.reply (T2), and CONNECT. The MGW performs 'Change Through-Connection + Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable)' for both T1 and T2 contexts.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S + participant MGW + + Note right of MSC-S: 5 + MSC-S->>RNC/BSC: ALERTING + MGW->>MSC-S: Address Complete + MGW->>MSC-S: Answer + MSC-S->>MGW: Context (C1) MOD.request (T1) + MGW-->>MSC-S: Context (C1) MOD.reply (T1) + Note right of MGW: Change Through-Connection + +Activate Inter-Working Function +(when applicable) + Activate Voi +Processing Function (when +applicable) + MSC-S->>MGW: Context (C1) MOD.request (T2) + MGW-->>MSC-S: Context (C1) MOD.reply (T2) + Note right of MGW: Activate Inter-Working +Function (when applicable) + +Activate Voice Processing +Function (when applicable) + MSC-S->>UE: CONNECT + +``` + +Sequence diagram for Basic Mobile Originating Call, Backward Bearer Establishment. Lifelines: UE, RNC/BSC, MSC-S, MGW. The diagram shows the flow of messages for call setup and bearer establishment. Messages include ALERTING, Address Complete, Answer, Context (C1) MOD.request (T1), Context (C1) MOD.reply (T1), Context (C1) MOD.request (T2), Context (C1) MOD.reply (T2), and CONNECT. The MGW performs 'Change Through-Connection + Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable)' for both T1 and T2 contexts. + +**Figure 6.4/2: Basic Mobile Originating Call, Backward Bearer Establishment +(message sequence chart continue)** + +### 6.1.3 Originating Call Establishment For Iu Interface on IP + +If IuCS on IP is supported by the MSC server, the Core Network side procedures described in 6.1.1 or 6.1.2 shall apply. For the access side termination, the exchange of IP addresses via call control procedures is described in this clause. + +Before the MSC server starts the access bearer assignment, the MSC server requests the MGW to prepare for the access bearer using the *Prepare\_IP\_Transport* procedure. The MSC server requests the MGW to provide an IP Transport Address and a Iu UDP Port and provides the MGW with the bearer characteristics. For speech calls, the MSC server shall provide the MGW with the speech coding information and conditionally GTT related information in accordance with 3GPP TS 23.226 [28]. For a non-speech call the MSC server also provides the MGW with a PLMN Bearer Capability [4]. After the MGW has replied with the IP address and UDP Port the MSC server requests access bearer assignment using the provided IP address and UDP Port in accordance with 3GPP TS 25.413 [26]. The IP addresses and UDP Ports of the MGW and the RNC are exchanged via the RANAP procedures. If the bearer transport is IP and IuUP mode is Transparent, when the MSC receives the RANAP RAB assignment response it shall send the RNC IP address and UDP Port to the MGW Access bearer termination using the *Modify\_IP\_Transport\_Address* procedure. + +If the bearer transport is IP and IuUP mode is Support, the MGW shall use the source IP address and UDP Port of the IuUP Init packet received from the radio access network as the destination address for subsequent downlink packets. + +The sequence is shown in figure 6.1.3/1. + +![Sequence diagram for Call Establishment for lu on IP. Lifelines: UE, RNC/BSC, MSC -S, MGW. The diagram shows the interaction between these components to establish a call. Key steps include SETUP, CALL PROCEEDING, Initial Address, Bearer Information, ADD.request, ADD.reply, RAB ASSIGNMENT REQ, UP Init, UP Init Ack, RAB ASSIGNMENT COMPL, MOD.request, Mod.reply, and Continuity. A green box labeled 'Bearer Establishment' and a red text 'Modify IP Transport' highlight specific parts of the process.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S as MSC -S + participant MGW + + Note right of MGW: Bearer Establishment + + UE->>MSC-S: SETUP + MSC-S-->>UE: CALL PROCEEDING + MSC-S->>MGW: 1 Initial Address + MGW-->>MSC-S: Bearer Information + MSC-S->>MGW: 2 Context ($) ADD.request ($) +Context (C1) ADD.reply (T2) + Note right of MGW: Establish Bearer + +Change Through -Connection + MSC-S->>MGW: 3 Context (C1) ADD.request ($) +Context (C1) ADD.reply (T1) + Note right of MGW: Prepare IP Transport +Change Through -Connection + RNC/BSC->>MSC-S: RAB ASSIGNMENT REQ + MSC-S->>MGW: UP Init + MGW-->>MSC-S: UP Init Ack + Note right of MGW: Ilf luUP in +Support Mode + RNC/BSC->>MSC-S: RAB ASSIGNMENT COMPL + Note right of RNC/BSC: Modify IP Transport + MSC-S->>MGW: Context (C1) MOD.request (T1) +Context(C1) Mod.reply (T1) + Note right of MGW: Ilf luUP in +Transparent Mode + MGW->>UE: UP Init + UE-->>MGW: UP Init Ack + MSC-S->>MGW: 5 Continuity + +``` + +Sequence diagram for Call Establishment for lu on IP. Lifelines: UE, RNC/BSC, MSC -S, MGW. The diagram shows the interaction between these components to establish a call. Key steps include SETUP, CALL PROCEEDING, Initial Address, Bearer Information, ADD.request, ADD.reply, RAB ASSIGNMENT REQ, UP Init, UP Init Ack, RAB ASSIGNMENT COMPL, MOD.request, Mod.reply, and Continuity. A green box labeled 'Bearer Establishment' and a red text 'Modify IP Transport' highlight specific parts of the process. + +Figure 6.1.3/1: Call Establishment for lu on IP + +## 6.1.4 Forward bearer establishment with Trace Session Activation + +The mobile originating call shall be established in accordance with 3GPP TS 23.108 [17]. The following clause describes the additional requirement for the bearer independent CS core network if a trace session is activated from a MSC Server to a MGW. + +### 6.1.4.1 Trace activation + +When a Trace Session is activated in the MSC Server and the trace control and configuration parameters require Trace Session activation to the MGW, the MSC Server activates the Trace Session to the MGW by using the trace activation procedure. + +### 6.1.4.2 Example + +Figure 6.1.4.1 shows the network model for the mobile originating call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. The MSC server seizes one context with two bearer terminations in the MGW. The bearer termination T1 is used for the bearer towards the RNC/BSC and the bearer termination T2 is used for the bearer towards the succeeding MGW. + +![Figure 6.1.4.1: Basic Mobile Originating Call, Forward Bearer Establishment with Trace Session Activation (network model). The diagram shows three main components: MSC-S (top), RNC/BSC (bottom left), and MGW (bottom center). MSC-S is connected to RNC/BSC by a green dashed line (call control signalling). MSC-S is connected to MGW by a solid blue line (bearer control signalling). MGW is connected to RNC/BSC by a red dotted line (bearer). MGW has two bearers: T1 (towards RNC/BSC) and T2 (towards the succeeding MGW). The MGW is labeled 'CTXT MGW'.](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg) + +``` +graph TD; MSC-S[MSC-S] -- "call control signalling (squared line)" --> RNC_BSC[RNC/BSC]; MSC-S -- "bearer control signalling (solid line)" --> MGW[MGW]; MGW -- "bearer (dotted line)" --> RNC_BSC; MGW -- "bearer (dotted line)" --> Succeeding_MGW[...]; subgraph MGW [MGW]; T1[T1]; T2[T2]; CTXT[CTXT]; end; +``` + +Figure 6.1.4.1: Basic Mobile Originating Call, Forward Bearer Establishment with Trace Session Activation (network model). The diagram shows three main components: MSC-S (top), RNC/BSC (bottom left), and MGW (bottom center). MSC-S is connected to RNC/BSC by a green dashed line (call control signalling). MSC-S is connected to MGW by a solid blue line (bearer control signalling). MGW is connected to RNC/BSC by a red dotted line (bearer). MGW has two bearers: T1 (towards RNC/BSC) and T2 (towards the succeeding MGW). The MGW is labeled 'CTXT MGW'. + +**Figure 6.1.4.1: Basic Mobile Originating Call, Forward Bearer Establishment with Trace Session Activation (network model)** + +Figure 6.1.4.2 shows the message sequence chart example for the mobile originating call. In the example the MSC server activates the Trace Session to MGW when it request the creation of the incoming and outgoing termination with ADD request. MGW sends the Trace Session Activation result with NOTIFY request to MSC Server. + +![Sequence diagram for Basic Mobile Originating Call, Forward Bearer Establishment with Trace Session Activation. Lifelines: UE, RNC/BSC, MSC-S, MGW. The diagram shows the flow of messages for UMTS and GSM bearers, including SETUP, CALL PROCEEDING, Initial Address, Bearer Information, ADD.request, ADD.reply, NOTIFY.request, NOTIFY.reply, RAB ASSIGNMENT REQ/COMPL, ASSIGNMENT REQUEST/COMPL, UP Init, and UP Init Ack. Key events include Bearer Establishment, Bearer Establishment and Iu UP Initialization, and Continuity.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +The sequence diagram illustrates the interaction between a User Equipment (UE), Radio Network Controller/Base Station Controller (RNC/BSC), Mobile Switching Center - Server (MSC-S), and Media Gateway (MGW) for a Basic Mobile Originating Call. The process involves bearer establishment and trace session activation for both UMTS and GSM networks. + +**Sequence of Messages:** + +- The UE sends a **SETUP** message to the MSC-S. +- The MSC-S responds with **CALL PROCEEDING** to the UE. +- The MSC-S sends an **Initial Address** message to the MGW. +- The MGW responds with **Bearer Information** to the MSC-S. +- For **UMTS** bearers (labeled 1 and 2): + - The MSC-S sends an **ADD.request (\$)** to the MGW, including Context (\$). + - The MGW responds with **ADD.reply (T2)**, including Context (C1). + - The MSC-S sends a **NOTIFY.request (T2)** to the MGW, including Context (C1). + - The MGW responds with **NOTIFY.reply (T2)**, including Context (C1). + - This sequence results in **Bearer Establishment** and **Trace Activation** at the MGW. +- For additional **UMTS** bearers (labeled 3): + - The MSC-S sends an **ADD.request (\$)** to the MGW, including Context (C1). + - The MGW responds with **ADD.reply (T1)**, including Context (C1). + - The MSC-S sends a **NOTIFY.request (T2)** to the MGW, including Context (C1). + - The MGW responds with **NOTIFY.reply (T2)**, including Context (C1). + - This sequence results in **Prepare Bearer + Change Through -Connection** and **Trace Activation** at the MGW. +- The MSC-S sends a **RAB ASSIGNMENT REQ** to the RNC/BSC. +- A green box indicates **Bearer Establishment and Iu UP Initialization** between the MSC-S and RNC/BSC. +- The MGW sends a **UP Init** message to the UE. +- The UE responds with a **UP Init Ack** message to the MGW. +- For **GSM** bearers (labeled 4): + - The MSC-S sends an **ADD.request (T1)** to the MGW, including Context (C1). + - The MGW responds with **ADD.reply (T1)**, including Context (C1). + - The MSC-S sends a **NOTIFY.request (T2)** to the MGW, including Context (C1). + - The MGW responds with **NOTIFY.reply (T2)**, including Context (C1). + - This sequence results in **Reserve Circuit + Change Through -Connection + Trace Activation** and **Trace Activation Result** at the MGW. +- The MSC-S sends an **ASSIGNMENT REQUEST** to the RNC/BSC. +- The RNC/BSC responds with an **ASSIGNMENT COMPL** message to the MSC-S. +- Finally, the MSC-S sends a **Continuity** message to the MGW (labeled 5). + +Sequence diagram for Basic Mobile Originating Call, Forward Bearer Establishment with Trace Session Activation. Lifelines: UE, RNC/BSC, MSC-S, MGW. The diagram shows the flow of messages for UMTS and GSM bearers, including SETUP, CALL PROCEEDING, Initial Address, Bearer Information, ADD.request, ADD.reply, NOTIFY.request, NOTIFY.reply, RAB ASSIGNMENT REQ/COMPL, ASSIGNMENT REQUEST/COMPL, UP Init, and UP Init Ack. Key events include Bearer Establishment, Bearer Establishment and Iu UP Initialization, and Continuity. + +Figure 6.1.4.2/1: Basic Mobile Originating Call, Forward Bearer Establishment with Trace Session Activation (message sequence chart) + +![Sequence diagram for Basic Mobile Originating Call, Forward Bearer Establishment with Trace Session Activation. Lifelines: UE, RNC/BSC, MSC-S, MGW. The diagram shows the following sequence of messages: 1. MSC-S sends 'Address Complete' to RNC/BSC. 2. RNC/BSC sends 'ALERTING' to UE. 3. MSC-S sends 'Answer' to RNC/BSC. 4. MSC-S sends 'Context (C1)' to MGW (labeled with a circled 6). 5. MGW responds with 'MOD.request (T1)'. 6. MSC-S responds with 'MOD.reply (T1)'. 7. MSC-S sends another 'Context (C1)' to MGW. 8. MGW responds with 'MOD.request (T2)'. 9. MSC-S responds with 'MOD.reply (T2)'. 10. MSC-S sends 'CONNECT' to RNC/BSC, which then sends it to UE. On the MGW side, the first pair of MOD.request/reply is associated with 'Change Through-Connection + Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable)'. The second pair is associated with 'Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable)'.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +Sequence diagram for Basic Mobile Originating Call, Forward Bearer Establishment with Trace Session Activation. Lifelines: UE, RNC/BSC, MSC-S, MGW. The diagram shows the following sequence of messages: 1. MSC-S sends 'Address Complete' to RNC/BSC. 2. RNC/BSC sends 'ALERTING' to UE. 3. MSC-S sends 'Answer' to RNC/BSC. 4. MSC-S sends 'Context (C1)' to MGW (labeled with a circled 6). 5. MGW responds with 'MOD.request (T1)'. 6. MSC-S responds with 'MOD.reply (T1)'. 7. MSC-S sends another 'Context (C1)' to MGW. 8. MGW responds with 'MOD.request (T2)'. 9. MSC-S responds with 'MOD.reply (T2)'. 10. MSC-S sends 'CONNECT' to RNC/BSC, which then sends it to UE. On the MGW side, the first pair of MOD.request/reply is associated with 'Change Through-Connection + Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable)'. The second pair is associated with 'Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable)'. + +**Figure 6.1.4.2/2: Basic Mobile Originating Call, Forward Bearer Establishment with Trace Session Activation** + (message sequence chart continue) + +## 6.1.5 Originating Call Establishment for A interface over IP + +If AoIP is supported by the MSC server, the Core Network side procedures described in 6.1.1 or 6.1.2 shall apply. For the access side termination, the exchange of IP addresses and UDP port numbers via call control procedures is described in this clause. + +Before the MSC server sends the Assignment Request to the BSC, the MSC server requests the MGW to reserve an RTP bearer termination using the Reserve RTP Connection Point procedure. The MSC server requests the MGW to reserve an IP Address and UDP Port and also may indicate that the IP interface type is for AoIP. The MGW reserves the RTP termination and indicates the IP address and UDP port number to the MSC server. MSC server then requests access bearer assignment using the provided IP address and UDP Port. When MSC server receives the BSSMAP ASSIGNMENT COMPLETE message, it shall send the BSC IP address and UDP Port to the MGW Access bearer termination using the Configure RTP Connection Point procedure. + +The sequence is shown in figure 6.1.5.1. + +![Sequence diagram for Originating Call Establishment for AoIP. Lifelines: UE, BSC, MSC-S, MGW. The process involves SETUP, CALL PROCEEDING, Initial Address, Bearer Information, ADD.request, ADD.reply, ASSIGNMENT REQ, ASSIGNMENT COMPL, MOD.request, Mod.reply, and Continuity messages. A green box labeled 'Bearer Establishment' is shown between MSC-S and MGW. Red text indicates actions like 'Establish Bearer + Change Through Connection', 'Reserve RTP Connection Point + Change Through Connection', and 'Configure RTP Connection Point'.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant BSC + participant MSC-S + participant MGW + + Note right of MGW: Bearer Establishment + + UE->>MSC-S: SETUP + MSC-S-->>UE: CALL PROCEEDING + Note right of MSC-S: 1 + MSC-S->>MGW: Initial Address + MGW-->>MSC-S: Bearer Information + Note right of MSC-S: 2 + MSC-S->>MGW: ADD.request ($) + Note right of MGW: Establish Bearer + Change Through Connection + MGW-->>MSC-S: ADD.reply (T2) + Note right of MSC-S: 3 + MSC-S->>MGW: ADD.request ($) + Note right of MGW: Reserve RTP Connection Point + Change Through Connection + MGW-->>MSC-S: ADD.reply (T1) + MSC-S->>BSC: ASSIGNMENT REQ + BSC-->>MSC-S: ASSIGNMENT COMPL + Note right of MSC-S: 4 + MSC-S->>MGW: MOD.request (T1) + Note right of MGW: Configure RTP Connection Point + MGW-->>MSC-S: Mod.reply (T1) + Note right of MSC-S: 5 + MSC-S->>MGW: Continuity + +``` + +Sequence diagram for Originating Call Establishment for AoIP. Lifelines: UE, BSC, MSC-S, MGW. The process involves SETUP, CALL PROCEEDING, Initial Address, Bearer Information, ADD.request, ADD.reply, ASSIGNMENT REQ, ASSIGNMENT COMPL, MOD.request, Mod.reply, and Continuity messages. A green box labeled 'Bearer Establishment' is shown between MSC-S and MGW. Red text indicates actions like 'Establish Bearer + Change Through Connection', 'Reserve RTP Connection Point + Change Through Connection', and 'Configure RTP Connection Point'. + +Figure 6.1.5.1: Originating Call Establishment for AoIP + +## 6.2 Basic Mobile Terminating Call + +### 6.2.1 Forward bearer establishment + +The basic mobile terminating call shall be established in accordance with 3GPP TS 23.108 [18]. The following clauses describe the additional requirements for the bearer independent CS core network. If out-of-band transcoder control is applied for a speech call, it shall be performed in accordance with 3GPP TS 23.153 [3]. + +#### 6.2.1.1 GMSC server + +##### 6.2.1.1.1 MGW selection + +The GMSC server shall select an MGW for the bearer connection before it performs the incoming side bearer establishment or the outgoing side bearer establishment. This may happen either before sending the IAM or after receiving the Bearer Information message. If the GMSC server received an MGW-id from the preceding node and/or from the succeeding node, then it may use one of them for the MGW selection (bullet 1 or bullet 4 in figure 6.6). + +NOTE: As an implementation option, if there is no need for the GMSC server to manipulate the bearer, the GMSC server may perform call control signalling without any associated MGW. In that case the bearer related information shall be passed transparently through the GMSC server. + +#### 6.2.1.1.2 Initial addressing + +The GMSC server shall indicate in the IAM that forward bearer establishment is to be used. The GMSC server shall also indicate in the IAM that the Continuity message will follow if either of the following conditions is satisfied before sending the IAM: + +1. the incoming IAM indicated that the Continuity message will follow, but no Continuity message has been received; +2. the GMSC server selected an MGW, but a notification of successful bearer establishment on the incoming side has not been received from the MGW. + +The GMSC server shall provide the bearer characteristics to the succeeding node in the IAM. If the MGW is selected at an early stage the MGW-id may also be provided in the IAM (bullet 1 in figure 6.6). + +#### 6.2.1.1.3 Outgoing side bearer establishment + +The GMSC server shall select bearer characteristics for the outgoing side bearer connection before it sends the IAM. After the GMSC server has received a bearer address and a binding reference in the Bearer Information message from the succeeding node the GMSC server requests the MGW to establish a bearer to the given destination MGW using the Establish Bearer procedure. The GMSC server shall provide the MGW with the bearer address, the binding reference and the bearer characteristics (bullet 4 in figure 6.6). + +#### 6.2.1.1.4 Incoming side bearer establishment + +The GMSC server requests the MGW to prepare for the incoming side bearer establishment using the Prepare Bearer procedure. The GMSC server requests the MGW to provide a bearer address, a binding reference and to notify when the bearer is established (bullet 5 in figure 6.6). The GMSC server also provides the MGW with the bearer characteristics that was received from the preceding node in the IAM. After the MGW has replied with the bearer address and the binding reference, the GMSC server sends the Bearer Information message to the preceding node. The GMSC server may also include the MGW-id in the Bearer Information message (bullet 6 in figure 6.6). + +NOTE: The incoming side bearer establishment may take place either before or after HLR interrogation. + +#### 6.2.1.1.5 Framing protocol initialisation + +In 3GPP CS CN speech and data shall be carried using the Iu/Nb User Plane Protocol. The specification for the Iu UP protocol is defined in [20] and the Nb UP Protocol in [7] and [21]. The Iu/Nb UP Protocol is established through the CN in a forward direction. This is established independently of the bearer establishment direction. The MGW derives the forward direction from information sent by the MSC server within the Establish Bearer and Prepare Bearer procedures [6]. The notification of bearer establishment shall not be sent until the Iu/Nb UP has been initialised. + +#### 6.2.1.1.6 Through-Connection + +During the Prepare Bearer and Establish Bearer procedures, the GMSC server will use the Change Through-Connection procedure to request the MGW to both-way through-connect the bearer termination (bullet 4 and bullet 5 in figure 6.6). + +#### 6.2.1.1.7 Confirmation of bearer establishment + +If the IAM which was sent to the succeeding node indicated that the Continuity message will follow, the Continuity message shall be sent when both of the following conditions are satisfied: + +1. Either: + - a. The incoming IAM indicated that the Continuity message will follow, and a Continuity message has been received from the preceding node (bullet 8 in figure 6.6), or + - b. The incoming IAM did not indicate that the Continuity message will follow; +2. Either: + - a. The GMSC server has selected an MGW, and a notification of successful bearer establishment in the incoming side has been received from the MGW (bullet 7 in figure 6.6), or + - b. MGW selection is not required for this call. + +#### 6.2.1.1.8 Voice Processing function + +A voice processing function located on the MGW may be used to achieve desired acoustic quality on the bearer terminations. The GMSC server shall request the activation of the voice processing functions in the bearer terminations. For non-speech calls, the GMSC server has the ability to instruct the MGW to disable the voice processing functions (bullet 13 in figure 6.6). The voice activation request from the GMSC server to MGW may be issued as soon as bullet 8 in figure 6.6, and may be issued as late as bullet 13 in figure 6.6 as illustrated. + +#### 6.2.1.1.9 Failure handling in GMSC server + +If any procedure between the GMSC server and the MGW has not completed successfully or the GMSC server receives a Bearer Released procedure from the MGW, the call shall be cleared as described in clause 7.3, (G)MSC server initiated call clearing or in clause 7.4, MGW initiated call clearing. Alternatively, the GMSC server may only release the resources in the MGW that caused the failure, possibly select a new MGW for the bearer connection and continue the call establishment using new resources in the selected MGW. + +#### 6.2.1.2 MSC server + +##### 6.2.1.2.1 Paging + +If the network side bearer establishment is delayed whilst the paging procedure is completed, the MSC server starts the Start\_Bearer\_Establishment timer when the paging procedure is started. The Start\_Bearer\_Establishment timer is stopped when the paging procedure is completed, or optionally when the Call Confirmed message is received in accordance with 3GPP TS 23.153 [3]. If the Start\_Bearer\_Establishment timer expires, the MSC server starts the network side bearer establishment. + +##### 6.2.1.2.2 Call setup + +The MSC server indicates to the UE in the SETUP message that early access bearer assignment is used in order to establish the bearer end-to-end before the UE starts alerting. The MSC server indicates to the UE in SETUP message that early access bearer assignment is used if either of the following conditions is satisfied before sending the SETUP message (bullet 2 in figure 6.6): + +1. The incoming IAM indicated that the Continuity message will follow, but no Continuity message has been received; +2. A notification of successful bearer establishment in the network side has not been received from the MGW. + +##### 6.2.1.2.3 MGW selection + +The MSC server shall select an MGW for the bearer connection before it performs the network side bearer establishment or the access bearer assignment. This happens at latest after the UE has sent the Call Confirmed message. If the MSC server received an MGW-id from the preceding node, it may use this for the MGW selection (bullet 3 in figure 6.6). For GSM, if performing Service based handover (see 3GPP TS 48.008 [27]) the MSC Server may omit MGW selection at this time. + +##### 6.2.1.2.4 Network side bearer establishment + +The MSC server requests the MGW to prepare for the network side bearer establishment using the Prepare Bearer procedure. The MSC server requests the MGW to provide a bearer address, a binding reference and to notify when the bearer is established (bullet 3 in figure 6.6). The MSC server also provides the MGW with the bearer characteristics that was received from the preceding node in the IAM. After the MGW has replied with the bearer address and the binding reference, the MSC server provides the Bearer Information message to the preceding node. The MSC server may also provide the MGW-id in the Bearer Information message. + +##### 6.2.1.2.5 Access bearer assignment + +The access bearer assignment shall be started only when both of the following conditions are satisfied: + +1. Either: + - a. The incoming IAM indicated that the Continuity message will follow, and a Continuity message has been received from the preceding node, or + - b. The incoming IAM did not indicate that the Continuity message will follow; + +2. A notification of successful bearer establishment in the network side has been received from the MGW (bullet 6 in figure 6.6). + +The MSC server shall select bearer characteristics for the access bearer. + +For the access bearer assignment in UMTS the MSC server requests the MGW to prepare for the access bearer establishment using the Prepare Bearer procedure. The MSC server requests the MGW to provide a bearer address and a binding reference, provides the MGW with the bearer characteristics and requests notification that the bearer can be modified. For speech calls, the MSC server shall provide the MGW with the speech coding information and conditionally GTT related information in accordance with 3GPP TS 23.226 [28] for the bearer. For a non-speech call the MSC server also provides the MGW with a PLMN Bearer Capability [4]. After the MGW has replied with the bearer address and the binding reference the MSC server requests the access bearer assignment using the provided bearer address and the binding reference (bullet 9 in figure 6.6) in accordance with 3GPP TS 25.413 [26]. The MSC shall only be notified by the MGW using the Bearer Modification Support procedure if the existing link characteristics of the access bearer can be modified at a later stage, see subclause 13.18.1. + +For GERAN Iu mode the MSC Server receives the GERAN capabilities within the RANAP INITIAL UE MESSAGE, indicating the services (e.g. for CS speech services the supported codec types and, for an adaptive codec type, the supported codec modes (for definition see [27])), which will be available at the RAB establishment procedure. The MSC server shall take the indicated GERAN capabilities into account as well as the received MS capabilities when negotiating a service. Additionally, when requesting the access bearer assignment the MSC server shall indicate to the GERAN the selected service (e.g. selected codec type). The MSC server shall not set codec information in the NAS Synchronisation Indicator (see [4]). Instead it shall set codec information in the GERAN BSC container. + +For GSM, before the MSC server starts the access bearer assignment, the MSC server uses the Reserve Circuit procedure to seize a TDM circuit. For a non-speech call the MSC server also provides the MGW with a PLMN Bearer Capability [4] and a GSM channel coding. After the MGW has replied the TDM circuit seizure the MSC server requests access bearer assignment (bullet 10 in figure 6.6) in accordance with 3GPP TS 48.008 [27]. If performing Service based handover (see 3GPP TS 48.008 [27]) the MSC Server may omit to perform Reserve Circuit procedure. + +#### 6.2.1.2.6 Framing protocol initialisation + +In 3GPP CS CN speech and data shall be carried using the Iu/Nb User Plane Protocol. The specification for the Iu UP protocol is defined in [20] and the Nb UP Protocol in [7] and [21]. The Iu/Nb UP Protocol is established through the CN in a forward direction. This is established independently of the bearer establishment direction. The MGW derives the forward direction from information sent by the MSC server within the Establish Bearer and Prepare Bearer procedures [6]. The notification of bearer establishment shall not be sent until the Nb UP has been initialised. + +#### 6.2.1.2.7 Called party alerting + +For a speech call, when the MSC server receives an Alerting message, it requests the MGW to provide a ringing tone to the calling party using the Send Tone procedure (bullet 11 in figure 6.6). + +NOTE: Other kind of tones may be provided to the calling party at an earlier stage of the call establishment. + +#### 6.2.1.2.8 Called party answer + +For a speech call, when the MSC server receives a Connect message, it requests the MGW to stop providing the ringing tone to the calling party using the Stop Tone procedure (bullet 12 in figure 6.6). + +#### 6.2.1.2.9 Through-Connection + +During the Prepare Bearer and Reserve Circuit procedures, the MSC server will use the Change Through-Connection procedure to request the MGW to through-connect the bearer terminations so that the bearer will be not through-connected (bullet 3, and bullet 9 or 10 in figure 6.6). + +When the MSC server receives the Connect message, it requests the MGW to both-way through-connect the bearer using the Change Through-Connection procedure (bullet 12 in figure 6.6). + +#### 6.2.1.2.10 Interworking function + +The MGW may use an interworking function that is based on the PLMN Bearer Capability [4] of the bearer termination. The activation of the possible interworking function in both bearer terminations will be requested by the MSC server at reception of the Connect message using the Activate Interworking Function procedure (bullet 12 in figure 6.6). + +#### 6.2.1.2.11 Codec handling + +The MGW may include a speech transcoder based upon the speech coding information provided to each bearer termination. + +#### 6.2.1.2.12 Voice Processing function + +A voice processing function located on the MGW may be used to achieve desired acoustic quality on the bearer terminations. The MSC server shall request the activation of the voice processing functions in the bearer terminations. For non-speech calls, the MSC server has the ability to instruct the MGW to disable the voice processing functions (bullet 12 in figure 6.6). + +#### 6.2.1.2.13 Failure handling in MSC server + +If any procedure between the MSC server and the MGW is not completed successfully, the call shall be cleared as described in clause 7.3, (G)MSC server initiated call clearing. Alternatively, the MSC server may only release the resources in the MGW that caused the failure, possibly select a new MGW for the bearer connection and continue the call establishment using new resources in the selected MGW. + +#### 6.2.1.2.14 Example + +Figure 6.5 shows the network model for the basic mobile terminating call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. The MSC server seizes one context with two bearer terminations in MGWb. The bearer termination T1 is used for the bearer towards the RNC/BSC and the bearer termination T2 is used for the bearer towards the GMSC server selected MGWa. The GMSC server seizes one context with two bearer terminations in MGWa. The bearer termination T3 is used for the bearer towards the MSC server selected MGWb and the bearer termination T4 is used for the bearer towards the preceding MGW. + +![Figure 6.5: Basic Mobile Terminating Call Forward Bearer Establishment (network model). The diagram shows three main components: GMSC-S, MSC-S, and RNC/BSC. GMSC-S is connected to MGWa (containing CTX2) via a solid line (call control) and a dotted line (bearer). MGWa is connected to MGWb (containing CTX1) via a solid line and a dotted line. MGWb is connected to RNC/BSC via a solid line and a dotted line. The dotted lines represent bearers, with T4, T3, T2, T1, and RNC/BSC labeled on the bottom row of MGWs. The solid lines represent call control signalling, connecting GMSC-S to MSC-S and then to RNC/BSC.](187bba66c887c745c512add37a577c5e_img.jpg) + +Figure 6.5: Basic Mobile Terminating Call Forward Bearer Establishment (network model). The diagram shows three main components: GMSC-S, MSC-S, and RNC/BSC. GMSC-S is connected to MGWa (containing CTX2) via a solid line (call control) and a dotted line (bearer). MGWa is connected to MGWb (containing CTX1) via a solid line and a dotted line. MGWb is connected to RNC/BSC via a solid line and a dotted line. The dotted lines represent bearers, with T4, T3, T2, T1, and RNC/BSC labeled on the bottom row of MGWs. The solid lines represent call control signalling, connecting GMSC-S to MSC-S and then to RNC/BSC. + +**Figure 6.5: Basic Mobile Terminating Call Forward Bearer Establishment (network model)** + +Figure 6.6 shows the message sequence example for the basic mobile terminating call. In the example the GMSC server requests seizure of the outgoing side bearer termination and establishment of the bearer when the Bearer Information message is received from the MSC server. After the outgoing side bearer termination is seized the GMSC server requests seizure of the incoming side bearer termination. The MGW sends a notification of an established incoming side bearer. The MSC server requests seizure of the network side bearer termination when Call Confirmed message is received from the UE. The MGW sends a notification of an established network side bearer. When the Continuity message is received from the GMSC server, the MSC server requests seizure of the access side bearer termination. For a speech call the MSC server requests MGW to provide a ringing tone to the calling party at alerting. At answer the MSC server requests MGW to both-way through-connect the bearer. For a speech call the MSC server requests MGW to stop the ringing tone to the calling party at answer. When the MSC server receives an answer indication, it shall request the possible activation of the interworking function in both bearer terminations. The (G)MSC server shall request the possible activation of the voice processing functions for the bearer terminations. + +![Sequence diagram for Basic Mobile Terminating Call, Forward Bearer Establishment. Lifelines: GMSGS, MGWa, MSGS, MGWb, RNC/BSC, UE. The diagram shows the flow of messages for call setup and bearer establishment, including HLR Interrogation, Paging + Security, SETUP, ADD.request, ADD.reply, Bearer Information, Bearer Establishment, UP Init, NOTIFY.request, NOTIFY.reply, and Continuity messages.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +sequenceDiagram + participant GMSGS + participant MGWa + participant MSGS + participant MGWb + participant RNC/BSC + participant UE + + Note left of GMSGS: Initial Address + Note right of GMSGS: HLR Interrogation + GMSGS->>MSG: 1 Initial Address + Note right of MSG: Paging + Security + MSG->>UE: 2 SETUP + UE-->>MSG: CALL CONFIRMED + Note right of MSG: Context ($), Context (C1) (T2) + MSG->>MGWb: 3 ADD.request + MGWb-->>MSG: ADD.reply + Note right of MGWb: Prepare Bearer + Change Through Connection + MGWb-->>MGWa: Bearer Information + Note right of MGWa: Context ($), Context (C2) + MGWa->>GMSGS: 4 ADD.request + GMSGS-->>MGWa: ADD.reply + Note right of MGWa: Establish Bearer + Change Through Connection + Note right of MGWa: Bearer Establishment + Note right of MGWa: Context (C2) + MGWa->>GMSGS: 5 ADD.request + GMSGS-->>MGWa: ADD.reply + Note right of MGWa: Prepare Bearer + Change Through Connection + MGWa-->>GMSGS: Bearer Information + Note right of GMSGS: Bearer Establishment + GMSGS->>MGWa: UP Init + MGWa-->>GMSGS: UP Init Ack + Note right of MGWa: Context (C2) + MGWa->>GMSGS: 7 NOTIFY.request + GMSGS-->>MGWa: NOTIFY.reply + Note right of MGWa: Bearer Established + MGWa->>MGWb: UP Init + MGWb-->>MGWa: UP Init Ack + Note right of MGWa: Context (C1) + MGWa->>MSG: 6 NOTIFY.request + MSG-->>MGWa: NOTIFY.reply + Note right of MSG: Bearer Established + Note right of MSG: Context (C1) + GMSGS->>MSG: 8 Continuity + +``` + +Sequence diagram for Basic Mobile Terminating Call, Forward Bearer Establishment. Lifelines: GMSGS, MGWa, MSGS, MGWb, RNC/BSC, UE. The diagram shows the flow of messages for call setup and bearer establishment, including HLR Interrogation, Paging + Security, SETUP, ADD.request, ADD.reply, Bearer Information, Bearer Establishment, UP Init, NOTIFY.request, NOTIFY.reply, and Continuity messages. + +Figure 6.6/1: Basic Mobile Terminating Call, Forward Bearer Establishment (message sequence chart) + +![Sequence diagram for Basic Mobile Terminating Call, Forward Bearer Establishment. Lifelines: GMSC-S, MGWa, MSC-S, MGWb, RNC/BSC, UE. The diagram shows message exchanges for UMTS and GSM contexts, including ADD.request, ADD.reply, RAB ASSIGNMENT REQ, ASSIGNMENT REQUEST, and various MOD.request/reply messages for bearer establishment and voice processing activation.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +The sequence diagram illustrates the message exchanges for a Basic Mobile Terminating Call, Forward Bearer Establishment. The lifelines are GMSC-S, MGWa, MSC-S, MGWb, RNC/BSC, and UE. The process is divided into UMTS and GSM sections. + +**UMTS Section:** + +- MSC-S sends **ADD.request (\$)** to MGWb (Context C1) [Step 9]. +- MGWb responds with **ADD.reply (T1)** to MSC-S (Context C1). +- MSC-S sends **RAB ASSIGNMENT REQ** to RNC/BSC. +- RNC/BSC performs **Bearer Establish. and Iu UP Initializa.** (highlighted in green). +- RNC/BSC sends **RAB ASSIGNMENT COMPL** to MSC-S. + +**GSM Section:** + +- MSC-S sends **ADD.request (T1)** to MGWb (Context C1) [Step 10]. +- MGWb responds with **ADD.reply (T1)** to MSC-S (Context C1). +- MSC-S sends **ASSIGNMENT REQUEST** to RNC/BSC. +- RNC/BSC sends **ASSIGNMENT COMPL** to MSC-S. +- MSC-S sends **ALERTING** to UE. +- MSC-S sends **Address Complete** to GMSC-S. +- GMSC-S sends **Address Complete** to MGWa. +- MSC-S sends **MOD.request (T2)** to MGWb (Context C1) [Step 11]. +- MGWb responds with **MOD.reply (T2)** to MSC-S (Context C1). +- MSC-S sends **CONNECT** to UE. +- MSC-S sends **MOD.request (T1)** to MGWb (Context C1) [Step 12]. +- MGWb responds with **MOD.reply (T1)** to MSC-S (Context C1). +- MSC-S sends **MOD.request (T2)** to MGWb (Context C1). +- MGWb responds with **MOD.reply (T2)** to MSC-S (Context C1). +- MSC-S sends **Answer** to GMSC-S. +- GMSC-S sends **Answer** to MGWa. +- MSC-S sends **MOD.request (T3)** to MGWa (Context C2) [Step 13]. +- MGWa responds with **MOD.reply (T3)** to MSC-S (Context C2). +- MSC-S sends **MOD.request (T4)** to MGWa (Context C2). +- MGWa responds with **MOD.reply (T4)** to MSC-S (Context C2). +- MSC-S sends **Answer** to MGWa. + +**Internal Messages and Notes:** + +- Prepare Bearer + Change Through-Connection** (between MGWb and RNC/BSC) +- Reserve Circuit + Change Through-Connection** (between MGWb and RNC/BSC) +- Send Tone (start providing a ringing tone for a speech call)** (between MGWb and UE) +- Change Through-Connection + Activate Inter-Working Function (when applicable) + Activate Voice Processing Function (when applicable)** (between MGWb and UE) +- Stop Tone (stop providing a ringing tone for speech call) + Activate Interworking Function (when applicable) + Activate Voice Processing Function (when applicable)** (between MGWb and UE) +- Activate Voice Processing Function (when applicable)** (between MSC-S and MGWa) +- Activate Voice Processing Function (when applicable)** (between MSC-S and MGWa) + +Sequence diagram for Basic Mobile Terminating Call, Forward Bearer Establishment. Lifelines: GMSC-S, MGWa, MSC-S, MGWb, RNC/BSC, UE. The diagram shows message exchanges for UMTS and GSM contexts, including ADD.request, ADD.reply, RAB ASSIGNMENT REQ, ASSIGNMENT REQUEST, and various MOD.request/reply messages for bearer establishment and voice processing activation. + +Figure 6.6/2: Basic Mobile Terminating Call, Forward Bearer Establishment +(message sequence chart continue) + +## 6.2.2 Backward bearer establishment + +The basic mobile terminating call shall be established in accordance with 3GPP TS 23.108 [4]. The following clauses describe the additional requirements for the bearer independent CS core network. If out-of-band transcoder control is applied for a speech call, it shall be performed in accordance with 3GPP TS 23.153 [3]. + +### 6.2.2.1 GMSC server + +#### 6.2.2.1.1 MGW selection + +The GMSC server shall select an MGW for the bearer connection before it performs the incoming side bearer establishment or the outgoing side bearer establishment. This happens before sending the IAM. If the GMSC server received an MGW-id from the preceding node, it may use this for the MGW selection (bullet 1 in figure 6.8). + +NOTE 1: As an implementation option, if there is no need for the GMSC server to manipulate the bearer, the GMSC server may perform call control signalling without any associated MGW. In that case the bearer related information shall be provided transparently through the GMSC server. + +#### 6.2.2.1.2 Outgoing side bearer establishment + +The GMSC server shall select bearer characteristics for the outgoing side bearer connection before it sends the IAM. The GMSC server requests the MGW to prepare for the outgoing side bearer establishment using the Prepare Bearer procedure. The GMSC server requests the MGW to provide a bearer address and a binding reference, and provides the MGW with the bearer characteristics (bullet 3 in figure 6.8). After the MGW has replied with the bearer address and the binding reference, the GMSC server sends the IAM to the succeeding node. + +#### 6.2.2.1.3 Initial addressing + +The GMSC server shall indicate in the IAM that backward bearer establishment is to be used. The GMSC server shall also indicate in the IAM that the Continuity message will follow if either of the following conditions is satisfied before sending the IAM: + +1. The incoming IAM indicated that the Continuity message will follow, but no Continuity message has been received, or +2. The GMSC server selected an MGW, but a notification of successful bearer establishment on the incoming side has not been received from the MGW. + +The GMSC server shall provide the bearer characteristics to the succeeding node in the IAM. The MGW-id may also be provided in the IAM (bullet 4 in figure 6.8). + +#### 6.2.2.1.4 Incoming side bearer establishment + +The GMSC server requests the MGW to establish a bearer to the given destination MGW and to notify when the bearer is established using the Establish Bearer procedure. The GMSC server provides the MGW with the bearer address, the binding reference and the bearer characteristics that were received from the preceding node in the IAM (bullet 1 in figure 6.8). + +NOTE 2: The incoming side bearer establishment may take place either before or after HLR interrogation. + +#### 6.2.2.1.5 Framing protocol initialisation + +In 3GPP CS CN speech and data shall be carried using the Iu/Nb User Plane Protocol. The specification for the Iu UP protocol is defined in [20] and the Nb UP Protocol in [7] and [21]. The Iu/Nb UP Protocol is established through the CN in a forward direction. This is established independently of the bearer establishment direction. The MGW derives the forward direction from information sent by the MSC server within the Establish Bearer and Prepare Bearer procedures [6]. The notification of bearer establishment shall not be sent until the Iu/Nb UP has been initialised + +#### 6.2.2.1.6 Through-Connection + +During the Prepare Bearer and Establish Bearer procedures, the GMSC server will use the Change Through-Connection procedure to request the MGW to both-way through-connect the bearer termination (bullet 1 and bullet 3 in figure 6.8). + +#### 6.2.2.1.7 Confirmation of bearer establishment + +If the IAM which was sent to the succeeding node indicated that the Continuity message will follow, the Continuity message shall be sent when both of the following conditions are satisfied: + +1. Either: + - a. The incoming IAM indicated that the Continuity message will follow, and a Continuity message has been received from the preceding node, or + - b. The incoming IAM did not indicate that the Continuity message will follow; +2. Either: + - a. The GMSC server has selected an MGW, and a notification of successful bearer establishment in the incoming side has been received from the MGW (bullet 2 in figure 6.8), or + - b. MGW selection is not required for this call. + +#### 6.2.2.1.8 Voice Processing function + +A voice processing function located on the MGW may be used to achieve desired acoustic quality on the bearer terminations. The (G)MSC server shall request the activation of voice processing functions in the bearer terminations. For non-speech calls, the GMSC server has the ability to instruct the MGW to disable the voice processing functions (bullet 12 in figure 6.8). The voice activation request from the GMSC server to MGWa may be issued as soon as bullet 4 in figure 6.8, and may be issued as late as bullet 12 in figure 6.8 as illustrated. + +#### 6.2.2.1.9 Failure handling in GMSC server + +If any procedure between the MSC server and the MGW is not completed successfully or the GMSC server receives a Bearer Released procedure from the MGW, the call shall be cleared as described in clause 7.3, (G)MSC server initiated call clearing or in clause 7.4, MGW initiated call clearing. Alternatively, the GMSC server may only release the resources in the MGW that caused the failure, possibly select a new MGW for the bearer connection and continue the call establishment using new resources in the selected MGW. + +### 6.2.2.2 MSC server + +#### 6.2.2.2.1 Paging + +If the network side bearer establishment is delayed whilst the paging procedure is completed, the MSC server starts the Start\_Bearer\_Establishment timer when the paging procedure is started. The Start\_Bearer\_Establishment timer is stopped when the paging procedure is completed, or optionally when the Call Confirmed message is received in accordance with 3GPP TS 23.153 [3]. If the Start\_Bearer\_Establishment timer expires, the MSC server starts the network side bearer establishment. + +#### 6.2.2.2.2 Call setup + +The MSC server indicates to the UE in the SETUP message that early access bearer assignment is used in order to establish the bearer end-to-end before the UE starts alerting. The MSC server indicates to the UE in the SETUP message that early access bearer assignment is used, if and only if, either of the following conditions are satisfied before sending the SETUP message (bullet 5 in figure 6.8): + +1. If the IAM indicated that the Continuity message will follow, but no Continuity message has been received. +2. A notification of successful bearer establishment in the network side has not been received from the MGW. + +#### 6.2.2.2.3 MGW selection + +The MSC server shall select an MGW for the bearer connection before it performs the network side bearer establishment or the access bearer assignment. This happens at latest after the UE has sent the Call Confirmed message. If the MSC server received an MGW-id from the preceding node, it may use this for the MGW selection (bullet 6 in figure 6.8). For GSM, if performing Service based handover (see 3GPP TS 48.008 [27]) the MSC Server may omit MGW selection at this time. + +#### 6.2.2.2.3 Network side bearer establishment + +The MSC server requests the MGW to establish a bearer to the given destination MGW and to notify when the bearer is established using the Establish Bearer procedure. The MSC server provides the MGW with the bearer address, the binding reference and the bearer characteristics that were received from the preceding node in the IAM (bullet 6 in figure 6.8). + +#### 6.2.2.2.4 Access bearer assignment + +The access bearer assignment shall be started only when both of the following conditions are satisfied: + +1. Either: + - a. The incoming IAM indicated that the Continuity message will follow, and a Continuity message has been received from the preceding node, or + - b. The incoming IAM did not indicate that the Continuity message will follow; +2. A notification of successful bearer establishment in the network side has been received from the MGW (bullet 7 in figure 6.8). + +The MSC server shall select bearer characteristics for the access bearer. + +For the access bearer assignment in UTRAN the MSC server requests the MGW to prepare for the access bearer establishment using the Prepare Bearer procedure. The MSC server requests the MGW to provide a bearer address and a binding reference, provides the MGW with the bearer characteristics and requests notification that the bearer can be modified. For speech calls, the MSC server shall provide the MGW with the speech coding information and conditionally GTT related information in accordance with 3GPP TS 23.226 [28] for the bearer. For a non-speech call the MSC server also provides the MGW with a PLMN Bearer Capability [4]. After the MGW has replied with the bearer address and the binding reference the MSC server requests the access bearer assignment using the provided bearer address and the binding reference (bullet 8 in figure 6.8) in accordance with 3GPP TS 25.413 [26]. The MSC shall only be notified by the MGW using the Bearer Modification Support procedure if the existing link characteristics of the access bearer can be modified at a later stage, see subclause 13.18.1. + +For GERAN Iu mode the MSC Server receives the GERAN capabilities within the RANAP INITIAL UE MESSAGE, indicating the services (e.g. for CS speech services the supported codec types and, for an adaptive codec type, the supported codec modes (for definition see [27])), which will be available at the RAB establishment procedure. The MSC server shall take the indicated GERAN capabilities into account as well as the received MS capabilities when negotiating a service. Additionally, when requesting the access bearer assignment the MSC server shall indicate to the GERAN the selected service (e.g. selected codec type). The MSC server shall not set codec information in the NAS Synchronisation Indicator (see [4]). Instead it shall set codec information in the GERAN BSC container.. + +For GSM, before the MSC server starts the access bearer assignment, the MSC server uses the Reserve Circuit procedure to seize a TDM circuit. For a non-speech call the MSC server also provides the MGW with a PLMN Bearer Capability [4] and a GSM channel coding. After the MGW has replied the TDM circuit seizure the MSC server requests access bearer assignment (bullet 9 in figure 6.8) in accordance with 3GPP TS 48.008 [27]. If performing Service based handover (see 3GPP TS 48.008 [27]) the MSC Server may omit to perform Reserve Circuit procedure. + +#### 6.2.2.2.5 Framing protocol initialisation + +In 3GPP CS CN speech and data shall be carried using the Iu/Nb User Plane Protocol. The specification for the Iu UP protocol is defined in [20] and the Nb UP Protocol in [7] and [21]. The Iu/Nb UP Protocol is established through the CN in a forward direction. This is established independently of the bearer establishment direction. The MGW derives the forward direction from information sent by the MSC server within the Establish Bearer and Prepare Bearer procedures [6]. The notification of bearer establishment shall not be sent until the Nb UP has been initialised. + +#### 6.2.2.2.6 Called party alerting + +For a speech call, when the MSC server receives an Alerting message, it requests the MGW to provide a ringing tone to the calling party using the Send Tone procedure (bullet 10 in figure 6.8). + +NOTE: Other kind of tones may be provided to the calling party at an earlier stage of the call establishment. + +#### 6.2.2.2.7 Called party answer + +For a speech call, when the MSC server receives a Connect message, it requests the MGW to stop providing the ringing tone to the calling party using the Stop Tone procedure (bullet 11 in figure 6.8). + +#### 6.2.2.2.8 Through-Connection + +During any one of the Prepare Bearer, Reserve Circuit and Establish Bearer procedures, the MSC server will use the Change Through-Connection procedure to request the MGW to through-connect the bearer terminations so that the bearer will be not through-connected (bullet 6, and bullet 8 or 9 in figure 6.8). + +When the MSC server receives the Connect message, it requests the MGW to both-way through-connect the bearer using the Change Through-Connection procedure (bullet 11 in figure 6.8). + +#### 6.2.2.2.9 Interworking function + +The MGW may use an interworking function that is based on the PLMN Bearer Capability [4] of the bearer termination. The activation of the possible interworking function in both bearer terminations will be requested by the MSC server at reception of the Connect message using the Activate Interworking Function procedure (bullet 11 in figure 6.8). + +#### 6.2.2.2.10 Codec handling + +The MGW may include a speech transcoder based upon the speech coding information provided to each bearer termination. + +#### 6.2.2.2.11 Voice Processing function + +A voice processing function located on the MGW may be used to achieve desired acoustic quality on the bearer terminations. The MSC server shall request the activation of the voice processing functions in the bearer terminations. For non-speech calls, the MSC server has the ability to instruct the MGW to disable the voice processing functions (bullet 11 in figure 6.8). + +#### 6.2.2.2.12 Failure handling in MSC server + +If any procedure between the MSC server and the MGW is not completed successfully or the MSC server receives a Bearer Released procedure from the MGW, the call shall be cleared as described in clause 7.3, (G)MSC server initiated call clearing or in clause 7.4, MGW initiated call clearing. Alternatively, the MSC server may only release the resources in the MGW that caused the failure, possibly select a new MGW for the bearer connection and continue the call establishment using new resources in the selected MGW. + +#### 6.2.2.2.13 Example + +Figure 6.7 shows the network model for the basic mobile terminating call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. The MSC server seizes one context with two bearer terminations in MGWb. The bearer termination T1 is used for the bearer towards the RNC/BSC and the bearer termination T2 is used for the bearer towards the GMSC server selected MGWa. The GMSC server seizes one context with two bearer terminations in MGWa. The bearer termination T3 is used for the bearer towards the MSC server selected MGWb and the bearer termination T4 is used for the bearer towards the preceding MGW. + +![Diagram of Basic Mobile Terminating Call, Backward Bearer Establishment (network model)](8e80de0cac529b2c3775d677c5203133_img.jpg) + +The diagram illustrates the network model for a Basic Mobile Terminating Call with Backward Bearer Establishment. It features five main components: GMSC-S (top left), MSC-S (top right), MGWa (bottom left), MGWb (bottom center), and RNC/BSC (bottom right). GMSC-S and MSC-S are connected by a horizontal green dashed line. MGWa and MGWb are connected by a horizontal red dotted line. RNC/BSC is connected to MGWb by a horizontal red dotted line. Vertical blue solid lines connect GMSC-S to MGWa and MSC-S to MGWb. Each component box contains an internal icon representing a switching or routing function. MGWa and MGWb have additional labels: 'CTX2' and 'T4', 'T3' for MGWa; 'CTX1' and 'T2', 'T1' for MGWb. + +Diagram of Basic Mobile Terminating Call, Backward Bearer Establishment (network model) + +**Figure 6.7: Basic Mobile Terminating Call, Backward Bearer Establishment (network model)** + +Figure 6.8 shows the message sequence example for the basic mobile terminating call. In the example the GMSC server requests seizure of the incoming side bearer termination and establishment of the bearer first. After a notification of incoming side bearer establishment has been received from the MGW, the GMSC server requests seizure of the outgoing side bearer termination. The MSC server requests seizure of the network side bearer termination and establishment of the bearer when the Call Confirmed message is received from the UE. After a notification of the network side bearer establishment has been received from the MGW the MSC server requests seizure of the access side bearer termination. For a speech call, When the MSC server receives an alerting message, it requests MGW to provide a ringing tone to the calling party. When the MSC server receives an answer indication, it requests MGW to both-way through-connect the bearer. For a speech, when the MSC server receives an answer indication, it requests MGW to stop the ringing tone to the calling party and requests the possible activation of the interworking function in both bearer terminations. The (G)MSC server shall request the possible activation of the voice processing functions for the bearer terminations. + +![Sequence diagram for Basic Mobile Terminating Call, Backward Bearer Establishment. Lifelines: GMSC-S, MGWa, MSC-S, MGWb, RNC/BSC, UE. The diagram shows the flow of messages for HLR interrogation, bearer establishment on the incoming side, paging and security, and bearer establishment on the outgoing side.](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) + +``` + +sequenceDiagram + participant GMSC-S + participant MGWa + participant MSC-S + participant MGWb + participant RNC/BSC + participant UE + + Note over GMSC-S, MGWa: Initial Address + Bearer Information + rect rgb(200, 255, 200) + Note over GMSC-S, MGWa: HLR Interrogation + end + Note left of GMSC-S: Context ($) + GMSC-S->>MGWa: 1 ADD.request ($) + Note left of GMSC-S: Context (C2) + MGWa-->>GMSC-S: ADD.reply (T4) + Note right of MGWa: Establish Bearer + +Change Through-Connection + rect rgb(200, 255, 200) + Note over GMSC-S, MGWa: Bearer Establishment + end + GMSC-S->>MGWa: UP Init + MGWa-->>GMSC-S: UP Init Ack + Note left of GMSC-S: Context (C2) + GMSC-S->>MGWa: 2 NOTIFY.request(T4) + Note left of GMSC-S: Context (C2) + MGWa-->>GMSC-S: NOTIFY.reply(T4) + Note right of MGWa: Bearer Established + Note left of GMSC-S: Context (C2) + GMSC-S->>MGWa: 3 ADD.request ($) + Note left of GMSC-S: Context (C2) + MGWa-->>GMSC-S: ADD.reply (T3) + Note right of MGWa: Prepare Bearer + +Change Through-Connection + GMSC-S->>MSC-S: 4 Initial Address + rect rgb(200, 255, 200) + Note over MSC-S, UE: Paging + Security + end + MSC-S->>UE: 5 SETUP + UE-->>MSC-S: CALL CONFIRMED + Note left of MSC-S: Context ($) + MSC-S->>MGWb: 6 ADD.request ($) + Note left of MSC-S: Context (C1) + MGWb-->>MSC-S: ADD.reply (T2) + Note right of MGWb: Establish Bearer + +Change Through-Connection + rect rgb(200, 255, 200) + Note over MSC-S, MGWb: Bearer Establishment + end + MSC-S->>MGWb: UP Init + MGWb-->>MSC-S: UP Init Ack + Note left of MSC-S: Context (C1) + MSC-S->>MGWb: 7 NOTIFY.request(T2) + Note left of MSC-S: Context (C1) + MGWb-->>MSC-S: NOTIFY.reply(T2) + Note right of MGWb: Bearer Established + +``` + +Sequence diagram for Basic Mobile Terminating Call, Backward Bearer Establishment. Lifelines: GMSC-S, MGWa, MSC-S, MGWb, RNC/BSC, UE. The diagram shows the flow of messages for HLR interrogation, bearer establishment on the incoming side, paging and security, and bearer establishment on the outgoing side. + +**Figure 6.8/1: Basic Mobile Terminating Call, Backward Bearer Establishment +(message sequence chart)** + +![Sequence diagram for Basic Mobile Terminating Call, Backward Bearer Establishment. Lifelines: GMSC-S, MGWa, MSC-S, MGWb, RNC/BSC, UE. The diagram shows UMTS and GSM bearer establishment steps, including ADD.request, ADD.reply, RAB ASSIGNMENT REQ/COMPL, ASSIGNMENT REQUEST/COMPL, and various MOD.request/reply messages for tone and voice processing activation.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +The sequence diagram illustrates the message flow for a Basic Mobile Terminating Call with Backward Bearer Establishment. The lifelines are GMSC-S, MGWa, MSC-S, MGWb, RNC/BSC, and UE. + +**UMTS Bearer Establishment:** + +- MSC-S sends **ADD.request (\$)** to MGWb for Context (C1) (Step 8). +- MGWb responds with **ADD.reply (T1)** to MSC-S, performing "Prepare Bearer + Change Through-Connection". +- MSC-S sends **RAB ASSIGNMENT REQ** to RNC/BSC. +- RNC/BSC performs **Bearer Establish. and Iu UP Initializa.** (highlighted in green). +- RNC/BSC sends **RAB ASSIGNMENT COMPL** back to MSC-S. + +**GSM Bearer Establishment:** + +- MSC-S sends **ADD.request (T1)** to MGWb for Context (C1) (Step 9). +- MGWb responds with **ADD.reply (T1)** to MSC-S, performing "Reserve Circuit + Change Through-Connection". +- MSC-S sends **ASSIGNMENT REQUEST** to RNC/BSC. +- RNC/BSC sends **ASSIGNMENT COMPL** back to MSC-S. + +**Call Progression:** + +- MGWb sends **ALERTING** to UE. +- MSC-S sends **Address Complete** to MGWa. +- MGWa sends **Address Complete** to GMSC-S. + +**Post-Answer Processing:** + +- UE sends **CONNECT** to RNC/BSC. +- MSC-S sends **MOD.request (T2)** to MGWb for Context (C1) (Step 10). +- MGWb responds with **MOD.reply (T2)** to MSC-S, performing "Send Tone (start providing a ringing tone for a speech call)". +- UE sends **Answer** to RNC/BSC. +- MSC-S sends **MOD.request (T1)** to MGWb for Context (C1) (Step 11). +- MGWb responds with **MOD.reply (T1)** to MSC-S, performing "Change Through-Connection + Activate Interworking Function (when applicable) + Activate Voice Processing Function (when applicable)". +- MSC-S sends **MOD.request (T2)** to MGWb for Context (C1). +- MGWb responds with **MOD.reply (T2)** to MSC-S, performing "Stop Tone (stop providing a ringing tone for speech call) + Activate Interworking Function (when applicable) + Activate Voice Processing Function (when applicable)". +- MSC-S sends **MOD.request (T3)** to MGWb for Context (C2) (Step 12). +- MGWb responds with **MOD.reply (T3)** to MSC-S, performing "Activate Voice Processing Function (when applicable)". +- MSC-S sends **MOD.request (T4)** to MGWb for Context (C2). +- MGWb responds with **MOD.reply (T4)** to MSC-S, performing "Activate Voice Processing Function (when applicable)". +- MSC-S sends **Answer** to MGWa. +- MGWa sends **Answer** to GMSC-S. + +Sequence diagram for Basic Mobile Terminating Call, Backward Bearer Establishment. Lifelines: GMSC-S, MGWa, MSC-S, MGWb, RNC/BSC, UE. The diagram shows UMTS and GSM bearer establishment steps, including ADD.request, ADD.reply, RAB ASSIGNMENT REQ/COMPL, ASSIGNMENT REQUEST/COMPL, and various MOD.request/reply messages for tone and voice processing activation. + +**Figure 6.8/2: Basic Mobile Terminating Call, Backward Bearer Establishment (message sequence chart continue)** + +### 6.2.3 Terminating Call Establishment For Iu Interface on IP + +If IuCS on IP is supported by the MSC server, the Core Network side procedures described in 6.2.1 or 6.2.2 shall apply. For the access bearer termination, the exchange of IP addresses via call control procedures is described in this clause. + +Before the MSC server starts the access bearer assignment, the MSC server requests the MGW to prepare for the access bearer using the Prepare\_IP\_Transport procedure. The MSC server requests the MGW to provide an IP Transport Address and UDP Port and provides the MGW with the bearer characteristics. For speech calls, the MSC server shall provide the MGW with the speech coding information and conditionally GTT related information in accordance with 3GPP TS 23.226 [28]. For a non-speech call the MSC server also provides the MGW with a PLMN Bearer Capability [4]. After the MGW has replied with the IP address and UDP Port the MSC server requests access bearer assignment using the provided IP address and UDP Port in accordance with 3GPP TS 25.413 [26]. The IP addresses and UDP Ports of the MGW and the RNC are exchanged via the RANAP procedures. If the bearer transport is IP and IuUP mode is Transparent, when the MSC receives the RANAP RAB assignment response it shall send the RNC IP address and UDP Port to the MGW Access bearer termination using the Modify\_IP\_Transport\_Address procedure. + +If the bearer transport is IP and IuUP mode is Support, the MGW shall use the source IP address and UDP Port of the IuUP Init packet received from the radio access network as the destination address for subsequent downlink packets. + +The sequence is shown in figure 6.2.3/1. + +![Sequence diagram showing the signaling flow for terminating call establishment for Iu interface on IP between GMSC-S, MGWa, MSC-S, MGWb, RNC/BSC, and UE. It details context requests and replies, RAB assignments, and tone management.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +``` + + sequenceDiagram + participant GMSC-S + participant MGWa + participant MSC-S + participant MGWb + participant RNC/BSC + participant UE + + Note over GMSC-S, UE: For preceding signalling sequences relating to CN bearer call establishment see Figures 6.6/1 or 6.8/1 + + Note right of MSC-S: UMTS: + MSC-S->>MGWb: Context (C1) ⑨ ADD.request ($) Prepare IP Bearer ++ Change Through Connection + MGWb-->>MSC-S: Context (C1) ADD.reply (T1) + MSC-S->>RNC/BSC: RAB ASSIGNMENT REQ + RNC/BSC->>MGWb: IuUP Init (If IuUP in Support Mode) + MGWb-->>RNC/BSC: IuUP Init Ack + RNC/BSC->>MSC-S: RAB ASSIGNMENT COMPL + MSC-S->>MGWb: Context (C1) Modify.request (T1) Modify IP Address (If IuUP in Transparent Mode) + MGWb-->>MSC-S: Context (C1) Mod.reply (T1) + UE->>MSC-S: ALERTING + MSC-S->>GMSC-S: Address Complete + GMSC-S->>GMSC-S: Address Complete + MSC-S->>MGWb: Context (C1) ⑪ MOD.request (T2) + MGWb-->>MSC-S: Context (C1) MOD.reply (T2) (Send Tone: start providing a ringing tone for a speech call) + UE->>MSC-S: CONNECT + MSC-S->>MGWb: Context (C1) ⑫ MOD.request (T1) (Change Through-Connection + Activate Inter-Working Function + Activate Voice Processing Function) + MGWb-->>MSC-S: Context (C1) MOD.reply (T1) + MSC-S->>MGWb: Context (C1) MOD.request (T2) (Stop Tone + Activate Interworking Function + Activate Voice Processing Function) + MGWb-->>MSC-S: Context (C1) MOD.reply (T2) + MSC-S->>GMSC-S: Answer + GMSC-S->>MGWa: Context (C2) ⑬ MOD.request (T3) (Activate Voice Processing Function) + MGWa-->>GMSC-S: Context (C2) MOD.reply (T3) + GMSC-S->>MGWa: Context (C2) MOD.request (T4) (Activate Voice Processing Function) + MGWa-->>GMSC-S: Context (C2) MOD.reply (T4) + GMSC-S->>GMSC-S: Answer + +``` + +Sequence diagram showing the signaling flow for terminating call establishment for Iu interface on IP between GMSC-S, MGWa, MSC-S, MGWb, RNC/BSC, and UE. It details context requests and replies, RAB assignments, and tone management. + +**Figure 6.2.3/1 Terminating Call Establishment For Iu Interface on IP** + +## 6.2.4 Terminating Call Establishment For A Interface over IP + +If AoIP is supported by the MSC server, the Core Network side procedures described in 6.2.1 or 6.2.2 shall apply. For the access side termination, the exchange of IP addresses via call control procedures is described in this clause. + +Before the MSC server sends the Assignment Request to the BSC, the MSC server requests the MGW to reserve an RTP bearer termination using the Reserve RTP Connection Point procedure. The MSC server requests the MGW to reserve an IP Address and UDP Port and also may indicate that the IP interface type is for A interface over IP. The MGW reserves the AoIP termination and indicates the IP address and UDP port number to the MSC server. MSC server then requests access bearer assignment using the provided IP address and UDP Port. When MSC server receives the BSSMAP ASSIGNMENT COMPLETE message, it shall send the BSC IP address and UDP Port to the MGW Access bearer termination using the Configure RTP Connection Point procedure. + +The sequence is shown in figure 6.2.3/1. + +![Sequence diagram for Terminating Call Establishment For AoIP. Lifelines: GMSC -S, MGWa, MSC -S, MGWb, BSC, UE. The sequence starts with MSC -S sending an ADD.request to MGWb, followed by MGWb's response, then MSC -S sending an ASSIGNMENT REQ to BSC, BSC's response, MSC -S sending a Modify.request to MGWb, MGWb's response, and finally MSC -S sending an ALERTING message to BSC. Red text annotations indicate 'Reserve RTP Connection Point + Change Through Connection' and 'Configure RTP Connection Point'.](fd76efce549d3713543bb5ed9b023c2e_img.jpg) + +``` + +sequenceDiagram + participant GMSC -S + participant MGWa + participant MSC -S + participant MGWb + participant BSC + participant UE + + Note over MGWa, UE: For preceding signalling sequences see Figures 6.6/1 or 6.8/1 + + MSC -S->>MGWb: ADD.request ($) + + Note right of MGWb: Reserve RTP Connection Point + Change Through Connection + + MGWb-->>MSC -S: ADD.reply (T1) + + MSC -S->>BSC: ASSIGNMENT REQ + + BSC-->>MSC -S: ASSIGNMENT COMPL + + MSC -S->>MGWb: Modify.request (T1) + + Note right of MGWb: Configure RTP Connection Point + + MGWb-->>MSC -S: Mod.reply (T1) + + MSC -S->>BSC: ALERTING + + Note over MGWa, UE: For succeeding signalling sequences see Figures 6.6/1 or 6.8/1 + +``` + +Sequence diagram for Terminating Call Establishment For AoIP. Lifelines: GMSC -S, MGWa, MSC -S, MGWb, BSC, UE. The sequence starts with MSC -S sending an ADD.request to MGWb, followed by MGWb's response, then MSC -S sending an ASSIGNMENT REQ to BSC, BSC's response, MSC -S sending a Modify.request to MGWb, MGWb's response, and finally MSC -S sending an ALERTING message to BSC. Red text annotations indicate 'Reserve RTP Connection Point + Change Through Connection' and 'Configure RTP Connection Point'. + +Figure 6.2.3/1 Terminating Call Establishment For AoIP + +## 7 Call Clearing + +NOTE: All message sequence charts in this clause are examples. All valid call establishment message sequences can be derived from the example message sequences and associated message pre-conditions. + +## 7.1 Network Initiated + +The terms "incoming" and "outgoing" in the following text refers to the direction of propagation of the Release message, not to the direction of establishing the original call. + +### 7.1.1 GMSC server + +#### 7.1.1.1 Call clearing from the incoming side + +Once the Release message has been received from the preceding node, the GMSC server releases any MGW allocated resources for the incoming side. If any resources were seized in the MGW, the GMSC server shall use the Release Bearer and Release Termination procedures to indicate to the MGW to remove the incoming side bearer termination and that the bearer can be released towards the preceding MGW. After the resources in the MGW are released the GMSC server sends the Release Complete message to the preceding node. + +#### 7.1.1.2 Call clearing to the outgoing side + +The GMSC server sends the Release message to the succeeding node. Once the succeeding node has sent the Release Complete message, the GMSC server releases any MGW allocated resources for the outgoing side. If any resources were seized in the MGW, the GMSC server shall use the Release Bearer and Release Termination procedures to indicate to the MGW to remove the outgoing side bearer termination and that the bearer can be released towards the succeeding MGW. + +### 7.1.2 MSC server + +The network initiated call clearing shall be performed in accordance with 3GPP TS 23.108 [18]. The following clauses describe the additional requirements for the bearer independent CS core network. + +#### 7.1.2.1 Call clearing from the network side + +Once the Release message has been received from the preceding/succeeding node, the MSC server releases any MGW allocated resources for the network side. If any resources were seized in the MGW, the MSC server shall use the Release Bearer and Release Termination procedures to indicate to the MGW to remove the network side bearer termination and that the bearer can be released towards the preceding/succeeding MGW. After the resources in the MGW are released the MSC server sends the Release Complete message to the preceding/succeeding node (bullet 1 in figure 7.2). + +#### 7.1.2.2 Call clearing to the UE + +The MSC server initiates call clearing towards the UE and requests release of the associated radio resources as described in 3GPP TS 23.108[18]. Once the call clearing and the release of the associated radio resources have been completed, the MSC server releases any MGW allocated resources for the access side. If any resources were seized in the MGW, the MSC server uses the Release Termination procedure to requests the MGW to remove the access side bearer termination (bullet 2 or bullet 3 in figure 7.2). + +### 7.1.2.3 Example + +Figure 7.1 shows the network model for a network initiated clearing of the mobile call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. The MSC server seizes one context with two bearer terminations in the MGW. Bearer termination T1 is used for the bearer towards RNC/BSC and bearer termination T2 is used for the bearer towards succeeding MGW. + +![Figure 7.1: Network Initiated Call Clearing (Network model) diagram](aeb2a26a07219661191294dba528067a_img.jpg) + +The diagram illustrates a network model for call clearing. It features three main components: an RNC/BSC on the left, an MSC-S at the top, and an MGW at the bottom. The RNC/BSC is connected to the MSC-S via a green dashed line (call control signalling). The MSC-S is connected to the MGW via a solid blue line (bearer control signalling). The MGW has two bearer terminations, T1 and T2. T1 is connected to the RNC/BSC via a red dotted line (bearer). T2 is connected to a succeeding MGW (represented by a red dotted line extending to the right). The MGW is labeled 'CTXI MGW' and the RNC/BSC is labeled 'RNC/BSC'. + +Figure 7.1: Network Initiated Call Clearing (Network model) diagram + +**Figure 7.1: Network Initiated Call Clearing (Network model)** + +Figure 7.2 shows the message sequence example for the network initiated clearing of a mobile call. In the example the when the call clearing indication is received from the preceding/succeeding node, MSC server indicates that the network bearer can be released and to release the network side bearer termination. After the release of the network side bearer termination the MSC server indicates to the preceding/succeeding node that call clearing has been completed. The MSC server initiates call clearing towards the UE and requests release of the radio resource. After the response of the radio resource release is received then the MSC server requests release of the access side bearer termination. + +![Sequence diagram for Network Initiated Call Clearing showing interactions between UE, RNC/BSC, MSCS, and MGW. The diagram includes message exchanges like DISCONNECT, REL, RLC, IU RELEASE CMD, IU RELEASE COMPLETE, CLEAR COMMAND, and CLEAR COMPLETE, along with context management messages (MOD, SUB) and Bearer Release actions.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +The sequence diagram illustrates the Network Initiated Call Clearing process across four lifelines: UE, RNC/BSC, MSCS, and MGW. + +- Initial Release:** The MGW sends a **Release** message to the MSCS. The MSCS responds with **DISCONNECT** to the RNC/BSC, which then sends **REL** to the UE. The UE replies with **RLC** to the RNC/BSC. +- Context Management:** The MSCS sends **Context (C1)** and **MOD.request (T2)** to the MGW. The MGW responds with **Release Bearer** and **MOD.reply (T2)**. The MSCS then sends another **Context (C1)** and **SUB.request** to the MGW. The MGW responds with **Release Termination** and **SUB.reply**. Finally, the MSCS sends **Release Complete** to the MGW. +- Bearer Release:** A green box labeled **Bearer Release** spans from the MGW to the RNC/BSC. +- UMTS Path:** The MSCS sends **Context (C1)** and **IU RELEASE CMD** (marked with circled 2) to the RNC/BSC. The RNC/BSC sends **IU RELEASE COMPLETE** to the MSCS. The MSCS then sends **Context (C1)** and **SUB.request (T1)** to the MGW. The MGW responds with **Release Termination** and **SUB.reply (T1)**. +- GSM Path:** The MSCS sends **Context (C1)** and **CLEAR COMMAND** (marked with circled 3) to the RNC/BSC. The RNC/BSC sends **CLEAR COMPLETE** to the MSCS. The MSCS then sends **Context (C1)** and **SUB.request (T1)** to the MGW. The MGW responds with **Release Termination** and **SUB.reply (T1)**. + +Sequence diagram for Network Initiated Call Clearing showing interactions between UE, RNC/BSC, MSCS, and MGW. The diagram includes message exchanges like DISCONNECT, REL, RLC, IU RELEASE CMD, IU RELEASE COMPLETE, CLEAR COMMAND, and CLEAR COMPLETE, along with context management messages (MOD, SUB) and Bearer Release actions. + +Figure 7.2: Network Initiated Call Clearing (message sequence chart) + +## 7.2 User Initiated + +The user initiated call clearing shall be performed in accordance with 3GPP TS 23.108 [18]. The following clauses describe the additional requirements for the bearer independent CS core network. + +## 7.2.1 Void + +## 7.2.2 MSC server + +### 7.2.2.1 all clearing from the UE + +The UE initiated call clearing is performed and the release of the associated radio resources is performed as described in 3GPP TS 23.108 [18]. Once the call clearing and the associated radio resources release have been completed, the MSC server releases any MGW allocated resources for the access side. If any resources were seized in the MGW the MSC server uses the Release Termination procedure to requests the MGW to remove the access side bearer termination (bullet 1 or bullet 2 in figure 7.4). + +### 7.2.2.2 Call clearing to the network side + +The MSC server sends the Release message to the preceding/succeeding node. Once the preceding/succeeding node has sent the Release Complete, the MSC server releases any MGW allocated resources for the network side. If any resources were seized in the MGW server shall use the Release Bearer and Release Termination procedures to indicate to the MGW to remove the network side bearer termination and that the bearer can be released towards the preceding/succeeding MGW (bullet 3 in figure 7.4). + +### 7.2.2.3 Example + +Figure 7.3 shows the network model for a user initiated clearing of a mobile call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. The MSC server seizes one context with two bearer terminations in the MGW. Bearer termination T1 is used for the bearer towards RNC/BSC and bearer termination T2 is used for the bearer towards succeeding MGW. + +![Figure 7.3: User Initiated Call Clearing (Network model). The diagram shows three network elements: MSC-S (top), RNC/BSC (bottom left), and MGW (bottom center). A solid line (call control signalling) connects MSC-S to RNC/BSC. A dotted line (bearer control signalling) connects MSC-S to MGW. The MGW has two bearer terminations, T1 and T2. T1 is connected to the RNC/BSC via a dotted line. T2 is connected to a succeeding MGW (represented by a dotted line extending to the right).](62ee64afa2d368d732de66628cf2c841_img.jpg) + +Figure 7.3: User Initiated Call Clearing (Network model). The diagram shows three network elements: MSC-S (top), RNC/BSC (bottom left), and MGW (bottom center). A solid line (call control signalling) connects MSC-S to RNC/BSC. A dotted line (bearer control signalling) connects MSC-S to MGW. The MGW has two bearer terminations, T1 and T2. T1 is connected to the RNC/BSC via a dotted line. T2 is connected to a succeeding MGW (represented by a dotted line extending to the right). + +**Figure 7.3: User Initiated Call Clearing (Network model)** + +Figure 7.4 shows the message sequence example for the user initiated clearing of a mobile call. In the example the UE initiates call clearing towards the MSC server and the MSC server requests release of the radio resource. After the response of the radio resource release is received the MSC server requests the release of the access side bearer termination. The MSC server initiates call clearing towards the preceding/succeeding node. Once the preceding/succeeding node has indicated that call clearing has been completed, the MSC server indicates that the network bearer can be released and to release the network side bearer termination. + +![Figure 7.4: User Initiated Call Clearing (message sequence chart). The diagram shows the interaction between UE, RNC/BSC, MSCS, and MGW for call clearing. The process starts with DISCONNECT from UE to MSCS, followed by Release from MSCS to MGW. UE then sends REL and RLC to RNC/BSC. The RNC/BSC initiates UMTS: IU RELEASE CM (1), which leads to a Bearer Release. MSCS then sends IU RELEASE COMPLETE. For UMTS, MSCS sends Context (C1) SUB.request (T1) to MGW, which responds with Release Termination. MSCS then sends Context(C1) SUB.reply (T1). For GSM, RNC/BSC sends CLEAR COMMAND (2) to MSCS, which responds with CLEAR COMPLETE. MSCS then sends Context (C1) SUB.request (T1) to MGW, which responds with Release Termination. MSCS then sends Context(C1) SUB.reply. MSCS then sends Release Complete (3) to RNC/BSC. For GSM, MSCS sends Context (C1) MOD.request (T2) to MGW, which responds with Release Bearer. MSCS then sends Context (C1) MOD.reply (T2). MSCS then sends Context (C1) SUB.request (T2) to MGW, which responds with Release Termination. MSCS then sends Context (C1) SUB.reply. Finally, a Bearer Release is shown at the MGW.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSCS + participant MGW + + Note left of UE: User Initiated Call Clearing + UE->>MSCS: DISCONNECT + MSCS->>MGW: Release + UE->>RNC/BSC: REL + UE->>MSCS: RLC + Note right of RNC/BSC: UMTS: + RNC/BSC->>MSCS: IU RELEASE CM (1) + Note right of MSCS: Bearer Release + MSCS->>RNC/BSC: IU RELEASE COMPLETE + Note right of MSCS: Context (C1) + MSCS->>MGW: SUB.request (T1) + MGW->>MSCS: Release Termination + Note right of MSCS: Context(C1) + MSCS->>MGW: SUB.reply (T1) + Note right of RNC/BSC: GSM: + RNC/BSC->>MSCS: CLEAR COMMAND (2) + MSCS->>RNC/BSC: CLEAR COMPLETE + Note right of MSCS: Context (C1) + MSCS->>MGW: SUB.request (T1) + MGW->>MSCS: Release Termination + Note right of MSCS: Context(C1) + MSCS->>MGW: SUB.reply + Note right of MSCS: (3) + MSCS->>RNC/BSC: Release Complete + Note right of MSCS: Context (C1) + MSCS->>MGW: MOD.request (T2) + MGW->>MSCS: Release Bearer + Note right of MSCS: Context (C1) + MSCS->>MGW: MOD.reply (T2) + Note right of MSCS: Context (C1) + MSCS->>MGW: SUB.request (T2) + MGW->>MSCS: Release Termination + Note right of MSCS: Context (C1) + MSCS->>MGW: SUB.reply + Note right of MGW: Bearer Release + +``` + +Figure 7.4: User Initiated Call Clearing (message sequence chart). The diagram shows the interaction between UE, RNC/BSC, MSCS, and MGW for call clearing. The process starts with DISCONNECT from UE to MSCS, followed by Release from MSCS to MGW. UE then sends REL and RLC to RNC/BSC. The RNC/BSC initiates UMTS: IU RELEASE CM (1), which leads to a Bearer Release. MSCS then sends IU RELEASE COMPLETE. For UMTS, MSCS sends Context (C1) SUB.request (T1) to MGW, which responds with Release Termination. MSCS then sends Context(C1) SUB.reply (T1). For GSM, RNC/BSC sends CLEAR COMMAND (2) to MSCS, which responds with CLEAR COMPLETE. MSCS then sends Context (C1) SUB.request (T1) to MGW, which responds with Release Termination. MSCS then sends Context(C1) SUB.reply. MSCS then sends Release Complete (3) to RNC/BSC. For GSM, MSCS sends Context (C1) MOD.request (T2) to MGW, which responds with Release Bearer. MSCS then sends Context (C1) MOD.reply (T2). MSCS then sends Context (C1) SUB.request (T2) to MGW, which responds with Release Termination. MSCS then sends Context (C1) SUB.reply. Finally, a Bearer Release is shown at the MGW. + +Figure 7.4: User Initiated Call Clearing (message sequence chart) + +## 7.3 (G)MSC server Initiated + +The following clauses describe the additional requirements for (G)MSC server initiated call clearing in the bearer independent CS core network. + +### 7.3.1 GMSC server + +#### 7.3.1.1 Call clearing to the destination side + +If the call is already established towards the destination, call clearing is performed as described in clause 7.1.1, call clearing to the outgoing side. + +#### 7.3.1.2 Call clearing to the originating side + +The call clearing to the originating side is performed as described in clause 7.1.1, call clearing to the outgoing side. + +## 7.3.2 MSC server + +### 7.3.2.1 Call clearing to the UE + +The call clearing to the UE is performed as described in clause 7.1.2, call clearing to the UE (bullet 1 and bullet 2 in figure 7.6). + +### 7.3.2.2 Call clearing to the network side + +If the call is already established towards the network side, the call clearing to the network side is performed as described in clause 7.2.2, call clearing to the network side (bullet 3 in figure 7.6). + +### 7.3.2.3 Example + +Figure 7.5 shows the network model for the MSC server initiated clearing of the mobile call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. The MSC server seizes one context with two bearer terminations in the MGW. Bearer termination T1 is used for the bearer towards RNC/BSC and bearer termination T2 is used for the bearer towards succeeding MGW. + +![Figure 7.5: MSC Server Initiated Call Clearing (Network model). The diagram shows three network elements: MSC-S (top), RNC/BSC (bottom left), and MGW (bottom center). MSC-S is connected to RNC/BSC by a green dashed line (bearer control signalling). MSC-S is connected to MGW by a solid blue line (call control signalling). MGW is connected to RNC/BSC by a red dotted line (bearer). MGW has two bearer terminations labeled T1 and T2. T1 is connected to the red dotted line towards RNC/BSC. T2 is connected to a red dotted line extending to the right towards a succeeding MGW.](7156cf400ef0e19f9d06a5d0549834a3_img.jpg) + +Figure 7.5: MSC Server Initiated Call Clearing (Network model). The diagram shows three network elements: MSC-S (top), RNC/BSC (bottom left), and MGW (bottom center). MSC-S is connected to RNC/BSC by a green dashed line (bearer control signalling). MSC-S is connected to MGW by a solid blue line (call control signalling). MGW is connected to RNC/BSC by a red dotted line (bearer). MGW has two bearer terminations labeled T1 and T2. T1 is connected to the red dotted line towards RNC/BSC. T2 is connected to a red dotted line extending to the right towards a succeeding MGW. + +**Figure 7.5: MSC Server Initiated Call Clearing (Network model)** + +Figure 7.6 shows the message sequence example for the MSC server initiated clearing of a mobile call. In the example the MSC server initiates call clearing of the network side and the access side. After the call clearing towards the UE and the release of the radio resource have been completed the MSC server requests release of the access side bearer termination. Once the preceding/succeeding node has indicated that call clearing has been completed, the MSC server indicates that the network bearer can be released and to release the network side bearer termination. + +![Figure 7.6: MSC Server Initiated Call Clearing (message sequence chart). The diagram shows the interaction between UE, RNC/BSC, MSGS, and MGW for call clearing. It includes steps for DISCONNECT, REL, RLC, UMTS (IU RELEASE CM, Bearer Release, IU RELEASE COMPLETE), and GSM (CLEAR COMMAND, CLEAR COMPLETE) procedures. The MGW sends Release, Release Termination, Release Bearer, and Bearer Release messages.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSGS + participant MGW + + Note left of UE: Error! No + Note right of MGW: Error! No text of specified style in + + UE->>RNC/BSC: DISCONNECT + RNC/BSC->>MSG: REL + MSG->>UE: RLC + + Note right of RNC/BSC: UMTS: + RNC/BSC->>MSG: IU RELEASE CM (1) + Note right of MSG: Bearer Release + MSG->>RNC/BSC: IU RELEASE COMPLETE + Note right of MSG: Context(C1) + MSG->>MGW: SUB.request (T1) + MGW->>MSG: SUB.reply (T1) Release Termination + Note right of MSG: Context(C1) + + Note right of RNC/BSC: GSM: + RNC/BSC->>MSG: CLEAR COMMAND (2) + MSG->>RNC/BSC: CLEAR COMPLETE + Note right of MSG: Context (C1) + MSG->>MGW: SUB.request(T1) + MGW->>MSG: SUB.reply(T1) Release Termination + Note right of MSG: Context (C1) + MSG->>MGW: Release Complete (3) + Note right of MSG: Context (C1) + MSG->>MGW: MOD.request (T2) Release Bearer + MGW->>MSG: MOD.reply (T2) + Note right of MSG: Context (C1) + MSG->>MGW: SUB.request(T2) + MGW->>MSG: SUB.reply(T2) Release Termination + Note right of MSG: Context (C1) + Note right of MGW: Bearer Release + +``` + +Figure 7.6: MSC Server Initiated Call Clearing (message sequence chart). The diagram shows the interaction between UE, RNC/BSC, MSGS, and MGW for call clearing. It includes steps for DISCONNECT, REL, RLC, UMTS (IU RELEASE CM, Bearer Release, IU RELEASE COMPLETE), and GSM (CLEAR COMMAND, CLEAR COMPLETE) procedures. The MGW sends Release, Release Termination, Release Bearer, and Bearer Release messages. + +Figure 7.6: MSC Server Initiated Call Clearing (message sequence chart) + +## 7.4 MGW Initiated + +The following clauses describe the additional requirements for MGW initiated call clearing in the bearer independent CS core network. + +### 7.4.1 GMSC server + +#### 7.4.1.1 Bearer released on the destination side + +After the GMSC server has received the Bearer Released procedure from the MGW, it shall send the Release message to the succeeding node. Once the succeeding node has sent the Release Complete message, the GMSC server releases + +any MGW allocated resources for the destination side. The GMSC server uses the Release Termination procedure to request the MGW to remove the destination side bearer termination. + +The call clearing to the incoming side is performed as described in clause 7.1.1.2, call clearing to the outgoing side. + +#### 7.4.1.2 Bearer released on the originating side + +After the GMSC server has received the Bearer Released procedure from the MGW, the GMSC server sends the Release message to the preceding node. Once the preceding node has sent the Release Complete message, the GMSC server releases any MGW allocated resources for the originating side. The GMSC server uses the Release Termination procedure to request the MGW to remove the originating side bearer termination. + +If the call is already established towards the destination side, call clearing to the destination side is performed as described in clause 7.1.1.2, call clearing to the outgoing side. + +### 7.4.2 MSC server + +#### 7.4.2.1 Bearer released on the access side + +After the MSC server has received the Bearer Released procedure from the MGW, the MSC server initiates the call clearing towards the UE and requests release of the allocated radio resources as described in 3GPP TS 23.108 [18]. Once the call clearing and the radio resources release have been completed, the MSC server releases any MGW allocated resources for the access side. The MSC server uses the Release Termination procedure to request the MGW to remove the access side bearer termination. + +If the call is already established towards the network side, call clearing to the network side is performed as described in clause 7.2, call clearing to the network side. + +#### 7.4.2.2 Bearer released on the network side + +After the MSC server has received the Bearer Released procedure from the MGW, the MSC server sends the Release message to the preceding/succeeding node. Once the preceding/succeeding node has sent the Release Complete message, the MSC server releases any MGW allocated resources for the network side. The MSC server uses the Release Termination procedure to request the MGW to remove the network side bearer termination (bullet 1 and bullet 2 in figure 7.8). + +Call clearing to the UE is performed as described in clause 7.1.2.2, call clearing to the UE (bullet 3 in figure 7.8). + +#### 7.4.2.3 Example + +Figure 7.7 shows the network model for an MGW initiated clearing of a mobile call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in A/Gb mode for the A-interface) and the bearer. The MSC server seizes one context with two bearer terminations in the MGW. Bearer termination T1 is used for the bearer towards RNC/BSC and bearer termination T2 is used for the bearer towards succeeding MGW. + +![Figure 7.7: MGW Initiated Call Clearing (Network model). The diagram shows three network elements: RNC/BSC, MSC-S, and MGW. The RNC/BSC is connected to the MSC-S via a dashed green line (call control signalling). The MSC-S is connected to the MGW via a solid blue line (bearer control signalling). The MGW has two bearer terminations, T1 and T2. T1 is connected to the RNC/BSC via a dotted red line (bearer control signalling). T2 is connected to a succeeding MGW via a dotted red line (bearer control signalling). The MGW is also connected to the RNC/BSC via a dotted red line (bearer control signalling).](907cc0e0bfee6288b926d1c38c232e5d_img.jpg) + +Figure 7.7: MGW Initiated Call Clearing (Network model). The diagram shows three network elements: RNC/BSC, MSC-S, and MGW. The RNC/BSC is connected to the MSC-S via a dashed green line (call control signalling). The MSC-S is connected to the MGW via a solid blue line (bearer control signalling). The MGW has two bearer terminations, T1 and T2. T1 is connected to the RNC/BSC via a dotted red line (bearer control signalling). T2 is connected to a succeeding MGW via a dotted red line (bearer control signalling). The MGW is also connected to the RNC/BSC via a dotted red line (bearer control signalling). + +**Figure 7.7: MGW Initiated Call Clearing (Network model)** + +Figure 7.8 shows the message sequence example for the MGW initiated clearing of a mobile call. After the MSC server is notified that the MGW has released the network side bearer, the MSC server initiates call clearing of the network side + +and the access side. After the call clearing towards the UE and the radio resource release have been completed the MSC server requests release of the access side bearer termination. Once the preceding/succeeding node has indicated that call clearing has been completed, the MSC server requests the release of the network side bearer termination. + +![Figure 7.8: MGW Initiated Call Clearing (message sequence chart). The diagram shows the interaction between UE, RNC/BSC, MSC-S, and MGW. The process starts with the MGW sending NOTIFY.request (T2) to the MSC-S, which responds with NOTIFY.reply (T2). The MGW then sends a Release message to the MSC-S. The MSC-S sends a DISCONNECT message to the RNC/BSC, which responds with REL and RLC messages. The RNC/BSC then sends an IU RELEASE CMD to the MSC-S, marked with a circled '1'. A green bar labeled 'Bearer Release' spans the next step. The MSC-S sends an IU RELEASE COMPLETE message to the RNC/BSC. The RNC/BSC then sends a CLEAR COMMAND to the MSC-S, marked with a circled '2'. The MSC-S responds with a CLEAR COMPLETE message. The MSC-S then sends Context (C1) and SUB.request (T1) to the MGW, which responds with Context(C1) and SUB.reply (T1), labeled 'Release Termination'. The MSC-S sends a CLEAR COMPLETE message to the RNC/BSC, marked with a circled '3'. The MSC-S then sends Context (C1) and SUB.request (T2) to the MGW, which responds with Context(C1) and SUB.reply (T2), labeled 'Release Termination'.](03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S + participant MGW + + Note right of MGW: Bearer Released + MGW->>MSC-S: NOTIFY.request (T2) + MSC-S-->>MGW: NOTIFY.reply (T2) + MGW->>MSC-S: Release + MSC-S->>RNC/BSC: DISCONNECT + RNC/BSC-->>MSC-S: REL + RNC/BSC-->>UE: RLC + Note right of RNC/BSC: UMTS: + RNC/BSC->>MSC-S: IU RELEASE CMD (1) + Note right of MSC-S: Bearer Release + MSC-S->>RNC/BSC: IU RELEASE COMPLETE + Note right of RNC/BSC: GSM: + RNC/BSC->>MSC-S: CLEAR COMMAND (2) + MSC-S-->>RNC/BSC: CLEAR COMPLETE + Note right of MSC-S: Release Termination + MSC-S->>MGW: Context (C1) + MSC-S->>MGW: SUB.request (T1) + MGW-->>MSC-S: Context(C1) + MGW-->>MSC-S: SUB.reply (T1) + RNC/BSC->>MSC-S: CLEAR COMPLETE (3) + Note right of MSC-S: Release Termination + MSC-S->>MGW: Context (C1) + MSC-S->>MGW: SUB.request (T2) + MGW-->>MSC-S: Context(C1) + MGW-->>MSC-S: SUB.reply (T2) + +``` + +Figure 7.8: MGW Initiated Call Clearing (message sequence chart). The diagram shows the interaction between UE, RNC/BSC, MSC-S, and MGW. The process starts with the MGW sending NOTIFY.request (T2) to the MSC-S, which responds with NOTIFY.reply (T2). The MGW then sends a Release message to the MSC-S. The MSC-S sends a DISCONNECT message to the RNC/BSC, which responds with REL and RLC messages. The RNC/BSC then sends an IU RELEASE CMD to the MSC-S, marked with a circled '1'. A green bar labeled 'Bearer Release' spans the next step. The MSC-S sends an IU RELEASE COMPLETE message to the RNC/BSC. The RNC/BSC then sends a CLEAR COMMAND to the MSC-S, marked with a circled '2'. The MSC-S responds with a CLEAR COMPLETE message. The MSC-S then sends Context (C1) and SUB.request (T1) to the MGW, which responds with Context(C1) and SUB.reply (T1), labeled 'Release Termination'. The MSC-S sends a CLEAR COMPLETE message to the RNC/BSC, marked with a circled '3'. The MSC-S then sends Context (C1) and SUB.request (T2) to the MGW, which responds with Context(C1) and SUB.reply (T2), labeled 'Release Termination'. + +Figure 7.8: MGW Initiated Call Clearing (message sequence chart) + +## 7.5 Call Clearing for Iu Interface on IP + +Procedures for Call Clearing where the Iu Interface is on IP are as described in sections 7.1 to 7.4, with the exception that only the Access side procedures apply and the Release Bearer procedure is not sent. For Iu Interface on IP, the Release Termination procedures for IP are used to clear the MGW termination from the (G)MSC. + +### Example + +Figure 7.9 shows the network model for a network initiated clearing of the mobile call when IP transport is used on the Iu interface. The 'squared' line represents the call control signalling. The 'dotted' line represents the bearer. The MSC server releases one context with two bearer terminations in the MGW. Bearer termination T1 is used for the bearer towards RNC/BSC and bearer termination T2 is used for the bearer towards succeeding MGW. + +![Figure 7.9 Network Initiated Call Clearing (Network model) diagram](848073118eebfdbfdb9a60e3923fe0b3_img.jpg) + +The diagram shows a network architecture for call clearing. + - **MSC-S** (Mobile Switching Center Server) is at the top. + - **RNC** (Radio Network Controller) is on the left. + - **MGW** (Media Gateway) is at the bottom center, containing a context **CTX1** with two terminations, **T1** and **T2**. + - A blue solid vertical line connects MSC-S to the MGW context. + - A green dashed line (representing call control signalling) connects MSC-S to RNC and also extends horizontally to the right from MSC-S. + - A red dotted line (representing the bearer) connects RNC to MGW termination T1, and another red dotted line extends horizontally to the right from MGW termination T2. + +Figure 7.9 Network Initiated Call Clearing (Network model) diagram + +**Figure 7.9 Network Initiated Call Clearing (Network model)** + +Figure 7.10 shows the message sequence example for the network initiated clearing of a mobile call when IP transport is used on the Iu Interface. In the example when the call clearing indication is received from the preceding/succeeding node, MSC server indicates that network bearer can be released and to release the network side bearer termination. After the release of the network side bearer termination the MSC server indicates to the preceding/succeeding node that call clearing has been completed. The MSC server initiates call clearing towards the UE and requests release of the radio resource. After the response of the radio resource release is received then the MSC server requests release of the access side bearer termination. + +![Figure 7.10 Network Initiated Call Clearing (message sequence chart). The diagram shows the interaction between UE, RNC, MSC-S, and M GW for call clearing. It is divided into two main parts: one for GERAN (steps 1 and 2) and one for UMTS (steps 3 and 4).](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC + participant MSC-S + participant M GW + + Note right of M GW: Release + M GW->>MSC-S: Release Bearer + MSC-S->>RNC: Context (C1) MOD.request (T2) + RNC->>MSC-S: Context (C1) MOD.reply (T2) + MSC-S->>RNC: Context (C1) SUB.request (T2) + Note left of MSC-S: 1 + RNC->>MSC-S: Context (C1) SUB.reply (T2) + MSC-S->>M GW: Release Complete + Note right of M GW: Bearer Release + UE->>RNC: DISCONNECT + RNC->>UE: REL + RNC->>MSC-S: Context (C1) + MSC-S->>RNC: Context (C1) + Note left of MSC-S: 2 + RNC->>UE: RLC + Note right of RNC: UMTS: + RNC->>MSC-S: IU RELEASE CMD + MSC-S->>RNC: IU RELEASE COMPLETE + MSC-S->>RNC: Context (C1) SUB.request (T1) + RNC->>MSC-S: Context(C1) SUB.reply (T1) + Note right of RNC: Release Termination + +``` + +Figure 7.10 Network Initiated Call Clearing (message sequence chart). The diagram shows the interaction between UE, RNC, MSC-S, and M GW for call clearing. It is divided into two main parts: one for GERAN (steps 1 and 2) and one for UMTS (steps 3 and 4). + +Figure 7.10 Network Initiated Call Clearing (message sequence chart) + +## 8 Handover/Relocation + +NOTE: All message sequence charts in this clause are examples. All valid handover/relocation message sequences can be derived from the example message sequences and associated message pre-conditions. + +### 8.1 UMTS to UMTS + +In the context of the following clauses, the terms RNS or RNC refer also to a GERAN BSS or BSC (respectively) when serving an UE in Iu mode. + +#### 8.1.1 Intra-MSC SRNS/SBSS Relocation + +The procedures specified in 3GPP TS 23.009 [8] for "Intra-3G\_MSC SRNS Relocation" shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +##### 8.1.1.1 Relocation Required + +When the Relocation Required message is received, the MSC server requests the MGW to provide a binding reference and a bearer address, using the Prepare Bearer procedure. For speech calls, the MSC server shall provide the MGW + +with the speech coding information for the bearer. For non-speech calls the MSC server also provides the MGW with the same PLMN Bearer Capability [4] as was provided at the last access bearer assignment. The MSC server uses the Change Flow Direction Procedure to request the MGW to set the Handover Device to initial state. The MSC server sends the Relocation Request message, containing the bearer address and the binding reference, to RNC-B (bullet 1 in figure 8.2/1). + +For Relocation towards GERAN Iu mode the GERAN capabilities of the target cell will be indicated to the MSC-Server within the RANAP RELOCATION REQUIRED message if the target cell provides different capabilities than the current cell. If no information about the GERAN capabilities of the target cell are received within this message, the MSC-Server shall assume that the GERAN target cell will provide the same capabilities as the current cell (for details see [29]). The MSC server shall indicate to GERAN the selected services within the RANAP RELOCATION REQUEST message. The MSC server shall not set codec information in the NAS Synchronisation Indicator (see [4]). Instead it shall set codec information in the GERAN BSC container. + +#### 8.1.1.2 Relocation Command/Relocation Detect + +When the MSC server sends the Relocation Command message or alternatively if it receives the Relocation Detect message, the MSC server uses the Change Flow Direction procedure to request the MGW to set the Handover Device to intermediate state (bullet 2 in figure 8.2/1). + +#### 8.1.1.3 Relocation Complete + +When the MSC server receives the Relocation Complete message, it requests RNC-A to release the IU. The MSC server also requests the MGW to set the Handover Device to its final state by removing the bearer termination towards RNC-A, using the Release Termination procedure (bullet 3 in figure 8.2/2). + +#### 8.1.1.4 Interworking function + +The interworking function used by the MGW before relocation will also be used after relocation. + +#### 8.1.1.5 Codec handling + +The MGW may include a speech transcoder based upon the speech coding information provided to each bearer termination. + +#### 8.1.1.6 Voice Processing function + +After relocation, the MGW may continue or modify voice-processing function(s) provided to each bearer termination. + +#### 8.1.1.7 Handling of multiple bearers (multicall) + +If the UE is engaged with multiple bearers all procedures related to the handling of bearers and terminations described for the relocation of a single bearer shall be repeated for each bearer. + +#### 8.1.1.8 Failure Handling in MSC server + +When a procedure between the MSC server and the MGW fails the MSC server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If MGW resources have been already seized at the target access side then the resources shall be released using the Release Termination procedure. If the call is to be cleared, then it shall be handled as described in clause 7.3. + +#### 8.1.1.9 Example + +Figure 8.1 shows the network model for the Intra-MSC SRNS Relocation. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. The bearer termination T1 is used for the bearer towards RNC-A, bearer termination T3 is used for the bearer towards RNC-B and the bearer termination T2 is used for the bearer towards the succeeding/preceding MGW. + +![Figure 8.1: Intra-MSC SRNS Relocation (network model). The diagram shows three stages: 'Before Relocation', 'During Relocation', and 'After Relocation'. In 'Before Relocation', RNC A is connected to MSC-S via a dashed green line, and MSC-S is connected to CTXI MGW via a solid blue line. CTXI MGW has two red dotted lines labeled T1 and T2. In 'During Relocation', RNC B is added, connected to MSC-S via a dashed green line, and to CTXI MGW via a red dotted line labeled T3. In 'After Relocation', RNC A is disconnected, and RNC B is connected to MSC-S via a dashed green line and to CTXI MGW via a red dotted line labeled T3. The CTXI MGW still has red dotted lines labeled T1 and T2.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +**Before Relocation:** + +**During Relocation:** + +**After Relocation:** + +Figure 8.1: Intra-MSC SRNS Relocation (network model). The diagram shows three stages: 'Before Relocation', 'During Relocation', and 'After Relocation'. In 'Before Relocation', RNC A is connected to MSC-S via a dashed green line, and MSC-S is connected to CTXI MGW via a solid blue line. CTXI MGW has two red dotted lines labeled T1 and T2. In 'During Relocation', RNC B is added, connected to MSC-S via a dashed green line, and to CTXI MGW via a red dotted line labeled T3. In 'After Relocation', RNC A is disconnected, and RNC B is connected to MSC-S via a dashed green line and to CTXI MGW via a red dotted line labeled T3. The CTXI MGW still has red dotted lines labeled T1 and T2. + +**Figure 8.1: Intra-MSC SRNS Relocation (network model)** + +Figure 8.2 shows the message sequence example for the Intra-MSC SRNS Relocation. + +It is assumed that the Handover Device is located in the MGW, which has been selected for the call establishment by the MSC server. The MSC server controls the call and the mobility management. It is also assumed that only one bearer has been established towards RNC-A. + +In the example the MSC server requests seizure of RNC-B side bearer termination with specific flow directions. The MSC server orders the establishment of the bearer by sending Relocation Request towards RNC-B. When the relocation is detected in RNC-B the MSC server requests to change the flow directions between the terminations within the context. When the MSC server receives a Relocation Complete indication from RNC-B it orders RNC-A to release the IU. This action causes release of the bearer between the RNC and the MGW. Finally the MSC server requests the MGW to release RNC-A side bearer termination. + +![Sequence diagram for Intra-MSC SRNS Relocation (Figure 8.2/1). Lifelines: RNC A, MSC-S, MGW, RNC B. The process involves: 1. RNC A sends 'Iu Relocation Required' to MSC-S. 2. MSC-S sends 'Context(C1)' to MGW. 3. MGW responds with 'TopDescr({*,$,isolate}, {T2,$,oneway})+ADD.Request($)' and 'Prepare bearer, Change Flow Direction'. 4. MGW sends 'TopDescr()+ADD.reply(T3)' back to MSC-S. 5. MSC-S sends 'Iu Relocation Request' to RNC B. 6. A 'Bearer Establishment' block occurs between MGW and RNC B. 7. RNC B sends 'Iu Relocation Request-Ack' to MSC-S. 8. MSC-S sends 'Iu Relocation Command' to RNC A. 9. A 'Relocation execution triggered in target RNC' block occurs in RNC B. 10. RNC B sends 'Iu Relocation Detect' to MSC-S. 11. MSC-S sends 'Context(C1)' to MGW. 12. MGW responds with 'TopDescr({T2,T1,oneway}, {T2,T3,bothway})' and 'Change Flow Direction'. 13. MGW sends 'TopDescr()' back to MSC-S. Callouts 1 and 2 are present on the MSC-S lifeline.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +Sequence diagram for Intra-MSC SRNS Relocation (Figure 8.2/1). Lifelines: RNC A, MSC-S, MGW, RNC B. The process involves: 1. RNC A sends 'Iu Relocation Required' to MSC-S. 2. MSC-S sends 'Context(C1)' to MGW. 3. MGW responds with 'TopDescr({\*,\$,isolate}, {T2,\$,oneway})+ADD.Request(\$)' and 'Prepare bearer, Change Flow Direction'. 4. MGW sends 'TopDescr()+ADD.reply(T3)' back to MSC-S. 5. MSC-S sends 'Iu Relocation Request' to RNC B. 6. A 'Bearer Establishment' block occurs between MGW and RNC B. 7. RNC B sends 'Iu Relocation Request-Ack' to MSC-S. 8. MSC-S sends 'Iu Relocation Command' to RNC A. 9. A 'Relocation execution triggered in target RNC' block occurs in RNC B. 10. RNC B sends 'Iu Relocation Detect' to MSC-S. 11. MSC-S sends 'Context(C1)' to MGW. 12. MGW responds with 'TopDescr({T2,T1,oneway}, {T2,T3,bothway})' and 'Change Flow Direction'. 13. MGW sends 'TopDescr()' back to MSC-S. Callouts 1 and 2 are present on the MSC-S lifeline. + +Figure 8.2/1: Intra-MSC SRNS Relocation (message sequence chart) + +![Sequence diagram for Intra-MSC SRNS Relocation (Figure 8.2/2). Lifelines: RNC A, MSC-S, MGW, RNC B. The process involves: 1. RNC B sends 'Iu Relocation Complete' to MSC-S. 2. MSC-S sends 'Iu Release Command' to RNC A. 3. A 'Release of bearer' block occurs between RNC A and MGW. 4. RNC A sends 'Iu Release Complete' to MSC-S. 5. MSC-S sends 'Context(C1)' to MGW. 6. MGW responds with 'SUB.request (T1)'. 7. MGW sends 'SUB.reply (T1)' back to MSC-S. 8. MGW sends 'Release Termination' to RNC B. Callout 3 is present on the MSC-S lifeline.](977811d1c73b74f801be9f4c376694ca_img.jpg) + +Sequence diagram for Intra-MSC SRNS Relocation (Figure 8.2/2). Lifelines: RNC A, MSC-S, MGW, RNC B. The process involves: 1. RNC B sends 'Iu Relocation Complete' to MSC-S. 2. MSC-S sends 'Iu Release Command' to RNC A. 3. A 'Release of bearer' block occurs between RNC A and MGW. 4. RNC A sends 'Iu Release Complete' to MSC-S. 5. MSC-S sends 'Context(C1)' to MGW. 6. MGW responds with 'SUB.request (T1)'. 7. MGW sends 'SUB.reply (T1)' back to MSC-S. 8. MGW sends 'Release Termination' to RNC B. Callout 3 is present on the MSC-S lifeline. + +Figure 8.2/2: Intra-MSC SRNS Relocation (message sequence chart) + +## 8.1.2 Basic Inter-MSC SRNS/SBSS Relocation + +The procedures specified in 3GPP TS 23.009 [8] for "Basic Relocation Procedure Requiring a Circuit Connection between 3G\_MSC-A and 3G\_MSC-B" shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +### 8.1.2.1 MSC-A/MGW-A + +#### 8.1.2.1.1 Relocation Required + +For Relocation towards GERAN Iu mode the GERAN capabilities of the target cell will be indicated to the MSC-A server within the RANAP RELOCATION REQUIRED message if the target cell provides different capabilities than the current cell. If no information about the GERAN capabilities of the target cell are received within this message, the MSC-A server shall assume that the GERAN target cell will provide the same capabilities as the current cell (for details see [29]). + +The MSC-A server shall indicate to the MSC-B server the GERAN capabilities of the target cell, if available, with the MAP Prepare Handover request. For speech calls, the MSC-A server shall additionally indicate to the MSC-B server the selected codec, the list of supported codecs, and the currently used codec. + +Furthermore, the MSC-A server shall indicate to the GERAN the selected service within the RANAP RELOCATION REQUEST message and shall set the RAB parameters within the RANAP RELOCATION REQUEST message according to the selected service. The MSC server shall not set codec information in the NAS Synchronisation Indicator (see [4]). Instead it shall set codec information in the GERAN BSC container.. + +#### 8.1.2.1.2 Bearer establishment between MGW-A and MGW-B + +The handling of the bearer establishment is as described for a Basic Mobile Originating Call, using either forward or backward bearer establishment. For speech calls, the MSC-A server shall provide the MGW-A with the speech coding information for the bearer. For non-speech calls, the MSC-A server shall provide MGW-A with the same PLMN Bearer Capability [4] as was provided at the last access bearer assignment. The MSC-A server also uses the Change Flow Direction procedure to request MGW-A to set the Handover Device to initial state (bullet 3 in figure 8.4/1). + +#### 8.1.2.1.3 Relocation Command/Relocation Detect + +When the MSC-A server sends the Relocation Command message or alternatively if it receives the Relocation Detect message, the MSC-A server uses the Change Flow Direction procedure to requests MGW-A to set the Handover Device to intermediate state (bullet 4 in figure 8.4/2). + +#### 8.1.2.1.4 Relocation Complete + +When the MSC-A server receives the Relocation Complete message, it requests RNC-A to release the IU. The MSC-A server also requests MGW-A to set the Handover Device to its final state by removing the bearer termination towards RNC-A, using the Release Termination procedure (bullet 5 in figure 8.4/2). + +#### 8.1.2.1.5 Interworking function + +The interworking function used by MGW-A before relocation will also be used after relocation. + +#### 8.1.2.1.6 Codec handling + +The MGW may include a speech transcoder based upon the speech coding information provided to each bearer termination. + +#### 8.1.2.1.7 Voice Processing function + +Voice processing function(s) provided by MGW-A before relocation, may be modified or disabled by MGW-A after relocation. + +#### 8.1.2.1.8 Handling of multiple bearers (multicall) + +If the UE is engaged with multiple bearers all procedures related to the handling of bearers and terminations described for the relocation of a single bearer shall be repeated for each bearer. + +#### 8.1.2.1.9 Failure Handling in MSC server + +When a procedure between the MSC-A server and MGW-A fails the MSC-A server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If call establishment towards MSC-B has already started then the call towards MSC-B server shall be cleared as described in clause 7.3. If the original call is to be cleared, then it shall be handled as described in clause 7.3. + +#### 8.1.2.2 MSC-B/MGW-B + +##### 8.1.2.2.1 MGW selection + +The MSC-B server selects an MGW when it receives Prepare Handover Request message (bullet 1 in figure 8.4/1). + +##### 8.1.2.2.2 Bearer establishment towards RNC-B + +When the MSC-B server has selected MGW-B it requests MGW-B to provide a binding reference and a bearer address, using the Prepare Bearer procedure. For speech calls, the MSC-B server shall provide the MGW-B with the speech coding information for the bearer. The MSC-B server sends the Relocation Request message to the RNC-B containing the bearer addresses and binding references (bullet 2 in figure 8.4/1). + +For Relocation towards GERAN Iu mode, if the selected service is speech and the MSC-B server cannot provide the codec requested by the MSC-A server, the MSC-B server shall select another codec according to the received GERAN capabilities of the target cell and the received list of supported codecs, and shall set the RAB parameters within the RANAP RELOCATION REQUEST message according to the new selected codec. Furthermore, the MSC-B server shall report the chosen codec and codec modes back to the MSC-A server with MAP Prepare Handover response. + +##### 8.1.2.2.3 Bearer establishment between MGW-A and MGW-B + +The handling of the bearer establishment is as described at Basic Mobile Terminating Call, using either forward or backward bearer establishment. + +##### 8.1.2.2.4 Codec handling + +The MGW may include a speech transcoder based upon the speech coding information provided to each bearer termination. + +##### 8.1.2.2.5 Voice Processing function + +Voice processing function(s) provided by MGW-A before relocation, may be continued or modified by MGW-B after relocation. + +##### 8.1.2.2.6 Handling of multiple bearers (multicall) + +If the UE is engaged with multiple bearers all procedures related to the handling of bearers and terminations described for the relocation of a single bearer shall be repeated for each bearer. + +##### 8.1.2.2.7 Failure Handling in MSC server + +When a procedure between the MSC-B server and MGW-B fails the MSC-B server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If MGW-B resources have been already seized at the target access side then the resources shall be released using the Release Termination procedure. The call from MSC-A server shall be released as described at clause 7.1. + +##### 8.1.2.2.8 Example + +Figure 8.3 shows the network model for the Basic Inter-MSC SRNS Relocation. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. In MGW-A the bearer termination T1 is used for the bearer towards RNC-A, bearer termination T3 is used for the bearer towards MGW-B, and the bearer termination T2 is used for the bearer towards the succeeding/preceding MGW. In MGW-B the bearer termination T4 is used for the bearer towards RNC-B, bearer termination T5 is used for the bearer towards MGW-A. + +![Diagram showing the network state before relocation. RNC A is connected to MGW A (containing CTX1) via a red dotted line. MSC-S A is connected to MGW A via a solid blue line. A green dashed line connects RNC A to MSC-S A.](5801c19431e76330430e92a598cc7a16_img.jpg) + +This diagram shows the initial network state. RNC A is connected to CTX1 in MGW A via a red dotted line. CTX1 in MGW A is connected to MSC-S A via a solid blue line. A green dashed line originates from RNC A and points towards MSC-S A. + +Diagram showing the network state before relocation. RNC A is connected to MGW A (containing CTX1) via a red dotted line. MSC-S A is connected to MGW A via a solid blue line. A green dashed line connects RNC A to MSC-S A. + +**Before Relocation:** + +![Diagram showing the network state during relocation. RNC A is connected to MSC-S A and MGW A. RNC B is connected to MGW B (CTX2) and MSC-S B. There are signaling and user plane connections between the old and new MSCs and MGWs.](a47713c2491e6ce619259ed2f196fd24_img.jpg) + +This diagram illustrates the network state during the relocation process. RNC A is shown with a green dashed line connecting it to MSC-S A. RNC B is connected to MSC-S B via a green dashed line. MSC-S B is connected to CTX2 in MGW B via a solid blue line. CTX2 in MGW B is connected to CTX1 in MGW A via a red dotted line. A green dashed line also connects MSC-S B to MSC-S A. A red dotted line connects RNC A to CTX1 in MGW A. MSC-S A remains connected to CTX1 in MGW A via a solid blue line. + +Diagram showing the network state during relocation. RNC A is connected to MSC-S A and MGW A. RNC B is connected to MGW B (CTX2) and MSC-S B. There are signaling and user plane connections between the old and new MSCs and MGWs. + +**During Relocation:** + +![Diagram showing the network state after relocation. RNC B is connected to MGW B (CTX2) and MSC-S B. MSC-S B is connected to MSC-S A, and MGW B is connected to MGW A (CTX1).](3e20f0289a1945c7c3894f51383d8e37_img.jpg) + +This diagram shows the network state after the relocation process. RNC B is connected to CTX2 in MGW B via a red dotted line. CTX2 in MGW B is connected to MSC-S B via a solid blue line. MSC-S B is connected to MSC-S A via a green dashed line. MSC-S A is connected to CTX1 in MGW A via a solid blue line. CTX1 in MGW A is connected to CTX2 in MGW B via a red dotted line. + +Diagram showing the network state after relocation. RNC B is connected to MGW B (CTX2) and MSC-S B. MSC-S B is connected to MSC-S A, and MGW B is connected to MGW A (CTX1). + +**After Relocation:** + +**Figure 8.3: Basic Inter-MSC SRNS Relocation (network model)** + +Figure 8.4 shows the message sequence example for the Basic Inter-MSC SRNS Relocation. It is assumed that the Handover Device is located in the MGW (MGW-A) selected for the call establishment by the MSC server (MSC-A server) which controls the call and the mobility management. It is also assumed that only one bearer has been established towards RNC-A. In the example the MSC-B server requests MGW-B to seize an RNC-B side bearer. The MSC-B server orders the establishment of the bearer towards RNC-B by sending Relocation Request. The call is established between MSC-A and MSC-B servers, and the bearer is established between MGW-A and MGW-B. When the relocation is detected in RNC-B the MSC-A server requests to change the flow directions between the terminations within the context in MGW-A. When MSC-A server receives Relocation Complete indication from MSC-B server it orders RNC-A to release the IU. This action causes release of the bearer between RNC-A and MGW-A. Finally MSC-A server requests MGW-A to remove RNC-A side bearer termination. + +![Sequence diagram for Basic Inter-MSC SRNS Relocation showing interactions between RNC A, MSC-S A, MGW A, MSC-S B, MGW B, and RNC B.](343e05a9fd8a8c8743428fa4ae6e2736_img.jpg) + +``` + +sequenceDiagram + participant RNC A + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant RNC B + + Note right of RNC B: Bearer Establishment + Note right of RNC B: Call and Bearer Establishment + Note right of RNC B: Relocation execution triggered in target RNC + + RNC A->>MSC-S A: Iu Relocation Required + MSC-S A->>MSC-S B: MAP Prepare Handover Req. + Note right of MSC-S B: 1 + MSC-S B->>MGW B: Context($), ADD.request ($), Context(C2) + Note right of MSC-S B: 2 + MGW B->>RNC B: Prepare Bearer + RNC B->>MSC-S B: Iu Relocation Request + MSC-S B->>RNC B: Iu Relocation Request-Ack + MSC-S B->>MGW B: ADD.request ($), Context(C2), Context(C2) + Note right of MSC-S B: 3 + MGW B->>RNC B: ADD.reply (T5) + MSC-S B->>MSC-S A: MAP Prepare Handover Resp. + Note right of MSC-S A: 4 + MSC-S A->>MGW A: Context(C1), TopDescr(({*, $, isolate}, {T2, $, oneway}))+ADD.request($), Context(C1) + MGW A->>MSC-S A: TopDescr()+ADD.reply (T3) + Note right of MGW A: Prepare Bearer, Change Flow Direction + Note right of MGW A: Call and Bearer Establishment + MSC-S A->>RNC A: Iu Relocation Command + Note right of RNC B: Relocation execution triggered in target RNC + RNC B->>MSC-S B: Iu Relocation Detect + MSC-S B->>MSC-S A: MAP Process Access Signalling Req. + +``` + +Sequence diagram for Basic Inter-MSC SRNS Relocation showing interactions between RNC A, MSC-S A, MGW A, MSC-S B, MGW B, and RNC B. + +Figure 8.4/1: Basic Inter-MSC SRNS Relocation (message sequence chart) + +![Figure 8.4/2: Basic Inter-MSC SRNS Relocation (message sequence chart). The diagram shows the interaction between RNC A, MSC-S A, MGW A, MSC-S B, MGW B, and RNC B. The sequence starts with Context(C1) from RNC A to MSC-S A. MSC-S A sends TopDescr to MGW A (step 5). MGW A responds with TopDescr(). MSC-S A then sends Context(C1) to MGW A. MGW A sends Change Flow Direction to MSC-S B. MSC-S B sends Iu Relocation Complete to MGW B. MGW B sends MAP Send End Signal Req. to MSC-S B. MSC-S B sends Iu Release Command to RNC A (step 6). RNC A sends Answer to MSC-S A. A green box labeled 'Release of bearer' is shown between MGW A and MGW B. MGW A sends Iu Release Complete to RNC A. RNC A sends Context(C1) to MSC-S A. MSC-S A sends SUB.request (T1) to MGW A. MGW A sends Context(C1) to MSC-S A. MSC-S A sends SUB.reply (T1) to MGW A. MGW A sends Release Bearer Termination to MSC-S B.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` + +sequenceDiagram + participant RNC A + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant RNC B + + Note right of RNC A: Context(C1) + RNC A->>MSC-S A: Context(C1) + Note right of MSC-S A: 5 + MSC-S A->>MGW A: TopDescr ({T2,T1, Oneway}, {T2, T3, bothway}) + MGW A-->>MSC-S A: TopDescr() + Note right of MSC-S A: Context(C1) + MSC-S A->>MGW A: Context(C1) + Note right of MGW A: Change Flow Direction + MGW A->>MSC-S B: Change Flow Direction + Note right of MSC-S B: Iu Relocation Complete + MSC-S B->>MGW B: Iu Relocation Complete + Note right of MGW B: MAP Send End Signal Req. + MGW B->>MSC-S B: MAP Send End Signal Req. + Note right of MSC-S B: Iu Release Command + MSC-S B->>RNC A: Iu Release Command + Note right of RNC A: 6 + RNC A-->>MSC-S A: Answer + Note right of MGW A: Release of bearer + MGW A->>MGW B: Release of bearer + Note right of MGW A: Iu Release Complete + MGW A->>RNC A: Iu Release Complete + Note right of RNC A: Context(C1) + RNC A->>MSC-S A: Context(C1) + Note right of MSC-S A: SUB.request (T1) + MSC-S A->>MGW A: SUB.request (T1) + Note right of MGW A: Context(C1) + MGW A->>MSC-S A: Context(C1) + Note right of MSC-S A: SUB.reply (T1) + MSC-S A->>MGW A: SUB.reply (T1) + Note right of MGW A: Release Bearer Termination + MGW A->>MSC-S B: Release Bearer Termination + +``` + +Figure 8.4/2: Basic Inter-MSC SRNS Relocation (message sequence chart). The diagram shows the interaction between RNC A, MSC-S A, MGW A, MSC-S B, MGW B, and RNC B. The sequence starts with Context(C1) from RNC A to MSC-S A. MSC-S A sends TopDescr to MGW A (step 5). MGW A responds with TopDescr(). MSC-S A then sends Context(C1) to MGW A. MGW A sends Change Flow Direction to MSC-S B. MSC-S B sends Iu Relocation Complete to MGW B. MGW B sends MAP Send End Signal Req. to MSC-S B. MSC-S B sends Iu Release Command to RNC A (step 6). RNC A sends Answer to MSC-S A. A green box labeled 'Release of bearer' is shown between MGW A and MGW B. MGW A sends Iu Release Complete to RNC A. RNC A sends Context(C1) to MSC-S A. MSC-S A sends SUB.request (T1) to MGW A. MGW A sends Context(C1) to MSC-S A. MSC-S A sends SUB.reply (T1) to MGW A. MGW A sends Release Bearer Termination to MSC-S B. + +Figure 8.4/2: Basic Inter-MSC SRNS Relocation (message sequence chart) + +### 8.1.3 Subsequent Inter-MSC SRNS/SBSS Relocation back to the Anchor MSC + +The procedures specified in 3GPP TS 23.009 [8] for "Subsequent Relocation from 3G\_MSC-B to 3G\_MSC-A requiring a Circuit Connection between 3G\_MSC-A and 3G\_MSC-B" shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +#### 8.1.3.1 MSC-A/MGW-A + +##### 8.1.3.1.1 Relocation Request + +When the MSC-A server receives the MAP Prepare Subsequent Handover request containing a Relocation Request message, it requests MGW-A to provide a binding reference and a bearer address using the Prepare Bearer procedure. For speech calls, the MSC-A server shall provide the MGW-A with the speech coding information for the bearer. For non-speech calls the MSC-A server shall provide MGW-A with the same PLMN Bearer Capability [4] as was provided at the last access bearer assignment. The MSC-A server uses the Change Flow Direction procedure to request the MGW-A to set the Handover Device to initial state. The MSC-A server sends the Relocation Request message, containing the bearer address and the binding reference, to RNC-B (bullet 1 in figure 8.6/1). + +For Relocation towards GERAN Iu mode, if the selected service is speech and the MSC-A server cannot provide the codec requested by the MSC-B server, the MSC-A server shall select another codec according to the received GERAN capabilities of the target cell and the list of supported codecs. + +##### 8.1.3.1.2 Relocation Command/Relocation Detect + +When the MSC-A server sends the MAP Prepare Subsequent Handover response message or alternatively if it receives the Relocation Detect message, the MSC-A server uses the Change Flow Direction procedure to requests MGW-A to set the Handover Device to intermediate state (bullet 2 in figure 8.6/1). + +##### 8.1.3.1.3 Relocation Complete + +When the MSC-A server receives the Relocation Complete message, it informs the MSC-B server about reception of this message. The MSC-A server then initiates call clearing towards the MSC-B server as described in clause 7.3. + +#### 8.1.3.1.4 Interworking function + +The interworking function used by MGW-A before relocation will also be used after relocation. + +#### 8.1.3.1.5 Codec handling + +The MGW may include a speech transcoder based upon the speech coding information provided to each bearer termination. + +#### 8.1.3.1.6 Voice Processing function + +Voice processing function(s) provided by MGW-A and MGW-B before relocation, may be continued or modified by MGW-A after relocation. + +#### 8.1.3.1.7 Handling of multiple bearers (multicall) + +If the UE is engaged with multiple bearers all procedures related to the handling of bearers and terminations described for the relocation of a single bearer shall be repeated for each bearer. + +#### 8.1.3.1.8 Failure Handling in MSC server + +When a procedure between the MSC-A server and the MGW fails the MSC-A server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If MGW resources have already been seized at the target access side then the resources shall be released using the Release Termination procedure. If the call is to be cleared, then it shall be handled as described in clause 7.3. + +### 8.1.3.2 MSC-B/MGW-B + +#### 8.1.3.2.1 Relocation Required + +For Relocation towards GERAN Iu mode the GERAN capabilities of the target cell will be indicated to the MSC-B server within the RANAP RELOCATION REQUIRED message if the target cell provides different capabilities than the current cell. If no information about the GERAN capabilities of the target cell are received within this message, the MSC-B server shall assume that the GERAN target cell will provide the same capabilities as the current cell (for details see [29]). The different interworking scenarios (e.g. interworking to pre-Rel5 UTRAN) are described in [29]. + +The MSC-B server shall indicate to the MSC-A server the GERAN capabilities of the target cell, if available, with the MAP Prepare Subsequent Handover request. For speech calls, the MSC-B server shall additionally indicate to the MSC-A server the selected codec and the currently used codec. + +Furthermore, the MSC-B server shall indicate to the GERAN the selected service within the RANAP RELOCATION REQUEST message and shall set the RAB parameters within the RANAP RELOCATION REQUEST message according to the selected service. The MSC server shall not set codec information in the NAS Synchronisation Indicator (see [4]). Instead it shall set codec information in the GERAN BSC container... + +#### 8.1.3.2.2 Relocation Complete + +When the MSC-B server receives the Relocation Complete message, it requests RNC-A to release the IU. The MSC-B server requests MGW-B to remove the bearer termination towards RNC-A using the Release Termination procedure (bullet 3 in figure 8.6/2). + +#### 8.1.3.2.3 Release of bearer towards MGW-A + +When the MSC-B server receives a call clearing indication from the MSC-A server, the MSC-B server handles it as described in clause 7.2. + +#### 8.1.3.2.4 Handling of multiple bearers (multicall) + +If the UE is engaged with multiple bearers all procedures related to the handling of bearers and terminations described for the relocation of a single bearer shall be repeated for each bearer. + +#### 8.1.3.2.5 Example + +Figure 8.5 shows the network model for the Subsequent Inter- MSC SRNS Relocation back to the Anchor MSC. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the + +bearer. In MGW-A the bearer termination T6 is used for the bearer towards RNC-B, bearer termination T3 is used for the bearer towards MGW-B, and the bearer termination T2 is used for the bearer towards the succeeding/preceding MGW. In MGW-B the bearer termination T4 is used for the bearer towards RNC-A, bearer termination T5 is used for the bearer towards MGW-A. + +![Diagram illustrating Subsequent Inter-MSC SRNS Relocation back to the Anchor MSC (network model) in three stages: Before Relocation, During Relocation, and After Relocation.](9cb54072e43a6b6717eb16036a7640a2_img.jpg) + +The diagram illustrates the network model for Subsequent Inter-MSC SRNS Relocation back to the Anchor MSC. It shows the flow of data bearers (dashed green lines) and signaling paths (solid blue lines) between various network elements: RNC A, RNC B, MSC-S B, MSC-S A, MGW B, and MGW A. + +**Before Relocation:** The network consists of RNC A connected to MGW B, which is connected to MSC-S B. MSC-S B is connected to MSC-S A, which is connected to MGW A. MGW A is connected to RNC B. The bearer path (dashed green line) starts at RNC A, goes through MGW B, MSC-S B, MSC-S A, and MGW A to RNC B. The signaling path (solid blue line) starts at RNC A, goes through MGW B, MSC-S B, MSC-S A, and MGW A to RNC B. + +**During Relocation:** The network elements are the same as in the 'Before Relocation' state, but the bearer path (dashed green line) is shown being rerouted. It now starts at RNC B, goes through MGW A, MSC-S A, MSC-S B, MGW B, and RNC A. The signaling path (solid blue line) remains the same as in the 'Before Relocation' state. + +**After Relocation:** The network has been reconfigured. RNC B is now directly connected to MGW A. The bearer path (dashed green line) starts at RNC B, goes through MGW A, MSC-S A, and then continues. The signaling path (solid blue line) starts at RNC B, goes through MGW A, MSC-S A, and then continues. + +Diagram illustrating Subsequent Inter-MSC SRNS Relocation back to the Anchor MSC (network model) in three stages: Before Relocation, During Relocation, and After Relocation. + +Figure 8.5: Subsequent Inter-MSC SRNS Relocation back to the Anchor MSC (network model) + +Figure 8.6 shows the message sequence example for the Subsequent Inter-MSC SRNS Relocation back to the Anchor MSC. It is assumed that the Handover Device is located in the MGW (MGW-A) selected for the call establishment by the MSC server (MSC-A server) which controls the call and the mobility management. Also assumed that only one bearer has been established towards RNC-A. In the example the MSC-A server requests MGW-A to seize RNC-B side bearer termination with specific flow directions. The MSC server orders the establishment of the bearer towards RNC-B by sending Relocation Request. When the relocation is detected in RNC-B the MSC-A server requests to change the flow directions between the terminations within the context in MGW-A. When the MSC-A server receives a Relocation Complete indication from RNC-B it transfers this indication to MSC-B server. MSC-B server orders RNC-A to release the IU. This action causes release of the bearer between RNC-A and the MGW-B. MSC-A server initiates call clearing towards MSC-B server. + +![Sequence diagram for Subsequent Inter-MSC SRNS Relocation back to the Anchor MSC. Lifelines: RNC B, MSC-S A, MGW A, MSC-S B, MGW B, RNC A. The process involves preparation, execution, and completion phases with various signaling messages like Context, TopDescr, MAP Prepare, and Iu Relocation.](c649cad02e45d7d9a16f3f5bdb332219_img.jpg) + +``` + +sequenceDiagram + participant RNC B + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant RNC A + + Note right of RNC B: Bearer Establishment + Note left of RNC A: Relocation execution triggered in target RNC + + RNC B->>MSC-S A: Context(C1) + MSC-S A->>MGW A: TopDescr(*, $, isolate), {T2, $, oneway}+Add.request($) + Note right of MGW A: Prepare bearer, Change Flow Direction + MGW A->>MSC-S A: TopDescr()+Add.reply (T6) + MSC-S A->>RNC B: Iu Relocation Request + Note right of RNC B: Bearer Establishment + RNC B->>MSC-S A: Iu Relocation Request-Ack + MSC-S A->>MSC-S B: MAP Prepare Subsequent HandoverReq. + MSC-S B->>RNC A: Iu Relocation Command + Note left of RNC A: Relocation execution triggered in target RNC + RNC B->>MSC-S A: Iu Relocation Detect + MSC-S A->>MGW A: TopDescr({T2, T3, oneway}, {T2,T6,bothway}) + Note right of MGW A: Change Flow Direction + MGW A->>MSC-S A: TopDescr() + +``` + +Sequence diagram for Subsequent Inter-MSC SRNS Relocation back to the Anchor MSC. Lifelines: RNC B, MSC-S A, MGW A, MSC-S B, MGW B, RNC A. The process involves preparation, execution, and completion phases with various signaling messages like Context, TopDescr, MAP Prepare, and Iu Relocation. + +**Figure 8.6/1: Subsequent Inter-MSC SRNS Relocation back to the Anchor MSC (message sequence chart)** + +![Figure 8.6/2: Subsequent Inter-MSC SRNS Relocation back to the Anchor MSC (message sequence chart). The diagram shows a sequence of messages between RNC B, MSC-S A, MGW A, MSC-S B, MGW B, and RNC A. The sequence starts with RNC B sending an 'Iu Relocation Complete' message to MSC-S A. MSC-S A then sends a 'MAP Send End Signal Resp.' to MSC-S B. MSC-S B sends an 'Iu Release Command' to MGW B, which triggers a 'Release of bearer' (highlighted in a green box). MGW B then sends an 'Iu Release Complete' message to MSC-S B. MSC-S B sends a 'Context(C2) SUB.request (T4)' to MGW A, which responds with 'Context(C2) SUB.reply (T4)'. Finally, a 'Call Clearing and Bearer Release' (highlighted in a green box) occurs between MSC-S A and MGW A.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +``` + +sequenceDiagram + participant RNC B + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant RNC A + + Note right of MSC-S A: 3 + RNC B->>MSC-S A: Iu Relocation Complete + MSC-S A->>MSC-S B: MAP Send End Signal Resp. + MSC-S B->>MGW B: Iu Release Command + Note right of MGW B: Release of bearer + MGW B->>MSC-S B: Iu Release Complete + MSC-S B->>MGW A: Context(C2) SUB.request (T4) + MGW A->>MSC-S B: Context(C2) SUB.reply (T4) + Note right of MSC-S A: Call Clearing and Bearer Release + +``` + +Figure 8.6/2: Subsequent Inter-MSC SRNS Relocation back to the Anchor MSC (message sequence chart). The diagram shows a sequence of messages between RNC B, MSC-S A, MGW A, MSC-S B, MGW B, and RNC A. The sequence starts with RNC B sending an 'Iu Relocation Complete' message to MSC-S A. MSC-S A then sends a 'MAP Send End Signal Resp.' to MSC-S B. MSC-S B sends an 'Iu Release Command' to MGW B, which triggers a 'Release of bearer' (highlighted in a green box). MGW B then sends an 'Iu Release Complete' message to MSC-S B. MSC-S B sends a 'Context(C2) SUB.request (T4)' to MGW A, which responds with 'Context(C2) SUB.reply (T4)'. Finally, a 'Call Clearing and Bearer Release' (highlighted in a green box) occurs between MSC-S A and MGW A. + +**Figure 8.6/2: Subsequent Inter-MSC SRNS Relocation back to the Anchor MSC +(message sequence chart)** + +## 8.1.4 Subsequent Inter-MSC SRNS/SBSS Relocation to a third MSC + +The relocation to a third MSC server (from MSC-B server to MSC-B server) is the combination of the two previous inter-MSC handover cases: + +- for MSC-B server a subsequent relocation from MSC-B server back to MSC-A server as described in clause 8.1.3; and +- for MSC-B server a basic relocation from MSC-A server to MSC-B server as described in clause 8.1.2. + +MSC-A server implements the corresponding parts of each handover case; i.e. access handling in MSC-A server is not included. + +## 8.1.5 SRNS/SBSS Relocation with Iu on IP + +If IuCS on IP is supported by the MSC server, the Core Network side procedures described in 8.1.1, 8.1.2, 8.1.3 and 8.1.4 shall apply. For the access bearer termination, the exchange of IP addresses via call control procedures is described in this clause. + +Before the MSC server starts the access bearer assignment, the MSC server requests the MGW to prepare for the access bearer using the *Prepare\_IP\_Transport* procedure. The MSC server requests the MGW to provide an IP Transport address and UDP Port and provides the MGW with the bearer characteristics. For speech calls, the MSC server shall provide the MGW with the speech coding information and conditionally GTT related information in accordance with 3GPP TS 23.226 [28] for the bearer. For a non-speech call the MSC server also provides the MGW with a PLMN Bearer Capability [4]. After the MGW has replied with the IP address and UDP Port the MSC server requests access bearer assignment using the provided IP address and UDP Port in accordance with 3GPP TS 25.413 [26]. The IP addresses and UDP Ports of the MGW and the RNC are exchanged via the RANAP procedures. If the bearer transport is IP and IuUP mode is Transparent, when the MSC receives the RANAP Iu Relocation Request response, it shall send the RNC IP address and UDP Port to the MGW Access bearer termination using the *Modify\_IP\_Transport\_Address* procedure. + +If the bearer transport is IP and IuUP mode is Support, the MGW shall use the source IP address and UDP Port of the IuUP Init packet received from the radio access network as the destination address for subsequent downlink packets. + +The sequence is shown in figure 8.1.5/1. + +![Sequence diagram for SRNS Relocation with Iu on IP. Lifelines: RNC A, MSC-S, MGW, RNC B. The diagram shows the interaction between these entities for context transfer and IP bearer preparation. A note at the top refers to preceding signalling sequences. The process involves ADD.request, ADD.reply, Iu Relocation Request, IuUP Init/Ack (if supported), Iu Relocation Request-Ack, MODIFY.request, Mod.reply, and finally Iu Relocation Command.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +For preceding signalling sequences for establishing core network bearer see Figures 8.2, 8.4 or 8.6 + +Sequence of messages: + +- Context(C1) from RNC A to MSC-S (bullet 1). +- ADD.request (S) from MSC-S to MGW. (Note: **Prepare IP bearer**) +- ADD.reply(T3) from MGW to MSC-S. +- Iu Relocation Request from MSC-S to RNC B. +- IuUP Init from RNC B to MGW (If IuUP in support mode). +- IuUP Init Ack from MGW to RNC B (If IuUP in support mode). +- Iu Relocation Request-Ack from RNC B to MSC-S. +- Context(C1) from RNC A to MSC-S. +- MODIFY.request (T3) from MSC-S to MGW. (Note: **Modify IP address**) +- Context(C1) from MSC-S to RNC A. +- Mod.reply (T3) from RNC A to MSC-S. +- Iu Relocation Command from MSC-S to RNC A. + +Sequence diagram for SRNS Relocation with Iu on IP. Lifelines: RNC A, MSC-S, MGW, RNC B. The diagram shows the interaction between these entities for context transfer and IP bearer preparation. A note at the top refers to preceding signalling sequences. The process involves ADD.request, ADD.reply, Iu Relocation Request, IuUP Init/Ack (if supported), Iu Relocation Request-Ack, MODIFY.request, Mod.reply, and finally Iu Relocation Command. + +Figure 8.1.5/1 SRNS Relocation with Iu on IP + +## 8.1.6 Intra-MSC enhanced SRNS Relocation + +### 8.1.6.1 Introduction + +The procedures specified in 3GPP TS 23.009 [8] for "Intra-3G\_MSC SRNS Relocation" shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. The support of the enhanced SRNS Relocation is optional. + +### 8.1.6.2 Enhanced Relocation Complete Request + +When the Enhanced Relocation Complete Request message is received, the MSC server requests the MGW to provide a binding reference and a bearer address, using the Prepare Bearer procedure. For speech calls, the MSC server shall provide the MGW with the speech coding information for the bearer. For non-speech calls the MSC server also provides the MGW with the same PLMN Bearer Capability [4] as was provided at the last access bearer assignment. The MSC server uses the Change Flow Direction Procedure to request the MGW to set the Handover Device to initial state. If required the MSC Server shall set-up an interconnection between the "anchor" and the "target" MGW. The MSC server then sends the Enhanced Relocation Complete Response message, containing the bearer address and the binding reference, to RNC-B (bullet 1 in figure 8.1.6/2). + +### 8.1.6.3 Enhanced Relocation Complete Confirm + +When the MSC server receives the Enhanced Relocation Complete Confirm message, the MSC server uses the Change Flow Direction procedure to request the MGW to set the Handover Device to intermediate state (bullet 2 in figure 8.1.6/1). + +After that the MSC Server requests RNC-A to release the IU. The MSC server also requests the MGW to set the Handover Device to its final state by removing the bearer termination towards RNC-A, using the Release Termination procedure (bullet 3 in figure 8.1.6/2). + +#### 8.1.6.4 Interworking function + +The interworking function used by the MGW before relocation will also be used after relocation. + +#### 8.1.6.5 Codec handling + +The MGW may include a speech transcoder based upon the speech coding information provided to each bearer termination. + +#### 8.1.6.6 Voice Processing function + +After relocation, the MGW may continue or modify voice-processing function(s) provided to each bearer termination. + +#### 8.1.6.7 Handling of multiple bearers (multicall) + +If the UE is engaged with multiple bearers all procedures related to the handling of bearers and terminations described for the relocation of a single bearer shall be repeated for each bearer. + +#### 8.1.6.8 Failure Handling in MSC server + +When a procedure between the MSC server and the MGW fails the MSC server shall send an IU-ENHANCED-RELOCATION-COMPLETE-FAILURE message to RNS-B in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If MGW resources have been already seized at the target access side then the resources shall be released using the Release Termination procedure. If the call is to be cleared, then it shall be handled as described in clause 7.3. + +#### 8.1.6.9 Example + +Figure 8.1.6/1 shows the network model for the Intra-MSC enhanced SRNS Relocation. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. The bearer termination T1 is used for the bearer towards RNC-A, bearer termination T3 is used for the bearer towards RNC-B and the bearer termination T2 is used for the bearer towards the succeeding/preceding MGW. + +![Figure 8.1.6/1: Intra-MSC Enhanced SRNS Relocation (network model). The diagram shows three stages of network configuration: 'Before Relocation', 'After Relocation', and 'After release of Source side resources'. Each stage shows the MSC-S, RNC-A, RNC-B, and CTXI MGW components and their connections.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +The diagram illustrates the network model for Intra-MSC Enhanced SRNS Relocation in three stages: + +- Before Relocation:** The MSC-S is connected to RNC-A and the CTXI MGW. RNC-A is connected to the CTXI MGW. The CTXI MGW has three interfaces: T1 (connected to RNC-A), T2 (connected to an external network), and T3 (unconnected). A green dashed line represents the user plane path from the external network through the MSC-S to RNC-A. +- After Relocation:** The MSC-S is now connected to RNC-B. RNC-B is connected to the CTXI MGW via interface T3. The CTXI MGW still has interface T2 connected to the external network. The green dashed line now represents the user plane path from the external network through the MSC-S to RNC-B. +- After release of Source side resources:** RNC-A has been removed from the network. The MSC-S remains connected to RNC-B and the CTXI MGW. RNC-B is connected to the CTXI MGW via interface T3. The CTXI MGW still has interface T2 connected to the external network. The green dashed line represents the user plane path from the external network through the MSC-S to RNC-B. + +Figure 8.1.6/1: Intra-MSC Enhanced SRNS Relocation (network model). The diagram shows three stages of network configuration: 'Before Relocation', 'After Relocation', and 'After release of Source side resources'. Each stage shows the MSC-S, RNC-A, RNC-B, and CTXI MGW components and their connections. + +**Figure 8.1.6/1: Intra-MSC Enhanced SRNS Relocation (network model)** + +Figure 8.1.6/2 shows the message sequence example for the Intra-MSC enhanced SRNS Relocation. + +It is assumed that the Handover Device is located in the MGW, which has been selected for the call establishment by the MSC server. The MSC server controls the call and the mobility management. It is also assumed that only one bearer has been established towards RNC-A. + +In the example the MSC server requests seizure of RNC-B side bearer termination with specific flow directions. The MSC server orders the establishment of the bearer by sending Enhanced Relocation Complete Response towards RNC-B. When the MSC server receives an Enhanced Relocation Complete Confirm indication from RNC-B the MSC server requests to change the flow directions between the terminations within the context. MSC Server also orders RNC-A to release the IU. This action causes release of the bearer between the RNC-A and the MGW. Finally the MSC server requests the MGW to release RNC-A side bearer termination. + +![Sequence diagram for Intra-MSC Enhanced SRNS Relocation. Lifelines: RNC A, MSC-S, MGW, RNC B. The sequence involves three numbered phases. Phase 1: MSC-S sends 'Enhanced Relocation Complete Request' to MGW. MGW responds with 'TopDescr({*,$,isolate},{T2,$,oneway})+ADD.Request($)'. MSC-S sends 'Prepare bearer, Change Flow Direction' and 'TopDescr()+ADD.reply(T3)' to MGW. MGW responds with 'Enhanced Relocation Complete Response'. MGW then performs 'Bearer Establishment'. MSC-S sends 'Enhanced Relocation Complete Confirm' to MGW. Phase 2: MSC-S and RNC A exchange 'Context(C1)'. MSC-S sends 'TopDescr({T2,T1,oneway}, {T2,T3,bothway})' to MGW. MGW responds with 'TopDescr()'. MSC-S sends 'Change Flow Direction' to MGW and 'Iu Release Command' to RNC A. RNC A performs 'Release of bearer'. Phase 3: RNC A sends 'Iu Release Complete' to MSC-S. MSC-S sends 'Context(C1)' and 'SUB request (T1)' to MGW. MGW responds with 'Context(C1)', 'SUB reply (T1)', and 'Release Termination'.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +``` + +sequenceDiagram + participant RNC A + participant MSC-S + participant MGW + participant RNC B + + Note left of MSC-S: 1 + MSC-S->>MGW: Enhanced Relocation Complete Request + MGW-->>MSC-S: TopDescr({*, $, isolate}, {T2, $, oneway}) + ADD.Request($) + MSC-S->>MGW: Prepare bearer, Change Flow Direction + MSC-S->>MGW: TopDescr() + ADD.reply(T3) + MGW-->>MSC-S: Enhanced Relocation Complete Response + Note over MGW: Bearer Establishment + MSC-S->>MGW: Enhanced Relocation Complete Confirm + + Note left of MSC-S: 2 + MSC-S->>RNC A: Context(C1) + RNC A-->>MSC-S: Context(C1) + MSC-S->>MGW: TopDescr({T2, T1, oneway}, {T2, T3, bothway}) + MGW-->>MSC-S: TopDescr() + MSC-S->>MGW: Change Flow Direction + MSC-S->>RNC A: Iu Release Command + Note over RNC A: Release of bearer + RNC A-->>MSC-S: Iu Release Complete + + Note left of MSC-S: 3 + MSC-S->>MGW: Context(C1) + MSC-S->>MGW: SUB request (T1) + MGW-->>MSC-S: Context(C1) + MGW-->>MSC-S: SUB reply (T1) + MGW-->>MGW: Release Termination + +``` + +Sequence diagram for Intra-MSC Enhanced SRNS Relocation. Lifelines: RNC A, MSC-S, MGW, RNC B. The sequence involves three numbered phases. Phase 1: MSC-S sends 'Enhanced Relocation Complete Request' to MGW. MGW responds with 'TopDescr({\*,\$,isolate},{T2,\$,oneway})+ADD.Request(\$)'. MSC-S sends 'Prepare bearer, Change Flow Direction' and 'TopDescr()+ADD.reply(T3)' to MGW. MGW responds with 'Enhanced Relocation Complete Response'. MGW then performs 'Bearer Establishment'. MSC-S sends 'Enhanced Relocation Complete Confirm' to MGW. Phase 2: MSC-S and RNC A exchange 'Context(C1)'. MSC-S sends 'TopDescr({T2,T1,oneway}, {T2,T3,bothway})' to MGW. MGW responds with 'TopDescr()'. MSC-S sends 'Change Flow Direction' to MGW and 'Iu Release Command' to RNC A. RNC A performs 'Release of bearer'. Phase 3: RNC A sends 'Iu Release Complete' to MSC-S. MSC-S sends 'Context(C1)' and 'SUB request (T1)' to MGW. MGW responds with 'Context(C1)', 'SUB reply (T1)', and 'Release Termination'. + +**Figure 8.1.6/2: Intra-MSC Enhanced SRNS Relocation (message sequence chart)** + +### 8.1.7 Intra-MSC enhanced SRNS Relocation with Iu on IP + +If IuCS on IP is supported by the MSC server, the Core Network side procedures described in 8.1.x shall apply. For the access bearer termination, the exchange of IP addresses via call control procedures as described in 8.1.5 applies with the following exception. The Prepare\_IP\_Transport procedure is used after the MSC Server receives the RANAP Enhanced Relocation Complete Request. If the bearer transport is IP and IuUP mode is Transparent, when the MSC Server receives the RANAP Enhanced Relocation Complete Response, it shall send the RNC IP address and UDP Port to the MGW Access bearer termination using the Modify\_IP\_Transport\_Address procedure. + +The sequence is shown in figure 8.7/1. + +![Sequence diagram for Enhanced SRNS Relocation with Iu on IP. It shows interactions between RNC A, MSC-S, MGW, and RNC B. Key steps include Enhanced Relocation Complete Request, IP transport preparation, IuUP initialization, bearer modification, and release of bearer (highlighted in green).](719ef0f734259484038b2434e5dc3f24_img.jpg) + +``` + +sequenceDiagram + participant RNC_A as RNC A + participant MSC_S as MSC-S + participant MGW as MGW + participant RNC_B as RNC B + + Note over MSC_S, RNC_B: Enhanced Relocation Complete Request + MSC_S->>MGW: TopDescr({*,$,isolate}, {T2,$,oneway})+ADD.Request($ + Note right of MSC_S: 1 + Note over MGW: Prepare IP Transport, +Change Flow Direction + MGW-->>MSC_S: TopDescr()+ADD.reply(T3) + MSC_S->>RNC_B: Enhanced Relocation Complete Response + Note right of RNC_B: If IuUP in +support mode + RNC_B->>MGW: IuUP Init + MGW-->>RNC_B: IuUP Init Ack + MSC_S->>RNC_B: Enhanced Relocation Complete Confirm + Note right of RNC_B: If IuUP in +Transparent +mode + MSC_S->>MGW: MOD request (T3) + Note over MGW: Modify IP Transport +address + MGW-->>MSC_S: MOD reply (T3) + MSC_S->>MGW: TopDescr ({T2,T1,oneway}, {T2,T3,bothway}) + Note over MGW: Change Flow Direction + Note right of MSC_S: 2 + MSC_S->>RNC_A: TopDescr() + MSC_S->>RNC_A: Iu Release Command + Note over RNC_A: Release of bearer + RNC_A->>MSC_S: Iu Release Complete + MSC_S->>MGW: SUB request (T1) + Note right of MSC_S: 3 + Note over MGW: Release Termination + MGW-->>MSC_S: SUB reply (T1) + +``` + +Sequence diagram for Enhanced SRNS Relocation with Iu on IP. It shows interactions between RNC A, MSC-S, MGW, and RNC B. Key steps include Enhanced Relocation Complete Request, IP transport preparation, IuUP initialization, bearer modification, and release of bearer (highlighted in green). + +**Figure 8.1.7/1 Enhanced SRNS Relocation with Iu on IP** + +## 8.2 UMTS to GSM + +In the context of the following clauses, the terms RNS or RNC refer also to a GERAN BSS or BSC (respectively) when serving an UE in Iu mode. + +### 8.2.1 Intra-MSC UMTS to GSM Handover + +The procedures specified in 3GPP TS 23.009 [8] for "Intra-3G\_MSC Handover from UMTS to GSM" shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +### 8.2.1.1 Relocation Required + +When the MSC server receives the Relocation Required message, it requests the MGW to seize a TDM circuit, using the Reserve Circuit procedure. For non-speech calls the MSC server shall provide the MGW with the GSM Channel coding properties and the same PLMN Bearer Capability [4] as was provided at the last access bearer assignment. The MSC server uses the Change Flow Direction procedure to request the MGW to set the Handover Device to initial state. The MSC server sends the Handover Request message, containing the CIC, to BSC-B (bullet 1 in figure 8.8/1). + +### 8.2.1.2 Handover Request Acknowledge + +For non-speech calls after receiving the Handover Request Acknowledge message if the assigned GSM Channel coding properties differ from the previously provided ones the MSC server provides the MGW with the assigned GSM Channel coding properties using the Modify Bearer Characteristics procedure (bullet 2 in figure 8.8/1). + +### 8.2.1.3 Relocation Command/Handover Detect + +When the MSC server sends the Relocation Command message or alternatively if it receives the Handover Detect message, the MSC server uses the Change Flow Direction procedure to requests the MGW to set the Handover Device to intermediate state (bullet 3 in figure 8.8/1). + +### 8.2.1.4 Handover Complete + +When the MSC server receives the Handover Complete message, it requests RNC-A to release the IU. The MSC server also requests the MGW to set the Handover Device to its final state by removing the bearer termination towards RNC-A, using the Release Termination procedure (bullet 4 in figure 8.8/2). + +### 8.2.1.5 Interworking function + +The interworking function used by the MGW before handover will also be used after handover. + +### 8.2.1.6 Voice Processing function + +After handover, the MGW may continue or modify voice processing function(s) provided to each bearer termination. + +### 8.2.1.7 Handling of multiple bearers (multicall) + +If the UE is engaged with multiple bearers then one bearer is selected to be handed over according to 3GPP TS 23.009 [8]. The calls carried by the bearers that have not been selected will be cleared after the reception of the Handover Complete message, as described in clause 7.3. + +### 8.2.1.8 Failure Handling in MSC server + +When a procedure between the MSC server and the MGW fails the MSC server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If MGW resources have been already seized at the target access side then the resources shall be released using the Release Termination procedure. If the call is to be cleared, then it shall be handled as described in clause 7.3. + +### 8.2.1.9 Example + +Figure 8.7 shows the network model for the Intra-MSC UMTS to GSM Handover. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in case of GSM access) and the bearer. The bearer termination T1 is used for the bearer towards RNC-A, bearer termination T3 is used for the bearer towards BSC-B and the bearer termination T2 is used for the bearer towards the succeeding/preceding MGW. + +![Figure 8.7: Intra- MSC UMTS to GSM Handover (network model). The diagram shows three stages: Before Handover, During Handover, and After Handover. In 'Before Handover', RNC A is connected to MSC-S via a dashed green line, and MSC-S is connected to CTXI MGW via a solid blue line. CTXI MGW has two red dotted lines labeled T1 and T2. In 'During Handover', RNC A and BSC B are both connected to MSC-S via dashed green lines. MSC-S is connected to CTXI MGW via a solid blue line. CTXI MGW has three red dotted lines labeled T1, T2, and T3. In 'After Handover', BSC B is connected to MSC-S via a dashed green line, and MSC-S is connected to CTXI MGW via a solid blue line. CTXI MGW has two red dotted lines labeled T3 and T2.](18bb06865e2dada3656ea3d57f290f7f_img.jpg) + +**Before Handover** + +**During Handover** + +**After Handover** + +Figure 8.7: Intra- MSC UMTS to GSM Handover (network model). The diagram shows three stages: Before Handover, During Handover, and After Handover. In 'Before Handover', RNC A is connected to MSC-S via a dashed green line, and MSC-S is connected to CTXI MGW via a solid blue line. CTXI MGW has two red dotted lines labeled T1 and T2. In 'During Handover', RNC A and BSC B are both connected to MSC-S via dashed green lines. MSC-S is connected to CTXI MGW via a solid blue line. CTXI MGW has three red dotted lines labeled T1, T2, and T3. In 'After Handover', BSC B is connected to MSC-S via a dashed green line, and MSC-S is connected to CTXI MGW via a solid blue line. CTXI MGW has two red dotted lines labeled T3 and T2. + +**Figure 8.7: Intra- MSC UMTS to GSM Handover (network model)** + +Figure 8.8 shows the message sequence example for the Intra- MSC UMTS to GSM Handover. + +It is assumed that the Handover Device is located in the MGW selected for the call establishment by the MSC server, which controls the call and the mobility management. It is also assumed that only one bearer has been established towards RNC-A and that MGW-A is capable of handling GSM access. + +In the example the MSC server requests seizure of BSC-B side bearer termination with specific flow directions. The MSC server starts handover execution by sending Handover Request towards BSC-B. When the handover is detected in BSC-B the MSC server requests to change the flow directions between the terminations within the context. When MSC server receives Handover Complete indication from BSC-B it orders RNC-A to release the IU. Finally the MSC server requests the MGW to release RNC-A side bearer termination. + +![Sequence diagram for Intra-MSC UMTS to GSM Handover involving RNC A, MSC-S, MGW, and BSC B.](2f587210e4f97c32758c5972e2e83d20_img.jpg) + +The sequence diagram illustrates the interaction between four network elements: RNC A, MSC-S, MGW, and BSC B. The process begins with RNC A sending an 'Iu Relocation Required' message to MSC-S. MSC-S then initiates step 1 by sending 'Context(C1)' and 'TopDescr({\*,T3,isolate},{T2,T3,oneway})+ADD.request (T3)' to MGW. MGW responds with 'Reserve Circuit Change Flow Direction' and 'TopDescr()+ADD.reply (T3)'. MSC-S then sends an 'A Handover Request' to BSC B, which responds with 'A Handover Request-Ack'. Step 2 involves 'Modify Bearer Characteristics (when applicable)', where MSC-S sends 'Context(C1)' and 'MOD.request (T3)' to MGW, and MGW replies with 'Context(C1)' and 'MOD.reply (T3)'. MSC-S then sends an 'Iu Relocation Command' to RNC A. A green box indicates 'Handover detected in target BSC'. BSC B sends an 'A Handover Detect' message to MSC-S. Finally, in step 3, MSC-S sends 'Context(C1)' and 'TopDescr({T2,T1,oneway},{T2,T3,bothway})' to MGW, which responds with 'Context(C1)', 'Change Flow Direction', and 'TopDescr()'. + +``` + +sequenceDiagram + participant RNC A + participant MSC-S + participant MGW + participant BSC B + + RNC A->>MSC-S: Iu Relocation Required + Note over MSC-S, MGW: 1 + MSC-S->>MGW: Context(C1) + MSC-S->>MGW: TopDescr({*,T3,isolate},{T2,T3,oneway})+ADD.request (T3) + MGW->>MSC-S: Reserve Circuit Change Flow Direction + MGW->>MSC-S: Context(C1) + MGW->>MSC-S: TopDescr()+ADD.reply (T3) + MSC-S->>BSC B: A Handover Request + BSC B->>MSC-S: A Handover Request-Ack + Note over MSC-S, MGW: 2 + Note right of MGW: Modify Bearer Characteristics (when applicable) + MSC-S->>MGW: Context(C1) + MSC-S->>MGW: MOD.request (T3) + MGW->>MSC-S: Context(C1) + MGW->>MSC-S: MOD.reply (T3) + MSC-S->>RNC A: Iu Relocation Command + Note over BSC B: Handover detected in target BSC + BSC B->>MSC-S: A Handover Detect + Note over MSC-S, MGW: 3 + MSC-S->>MGW: Context(C1) + MSC-S->>MGW: TopDescr({T2,T1,oneway},{T2,T3,bothway}) + MGW->>MSC-S: Change Flow Direction + MGW->>MSC-S: Context(C1) + MGW->>MSC-S: TopDescr() + +``` + +Sequence diagram for Intra-MSC UMTS to GSM Handover involving RNC A, MSC-S, MGW, and BSC B. + +**Figure 8.8/1: Intra-MSC UMTS to GSM Handover (message sequence chart)** + +![Figure 8.8/2: Intra-MSC UMTS to GSM Handover (message sequence chart). The diagram shows the interaction between RNC A, MSC-S, MGW, and BSC B. The sequence starts with 'A Handover Complete' from BSC B to MSC-S. MSC-S sends 'Iu Release Command' to RNC A. A green box labeled 'Release of bearer' spans the MGW lifeline. RNC A sends 'Iu Release Complete' to MSC-S. MSC-S sends 'Context(C1)' and 'SUB.request (T1)' to MGW. MGW sends 'Context(C1)' and 'SUB.reply (T1)' back to MSC-S. Finally, MGW sends 'Release Termination' to BSC B. A circled number 4 is on the MSC-S lifeline between 'Iu Release Complete' and 'Context(C1)'.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +``` + +sequenceDiagram + participant RNC A + participant MSC-S + participant MGW + participant BSC B + Note right of MGW: Release of bearer + BSC B->>MSC-S: A Handover Complete + MSC-S->>RNC A: Iu Release Command + RNC A->>MSC-S: Iu Release Complete + MSC-S->>MGW: Context(C1) SUB.request (T1) + MGW->>MSC-S: Context(C1) SUB.reply (T1) + MGW->>BSC B: Release Termination + +``` + +Figure 8.8/2: Intra-MSC UMTS to GSM Handover (message sequence chart). The diagram shows the interaction between RNC A, MSC-S, MGW, and BSC B. The sequence starts with 'A Handover Complete' from BSC B to MSC-S. MSC-S sends 'Iu Release Command' to RNC A. A green box labeled 'Release of bearer' spans the MGW lifeline. RNC A sends 'Iu Release Complete' to MSC-S. MSC-S sends 'Context(C1)' and 'SUB.request (T1)' to MGW. MGW sends 'Context(C1)' and 'SUB.reply (T1)' back to MSC-S. Finally, MGW sends 'Release Termination' to BSC B. A circled number 4 is on the MSC-S lifeline between 'Iu Release Complete' and 'Context(C1)'. + +**Figure 8.8/2: Intra-MSC UMTS to GSM Handover (message sequence chart)** + +#### 8.2.1.10 Intra-MSC UMTS to GSM Handover for A interface over IP + +When the MSC server receives the RANAP Relocation Required message, it requests the MGW to reserve an RTP bearer termination using the Reserve RTP Connection Point procedure. The MSC server requests the MGW to reserve an IP address and UDP port. The MSC server uses the Change Flow Direction procedure to request the MGW to set the Handover Device to initial state. + +The MGW reserves the RTP termination and indicates the IP address and UDP port number to the MSC server. The IP addresses and UDP ports of the MGW is sent to the BSC in the BSSMAP Handover Request message. When the MSC server receives the BSSMAP Handover Request-Ack message, it shall send the BSC IP address and UDP Port number to the MGW using the Configure RTP Connection Point procedure. + +The sequence is shown in Figure 8.2.1.10/1. + +![Sequence diagram for Intra-MSC UMTS to GSM Handover for AoIP. Lifelines: RNC A, MSC-S, MGW, BSC B. The sequence starts with RNC A sending an 'Iu Relocation Required' to MSC-S. MSC-S sends a 'TopDescr' message to MGW (labeled 1). MGW responds with 'Reserve RTP Connection Point, Change Flow Direction' and 'TopDescr()+ADD.reply (T3)'. MSC-S sends 'A Handover Request' to BSC B, which responds with 'A Handover Request-Ack'. MSC-S sends 'MOD.request (T3)' to MGW (labeled 2). MGW responds with 'Configure RTP Connection Point' and 'MOD.reply (T3)'. MSC-S sends 'Iu Relocation Command' to RNC A. A box at the bottom indicates 'Flow Continues as in Figure 8.8/1-2'.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +``` + +sequenceDiagram + participant RNC A + participant MSC-S + participant MGW + participant BSC B + + Note left of RNC A: Context(C1) + RNC A->>MSC-S: Iu Relocation Required + Note left of MSC-S: Context(C1) + MSC-S->>MGW: TopDescr({*,$,isolate},{T2,$,oneway})+ADD.request ($) + Note right of MGW: Reserve RTP Connection Point, Change Flow Direction + MGW-->>MSC-S: TopDescr()+ADD.reply (T3) + Note left of MSC-S: Context(C1) + MSC-S->>BSC B: A Handover Request + BSC B-->>MSC-S: A Handover Request-Ack + Note left of MSC-S: Context(C1) + MSC-S->>MGW: MOD.request (T3) + Note right of MGW: Configure RTP Connection Point + MGW-->>MSC-S: MOD.reply (T3) + Note left of MSC-S: Context(C1) + MSC-S->>RNC A: Iu Relocation Command + Note right of RNC A: Context(C1) + Note bottom: Flow Continues as in Figure 8.8/1-2 + +``` + +Sequence diagram for Intra-MSC UMTS to GSM Handover for AoIP. Lifelines: RNC A, MSC-S, MGW, BSC B. The sequence starts with RNC A sending an 'Iu Relocation Required' to MSC-S. MSC-S sends a 'TopDescr' message to MGW (labeled 1). MGW responds with 'Reserve RTP Connection Point, Change Flow Direction' and 'TopDescr()+ADD.reply (T3)'. MSC-S sends 'A Handover Request' to BSC B, which responds with 'A Handover Request-Ack'. MSC-S sends 'MOD.request (T3)' to MGW (labeled 2). MGW responds with 'Configure RTP Connection Point' and 'MOD.reply (T3)'. MSC-S sends 'Iu Relocation Command' to RNC A. A box at the bottom indicates 'Flow Continues as in Figure 8.8/1-2'. + +Figure 8.2.1.10/1: Intra-MSC UMTS to GSM Handover for AoIP (message sequence chart) + +## 8.2.2 Basic Inter-MSC UMTS to GSM Handover + +The procedures specified in 3GPP TS 23.009 [8] for "Basic Handover Procedure Requiring a Circuit Connection between 3G\_MSC-A and MSC-B" shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +### 8.2.2.1 MSC-A/ MGW-A + +#### 8.2.2.1.1 Bearer establishment between MGW-A and MGW-B + +The handling of the bearer establishment between MGW-A and MGW-B is as described for a Basic Mobile Originating Call, using either forward or backward bearer establishment. For non-speech calls the MSC-A server shall provide MGW-A with the GSM Channel coding properties and the same PLMN Bearer Capability [4] as was provided at the last access bearer assignment. The MSC-A server also uses the Change Flow Direction procedure to request MGW-A to set the Handover Device to initial state (bullet 3 in figure 8.10/1). + +#### 8.2.2.1.2 Relocation Command/Handover Detect + +When the MSC-A server sends the Relocation Command message or alternatively if it receives the Handover Detect message, the MSC-A server uses the Change Flow Direction procedure to requests the MGW to set the Handover Device to intermediate state (bullet 2 in figure 8.10/1). + +#### 8.2.2.1.3 Handover Complete + +When the MSC-A server receives the Relocation Complete message, it requests RNC-A to release the IU. The MSC-A also requests the MGW to set the Handover Device to its final state by removing the bearer termination towards RNC-A, using the Release Termination procedure (bullet 3 in figure 8.10/1). + +#### 8.2.2.1.4 Interworking function + +The interworking function used by MGW-A before handover will also be used after handover. + +#### 8.2.2.1.5 Voice Processing function + +Voice processing function(s) provided by MGW-A before handover, may be continued or modified by MGW-A and/or MGW-B after handover. + +#### 8.2.2.1.6 Handling of multiple bearers (multicall) + +If the UE is engaged with multiple bearers then one bearer is selected to be handed over according to 3GPP TS 23.009 [8]. The calls carried by bearers that have not been selected will be cleared after the reception of Handover Complete message, as described in clause 7.3. + +#### 8.2.2.1.7 Failure Handling in MSC server + +When a procedure between the MSC-A server and MGW-A fails the MSC-A server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If MGW-A resources have been already seized for the bearer towards MGW-B then the resources shall be released using the Release Termination procedure. The call towards MSC-B server shall be cleared as described in clause 7.3. If the original call is to be cleared, then it shall be handled as described in clause 7.3. + +### 8.2.2.2 MSC-B/MGW-B + +#### 8.2.2.2.1 MGW selection + +The MSC-B server selects an MGW when it receives Prepare Handover Request message (bullet 1 in figure 8.10/1). + +#### 8.2.2.2.2 Bearer establishment towards BSC-B + +When the MSC-B server has selected MGW-B it requests MGW-B to seize a TDM circuit, using the Reserve Circuit procedure. The MSC-B server sends the Handover Request message to the BSC-B containing the CIC (bullet 2 in figure 8.10/1). + +#### 8.2.2.2.3 Bearer establishment between MGW-A and MGW-B + +The handling of the bearer establishment between MGW-A and MGW-B is as described for a Basic Mobile Terminating Call, using either forward or backward bearer establishment. + +#### 8.2.2.2.4 Voice Processing function + +Voice processing function(s) provided by MGW-A before handover, may be continued or modified by MGW-B after handover. + +#### 8.2.2.2.5 Failure Handling in MSC server + +When a procedure between the MSC-B server and MGW-B fails the MSC-B server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If MGW-B resources have already been seized at the target access side then the resources shall be released using the Release Termination procedure. The call from MSC-A server shall be released as described at subclause 7.1. + +#### 8.2.2.2.6 Example + +Figure 8.9 shows the network model for the Basic Inter-MSC UMTS to GSM Handover. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in case of GSM access) and the bearer. In MGW-A the bearer termination T1 is used for the bearer towards RNC-A, bearer termination + +T3 is used for the bearer towards MGW-B, and the bearer termination T2 is used for the bearer towards the succeeding/preceding MGW. In MGW-B the bearer termination T4 is used for the bearer towards BSC-B, bearer termination T5 is used for the bearer towards MGW-A. + +![Diagram illustrating the network model for Basic Inter-MSC UMTS to GSM Handover, showing three stages: Before Handover, During Handover, and After Handover.](18d7d8de298d79e7bc87af5217f11203_img.jpg) + +The diagram illustrates the network model for Basic Inter-MSC UMTS to GSM Handover across three stages: + +- Before Handover:** A User Equipment (UE) is connected to RNC A. RNC A is connected to MSC-S A via a dashed green line. MSC-S A is connected to MGW A via a solid blue line. MGW A has bearers T1 and T2. T1 is connected to RNC A via a dotted red line. T2 is connected to an external network via a dotted red line. +- During Handover:** The UE is shown moving from RNC A towards BSC B. A new dashed green line is established from the UE to MSC-S B. MSC-S B is connected to MGW B via a solid blue line. MGW B has bearers T4 and T5. T4 is connected to BSC B via a dotted red line. T5 is connected to MGW A via a dotted red line. MGW A still has bearers T1, T2, and T3. T3 is connected to MGW B via a dotted red line. +- After Handover:** The UE is now connected to BSC B. BSC B is connected to MGW B via a dotted red line. MGW B is connected to MSC-S B via a solid blue line. MSC-S B is connected to MSC-S A via a dashed green line. MSC-S A is connected to MGW A via a solid blue line. MGW A has bearers T2 and T3. T2 is connected to an external network via a dotted red line. T3 is connected to MGW B via a dotted red line. + +Diagram illustrating the network model for Basic Inter-MSC UMTS to GSM Handover, showing three stages: Before Handover, During Handover, and After Handover. + +Figure 8.9: Basic Inter-MSC UMTS to GSM Handover (network model) + +Figure 8.10 shows the message sequence example for the Basic Inter-MSC UMTS to GSM Handover. + +It is assumed that the Handover Device is located in the MGW (MGW-A) which has been selected for the call establishment by the MSC server (MSC-A server). The MSC server controls the call and the mobility management. It is also assumed that only one bearer has been established towards RNC-A. + +In the example the MSC-B server requests MGW-B to seize BSC-B side bearer termination. The call is established between MSC-A server and MSC-B server, and the bearer is established between MGW-A and MGW-B. When the handover is detected in BSC-B the MSC-A server requests to change the flow directions between the terminations within the context in MGW-A. When MSC-A server receives Handover Complete indication from MSC-B server it orders RNC-A to release the IU. Finally MSC-A server requests MGW-A to remove RNC-A side bearer termination. + +![Sequence diagram for Basic Inter-MSC UMTS to GSM Handover. Lifelines: RNC A, MSC-S A, MGW A, MSC-S B, MGW B, BSC B. The diagram shows the message exchange for preparing and executing the handover, including context transfer, bearer setup, and final relocation commands.](1314748d1fff41b2d57a8ba9e9687c6a_img.jpg) + +``` + +sequenceDiagram + participant RNC A + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant BSC B + + Note right of MSC-S B: 1 + MSC-S A->>MSC-S B: MAP Prepare Handover Req. + Note right of MSC-S B: 2 + MSC-S B->>MGW B: ADD.request (T4) Context($) + + Note right of BSC B: Reserve Circuit + MGW B->>MSC-S B: ADD.reply (T4) Context(C2) + MSC-S B->>BSC B: A Handover Request + BSC B->>MSC-S B: A Handover Request-Ack + MSC-S B->>MSC-S A: MAP Prepare Handover Resp. + Note right of MSC-S A: 3 + MSC-S A->>MGW A: Context(C1) TopDescr({*, $, isolate}, {T2, $, oneway})+ADD.request($) + + Note right of MGW A: Prepare Bearer, Change Flow Direction + MGW A->>MSC-S A: Context(C1) TopDescr()+ADD.reply (T3) + Note over MGW A, MGW B: Call and Bearer Establishment + MSC-S A->>RNC A: Iu Relocation Command + +``` + +Sequence diagram for Basic Inter-MSC UMTS to GSM Handover. Lifelines: RNC A, MSC-S A, MGW A, MSC-S B, MGW B, BSC B. The diagram shows the message exchange for preparing and executing the handover, including context transfer, bearer setup, and final relocation commands. + +Figure 8.10/1: Basic Inter-MSC UMTS to GSM Handover (message sequence chart) + +![Sequence diagram for Basic Inter-MSC UMTS to GSM Handover. Lifelines: RNC A, MSC-S A, MGW A, MSC-S B, MGW B, BSC B. The process starts with a handover detection in BSC B, followed by signaling and bearer release procedures between the network elements.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +``` + +sequenceDiagram + participant RNC A + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant BSC B + + Note right of BSC B: Handover detected in target BSC + BSC B->>MSC-S B: A Handover Detect + MSC-S B->>MSC-S A: MAP Process AccessSignalling Req. + MSC-S A->>MGW A: Context(C1) TopDescr({T2, T1, oneway}, {T2,T3,bothway}) + Note right of MGW A: 4 Change Flow Direction + MGW A->>MSC-S A: Context(C1) TopDescr() + MSC-S B->>BSC B: A Handover Complete + MSC-S B->>MSC-S A: MAP Send EndSignal Req. + MSC-S A->>MGW A: Answer + MSC-S A->>RNC A: Iu Release Command + Note right of RNC A: 5 + Note right of RNC A: Release of bearer + RNC A->>MSC-S A: Iu Release Complete + MSC-S A->>MGW A: Context(C1) SUB.request (T1) + MGW A->>MSC-S A: Context(C1) SUB.reply (T1) Release Termination + +``` + +Sequence diagram for Basic Inter-MSC UMTS to GSM Handover. Lifelines: RNC A, MSC-S A, MGW A, MSC-S B, MGW B, BSC B. The process starts with a handover detection in BSC B, followed by signaling and bearer release procedures between the network elements. + +Figure 8.10/2: Basic Inter-MSC UMTS to GSM Handover (message sequence chart) + +### 8.2.2.3 Basic Inter-MSC UMTS to GSM Handover for A Interface over IP + +If AoIP is supported by the MSC server, the Core Network side procedures described earlier in 8.2.2 shall apply. For the access side termination, the exchange of IP addresses via call control procedures is described in this clause. + +When the MSC-B server receives the MAP Prepare Handover Request., it requests the MGW-B to reserve an RTP bearer termination using the Reserve RTP Connection Point procedure. The MSC-B server requests the MGW-B to reserve an IP address and UDP port. + +The MGW-B reserves the RTP termination and indicates the IP address and UDP port number to the MSC-B server. The IP addresses and UDP ports of the MGW is sent to the BSC-B in the BSSMAP Handover Request message. When the MSC-B server receives the BSSMAP Handover Request-Ack message, it shall send the BSC-B IP address and UDP Port number to the MGW-B using the Configure RTP Connection Point procedure. + +The sequence is shown in Figure 8.2.2.3/1. + +![Figure 8.2.2.3/1: Basic Inter-MSC UMTS to GSM Handover for AoIP (message sequence chart). The diagram shows the interaction between RNC A, MSC-S A, MGW A, MSC-S B, MGW B, and BSC B. The sequence starts with RNC A sending an 'Iu Relocation Required' to MSC-S A. MSC-S A sends a 'MAP Prepare Handover Req.' to MSC-S B (labeled 1). MSC-S B sends an 'ADD.request ($)' to MGW B, which responds with 'ADD.reply (T4)'. MSC-S B then sends an 'A Handover Request' to BSC B, which responds with 'A Handover Request-Ack'. MSC-S B sends a 'MOD.request (T4)' to MGW B, which responds with 'MOD.reply (T4)'. MSC-S B sends a 'MAP Prepare Handover Resp.' back to MSC-S A. A note indicates the flow continues as in Figure 8.10/1-2.](8f8caebe58364416a2eda21039d8c7bf_img.jpg) + +``` + +sequenceDiagram + participant RNC A + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant BSC B + + Note left of RNC A: Iu Relocation Required + RNC A->>MSC-S A: Iu Relocation Required + MSC-S A->>MSC-S B: MAP Prepare Handover Req. (1) + MSC-S B->>MGW B: ADD.request ($) + MGW B-->>MSC-S B: ADD.reply (T4) + Note right of MGW B: Reserve RTP Connection Point + MSC-S B->>BSC B: A Handover Request + BSC B-->>MSC-S B: A Handover Request-Ack + MSC-S B->>MGW B: MOD.request (T4) + MGW B-->>MSC-S B: MOD.reply (T4) + Note right of MGW B: Configure RTP Connection Point + MSC-S B-->>MSC-S A: MAP Prepare Handover Resp. + Note right of MSC-S A: Context($), Context(C2) + Note right of MSC-S B: Context(C2), Context(C2) + Note right of RNC A: Flow Continues as in Figure 8.10/1-2 + +``` + +Figure 8.2.2.3/1: Basic Inter-MSC UMTS to GSM Handover for AoIP (message sequence chart). The diagram shows the interaction between RNC A, MSC-S A, MGW A, MSC-S B, MGW B, and BSC B. The sequence starts with RNC A sending an 'Iu Relocation Required' to MSC-S A. MSC-S A sends a 'MAP Prepare Handover Req.' to MSC-S B (labeled 1). MSC-S B sends an 'ADD.request (\$)' to MGW B, which responds with 'ADD.reply (T4)'. MSC-S B then sends an 'A Handover Request' to BSC B, which responds with 'A Handover Request-Ack'. MSC-S B sends a 'MOD.request (T4)' to MGW B, which responds with 'MOD.reply (T4)'. MSC-S B sends a 'MAP Prepare Handover Resp.' back to MSC-S A. A note indicates the flow continues as in Figure 8.10/1-2. + +Figure 8.2.2.3/1: Basic Inter-MSC UMTS to GSM Handover for AoIP (message sequence chart) + +## 8.2.3 Subsequent Inter-MSC UMTS to GSM Handover back to the Anchor MSC + +The following handling shall be applied for a call that started as UMTS call. The procedures specified in 3GPP TS 23.009 [8] for "Subsequent UMTS to GSM handover requiring a Circuit Connection between 3G\_MSC-A and 3G\_MSC-B, 3G\_MSC-B to MSC-A" shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +### 8.2.3.1 MSC-A + +#### 8.2.3.1.1 Handover Request + +When the MSC-A server receives the MAP Prepare Subsequent Handover request containing a Handover Request message, it requests MGW-A to seize a TDM circuit, using the Reserve Circuit procedure. For non-speech calls the MSC-A server shall provide MGW-A with the GSM Channel coding properties and the same PLMN Bearer Capability [4] as was provided at the first access bearer assignment. The MSC-A server uses the Change Flow Direction procedure + +to request MGW-A to set the Handover Device to initial state. The MSC-A server sends the Handover Request message, containing the CIC, to BSC-B (bullet 1 in figure 8.12/1). + +#### 8.2.3.1.2 Handover Request Acknowledge + +For non-speech calls after receiving the Handover Request Acknowledge message if the assigned GSM Channel coding properties differ from the previously provided ones the MSC-A server shall provide MGW-A with the assigned GSM Channel coding properties using the Modify Bearer Characteristics procedure (bullet 2 in figure 8.12/1). + +#### 8.2.3.1.3 Relocation Command/Handover Detect + +When the MSC-A server sends the MAP Prepare Subsequent Handover response message or alternatively if it receives the Handover Detect message, the MSC-A server uses the Change Flow Direction procedure to requests MGW-A to set the Handover Device to intermediate state (bullet 3 in figure 8.12/2). + +#### 8.2.3.1.4 Handover Complete + +When the MSC-A server receives the Handover Complete message, it informs the MSC-B server about reception of this message (bullet 3 in figure 8.12/2). The MSC-A server then initiates call clearing towards the MSC-B server as described at 7.3. + +#### 8.2.3.1.5 Interworking function + +The interworking function used by MGW-A before handover will also be used after handover. + +#### 8.2.3.1.6 Voice Processing function + +Voice processing function(s) provided by MGW-A and MGW-B before handover, may be continued or modified by MGW-A after handover. + +#### 8.2.3.1.7 Handling of multiple bearers (multicall) + +If the UE is engaged with multiple bearers the selected bearer to be handed over is received from MSC-B server in the Handover Request message according to 3GPP TS 23.009 [8]. The calls carried by the bearers that have not been selected will be cleared by MSC-A server after the reception of the Handover Complete message, as described in clause 7.3. + +#### 8.2.3.1.8 Failure Handling in MSC server + +When a procedure between the MSC-A server and the MGW fails the MSC-A server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If MGW resources have already been seized at the target access side then the resources shall be released using the Release Termination procedure. If the call is to be cleared, then it shall be handled as described in clause 7.3. + +### 8.2.3.2 MSC-B + +#### 8.2.3.2.1 Handover Complete + +When the MSC-B server receives the Handover Complete message, it requests RNC-A to release the IU. The MSC-B server also requests MGW-B to remove the bearer termination towards RNC-A using the Release Termination procedure (bullet 4 in figure 8.12/2). + +#### 8.2.3.2.2 Release of bearer towards MGW-A + +When the MSC-B server receives a call clearing indication from the MSC-A server, the MSC-B server handles it as described in clause 7.2. + +#### 8.2.3.2.3 Handling of multiple bearers (multicall) + +If the UE is engaged with multiple bearers then one bearer is selected by MSC-B server to be handed over according to 3GPP TS 23.009 [8]. + +### 8.2.3.2.4 Example + +Figure 8.11 shows the network model for the Subsequent Inter- MSC UMTS to GSM handover back to the Anchor MSC. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in case of GSM access) and the bearer. In MGW-A the bearer termination T6 is used for the bearer towards BSC-B, bearer termination T3 is used for the bearer towards MGW-B, and the bearer termination T2 is used for the bearer towards the succeeding/preceding MGW. In MGW-B the bearer termination T4 is used for the bearer towards RNC-A, bearer termination T5 is used for the bearer towards MGW-A. + +![Figure 8.11: Subsequent Inter- MSC UMTS to GSM Handover back to the Anchor MSC (network model). The diagram illustrates three stages of a network configuration: 'Before Handover', 'During Handover', and 'After Handover'. In 'Before Handover', RNC A is connected to MGW B (CTX2) via bearers T4 and T5. MGW B is connected to MSC-S B via a squared call control line. MSC-S B is connected to MSC-S A via a squared call control line. MSC-S A is connected to MGW A (CTX1) via a squared call control line. MGW A has bearers T3, T2, and T6. T3 is connected to MGW B, T2 is connected to the right, and T6 is connected to RNC A. In 'During Handover', the connections are reconfigured: RNC A is now connected to BSC B. BSC B is connected to MSC-S A via a squared call control line. MSC-S A is connected to MGW A (CTX1) via a squared call control line. MGW A has bearers T6, T2, and T3. T6 is connected to BSC B, T2 is connected to the right, and T3 is connected to MGW B. MGW B is connected to RNC A via bearers T4 and T5. In 'After Handover', RNC A is connected to BSC B. BSC B is connected to MSC-S A via a squared call control line. MSC-S A is connected to MGW A (CTX1) via a squared call control line. MGW A has bearers T6, T2, and T3. T6 is connected to BSC B, T2 is connected to the right, and T3 is connected to MGW B. MGW B is connected to RNC A via bearers T4 and T5.](070352b751dd0711b8ac6ddfa6df1d98_img.jpg) + +**Before Handover** + +**During Handover** + +**After Handover** + +Figure 8.11: Subsequent Inter- MSC UMTS to GSM Handover back to the Anchor MSC (network model). The diagram illustrates three stages of a network configuration: 'Before Handover', 'During Handover', and 'After Handover'. In 'Before Handover', RNC A is connected to MGW B (CTX2) via bearers T4 and T5. MGW B is connected to MSC-S B via a squared call control line. MSC-S B is connected to MSC-S A via a squared call control line. MSC-S A is connected to MGW A (CTX1) via a squared call control line. MGW A has bearers T3, T2, and T6. T3 is connected to MGW B, T2 is connected to the right, and T6 is connected to RNC A. In 'During Handover', the connections are reconfigured: RNC A is now connected to BSC B. BSC B is connected to MSC-S A via a squared call control line. MSC-S A is connected to MGW A (CTX1) via a squared call control line. MGW A has bearers T6, T2, and T3. T6 is connected to BSC B, T2 is connected to the right, and T3 is connected to MGW B. MGW B is connected to RNC A via bearers T4 and T5. In 'After Handover', RNC A is connected to BSC B. BSC B is connected to MSC-S A via a squared call control line. MSC-S A is connected to MGW A (CTX1) via a squared call control line. MGW A has bearers T6, T2, and T3. T6 is connected to BSC B, T2 is connected to the right, and T3 is connected to MGW B. MGW B is connected to RNC A via bearers T4 and T5. + +**Figure 8.11: Subsequent Inter- MSC UMTS to GSM Handover back to the Anchor MSC (network model)** + +Figure 8.12 shows the message sequence example for the Subsequent Inter-MSC UMTS to GSM Handover back to the Anchor MSC. It is assumed that the Handover Device is located in the MGW (MGW-A) selected for the call establishment by the MSC server (MSC-A server) which controls the call and the mobility management. Also assumed that only one bearer has been established towards RNC-A and that MGW-A is capable to handle GSM access. In the example the MSC-A server requests MGW-A to seize BSC-B side bearer termination with specific flow directions. When the relocation is detected in BSC-B the MSC-A server requests to change the flow directions between the terminations within the context in MGW-A. When MSC-A server receives Handover Complete indication from BSC-B it transfers this indication to MSC-B server. MSC-B server orders RNC-A to release the IU. MSC-A server initiates call clearing towards MSC-B server. + +![Sequence diagram for Subsequent Inter-MSC UMTS to GSM Handover back to the Anchor MSC. Lifelines: BSC B, MSC-S A, MGW A, MSC-S B, MGW B, RNC A. The sequence shows the flow of messages for context transfer, bearer modification, and handover signaling between the network elements.](f7b2cf9e1b71dc4f900f3810646d3903_img.jpg) + +``` + +sequenceDiagram + participant BSC B + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant RNC A + + Note right of RNC A: Iu Relocation Required + MSC-S B->>MSC-S A: MAP Prepare Subsequent Handover Req. + Note left of MGW A: 1 + MSC-S A->>MGW A: Context(C1) TopDescr({*,T6,isolate}, {T2,T6,oneway}) +ADD.request (T6) + Note right of MGW A: Reserve Circuit, Change Flow Direction + MGW A->>MSC-S A: Context(C1) TopDescr() +ADD.reply (T6) + MSC-S A->>BSC B: A Handover Request + BSC B->>MSC-S A: A Handover Request-Ack + Note left of MGW A: 2 + MSC-S A->>MGW A: Context(C1) MOD.request (T6) + Note right of MGW A: Modify Bearer Characteristics (when applicable) + MGW A->>MSC-S A: Context(C1) MOD.reply (T6) + +``` + +Sequence diagram for Subsequent Inter-MSC UMTS to GSM Handover back to the Anchor MSC. Lifelines: BSC B, MSC-S A, MGW A, MSC-S B, MGW B, RNC A. The sequence shows the flow of messages for context transfer, bearer modification, and handover signaling between the network elements. + +**Figure 8.12/1: Subsequent Inter-MSC UMTS to GSM Handover back to the Anchor MSC (message sequence chart)** + +![Sequence diagram for Subsequent Inter-MSC UMTS to GSM Handover back to the Anchor MSC. Lifelines: BSC B, MSC-S A, MGW A, MSC-S B, MGW B, RNC A. The process involves handover detection, context transfer, bearer preparation, and final release and clearing.](38d82ffe820e339811b396206f40a201_img.jpg) + +``` + +sequenceDiagram + participant BSC B + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant RNC A + + Note left of BSC B: Handover detected in target BSC + BSC B->>MSC-S A: A Handover Detect + MSC-S A->>MGW A: Context(C1) TopDescr({T2, T3, oneway}, {T2, T6,bothway}) + Note right of MGW A: Change Flow Direction + MGW A->>MSC-S A: Context(C1) TopDescr() + Note right of MSC-S A: 3 + MSC-S A->>BSC B: A Handover Complete + MSC-S A->>MSC-S B: MAP Prepare Subsequent HandoverResp. + MSC-S B->>RNC A: Iu Relocation Command + Note right of MSC-S B: 4 + MSC-S B->>MGW B: Iu Release Command + Note right of MGW B: Release of bearer + MGW B->>MSC-S B: Iu Release Complete + MSC-S B->>MGW A: Context(C2) SUB.request (T4) + MGW A->>MSC-S B: Context(C2) SUB.reply (T4) + Note right of MGW A: Call Clearing and Bearer Release + +``` + +Sequence diagram for Subsequent Inter-MSC UMTS to GSM Handover back to the Anchor MSC. Lifelines: BSC B, MSC-S A, MGW A, MSC-S B, MGW B, RNC A. The process involves handover detection, context transfer, bearer preparation, and final release and clearing. + +**Figure 8.12/2: Subsequent Inter-MSC UMTS to GSM Handover back to the Anchor MSC (message sequence chart)** + +### 8.2.3.3 Subsequent Inter-MSC UMTS to GSM Handover back to the anchor MSC for A Interface over IP + +When the MSC-A server receives the MAP Prepare Subsequent Handover Request. message, it requests the MGW-A to reserve an RTP bearer termination using the Reserve RTP Connection Point procedure. The MSC-A server requests the MGW-A to reserve an IP address and UDP port. The MSC-A server uses the Change Flow Direction procedure to request the MGW-A to set the Handover Device to initial state. + +The MGW-A reserves the RTP termination and indicates the IP address and UDP port number to the MSC-A server. The IP addresses and UDP ports of the MGW-A is sent to the BSC-B in the BSSMAP Handover Request message. When the MSC-A server receives the BSSMAP Handover Request-Ack message, it shall send the BSC-A IP address and UDP Port number to the MGW-B using the Configure RTP Connection Point procedure. + +The sequence is shown in Figure 8.2.3.3/1. + +![Figure 8.2.3.c.1: Subsequent Inter-MSC UMTS to GSM Handover back to the anchor MSC for AoIP (message sequence chart).](d9638e837004a4e09dbbc50b8aecbd5f_img.jpg) + +The diagram is a message sequence chart showing the interaction between six network elements: BSC B, MSC-A, MGW A, MSC-B, MGW B, and RNC A. The sequence of messages is as follows: + +- Iu Relocation Required:** RNC A sends this message to MSC-B. +- MAP Prepare Subsequent Handover Req.:** MSC-B sends this message to MSC-A. +- TopDescr(\*,\$,isolate), {T2,\$,oneway} +ADD.request (\$):** MSC-A sends this message to MGW A. A circled '1' is next to this message. +- Reserve RTP Connection Point, Change Flow Direction:** MGW A performs this internal action. +- TopDescr() +ADD.reply (T6):** MGW A sends this message to MSC-A. +- A Handover Request:** MSC-A sends this message to BSC B. +- A Handover Request-Ack:** BSC B sends this message to MSC-A. +- MOD.request (T6):** MSC-A sends this message to MGW A. A circled '2' is next to this message. +- Configure RTP Connection Point:** MGW A performs this internal action. +- MOD.reply (T6):** MGW A sends this message to MSC-A. +- MAP Prepare Subsequent Handover Resp.:** MSC-A sends this message to MSC-B. +- Flow Continues as in Figure 8.12/2:** A final message indicating the continuation of the sequence. + +Figure 8.2.3.c.1: Subsequent Inter-MSC UMTS to GSM Handover back to the anchor MSC for AoIP (message sequence chart). + +**Figure 8.2.3.c.1: Subsequent Inter-MSC UMTS to GSM Handover back to the anchor MSC for AoIP (message sequence chart)** + +## 8.2.4 Subsequent Inter-MSC UMTS to GSM Handover to a third MSC + +The UMTS to GSM handover to a third MSC server (from MSC-B server to MSC-B server) is the combination of the two previous inter-MSC handover cases: + +- for MSC-B server a subsequent UMTS to GSM handover from MSC-B server back to MSC-A server as described in clause 8.2.3; and +- for MSC-B server a basic UMTS to GSM handover from MSC-A server to MSC-B server as described in clause 8.2.2. + +MSC-A server implements the corresponding parts of each handover case; i.e. access handling in MSC-A server is not included. + +## 8.3 GSM to UMTS + +In the context of the following clauses, the terms RNS or RNC refer also to a GERAN BSS or BSC (respectively) when serving a UE in Iu mode. + +### 8.3.1 Intra-MSC GSM to UMTS Handover + +The procedures specified in 3GPP TS 23.009 [8] for "Intra-3G\_MSC GSM to UMTS Handover" shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +### 8.3.1.1 Handover Required + +When the MSC server receives the Handover Required message, it requests the MGW to provide a binding reference and a bearer address using the Prepare Bearer procedure. For speech calls, the MSC server shall provide the MGW with the speech coding information for the bearer. For non-speech calls the MSC server shall provide the MGW with the same PLMN Bearer Capability [4] as was provided at the last channel assignment. The MSC server uses the Change Flow Direction procedure to request the MGW to set the Handover Device to initial state. The MSC server sends the Relocation Request message to the RNC-B containing the bearer address and binding reference (bullet 1 in figure 8.14). + +For Relocation towards GERAN Iu mode the GERAN capabilities of the target cell will be indicated to the MSC-Server within the Handover Required message if the target cell provides different capabilities than the current cell. If no information about the GERAN capabilities of the target cell are received within this message, the MSC-Server shall assume that the GERAN target cell will provide the same capabilities as the current cell (for details see [29]). The MSC server shall indicate to GERAN the selected services within the RANAP RELOCATION REQUEST message. The MSC server shall not set codec information in the NAS Synchronisation Indicator (see [4]). Instead it shall set codec information in the GERAN BSC container. + +### 8.3.1.2 Handover Command/Relocation Detect + +When the MSC server sends the Handover Command message or alternatively if it receives a Relocation Detect message, the MSC server uses the Change Flow Direction procedure to requests the MGW to set the Handover Device to intermediate state (bullet 2 in figure 8.14). + +### 8.3.1.3 Relocation Complete + +When the MSC server receives the Relocation Complete message, it releases the A-interface line towards BSC-A and requests the MGW to set the Handover Device to its final state removing the bearer termination towards BSC-A, using Release Termination procedure (bullet 3 in figure 8.14). + +### 8.3.1.4 Interworking function + +The interworking function used by the MGW before handover will also be used after handover. + +### 8.3.1.5 Codec handling + +The MGW may include a speech transcoder based upon the speech coding information provided to each bearer termination. + +### 8.3.1.6 Voice Processing function + +After handover, the MGW may continue or modify voice processing function(s) provided to each bearer termination. + +### 8.3.1.7 Failure Handling in MSC server + +When a procedure between the MSC server and the MGW fails the MSC server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If MGW resources have already been seized at the target access side then the resources shall be released using the Release Termination procedure. If the call is to be cleared, then it shall be handled as described in clause 7.3. + +### 8.3.1.8 Example + +Figure 8.13 shows the network model for the Intra-3G\_MSC GSM to UMTS Handover. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. The bearer termination T1 is used for the bearer towards the BSC-A (connected through the MSC server), the bearer termination T3 is used for the bearer towards the RNC-B and the bearer termination T2 is used for the bearer towards the succeeding/preceding MGW. + +![Figure 8.13: Intra-3G_MSC GSM to UMTS Handover (network model). The diagram shows three stages: 'Before Handover', 'During Handover', and 'After Handover'. In 'Before Handover', a mobile device is connected to BSC A, which is connected to MSC-S. MSC-S is connected to CTXI MGW. A dashed green line represents the data path from the device through BSC A and MSC-S. In 'During Handover', the device is shown connected to RNC B, which is also connected to CTXI MGW. The data path is shown switching from BSC A to RNC B. In 'After Handover', the device is connected to RNC B, which is connected to CTXI MGW. The data path is now entirely through RNC B and CTXI MGW.](d2417b04116c354deccb25d98a84a0fb_img.jpg) + +**Before Handover** + +**During Handover** + +**After Handover** + +Figure 8.13: Intra-3G\_MSC GSM to UMTS Handover (network model). The diagram shows three stages: 'Before Handover', 'During Handover', and 'After Handover'. In 'Before Handover', a mobile device is connected to BSC A, which is connected to MSC-S. MSC-S is connected to CTXI MGW. A dashed green line represents the data path from the device through BSC A and MSC-S. In 'During Handover', the device is shown connected to RNC B, which is also connected to CTXI MGW. The data path is shown switching from BSC A to RNC B. In 'After Handover', the device is connected to RNC B, which is connected to CTXI MGW. The data path is now entirely through RNC B and CTXI MGW. + +**Figure 8.13: Intra-3G\_MSC GSM to UMTS Handover (network model)** + +Figure 8.14 shows the message sequence example for the Intra-MSC GSM to UMTS Handover. It is assumed that the Handover Device is located in the MGW selected for the call establishment by the MSC server, which controls the call and the mobility management. In the example the MSC server requests seizure of RNC-B side bearer termination with specific flow directions. The MSC server starts handover execution by sending Relocation Request towards RNC-B. When the relocation is detected in RNC-B the MSC server requests to change the flow directions between the terminations within the context. When MSC server receives Relocation Complete indication from RNC-B it releases the A-interface line towards the BSC-A. Finally the MSC server requests the MGW to release BSC-A side bearer termination. + +![Sequence diagram for Intra-3G_MSC GSM to UMTS Handover. Lifelines: BSC A, MSC-S, MGW, RNC B. The process involves: 1. A Handover Required from BSC A to MSC-S. 2. Context(C1) from MSC-S to MGW with TopDescr({*,$,isolate}, {T2, $,oneway})+ADD.request($). 3. Prepare bearer, Change Flow Direction from MGW to MSC-S. 4. TopDescr()+ADD.reply (T3) from MGW to MSC-S. 5. Iu Relocation Request from MSC-S to RNC B. 6. Bearer Establishment (green box) in RNC B. 7. Iu Relocation Request-Ack from RNC B to MSC-S. 8. A Handover Command from MSC-S to BSC A. 9. Relocation execution triggered in target RNC (green box) in RNC B. 10. Iu Relocation Detect from RNC B to MSC-S. 11. Context(C1) from MSC-S to MGW with TopDescr({T2,T1,isolate}, {T2,T3,bothway}). 12. Change Flow Direction from MGW to MSC-S. 13. TopDescr() from MGW to MSC-S. 14. Iu Relocation Complete from MSC-S to RNC B. 15. A Clear Command from MSC-S to BSC A. 16. A Clear Complete from BSC A to MSC-S. 17. Context(C1) from MSC-S to MGW with SUB.request (T1). 18. Context(C1) from MGW to MSC-S with SUB.reply (T1) and Release Termination.](18003425d0e8638dde4acc9c5c468c5c_img.jpg) + +``` + +sequenceDiagram + participant BSC A + participant MSC-S + participant MGW + participant RNC B + + BSC A->>MSC-S: A Handover Required + Note over MSC-S, MGW: 1 + MSC-S->>MGW: Context(C1) TopDescr({*,$,isolate}, {T2, $,oneway})+ADD.request($) + MGW-->>MSC-S: Prepare bearer, Change Flow Direction + MGW-->>MSC-S: Context(C1) TopDescr()+ADD.reply (T3) + MSC-S->>RNC B: Iu Relocation Request + Note right of RNC B: Bearer Establishment + RNC B-->>MSC-S: Iu Relocation Request-Ack + MSC-S->>BSC A: A Handover Command + Note right of RNC B: Relocation execution triggered in target RNC + RNC B-->>MSC-S: Iu Relocation Detect + Note over MSC-S, MGW: 2 + MSC-S->>MGW: Context(C1) TopDescr({T2,T1,isolate}, {T2,T3,bothway}) + MGW-->>MSC-S: Change Flow Direction + MGW-->>MSC-S: Context(C1) TopDescr() + MSC-S->>RNC B: Iu Relocation Complete + MSC-S->>BSC A: A Clear Command + BSC A->>MSC-S: A Clear Complete + Note over MSC-S, MGW: 3 + MSC-S->>MGW: Context(C1) SUB.request (T1) + MGW-->>MSC-S: Context(C1) SUB.reply (T1) Release Termination + +``` + +Sequence diagram for Intra-3G\_MSC GSM to UMTS Handover. Lifelines: BSC A, MSC-S, MGW, RNC B. The process involves: 1. A Handover Required from BSC A to MSC-S. 2. Context(C1) from MSC-S to MGW with TopDescr({\*,\$,isolate}, {T2, \$,oneway})+ADD.request(\$). 3. Prepare bearer, Change Flow Direction from MGW to MSC-S. 4. TopDescr()+ADD.reply (T3) from MGW to MSC-S. 5. Iu Relocation Request from MSC-S to RNC B. 6. Bearer Establishment (green box) in RNC B. 7. Iu Relocation Request-Ack from RNC B to MSC-S. 8. A Handover Command from MSC-S to BSC A. 9. Relocation execution triggered in target RNC (green box) in RNC B. 10. Iu Relocation Detect from RNC B to MSC-S. 11. Context(C1) from MSC-S to MGW with TopDescr({T2,T1,isolate}, {T2,T3,bothway}). 12. Change Flow Direction from MGW to MSC-S. 13. TopDescr() from MGW to MSC-S. 14. Iu Relocation Complete from MSC-S to RNC B. 15. A Clear Command from MSC-S to BSC A. 16. A Clear Complete from BSC A to MSC-S. 17. Context(C1) from MSC-S to MGW with SUB.request (T1). 18. Context(C1) from MGW to MSC-S with SUB.reply (T1) and Release Termination. + +**Figure 8.14: Intra-3G\_MSC GSM to UMTS Handover (message sequence chart)** + +## 8.3.2 Basic Inter-MSC GSM to UMTS Handover + +The following handling shall be applied for a call that started as UMTS call. The procedures specified in 3GPP TS 23.009 [8] for "Basic Handover Procedure Requiring a Circuit Connection between MSC-A and 3G\_MSC-B" shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +### 8.3.2.1 MSC-A + +#### 8.3.2.1.1 Handover Required + +For Handover towards GERAN Iu mode the GERAN capabilities of the target cell will be indicated to the MSC-A server within the Handover Required message if the target cell provides different capabilities than the current cell. If no + +information about the GERAN capabilities of the target cell are received within this message, the MSC-A server shall assume that the GERAN target cell will provide the same capabilities as the current cell (for details see [29]). + +The MSC-A server shall indicate to the MSC-B server the GERAN capabilities of the target cell, if available, with the MAP Prepare Handover request. For speech calls, the MSC-A server shall additionally indicate to the MSC-B server the selected codec, the list of supported codecs, and the currently used codec. + +#### 8.3.2.1.2 Bearer establishment between MGW-A and MGW-B + +The handling of the bearer establishment between MGW-A and MGW-B is as described for a Basic Mobile Originating Call, using either forward or backward bearer establishment. For speech calls, the MSC-A server shall provide the MGW-A with the speech coding information for the bearer. For non-speech calls the MSC-A server shall provide MGW-A with the same PLMN Bearer Capabilities [4] as were provided at the last access bearer assignment. The MSC-A server also uses the Change Flow Direction procedure to request MGW-A to set the Handover Device to initial state (bullet 3 in figure 8.16/1). + +#### 8.3.2.1.3 Handover Command/Handover Detect + +When the MSC-A server sends the Handover Command message or alternatively if it receives the Handover Detect message, the MSC-A server uses the Change Flow Direction procedure to requests MGW-A to set the Handover Device to intermediate state (bullet 4 in figure 8.16/2). + +#### 8.3.2.1.4 Handover Complete + +When the MSC-A server receives the Handover Complete message, it releases the A-interface line towards BSC-A and requests MGW-A to set the Handover Device to its final state by removing the bearer termination towards BSC-A, using Release Termination procedure (bullet 5 in figure 8.16/2). + +#### 8.3.2.1.5 Interworking function + +The interworking function used by MGW-A before handover will also be used after handover. + +#### 8.3.2.1.6 Codec handling + +The MGW may include a speech transcoder based upon the speech coding information provided to each bearer termination. + +#### 8.3.2.1.7 Voice Processing function + +Voice processing function(s) provided by MGW-A before handover, may be modified or disabled by MGW-A after handover. + +#### 8.3.2.1.8 Failure Handling in MSC server + +When a procedure between the MSC-A server and MGW-A fails the MSC-A server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If the call establishment towards MSC-B has already started then the call towards MSC-B server shall be cleared as described in clause 7.3. If the original call is to be cleared, then it shall be handled as described in clause 7.3. + +### 8.3.2.2 MSC-B + +#### 8.3.2.2.1 MGW selection + +The MSC-B server selects an MGW when it receives Prepare Handover Request message (bullet 1 in figure 8.16). + +#### 8.3.2.2.2 Bearer establishment towards RNC-B + +When the MSC-B server has selected MGW-B it requests MGW-B to provide a binding reference and a bearer address using the Prepare Bearer procedure. For speech calls, the MSC server shall provide the MGW with the speech coding information for the bearer. The MSC-B server sends the Relocation Request message to the RNC-B containing the bearer address and binding reference (bullet 2 in figure 8.16). + +For Handover towards GERAN Iu-mode, the MSC-B Server shall select a service according to the Channel Type received with the Handover Request message and the capabilities of the GERAN target cell, if the GERAN classmark was received. For speech calls, the MSC-B server shall additionally take into account the selected codec, the list of + +supported codecs and the currently used codec received with MAP Prepare Handover request. The list of permitted speech versions received with the Channel Type in the Handover Request message is applicable to GERAN A/Gb mode only. + +The MSC-B server shall indicate to the GERAN the selected service within the RANAP RELOCATION REQUEST message and shall set the RAB parameters within the RANAP RELOCATION REQUEST message according to the selected service. The MSC server shall not set codec information in the NAS Synchronisation Indicator (see [4]). Instead it shall set codec information in the GERAN BSC container.. + +For speech calls, the MSC-B server shall report the chosen codec and codec modes back to the MSC-A server with MAP Prepare Handover response. + +#### 8.3.2.2.3 Bearer establishment between MGW-A and MGW-B + +The handling of the bearer establishment is as described at Basic Mobile Terminating Call, using either forward or backward bearer establishment. + +#### 8.3.2.2.4 Codec handling + +The MGW may include a speech transcoder based upon the speech coding information provided to each bearer termination. + +#### 8.3.2.2.5 Voice Processing function + +Voice processing function(s) provided by MGW-A before handover, may be continued or modified by MGW-B after handover. + +#### 8.3.2.2.6 Failure Handling in MSC server + +When a procedure between the MSC-B server and MGW-B fails the MSC-B server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If MGW-B resources have already been seized at the target access side then the resources shall be released using the Release Termination procedure. The call from MSC-A server shall be released as described at clause 7.1. + +#### 8.3.2.2.7 Example + +Figure 8.15 shows the network model for the Basic Inter-MSC GSM to UMTS Handover. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in case of GSM access) and the bearer. In MGW-A the bearer termination T1 is used for the bearer towards BSC-A, bearer termination T3 is used for the bearer towards MGW-B, and the bearer termination T2 is used for the bearer towards the succeeding/preceding MGW. In MGW-B the bearer termination T4 is used for the bearer towards RNC-B, bearer termination T5 is used for the bearer towards MGW-A. + +![Diagram of the network model for Basic Inter-MSC GSM to UMTS Handover before handover. It shows three main components: MSC-S A (top), BSC A (bottom left), and MGW A (bottom right). MSC-S A is connected to BSC A by a dashed green line (call control signalling). MSC-S A is connected to MGW A by a solid blue line (bearer control signalling). BSC A is connected to MGW A by a dotted red line (bearer). MGW A has three bearers: T1 (towards BSC A), T2 (towards the succeeding/preceding MGW), and T3 (towards MGW-B).](d9d41a512d5ad50bad281dba2f0061b0_img.jpg) + +``` + +graph TD + MSCSA[MSC-S A] -- "Call Control (Dashed Green)" --> BSCA[BSC A] + MSCSA -- "Bearer Control (Solid Blue)" --> MGWA[MGW A] + BSCA -- "Bearer (Dotted Red)" --> T1[T1] + subgraph MGWA_Node [MGW A] + T1 + CTX1[CTX1] + T2[T2] + end + T1 --- CTX1 + CTX1 --- T2 + T2 -- "Bearer (Dotted Red)" --> Out[...] + +``` + +Diagram of the network model for Basic Inter-MSC GSM to UMTS Handover before handover. It shows three main components: MSC-S A (top), BSC A (bottom left), and MGW A (bottom right). MSC-S A is connected to BSC A by a dashed green line (call control signalling). MSC-S A is connected to MGW A by a solid blue line (bearer control signalling). BSC A is connected to MGW A by a dotted red line (bearer). MGW A has three bearers: T1 (towards BSC A), T2 (towards the succeeding/preceding MGW), and T3 (towards MGW-B). + +**Before Handover** + +![Figure 8.15: Basic Inter-MSC GSM to UMTS Handover (network model). The diagram is divided into two sections: 'During Handover' and 'After Handover'. In the 'During Handover' section, a BSC A is connected to an MSC-S A via a red dotted line. BSC A is also connected to an RNC B via a green dashed line. RNC B is connected to an MGW B (CTX2) via a red dotted line. MGW B is connected to an MSC-S B via a blue solid line. MSC-S B is connected to an MGW A (CTX1) via a green dashed line. MGW A is connected to an MSC-S A via a blue solid line. In the 'After Handover' section, the BSC A is disconnected from the RNC B. The RNC B is connected to the MGW B (CTX2) via a red dotted line. MGW B is connected to the MSC-S B via a blue solid line. MSC-S B is connected to the MGW A (CTX1) via a green dashed line. MGW A is connected to the MSC-S A via a blue solid line.](a963ca41bde1669b18a4b783616f228b_img.jpg) + +**During Handover** + +**After Handover** + +Figure 8.15: Basic Inter-MSC GSM to UMTS Handover (network model). The diagram is divided into two sections: 'During Handover' and 'After Handover'. In the 'During Handover' section, a BSC A is connected to an MSC-S A via a red dotted line. BSC A is also connected to an RNC B via a green dashed line. RNC B is connected to an MGW B (CTX2) via a red dotted line. MGW B is connected to an MSC-S B via a blue solid line. MSC-S B is connected to an MGW A (CTX1) via a green dashed line. MGW A is connected to an MSC-S A via a blue solid line. In the 'After Handover' section, the BSC A is disconnected from the RNC B. The RNC B is connected to the MGW B (CTX2) via a red dotted line. MGW B is connected to the MSC-S B via a blue solid line. MSC-S B is connected to the MGW A (CTX1) via a green dashed line. MGW A is connected to the MSC-S A via a blue solid line. + +**Figure 8.15: Basic Inter-MSC GSM to UMTS Handover (network model)** + +Figure 8.16 shows the message sequence example for the Basic Inter-MSC GSM to UMTS Handover. It is assumed that the Handover Device is located in the MGW (MGW-A) selected for the call establishment by the MSC server (MSC-A server) which controls the call and the mobility management. + +In the example the MSC-B server requests MGW-B to seize RNC-B side bearer termination. The call is established between MSC-A server and MSC-B server, and the bearer is established between MGW-A and MGW-B. When the relocation is detected in RNC-B the MSC-A server requests to change the flow directions between the terminations within the context in MGW-A. When MSC-A server receives Handover Complete indication from MSC-B server it releases the A-interface line towards the BSC-A. Finally MSC-A server requests MGW-A to remove BSC-A side bearer termination. + +![Sequence diagram for Basic Inter-MSC GSM to UMTS Handover. Lifelines: BSC A, MSC-S A, MGW A, MSC-S B, MGW B, RNC B. The process involves a handover request from BSC A to MSC-S A, followed by MAP signaling and bearer preparation between MSC-S A, MGW A, MSC-S B, and MGW B. RNC B prepares the bearer and responds. MSC-S A then sends a handover command to BSC A.](de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg) + +``` + +sequenceDiagram + participant BSC A + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant RNC B + + Note over BSC A, MSC-S A: A Handover Required + BSC A->>MSC-S A: + MSC-S A->>MSC-S B: MAP Prepare Handover Req. + Note right of MSC-S B: 1 + MSC-S B->>MGW B: Context($) ADD.request (T4) + Note right of MSC-S B: 2 + MGW B->>MSC-S B: Context(C2) ADD.reply (T4) + Note right of MGW B: Prepare Bearer + MSC-S B->>RNC B: Iu Relocation Request + Note over RNC B: Bearer Establishment + RNC B->>MSC-S B: Iu Relocation Request-Ack + MSC-S B->>MSC-S A: MAP Prepare Handover Resp. + Note right of MSC-S A: 3 + MSC-S A->>MGW A: Context(C1) TopDescr({*, $, isolate}, {T2,$,oneway})+ADD.request($) + Note right of MGW A: Prepare Bearer, Change Flow Direction + MGW A->>MSC-S A: Context(C1) TopDescr()+ADD.reply (T3) + Note over MGW A, MGW B: Call and Bearer Establishment + MSC-S A->>BSC A: A Handover Command + +``` + +Sequence diagram for Basic Inter-MSC GSM to UMTS Handover. Lifelines: BSC A, MSC-S A, MGW A, MSC-S B, MGW B, RNC B. The process involves a handover request from BSC A to MSC-S A, followed by MAP signaling and bearer preparation between MSC-S A, MGW A, MSC-S B, and MGW B. RNC B prepares the bearer and responds. MSC-S A then sends a handover command to BSC A. + +**Figure 8.16/1: Basic Inter-MSC GSM to UMTS Handover (message sequence chart)** + +![Sequence diagram for Basic Inter-MSI GSM to UMTS Handover. Lifelines: BSC A, MSC-S A, MGW A, MSC-S B, MGW B, RNC B. The sequence starts with 'Relocation execution triggered in target RNC' in RNC B. RNC B sends 'Iu Relocation Detect' to MSC-S B. MSC-S B sends 'MAP Process Access Signalling Req.' to MSC-S A. MSC-S A sends 'Context(C1)' and 'TopDescr({T2,T1, oneway}, {T2,T3,bothway})' to MGW A (labeled with circled 4). MGW A responds with 'Change Flow Direction'. MSC-S A sends 'Context(C1)' and 'TopDescr()' to MGW A. MGW A sends 'Iu Relocation Complete' to MSC-S B. MSC-S B sends 'MAP Send End Signal Req.' to MSC-S A. MSC-S A sends 'Answer' to MSC-S B. MSC-S A sends 'A Clear Command' to BSC A (labeled with circled 5). BSC A sends 'A Clear Complete' to MSC-S A. MSC-S A sends 'Context(C1)' and 'SUB.request (T1)' to MGW A. MGW A responds with 'Context(C1)' and 'SUB.reply (T1) Release Termination'.](e16bfa31d748f4d99ec4ae3d16656926_img.jpg) + +Sequence diagram for Basic Inter-MSI GSM to UMTS Handover. Lifelines: BSC A, MSC-S A, MGW A, MSC-S B, MGW B, RNC B. The sequence starts with 'Relocation execution triggered in target RNC' in RNC B. RNC B sends 'Iu Relocation Detect' to MSC-S B. MSC-S B sends 'MAP Process Access Signalling Req.' to MSC-S A. MSC-S A sends 'Context(C1)' and 'TopDescr({T2,T1, oneway}, {T2,T3,bothway})' to MGW A (labeled with circled 4). MGW A responds with 'Change Flow Direction'. MSC-S A sends 'Context(C1)' and 'TopDescr()' to MGW A. MGW A sends 'Iu Relocation Complete' to MSC-S B. MSC-S B sends 'MAP Send End Signal Req.' to MSC-S A. MSC-S A sends 'Answer' to MSC-S B. MSC-S A sends 'A Clear Command' to BSC A (labeled with circled 5). BSC A sends 'A Clear Complete' to MSC-S A. MSC-S A sends 'Context(C1)' and 'SUB.request (T1)' to MGW A. MGW A responds with 'Context(C1)' and 'SUB.reply (T1) Release Termination'. + +Figure 8.16/2: Basic Inter-MSI GSM to UMTS Handover (message sequence chart) + +### 8.3.3 Subsequent Inter-MSI GSM to UMTS Handover back to the Anchor MSC + +The following handling shall be applied for a call that started as UMTS call. The procedures specified in 3GPP TS 23.009 [8] for "Subsequent Inter-MSI GSM to UMTS Handover back to the Anchor MSC" shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +#### 8.3.3.1 MSC-A + +##### 8.3.3.1.1 Handover Request + +When the MSC-A server receives a MAP Prepare Subsequent Handover request containing a Handover Request message, it requests the MGW-A to provide a binding reference and a bearer address using the Prepare Bearer procedure. For speech calls, the MSC-A server shall provide the MGW-A with the speech coding information for the bearer. For non-speech calls the MSC-A server shall provide MGW-A with the same PLMN Bearer Capability [4] as was provided at the last channel assignment. The MSC-A server uses the Change Flow Direction Procedure to request + +the MGW-A to set the Handover Device to initial state. The MSC-A server sends the Relocation Request message to the RNC-B containing the bearer address and binding reference (bullet 1 in figure 8.18/1). + +For Handover towards GERAN Iu-mode, the MSC-A Server shall select a service according to the Channel Type received with the Handover Request message and the capabilities of the GERAN target cell, if the GERAN classmark was received. For speech calls, the MSC-A server shall additionally take into account the selected codec and the currently used codec received with MAP Prepare Subsequent Handover request, and the list of supported codecs. + +The MSC-A server shall indicate to the GERAN the selected service within the RANAP RELOCATION REQUEST message and shall set the RAB parameters within the RANAP RELOCATION REQUEST message according to the selected service. The MSC server shall not set codec information in the NAS Synchronisation Indicator (see [4]). Instead it shall set codec information in the GERAN BSC container. + +#### 8.3.3.1.2 Handover Command/Relocation Detect + +When the MSC-A server sends the MAP Prepare Subsequent Handover response message or alternatively if it receives a Relocation Detect message, the MSC-A server uses the Change Flow Direction procedure to requests the MGW-A to set the Handover Device to intermediate state (bullet 2 in figure 8.18/2). + +#### 8.3.3.1.3 Relocation Complete + +When the MSC-A server receives a Relocation Complete message, it informs the MSC-B server about reception of this message. MSC-A server then initiates call clearing towards the MSC-B server as described in clause 7.3. + +#### 8.3.3.1.4 Interworking function + +The interworking function used by MGW-A before handover will also be used after handover. + +#### 8.3.3.1.5 Codec handling + +The MGW may include a speech transcoder based upon the speech coding information provided to each bearer termination. + +#### 8.3.3.1.6 Voice Processing function + +Voice processing function(s) provided by MGW-A and MGW-B before handover, may be continued or modified by MGW-A after handover. + +#### 8.3.3.1.7 Failure Handling in MSC server + +When a procedure between the MSC-A server and the MGW fails the MSC-A server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If MGW resources have been already seized at the target access side then the resources shall be released using the Release Termination procedure. If the call is to be cleared, then it shall be handled as described in clause 7.3. + +### 8.3.3.2 MSC-B / MGW-B + +#### 8.3.3.2.1 Handover Required + +For Handover towards GERAN Iu mode the GERAN capabilities of the target cell will be indicated to the MSC-B server within the Handover Required message if the target cell provides different capabilities than the current cell. If no information about the GERAN capabilities of the target cell are received within this message, the MSC-B server shall assume that the GERAN target cell will provide the same capabilities as the current cell (for details see [29]). + +The MSC-B server shall indicate to the MSC-A server the GERAN capabilities of the target cell, if available, with the MAP Prepare Subsequent Handover request. For speech calls, the MSC-B server shall additionally indicate to the MSC-A server the selected codec and the currently used codec. + +#### 8.3.3.2.2 Handover Complete + +When the MSC-B server receives the Handover Complete message, it releases the A-interface line towards the BSC-A and requests the MGW-B to remove the bearer termination towards the BSC-A using the Release Termination procedure (bullet 3 in figure 8.18/2). + +### 8.3.3.2.3 Release of bearer towards MGW-A + +When the MSC-B server receives a call clearing indication from the MSC-A server, the MSC-B server handles it as described in subclause 7.2. + +### 8.3.3.2.4 Example + +Figure 8.17 shows the network model for Subsequent Inter-MSC GSM to UMTS Handover back to the Anchor MSC. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling (not applicable in case of GSM access) and the bearer. In the MGW the bearer termination T1 is used for the bearer towards RNC-B, the bearer termination T3 is used for the bearer towards MSC-A server, and the bearer termination T2 is used for the bearer towards the succeeding/preceding MGW. In MGW-B the bearer termination T4 is used for the bearer towards BSC-A, bearer termination T5 is used for the bearer towards MGW-A. + +![Figure 8.17: Network model for Subsequent Inter-MSC GSM to UMTS Handover back to the Anchor MSC. The diagram is divided into three sections: 'Before Handover', 'During Handover', and 'After Handover'. In 'Before Handover', MSC-S B is connected to BSC A (squared line) and MGW B (dotted line). MGW B is connected to MGW A (dotted line). MSC-S A is connected to MGW A (squared line). In 'During Handover', MSC-S A is connected to RNC B (squared line) and MGW A (dotted line). MSC-S B is connected to BSC A (squared line) and MGW B (dotted line). MGW B is connected to MGW A (dotted line). In 'After Handover', MSC-S A is connected to RNC B (squared line) and MGW A (dotted line). MGW A is connected to BSC A (dotted line).](3922e505954d53f8864a44dc9ea664c6_img.jpg) + +**Before Handover** + +The diagram shows MSC-S B connected to BSC A via a squared line (call control signalling) and to MGW B via a dotted line (bearer control signalling). MGW B is connected to MGW A via a dotted line. MSC-S A is connected to MGW A via a squared line. + +**During Handover** + +The diagram shows MSC-S A connected to RNC B via a squared line and to MGW A via a dotted line. MSC-S B is connected to BSC A via a squared line and to MGW B via a dotted line. MGW B is connected to MGW A via a dotted line. + +**After Handover** + +The diagram shows MSC-S A connected to RNC B via a squared line and to MGW A via a dotted line. MGW A is connected to BSC A via a dotted line. + +Figure 8.17: Network model for Subsequent Inter-MSC GSM to UMTS Handover back to the Anchor MSC. The diagram is divided into three sections: 'Before Handover', 'During Handover', and 'After Handover'. In 'Before Handover', MSC-S B is connected to BSC A (squared line) and MGW B (dotted line). MGW B is connected to MGW A (dotted line). MSC-S A is connected to MGW A (squared line). In 'During Handover', MSC-S A is connected to RNC B (squared line) and MGW A (dotted line). MSC-S B is connected to BSC A (squared line) and MGW B (dotted line). MGW B is connected to MGW A (dotted line). In 'After Handover', MSC-S A is connected to RNC B (squared line) and MGW A (dotted line). MGW A is connected to BSC A (dotted line). + +**Figure 8.17: Subsequent Inter-MSC GSM to UMTS Handover back to the Anchor MSC (network model)** + +Figure 8.18 shows the message sequence example for the Subsequent Inter-MSC GSM to UMTS Handover back to the Anchor MSC. It is assumed that the Handover Device is located in the MGW (MGW-A) selected for the call establishment by the MSC server (MSC-A server) which controls the call and the mobility management. + +In the example the MSC-A server requests MGW-A to seize RNC-B side bearer termination with specific flow directions. When the relocation is detected in RNC-B the MSC-A server requests to change the flow directions between the terminations within the context in MGW-A. When MSC-A server receives Handover Complete indication from RNC-B it transfers this indication to MSC-B server. MSC-B server releases the A-interface line towards the BSC-A. MSC-A server initiates call clearing towards MSC-B server. + +![Sequence diagram for Subsequent Inter-MSC GSM to UMTS Handover back to the Anchor MSC. Lifelines: RNC B, MSC-S A, MGW A, MSC-S B, MGW B, BSC A. The sequence starts with 'A Handover Required' from BSC A to MGW B. Then 'MAP Prepare Subsequent Handover Req.' from MSC-S B to MSC-S A. MSC-S A sends 'Context(C1)' and 'TopDescr({*, $, isolate}, {T2, $, oneway})+ADD.request($)' to MGW A (marked with a circled '1'). MGW A responds with 'TopDescr()+ADD.reply (T6)'. MSC-S A then sends 'Context(C1)' and 'Iu Relocation Request' to RNC B. A green box labeled 'Bearer Establishment' spans between RNC B and MGW A. Finally, 'Iu Relocation Request-Ack' is sent from RNC B to MSC-S A.](6d67eee81b97a14e06a6fe57a95aff36_img.jpg) + +``` + +sequenceDiagram + participant RNC B + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant BSC A + + Note right of BSC A: A Handover Required + BSC A->>MGW B: A Handover Required + MSC-S B->>MSC-S A: MAP Prepare Subsequent Handover Req. + MSC-S A->>MGW A: Context(C1) + Note right of MSC-S A: 1 + MSC-S A->>MGW A: TopDescr({*, $, isolate}, {T2, $, oneway})+ADD.request($) + MGW A->>MSC-S A: TopDescr()+ADD.reply (T6) + Note right of MGW A: Prepare bearer, Change Flow Direction + MSC-S A->>RNC B: Context(C1) + MSC-S A->>RNC B: Iu Relocation Request + Note over RNC B, MGW A: Bearer Establishment + RNC B->>MSC-S A: Iu Relocation Request-Ack + +``` + +Sequence diagram for Subsequent Inter-MSC GSM to UMTS Handover back to the Anchor MSC. Lifelines: RNC B, MSC-S A, MGW A, MSC-S B, MGW B, BSC A. The sequence starts with 'A Handover Required' from BSC A to MGW B. Then 'MAP Prepare Subsequent Handover Req.' from MSC-S B to MSC-S A. MSC-S A sends 'Context(C1)' and 'TopDescr({\*, \$, isolate}, {T2, \$, oneway})+ADD.request(\$)' to MGW A (marked with a circled '1'). MGW A responds with 'TopDescr()+ADD.reply (T6)'. MSC-S A then sends 'Context(C1)' and 'Iu Relocation Request' to RNC B. A green box labeled 'Bearer Establishment' spans between RNC B and MGW A. Finally, 'Iu Relocation Request-Ack' is sent from RNC B to MSC-S A. + +**Figure 8.18/1: Subsequent Inter-MSC GSM to UMTS Handover back to the Anchor MSC (message sequence chart)** + +![Sequence diagram for Subsequent Inter-MSC GSM to UMTS Handover back to the Anchor MSC. Lifelines: RNC B, MSC-S A, MGW A, MSC-S B, MGW B, BSC A. The process involves preparation, execution, and clearing phases.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +``` + +sequenceDiagram + participant RNC B + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant BSC A + + Note left of RNC B: Relocation execution triggered in target RNC + + MSC-S A->>MSC-S B: MAP Prepare Subsequent HandoverResp. + MSC-S B->>BSC A: A Handover Command + Note left of RNC B: Relocation execution triggered in target RNC + RNC B->>MSC-S A: Iu Relocation Detect + MSC-S A->>MGW A: Context(C1) TopDescr({T2,T3,oneway}, {T2,T6,bothway}) + Note right of MGW A: Change Flow Direction + Note right of MSC-S A: 2 + MGW A->>MSC-S A: Context(C1) TopDescr() + RNC B->>MSC-S A: Iu Relocation Complete + MSC-S A->>MSC-S B: MAP Send End Signal Resp + Note right of MSC-S B: 3 + MSC-S B->>BSC A: A Clear Command + BSC A->>MSC-S B: A Clear Complete + Note right of MGW A: Context(C2) + MSC-S B->>MGW B: SUB.request (T4) + Note right of MGW A: Context(C2) + MGW B->>MSC-S B: SUB.reply (T4) + Note right of MGW B: Call Clearing and Bearer Release + +``` + +Sequence diagram for Subsequent Inter-MSC GSM to UMTS Handover back to the Anchor MSC. Lifelines: RNC B, MSC-S A, MGW A, MSC-S B, MGW B, BSC A. The process involves preparation, execution, and clearing phases. + +**Figure 8.18/2: Subsequent Inter-MSC GSM to UMTS Handover back to the Anchor MSC (message sequence chart)** + +### 8.3.4 Subsequent Inter-MSC GSM to UMTS Handover to a third MSC + +The GSM to UMTS handover to a third MSC server (from MSC-B server to MSC-B server) is the combination of the two previous inter-MSC handover cases: + +- for MSC-B server a subsequent GSM to UMTS handover from MSC-B server back to MSC-A server as described in clause 8.3.3; and +- for MSC-B server a basic GSM to UMTS handover from MSC-A server to MSC-B server as described in clause 8.3.2. + +MSC-A server implements the corresponding parts of each handover case; i.e. access handling in MSC-A server is not included. + +### 8.3.5 GSM to UMTS Handover with Iu on IP + +If IuCS on IP is supported by the MSC server, the Core Network side procedures described in clauses 8.3.1, 8.3.2, 8.3.3, 8.3.4 shall apply. For the access bearer termination, the exchange of IP addresses via call control procedures is described in this clause. + +Before the MSC server starts the access bearer assignment, the MSC server requests the MGW to prepare for the access bearer using the *Prepare\_IP\_Transport* procedure. The MSC server requests the MGW to provide an IP Transport address and UDP Port and provides the MGW with the bearer characteristics. For speech calls, the MSC server shall provide the MGW with the speech coding information and conditionally GTT related information in accordance with 3GPP TS 23.226 [28] for the bearer. For a non-speech call the MSC server also provides the MGW with a PLMN Bearer Capability [4]. After the MGW has replied with the IP address and UDP Port the MSC server requests access bearer assignment using the provided IP address and UDP Port in accordance with 3GPP TS 25.413 [26]. The IP addresses and UDP Ports of the MGW and the RNC are exchanged via the RANAP procedures. If the bearer transport is IP and IuUP mode is Transparent, when the MSC receives the RANAP Iu Relocation Request response, it shall send the RNC IP address and UDP Port to the MGW Access bearer termination using the *Modify\_IP\_Transport\_Address* procedure. + +If the bearer transport is IP and IuUP mode is Support, the MGW shall use the source IP address and UDP Port of the IuUP Init packet received from the radio access network as the destination address for subsequent downlink packets. + +The sequence is shown in figure 8.3.5/1. + +![Sequence diagram for GSM to UMTS Handover with Iu on IP. The diagram shows the interaction between BSC A, MSC-S, MGW, and RNC B. It starts with 'A Handover Required' from BSC A to MSC-S. A note indicates preceding signaling for core network bearer establishment. The sequence includes Context(C1) ADD.request ($), Context(C1) ADD.reply(T3), Iu Relocation Request, IuUP Init/Init Ack (support mode), Iu Relocation Request-Ack, Context(C1) MODIFY.request (T3), Context(C1) Mod.reply (T3) (transparent mode), A Handover Command, Relocation execution triggered in target RNC, and Iu Relocation Detect.](0b998e3ad8f9d104768642612605cb35_img.jpg) + +Sequence diagram illustrating the GSM to UMTS Handover with Iu on IP. The diagram shows the interaction between BSC A, MSC-S, MGW, and RNC B. + +For preceding signalling sequences for establishing core network bearer see Figures 8.14, 8.16/1 or 8.18/1 + +The sequence of messages is as follows: + +- BSC A sends "A Handover Required" to MSC-S. +- MSC-S sends "Context(C1) ADD.request (\$)" to MGW. (Note: Prepare IP bearer) +- MGW sends "Context(C1) ADD.reply(T3)" to MSC-S. +- MSC-S sends "Iu Relocation Request" to RNC B. +- RNC B sends "IuUP Init" to MGW and "IuUP Init Ack" to RNC B. (Note: If IuUP in support mode) +- MSC-S sends "Iu Relocation Request-Ack" to RNC B. +- MSC-S sends "Context(C1) MODIFY.request (T3)" to MGW. (Note: Modify IP address) +- MGW sends "Context(C1) Mod.reply (T3)" to MSC-S. (Note: If IuUP in Transparent Mode) +- MSC-S sends "A Handover Command" to BSC A. +- RNC B sends a message to a green box labeled "Relocation execution triggered in target RNC". +- RNC B sends "Iu Relocation Detect" to MSC-S. + +Sequence diagram for GSM to UMTS Handover with Iu on IP. The diagram shows the interaction between BSC A, MSC-S, MGW, and RNC B. It starts with 'A Handover Required' from BSC A to MSC-S. A note indicates preceding signaling for core network bearer establishment. The sequence includes Context(C1) ADD.request (\$), Context(C1) ADD.reply(T3), Iu Relocation Request, IuUP Init/Init Ack (support mode), Iu Relocation Request-Ack, Context(C1) MODIFY.request (T3), Context(C1) Mod.reply (T3) (transparent mode), A Handover Command, Relocation execution triggered in target RNC, and Iu Relocation Detect. + +Figure 8.3.5/1 GSM to UMTS Handover with Iu on IP + +## 8.4 GSM to GSM + +### 8.4.1 Intra-MSC Inter-BSS GSM to GSM Handover + +The procedures specified in 3GPP TS 23.009 [8] for "Intra-MSC Handover" shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +#### 8.4.1.1 Handover Required + +When the MSC server receives a Handover Required message, it requests the MGW to seize a TDM circuit, using the Reserve Circuit procedure. For non-speech calls the MSC server shall provide the MGW with the GSM Channel coding properties and the same PLMN Bearer Capability [4] as was provided at the last access bearer assignment. The MSC server uses the Change Flow Direction procedure to request the MGW to set the Handover Device to initial state. The MSC server sends the Handover Request message to the BSC-B containing the CIC (bullet 1 in figure 8.20/1). + +#### 8.4.1.2 Handover Request Acknowledge + +For non-speech calls after receiving Handover Request Acknowledge message if the assigned GSM Channel coding properties differ from the previously provided ones the MSC server provides the MGW-A with the assigned GSM Channel coding properties using the Modify Bearer Characteristics procedure (bullet 2 in figure 8.20/1). + +#### 8.4.1.3 Handover Command/Handover Detect + +When the MSC server sends the Handover Command message or alternatively if it receives the Handover Detect message, the MSC server uses the Change Flow Direction procedure to requests the MGW to set the Handover Device to intermediate state (bullet 3 in figure 8.20/1). + +#### 8.4.1.4 Handover Complete + +When the MSC server receives the Handover Complete message, it releases the A-interface line towards BSC-A. The MSC server also requests the MGW to set the Handover Device to its final state by removing the bearer termination towards the BSC-A, using the Release Termination procedure (bullet 4 in figure 8.20/2). + +#### 8.4.1.5 Interworking function + +The interworking function used by the MGW before handover will also be used after handover. + +#### 8.4.1.6 Voice Processing function + +After handover, the MGW may continue or modify voice processing function(s) provided to each bearer termination. + +#### 8.4.1.7 Failure Handling in MSC server + +When a procedure between the MSC server and the MGW fails the MSC server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If MGW resources have already been seized at the target access side then the resources shall be released using the Release Termination procedure. If the call is to be cleared, then it shall be handled as described in clause 7.3. + +### 8.4.1.8 Example + +Figure 8.19 shows the network model for the Intra-MSC GSM to GSM Handover. The "squared" line represents the call control signalling. The "dotted" line represents the bearer. The bearer termination T1 is used for the bearer towards BSC-A, bearer termination T3 is used for the bearer towards BSC-B and the bearer termination T2 is used for the bearer towards the succeeding/preceding MGW. + +![Figure 8.19: Intra-MSC GSM to GSM Handover (network model). The diagram illustrates three stages of a handover: 'Before Handover', 'During Handover', and 'After Handover'. In all stages, an MSC-S is connected to a CTXI MGW via a solid blue line (call control signalling). The CTXI MGW has three bearer terminations: T1, T2, and T3. In the 'Before Handover' stage, a dotted green line (bearer) connects the MSC-S to BSC A, which is connected to the CTXI MGW via termination T1. In the 'During Handover' stage, the dotted green line is rerouted from the MSC-S to BSC B, which is connected to the CTXI MGW via termination T3. In the 'After Handover' stage, the dotted green line connects the MSC-S to BSC B via termination T3. The CTXI MGW also has termination T2 connected to another MGW (indicated by a dotted red line).](b4c825454b7a89b4d7744e4f45521174_img.jpg) + +Figure 8.19: Intra-MSC GSM to GSM Handover (network model). The diagram illustrates three stages of a handover: 'Before Handover', 'During Handover', and 'After Handover'. In all stages, an MSC-S is connected to a CTXI MGW via a solid blue line (call control signalling). The CTXI MGW has three bearer terminations: T1, T2, and T3. In the 'Before Handover' stage, a dotted green line (bearer) connects the MSC-S to BSC A, which is connected to the CTXI MGW via termination T1. In the 'During Handover' stage, the dotted green line is rerouted from the MSC-S to BSC B, which is connected to the CTXI MGW via termination T3. In the 'After Handover' stage, the dotted green line connects the MSC-S to BSC B via termination T3. The CTXI MGW also has termination T2 connected to another MGW (indicated by a dotted red line). + +**Figure 8.19: Intra-MSC GSM to GSM Handover (network model)** + +Figure 8.20 shows the message sequence example for the Intra-MSC GSM to GSM Handover. It is assumed that the Handover Device is located in the MGW selected for the call establishment by the MSC server, which controls the call and the mobility management. + +In the example the MSC server requests seizure of BSC-B side bearer termination with specific flow directions. The MSC server starts handover execution by sending Handover Request towards BSC-B. When the handover is detected in + +BSC-B the MSC server requests to change the flow directions between the terminations within the context. When MSC server receives Handover Complete indication from BSC-B it releases the A-interface line towards the BSC-A. Finally the MSC server requests the MGW to release BSC-A side bearer termination. + +![Sequence diagram for Intra-MSC GSM to GSM Handover. Lifelines: BSC A, MSC-S, MGW, BSC B. The process involves: 1. BSC A sends 'A Handover Required' to MSC-S. MSC-S sends 'TopDescr({*,T3, isolate}, {T2,T3, oneway})+ADD.request (T3)' to MGW. MGW responds with 'Reserve Circuit, Change Flow Direction' and 'TopDescr()+ADD.reply (T3)'. MSC-S sends 'A Handover Request' to BSC B, which responds with 'A Handover Request-Ack'. 2. MSC-S sends 'MOD.request (T3)' to MGW. MGW responds with 'Modify Bearer Characteristics (when applicable)' and 'MOD.reply (T3)'. 3. MSC-S sends 'A Handover Command' to BSC A. BSC B sends 'Handover detected in target BSC' (highlighted in green) to MSC-S. MSC-S sends 'A Handover Detect' to MGW. MGW responds with 'TopDescr({T2,T1, oneway}, {T2,T3, bothway})' and 'Change Flow Direction'. MSC-S sends 'TopDescr()' to MGW and 'A Handover Complete' to BSC B.](b30e390cb591b39482fe7ecd4c4cd84b_img.jpg) + +``` + +sequenceDiagram + participant BSC A + participant MSC-S + participant MGW + participant BSC B + + Note left of BSC A: Context(C1) + BSC A->>MSC-S: A Handover Required + Note right of MSC-S: 1 + MSC-S->>MGW: TopDescr({*,T3, isolate}, {T2,T3, oneway})+ADD.request (T3) + MGW-->>MSC-S: Reserve Circuit, Change Flow Direction + MGW-->>MSC-S: TopDescr()+ADD.reply (T3) + MSC-S->>BSC B: A Handover Request + BSC B-->>MSC-S: A Handover Request-Ack + + Note left of BSC A: Context(C1) + Note right of MSC-S: 2 + MSC-S->>MGW: MOD.request (T3) + MGW-->>MSC-S: Modify Bearer Characteristics (when applicable) + MGW-->>MSC-S: MOD.reply (T3) + + Note left of BSC A: Context(C1) + MSC-S->>BSC A: A Handover Command + + Note right of BSC B: Handover detected in target BSC + BSC B->>MSC-S: A Handover Detect + Note left of BSC A: Context(C1) + Note right of MSC-S: 3 + MSC-S->>MGW: TopDescr({T2,T1, oneway}, {T2,T3, bothway}) + MGW-->>MSC-S: Change Flow Direction + MSC-S->>MGW: TopDescr() + MSC-S->>BSC B: A Handover Complete + +``` + +Sequence diagram for Intra-MSC GSM to GSM Handover. Lifelines: BSC A, MSC-S, MGW, BSC B. The process involves: 1. BSC A sends 'A Handover Required' to MSC-S. MSC-S sends 'TopDescr({\*,T3, isolate}, {T2,T3, oneway})+ADD.request (T3)' to MGW. MGW responds with 'Reserve Circuit, Change Flow Direction' and 'TopDescr()+ADD.reply (T3)'. MSC-S sends 'A Handover Request' to BSC B, which responds with 'A Handover Request-Ack'. 2. MSC-S sends 'MOD.request (T3)' to MGW. MGW responds with 'Modify Bearer Characteristics (when applicable)' and 'MOD.reply (T3)'. 3. MSC-S sends 'A Handover Command' to BSC A. BSC B sends 'Handover detected in target BSC' (highlighted in green) to MSC-S. MSC-S sends 'A Handover Detect' to MGW. MGW responds with 'TopDescr({T2,T1, oneway}, {T2,T3, bothway})' and 'Change Flow Direction'. MSC-S sends 'TopDescr()' to MGW and 'A Handover Complete' to BSC B. + +Figure 8.20/1: Intra-MSC GSM to GSM Handover (message sequence chart) + +![Sequence diagram for Intra-MSC GSM to GSM Handover. Lifelines: BSC A, MSC-S, MGW, BSC B. The sequence shows: 1. MSC-S sends 'A Clear Command' to BSC A. 2. BSC A sends 'A Clear Complete' to MSC-S. 3. MSC-S sends 'Context(C1)' to BSC A. 4. MSC-S sends 'SUB.request (T1)' to MGW (marked with a circled 4). 5. MGW sends 'Release Termination' to BSC B. 6. MGW sends 'SUB.reply (T1)' to MSC-S. 7. MSC-S sends 'Context(C1)' to BSC A.](a7450c80e88ad3f6ca1427ad84020998_img.jpg) + +``` + +sequenceDiagram + participant BSC A + participant MSC-S + participant MGW + participant BSC B + MSC-S->>BSC A: A Clear Command + BSC A->>MSC-S: A Clear Complete + MSC-S->>BSC A: Context(C1) + Note over MSC-S, MGW: 4 + MSC-S->>MGW: SUB.request (T1) + MGW->>BSC B: Release Termination + MGW->>MSC-S: SUB.reply (T1) + MSC-S->>BSC A: Context(C1) + +``` + +Sequence diagram for Intra-MSC GSM to GSM Handover. Lifelines: BSC A, MSC-S, MGW, BSC B. The sequence shows: 1. MSC-S sends 'A Clear Command' to BSC A. 2. BSC A sends 'A Clear Complete' to MSC-S. 3. MSC-S sends 'Context(C1)' to BSC A. 4. MSC-S sends 'SUB.request (T1)' to MGW (marked with a circled 4). 5. MGW sends 'Release Termination' to BSC B. 6. MGW sends 'SUB.reply (T1)' to MSC-S. 7. MSC-S sends 'Context(C1)' to BSC A. + +**Figure 8.20/2: Intra-MSC GSM to GSM Handover (message sequence chart)** + +### 8.4.1.9 Intra-MSC GSM to GSM Handover for A interface over IP + +When the MSC server receives the BSSAP Handover Required message, it requests the MGW to reserve an RTP bearer termination using the Reserve RTP Connection Point procedure. The MSC server requests the MGW to reserve an IP address and UDP port. The MSC server uses the Change Flow Direction procedure to request the MGW to set the Handover Device to initial state. + +The MGW reserves the RTP termination and indicates the IP address and UDP port number to the MSC server. The IP addresses and UDP ports of the MGW is sent to the BSC in the BSSMAP Handover Request message. When the MSC server receives the BSSMAP Handover Request-Ack message, it shall send the BSC IP address and UDP Port number to the MGW using the Configure RTP Connection Point procedure. + +The sequence is shown in Figure 8.4.1.9/1. + +![Sequence diagram for Intra-MSC GSM to GSM Handover for AoIP. Lifelines: BSC A, MSC-S, MGW, BSC B. The process involves: 1. BSC A sends 'A Handover Required' to MSC-S. MSC-S sends 'TopDescr({*,$,isolate},{T2,$,oneway})+ADD.request ($)' to MGW. MGW responds 'Reserve RTP Connection Point, Change Flow Direction' and 'TopDescr()+ADD.reply (T3)'. MSC-S sends 'A Handover Request' to BSC B, which responds 'A Handover Request-Ack'. 2. MSC-S sends 'MOD.request (T3)' to MGW. MGW responds 'Configure RTP Connection Point' and 'MOD.reply (T3)'. MSC-S sends 'A Handover Command' to BSC A. A box at the bottom indicates 'Flow Continues as in Figure 8.20/1-2'.](9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg) + +``` + +sequenceDiagram + participant BSC A + participant MSC-S + participant MGW + participant BSC B + + Note left of BSC A: Context(C1) + BSC A->>MSC-S: A Handover Required + Note left of MSC-S: Context(C1) + MSC-S->>MGW: TopDescr({*,$,isolate},{T2,$,oneway})+ADD.request ($) + Note right of MGW: Reserve RTP Connection Point, Change Flow Direction + MGW-->>MSC-S: TopDescr()+ADD.reply (T3) + Note left of MSC-S: Context(C1) + MSC-S->>BSC B: A Handover Request + BSC B-->>MSC-S: A Handover Request-Ack + Note left of MSC-S: Context(C1) + MSC-S->>MGW: MOD.request (T3) + Note right of MGW: Configure RTP Connection Point + MGW-->>MSC-S: MOD.reply (T3) + Note left of MSC-S: Context(C1) + MSC-S->>BSC A: A Handover Command + Note left of BSC A: Context(C1) + Note right of BSC B: Flow Continues as in Figure 8.20/1-2 + +``` + +Sequence diagram for Intra-MSC GSM to GSM Handover for AoIP. Lifelines: BSC A, MSC-S, MGW, BSC B. The process involves: 1. BSC A sends 'A Handover Required' to MSC-S. MSC-S sends 'TopDescr({\*,\$,isolate},{T2,\$,oneway})+ADD.request (\$)' to MGW. MGW responds 'Reserve RTP Connection Point, Change Flow Direction' and 'TopDescr()+ADD.reply (T3)'. MSC-S sends 'A Handover Request' to BSC B, which responds 'A Handover Request-Ack'. 2. MSC-S sends 'MOD.request (T3)' to MGW. MGW responds 'Configure RTP Connection Point' and 'MOD.reply (T3)'. MSC-S sends 'A Handover Command' to BSC A. A box at the bottom indicates 'Flow Continues as in Figure 8.20/1-2'. + +Figure 8.4.1.9/1: Intra-MSC GSM to GSM Handover for AoIP (message sequence chart) + +## 8.4.2 Basic Inter-MSC GSM to GSM Handover + +The procedures specified in 3GPP TS 23.009 [8] for "Basic Handover Procedure Requiring a Circuit Connection between MSC-A and MSC-B" shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +### 8.4.2.1 MSC-A / MGW-A + +#### 8.4.2.1.1 Bearer establishment between MGW-A and MGW-B + +The handling of the bearer establishment between MGW-A and MGW-B is as described for a Basic Mobile Originating Call, using either forward or backward bearer establishment. For non-speech calls the MSC-A server shall provide MGW-A with the GSM Channel coding properties and the same PLMN Bearer Capability [4] as was provided at the last access bearer assignment. The MSC-A server also uses the Change Flow Direction procedure to request MGW-A to set the Handover Device to initial state (bullet 3 in figure 8.22/2). + +#### 8.4.2.1.2 Handover Command/Handover Detect + +When the MSC-A server sends the Handover Command message or alternatively if it receives the Handover Detect message, the MSC-A server uses the Change Flow Direction procedure to requests MGW-A to set the Handover Device to intermediate state (bullet 4 in figure 8.22/2). + +#### 8.4.2.1.3 Handover Complete + +When the MSC-A server receives the Handover Complete message, it releases the A-interface line towards the BSC-A. The MSC-A server also requests MGW-A to set the Handover Device to its final state by removing the bearer termination towards the BSC-A, using the Release Termination procedure (bullet 5 in figure 8.22/2). + +#### 8.4.2.1.4 Interworking function + +The interworking function used by MGW-A before handover will also be used after handover. + +#### 8.4.2.1.5 Voice Processing function + +Voice processing function(s) provided by MGW-A before handover, may be modified or disabled by MGW-A after handover. + +#### 8.4.2.1.6 Failure Handling in MSC server + +When a procedure between the MSC-A server and MGW-A fails the MSC-A server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If call establishment towards the MSC-B server has already started then the call towards MSC-B server shall be cleared as described in clause 7.3. If the original call is to be cleared, then it shall be handled as described in clause 7.3. + +### 8.4.2.2 MSC-B / MGW-B + +#### 8.4.2.2.1 MGW selection + +The MSC-B server selects an MGW when it receives Prepare Handover Request message (bullet 1 in figure 8.22/1). + +#### 8.4.2.2.2 Bearer establishment towards BSC-B + +When the MSC-B server has selected MGW-B it requests MGW-B to seize a TDM circuit, using the Reserve Circuit procedure. The MSC-B server sends the Handover Request message to the BSC-B containing the CIC (bullet 2 in figure 8.22/1). + +#### 8.4.2.2.3 Bearer establishment between MGW-A and MGW-B + +The handling of the bearer establishment between MGW-A and MGW-B is as described for a Basic Mobile Terminating Call, using either forward or backward bearer establishment. + +#### 8.4.2.2.4 Voice Processing function + +Voice processing function(s) provided by MGW-A before handover, may be continued or modified by MGW-B after handover. + +#### 8.4.2.2.5 Failure Handling in MSC server + +When a procedure between the MSC-B server and MGW-B fails the MSC-B server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If MGW-B resources have already been seized at the target access side then the resources shall be released using the Release Termination procedure. The call from MSC-A server shall be released as described at clause 7.1. + +#### 8.4.2.2.6 Example + +Figure 8.21 shows the network model for the Basic Inter- MSC GSM to GSM. The "squared" line represents the call control signalling. The "dotted" line represents the bearer. In MGW-A the bearer termination T1 is used for the bearer towards BSC-A, bearer termination T3 is used for the bearer towards MGW-B, and the bearer termination T2 is used for the bearer towards the succeeding/preceding MGW. In MGW-B the bearer termination T4 is used for the bearer towards BSC-B, bearer termination T5 is used for the bearer towards MGW-A. + +![Figure 8.21: Basic Inter-MSC GSM to GSM Handover (network model). The diagram illustrates three stages of a handover: 'Before Handover', 'During Handover', and 'After Handover'. In 'Before Handover', a mobile station (MS) is connected to BSC A, which is connected to MGW A (CTX1). MGW A is connected to MSC-S A. In 'During Handover', the MS is shown moving from BSC A towards BSC B. MSC-S A is shown interacting with MSC-S B, which is connected to MGW B (CTX2). MGW B is connected to BSC B. In 'After Handover', the MS is connected to BSC B, which is connected to MGW B (CTX2). MGW B is connected to MSC-S B, which is connected to MSC-S A. MSC-S A is connected to MGW A (CTX1), which is connected to BSC A. The diagram uses solid lines for data paths and dashed lines for signaling paths.](6e9d059430baba0c363e33749f68b107_img.jpg) + +**Before Handover** + +**During Handover** + +**After Handover** + +Figure 8.21: Basic Inter-MSC GSM to GSM Handover (network model). The diagram illustrates three stages of a handover: 'Before Handover', 'During Handover', and 'After Handover'. In 'Before Handover', a mobile station (MS) is connected to BSC A, which is connected to MGW A (CTX1). MGW A is connected to MSC-S A. In 'During Handover', the MS is shown moving from BSC A towards BSC B. MSC-S A is shown interacting with MSC-S B, which is connected to MGW B (CTX2). MGW B is connected to BSC B. In 'After Handover', the MS is connected to BSC B, which is connected to MGW B (CTX2). MGW B is connected to MSC-S B, which is connected to MSC-S A. MSC-S A is connected to MGW A (CTX1), which is connected to BSC A. The diagram uses solid lines for data paths and dashed lines for signaling paths. + +**Figure 8.21: Basic Inter-MSC GSM to GSM Handover (network model)** + +Figure 8.22 shows the message sequence example for the Basic Inter-MSC GSM to GSM Handover. + +It is assumed that the Handover Device is located in the MGW (MGW-A) selected for the call establishment by the MSC server (MSC-A server) which controls the call and the mobility management. + +In the example the MSC-B server requests MGW-B to seize BSC-B side bearer termination. The call is established between MSC-A server and MSC-B server, and the bearer is established between MGW-A and MGW-B. When the handover is detected in BSC-B the MSC-A server requests to change the flow directions between the terminations within the context in MGW-A. When MSC-A server receives Relocation Complete indication from MSC-B server it releases the A-interface line towards the BSC-A. Finally MSC-A server requests MGW-A to remove BSC-A side bearer termination. + +![Sequence diagram for Basic Inter- MSC GSM to GSM Handover. Lifelines: BSC A, MSC-S A, MGW A, MSC-S B, MGW B, BSC B. The process involves a handover request from BSC A to MSC-S A, followed by MAP Prepare Handover Req. to MSC-S B (labeled 1). MSC-S B sends ADD.request (T4) to MGW B (labeled 2), which reserves a circuit and responds. MSC-S B then sends a handover request to BSC B, which responds. MSC-S A receives the response and sends TopDescr and ADD.request (T3) to MGW A (labeled 3). MGW A reserves a circuit, changes flow direction, and responds. Finally, a 'Call and Bearer Establishment' phase occurs.](eabcb2f8b9acedb194571d5bc734b463_img.jpg) + +``` + +sequenceDiagram + participant BSC A + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant BSC B + + Note left of BSC A: A Handover Required + BSC A->>MSC-S A: + MSC-S A->>MSC-S B: MAP Prepare Handover Req. + Note right of MSC-S B: 1 + MSC-S B->>MGW B: ADD.request (T4) + Note right of MGW B: Reserve Circuit + MGW B-->>MSC-S B: ADD.reply (T4) + Note left of MSC-S B: Context($) +Context(C2) + Note right of MSC-S B: 2 + MSC-S B->>BSC B: A Handover Request + BSC B-->>MSC-S B: A Handover Request-Ack + MSC-S B-->>MSC-S A: MAP Prepare Handover Resp. + Note left of MSC-S A: Context(C1) + Note right of MSC-S A: 3 + MSC-S A->>MGW A: TopDescr({*,T3, isolate}, {T2,T3,oneway})+ADD.request(T3) + Note right of MGW A: Reserve Circuit, +Change Flow Direction + MGW A-->>MSC-S A: TopDescr()+ADD.reply (T3) + Note left of MSC-S A: Context(C1) + Note right of MGW A: Call and Bearer Establishment + +``` + +Sequence diagram for Basic Inter- MSC GSM to GSM Handover. Lifelines: BSC A, MSC-S A, MGW A, MSC-S B, MGW B, BSC B. The process involves a handover request from BSC A to MSC-S A, followed by MAP Prepare Handover Req. to MSC-S B (labeled 1). MSC-S B sends ADD.request (T4) to MGW B (labeled 2), which reserves a circuit and responds. MSC-S B then sends a handover request to BSC B, which responds. MSC-S A receives the response and sends TopDescr and ADD.request (T3) to MGW A (labeled 3). MGW A reserves a circuit, changes flow direction, and responds. Finally, a 'Call and Bearer Establishment' phase occurs. + +Figure 8.22/1: Basic Inter- MSC GSM to GSM Handover (message sequence chart) + +![Sequence diagram for Basic Inter-MSC GSM to GSM Handover. Lifelines: BSC A, MSC-S A, MGW A, MSC-S B, MGW B, BSC B. The sequence starts with a Handover Command from MSC-S A to BSC A. A 'Handover detected in target BSC' event occurs at BSC B. BSC B sends a Handover Detect to MSC-S B. MSC-S B sends a MAP Process AccessSignalling Req. to MSC-S A. MSC-S A responds with Context(C1) and TopDescr messages. MSC-S B sends a Change Flow Direction to MGW A. MSC-S B sends a Handover Complete to MSC-S A. MSC-S A sends a MAP Send EndSignal Req. to MSC-S B, which responds with an Answer. MSC-S A sends a Clear Command to BSC A. BSC A responds with a Clear Complete. MSC-S A sends Context(C1) and SUB.request (T1) to MGW A. MGW A responds with Context(C1) and SUB.reply (T1) Release Termination.](2b00743506f6a3bbd17af764162dc76d_img.jpg) + +``` + +sequenceDiagram + participant BSC A + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant BSC B + + Note right of BSC B: Handover detected in target BSC + MSC-S A->>BSC A: A Handover Command + BSC B->>MSC-S B: A Handover Detect + MSC-S B->>MSC-S A: MAP Process AccessSignalling Req. + MSC-S A->>MSC-S B: Context(C1) + MSC-S A->>MGW A: TopDescr({T2,T1,oneway}, {T2,T3,bothway}) + Note right of MGW A: 4 Change Flow Direction + MSC-S A->>MGW A: Context(C1) TopDescr() + MSC-S B->>MSC-S A: A Handover Complete + MSC-S A->>MSC-S B: MAP Send EndSignal Req. + MSC-S B->>MSC-S A: Answer + MSC-S A->>BSC A: A Clear Command + Note right of BSC A: 5 + BSC A->>MSC-S A: A Clear Complete + MSC-S A->>MGW A: Context(C1) SUB.request (T1) + MGW A->>MSC-S A: Context(C1) SUB.reply (T1) Release Termination + +``` + +Sequence diagram for Basic Inter-MSC GSM to GSM Handover. Lifelines: BSC A, MSC-S A, MGW A, MSC-S B, MGW B, BSC B. The sequence starts with a Handover Command from MSC-S A to BSC A. A 'Handover detected in target BSC' event occurs at BSC B. BSC B sends a Handover Detect to MSC-S B. MSC-S B sends a MAP Process AccessSignalling Req. to MSC-S A. MSC-S A responds with Context(C1) and TopDescr messages. MSC-S B sends a Change Flow Direction to MGW A. MSC-S B sends a Handover Complete to MSC-S A. MSC-S A sends a MAP Send EndSignal Req. to MSC-S B, which responds with an Answer. MSC-S A sends a Clear Command to BSC A. BSC A responds with a Clear Complete. MSC-S A sends Context(C1) and SUB.request (T1) to MGW A. MGW A responds with Context(C1) and SUB.reply (T1) Release Termination. + +Figure 8.22/2: Basic Inter-MSC GSM to GSM Handover (message sequence chart) + +#### 8.4.2.3 Basic Inter-MSC GSM to GSM Handover for A Interface over IP + +If AoIP is supported by the MSC server, the Core Network side procedures described earlier in 8.4.2 shall apply. For the access side termination, the exchange of IP addresses via call control procedures is described in this clause. + +When the MSC-B server receives the MAP Prepare Handover Request., it requests the MGW-B to reserve an RTP bearer termination using the Reserve RTP Connection Point procedure. The MSC-B server requests the MGW-B to reserve an IP address and UDP port. + +The MGW-B reserves the RTP termination and indicates the IP address and UDP port number to the MSC-B server. The IP addresses and UDP ports of the MGW is sent to the BSC-B in the BSSMAP Handover Request message. When the MSC-B server receives the BSSMAP Handover Request-Ack message, it shall send the BSC-B IP address and UDP Port number to the MGW-B using the Configure RTP Connection Point procedure. + +The sequence is shown in Figure 8.4.2.3/1. + +![Sequence diagram for Basic Inter-MSC GSM to GSM Handover for AoIP. Lifelines: BSC A, MSC-S A, MGW A, MSC-S B, MGW B, BSC B. The process starts with 'A Handover Required' from BSC A to MSC-S A. MSC-S A sends 'MAP Prepare Handover Req.' to MSC-S B. MSC-S B sends 'ADD.request ($)' to MGW B, which responds with 'ADD.reply (T4)' and 'Reserve RTP Connection Point'. MSC-S B then sends 'A Handover Request' to BSC B, which responds with 'A Handover Request-Ack'. MSC-S B sends 'MOD.request (T4)' to MGW B, which responds with 'MOD.reply (T4)' and 'Configure RTP Connection Point'. MSC-S B sends 'MAP Prepare Handover Resp.' back to MSC-S A. A note indicates 'Flow Continues as in Figure 8.22/1-2'.](cc7baa8e5118f4b42c01166637c738ea_img.jpg) + +``` + +sequenceDiagram + participant BSC A + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant BSC B + + Note left of BSC A: A Handover Required + BSC A->>MSC-S A: A Handover Required + MSC-S A->>MSC-S B: MAP Prepare Handover Req. + Note right of MSC-S B: 1 + MSC-S B->>MGW B: ADD.request ($) + + Note right of MGW B: Reserve RTP Connection Point + MGW B-->>MSC-S B: ADD.reply (T4) + + Note left of MSC-S B: Context($) + + MSC-S B->>BSC B: A Handover Request + BSC B-->>MSC-S B: A Handover Request-Ack + Note left of MSC-S B: Context(C2) + Note right of MSC-S B: 2 + MSC-S B->>MGW B: MOD.request (T4) + + Note right of MGW B: Configure RTP Connection Point + MGW B-->>MSC-S B: MOD.reply (T4) + + Note left of MSC-S B: Context(C2) + + Note left of MSC-S B: Context(C2) + MSC-S B-->>MSC-S A: MAP Prepare Handover Resp. + Note right of BSC A: Flow Continues as in Figure 8.22/1-2 + +``` + +Sequence diagram for Basic Inter-MSC GSM to GSM Handover for AoIP. Lifelines: BSC A, MSC-S A, MGW A, MSC-S B, MGW B, BSC B. The process starts with 'A Handover Required' from BSC A to MSC-S A. MSC-S A sends 'MAP Prepare Handover Req.' to MSC-S B. MSC-S B sends 'ADD.request (\$)' to MGW B, which responds with 'ADD.reply (T4)' and 'Reserve RTP Connection Point'. MSC-S B then sends 'A Handover Request' to BSC B, which responds with 'A Handover Request-Ack'. MSC-S B sends 'MOD.request (T4)' to MGW B, which responds with 'MOD.reply (T4)' and 'Configure RTP Connection Point'. MSC-S B sends 'MAP Prepare Handover Resp.' back to MSC-S A. A note indicates 'Flow Continues as in Figure 8.22/1-2'. + +Figure 8.4.2.3/1: Basic Inter-MSC GSM to GSM Handover for AoIP (message sequence chart) + +## 8.4.3 Subsequent Inter-MSC GSM to GSM Handover back to the Anchor MSC + +The procedures specified in 3GPP TS 23.009 [8] for "Subsequent Handover from MSC-B to MSC-A requiring a Circuit Connection between 3G\_MSC-A and 3G\_MSC-B" shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +### 8.4.3.1 MSC-A / MGW-A + +When the MSC-A server receives a MAP Prepare Subsequent Handover request containing a Handover Request message, it requests MGW-A to seize a TDM circuit, using the Reserve Circuit procedure. For non-speech calls the MSC-A server shall provide MGW-A with the GSM Channel coding properties and the same PLMN Bearer Capability [4] as was provided at the first access bearer assignment. The MSC-A server uses the Change Flow Direction Procedure to request MGW-A to set the Handover Device to initial state. The MSC-A server sends the Handover Request message to the BSC-B containing the CIC (bullet 1 in figure 8.24/1). + +#### 8.4.3.1.1 Handover Request Acknowledge + +For non-speech calls after receiving Handover Request Acknowledge message if the assigned GSM Channel coding properties differ from the previously provided ones the MSC-A server provides the MGW-A with the assigned GSM Channel coding properties using the Modify Bearer Characteristics procedure (bullet 2 in figure 8.24/2). + +#### 8.4.3.1.2 Handover Command/Handover Detect + +When the MSC-A server sends the MAP Prepare Subsequent Handover response message or alternatively if it receives the Handover Detect message, the MSC-A server uses the Change Flow Direction procedure to request MGW-A to set the Handover Device to intermediate state (bullet 3 in figure 8.24/2). + +#### 8.4.3.1.3 Handover Complete + +When the MSC-A server receives the Handover Complete message, it informs the MSC-B server about reception of this message. The MSC-A server then initiates call clearing towards the MSC-B server as described in clause 7.3. + +#### 8.4.3.1.4 Interworking function + +The interworking function used by MGW-A before handover will also be used after handover. + +#### 8.4.3.1.5 Voice Processing function + +Voice processing function(s) provided by MGW-A and MGW-B before handover, may be continued or modified by MGW-A after handover. + +#### 8.4.3.1.6 Failure Handling in MSC server + +When a procedure between the MSC-A server and MGW-A fails the MSC-A server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If MGW-A resources have already been seized at the target access side then the resources shall be released using the Release Termination procedure. If the call is to be cleared, then it shall be handled as described in clause 7.3. + +### 8.4.3.2 MSC-B/MGW-B + +#### 8.4.3.2.1 Handover Complete + +When the MSC-B server receives the Handover Complete message, it releases the A-interface line towards the BSC-A and requests the MGW-B to remove the bearer termination towards the BSC-A using the Release Termination procedure (bullet 4 in figure 8.24/2). + +#### 8.4.3.2.2 Release of bearer towards MGW-A + +When the MSC-B server receives a call clearing indication from the MSC-A server, the MSC-B server handles it as described in clause 7.2. + +#### 8.4.3.2.3 Example + +Figure 8.24 shows the network model for the Subsequent Inter- MSC GSM to GSM Handover back to the Anchor MSC. The "squared" line represents the call control signalling. The "dotted" line represents the bearer. In MGW-A the bearer termination T6 is used for the bearer towards BSC-B, bearer termination T3 is used for the bearer towards MGW-B, and the bearer termination T2 is used for the bearer towards the succeeding/preceding MGW. In MGW-B the bearer termination T4 is used for the bearer towards BSC-A, bearer termination T5 is used for the bearer towards MGW-A. + +![Diagram of the network model before handover. It shows three main components: BSC A, MGW B, and MGW A. BSC A is connected to MGW B via a solid blue line (call control signalling) and a dotted red line (bearer). MGW B is connected to MGW A via a solid blue line (call control signalling) and a dotted red line (bearer). MGW A is connected to MSC-S A via a solid blue line (call control signalling) and a dotted red line (bearer). MSC-S A is connected to MSC-S B via a solid blue line (call control signalling) and a dotted red line (bearer). MSC-S B is connected to BSC A via a solid blue line (call control signalling) and a dotted red line (bearer). The diagram is labeled 'Before Handover'.](c24b21874de17e073506dd8797e4e45a_img.jpg) + +Diagram of the network model before handover. It shows three main components: BSC A, MGW B, and MGW A. BSC A is connected to MGW B via a solid blue line (call control signalling) and a dotted red line (bearer). MGW B is connected to MGW A via a solid blue line (call control signalling) and a dotted red line (bearer). MGW A is connected to MSC-S A via a solid blue line (call control signalling) and a dotted red line (bearer). MSC-S A is connected to MSC-S B via a solid blue line (call control signalling) and a dotted red line (bearer). MSC-S B is connected to BSC A via a solid blue line (call control signalling) and a dotted red line (bearer). The diagram is labeled 'Before Handover'. + +Before Handover + +![Diagram illustrating the network model during a handover. It shows four main components: BSC B (top left), MSC-S A (top right), MSC-S B (middle left), and a combined box containing CTXI MGW A (middle right) and CTX2 MGW B (bottom middle). BSC B is connected to MSC-S B via a green dashed line. MSC-S B is connected to CTX2 MGW B via a solid blue line. CTX2 MGW B is connected to CTXI MGW A via a solid blue line. CTXI MGW A is connected to MSC-S A via a solid blue line. There are also red dotted lines connecting BSC B to CTX2 MGW B and CTXI MGW A to MSC-S A.](9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg) + +Diagram illustrating the network model during a handover. It shows four main components: BSC B (top left), MSC-S A (top right), MSC-S B (middle left), and a combined box containing CTXI MGW A (middle right) and CTX2 MGW B (bottom middle). BSC B is connected to MSC-S B via a green dashed line. MSC-S B is connected to CTX2 MGW B via a solid blue line. CTX2 MGW B is connected to CTXI MGW A via a solid blue line. CTXI MGW A is connected to MSC-S A via a solid blue line. There are also red dotted lines connecting BSC B to CTX2 MGW B and CTXI MGW A to MSC-S A. + +During Handover + +![Diagram illustrating the network model after the handover. It shows three main components: BSC B (bottom left), MSC-S A (top right), and a combined box containing CTXI MGW A (bottom middle). BSC B is now connected directly to MSC-S A via a green dashed line. CTXI MGW A remains connected to MSC-S A via a solid blue line. A red dotted line connects BSC B to CTXI MGW A.](67a1dd734d3de6e31754caf85d6fe77f_img.jpg) + +Diagram illustrating the network model after the handover. It shows three main components: BSC B (bottom left), MSC-S A (top right), and a combined box containing CTXI MGW A (bottom middle). BSC B is now connected directly to MSC-S A via a green dashed line. CTXI MGW A remains connected to MSC-S A via a solid blue line. A red dotted line connects BSC B to CTXI MGW A. + +After Handover + +**Figure 8.23: Subsequent Inter-MSC GSM to GSM Handover back to the Anchor MSC (network model)** + +Figure 8.24 shows the message sequence example for the Subsequent Inter-MSC GSM to GSM Handover back to the Anchor MSC. It is assumed that the Handover Device is located in the MGW (MGW-A) selected for the call establishment by the MSC server (MSC-A server) which controls the call and the mobility management. + +In the example the MSC-A server requests MGW-A to seize BSC-B side bearer termination with specific flow directions. When the handover is detected in BSC-B the MSC-A server requests to change the flow directions between the terminations within the context in MGW-A. When MSC-A server receives Relocation Complete indication from BSC-B it transfers this indication to MSC-B server. MSC-B server releases the A-interface line towards the BSC-A. MSC-A server initiates call clearing towards MSC-B server. + +![Sequence diagram for Subsequent Inter-MSC GSM to GSM Handover back to the Anchor MSC. Lifelines: BSC B, MSC-S A, MGW A, MSC-S B, MGW B, BSC A. The sequence starts with BSC A sending 'A Handover Required' to MGW B, which then sends 'MAP Prepare Subsequent Handover Req.' to MSC-S B. MSC-S B sends 'Context(C1)' to MGW A. MGW A sends 'TopDescr(*,T6,isolate), {T2,T6,oneway}) + ADD.request (T6)' to MSC-S A. MSC-S A sends 'Context(C1)' to BSC B. BSC B sends 'A Handover Request' to MSC-S A. MSC-S A sends 'TopDescr() + ADD.reply (T6)' to MGW A. MGW A performs 'Reserve Circuit Change Flow Direction'. Finally, MSC-S A sends 'A Handover Request-Ack' to BSC B.](9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg) + +``` +sequenceDiagram + participant BSC B + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant BSC A + + Note right of BSC A: 1 + BSC A->>MGW B: A Handover Required + MGW B->>MSC-S B: MAP Prepare Subsequent Handover Req. + MSC-S B->>MGW A: Context(C1) + MGW A->>MSC-S A: TopDescr(*,T6,isolate), {T2,T6,oneway}) + ADD.request (T6) + MSC-S A->>BSC B: Context(C1) + BSC B->>MSC-S A: A Handover Request + MSC-S A->>MGW A: TopDescr() + ADD.reply (T6) + Note right of MGW A: Reserve Circuit +Change Flow Direction + MSC-S A->>BSC B: A Handover Request-Ack +``` + +Sequence diagram for Subsequent Inter-MSC GSM to GSM Handover back to the Anchor MSC. Lifelines: BSC B, MSC-S A, MGW A, MSC-S B, MGW B, BSC A. The sequence starts with BSC A sending 'A Handover Required' to MGW B, which then sends 'MAP Prepare Subsequent Handover Req.' to MSC-S B. MSC-S B sends 'Context(C1)' to MGW A. MGW A sends 'TopDescr(\*,T6,isolate), {T2,T6,oneway}) + ADD.request (T6)' to MSC-S A. MSC-S A sends 'Context(C1)' to BSC B. BSC B sends 'A Handover Request' to MSC-S A. MSC-S A sends 'TopDescr() + ADD.reply (T6)' to MGW A. MGW A performs 'Reserve Circuit Change Flow Direction'. Finally, MSC-S A sends 'A Handover Request-Ack' to BSC B. + +Figure 8.24/1: Subsequent Inter-MSC GSM to GSM Handover back to the Anchor MSC (message sequence chart) + +![Sequence diagram for Subsequent Inter-MSC GSM to GSM Handover back to the Anchor MSC. Lifelines: BSC B, MSC A, MGW A, MSC B, MGW B, BSC A. The diagram shows the flow of messages for modifying bearer characteristics, detecting handover, changing flow direction, completing handover, clearing resources, and releasing bearers.](da85343976fdbb19f866d9ddbdad0eae_img.jpg) + +``` + +sequenceDiagram + participant BSC B + participant MSC A + participant MGW A + participant MSC B + participant MGW B + participant BSC A + + Note left of BSC B: Handover detected in target BSC + BSC B->>MSC A: A Handover Detect + Note right of MSC A: 2 + MSC A->>MGW A: Context(C1) MOD.request (T6) + Note right of MGW A: Modify Bearer Characteristics (when applicable) + MGW A-->>MSC A: Context(C1) MOD.reply (T6) + MSC A->>MSC B: MAP Prepare Subsequent Handover Resp. + MSC B->>BSC A: A Handover Command + BSC A->>MSC A: A Handover Complete + Note right of MSC A: 3 + MSC A->>MGW A: Context(C1) TopDescr ({T2,T3,oneway},{T2,T6,bothway}) + Note right of MGW A: Change Flow Direction + MGW A-->>MSC A: Context(C1) TopDescr() + MSC A->>MSC B: MAP Send End Signal Resp. + Note right of MSC B: 4 + MSC B->>BSC A: A Clear Command + BSC A-->>MSC B: A Clear Complete + MSC B->>MGW B: Context(C2) SUB.request (T4) + MGW B-->>MSC B: Context(C2) SUB.reply (T4) + Note right of MGW B: Call Clearing and Bearer Release + +``` + +Sequence diagram for Subsequent Inter-MSC GSM to GSM Handover back to the Anchor MSC. Lifelines: BSC B, MSC A, MGW A, MSC B, MGW B, BSC A. The diagram shows the flow of messages for modifying bearer characteristics, detecting handover, changing flow direction, completing handover, clearing resources, and releasing bearers. + +**Figure 8.24/2: Subsequent Inter-MSC GSM to GSM Handover back to the Anchor MSC (message sequence chart)** + +### 8.4.3.3 Subsequent Inter-MSC GSM to GSM Handover back to the anchor MSC for A Interface over IP + +When the MSC-A server receives the MAP Prepare Subsequent Handover Request message, it requests the MGW-A to reserve an RTP bearer termination using the Reserve RTP Connection Point procedure. The MSC-A server requests the + +MGW-A to reserve an IP address and UDP port. The MSC-A server uses the Change Flow Direction procedure to request the MGW-A to set the Handover Device to initial state. + +The MGW-A reserves the RTP termination and indicates the IP address and UDP port number to the MSC-A server. The IP addresses and UDP ports of the MGW-A is sent to the BSC-B in the BSSMAP Handover Request message. When the MSC-A server receives the BSSMAP Handover Request-Ack message, it shall send the BSC-A IP address and UDP Port number to the MGW-B using the Configure RTP Connection Point procedure. + +The sequence is shown in Figure 8.4.3.3/1. + +![Figure 8.4.3.3/1: Subsequent Inter-MSC GSM to GSM Handover back to the anchor MSC for AoIP (message sequence chart).](f99313b06c15e9882079b773ce50a7b2_img.jpg) + +The sequence diagram illustrates the message exchange for a subsequent inter-MSC GSM to GSM handover back to the anchor MSC for AoIP. The participants are BSC B, MSC-S A, MGW A, MSC-S B, MGW B, and BSC A. The sequence starts with BSC A sending 'A Handover Required' to MSC-S B. MSC-S B sends 'MAP Prepare Subsequent Handover Req.' to MSC-S A. MSC-S A sends 'TopDescr({\*,\$,isolate}, {T2,\$,oneway}) +ADD.request (\$)' to MGW A. MGW A responds with 'Reserve RTP Connection Point, Change Flow Direction'. MSC-S A sends 'TopDescr() +ADD.reply (T6)' to MGW A. MSC-S A sends 'A Handover Request' to BSC B. BSC B responds with 'A Handover Request-Ack'. MSC-S A sends 'MOD.request (T6)' to MGW A. MGW A responds with 'Configure RTP Connection Point'. MSC-S A sends 'MOD.reply (T6)' to MGW A. MSC-S A sends 'MAP Prepare Subsequent Handover Resp.' to MSC-S B. The sequence concludes with 'Flow Continues as in Figure 8.24/2'. + +``` + +sequenceDiagram + participant BSC B + participant MSC-S A + participant MGW A + participant MSC-S B + participant MGW B + participant BSC A + + Note left of BSC B: Context(C1) 1 + BSC A->>MSC-S B: A Handover Required + MSC-S B->>MSC-S A: MAP Prepare Subsequent Handover Req. + MSC-S A->>MGW A: TopDescr({*,$,isolate}, {T2,$,oneway}) +ADD.request ($) + MGW A-->>MSC-S A: Reserve RTP Connection Point, Change Flow Direction + MSC-S A->>MGW A: TopDescr() +ADD.reply (T6) + MSC-S A->>BSC B: A Handover Request + BSC B-->>MSC-S A: A Handover Request-Ack + Note left of BSC B: Context(C1) 2 + MSC-S A->>MGW A: MOD.request (T6) + MGW A-->>MSC-S A: Configure RTP Connection Point + MSC-S A->>MGW A: MOD.reply (T6) + MSC-S A->>MSC-S B: MAP Prepare Subsequent Handover Resp. + Note right of MGW B: Flow Continues as in Figure 8.24/2 + +``` + +Figure 8.4.3.3/1: Subsequent Inter-MSC GSM to GSM Handover back to the anchor MSC for AoIP (message sequence chart). + +Figure 8.4.3.3/1: Subsequent Inter-MSC GSM to GSM Handover back to the anchor MSC for AoIP (message sequence chart) + +## 8.4.4 Subsequent GSM to GSM Handover to a third MSC + +The GSM to GSM handover to a third MSC server (from MSC-B server to MSC-B server) is the combination of the two previous inter-MSC handover cases: + +- for MSC-B server a subsequent GSM to GSM handover from MSC-B server back to MSC-A server as described in clause 8.4.3; and +- for MSC-B server a basic GSM to GSM handover from MSC-A server to MSC-B server as described in clause 8.4.2. + +MSC-A server implements the corresponding parts of each handover case, i.e. access handling in MSC-A server is not included. + +## 8.4.5 BSS Internal Handover + +### 8.4.5.1 Introduction + +The procedures specified in 3GPP TS 23.009 [8] for "BSS Internal Handover" shall be followed. The protocol messages are defined in 3GPP TS 48.008 [27]. The following clauses describe the additional requirements for the bearer independent CS core network due to BSS internal handover for A-Interface User Plane over IP (AoIP). + +A BSS Internal Handover may be initiated by the BSS on its own, or triggered by the MSC server with the transmission of an Internal Handover Enquiry message to the BSS. + +#### 8.4.5.2 Internal Handover Required + +When the MSC server receives an Internal Handover Required message, it requests the MGW to seize a TDM circuit using the Reserve Circuit procedure or an RTP termination using the Reserve and Configure RTP Connection Point procedure. In the latter case, the MSC server sends the BSC IP address and UDP port and the determined A-Interface Codec Type/Configuration to the MGW and requests the MGW to reserve a local IP address and UDP port. + +**NOTE:** During a BSS Internal handover procedure involving an IP-based target A-Interface Type before and after the handover, the BSC IP addresses and UDP ports used before and after the handover may be identical or different. This is transparent to the MSC Server. In the former case, the BSC can receive on its BSC IP address and UDP port identical RTP flows received from the source and target access terminations reserved in the MGW. + +For non-speech calls the MSC server shall provide the MGW with the GSM Channel coding properties and the same PLMN Bearer Capability as was provided at the last access bearer assignment. The MSC server uses the Change Flow Direction procedure to request the MGW to set the Handover Device to initial state. + +The MGW reserves the TDM circuit or RTP termination and indicates in the latter case its own IP address and UDP port to the MSC server. The MSC server then sends the Internal Handover Command message to the BSC containing the speech codec type/configuration chosen and either the CIC or the MGW IP address and UDP port. + +If the resources requested by the BSS in the Internal Handover Required message (e.g. codec type or codec configuration, interface type, etc.) are not available, an Internal Handover Required Reject message shall be returned to the BSS with the appropriate failure cause, and the procedure shall be terminated. + +#### 8.4.5.3 Internal Handover Command/Handover Detect + +When the MSC server sends the Internal Handover Command message or alternatively if it receives the Handover Detect message, the MSC server uses the Change Flow Direction procedure to requests the MGW to set the Handover Device to intermediate state (bullet 2 in figure 8.4.5.8.2). + +#### 8.4.5.4 Handover Complete + +When the MSC server receives the Handover Complete message, it requests the MGW to set the Handover Device to its final state by removing the bearer termination towards the source BSC IP address and UDP port number, using the Release Termination procedure (bullet 3 in figure 8.4.5.8.2). + +#### 8.4.5.5 Interworking function + +The interworking function used by the MGW before handover will also be used after handover. + +#### 8.4.5.6 Voice Processing function + +After handover, the MGW may continue or modify voice processing function(s) provided to each bearer termination. + +#### 8.4.5.7 Failure Handling in MSC server + +When a procedure between the MSC server and the MGW fails the MSC server shall handle the failure as an internal error in accordance with 3GPP TS 23.009 [8] and 3GPP TS 29.010 [23]. If MGW resources have already been seized for BSS internal handover then the resources shall be released using the Release Termination procedure. If the call is to be cleared, then it shall be handled as described in clause 7.3. + +If the MSC server receives the Handover Failure message during BSS internal handover procedure, it shall release MGW resources if they have been seized for BSS internal handover using the Release Termination procedure. + +### 8.4.5.8 Example for a successful BSS Internal Handover + +Figure 8.4.5.8.1 shows the network model for the BSS Internal Handover, where IP transport is used on the A interface before and after the BSS Internal Handover procedure. The "squared" line represents the call control signalling. The "dotted" line represents the bearer. The bearer termination T1 is used for the bearer towards the source BSC IP address and UDP port number Ta, bearer termination T3 is used for the bearer towards the target BSC IP address and UDP port number Tb and the bearer termination T2 is used for the bearer towards the succeeding/preceding MGW. + +![Diagram showing the network model before BSS Internal Handover. A BSC (Base Station Controller) is connected to an MGW (Media Gateway) via a dotted red line representing the bearer. The BSC has a bearer termination labeled Ta. The MGW has three bearers: T1 (connected to the BSC), T2 (connected to an MSCS), and T3 (connected to the MSCS). The MSCS is connected to the MGW via a solid blue line representing call control signalling. The MSCS is also connected to a dotted green line representing the bearer towards the target BSC.](5d5ec4f1999e7c46d426dddc16ba1e08_img.jpg) + +Diagram showing the network model before BSS Internal Handover. A BSC (Base Station Controller) is connected to an MGW (Media Gateway) via a dotted red line representing the bearer. The BSC has a bearer termination labeled Ta. The MGW has three bearers: T1 (connected to the BSC), T2 (connected to an MSCS), and T3 (connected to the MSCS). The MSCS is connected to the MGW via a solid blue line representing call control signalling. The MSCS is also connected to a dotted green line representing the bearer towards the target BSC. + +Before BSS Internal Handover + +![Diagram showing the network model during BSS Internal Handover. The BSC now has two bearer terminations: Ta (connected to the MGW) and Tb (connected to the MGW). The MGW has four bearers: T1 (connected to the BSC), T2 (connected to the MSCS), T3 (connected to the BSC), and T4 (connected to the MSCS). The MSCS is connected to the MGW via a solid blue line representing call control signalling. The MSCS is also connected to a dotted green line representing the bearer towards the target BSC.](fb73a07d61dc5c47709b9802b894d716_img.jpg) + +Diagram showing the network model during BSS Internal Handover. The BSC now has two bearer terminations: Ta (connected to the MGW) and Tb (connected to the MGW). The MGW has four bearers: T1 (connected to the BSC), T2 (connected to the MSCS), T3 (connected to the BSC), and T4 (connected to the MSCS). The MSCS is connected to the MGW via a solid blue line representing call control signalling. The MSCS is also connected to a dotted green line representing the bearer towards the target BSC. + +During BSS Internal Handover + +![Diagram of Intra-MSC BSS Internal Handover (network model) after BSS Internal Handover. The diagram shows three main components: BSC (Base Station Controller), MGW (Media Gateway), and MSCS (MSC Server). The BSC is connected to the MGW via a red dotted line labeled 'Tb'. The MGW is connected to the MSCS via a solid blue line. The MSCS is connected to the BSC via a green dashed line. The MGW contains three RTP bearers: T3, CTX1, and T2. The BSC contains a single RTP bearer labeled 'Tb'. The MGW also contains an 'X' symbol, indicating a switch or connection point.](3ec35c497a0765a1a885c85f214b1bef_img.jpg) + +Diagram of Intra-MSC BSS Internal Handover (network model) after BSS Internal Handover. The diagram shows three main components: BSC (Base Station Controller), MGW (Media Gateway), and MSCS (MSC Server). The BSC is connected to the MGW via a red dotted line labeled 'Tb'. The MGW is connected to the MSCS via a solid blue line. The MSCS is connected to the BSC via a green dashed line. The MGW contains three RTP bearers: T3, CTX1, and T2. The BSC contains a single RTP bearer labeled 'Tb'. The MGW also contains an 'X' symbol, indicating a switch or connection point. + +#### After BSS Internal Handover + +**Figure 8.4.5.8.1: Intra-MSC BSS Internal Handover (network model)** + +Figure 8.4.5.8.2 shows the message sequence example for the Intra-MSC BSS Internal Handover. + +In the example, the MSC server receives the Internal Handover Required message and requests the MGW to reserve an RTP bearer termination (T3) using the Reserve and Configure RTP Connection Point procedure with specific flow directions. + +The MSC server starts the Internal Handover execution by sending the Internal Handover Command towards the BSC in which it provides the IP address and UDP port of the target MGW RTP termination (T3). When the handover is detected in the BSC, the MSC server requests the MGW to change the flow directions between the terminations within the context. When the MSC server receives the Handover Complete indication from the BSC it requests the MGW to release the bearer termination T1 towards the source BSC IP address and UDP port number Ta that was used before the BSS Internal Handover was initiated. The sequence is shown in Figure 8.4.5.8.2. + +![Sequence diagram for Intra-MSC BSS Internal Handover for AoIP. Lifelines: BSC A, MSC-S, MGW. The process involves: 1. Internal Handover Enquiry from BSC A to MSC-S. 2. Internal Handover Required from MSC-S to BSC A. 3. TopDescr(*,$,isolate), {T2,$,oneway}+ADD.request ($1) from MSC-S to MGW, with actions: Reserve and Configure RTP Connection Point, Change Flow Direction. 4. TopDescr()+ADD.reply (T3) from MGW to MSC-S. 5. Internal Handover Command from MSC-S to BSC A. 6. Handover detected in target cell (green box) from BSC A. 7. Handover Detected from BSC A to MSC-S. 8. TopDescr({T2,T1,oneway}, {T2,T3,bothway}) from MSC-S to MGW, with action: Change Flow Direction. 9. TopDescr() from MGW to MSC-S. 10. Handover Complete from MSC-S to BSC A. 11. SUB.request (T1) from MSC-S to MGW, with action: Release Termination. 12. SUB.reply (T1) from MGW to MSC-S.](24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg) + +``` + +sequenceDiagram + participant BSC A + participant MSC-S + participant MGW + Note right of BSC A: Handover detected in target cell + BSC A->>MSC-S: Internal Handover Enquiry + MSC-S->>BSC A: Internal Handover Required + MSC-S->>MGW: Context(C1) 1 TopDescr(*,$,isolate), {T2,$,oneway}+ADD.request ($1) + Note right of MGW: Reserve and Configure RTP Connection Point, Change Flow Direction + MGW->>MSC-S: Context(C1) TopDescr()+ADD.reply (T3) + MSC-S->>BSC A: Context(C1) Internal Handover Command + BSC A->>MSC-S: Handover Detected + MSC-S->>MGW: Context(C1) 2 TopDescr({T2,T1,oneway}, {T2,T3,bothway}) + Note right of MGW: Change Flow Direction + MGW->>MSC-S: Context(C1) TopDescr() + MSC-S->>BSC A: Handover Complete + MSC-S->>MGW: Context(C1) 3 SUB.request (T1) + Note right of MGW: Release Termination + MGW->>MSC-S: Context(C1) SUB.reply (T1) + +``` + +Sequence diagram for Intra-MSC BSS Internal Handover for AoIP. Lifelines: BSC A, MSC-S, MGW. The process involves: 1. Internal Handover Enquiry from BSC A to MSC-S. 2. Internal Handover Required from MSC-S to BSC A. 3. TopDescr(\*,\$,isolate), {T2,\$,oneway}+ADD.request (\$1) from MSC-S to MGW, with actions: Reserve and Configure RTP Connection Point, Change Flow Direction. 4. TopDescr()+ADD.reply (T3) from MGW to MSC-S. 5. Internal Handover Command from MSC-S to BSC A. 6. Handover detected in target cell (green box) from BSC A. 7. Handover Detected from BSC A to MSC-S. 8. TopDescr({T2,T1,oneway}, {T2,T3,bothway}) from MSC-S to MGW, with action: Change Flow Direction. 9. TopDescr() from MGW to MSC-S. 10. Handover Complete from MSC-S to BSC A. 11. SUB.request (T1) from MSC-S to MGW, with action: Release Termination. 12. SUB.reply (T1) from MGW to MSC-S. + +Figure 8.4.5.8.2: Intra-MSC BSS Internal Handover for AoIP (message sequence chart) + +## 8.5 Handling of GSM Services after UMTS to GSM Handover + +The handling of GSM services after handover in the Bearer Independent CS Core Network architecture is as for the corresponding UMTS services, if not stated differently. + +## 9 Compatibility Issues + +A Release 4 (or later) node, according to 3GPP TS 23.205, is backward compatible with a Release 99 (or earlier) node. + +### 9.1 Interworking with GERAN (A i/f) + +#### 9.1.1 Introduction + +The A-interface signalling terminates in the MSC server and the user plane terminates in the MGW. TDM and/or IP transports may be supported on the A-interface. The MSC server uses the Mc interface to remotely control the TDM or IP resources in the MGW. + +For intra-MSC handover, the target A-interface is handled as described in clause 8. If the target A-interface user plane terminates in a different MGW from the MGW that terminates the serving A-interface user plane, a bearer has to be established between the two MGWs using Prepare Bearer and Establish Bearer procedures. Because the same MSC server controls both MGWs, no external call control signalling is involved. + +It is important to note that the separation between the user and control planes remains the same before and after interaction with services in the 3G BICC CSCN. + +### 9.1.2 A interface over TDM + +Only one MSC server may control the TDM circuits connected to one GERAN node. + +For each TDM circuit a physical termination is provisioned in the MGW. The TDM circuit is identified by the termination Id in the Mc interface. Since TDM circuits are also grouped together, the physical termination Ids are structured in accordance with the grouping of TDM circuits. The MSC server also knows the termination Ids and the grouping of termination Ids. The physical termination exists as long as the TDM circuit(s) exists in the MGW. + +Figure 9.1 shows the network model for the A-interface. The "squared" line represents the call control signalling and the "dotted" line represents the TDM circuits. The terminations T1-Tn represent the TDM circuits in the MGW. The MSC server has a mapping table between circuits CIC1-CICn and the terminations T1-Tn. + +![Figure 9.1: TDM circuits used for A-interface (network model). The diagram shows three main components: BSC (Base Station Controller), MSC-S (MSC Server), and MGW (Media Gateway). The BSC is connected to the MSC-S via a solid line (signalling) and a dotted line (TDM circuits). The MSC-S is connected to the MGW via a solid line (signalling) and a dotted line (TDM circuits). The MGW has multiple physical terminations labeled T1 to Tn. The MSC-S has labels CIC1=T1 and CICn=Tn, indicating a mapping between TDM circuits and physical terminations.](70a07cbdcf39ad922c4f80528f12bc46_img.jpg) + +Figure 9.1: TDM circuits used for A-interface (network model). The diagram shows three main components: BSC (Base Station Controller), MSC-S (MSC Server), and MGW (Media Gateway). The BSC is connected to the MSC-S via a solid line (signalling) and a dotted line (TDM circuits). The MSC-S is connected to the MGW via a solid line (signalling) and a dotted line (TDM circuits). The MGW has multiple physical terminations labeled T1 to Tn. The MSC-S has labels CIC1=T1 and CICn=Tn, indicating a mapping between TDM circuits and physical terminations. + +**Figure 9.1 TDM circuits used for A-interface (network model)** + +For call-independent transactions the general (G)MSC server-MGW procedures, as described in clause 10, apply to the physical terminations in the same way as to any other terminations. + +For call related transactions the handling as described in the clauses 6, 7 and 8 apply to physical terminations in the same way as any other terminations. All call related procedures, except Prepare Bearer, Establish Bearer, Release Bearer and Tunnel Information Up/Down, as described in clause 16, apply to the physical terminations in the same way as any other terminations. + +## 10 General (G)MSC server-MGW Procedures + +### 10.1 MGW Unavailable + +The (G)MSC server recognises that the MGW is unavailable in the following 4 cases: + +1. The signalling connection is unavailable + +![Figure 10.1: Signalling connection failure. The diagram shows two main components: (G)MSC-S (MSC Server) and MGW (Media Gateway). A dashed line with an arrow pointing from the (G)MSC-S to the MGW represents the signalling connection. The line is broken, and the text 'Signalling Connection Failure' is written below the break.](1520ac6ca40d678c53dca4ef6550963f_img.jpg) + +Figure 10.1: Signalling connection failure. The diagram shows two main components: (G)MSC-S (MSC Server) and MGW (Media Gateway). A dashed line with an arrow pointing from the (G)MSC-S to the MGW represents the signalling connection. The line is broken, and the text 'Signalling Connection Failure' is written below the break. + +**Figure 10.1: Signalling connection failure** + +2. The MGW indicates the failure condition to all connected (G)MSC servers + +![Sequence diagram showing MGW Out of Service and MGW Out of Service Ack messages between (G)MSC-S and MGW.](684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg) + +``` + +sequenceDiagram + participant (G)MSC-S + participant MGW + Note right of MGW: MGW Out of Service + MGW->>(G)MSC-S: MGW Out of Service + Note left of (G)MSC-S: MGW Out of Service Ack + (G)MSC-S->>MGW: MGW Out of Service Ack + +``` + +Sequence diagram showing MGW Out of Service and MGW Out of Service Ack messages between (G)MSC-S and MGW. + +**Figure 10.2: MGW indicates the Failure/Maintenance locking** + +The failure indication indicates that the MGW will soon go out of service and that no new connections should be established using this MGW. The MGW can choose between the "graceful" and the "forced" method. In the graceful method the connections are cleared when the corresponding calls are disconnected. In the forced method all connection are cleared immediately. + +3. The (G)MSC server recognises that the MGW is not functioning correctly, e.g. because there is no reply on periodic sending of Audits. The periodic sending of Audits by (G)MSC server should go on. +4. The MGW indicates the maintenance locking condition to all concerned (G)MSC servers. + +The maintenance locking indication indicates that the MGW is locked for new calls and that no new connections shall be established using this MGW. The MGW can choose between the "graceful" and the "forced" method. In the graceful method the connections are cleared when the corresponding calls are disconnected. In the forced method all connection are cleared immediately + +In all of the above cases the (G)MSC server shall prevent the usage of the MGW until the MGW has recovered or the communication with the MGW is restored. The (G)MSC server shall prohibit the surrounding network from seizing circuits connected to the unavailable TDM access by sending blocking messages. + +## 10.2 MGW Available + +The (G)MSC server discovers that the MGW is available when it receives an MGW Communication Up message or an MGW Restoration message. If the (G)MSC does not wish to sustain an association with the MGW, the response sent to the MGW may indicate an alternative MGCIId signalling address, in which case the MGW shall not consider itself registered and should preferably attempt to re-register with this alternative MGC before any further alternate MGCs. Otherwise, the response shall not indicate any alternative MGCIId signalling address. + +When the (G)MSC server discovers that the MGW is available the following shall occur: + +1. Signalling recovery + +The MGW indicates to all connected (G)MSC servers that the signalling connection is restored. Any changes to the physical termination state during the loss of communication shall be reported by the MGW using Termination Out Of Service (10.7) or Termination Restoration (10.8), otherwise the (G)MSC Server can assume that Terminations service state has not changed. To avoid unsuccessful calls for physical terminations which went out of service during the loss of communication but have not yet been reported by the MGW the MSC Server may Audit the physical terminations before it uses them. + +NOTE: Auditing in this case will cause duplicate signalling. + +![Sequence diagram showing communication going up between (G)MSC-S and MGW.](921f8fa0f7ce2c9956f20d33162c13a2_img.jpg) + +``` + +sequenceDiagram + participant (G)MSC-S + participant MGW + Note right of (G)MSC-S: Signalling in service + (G)MSC-S->>MGW: MGW Communication Up + MGW-->>(G)MSC-S: MGW Communication Up Ack + +``` + +The diagram illustrates a sequence of messages between a (G)MSC-S and an MGW. It starts with a dashed arrow labeled 'Signalling in service' pointing from the (G)MSC-S to the MGW. This is followed by a solid arrow labeled 'MGW Communication Up' pointing from the (G)MSC-S to the MGW. Finally, a solid arrow labeled 'MGW Communication Up Ack' points from the MGW back to the (G)MSC-S. + +Sequence diagram showing communication going up between (G)MSC-S and MGW. + +**Figure 10.3: Communication goes up** + +2. MGW restoration/maintenance unlocking indication. + +The MGW indicates to all connected (G)MSC servers that normal operation has resumed. Changes of the physical termination state during the connection break shall be reported by the MGW using Termination Out Of Service (10.7) and Termination restoration (10.8) procedures, otherwise the (G)MSC Server can assume that Terminations service state has not changed. To avoid unsuccessful calls for physical terminations which went out of service during the loss of communication but have not yet been reported by the MGW the (G)MSC Server may Audit the physical terminations before it uses them. + +NOTE: Auditing in this case will cause duplicate signalling. + +![Sequence diagram showing MGW indicates recovery from a failure/or maintenance unlocking.](77c78bfdbbee0e121808674b08fd7046_img.jpg) + +``` + +sequenceDiagram + participant (G)MSC- + participant MG + Note right of (G)MSC-: Signalling in + (G)MSC-->>MG: MGW Restoration + MG-->>(G)MSC-: MGW Restoration Ack + +``` + +The diagram illustrates a sequence of messages between a (G)MSC- and an MG. It starts with a dashed arrow labeled 'Signalling in' pointing from the (G)MSC- to the MG. This is followed by a solid arrow labeled 'MGW Restoration' pointing from the (G)MSC- to the MG. Finally, a solid arrow labeled 'MGW Restoration Ack' points from the MG back to the (G)MSC-. + +Sequence diagram showing MGW indicates recovery from a failure/or maintenance unlocking. + +**Figure 10.4: MGW indicates recovery from a failure/or maintenance unlocking** + +NOTE: This procedure may be used after recovery from a signalling failure. + +3. The (G)MSC server recognises that the MGW is now functioning correctly, e.g. because there is a reply on periodic sending of Audits. + +After this the (G)MSC server can use the MGW. If the corresponding devices of the surrounding network are blocked, unblocked messages shall be sent to the nodes concerned for devices that are in service: the (G)MSC Server has determined the actual state of the physical devices either by receiving Termination Restoration procedure (10.8) or by performing an Audit.. + +If none of 1,2, and 3 happens the (G)MSC server can initiate the (G)MSC Server Ordered Re-register procedure. + +## 10.3 MGW Recovery + +If the MGW recovers from a failure, is maintenance unlocked, or it has been restarted, it registers to its known (G)MSC servers using the MGW Restoration procedure or the MGW Registration procedure. The MGW can indicate whether the Service has been restored or whether it has restarted with a cold or warm boot. If the (G)MSC does not wish to sustain an association with the MGW, the response sent to the MGW may indicate an alternative MGCI signalling address, in which case the MGW shall not consider itself registered and should preferably attempt to re-register with this alternative MGC before any further alternate MGCs. Otherwise, the response shall not indicate any alternative MGCI signalling address. + +![Sequence diagram for MGW Restoration](536768a30136cd5c2d57f46c25d1d804_img.jpg) + +``` +sequenceDiagram + participant (G)MSC-S + participant MGW + Note right of MGW: MGW Restoration + MGW->>(G)MSC-S: (Service Restored) + Note left of (G)MSC-S: MGW Restoration Ack + (G)MSC-S->>MGW: (G)MSC-S address +``` + +The diagram illustrates the MGW Restoration process. It features two vertical lifelines: (G)MSC-S on the left and MGW on the right. The sequence begins with a message labeled 'MGW Restoration' originating from the MGW lifeline. Below this, a message labeled '(Service Restored)' is shown as a return message from the MGW to the (G)MSC-S. Next, a message labeled 'MGW Restoration Ack' originates from the (G)MSC-S lifeline. Finally, a message labeled '(G)MSC-S address' is shown as a return message from the (G)MSC-S to the MGW. + +Sequence diagram for MGW Restoration + +**Figure 10.5/1: MGW Restoration**![Sequence diagram for MGW Registration](c9bcc9f954279dd8f99cdcb0f41fff4a_img.jpg) + +``` +sequenceDiagram + participant (G)MSC-S + participant MGW + Note right of MGW: MGW Register + MGW->>(G)MSC-S: (Cold/Warm boot) + Note left of (G)MSC-S: MGW Register Ack + (G)MSC-S->>MGW: (G)MSC-S address +``` + +The diagram illustrates the MGW Registration process. It features two vertical lifelines: (G)MSC-S on the left and MGW on the right. The sequence begins with a message labeled 'MGW Register' originating from the MGW lifeline. Below this, a message labeled '(Cold/Warm boot)' is shown as a return message from the MGW to the (G)MSC-S. Next, a message labeled 'MGW Register Ack' originates from the (G)MSC-S lifeline. Finally, a message labeled '(G)MSC-S address' is shown as a return message from the (G)MSC-S to the MGW. + +Sequence diagram for MGW Registration + +**Figure 10.5/2 MGW Registration** + +After the recovery the (G)MSC server can use the MGW. After a MGW warm boot or service restored, the (G)MSC Server can assume the physical terminations state has not changed. Changes of the physical termination state during the connection break shall be reported by the MGW using Termination Out Of Service (10.7) and Termination restoration (10.8) procedures. To avoid unsuccessful calls for physical terminations which went out of service during the loss of communication but have not yet been reported by the MGW the MSC Server may Audit the physical terminations before it uses them. + +NOTE: Auditing in this case will cause duplicate signalling. + +After receiving a MGW Register (with cold boot) the (G)MSC Server shall audit the termination state of all physical terminations (10.9) if it has not been specifically informed of the actual service state since receiving the MGW service change on ROOT (Register) via independent service change commands (10.7 or 10.8). The (G)MSC Server shall thereby determine the actual Service State of devices. If the corresponding devices of the surrounding network are blocked, unblocked messages are sent to the nodes concerned for all devices that are in service. + +## 10.4 (G)MSC server Recovery + +### 10.4.1 General + +If an MGW-unavailable condition is provoked by a failure/recovery action, the (G)MSC server recovery sequence will, from an information flow point of view, look like MGW unavailable and then MGW available. If an MGW-unavailable condition is not provoked, the (G)MSC server recovery sequence will look like MGW available. + +After the information flow, the terminations affected by the recovery action are released. + +## 10.4.2 (G)MSC Server Restoration + +![Sequence diagram for (G)MSC Server Restoration](649f424fd35ea31f622163506a6148ed_img.jpg) + +A sequence diagram illustrating the (G)MSC Server Restoration procedure between a (G)MSC-S and an MGW. The sequence starts with the (G)MSC-S sending a '(G)MSC recovery complete' message to the MGW. A dashed line labeled 'Signalling working' follows. The MGW then sends a 'Communication Up/MGW Restoration' message to the (G)MSC-S. The (G)MSC-S responds with a 'Communication Up/MGW Restoration Ack' message. Next, the (G)MSC-S sends a '(G)MSC Server Restoration warm, cold ( boot) note' message to the MGW. Finally, the MGW sends a '(G)MSC Server Restoration Ack' message back to the (G)MSC-S. A vertical line labeled 'Tw' is shown on the (G)MSC-S lifeline, indicating a timer. + +Sequence diagram for (G)MSC Server Restoration + +Figure 10.6: (G)MSC Server Restoration + +NOTE: Normal release procedure may also be initiated. + +After the recovery action is complete and it is possible to signal to the MGW the (G)MSC server starts a timer Tw. If recovery indications are not received (MGW Communication Up or MGW Restoration) from the MGW during Tw an Audit is sent. If the (G)MSC server receives a recovery indication or MGW communication up indication, it shall acknowledge the indication before the (G)MSC Server Restoration may be sent or the release procedure is initiated. + +## 10.5 MGW Re-register + +When the (G)MSC requests an MGW to perform a registration (see clause 10.2, 10.3 and 10.6), the MGW performs a re-registration to the (G)MSC which is defined in the (G)MSC address. If the (G)MSC Server is uncertain of the termination service state of physical terminations after the Re-Register it shall use the Audit Procedure (10.9). Changes of the physical termination state during the connection break shall be reported by the MGW using Termination Out Of Service (10.7) and Termination restoration (10.8) procedures. + +![Sequence diagram for MGW Re-register](288220dc8e18b23fc8f294cf1ca909b4_img.jpg) + +A sequence diagram illustrating the MGW Re-register procedure between a (G)MSC-S and an MGW. The MGW sends an 'MGW Re-register' message to the (G)MSC-S. The (G)MSC-S responds with an 'MGW Re-register Ack' message back to the MGW. + +Sequence diagram for MGW Re-register + +Figure 10.7: Re-registration of an MGW + +## 10.6 MGW Re-registration Ordered by (G)MSC server + +If the (G)MSC server knows that communication is possible, but the MGW has not registered, the (G)MSC server can order re-registration of the MGW. + +![Sequence diagram showing re-registration ordered by the (G)MSC server.](820515db47ded68f5e0b625f4ec7d2c1_img.jpg) + +``` +sequenceDiagram + participant (G)MSC-S + participant MGW + Note right of (G)MSC-S: (G)MSC Server Ordered Re-register + (G)MSC-S->>MGW: (G)MSC Server Ordered Re-register ((G)MSC address) + Note left of MGW: (G)MSC Server Ordered Re-register + MGW-->>(G)MSC-S: Ack +``` + +The diagram illustrates a sequence of messages between a (G)MSC-S and an MGW. The (G)MSC-S sends a message labeled "(G)MSC Server Ordered Re-register" with the parameter "(G)MSC address" to the MGW. The MGW responds with an "Ack" message. A second, identical message label is shown on the (G)MSC-S side, likely due to a rendering error in the original document. + +Sequence diagram showing re-registration ordered by the (G)MSC server. + +**Figure 10.8: Re-registration ordered by the (G)MSC server** + +If the re-registration request is accepted the MGW uses the MGW Re-register procedure to register with the (G)MSC server. + +## 10.7 Removal from Service of a Physical Termination + +The MGW indicates the removal from service of a physical termination using the Termination Out-of-Service procedure. In this procedure the MGW indicates which termination is to be removed from service and whether the "graceful" or "forced" method will be used. In the graceful method a possible connection is cleared when the corresponding call is disconnected. In the forced method the possible connection is cleared immediately. + +![Sequence diagram showing removal from service of a physical termination.](868ef3e0abb37916a7af1e923995f329_img.jpg) + +``` +sequenceDiagram + participant (G)MSC-S + participant MGW + Note right of MGW: Termination Out-Of-Service + MGW->>(G)MSC-S: Termination Out-Of-Service (Termination(s)) + Note left of (G)MSC-S: Termination Out-Of-Service Ack + (G)MSC-S-->>MGW: Termination Out-Of-Service Ack +``` + +The diagram illustrates a sequence of messages between an MGW and a (G)MSC-S. The MGW sends a message labeled "Termination Out-Of-Service" with the parameter "(Termination(s))" to the (G)MSC-S. The (G)MSC-S responds with a "Termination Out-Of-Service Ack" message. + +Sequence diagram showing removal from service of a physical termination. + +**Figure 10.9: Removal from service of a Physical Termination** + +The (G)MSC server shall prevent the use of the Termination(s) concerned until the physical termination is restored to service. + +## 10.8 Restoration to Service of a Physical Termination + +If the physical termination is restored to service, the MGW shall report it to the (G)MSC server(s) using the Termination Restoration procedure. + +![Sequence diagram for Termination Restoration procedure between (G)MSC-S and MGW.](6d6670b8e65d3ff8126e5ab9aeaffbd8_img.jpg) + +``` +sequenceDiagram + participant (G)MSC-S + participant MGW + Note right of MGW: Termination restored + MGW->>(G)MSC-S: Termination Restoration (Termination(s)) + (G)MSC-S-->>MGW: Termination Restoration Ack +``` + +The diagram illustrates the interaction between a (G)MSC-S and an MGW. The MGW sends a 'Termination Restoration' message containing '(Termination(s))' to the (G)MSC-S. The (G)MSC-S responds with a 'Termination Restoration Ack' message. + +Sequence diagram for Termination Restoration procedure between (G)MSC-S and MGW. + +**Figure 10.10: Restoration to service of a Physical Termination** + +The (G)MSC server can use the physical termination when the termination has been restored to service. If the corresponding devices of the surrounding network are blocked, the (G)MSC server sends an unblocked message to each node concerned. + +## 10.9 Audit of MGW + +### 10.9.1 Audit of Value + +The (G)MSC server may request the MGW to report the current values assigned to distinct objects in the MGW. Objects, which can be addressed, are listed in 3GPP TS 29.232 [6]. This procedure shall be used when a change has occurred in the (G)MSC server such that the server is unsure of the current Service State of Terminations, such as restart or new trunks configured in the server. For any situation where a change to the Service State occurs in the MGW the (G)MSC server shall expect the Service State to be reported by Termination Restoration (10.8) or Termination Out Of Service (10.7). + +![Sequence diagram for Audit Value procedure between (G)MSC-S and MGW.](72bc1a2b64dd6bac8285f560440c1218_img.jpg) + +``` +sequenceDiagram + participant (G)MSC-S + participant MGW + (G)MSC-S->>MGW: Audit Value (Object(s)) + MGW-->>(G)MSC-S: Audit Value Ack (values per requested object) +``` + +The diagram illustrates the interaction between a (G)MSC-S and an MGW. The (G)MSC-S sends an 'Audit Value' message containing '(Object(s))' to the MGW. The MGW responds with an 'Audit Value Ack' message containing '(values per requested object)'. + +Sequence diagram for Audit Value procedure between (G)MSC-S and MGW. + +**Figure 10.11: Audit Value** + +### 10.9.2 Audit of Capability + +The (G)MSC server may request the MGW to report the capabilities of distinct objects in the MGW. Objects, which can be addressed, are listed in 3GPP TS 29.232 [6]. + +![Sequence diagram for Audit Capability between (G)MSC-S and MGW.](d244183a8ff3d94b0dcf30140f51020d_img.jpg) + +``` +sequenceDiagram + participant (G)MSC-S + participant MGW + Note left of (G)MSC-S: + (G)MSC-S->>MGW: Audit Capability (Object(s)) + Note right of MGW: + MGW-->>(G)MSC-S: Audit Capability Ack (capabilities per requested object) +``` + +The diagram shows a sequence of messages between (G)MSC-S and MGW. The (G)MSC-S sends an 'Audit Capability' message to the MGW, which includes '(Object(s))'. The MGW responds with an 'Audit Capability Ack' message, which includes '(capabilities per requested object)'. + +Sequence diagram for Audit Capability between (G)MSC-S and MGW. + +Figure 10.12: Audit Capability + +## 10.10 MGW Capability Change + +The MGW reports a change of capability of distinct objects in the MGW. Objects, which can be addressed, are listed in 3GPP TS 29.232 [6]. + +![Sequence diagram for MGW Capability Change between (G)MSC-S and MGW.](f89631cc38aa971e8d15cbffe28f1183_img.jpg) + +``` +sequenceDiagram + participant (G)MSC-S + participant MGW + Note right of MGW: + MGW->>(G)MSC-S: Capability Update (Object(s)) + Note left of (G)MSC-S: + (G)MSC-S-->>MGW: Capability Update Ack +``` + +The diagram shows a sequence of messages between (G)MSC-S and MGW. The MGW sends a 'Capability Update' message to the (G)MSC-S, which includes '(Object(s))'. The (G)MSC-S responds with a 'Capability Update Ack' message. + +Sequence diagram for MGW Capability Change between (G)MSC-S and MGW. + +Figure 10.13: Capability Update + +The (G)MSC server can use the Audit Value and/or Audit Capability procedures to obtain further information, about the objects whose capabilities have changed. + +10.11 Void + +10.12 (G)MSC Server Out of service + +![Sequence diagram for (G)MSC Server Out of Service procedure.](f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg) + +``` +sequenceDiagram + participant (G)MSC-S + participant MGW + Note left of (G)MSC-S: (G)MSC Server Out of Service + (G)MSC-S->>MGW: (G)MSC Server Out of Service (Forced/graceful) + MGW-->>(G)MSC-S: (G)MSC Server Out of Service Ack +``` + +The diagram shows a sequence of messages between a (G)MSC-S and an MGW. The (G)MSC-S sends a message labeled "(G)MSC Server Out of Service (Forced/graceful)" to the MGW. The MGW responds with a message labeled "(G)MSC Server Out of Service Ack" back to the (G)MSC-S. + +Sequence diagram for (G)MSC Server Out of Service procedure. + +Figure 10.14: (G)MSC Server Out of Service + +If a (G)MSC server discovers that it wants to go out of service it starts a (G)MSC Server Out of Service procedure. The (G)MSC server can indicate whether it requires the context to be cleared immediately (forced) or cleared as the bearer control protocol clears the bearer (Graceful). Physical terminations are always cleared when the (G)MSC Server Out of Service indication reaches the MGW. + +10.13 MGW Resource Congestion Handling - Activate + +When the (G)MSC server requires that a MGW congestion notification mechanism be applied in the MGW, the (G)MSC server shall use the MGW Resource Congestion Handling - Activate procedure towards the MGW. + +![Sequence diagram for MGW Resource Congestion Handling - Activate procedure.](32acdaad6c921e80fd17e42562858b80_img.jpg) + +``` +sequenceDiagram + participant (G)MSC-S + participant MGW + (G)MSC-S->>MGW: MGW Resource Congestion Handling - Activate + MGW-->>(G)MSC-S: MGW Resource Congestion Handling - Activate -Ack +``` + +The diagram shows a sequence of messages between a (G)MSC-S and an MGW. The (G)MSC-S sends a message labeled "MGW Resource Congestion Handling - Activate" to the MGW. The MGW responds with a message labeled "MGW Resource Congestion Handling - Activate -Ack" back to the (G)MSC-S. + +Sequence diagram for MGW Resource Congestion Handling - Activate procedure. + +Figure 10.15: MGW Resource Congestion Handling - Activate + +10.14 MGW Resource Congestion Handling -Indication + +When the (G)MSC server receives a load reduction notification from the MGW via the MGW Resource Congestion Handling - Indication procedure, the (G)MSC server tries to reduce the processing load that the (G)MSC server creates on the MGW. The MGW shall decide the actual level of traffic reduction. + +![Sequence diagram for MGW Resource Congestion Handling - Indication procedure.](86f61404a19a384d06a7b0b2c4e6937a_img.jpg) + +``` +sequenceDiagram + participant (G)MSC-S + participant MGW + MGW->>(G)MSC-S: MGW Resource Congestion Handling - Indication + (G)MSC-S-->>MGW: MGW Resource Congestion Handling - Indication-Ack +``` + +The diagram shows a sequence of messages between a (G)MSC-S and an MGW. The MGW sends a message labeled "MGW Resource Congestion Handling - Indication" to the (G)MSC-S. The (G)MSC-S responds with a message labeled "MGW Resource Congestion Handling - Indication-Ack" back to the MGW. + +Sequence diagram for MGW Resource Congestion Handling - Indication procedure. + +Figure 10.17: MGW Resource Congestion Handling – Indication + +## 10.15 Control association monitoring + +Monitoring of the H.248 control association may be performed by monitoring the status of the transport link association where the transport protocol provides sufficient coupling to the H.248.1 protocol, i.e. if the transport link association is disconnected when no local H.248.1 protocol connection exists. + +An alternative method for the MGW to detect loss of the MGC may be achieved by requesting the MGW to poll the (G)MSC periodically + +Upon registration of a MGW, the (G)MSC server may use the Inactivity Timeout - Activate procedure towards the MGW to request the MGW to monitor incoming messages for periods of silence exceeding the maximum inactivity timer value. + +![Sequence diagram for Inactivity Timeout - Activate procedure](1b896a95bc9974ad01fac7ac6f541a96_img.jpg) + +``` +sequenceDiagram + participant G(MSC) - S + participant MGW + Note left of G(MSC) - S: Upon registration of a MGW + G(MSC) - S->>MGW: Inactivity Timeout- Activate + MGW-->>G(MSC) - S: Inactivity Timeout- ActivateAck +``` + +The diagram shows a sequence of messages between a G(MSC) - S and an MGW. The G(MSC) - S sends an 'Inactivity Timeout- Activate' message to the MGW, and the MGW responds with an 'Inactivity Timeout- ActivateAck' message. + +Sequence diagram for Inactivity Timeout - Activate procedure + +**Figure 10.15.1: Inactivity Timeout - Activate** + +Upon receipt of an inactivity timeout notification from the MGW via the Inactivity Timeout -Indication procedure, the (G)MSC server shall send a reply to the MGW. If the MGC has failed, the MGW will not receive a reply. + +![Sequence diagram for Inactivity Timeout - Indication procedure](01141eb99b707de5aead56f84afe3b1f_img.jpg) + +``` +sequenceDiagram + participant G(MSC) - S + participant MGW + MGW->>G(MSC) - S: Inactivity Timeout - Indication + G(MSC) - S->>MGW: Inactivity Timeout - Indication Ack +``` + +The diagram shows a sequence of messages between a G(MSC) - S and an MGW. The MGW sends an 'Inactivity Timeout - Indication' message to the G(MSC) - S, and the G(MSC) - S responds with an 'Inactivity Timeout - Indication Ack' message. + +Sequence diagram for Inactivity Timeout - Indication procedure + +**Figure 10.15.2: Inactivity Timeout - Indication** + +If no Inactivity Timeout – Indication Ack reply is received, the MGW shall consider the (G)MSC to have failed. The MGW may then attempt to recontact its controlling (G)MSC by performing MGW Communication UP. If not successful, the MGW may then attempt to register to a new (G)MSC. + +## 10.16 Hanging termination detection + +Whenever requesting new ephemeral bearer terminations, the (G)MSC shall request the MGW to periodically report termination heartbeat indications to detect hanging context and termination in the MGW that may result e.g. from a loss of communication between the MSC-S and the MGW. This may also be done when requesting TDM terminations, though alternative means exist for the (G)MSC to detect hanging TDM terminations, e.g. via receipt of the error #433 when seizing the termination. + +When the (G)MSC server receives a termination heartbeat notification from the MGW via the Termination heartbeat - Indication procedure, the (G)MSC shall return a Termination heartbeat –Indication Ack (without an error) if the context id / termination identity combination exists in the (G)MSC. If it does not exist, the (G)MSC shall return an error and shall correct the mismatch, e.g. by requesting the MGW to subtract the indicated termination and to clear any associated context. + +![Sequence diagram showing Termination heartbeat - Indication messages between (G)MSGS and MGW.](88b0f3f4393228e9ea4d6542aef7c399_img.jpg) + +A sequence diagram illustrating the exchange of Termination heartbeat - Indication messages between a (G)MSGS and an MGW. The (G)MSGS is on the left and the MGW is on the right. The first message is a Termination heartbeat - Indication sent from the MGW to the (G)MSGS. The second message is a Termination heartbeat - Indication Aek sent from the (G)MSGS to the MGW. + +``` +sequenceDiagram + participant (G)MSGS + participant MGW + Note right of MGW: Termination heartbeat - Indication + MGW->>(G)MSGS: Termination heartbeat - Indication + Note left of (G)MSGS: Termination heartbeat - Indication Aek + (G)MSGS->>MGW: Termination heartbeat - Indication Aek +``` + +Sequence diagram showing Termination heartbeat - Indication messages between (G)MSGS and MGW. + +Figure 10.16.1: Termination heartbeat – Indication + +# 11 Identities + +## 11.1 Bearer Address and Binding Reference + +The Bearer Address is exchanged on the Nc and Mc interfaces to identify the termination point of the bearer control signalling within the peer Media Gateway. + +A Binding Reference is an identity, unique within the scope of one bearer control function, which identifies a bearer network connection. This information is exchanged on the Nc and Mc interfaces. The bearer control function is identified by the Bearer Address. + +## 11.2 MGW-Id + +The Media Gateway Identity (MGW-Id) is information sent on the Nc interface to aid Media Gateway selection by the succeeding/preceding node. + +The MGW-Id is bearer independent and it can be translated into a signalling address towards the appropriate MGW. + +## 11.3 (G)MSC server Address + +The (G)MSC server Address defines the signalling address associated with the (G)MSC server that is used to interact with the Media Gateway over the Mc interface. This is a unique address in the network service supplier domain. + +# 12 Operational Aspects + +## 12.1 Charging + +No impacts. + +# 13 Interactions with Other Services + +NOTE 1: All message sequence charts in this clause are informative examples. + +NOTE 2: The continuity indication in the IAM is not used to indicate that a continuity check will be performed on the current leg of the call, but it is used to indicate that a Continuity message can be expected as a result of a continuity check on a preceding ISUP circuit, or establishment of a preceding bearer connection. + +## 13.1 Enhanced Multi-Level Precedence and Pre-emption service (eMLPP) + +No impact. + +## 13.2 Call Deflection Service + +The procedures specified in 3GPP TS 23.072 [9] for the Call Deflection supplementary service shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +### 13.2.1 MGW selection and incoming side bearer establishment + +The MGW selected for the mobile terminating call is used. The incoming side bearer has already been established by the mobile terminating call procedures. + +### 13.2.2 IU/A-interface release + +If the call deflection request from a served subscriber is accepted the call towards the served mobile subscriber shall be released as described in the clause for call clearing. + +### 13.2.3 Notification to the Calling Subscriber + +If the served mobile subscriber has requested that the calling subscriber shall receive a notification about the call forwarding, a notification is sent to the calling party. If the notification is implemented using intermediate tones or announcements the MSC server requests the MGW to play an announcement/tone to the calling party, as described in clause 14.6, before establishing the call to the forwarded-to subscriber. + +### 13.2.4 Initial addressing + +The call towards the deflected-to subscriber is established as for basic call. If out-of-band transcoder control is applied for a speech call, it shall be performed in accordance with 3GPP TS 23.153 [3]. After the possible generation of in-band information has been completed the MSC server shall indicate in the IAM that forward or backward bearer establishment is to be used. The MSC server shall indicate in the IAM that no Continuity message will follow since the incoming bearer has already been established. + +The MGW-id can be provided to the succeeding node in the IAM. + +### 13.2.5 Establishment of bearer towards the forwarded-to subscriber + +The bearer establishment towards the forwarded-to subscriber is performed as described for the mobile originating call, network side bearer establishment, using either forward or backward bearer establishment. The MSC server also requests the MGW to both-way through-connect the bearer. + +### 13.2.6 Failure handling in MSC server + +The failures are handled as described for the basic mobile originating call. + +### 13.2.7 Example + +Figure 13.1 shows the network model for call deflection. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. Note that for a TDM access case there is no separation of call and bearer control signalling. The MSC server replaces the bearer termination for the served mobile subscriber ( $T_B$ ) with the bearer termination for the deflected-to subscriber ( $T_C$ ) in an existing context in the MGW. The bearer termination $T_A$ is used for the bearer towards the preceding MGW (calling subscriber). + +![Figure 13.1: Call deflection (Network model). The diagram shows two network states: 'Before CD:' and 'After CD:'. In 'Before CD:', an MSC-S is connected to an MGW (with ports T_A and T_B and context CTX_AB), which is connected to an RNC/BSC. A dashed green line represents a call path from an external source to the RNC/BSC. In 'After CD:', the call path is deflected, and the dashed green line is shown only between the external source and the MSC-S.](d0abac95583b52a3b35f74a215567334_img.jpg) + +Figure 13.1: Call deflection (Network model). The diagram shows two network states: 'Before CD:' and 'After CD:'. In 'Before CD:', an MSC-S is connected to an MGW (with ports T\_A and T\_B and context CTX\_AB), which is connected to an RNC/BSC. A dashed green line represents a call path from an external source to the RNC/BSC. In 'After CD:', the call path is deflected, and the dashed green line is shown only between the external source and the MSC-S. + +Figure 13.1: Call deflection (Network model) + +Figure 13.2 shows the message sequence example for the call deflection with a possible notification to the calling party using an announcement. In the example, after the call and the bearer towards the access side have been released the MSC server requests the MGW to remove the bearer termination for the served mobile subscriber, and optionally requests the MGW to play an announcement and to notify the announcement completion. The MSC server shall request the establishment of the call towards the deflected-to subscriber after the possible announcement has completed. + +![Figure 13.2: Call deflection (message sequence chart). The sequence chart shows interactions between MSC-S, MGW, RNC/BSC, and UE. It is divided into three main phases: 'Mobile terminating call and bearer establishment', 'Call and bearer release', and 'Outgoing call and bearer establishment'. During the release phase, the MSC-S sends a SUB.request (T_B) to the MGW, which responds with a SUB.reply (T_B). A 'Play announcement (T_A)' is then performed by the MGW, with a 'Call Progress' message sent to the UE. A bracket labeled 'OR1: Y' indicates a notification to the calling subscriber is required.](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg) + +Figure 13.2: Call deflection (message sequence chart). The sequence chart shows interactions between MSC-S, MGW, RNC/BSC, and UE. It is divided into three main phases: 'Mobile terminating call and bearer establishment', 'Call and bearer release', and 'Outgoing call and bearer establishment'. During the release phase, the MSC-S sends a SUB.request (T\_B) to the MGW, which responds with a SUB.reply (T\_B). A 'Play announcement (T\_A)' is then performed by the MGW, with a 'Call Progress' message sent to the UE. A bracket labeled 'OR1: Y' indicates a notification to the calling subscriber is required. + +NOTE: OR1: Notification to calling subscriber required (Y:yes N:no) + +Figure 13.2: Call deflection (message sequence chart) + +## 13.3 Line identification Services + +### 13.3.1 Calling Line Identification Presentation (CLIP) + +No impact. + +### 13.3.2 Calling Line Identification Restriction (CLIR) + +No impact. + +### 13.3.3 Connected Line Identification Presentation (COLP) + +No impact. + +### 13.3.4 Connected Line Identification Restriction (COLR) + +No impact. + +## 13.4 Call Forwarding Services + +### 13.4.1 Call Forwarding Unconditional (CFU) + +The procedures specified in 3GPP TS 23.082 [12] for the Call Forwarding Unconditional supplementary service shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +#### 13.4.1.1 MGW selection + +If in-band information is to be provided to the calling subscriber the GMSC server shall select the MGW before providing the in-band information. The MGW selection can be based on a possibly received MGW-Id from the preceding node. + +If in-band information is to not to be provided to the calling subscriber the GMSC server shall select the MGW for the bearer as described for the basic mobile terminating call. + +#### 13.4.1.2 Incoming side bearer establishment + +The incoming side bearer establishment is handled in the GMSC server as described for the mobile terminating call using either forward or backward bearer establishment. + +#### 13.4.1.3 Notification to the Calling Subscriber + +If the served mobile subscriber has requested that the calling subscriber shall receive a notification about the call forwarding, a notification is sent to the calling party. If the notification is implemented using intermediate tones or announcements the GMSC server requests the MGW to play an announcement/tone to the calling party, as described in clause 14.6, before establishing the call to the forwarded-to subscriber. + +#### 13.4.1.4 Initial addressing + +If the incoming call is to be forwarded without being offered to the served mobile subscriber the call towards the forwarded-to subscriber is established as for a basic call. If out-of-band transcoder control is applied for a speech call, it shall be performed in accordance with 3GPP TS 23.153 [3]. After the possible generation of in-band information has been completed the initial addressing towards the forwarded-to subscriber is performed as described for the basic mobile terminating call indicating either forward or backward bearer establishment. + +#### 13.4.1.5 Establishment of bearer towards the forwarded-to subscriber + +The bearer establishment towards the forwarded-to subscriber is performed as described for the mobile originating call, network side bearer establishment, using either forward or backward bearer establishment. The GMSC server also requests the MGW to both-way through-connect the bearer. + +#### 13.4.1.6 Confirmation of bearer establishment + +The confirmation of the bearer establishment is handled as described for the basic mobile terminating call. + +#### 13.4.1.7 Failure handling in GMSC server + +The failures are handled as described for the basic mobile terminating call. + +#### 13.4.1.8 Example + +Figure 13.3 shows the network model for call forwarding unconditional. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. The GMSC server seizes one context with two bearer terminations in the MGW. The bearer termination $T_A$ is used for the bearer towards the preceding MGW (calling subscriber) and the bearer termination $T_C$ is used for the bearer towards the succeeding MGW (forwarded-to subscriber). + +![Figure 13.3: CFU (Network model)](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) + +The diagram illustrates the network model for call forwarding unconditional (CFU) in two states: 'Before CFU:' and 'After CFU:'. In the 'Before CFU:' state, a GMSC-S (Gateway Mobile Switching Center Server) is shown with a dotted line (bearer) entering from the left and a squared line (call control signalling) exiting to the right. In the 'After CFU:' state, the GMSC-S is connected via a squared line to an MGW (Media Gateway). The MGW has two bearer terminations, $T_A$ and $T_C$ , labeled 'CTXAC'. A dotted line enters the MGW from the left, terminates at $T_A$ , and another dotted line originates from $T_C$ and exits to the right. + +Figure 13.3: CFU (Network model) + +Figure 13.3: CFU (Network model) + +Figure 13.4 shows the message sequence example for the call forwarding unconditional with a possible notification to the calling party using an announcement. In the example the GMSC server optionally requests the MGW to play an announcement and to notify the announcement completion, after the bearer to the incoming side has been established. When the possible announcement has completed the GMSC server requests the establishment of the call and the bearer towards the forward-to subscriber. + +![Figure 13.4: CFU (message sequence chart)](fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg) + +The message sequence chart shows the interaction between a GMSC-S and an MGW. The sequence of events is as follows: + + +- Incoming call and bearer establishment:** A message from the MGW to the GMSC-S. +- HLR interrogation:** A message from the GMSC-S to the MGW. +- Address Complete:** A message from the GMSC-S to the left (outward). +- Play Announcement ( $T_A$ ):** A message from the GMSC-S to the MGW. This step is enclosed in a bracket indicating it is optional. +- Outgoing call and bearer establishment:** A message from the GMSC-S to the MGW. + +Figure 13.4: CFU (message sequence chart) + +Figure 13.4: CFU (message sequence chart) + +### 13.4.2 Call Forwarding on mobile subscriber Busy (CFB) + +The procedures specified in 3GPP TS 23.082 [12] for the Call Forwarding on Busy supplementary service shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +#### 13.4.2.1 Network Determined User Busy (NDUB) + +If the mobile is Network Determined User Busy the incoming call for the specified basic service(s) shall be forwarded without being offered to the served mobile subscriber. + +##### 13.4.2.1.1 MGW selection + +The MSC server shall select an MGW for the bearer connection either before sending the IAM or after receiving the Bearer Information message. If the MSC server received an MGW-id from the preceding node and/or from the succeeding node, then it may use one of them for the MGW selection. + +If in-band information is to be provided to the calling subscriber the MSC server shall select the MGW before providing the in-band information. The MGW selection can be based on a possibly received MGW-Id from the preceding node. + +NOTE: As an implementation option, if there is no need for the MSC server to manipulate the bearer, the MSC server may only perform call control signalling without any associated MGW. In that case the bearer related information shall be provided transparently through the MSC server. + +##### 13.4.2.1.2 Incoming side bearer establishment + +The incoming side bearer establishment is handled in the MSC server as described for the mobile terminating call using either forward or backward bearer establishment. The incoming side bearer establishment can take place either before or after the detection of NDUB condition. + +##### 13.4.2.1.3 Notification to the calling subscriber + +If the served mobile subscriber has requested that the calling subscriber shall receive a notification about the call forwarding, a notification is sent to the calling party. If the notification is implemented using intermediate tones or announcements the MSC server requests the MGW to play an announcement/tone to the calling party, as described in clause 14.6, before establishing the call to the forwarded-to subscriber. + +##### 13.4.2.1.4 Initial addressing + +The call towards the forwarded-to subscriber is established as for basic call. If out-of-band transcoder control is applied for a speech call, it shall be performed in accordance with 3GPP TS 23.153 [3]. In-band information may be played to the calling subscriber. + +If no in-band information is to be played to the calling subscriber, in order to withhold the call completion until the establishment of the bearer is complete. + +The MSC server shall indicate in the IAM that the Continuity message will follow from the preceding node if either of the following conditions is satisfied before sending the IAM: + +1. The incoming IAM indicated that the Continuity message will follow, but no Continuity message has been received, or +2. The incoming side bearer has not been established. + +If the MGW is selected at an early stage the MGW-id can be provided to the succeeding node in the IAM. + +##### 13.4.2.1.5 Establishment of bearer towards the forwarded-to subscriber + +The bearer establishment towards the forwarded-to subscriber is performed as described for mobile originating call, network side bearer establishment, using either forward or backward bearer establishment. The MSC server also requests the MGW to both-way through-connect the bearer. + +##### 13.4.2.1.5 Confirmation of bearer establishment + +If the outgoing IAM indicated that the Continuity message will follow, the Continuity message is sent when both of the following conditions are satisfied: + +1. Either: + - 1 a. The incoming IAM indicated that the Continuity message will follow, and a Continuity message has been received, or + - 2 b. The incoming IAM indicated that no Continuity message will follow. +2. Either: + - 3 a. The MSC server has selected an MGW, and a notification indicating successful completion of the incoming side bearer set-up has been received from the MGW using the Bearer Established procedure, or + - 4 b. MGW selection is not required for this call. + +##### 13.4.2.1.6 Failure handling in MSC server + +The failures are handled as described for the basic mobile originating call. + +##### 13.4.2.1.7 Example + +Figure 13.5 shows the network model for call forwarding busy (network determined user busy). The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. The MSC server seizes one context with two bearer terminations in the MGW. The bearer termination $T_A$ is used for the bearer towards the preceding MGW (calling subscriber) and the bearer termination $T_C$ is used for the bearer towards the succeeding MGW (forwarded-to subscriber). + +![Figure 13.5: CFB; NDUB (Network model). The diagram shows two states: 'Before CFB (NDUB)' and 'After CFB (NDUB)'. In the 'Before' state, a green dotted line (bearer) enters an MSC-S box from the left. In the 'After' state, the green dotted line enters the MSC-S box from the left, and a blue squared line (call control signalling) connects the MSC-S box to an MGW box below it. The MGW box has two bearers: a red dotted line labeled 'T_A' entering from the left and a red dotted line labeled 'T_C' exiting to the right. The MGW box also contains a label 'CTXAc'.](af6be343f0c0a8f155f965dcf337b8af_img.jpg) + +Figure 13.5: CFB; NDUB (Network model). The diagram shows two states: 'Before CFB (NDUB)' and 'After CFB (NDUB)'. In the 'Before' state, a green dotted line (bearer) enters an MSC-S box from the left. In the 'After' state, the green dotted line enters the MSC-S box from the left, and a blue squared line (call control signalling) connects the MSC-S box to an MGW box below it. The MGW box has two bearers: a red dotted line labeled 'T\_A' entering from the left and a red dotted line labeled 'T\_C' exiting to the right. The MGW box also contains a label 'CTXAc'. + +Figure 13.5: CFB; NDUB (Network model) + +Figure 13.6 shows the message sequence example for the call forwarding busy (network determined user busy) using a possible announcement. In the example the MSC server optionally requests the MGW to play an announcement and to notify the announcement completion, after the bearer to the incoming side has been established. When the possible announcement has been completed the MSC server requests the establishment of the call towards the forward-to subscriber. + +![Sequence diagram for CFB (NDUB) showing interactions between MSC-S, MGW, RNC/BSC, and UE. The process involves an incoming call, bearer establishment, NDUB detection, announcement playing, and subsequent outgoing call establishment.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant MSC-S + participant MGW + participant RNC/BSC + participant UE + + Note left of MGW: Incoming Call and Bearer Establishment + Note left of MGW: NDUB + MSC-S->>: Address Complete + Note right of MGW: Play Announcement (TA) + Note right of MGW: OR1: Y + MGW->>RNC/BSC: Notification + Note right of MGW: Outgoing Call and Bearer Establishment + +``` + +Sequence diagram for CFB (NDUB) showing interactions between MSC-S, MGW, RNC/BSC, and UE. The process involves an incoming call, bearer establishment, NDUB detection, announcement playing, and subsequent outgoing call establishment. + +NOTE: OR1: Notification to forwarding subscriber required (Y: yes N: no) + NDUB: Network Determined User Busy + +**Figure 13.6: CFB (NDUB)** + +#### 13.4.2.2 User Determined User Busy (UDUB) + +##### 13.4.2.2.1 MGW selection + +The MGW selected for the mobile terminating call is used, if already selected by the mobile terminating call procedures. + +The MSC server selects an MGW for the bearer either before sending the IAM or after receiving the Bearer Information message. If the MSC server received an MGW-id from the preceding node and/or from the succeeding node, then it may use one of them for the MGW selection. + +If in-band information is to be provided to the calling subscriber the MSC server shall select the MGW before providing the in-band information. The MGW selection can be based on a possibly received MGW-Id from the preceding node. + +NOTE: As an implementation option, if there is no need for the MSC server to manipulate the bearer, the MSC server may only perform call control signalling without any associated MGW. In that case the bearer related information shall be provided transparently through the MSC server. + +##### 13.4.2.2.2 Incoming side bearer establishment + +For bearer establishment, the sending of bearer information is handled in the MSC server as described for the basic mobile terminating call indicating either forward or backward bearer establishment. The incoming side bearer establishment can take place either before or after the detection of UDUB condition. + +##### 13.4.2.2.3 IU/A-interface release + +If the mobile is not Network Determined User Busy (NDUB as defined in GSM TS 02.01) the incoming call is offered (as a normal or waiting call) to the served mobile subscriber. If the mobile indicating "User Busy" subsequently releases the call, the call towards the served mobile subscriber is released as described in the clause for call clearing. + +NOTE: The MSC server orders the MGW to remove the bearer termination towards the served mobile subscriber only in the case where the radio resources had already been allocated in the MGW (bullet 1 in figure 13.8). + +##### 13.4.2.2.4 Notification to the Calling Subscriber + +If the served mobile subscriber has requested that the calling subscriber shall receive a notification about the call forwarding, a notification is sent to the calling party. If the notification is implemented using intermediate tones or announcements the MSC server requests the MGW to play an announcement/tone to the calling party as described in clause 14.6 before establishing the call to the forwarded-to subscriber. + +##### 13.4.2.2.5 Initial addressing + +The call towards the forwarded-to subscriber is established as basic call. If out-of-band transcoder control is applied for a speech call, it shall be performed in accordance with 3GPP TS 23.153 [3]. In-band information may be played to the calling subscriber. + +If no in-band information is to be played to the calling subscriber, in order to withhold the call completion until the establishment of the bearer is complete. The MSC server shall indicate in the IAM that the Continuity message will follow from the preceding node if either of the following conditions is satisfied before sending the IAM: + +1. The incoming IAM indicated that the Continuity message will follow, but no Continuity message has been received, or +2. The incoming side bearer has not been established. + +If the MGW is selected at an early stage the MGW-id can be provided to the succeeding node in the IAM. + +##### 13.4.2.2.6 Establishment of bearer towards the forwarded-to subscriber + +The bearer establishment towards the forwarded-to subscriber is performed as described for the mobile originating call, network side bearer establishment, using either forward or backward bearer establishment. The MSC server also requests the MGW to both-way through-connect the bearer. + +##### 13.4.2.2.7 Confirmation of bearer establishment + +If the outgoing IAM indicated that the Continuity message will follow, the Continuity message is sent when both of the following conditions are satisfied: + +1. Either: + - 5 a. The incoming IAM indicated that the Continuity message will follow, and a Continuity message has been received from the preceding node (bullet 8 in figure 6.6), or + - 6 b. The incoming IAM indicated that no Continuity message will follow; +2. Either: + - 7 a. The MSC server has selected an MGW, and a notification of successful bearer establishment in the incoming side has been received from the MGW (bullet 7 in figure 6.6), or + - 8 b. MGW selection is not required for this call. + +##### 13.4.2.2.8 Failure handling in MSC server + +The failures are handled as described for the basic mobile originating call. + +##### 13.4.2.2.9 Example + +Figure 13.7 shows the network model for call forwarding busy (user determined user busy). The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. Note that + +for a TDM access case there is no separation of call and bearer signalling. The MSC server replaces the bearer termination for the served mobile subscriber (TB) with the bearer termination for the forwarded-to subscriber (TC) in an existing context in the MGW. The bearer termination TA is used for the bearer towards the preceding MGW (calling subscriber). + +![Figure 13.7: CFB; UDUB (Network model). The diagram illustrates the network configuration before and after Call Forwarding Busy (User Determined User Busy). + 'Before CFB (UDUB)': An MSC-S is connected via a blue control line to an MGW. Inside the MGW, there is a context CTX_AB with two terminations: T_A and T_B. T_A is connected to a preceding network element via a red dotted bearer line. T_B is connected to an RNC/BSC via a red dotted bearer line. A green dashed signaling line also connects the MSC-S to the RNC/BSC. + 'After CFB (UDUB)': The MSC-S remains connected to the MGW. In the MGW context CTX_AB, termination T_B has been replaced by T_C. T_A remains connected to the preceding network element. T_C is now connected to a subsequent network element (indicated by red dots). The green signaling line from MSC-S now extends towards the new destination.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +``` + + graph LR + subgraph Before_CFB + MSCS1[MSC-S] -- signaling --- RNC[RNC/BSC] + MSCS1 -- control --- MGW1[MGW: CTX_AB] + Prev1((...)) -. bearer .- TA1[T_A] + TA1 --- TB1[T_B] + TB1 -. bearer .- RNC + end + subgraph After_CFB + MSCS2[MSC-S] -- signaling --- Next2((...)) + MSCS2 -- control --- MGW2[MGW: CTX_AB] + Prev2((...)) -. bearer .- TA2[T_A] + TA2 --- TC2[T_C] + TC2 -. bearer .- Next2 + end + +``` + +Figure 13.7: CFB; UDUB (Network model). The diagram illustrates the network configuration before and after Call Forwarding Busy (User Determined User Busy). + 'Before CFB (UDUB)': An MSC-S is connected via a blue control line to an MGW. Inside the MGW, there is a context CTX\_AB with two terminations: T\_A and T\_B. T\_A is connected to a preceding network element via a red dotted bearer line. T\_B is connected to an RNC/BSC via a red dotted bearer line. A green dashed signaling line also connects the MSC-S to the RNC/BSC. + 'After CFB (UDUB)': The MSC-S remains connected to the MGW. In the MGW context CTX\_AB, termination T\_B has been replaced by T\_C. T\_A remains connected to the preceding network element. T\_C is now connected to a subsequent network element (indicated by red dots). The green signaling line from MSC-S now extends towards the new destination. + +**Figure 13.7: CFB; UDUB (Network model)** + +Figure 13.8 shows the message sequence example for the call forwarding busy (user determined user busy) with a possible notification to the calling party using an announcement. In the example, after the call and the bearer towards the access have been released the MSC server requests the MGW to remove the bearer termination for the served mobile subscriber, optionally requests the MGW to play an announcement and to notify the announcement completion. After the possible announcement has been completed the MSC server requests the establishment of the call towards the forward-to subscriber. + +![Sequence diagram for CFB (UDUB) showing call flow between MSC-S, MGW, RNC/BSC, and UE. The diagram illustrates the process of call forwarding on no reply, including normal call establishment, timer expiry, call release, and subsequent outgoing call establishment.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +The sequence diagram illustrates the interaction between four entities: MSC-S, MGW, RNC/BSC, and UE. The process begins with a green bar labeled "Normal call and bearer establishment". Following this, a green box labeled "Expiry of no reply condition timer" appears on the MSC-S lifeline. A green bar labeled "Call and bearer release" spans across the MGW, RNC/BSC, and UE lifelines. The sequence of messages is as follows: + + +- Context ( $C_{AB}$ ) is sent from MSC-S to MGW. +- A circled number 1 is on the MSC-S lifeline. +- Context ( $C_{AB}$ ) is sent from MGW to MSC-S. +- SUB.request ( $T_B$ ) is sent from MGW to MSC-S. +- SUB.reply ( $T_B$ ) is sent from MSC-S to MGW. +- OR1: Y is sent from MSC-S to MGW. +- A green box labeled "Play Announcement ( $T_A$ )" is shown between MSC-S and MGW, with a bracket indicating the duration. +- OR2: Y is sent from MSC-S to MGW. +- Notification is sent from MGW to UE. +- A final green bar labeled "Outgoing call and bearer establishment" spans across the MGW, RNC/BSC, and UE lifelines. +- An arrow labeled "Call Progress" points left from the MSC-S lifeline. + +Sequence diagram for CFB (UDUB) showing call flow between MSC-S, MGW, RNC/BSC, and UE. The diagram illustrates the process of call forwarding on no reply, including normal call establishment, timer expiry, call release, and subsequent outgoing call establishment. + +NOTE: OR1: Notification to calling subscriber required (Y:yes N:no) + +Figure 13.8: CFB (UDUB) + +### 13.4.3 Call Forwarding on No Reply (CFNRy) + +The procedures specified in 3GPP TS 23.082 [12] for the Call Forwarding on No Reply supplementary service shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +#### 13.4.3.1 MGW selection and incoming side bearer establishment + +The MGW selected for the mobile terminating call is used. The incoming side bearer has already been established by the mobile terminating call procedures. + +#### 13.4.3.2 IU/A-interface release + +If the call is not answered within the period defined by the no reply condition timer the call towards the served mobile subscriber will be released as described in the clause for call clearing. + +#### 13.4.3.3 Notification to the Calling Subscriber + +If the served mobile subscriber has requested that the calling subscriber shall receive a notification about the call forwarding, a notification is sent to the calling party. If the notification is implemented using intermediate tones or announcements the MSC server requests the MGW to play an announcement/tone to the calling party, as described in clause 14.6, before establishing the call to the forwarded-to subscriber. + +#### 13.4.3.4 Initial addressing + +The call towards the forwarded-to subscriber is established as a basic call. If out-of-band transcoder control is applied for a speech call, it shall be performed in accordance with 3GPP TS 23.153 [3]. After the possible generation of in-band information has been completed (bullet 2 in figure 13.10) the MSC server shall indicate in the IAM that no Continuity message will follow from the preceding node because the incoming side bearer has already been established. + +The MGW-id can be provided to the succeeding node in the IAM. + +#### 13.4.3.5 Establishment of bearer towards the forwarded-to subscriber + +The bearer establishment towards the forwarded-to subscriber is performed as described for the mobile originating call, network side bearer establishment, using either forward or backward bearer establishment. The MSC server also requests the MGW to both-way through-connect the bearer. + +#### 13.4.3.6 Failure handling in MSC server + +The failures are handled as described for the basic mobile originating call. + +#### 13.4.3.7 Example + +Figure 13.9 shows the network model for call forwarding no reply. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. Note that for a TDM access case there is no separation of call and bearer control signalling. The MSC server replaces the bearer termination for the served mobile subscriber ( $T_B$ ) with the bearer termination for the forwarded-to subscriber ( $T_C$ ) in an existing context in the MGW. The bearer termination $T_A$ is used for the bearer towards the preceding MGW (calling subscriber). + +![Figure 13.9: CFNRy (Network model). The diagram shows two network states: 'Before CFNRy:' and 'After CFNRy:'. In 'Before CFNRy:', an MSC-S is connected to an MGW (labeled CTX_AB) via a solid blue line. The MGW is connected to an RNC/BSC via a dotted red line. A dotted green line (bearer) goes from the MSC-S to the RNC/BSC. A squared green line (call control) goes from the MSC-S to the MGW. In 'After CFNRy:', the MSC-S is connected to the MGW via a solid blue line. The MGW is connected to the RNC/BSC via a dotted red line. A dotted green line (bearer) goes from the MSC-S to the MGW. A squared green line (call control) goes from the MSC-S to the MGW. The MGW has three bearers: T_A (dotted red line to the RNC/BSC), T_B (dotted red line from the RNC/BSC), and T_C (dotted green line from the MSC-S).](9b62a616c7a1097c5da57f001ab6dd64_img.jpg) + +Figure 13.9: CFNRy (Network model). The diagram shows two network states: 'Before CFNRy:' and 'After CFNRy:'. In 'Before CFNRy:', an MSC-S is connected to an MGW (labeled CTX\_AB) via a solid blue line. The MGW is connected to an RNC/BSC via a dotted red line. A dotted green line (bearer) goes from the MSC-S to the RNC/BSC. A squared green line (call control) goes from the MSC-S to the MGW. In 'After CFNRy:', the MSC-S is connected to the MGW via a solid blue line. The MGW is connected to the RNC/BSC via a dotted red line. A dotted green line (bearer) goes from the MSC-S to the MGW. A squared green line (call control) goes from the MSC-S to the MGW. The MGW has three bearers: T\_A (dotted red line to the RNC/BSC), T\_B (dotted red line from the RNC/BSC), and T\_C (dotted green line from the MSC-S). + +Figure 13.9: CFNRy (Network model) + +Figure 13.10 shows the message sequence example for the call forwarding on no reply with a possible announcement. In the example, after the call and the bearer towards the access have been released the MSC server requests the MGW to remove the bearer termination for the served mobile subscriber, and optionally requests the MGW to play an announcement and to notify the announcement completion. When the possible announcement has been completed the MSC server requests the establishment of the call towards the forward-to subscriber. + +![Sequence diagram for CFNRy (Call Forwarding on No Reply). Lifelines: MSC-S, MGW, RNC/BSC, UE. The process starts with 'Normal call and bearer establishment'. A timer 'Expiry of no reply condition timer' expires at the MSC-S. The MSC-S sends a 'SUB.request (T_B)' to the MGW, which responds with 'SUB.reply (T_B)'. The MSC-S then checks 'OR1: Y'. If yes, it sends 'Call Progress' to the RNC/BSC and initiates 'Play Announcement (T_A)'. After the announcement, it checks 'OR2: Y'. If yes, it sends a 'Notification' to the UE and initiates 'Outgoing Call and Bearer Establishment'.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant MSC-S + participant MGW + participant RNC/BSC + participant UE + + Note over MSC-S, UE: Normal call and bearer establishment + Note left of MSC-S: Expiry of no reply condition timer + Note over MSC-S, UE: Call and bearer release + MSC-S->>MGW: SUB.request (TB) + MGW-->>MSC-S: SUB.reply (TB) + Note left of MSC-S: Context (CAB) + Note left of MSC-S: Context (CAB) + Note left of MSC-S: OR1: Y + Note left of MSC-S: Call Progress + Note left of MSC-S: Play Announcement (TA) + Note left of MSC-S: OR2: Y + Note left of MSC-S: Notification + Note over MSC-S, UE: Outgoing Call and Bearer Establishment + +``` + +Sequence diagram for CFNRy (Call Forwarding on No Reply). Lifelines: MSC-S, MGW, RNC/BSC, UE. The process starts with 'Normal call and bearer establishment'. A timer 'Expiry of no reply condition timer' expires at the MSC-S. The MSC-S sends a 'SUB.request (T\_B)' to the MGW, which responds with 'SUB.reply (T\_B)'. The MSC-S then checks 'OR1: Y'. If yes, it sends 'Call Progress' to the RNC/BSC and initiates 'Play Announcement (T\_A)'. After the announcement, it checks 'OR2: Y'. If yes, it sends a 'Notification' to the UE and initiates 'Outgoing Call and Bearer Establishment'. + +NOTE: OR1: Notification to calling subscriber required (Y:yes N:no) + +Figure 13.10: CFNRy (message sequence chart) + +### 13.4.4 Call Forwarding on mobile subscriber Not Reachable (CFNRc) + +The procedures specified in 3GPP TS 23.082 [12] for the Call Forwarding on Not Reachable supplementary service shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +#### 13.4.4.1 Rerouting by HLR + +The same handling as for Call Forwarding Unconditional applies. + +#### 13.4.4.2 Rerouting by VLR + +If the mobile is not reachable the incoming call for the specified basic service(s) will be forwarded without being offered to the served mobile subscriber. + +##### 13.4.4.2.1 MGW selection + +If in-band information is to be provided to the calling subscriber the MSC server shall select the MGW before providing the in-band information. The MGW selection can be based on a possibly received MGW-Id from the preceding node. + +NOTE: As an implementation option, if in-band information is not to be provided to the calling subscriber the MSC server may either perform call control without any associated MGW, or reserve resources from an MGW and request bearer establishment through that MGW. In the latter case the MSC server selects an MGW for the bearer either before sending the IAM or after receiving the Bearer Information message. If the MSC server received an MGW-Id from the preceding node and/or from the succeeding node, those can be used for the MGW selection. + +##### 13.4.4.2.2 Incoming side bearer establishment + +The incoming side bearer establishment is handled in the MSC server as described for the mobile terminating call, using either forward or backward bearer establishment. The incoming side bearer establishment can take place either before or after the detection of the not reachable condition. + +##### 13.4.4.2.3 Notification to the calling subscriber + +If the served mobile subscriber has requested that the calling subscriber shall receive a notification about the call forwarding, a notification is sent to the calling party. If the notification is implemented using intermediate tones or announcements the MSC server requests the MGW to play an announcement/tone to the calling party, as described in clause 14.6, before establishing the call towards the forwarded-to party. + +##### 13.4.4.2.4 Initial addressing + +The call towards the forwarded-to subscriber is established as a basic call. If out-of-band transcoder control is applied for a speech call, it shall be performed in accordance with 3GPP TS 23.153 [3]. In-band information may be played to the calling subscriber. + +If no in-band information is to be played to the calling subscriber, in order to withhold the call completion until the establishment of the bearer is complete the MSC server shall indicate in the IAM that the Continuity message will follow from the preceding node, if either of the following conditions is satisfied before sending the IAM: + +1. The incoming IAM indicated that the Continuity message will follow, but no Continuity message has been received, or +2. The incoming side bearer has not been established. + +If the MGW is selected at an early stage the MGW-id can be provided to the succeeding node in the IAM. + +##### 13.4.4.2.5 Establishment of bearer towards the forwarded-to subscriber + +The bearer establishment towards the forwarded-to subscriber is performed as described for mobile originating call, network side bearer establishment, using either forward or backward bearer establishment. The MSC server also requests the MGW to both-way through-connect the bearer. + +##### 13.4.4.2.6 Confirmation of bearer establishment + +If the outgoing IAM indicated that a Continuity message will follow, the Continuity message shall be sent when both of the following conditions are satisfied: + +1. Either: + - 9 a. The incoming IAM indicated that the Continuity message will follow, and a Continuity message has been received, or + - 10 b. The incoming IAM indicated that no Continuity message will follow. +2. Either: + - 11 a. The MSC server has selected an MGW, and a notification indicating successful completion of the incoming side bearer set-up has been received from the MGW using the Bearer Established procedure, or + +12 b. MGW selection is not required for this call. + +##### 13.4.4.2.7 Failure handling in MSC server + +The failures are handled as described for the basic mobile originating call. + +##### 13.4.4.2.8 Example + +Figure 13.11 shows the network model for call forwarding on not reachable. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. The MSC server seizes one context with two bearer terminations in the MGW. The bearer termination $T_A$ is used for the bearer towards the preceding MGW (calling subscriber) and the bearer termination $T_C$ is used for the bearer towards the succeeding MGW (forwarded-to subscriber). + +![Figure 13.11: CFNRc; Rerouting by VLR (Network model). The diagram shows two states: 'Before CFNRc:' and 'After CFNRc:'. In 'Before CFNRc:', an MSC-S is shown with a green dotted line (bearer) entering from the left and a green squared line (call control) exiting to the right. In 'After CFNRc:', the MSC-S is connected to an MGW. The MGW has two bearers: T_A (green dotted line) entering from the left and T_C (green dotted line) exiting to the right. The MGW also has a green squared line (call control) entering from the MSC-S and a green squared line (call control) exiting to the right.](1a85642ed2356d183ce598f2c8b3ee8b_img.jpg) + +Figure 13.11: CFNRc; Rerouting by VLR (Network model). The diagram shows two states: 'Before CFNRc:' and 'After CFNRc:'. In 'Before CFNRc:', an MSC-S is shown with a green dotted line (bearer) entering from the left and a green squared line (call control) exiting to the right. In 'After CFNRc:', the MSC-S is connected to an MGW. The MGW has two bearers: T\_A (green dotted line) entering from the left and T\_C (green dotted line) exiting to the right. The MGW also has a green squared line (call control) entering from the MSC-S and a green squared line (call control) exiting to the right. + +Figure 13.11: CFNRc; Rerouting by VLR (Network model) + +Figure 13.12 shows the message sequence example for the call forwarding on not reachable with a possible announcement. In the example the MSC server optionally requests the MGW to play an announcement and to notify the announcement completion, after the bearer to the incoming side has been established. When the possible announcement has been completed the MSC server requests the establishment of the call towards the forward-to subscriber. + +![Figure 13.12: CFNRc (Rerouting by VLR) (message sequence chart). The sequence chart shows four lifelines: MSC-S, MGW, RNC/BSC, and UE. The sequence of events is: 1. 'Incoming Call and Bearer Establishment' (MSC-S to MGW). 2. 'Mobile subscriber not reachable' (MGW to MSC-S). 3. 'Play Announcement (T_A)' (MSC-S to MGW). 4. 'Outgoing Call and Bearer Establishment' (MGW to RNC/BSC). 5. 'Address Complete' (MSC-S to the left).](d79d33da852cb7bca3e87b400a15c3e8_img.jpg) + +Figure 13.12: CFNRc (Rerouting by VLR) (message sequence chart). The sequence chart shows four lifelines: MSC-S, MGW, RNC/BSC, and UE. The sequence of events is: 1. 'Incoming Call and Bearer Establishment' (MSC-S to MGW). 2. 'Mobile subscriber not reachable' (MGW to MSC-S). 3. 'Play Announcement (T\_A)' (MSC-S to MGW). 4. 'Outgoing Call and Bearer Establishment' (MGW to RNC/BSC). 5. 'Address Complete' (MSC-S to the left). + +Figure 13.12: CFNRc (Rerouting by VLR) (message sequence chart) + +## 13.5 Call Waiting (CW) + +The procedures specified in 3GPP TS 23.083 [13] for the Call Waiting supplementary service shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. The following clauses assume subscriber A to be the served subscriber with the call waiting supplementary service, subscriber B to be the one who is engaged in a call with user A, subscriber C to be the one who has originated a call to subscriber A which causes the call waiting supplementary service to be invoked. + +### Call confirmation to the waiting call + +The MSC server shall, on reception of the call confirmation, select the MGW that will be used for the waiting call. The MSC server should select the MGW which is already in use for the active call. If out-of-band transcoder control is applied for the waiting speech call, it shall be performed in accordance with 3GPP TS 23.153 [3]. + +### Existing call on hold + +The clause "Hold request" in clause 13.6 applies. + +### Existing call released + +If the active call is disconnected while another call is waiting, the bearer termination towards the waiting party (C) as well as to the called party (A) is not removed. + +### Acceptance of waiting call + +If the mobile subscriber decides to accept the waiting call, it handles (according to 3GPP TS 23.083 [13]) the existing call as described in clause 13.5 (i.e. it either puts the call on hold or the call is released). When the MSC server receives the connect indication from subscriber A, if required the MSC server shall modify the access bearer as described in subclause 13.18.1. Finally, the MSC server shall connect the access side bearer termination to the previously created bearer termination of the remote party in the waiting call and modify the waiting call's bearer termination so that it is both-way through-connected. + +If a different MGW is selected for the incoming call, then a bearer from the new MGW (MGW2) shall be connected towards the old MGW (MGW1) before offering the call to the subscriber A. + +If out-of-band transcoder control is applied for the waiting speech call, it shall be performed in accordance with 3GPP TS 23.153[3]. + +### Waiting call released by calling subscriber (subscriber C) + +The respective resources already allocated at the selected MGW for the waiting call shall be released. + +### Example + +Figure 13.13 shows the network model for a waiting call at the serving MSC server/MGW. The "thick, squared" line represents the call control signalling for the existing call and, on the Iu interface, the already existing control plane toward the serving RNC. The "thin, squared" line represents the call control signalling for the waiting call. The "thick, dotted" line represents the bearer control signalling and the bearer for the existing call, whereas the "thin, dotted" line represents the ones for the waiting call. Note that for a TDM access there is no separation of call and bearer control signalling. + +NOTE: There shall be only one instance of bearer resource/bearer control signalling on the radio side. + +If the CW condition applies, the MSC server seizes a new context with one bearer termination, $T_C$ , in the MGW. $T_A$ and $T_B$ are the terminations of the already existing call. + +**Error:** + +22 + +**Error: Reference source not** + +![Figure 13.13: Call Wait (network model). The diagram is split into two parts: 'one MGW involved' and 'two MGWs involved'. In the 'one MGW involved' side, an RNC/BSC is connected to an MSC-S via a green dashed line. Below the MSC-S is a single MGW containing two contexts: CTX1(A-B) and CTX2(...-C). Red dotted lines connect the RNC/BSC to these contexts. Blue solid lines connect the MSC-S to the contexts. Signaling paths lead to 'B party' and 'C party'. In the 'two MGWs involved' side, the RNC/BSC is connected to MSC-S. There are two MGWs: MGW1 contains CTX1(A-B) and CTX2(...-C), while MGW2 contains CTX3(...-C). Similar green dashed, red dotted, and blue solid lines show the connectivity between RNC/BSC, MSC-S, and the contexts in the two MGWs leading to B and C parties.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +Figure 13.13: Call Wait (network model). The diagram is split into two parts: 'one MGW involved' and 'two MGWs involved'. In the 'one MGW involved' side, an RNC/BSC is connected to an MSC-S via a green dashed line. Below the MSC-S is a single MGW containing two contexts: CTX1(A-B) and CTX2(...-C). Red dotted lines connect the RNC/BSC to these contexts. Blue solid lines connect the MSC-S to the contexts. Signaling paths lead to 'B party' and 'C party'. In the 'two MGWs involved' side, the RNC/BSC is connected to MSC-S. There are two MGWs: MGW1 contains CTX1(A-B) and CTX2(...-C), while MGW2 contains CTX3(...-C). Similar green dashed, red dotted, and blue solid lines show the connectivity between RNC/BSC, MSC-S, and the contexts in the two MGWs leading to B and C parties. + +**Figure 13.13: Call Wait (network model)** + +### 13.5.1 Call Confirmation of the waiting call + +Figure 13.14 shows the sequence chart for the actions necessary within the bearer independent CS core network during call confirmation of the waiting call. Call and bearer establishment shall be as described for the mobile terminating call. When the MSC server receives the Alerting indication from the called subscriber (subscriber A), it shall apply the ringing tone to the waiting termination (TC). + +![Figure 13.14: Call Confirmation of the Waiting Call sequence diagram. The diagram shows vertical lifelines for UE, RNC/BSC, MSC-S, and MGW. 1. An 'active call A-B' is shown as a green horizontal bar across all entities. 2. A 'Call and Bearer establishment C ⇒ A' bar is shown between MSC-S and MGW. 3. MSC-S sends 'SETUP A-C' to UE. 4. UE sends 'CALL CONFIRMED A-C (A=busy)' to MSC-S. 5. UE sends 'ALERTING A-C' to MSC-S. 6. MSC-S and RNC/BSC exchange 'Context (C2)' signaling. 7. MSC-S sends 'MOD.request(TC)' to MGW. 8. MGW sends 'MOD.reply(TC)' to MSC-S. 9. MGW performs 'Apply Tone'. 10. MSC-S sends 'Address Complete' message outwards to the right.](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +Figure 13.14: Call Confirmation of the Waiting Call sequence diagram. The diagram shows vertical lifelines for UE, RNC/BSC, MSC-S, and MGW. 1. An 'active call A-B' is shown as a green horizontal bar across all entities. 2. A 'Call and Bearer establishment C ⇒ A' bar is shown between MSC-S and MGW. 3. MSC-S sends 'SETUP A-C' to UE. 4. UE sends 'CALL CONFIRMED A-C (A=busy)' to MSC-S. 5. UE sends 'ALERTING A-C' to MSC-S. 6. MSC-S and RNC/BSC exchange 'Context (C2)' signaling. 7. MSC-S sends 'MOD.request(TC)' to MGW. 8. MGW sends 'MOD.reply(TC)' to MSC-S. 9. MGW performs 'Apply Tone'. 10. MSC-S sends 'Address Complete' message outwards to the right. + +**Figure 13.14: Call Confirmation of the Waiting Call.** + +### 13.5.2 Acceptance of the Waiting Call + +Figure 13.15 shows the sequence chart for the actions necessary within the bearer independent CS core network for the acceptance of a waiting call. When the MSC server receives the Connect indication from the UE (subscriber A) (bullet 1 in figure 13.15), it shall request the MGW to disconnect subscriber C from the applied ringing tone (bullet 2 in figure 13.15) and move TA to the context of the waiting call (bullet 3 in figure 13.15). The MSC server then requests the MGW to change the through-connection of the termination TC so that it will be both way through-connected (bullet 4 in figure 13.15). + +![Sequence chart for the Acceptance of the Waiting Call. The diagram shows four lifelines: UE, RNC/BSC, MSC-S, and MGW. A green bar at the top indicates the state 'B-on hold, C-waiting'. The sequence of messages involves CONNECT, MOD.request, MOVE.request, and Answer.](d9c0a780cd22626253dab4aa41699e2f_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S + participant MGW + Note over UE, MGW: B-on hold, C-waiting + + UE->>MSC-S: CONNECT A-C + Note right of MSC-S: 1' + MSC-S->>MGW: Context-(C2) MOD.request(Tt) + Note right of MSC-S: 2' + Note right of MGW: Disconnect Tt from Announcement/Tone + MGW-->>MSC-S: Context-(C2) MOD.reply(Tt) + + MSC-S->>MGW: Context-(C2) MOVE.request(TA) + Note right of MSC-S: 3' + Note right of MGW: Move TA to C2 + MGW-->>MSC-S: Context-(C2) MOVE.reply(TA) + + MSC-S->>MGW: Context-(C2) MOD.request(T' c) + Note right of MSC-S: 4' + Note right of MGW: Change Tc's Flow direction to bothway + MGW-->>MSC-S: Context-(C2) MOD.reply(T' c) + + MSC-S->>UE: CONNECT-ACK A-C + Note right of MSC-S: 5' + MSC-S->>External: Answer + +``` + +Sequence chart for the Acceptance of the Waiting Call. The diagram shows four lifelines: UE, RNC/BSC, MSC-S, and MGW. A green bar at the top indicates the state 'B-on hold, C-waiting'. The sequence of messages involves CONNECT, MOD.request, MOVE.request, and Answer. + +**Figure 13.15: Acceptance of the Waiting Call.** + +## 13.6 Call Hold (CH) + +The procedures specified in 3GPP TS 23.083 [13] for the Call Hold supplementary service shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +### 13.6.1 Hold request + +When the UE makes a request for the hold function the MSC server requests the MGW to interrupt the communication on the bearer by changing the through-connection of the bearer termination towards the served mobile subscriber to "not through-connected" or by using the Isolate Bearer Termination Procedure. Announcements may be applied to the held party as described in clause 14.6. + +### 13.6.2 Retrieval request + +When the UE makes a request to retrieve a held call the MSC server requests the MGW to re-establish communication to the held party by changing the through-connection of the bearer termination towards the served mobile subscriber to be both-way through-connected or by using the Join Bearer Termination Procedure. + +### 13.6.3 Setting up another call + +The call towards the C party is established as described for the mobile originating call. A new MGW may be selected in the course of setting up the new call. If out-of-band transcoder control is applied for a speech call, it shall be performed in accordance with 3GPP TS 23.153 [3]. If required, the MSC server shall modify the access bearer for the new call as described in subclause 13.18.1. The MSC server will request the MGW to connect the access side bearer termination to the bearer termination of the remote party. + +### 13.6.4 Alternate from one call to the other + +When the hold request for the active call is immediately followed by a retrieve request for the held call the MSC server shall request the MGW to connect the bearer termination of the served mobile subscriber to the bearer termination of the held party. The MSC server also requests the MGW to both-way through-connect the bearer for the previously held call. + +### 13.6.5 Disconnect + +If the active call is disconnected while another call is on hold, the bearer termination towards the served mobile subscriber is not removed but the call towards the active party is disconnected as described in the clause for call clearing. + +If the held call is disconnected while the served mobile subscriber is connected to an active call the bearer termination towards the served mobile subscriber shall not be removed but the call towards the held party is disconnected as described in the clause for call clearing. + +### 13.6.6 Failure handling in MSC server + +If any procedure between the MSC server and the MGW has not completed successfully, the MSC server shall reject the hold/retrieve request. + +### 13.6.7 Example 1 + +Figure 13.16 shows the network model for the call hold with an establishment of a new call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. The MSC server isolates the flow connection between the served mobile and the termination in the MGW that is used for the held call. If an announcement is to be played to the held party the MSC Server may seize a new context in the MGW. If a new call is made to C subscriber the MSC server seizes a new context in the MGW if not previously done. The new context is used for the new call and the old context is used for the held call. The bearer termination $T_A$ is moved with the bearer towards the RNC (served mobile subscriber) and the bearer termination $T_C$ is used for the bearer towards the succeeding MGW (C-party). + +NOTE: The main advantage with example 1 is that if B party is connected to a radio access and a handover occurs then the announcement termination is unaffected and therefore there is no break in the announcement. It is also an option to put the B-party on hold using the isolate bearer procedure immediately but this is not shown in this example. + +![Two network diagrams illustrating call hold and new call establishment. The left diagram shows 'B-party on hold' with MSC-S, RNC/BSC, and MGW (CTX_AB) components. The right diagram shows 'New call to C subscriber/Announcement to B party' with additional components like CTX_AC and T_A2.](26d664119ad25250780f554633444e54_img.jpg) + +The diagram consists of two parts illustrating network models for call hold and new call establishment. + +**B-party on hold:** This diagram shows a mobile subscriber (RNC/BSC) connected to an MGW (CTXAB), which is in turn connected to an MSC-S. The B party is indicated by a green dashed line. The MGW has a termination labeled 'INACTIVE'. + +**New call to C subscriber/Announcement to B party:** This diagram shows a more complex setup. The RNC/BSC is connected to an MGW (CTXAB). The MGW (CTXAB) is connected to another MGW (CTXAC). The MSC-S is connected to the MGW (CTXAB). The B party is indicated by a green dashed line, and the C party is indicated by a red dashed line. The MGW (CTXAB) has terminations labeled TA2 and TA. The MGW (CTXAC) has a termination labeled TC. + +Two network diagrams illustrating call hold and new call establishment. The left diagram shows 'B-party on hold' with MSC-S, RNC/BSC, and MGW (CTX\_AB) components. The right diagram shows 'New call to C subscriber/Announcement to B party' with additional components like CTX\_AC and T\_A2. + +**Figure 13.16: Call hold and establishment of a new call (Network model) example 1** + +Figure 13.17 shows the message sequence for example 1 for the call hold procedure. In the example the MSC server requests the MGW to change the through-connection of the bearer so that it will not be through-connected when the hold request is received from the served mobile subscriber (bullet 2 in figure 13.17). Subsequently if an announcement is to be applied then Termination TA may be isolated from the held party (bullet 3 in figure 13.17) and a new announcement termination TA2 is added to context CTXAB and announcement applied to termination TA2 (bullet 3a in figure 13.17). For setting up a new call to the C-party the termination TA is moved to a new context if not done previously (bullet 4 in figure 13.17) and a new termination TC is reserved (bullet 5 in figure 13.17) and the call shall continue with the appropriate stream mode settings as for a normal call establishment in accordance with Clause 6.1, see figure 6.2. + +![Sequence diagram for Figure 13.17: Hold request (message sequence chart), example 1. The diagram shows interactions between UE, RNC/BSC, MSC-S, and MGW. The sequence starts with a HOLD message from UE to MSC-S. MSC-S accepts the request and sends a MOD.request(T_A INACTIVE) to MGW. MGW responds with MOD.reply(T_A) and a Call Progress message. MSC-S then sends a HOLD ACK to UE. Next, MSC-S sends Context (C_AB) to RNC/BSC. MSC-S then sends MOV.request(T_A) to MGW, which responds with MOV.reply(T_A). MSC-S then sends Context (C_S) and Context (C_AC) to RNC/BSC. MSC-S then sends ADD.request(T_S) to MGW, which responds with ADD.reply(T_A2). MSC-S then sends Context (C_AB) to RNC/BSC. MSC-S then sends a Play Announcement (T_A) to MGW. MSC-S then sends Context (C_S) and Context (C_AC) to RNC/BSC. MSC-S then sends MOV.request(T_A) to MGW, which responds with MOV.reply(T_A). MSC-S then sends Context (C_AC) to RNC/BSC. MSC-S then sends ADD.request(T_S) to MGW, which responds with ADD.reply(T_C). MSC-S then sends Context (C_AC) to RNC/BSC. MSC-S then sends an ENQUIRY to C-Party to RNC/BSC.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S + participant MGW + + Note right of MSC-S: MSC accepts Hold Request + + UE->>MSC-S: HOLD + Note right of MSC-S: 1 + Note right of MSC-S: MSC accepts Hold Request + Note right of MSC-S: Context (C_AB) + Note right of MSC-S: 2 + MSC-S->>MGW: MOD.request(T_A INACTIVE) + MGW-->>MSC-S: MOD.reply(T_A) + Note right of MGW: Change Through-Connection + MSC-S->>MGW: Call Progress + Note right of MSC-S: Context (C_AB) + Note right of MSC-S: 3 + MSC-S->>UE: HOLD ACK + Note right of MSC-S: Context (C_AB) + Note right of MSC-S: Context (C_S) + Note right of MSC-S: Context (C_AC) + Note right of MSC-S: Context (C_AB) + Note right of MSC-S: 3a + MSC-S->>MGW: MOV.request(T_A) + MGW-->>MSC-S: MOV.reply(T_A) + Note right of MGW: Isolate Bearer Termination + MSC-S->>MGW: ADD.request(T_S) + MGW-->>MSC-S: ADD.reply(T_A2) + Note right of MGW: Add Announcement Termination + Note right of MSC-S: Context (C_AB) + Note right of MSC-S: Play Announcement (T_A) + Note right of MSC-S: Context (C_S) + Note right of MSC-S: Context (C_AC) + Note right of MSC-S: 4 + MSC-S->>MGW: MOV.request(T_A) + MGW-->>MSC-S: MOV.reply(T_A) + Note right of MGW: Isolate Bearer Termination (if not previously isolated) + Note right of MSC-S: Context (C_AC) + Note right of MSC-S: 5 + MSC-S->>MGW: ADD.request(T_S) + MGW-->>MSC-S: ADD.reply(T_C) + Note right of MGW: Add Bearer Termination + Note right of MSC-S: Context (C_AC) + Note right of MSC-S: ENQUIRY to C-Party + +``` + +Sequence diagram for Figure 13.17: Hold request (message sequence chart), example 1. The diagram shows interactions between UE, RNC/BSC, MSC-S, and MGW. The sequence starts with a HOLD message from UE to MSC-S. MSC-S accepts the request and sends a MOD.request(T\_A INACTIVE) to MGW. MGW responds with MOD.reply(T\_A) and a Call Progress message. MSC-S then sends a HOLD ACK to UE. Next, MSC-S sends Context (C\_AB) to RNC/BSC. MSC-S then sends MOV.request(T\_A) to MGW, which responds with MOV.reply(T\_A). MSC-S then sends Context (C\_S) and Context (C\_AC) to RNC/BSC. MSC-S then sends ADD.request(T\_S) to MGW, which responds with ADD.reply(T\_A2). MSC-S then sends Context (C\_AB) to RNC/BSC. MSC-S then sends a Play Announcement (T\_A) to MGW. MSC-S then sends Context (C\_S) and Context (C\_AC) to RNC/BSC. MSC-S then sends MOV.request(T\_A) to MGW, which responds with MOV.reply(T\_A). MSC-S then sends Context (C\_AC) to RNC/BSC. MSC-S then sends ADD.request(T\_S) to MGW, which responds with ADD.reply(T\_C). MSC-S then sends Context (C\_AC) to RNC/BSC. MSC-S then sends an ENQUIRY to C-Party to RNC/BSC. + +**Figure 13.17: Hold request (message sequence chart), example 1** + +Figure 13.18 shows the message sequence for example 1 for the retrieval procedure. In the example the MSC server requests the MGW to move the connection of the bearer back to be both-way through-connected (bullet 3 and 4 in figure 13.18) to the held party, after the held party has been disconnected from an optionally applied announcement (bullet 2 in figure 13.18). The MOVE command (Join Bearer termination procedure) is not required (bullet 3 in figure 13.18) if $T_A$ has not previously been moved into the $CTX_{AC}$ . The Change Through-Connection is only required if the retrieval occurs prior to any connection to C-party. + +![Figure 13.18: Retrieval request (message sequence chart), example 1. This sequence diagram shows the interaction between UE, RNC/BSC, MSC-S, and MGW. The process starts with a RETRIEVAL message from UE to MSC-S. MSC-S accepts the request and initiates a 'Stop announcement (T_A2)'. It then sends a SUB.request(T_A2) to MGW, which responds with SUB.reply(T_A2). Next, MSC-S sends a MOV.request(T_A) to MGW, which responds with MOV.reply(T_A). Finally, MSC-S sends a MOD.request(T_A SENDRECV) to MGW, which responds with MOD.reply(T_A). The MGW performs 'Remove Announcement Termination', 'Join Bearer Termination', and 'Change Through-connection'. The MSC-S then sends a RETRIEVAL ACK back to the UE. Context (C_AB) is shown being updated at steps 2, 3, and 4.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +Figure 13.18: Retrieval request (message sequence chart), example 1. This sequence diagram shows the interaction between UE, RNC/BSC, MSC-S, and MGW. The process starts with a RETRIEVAL message from UE to MSC-S. MSC-S accepts the request and initiates a 'Stop announcement (T\_A2)'. It then sends a SUB.request(T\_A2) to MGW, which responds with SUB.reply(T\_A2). Next, MSC-S sends a MOV.request(T\_A) to MGW, which responds with MOV.reply(T\_A). Finally, MSC-S sends a MOD.request(T\_A SENDRECV) to MGW, which responds with MOD.reply(T\_A). The MGW performs 'Remove Announcement Termination', 'Join Bearer Termination', and 'Change Through-connection'. The MSC-S then sends a RETRIEVAL ACK back to the UE. Context (C\_AB) is shown being updated at steps 2, 3, and 4. + +Figure 13.18: Retrieval request (message sequence chart), example 1 + +### 13.6.8 Example 2 + +Figure 13.18a shows the network model for the call hold with an establishment of a new call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. The MSC server isolates the flow connection between the served mobile and the termination in the MGW that is used for the held call. After the request to establish a new call is made the MSC server seizes a new context in the MGW, the new context is used for the new call and the old context is used for the held call. The bearer termination $T_A$ for the bearer towards the RNC (served mobile subscriber) is moved to this context and the bearer termination $T_C$ is used for the bearer towards the succeeding MGW (C-party). In this example the announcement is played directly to Termination $T_B$ . + +NOTE: if B party is connected to a radio access and a handover occurs during the announcement then the announcement will be interrupted. It is also possible to put B-party on hold using the isolate bearer termination but if the announcement is still played directly to termination $T_B$ as proposed by this example and a handover occurs then the problem still arises. + +![Figure 13.18a: Call hold and establishment of a new call (Network model) example 2. This diagram shows two network models. The left model, 'B-party on hold/announcement played:', shows a UE connected to an RNC/BSC, which is connected to an MSC-S. The MSC-S is connected to an MGW. The MGW has two bearers: one active bearer (solid blue line) between the RNC/BSC and the MGW, and one inactive bearer (dotted red line) between the MSC-S and the MGW. The inactive bearer is labeled 'B party'. The right model, 'New call to C subscriber:', shows the same UE and RNC/BSC connected to the MSC-S. The MSC-S is now connected to a new MGW. This new MGW has two bearers: one active bearer (solid blue line) between the RNC/BSC and the MGW, and one inactive bearer (dotted red line) between the MSC-S and the MGW. The inactive bearer is labeled 'B party'. A new active bearer (solid blue line) is shown between the MSC-S and the new MGW, labeled 'C party'.](356eb99ab9489bbd647223390a913903_img.jpg) + +Figure 13.18a: Call hold and establishment of a new call (Network model) example 2. This diagram shows two network models. The left model, 'B-party on hold/announcement played:', shows a UE connected to an RNC/BSC, which is connected to an MSC-S. The MSC-S is connected to an MGW. The MGW has two bearers: one active bearer (solid blue line) between the RNC/BSC and the MGW, and one inactive bearer (dotted red line) between the MSC-S and the MGW. The inactive bearer is labeled 'B party'. The right model, 'New call to C subscriber:', shows the same UE and RNC/BSC connected to the MSC-S. The MSC-S is now connected to a new MGW. This new MGW has two bearers: one active bearer (solid blue line) between the RNC/BSC and the MGW, and one inactive bearer (dotted red line) between the MSC-S and the MGW. The inactive bearer is labeled 'B party'. A new active bearer (solid blue line) is shown between the MSC-S and the new MGW, labeled 'C party'. + +Figure 13.18a: Call hold and establishment of a new call (Network model) example 2 + +Figure 13.18b shows the message sequence for example 2 for the call hold procedure. In the example the MSC server requests the MGW to change the through-connection of the bearer to inactive when the hold request is received from the served mobile subscriber (bullet 2 in figure 13.18b). Subsequently an announcement may be applied to termination TB (bullet 3 in figure 13.18b). Then the new call is established via a new context with served mobile subscriber termination TA being moved to this new context (bullet 4 in figure 13.18b) and a new termination TC is reserved (bullet 5 in figure 13.18b) and the call shall continue with the appropriate stream mode settings as for a normal call establishment in accordance with Clause 6.1, see figure 6.2. + +![Sequence diagram for Figure 13.18b: Hold request (message sequence chart), example 2. The diagram shows interactions between UE, RNC/BSC, MSC-S, and MGW. The sequence starts with a HOLD message from UE to MSC-S. MSC-S responds with 'MSC accepts Hold Request' and sends a MOD.request(T_A INACTIVE) to MGW. MGW responds with MOD.reply(T_A) and 'Change Through-Connection'. MSC-S sends 'Call Progress' to UE, which responds with 'HOLD ACK'. A 'Play Announcement (T_B)' is performed between MSC-S and MGW. UE sends an 'ENQUIRY to C-Party' to MSC-S. MSC-S sends Context (C_S) to MGW, which responds with MOV.request(T_A) and 'Isolate Bearer Termination'. MSC-S sends Context (C_Ac) to MGW, which responds with MOV.reply(T_A) and 'Add Bearer Termination'. MSC-S sends Context (C_Ac) to MGW, which responds with ADD.request(T_S) and 'Add Bearer Termination'. MSC-S sends Context (C_Ac) to MGW, which responds with ADD.reply(T_C).](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC_BSC as RNC/BSC + participant MSC_S as MSC-S + participant MGW + + Note over MSC_S: 1 + UE->>MSC_S: HOLD + Note over MSC_S: MSC accepts Hold Request + Note over MSC_S: 2 + Note left of MSC_S: Context (C_AB) + MSC_S->>MGW: MOD.request(T_A INACTIVE) + MGW-->>MSC_S: MOD.reply(T_A) + Note right of MGW: Change Through-Connection + MSC_S->>UE: Call Progress + Note over MSC_S: 3 + UE-->>MSC_S: HOLD ACK + rect rgb(200, 255, 200) + Note over MGW: Play Announcement (T_B) + end + Note over MSC_S: 4 + UE->>MSC_S: ENQUIRY to C-Party + Note left of MSC_S: Context (C_S) + MSC_S->>MGW: MOV.request(T_A) + Note right of MGW: Isolate Bearer Termination + Note left of MSC_S: Context (C_AC) + MGW-->>MSC_S: MOV.reply(T_A) + Note left of MSC_S: Context (C_AC) + MSC_S->>MGW: ADD.request(T_S) + Note right of MGW: Add Bearer Termination + Note over MSC_S: 5 + Note left of MSC_S: Context (C_AC) + MGW-->>MSC_S: ADD.reply(T_C) + +``` + +Sequence diagram for Figure 13.18b: Hold request (message sequence chart), example 2. The diagram shows interactions between UE, RNC/BSC, MSC-S, and MGW. The sequence starts with a HOLD message from UE to MSC-S. MSC-S responds with 'MSC accepts Hold Request' and sends a MOD.request(T\_A INACTIVE) to MGW. MGW responds with MOD.reply(T\_A) and 'Change Through-Connection'. MSC-S sends 'Call Progress' to UE, which responds with 'HOLD ACK'. A 'Play Announcement (T\_B)' is performed between MSC-S and MGW. UE sends an 'ENQUIRY to C-Party' to MSC-S. MSC-S sends Context (C\_S) to MGW, which responds with MOV.request(T\_A) and 'Isolate Bearer Termination'. MSC-S sends Context (C\_Ac) to MGW, which responds with MOV.reply(T\_A) and 'Add Bearer Termination'. MSC-S sends Context (C\_Ac) to MGW, which responds with ADD.request(T\_S) and 'Add Bearer Termination'. MSC-S sends Context (C\_Ac) to MGW, which responds with ADD.reply(T\_C). + +**Figure 13.18b: Hold request (message sequence chart), example 2** + +Figure 13.18c shows the message sequence example for the retrieval procedure. In the example the MSC server moves the served mobile subscriber back to the context with termination TB and requests the MGW to change the through-connection of the bearer to be both-way through-connected (bullet 3 and 4 in figure 13.18c) after the held party has been disconnected from an optionally applied announcement (bullet 2 in figure 13.18c). The MOVE command (Join Bearer Termination procedure) is not required (bullet 3 in figure 13.18c) if TA has not been in the CTXAC. The Change Through-Connection is only required if the retrieval occurs prior to any connection to C-party. + +![Figure 13.18c: Retrieval request (message sequence chart), example 2. The diagram shows a sequence of messages between UE, RNC/BSC, MSC-S, and MGW. The sequence starts with a RETRIEVAL message from UE to MSC-S. MSC-S accepts the request and sends a Stop announcement (TB) to MGW. Then, MSC-S sends Context (C_AB) and MOV.request(TA) to MGW. MGW responds with MOV.reply(TA). Next, MSC-S sends Context (C_AB) and MOD.request(TA SENRECV) to MGW. MGW responds with MOD.reply(TA). Finally, MSC-S sends a RETRIEVAL ACK to UE. The diagram also includes annotations: 'MSC accepts Retrieval Request', 'Stop announcement (TB)', 'Join Bearer Termination', and 'Change Through-connection'.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S + participant MGW + + Note right of MSC-S: MSC accepts Retrieval Request + + UE->>MSC-S: RETRIEVAL + MSC-S->>MGW: Stop announcement (TB) + Note right of MGW: Join Bearer Termination + MSC-S->>MGW: Context (C_AB) MOV.request(TA) + MGW-->>MSC-S: MOV.reply(TA) + MSC-S->>MGW: Context (C_AB) MOD.request(TA SENRECV) + Note right of MGW: Change Through-connection + MGW-->>MSC-S: MOD.reply(TA) + MSC-S->>UE: RETRIEVAL ACK + +``` + +Figure 13.18c: Retrieval request (message sequence chart), example 2. The diagram shows a sequence of messages between UE, RNC/BSC, MSC-S, and MGW. The sequence starts with a RETRIEVAL message from UE to MSC-S. MSC-S accepts the request and sends a Stop announcement (TB) to MGW. Then, MSC-S sends Context (C\_AB) and MOV.request(TA) to MGW. MGW responds with MOV.reply(TA). Next, MSC-S sends Context (C\_AB) and MOD.request(TA SENRECV) to MGW. MGW responds with MOD.reply(TA). Finally, MSC-S sends a RETRIEVAL ACK to UE. The diagram also includes annotations: 'MSC accepts Retrieval Request', 'Stop announcement (TB)', 'Join Bearer Termination', and 'Change Through-connection'. + +Figure 13.18c: Retrieval request (message sequence chart), example 2 + +## 13.7 Multiparty (MPTY) + +The procedures specified in 3GPP TS 23.084 [14] for the Multi Party supplementary service shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. If out-of-band transcoder control is applied for the call, it shall be performed in accordance with 3GPP TS 23.153 [3]. + +### 13.7.1 Beginning the Multi Party call + +When the served mobile subscriber invokes a Multi Party service the MSC server selects an MGW that provides the Multi Party bridge capabilities. If the selected MGW is different from the MGW that is used for the active call, the MSC server requests the MGW(s) to connect the bearer terminations of the participants to the selected MGW. The bearer terminations are connected together. + +### 13.7.2 Managing an active Multi Party call + +When the served mobile subscriber puts the Multi Party call on hold the MSC server requests the MGW to interrupt the connection between the served mobile subscriber and the Multi Party bridge. + +When the served mobile subscriber retrieves a held Multi Party call the MSC server requests the MGW to re-establish the connection between the served mobile subscriber and the Multi Party bridge. + +When the served mobile subscriber requests private communication with one of the remote parties (e.g. B-party), the MSC server shall request the MGW to interrupt the connection between the served mobile subscriber and the Multi Party bridge, and connection between the remote B party and the Multi Party bridge. The MSC server requests the MGW to connect the bearer termination of the served mobile subscriber to the bearer termination of the remote party (or vice versa) within a same context. + +### 13.7.3 Disconnect + +If a remote party is disconnected while other parties still remain the call towards the remote party is disconnected as described in the clause for call clearing. + +### 13.7.4 Failure handling in MSC server + +If resources for the Multi Party service cannot be allocated in any of the MGW resources assigned to the MSC server, then the MSC server shall reject the MPTY request. + +### 13.7.5 Example 1 – Multiparty call establishment + +Figure 13.19 shows the network model for multi party call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. Note that for a TDM access there is no separation between the call and bearer control signalling. In the following example it is assumed that each party participating in the Multi Party conference is handled in a separate context representing the call leg between the Multi Party bridge and the Multi Party participant. The Multi Party bridge itself is handled in a separate context. This separation to several contexts is done in order to simplify interactions with other functionality, such as handover, even though other implementation options are not excluded. + +![Figure 13.19: Multi Party call (Network model). The diagram shows a network architecture for a multiparty call. At the top is the MSC-S (Mobile Switching Center Server). Below it is a large box representing the MGW (Media Gateway). Inside the MGW box, there are several context boxes: CTX_A, CTX_MPTY, CTX_AB, and CTX_AC. The CTX_A context is connected to an RNC/BSC (Radio Network Controller/Base Station Controller) on the left. The CTX_MPTY context is the central bridge. The CTX_AB and CTX_AC contexts are connected to the CTX_MPTY context. The RNC/BSC is connected to the MSC-S via a green dotted line (bearer control signalling). The MSC-S is connected to the CTX_A context via a blue squared line (call control signalling). The CTX_A context is connected to the CTX_MPTY context via a blue squared line. The CTX_MPTY context is connected to the CTX_AB and CTX_AC contexts via blue squared lines. The CTX_AB and CTX_AC contexts are connected to the B-party and C-party respectively via green dotted lines. The B-party and C-party are represented by red dots.](7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg) + +Figure 13.19: Multi Party call (Network model). The diagram shows a network architecture for a multiparty call. At the top is the MSC-S (Mobile Switching Center Server). Below it is a large box representing the MGW (Media Gateway). Inside the MGW box, there are several context boxes: CTX\_A, CTX\_MPTY, CTX\_AB, and CTX\_AC. The CTX\_A context is connected to an RNC/BSC (Radio Network Controller/Base Station Controller) on the left. The CTX\_MPTY context is the central bridge. The CTX\_AB and CTX\_AC contexts are connected to the CTX\_MPTY context. The RNC/BSC is connected to the MSC-S via a green dotted line (bearer control signalling). The MSC-S is connected to the CTX\_A context via a blue squared line (call control signalling). The CTX\_A context is connected to the CTX\_MPTY context via a blue squared line. The CTX\_MPTY context is connected to the CTX\_AB and CTX\_AC contexts via blue squared lines. The CTX\_AB and CTX\_AC contexts are connected to the B-party and C-party respectively via green dotted lines. The B-party and C-party are represented by red dots. + +Figure 13.19: Multi Party call (Network model) + +For the purposes of the information flow diagrams it is assumed that there are only two remote parties. Party A is the subscriber controlling the Multi Party service (served mobile subscriber). Party B is the held party and party C is the active party. + +It is assumed that the Multi Party bridge is located in the MGW that has been selected for the served mobile subscriber. + +Figure 13.20 shows the message sequence example for the beginning of multi party call. When the served mobile subscriber invokes a Multi Party service the MSC server requests the MGW to create a separate context for the Multi Party bridge. The MSC server seizes a bearer termination for each party in that context. In addition, each call leg is represented by a separate context. Therefore the parties in the active call will be split in separate contexts. The MSC server requests the MGW to create a new context and to move the bearer termination for the served mobile subscriber from the active call context to the new context. To connect the parties to the Multi Party bridge the MSC server requests the MGW to establish internal Nb connections between the bearer terminations in the Multi Party bridge context and the call leg contexts, using the standard external bearer setup procedures. The held party is informed about the retrieval of the held call, and the both remote parties are informed about the multi party call establishment. + +![Sequence diagram showing information flow for a multi-party call with internal ATM bearers between UE, RNC/BSC, MSC-S, and MGW.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +The sequence diagram illustrates the interaction between four entities: UE, RNC/BSC, MSC-S, and MGW. The process begins with the UE sending a 'Multi Party req' to the MSC-S. The MSC-S then initiates a series of messages with the MGW to prepare and establish bearers for multiple parties. The MSC-S sends 'Context (\$)' and 'MOV.request (TA)' to the MGW. The MGW responds with 'MOV.reply (TA)'. Subsequently, the MSC-S sends 'Context (\$)' and three 'ADD.request (\$)' messages to the MGW. The MGW performs 'Prepare bearer' operations and responds with 'ADD.reply (TA0)', 'ADD.reply (TB0)', and 'ADD.reply (TC0)' within 'Context (CMPTY)'. Next, the MSC-S sends 'Context (CA)' and 'ADD.request (\$)' to the MGW, which responds with 'ADD.reply (TA1)' and performs an 'Establish bearer' operation. This pattern repeats for 'Context (CAB)' with 'ADD.reply (TB1)' and 'Context (CAC)' with 'ADD.reply (TC1)'. Finally, the MSC-S sends 'Call Progress' messages for parties B and C. The process concludes with a 'Multi Party acknowledge' from the MSC-S to the UE. + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S + participant MGW + + UE->>MSC-S: Multi Party req + MSC-S->>MGW: Context ($) / MOV.request (TA) + MGW-->>MSC-S: MOV.reply (TA) (Context CA) + MSC-S->>MGW: Context ($) / ADD.request ($) (x3) + Note right of MGW: Prepare bearer (x3) + MGW-->>MSC-S: ADD.reply (TA0, TB0, TC0) (Context CMPTY) + MSC-S->>MGW: Context (CA) / ADD.request ($) + Note right of MGW: Establish bearer + MGW-->>MSC-S: ADD.reply (TA1) (Context CA) + MSC-S->>MGW: Context (CAB) / ADD.request ($) + Note right of MGW: Establish bearer + MGW-->>MSC-S: ADD.reply (TB1) (Context CAB) + MSC-S->>MGW: Context (CAC) / ADD.request ($) + Note right of MGW: Establish bearer + MGW-->>MSC-S: ADD.reply (TC1) (Context CAC) + MSC-S->>MGW: Call Progress (to B) + MSC-S->>MGW: Call Progress (to B) + MSC-S->>MGW: Call Progress (to C) + MSC-S->>UE: Multi Party acknowledge + +``` + +Sequence diagram showing information flow for a multi-party call with internal ATM bearers between UE, RNC/BSC, MSC-S, and MGW. + +Figure 13.20: Information flow for multi party call, internal ATM bearer (message sequence chart) + +![Sequence diagram showing a call setup process between UE, RNC/BSC, MSC-S, and MGW. The diagram includes messages like Multi Party req, Context ($), MOV.request, MOV.reply, ADD.request, ADD.reply, NOTIFY.request, NOTIFY.reply, MOD.request, MOD.reply, Call Progress, and Multi Party acknowledge. Annotations on the right indicate actions like 'Establish bearer', 'Tunnel Information Up', and 'Tunnel Information Down'.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S + participant MGW + + Note right of UE: Error: + Note right of MSC-S: 32 + Note right of MGW: Error: Reference source not + + UE->>MSC-S: Multi Party req + MSC-S->>MGW: Context ($), MOV.request (TA) + MGW-->>MSC-S: MOV.reply (TA) + MSC-S->>MGW: Context ($), ADD.request ($), ADD.request ($), ADD.request ($) + Note right of MGW: Establish bearer +Establish bearer +Establish bearer + MGW-->>MSC-S: Context (CMPTY), ADD.reply (TA0), ADD.reply (TB0), ADD.reply (TC0) + MSC-S->>MGW: Context (CMPTY), NOTIFY.request (TA0), NOTIFY.request (TB0), NOTIFY.request (TC0) + Note right of MGW: Tunnel Information Up +Tunnel Information Up +Tunnel Information Up + MGW-->>MSC-S: Context (CMPTY), NOTIFY.reply (TA0), NOTIFY.reply (TB0), NOTIFY.reply (TC0) + MSC-S->>MGW: Context (CA), ADD.request ($), ADD.reply (TA1) + Note right of MGW: Prepare bearer + Tunnel +Information Down + MSC-S->>MGW: Context (CA), NOTIFY.request (TA1) + Note right of MGW: Tunnel Information Up + MGW-->>MSC-S: Context (CA), NOTIFY.reply (TA1) + MSC-S->>MGW: Context (CAB), ADD.request ($), ADD.reply (TB1) + Note right of MGW: Prepare bearer + Tunnel +Information Down + MSC-S->>MGW: Context (CAB), NOTIFY.request (TB1) + Note right of MGW: Tunnel Information Up + MGW-->>MSC-S: Context (CAB), NOTIFY.reply (TB1) + MSC-S->>MGW: Context (CAC), ADD.request ($), ADD.reply (TC1) + Note right of MGW: Prepare bearer + Tunnel +Information Down + MSC-S->>MGW: Context (CAC), NOTIFY.request (TC1) + Note right of MGW: Tunnel Information Up + MGW-->>MSC-S: Context (CAC), NOTIFY.reply (TC1) + MSC-S->>MGW: Context (CMPTY), MOD.request (TA0), MOD.request (TB0), MOD.request (TC0) + Note right of MGW: Tunnel Information Down +Tunnel Information Down +Tunnel Information Down + MGW-->>MSC-S: Context (CMPTY), MOD.reply (TA0), MOD.reply (TB0), MOD.reply (TC0) + MSC-S->>UE: Call Progress (to B) + MSC-S->>UE: Call Progress (to B) + MSC-S->>UE: Call Progress (to C) + MSC-S->>UE: Multi Party acknowledge + +``` + +Sequence diagram showing a call setup process between UE, RNC/BSC, MSC-S, and MGW. The diagram includes messages like Multi Party req, Context (\$), MOV.request, MOV.reply, ADD.request, ADD.reply, NOTIFY.request, NOTIFY.reply, MOD.request, MOD.reply, Call Progress, and Multi Party acknowledge. Annotations on the right indicate actions like 'Establish bearer', 'Tunnel Information Up', and 'Tunnel Information Down'. + +Figure 13.20a: Information flow for multi party call, internal IP bearer (message sequence chart) + +### 13.7.6 Example 2 – Private call establishment during multiparty call + +Figure 13.20b shows the network model for private call. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. Note that for a TDM access there is no separation between the call and bearer control signalling. + +![Figure 13.20b: Private call (Network model) diagram showing MSC-S, RNC/BSC, and MGW components with various context labels like CTX_A, CTX_MPTY, CTX_AB, CTX_AC, and CTX_PRIV.](dbbc0baac7341cda76cc4f8355dce23f_img.jpg) + +The diagram illustrates the network architecture for a private call. At the top is the MSC-S (Mobile Switching Center - Server). Below it, a large box contains the RNC/BSC (Radio Network Controller / Base Station Controller) on the left and the MGW (Media Gateway) at the bottom. Inside the box, there are several context nodes: CTX\_A, CTX\_MPTY, CTX\_AB, CTX\_AC, and CTX\_PRIV. Solid blue lines represent call control signalling paths between the MSC-S and these contexts. Dotted red lines represent bearer control signalling and bearer paths, leading to external parties labeled 'B-party' and 'C party'. A green dashed line connects the MSC-S to the RNC/BSC. + +Figure 13.20b: Private call (Network model) diagram showing MSC-S, RNC/BSC, and MGW components with various context labels like CTX\_A, CTX\_MPTY, CTX\_AB, CTX\_AC, and CTX\_PRIV. + +Figure 13.20b: Private call (Network model) + +![Figure 13.20c: Information flow for private call (message sequence chart) showing interactions between UE, RNC/BSC, MSC-S, and MGW with messages like SplitMPTY Invoke, Context ($), MOV. request, MOV. reply, Call Progress, and SplitMPTY Result.](1b893df61c2b73b7a85e65fc1f58e203_img.jpg) + +This sequence diagram shows the interaction between four entities: UE (User Equipment), RNC/BSC, MSC-S, and MGW. The sequence of messages is as follows: + + +- The UE sends a 'SplitMPTY Invoke' message to the MSC-S. +- The MSC-S sends a 'Context (\$)' message to the RNC/BSC. +- The MSC-S sends 'MOV. request (TA)' and 'MOV. request (Tc)' messages to the MGW. +- The MGW responds with 'MOV. reply (TA)' and 'MOV. reply (Tc)' messages to the MSC-S. +- The MSC-S sends a 'Context (CPRIV)' message to the RNC/BSC. +- The MSC-S sends two 'Call Progress' messages: one indicating 'conference disconnected to C' and another indicating 'other party split to B'. +- Finally, the MSC-S sends a 'SplitMPTY Result' message back to the UE. + +Figure 13.20c: Information flow for private call (message sequence chart) showing interactions between UE, RNC/BSC, MSC-S, and MGW with messages like SplitMPTY Invoke, Context (\$), MOV. request, MOV. reply, Call Progress, and SplitMPTY Result. + +Figure 13.20c: Information flow for private call (message sequence chart) + +NOTE: The two MOVE commands may be sent in different transactions. + +For the purposes of the information flow diagrams it is assumed that there are only two remote parties and the private call is established between the served mobile subscriber (Party A) and the remote C-party. + +Figure 13.20c shows the message sequence example for the beginning of private communication between the served mobile subscriber and the remote parties (e.g. C-party). + +## 13.8 Closed User Group (CUG) + +No impact. + +## 13.9 Advice of Charge (AoC) + +No impact. + +## 13.10 User-to-User Signalling (UUS) + +No impact. + +## 13.11 Call Barring Services + +### 13.11.1 Barring of outgoing calls + +No impact. + +### 13.11.2 Barring of incoming calls other than Anonymous Call Rejection + +No impact. + +### 13.11.3 Anonymous Call Rejection (ACR) + +#### 13.11.3.1 General + +The Anonymous Call Rejection service is described in 3GPP TS 23.088 [46]. + +#### 13.11.3.2 Anonymous Call Rejection by the GMSC + +If the incoming call to the mobile station is determined to be barred by the Anonymous Call Rejection service, the call shall be barred. Otherwise the call shall be delivered as described in clause 6, Call Establishment. + +If the call is to be rejected due to ACR the GMSC shall seize a MGW to connect the call to a recorded announcement as for existing barring procedures requiring a tone or announcement. + +The GMSC shall include Cause No. 24 – Call rejected due to feature at destination in the CPG or ACM and then the GMSC server provides the MGW with the announcement identification and requests the MGW to notify the announcement completion using the Play Announcement procedure as described in subclause 14.6. + +After the announcement has been completed the GMSC server initiates the call release as described in the clause 7, with the cause 31 (normal, unspecified). + +## 13.12 Explicit Call Transfer (ECT) + +The procedures specified in 3GPP TS 23.091 [15] for the Explicit Call Transfer supplementary service shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +Party A is the subscriber controlling the Explicit Call Transfer Call (served mobile subscriber). Party B is the first remote called party (held party). Party C is the second remote called party. + +### 13.12.1 Connection of remote parties + +If the result of the ECT checks is successful the MSC server will order the MGW to connect the bearer termination of the C-party to the bearer termination of the B-party (bullet 1 in figure 13.24 or in figure 13.21). As a result of this action the held party will be retrieved. + +If the call towards the C-party has not been answered, the MSC server requests the MGW to both-way through-connect the bearer termination towards the C-party. + +### 13.12.2 IU/A-interface release + +The served party is disconnected after a successful transfer request. The call towards the served mobile subscriber shall be released as described in the clause for call clearing. + +### 13.12.3 Failure handling in MSC server + +If the bearer terminations for the remote parties can not be connected successfully, the MSC server shall reject the ECT request. + +### 13.12.4 Example + +Figure 13.23 shows the network model for call explicit call transfer. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. Note that for a TDM access case there is no separation of call and bearer control signalling. The MSC server moves the bearer terminations of the remote parties in the same context and removes the bearer termination for the served mobile subscriber. The bearer termination $T_A$ is used for the bearer towards the served mobile subscriber, the bearer termination $T_B$ is used for the bearer towards the B-party and the bearer termination $T_C$ is used for the bearer towards the C-party. + +![Figure 13.23: ECT (Network model) diagram showing the network configuration before and after an Explicit Call Transfer (ECT) request. The diagram consists of two parts: 'Before ECT request:' and 'After ECT:'. In the 'Before' state, an MSC-S is connected to an RNC/BSC (served party) and an MGW. The MGW has three bearers: T_A (to RNC/BSC), T_B (to B party), and T_C (to C party). The MSC-S is connected to the B party via a green dotted line. In the 'After ECT' state, the MSC-S is disconnected from the RNC/BSC. The MGW now has two bearers: T_B (to B party) and T_C (to C party). The MSC-S is connected to the B party via a green dotted line, and the C party is connected to the MGW via a red dotted line.](eb450c92214e8409c1e0f0846e30d876_img.jpg) + +Figure 13.23: ECT (Network model) diagram showing the network configuration before and after an Explicit Call Transfer (ECT) request. The diagram consists of two parts: 'Before ECT request:' and 'After ECT:'. In the 'Before' state, an MSC-S is connected to an RNC/BSC (served party) and an MGW. The MGW has three bearers: T\_A (to RNC/BSC), T\_B (to B party), and T\_C (to C party). The MSC-S is connected to the B party via a green dotted line. In the 'After ECT' state, the MSC-S is disconnected from the RNC/BSC. The MGW now has two bearers: T\_B (to B party) and T\_C (to C party). The MSC-S is connected to the B party via a green dotted line, and the C party is connected to the MGW via a red dotted line. + +Figure 13.23: ECT (Network model) + +Figure 13.24 shows the message sequence example for the explicit call transfer when both calls have been answered. In the example the MSC server requests the MGW to move the bearer termination for the C-party in the active call to the same context which contains the bearer termination for the B-party. The held party is informed about the retrieval of the held call. Both the remote parties are informed about the call transfer. After the move the MSC server releases the call and the bearer connection towards the served mobile subscriber and requests the MGW to remove the bearer termination for the served mobile subscriber. + +![Sequence diagram for explicit call transfer (Figure 13.24).](1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg) + +The sequence diagram illustrates the interaction between four entities: UE, RNC/BSC, MSC-S, and MGW. The process is divided into two main phases indicated by green background bars. + +**Phase 1: A-B active, held / A-C active, idle** + +- The UE sends an **ECT req** to the MSC-S. +- The MSC-S sends a **Context (CAB)** message to the MGW. +- The MGW responds with **MOV.request (TC)** and **MOV.reply (TC)** messages. +- The MSC-S then sends **Call progress (to B)**, **Call Progress (to B)**, and **Call Progress (to C)** messages to the UE. +- The UE responds with an **ECT acknowledge** message to the MSC-S. + +**Phase 2: Call and bearer release** + +- The MSC-S sends a **Context (CAC)** message to the MGW. +- The MGW responds with **SUB.request (TA)** and **SUB.reply (TA)** messages. +- The MGW then sends a **Release Termination** message to the MSC-S. + +Sequence diagram for explicit call transfer (Figure 13.24). + +**Figure 13.24: Explicit call transfer; both calls answered (message sequence chart)** + +Figure 13.25 shows the message sequence example for the explicit call transfer when one call is answered and the other call has been delivered. In the example the MSC server requests the MGW to move the bearer termination for the C-party in the active call to the same context which contains the bearer termination for the B-party. The held party is informed about the retrieval of the held call. Both the remote parties are informed about the call transfer. After the move the MSC server releases the call and the bearer connection towards the served mobile subscriber and requests the MGW to remove the bearer termination for the served mobile subscriber. The B-party is informed about the active call when the C-party sends the Answer indication. + +![Figure 13.25: Explicit call transfer; other call delivered (message sequence chart). The diagram shows a sequence of messages between UE, RNC/BSC, MSC-S, and MGW. It starts with a green bar 'A-B active, held / A-C active, delivered'. The sequence includes: 1. UE sends ECT req to MSC-S. 2. MSC-S sends Context (C_AB) to RNC/BSC. 3. MSC-S sends MOV.request (T_C) to MGW. 4. MGW sends MOV.reply (T_C) to MSC-S. 5. MSC-S sends Call Progress (to B) to MGW. 6. MSC-S sends Call Progress (to B) to MGW. 7. MSC-S sends Call Progress (to C) to MGW. 8. MSC-S sends ECT acknowledge to UE. 9. A green bar 'Call and bearer release' appears. 10. MSC-S sends Context (C_AC) to RNC/BSC. 11. MSC-S sends SUB.request (T_A) to MGW. 12. MGW sends SUB.reply (T_A) to MSC-S. 13. MGW sends Release Termination to MSC-S. 14. MSC-S sends Answer (from C) to RNC/BSC. 15. MSC-S sends Call Progress (to B) to MGW.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +Figure 13.25: Explicit call transfer; other call delivered (message sequence chart). The diagram shows a sequence of messages between UE, RNC/BSC, MSC-S, and MGW. It starts with a green bar 'A-B active, held / A-C active, delivered'. The sequence includes: 1. UE sends ECT req to MSC-S. 2. MSC-S sends Context (C\_AB) to RNC/BSC. 3. MSC-S sends MOV.request (T\_C) to MGW. 4. MGW sends MOV.reply (T\_C) to MSC-S. 5. MSC-S sends Call Progress (to B) to MGW. 6. MSC-S sends Call Progress (to B) to MGW. 7. MSC-S sends Call Progress (to C) to MGW. 8. MSC-S sends ECT acknowledge to UE. 9. A green bar 'Call and bearer release' appears. 10. MSC-S sends Context (C\_AC) to RNC/BSC. 11. MSC-S sends SUB.request (T\_A) to MGW. 12. MGW sends SUB.reply (T\_A) to MSC-S. 13. MGW sends Release Termination to MSC-S. 14. MSC-S sends Answer (from C) to RNC/BSC. 15. MSC-S sends Call Progress (to B) to MGW. + +Figure 13.25: Explicit call transfer; other call delivered (message sequence chart) + +## 13.13 Completion of Calls to Busy Subscriber (CCBS) + +The procedures specified in 3GPP TS 23.093 [16] for the Completion of Calls to Busy Subscriber supplementary service and 3GPP TS 23.108 [18] shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +### 13.13.1 Clearing when tones/announcements are provided to the calling subscriber + +If an announcement is to be provided for the purpose of notifying the subscriber that CCBS activation is possible, the MSC server shall select an MGW. The MGW performs the traffic channel assignment if the bearer termination has not been through-connected (as described in clause 6.1 for the basic mobile originating call). The MGW through-connects the bearer before providing the in-band information. The MSC server requests the MGW to play an announcement/tone using the Play Announcement or Send Tone procedure. When the announcement has completed the MGW notifies the MSC server (using the Announcement Completed procedure as described in clause 14.6) that the announcement is complete. + +Otherwise the MSC server handles the call clearing as described in clause 7. + +### 13.13.2 Network initiated mobile originated call + +The call is established as described in clause 6.1 for basic mobile originating call. + +#### 13.13.2.1 Early Traffic Channel Assignment + +Within CCBS there is an option for a CCBS call to establish a bearer before setup in state "CC-establishment confirmed". In this case the MSC server shall check whether an access bearer assignment modification has to be performed after receiving the setup message from UE. + +##### 13.13.2.1.1 Example + +For the network model, please refer to figure 6.1. + +Figure 13.26 shows the message sequence chart for the network initiated mobile originating call using the option assignment after A and B party alerting. In the following, the case with backward bearer establishment is considered. + +![Sequence diagram for network initiated mobile originating call establishment. Lifelines: UE, RNC/BSC, MSC-S, MGW. The process involves PAGING + SECURITY, CCBS RECALL, SETUP, CALL PROCEEDING, Initial Address, ADD.request ($), Context (C1), ADD.reply (T2), Bearer Establishment, Context (C1), Context (C$), ADD.request ($), Context (C1), ADD.reply (T1), RAB ASSIGNMENT REQ, Bearer Establishment, RAB ASSIGNMENT COMPL, Continuity, Address Complete, ALERTING, Answer, Context (C1), MOD.request (T2), Context (C1), MOD.reply (T2), Activate Inter-Working function (when applicable) + Activate Voice Processing function (when applicable), and CONNECT.](5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC/BSC + participant MSC-S + participant MGW + + Note over UE, RNC/BSC: PAGING + SECURITY + RNC/BSC->>UE: CCBS RECALL + RNC/BSC->>MSC-S: SETUP + MSC-S->>UE: CALL PROCEEDING + Note over MSC-S, MGW: Initial Address + MSC-S->>MGW: ADD.request ($), Context (C1) + MGW->>MSC-S: ADD.reply (T2), Context (C1) + Note over MGW: Bearer Establishment + MSC-S->>MGW: ADD.request ($), Context (C$) + MGW->>MSC-S: ADD.reply (T1), Context (C1) + Note over MGW: Prepare Bearer + Change Through-Connection + Activate Inter-Working function (when applicable) + Activate Voice Processing function (when applicable) + MSC-S->>RNC/BSC: RAB ASSIGNMENT REQ + Note over RNC/BSC, MGW: Bearer Establishment + RNC/BSC->>MSC-S: RAB ASSIGNMENT COMPL + MSC-S->>MGW: Continuity + MSC-S->>UE: ALERTING + MSC-S->>MGW: Address Complete + MSC-S->>UE: Answer + Note over MSC-S, MGW: Activate Inter-Working function (when applicable) + Activate Voice Processing function (when applicable) + MSC-S->>MGW: MOD.request (T2), Context (C1) + MGW->>MSC-S: MOD.reply (T2), Context (C1) + MSC-S->>UE: CONNECT + +``` + +Sequence diagram for network initiated mobile originating call establishment. Lifelines: UE, RNC/BSC, MSC-S, MGW. The process involves PAGING + SECURITY, CCBS RECALL, SETUP, CALL PROCEEDING, Initial Address, ADD.request (\$), Context (C1), ADD.reply (T2), Bearer Establishment, Context (C1), Context (C\$), ADD.request (\$), Context (C1), ADD.reply (T1), RAB ASSIGNMENT REQ, Bearer Establishment, RAB ASSIGNMENT COMPL, Continuity, Address Complete, ALERTING, Answer, Context (C1), MOD.request (T2), Context (C1), MOD.reply (T2), Activate Inter-Working function (when applicable) + Activate Voice Processing function (when applicable), and CONNECT. + +Figure 13.26: Network initiated mobile originating call establishment with assignment after A and B party alerting (message sequence chart) + +### 13.13.3 CCBS Information conveyed by Call Signalling + +For CCBS, application specific information needs to be conveyed via the call signalling. Specific details of the CCBS information are described in 3GPP TS 23.093 [16]. + +## 13.14 Multiple Subscriber Profile (MSP) + +No impact. + +## 13.15 Multicall + +The procedures specified in 3GPP TS 23.135 [17] for the Multicall supplementary service shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. If out-of-band transcoder control is applied for a speech call, it shall be performed in accordance with 3GPP TS 23.153 [3]. + +### 13.15.1 Mobile Originating + +When the UE is in active mode and it makes a request for the multicall function on a new traffic channel, call and bearer establishment shall be as described for mobile originating call. + +When the UE is in active mode and it makes a request for the multicall function using an existing traffic channel, call and bearer establishment shall be as described for call hold function. An active call will be placed on hold and the additional originating call will be initiated. + +### 13.15.2 Mobile Terminating + +When the UE is in active mode and it makes a request for the multicall function on a new traffic channel, call and bearer establishment shall be as described for mobile terminating call. Access bearer assignment shall occur either after a Call Confirmed or a Connect message is received from the UE. + +When the UE is in active mode and it makes a request for the multicall function using an existing traffic channel, call and bearer establishment shall be as described for call hold function. An active call will be placed on hold and the additional terminating call will be initiated. + +## 13.16 Calling Name Presentation (CNAP) + +No impact. + +## 13.17 Alternate Speech/Fax + +The procedures for facsimile group 3 transparent/non-transparent shall be followed in accordance with 3GPP TS 43.045 [24] and 3GPP TS 23.146 [25]. The following clauses describe the additional requirements for the bearer independent CS core network. If out-of-band transcoder control is applied for a speech call, it shall be performed in accordance with 3GPP TS 23.153 [3]. + +Call and bearer establishment shall be handled as described in the Call Establishment clause. In order to change from speech to fax (or vice versa), the MSC server shall modify the access bearer as described in subclause 13.18.1. + +If the MGW responds with an error to any of the procedures initiated by the MSC server, or the MSC server receives a Bearer Failure procedure from the MGW, the MSC server may either clear the call or reject the change from speech to fax (or vice versa). + +After this possible modification, the MGW shall seize an interworking function if a PLMN Bearer Capability [4] has been supplied to the access side bearer termination. When the MSC server receives an answer indication, it shall request activation of the interworking function using the Activate Interworking Function procedure. + +## 13.18 Modification of the Access Bearer + +### 13.18.1 Modification of Bearer Characteristics + +The modification of the access bearer is possible during a call establishment and during an active call. If the MSC server needs to modify the access bearer, the existing bearer termination in the MGW is modified or a new access side bearer termination is created. The modification of the access bearer shall be performed in accordance with 3GPP TS 25.413 [26] or 3GPP TS 48.008 [27]. + +#### 13.18.1.1 Iu mode + +If the link characteristics for the existing access bearer need to be changed and the MSC server previously received a notification from the MGW that modification of link characteristics of the current transport connection is supported [refer to 26], the MSC server shall use the Modify Bearer Characteristics procedure to provide the MGW with the new + +bearer characteristics for the existing access side bearer termination. After the MGW has replied, the MSC server shall initiate the access bearer modification towards RAN. + +If the MSC server has not previously received a notification from the MGW that modification of existing link characteristics is supported, the MSC server shall use the Prepare Bearer procedure to request the MGW to add a new context and a new access side bearer termination, and to provide a bearer address and a binding reference. After the MGW has replied, the MSC server shall initiate the access bearer modification towards RAN using the provided bearer address and the binding reference. Upon successful access bearer modification, the MSC server shall connect the new access side bearer termination to the old context and release the old access side bearer termination. + +If the user plane mode of the modified access bearer is "Support Mode", the Iu UP will also be re-initialised as defined in [20]. + +#### 13.18.1.2 A/Gb mode + +The MSC server shall use the Modify Bearer Characteristics procedure for A interface TDM termination and may use the Modify Bearer Characteristics procedure or the Configure RTP Connection procedure for AoIP termination to the MGW to provide the new bearer characteristics for the existing access side bearer termination. After the MGW has replied, the MSC server shall initiate the access bearer modification towards GERAN. + +### 13.18.2 IWF Protocol Change + +If the MSC server has requested indication on IWF protocol events, the MGW informs the MSC server about changes related to IWF protocol, using the Protocol Negotiation Result and Rate Change procedures. + +For AoIP terminations there shall be no change to the AoIP Transport Layer Address (MGW) and AoIP Transport Layer Address (BSS) for Rate Changes in data calls. Instead the MSC shall include the previously returned Local Connection Address in any subsequent Assignment request to the BSS. + +## 13.19 GSM Fax + +The procedures for facsimile group 3 transparent service toward a GSM BSS shall be followed in accordance with 3GPP TS 43.045 [24]. The following clauses describe the additional requirements for the bearer independent CS core network. + +Call and bearer establishment shall be handled as described in the Call Establishment clause with the addition that the Rate Change Event Notification shall be requested. If the MGW detects a mismatch between the radio channel rate to the facsimile transmission speed then it shall indicate this to the MSC server by use of the rate change procedure. The MSC server shall initiate a new Assignment towards the GSM RAN and if successful modify the PLMN Bearer Capability and GSM Channel Coding at the associated access bearer termination using the Modify Bearer Characteristics procedure as described in 16.2.41 to signal to the MGW that fax transmission can continue. The sequence is shown in Figure 13.19/1. + +![Sequence diagram for GSM access Channel Mode Modify message. Lifelines: MS, BSC A, MSC-S, MGW, BSC B. The sequence starts with MGW sending Context(Cl) NOT.request [Event=ratechange] (T1) to MSC-S (1). MSC-S responds with Context(Cl) NOT.reply (T1) (2). BSC A sends Assignment to MS. A note indicates: 'If channel kept (otherwise assignment message may be sent to MS)'. MS sends Channel Mode Modify to BSC A, which forwards it to MSC-S. MSC-S sends Assignment Ack (3) to BSC A. BSC A sends Channel Mode Modify ACK to MS. MSC-S sends Context(Cl) MOD.request [Modify Bearer Characteristics (PLMN-BC), [GSMchannelCoding]] (T1) to MGW. MGW responds with Context(Cl) MOD.reply (T1).](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` + +sequenceDiagram + participant MS + participant BSC A + participant MSC-S + participant MGW + participant BSC B + + MGW->>MSC-S: Context(Cl) NOT.request [Event=ratechange] (T1) (1) + MSC-S-->>MGW: Context(Cl) NOT.reply (T1) (2) + BSC A->>MS: Assignment + Note right of MS: If channel kept (otherwise assignment message may be sent to MS) + MS->>BSC A: Channel Mode Modify + BSC A->>MSC-S: Channel Mode Modify + MSC-S-->>BSC A: Assignment Ack (3) + BSC A->>MS: Channel Mode Modify ACK + MSC-S->>MGW: Context(Cl) MOD.request [Modify Bearer Characteristics (PLMN-BC), [GSMchannelCoding]] (T1) + MGW-->>MSC-S: Context(Cl) MOD.reply (T1) + +``` + +Sequence diagram for GSM access Channel Mode Modify message. Lifelines: MS, BSC A, MSC-S, MGW, BSC B. The sequence starts with MGW sending Context(Cl) NOT.request [Event=ratechange] (T1) to MSC-S (1). MSC-S responds with Context(Cl) NOT.reply (T1) (2). BSC A sends Assignment to MS. A note indicates: 'If channel kept (otherwise assignment message may be sent to MS)'. MS sends Channel Mode Modify to BSC A, which forwards it to MSC-S. MSC-S sends Assignment Ack (3) to BSC A. BSC A sends Channel Mode Modify ACK to MS. MSC-S sends Context(Cl) MOD.request [Modify Bearer Characteristics (PLMN-BC), [GSMchannelCoding]] (T1) to MGW. MGW responds with Context(Cl) MOD.reply (T1). + +Figure 13.19/1: GSM access Channel Mode Modify message + +For AoIP terminations the Configure RTP Connection Point Procedure may be used instead of the Modify Bearer Characteristics procedure. + +## 13.20 Voice group call service (VGCS), Voice broadcast service (VBS) + +### 13.20.1 Beginning the Voice group call + +The procedures specified in 3GPP TS 43.068 [39] and 3GPP TS 48.008 [27] (for AoIP) for the Voice group call service shall be followed. For a Voice broadcast call the procedures in 3GPP TS 43.069 [40] and 3GPP TS 48.008 [27] (for AoIP) shall be followed. When the served mobile subscriber invokes a Voice group call service the MSC server selects an MGW that provides the conference bridge capabilities with enhancements to support Voice group calls. The MSC server shall estimate the size of the Conference terminations needed for the VGCS call from the data retrieved from GCR and reserves the requested number of Conference terminations for that call. The number of needed conference terminations is provided within the prepare bearer procedure. + +### 13.20.2 Talker change in Voice group call (1 channel model) + +If the MSC server decides that the talker shall use the uplink associated to the downlink of the ASCI broadcast (common group call) channel (1 channel model, see 3GPP TS 43.068 [39] or 3GPP TS 48.008 [27] (for AoIP)), the talker's speech is transferred via the uplink channel of the ASCI broadcast channel of the cell. The stream arrives within the MGW on the termination of the traffic channel serving the cell or BSS (enhanced A-interface) and is transferred to the conference function where the summarized conference signal is calculated. The resulting stream is then transferred to all conference terminations. The normal behaviour of a conference bridge is to subtract for each conference member its own speech (incoming stream) from the summarized signal, otherwise it hears itself (outgoing stream). Therefore the Talker context need to be modified by adding a new termination to the context which is connected to the listener context (see figure 13.20.5/3 and 13.20.5/5). The topology within the talker context is set oneway from uplink of the ASCI broadcast channel in direction to Conference bridge (old termination of the talker context) and the topology is set to Oneway from the new added termination towards the termination connected to the downlink of the ASCI broadcast channel. This is performed using establish bearer procedure and change flowdirection. To avoid, that the talker hears himself, the UE internally switches off the loudspeaker (muting/unmuting functionality, 3GPP TS 43.068 [39]) on request of the MSC server. + +### 13.20.3 Disconnect + +A dispatcher can leave or reenter the call at any time without any influence of the ongoing call. Only the dispatcher is disconnected as described in the clause for call clearing (see 3GPP TS 43.068 [39], 3GPP TS 43.069 [40]). + +The Voice group call can only be released by an authorised subscriber (see 3GPP TS 43.068 [39], 3GPP TS 43.069 [40]). If an authorised subscriber triggers the release of the group call all other parties are disconnected as described in the clause for call clearing. + +### 13.20.4 Failure handling in MSC server + +If resources for the Voice group call service cannot be allocated in any of the MGW resources assigned to the MSC server (e.g. not enough conference terminations are available with cause "510 - Insufficient resources"), then the MSC server shall reject the VGCS request. + +### 13.20.5 Example + +Figure 13.20.5/1 shows a possible network model of an anchor MSC for a voice group call when the Talker is on the dedicated channel. At call setup Dispatchers, R-MSC and the talker can be seen as a multi party call. The listeners are connected oneway in their context (bullet 1 and 2 in figure 13.20.5/2). In the example every kind of termination is shown in its own context. + +![Diagram of a VGCS call termination overview for a talker on a dedicated channel. It shows a rectangular box representing the MSC server context. Inside, at the top, a horizontal line with arrows at both ends connects two points. A diagonal line descends from the right point to a third point located in the lower right area. At the bottom of the box, the text 'VGCS Listener Ctx' is displayed.](63a2519518616620ef0e53d98b923c05_img.jpg) + +VGCS Listener Ctx + +Diagram of a VGCS call termination overview for a talker on a dedicated channel. It shows a rectangular box representing the MSC server context. Inside, at the top, a horizontal line with arrows at both ends connects two points. A diagonal line descends from the right point to a third point located in the lower right area. At the bottom of the box, the text 'VGCS Listener Ctx' is displayed. + +**Figure 13.20.5/1: VGCS call (termination overview for talker on dedicated channel)** + +If the talker is on a dedicated channel, the talker context contains two terminations which are connected bothway a termination overview is given in figure 13.20.5/1. + +Figure 13.20.5/2 shows the message flow establishment of a VGCS call with two cells and the talker is located in cell1 when the Talker is on the dedicated channel. To connect the parties to the VGCS Multi Party Bridge the MSC server requests the MGW to establish internal Nb connections between the bearer terminations in the VGCS Multi Party bridge context and the call leg contexts, using the standard external bearer setup procedures. VGCS call acknowledge (bullet 3 in figure 13.20.5/2) should be sent after the ASCI broadcast channel is established in the cell where the talker is located (see 3GPP TS 43.068 [39], 3GPP TS 43.069 [40]). + +![Message sequence chart showing interactions between two network entities.](ddee3e67e0dfc22e25188fa635a19558_img.jpg) + +The diagram is a message sequence chart representing the establishment of a VGCS call. It features two vertical lifelines, each topped with a rectangular box representing a network entity. A series of horizontal arrows represent messages exchanged between these entities. +- An initial arrow comes from the left into the first entity. +- Multiple bidirectional exchanges (arrows pointing left and right) occur between the two lifelines. +- Near the bottom, a small circle is placed on the left lifeline, from which a horizontal arrow points left. +- Several long horizontal arrows originate from the lifelines and point towards the right edge of the diagram, indicating messages sent to external entities. + +Message sequence chart showing interactions between two network entities. + +**Figure 13.20.5/2: Talker on dedicated channel (Message sequence chart)** + +Figure 13.20.5/3 shows a possible network model of an anchor MSC for a voice group call when the Talker is on one channel mode. + +![Sequence diagram for VGCS call termination overview for Talker on one channel model. It shows interactions between a Dispatcher, R-MSC, and multiple BSS entities (CELL1, CELL2, CELL-n) through various context and listener objects (T Disp, T RMSC, T Iker, T Listener, etc.) leading to a central summation node (Σ).](32ff77da4286b58c4778033acaa10836_img.jpg) + +The diagram illustrates the message flow for VGCS call termination. On the left, external entities are shown in boxes: **Dispatcher**, **R-MSC**, and three **BSS** boxes. These connect to internal objects within a large rectangular frame. **Dispatcher** connects to an oval containing **T Disp** and **T Disp1**, labeled **Dispatcher - Ctx**. **R-MSC** connects to an oval containing **T RMSC** and **T RMSC1**, labeled **R-MSC - Ctx**. The first **BSS** connects to a red oval containing **T Iker - Ctx**, **T CELL1**, and **T listen-T ik1**. The second **BSS** connects to an oval containing **T CELL2** and **T Listener1**. The third **BSS** connects to an oval containing **T CELL-n** and **T Listener-n**, labeled **VGCS Listener Ctx**. All these ovals have arrows pointing towards a large oval on the right. This large oval contains a central circle with the symbol **Σ** and is labeled **VGCS MPTY CTX**. Inside this large oval are objects **T Disp0**, **T RMSC0**, **T T ik0**, and **T Listener0**. Arrows from the left ovals point to these objects, and from these objects to the central **Σ** circle. Additionally, there are red and green arrows within the red oval, indicating internal message flows between **T Iker - Ctx**, **T CELL1**, and **T listen-T ik1**. + +Sequence diagram for VGCS call termination overview for Talker on one channel model. It shows interactions between a Dispatcher, R-MSC, and multiple BSS entities (CELL1, CELL2, CELL-n) through various context and listener objects (T Disp, T RMSC, T Iker, T Listener, etc.) leading to a central summation node (Σ). + +**Figure 13.20.5/3: VGCS call (termination overview for Talker on one channel model)** + +Figure 13.20.5/4 shows the message flow establishment of a VGCS call with two cells and the talker is located in cell1 when the Talker is on one channel mode. + +**Error:** + +45 + +**Error: Reference source not** + +![A diagram illustrating a sequence of operations between two vertical lines, possibly representing a protocol or a state transition system. The left vertical line has an incoming arrow from the top left and an outgoing arrow to the bottom left. The right vertical line has multiple outgoing arrows to the right. Between the lines, there are 12 horizontal segments. The first 8 segments each have a right-pointing arrow on the right line and a left-pointing arrow on the left line. The remaining 4 segments each have only a right-pointing arrow on the right line. Two rectangular boxes are positioned at the top, one above each vertical line.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +The diagram illustrates a sequence of interactions between two vertical lines, likely representing a protocol or a state transition system. At the top, two rectangular boxes are positioned, one above each vertical line. The left vertical line has an incoming arrow from the top left and an outgoing arrow to the bottom left. The right vertical line has multiple outgoing arrows to the right. Between the lines, there are 12 horizontal segments. The first 8 segments each have a right-pointing arrow on the right line and a left-pointing arrow on the left line. The remaining 4 segments each have only a right-pointing arrow on the right line. This pattern suggests a sequence of 8 bidirectional exchanges followed by 4 unidirectional outputs from the right side. + +A diagram illustrating a sequence of operations between two vertical lines, possibly representing a protocol or a state transition system. The left vertical line has an incoming arrow from the top left and an outgoing arrow to the bottom left. The right vertical line has multiple outgoing arrows to the right. Between the lines, there are 12 horizontal segments. The first 8 segments each have a right-pointing arrow on the right line and a left-pointing arrow on the left line. The remaining 4 segments each have only a right-pointing arrow on the right line. Two rectangular boxes are positioned at the top, one above each vertical line. + +**Figure 13.20.5/4: Talker on one channel mode (Message sequence chart)** + +Figure 13.20.5/5 shows the message flow of the talker move to uplink. + +If the MSC server decides that the talker shall use the uplink of the cell. The MSC server adds a termination to the talker context which is connected to the Listener context and changes the topology of the talker context (bullet 1 and 2 in figure 13.20.5/5). Substract of the termination of the talker is only performed when the MSC server decides to move an active talker to the ASCI broadcast channel (bullet 3 in figure 13.20.5/5). The termination towards the cell where the talker is located is moved to the talker context. Further talker changes or cell changes of the current talker would be handled with move commands related to the termination towards the cell where the talker is located (bullet 4 in figure 13.20.5/5). Thus the talker's speech to all the listeners in that cell is transmitted (broadcast channel). The termination overview after the talker is moved to the uplink is given in figure 13.20.5/3. + +![Figure 13.20.5/5: Information flow talker move to uplink (Message sequence chart). The diagram shows two rectangular boxes at the top, representing network entities. Below them is a large rectangular box representing a communication channel or interface. Four horizontal green arrows are shown within this channel, alternating between the two entities above. The first and third arrows point from left to right, while the second and fourth arrows point from right to left, indicating a sequence of four messages exchanged between the entities.](b44f89b176c971c7dd264c07bfef2c2a_img.jpg) + +Figure 13.20.5/5: Information flow talker move to uplink (Message sequence chart). The diagram shows two rectangular boxes at the top, representing network entities. Below them is a large rectangular box representing a communication channel or interface. Four horizontal green arrows are shown within this channel, alternating between the two entities above. The first and third arrows point from left to right, while the second and fourth arrows point from right to left, indicating a sequence of four messages exchanged between the entities. + +**Figure 13.20.5/5: Information flow talker move to uplink (Message sequence chart)** + +### 13.20.6 Voice group call and voice broadcast services with AoIP + +Figure 13.20.6/1 shows the example message flow for the establishment of a VGCS call when AoIP is used with two cells and when the talker is located in cell1 and the Talker is on a dedicated channel. Figure 13.20.5/1 shows the applicable possible network model of an anchor MSC for a voice group call when the talker is on the dedicated channel. + +Before the MSC server sends the Assignment Request to the BSC, the MSC server requests the MGW to reserve an RTP bearer termination using the Reserve RTP Connection Point procedure. + +The MSC server requests the MGW to reserve an IP Address and UDP Port and also may indicate that the IP interface type is for AoIP. The MGW reserves the RTP termination and indicates the IP address and UDP port number to the MSC server. + +The MSC server then requests access bearer assignment using the provided IP address and UDP Port. + +When the MSC server receives the BSSMAP ASSIGNMENT COMPLETE message, it shall send the BSC IP address and UDP Port to the MGW Access bearer termination using the Configure RTP Connection Point procedure. + +Error: + +47 + +Error: Reference source not + +![Sequence diagram showing protocol interaction between two entities with multiple message exchanges and a self-call.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +``` + + sequenceDiagram + participant L as Lifeline 1 + participant R as Lifeline 2 + Note over L,R: [External Message In] + ->>L: + L->>R: + R->>L: + Note right of R: [Blue lines] + L->>R: + R->>L: + L->>R: + R->>L: + L->>R: + R->>L: + L->>R: + R->>L: + L->>L: [Self-call circle] + R->>: + R->>: + +``` + +Sequence diagram showing protocol interaction between two entities with multiple message exchanges and a self-call. + +**Figure 13.20.6/1: Message sequence chart for a voice group call with AoIP when talker is on dedicated channel** + +--- + +# 14 Interactions with Other Network Features and Services + +NOTE: All message sequence charts in this clause are informative examples. + +## 14.1 Customised Applications for Mobile network Enhanced Logic (CAMEL) + +If the gsmSRF is co-located with the (G)MSC server, the gsmSRF is divided into a gsmSRF server and an MGW. The gsmSRF server terminates the CAP protocol and signals over the Mc interface to instruct its MGW to provide the required resource. All the logic of the gsmSRF is located in the gsmSRF server. The MGW provides only simple resources for playing a single announcement or tone, or detection of single DTMF tone pair. If one single resource in the MGW does not fulfil the requirement of the gsmSCF, the gsmSRF server has to use different resources in sequence to fulfil the whole requirement. + +The gsmSSF uses the capabilities of the (G)MSC server and the MGW to play announcements or send tones to the server. + +NOTE 1: In the subsequent figures within clause 14.1, the "Connect To Resource" scenario is used. However the other CAMEL Intelligent Peripheral (IP) scenarios are not intended to be excluded. No impacts are identified when applying these other CAMEL scenarios. + +NOTE 2: The gsmSRF functionality may be deployed within the MSC server, and either the current serving MGW or any MGW resource under the control of the current MSC server. + +### 14.1.1 Play Announcement/Send Tone + +The playing of an announcement or sending of a tone shall be performed in accordance with 3GPP TS 23.078 [10]. It is assumed that the MGW selected for the call has the capabilities to provide announcements and tones. + +When the gsmSCF requests the gsmSRF to play a specified announcement or tone, the gsmSRF orders the MGW to play the announcement or tone as described in clause 14.6. + +After the gsmSRF has received the announcement or tone completed notification from its MGW, it reports the announcement or tone completion to the gsmSCF. + +If the gsmSCF requests the gsmSRF to cancel the earlier started announcement or tone, the gsmSRF orders the MGW to stop playing the announcement or tone as described in clause 14.6. + +#### 14.1.1.1 Example of playing announcement by the gsmSRF + +![Figure 14.1: CAMEL Announcement Playing (message sequence chart). The diagram shows three lifelines: gsmSCF, (G)MSC-S/gsmSRF, and MGW/gsmSRF. The sequence of messages is: 1. gsmSCF sends 'Connect To Resource' to (G)MSC-S/gsmSRF. 2. gsmSCF sends 'Play Announcement' to (G)MSC-S/gsmSRF. 3. (G)MSC-S/gsmSRF sends a message to MGW/gsmSRF, which is represented by a green box labeled 'Play announcement'. 4. (G)MSC-S/gsmSRF sends 'Specialized Resource Report' back to gsmSCF.](0f1767577a073167eb9628d72034e083_img.jpg) + +``` +sequenceDiagram + participant gsmSCF + participant (G)MSC-S/gsmSRF + participant MGW/gsmSRF + gsmSCF->>(G)MSC-S/gsmSRF: Connect To Resource + gsmSCF->>(G)MSC-S/gsmSRF: Play Announcement + Note right of (G)MSC-S/gsmSRF: Play announcement + (G)MSC-S/gsmSRF->>gsmSCF: Specialized Resource Report +``` + +Figure 14.1: CAMEL Announcement Playing (message sequence chart). The diagram shows three lifelines: gsmSCF, (G)MSC-S/gsmSRF, and MGW/gsmSRF. The sequence of messages is: 1. gsmSCF sends 'Connect To Resource' to (G)MSC-S/gsmSRF. 2. gsmSCF sends 'Play Announcement' to (G)MSC-S/gsmSRF. 3. (G)MSC-S/gsmSRF sends a message to MGW/gsmSRF, which is represented by a green box labeled 'Play announcement'. 4. (G)MSC-S/gsmSRF sends 'Specialized Resource Report' back to gsmSCF. + +Figure 14.1: CAMEL Announcement Playing (message sequence chart) + +### 14.1.2 User Interaction + +The user interaction shall be performed in accordance with 3GPP TS 23.078 [10]. It shall be assumed that the MGW selected for the call has the capabilities to provide announcements. In bearer independent CS core network the DTMF digits can be propagated inband or out-of-band. + +#### 14.1.2.1 Play announcement + +When the gsmSCF requests the gsmSRF/SSF to play a specified announcement and to collect digits that are sent by the user the gsmSRF/SSF requests the MGW to play the announcement as described in clause 14.6. + +#### 14.1.2.2 Detect DTMF tones + +The gsmSRF/gsmSSF starts detecting DTMF tones, as described in clause 14.4.2, before it receives the announcement or tone completed notification (see clause 14.6). + +#### 14.1.2.3 Report DTMF tones + +The DTMF tones are reported to the gsmSRF/SSF as described in clause 14.4.2. After all requested digits are received the gsmSRF/SSF reports the digits to the gsmSCF. + +#### 14.1.2.4 Cancel prompt and collect user information + +If the gsmSCF requests the gsmSRF to cancel the prompt and collect user information procedure, which had been started earlier, the gsmSRF orders the MGW to stop playing the announcement or sending tone, if they are still in progress, using the Stop Announcement or the Stop Tone procedure. The gsmSRF shall also order the MGW to stop detecting DTMF tones using the Stop DTMF Detection procedure. + +![Figure 14.2: CAMEL User Interaction (message sequence chart). The diagram shows three lifelines: gsmSCF, gsmSRF/SSF, and MGW. The sequence starts with gsmSCF sending a 'Connect To Resource' message to gsmSRF/SSF. Next, gsmSCF sends a 'Prompt And Collect User Information' message to gsmSRF/SSF. gsmSRF/SSF then sends a message to MGW, which triggers two parallel processes: 'Inband DTMF detection and Play announcement' and 'Out-of-band DTMF detection'. Finally, gsmSRF/SSF sends an 'Ack' message back to gsmSCF, and gsmSCF sends another 'Prompt And Collect User Information' message to gsmSRF/SSF.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +``` + +sequenceDiagram + participant gsmSCF + participant gsmSRF/SSF + participant MGW + Note right of gsmSRF/SSF: Inband DTMF detection and Play announcement + Note right of gsmSRF/SSF: Out-of-band DTMF detection + gsmSCF->>gsmSRF/SSF: Connect To Resource + gsmSCF->>gsmSRF/SSF: Prompt And Collect User Information + gsmSRF/SSF->>MGW: + Note right of gsmSRF/SSF: Inband DTMF detection and Play announcement + Note right of gsmSRF/SSF: Out-of-band DTMF detection + gsmSRF/SSF->>gsmSCF: Ack + gsmSCF->>gsmSRF/SSF: Prompt And Collect User Information + +``` + +Figure 14.2: CAMEL User Interaction (message sequence chart). The diagram shows three lifelines: gsmSCF, gsmSRF/SSF, and MGW. The sequence starts with gsmSCF sending a 'Connect To Resource' message to gsmSRF/SSF. Next, gsmSCF sends a 'Prompt And Collect User Information' message to gsmSRF/SSF. gsmSRF/SSF then sends a message to MGW, which triggers two parallel processes: 'Inband DTMF detection and Play announcement' and 'Out-of-band DTMF detection'. Finally, gsmSRF/SSF sends an 'Ack' message back to gsmSCF, and gsmSCF sends another 'Prompt And Collect User Information' message to gsmSRF/SSF. + +**Figure 14.2: CAMEL User Interaction (message sequence chart)** + +NOTE: Since gsmSRF don not know whether DTMF digits are provided inband or out-of-band the gsmSRF has to be able to collect DTMF tones both inband and out-of-band. + +### 14.1.3 Call Party Handling (CPH) + +The procedures specified in 3GPP TS 23.078 [10] for Call Party Handling (CPH) shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +In contrast with HOLD and MPTY, the call parties created on instruction from the gsmSCF are not seen as separate calls in the Mobile Station, i.e. all call parties in a CPH configuration use the same *transaction id* towards the MS. In addition, CPH may take place in an MSC-S different from the one where the CAMEL served subscriber is registered. Furthermore, in CPH it is possible to have multiple call parties in separate *call segments* whereas the call hold supplementary service has a limit of one held call party and one active call. + +The gsmSCF always triggers the elementary procedures which are described in this subclause. CPH elementary procedures can be used in more complex procedures to provide useful services, but the more complex procedures are out of scope of this specification. + +NOTE: For simplicity, the figures below which show network models do not show the gsmSCF. The gsmSCF is in the HPLMN of the served (CAMEL) party. The GMSC-S is in the interrogating network (IPLMN). The MSC-S is in the VPLMN of the served party. + +#### Use of a multi-party (conference) bridge + +When the gsmSCF invokes a CPH procedure which requires the connection of three or more legs in a multi-party configuration, the MSC server selects an MGW which provides multi-party bridge capabilities. The timing of the selection of the MGW with the multi-party bridge capabilities is vendor specific. If the selected MGW is not the MGW which is used for the active call, the MSC server requests the MGW(s) to connect the bearer terminations of the participants to the selected MGW. The bearer terminations are connected together. + +#### 14.1.3.1 Call Party Handling concepts + +The relationship between Call Segments and voice connections is explained in 3GPP TS 23.078 [10] subclause 4.5.1. + +#### 14.1.3.2 Initiate Call Attempt procedure + +The Initiate Call Attempt (ICA) procedure is used either: + +- To create a new call (out-of-the-blue), in which case the gsmSCF makes the initial contact with the MSC-S, or +- To create an additional call party in an existing call. The new call party is always created in a new call segment. The existing call may have triggered contact with the gsmSCF based on CAMEL subscription information (MO + +or MT in VMSC, MT in GMSC, call forwarding etc), or the gsmSCF may have initiated the contact using the ICA procedure (out-of-the-blue). + +The gsmSCF may create additional call parties before it establishes the bearer to the calling party. The MSC-S/GMSC-S shall establish bearers to the additional call parties independently of the other parties, including the calling party. + +The leg which is created by the Initiate Call Attempt procedure is initially in the held state. + +##### 14.1.3.2.1 Example + +Figure 14.1.3/1 shows an example network model for the Initiate Call Attempt procedure with an establishment of a new call leg. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. The MSC-S seizes a new context with one bearer termination in the MGW which is used for the new call leg. + +![Figure 14.1.3/1 Initiate Call Attempt procedure (Network model). The diagram is split into two parts. The left part, 'A-B 2-party call before ICA:', shows an RNC/BSC connected to an MGW (CTX_AB) which is connected to an MSC-S. A green dotted line (bearer) goes from the RNC/BSC to the MSC-S, and a red dotted line (bearer) goes from the MSC-S to the 'B party'. A blue squared line (signalling) connects the RNC/BSC to the MGW and the MGW to the MSC-S. The right part, 'ICA for new call to C subscriber:', shows the same RNC/BSC and MGW (CTX_AB) connected to the MSC-S. A new green dotted line (bearer) is added from the MSC-S to a 'C party'. A new blue squared line (signalling) is added from the MSC-S to a new MGW context (CTX_C), which is then connected to the 'C party' via another green dotted line. The 'B party' connection remains.](78e846f2858d131dc5a4dcbabcca1e4d_img.jpg) + +Figure 14.1.3/1 Initiate Call Attempt procedure (Network model). The diagram is split into two parts. The left part, 'A-B 2-party call before ICA:', shows an RNC/BSC connected to an MGW (CTX\_AB) which is connected to an MSC-S. A green dotted line (bearer) goes from the RNC/BSC to the MSC-S, and a red dotted line (bearer) goes from the MSC-S to the 'B party'. A blue squared line (signalling) connects the RNC/BSC to the MGW and the MGW to the MSC-S. The right part, 'ICA for new call to C subscriber:', shows the same RNC/BSC and MGW (CTX\_AB) connected to the MSC-S. A new green dotted line (bearer) is added from the MSC-S to a 'C party'. A new blue squared line (signalling) is added from the MSC-S to a new MGW context (CTX\_C), which is then connected to the 'C party' via another green dotted line. The 'B party' connection remains. + +**Figure 14.1.3/1 Initiate Call Attempt procedure (Network model)** + +Figure 14.1.3/2 shows an example message sequence for the Initiate Call Attempt procedure. + +In this example a new call leg to the C-party is established. + +![Sequence diagram for Initiate Call Attempt showing interactions between gsmSCF, (G)MSC-S, and MGW.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +``` +sequenceDiagram + participant gsmSCF + participant (G)MSC-S + participant MGW + + Note left of gsmSCF: Initiate Call Attempt + gsmSCF->>(G)MSC-S: Context($) +gsmSCF->>(G)MSC-S: Context(Cc) + (G)MSC-S->>MGW: ADD.request($) +MGW-->>(G)MSC-S: ADD.reply(Tc) + Note left of gsmSCF: Initiate Call Attempt Ack + gsmSCF->>(G)MSC-S: + Note over gsmSCF, (G)MSC-S: CAP operations + Note left of gsmSCF: Continue With Argument + gsmSCF->>(G)MSC-S: + Note over (G)MSC-S, MGW: Call and Bearer Establishment => C-party +``` + +The sequence diagram illustrates the information flow for an Initiate Call Attempt. It involves three main entities: gsmSCF, (G)MSC-S, and MGW. The process begins with the gsmSCF sending an 'Initiate Call Attempt' message to the (G)MSC-S. The (G)MSC-S responds with two context messages, 'Context(\$)' and 'Context(Cc)'. The (G)MSC-S then sends an 'ADD.request(\$)' to the MGW, which replies with 'ADD.reply(Tc)'. The gsmSCF receives an 'Initiate Call Attempt Ack' from the (G)MSC-S. A 'CAP operations' block is shown between the gsmSCF and (G)MSC-S. The gsmSCF sends a 'Continue With Argument' message to the (G)MSC-S. Finally, a 'Call and Bearer Establishment => C-party' block is shown between the (G)MSC-S and MGW. + +Sequence diagram for Initiate Call Attempt showing interactions between gsmSCF, (G)MSC-S, and MGW. + +Figure 14. 1.3/2 Information flow for Initiate Call Attempt (message sequence chart) + +#### 14.1.3.3 Move Leg procedure + +The Move Leg procedure is used to move a leg from its current call segment to the (existing) target call segment. + +Using Move Leg to add a leg to a call segment which already includes 2 call legs requires the establishment of a multiparty call (if it does not already exist for the served CAMEL subscriber) as described in clause 13.7. Other call parties may be involved in independent Multiparty calls due to MPTY SS or CPH. If the call segment to which the specified leg is added is already using a multi-party bridge, the MSC server requests the MGW to establish the connection between the specified leg and the multi-party bridge. + +##### Example + +Figure 14. 1.3/3 shows an example network model for the Move Leg procedure. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer + +![Network diagram showing MSC-S connected to RNC/BSC and MGW. MGW has two contexts: CTX_AB and CTX_C. The C party is connected to CTX_C. Network diagram showing MSC-S connected to RNC/BSC and MGW. MGW now has only CTX_AB context, and the C party is moved to it.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +Situation before MoveLeg + +Situation after MoveLeg + +Network diagram showing MSC-S connected to RNC/BSC and MGW. MGW has two contexts: CTX\_AB and CTX\_C. The C party is connected to CTX\_C. Network diagram showing MSC-S connected to RNC/BSC and MGW. MGW now has only CTX\_AB context, and the C party is moved to it. + +**Figure 14. 1.3/3 Move Leg procedure (Network model)** + +Figure 14. 1.3/4 shows an example message sequence for the Move Leg procedure. + +In this example the leg of the C-party is moved to an existing call segment. The MSC-S requests the MGW to move the bearer termination for the C-party to the same Context which contains the bearer termination for the A-party + +![Message sequence chart for Move Leg procedure. gsmSCF sends MoveLeg to (G)MSC-S. (G)MSC-S sends MOVE.request(Tc) to MGW. MGW replies with MOVE.reply(Tc). (G)MSC-S returns result to gsmSCF. Action: Move Tc to CAB.](458fdbcb4015a4ee90bd84809afc4aac_img.jpg) + +Message sequence chart for Move Leg procedure. gsmSCF sends MoveLeg to (G)MSC-S. (G)MSC-S sends MOVE.request(Tc) to MGW. MGW replies with MOVE.reply(Tc). (G)MSC-S returns result to gsmSCF. Action: Move Tc to CAB. + +**Figure 14. 1.3/4 Information flow for Move Leg (message sequence chart)** + +#### 14.1.3.4 Split Leg procedure + +The Split Leg procedure is used to separate a call leg from a source call segment and place it in a (new) target call segment. + +When the gsmSCF uses the Split Leg procedure to put a call leg on hold, the MSC server instructs the MGW to interrupt the connection between the specified call leg and the other party/parties in the call segment. If the call segment is using a multi-party bridge, the connection from the specified call leg to the multi-party bridge is interrupted. + +##### Example + +Figure 14. 1.3/5 shows an example network model for Split Leg procedure. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. + +![Figure 14. 1.3/5 Split Leg procedure (Network model)](508bc574df81fa8d3027a374f6d155fc_img.jpg) + +The diagram illustrates the network model for the Split Leg procedure in two states: 'Situation before SplitLeg' and 'Situation after SplitLeg'. + +**Situation before SplitLeg:** An RNC/BSC is connected to an MGW (labeled CTXAB). The MGW is connected to an MSC-S. A green dotted line (bearer) originates from the RNC/BSC and goes to the MSC-S. A red dotted line (bearer control signalling) originates from the RNC/BSC and goes to the MGW. A blue squared line (call control signalling) originates from the MSC-S and goes to the MGW. A red dotted line (bearer control signalling) originates from the MGW and goes to the B party. + +**Situation after SplitLeg:** The RNC/BSC is connected to an MGW (labeled CTXAB). The MGW is connected to an MSC-S. A green dotted line (bearer) originates from the RNC/BSC and goes to the MSC-S. A red dotted line (bearer control signalling) originates from the RNC/BSC and goes to the MGW. A blue squared line (call control signalling) originates from the MSC-S and goes to the MGW. A red dotted line (bearer control signalling) originates from the MGW and goes to the B party. A new blue squared line (call control signalling) originates from the MSC-S and goes to a new MGW (labeled CTXB). A red dotted line (bearer control signalling) originates from the new MGW and goes to the B party. + +Figure 14. 1.3/5 Split Leg procedure (Network model) + +Figure 14. 1.3/5 Split Leg procedure (Network model) + +Figure 14. 1.3/6 shows an example message sequence for the Split Leg procedure. + +In this example the leg of the B-party is moved to a new call segment. The MSC-S requests the MGW to move the bearer termination for the B-party in the active call to a new context. + +![Figure 14. 1.3/6 Information flow for Split Leg (message sequence chart)](9e4f582a5d5f6742d1372956db0f8f0b_img.jpg) + +The message sequence chart shows the interaction between gsmSCF, (G)MSC-S, and MGW. + +- The gsmSCF sends a **SplitLeg** message to the (G)MSC-S. +- The (G)MSC-S sends a **MOVE.request(TB)** message to the MGW. +- The MGW responds with a **MOVE.reply(TB)** message to the (G)MSC-S. +- The (G)MSC-S sends a **Return Result** message to the gsmSCF. + +During the process, the (G)MSC-S maintains two contexts: **Context (CS)** and **Context (CB)**. The MGW performs the action **Move TB to CB**. + +Figure 14. 1.3/6 Information flow for Split Leg (message sequence chart) + +Figure 14. 1.3/6 Information flow for Split Leg (message sequence chart) + +#### 14.1.3.5 CAMEL User interaction procedure + +In accordance with 3GPP TS 23.078 [10] the gsmSCF may order the MSC-S/gsmSSF to play an announcement or control user interaction as specified in subclauses 14.1.1 and 14.1.2 respectively. The tones are provided in accordance with subclause 14.6 of the present document. As part of Call Party Handling, announcements or tones can be played to an individual party or to all the parties connected in the call segment. + +The gsmSCF may also instruct the MSC-S to establish a temporary connection to an external device which provides the user interaction. + +#### 14.1.3.6 Failure handling in the MSC-S + +If resources for Call Party Handling cannot be allocated in any of the MGWs assigned to the MSC-S, then the MSC-S shall reject the request for the Call Party Handling procedure. + +## 14.2 IST + +The handling of IST shall be performed in accordance with 3GPP TS 42.032 [19]. This clause describes the additional requirements for the Bearer Independent CS Core Network. + +The clearing of calls due to IST is the same as for (G)MSC server initiated call clearing, refer to clause 7.3,(G)MSC server Initiated. + +## 14.3 Operator Determined Barring (ODB) + +NOTE: The subsequent clauses in 14.3 describe the impacts of "Barring of Outgoing Calls" and "Barring of Incoming Calls" on Bearer Independent CS CN. Other flavours of Operator Determined Barring may be supported by the Bearer Independent CS CN. However no impacts caused by these other flavours are identified. + +### 14.3.1 Barring of Outgoing Calls + +If the mobile station attempts to connect to an address determined to be barred by the Operator Determined Barring service, the call shall be cleared as described in clause 7, Call Clearing. + +Otherwise, the call is established as described in clause 6, Call Establishment. + +### 14.3.2 Barring of Incoming Calls + +If the incoming call to the mobile station is determined to be barred by the Operator Determined Barring service, the call shall be barred. Otherwise the call shall be delivered as described in clause 6, Call Establishment. + +If the GMSC connects the call to a recorded announcement due to Operator Determined Barring, the GMSC server selects the MGW before providing the in-band information. It is possible that the MGW selection is based on an MGW-Id received from the preceding node. + +The incoming side bearer establishment is handled in the GMSC server as described for the mobile terminating call using either forward or backward bearer establishment. + +In-band information may be provided to the calling subscriber only when both of the following conditions are satisfied: + +1. Either: + - 13 a. The incoming IAM indicated that the Continuity message will follow, and a Continuity message has been received, or + - 14 b. The incoming IAM did not indicate that the Continuity message will follow; +2. Notification indicating successful completion of the incoming side bearer set-up has been received from the MGW using the Bearer Established procedure. + +The GMSC server provides the MGW with the announcement identification and requests the MGW to notify the announcement completion using the Play Announcement procedure as described in clause 4.6. + +After the possible announcement has been completed the GMSC server initiates the call release as described in the clause 7, Call Clearing. + +## 14.4 DTMF + +DTMF information can be transported either inband or out of band. In order to minimise the interworking between out of band and in band DTMF signalling, the general principle is to use the DTMF signalling method of the preceding + +node whenever possible. A node supporting OoB DTMF shall also be able to receive inband DTMF digits, but no DTMF digits shall be duplicated, i.e. any detected digit shall either be sent forward by inband or out-of-band, but never by both methods. Transitions between inband and out-of-band may occur due to changes to an ongoing call (Explicit Call Transfer for example) but digits shall not be sent both inband and OoB for the same link. + +If out-of-band transcoder control is applied for a speech call, it shall be performed in accordance with 3GPP TS 23.153 [3] + +### 14.4.1 DTMF Tone Generation + +#### 14.4.1.1 Inband DTMF Tone Generation + +This option uses inband signalling to transport DTMF digits in the core network. + +The DTMF tone generation shall be performed in accordance with 3GPP TS 23.108 [18]. The following clauses describe the additional requirements for the bearer independent CS core network. + +##### 14.4.1.1.1 Start DTMF + +When the MSC server receives the Start DTMF message from the UE, it uses the Send DTMF procedure to request the MGW to modify the bearer termination to play a tone for the pressed digit. The result of the tone sending by the bearer termination will be received by the MSC server and sent to the UE (bullet 1 in figure 14.3). + +##### 14.4.1.1.2 Stop DTMF + +When the MSC server receives the Stop DTMF message from the UE, it uses the Stop DTMF procedure to request the MGW to modify the bearer termination to stop digit playing. When the response is received from the MGW, the MSC server will acknowledge the Stop DTMF (bullet 2 in figure 14.3). + +The MGW shall check the minimum duration and minimum interval in accordance with the DTMF timing defined in TS 23.014 [33]. + +##### 14.4.1.1.3 Example + +Figure 14.3 shows an example where out-of-band signalling of DTMF information is not supported by the call control protocol. When the UE sends Start DTMF and Stop DTMF messages, the MSC server uses resources in the MGW to generate tones by modifying the bearer termination. + +![Sequence diagram for Inband DTMF generation showing interactions between UE, RNC, MSC-S, and MGW.](9b25cfd1657391070da4ca3e922b82b1_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC + participant MSC-S + participant MGW + + Note right of MGW: Send DTMF + UE->>MSC-S: START DTMF + Note right of MSC-S: 1 + MSC-S->>MGW: Context (Cx) + MSC-S->>MGW: MOD.request (Tx) + MGW-->>MSC-S: Context (Cx) + MGW-->>MSC-S: MOD.reply (Tx) + MSC-S->>UE: START DTMF ACK + + Note right of MGW: Stop DTMF + UE->>MSC-S: STOP DTMF + Note right of MSC-S: 2 + MSC-S->>MGW: Context (Cx) + MSC-S->>MGW: MOD.request + MGW-->>MSC-S: Context (Cx) + MGW-->>MSC-S: MOD.reply (Tx) + MSC-S->>UE: STOP DTMF ACK + +``` + +The sequence diagram illustrates the interaction for inband DTMF generation. It involves four lifelines: UE, RNC, MSC-S, and MGW. The process is divided into two main parts, labeled 1 and 2. In part 1, the UE sends a START DTMF message to the MSC-S. The MSC-S then sends a Context (Cx) message and a MOD.request (Tx) message to the MGW. The MGW responds with Context (Cx) and MOD.reply (Tx) messages. Finally, the MSC-S sends a START DTMF ACK message back to the UE. A label 'Send DTMF' is placed next to the MGW lifeline. In part 2, the UE sends a STOP DTMF message to the MSC-S. The MSC-S sends a Context (Cx) message and a MOD.request message to the MGW. The MGW responds with Context (Cx) and MOD.reply (Tx) messages. Finally, the MSC-S sends a STOP DTMF ACK message back to the UE. A label 'Stop DTMF' is placed next to the MGW lifeline. + +Sequence diagram for Inband DTMF generation showing interactions between UE, RNC, MSC-S, and MGW. + +Figure 14.3: Inband DTMF generation (message sequence chart) + +#### 14.4.1.2 Out-of-Band DTMF Tone Generation + +This option uses out-of-band network signalling to transport DTMF digits in the core network, where the information is sent on a call control layer. + +The DTMF Tone Generation shall be performed in accordance with 3GPP TS 23.108 [18]. The following clauses describe the additional requirements for the bearer independent CS core network. + +##### 14.4.1.2.1 Start DTMF + +When the MSC server receives a Start DTMF message from the UE, it indicates digit playing using out-of-band signalling. The corresponding result received from the preceding/succeeding node will be sent to the UE (bullet 1 in figure 14.4). + +##### 14.4.1.2.2 Stop DTMF + +When the MSC server receives a Stop DTMF message from the UE, it indicates stop digit playing using out-of-band signalling. The succeeding node will indicate that digit playing is stopped. The MSC server will send the result back to the UE (bullet 2 in figure 14.4). + +##### 14.4.1.2.3 Example + +Figure 14.4 shows the message sequence example for the out-of-band DTMF during a call. When the MSC server receives the Start DTMF and Stop DTMF messages from the UE, it shall send the information using signalling on call control layer. The MSC server will not use any dedicated resources of the MGW. + +![Sequence diagram for Out-of-Band DTMF generation showing interactions between UE, RNC, MSC-S, and Ext.](44c649b1c110b4cd617810ae17342927_img.jpg) + +``` +sequenceDiagram + participant UE + participant RNC + participant MSC-S + participant Ext + + Note left of UE: START DTMF + UE->>MSC-S: START DTMF + Note right of MSC-S: 1 + MSC-S->>Ext: Start DTMF + Ext-->>MSC-S: Start DTMF Ack + Note right of MSC-S: 2 + MSC-S->>UE: START DTMF ACK + Note left of UE: STOP DTMF + UE->>MSC-S: STOP DTMF + Note right of MSC-S: 2 + MSC-S->>Ext: Stop DTMF + Ext-->>MSC-S: Stop DTMF Ack + Note right of MSC-S: 2 + MSC-S->>UE: STOP DTMF ACK +``` + +The diagram illustrates the message sequence for out-of-band DTMF generation. It involves four entities: UE (User Equipment), RNC (Radio Network Controller), MSC-S (MSC Server), and Ext (External entity). The sequence starts with the UE sending a 'START DTMF' message to the MSC-S. The MSC-S then sends a 'Start DTMF' message to the Ext entity. The Ext entity responds with a 'Start DTMF Ack' message to the MSC-S. The MSC-S then sends a 'START DTMF ACK' message back to the UE. Next, the UE sends a 'STOP DTMF' message to the MSC-S. The MSC-S sends a 'Stop DTMF' message to the Ext entity. The Ext entity responds with a 'Stop DTMF Ack' message to the MSC-S. Finally, the MSC-S sends a 'STOP DTMF ACK' message back to the UE. Circled numbers 1 and 2 are used to mark specific points in the sequence: 1 is at the MSC-S to Ext 'Start DTMF' message, and 2 is at the MSC-S to Ext 'Stop DTMF' message. + +Sequence diagram for Out-of-Band DTMF generation showing interactions between UE, RNC, MSC-S, and Ext. + +Figure 14.4: Out-of-Band DTMF generation (message sequence chart) + +### 14.4.2 DTMF Detection + +#### 14.4.2.1 Inband DTMF Detection + +The (G)MSC server/gsmSSF/gsmSRF requests the MGW to detect DTMF tones using Detect DTMF procedure (bullet 1 in figure 14.5). + +At detection of the DTMF tone the MGW reports the digit to the (G)MSC server/gsmSSF/gsmSRF using the Report DTMF procedure (bullet 2 in figure 14.5). At reception of the DTMF tone report the (G)MSC server/gsmSSF/gsmSRF either expects the MGW to detect other DTMF tones (in which case no new Detect DTMF request needs to be sent) or requests the MGW to stop the detection of DTMF tone (bullet 3 in figure 14.5) using the Stop DTMF Detection procedure. + +![Figure 14.5: Inband DTMF detection (message sequence chart). The diagram shows the interaction between (G)MSC-S and MGW. 1. (G)MSC-S sends a MOD.request (Tx) to MGW to 'Detect DTMF'. 2. MGW sends a NOTIFY.request (Tx) to (G)MSC-S to 'Report DTMF' after 'Digit 1, 2 or 3 Played'. 3. (G)MSC-S sends a MOD.request (Tx) to MGW to 'Stop DTMF Detection'. Both MOD.request and NOTIFY.request messages are associated with Context (Cx).](10b0dda884baae493ad958422d11b552_img.jpg) + +``` + +sequenceDiagram + participant (G)MSC-S + participant MGW + Note left of (G)MSC-S: Context (Cx) + (G)MSC-S->>MGW: MOD.request (Tx) + Note right of MGW: Detect DTMF + MGW-->>(G)MSC-S: MOD.reply (Tx) + Note left of (G)MSC-S: Context (Cx) + Note right of MGW: Digit 1, 2 or 3 Played + MGW->>(G)MSC-S: NOTIFY.request (Tx) + Note right of MGW: Report DTMF + Note left of (G)MSC-S: Context (Cx) + (G)MSC-S-->>MGW: NOTIFY.reply (Tx) + Note left of (G)MSC-S: Context (Cx) + (G)MSC-S->>MGW: MOD.request (Tx) + Note right of MGW: Stop DTMF Detection + Note left of (G)MSC-S: Context (Cx) + MGW-->>(G)MSC-S: MOD.reply (Tx) + +``` + +Figure 14.5: Inband DTMF detection (message sequence chart). The diagram shows the interaction between (G)MSC-S and MGW. 1. (G)MSC-S sends a MOD.request (Tx) to MGW to 'Detect DTMF'. 2. MGW sends a NOTIFY.request (Tx) to (G)MSC-S to 'Report DTMF' after 'Digit 1, 2 or 3 Played'. 3. (G)MSC-S sends a MOD.request (Tx) to MGW to 'Stop DTMF Detection'. Both MOD.request and NOTIFY.request messages are associated with Context (Cx). + +Figure 14.5: Inband DTMF detection (message sequence chart) + +#### 14.4.2.2 Out-of-Band DTMF Detection + +The (G)MSC server/gsmSSF/gsmSRF starts collecting out-of-band DTMF tones. One DTMF tone consists of Start DTMF (bullet 1 in figure 14.6) and Stop DTMF messages (bullet 2 in figure 14.6). + +![Figure 14.6: Out-of-Band DTMF detection (message sequence chart). The diagram shows the interaction between (G)MSC-S and MGW. 1. (G)MSC-S sends a Start DTMF message to MGW and receives a Start DTMF Ack. 2. (G)MSC-S sends a Stop DTMF message to MGW and receives a Stop DTMF Ack.](3263a25e110201638bda790456af2909_img.jpg) + +``` + +sequenceDiagram + participant (G)MSC-S + participant MGW + Note left of (G)MSC-S: Context (Cx) + (G)MSC-S->>MGW: Start DTMF + MGW-->>(G)MSC-S: Start DTMF Ack + Note left of (G)MSC-S: Context (Cx) + (G)MSC-S->>MGW: Stop DTMF + MGW-->>(G)MSC-S: Stop DTMF Ack + +``` + +Figure 14.6: Out-of-Band DTMF detection (message sequence chart). The diagram shows the interaction between (G)MSC-S and MGW. 1. (G)MSC-S sends a Start DTMF message to MGW and receives a Start DTMF Ack. 2. (G)MSC-S sends a Stop DTMF message to MGW and receives a Stop DTMF Ack. + +Figure 14.6: Out-of-Band DTMF detection (message sequence chart) + +## 14.5 OR + +The procedures specified in 3GPP TS 23.079 [11] for the Optimal Routeing network service shall be followed. The following clauses describe the additional requirements for the bearer independent CS core network. + +### 14.5.1 Optimal routeing for basic mobile-to-mobile calls + +The optimally routed call from one mobile subscriber to another mobile subscriber is established as a normal basic call. + +### 14.5.2 Optimal routeing for conditional call forwarding; Early call forwarding + +For early call forwarding the same procedures as described for CFU and CFNRc (rerouting by HLR) shall apply. + +### 14.5.3 Optimal routeing for conditional call forwarding; Late call forwarding + +#### 14.5.3.1 MSC server + +##### 14.5.3.1.1 Resume Call Handling and clearing of connection to GMSC server + +When the MSC server determines that the call should be forwarded because the called mobile subscriber is busy (NDUB, UDUB), not reachable or has not replied to the call before the no-reply timer has expired, the MSC server sends a request to resume call handling to the GMSC server. + +If the GMSC server determines that the call can be forwarded to the forwarded-to destination it sends a Release message to the MSC server. If no bearer has been established yet the MSC server handles the release only on call control level. If the bearer had been established, the MSC server handles the network side bearer release as described in the clause for the call clearing. + +##### 14.5.3.1.2 IU release + +When the MSC server determines that the call should be forwarded because the called mobile subscriber is busy (UDUB) or it has not replied to the call before the no-reply call timer has expired, the MSC server shall release the call and bearer connection to the served mobile subscriber as described in the clause for call clearing. + +#### 14.5.3.2 GMSC server + +##### 14.5.3.2.1 Resume Call Handling and Clearing of Connection to visited MSC server + +If the GMSC server determines that the call can be forwarded to the forwarded-to destination it sends a Release message to the MSC server and handles the outgoing side bearer release as described in the clause for call clearing, if the bearer had already been established. + +##### 14.5.3.2.2 MGW selection + +The GMSC server shall select an MGW for the bearer connection as described for the CFU and CFNRc (in HLR) supplementary services, if not already selected by the mobile terminating call procedures. + +##### 14.5.3.2.3 Incoming side bearer establishment + +The bearer establishment towards the preceding MGW is handled in the GMSC server as described for the mobile terminating call, if not already established by the mobile terminating call procedures. + +##### 14.5.3.2.4 Notification to the Calling Subscriber + +The GMSC server sends the possible notification towards the calling subscriber according to the procedures described for the CFU and CFNRc (in HLR) supplementary services. + +##### 14.5.3.2.5 Establishment of call and bearer towards the forwarded-to subscriber + +The GMSC server establishes the call and bearer towards the forwarded-to subscriber according to the procedures described for the CFU and CFNRc (in HLR) supplementary services. + +##### 14.5.3.2.6 Example + +Figure 14.7 shows the network model for optimal routeing when no bearer has been established before the invocation of late call forwarding. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. The GMSC server seizes one context with two bearer terminations in the MGW. The bearer termination $T_A$ is used for the bearer towards the preceding MGW (calling subscriber) and the bearer termination $T_C$ is used for the bearer towards the succeeding MGW (forwarded-to subscriber). + +![Network model diagram 'Before'. Two nodes, GMSC-S and MSC-S, are shown. A thick green dashed line representing the bearer path passes through both nodes. Inside each node, there are internal connection symbols. Network model diagram 'After'. GMSC-S is at the top, connected by a solid blue line to an MGW below it. The MGW contains a context CTX1 with two terminations, T_A and T_C. A thick red dotted line representing the bearer path enters at T_A and exits at T_C. The GMSC-S also has a thick green dashed line passing through it horizontally.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +Before CFB (NDUB), CFNRc: + +After CFB (NDUB), CFNRc: + +Network model diagram 'Before'. Two nodes, GMSC-S and MSC-S, are shown. A thick green dashed line representing the bearer path passes through both nodes. Inside each node, there are internal connection symbols. Network model diagram 'After'. GMSC-S is at the top, connected by a solid blue line to an MGW below it. The MGW contains a context CTX1 with two terminations, T\_A and T\_C. A thick red dotted line representing the bearer path enters at T\_A and exits at T\_C. The GMSC-S also has a thick green dashed line passing through it horizontally. + +**Figure 14.7: Optimal routeing; late call forwarding (CFB (NDUB), CFNRc) (Network model)** + +Figure 14.8 shows the message sequence example for the optimal routeing with late call forwarding without any notification to the calling party. In the example below no bearer has been established for the connection when the MSC server sends the Resume Call Handling request to the GMSC server. After the call towards the visited MSC server has been released the GMSC server establishes the call and the bearer as described for Call Forwarding Unconditional. + +![Message sequence chart for optimal routing. Vertical lifelines for GMSC-S, MGWgmsc, MSC-S, and MGWmsc. +1. Initial Address enters from left to GMSC-S. +2. GMSC-S sends Initial Address to MSC-S. +3. MSC-S triggers CFB (NDUB), CFNRc (green box). +4. MSC-S sends Resume Call Handling to GMSC-S (green box). +5. GMSC-S sends Release to MSC-S. +6. MSC-S sends Release Complete to GMSC-S. +7. A large green box at the bottom indicates 'Normal call and bearer establishment to forwarded-to subscriber'.](3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg) + +Message sequence chart for optimal routing. Vertical lifelines for GMSC-S, MGWgmsc, MSC-S, and MGWmsc. +1. Initial Address enters from left to GMSC-S. +2. GMSC-S sends Initial Address to MSC-S. +3. MSC-S triggers CFB (NDUB), CFNRc (green box). +4. MSC-S sends Resume Call Handling to GMSC-S (green box). +5. GMSC-S sends Release to MSC-S. +6. MSC-S sends Release Complete to GMSC-S. +7. A large green box at the bottom indicates 'Normal call and bearer establishment to forwarded-to subscriber'. + +NOTE: CFB Call Forwarding on Busy +NDUB Network Determined User Busy +CFNRc Call Forwarding on Not Reachable + +**Figure 14.8: Information flow for optimal routeing; late call forwarding (CFB (NDUB), CFNRc) (message sequence chart)** + +Figure 14.9 shows the network model for optimal routeing when a bearer has been established before the invocation of late call forwarding. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. The GMSC server replaces the bearer termination towards the visited MSC server ( $T_{MSC}$ ) with the bearer termination for the forwarded-to subscriber ( $T_C$ ) in an existing context in the MGW. The bearer termination $T_A$ is used for the bearer towards the preceding MGW (calling subscriber). + +![Diagram comparing network routing before and after CFB (UDUB). The 'Before' state shows a path from GMSC-S to MSC-S to CTXI MGW to CTXAB MGW to RNC. The 'After' state shows a direct path from GMSC-S to CTXI MGW.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +The diagram illustrates two network configurations for optimal routing with late call forwarding (CFB (UDUB), CFNRy, CD). + +**Before CFB (UDUB), CFNRy, CD:** This configuration shows a multi-hop path. At the top, a **GMSC-S** (Gateway Mobile Switching Center - Service) is connected to an **MSC-S** (Mobile Switching Center - Service) via a green dashed line. Below the **GMSC-S** is a **CTXI MGW** (Media Gateway) connected via a solid blue line. Below the **MSC-S** is a **CTXAB MGW** connected via a solid blue line. A third **RNC** (Radio Network Controller) is shown to the right of the **CTXAB MGW**. A green dashed line connects the **MSC-S** to the **RNC**. Red dotted lines represent other network paths: one from the left to the first **CTXI MGW** (labeled $T_x$ and $T_{MSC}$ ), and another from the **CTXAB MGW** (labeled $T_A$ and $T_B$ ) to the **RNC**. + +**After CFB (UDUB), CFNRy, CD:** This configuration shows a simplified path. The **GMSC-S** is now directly connected to the **CTXI MGW** via a solid blue line. The green dashed line from the **GMSC-S** continues to the right. The red dotted line from the left connects to the **CTXI MGW** (labeled $T_x$ and $T_c$ ). + +Diagram comparing network routing before and after CFB (UDUB). The 'Before' state shows a path from GMSC-S to MSC-S to CTXI MGW to CTXAB MGW to RNC. The 'After' state shows a direct path from GMSC-S to CTXI MGW. + +Figure 14.9: Optimal routeing; late call forwarding (CFB (UDUB), CFNRy, CD) (Network model) + +Figure 14.10 shows the message sequence example for the optimal routeing for late call forwarding with a forward bearer release. In the example the MSC server requests the MGW to remove the termination towards the served mobile subscriber after the bearer towards the RNC has been released. At reception of the release message from the GMSC server the MSC server requests the MGW to be prepared for the bearer release. When the GMSC server receives the Release Complete it requests the MGW to release the bearer. + +![Sequence diagram showing information flow for optimal call routing, late call forwarding (CFB (UDUB), CFNRy, CD), and forward bearer release. Lifelines: GMSC-S, MGWgmsc, MSC-S, MGWmsc, RNC, UE. The diagram is divided into phases: Mobile terminating call and bearer establishment, CFB(UDUB), No reply, CD, Call and bearer release, Resume Call Handling, Bearer release, and Call and bearer establishment to forwarded-to subscriber.](212c50c4e3d043c989037a01e13c1a98_img.jpg) + +``` + +sequenceDiagram + participant GMSC-S + participant MGWgmsc + participant MSC-S + participant MGWmsc + participant RNC + participant UE + + Note over GMSC-S, UE: Mobile terminating call and bearer establishment + + Note over MSC-S: CFB(UDUB), +No reply, CD + + Note over MSC-S, UE: Call and bearer release + + MSC-S->>MGWmsc: Context (CAB) + MGWmsc->>MSC-S: SUB.request (TB) + MSC-S->>MGWmsc: Context (CAB) + MGWmsc->>MSC-S: SUB.reply (TB) + Note right of MGWmsc: Release Termination + + Note over GMSC-S, MSC-S: Resume Call Handling + + GMSC-S->>MSC-S: Release + + MSC-S->>MGWmsc: Context (CAB) + MGWmsc->>MSC-S: SUB.request (TA) + MSC-S->>MGWmsc: Context (CAB) + MGWmsc->>MSC-S: SUB.reply (TA) + Note right of MGWmsc: Release Termination + + MSC-S->>GMSC-S: Release Complete + + GMSC-S->>MGWgmsc: Context (C1) MOD.request (TMSC) + MGWgmsc->>GMSC-S: Context (C1) MOD.reply (TMSC) + Note right of MGWgmsc: Release Bearer + + GMSC-S->>MGWgmsc: Context (C1) SUB.request (TMSC) + MGWgmsc->>GMSC-S: Context (C1) SUB.reply (TMSC) + Note right of MGWgmsc: Release Termination + + Note over MGWgmsc, MGWmsc: Bearer release + + Note over GMSC-S, UE: Call and bearer establishment to forwarded-to subscriber + +``` + +Sequence diagram showing information flow for optimal call routing, late call forwarding (CFB (UDUB), CFNRy, CD), and forward bearer release. Lifelines: GMSC-S, MGWgmsc, MSC-S, MGWmsc, RNC, UE. The diagram is divided into phases: Mobile terminating call and bearer establishment, CFB(UDUB), No reply, CD, Call and bearer release, Resume Call Handling, Bearer release, and Call and bearer establishment to forwarded-to subscriber. + +NOTE: CFB Call Forwarding on Busy + UDUB User Determined User Busy + CD Call Deflection + +**Figure 14.10: Information flow for optimal call routeing; late call forwarding (CFB (UDUB), CFNRy, CD), forward bearer release (message sequence chart)** + +Figure 14.11 shows the message sequence example for the optimal routing for late call forwarding with a backward bearer release. In the example the MSC server requests the MGW to remove the termination towards the served mobile subscriber after the bearer towards the RNC has been released. At reception of the release message from the GMSC server the MSC server requests the MGW to be release the bearer. When the GMSC server receives the Release Complete it requests the MGW to remove the bearer termination. + +![Sequence diagram for optimal call routing with late call forwarding and backward bearer release. Lifelines: GMSC-S, MGWgmsc, MSC-S, MGWmsc, RNC, UE. The diagram shows phases for call establishment, forwarding decision, release, and subsequent re-establishment.](376f80eb8a41369e87da63a0210d173e_img.jpg) + +``` + +sequenceDiagram + participant GMSC-S + participant MGWgmsc + participant MSC-S + participant MGWmsc + participant RNC + participant UE + + Note over all: Mobile terminating call and bearer establishment + Note over MSC-S: CFB(UDUB, No reply, CD) + Note over all: Call and bearer release + + MSC-S->>MGWmsc: Context (C_AB) SUB.request (T_B) + MGWmsc-->>MSC-S: Context (C_AB) SUB.reply (T_B) Release Termination + Note over all: Resume Call Handling + GMSC-S->>MSC-S: Release + MSC-S->>MGWmsc: Context (C_AB) MOD.request (T_A) + MGWmsc-->>MSC-S: Context (C_AB) MOD.reply (T_A) Release Bearer + MSC-S->>MGWmsc: Context (C_AB) SUB.request (T_A) + MGWmsc-->>MSC-S: Context (C_AB) SUB.reply (T_A) Release Termination + Note over all: Bearer release + GMSC-S->>MGWgmsc: Release Complete + Note over GMSC-S: Context (C1) + GMSC-S->>MGWgmsc: Context (C1) SUB.request (T_MSC) + Note over GMSC-S: Context (C1) + MGWgmsc-->>GMSC-S: Context (C1) SUB.reply (T_MSC) Release Termination + Note over all: Call and bearer establishment to forwarded-to subscriber + +``` + +Sequence diagram for optimal call routing with late call forwarding and backward bearer release. Lifelines: GMSC-S, MGWgmsc, MSC-S, MGWmsc, RNC, UE. The diagram shows phases for call establishment, forwarding decision, release, and subsequent re-establishment. + +NOTE: CFB Call Forwarding on Busy +UDUB User Determined User Busy +CD Call Deflection + +**Figure 14.11: Optimal call routing; late call forwarding (CFB (UDUB), CFNRy, CD), backward bearer release (message sequence chart)** + +## 14.6 Providing tones or announcements + +It shall be assumed that the MGW selected for the call has the capabilities to provide announcements and tones. + +### 14.6.1 Preconditions when providing in-band information to the calling subscriber + +For a mobile terminating/forwarded call, announcements/tones may be provided to the calling subscriber only when both of the following conditions are satisfied: + +1. Either: + - 15 a. The incoming IAM indicated that the Continuity message will follow, and a Continuity message has been received, or + - 16 b. The incoming IAM did not indicate that the Continuity message will follow; +2. Notification indicating successful completion of the incoming side bearer set-up has been received from the MGW using the Bearer Established procedure. + +For a mobile originating call, the traffic channel assignment shall be completed before providing the in-band information to the calling subscriber. + +### 14.6.2 Preconditions when providing in-band information to the called subscriber + +The called party is selected by the calling party, or a supplementary service (call forwarding, call deflection, CAMEL redirection etc), or a call is initiated by the gsmSCF using the Initiate Call Attempt procedure. The called party may also be in the PSTN. + +Announcements/tones may be provided to the called subscriber only when both of the following conditions are satisfied: + +1. The called party has answered and is still active in the call. +2. Notification indicating successful completion of the outgoing side bearer set-up has been received from the MGW using the Bearer Established procedure. + +### 14.6.3 Preconditions when providing in-band information to multiple subscribers + +The gsmSCF may instruct the MSC-S/gsmSSF to provide announcements or tones for multiple subscribers. For each calling and called subscriber the precondition for calling and called subscriber (respectively) shall be fulfilled. If the preconditions are not fulfilled for all subscribers (e.g. one of the called parties is in the alerting phase), then the announcements/tones shall not be played to the subscribers who do not meet the preconditions, but the announcements/tones shall be played to the subscribers (if any) who meet the preconditions. + +### 14.6.4 Request to play an announcement/tone + +The (G)MSC server/gsmSSF/gsmSRF provides the MGW with the announcement/tone identification and optionally requests the MGW to notify the announcement/tone completion using the Play Announcement or Send Tone procedure (bullet 1 in figure 14.13). + +### 14.6.5 Stopping an announcement/tone + +The (G)MSC server/gsmSSF/gsmSRF can order the MGW to stop the current announcement/tone using the Stop Announcement or Stop Tone procedure (bullet 2 in figure 14.13). + +### 14.6.6 Announcement/tone completed + +If notification of the announcement/tone completion was requested in the Play Announcement or Send Tone procedure, the MGW notifies the (G)MSC server/gsmSSF/gsmSRF when the announcement/tone has been completed using the Announcement Completed or Tone Completed procedure (bullet 3 in figure 14.13). + +### 14.6.7 Example 1 + +Figure 14.12 shows the network model for providing in-band information to the calling subscriber where the (G)MSC-S requests to play the announcement/tone directly on the desired termination from which the signal shall be sent. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. The bearer termination Tx is used for the bearer towards the preceding MGW (calling subscriber). + +A bearer termination Ty may exist in the same context towards the succeeding MGW (called subscriber) and may be both-way connected and through-connected with Tx. In that case, the exchange of media streams between the terminations Tx and Ty is assumed to be normally interrupted during playing the announcement in the direction towards which the announcement is played. + +![Figure 14.12: Providing in-band information (Network model). Two alternatives showing (G)MSC-S connected to MGW. Alternative 1 has one termination Tx. Alternative 2 has two terminations Tx and Ty.](f23879f003c58b57f690e2dc6c95816a_img.jpg) + +``` + +graph TD + subgraph "Alternative 1" + MSC1["(G)MSC-S"] --- MGW1["CTX x MGW"] + MGW1 --- Tx1["Tx"] + end + subgraph "Alternative 2" + MSC2["(G)MSC-S"] --- MGW2["CTX x MGW"] + MGW2 --- Tx2["Tx"] + MGW2 --- Ty2["Ty"] + end + +``` + +**Alternative 1** +with only Tx in the context + +**Alternative 2** +with Tx and Ty in the context + +Figure 14.12: Providing in-band information (Network model). Two alternatives showing (G)MSC-S connected to MGW. Alternative 1 has one termination Tx. Alternative 2 has two terminations Tx and Ty. + +**Figure 14.12: Providing in-band information +(Network model)** + +Figure 14.13 shows the message sequence example for providing the calling party with an announcement/tone. In the example the (G)MSC server requests the MGW to play an announcement/tone and to notify the announcement/tone completion. The (G)MSC server may stop the announcement while the current announcement/tone is ongoing. + +![Figure 14.13: Playing an announcement/tone (message sequence chart). The diagram shows a sequence of messages between (G)MSC-S and MGW. 1. (G)MSC-S sends MOD.request (Tx) to MGW, which plays the announcement/sends tone. MGW responds with MOD.reply (Tx). 2. (G)MSC-S sends another MOD.request (Tx) to MGW, which stops the announcement/stops tone. MGW responds with MOD.reply (Tx). 3. (G)MSC-S sends NOTIFY.request (Tx) to MGW, indicating announcement/tone completion. MGW responds with NOTIFY.reply (Tx). Context (Cx) is maintained throughout. OR1: Y indicates the first MOD.request is for stopping. OR2: Y indicates the NOTIFY.request is required.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +``` + +sequenceDiagram + participant (G)MSC-S + participant MGW + Note left of (G)MSC-S: Context (Cx) + (G)MSC-S->>MGW: MOD.request (Tx) + Note right of MGW: Play announcement / Send Tone + MGW-->>(G)MSC-S: MOD.reply (Tx) + Note left of (G)MSC-S: Context (Cx) + Note left of (G)MSC-S: OR1: Y + (G)MSC-S->>MGW: MOD.request (Tx) + Note right of MGW: Stop announcement / Stop tone + MGW-->>(G)MSC-S: MOD.reply (Tx) + Note left of (G)MSC-S: Context (Cx) + Note right of MGW: OR2: Y + (G)MSC-S->>MGW: NOTIFY.request (Tx) + Note right of MGW: Announcement completed / Tone completed + MGW-->>(G)MSC-S: NOTIFY.reply (Tx) + Note left of (G)MSC-S: Context (Cx) + +``` + +NOTE: OR1: Stop the announcement/tone (Y: yes N:no) +OR2: Notification of completion required (Y: yes N:no) + +Figure 14.13: Playing an announcement/tone (message sequence chart). The diagram shows a sequence of messages between (G)MSC-S and MGW. 1. (G)MSC-S sends MOD.request (Tx) to MGW, which plays the announcement/sends tone. MGW responds with MOD.reply (Tx). 2. (G)MSC-S sends another MOD.request (Tx) to MGW, which stops the announcement/stops tone. MGW responds with MOD.reply (Tx). 3. (G)MSC-S sends NOTIFY.request (Tx) to MGW, indicating announcement/tone completion. MGW responds with NOTIFY.reply (Tx). Context (Cx) is maintained throughout. OR1: Y indicates the first MOD.request is for stopping. OR2: Y indicates the NOTIFY.request is required. + +**Figure 14.13: Playing an announcement/tone (message sequence chart)** + +### 14.6.8 Example 2 + +Figure 14.6.8/1 shows the network model for providing in-band information to the calling subscriber where the (G)MSC-S requests to play the announcement/tone on another termination in the context connected via topology information to the desired termination(s). E.g. during the call setup, the MSC-S requests the MGW to send a ring back tone to the calling subscriber when receiving the indication that the called subscriber is being alerted. + +The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling and the bearer. The in-band information applied on the T0 termination is forwarded to the bearer termination(s) towards which the topology association is either 'oneway' or 'bothway', i.e. towards the Ta termination in this example. + +![Figure 14.6.8/1: Providing in-band information (Network model). The diagram shows a network model with MSC-S at the top, connected to T0. T0 is connected to two RNC/BSC units via Ta and Tb terminations. The RNC/BSC units are connected to CTX 1, which is connected to MGW.](2438c4dd81a8b76ec881d47d87b11fc3_img.jpg) + +``` + +graph TD + MSCS[MSC-S] --- T0[T0] + T0 -.- Ta[Ta] + T0 -.- Tb[Tb] + Ta -.- RNC1[RNC/BSC] + Tb -.- RNC2[RNC/BSC] + RNC1 --- CTX1[CTX 1] + RNC2 --- CTX1 + CTX1 --- MGW[MGW] + +``` + +Figure 14.6.8/1: Providing in-band information (Network model). The diagram shows a network model with MSC-S at the top, connected to T0. T0 is connected to two RNC/BSC units via Ta and Tb terminations. The RNC/BSC units are connected to CTX 1, which is connected to MGW. + +**Figure 14.6.8/1: Proving in-band information (Network model)** + +Figure 14.6.8/2 shows the message sequence example for providing the calling party with the announcement/tone. In the example the MSC requests the MGW to play an announcement/tone by seizing a new ephemeral + +announcement/tone termination with the indication that a tone or announcement shall be forwarded internally to the bearer termination(s) towards which the topology association is either 'oneway' or 'bothway'. + +(G)MSC-S            MGW + +Ta & Tb terminations added in the context, as per mobile originating & mobile terminating call flows + +| | | | +|--------------|---------------------|----------------------------------------------------------------------------| +| Context (C1) | ADD.request (T0) | Play announcement / Send Tone + | +| | 1 | | +| Context (C1) | ADD.reply (T0) | Change Flow Direction (Ta,Tb,isolate), (T0,Tb,isolate),
(T0, Ta,oneway) | +| | | OR1: Y | +| Context (C1) | NOTIFY.request (T0) | Announcement completed/
Tone completed | +| | 3 | | +| Context (C1) | NOTIFY.reply (T0) | | +| | | OR2: Y | +| Context (C1) | SUB.request (T0) | Release termination + | +| | 2 | | +| Context (C1) | SUB.reply ( T0) | Change Flow Direction (Ta, Tb, bothway) | + +NOTE OR1: Notification of completion required (Y: yes , N::no) + +OR2: Stop the announcement/tone (Y: yes , N::no) + +**Figure 14.6.8/2: Playing an announcement/tone (message sequence chart)** + +## 14.7 Global Text Telephony + +3GPP TS 23.226 [26] describes the high level architecture and functionality of GTT. When text based conversation is needed by a subscriber, the call is established with general call control functions like any other call. Within the call control transactions the UE indicates the need for text conversation (see 3GPP TS 24.008 [4]), which then requires actions in the core network where the pooling mechanism is chosen for GTT feature. This section describes only the option where the CTM pool is provided in the Media Gateway in the Core Network. + +MSC Server receives an indication by the UE about the need of text conversation, allocates terminations in MGW with CTM (Cellular Text telephony Modem) capabilities for the detection of CTM signals from radio access network. The default action of the call path in the CTM-detection/conversion function in MGW is to transfer audio transparently while monitoring for text telephone signals. When valid text telephone signals are detected, the converting action of the channel takes effect. The path converts between the detected CTM at the access termination and PSTN text telephony signalling methods on the network side. This mode of operation continues until text signalling ceases. Then transparent audio transport is re-established, again monitoring for text signals. + +The CTM channel is created with Prepare bearer for Iu/ATM terminations, Prepare IP Transport for Iu/IP terminations, Reserve circuit procedure for A interface over TDM terminations or with Reserve RTP Connection Point for A interface over IP by including Cellular Text Telephone package properties. The core network bearer shall be established with default PCM codec to carry the T.140 protocol. + +The outcome of CTM negotiation towards the CTM user in the user plane is reported in the CTM report procedure. + +At release the MGW may report the number of bits of Global Text Telephony data in accordance with ITU recommendation T.140 sent for the call. + +## 14.8 Emergency Calls + +Emergency Calls shall be handled as in clause 6.1 Basic Mobile Originating Call. and clause 6.2 Basic Mobile Terminating Call. The Procedure Emergency Call Indication may be used for informing the MGW about the emergency call. + +## 14.9 Subscriber and equipment trace + +For the subscriber and equipment trace the MSC server may be activated for tracing (see 3GPP 32.421 [34]). Besides performing trace record generation, if Signalling based activation the MSC server shall forward the Trace Session activation to GERAN with BSSAP signaling, UTRAN with RANAP signaling (see 3GPP TS 25.413) and if the trace control and configuration parameters are defined so, the MGW. For detailed description of trace session activation mechanism see 3GPP TS 32.422 [35]. The activation to the MGW is sent using a trace package which is included either to the Add or Modify command(s) in mobile originated call or mobile terminating call. In the case of handovers where new termination is created the trace package is also included into the Add command. If the MSC does not receive the optional trace interface list IE in the trace activation request it shall request tracing on all terminations that support the total MGW trace interfaces as defined in TS 32.422. The MSC Server shall only set the trace interface list value that is associated to the interface that the termination supports and optionally the Mc interface trace value if requested from the HLR. The content of the trace records generated in the MSC server and the MGW will follow the rules of 3GPP TS 32.421[34] and 3GPP TS 32.422[35], 3GPP TS 32.423 [36]. The content of the MGW and MSC Server trace record is described in TS 32.423 [36]. + +## 14.10 Customized Alerting Tone + +### 14.10.1 General + +Customised Alerting Tone may be provided from a "CAT Server" switched into the call at appropriate trigger points. The "CAT Server" is out of the scope of the 3GPP architecture and therefore the signalling procedures towards the CAT Server (if not collocated) are not described. + +The Forward CAT indicators and Backward CAT indicators information elements are specified in 3GPP TS 29.205 [22]. + +The following sub-clauses describe extensions to basic call handling and unless explicit exceptions are made all basic call protocol handling support is unchanged. + +### 14.10.2 Audio CAT + +#### 14.10.2.1 Audio CAT Activated by the Calling Party + +If the calling party subscriber has activated the CAT service (CAT-A) for audio and the subscriber is in its Home PLMN and the calling party subscriber gives priority to CAT-A, the originating MSC Server supporting the audio CAT-A service shall connect that calling party UE towards the CAT Server during alerting phase. The MSC Server is responsible for switching the user plane towards the CAT Server during alerting phase and then on receipt of answer message from the called party the MSC Server shall switch the user plane towards the called party and releasing the connection to the CAT Server. + +The originating MSC may indicate the CAT priority to the terminating network by setting the CAT Priority indicator of the Forward CAT indicators information element when sending an IAM to the succeeding node. + +If the calling party subscriber supports CAT-A but gives priority to CAT-B and the originating MSC receives an ACM or CPG from the succeeding network with the CAT content Indicator in the Backward CAT indicators information element set to "inband media content available" then it shall not switch the user plane towards the CAT Server. If however the originating MSC does not receive an indication that CAT-B is present then it shall switch the user plane towards the CAT server as described above for the CAT-A priority case. + +NOTE: Providing alerting tone at the calling party rather than from the called party network can cause voice clipping if the called party answers and speaks while the calling party network has not disconnected the inband alerting tone. + +#### 14.10.2.2 Audio CAT Activated by the Called Party + +If the called party subscriber has activated the CAT service (CAT-B) for audio, the GMSC Server supporting the audio CAT-B service shall check the CAT Priority indicator if the Forward CAT indicators information element is received. If CAT-A priority is requested the GMSC Server shall handle the call in accordance with normal call handling not supporting CAT-B service. If no CAT-A priority is received the GMSC Server shall connect the calling party network to the CAT Server during alerting phase. The GMSC Server should indicate in ACM or CPG message if CAT-B is inserted by setting the CAT content Indicator in the Backward CAT indicators information element. The GMSC Server is responsible for switching the user plane towards the CAT Server during alerting phase and then on receipt of answer message from the called party the GMSC Server shall switch the user plane towards the called party and releasing the connection to the CAT Server. + +### 14.10.3 Multimedia CAT + +#### 14.10.3.1 Introduction + +The following subclauses specify the mobile originated and mobile terminated multimedia call procedures to generate a multimedia CAT to a UE supporting the multimedia CAT capability. + +A UE supporting multimedia CAT will indicate support of this capability to the MSC server as specified in 3GPP TS 24.008 [4]. + +To play a multimedia CAT to such a UE, upon receiving the indication that the called party is being alerted and that a multimedia CAT is available, the MSC Server supporting multimedia CAT shall request the MGW to both-way through-connect the bearer towards the source of the multimedia CAT using the Change Through-Connection procedure, and then request the calling UE to attach to the user connection for multimedia as soon as an appropriate channel in multimedia mode is available and to set up an H.324 call by indicating "inband multimedia CAT available" within an ALERTING message or a PROGRESS message as specified in 3GPP TS 24.008 [4] subclause 5.3.6.4. + +#### 14.10.3.2 Multimedia CAT Activated by the Calling Party + +If the calling party subscriber has activated CAT service (CAT-A) for multimedia and the subscriber is in its Home PLMN and the calling party subscriber gives priority to CAT-A, the originating MSC Server supporting multimedia CAT-A service for multimedia it shall connect that calling UE towards the CAT Server during alerting phase. The MSC Server is responsible for switching the user plane towards the CAT Server during alerting phase and then on receipt of answer message from the called party the MSC Server shall switch the user plane towards the called party and release the connection to the CAT Server. + +The originating MSC may indicate CAT-A has priority to the terminating network by setting the CAT Priority indicator of the Forward CAT indicators information element to 'Priority given to Calling party (CAT-A)' when sending an IAM to the succeeding node. + +NOTE: As the Forward CAT indicators information element is required to be sent by the originating MSC with the Multimedia CAT capability Indicator set to "MCAT supported" if it permits multimedia CAT-B, the inclusion of the Forward CAT indicators information element is not strictly required since if no CAT parameters are included it has the same effect as indicate CAT-A has priority however it does provide explicit indication that the calling party supports CAT-A. + +If CAT-B is given priority then the Multimedia CAT capability Indicator of the Forward CAT indicators information element shall be set as described in subclause 14.10.3.3.1. + +If the calling party subscriber supports CAT-A but gives priority to CAT-B and the originating MSC receives an ACM or CPG from the succeeding network with the CAT content Indicator in the Backward CAT indicators information element set to "inband media content available" then it shall not switch the user plane towards the CAT Server and shall follow the procedures defined in subclause 14.10.3.3.1. If however the originating MSC does not receive an indication that CAT-B is present then it shall switch the user plane towards the CAT server as described above for the CAT-A priority case. + +#### 14.10.3.3 Multimedia CAT Activated by the Called Party + +##### 14.10.3.3.1 Mobile originated multimedia call + +If the calling UE supports the multimedia CAT service and no CAT-A priority exists, the originating MSC supporting the multimedia CAT service shall inform the succeeding node that multimedia CAT is supported by setting the Multimedia CAT capability Indicator of the Forward CAT indicators information element to "MCAT supported" in the IAM message sent to the succeeding node. + +The MSC Server supporting the multimedia CAT service shall consider that a multimedia CAT is available if it receives an ACM or CPG message including the Multimedia CAT content Indicator in the Backward CAT indicators information element set to "inband media content available". + +##### 14.10.3.3.2 Mobile terminated multimedia call + +If the called party subscriber supports the "CAT-B" service for multimedia and if the GMSC Server supporting the optional CAT-B service for multimedia receives the Multimedia CAT capability Indicator in the Forward CAT indicators information element set to "MCAT supported" in the IAM from the preceding node, the GMSC Server shall connect the calling party to the CAT Server during the alerting phase. + +To play a multimedia CAT to the calling subscriber, upon receiving the indication that the called party is being alerted, the GMSC supporting multimedia CAT shall request the MGW to establish, and both-way through-connect, a bearer connection towards a CAT Server. + +The GMSC shall inform the originating MSC that a multimedia CAT is available (if any) by setting the Multimedia CAT content Indicator of the Backward CAT indicators information element to "inband media content available" in the ACM or CPG message. + +##### 14.10.3.3.3 Example + +Figure 14.10.3.3.1 shows the message sequence chart example for providing multimedia CAT activated by the called party during a basic multimedia call establishment. In the example, the calling UE, the originating MSC and GMSC support the multimedia CAT capability. + +The calling UE initiates a multimedia call establishment during which it indicates that it supports multimedia CAT capability (bullet 1). The originating MSC sends an Initial Address message to the GMSC of the called party indicating that Multimedia CAT is supported. + +The GMSC server determines that the called party has a multimedia CAT subscription (bullet 6) e.g. based on OSS code retrieved from the HLR. + +Upon receiving the indication that the called party is being alerted, the GMSC sets up a UDI call towards the CAT Server. Upon reception of an Address Complete message from the CAT server, it returns to the originating MSC an Address Complete or Call Progress message indicating that multimedia CAT is available (bullet 13). This leads the originating MSC to request the calling UE (supporting multimedia CAT) to attach to the user connection and to set up a H.324 call to the CAT server (bullet 14). + +When the called party accepts the call, the GMSC releases the call towards the CAT server (bullet 18), waits for the Release Complete message from the CAT Server, and then through-connects the calling and called legs and returns an answer indication to the originating MSC. + +Upon reception of the CONNECT message, the calling UE releases any on-going H.324 call and establishes a new H.324 call towards the called party. + +![A diagram showing a message sequence chart (MSC) for a multimedia CAT during a multimedia mobile originated call. The diagram is mostly obscured by a large black rectangle, with only the bottom portion visible, showing lifelines and a single message arrow.](5e9af8986a5845504f251d3079da8078_img.jpg) + +The diagram is a message sequence chart (MSC) that has been partially redacted. A large black rectangle covers the top and middle portions of the chart. Only the bottom section is visible, showing five vertical lifelines. A single message arrow is depicted at the top of this visible section, pointing from the first lifeline to the second. Below the arrow, there are three horizontal rectangular boxes, each spanning across the first four lifelines. These boxes likely represent activation bars or message frames that have been partially obscured. The fifth lifeline on the far right is not covered by these boxes. + +A diagram showing a message sequence chart (MSC) for a multimedia CAT during a multimedia mobile originated call. The diagram is mostly obscured by a large black rectangle, with only the bottom portion visible, showing lifelines and a single message arrow. + +Figure 14.10.3.3.3.1: Multimedia CAT during a multimedia mobile originated call (message sequence chart) + +# 15 Tunnelling + +NOTE: All message sequence charts in this clause are examples. All valid call establishment message sequences can be derived from the example message sequences and associated message pre-conditions. + +## 15.1 Forward Bearer Establishment + +The following clauses describe the requirements for tunnelling transport mechanism within the bearer independent CS core network. These requirements are supplementary to those already stated in the Call Establishment clause. If out-of-band transcoder control is applied for a speech call, it shall be performed in accordance with 3GPP TS 23.153 [3]. + +### 15.1.1 Outgoing Side + +#### 15.1.1.1 Tunnel Selection + +If the MGW selection occurs before the IAM is sent, the (G)MSC server uses the Prepare Bearer procedure to indicate a tunnel support to the MGW. Depending upon the received value, the MGW shall determine whether tunnelling shall actually be used and when to send the tunnel data (bullet 1 in figure 15.2). + +If the (G)MSC server indicated that tunnelling is not supported, the bearer will be established as described in clause Call Establishment. + +If the (G)MSC server indicated that fast tunnelling is supported, the MGW may select which tunnelling method to use. In this case the MGW shall select either fast tunnelling or the non-tunnelling method. + +If the (G)MSC server indicated that delayed tunnelling is supported, the MGW may select which tunnelling method to use. In this case the MGW shall select either delayed tunnelling or the non-tunnelling method. + +If the MGW is allowed to choose whether tunnelling is to be used, it shall select either fast, delayed, or the non-tunnelling method. + +The MGW shall respond to the Prepare Bearer procedure with the used tunnel indication, when the type of tunnelling mechanism has been decided. + +NOTE: For a given bearer type, other specifications may describe the mechanism to be used to transport bearer control information. An MGW is only required to comply with that specification. + +#### 15.1.1.2 Initial addressing + +If the MGW selection has occurred, the MGW shall respond to the Prepare Bearer procedure indicating whether tunnelling is allowed and what type of tunnelling is used – fast or delayed forward. The (G)MSC server provides a tunnel indicator to the succeeding node in the IAM to indicate that tunnelling is to be used. For fast tunnelling, the (G)MSC server waits for the MGW to use the Tunnel Information Up procedure to provide the tunnel data before the IAM is sent. + +If the MGW indicates that tunnelling is not to be used, then tunnel indicator is not included in the Initial Address message and the bearer will be established as described in clause Call Establishment. + +If the MGW has not been selected yet, then the (G)MSC server decides whether delayed tunnelling is supported or not. If the delayed tunnelling is supported the tunnel indicator is included to the Initial Address message to indicate that. Otherwise the tunnel indicator is not included to the Initial Address message and the bearer will be established as described in clause Call Establishment. + +#### 15.1.1.3 Fast forward tunnelling + +The tunnel data is transferred in the IAM and the subsequent Tunnel Information message(s). + +Before the IAM is sent, the (G)MSC server waits for the MGW to use the Tunnel Information Up procedure to supply the tunnel data. The (G)MSC server sends the received tunnel data to the succeeding node in the IAM (bullet 2 in example, clause 15.2). + +When the (G)MSC server receives a Tunnel Information message from the succeeding node the (G)MSC server uses the Tunnel Information Down procedure to supply the MGW with the received tunnel data (bullet 5 in example sequence 15.2). + +#### 15.1.1.4 Delayed forward tunnelling + +The tunnel data is transferred in the Tunnel Information messages following the Bearer Information message. + +If tunnel indicator was included in the IAM indicating that delayed tunnelling is supported, the succeeding node may include the tunnel indicator to the Bearer Information message. If the tunnel indicator is received the (G)MSC server indicates the delayed tunnel support in the Establish Bearer procedure. + +When the MGW sends the Tunnel Information Up procedure, the (G)MSC server sends the received tunnel data in the Tunnel Information message to the succeeding node. + +When the (G)MSC server receives a Tunnel Information message from the succeeding node, the (G)MSC server uses the Tunnel Information Down procedure to send the received tunnel data to the MGW. + +#### 15.1.1.5 Bearer control signalling transfer + +The tunnelling of the bearer control signalling is transported transparently through the (G)MSC server during the call establishment and at any other time until Release is sent or received. + +### 15.1.2 Incoming Side + +#### 15.1.2.1 Initial addressing + +The (G)MSC server receives the possible tunnel indicator and the tunnel data in IAM. Based on received information it provides the tunnel support indication and the tunnel data to the MGW. + +#### 15.1.2.2 Tunnel Selection + +If the tunnel indicator was received in the IAM, the (G)MSC server uses the received tunnel indicator to indicate the support of tunnel to the MGW. If the tunnel indicator is received in the IAM without tunnel data, the (G)MSC server checks the value of the tunnel indicator. If the tunnel indicator indicates that tunnel mechanism is to be used then delayed tunnelling is indicated to the MGW. If the tunnel indicator indicates that tunnel mechanism is supported the (G)MSC server decides whether the delayed tunnel is supported or non tunnelling mechanism is used. If both tunnel indicator and tunnel data are received in the IAM, fast tunnelling is indicated to the MGW. + +If no tunnel indicator was received in the IAM, then the preceding node has indicated that non-tunnelling mechanism is to be used. + +The (G)MSC server uses the Prepare Bearer procedure to supply the tunnel support indication to the MGW. + +The MGW decides based on the received tunnel support indication from the (G)MSC server whether to use delayed tunnelling or not. In the response the MGW provides the used tunnel indication to the (G)MSC server. + +#### 15.1.2.3 Fast forward tunnelling + +The tunnel data is transferred in the IAM and the subsequent Tunnel Information message(s). + +The (G)MSC server sends the tunnel data received in the IAM to the MGW using the Tunnel Information Down procedure (bullet 3 in example, clause 15.2). + +When the MGW sends the Tunnel Information Up procedure, the (G)MSC server sends the received tunnel data in the Tunnel Information message to the preceding node (bullet 4 in example, clause 15.2). + +#### 15.1.2.4 Delayed forward tunnelling + +The tunnel data is transferred in the Tunnel Information messages following the Bearer Information message. + +If tunnel indicator was received in the IAM indicating that delayed tunnel is supported and delayed tunnelling was indicated by the MGW, the (G)MSC server shall include the tunnel indicator to the Bearer Information message which is sent to the preceding node. + +When the (G)MSC server receives a Tunnel Information message from the preceding node, the (G)MSC server uses the Tunnel Information Down procedure to send the received tunnel data to the MGW. + +When the MGW sends the Tunnel Information Up procedure, the (G)MSC server sends the received tunnel data in the Tunnel Information message to the preceding node. + +#### 15.1.2.5 Bearer control signalling transfer + +The tunnelling of bearer control signalling is transported transparently during the call establishment and at any other time until Release is sent or received. + +#### 15.1.2.6 Example + +Figure 15.1 shows the network model for the forward tunnelling transport mechanism. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling. The (G)MSCa seizes one context with two bearer terminations in MGWa. The bearer termination T1 is used for the bearer towards the incoming side of (G)MSCa and the bearer termination T2 is used for the tunnelling towards the succeeding MGW. The (G)MSCb seizes one context with two bearer terminations in MGWb. The bearer termination T3 is used for the bearer towards the outgoing side of (G)MSCb and the bearer termination T4 is used for the tunnelling towards the preceding MGW. + +![Figure 15.1: Forward Tunnelling Transport Mechanism (network model). The diagram shows two (G)MSC-S nodes, labeled 'a' and 'b', connected by a horizontal line. Below each (G)MSC-S node is an MGW node, labeled 'MGWa' and 'MGWb' respectively. The (G)MSC-S nodes are connected to their respective MGW nodes by vertical lines. The MGW nodes are connected to each other by a horizontal line. The (G)MSC-S nodes are represented by rounded rectangles with two internal arrows pointing outwards. The MGW nodes are represented by rounded rectangles containing an 'X' symbol and two internal arrows pointing outwards. The horizontal line between the (G)MSC-S nodes is a dashed green line. The horizontal line between the MGW nodes is a dotted red line. The vertical lines between the (G)MSC-S nodes and the MGW nodes are solid blue lines. The MGW nodes are labeled with 'CTX1' and 'CTX2' respectively. The (G)MSC-S nodes are labeled with 'a' and 'b' respectively. The MGW nodes are labeled with 'MGWa' and 'MGWb' respectively. The internal arrows in the MGW nodes are labeled with 'T1', 'T2', 'T3', and 'T4' respectively.](ddcdc1712375261ba1d89165fdf12aa6_img.jpg) + +Figure 15.1: Forward Tunnelling Transport Mechanism (network model). The diagram shows two (G)MSC-S nodes, labeled 'a' and 'b', connected by a horizontal line. Below each (G)MSC-S node is an MGW node, labeled 'MGWa' and 'MGWb' respectively. The (G)MSC-S nodes are connected to their respective MGW nodes by vertical lines. The MGW nodes are connected to each other by a horizontal line. The (G)MSC-S nodes are represented by rounded rectangles with two internal arrows pointing outwards. The MGW nodes are represented by rounded rectangles containing an 'X' symbol and two internal arrows pointing outwards. The horizontal line between the (G)MSC-S nodes is a dashed green line. The horizontal line between the MGW nodes is a dotted red line. The vertical lines between the (G)MSC-S nodes and the MGW nodes are solid blue lines. The MGW nodes are labeled with 'CTX1' and 'CTX2' respectively. The (G)MSC-S nodes are labeled with 'a' and 'b' respectively. The MGW nodes are labeled with 'MGWa' and 'MGWb' respectively. The internal arrows in the MGW nodes are labeled with 'T1', 'T2', 'T3', and 'T4' respectively. + +**Figure 15.1: Forward Tunnelling Transport Mechanism (network model)** + +Figure 15.2 shows the message sequence example for fast forward tunnelling transport mechanism. In the example (G)MSCa indicates to MGWa that fast tunnelling is requested. After MGWa has notified the (G)MSCa of the tunnel data, the IAM is sent to the (G)MSCb. The (G)MSCb indicates to MGWb that fast tunnelling is supported and sends the received tunnel data to MGWb. Once MGWb has sent the tunnel data to the (G)MSCb, the (G)MSCb sends a Tunnel Information message with the tunnel data to the (G)MSCa. The (G)MSCa sends the received tunnel data to MGWa. The handling of Continuity message, through-connection and answer is as normal for non-tunnelled forward bearer establishment. + +![Figure 15.2: Fast Forward Tunnelling Transport Mechanism (message sequence chart). The diagram shows a sequence of messages between four entities: (G)MSC-S a, MGWa, (G)MSC-S b, and MGWb. The sequence is numbered 1 to 5. Step 1: (G)MSC-S a sends an ADD.request ($) to MGWa. MGWa responds with a Prepare Bearer. Step 2: (G)MSC-S a sends a NOTIFY.request (T2) to MGWa. MGWa responds with Tunnel Information Up. Step 3: (G)MSC-S a sends an Initial Address to (G)MSC-S b. (G)MSC-S b sends an ADD.request ($) to MGWb. MGWb responds with Prepare Bearer and Tunnel Information Down. Step 4: (G)MSC-S b sends an ADD.reply (T4) to MGWb. MGWb responds with Tunnel Information Up. Step 5: (G)MSC-S b sends a NOTIFY.request (T4) to MGWb. MGWb responds with NOTIFY.reply (T4). Finally, (G)MSC-S b sends Tunnel Information to (G)MSC-S a. (G)MSC-S a sends a MOD.request (T2) to MGWa. MGWa responds with Tunnel Information Down. (G)MSC-S a sends a MOD.reply (T2) to MGWa.](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +``` + +sequenceDiagram + participant (G)MSC-S a + participant MGWa + participant (G)MSC-S b + participant MGWb + + Note left of (G)MSC-S a: Context ($) +1) (G)MSC-S a->>MGWa: ADD.request ($) +Note right of MGWa: Prepare Bearer +MGWa-->>(G)MSC-S a: ADD.reply (T2) +Note left of (G)MSC-S a: Context (C1) +2) (G)MSC-S a->>MGWa: NOTIFY.request (T2) +Note right of MGWa: Tunnel Information Up +MGWa-->>(G)MSC-S a: NOTIFY.reply (T2) +Note left of (G)MSC-S a: Context (C1) +(G)MSC-S a->>(G)MSC-S b: Initial Address +Note right of (G)MSC-S b: Context ($) +3) (G)MSC-S b->>MGWb: ADD.request ($) +Note right of MGWb: Prepare Bearer + Tunnel Information Down +MGWb-->>(G)MSC-S b: ADD.reply (T4) +Note right of (G)MSC-S b: Context (C2) +4) (G)MSC-S b->>MGWb: NOTIFY.request (T4) +Note right of MGWb: Tunnel Information Up +MGWb-->>(G)MSC-S b: NOTIFY.reply (T4) +Note right of (G)MSC-S b: Context (C2) +(G)MSC-S b->>(G)MSC-S a: Tunnel Information +Note left of (G)MSC-S a: Context (C1) +5) (G)MSC-S a->>MGWa: MOD.request (T2) +Note right of MGWa: Tunnel Information Down +MGWa-->>(G)MSC-S a: MOD.reply (T2) +Note left of (G)MSC-S a: Context (C1) + +``` + +Figure 15.2: Fast Forward Tunnelling Transport Mechanism (message sequence chart). The diagram shows a sequence of messages between four entities: (G)MSC-S a, MGWa, (G)MSC-S b, and MGWb. The sequence is numbered 1 to 5. Step 1: (G)MSC-S a sends an ADD.request (\$) to MGWa. MGWa responds with a Prepare Bearer. Step 2: (G)MSC-S a sends a NOTIFY.request (T2) to MGWa. MGWa responds with Tunnel Information Up. Step 3: (G)MSC-S a sends an Initial Address to (G)MSC-S b. (G)MSC-S b sends an ADD.request (\$) to MGWb. MGWb responds with Prepare Bearer and Tunnel Information Down. Step 4: (G)MSC-S b sends an ADD.reply (T4) to MGWb. MGWb responds with Tunnel Information Up. Step 5: (G)MSC-S b sends a NOTIFY.request (T4) to MGWb. MGWb responds with NOTIFY.reply (T4). Finally, (G)MSC-S b sends Tunnel Information to (G)MSC-S a. (G)MSC-S a sends a MOD.request (T2) to MGWa. MGWa responds with Tunnel Information Down. (G)MSC-S a sends a MOD.reply (T2) to MGWa. + +Figure 15.2: Fast Forward Tunnelling Transport Mechanism (message sequence chart) + +## 15.2 Backward Bearer Establishment + +The following clauses describe the additional requirements for tunnelling transport mechanism within the bearer independent CS core network. If out-of-band transcoder control is applied for a speech call, it shall be performed in accordance with 3GPP TS 23.153[3]. + +### 15.2.1 Outgoing Side + +#### 15.2.1.1 Tunnel Selection + +The (G)MSC server uses the Prepare Bearer procedure to indicate a tunnel support to the MGW. Depending upon the received value, the MGW shall determine whether tunnelling shall actually be used and when to send the tunnel data (bullet 1 in example, clause 15.4). + +If the (G)MSC server indicated that tunnelling will be not supported, the bearer is established as described in clause Call Establishment. + +If the (G)MSC server indicated that fast tunnelling is supported, the MGW may select which tunnelling method it can use. In this case the (G)MSC may select either fast tunnelling or the non-tunnelling method. + +If the (G)MSC server indicated that delayed tunnelling is supported, the MGW may select which tunnelling method it can use. In this case the (G)MSC server may select either delayed tunnelling or the non-tunnelling method. + +If the MGW is allowed to choose whether tunnelling is to be used, it shall select either fast, delayed or the non-tunnelling method. + +After MGW has decided which tunnelling mechanism to use, it responds to the Prepare Bearer procedure with the used tunnel indication. + +#### 15.2.1.2 Initial addressing + +The MGW shall respond to the Prepare Bearer procedure to indicate whether tunnelling is allowed and what type of tunnelling is used – fast or delayed forward. The (G)MSC server provides a tunnel indicator to the succeeding node in the IAM. For fast tunnelling, the (G)MSC server waits for the MGW to use the Tunnel Information Up procedure to provide the tunnel data before the IAM is sent. + +If the MGW indicates that tunnelling is not to be used, the bearer will be established as described in clause Call Establishment. + +#### 15.2.1.3 Fast forward tunnelling + +The tunnel data is transferred in the IAM and the subsequent Tunnel Information message(s). + +Before the IAM is sent, the (G)MSC server waits for the MGW to use the Tunnel Information Up procedure to supply the tunnel data. The (G)MSC server sends the received tunnel data to the succeeding node in the IAM. + +When the (G)MSC server receives a Tunnel Information message from the succeeding node the (G)MSC server uses the Tunnel Information Down procedure to supply the MGW with the received tunnel data. + +#### 15.2.1.4 Delayed backward tunnelling + +The tunnel data is transferred in the Tunnel Information messages following the IAM. + +When the (G)MSC server receives a Tunnel Information message from the succeeding node the (G)MSC server uses the Tunnel Information Down procedure to supply the MGW with the received tunnel data (bullet 4 in example, clause 15.4). + +When the MGW sends the Tunnel Information Up procedure, the (G)MSC server sends the received tunnel data in the Tunnel Information message to the succeeding node (bullet 5 in example, clause 15.4). + +#### 15.2.1.5 Bearer control signalling transfer + +The tunnelling of bearer control signalling is transported transparently through the (G)MSC server during the call establishment and at any other time until Release is sent or received. + +### 15.2.2 Incoming Side + +#### 15.2.2.1 Initial addressing + +The (G)MSC server receives the possible tunnel indicator and the tunnel data in the IAM. Based on received information it provides the tunnel support indication and the tunnel data to the MGW. + +#### 15.2.2.2 Tunnel Selection + +If the tunnel indicator was received in the IAM, the (G)MSC server uses the received tunnel indicator to indicate the support of tunnel to the MGW. If the tunnel indicator is received in the IAM without tunnel data, delayed tunnelling is indicated to the MGW. If tunnel indicator and tunnel data are received in the IAM, fast tunnelling is indicated to the MGW. + +The (G)MSC server uses the Establish Bearer procedure to supply the tunnel support indication to the MGW (bullet 2 in example, clause 15.4). + +#### 15.2.2.3 Fast forward tunnelling + +The tunnel data is transferred in the IAM and the subsequent Tunnel Information message(s). + +The (G)MSC server sends the tunnel data received in the IAM to the MGW using the Tunnel Information Down procedure. + +When the MGW sends the Tunnel Information Up procedure, the (G)MSC server sends the received tunnel data in the Tunnel Information message to the preceding node. + +#### 15.2.2.4 Delayed backward tunnelling + +When the MGW sends the Tunnel Information Up procedure, the (G)MSC server sends the received tunnel data in the Tunnel Information message to the preceding node (bullet 3 in example, clause 15.4). + +When the MGW receives an Nb User Plane Initialisation message (bullet 5a in example sequence 15.4), before the subsequent Tunnel Information Down procedure (bullet 6 in example sequence 15.4), the MGW may acknowledge this Nb User Plane Initialisation message without waiting for the Tunnel Information Down procedure, and send the acknowledge message towards the IP address and port that were supplied as source within the IP packet transporting the Nb User Plane Initialisation message (bullet 5b in example sequence 15.4). The MGW shall use the same RTP Payload-Type number for the acknowledge message, which was used in the RTP header of the packet transporting the Nb User Plane Initialisation message. + +Alternatively, when the MGW receives an Nb User Plane Initialisation message (bullet 5a in example sequence 15.4), before the subsequent Tunnel Information Down procedure (bullet 6 in example sequence 15.4), the MGW may wait for the Tunnel Information Down procedure, before sending the Nb User Plane Initialisation acknowledge message (bullet 6a in example sequence 15.4). While waiting for the Tunnel Information Down procedure, the MGW may receive repetition(s) of the Nb User Plane Initialisation message and shall not treat this as error case. + +When the (G)MSC server receives a Tunnel Information message from the preceding node, the (G)MSC server uses the Tunnel Information Down procedure to send the received tunnel data to the MGW (bullet 6 in example, clause 15.4). + +After receiving the Tunnel Information Down procedure (bullet 6 in example sequence 15.4) and acknowledging the NbFP Init message (bullet 5b or 6a in example sequence 15.4), the MGW shall notify the MSC server about the bearer establishment (bullet 7 in example sequence 15.4). + +#### 15.2.2.5 Bearer control signalling transfer + +The tunnelling of bearer control signalling is transported transparently through the (G)MSC server during the call establishment and at any other time until Release is sent or received. + +#### 15.2.2.6 Example + +Figure 15.3 shows the network model for the backward delayed tunnelling transport mechanism. The "squared" line represents the call control signalling. The "dotted" line represents the bearer control signalling. The (G)MSCa seizes one context with two bearer terminations in MGWa. The bearer termination T1 is used for the bearer towards the incoming side of (G)MSCa and the bearer termination T2 is used for the tunnelling towards the succeeding MGW. The (G)MSCb seizes one context with two bearer terminations in MGWb. The bearer termination T3 is used for the bearer towards the outgoing side of (G)MSCb and the bearer termination T4 is used for the tunnelling towards the preceding MGW. + +![Figure 15.3: Delayed Backward Tunnelling Transport Mechanism (network model). The diagram shows two (G)MSC servers, (G)MSC-S a and (G)MSC-S b, connected by a horizontal line. (G)MSC-S a is connected to MGWa via a vertical line. (G)MSC-S b is connected to MGWb via a vertical line. MGWa and MGWb are connected to each other by a horizontal line. The horizontal lines are composed of green squares and red dots. The vertical lines are solid blue. The MGWs are represented by boxes containing an 'X' and labels T1, T2, CTX1, MGWa for MGWa and T3, T4, CTX2, MGWb for MGWb. The (G)MSC-S boxes are labeled 'a' and 'b'.](a2586540d49d5665489c8b5a273f86d3_img.jpg) + +Figure 15.3: Delayed Backward Tunnelling Transport Mechanism (network model). The diagram shows two (G)MSC servers, (G)MSC-S a and (G)MSC-S b, connected by a horizontal line. (G)MSC-S a is connected to MGWa via a vertical line. (G)MSC-S b is connected to MGWb via a vertical line. MGWa and MGWb are connected to each other by a horizontal line. The horizontal lines are composed of green squares and red dots. The vertical lines are solid blue. The MGWs are represented by boxes containing an 'X' and labels T1, T2, CTX1, MGWa for MGWa and T3, T4, CTX2, MGWb for MGWb. The (G)MSC-S boxes are labeled 'a' and 'b'. + +**Figure 15.3: Delayed Backward Tunnelling Transport Mechanism (network model)** + +Figure 15.4 shows the message sequence example for backward tunnelling transport mechanism. In the example the (G)MSCa indicates to MGWa that delayed tunnelling is requested. After MGWa has responded the (G)MSCa of tunnelling, the IAM is sent to (G)MSCb. The (G)MSCb indicates to MGWb that delayed tunnelling is supported. Once MGWb has sent the tunnel data to the (G)MSCb, the (G)MSCb sends the received tunnel data in the Tunnel Information message to the (G)MSCa. The (G)MSCa sends the received tunnel data to MGWa. Once MGWa has sent the tunnel data to the (G)MSCa, the (G)MSCa sends the received tunnel data in the Tunnel Information message to the + +(G)MSCb. The (G)MSCb sends the received tunnel data to MGWb. The handling of Continuity message, through-connection and answer is as normal for non-tunnelled backward bearer establishment. + +![Sequence diagram for Delayed Backward Tunneling Transport Mechanism. Lifelines: (G)MSC-S a, MGWa, (G)MSC-S b, MGWb. The diagram shows a series of messages (ADD.request, ADD.reply, Initial Address, MOD.request, MOD.reply, NOTIFY.request, NOTIFY.reply, Tunnel Information, UP Init, UP Init Ack) exchanged between the lifelines, with numbered steps 1 through 7 indicating the sequence of events.](1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg) + +``` + +sequenceDiagram + participant (G)MSC-S a + participant MGWa + participant (G)MSC-S b + participant MGWb + + Note left of (G)MSC-S a: Context ($) + + (G)MSC-S a->>MGWa: 1 ADD.request ($) + + Note right of MGWa: Prepare Bearer + + MGWa-->>(G)MSC-S a: Context (C1) ADD.reply (T2) + + (G)MSC-S a->>(G)MSC-S b: Initial Address + + Note right of (G)MSC-S b: Context ($) + + (G)MSC-S b->>MGWb: 2 ADD.request ($) + + Note right of MGWb: Establish Bearer + + MGWb-->>(G)MSC-S b: Context (C2) ADD.reply (T4) + + (G)MSC-S b->>MGWb: Context (C2) NOTIFY.request (T4) + + Note right of (G)MSC-S b: 3 + + MGWb-->>(G)MSC-S b: Context (C2) NOTIFY.reply (T4) + + (G)MSC-S b->>(G)MSC-S a: Tunnel Information + + Note left of (G)MSC-S a: 4 + + (G)MSC-S a->>MGWa: Context (C1) MOD.request (T2) + + Note right of MGWa: Tunnel Information Down + + MGWa-->>(G)MSC-S a: Context (C1) MOD.reply(T2) + + (G)MSC-S a->>MGWa: Context (C1) NOTIFY.request (T2) + + Note right of MGWa: 5 UP Init + + MGWa->>MGWb: Tunnel Information Up + + Note left of (G)MSC-S a: Context (C1) + + (G)MSC-S a->>MGWa: NOTIFY.reply(T2) + + Note right of MGWa: UP Init Ack + + MGWa-->>MGWb: 5b + + (G)MSC-S b->>(G)MSC-S a: Tunnel Information + + Note right of (G)MSC-S b: 6 + + (G)MSC-S b->>MGWb: Context (C2) MOD.request (T4) + + MGWb-->>(G)MSC-S b: Context (C2) MOD.reply (T4) + + Note right of MGWb: UP Init Ack + + MGWb-->>MGWa: 6a + + (G)MSC-S b->>MGWb: Context (C2) NOTIFY.request (T4) + + Note right of (G)MSC-S b: 7 + + MGWb-->>(G)MSC-S b: Context (C2) NOTIFY.reply (T4) + + Note right of MGWb: Bearer Establishment + +``` + +Sequence diagram for Delayed Backward Tunneling Transport Mechanism. Lifelines: (G)MSC-S a, MGWa, (G)MSC-S b, MGWb. The diagram shows a series of messages (ADD.request, ADD.reply, Initial Address, MOD.request, MOD.reply, NOTIFY.request, NOTIFY.reply, Tunnel Information, UP Init, UP Init Ack) exchanged between the lifelines, with numbered steps 1 through 7 indicating the sequence of events. + +Figure 15.4: Delayed Backward Tunneling Transport Mechanism (message sequence chart) + +# 16 Messages/Procedures and their contents + +This clause contains the detailed description of the information flows used in bearer independent CS core network. + +Each Information Element, IE, is marked as (M) Mandatory, (C) Conditional or (O) Optional. A mandatory information element shall always be present. A conditional information shall be present if certain conditions are fulfilled; if those conditions are not fulfilled it shall be absent. An optional information element may be present or absent, at the discretion of the application at the sending entity. This categorisation is a functional classification, i.e., stage 2 information and not a stage 3 classification to be used for the protocol. + +The stage 2 and stage 3 message and information element names are not necessarily identical. + +## 16.1 Messages between (G)MSC servers + +Table 16.1 indicates messages between (G)MSC servers in Nc interface. Only the new messages and information elements required by the bearer independent CS core network are shown. + +Table 16.1: Messages between (G)MSC servers + +| Message | Message direction | Information element name | Information element required | Information element description | +|--------------------|-------------------|--------------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial Address | Forward | Bearer Establishment Direction | M | This information element indicates that the direction of bearer establishment. | +| | | Bearer Address | C | This information element indicates the bearer address of the MGW used by the preceding node. This information element is included when an AAL2 bearer is established using backward bearer establishment control protocol. Otherwise the information element is optional. | +| | | Binding Reference | C | This information element indicates the bearer identifier in the MGW used by the preceding node. This information element is included when an AAL2 bearer is established using backward bearer establishment control protocol. Otherwise the information element is optional. | +| | | MGW-id | O | This information element indicates the MGW selected by the preceding node. | +| | | Bearer Characteristics | M | This information element indicates the characteristics of the bearer. | +| | | Tunnel Indicator | O | This information element indicates either that tunnelling is to be used or tunnelling is supported. | +| | | Tunnel data | O | This information element contains the tunnel data that is provided between MGWs. | +| Bearer Information | Backward | Bearer Address | C | This information element indicates the bearer address of the MGW used by the succeeding node. This information element is included when an AAL2 bearer is established using forward bearer establishment control protocol. Otherwise the information element is optional. | +| | | Binding Reference | C | This information element indicates the bearer identifier in the MGW used by the succeeding node. This information element is included when an AAL2 bearer is established using forward bearer establishment control protocol. Otherwise the information element is optional. | +| | | MGW-id | O | This information element indicates the MGW selected by the succeeding node. | +| | | Tunnel Indicator | O | This information element indicates that tunnelling is used. | +| | | | | | +| Tunnel Information | Both | Tunnel Indicator | M | This information element indicates that the message contains tunnelling information. | +| | | Tunnel data | M | This information element contains the tunnel data that is provided between MGWs. | +| Start DTMF | Both | Start DTMF indicator | M | This information element indicates that the message is used for Start DTMF. | +| | | Digit | M | This information element indicates the digit for DTMF tone generation. | +| Start DTMF Ack | Both | Start DTMF Ack indicator | M | This information element indicates that the message is used for Start DTMF Ack. | +| Stop DTMF | Both | Stop DTMF indicator | M | This information element indicates that the message is used for Stop DTMF. | +| Stop DTMF Ack | Both | Stop DTMF Ack indicator | M | This information element indicates that the message is used for Stop DTMF Ack. | + +## 16.2 Procedures between (G)MSC server and MGW + +The clauses below indicate the procedures used between (G)MSC server and MGW in Mc interface. The procedures are logical, i.e. message identifiers are not part of the protocol. Several logical procedures can be combined into one H.248 command in order to perform required transactions. If several logical procedures are combined, only one context/context request and only one bearer termination/bearer termination request is sent in the H.248 command. Exemption is the Change Flow Direction procedure, where the two bearer terminations are related to a change of the context and not to a command of the bearer termination. All the procedures below describe a successful operation. If the procedure is rejected, a Command Reject is sent back to the entity that sent the command request. + +### 16.2.1 Change Flow Direction + +This procedure is used to change the flow direction between bearer terminations within the context. + +**Table 16.2: Procedures between (G)MSC server and MGW: Change Flow Direction** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------|-----------|----------------------------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Change Flow Direction | (G)MSC-S | Context/Context Request | M | This information element indicates the existing context or a new context where the flow direction is changed. | +| | | Bearer Termination 1/ Bearer Termination 1 Request | M | This information element indicates the existing bearer termination or a new bearer termination from where the new flow direction is applied. | +| | | Bearer Termination 2/ Bearer Termination 2 Request | M | This information element indicates the existing bearer termination or a new bearer termination where to the new flow direction is applied. | +| | | Flow Direction | M | This information element indicates the flow direction from the bearer termination 1 to bearer termination 2 within the context. | +| Change Flow Direction Ack | MGW | Context | M | This information element indicates the context where the command was executed. | + +NOTE 1: This procedure may be combined with Prepare Bearer, Prepare\_IP\_Transport, Establish Bearer, Reserve Circuit, Reserve RTP Connection Point, Configure RTP Connection Point or Reserve and Configure RTP Connection Point, Join Bearer Termination or Isolate Bearer Termination procedure. This list of procedures is not exhaustive. + +NOTE 2: Only one of the bearer terminations can be a new bearer termination within this procedure. + +### 16.2.2 Join Bearer Termination + +This procedure is used to join a bearer termination with other bearer terminations within the context. + +**Table 16.3: Procedures between (G)MSC server and MGW: Join Bearer Termination** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------|-----------|-----------------------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Join Bearer Termination | (G)MSC-S | Context | M | This information element indicates the context where the bearer termination is joined. | +| | | Bearer Termination/Bearer Termination Request | M | This information element indicates the existing bearer termination or requests a new bearer termination to be joined with the other bearer terminations within the context. | +| Join Bearer Termination Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.3 Isolate Bearer Termination + +This procedure is used to isolate one bearer termination from the other bearer terminations within the context. + +**Table 16.4: Procedures between (G)MSC server and MGW: Isolate Bearer Termination** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------|-----------|-----------------------------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Isolate Bearer Termination | (G)MSC-S | Context/Context Request | M | This information element indicates the existing context or a new context where to the bearer termination is isolated. | +| | | Bearer Termination/Bearer Termination Request | M | This information element indicates the existing bearer termination or requests a new bearer termination to be isolated from the other bearer terminations within the context. | +| Isolate Bearer Termination Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.4 Establish Bearer + +This procedure is used to request a bearer establishment. + +**Table 16.5: Procedures between (G)MSC server and MGW: Establish Bearer** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------|-----------|-----------------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Establish Bearer (G)MSC-S | | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Bearer Termination/Bearer Termination Request | M | This information element indicates the existing bearer termination or requests a new bearer termination for the bearer to be established. | +| | | Bearer Establishment Request | M | This information element requests establishment of a bearer. | +| | | Destination Binding Reference | C | This information element indicates the bearer identifier in the destination MGW. This information element shall be included when requesting the establishment of an AAL2 bearer. Otherwise the information element is optional. | +| | | Destination Bearer Address | C | This information element indicates the bearer address of the destination MGW. This information element shall be included when requesting the establishment of an AAL2 bearer. Otherwise the information element is optional. | +| | | Bearer Characteristics | M | This information element indicates the characteristics of the bearer connection. | +| | | Bearer Service Characteristics | C | This information element indicates the bearer service requested by the user. This information element is not included if the Codec information element is provided. It may be included for a non-speech / non SCUDIF multimedia call (see 3GPP TS 23.172 [38], 3GPP TS 29.007 [37] and 3GPP TS 29.232 [6]). | +| | | Notify Bearer Event | O | This information element requests a notification of an established bearer, a released bearer, a modified bearer or a bearer modification failure. | +| | | Tunnel Support | O | This information element indicates the support of tunnel data transfer and when to send tunnel data. In 29.232 this information element is defined in the Tunnel Information down procedure. | +| | | Circuit Switched Data | C | This information element indicates the PLMN bearer capabilities and when applicable GSM channel coding. This information element shall be included according to 3GPP TS 29.007 [37] and 3GPP TS 29.232 [6] for a non-speech / non SCUDIF multimedia call (see 3GPP TS 23.172 [38]) by the MSC server, or by the anchor-MSC in case of inter-MSC handover, for an anchor MGW network termination. | +| | | Codec | C | This information element indicates the speech coding format to be used for the bearer. This information element is included for a speech call for a network side bearer termination. | + +| | | | | | +|-----------------------------------------------------------------------------------------------------|-------------------------------------------------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| +| | Framing Protocol | O | This information element indicates the framing protocol to be used for the bearer. | | +| | Call Type Discrimination | O | This information element supports modem signalling for GTT feature.
NOTE | | +| | Text Telephone | O | This information element supports interworking with PSTN text telephone.
NOTE | | +| | Notify termination heartbeat | C | This information element requests termination heartbeat indications. This information element shall be included when requesting a new bearer termination. Otherwise the information element is optional. | | +| | IP Realm Identifier | O | This information element indicates the IP realm of the IP termination. | | +| | Number of desired listener context terminations | O | This information element indicates the number of desired terminations for a listener context in a VGCS or VBS call. It should be included in the first ADD request which establishes a Listener context. | | +| Establish Bearer Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | +| NOTE: Procedures for use of Text Telephony indication and Call Type discrimination are not defined. | | | | | + +### 16.2.5 Prepare Bearer + +This procedure is used to prepare for a bearer establishment. + +**Table 16.6: Procedures between (G)MSC server and MGW: Prepare Bearer** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------|-----------|--------------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Prepare Bearer (G)MSC-S | | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Bearer Termination Request | M | This information element requests a new bearer termination for the bearer to be established. | +| | | Binding Reference Request | C | This information element requests the bearer identifier in the MGW. This information element shall be included when preparing the establishment of an AAL2 bearer. Otherwise the information element is optional. | +| | | Bearer Address Request | C | This information element requests the bearer address of the MGW. This information element shall be included when preparing the establishment of an AAL2 bearer. Otherwise the information element is optional. | +| | | Sender Binding Reference | O | This information element indicates the bearer identifier of the sending MGW. | +| | | Sender Bearer Address | O | This information element indicates the bearer address of the sending MGW. | +| | | Bearer Characteristics | M | This information element indicates the requested characteristics of the bearer connection. | +| | | Bearer Service Characteristics | C | This information element indicates the bearer service requested by the user. This information element is not included if the Codec information element is provided. It may be included for a data call (see 3GPP TS 29.007 [37] and 3GPP TS 29.232 [6]). | +| | | Notify Bearer Event | O | This information element requests a notification of an established bearer, a released bearer, a modified bearer or a bearer modification failure. | +| | | Notify Bearer Modification | O | This information element requests a notification that bearer modification of the established bearer is allowed. This information element may be included for access bearer assignment. | +| | | Tunnel Support | O | This information element indicates the support of tunnel data transfer and when to send tunnel data. In 3GPP TS 29.232 [6] this information element is defined in the Tunnel Information down procedure. | +| | | Circuit Switched Data | C | This information element indicates the PLMN bearer capabilities and when applicable GSM channel coding and user bit rate. This information element shall be included according to 3GPP TS 29.007 [37] and 3GPP TS 29.232 [6] for a non-speech call by the MSC server, or by the anchor-MSC in case of inter-MSC handover, for a radio access network termination and for an anchor MGW network termination. | +| | | Codec | C | This information element indicates the speech or multimedia coding format to be used for the bearer. This information element is included for a speech call and may be included for a SCUDIF multimedia call (see 3GPP TS 23.172 [38], 3GPP TS 29.007 [37] and 3GPP TS 29.232 [6]). | +| | | Framing Protocol | O | This information element indicates the framing protocol to be used for the bearer. | +| | | Cellular Text telephony modem | C | This information element indicates the need of CTM function. | + +| | | | | | +|--------------------|-----|------------------------------------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Notify termination heartbeat | M | This information element requests termination heartbeat indications. | +| | | Number of needed conference terminations | O | This information element indicates the number of conference ports needed for that VGCS or VBS call. It shall be included in the first ADD request which establishes the Multiparty context. | +| | | IP Realm Identifier | O | This information element indicates the IP realm of the IP termination. | +| Prepare Bearer Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | +| | | Binding Reference | C | This information element indicates the bearer identifier in the MGW. This information element is included if requested in the Prepare Bearer request. | +| | | Bearer Address | C | This information element indicates the bearer address of the MGW. This information element is included if requested in the Prepare Bearer request. | + +### 16.2.6 Reserve Circuit + +This procedure is used to select a TDM circuit in the MGW. + +**Table 16.7: Procedures between (G)MSC server and MGW: Reserve Circuit** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------|-----------|-------------------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserve Circuit
(G)MSC-S | | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the physical bearer termination for the TDM circuit. | +| | | Circuit Switched Data | C | This information element indicates the PLMN bearer capabilities and GSM channel coding. This information element shall be included according to 3GPP TS 29.007 [37] and 3GPP TS 29.232 [6] for a non-speech call by the MSC server, or by the anchor-MSC in case of inter-MSC handover, for a radio access network side bearer termination. | +| | | Bearer Service Characteristics | C | This information element indicates the bearer service requested by the user. This information element is included if no Circuit Switched Data information element is provided. | +| | | Cellular Text telephony modem | C | This information element indicates the need of CTM function. | +| | | Notify Released Bearer | O | This information element requests a notification of a released bearer | +| | | Notify termination heartbeat | O | This information element requests termination heartbeat indications. | +| | | Number of desired listener context terminations | O | This information element indicates the number of desired terminations for a listener context in a VGCS or VBS call. It should be included in the first ADD request which establishes a Listener context. | +| Reserve Circuit
Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed.. | + +### 16.2.7 Change Through-Connection + +This procedure is used to change the through-connection in the bearer termination. + +**Table 16.8: Procedures between (G)MSC server and MGW: Change Through-Connection** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|-----------------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| Change Through-Connection | (G)MSC-S | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Bearer Termination/Bearer Termination Request | M | This information element indicates the existing bearer termination or requests a new bearer termination where the through-connection is changed. | +| | | Through-Connection | M | This information element indicates the through-connection of the bearer termination. | +| Change Through-Connection Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +NOTE: This procedure may be combined with Prepare Bearer, Prepare\_IP\_Transport, Establish Bearer, Reserve Circuit, Reserve RTP Connection Point, Configure RTP Connection Point or Reserve and Configure RTP Connection Point, Join Bearer Termination, Isolate Bearer Termination or Release Bearer procedure. This list of procedures is not exhaustive. + +### 16.2.8 Activate Interworking Function + +This procedure is used to activate the interworking function. + +**Table 16.9: Procedures between (G)MSC server and MGW: Activate Interworking Function** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------------|-----------|--------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------| +| Activate Interworking Function | (G)MSC-S | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the interworking function is activated. | +| | | Circuit Switched Data Activate | M | This information element requests to activate the interworking function. | +| | | Circuit Switched Data | O | This information element indicates the request for IWF protocol negotiation result and rate change indication. | +| Activate Interworking Function Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.9 Release Bearer + +This procedure is used to release the bearer. + +**Table 16.10: Procedures between (G)MSC server and MGW: Release Bearer** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Release Bearer | (G)MSC-S | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for the bearer to be released. | +| | | Bearer Release Request | M | This information element requests release of a bearer. | +| | | Release Cause | O | This information element indicates the cause of a bearer release. | +| Release Bearer Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.10 Bearer Established + +This procedure is used to notify the established bearer. + +**Table 16.11: Procedures between (G)MSC server and MGW: Bearer Established** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------|-----------|--------------------------|------------------------------|---------------------------------------------------------------------------------------------| +| Bearer Established | MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the bearer was established. | +| | | Bearer Established | M | This information element notifies a bearer establishment. | +| Bearer Established Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the Bearer Termination where the command was executed. | + +### 16.2.11 Bearer Released + +This procedure is used to notify the released bearer or failed bearer establishment. + +**Table 16.12: Procedures between (G)MSC server and MGW: Bearer Released** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Bearer Released | MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the bearer was released. | +| | | Bearer Released | M | This information element notifies a bearer release. | +| | | Release Cause | M | This information element indicates the cause of a bearer release. | +| Bearer Released Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the Bearer Termination where the command was executed. | + +### 16.2.12 Release Termination + +This procedure is used to release the bearer termination. + +**Table 16.13: Procedures between (G)MSC server and MGW: Release Termination** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Release Termination | (G)MSC-S | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination to be released. | +| Release Termination Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | +| | | T.140 data statistics | C | Number of t.140 data bits transmitted over the termination | + +### 16.2.13 Tunnel Information Up + +This procedure is used to transfer tunnel data from the MGW to the (G)MSC server. + +**Table 16.14: Procedures between (G)MSC server and MGW: Tunnel Information Up** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------------| +| Tunnel Information Up | MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination from where the tunnel data is sent. | +| | | Tunnel Data | M | This information element contains the tunnel data that is provided between MGWs. | +| Tunnel InformationUp Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the Bearer Termination where the command was executed. | + +### 16.2.14 Tunnel Information Down + +This procedure is used to transfer tunnel data from the (G)MSC server to the MGW. + +**Table 16.15: Procedures between (G)MSC server and MGW: Tunnel Information** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------|-----------|--------------------------|------------------------------|---------------------------------------------------------------------------------------------| +| Tunnel Information Down | (G)MSC-S | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where to the tunnel data is sent. | +| | | Tunnel Data | M | This information element contains the tunnel data that is provided between MGWs. | +| Tunnel Information Down Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +NOTE: This procedure may be combined with Prepare Bearer or Establish Bearer procedure. + +### 16.2.15 Send Tone + +This procedure is used to send a tone. + +**Table 16.16: Procedures between (G)MSC server and MGW: Send Tone** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------|-----------|-----------------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Send Tone
(G)MSC-S | | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination/Bearer Termination Request | M | This information element indicates the existing bearer termination or requests a new bearer termination where the tone is sent. | +| | | Tone | M | This information element indicates the tone to be generated. | +| | | Notify Tone Completion | O | This information element requests a notification of a completed tone. | +| | | Tone Direction | O | This information element indicates the tone direction in the bearer termination. | +| | | Tone Timing | O | This information element indicates the time for the tone. | +| | | Notify termination heartbeat | C | This information element requests termination heartbeat indications. This information element shall be included when requesting a new ephemeral bearer termination. | +| Send Tone Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +NOTE: This procedure may be combined with Join Bearer Termination or Isolate Bearer Termination procedure. + +### 16.2.16 Stop Tone + +This procedure is used to stop the tone. + +**Table 16.17: Procedures between (G)MSC server and MGW: Stop Tone** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Stop Tone | (G)MSC-S | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the tone is stopped. | +| | | Stop Tone | M | This information element requests that tone generation is stopped. | +| Stop Tone Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.17 Play Announcement + +This procedure is used to play an announcement. + +**Table 16.18: Procedures between (G)MSC server and MGW: Play Announcement** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|-----------------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Play Announcement
(G)MSC-S | | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination/Bearer Termination Request | M | This information element indicates the existing bearer termination or requests a new bearer termination where the announcement is sent. | +| | | Announcement | M | This information element indicates the announcement to be played. | +| | | Notify Announcement Completion | O | This information element requests a notification of a completed announcement. | +| | | Announcement Direction | O | This information element indicates the announcement direction in the bearer termination. | +| | | Announcement Timing | O | This information element indicates the time for the announcement. | +| | | Notify termination heartbeat | C | This information element requests termination heartbeat indications. This information element shall be included when requesting a new ephemeral bearer termination. | +| Play Announcement Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +NOTE: This procedure may be combined with Join Bearer Termination or Isolate Bearer Termination procedure. + +### 16.2.18 Stop Announcement + +This procedure is used to stop the announcement. + +**Table 16.19: Procedures between (G)MSC server and MGW: Stop Announcement** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------|-----------|--------------------------|------------------------------|----------------------------------------------------------------------------------------------| +| Stop Announcement | (G)MSC-S | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the announcement is stopped. | +| | | Stop Announcement | M | This information element requests that announcement playing is stopped. | +| Stop Announcement Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.19 Announcement Completed + +This procedure is used to notify the completed announcement. + +**Table 16.20: Procedures between (G)MSC server and MGW: Announcement Completed** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|----------------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------------| +| Announcement Completed | MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the announcement was completed. | +| | | Announcement Completed | M | This information element indicates completion of the announcement. | +| Announcement Completed Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the Bearer Termination where the command was executed. | + +### 16.2.20 Tone Completed + +This procedure is used to notify the completed tone. + +**Table 16.21: Procedures between (G)MSC server and MGW: Tone Completed** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Tone Completed | MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the tone was completed. | +| | | Tone Completed | M | This information element indicates completion of the tone. | +| Tone Completed Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the Bearer Termination where the command was executed. | + +### 16.2.21 Detect DTMF + +This procedure is used to request detection of a DTMF tone. + +**Table 16.22: Procedures between (G)MSC server and MGW: Detect DTMF** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------|-----------|-----------------------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| +| Detect DTMF | (G)MSC-S | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination/Bearer Termination Request | M | This information element indicates the existing bearer termination or requests a new bearer termination where the DTMF tone detection is requested. | +| | | Digit | M | This information element requests MGW to detect a DTMF tone. | +| Detect DTMF Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +NOTE This procedure may be combined with Prepare Bearer, Prepare\_IP\_Transport, Establish Bearer, Reserve Circuit, Reserve RTP Connection Point procedure, Configure RTP Connection Point or Reserve and Configure RTP Connection Point. This list of procedures is not exhaustive. + +### 16.2.22 Stop DTMF Detection + +This procedure is used to stop detection of the DTMF tone. + +**Table 16.23: Procedures between (G)MSC server and MGW: Stop DTMF Detection** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------------------| +| Stop DTMF Detection | (G)MSC-S | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the DTMF tone detection is stopped. | +| | | Stop DTMF Detection | M | This information element requests that DTMF tone detection is stopped. | +| Stop DTMF Detection Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.23 Report DTMF + +This procedure is used to report a detected DTMF tone. + +**Table 16.24: Procedures between (G)MSC server and MGW: Report DTMF** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------|-----------|--------------------------|------------------------------|---------------------------------------------------------------------------------------------| +| Report DTMF | MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the DTMF tone was detected. | +| | | Digit | M | This information element reports the detected DTMF tone. | +| Report DTMF Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the Bearer Termination where the command was executed. | + +### 16.2.24 Send DTMF + +This procedure is used to request sending of a DTMF tone. + +**Table 16.25: Procedures between (G)MSC server and MGW: Send DTMF** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------|-----------|-----------------------------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| Send DTMF | (G)MSC-S | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination/Bearer Termination Request | M | This information element indicates the existing bearer termination or requests a new bearer termination where the DTMF tone generation is requested. | +| | | Digit | M | This information element requests MGW to generate a DTMF tone. | +| | | DTMF Tone Timing | O | This information element indicates the time for the DTMF tone in the bearer termination. | +| Send DTMF Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.25 Stop DTMF + +This procedure is used to stop sending of the DTMF tone. + +**Table 16.26: Procedures between (G)MSC server and MGW: Stop DTMF** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------| +| Stop DTMF | (G)MSC-S | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the DTMF tone generation is stopped. | +| | | Stop DTMF | M | This information element requests that DTMF tone generation is stopped. | +| Stop DTMF Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.26 MGW Out-of-Service/ Maintenance locking + +This procedure is used to indicate that the MGW will go out of service or is maintenance locked. + +**Table 16.27: Procedures between (G)MSC server and MGW: MGW Out-of-Service or Maintenance Locked** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------| +| MGW Out-of-Service/
Maintenance locked | MGW | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates the root termination for the command. | +| | | Reason | M | This information element indicates the reason for service change. | +| | | Method | M | This information element indicates the method for service change. | +| MGW Out-of-Service/
Maintenance locked Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates the root termination where the command was executed. | + +### 16.2.27 MGW Communication Up + +This procedure is used to indicate that the MGW is back in service. + +**Table 16.28: Procedures between (G)MSC server and MGW: MGW Communication Up** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| MGW Communication Up | MGW | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates the root termination for the command. | +| | | Reason | M | This information element indicates the reason for service change. | +| | | Method | M | This information element indicates the method for service change. | +| MGW Communication Up Ack (G)MSC-S | | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates the root termination where the command was executed. | +| | | (G)MSC-S Address | O | This information element indicates the (G)MSC server signalling address to which the MGW should preferably attempt to re-register. | + +### 16.2.28 MGW Restoration + +This procedure is used to indicate the MGW failure or recovery. + +**Table 16.29: Procedures between (G)MSC server and MGW: MGW Restoration** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| MGW Restoration | MGW | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates the root termination for the command. | +| | | Reason | M | This information element indicates the reason for the service change. | +| | | Method | M | This information element indicates the method for service change. | +| MGW Restoration Ack (G)MSC-S | | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates the root termination where the command was executed. | +| | | (G)MSC-S Address | O | This information element indicates the (G)MSC server signalling address to which the MGW should preferably attempt to re-register. | + +### 16.2.29 MGW Register + +This procedure is used to register the MGW. + +**Table 16.30: Procedures between (G)MSC server and MGW: MGW Register** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| MGW Register | MGW | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates the root termination for the command. | +| | | Reason | M | This information element indicates the reason for the service change. | +| | | Method | M | This information element indicates the method for service change. | +| | | Protocol Version | M | This information element indicates the protocol version for Mc interface requested by the MGW. | +| | | Service Change Profile | M | This information element indicates the profile for the Mc interface requested by the MGW. | +| MGW Register Ack
(G)MSC-S | | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates the root termination where the command was executed. | +| | | Protocol Version | O | This information element indicates the protocol version for Mc interface supported by the (G)MSC server. | +| | | Service Change Profile | O | This information element indicates the profile for the Mc interface supported by the (G)MSC Server. | +| | | (G)MSC-S Address | O | This information element indicates the (G)MSC server signalling address to which the MGW should preferably attempt to re-register. | + +### 16.2.30 MGW Re-register + +This procedure is used to re-register the MGW. + +**Table 16.31: Procedures between (G)MSC server and MGW: MGW Re-register** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------| +| MGW Re-register | MGW | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates the root termination for the command. | +| | | Reason | M | This information element indicates the reason for the service change. | +| | | Method | M | This information element indicates the method for service change. | +| | | Protocol Version | M | This information element indicates the protocol version for Mc interface requested by the MGW. | +| | | Service Change Profile | M | This information element indicates the profile for the Mc interface requested by the MGW. | +| MGW Re-register Ack
(G)MSC-S | | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates the root termination where the command was executed. | +| | | Protocol Version | O | This information element indicates the protocol version for Mc interface supported by the (G)MSC server. | +| | | Service Change Profile | O | This information element indicates the profile for the Mc interface supported by the (G)MSC Server. | +| | | (G)MSC-S Address | O | This information element indicates the (G)MSC server signalling address to which the MGW should preferably attempt to re-register. | + +### 16.2.31 (G)MSC Server Ordered Re-register + +This procedure is used by the (G)MSC server to request the MGW to register itself. + +**Table 16.32: Procedures between (G)MSC server and MGW: (G)MSC Server Ordered Re-register** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------| +| (G)MSC Server
Ordered Re-register | (G)MSC-S | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates the root termination for the command. | +| | | Reason | M | This information element indicates the reason for the service change. | +| | | (G)MSC-S Address | O | This information element indicates the (G)MSC server signalling address. | +| (G)MSC Server
Ordered Re-register Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates the root termination where the command was executed. | + +### 16.2.32 (G)MSC Server Restoration + +This procedure is used to indicate the (G)MSC server failure or recovery. + +**Table 16.33: Procedures between (G)MSC server and MGW: (G)MSC Server Restoration** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------| +| (G)MSC Server Restoration | (G)MSC-S | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates the root termination for the command. | +| | | Reason | M | This information element indicates the reason for the service change. | +| | | Method | M | This information element indicates the method for service change. | +| (G)MSC Server Restoration Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates the root termination where the command was executed. | + +### 16.2.33 (G)MSC Server Out of Service + +This procedure is used to indicate that (G)MSC server has gone out of service. + +**Table 16.34: Procedures between (G)MSC server and MGW: (G)MSC Server Out of Service** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|----------------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------| +| (G)MSC Server Out of Service | (G)MSC-S | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates the root termination for the command. | +| | | Reason | M | This information element indicates the reason for the service change. | +| | | Method | M | This information element indicates the method for service change. | +| (G)MSC Server Out of Service Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates the root termination where the command was executed. | + +### 16.2.34 Termination Out-of-Service + +This procedure is used to indicate that physical termination(s) will go out of service. + +**Table 16.35: Procedures between (G)MSC server and MGW: Termination Out-of-Service** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Termination Out-of-Service | MGW | Context | M | This information element indicates the context for the command. | +| | | Bearer Termination | M | This information element indicates the bearer termination(s) for the command. | +| | | Reason | M | This information element indicates the reason for service change. | +| | | Method | M | This information element indicates the method for service change. | +| Termination Out-of-Service Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.35 Termination Restoration + +This procedure is used to indicate that physical termination(s) are back in service. + +**Table 16.36: Procedures between (G)MSC server and MGW: Termination Restoration** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Termination Restoration | MGW | Context | M | This information element indicates the context for the command. | +| | | Bearer Termination | M | This information element indicates the bearer termination(s) for the command. | +| | | Reason | M | This information element indicates the reason for service change. | +| | | Method | M | This information element indicates the method for service change. | +| Termination Restoration Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.36 Audit Value + +This procedure is used to audit values of different object(s). + +**Table 16.37: Procedures between (G)MSC server and MGW: Audit Value** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Audit Value | (G)MSC-S | Context | M | This information element indicates the context for the command. | +| | | Bearer Termination | M | This information element indicates the bearer termination(s) for the command. | +| | | Object(s) | M | This information element indicates the object(s) to be audited. | +| Audit Value Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | +| | | Value(s) | M | This information element indicates the value(s) of the object(s). | + +### 16.2.37 Audit Capability + +This procedure is used to audit capabilities of different object(s). + +**Table 16.38: Procedures between (G)MSC server and MGW: Audit Capability** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|----------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Audit Capability | (G)MSC-S | Context | M | This information element indicates the context for the command. | +| | | Bearer Termination | M | This information element indicates the bearer termination(s) for the command. | +| | | Object(s) | M | This information element indicates the object(s) which capability is requested. | +| Audit Capability Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | +| | | Capabilities(s) | M | This information element indicates the capabilities of the object(s). | + +### 16.2.38 Capability Update + +This procedure is used to indicate update of an object capability. + +**Table 16.39: Procedures between (G)MSC server and MGW: Capability Update** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Capability Update | MGW | Context | M | This information element indicates the context for the command. | +| | | Bearer Termination | M | This information element indicates the bearer termination(s) for the command. | +| | | Reason | M | This information element indicates the reason for service change. | +| | | Method | M | This information element indicates the method for service change. | +| Capability Update Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.39 Command Reject + +This command is used to reject the received command request. It may be used as response to any of the above procedures. + +**Table 16.40: Procedures between (G)MSC server and MGW: Command Reject** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|----------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Command Reject | Both | Context | M | This information element indicates the context where the command was rejected. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was rejected. | +| | | Error | M | This information element indicates the error that caused command rejection. | + +### 16.2.40 Activate Voice Processing Function + +This procedure is used to activate the voice processing (echo cancellation) function. + +**Table 16.41: Procedures between (G)MSC server and MGW: Activate Voice Processing Function** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|----------------------------------------|-----------|------------------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------| +| Activate Voice Processing Function | (G)MSC-S | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the voice processing function is activated. | +| | | Activate Voice Processing Function | M | This information element requests to activate the voice processing function. | +| Activate Voice Processing Function Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.41 Modify Bearer Characteristics + +This procedure is used to modify the bearer characteristics. + +**Table 16.42: Procedures between (G)MSC server and MGW: Modify Bearer Characteristics** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------|-----------|--------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Modify Bearer Characteristics | (G)MSC-S | Context | M | This information element indicates the existing context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for the bearer to be modified. | +| | | Bearer Service Characteristics | C | This information element indicates the bearer service requested by the user. This information element is not included if the Codec information element is provided. It may be included for a data call (see 3GPP TS 29.007 [37] and 3GPP TS 29.232 [6]). | +| | | Circuit Switched Data | C | This information element indicates the PLMN bearer capabilities and when applicable GSM channel coding and user bit rate. This information element shall be included according to 3GPP TS 29.007 [37] and 3GPP TS 29.232 [6] for a non-speech call by the MSC server, or by the anchor-MSC in case of inter-MSC handover, for UMTS radio access network side bearer termination and for network side bearer termination. | +| | | Codec | C | This information element indicates the speech or multimedia coding format to be used for the bearer. This information element is included for the speech call and may be included for a SCUDIF multimedia call (see 3GPP TS 23.172 [38], 3GPP TS 29.007 [37] and 3GPP TS 29.232 [6]), for UMTS radio access network side bearer termination and for network side bearer termination. | +| | | Framing Protocol | O | This information element indicates the framing protocol to be used for the bearer. | +| Modify Bearer Characteristics Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.42 Protocol Negotiation Result + +This procedure is used to inform the MSC about protocol negotiation result. + +**Table 16.43: Procedures between MSC server and MGW: Protocol Negotiation Result** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------|-----------|-----------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| IWF Protocol Indication | MGW | Context | M | This information element indicates the existing context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for the bearer to be modified. | +| | | Protocol Negotiation result | M | This information element indicates the IWF protocol negotiation result | +| IWF Protocol Indication Ack | MSC | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.43 MGW Resource Congestion Handling - Activate + +This procedure is used to activate the congestion handling mechanism. + +**Table 16.44: Procedures between (G)MSC server and MGW: MGW Resource Congestion Handling - Activate** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------------------------|-----------|--------------------------|------------------------------|----------------------------------------------------------------------------------------------------------| +| MGW Resource Congestion Handling – Activate | (G)MSC-S | Context | M | This information element indicates that all context are applicable for the root termination. | +| | | Root Termination | M | This information element indicates that root termination is where the congestion mechanism is activated. | +| | | Congestion Activate | M | This information element requests to activate the congestion mechanism. | +| MGW Resource Congestion Handling - Activate Ack | MGW | Context | M | This information element indicates that all context are where the command was executed. | +| | | Root Termination | M | This information element indicates that root termination is where the command was executed. | + +### 16.2.44 MGW Resource Congestion Handling - Indication + +This procedure is used to inform the (G)MSC server that traffic restriction is advised. + +**Table 16.45: Procedures between (G)MSC server and MGW: MGW Resource Congestion Handling - Indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------| +| MGW Resource Congestion Handling - Indication | MGW | Context | M | This information element indicates all context are applicable for the root termination. | +| | | Root Termination | M | This information element indicates that root termination is where the congestion mechanism was activated. | +| | | Reduction | M | This information element indicates the load percentage to be reduced. | + +| | | | | | +|---------------------------------------------------|--------|------------------|---|---------------------------------------------------------------------------------------------| +| MGW Resource Congestion Handling - Indication Ack | (G)MSC | Context | M | This information element indicates all context are where the command was executed. | +| | | Root Termination | M | This information element indicates that root termination is where the command was executed. | + +### 16.2.45 Bearer Modification Support + +This procedure is used to notify that the established bearer can be modified. + +**Table 16.46: Procedures between (G)MSC server and MGW: Bearer Modification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------|-----------|--------------------------|------------------------------|---------------------------------------------------------------------------------------------| +| Bearer Modification Support | MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the bearer was established. | +| | | Bearer Modification | M | This information element notifies that the established bearer can be modified. | +| Bearer Modification Support Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the Bearer Termination where the command was executed. | + +### 16.2.46 CTM report + +This procedure is used to notify the outcome of the CTM negotiation in the user plane. + +**Table 16.47: Procedures between (G)MSC server and MGW: CTM report** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|----------------|-----------|----------------------------|------------------------------|-----------------------------------------------------------------------------------------------------| +| CTM report | MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the CTM function was activated | +| | | Outcome of CTM negotiation | M | This information element indicates whether the CTM negotiation in user plane was successful or not. | +| CTM report Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the Bearer Termination where the command was executed. | + +### 16.2.47 Prepare\_IP\_Transport + +This procedure is used to prepare for a bearer establishment when IuCS on IP is supported by the MSC. + +**Table 16.48: Procedures between (G)MSC server and MGW: Prepare\_IP\_Transport** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|----------------------------------|-----------|------------------------------------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Prepare_IP_Transport
(G)MSC-S | | Context/Context Request | M | This information element indicates the existing context or requests a new context for the IP Access bearer termination. | +| | | Bearer Termination Request | M | This information element requests a new bearer termination for the IP Access bearer to be established. | +| | | Iu UDP Port Request | M | This information element requests the Iu UDP Port in the MGW | +| | | IP Transport Address Request | M | This information element requests the IP address of the MGW. | +| | | Bearer Characteristics/
Bearer Characteristics Requests | M | This information element indicates the preferred characteristics of the bearer connection or requests the MGW to select and provide the bearer characteristics. | +| | | Bearer Service Characteristics | C | This information element indicates the bearer service requested by the user. This information element is not included if the Codec information element is provided. It may be included for a data call (see 3GPP TS 29.007 [37] and 3GPP TS 29.232 [6]). | +| | | Notify Bearer Event | O | This information element requests a notification of an established bearer, a released bearer, a modified bearer or a bearer modification failure. | +| | | Circuit Switched Data | C | This information element indicates the PLMN bearer capabilities and when applicable the user bit rate. This information element shall be included according to 3GPP TS 29.007 [37] and 3GPP TS 29.232 [6] for a non-speech call by the MSC server, or by the anchor-MSC in case of inter-MSC handover, for a UMTS radio access network side bearer termination. | +| | | Codec | C | This information element indicates the speech or multimedia coding format to be used for the bearer. This information element is included for a speech call and may be included for a SCUDIF multimedia call (see 3GPP TS 23.172 [38], 3GPP TS 29.007 [37] and 3GPP TS 29.232 [6]), for a UMTS radio access network side bearer termination. | +| | | Framing Protocol | O | This information element indicates the framing protocol to be used for the bearer. | +| | | Cellular Text telephony modem | C | This information element indicates the need of CTM function. | +| | | IP Realm Identifier | O | This information element indicates the IP realm of the IP termination. | +| | | Notify termination heartbeat | M | This information element requests termination heartbeat indications. | +| Prepare IP Transport Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | +| | | IP Transport Address | M | This information element indicates the IP address of the MGW | +| | | Iu UDP Port | M | This information element requests the Iu UDP Port in the MGW | + +### 16.2.48 Modify IP Transport Address + +This procedure is used when IuCS on IP is supported by the MGW and IuUP in transparent mode is configured. + +**Table 16.49: Procedures between (G)MSC server and MGW: RNC IP address notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------|-----------|--------------------------|------------------------------|--------------------------------------------------------------------------------------------------| +| Modify IP Transport Address | MSC-S | Context | M | This information element indicates the context for the IP bearer termination. | +| | | Bearer Termination | M | This information element indicates the IP bearer termination where the RNC IP Address is needed. | +| | | IP Transport address | M | This information element indicates the IP address of the RNC | +| | | Iu UDP Port | M | This information element indicates the Iu UDP Port in the RNC | +| Modify IP Address Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the IP bearer termination where the command is executed. | + +### 16.2.49 Emergency Call Indication + +This procedure is used to indicate that the call is an emergency call. + +**Table 16.50: Procedures between (G)MSC server and MGW: Emergency Call Indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|--------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------| +| Emergency Call Indication | (G)MSC-S | Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Emergency Call Indicator | M | This information element indicates the emergency call information | +| Emergency Call Indication Ack | MGW | Context | M | This information element indicates the context where the command was executed. | + +### 16.2.50 Trace Activation + +This procedure is used for activation of a Trace Session in a MGW. + +**Table 16.51: Procedures between (G)MSC server and MGW: Trace Activation** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------|-----------|-----------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------| +| Trace Activation | MSC-S | Context | M | This information element indicates the context for the command. | +| | | Bearer Termination | M | This information element indicates the bearer termination(s) for the command. | +| | | Trace Reference | C | Defined in 3GPP TS 32.421 and 3GPP TS 32.422 | +| | | Trace Session Recording Reference | C | Defined in 3GPP TS 32.421 and 3GPP TS 32.422 | +| | | Triggering Events | C | Defined in 3GPP TS 32.421 and 3GPP TS 32.422 | +| | | Trace Depth | C | Defined in 3GPP TS 32.421 and 3GPP TS 32.422 | +| | | List of interfaces | O | Defined 3GPP TS 32.422 | +| | | Trace Activity Control | M | This information element indicates the trace activation) | +| | | IMSI | C | This information element shows the IMSI of the traced subscriber. Either IMSI or IMEI(SV) must be provided. | +| | | IMEI(SV) | C | This information element shows the IMEI(SV) of the traced equipment. Either IMSI or IMEI(SV) must be provided. | +| | | Notify Trace Activation result | O | This information element requests a notification of the result of the trace activation. | +| Trace Activation Reply | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.51 Trace Deactivation + +This procedure is used for deactivation of a Trace Session in a MGW.. + +**Table 16.52: Procedures between (G)MSC server and MGW: Trace Deactivation** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------| +| Trace Deactivation | MSC-S | Context | M | This information element indicates the context for the command. | +| | | Bearer Termination | M | This information element indicates the bearer termination(s) for the command. | +| | | Trace Reference | M | Defined in 3GPP TS 32.421 and 3GPP TS 32.422 | +| | | Trace Activity Control | M | This information element indicates the trace deactivation | +| Trace Deactivation Reply | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed | + +### 16.2.52 Trace Activation result notification + +This procedure is used for informing the MSC Server about the result of the Trace Session Activation. + +**Table 16.53: Procedures between MGW and (G)MSC Server: Trace Activation result notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Trace Activation result notification | MGW | Context | M | This information element indicates the context for the command | +| | | Bearer Termination | M | This information element indicates the bearer termination(s) for the command | +| | | Result | M | This information element defines the result of the Trace Session Activation | +| Trace Activation result notification Ack | MSC-S | Context | M | This information element indicates the context where the command was executed | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.53 Continuity Check Tone + +This procedure is used by the (G)MSC to order the MGW to generate a continuity check tone at a TDM termination and to inform the (G)MSC about the result of the continuity check as soon as the continuity check tone is received or a time-out occurs. + +**Table 16.54: Continuity Check Tone procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------|-----------|---------------------------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------| +| Continuity Check Tone | (G)MSC | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | TDM Termination | M | This information element indicates the bearer termination | +| | | Request for continuity tone sending | M | This information request the MGW to apply the continuity check procedure on the indicated TDM termination | +| | | Request for continuity check tone detection | M | This information request the MGW to inform of result of the continuity check procedure on the indicated TDM termination | +| Continuity Check Tone Ack | IMGW | Context | M | This information element indicates the context where the command was executed. | + +### 16.2.54 Continuity Check Verify + +This procedure is used by the MGW to indicate towards the (G)MSC that the continuity check at a TDM termination has been completed and to return the result of the check: success or failure. + +**Table 16.55: Continuity Check Verify procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------|-----------|---------------------------------|------------------------------|--------------------------------------------------------------------------------------------------| +| Continuity check Verify | MGW | Context/t | M | This information element indicates the context where the command was executed. | +| | | TDM Termination | M | This information element indicates the TDM termination involved in the procedure | +| | | Outcome of the continuity check | M | This information element indicates the outcome of the continuity check (successful/unsuccessful) | +| Continuity Check Verify Ack | (G)MSC | Context | M | This information element indicates the context where the command was executed. | + +### 16.2.55 Continuity Check Response + +This procedure is used by the (G)MSC to order the MGW to loop back an incoming continuity check tone at a TDM termination. + +**Table 16.56: Continuity Check Response procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|----------------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------| +| Continuity Check Response | (G)MSC | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | TDM Termination | M | This information element indicates the bearer termination | +| | | Request for loop back of the continuity tone | M | This information request the MGW to loop back the continuity check tone on the indicated TDM termination | +| Continuity Check Response Ack | IMGW | Context | M | This information element indicates the context where the command was executed. | + +### 16.2.56 Rate Change + +This procedure is used to notify that the CS data rate should be changed. + +**Table 16.57: Procedures between (G)MSC server and MGW: Rate Change** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------|-----------|--------------------------|------------------------------|----------------------------------------------------------------------------------------------| +| Rate Change | MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the rate change is required. | +| | | Rate | M | This information element notifies the current rate. | +| Rate Change Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.57 Bearer Modified + +This procedure is used to notify the modified bearer. + +**Table 16.2.57/1: Procedures between (G)MSC server and MGW: Bearer Modified** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Bearer Modified | MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the bearer was modified. | +| | | Bearer Modified | M | This information element notifies a bearer modification. | +| Bearer Modified Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.58 Bearer Modification Failed + +This procedure is used to notify the failed bearer modification. + +**Table 16.2.58/1: Procedures between (G)MSC server and MGW: Bearer Modification failed** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------|-----------|-----------------------------|------------------------------|-------------------------------------------------------------------------------------------------| +| Bearer Modification Failed | MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the bearer modification failed. | +| | | Bearer Modification failure | M | This information element notifies a bearer modification failure | +| Bearer Modification Failed Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +### 16.2.59 Termination heartbeat indication + +This procedure is used to report indication of hanging termination. + +**Table 16.2.59/1: Procedures between (G)MSC server and MGW: Hanging termination indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------| +| Termination heartbeat indication | MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the termination heartbeat is reported. | +| | | Termination heartbeat | M | Hanging termination event as defined in 3GPP TS 29.232 [6]. | +| Termination heartbeat indication Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the Bearer Termination where the command was executed. | + +### 16.2.60 Inactivity timeout activation + +This procedure is used to activate the inactivity timeout mechanism. + +**Table 16.2.60/1: Procedures between (G)MSC server and MGW: Inactivity timeout activation** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------| +| Inactivity timeout activation | (G)MSC-S | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates that root termination is where the inactivity timeout mechanism is activated. | +| | | Inactivity Timeout | M | Inactivity timeout event as defined in 3GPP TS 29.232 [6]. | +| Inactivity timeout activation Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates that root termination is where the command was executed. | + +### 16.2.61 Inactivity timeout indication + +This procedure is used by MGW to report indication of inactivity timeout to MGC. + +**Table 16.2.61/1: Procedures between (G)MSC server and MGW: Inactivity timeout indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------| +| Inactivity timeout indication | MGW | Context | M | This information element indicates the context for the command. | +| | | ROOT Termination | M | This information element indicates that root termination is where the inactivity timeout mechanism was activated. | +| | | Inactivity Timeout | M | Inactivity timeout event as defined in 3GPP TS 29.232 [6]. | +| Inactivity timeout indication Ack | (G)MSC-S | Context | M | This information element indicates the context where the command was executed. | +| | | ROOT Termination | M | This information element indicates that root termination is where the command was executed. | + +### 16.2.62 Reserve RTP Connection Point + +This procedure is used to reserve an RTP bearer termination. + +**Table 16.2.62.1: Reserve RTP Connection Point** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------|---------------|-------------------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserve RTP Connection Point | (G)MSC-Server | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Termination Request | M | This information element requests a new termination for the bearer to be established. | +| | | IP Interface | O | This information element specifies the type of external interface to be used for the IP termination (e.g. AoIP). | +| | | Local IP Resources | M | This information element indicates the resource(s) (e.g. codec, auxiliary payload types) for which the MGW shall be prepared to receive user data. | +| | | ReserveValue | C | This information element indicates if multiple local resources are to be reserved.
This information element shall be included if a speech codec and auxiliary payload types are required. | +| | | Local Connection Address Request | M | This information element requests an IP address and port number on the MGW that the remote end can send user plane data to. | +| | | Notify termination heartbeat | M | This information element requests termination heartbeat indications. | +| | | Notify Released Bearer | O | This information element requests a notification of a released bearer. | +| | | IP Realm Identifier | O | This information element indicates the IP realm of the IP termination. | +| | | Cellular Text telephony modem | C | This information element indicates the need of CTM function. (NOTE 1) | +| | | Number of desired listener context terminations | O | This information element indicates the number of desired terminations for a listener context in a VGCS or VBS call. It should be included in the first ADD request which establishes a Listener context. (NOTE 1) | +| | | Circuit Switched Data | C | This information element indicates the PLMN bearer capabilities and when applicable GSM channel coding. This information element shall be included according to 3GPP TS 29.007 [37] and 3GPP TS 29.232 [6] for a non-speech / non SCUDIF multimedia call (see 3GPP TS 23.172 [20]) by the MSC server, or by the anchor-MSC in case of inter-MSC handover, for an anchor MGW network termination. | +| | | IP Version | C | This information element indicates the version of the internet protocol to be applied at the termination for the user plane. This is required for IP address translation. (NOTE 4) | +| | | DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the IP termination. (NOTE 4) | + +| | | | | | +|--|--|-------------------------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the IP termination should be copied from the received value or set to a specific value. (NOTE 4) | +| | | Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. (NOTE 4) | +| | | Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This may be included if remote source address filtering is included. It shall not be included if remote source address filtering is not included. (NOTE 4) | +| | | Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. (NOTE 4) | +| | | Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 2, NOTE 4) | +| | | Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 2, NOTE 4) | +| | | Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. (NOTE 4) | +| | | Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. (NOTE 4) | +| | | Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. (NOTE 4) | +| | | RTCP handling | O | Indicates whether or not the CS-MGW shall reserve a port for an RTCP flow. (NOTE 4) | +| | | Traffic Policing Required | O | This information element indicates that policing of the media flow is required. (NOTE 4) | +| | | Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream. (NOTE 3, NOTE 4) | +| | | Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream. (NOTE 3, NOTE 4) | +| | | Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. (NOTE 4) | +| | | Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. (NOTE 4) | + +| | | | | | | +|--------------------------------------------------------------------------------------------------------------------|-----|--------------------------|---|---------------------------------------------------------------------------------------------------------------------------------|--| +| Reserve RTP Connection Point Ack | MGW | Context | M | This information element indicates the context where the command was executed. | | +| | | Termination | M | This information element indicates the termination where the command was executed. | | +| | | Local IP Resources | M | This information element indicates the resources that the MGW has reserved to receive the user plane data from the remote peer. | | +| | | Local Connection Address | M | This information element indicates the IP address and port on the MGW that shall receive user plane data from the remote peer. | | +| NOTE 1: Only applies for Access side terminations | | | | | | +| NOTE 2: Remote Source Port and Remote Source Port Range are mutually exclusive. | | | | | | +| NOTE 3: At least one of these IEs shall be present when policing is required. | | | | | | +| NOTE 4: This information element is used for border control functions as defined in Annex A of 3GPP TS 29.235 [44] | | | | | | + +### 16.2.63 Configure RTP Connection Point + +This procedure is used to configure or reconfigure an RTP bearer termination. + +##### **Table 16.2.63.1: Configure RTP Connection Point Procedure** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------|---------------|-------------------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Configure RTP Connection Point | (G)MSC-Server | Context | M | This information element indicates the existing context. | +| | | Termination | M | This information element indicates the existing bearer termination. | +| | | IP Interface | O | This information element specifies the type of external interface to be used for the IP termination (e.g. AoIP). | +| | | Local IP Resources | O | This information element indicates the resources (e.g. codec, auxiliary payload types) that the MGW may use on the reception of user plane data. | +| | | Remote IP Resources | O | This information element indicates the resources (e.g. codec, auxiliary payload types) that the MGW may send user plane data to. | +| | | Local Connection Address | O | This information element indicates the IP address and port on the MGW that the remote peer can send user plane data to. | +| | | Remote Connection Address | O | This information element indicates the IP address and port that the MGW can send user plane data to. | +| | | Reserve Value | C | This information element indicates if multiple resources are to be reserved. This information element shall be included if a speech codec and auxiliary payload types are required. | +| | | Cellular Text telephony modem | C | This information element indicates the need of CTM function. (NOTE 1) | +| | | Number of desired listener context terminations | O | This information element indicates the number of desired terminations for a listener context in a VGCS or VBS call. It should be included in the first ADD request which establishes a Listener context. (NOTE 1) | +| | | Circuit Switched Data | O | This information element indicates the PLMN bearer capabilities and when applicable GSM channel coding. This information element shall be included according to 3GPP TS 29.007 [37] and 3GPP TS 29.232 [6] for a non-speech/non SCUDIF multimedia call by the MSC server, or by the anchor-MSC in case of inter-MSC handover for an anchor MGW network termination. | +| | | DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the IP termination. (NOTE 4) | +| | | DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the IP termination should be copied from the received value or set to a specific value. (NOTE 4) | +| | | Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. (NOTE 4) | + +| | | | | | +|------------------------------------|-----|-------------------------------------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This may be included if remote source address filtering is included. It shall not be included if remote source address filtering is not included. (NOTE 4) | +| | | Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. (NOTE 4) | +| | | Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 2, NOTE 4) | +| | | Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 2, NOTE 4) | +| | | Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. (NOTE 4) | +| | | Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. (NOTE 4) | +| | | Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. (NOTE 4) | +| | | RTCP handling | O | Indicates whether or not the CS-MGW shall reserve a port for an RTCP flow. (NOTE 4) | +| | | Traffic Policing Required | O | This information element indicates that policing of the media flow is required. (NOTE 4) | +| | | Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream.(NOTE 3, NOTE 4) | +| | | Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream.(NOTE 3, NOTE 4) | +| | | Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. (NOTE 4) | +| | | Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. (NOTE 4) | +| Configure RTP Connection Point Ack | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | +| | | Local IP Resource | O | This information element indicates the resources that the MGW has reserved to receive the user plane data from the far end. | + +| | | | | +|--|---------------------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Remote IP Resource | C | This information element indicates the resource (i.e. codec) that the MGW shall use to send user data to. Shall be present if corresponding IE is present in the request. | +| | Local Connection Address | O | This information element indicates the IP address and port on the MGW that the remote end can send user plane data to. | +| | Remote Connection Address | C | This information element indicates the IP address and port that the MGW can send user plane data to. Shall be present if corresponding IE is present in the request. | + +NOTE 1: Only applies for Access side terminations +NOTE 2: Remote Source Port and Remote Source Port Range are mutually exclusive. +NOTE 3: At least one of these IEs shall be present when policing is required. +NOTE 4: This information element is used for border control functions as defined in Annex A of 3GPP TS 29.235 [44] + +### 16.2.64 Reserve and Configure RTP Connection Point + +This procedure is used to reserve and configure multimedia-processing resources for an RTP termination. + +**Table 16.2.64.1: Reserve and Configure RTP Connection Point** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------------------|---------------|----------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserve and Configure RTP Connection Point | (G)MSC-Server | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Termination/Termination Request | M | This information element indicates the existing bearer termination or requests a new termination for the bearer to be established. | +| | | IP Interface | O | This information element specifies the used interface type for the IP termination (e.g. NboIP). | +| | | Local IP Resources | M | This information element indicates the resource(s) (e.g. codec, auxiliary payload types) for which the MGW shall be prepared to receive user data. | +| | | Remote IP Resources | M | This information element indicates the resources (e.g. codec, auxiliary payload types) that the MGW shall use to send user data. | +| | | Reserve Value | C | This information element indicates if multiple IP resources are to be reserved. This information element shall be included if a speech codec and auxiliary payload types are required. | +| | | Cellular Text telephony modem | C | This information element indicates the need of CTM function. (NOTE 1) | +| | | Local Connection Address Request | M | This information element requests an IP address and port number on the MGW that the remote end can send user plane data to. | + +| | | | +|-------------------------------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Remote Connection Address | M | This information element indicates the IP address and ports of the remote party that the MGW can send user plane data to. | +| Notify termination heartbeat | M | This information element requests termination heartbeat indications. | +| Notify Released Bearer | O | This information element requests a notification of a released bearer. | +| IP Realm Identifier | O | This information element indicates the IP realm of the IP termination. | +| Circuit Switched Data | O | This information element indicates the PLMN bearer capabilities and when applicable GSM channel coding. This information element shall be included according to 3GPP TS 29.007 [6] and 3GPP TS 29.232 [8] for a non-speech / non SCUDIF multimedia call (see 3GPP TS 23.172 [20]) by the MSC server, or by the anchor-MSC in case of inter-MSC handover, for an anchor MGW network termination. | +| IP Version | C | This information element indicates the version of the internet protocol to be applied at the termination for the user plane. This is required for IP address translation. (NOTE 4) | +| DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the IP termination. (NOTE 4) | +| DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the IP termination should be copied from the received value or set to a specific value. (NOTE 4) | +| Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. (NOTE 4) | +| Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This may be included if remote source address filtering is included. It shall not be included if remote source address filtering is not included. (NOTE 4) | +| Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. (NOTE 4) | +| Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 2, NOTE 4) | +| Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. It shall not be included if remote source port filtering is not included. (NOTE 2, NOTE 4) | +| Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. (NOTE 4) | +| Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. (NOTE 4) | +| Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. (NOTE 4) | + +| | | | | | +|--------------------------------------------|-----|----------------------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | RTCP handling | O | Indicates whether or not the CS-MGW shall reserve a port for an RTCP flow. (NOTE 4) | +| | | Traffic Policing Required | O | This information element indicates that policing of the media flow is required. (NOTE 4) | +| | | Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream.(NOTE 3, NOTE 4) | +| | | Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream.(NOTE 3, NOTE 4) | +| | | Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. (NOTE 4) | +| | | Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. (NOTE 4) | +| Reserve and Configure RTP Connection Point | MGW | Context | M | This information element indicates the context where the command was executed. | +| | | Termination | M | This information element indicates the termination where the command was executed. | +| | | Local IP Resources | M | This information element indicates the resources that the MGW has reserved to receive the user plane data from the remote side. | +| | | Remote IP Resources | M | This information element indicates the resource (i.e. codec) that the MGW shall use to send user data. | +| | | Local Connection Addresses | M | This information element indicates the IP address and port on the MGW that shall receive user plane data. | + +NOTE 1: Only applies for Access side terminations +NOTE 2: Remote Source Port and Remote Source Port Range are mutually exclusive. +NOTE 3: At least one of these IEs shall be present when policing is required. +NOTE 4: This information element is used for border control functions as defined in Annex A of 3GPP TS 29.235 [44] + +### 16.2.65 Realm Availability Change - Activation + +This procedure is used to activate the realm availability notification mechanism. + +**Table 16.2.65.1: Realm Availability Change - Activation** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------------|---------------|------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------| +| Realm Availability Change – Activate | (G)MSC-Server | Context | M | This information element indicates the NULL context. | +| | | Root Termination | M | This information element indicates that root termination is where the realm availability change notification mechanism is activated. | +| | | Realm Availability Change Activate | M | This information element requests to activate the realm availability change notification mechanism. | +| Realm Availability Change -Activate Ack | MGW | Context | M | This information element indicates the NULL context. | +| | | Root Termination | M | This information element indicates that root termination is where the command was executed. | + +NOTE: This procedure is used for border control functions as defined in Annex A of 3GPP TS 29.235 [44] + +### 16.2.66 Realm Availability Change - Indication + +This procedure is used to inform the (G)MSC-Server that there has been a change to the list of currently available realms. + +**Table 16.2.66.1: Realm Availability Change - Indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------------------|---------------|-------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| Realm Availability Change - Indication | MGW | Context | M | This information element indicates the NULL context. | +| | | Root Termination | M | This information element indicates that root termination is where the realm availability change notification mechanism was activated. | +| | | Changes to Realm Availability | M | This information element indicates the changes to the list of available realms. | +| Realm Availability Change - Indication Ack | (G)MSC-Server | Context | M | This information element indicates the NULL context. | +| | | Root Termination | M | This information element indicates that root termination is where the command was executed. | + +NOTE: This procedure is used for border control functions as defined in Annex A of 3GPP TS 29.235 [44] + +### 16.2.67 Media Inactivity Notification + +This procedure is used to notify the (G)MSC-Server of media inactivity on the MGW. + +**Table 16.2.67.1: Media Inactivity Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------|---------------|--------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------| +| Media Inactivity Notification | MGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the media inactivity detection was activated. | +| | | Media Inactivity | M | This information element notifies the (G)MSC-Server of Media inactivity detection on the bearer termination. | +| Media Inactivity Notification Ack | (G)MSC-Server | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +NOTE: This procedure is used for border control functions as defined in Annex A of 3GPP TS 29.235 [44] + +# 17 Bearer Redirect + +The BICC [22] Bearer Redirect mechanism may be used for optimising the bearer path when an endpoint of a call changes due to the operation of an application layer service. + +## 17.1 Example of use of Bearer Redirect with Call Forwarding on No Reply (CFNRy) + +Before CFNRy: + +![Figure 17.1A: Network model diagram showing the state before CFNRy. A GMSC-S is connected to an MGW G (CTX1). The MGW G is connected to an MGW A (CTX2). The MGW A is connected to an RNC. The GMSC-S is also connected to an MSC-S A. The MSC-S A is connected to the MGW A. The RNC is connected to the MGW A. The connections are shown as dashed lines: green for the GMSC-S to MSC-S A path, red for the MGW G to MGW A path, and green for the MSC-S A to RNC path.](77c78bfdbbee0e121808674b08fd7046_img.jpg) + +Figure 17.1A: Network model diagram showing the state before CFNRy. A GMSC-S is connected to an MGW G (CTX1). The MGW G is connected to an MGW A (CTX2). The MGW A is connected to an RNC. The GMSC-S is also connected to an MSC-S A. The MSC-S A is connected to the MGW A. The RNC is connected to the MGW A. The connections are shown as dashed lines: green for the GMSC-S to MSC-S A path, red for the MGW G to MGW A path, and green for the MSC-S A to RNC path. + +Figure 17.1A: Before CFNRy (Network model) + +After CFNRy and Bearer Redirection: + +![Figure 17.1B: Network model diagram showing the state after CFNRy and Bearer Redirection. The GMSC-S is now connected to an MSC-S B. The MSC-S B is connected to an MGW B (CTX2). The MGW B is connected to the MGW G (CTX1). The GMSC-S is also connected to the MSC-S A. The MSC-S A is connected to the MGW A (CTX2). The MGW A is connected to the RNC. The connections are shown as dashed lines: green for the GMSC-S to MSC-S A path, green for the GMSC-S to MSC-S B path, red for the MGW G to MGW B path, and green for the MSC-S A to RNC path.](a49d2de328d172709cd326a374415d6d_img.jpg) + +Figure 17.1B: Network model diagram showing the state after CFNRy and Bearer Redirection. The GMSC-S is now connected to an MSC-S B. The MSC-S B is connected to an MGW B (CTX2). The MGW B is connected to the MGW G (CTX1). The GMSC-S is also connected to the MSC-S A. The MSC-S A is connected to the MGW A (CTX2). The MGW A is connected to the RNC. The connections are shown as dashed lines: green for the GMSC-S to MSC-S A path, green for the GMSC-S to MSC-S B path, red for the MGW G to MGW B path, and green for the MSC-S A to RNC path. + +Figure 17.1B: CFNRy and Bearer Redirect (Network model) + +Figure 17.2 shows the message sequence example for the call forwarding on no reply with Bearer Redirect. In the example, after the call and the bearer towards the access have been released MSC server A requests the MGW A to remove the bearer termination for the served mobile subscriber. MSC server A requests the GMSC server to redirect the bearer to the forwarded to subscriber (interactions towards the access are not shown), using MSC server A as a call control anchor. Once the bearer towards MGW B is established the GMSC server instructs MGW G to connect the incoming bearer to the new bearer (towards MGW B) and informs MSC server A. Once informed that the new bearer has been established MSC server A instructs the GMSC server to removes the old bearer termination (towards MGW A). + +![Sequence diagram showing information flow for CFNRy with Bearer Redirect. Lifelines: GMSC-S, MGW G, MSC-S A, MGW A, MSC-S B, MGW B. The diagram details message exchanges for context management, bearer redirection, and release procedures.](536768a30136cd5c2d57f46c25d1d804_img.jpg) + +The sequence diagram illustrates the information flow for CFNRy with Bearer Redirect across six lifelines: GMSC-S, MGW G, MSC-S A, MGW A, MSC-S B, and MGW B. + +**Phase 1: Initial Setup** + +- A block indicates **Normal call and bearer establishment** across all lifelines. +- A condition box above MSC-S A and MGW A indicates **Expiry of no reply condition timer**. +- A condition box above MGW A and MSC-S B indicates **Release of Iu Bearer**. +- GMSC-S sends **Redirect Backwards Request** to MSC-S A. +- MSC-S A sends **ADD.request (\$)** to MGW G (Context (\$)). +- MGW G sends **ADD.reply (T5)** to MSC-S A (Context (C3)). +- MSC-S A sends **Prepare Bearer** to MGW G. +- MSC-S A sends **Bearer Redirection Connect Backwards** to GMSC-S. +- MSC-S A sends **Initial Address + Bearer Information** to MSC-S B. +- MSC-S B sends **ADD.request (\$)** to MGW B (Context (\$)). +- MSC-S B sends **Establish Bearer** to MGW A. +- MGW B sends **ADD.reply (T6)** to MSC-S B (Context (C4)). + +**Phase 2: Bearer Establishment** + +- A block indicates **Bearer Establishment** between MGW G, MGW A, and MGW B. +- MGW G sends **NOTIFY.request (T5)** to MSC-S A (Context (C3)). +- MSC-S A sends **NOTIFY.reply (T5)** to MGW G (Context (C3)). +- MGW B sends **NOTIFY.request (T6)** to MSC-S B (Context (C4)). +- MSC-S B sends **NOTIFY.reply (T6)** to MGW B (Context (C4)). +- MGW A sends **Bearer Established** to MGW G. +- MSC-S B sends **Address Complete + Answer** to MSC-S A. +- MSC-S A sends **Address Complete + Answer** to GMSC-S. +- GMSC-S sends **Redirect Bearer Connected** to MSC-S A. + +**Phase 3: Release Procedures** + +- GMSC-S sends **MOD.request (T5)** to MGW G (Context (C1)). +- MGW G sends **MOD.reply (T5)** to GMSC-S (Context (C1)). +- GMSC-S sends **Redirect Bearer Release Request** to MSC-S A. +- MSC-S A sends **Redirect Bearer Release Proceed** to GMSC-S. +- MSC-S A sends **SUB.request (T3)** to MGW A (Context (C2)). +- MGW A sends **SUB.reply (T3)** to MSC-S A (Context (C2)). +- MSC-S A sends **Release Termination** to MGW A. +- MSC-S A sends **Redirect Bearer Release Complete** to GMSC-S. +- GMSC-S sends **SUB.request (T2)** to MGW G (Context (C1)). +- MGW G sends **SUB.reply (T2)** to GMSC-S (Context (C1)). +- GMSC-S sends **Release Termination** to MGW G. + +Sequence diagram showing information flow for CFNRy with Bearer Redirect. Lifelines: GMSC-S, MGW G, MSC-S A, MGW A, MSC-S B, MGW B. The diagram details message exchanges for context management, bearer redirection, and release procedures. + +**Figure 17.2: Information flow for CFNRy with Bearer Redirect (message sequence chart)** + +# 18 (G)MSC MGW Tandeming + +In all call flow examples a (G)MSC server may tandem (either during call setup or during an active call, as part of an application layer service invocation) the bearer through one or more MGWs under its control, in order to access bearer resources which may be distributed over a number of specialised MGWs. + +## 18.1 Example of use of MSC MGW Tandeming during call setup to provide bearer access to specialised MGW resources + +Before MGW tandeming: + +![Diagram of MSC before MGW Tandeming](e699312f10b7831b388e6c6a5e7032ee_img.jpg) + +The diagram shows two MSC servers, GMSC-S and MSC-S A, connected by a green dashed line. Below GMSC-S is MGW A, connected by a solid blue line. Below MSC-S A is MGW B, also connected by a solid blue line. A red dotted line connects MGW A and MGW B. MGW A has two ports labeled T1 and T2, and a central box labeled CTX1. MGW B has two ports labeled T3 and T4, and a central box labeled CTX2. + +Diagram of MSC before MGW Tandeming + +**Figure 18.1A: MSC before MGW Tandeming during call setup to provide bearer access to specialised MGW resources (Network model)** + +After MGW tandeming: + +![Diagram of MSC after MGW Tandeming](288220dc8e18b23fc8f294cf1ca909b4_img.jpg) + +The diagram shows the same GMSC-S and MSC-S A as before. MGW A remains connected to GMSC-S. However, MSC-S A is now connected to both MGW B and MGW C by solid blue lines. MGW B is connected to MGW A and MGW C by red dotted lines. MGW C has two ports labeled T5 and T6, and a central box labeled CTX3. The green dashed line between GMSC-S and MSC-S A remains. + +Diagram of MSC after MGW Tandeming + +**Figure 18.1B: MSC after MGW Tandeming during call setup to provide bearer access to specialised MGW resources (Network model)** + +The figure 18.2 below shows the message sequence example for MSC MGW Tandeming during call setup to provide bearer access to specialised MGW resources. In the example, after the signalling towards MSC server A and the bearer towards the MGW B is established, MSC server A requests the MGW B to tandem the bearer and terminate it at MGW C, where specialised bearer resources which are not available at MGW B may be provided. + +![Figure 18.2: MSC MGW Tandeming during call setup to provide bearer access to specialised MGW resources (message sequence chart).](92724c769da9d46b730fde1a6dccb023_img.jpg) + +The diagram is a message sequence chart showing the interaction between five entities: GMSC-S, MGW A, MSC-S A, MGW B, and MGW C. The sequence starts with a 'Normal call and bearer establishment' phase. MSC-S A sends an 'ADD.request (\$)' to MGW B. MGW B responds with 'ADD.reply (T4)'. MSC-S A then sends another 'ADD.request (\$)' to MGW C. MGW C responds with 'ADD.reply (T5)'. MGW B initiates a 'Prepare Bearer' phase with MGW C. Finally, a 'Bearer Establishment' phase occurs between MGW B and MGW C. The 'Establish Bearer' phase is shown on the left side, involving Context (C2), Context (\$), and Context (C3) messages between GMSC-S and MGW A. + +Figure 18.2: MSC MGW Tandeming during call setup to provide bearer access to specialised MGW resources (message sequence chart). + +Figure 18.2: MSC MGW Tandeming during call setup to provide bearer access to specialised MGW resources (message sequence chart) + +# 19 Timers for bearer independent CS core network + +Table 19.1: Timers for bearer independent CS core network + +| Timer identity | Timer value | Timer started | Timer stopped | Timer expiry | +|------------------------------|----------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|---------------------------------------------------| +| Start_Bearer_E establishment | 1 – 14 seconds | Paging procedure is started. Applied only if network side bearer establishment is delayed until paging procedure is completed. | Paging procedure is completed or optionally when Call Confirmed message is received. | The network side bearer establishment is started. | + +# 20 Multiple IP Realms + +Figure 20/1 shows a scenario to support multiple IP realms when the Iu interface or Nb interface supports IP bearer. + +![Figure 20/1 Multiple IP realms scenario for Iu or Nb interface.](43ff52fe5a7c6990f4f0d5e0ca55d4b4_img.jpg) + +The diagram illustrates a scenario for multiple IP realms. It shows a central network element (represented by a large rectangle) connected to two separate IP realms (represented by clouds labeled RAN1 and RAN2). The network element has two interfaces (represented by horizontal lines) that connect to the IP realms. The IP realms are connected to two separate user equipment (UE) devices (represented by small circles with antennas). The diagram shows the flow of data from the UE devices through the IP realms and into the central network element. + +Figure 20/1 Multiple IP realms scenario for Iu or Nb interface. + +Figure 20/1 Multiple IP realms scenario for Iu or Nb interface + +The RAN1, RAN2, CN1 and CN2 represents separate IP realm. The definition of IP realm is specified in IETF RFC 2663 [41]. + +The Logical Port 1/2/3/4 represents a logical port connected with the IP realm in the MGW. + +For establishing session when multiple IP realms are used in the MGW, the MGC may indicate the IP realm identifier to the MGW. The MGW shall assign the IP termination in the IP realm indicated. + +A default IP realm may be configured such that if the MGW has not received the IP realm identifier and the MGW supports multiple IP realms then the default IP realm shall be used. + +If the MGW does not support the option to indicate an IP realm then it is free to select an IP port as per implementation permitted in previous releases. + +# --- Annex A (informative): Change History + +| Change history | | | | | | | | +|----------------|-------|-----------|-----|-----|--------------------------------------------------------------------------------------------------------|-------|-------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| Jul 2000 | | | | | Initial draft | 0.0.1 | 0.0.2 | +| Aug 2000 | | | | | Comments from TSG-CN WG4#3 incorporated and draft further elaborated | 0.0.2 | 0.1.0 | +| Sep 2000 | | | | | Contributions and comments from TSG-CN WG4#4 incorporated and draft further elaborated | 0.1.0 | 0.2.0 | +| Oct 2000 | | | | | Contributions and comments from TSG-CN WG4 Ad Hoc incorporated and draft further elaborated | 0.2.0 | 1.0.1 | +| Nov 2000 | CN#10 | | | | For information to TSG-CN #10 | 1.0.1 | 1.1.0 | +| Jan 2001 | | | | | Contributions and comments from TSG-CN WG4 #6 incorporated and draft further elaborated. | 1.1.0 | 1.1.1 | +| Feb 2001 | | | | | New clause structure for handover, editorial corrections. | 1.1.1 | 1.2.0 | +| Feb 2001 | | | | | Contributions and comments from TSG-CN WG4 Ad Hoc incorporated. | 1.2.0 | 2.0.0 | +| Mar 2001 | CN#11 | NP-010081 | | | Contributions and comments from TSG-CN WG4 #7 incorporated.
Approved in CN#11 | 2.0.0 | 4.0.0 | +| Jun 2001 | CN#12 | N4-010676 | 002 | 1 | Voice Processing Function Alignment/Clean Up for Call Handover and Relocation | 4.0.0 | 4.1.0 | +| Jun 2001 | CN#12 | N4-010678 | 004 | 1 | Corrections to Call Clearing | 4.0.0 | 4.1.0 | +| Jun 2001 | CN#12 | N4-010680 | 006 | 1 | Alignment of procedure names to TS 29.232 and editorial changes | 4.0.0 | 4.1.0 | +| Sep 2001 | CN#13 | NP-010452 | 008 | 1 | Slight Misalignment of Continuity Message Handling | 4.1.0 | 4.2.0 | +| Sep 2001 | CN#13 | NP-010452 | 009 | | Updates to Clause 9.1 | 4.1.0 | 4.2.0 | +| Sep 2001 | CN#13 | | | | Editorial clean up | 4.1.0 | 4.2.0 | +| Dec 2001 | CN#14 | NP-010619 | 012 | | Correction of Handover/Relocation for Speech and Non-speech calls | 4.2.0 | 4.3.0 | +| Dec 2001 | CN#14 | NP-010619 | 014 | 2 | New timer to support long paging in bearer independent network | 4.2.0 | 4.3.0 | +| Dec 2001 | CN#14 | NP-010619 | 016 | 1 | Correction for Release of Network Bearer | 4.2.0 | 4.3.0 | +| Dec 2001 | CN#14 | NP-010631 | 011 | | Introduction of MGW Congestion Handling | 4.3.0 | 5.0.0 | +| Dec 2001 | CN#14 | NP-010631 | 013 | 1 | Maintenance locking of MG | 4.3.0 | 5.0.0 | +| Mar 2002 | CN#15 | NP-020029 | 021 | | (G)MSC restoration | 5.0.0 | 5.1.0 | +| Mar 2002 | CN#15 | NP-020029 | 023 | 2 | Correction of Bearer Modification Handling | 5.0.0 | 5.1.0 | +| Jun 2002 | CN#16 | NP-020260 | 024 | | MSC server GTT enhancement | 5.1.0 | 5.2.0 | +| Jun 2002 | CN#16 | NP-020260 | 025 | 1 | Alignment of terminology regarding GERAN access | 5.1.0 | 5.2.0 | +| Jun 2002 | CN#16 | NP-020248 | 028 | | Correction of an incorrect reference in Section 8.3.3.2 | 5.1.0 | 5.2.0 | +| Sep 2002 | CN#17 | NP-020458 | 026 | 4 | Introduction of GERAN lu-mode | 5.2.0 | 5.3.0 | +| Sep 2002 | CN#17 | NP-020459 | 029 | 1 | Misalignment between TS 23205 and TS 29232 for Global Text Telephony | 5.2.0 | 5.3.0 | +| Sep 2002 | CN#17 | NP-020459 | 030 | 1 | Misalignment between TS 23.226 and TS 23.205 for Global Text Telephony. | 5.2.0 | 5.3.0 | +| Sep 2002 | CN#17 | NP-020463 | 033 | 1 | Correction on wrong message handling for subsequent Handover | 5.2.0 | 5.3.0 | +| Dec 2002 | CN#18 | NP-020597 | 031 | 3 | lu-cs over IP related corrections for 23.205 | 5.3.0 | 5.4.0 | +| Dec 2002 | CN#18 | NP-020596 | 035 | 2 | CAMEL4 Call Party Handling interworking with Bearer independent CS core | 5.3.0 | 5.4.0 | +| Dec 2002 | CN#18 | NP-020596 | 036 | 1 | Clarification of the termination of the lu interface components in the Bearer Independent Architecture | 5.3.0 | 5.4.0 | +| Mar 2003 | CN#19 | NP-030108 | 039 | 1 | Bearer Release for lu CS on IP | 5.4.0 | 5.5.0 | +| Jun 2003 | CN#20 | NP-030212 | 042 | | Clarification of handling of DTMF | 5.5.0 | 5.6.0 | +| Jun 2003 | CN#20 | NP-030212 | 044 | 1 | Clarification of handling of DTMF timing | 5.5.0 | 5.6.0 | +| Mar 2003 | CN#23 | NP-040052 | 050 | 1 | Use Modify command for change of flow direction to bothway | 5.6.0 | 5.7.0 | +| Dec 2004 | CN#26 | | | | Release 6 after CN#26 | 5.7.0 | 6.0.0 | +| Mar 2005 | CN#27 | NP-050057 | 045 | 7 | Addition of the trace package | 6.0.0 | 6.1.0 | +| Mar 2005 | CN#27 | NP-050034 | 052 | 2 | Stage 2 Procedure for Emergency Call Indication | 6.0.0 | 6.1.0 | +| Mar 2005 | CN#27 | NP-050028 | 056 | | Solving contradiction for Release Cause in Release Bearer Procedure between stage 2 and stage 3 | 6.0.0 | 6.1.0 | +| Jun 2005 | CT#28 | CP-050101 | 065 | | Multi-Party Conference call Implementation | 6.1.0 | 6.2.0 | +| Sep 2005 | CT#29 | CP-050289 | 059 | 2 | Introducing the ServiceChangeProfile also to the relevant stage 2 procedures | 6.2.0 | 6.3.0 | + +| | | | | | | | | +|----------|-------|-----------|------|---|----------------------------------------------------------------------------------------------------------------------|-------|-------| +| Sep 2005 | CT#29 | CP-050289 | 061 | 2 | MGW Recovery clarification | 6.2.0 | 6.3.0 | +| Sep 2005 | CT#29 | CP-050308 | 068 | 1 | Alignment of Stage 2 with Continuity test Procedure | 6.2.0 | 6.3.0 | +| Sep 2005 | CT#29 | CP-050277 | 071 | | Introduction of chapter to describe CMM message for GSM fax | 6.2.0 | 6.3.0 | +| Sep 2005 | CT#29 | CP-050289 | 073 | 1 | Notifications for IP Bearer Establishment | 6.2.0 | 6.3.0 | +| Sep 2005 | CT#29 | CP-050308 | 082 | | Minor correction in references | 6.2.0 | 6.3.0 | +| Sep 2005 | CT#29 | CP-050308 | 083 | 1 | Transparent data call request in dual mode case | 6.2.0 | 6.3.0 | +| Dec 2005 | CT#30 | CP-050608 | 0095 | | Correction of Notify establish bearer information element | 6.3.0 | 6.4.0 | +| Dec 2005 | CT#30 | CP-050603 | 0098 | | Missing stage 2 definition for Bearer Modified and Bearer Modification Failed procedures | 6.3.0 | 6.4.0 | +| Dec 2005 | CT#30 | CP-050603 | 0102 | | Correction of term Bearer Termination in procedures that concern the whole MGW | 6.3.0 | 6.4.0 | +| Dec 2005 | CT#30 | CP-050603 | 0104 | | Adding missing termination ID to Acknowledgement part of notification procedures | 6.3.0 | 6.4.0 | +| Dec 2005 | CT#30 | CP-050608 | 0107 | | Removing Notify Bearer Modification Information element from Prepare IP transport procedure | 6.3.0 | 6.4.0 | +| Dec 2005 | CT#30 | CP-050607 | 0108 | 1 | Bearer Released Event to Reserve Circuit procedure stage 2 | 6.3.0 | 6.4.0 | +| Dec 2005 | CT#30 | CP-050629 | 0089 | 2 | Clean-up of hanging contexts and terminations | 6.4.0 | 7.0.0 | +| Dec 2005 | CT#30 | CP-050629 | 0092 | 1 | Corrections for Delayed Backward Bearer Establishment with IP Transport | 6.4.0 | 7.0.0 | +| Dec 2005 | CT#30 | CP-050618 | 0110 | 2 | Correct the UP initialization error in Figure 6.6/1 | 6.4.0 | 7.0.0 | +| Mar 2006 | CT#31 | CP-060064 | 0117 | 3 | Correction To Termination State Handling | 7.0.0 | 7.1.0 | +| Mar 2006 | CT#31 | CP-060078 | 0120 | 2 | Clarification of periodic sending of Audits to recognize MGW unavailable | 7.0.0 | 7.1.0 | +| Mar 2006 | CT#31 | CP-060064 | 0123 | 1 | Miscellaneous corrections to messages/procedures | 7.0.0 | 7.1.0 | +| Mar 2006 | CT#31 | CP-060078 | 0126 | 1 | Internal bearer for multiparty service | 7.0.0 | 7.1.0 | +| Mar 2006 | CT#31 | CP-060078 | 0127 | 1 | Wrong implementation of CP-050629 / C4-051767 (CR#089rev2) | 7.0.0 | 7.1.0 | +| Mar 2006 | CT#31 | CP-060078 | 0128 | | ServiceChangeVersion in MGW Re-Register procedure | 7.0.0 | 7.1.0 | +| Mar 2006 | CT#31 | CP-060078 | 0132 | | Correct the termination error in figure 13.19 | 7.0.0 | 7.1.0 | +| Mar 2006 | CT#31 | CP-060064 | 0135 | 1 | Removal Of stream mode modification at bearer release | 7.0.0 | 7.1.0 | +| Mar 2006 | CT#31 | CP-060064 | 0141 | | Replacing Notify Bearer Modification information element with Notify Bearer Event in Prepare IP Transport procedure. | 7.0.0 | 7.1.0 | +| Jun 2006 | CT#32 | CP-060301 | 0150 | 1 | Multimedia & CSD calls | 7.1.0 | 7.2.0 | +| Jun 2006 | CT#32 | CP-060315 | 0153 | 1 | Solving contradiction between tunnel option in 23.205 and 29.232 | 7.1.0 | 7.2.0 | +| Dec 2006 | CT#34 | CP-060554 | 0165 | | Amend the call flow of handover procedure | 7.2.0 | 7.3.0 | +| | | CP-060569 | 0159 | 5 | Enhancements for VGCS/VBS in SPLIT architecture | | | +| | | CP-060569 | 0167 | 1 | Example of in-band information sending with the topology descriptor | | | +| Mar 2007 | CT#35 | CP-070014 | 0172 | 3 | IP domain connection indication | 7.3.0 | 7.4.0 | +| | | | 0173 | 1 | Clarify message sequence of VGCS call | | | +| Jun 2007 | CT#36 | CP-070322 | 0177 | | ServiceChangeMGCIId parameter | 7.4.0 | 7.5.0 | +| Sep 2007 | CT#37 | CP-070521 | 0180 | 3 | Correction To Call Hold | 7.5.0 | 7.6.0 | +| | | CP-070530 | 0185 | 2 | Establish internal Nb connections via IPBCP in MPTY | | | +| | | CP-070530 | 0190 | 3 | Support inactivity timer (H.248.14) for MGWs detecting the failure of MGC | | | +| Sep 2007 | CT#37 | CP-070569 | 0191 | 2 | Mandatory use termination heartbeat (H.248.36) when establish bearer/prepare bearer | 7.6.0 | 8.0.0 | +| Dec 2007 | CT#38 | CP-070749 | 0196 | 1 | Number of needed listener context terminations to ASCII package | 8.0.0 | 8.1.0 | +| | | | 0192 | 1 | Clarifications to Send Tone / Play Announcement procedures | | | +| Mar 2008 | CT#39 | CP-080011 | 0200 | | Detect DTMF event after reporting of DTMF | 8.1.0 | 8.2.0 | +| | | CP-080025 | 0204 | 1 | Private communication during a Multiparty call | | | +| Jun 2008 | CT#40 | CP-080271 | 0207 | 3 | Clarification of several inconsistencies in procedure | 8.2.0 | 8.3.0 | +| | | | 0208 | 1 | Clarification of subscribers' roles in CW procedure | | | +| | | | 0211 | 1 | Protocol negotiation result procedures between MSC Server and MGW | | | +| | | | 0209 | 3 | Support for A interface user plane over IP | | | +| | | | 0210 | 2 | Revision of scope of TS 23.205 | | | +| Sep 2008 | CT#41 | CP-080466 | 0213 | 1 | Handover Scenarios for AoIP | 8.3.0 | 8.4.0 | + +| | | | | | | | | +|----------|------------|-----------|------|---|---------------------------------------------------------------------------------------|--------|--------| +| | | | 0215 | | Call Clearing for A Interface on IP | | | +| | | | 0216 | 1 | IP interface type indicator | | | +| | | | 0217 | | Use of Global Text Telephony with A over IP | | | +| | | | 0218 | 1 | Combining certain procedures with 'Reserve RTP Connection Point' | | | +| Dec 2008 | CT#42 | CP-080705 | 0220 | 1 | Corrections to Call Forwarding procedures | 8.4.0 | 8.5.0 | +| | | CP-080710 | 0222 | 1 | Enhanced SRNS relocation | | | +| | | CP-080697 | 0224 | 2 | BSS Internal Handover procedure | | | +| | | CP-080697 | 0225 | | AoIP impacts on subclause 'Interworking with GERAN A interface' | | | +| | | CP-080695 | 0226 | 4 | Signalling of CAT Capability | | | +| | | CP-080697 | 0228 | 2 | Impact on HandoverRelocation and Interactions with Other Services for AoIP | | | +| Jun 2009 | CT#44 | CP-090312 | 0231 | 2 | Customized alerting tone indicators | 8.5.0 | 8.6.0 | +| | | CP-090309 | 0232 | | BSS Internal Handover procedure | | | +| | | | | | Correct previous entry in history table | 8.6.0 | 8.6.1 | +| Sep 2009 | CT#45 | CP-090541 | 0234 | | Clarification of Use of Reserve and Configure RTP Connection Point | 8.6.1 | 8.7.0 | +| | | CP-090541 | 0235 | | IWF Rate Change Procedure with AoIP | | | +| | | CP-090541 | 0236 | | Removal of Editor's Notes for IP Interface Type | | | +| 2009-12 | - | - | - | - | Update to Rel-9 version (MCC) | 8.7.0 | 9.0.0 | +| 2010-09 | CT#49 | CP-100450 | 0239 | - | Terminating Access Bearer Assignment | 9.0.0 | 9.1.0 | +| 2011-03 | CT#51 | CP-110046 | 0243 | - | BSS Internal Handover | 9.1.0 | 9.2.0 | +| | | | 0240 | 1 | Adding CS-Ix functionalities to Mc-profile | | | +| 2011-03 | CT#51 | CP-110254 | 0241 | 2 | Introduction of LCLS | 9.2.0 | 10.0.0 | +| 2011-06 | CT#52 | CP-110352 | 0247 | 1 | Adding Local Connection Address request to Reserve and Configure RTP Connection point | 10.0.0 | 10.1.0 | +| 2011-09 | CT#53 | CP-110563 | 0249 | | Media inactivity notification procedure | 10.1.0 | 10.2.0 | +| 2011-09 | CT#53 | CP-110585 | 0250 | 2 | Addition of Anonymous Call Rejection in the CS layered architecture | 10.2.0 | 11.0.0 | +| 2013-09 | CT#61 | CP-130462 | 0251 | 1 | GERAN Iu Mode | 11.0.0 | 12.0.0 | +| 2015-06 | CT#68 | CP-150269 | 0253 | 2 | RT: Voice group call and voice broadcast services with AoIP | 12.0.0 | 12.1.0 | +| 2015-12 | CT#70 | | | | Update to Rel-13 version (MCC) | 12.1.0 | 13.0.0 | +| 2017-03 | CT#75 | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 | +| 2018-06 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | CT#88
e | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23251/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/23_series/23251/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..218fd99b1d5c182f9ebd330889dfe9f63892035e --- /dev/null +++ b/marked/Rel-16/23_series/23251/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56a489676f825b8d8c01b394293917bf8d40b38ac0fe6787e2b9d00fac8836ba +size 32720 diff --git a/marked/Rel-16/23_series/23251/24c9e038a791677ed33100667b64f7e6_img.jpg b/marked/Rel-16/23_series/23251/24c9e038a791677ed33100667b64f7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b9a9cda595ecec1ee9647bc9df460e34a0436a8 --- /dev/null +++ b/marked/Rel-16/23_series/23251/24c9e038a791677ed33100667b64f7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fbbae9d9de6b20ea545b113be789b94653ff8b910ccefa49f1b2ae1b1f7bc12 +size 39832 diff --git a/marked/Rel-16/23_series/23251/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/23_series/23251/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d36196b1a147cfa314e2fe24af6eff6e0196a32 --- /dev/null +++ b/marked/Rel-16/23_series/23251/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c18c5f907fb30454212e468d7bf266f025b97af17c95def9e20696b8c514c5b +size 110658 diff --git a/marked/Rel-16/23_series/23251/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23251/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..567b79b75fa73a59a265aa74cf570a6842cca833 --- /dev/null +++ b/marked/Rel-16/23_series/23251/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00b5fb5c2494ebb601616cd382412ae2ae30ba79e7520309af988f180cafce93 +size 103189 diff --git a/marked/Rel-16/23_series/23251/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23251/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d481409eff37c923357cc88f683a28b6c8db5651 --- /dev/null +++ b/marked/Rel-16/23_series/23251/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:685f4396eae8683d30a87fe329e323b2a6818893a7445cd2a61e4e6392e8eec2 +size 142739 diff --git a/marked/Rel-16/23_series/23251/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/marked/Rel-16/23_series/23251/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ef05d5f9ed749b9dd1de48eff57d78aa0bec17c --- /dev/null +++ b/marked/Rel-16/23_series/23251/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bdc5a50f7b5045c62406086a8af7490fbfcff23b55c19cf30e1467562d90d16 +size 69940 diff --git a/marked/Rel-16/23_series/23251/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/Rel-16/23_series/23251/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1f65959b0239a386e4c2cfe39f4d961ff76008b --- /dev/null +++ b/marked/Rel-16/23_series/23251/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f865ea534b77ee38e4cce229c7f7872cf53cd6709201df6685f716d594115128 +size 41940 diff --git a/marked/Rel-16/23_series/23251/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-16/23_series/23251/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d41c1db356ebf0deec9219109a36920c9ba4d437 --- /dev/null +++ b/marked/Rel-16/23_series/23251/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:652a3e79469d6f0c2b099baf25287d132c07906d1a5d8c55bfacfa8d6156b4c2 +size 114388 diff --git a/marked/Rel-16/23_series/23251/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/marked/Rel-16/23_series/23251/933ecd14c858bf3fc919222d8e357bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15146b9a263d922ca40d7b8b83d76e88f9092006 --- /dev/null +++ b/marked/Rel-16/23_series/23251/933ecd14c858bf3fc919222d8e357bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e2c8ad63cdb8a3027a6aa990d3b7907490017670f72abd73a95dafabe205ef9 +size 89226 diff --git a/marked/Rel-16/23_series/23251/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23251/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09a2e1b6a217aa84ff961369f0206ef649461d42 --- /dev/null +++ b/marked/Rel-16/23_series/23251/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a913d94b875760922021bab5f0deb0c9cf9a2cb05874532940f1e6653a8b92e +size 41212 diff --git a/marked/Rel-16/23_series/23251/cd141897aa368dbbaa398ace230cdd85_img.jpg b/marked/Rel-16/23_series/23251/cd141897aa368dbbaa398ace230cdd85_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ddf34e8ecb798a03a14480833d9ebfa15acfb82 --- /dev/null +++ b/marked/Rel-16/23_series/23251/cd141897aa368dbbaa398ace230cdd85_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2c19ba592d8ed9210e7b0ed9daec45c90268457f16ded51f94eb26cbbabb4c7 +size 69134 diff --git a/marked/Rel-16/23_series/23251/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Rel-16/23_series/23251/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef1921414f6c23f229e8a4d8a1db078d243fbaa9 --- /dev/null +++ b/marked/Rel-16/23_series/23251/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ba2613cd710a608a015d6cfc858b8e167d7dcc04bdd469263a4394dd561f160 +size 21962 diff --git a/marked/Rel-16/23_series/23251/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23251/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fb58a3e68a1f5b638d5d41d3ffb58cb131d9e55 --- /dev/null +++ b/marked/Rel-16/23_series/23251/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa72f6b5f9bab557bb8a0de06fc203ce9bf299be22c698e1f80f191137942109 +size 140824 diff --git a/marked/Rel-16/23_series/23251/raw.md b/marked/Rel-16/23_series/23251/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..5b7ae3f2b8b0646396a9efc4458c3c3f3a4c7508 --- /dev/null +++ b/marked/Rel-16/23_series/23251/raw.md @@ -0,0 +1,1256 @@ + + + + + + +# Contents + +| | | +|--------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Void..... | 8 | +| 3.3 Abbreviations ..... | 8 | +| 4 General Description ..... | 8 | +| 4.1 Overview ..... | 8 | +| 4.2 Core Network Operator and Network Selection ..... | 9 | +| 4.2.1 Core network operator identity..... | 9 | +| 4.2.2 Broadcast system information for network sharing..... | 10 | +| 4.2.3 Network selection in a shared network..... | 10 | +| 4.2.3.1 Behaviour of supporting UEs (GERAN, UTRAN and E-UTRAN)..... | 10 | +| 4.2.3.2 Behaviour of non-supporting UEs (GERAN, UTRAN)..... | 10 | +| 4.2.4 Assignment of core network operator and core network node..... | 10 | +| 4.2.5 PS and CS domain registration coordination in UTRAN and GERAN ..... | 11 | +| 4.2.5a PS and CS domain registration coordination in E-UTRAN ..... | 11 | +| 4.2.5.1 Void ..... | 12 | +| 4.2.5.2 Void ..... | 12 | +| 4.2.5.3 CS/PS domain coordination and operator selection in GERAN and UTRAN..... | 12 | +| 4.2.6 Attach/detach handling..... | 13 | +| 4.3 Network Name Display for Supporting UEs..... | 13 | +| 4.4 HPLMN Support ..... | 13 | +| 4.5 Support of Cell Broadcast Services and Warning System ..... | 14 | +| 4.6 Support of Extended Access Barring ..... | 14 | +| 4.7 Support of service identification for improved radio utilization for GERAN ..... | 14 | +| 5 Functional description..... | 14 | +| 5.1 UE functions..... | 14 | +| 5.2 RNC functions..... | 14 | +| 5.2a eNodeB functions..... | 15 | +| 5.2b BSC functions ..... | 16 | +| 5.3 MSC functions..... | 17 | +| 5.4 SGSN functions..... | 18 | +| 5.5 MME functions ..... | 19 | +| 6 Charging and accounting aspects..... | 20 | +| 7 Example signalling flows..... | 20 | +| 7.1 Network selection..... | 20 | +| 7.1.2 Non-supporting UEs in a GWCN configuration ..... | 20 | +| 7.1.3 Supporting UEs in a GWCN configuration..... | 22 | +| 7.1.4 Non-supporting UEs in a MOCN configuration ..... | 22 | +| 7.1.4.1 UTRAN based MOCN configuration..... | 22 | +| 7.1.4.2 GERAN based MOCN configuration..... | 25 | +| 7.1.4.3 CS registration after PS Handover..... | 28 | +| 7.1.5 Supporting UEs in a MOCN configuration ..... | 30 | +| 7.1.5.1 UTRAN based MOCN configuration..... | 30 | +| 7.1.5.2 GERAN based MOCN configuration..... | 31 | +| 7.1.6 Query to opposite domain ..... | 32 | + +| | | +|-----------------------------------------------------------------------------------------|-----------| +| Annex A (informative): Network Resource Indicator (NRI) allocation examples..... | 33 | +| A.1 NRI in shared UTRAN/GERAN networks..... | 33 | +| A.2 Alternatives for NRI split in UTRAN and GERAN ..... | 34 | +| A.3 NRI and CS/PS coordination in GWCN ..... | 35 | +| A.4 CSPS Coordination ..... | 35 | +| Annex B (normative): Interaction with other network capabilities ..... | 38 | +| B.1 General..... | 38 | +| B.2 Support for RAN sharing for CSG and hybrid cells ..... | 38 | +| Annex C (informative): Change History ..... | 39 | + +# --- Foreword + +This Technical Specification has been produced by the 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. + +# --- Introduction + +Network sharing is a way for operators to share the heavy deployment costs for mobile networks, especially in the roll-out phase. In the current mobile telephony marketplace, functionality that enables various forms of network sharing is becoming more and more important. These aspects have not really been addressed before Release 6 in 3GPP UTRAN based access networks, before Release 8 in 3GPP E-UTRAN based access networks and before Release 10 in 3GPP GERAN based access networks, although there has been functionality that supports a very basic type of network sharing since the Release 5 versions of the 3GPP specifications. + +To cope with 3GPP pre-Release 6 UTRAN UEs and with non supporting 3GPP GERAN UEs, this specification describes extra functionality for MSCs, SGSNs, BSCs and RNCs in order to provide network sharing functionality to "non-supporting UEs". + +In this Release of the specifications, all UTRAN and E-UTRAN capable UEs are required to support the UTRAN and E-UTRAN network sharing requirements. Hence the E-UTRAN and MMEs (which were introduced in 3GPP Release 8) do not need functionality to handle "non-supporting UEs". + +Scenarios and user requirements are described in TR 22.951 [1], while the current document presents the stage 2 details and descriptions of how these requirements are supported in a 3GPP GERAN, UTRAN and/or E-UTRAN based network. + +# --- 1 Scope + +The present document covers the details of Network Sharing for GERAN, UTRAN and E-UTRAN. It shows how several core network operators can share one radio access network and details the impacts on the network architecture. All UEs shall comply with existing requirements, among them PLMN selection and system information reception. The present document also defines requirements for network-sharing supporting UEs. + +# --- 2 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 22.951: "Service Aspects and Requirements for Network Sharing". +- [2] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [3] 3GPP TS 25.331: "RRC Protocol Specification". +- [4] 3GPP TS 23.122: "NAS Functions related to Mobile Station (MS) in idle mode". +- [5] 3GPP TS 32.250: "Telecommunication management; Charging management; Circuit Switched (CS) domain charging". +- [6] 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched (PS) domain charging". +- [7] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [8] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes". +- [9] 3GPP TS 23.401: "Technical Specification Group Services and System Aspects; GPRS enhancements for E-UTRAN access". +- [10] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRAN); Overall description; Stage 2". +- [11] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [12] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3". +- [13] 3GPP TS 25.413: "UTRAN Iu interface, Radio Access Network Application Part (RANAP) signalling". +- [14] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)". +- [15] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2". +- [16] 3GPP TS 44.018: "Radio Resource Control RRC Protocol Specification". +- [17] 3GPP TS 25.467: "UTRAN architecture for 3G Home Node B (HNB); Stage 2". + +- [18] 3GPP TS 22.042: "Network Identity and Time Zone (NITZ); Service description; Stage 1". +- [19] 3GPP TS 44.064: "General Packet Radio Service (GPRS); Mobile Station - Serving GPRS Support Node (MS SGSN) Logical Link Control (LLC) layer specification". +- [20] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". +- [21] 3GPP TS 29.280: "3GPP Sv interface (MME to MSC, and SGSN to MSC) for SRVCC". +- [22] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [23] 3GPP TS 22.011: "Service Accessibility". +- [24] 3GPP TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)". +- [25] 3GPP TS 48.008: "Mobile-services Switching Centre Base Station System (MSC BSS) interface; Layer 3 specification". +- [26] 3GPP TS 29.018: "General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) Visitors Location Register (VLR); Gs interface layer 3 specification". +- [27] 3GPP TS 29.118: "Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definition below apply. Terms and definitions not defined below can be found in TR 21.905 [2]. + +**Conventional network:** A PLMN consisting of radio access network and core network, by which only one serving operator provides services to its subscriber. Subscribers of other operators may receive services by national or international roaming. + +**Common PLMN:** The PLMN-id indicated in the system broadcast information as defined for conventional networks, which non-supporting UEs understand as the serving operator. + +**Core network operator:** An operator that provides services to subscribers as one of multiple serving operators that share at least a radio access network. Each core network operator may provide services to subscriber of other operators by national or international roaming. + +**Gateway Core Network:** A network sharing configuration in which parts of the core network (MSCs/SGSNs/MMEs) are also shared. + +**Multi-Operator Core Network:** A network-sharing configuration in which only the RAN is shared. + +**Non-supporting UE:** A UE that does not support network sharing in the sense that it ignores the additional broadcast system information that is specific for network sharing for 3GPP UTRAN and GERAN. In other specifications, the term "network sharing non-supporting UE" may be used. + +**Supporting UE:** A UE that supports network sharing in the sense that it is able to select a core network operator as the serving operator within a shared network. In other specifications, the term "network sharing supporting UE" may be used. + +**Anchor PLMN:** With regard to SRVCC from CS to PS, this Anchor PLMN points to the PS domain operator in which the voice media is anchored in Access Transfer Gateway as part of the SRVCC procedure. + +## 3.2 Void + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [2] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [2]. + +| | | +|---------|----------------------------------------------------| +| BSC | Base Station Controller | +| CN | Core Network | +| E-UTRAN | Evolved Universal Terrestrial Radio Access Network | +| eNodeB | E-UTRAN NodeB | +| gsmSCF | GSM Service Control Function | +| GERAN | GSM/EDGE Radio Access Network | +| GUTI | Globally Unique Temporary Identity | +| GWCN | Gateway Core Network | +| HLR | Home Location Register | +| HSS | Home Subscriber Server | +| MCC | Mobile Country Code | +| MME | Mobility Management Entity | +| MNC | Mobile Network Code | +| MOCN | Multi-Operator Core Network | +| MSC | Mobile Switching Centre | +| NITZ | Network Identity and Time Zone | +| PLMN | Public Land Mobile Network | +| RNC | Radio Network Controller | +| SGSN | Serving GPRS Support Node | +| TMSI | Temporary Mobile Subscriber Identity | +| UE | User Equipment | +| UTRAN | Universal Terrestrial Radio Access Network | +| VLR | Visitor Location Register | + +# --- 4 General Description + +## 4.1 Overview + +A network sharing architecture shall allow different core network operators to connect to a shared radio access network. The operators do not only share the radio network elements, but may also share the radio resources themselves. In addition to this shared radio access network the operators may or may not have additional dedicated radio access networks, like for example, 2G radio access networks. There are two identified architectures to be supported by network sharing. They are shown in the figures below. + +In both architectures, the radio access network is shared. Figure 1 below shows reference architecture for network sharing in which also MSCs and SGSNs are shared. This configuration will be referred to as a Gateway Core Network (GWCN) configuration. + +![Figure 1: A Gateway Core Network (GWCN) configuration for network sharing. The diagram shows three CN Operator boxes (A, B, and C) at the top. Below them are three Shared MSC/SGSN boxes. Dashed lines connect each operator to each shared node. Below a dashed horizontal line labeled 'Iu', there is an oval containing three RNC boxes, labeled 'Radio Access Network Operator X'. Solid lines connect each Shared MSC/SGSN box to one of the RNC boxes within the oval.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +Figure 1: A Gateway Core Network (GWCN) configuration for network sharing. The diagram shows three CN Operator boxes (A, B, and C) at the top. Below them are three Shared MSC/SGSN boxes. Dashed lines connect each operator to each shared node. Below a dashed horizontal line labeled 'Iu', there is an oval containing three RNC boxes, labeled 'Radio Access Network Operator X'. Solid lines connect each Shared MSC/SGSN box to one of the RNC boxes within the oval. + +**Figure 1: A Gateway Core Network (GWCN) configuration for network sharing. Besides shared radio access network nodes, the core network operators also share core network nodes** + +Figure 2 below shows the reference architecture for network sharing in which only the radio access network is shared, the Multi-Operator Core Network (MOCN) configuration. + +![Figure 2: A Multi-Operator Core Network (MOCN) configuration. The diagram shows three CN Operator boxes (A, B, and C) at the top. Below a dashed horizontal line labeled 'Iu', there is an oval containing a single RNC box, labeled 'Radio Access Network Operator X'. Solid lines connect each CN Operator box directly to this single RNC box.](dbe553cf16dd14073b89a8263a428664_img.jpg) + +Figure 2: A Multi-Operator Core Network (MOCN) configuration. The diagram shows three CN Operator boxes (A, B, and C) at the top. Below a dashed horizontal line labeled 'Iu', there is an oval containing a single RNC box, labeled 'Radio Access Network Operator X'. Solid lines connect each CN Operator box directly to this single RNC box. + +**Figure 2: A Multi-Operator Core Network (MOCN) in which multiple CN nodes are connected to the same RNC and the CN nodes are operated by different operators** + +The UE behaviour in both of these configurations shall be the same. No information concerning the configuration of a shared network shall be indicated to the UE. + +For the Evolved Packet System, only the PS domain of the above figures is relevant. For E-UTRAN access Figures 1 and 2 both apply but with the MME replacing the SGSN, the eNodeB replacing the RNC, and the S1 reference point replacing the Iu interface. + +For GERAN access, both GWCN and MOCN are applicable but with the BSC replacing the RNC and the A/Gb-Interfaces replacing the Iu interface. + +## 4.2 Core Network Operator and Network Selection + +Network sharing is an agreement between operators and shall be transparent to the user. This implies that a supporting UE needs to be able to discriminate between core network operators available in a shared radio access network and that these operators can be handled in the same way as operators in non-shared networks. + +### 4.2.1 Core network operator identity + +A core network operator is identified by a PLMN-id (MCC+MNC). + +### 4.2.2 Broadcast system information for network sharing + +If a shared RAN is configured to indicate available core network operators for selection by UEs, each cell in shared radio access network shall in the broadcast system information include information concerning available core network operators in the shared network. + +The available core network operators shall be the same for all cells of a Location Area in a shared UTRAN or GERAN network. + +For E-UTRAN, the Broadcast System Information broadcasts a basic set of PLMN IDs and optionally one or more additional set of PLMN IDs. All E-UTRAN UEs support reception of the basic set, only Release 14 and later E-UTRAN UEs are required to receive the additional set (see TS 36.331 [11]). + +The available core network operators shall be the same for all cells of a Tracking Area in a shared E-UTRAN network. The basic and the additional sets allow different (sets of) PLMNs to have different cell ID and TAC. + +A supporting UE decodes the broadcast system information and takes the information concerning available core network operators into account in network and cell (re-)selection procedures. Broadcast system information is specified in TS 44.018 [16] for GERAN, TS 25.331 [3] for UTRAN and TS 36.331 [11] for E-UTRAN. + +### 4.2.3 Network selection in a shared network + +#### 4.2.3.1 Behaviour of supporting UEs (GERAN, UTRAN and E-UTRAN) + +In some sharing scenarios, the sharing operators require the UTRAN/GERAN to broadcast, to non-supporting UEs, a PLMN ID that does not identify any of the sharing core network operators. In this case, it is necessary that a supporting UE does not select this "common PLMN ID". + +In other sharing scenarios, the sharing operators may want the PLMN broadcast to non-supporting UEs to be selectable by supporting UEs. + +A supporting UE decodes the broadcast system information to determine available core network operators in the shared network. The UE regards both the core network operators indicated in the broadcast system information and conventional networks as individual networks. The core network operators together with all conventional networks are candidate PLMNs for the PLMN selection procedure that shall be performed by the UE as specified in TS 23.122 [4]. + +In GERAN and UTRAN, non-supporting UEs use the broadcast "common PLMN-id" in their PLMN (re)selection processes. + +In UTRAN, supporting UEs shall use the PLMN-ids that are broadcast in the Multiple PLMN ID List information element in their PLMN (re)selection processes. UTRAN AS signalling permits the Multiple PLMN ID List to indicate to supporting UEs whether to include or exclude the MCC+MNC of the "common PLMN-id" in their network (re)selection processes. + +For supporting UEs, GERAN provides equivalent functionality to UTRAN. + +For E-UTRAN, the UE uses all of the received broadcast PLMN-ids in its PLMN (re)selection processes. + +#### 4.2.3.2 Behaviour of non-supporting UEs (GERAN, UTRAN) + +Non-supporting UEs ignore the broadcast system information that is relevant for network sharing. The common PLMN together with all conventional networks are candidate PLMNs for the PLMN selection procedure that shall be performed by the UE as specified in TS 23.122 [4]. + +It is recommended for the network and the UE to support the Network Identity part of the Network Identity and Time Zone (NITZ) feature (see TS 22.042 [18]) for providing the UE with the name of the serving PLMN operator. + +### 4.2.4 Assignment of core network operator and core network node + +When a UE performs an initial access to a shared network, one of available CN operators shall be selected to serve the UE. For non-supporting UEs, the shared network selects an operator from the available CN operators. For supporting UEs, the selection of core network operator by the UE shall be respected by the network. Supporting UEs inform the BSC/RNC/eNodeB of the network identity of the chosen core network operator. + +In a UTRAN GWCN configuration, the RNC relays the chosen network identity to the shared core network node (in UTRAN MOCN, the RNC indicates that the UE is a "supporting UE" by relaying the chosen network identity to the core network node). To permit GWCN operation, in E-UTRAN, the eNodeB always relays the chosen network identity to the shared MME. In a GERAN GWCN configuration, the BSC relays the chosen network identity to the core network node (in GERAN MOCN, the BSC indicates that the UE is a "supporting UE" by relaying the chosen network identity to the core network node). + +In a MOCN configuration, the RAN routes the UE's initial access to the shared network to one of the available CN nodes. Supporting UEs shall inform the RAN of the chosen core network operator so that the RAN can route correctly. For non-supporting UEs the shared network selects an operator from the available CN operators. A redirection to another CN operator may be required for non-supporting UEs until an operator is found that can serve the UE. Redirection is described in clause 7.1.4. + +After initial access to the shared network the UE does not change to another available CN operator as long as the selected CN operator is available to serve the UE's location. Only the network selection procedures specified in TS 23.122 [4] may cause a reselection of another available CN operator. Also the network does not move the UE to another available CN operator, e.g. by handover, as long as the selected CN operator is available to serve the UE's location. Furthermore the UE does not change to another CN node as long as the selected CN node is available to serve the UE's location. + +In GERAN and UTRAN, when the network signals location/routing area identities to supporting UEs, e.g. in location updating accept messages, these identities shall contain the chosen core network operator identity. For non-supporting UEs, they shall contain the common PLMN. The UE stores the received LAI/RAI on the SIM/USIM, as already specified in TS 24.008 [7]. + +In E-UTRAN, the chosen core network operator identity is included in the GUTI in e.g. the Attach Accept message. The UE shall store the received GUTI on the USIM according to the rules specified in TS 24.301 [12]. + +### 4.2.5 PS and CS domain registration coordination in UTRAN and GERAN + +In conventional networks, the same CN operator always serves the UE in CS and PS domains. In a shared network, supporting UEs shall behave as UEs in conventional networks with respect to registration with CS and PS domains and always register with the same operator for the CS and PS domains. CS/PS coordination should be performed at registration when a redirect attempt flag is included in A/Gb/Iu messages carrying the NAS registration message (see TS 48.008 [25], TS 48.018 [24], and TS 25.413 [13]). The term registration includes attach, and LA and RA updates. + +When multiple PLMNs are available and SRVCC from UTRAN/GERAN CS domain to E-UTRAN/HSPA PS is deployed, the source BSC/RNC determines a core network operator to be used in the target network based on current PLMN in use, Anchor PLMN provided by PS core network, or other information present in the BSC/RNC. The source BSC/RNC shall at handover indicate the selected core network operator to the source core network node in the handover required message. The anchor MSC Server shall forward the selected core network operator chosen by the source BSC/RNC to the target MME/SGSN. + +#### 4.2.5a PS and CS domain registration coordination in E-UTRAN + +When multiple core network operators share the E-UTRAN using a GWCN configuration, separate MSCs may still be used for the CS Fall Back functionality. In this case the MME uses the 'selected network' information received from the E-UTRAN to select an MSC from the already selected operator. + +When multiple PLMNs are available for CS domain, the MME selects the MSC for CS Fallback functionality based on the 'selected network' information received from the E-UTRAN, current TAI, old LAI provided by the UE and operator selection policies as specified in TS 23.272 [15]. In this case, the selected PLMN-id for CS domain may be different to the PLMN-id for EPS domain. If the selected MSC is shared network configured, the MME selects the CS domain operator as specified in TS 23.272 [15]. If the UE is a GERAN network-sharing non-supporting UE and the preferred RAT of the selected CS network is GERAN with GWCN configuration, or the preferred RAT of the selected CS network is shared network in GWCN configuration not offering the broadcast of available Core Network operators for selection by the UE, the MME sends the 'selected CS domain operator' in addition to the Common PLMN-id included in the LAI to the VLR. If the MSC is GWCN configured, the MSC applies local policy (e.g. uses a fixed split of IMSI ranges or IMSI hash) to determine the CN operator when the PLMN-id included in the LAI contains Common PLMN-id (i.e. does not identify any CS domain operator) and the 'selected CS domain operator' is absent. Otherwise, the MSC accepts the CS domain operator selected by the MME. + +When multiple PLMNs are available for CS domain and SRVCC from E-UTRAN PS to UTRAN/GERAN CS domain is deployed, the MME sends the Handover Restriction List (see TS 23.401 [9]) to eNB including the currently serving PLMN and equivalent PLMNs together with information about which PLMNs are preferred for SRVCC. The eNB selects target PLMN for SRVCC from the list based on HRL and local policy and constructs the Neighbour Cell list (NCL) based on this knowledge of the target PLMN. The selected target core network PLMN should, if possible, be the same as the one in use. + +#### 4.2.5.1 Void + +#### 4.2.5.2 Void + +#### 4.2.5.3 CS/PS domain coordination and operator selection in GERAN and UTRAN + +At combined or non-combined registration by a non-supporting UE the BSC/RNC routes the request to one of the available CN nodes. In all Attach Request/Routeing Area Update Request/Location Area Update Request messages from the BSC/RNC to CN a redirect attempt flag shall be included to indicate that the CN should either return a Reroute Command or a Reroute Complete message. If the BSC/RNC can determine that the UE is already served by a CN operator in the opposite domain, then a CN node from this operator shall be selected and the serving CN operator shall be indicated to the CN node together with an indication that the selected CN operator is already serving the UE in the opposite domain. If the BSC/RNC cannot determine a CN operator this way, the selection of CN node by the BSC/RNC is based on the NRI if provided by the UE. The RAN stores the NRI received from the UE. + +If the UE is already served by the CN node that receives the registration request and this CN node can continue to serve the UE (for example if there are no regional roaming restrictions for the target area), or if the UE is a non-roaming subscriber, or if the BSC/RNC indicated a BSC/RNC selected CN operator and that the selected CN operator is serving the UE in the opposite domain then the CN node accepts the registration attempt and completes the registration procedure. Otherwise the CN node returns IMSI and a Reroute Command message to the BSC/RNC with an indication that it is for coordination purposes. The old LAI (for the CS domain) or old RAI (for the PS domain), or an indication whether the UE is attaching shall also be included. + +Based on information received from CN node (old LAI or old RAI), UE (CS-NRI or PS-NRI, as stored in the RAN) and BSC/RNC internal configuration the BSC/RNC concludes whether: + +- (i) The UE is 'under operator coordination' i.e. if the UEs (CS-NRI, old LAI) tuple for the CS domain or (PS-NRI, old RAI) tuple for the PS domain can be used to uniquely identify one of the operators in the shared network. The old RAI/PS-NRI can be "native" (i.e. no RAT change) or "mapped" (i.e. RAT change). +- (ii) The UE is not 'under operator coordination' i.e. the UEs (CS-NRI, old LAI) tuple for the CS domain or (PS-NRI, old RAI) tuple for the PS domain cannot uniquely identify any operator in the shared network. The old RAI/PS-NRI can be "native" (i.e. no RAT change) or "mapped" (i.e. RAT change). +- (iii) The UE is attaching. + +For case (i) the BSC/RNC selects serving CN operator based on the identified operator and routes the request to the selected operator. The IMSI and the BSC/RNC selected CN operator shall be indicated to the CN. + +For case (ii) and (iii) the BSC/RNC shall for a (combined or non-combined) registration attempt in the PS domain query its connected MSCs, whether the UE is registered with any of the sharing operators in the CS domain. Similarly for a registration attempt in the CS domain the BSC/RNC shall query its connected SGSNs, whether the UE is registered at any of the sharing operators in the PS domain. For a registration attempt in the CS domain this means that the SGSNs on behalf of the BSC/RNC may be needed to query all MMEs that may hold the UEs context of the sharing operators whether the UE is registered at any of the MMEs of the sharing operators. Registration in MME but not in the CS domain can e.g. occur at cell reselection from LTE for a UE that is not SGs registered. If MMEs are not updated to support registration queries, it may not be possible to guarantee CS/PS coordination in certain scenarios. + +For case (ii) and (iii) and if the UE is found to be registered with one of the sharing operators then that operator shall be selected by the BSC/RNC and the registration message shall be forwarded to a CN node of this operator. The BSC/RNC selected CN operator shall be indicated to the CN and the BSC/RNC shall indicate that BSC/RNC selected CN operator is serving the UE in the opposite domain. + +For cases (ii) and (iii) and the UE is not found to be registered at one of the sharing operators then the BSC/RNC routes the request to one of the available CN operators. Selection of CN operator is done in the BSC/RNC by IMSI analysis, e.g. using a fixed split of IMSI ranges or IMSI hash table between operators, etc. The CN node / CN operator selection may result in that the registration is sent back to the same CN node or CN operator again. At non-combined registration CS/PS coordination is done in the BSC/RNC (without memorising IMSI information for IDLE mode UEs) by applying the same IMSI analysis for both CS and PS domains. The BSC/RNC selected CN operator shall be indicated to the CN and IMSI shall be included to the CN node. + +If a registration attempt is ongoing in the PS domain when a registration attempt starts in the CS domain then the BSC/RNC selects operator as specified below and the IMSI and the BSC/RNC selected CN operator shall be sent to the CN node: + +- If for the CS domain case (i) applies then that operator shall be selected for both domains. +- If for the CS domain case (ii) or (iii) applies then depending on: + - If for the PS domain case (i) applies then that operator shall be selected for both domains + - If for the PS domain case (ii) or (iii) applies then the BSC/RNC selects operator for both domains based on IMSI analysis + +Similar handling applies if a registration attempt is ongoing in the CS domain when a registration attempt starts in the PS domain. + +At combined registration the SGSN may indicate over Gs interface the selected CN operator that serves the subscriber. + +NOTE: Support for CS/PS domain coordination functionality as specified in this release requires support in shared CN nodes (for GWCN) and non-shared CN nodes (for MOCN) as well as in the shared RAN to achieve CS/PS coordination for UEs in the shared network. If sufficient support is not available, CS/PS coordination is performed as in pre- Release 13. + +### 4.2.6 Attach/detach handling + +To attach to the same core network operator from which it detached, a UE uses information stored in the UE (e.g. on the SIM/USIM) when the UE was detached. For a supporting UE in a shared network, the stored information indicates the core network operator it detached from (as specified in clause 4.2.4). This information enables a supporting UE to attach to the same core network operator from which it detached. For non-supporting UEs in a shared network, the stored information indicates the common PLMN. + +## 4.3 Network Name Display for Supporting UEs + +A supporting UE shows the name of the PLMN-id it has registered with. In case of a shared network, it is the PLMN-id of the chosen core network operator. The name stored in the UE for the PLMN-id is displayed except when the network indicates to the UE a name to be displayed, as already specified for non-supporting UEs. + +## 4.4 HPLMN Support + +The use of a shared VLR/SGSN/MME shall not result in service restrictions, e.g. roaming restrictions. Since the HSS and gsmSCF derives whether the subscriber roams in H- or V-PLMN from the VLR/SGSN/MME identifier, a shared VLR/SGSN/MME in a GWCN shall be allocated a separate identifier from each operator sharing that CN node, i.e. a shared VLR/SGSN/MME has multiple identifiers. The VLR/SGSN/MME identifier of the user's serving CN operator (either the one selected by a supporting UE, or, the one allocated by the network for a non-supporting UE) shall be used in signalling with the HSS and the gsmSCF. + +In the roaming scenario, the VPLMN shall ensure that any PLMN ID that is communicated to the HPLMN via any interface is that of the selected Core Network Operator for supporting UEs, or that of the allocated Core Network Operator for non-supporting UEs. An exception to this is that the HPLMN operator may specify in the inter-operator roaming/sharing agreement that for non-supporting UEs any PLMN ID that is communicated to the HPLMN is the Common PLMN ID. + +When the MME/SGSN and PGW/GGSN pertain to the same PLMN, i.e. in non-roaming scenario and in roaming local breakout scenario, the PLMN ID (as described in TS 36.300 [10] constructed to define the ECGI) shall be communicated via ECGI to the PGW, and the Common PLMN ID shall be communicated in SAI/CGI to the PGW/GGSN for both supporting and non-supporting UEs. + +## 4.5 Support of Cell Broadcast Services and Warning System + +In shared networks Cell Broadcast and Warning System services are provided via a single common CBC, which connects to GERAN/UTRAN as described in TS 23.041 [20] and connects to E-UTRAN as described in TS 23.401 [9]. The deployment and configuration of the common CBC is per agreement between the sharing operators. The sharing operators need to coordinate the broadcast services between each other, e.g. how to provide Warning System services. + +## 4.6 Support of Extended Access Barring + +In shared networks, BSC/RNC/eNodeB shall provide independent support for the barring of MSs configured for Extended Access Barring (as defined in TS 22.011 [23]) for each sharing operator. The BSC/RNC/eNodeB may initiate Extended Access Barring for a specific sharing operator when all the SGSNs/MMEs belonging to that sharing operator connected to this BSC/RNC/eNodeB request to restrict the load for UEs configured for low access priority, or if requested by O&M. Broadcast Extended Access Barring information is specified in TS 44.018 [16] for GERAN, TS 25.331 [3] for UTRAN and TS 36.331 [11] for E-UTRAN. + +## 4.7 Support of service identification for improved radio utilization for GERAN + +Service Class Indicator (SCI) for improved radio utilization for GERAN (see TS 23.060 [22]) is supported in shared network for A/Gb mode GERAN PS domain. The A/Gb mode GERAN identifies the service class associated with downlink user plane packets according to TS 23.060 [22]. When deciding whether to use or discard the SCI information, the A/Gb mode GERAN may need to take the identity of the MS's Core Network operator into account. + +# --- 5 Functional description + +The new behaviours of network nodes needed in order to describe network sharing are described. + +## 5.1 UE functions + +A supporting UE operating in Idle mode selects the core network operator and provides the PLMN-id of this operator to the network for routing purposes and to indicate which of the core network operators is selected. A supporting GERAN UE provides PLMN-index when establishing a connection with the MSC, and, when sending GPRS LLC frames with a non-local TLLI. + +A supporting GERAN UE, upon completion of a CS or PS handover, uses the PLMN index received during the CS handover and PS handover procedure to indicate the selected PLMN in the subsequent RAU in connected mode if the conditions for performing a normal RAU are met, see TS 24.008, when sending GPRS LLC frames with a non-local TLLI. Normal RAU following a CS handover is performed if the UE and the network support DTM and the conditions for RAU are met whereas a RAU following a PS handover is performed if the conditions for normal RAU are met. + +## 5.2 RNC functions + +Network sharing information, i.e. available core network operators in the shared network, shall be transmitted in broadcast system information. + +If system information relating to NAS is transmitted to a UE in dedicated signalling, the RNC sends information for both supporting and non-supporting UEs and the UE shall select the appropriate information to use. + +The RNC shall indicate the UE selected core network operator to the CN for supporting UEs when transferring initial layer 3 signalling. The selected CN operator is (i) indicated by the UE in RRC signalling or (ii) known implicitly from an already existing signalling connection. For non-supporting UEs, the RNC selected core network operator shall, if available, be indicated by the RNC to the CN. RNC selection of core network operator is described in clause 4.2.5.3. + +In case of relocation to a shared network: + +- the source RNC determines a core network operator to be used in the target network, including the selection of PLMN(s) to support SRVCC functionality from CS domain to PS, based on available shared networks access control information, current PLMN in use, Anchor PLMN, or similar information present in the node, the source RNC shall at relocation indicate that selected core network operator to the source core network node as part of + +the TAI/RAI sent in Target ID in the Relocation Required message. The selected target core network operator should be the same as the one in use. If the source core network operator is not supported in the target cell the RNC selects the target PLMN based on either (i) pre-configured information in the RNC, or (ii) the SNA (Shared Network Area) Access Information IE (see TS 25.413 [13]) provided by the SGSN. When the RNC triggers the enhanced relocation and selects a new PLMN, the selected PLMN is indicated to the SGSN during the following RA update procedure. + +- In order to support SRVCC from CS to PS, the source RNC informs the target RNC/BSC of the Anchor PLMN identity. +- The target RNC may need to know whether or not the UE supports UTRAN network sharing. + +The behaviour of the RNC in relation to CS/PS coordination for non-supporting UEs is described in clause 4.2.5.3. + +NOTE: For PS-to-CS SRVCC, any SRVCC specific PLMN information should be pre-configured in the RNC. + +## 5.2a eNodeB functions + +Network sharing information, i.e. available core network operators in the shared network, shall be transmitted in broadcast system information. + +The eNodeB shall indicate the selected core network operator when transferring initial layer 3 signalling. The eNodeB uses the selected core network information (provided by the UE at RRC establishment, or, provided by the MME/source eNodeB at S1/X2 handover) to select target cells for future handovers (and radio resources in general) appropriately. + +In the case of handover to a shared network: + +- the source eNodeB determines a core network operator to be used in the target network based on current PLMN in use, or other information present in the eNodeB, the source eNodeB shall at handover indicate that selected core network operator to the MME as part of the TAI/RAI sent in the HO required message. The selected target core network operator should be the same as the one in use. This is accomplished by not changing the serving PLMN if the PLMN in use is supported in the target cell. If the PLMN in use is not supported in the target cell the eNB selects the target PLMN based on either (i) pre-configured information in the eNB, or (ii) the Equivalent PLMNs list (see TS 36.413 [14]) provided by the MME. +- when multiple PLMNs are available for CS domain to support CS Fallback functionality, the source eNodeB determines a core network operator to be used in the target GERAN/UTRAN network based on the allocated LAI provided by the MME as specified in TS 23.272 [15]. The source eNodeB shall at handover indicate that selected core network operator to the MME as part of the Target ID sent in the HO required message. If the selected PLMN for CS domain is not supported in the target cell the eNodeB selects the target PLMN based on either (i) pre-configured information in the eNodeB, or (ii) the Equivalent PLMNs list (see TS 36.413 [14]) provided by the MME. +- when multiple PLMNs are available for CS domain to support SRVCC functionality, the source eNodeB determines a core network operator to be used in the target GERAN/UTRAN network. If the currently serving PLMN is not supported in the target cell, the eNodeB selects the target PLMN based local configured information in the eNodeB along with the information provided by the MME in HRL (see TS 36.413 [14]). The HRL provides the currently serving PLMN and equivalent PLMNs together with information about which PLMNs are preferred for SRVCC target cell selection. The source eNodeB shall at SRVCC handover indicate the selected core network operator to the MME as part of the Target ID sent in the HO required message. +- the target eNodeB uses the selected core network information to select target cells for future handovers appropriately. + +In the case of dual connectivity (as described in TS 36.300 [10]): + +- the Master eNodeB uses the selected core network information to select any Secondary Cell Group appropriately (e.g. to respect network sharing agreements). + +## 5.2b BSC functions + +Network sharing information, i.e. available core network operators in the shared network, shall be transmitted in broadcast system information. + +If system information is transmitted to a supporting UE in dedicated signalling e.g. to support handover to other RATs, the BSC shall indicate the PLMN-id of the core network operator towards which the UE already has a signalling connection (if a PLMN-id is included in the signalling). If the UE is non-supporting, the BSC shall indicate the common PLMN (if a PLMN-id identity is included in the signalling). + +The BSC shall indicate the selected core network operator to the CN for supporting UEs. The selected CN operator is: + +- i) indicated by the UE to the BSC as follows: + - for the CS domain, in the Initial L3 message, a supporting UE shall send the PLMN Index that corresponds to the position of the chosen PLMN in the broadcast system information, as part of the Initial L3 message. The BSC shall then derive the PLMN-id chosen by the UE from the indicated PLMN Index, select the corresponding CN operator and inform the MSC of the chosen PLMN-id; + - for the PS domain, when the UE has a non-local TLLI, a supporting UE shall send the PLMN Index that corresponds to the position of the chosen PLMN in the broadcast system information, as part of the AS signalling. The BSC shall then derive the PLMN-id chosen by the UE from the indicated PLMN Index, select the corresponding CN operator and inform the SGSN of the chosen PLMN-id; + +or: + +- ii) known implicitly from an already existing signalling connection. + +For non-supporting UEs, the BSC selected core network operator shall, if available, be indicated by the BSC to the CN. + +In the PS domain, when the UE has a local TLLI: + +- for MOCN, the BSC uses the NRI bits from within the TLLI to derive the selected CN operator; +- for GWCN, the SGSN passes the selected CN operator identity with the downlink user data/signalling. + +For handover to a shared network from GERAN: + +- the source BSC determines a core network operator to be used in the target network, including the selection of PLMN(s) to support SRVCC functionality from CS domain to PS, based on current PLMN in use, Anchor PLMN, or other information present in the BSC. The selected target core network operator should be the same as the one in use. If the source core network operator is not supported in the target cell the BSC selects the target PLMN based on pre-configured information in the BSC. +- the source BSC shall indicate the target core network operator PLMN ID to the source core network node as part of the TAI/RAI sent in the Target Cell Identifier IE/Target RNC Identifier IE/Target eNodeB Identifier IE in the PS-Handover-Required message (TS 48.018 [24]) and in the LAI sent in the Cell Identifier List IE in the Handover Required message (TS 48.008 [25]). +- In order to support SRVCC for CS to PS, the source BSC informs the target RNC/BSC of the Anchor PLMN identity. + +For handover to a GERAN shared network: + +- The target BSS needs to know whether or not the UE supports GERAN network sharing. +- the source RAN determines a core network operator to be used in the target network and indicates the selected target core network operator PLMN ID to the source core network node. The target MSC/SGSN indicates the selected target core network operator to target BSC. +- At CS handover the target BSC (BSS-B) shall, for a GERAN supporting UE, provide PLMN index information corresponding to the selected target PLMN-id via the source RAN. When the UE arrives in the target cell the target BSC shall indicate the RAI corresponding to the selected PLMN. +- At PS handover the target BSC (BSS-B) shall, for a GERAN supporting UE, provide PLMN index information corresponding to the selected target PLMN-id via the source RAN. The target BSC shall also via the source RAN indicate the RAI corresponding to the selected PLMN. +- At normal RAU in connected mode after completing a handover, the target BSC is informed of the PLMN index corresponding to the selected target PLMN when the UE appears in the target access. + +In all other non handover signalling from the GERAN to the MSC/SGSN, unless specified differently by stage 3 specifications, any PLMN ID sent is the Common PLMN ID. In signalling from the Core Network to the GERAN, the BSS shall accept signalling that uses any of the PLMN IDs that share the cell. + +The behaviour of the BSC in relation to CS/PS coordination for non-supporting UEs is described in clause 4.2.5.3. + +## 5.3 MSC functions + +When a UE accesses an MSC the first time, i.e. when there is no VLR entry for this UE, the MSC retrieves the IMSI from another MSC/VLR or from the UE. For GWCN, the MSC determines a serving CN operator based on the UE Selected operator (PLMN) indicated by the RAN, or, for a non-supporting UE, based on the RAN Selected CN operator (PLMN). The MSC/VLR shall also store the identity of the serving core network operator. + +In the case of a MOCN configuration, an MSC may not be able to provide service to the UE. The UE may then have to be redirected to a MSC of another core network operator. The MSC/VLR that finally serves the UE assigns a NRI to the UE. This will allow the RAN to route any subsequent UE accesses to the serving MSC/VLR. + +The behaviour of the MSC in relation to CS/PS coordination for non-supporting UEs is described in clause 4.2.5.3. + +For supporting UEs, i.e. when a UE selected core network operator has been indicated to the MSC by the RNC/BSC, the MSC indicates the selected core network operator PLMN-id in the LAI signalled to the UE in dedicated signalling. + +For sharing scenarios with both E-UTRAN and GERAN/UTRAN access, where the network also applies idle-mode signalling reduction (see TS 23.401 [9]), the contents of the SNA Access Information IE (see TS 25.413 [13]) provided by the MSC to the RNC for a specific UE guides the target PLMN selection if the UE's registered PLMN is not available in the target cell. The SNA Access Information IE should be configured such that for any target cell there is only one PLMN-ID that can be selected for the cell. + +Also, for the above scenario, in the routing areas and tracking areas between which ISR may be activated the "equivalent PLMNs" list provided by the SGSN, MSC and MME to a UE (see TS 24.008 [7]) should result in a single consistent "equivalent PLMNs" list stored by the UE. The single "equivalent PLMNs" list applies to all the UE's registered routing areas, location areas and tracking areas. + +In case of relocation to a GWCN or a MOCN: + +- There is no functionality in the source MSC to select a target core network operator or to modify the target core network operator selected by the RNC/BSC. +- For handover to a shared UTRAN the source MSC shall forward the selected core network operator chosen by the source RNC/BSC to the target MSC, which relays this information unchanged to the target RNC so that the appropriate PLMN-id can be signalled to the UE in dedicated system information signalling, as described in clause 5.2. +- For handover to a shared GERAN the source MSC shall forward the PLMN-ID selected by the source RAN to the target MSC. Target MSC sends information of selected operator to the target BSC. +- For SRVCC from E-UTRAN PS to UTRAN/GERAN CS domain, in case of GWCN configuration, the MSC selects the target PLMN based on the indication of the selected target PLMN provided by the MME/SGSN in the PS-to-CS handover command. The MSC receives the Anchor PLMN from the MME/SGSN and forwards that information to the target BSC/RNC. + +For SRVCC from UTRAN/GERAN CS domain to E-UTRAN/HSPA PS, the MSC selects the MME based on selected target PLMN provided by the RNC/BSC in handover required message and forwards the selected target PLMN to MME in the CS to PS handover request. + +In signalling to the HSS, the MSC shall ensure that any PLMN ID that is sent is the ID of the selected Core Network Operator for supporting UEs, or that of the allocated Core Network Operator for non-supporting UEs (unless the exception to send the Common PLMN ID for a non-supporting UE (see clause 4.4) is in use with that HPLMN). + +## 5.4 SGSN functions + +When a UE accesses an SGSN the first time, i.e. when the UE is not yet known by the SGSN the SGSN retrieves the IMSI from another SGSN/MME or from the UE. For GWCN, the SGSN determines a serving CN operator based on the + +Selected PLMN indicated by the RAN, or, for a non-supporting UE, based on the RAN Selected CN operator (PLMN). The SGSN shall store the identity of the serving core network operator. + +In the case of a MOCN configuration, a SGSN may not be able to provide service to the UE. The UE may then have to be redirected to a SGSN of another core network operator. The SGSN that finally serves the UE assigns a NRI to the UE. This will allow the RAN to route any subsequent UE accesses to the serving SGSN. + +The behaviour of the SGSN in relation to CS/PS coordination for non-supporting UEs is described in clause 4.2.5.3. + +For supporting UEs, i.e. when a UE selected core network operator has been indicated to the SGSN by the RNC/BSC, the SGSN indicates the selected core network operator PLMN-id in the LAI/RAI signalled to the UE in dedicated signalling. + +For sharing scenarios with both E-UTRAN and GERAN/UTRAN access, where the network also applies idle-mode signalling reduction (see TS 23.401 [9]), the contents of the SNA Access Information IE (see TS 25.413 [13]) provided by the SGSN to the RNC for a specific UE guides the target PLMN selection if the UE's registered PLMN is not available in the target cell. The SNA Access Information IE should be configured such that for any target cell there is only one PLMN-ID that can be selected for the cell. + +Also, for the above scenario, in the routing areas and tracking areas between which ISR may be activated the "equivalent PLMNs" list provided by the SGSN, MSC and MME to a UE (see TS 24.008 [7]) should result in a single consistent "equivalent PLMNs" list stored by the UE. The single "equivalent PLMNs" list applies to all the UE's registered routing areas, location areas and tracking areas. + +At relocation/handover to a GWCN or a MOCN: + +- There is no functionality in the source SGSN to select a target core network operator or to modify the target core network operator selected by the RNC/BSC. Instead, the source SGSN uses the selected PLMN received from the RNC/BSC to determine the target core network operator. The source SGSN shall forward the selected core network operator chosen by the source RNC/BSC to the target SGSN/MME. +- For handover to a shared UTRAN the target SGSN indicates the selected core network operator chosen by the source RNC/BSC/eNodeB to the target RNC so that the appropriate PLMN-id can be signalled to the UE in dedicated system information signalling, as described in clause 5.2. +- For handover to a shared GERAN the source SGSN/MME shall forward the PLMN-ID selected by the source RAN to the target SGSN. Target SGSN sends information of selected operator to the target BSC. +- For SRVCC from UTRAN PS to UTRAN/GERAN CS domain, the SGSN selects the MSC based on the selected target PLMN indicated by the RNC. The SGSN includes the indication of the selected target PLMN in the target CGI/RNC ID and Anchor PLMN in the SRVCC PS-to-CS Request sent to the MSC (see TS 29.280 [21]). + +In signalling to the GGSN/S-GW/P-GW and HSS, the SGSN shall ensure that any PLMN ID that is sent is the ID of the selected Core Network Operator for supporting UEs, or that of the allocated Core Network Operator for non-supporting UEs (unless the exception to send the Common PLMN ID for a non-supporting UE (see clause 4.4) is in use with that HPLMN). + +## 5.5 MME functions + +When a UE accesses an MME for the first time, i.e. when the UE is not yet known by the MME, the MME verifies whether the UE is permitted to access the selected PLMN. For that purpose the MME retrieves the IMSI from another MME/SGSN or from the UE. The MME shall store the identity of the selected core network operator. + +The MME indicates the selected core network operator PLMN-id to the UE in the GUTI. + +For sharing scenarios with both E-UTRAN and GERAN/UTRAN access, where the network also applies idle-mode signalling reduction (see TS 23.401 [9]), the PLMN IDs included in the equivalent PLMN list (as defined in TS 24.008 [7]) provided by the MME to the eNB guides the target PLMN selection if the UE's registered PLMN is not available in the target cell. The equivalent PLMN list should be configured such that for any target cell there is only one PLMN-ID that can be selected for the cell. + +Also, for the above scenario, in the routing areas and tracking areas between which ISR may be activated the "equivalent PLMNs" list provided by the SGSN, MSC and MME to a UE (see TS 24.008 [7]) should result in a single consistent "equivalent PLMNs" list stored by the UE. The single "equivalent PLMNs" list applies to all the UE's registered routing areas, location areas and tracking areas. + +For sharing scenarios with both E-UTRAN and GERAN/UTRAN access, when multiple PLMNs are available for CS domain to support CS Fallback functionality, the MME provides the allocated LAI including the selected PLMN ID for CS domain along with "CS Fallback indicator" to the eNodeB as specified in TS 23.272 [15], to guide the selection of the target GERAN/UTRAN network. + +If the operator-configured preferred target RAT for CS Fallback is a shared RAN not offering the broadcast of available Core Network operators for selection by the UE, the MME shall always select the common PLMN broadcasted in the shared RAN as the selected PLMN-id for the CS domain. + +If the operator-configured preferred target RAT for CS Fallback is a shared RAN offering the broadcast of available Core Network operators for selection by the UE, the MME shall take into account the UE's capability of supporting network sharing in the preferred target RAT when selecting the PLMN for the CS domain for CS Fallback. For GERAN network sharing, the UE signals its capability of GERAN network sharing support explicitly to the MME. If the UE is a network-sharing non-supporting UE with respect to the preferred target RAT, a common PLMN-id shall be selected, while if the UE is a network-sharing supporting UE with respect to the preferred target RAT, one of the PLMN-IDs in the broadcasted multiple PLMN-id list of the preferred target shared RAT shall be selected as the PLMN-id for the CS domain. + +The selected PLMN-id for the CS domain shall be included the allocated LAI sent to the MSC/VLR as defined in TS 23.272 [15]. + +If the shared network is in GWCN configuration, MME sends the 'selected CS domain operator' as indicated in clause 4.2.5.a. + +The list of PLMN-ID(s) included in the handover restriction list (as defined in TS 36.413 [14]), if provided by the MME to the eNB for the target PLMN selection, shall be configured such that for any target GERAN/UTRAN cell, only PLMN-ID(s) associated with the same CN operator as the one that the UE has registered to in the CS domain can be selected by the eNB when one of the following conditions apply: + +- the preferred RAT of the registered network is shared network not offering the broadcast of available Core Network operators for selection by the UE, or, +- the RAT preference for the UE is GERAN and the allocated LAI belongs to a shared GERAN and the UE is a GERAN network-sharing non-supporting UE. + +The list of PLMN-ID(s) included in the equivalent PLMN list sent to the UE shall be configured to include the list of PLMN IDs in the handover restriction list. + +NOTE: When performing CS Fallback to GERAN/UTRAN cell, if the PLMN-ID(s) in the equivalent PLMN list contains a CS CN operator(s) PLMN different from the registered CS PLMN, then the UE may possibly select a CS CN operator it has not registered to. + +At handover/relocation to a GWCN or a MOCN: + +- The source MME uses the TAI/RAI information supplied by the eNodeB to select the target MME/SGSN. There is no additional functionality in the source MME to select a target core network operator or to modify the target core network operator selected by the eNodeB. Instead, the source MME uses the selected PLMN received from the eNodeB to determine the target core network operator. The source MME shall forward the selected target core network operator chosen by the source eNodeB to the target MME/SGSN. +- The target MME indicates the selected target core network operator chosen by the source eNodeB/RNC/BSC to the target eNodeB so that the eNodeB can select target cells for future handovers appropriately. Subsequent Tracking Area Update signalling is used to update the UE about any change of core network operator. +- At SRVCC from E-UTRAN PS to UTRAN/GERAN CS domain, the MME selects the MSC based on the selected target PLMN indicated by the eNodeB. The MME includes the indication of the selected target PLMN in the target CGI/RNC ID and Anchor PLMN in the PS-to-CS Request sent to the MSC (see TS 29.280 [21]). + +In signalling to the S-GW/P-GW and HSS, the MME shall ensure that any PLMN ID that is sent is the ID of the selected Core Network Operator. + +The behaviour of the MME in relation to CS/PS coordination in GERAN and UTRAN for non-supporting UEs is described in clause 4.2.5.3. + +# 6 Charging and accounting aspects + +To support inter-operator accounting in a shared network, it shall be possible to distinguish the share of usage of the shared core network node(s) between the sharing partners. The identity of the serving core network operator (i.e. the one selected by a supporting UE in a network broadcasting a multiple PLMN-id list, or, the one allocated by the network for a non-supporting UE in a network broadcasting a multiple PLMN-id list, or, the one allocated for any UE in a shared network only broadcasting a common PLMN) and whether the core network operator was selected by a supporting UE or allocated by the network to a UE shall be included in MSC, SGSN, Serving GW and GGSN/PDN GW CDR types as specified in TS 32.250 [5] (CS) and TS 32.251 [6] (GPRS/EPS). For handover scenarios, it is up to operator configuration whether the core network operator shall be indicated as selected or allocated to a UE in the CS domain CDR. In CSFB scenario, the core network operator is allocated by the network as specified in clause 4.2.5a, but the indication in the CS domain CDR is up to operator configuration. + +As specified in clause 4.4, for online charging, the gsmSCF can use the identifier of the MSC/SGSN to determine the operator selected by a supporting UE or the operator allocated to a UE. The MSC/SGSN shall inform gsmSCF as to whether the UE selected, or the network allocated, the serving operator on that RAT. + +Whether the Core Network Operator was selected by a supporting UE or allocated by the network to the UE shall be communicated to the Serving GW and the GGSN/PDN GW and be included in MSC, SGSN, Serving GW and GGSN/PDN GW CDR types as specified in TS 32.250 [5] (CS) and TS 32.251 [6] (GPRS/EPS). + +# 7 Example signalling flows + +## 7.1 Network selection + +Signalling flows for manual and automatic network selection in a shared network architecture for successful and unsuccessful registration attempts are presented. + +### 7.1.2 Non-supporting UEs in a GWCN configuration + +This example shows network selection for a non-supporting UE in a shared UTRAN/GERAN network. The UE is not a subscriber of any of the sharing operators and is under operator coordination. The UE is not coming from E-UTRAN i.e. the UE is not registered in any old MME. The UE is not served by the shared SGSN nor by the shared MSC. After the first registration attempted the operator accepts the UE after CS/PS coordination. + +![Sequence diagram illustrating network selection for a non-supporting UE in a shared UTRAN/GERAN network. The diagram shows interactions between a Shared SGSN/shared MSC, a RAN, and a Non-supporting UE. The process starts with System information from RAN to UE. The UE responds that it cannot decode network sharing information. The UE then performs network selection, identifying a Common PLMN as a candidate. The UE sends a 4a. LAU/RAU/ATTACH REQUEST to the RAN. The RAN forwards this to the Shared SGSN/shared MSC. The Shared SGSN/shared MSC sends a 4b. Reroute Command back to the RAN. The RAN concludes that the UE is moving within an operator coordinated area (4c. LAU/RAU REQUEST) or queries CN nodes in the opposite domain (4d. ATTACH REQUEST). The CN Node determines whether the UE is allowed to attach (5). Finally, the Shared SGSN/shared MSC sends a 6. LAU/RAU/ATTACH ACCEPT to the RAN, which then reaches the UE. Conditional steps 4c and 4d are grouped under 'If RAU/LAU procedure' and 'If ATTACH procedure' respectively.](cd141897aa368dbbaa398ace230cdd85_img.jpg) + +``` + +sequenceDiagram + participant UE as Non-supporting UE + participant RAN + participant CN as Shared SGSN/shared MSC + + Note right of UE: 2. UE cannot decode network sharing information in system broadcast information. + Note right of UE: 3. Network selection (Common PLMN is candidate) + + RAN->>UE: 1. System information + UE-->>RAN: 4a. LAU/RAU/ATTACH REQUEST + RAN->>CN: 4a. LAU/RAU/ATTACH REQUEST + CN-->>RAN: 4b. Reroute Command + Note right of RAN: 4c. RAN concludes the UE is moving within an operator coordinated area + Note right of RAN: 4d. RAN queries the CN nodes in opposite domain, see clause 7.1.6 + RAN-->>CN: 4c. LAU/RAU REQUEST + RAN-->>CN: 4d. ATTACH REQUEST + Note left of CN: 5. CN Node determines whether the UE is allowed to attach + CN-->>RAN: 6. LAU/RAU/ATTACH ACCEPT + RAN-->>UE: 6. LAU/RAU/ATTACH ACCEPT + + Note right of UE: If RAU/LAU procedure + Note right of UE: If ATTACH procedure + +``` + +Sequence diagram illustrating network selection for a non-supporting UE in a shared UTRAN/GERAN network. The diagram shows interactions between a Shared SGSN/shared MSC, a RAN, and a Non-supporting UE. The process starts with System information from RAN to UE. The UE responds that it cannot decode network sharing information. The UE then performs network selection, identifying a Common PLMN as a candidate. The UE sends a 4a. LAU/RAU/ATTACH REQUEST to the RAN. The RAN forwards this to the Shared SGSN/shared MSC. The Shared SGSN/shared MSC sends a 4b. Reroute Command back to the RAN. The RAN concludes that the UE is moving within an operator coordinated area (4c. LAU/RAU REQUEST) or queries CN nodes in the opposite domain (4d. ATTACH REQUEST). The CN Node determines whether the UE is allowed to attach (5). Finally, the Shared SGSN/shared MSC sends a 6. LAU/RAU/ATTACH ACCEPT to the RAN, which then reaches the UE. Conditional steps 4c and 4d are grouped under 'If RAU/LAU procedure' and 'If ATTACH procedure' respectively. + +Figure 3: Network selection for a non-supporting UE in a shared UTRAN/GERAN network + +1. The UE reads the broadcast system information in the shared RAN. +2. A non-supporting UE cannot decode the shared network information in the broadcast system information. The common PLMN is the only candidate to be considered together with other PLMNs for network selection. +3. The UE performs network selection among available PLMNs. +- 4a. The UE sends an ATTACH REQUEST/ROUTEING AREA UPDATE/LOCATION AREA UPDATE message to the network. The RAN selects CN node based on NRI (valid or invalid) if present or by random selection. A *redirect attempt flag* is included in the signalling from RAN to Core Network. The signalling from the RAN to the Core Network enables the Core Network to determine that the UE did not select a Core Network operator. The RAN stores the NRI received from the UE. +- 4b. A *Reroute Command* message is sent back to the RAN node with an indication that it is for coordination purposes. The *Reroute Command* message includes the LAU/RAU /ATTACH REJECT message and the original ATTACH REQUEST/ROUTING AREA UPDATE/LOCATION AREA UPDATE message received from the UE. Included is also IMSI and old LAI (for the CS domain) or old RAI (for the PS domain), or an indication whether the UE is attaching. +- 4c. At ROUTEING AREA UPDATE/LOCATION AREA UPDATE the RAN node concludes that the UE is roaming under operator coordination and sends a ROUTEING AREA UPDATE/LOCATION AREA UPDATE to the Core Network. The CN operator selected by the RAN is included in the signalling from RAN to Core Network. IMSI and the redirect attempt flag shall be included. +- 4d. At ATTACH REQUEST in PS domain the RAN node queries the MSCs in the CS domain whether the UE (IMSI) is registered at any of the sharing operators in the CS domain. At ATTACH REQUEST in CS domain the RAN node queries the SGSNs in the PS domain whether the UE (IMSI) is registered at any of the sharing operators in the PS domain. For PS domain the SGSNs may need to query all MMEs that may hold the UEs context, refer to sub clause 7.1.6. + +In this example the UE is yet neither registered in the CS domain nor in the PS domain. Based on IMSI analysis the RAN node selects an operator. The RAN node sends a ATTACH REQUEST/ to the Core Network. The CN operator selected by the RAN is included in the signalling from RAN to Core Network. IMSI and the *redirect attempt flag* shall be included. + +5. The shared SGSN determines whether the UE is allowed to attach. +6. The shared SGSN sends the appropriate ACCEPT message back to the UE. + +### 7.1.3 Supporting UEs in a GWCN configuration + +This example shows network selection for a supporting UE in a shared E-UTRAN/UTRAN/GERAN network. + +![Sequence diagram illustrating network selection for a supporting UE in a shared E-UTRAN/UTRAN/GERAN network. The diagram shows three main entities: Shared SGSN / shared MME / shared MSC, RAN, and Supporting UE. The sequence of messages is: 1. System information from RAN to UE; 2. UE decodes network sharing information in system broadcast information (internal UE process); 3. Network selection (internal UE process); 4. LAU/RAU/ATTACH/TAU REQUEST from UE to RAN; 5. CN node determines whether the UE is allowed to attach (internal SGSN process); 6. LAU/RAU/ATTACH/TAU ACCEPT/REJECT from RAN to UE.](75e4b78ee25f885d73120e3066a5253e_img.jpg) + +``` + +sequenceDiagram + participant UE as Supporting UE + participant RAN as RAN + participant CN as Shared SGSN / shared MME / shared MSC + + Note right of UE: 2. UE decodes network sharing information in system broadcast information. + Note right of UE: 3. Network selection + + RAN->>UE: 1. System information + UE->>RAN: 4. LAU/RAU/ATTACH/TAU REQUEST + Note left of CN: 5. CN node determines whether the UE is allowed to attach. + CN->>RAN: 6. LAU/RAU/ATTACH/TAU ACCEPT/REJECT + RAN->>UE: 6. LAU/RAU/ATTACH/TAU ACCEPT/REJECT + +``` + +Sequence diagram illustrating network selection for a supporting UE in a shared E-UTRAN/UTRAN/GERAN network. The diagram shows three main entities: Shared SGSN / shared MME / shared MSC, RAN, and Supporting UE. The sequence of messages is: 1. System information from RAN to UE; 2. UE decodes network sharing information in system broadcast information (internal UE process); 3. Network selection (internal UE process); 4. LAU/RAU/ATTACH/TAU REQUEST from UE to RAN; 5. CN node determines whether the UE is allowed to attach (internal SGSN process); 6. LAU/RAU/ATTACH/TAU ACCEPT/REJECT from RAN to UE. + +**Figure 4: Network selection for a supporting UE in a shared E-UTRAN/UTRAN/GERAN network** + +1. The UE reads the broadcast system information in the shared RAN. + +2. A supporting UE decodes the shared network information and supplies the available core network operator PLMN-ids as candidates to the PLMN selection procedure. Only PLMNs in the Multiple PLMN ID List are candidates for network selection. +3. The UE performs network selection among available PLMNs. +4. The UE sends an ATTACH/ROUTEING AREA UPDATE/TRACKING AREA UPDATE/LOCATION AREA UPDATE REQUEST message to the network indicating, to the RAN, the chosen core network operator. The RAN converts the core network 'indicator' into the actual selected PLMN identity and sends this with the ATTACH/ROUTEING AREA UPDATE/TRACKING AREA UPDATE/LOCATION AREA UPDATE REQUEST to the core network. +5. The shared SGSN determines whether the UE is allowed to attach. +6. The shared SGSN sends the appropriate ACCEPT/REJECT message back to the UE. + +### 7.1.4 Non-supporting UEs in a MOCN configuration + +#### 7.1.4.1 UTRAN based MOCN configuration + +An example of an information flow for redirection in UTRAN is shown below. + +In this example an attach request from a non-supporting UE is directed to three different CN operators. The UE is not a subscriber of any of the sharing operators. The UE is not served by any shared SGSN nor by any shared MSC. The UE is furthermore not under operator coordination. The first rejects since it has no roaming agreement with the subscribers Home PLMN or rejects due to CS/PS coordination required. The second rejects because of a roaming restriction found in HLR. The third CN operator accepts and completes the attach request. The different "MSC/SGSNs" in the example below shall be seen as different CN operators. One specific CN operator may also have several pooled MSCs/SGSNs connected to the RNC if Iu-flex is used. + +![Sequence diagram showing information flow for redirection in UTRAN. Lifelines: UE, RNC, MSC/SGSN A, MSC/SGSN B, MSC/SGSN C, HLR. The process involves RRC connection establishment, initial direct transfer, identity request/response, roaming checks, reroute commands, and final attach complete messages.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC + participant MSC_A as MSC/SGSN A + participant MSC_B as MSC/SGSN B + participant MSC_C as MSC/SGSN C + participant HLR + + Note left of UE: 1. RRC Connection Establishment + UE->>RNC: 2. Initial Direct Transfer + RNC->>MSC_A: 3. Initial UE (Attach request, redirect attempt flag) + Note right of MSC_A: Roaming not allowed for HPLMN of IMSI / +Roaming allowed but CS/PS coordination required + MSC_A->>UE: 4. Identity Req + UE->>MSC_A: 4. Identity Resp (IMSI) + MSC_A->>RNC: 5a. Reroute Command + Note left of RNC: 5b.RAN queries the CN nodes in the opposite domain, see clause 7.1.6 + RNC->>MSC_C: 6. Initial UE (Attach request, redirect attempt flag, IMSI, ...) + MSC_C->>HLR: 7. Authentication & Ciphering + HLR->>MSC_C: 8. Update Location / Insert Subscr. Data + Note right of MSC_C: Roaming not allowed for HPLMN of IMSI + MSC_C->>RNC: 9. Reroute Command + RNC->>MSC_C: 10. Initial UE (Attach request, redirect attempt flag, IMSI, ...) + MSC_C->>HLR: 11. Authentication & Ciphering + HLR->>MSC_C: 12. Update Loc./ Cancel Loc./ Insert Subscr. Data + MSC_C->>RNC: 13. Reroute Complete ( Attach accept, ... ) + RNC->>UE: 14. Direct Transfer( Attach accept ) + UE->>MSC_C: 15. Attach Complete + +``` + +Sequence diagram showing information flow for redirection in UTRAN. Lifelines: UE, RNC, MSC/SGSN A, MSC/SGSN B, MSC/SGSN C, HLR. The process involves RRC connection establishment, initial direct transfer, identity request/response, roaming checks, reroute commands, and final attach complete messages. + +Figure 5: Information flow for redirection in UTRAN + +- 1) The RRC connection is established. +- 2) RNC receives an Initial Direct Transfer from an UE. The RNC is configured to work in a Shared RAN MOCN, and therefore it forwards the NAS message in an Initial UE message with an additional *redirect attempt flag* set. The flag indicates that the MSC/SGSN shall respond to the attach request with a *Reroute Command* or *Reroute Complete* IE in the Direct Transfer message. Selection of CN node is based on NRI (valid or invalid) if present in IDNNS or by random selection. + +A *redirect attempt flag* could also simply be the fact that the Initial UE message does not include any UE selected PLMN-ID, which a supporting UE would include. Redirect is never done for supporting UEs. +- 3) The MSC/SGSN receives the Initial UE with the *redirect attempt flag* set. It then knows it shall answer with a *Reroute Command* or *Reroute Complete* IE in the Direct Transfer message. +- 4) The MSC/SGSN needs the IMSI of the UE. It is retrieved either from old MSC / old SGSN or from the UE as in this example. By comparing the IMSI with the roaming agreements of the CN operator, the MSC/SGSN discovers that roaming is not allowed or that roaming is allowed but CS/PS coordination required. Attach procedure is aborted. +- 5a) A message is sent back to the RNC with two NAS messages, the attach reject message and the original attach request message received from the UE (alternatively the original NAS message may be stored in the RNC). The IMSI and an indication that the UE is attaching is also included in the message, plus a reject cause code to the RNC. The *Reroute Command* IE is in the Direct Transfer message. +- 5b) The RAN node concludes that UE is attaching. For attach in PS domain the RAN node queries the MSCs in the CS domain whether the UE (IMSI) is served by any of the sharing operators in the CS domain. For attach in CS + +domain the RAN node queries the SGSNs in the PS domain whether the UE (IMSI) is served by any of the sharing operators in the PS domain. For PS domain the SGSNs may need to query all MMEs that may hold the UEs context, refer to clause 7.1.6. + +In this example the UE is yet neither served by a node in the CS domain nor in the PS domain. The signalling connection between RNC and MSC/SGSN A is released. Based on deterministic IMSI analysis the RNC selects a MSC/SGSN in the next step. If reject was due to CS/PS coordination required then the same operator may be selected again. If reject was not due to CS/PS coordination required then the already tried MSC/SGSNs is stored in the RNC during the redirect procedure so that the same node is not selected twice. + +- 6) The RNC sends a new Initial UE to the next selected MSC/SGSN with the original NAS attach request message (in case of CS/PS coordination the Initial UE may also be sent back to the first MSC/SGSN depending on the outcome of the coordination). Redirect attempt flag is set and IMSI shall also be included to avoid a second IMSI retrieval from UE or old MSC/SGSN and to indicate that PS/CS domain coordination has been done in RNC. The CN operator selected by the RAN is included in the signalling from RAN to Core Network The MSC/SGSN receiving the message starts its attach procedure. +- 7) MSC/SGSN B does in general support roaming for the HPLMN of the IMSI and hence authentication is done and RAN ciphering is established. +- 8) MSC/SGSN B updates the HLR and receives subscriber data from HLR. +- 9) The subscription data do not allow roaming (e.g. regional or 3G). MSC/SGSN B sends a Reroute Command message including the attach reject message, a reject cause code, the original attach request message and the N(SD) (for MSC only). IMSI is included in Reroute Command message only if it was not included in the Initial UE received by the MSC/SGSN. + +The signalling connection between the RNC and the MSC/SGSN B is released. The RNC then selects a new operator and a new MSC/SGSN based on deterministic IMSI analysis as in step 5b. + +- 10) The MSC/SGSN C receives an Initial UE (with the original NAS attach request message) with the redirect attempt flag is set, an IMSI, and N(SD) (if MSC). The MSC/SGSN C also receives the CN operator selected by the RAN. The MSC/SGSN C starts the attach procedure and uses provided information (IMSI and N(SD)). +- 11) MSC/SGSN C does in general support roaming for the HPLMN of the IMSI and hence authentication is done and RAN ciphering is established. +- 12) MSC/SGSN C updates the HLR and receives subscriber data from HLR. Subscriber data allows roaming, and the MSC/SGSN C completes the attach procedure. This includes the assignment of a new TMSI/P-TMSI with an NRI that can be used by RNC to route subsequent signalling between UE and correct MSC/SGSN (Iu-flex functionality). The Update Location sent to HLR also triggers a Cancel Location sent to the MSC/SGSN B. +- 13) A *Reroute Complete* IE in the Direct Transfer message with the NAS Attach accept message is sent to RNC. By this, the RNC knows that the redirect is finished and can both forward the NAS message to the UE and clean up any stored redirect data. +- 14) The Attach Accept is forwarded to the UE. The UE stores the TMSI/P-TMSI with the Iu-flex NRI to be used for future signalling, even after power off. +- 15) UE responds with an Attach Complete message. + +If the RNC finds no more MSC/SGSN to redirect to after receiving a Reroute Command message, e.g. step 5 or step 9, it compares the cause code with cause codes from other Reroute Command messages it has earlier received for this UE. A cause code ranking is done and the "softest" cause code is chosen and the corresponding saved NAS attach reject message is returned to the UE. + +Each CN node that receives an Initial UE, shall run its own authentication procedure. This may in some rare situations cause the UE to be authenticated more than once, however the trust-model used is that one CN operator shall not trust an authentication done by another CN operator. This will of course not be an optimal usage of radio resources, but given the rare occurrence of this, the increased signalling should not be of any significance. + +During the redirect procedure the RNC keeps a timer, which corresponds to the UE timer of releasing the RR connection (20 seconds). If the RNC when receiving a Reroute Command message finds that there is not sufficient time for another redirect, further redirect attempts are stopped (for this attach request message). The UE will repeat its attach request four times (each time waiting 15 seconds before it re-establishes the RR connection for another try). + +#### 7.1.4.2 GERAN based MOCN configuration + +An example of an information flow for redirection in GERAN is shown below. + +In this example an attach request from a non-supporting UE is directed to two different CN operators. The UE is not a subscriber of any of the sharing operators. The UE is not served by any shared SGSN nor by any shared MSC. The UE is furthermore not under operator coordination. The first CN operator rejects since it has no roaming agreement with the subscribers Home PLMN or rejects due to CS/PS coordination required. The second CN operator accepts and completes the attach request. The different "MSC/SGSNs" in the example below shall be seen as different CN operators. One specific CN operator may also have several pooled MSCs/SGSNs connected to the BSC if A/Gb-Flex is used. + +Separate call flows are shown for CS domain and for PS domain. + +![Sequence diagram showing information flow for redirection in GERAN (CS domain).](8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant BTS + participant BSC + participant MSC A + participant MSC B + participant HLR B + + Note right of MSC A: Roaming not allowed for HPLMN of IMSI / +Roaming allowed but CS/PS coordination required + + UE->>BSC: 1. RRC Connection Establishment + UE->>BTS: 2. SABM + BTS->>BSC: 2. Establish Ind + BSC->>MSC A: 3. Complete Layer 3 Information (Attach request, redirect attempt flag) + MSC A->>UE: 4. Identity Req + UE->>MSC A: 4. Identity Resp (IMSI) + MSC A->>BSC: 5a. Reroute Command (Attach request, Attach reject, IMSI) + Note left of BSC: 5b. The RAN node queries the SGSNs in the PS domain, see clause 7.1.6 + BSC->>MSC B: 6. Complete Layer 3 Information (Attach request, redirect attempt flag, IMSI ...) + MSC B->>UE: 7. Authentication & Ciphering + MSC B->>HLR B: 8. Update Location / Insert Subscr. Data + HLR B->>MSC B: + MSC B->>UE: 9. (Attach accept) + UE->>MSC B: 10. Attach Complete + MSC B->>BSC: 11. Reroute Complete + +``` + +Sequence diagram showing information flow for redirection in GERAN (CS domain). + +**Figure 6: Information flow for redirection in GERAN (CS domain)** + +- 1) The RRC connection is established. +- 2) BSC receives the Layer 3 message from an UE. The BSC is configured to work in a Shared RAN MOCN, and therefore it forwards the message in a Complete Layer 3 Information message with an additional redirect attempt flag set. The flag indicates that the MSC shall respond to the attach request with a Reroute Command message to inform the BSC that a redirection to another CN has to be performed. + +The selection of CN node is based on NRI (valid or invalid) or by random selection. The same mechanism as defined for A-Flex in TS 23.236 [8] is used. + +- 3) The MSC receives the Complete Layer 3 Information message with the redirect attempt flag set. It then knows it may have to provide the BSC with a Reroute Command message. + +- 4) The MSC needs the IMSI of the UE. It is retrieved either from old MSC or from the UE as in this example. By comparing the IMSI with the roaming agreements of the CN operator, the MSC A discovers that roaming is not allowed or that roaming is allowed but CS/PS coordination required. Attach procedure is aborted. +- 5a) A Reroute Command message is sent back to the BSC with the attach reject message and the original attach request message received from the UE. The IMSI and an indication that the UE is attaching is also included in the message, plus a reject cause code to the BSC. +- 5b) The BSC concludes that UE is attaching. The BSC node queries the SGSNs in the PS domain whether the UE (IMSI) is served by any of the sharing operators in the PS domain. The SGSNs may need to query all MMEs that may hold the UEs context, refer to clause 7.1.6. + +In this example the UE is yet not served by a node in the PS domain. The signalling connection between BSC and MSC A is released. Based on deterministic IMSI analysis the BSC selects a MSC B in the next step. If reject was not due to CS/PS coordination required then the already tried MSC A is stored in the BSC during the redirect procedure so that the same node is not selected twice. + +- 6) The BSC sends a new Complete Layer 3 Information to the next selected MSC B with the original attach request message (in case of CS/PS coordination the Complete Layer 3 Information may also be sent back to the first MSC depending on the outcome of the coordination). Redirect attempt flag is set and IMSI shall also be included to avoid a second IMSI retrieval from UE or old MSC and to indicate that PS/CS domain coordination has been done in BSC. The CN operator selected by the BSC is included in the signalling from BSC to Core Network. The MSC B receiving the message starts its attach procedure. +- 7) MSC B does in general support roaming for the HPLMN of the IMSI and hence authentication is done and RAN ciphering is established. +- 8) MSC B updates the HLR and receives subscriber data from HLR. Subscriber data allows roaming, and the MSC B completes the attach procedure. This includes the assignment of a new TMSI with an NRI that can be used by BSC to route subsequent signalling between UE and correct MSC (A-Flex functionality). +- 9) The Attach Accept is forwarded to the UE. The UE stores the TMSI with the A-Flex NRI to be used for future signalling, even after power off. This is existing functionality. +- 10) UE responds with an Attach Complete message (TMSI (re-)allocation if not already made in Attach accept). +- 11) A Reroute Complete message is sent to BSC. The BSC knows that the redirect is completed and clean up any stored redirect data. + +If the BSC finds no more MSC to redirect to after receiving a Reroute Command message, it compares the cause code with cause codes from other Reroute Command messages it has earlier received for this UE. A cause code ranking is done and the "softest" cause code is chosen and the corresponding saved attach reject message is returned to the UE. + +Each CN node that receives a Complete Layer 3 Information shall run its own authentication procedure. This may in some rare situations cause the UE to be authenticated more than once, however the trust-model used is that one CN operator shall not trust an authentication done by another CN operator. This will of course not be an optimal usage of radio resources, but given the rare occurrence of this, the increased signalling should not be of any significance. + +During the redirect procedure the BSC keeps a timer, which corresponds to the UE timer of releasing the RR connection (20 seconds). If the BSC when receiving a Reroute Command message finds that there is not sufficient time for another redirect, further redirect attempts are stopped (for this attach request message). The UE will repeat its attach request four times (each time waiting 15 seconds before it re-establishes the RR connection for another try). + +![Sequence diagram showing information flow for redirection in GERAN (PS domain) between UE, BTS, BSC, SGSN A, SGSN B, and HLR B.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +``` + +sequenceDiagram + participant UE + participant BTS + participant BSC + participant SGSN_A as SGSN A + participant SGSN_B as SGSN B + participant HLR_B as HLR B + + Note left of UE: 1. TBF Establishment + Note left of UE: 2a. LLC (foreign TLLI=X, Attach Request) + Note left of BSC: 2b the NRI of TLLI=X points to SGSN A + Note left of SGSN_A: 3. BSSGP UL-UNIDATA (TLLI=X, Attach request, redirect attempt flag) + Note left of UE: 4. Identity Req + Note left of UE: 4. Identity Resp (IMSI) + Note right of BSC: Roaming not allowed for HPLMN of IMSI / Roaming allowed but CS/PS coordination required + Note left of BSC: 5. BSSGP DL-UNIDATA (Attach request, Attach reject, redirection indication, IMSI) + Note left of BSC: 5b. The RAN node queries the MSCs in the CS domain, see clause 7.1.6 + Note left of SGSN_B: 6. BSSGP UL-UNIDATA (Attach request, redirect attempt flag, IMSI ...) + Note left of HLR_B: 7a. Send Authentication Info + Note left of SGSN_B: 7b. Send Authentication Info Ack + Note left of UE: 7c. Authentication & Ciphering Request + Note left of SGSN_B: 7d. Authentication & Ciphering Response: Uplink LLC frame NOT routed on NRI of TLLI=X + Note left of HLR_B: 8. Update Location / Insert Subscr. Data + Note left of UE: 9. BSSGP DL-UNIDATA ( Attach accept, redirection completed...) + Note left of UE: 10. ( Attach accept ) + Note left of UE: 11. Attach Complete: new TLLI + +``` + +Sequence diagram showing information flow for redirection in GERAN (PS domain) between UE, BTS, BSC, SGSN A, SGSN B, and HLR B. + +**Figure 7-1: Information flow for redirection in GERAN (PS domain)** + +1) The TBF is established. + +2, 2a) BSC receives the LLC frame with foreign [or random] TLLI =X. + +The BSC is configured to work in a Shared RAN MOCN, and therefore it forwards the message in a BSSGP UL-UNITDATA message with an additional redirect attempt flag set. The flag indicates that the SGSN shall respond to the attach request with a BSSGP DL-UNITDATA message providing when relevant a redirection indication flag set to inform the BSC that a redirection to another CN has to be performed. + +The selection of CN node is based on NRI (valid or invalid) or by random selection. The same mechanism as defined for Gb-Flex in TS 23.236 [8] is used. + +3) The SGSN receives the BSSGP UL-UNITDATA message with the redirect attempt flag set. It then knows it may have to provide the BSC with a redirection indication flag set or a redirection completed flag set. + +4) The SGSN needs the IMSI of the UE. It is retrieved either from old SGSN or from the UE as in this example. By comparing the IMSI with the roaming agreements of the CN operator, the SGSN A discovers that roaming is not allowed or that roaming is allowed but CS/PS coordination required. Attach procedure is aborted. + +5a) A BSSGP DL-UNITDATA message is sent back to the BSC with a redirection indication flag set containing the reject cause, the attach reject message and the original attach request message received from the UE. The V(U) used for LLC-PDU setting (refer to TS 44.064 [19]) is included in the message. The IMSI and an indication that the UE is attaching is also included in the message. + +- 5b) The BSC node concludes that UE is attaching. The BSC node queries the MSCs in the CS domain whether the UE (IMSI) is served by any of the sharing operators in the CS domain. + +In this example the UE is yet not served by any node in the CS domain. Based on deterministic IMSI analysis the BSC selects a SGSN B in the next step. If reject was not due to CS/PS coordination required then the already tried SGSN A is stored in the BSC during the redirect procedure so that the same node is not selected twice. + +The BSC makes a short-lived binding between the TLLI = X and SGSN ID so that it points to SGSN B. + +- 6) The BSC sends a new BSSGP UL-UNITDATA to the next selected SGSN B with the original attach request message (in case of CS/PS coordination the BSSGP UL-UNITDATA may also be sent back to the first SGSN depending on the outcome of the coordination). Redirect attempt flag is set and IMSI shall be included to avoid a second IMSI retrieval from UE or old SGSN and to indicate that PS/CS domain coordination has been done in BSC. The V(U) shall also be included in the message. The CN operator selected by the BSC is included in the signalling from BSC to Core Network. The SGSN B receiving the message starts its attach procedure. +- 7) SGSN B does in general support roaming for the HPLMN of the IMSI and hence authentication is done and RAN ciphering is established. The value of V(U) in SGSN-B shall be set according to the received value from BSC. + +Uplink LLC frames shall be routed to SGSN B despite the NRI of the TLLI=X pointing to SGSN A. + +- 8) SGSN B updates the HLR and receives subscriber data from HLR. Subscriber data allows roaming, and the SGSN B completes the attach procedure. This includes the assignment of a new P-TMSI with an NRI that can be used by BSC to route subsequent signalling between UE and correct SGSN (Gb-Flex functionality). +- 9) A BSSGP DL-UNITDATA Attach accept message is sent to BSC with the redirection completed flag set. The BSC knows that the redirect is finished and can both forward the Attach Accept message to the UE and clean up any stored redirect data. + +SGSN B is allowed to reset the XID parameter only after the attach request is accepted. + +- 10) The Attach Accept is forwarded to the UE. The UE stores the P-TMSI with the Gb-Flex NRI to be used for future signalling, even after power off. This is existing functionality. +- 11) UE responds with an Attach Complete message (P-TMSI (re-)allocation if not already made in Attach Accept). The Attach Complete uses new TLLI. After this, the BSS releases the binding between TLLI=X and SGSN B. + +If the BSC finds no more SGSN to redirect to after receiving a BSSGP DL-UNITDATA message with the redirection indication flag set, it compares the cause code with cause codes from other BSSGP DL-UNITDATA messages it has earlier received for this UE. A cause code ranking is done and the "softest" cause code is chosen and the corresponding saved attach reject message is returned to the UE. + +Each CN node that receives a BSSGP UL-UNITDATA, shall run its own authentication procedure. This may in some rare situations cause the UE to be authenticated more than once, however the trust-model used is that one CN operator shall not trust an authentication done by another CN operator. This will of course not be an optimal usage of radio resources, but given the rare occurrence of this, the increased signalling should not be of any significance. + +During the redirect procedure the BSC keeps a timer, which corresponds to the UE timer of releasing the RR connection (20 seconds). If the BSC when receiving a BSSGP DL-UNITDATA message with the redirection indication flag set finds that there is not sufficient time for another redirect, further redirect attempts are stopped (for this attach request message). The UE will repeat its attach request four times (each time waiting 15 seconds before it re-establishes the RR connection for another try). + +#### 7.1.4.3 CS registration after PS Handover + +An example of an information flow at registration in current domain when already registered in opposite domain is shown below. + +This example shows network selection for a non-supporting UE in a shared UTRAN network. The UE is not a subscriber of any of the sharing operators. The UE is not under operator coordination. Due to PS Handover the UE is registered in the PS domain of the shared UTRAN network when the registration attempt for the CS domain occurs. + +![Sequence diagram showing information flow for registration in CS domain after PS Handover. Lifelines: UE, RNC, SGSN Operator 2, MSC Operator 1, MSC Operator 2. The process starts with 'PS Handover concluded'. Step 1: RRC Connection Establishment between UE and RNC. Step 2: Initial Direct Transfer from UE to RNC. Step 3: Initial UE (LAU Request, Redirect Attempt Flag) from RNC to MSC Operator 1. Step 4: Identity Request from MSC Operator 1 to UE. Step 4: Identity Response (IMSI) from UE to MSC Operator 1. Step 4: A note indicates the MSC concludes the UE is not served by this MSC. Step 5: Reroute Command from MSC Operator 1 to RNC. Step 6: A note indicates the RNC queries the PS domain (see clause 7.1.6). Step 7: Initial UE (LAU Request) from RNC to MSC Operator 2. Step 8: A note indicates the MSC determines if the UE is allowed to attach. Step 9: Reroute Complete (LAU accept/reject, ...) from MSC Operator 2 to RNC. Step 9: Direct Transfer from RNC to UE.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC + participant SGSN Operator 2 + participant MSC Operator 1 + participant MSC Operator 2 + + Note over UE, SGSN Operator 2: PS Handover concluded + + UE->>RNC: 1. RRC Connection Establishment + UE->>RNC: 2. Initial Direct Transfer + RNC->>MSC Operator 1: 3. Initial UE (LAU Request, Redirect Attempt Flag) + MSC Operator 1->>UE: 4. Identity Request + UE->>MSC Operator 1: 4. Identity Response (IMSI) + Note right of MSC Operator 1: 4. The MSC concludes that the UE is not served by this MSC + MSC Operator 1->>RNC: 5. Reroute Command + Note right of RNC: 6. The RNC queries the PS domain, see clause 7.1.6 + RNC->>MSC Operator 2: 7. Initial UE (LAU Request) + Note right of MSC Operator 2: 8. The MSC determines if the UE is allowed to attach + MSC Operator 2->>RNC: 9. Reroute Complete (LAU accept/reject, ...) + RNC->>UE: 9. Direct Transfer + +``` + +Sequence diagram showing information flow for registration in CS domain after PS Handover. Lifelines: UE, RNC, SGSN Operator 2, MSC Operator 1, MSC Operator 2. The process starts with 'PS Handover concluded'. Step 1: RRC Connection Establishment between UE and RNC. Step 2: Initial Direct Transfer from UE to RNC. Step 3: Initial UE (LAU Request, Redirect Attempt Flag) from RNC to MSC Operator 1. Step 4: Identity Request from MSC Operator 1 to UE. Step 4: Identity Response (IMSI) from UE to MSC Operator 1. Step 4: A note indicates the MSC concludes the UE is not served by this MSC. Step 5: Reroute Command from MSC Operator 1 to RNC. Step 6: A note indicates the RNC queries the PS domain (see clause 7.1.6). Step 7: Initial UE (LAU Request) from RNC to MSC Operator 2. Step 8: A note indicates the MSC determines if the UE is allowed to attach. Step 9: Reroute Complete (LAU accept/reject, ...) from MSC Operator 2 to RNC. Step 9: Direct Transfer from RNC to UE. + +**Figure 7-2: Information flow for registration in CS domain after PS Handover** + +- 1) The RRC connection is established. +- 2) RNC receives an Initial Direct Transfer from an UE. The RNC is configured to work in a Shared RAN MO CN, and therefore it forwards the NAS message in an Initial UE message with an additional redirect attempt flag set. The flag indicates that the MSC shall respond to the attach request with a Reroute Command or Reroute Complete IE in the Direct Transfer message. Selection of CN node is based on NRI (valid or invalid) if present in IDNNS or by random selection. The RAN stores the NRI received from the UE. +- 3) The MSC receives the Initial UE with the redirect attempt flag set. It then knows it shall answer with a Reroute Command or Reroute Complete IE in the Direct Transfer message. +- 4) The MSC needs the IMSI of the UE. It is retrieved either from old MSC or from the UE as in this example. By comparing the IMSI with the roaming agreements of the CN operator, the MSC discovers that the UE has no subscription in operator's network. The MSC concludes also that the UE is not served by the MSC. +- 5) A Reroute Command message is sent back to the RNC with an indication that it is for CSPS coordination purposes. The Reroute Command message includes the IMSI, the LAU REJECT message and the original LOCATION AREA UPDATE message received from the UE. Included is also old LAI. The Reroute Command IE is in the Direct Transfer message. +- 6) The RNC concludes that the UE is not under operator coordination. The RNC queries the SGSNs in the PS domain whether the UE (IMSI) is served by any of the sharing operators in the PS domain. The SGSNs may need to query all MMEs that may hold the UEs context, refer to clause 7.1.6. +- 7) In this example the UE is served by an SGSN node in the PS domain. The RNC selects the same operator for the CS domain and sends the Initial UE to an MSC belonging to the selected operator. The operator selected by the RNC is included in the signalling from RNC to MSC. The redirect attempt flag and an indication that the UE in the PS domain is served by the RNC selected operator shall also be included. + +- 8) The MSC determines whether the UE is allowed to attach. +- 9) The MSC sends the appropriate ACCEPT/REJECT message back to the UE. + +### 7.1.5 Supporting UEs in a MOCN configuration + +#### 7.1.5.1 UTRAN based MOCN configuration + +Supporting UEs can make use of the additional information in the broadcast system information. The UTRAN signalling flow is shown in the figure below. + +![Sequence diagram showing network selection by a supporting UE in a UTRAN MOCN configuration. The diagram involves four lifelines: SGSN Operator A, SGSN Operator B, RNC, and Supporting UE. The sequence of messages is: 1. System information from RNC to UE; 2. UE decodes network information; 3. Network selection by UE; 4. ATTACH REQUEST from UE to RNC, with a note that the RNC uses information in the header to route it to the chosen core network operator (Operator A); 5. CN node (Operator A) determines if the UE is allowed to attach; 6. ATTACH ACCEPT/REJECT from Operator A to UE.](24c9e038a791677ed33100667b64f7e6_img.jpg) + +``` +sequenceDiagram + participant SGSN Operator A + participant SGSN Operator B + participant RNC + participant Supporting UE + + Note right of Supporting UE: 2. UE decodes network information in system broadcast information. + Note right of Supporting UE: 3. Network selection + + RNC->>Supporting UE: 1. System information + Supporting UE->>RNC: 4. ATTACH REQUEST + Note right of RNC: RNC uses information in header to route the ATTACH REQUEST to the chosen core network operator + RNC->>SGSN Operator A: 4. ATTACH REQUEST + Note left of SGSN Operator A: 5. CN node determines whether the UE is allowed to attach. + SGSN Operator A->>Supporting UE: 6. ATTACH ACCEPT/REJECT +``` + +Sequence diagram showing network selection by a supporting UE in a UTRAN MOCN configuration. The diagram involves four lifelines: SGSN Operator A, SGSN Operator B, RNC, and Supporting UE. The sequence of messages is: 1. System information from RNC to UE; 2. UE decodes network information; 3. Network selection by UE; 4. ATTACH REQUEST from UE to RNC, with a note that the RNC uses information in the header to route it to the chosen core network operator (Operator A); 5. CN node (Operator A) determines if the UE is allowed to attach; 6. ATTACH ACCEPT/REJECT from Operator A to UE. + +**Figure 8: Network selection by a supporting UE in a UTRAN MOCN** + +1. The UE reads the broadcast system information in the shared RAN. +2. A supporting UE decodes the shared network information and supplies the available core network operator PLMN-ids as candidates to the PLMN selection procedure. Only PLMNs in the Multiple PLMN ID List are candidates for network selection. +3. The UE performs network selection among available PLMNs. +4. The UE sends an ATTACH REQUEST message to the network. It also indicates to the RNC the chosen core network operator. The RNC uses the routing information to determine which core network operator the message should be routed to and the ATTACH REQUEST message is sent to the core network operator chosen by the UE. +5. The core network determines whether the UE is allowed to attach to the network. +6. The shared core network node sends the appropriate ACCEPT/REJECT message back to the UE. In case of an ATTACH ACCEPT message, the core network assigns the UE an appropriate TMSI/P-TMSI so that this identity can be used for any further rerouting of messages by the RNC. + +#### 7.1.5.2 GERAN based MOCN configuration + +Supporting UEs can make use of the additional information in the broadcast system information. The GERAN signalling flow is shown in the figure below. + +![Sequence diagram showing network selection by a supporting UE in a GERAN MOCN configuration. Lifelines: SGSN Operator A, SGSN Operator B, BSC, and Supporting UE. The process involves system information broadcast, UE decoding, network selection, ATTACH REQUEST, CN node decision, and ATTACH ACCEPT/REJECT.](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg) + +``` +sequenceDiagram + participant BSC + participant UE as Supporting UE + participant SGSN_A as SGSN Operator A + participant SGSN_B as SGSN Operator B + + Note right of UE: 2. UE decodes network sharing information in system broadcast information. + Note right of UE: 3. Network selection + + BSC->>UE: 1. System information + UE->>BSC: 4. ATTACH REQUEST + Note right of BSC: BSC uses information in header to route the ATTACH REQUEST to the chosen core network operator + BSC->>SGSN_A + Note left of SGSN_A: 5. CN node determines whether the UE is allowed to attach. + SGSN_A->>UE: 6. ATTACH ACCEPT/REJECT +``` + +Sequence diagram showing network selection by a supporting UE in a GERAN MOCN configuration. Lifelines: SGSN Operator A, SGSN Operator B, BSC, and Supporting UE. The process involves system information broadcast, UE decoding, network selection, ATTACH REQUEST, CN node decision, and ATTACH ACCEPT/REJECT. + +**Figure 9: Network selection by a supporting UE in a GERAN MOCN** + +1. The UE reads the broadcast system information in the shared RAN. +2. A supporting UE decodes the shared network information and supplies the available core network operator PLMN-ids as candidates to the PLMN selection procedure. Only PLMNs in the Multiple PLMN ID List are candidates for network selection. +3. The UE performs network selection among available PLMNs. +4. The UE sends an ATTACH REQUEST message to the network. It also indicates to the BSC the chosen core network operator (via Initial L3 message for CS domain, via AS signalling for the PS domain). The BSC uses the routing information to determine which core network operator the message should be routed to and the ATTACH REQUEST message is sent to the core network operator chosen by the UE together with the chosen PLMN-id. +5. The core network determines whether the UE is allowed to attach to the network. +6. The core network node sends the appropriate ACCEPT/REJECT message back to the UE. In case of an ATTACH ACCEPT message, the core network assigns the UE an appropriate TMSI/P-TMSI so that this identity can be used for any further rerouting of messages by the BSC. + +### 7.1.6 Query to opposite domain + +The RAN may query the CN nodes in the opposite domain whether the UE is served by any of the sharing operators in the opposite domain. In the example below a registration attempt is made in the CS domain and the query in the opposite domain is sent to the PS domain i.e. the SGSNs and if not registered in the SGSN the SGSN sends the query to all MMEs that may hold the UEs context. If the registration attempt was made in the PS domain the query to opposite domain is sent to the CS domain i.e. the MSCs. + +![Sequence diagram illustrating the PS domain query process. The diagram shows the interaction between a RAN node, two SGSNs (Operator 1 and Operator 2), and four MMEs (MMEa and MMEb for Operator 1 and Operator 2). The process starts with the RAN sending a '1. UE Registration Query (MME query)' to both SGSNs. The SGSN for Operator 1 then sends a '2. UE Registration Query' to MMEa and MMEb of Operator 1. MMEa responds with '3. UE Registration Response', which the SGSN forwards as '4. UE Registration Response' to the RAN. The SGSN for Operator 2 then sends a '2. UE Registration Query' to MMEa and MMEb of Operator 2. MMEa responds with '3. UE Registration Response', which the SGSN forwards as '4. UE Registration Response' to the RAN.](933ecd14c858bf3fc919222d8e357bc8_img.jpg) + +``` + +sequenceDiagram + participant RAN + participant SGSN1 as SGSN Operator 1 + participant SGSN2 as SGSN Operator 2 + participant MMEa1 as MMEa Operator 1 + participant MMEb1 as MMEb Operator 1 + participant MMEa2 as MMEa Operator 2 + participant MMEb2 as MMEb Operator 2 + + Note left of RAN: 1. UE Registration Query (MME query) + RAN->>SGSN1: 1. UE Registration Query (MME query) + RAN->>SGSN2: 1. UE Registration Query (MME query) + Note left of SGSN1: 2. UE Registration Query + SGSN1-->>MMEa1: 2. UE Registration Query + Note left of MMEa1: 3. UE Registration Response + MMEa1-->>SGSN1: 3. UE Registration Response + Note left of SGSN1: 4. UE Registration Response + SGSN1-->>RAN: 4. UE Registration Response + Note left of SGSN2: 2. UE Registration Query + SGSN2-->>MMEa2: 2. UE Registration Query + Note left of MMEa2: 3. UE Registration Response + MMEa2-->>SGSN2: 3. UE Registration Response + Note left of SGSN2: 4. UE Registration Response + SGSN2-->>RAN: 4. UE Registration Response + +``` + +Sequence diagram illustrating the PS domain query process. The diagram shows the interaction between a RAN node, two SGSNs (Operator 1 and Operator 2), and four MMEs (MMEa and MMEb for Operator 1 and Operator 2). The process starts with the RAN sending a '1. UE Registration Query (MME query)' to both SGSNs. The SGSN for Operator 1 then sends a '2. UE Registration Query' to MMEa and MMEb of Operator 1. MMEa responds with '3. UE Registration Response', which the SGSN forwards as '4. UE Registration Response' to the RAN. The SGSN for Operator 2 then sends a '2. UE Registration Query' to MMEa and MMEb of Operator 2. MMEa responds with '3. UE Registration Response', which the SGSN forwards as '4. UE Registration Response' to the RAN. + +Figure 10: PS domain query + +- 1) The SGSN receives a UE (IMSI) query from the RAN node including an indication to also query MMEs if the UE is not served by the SGSN. +- 2) If the UE is not served by the SGSN the SGSN forwards the UE (IMSI) query to all MMEs that may hold the UEs context of the same operator as the SGSN. +- 3) If the UE is not served by any node in E-UTRAN each MME replies with a negative response to the UE query. If the UE is served by any of the MMEs, this MME replies with a positive response. +- 4) If the SGSN or any MME serves the UE, the SGSN replies with a positive response to the UE query from RAN. If the UE is not served by any SGSN or MME, the SGSN replies with a negative response to RAN. + +# --- Annex A (informative): Network Resource Indicator (NRI) allocation examples + +This annex contains examples for NRI co-ordination for non-supporting UEs in shared networks. + +--- + +## A.1 NRI in shared UTRAN/GERAN networks + +The Network Resource Identifier (NRI) is specified in Rel-5 for Intra Domain Connection of RAN Nodes to Multiple CN nodes (see TS 23.236 [8]). NRI is part of the temporary identity TMSI (CS domain) or P-TMSI (PS domain), which is assigned by the serving CN node to the MS. This clause describes NRI usage in MOCN. + +Within the shared network NRIs has to be coordinated between the operators at least due to following reasons: + +- to avoid redirection or CS/PS un-coordination when the non-supporting UE performs LA/RA update. +- to achieve that correct UE answers to paging (TMSI/P-TMSI shall be unique within shared network). +- to achieve that a non-supporting UE in visited PLMN will not change network due to LA/RA update or Detach/Attach function. +- to achieve that non-supporting UE in visited PLMN remains CS/PS coordinated when the UE moves within shared network. + +Operator coordination of CS-NRI and LAI tuple for the CS domain, and PS-NRI and RAI tuple for the PS domain is also required between the shared network and the dedicated networks of the sharing partners: + +- to achieve that non-supporting UE in visited PLMN remain registered in the same operators network when the UE moves from dedicated network to a shared network. +- to achieve that non-supporting UE in visited PLMN remains CS/PS coordinated when the UE moves from dedicated network to a shared network. + +By coordinating the actual values of the CS-NRIs for the CS domain and the PS-NRIs/MMECs for the PS domains between networks, additional signalling can be avoided when handling LA/RA updates for subscribers of the sharing partners since analysis of LAI/RAI will not be necessary. + +Operator coordination of TAI and MMEC (mapped to PS-NRI) is also required between shared UTRAN or GERAN and E-UTRANs of the sharing partners: + +- to achieve that non-supporting UE in visited PLMN remain registered in the same operators network when the UE moves from dedicated network to a shared network. +- to achieve that non-supporting UE in visited PLMN becomes CS/PS coordinated when the UE moves from EUTRAN to a shared UTRAN or GERAN network. + +If CSFB is configured for a UE, the TAI and MMEC (mapped to PS-NRI) should be operator coordinated so that additional signalling can be avoided. In any case the TAI and MMEC (mapped to PS-NRI) coordinated with another operator than the selected CS domain operator of the UE is not allowed. + +CS/PS coordination is achieved by allocating to the UE, an NRI for the CS domain and an NRI for the PS domain that together with LAI and RAI respectively indicates the same operator in the shared network. + +At LA/RA update the RNC/BSC routes the NAS message to the operator that is defined by NRI, even if NRI is created in a PLMN different from Common PLMN. + +In figure A.1 below operators A, B and C have both shared and dedicated networks, operator D has only dedicated network and operator E only shared network. + +![Figure A.1: Shared and Dedicated network example. The diagram shows a central yellow oval labeled 'A + B + C + E' with a small white rectangle inside. Surrounding this central oval are four other ovals: 'D' (white, top-left), 'C' (light blue, top-right), 'A' (green, bottom-left), and 'B' (pink, bottom-right). Oval 'A' also contains a small white rectangle. The ovals are arranged such that 'D' and 'C' are above the central oval, and 'A' and 'B' are below it, with 'A' and 'B' overlapping the central oval.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +Figure A.1: Shared and Dedicated network example. The diagram shows a central yellow oval labeled 'A + B + C + E' with a small white rectangle inside. Surrounding this central oval are four other ovals: 'D' (white, top-left), 'C' (light blue, top-right), 'A' (green, bottom-left), and 'B' (pink, bottom-right). Oval 'A' also contains a small white rectangle. The ovals are arranged such that 'D' and 'C' are above the central oval, and 'A' and 'B' are below it, with 'A' and 'B' overlapping the central oval. + +**Figure A.1: Shared and Dedicated network example** + +In the above, one or more of the operators in the shared network may deploy Iu-Flex or A/Gb-Flex between that shared radio access network and their core networks. Additionally, operators may deploy Iu-Flex or A/Gb-Flex within their dedicated core networks. For non-supporting UEs, operator coordination of the CS-NRI and LAI tuple and PS-NRI/MMEC and RAI/TAI tuple is needed not only within the shared network, but also between the shared network and the dedicated networks. + +## A.2 Alternatives for NRI split in UTRAN and GERAN + +Sharing operators need to coordinate the used NRI, following alternatives are considered: + +- 1) even split of NRI space, 1...3 most significant bits of NRI is used to identify the CN operator. +- 2) individual NRI values used to identify the CN operator. + +### Alternative 1; even split of NRI space + +| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +|-------|----|---------------|----|----|----|----|----------------|----|----|----|----|----------------------------------------------|----|----|----|----|----|----|----|----|----|---|---|---|---|---|---|---|---|---|---| +| CS/PS | | 'VLR-restart' | | | | | CN operator ID | | | | | Non shared NRI for CN operator internal use. | | | | | | | | | | | | | | | | | | | | + +A calculation for the possible number of subscribers in this scenario is: + +- With max 4 sharing CN operators, two most significant bits of NRI is required to identify the CN operator. +- 3 bits are used for the restart counter. +- 5 bits of NRI allows 32 independent NRI values for each CN operator. +- This leaves 20 bits for every MSC that is 1 M non-purged TMSI. + +The following aspects need to be considered for this solution: + +- If more bits are needed for the restart counter or CN operator ID, each additional bit reduces the available TMSI space half. +- The basic configuration allows 32 M TMSI values for each CN operator, a lot of TMSI values are wasted if some sharing partners have substantially less subscribers than others. +- It may not be feasible in large networks that use Iu-Flex or A/Gb-Flex for load balancing (see Annex A, network configuration examples in TS 23.236 [8]). +- The number of NRI bits used for CN operator ID may need to be fixed in the initial planning. Otherwise configuration of all existing nodes must be changed when new partners join the shared network. + +### Alternative 2; individual NRI values used to identify the CN operator + +This could be considered in the case where a network is shared between one big and many small CN operators. + +| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +|-------|---------------|----|----|------------------|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|----|---|---|---|---|---|---|---|---|---|---| +| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| CS/PS | 'VLR-restart' | | | Shared NRI space | | | | | | | | | | | | | | | | | | | | | | | | | | | | + +- The biggest CN operator who needs more pool areas and TMSI space takes NRI values 32...63, [1xxxxx], this means 32M TMSI values when 4 bit is used for restart counter. +- Rest of shared NRI space is allocated to other CN operators in blocks of 4M TMSI values like NRI = 28 - 31 [0111xx], 24 - 27 [0110xx] .... 0 - 3 [000xx]. Initially gaps can be left between allocated NRI range that can be used for expansion. + +Following aspects need to be considered for this solution: + +- If more bits are needed for the restart counter or NRI, each additional bit reduces the available TMSI space half. +- The initial planning of NRI length should take into account the pool area configurations of all sharing operators. + +#### TMSI per LA: + +Taking the example configurations mentioned above but changing the TMSI allocation per LA would result in an increase of the addressing space, then the same TMSI value can be used multiple times in the same VLR. More considerations with this TMSI per LA approach can be found in TS 23.236 [8]. + +## A.3 NRI and CS/PS coordination in GWCN + +For GWCN, the BSC and RNC determines a serving CN operator for a non-supporting UE based on the principles defined in clause 4.2.5.3, such that determined CN operator outcome (deterministic outcome) is the same in CS and PS domain. + +When source network determines target CN operator in handover and CS fallback, the NRI and MMEC coordination is required as for MOCN (see clause A.1) within the shared network and operator coordination of the CS-NRI and LAI tuple and PS-NRI/MMEC and RAI/TAI tuple between the shared network and the dedicated networks of the sharing partners: + +- to achieve that a non-supporting UE in visited PLMN will not change network due to LA/RA update; +- to achieve that non-supporting UE in visited PLMN becomes CS/PS coordinated. + +## A.4 CSPS Coordination + +In figure A.4-1 an example is given how the CSPS coordination can be handled, see also clause 4.2.5.3. + +![Flow diagram for CSPS Coordination. The process starts with 'RAN receives signalling from UE', followed by 'A. RAN is routing to a CN node using received NRI'. A decision diamond asks 'Can the UE be served by the CN operator?'. If YES, 'B. UE is kept in the CN operator'. If NO, 'C. Info sent from CN to RAN' (Old LA/RAI, IMSI, Attach or not). A second decision diamond asks 'Based on the received NAS routing information the RAN node shall conclude whether the UE is a) under operator coordination b) not under operator coordination or attaching'. If a), 'D. RAN forwards the registration message to the operator for which the UE is 'under operator coordination''. If b), 'E. RAN node queries CN nodes in opposite domain if UE registration'. A third decision diamond asks 'Is UE registered in the opposite domain?'. If YES, 'f1. Register the UE in current domain by same operator as in the opposite domain'. If NO, 'f2. Register the UE in current domain based on IMSI analysis'.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` + +graph TD + Start([RAN receives signalling from UE]) --> A[A. RAN is routing to a CN node using received NRI] + A --> B{Can the UE be served by the CN operator?} + B -- YES --> B_out([B. UE is kept in the CN operator]) + B -- NO --> C[C. Info sent from CN to RAN +• Old LA/RAI +• IMSI +• Attach or not] + C --> D{Based on the received NAS routing information the RAN node shall conclude whether the UE is +a) under operator coordination +b) not under operator coordination or attaching} + D -- a) --> D_out([D. RAN forwards the registration message to the operator for which the UE is 'under operator coordination']) + D -- b) --> E[E. RAN node queries CN nodes in opposite domain if UE registration] + E --> F{Is UE registered in the opposite domain?} + F -- YES --> F1([f1. Register the UE in current domain by same operator as in the opposite domain]) + F -- NO --> F2([f2. Register the UE in current domain based on IMSI analysis]) + +``` + +Flow diagram for CSPS Coordination. The process starts with 'RAN receives signalling from UE', followed by 'A. RAN is routing to a CN node using received NRI'. A decision diamond asks 'Can the UE be served by the CN operator?'. If YES, 'B. UE is kept in the CN operator'. If NO, 'C. Info sent from CN to RAN' (Old LA/RAI, IMSI, Attach or not). A second decision diamond asks 'Based on the received NAS routing information the RAN node shall conclude whether the UE is a) under operator coordination b) not under operator coordination or attaching'. If a), 'D. RAN forwards the registration message to the operator for which the UE is 'under operator coordination''. If b), 'E. RAN node queries CN nodes in opposite domain if UE registration'. A third decision diamond asks 'Is UE registered in the opposite domain?'. If YES, 'f1. Register the UE in current domain by same operator as in the opposite domain'. If NO, 'f2. Register the UE in current domain based on IMSI analysis'. + +**Figure A.4-1: Flow diagram for CSPS Coordination** + +- A. When the target RAN node receives an idle mode signalling (Attach Request/Routeing Area Update Request/Location Area Update Request messages) from a UE it routes the request to a CN node based on the NRI provided by the UE. For MOCN an operator is thereby selected. For GWCN an operator is selected by the CN node. The RAN stores the NRI received from the UE. +- B. If the UE can be served by the selected CN operator the UE is kept. A 'Redirection Completed' indication shall then be included in the response to the RAN node and the procedure ends. In the following cases the CN operator can serve the UE: +1. The UE is a non-roaming subscriber of the selected CN operator. + 2. The UE is already served by the selected CN operator (e.g. periodic updates or mobility within a pool). + 3. The RAN node indicates a RAN selected CN operator and the selected CN operator is serving the UE in the opposite domain. +- C. If the UE is not kept by the selected CN operator then 'Redirection Indication' with 'CS/PS coordination Required' and IMSI is included in the response to the RAN node. Old LAI (for the CS domain) or old RAI (for the PS domain) or an indication whether the UE is attaching in the current domain, is also included in the response. +- D. If the UE is under operator coordination, the RAN node selects a core node of the identified operator and forwards the message accordingly. The procedure ends. + +NOTE 1: If the UE is under operator coordination and is both CS and PS registered in the source network, this operator is kept and CS/PS coordination is achieved. + +However, in conditions valid for step E and if the UE lacks CS registration in the source network (e.g. as with source LTE and no SGs registration) then achieving a successful CS/PS coordination and keeping the same serving operator as in the source network will be dependent upon the access to the information about the source network PS domain registration. For that reason it becomes necessary to check if the UE is registered in the PS domain (see step E) and if so register with that operator also in the CS domain. For example at cell reselection from a source LTE to a target GERAN network without DTM there will, during CS registration, be no registration in the PS domain within the shared target network. Therefore a check must also been done in all possible source networks of the sharing operators otherwise users may become CS/PS uncoordinated. The lack of CS registration in the source network implies an initial CS attach in the target network and therefore step E will be performed. + +A similar situation can occur when the UE lacks PS registration (as with no Data roaming for the UE) but for normal cases the UE is already registered in the target shared network in the CS domain when the PS registration occur. Checking in the source networks is then not necessary. + +E. If the UE is not under operator coordination, or if the UE is making an initial attach, the RAN node sends requests to all connected CN nodes or by a possible optimization to one CN node per operator in the opposite domain in the target shared network, to inquire if the UE is served by the opposite domain. To not risk a change of serving operator for cases described in step D (i.e. when attaching to CS domain) then it is also necessary to check in the all MMEs that may hold the UEs context, of the sharing operators, if the UE is registered in the PS domain. Checking the source MMEs is done by relaying requests from target RAN via the CN in the target shared network. However in deployments where these cases are not applicable (e.g. always CS registration in source networks) or when it is sufficient to achieve CS/PS coordination, then the source networks need not to be checked. + +NOTE 2: Checking CN nodes in the opposite domain in the target shared network is also used at e.g. CS and PS Handover when the UE is not under operator coordination. For such cases the idle mode domain registration needs to select the same operator as is already in use for the connected domain. + +F1. If the UE is registered in the opposite domain then the RAN node retrieves the PLMN of that registered operator and selects the same operator for the current domain. The procedure ends. + +F2. If the UE is not registered in the opposite domain then the RAN node selects operator based on the IMSI analysis. The procedure ends. + +If during execution of step D or E, a registration in the opposite domain occurs, then the RAN node can optionally select as follows: + +- If the UE is registered in the opposite domain and is under operator coordination and is not performing an initial attach, then the RAN node, for both domains, selects serving operator based on the registration information from the opposite domain. +- If the UE is registered in the opposite domain and is not under operator coordination or is attaching, but with regards to the current domain the UE: + - is under operator coordination and is not performing an initial attach, then the RAN node, for both domains, selects serving operator based on the registration information applicable to the current domain. + - is not under operator coordination or is attaching then the RAN node, for both domains, selects serving operator based on IMSI analysis. + +For parallel registrations in the CS and PS domains the above means that CS/PS coordination is achieved and that serving operator is kept. + +# --- Annex B (normative): Interaction with other network capabilities + +## B.1 General + +The provision of services and service capabilities in a network should not be restricted by the existence of network sharing. Therefore, all new features (or enhancements to existing features) should be specified to work in network sharing environments. If it is not possible to specify complete support for Network Sharing (i.e. PLMNs in a Shared Network has the same features/capabilities and the same operational situation as a stand alone PLMN) then such deviations are documented in this Annex. + +## --- B.2 Support for RAN sharing for CSG and hybrid cells + +A cell with closed/hybrid access can only broadcast one CSG ID but may broadcast several PLMN IDs. If a cell with closed/hybrid access broadcasts several PLMNs (see clauses 5.2 and 5.2a) for a UE supporting shared network or a non-supporting UE that performs the PLMN selection (see clause 4.2.3.2), it is the operator responsibility to coordinate the CSG IDs between the operators' PLMNs. + +For handover into a shared hybrid or shared CSG cell, the source RAN shall determine a target core network operator for which the UE is a CSG member since otherwise the handover is likely to fail. In case the UE is capable of reporting the subset of the broadcasted PLMN IDs in the target cell to which its CSG membership is verified, the source RAN bases its core network operator selection on this information. If this information is not reported by the UE the selection of a target core network operator is based on pre-configured information in the RAN. + +**NOTE:** To ensure that handovers do not fail due to the source RAN selecting a core network operator for which the UE is not a CSG member in the case when the UE only reports the Primary PLMN-ID (E-UTRAN) as described in TS 36.331 [11] or no PLMN ID (UTRAN), the following RAN configuration can be used. The source RAN is configured with all broadcasted PLMN identities of neighbouring shared hybrid and closed access mode CSG cells, so that this data can be retrieved based on the UE-provided information (ECGI/TAC/CSG ID in E-UTRAN and Cell ID in UTRAN) of the target H(e)NB. The source RAN determines a target PLMN ID from the Handover Restriction List (HRL, see TS 36.413 [14]) in E-UTRAN or Shared Network Area (SNA) access information (see TS 25.413 [13]) in UTRAN. If HRL or SNA are not supported, local configuration in the RAN could be used. For a target cell, the allowed PLMN identities according to CSG membership should be the same as the allowed PLMN identities for handover because otherwise handovers can fail. If the target is hybrid cell and the UE is not a CSG member, the handover may be solved in the same way. + +For further details on Closed Subscriber Group (CSG) and closed/hybrid access, see TS 36.300 [10] and TS 25.467 [17]. + +# Annex C (informative): Change History + +| Change history | | | | | | | | | +|----------------|---------|-----------|------|-----|-----|------------------------------------------------------------------------------------------------------------------|---------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 2011-09 | SP-53 | SP-110457 | 0034 | 5 | B | Introduction of FULL-MOCN-GERAN feature | 11.0.0 | | +| 2012-03 | SP-55 | SP-120088 | 0037 | 2 | B | SRVCC and Network Sharing from E-UTRAN | 11.1.0 | | +| 2012-03 | SP-55 | SP-120088 | 0039 | - | D | Editorial corrections on redirection message for Non-supporting UEs in a MOCN configuration | 11.1.0 | | +| 2012-03 | SP-55 | SP-120079 | 0040 | 1 | B | Introduction of FULL-MOCN-GERAN feature | 11.1.0 | | +| 2012-03 | SP-55 | SP-120079 | 0043 | 1 | C | FULL-MOCN-GERAN support | 11.1.0 | | +| 2012-03 | SP-55 | SP-120088 | 0045 | 2 | B | EAB for network sharing | 11.1.0 | | +| 2012-06 | SP-56 | SP-120251 | 0046 | 2 | F | Support for RAN sharing for CSG and hybrid cells | 11.2.0 | | +| 2012-06 | SP-56 | SP-120237 | 0051 | 2 | A | SRVCC and Network Sharing | 11.2.0 | | +| 2012-06 | SP-56 | SP-120251 | 0053 | 2 | F | EAB overload control from CN to RAN for UTRAN/GERAN in shared networks | 11.2.0 | | +| 2012-06 | SP-56 | SP-120248 | 0054 | 1 | B | rSRVCC in network sharing with LTE to CS and back to LTE | 11.2.0 | | +| 2012-06 | SP-56 | SP-120251 | 0060 | 1 | F | Network Sharing Corrections for SRVCC | 11.2.0 | | +| 2012-06 | SP-56 | SP-120246 | 0061 | 2 | F | Corrections for MOCN GERAN | 11.2.0 | | +| 2012-06 | SP-56 | SP-120251 | 0062 | 2 | B | GWCN for GERAN | 11.2.0 | | +| 2012-06 | SP-56 | SP-120252 | 0063 | 3 | B | SIRIG support in shared networks | 11.2.0 | | +| 2012-06 | SP-56 | SP-120246 | 0064 | 1 | B | Selection of PLMN for the CS Domain in CSFB towards a shared GERAN | 11.2.0 | | +| 2012-06 | SP-56 | SP-120239 | 0068 | 4 | F | EAB in shared networks | 11.2.0 | | +| 2012-09 | SP-57 | SP-120486 | 0057 | 6 | F | Network Sharing Corrections following review of GWCN UTRAN | 11.3.0 | | +| 2012-09 | SP-57 | SP-120483 | 0074 | - | F | Impact of SIRIG on the BSS in a shared network | 11.3.0 | | +| 2012-12 | SP-58 | SP-120726 | 0059 | 5 | F | GWCN UTRAN and charging | 11.4.0 | | +| 2012-12 | SP-58 | SP-120902 | 0067 | 8 | F | Network sharing impact on the CSFB | 11.4.0 | | +| 2012-12 | SP-58 | SP-120722 | 0077 | 5 | F | Using NRI for CS/PS coordination | 11.4.0 | | +| 2012-12 | SP-58 | SP-120724 | 0078 | 1 | F | Incorrect definition of Anchor PLMN | 11.4.0 | | +| 2012-12 | SP-58 | SP-120722 | 0080 | 3 | C | Indicating selected PLMN to target BSC during handover | 11.4.0 | | +| 2012-12 | SP-58 | SP-120710 | 0085 | - | A | HPLMN needs to be unaware of network sharing in VPLMN | 11.4.0 | | +| 2013-03 | SP-59 | SP-130085 | 0086 | 2 | F | Further consideration on the network sharing impact on the CSFB | 11.5.0 | | +| 2013-03 | SP-59 | SP-130085 | 0087 | 2 | F | CDRs needs to reflect whether the core network operator was selected by a UE or allocated by the network to a UE | 11.5.0 | | +| 2013-03 | SP-59 | SP-130085 | 0089 | 4 | C | Indicating selected PLMN to target BSC during handover | 11.5.0 | | +| 2013-12 | SP-62 | SP-130523 | 0095 | 2 | F | RNC functionality in GWCN deployments | 11.6.0 | | +| 2013-12 | SP-62 | SP-130534 | 0096 | 5 | F | Core Network Operator selection origin | 12.0.0 | | +| 2013-12 | SP-62 | SP-130536 | 0097 | 2 | F | Support of inbound mobility to a shared CSG cell | 12.0.0 | | +| 2014-06 | SP-64 | SP-140262 | 0099 | 2 | B | Master eNB is responsible to select Secondary eNBs compliant to network sharing agreements | 12.1.0 | | +| 2014-06 | SP-64 | SP-140377 | 0100 | 3 | F | Exchange of PLMN identities in Shared Networks | 12.1.0 | | +| 2014-12 | SP-66 | SP-140692 | 0101 | 2 | C | CSPS Coordination General Description | 13.0.0 | | +| 2014-12 | SP-66 | SP-140692 | 0102 | 1 | C | Example signalling flows | 13.0.0 | | +| 2014-12 | SP-66 | SP-140692 | 0103 | 1 | C | Example logics for CSPS Coordination | 13.0.0 | | +| 2014-12 | SP-66 | SP-140692 | 0104 | 1 | C | Functional description | 13.0.0 | | +| 2015-03 | SP-67 | SP-150026 | 0105 | 3 | C | CSPS Coordination Annex A.1 and A.3 updates | 13.1.0 | | +| 2016-06 | SP-72 | SP-160288 | 0106 | 1 | F | Removing CS/PS-NRI signalling from MSC/SGSN to RNC/BSC | 13.2.0 | | +| 2017-03 | - | - | - | - | - | Update to Rel-14 version (MCC) | 14.0.0 | | +| 2017-09 | SP-77 | SP-170723 | 0107 | 2 | C | EUTRAN sharing enhancement alignment | 14.1.0 | | +| 2018-06 | SP-80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | | +| 2018-09 | SP-81 | SP-180729 | 0108 | 2 | F | Definition of Primary PLMN ID | 15.1.0 | | +| 2020-07 | SP-88E | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23379/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg b/marked/Rel-16/23_series/23379/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f1edaa531446f0e76af4fcaeb3eaa19896cdb9d --- /dev/null +++ b/marked/Rel-16/23_series/23379/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74a16f9ed3e44c31357e098abf4cb294c5075d91b6a4b89a1b05deeed027591d +size 52776 diff --git a/marked/Rel-16/23_series/23379/077f85b82901283b4657fd2b45fc0294_img.jpg b/marked/Rel-16/23_series/23379/077f85b82901283b4657fd2b45fc0294_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..684d83e675209fd575b0bec6dce1e33a5dd3b0e7 --- /dev/null +++ b/marked/Rel-16/23_series/23379/077f85b82901283b4657fd2b45fc0294_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16a8f452edb0d1d8bbcf5bc1cf18258e595fc05ac17b798d2e2ec64056c338b7 +size 64223 diff --git a/marked/Rel-16/23_series/23379/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-16/23_series/23379/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3003e09c89a796e5242a5251d7ee68a73d879c45 --- /dev/null +++ b/marked/Rel-16/23_series/23379/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff08d96974a72f1296e1b6ac5e38979ec8ee67c214d67978b50dc7f8118a2542 +size 45104 diff --git a/marked/Rel-16/23_series/23379/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg b/marked/Rel-16/23_series/23379/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f553ace829508b836a639224ad6344c863927b71 --- /dev/null +++ b/marked/Rel-16/23_series/23379/0a06de972d61ab9bb901bd74dd4ff51f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69c2b0c318e295c6269e1ee73d6ecfca32f96dbac19de3f80d7ec394b527a25f +size 41359 diff --git a/marked/Rel-16/23_series/23379/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-16/23_series/23379/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fb45a6e2dabb7ab8b8db17d8c59466235599249 --- /dev/null +++ b/marked/Rel-16/23_series/23379/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb6e1bd6f77229ac7ac253b784de860034b85fcf2a6825e91c15989f19b058c2 +size 107654 diff --git a/marked/Rel-16/23_series/23379/0f5c79ad7c317f14f16aa5a2c036e406_img.jpg b/marked/Rel-16/23_series/23379/0f5c79ad7c317f14f16aa5a2c036e406_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e18968b71dfc626ffe4b79948fbcf12bd64edbd --- /dev/null +++ b/marked/Rel-16/23_series/23379/0f5c79ad7c317f14f16aa5a2c036e406_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ba084bb74f722a7a3b3a6f043b488320cd838cb435224067b8f331792f5eb5d +size 37502 diff --git a/marked/Rel-16/23_series/23379/163688ca8da9787f5d48edd68d8cc75b_img.jpg b/marked/Rel-16/23_series/23379/163688ca8da9787f5d48edd68d8cc75b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f31503dc980d31320dbe40feea051bef2d3f3aaf --- /dev/null +++ b/marked/Rel-16/23_series/23379/163688ca8da9787f5d48edd68d8cc75b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c27a3217a3213a36be0b662863c242b4c2fc3224ab6af8f5c08092a044ac05a2 +size 46541 diff --git a/marked/Rel-16/23_series/23379/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/Rel-16/23_series/23379/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7ff65539bbc6f57cb0f4d4e31a5525082bece77 --- /dev/null +++ b/marked/Rel-16/23_series/23379/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da6db05eaa0387abe9a00b7334016b796599038fde4b952c830cd217a8f442d2 +size 69343 diff --git a/marked/Rel-16/23_series/23379/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/marked/Rel-16/23_series/23379/18bb06865e2dada3656ea3d57f290f7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8248964acd8cf9c057391766c5287e687f1215fd --- /dev/null +++ b/marked/Rel-16/23_series/23379/18bb06865e2dada3656ea3d57f290f7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc16ee01d9c9b4d582c1e93d74535491a43b3d5bb12dfce9dda071e6934d64d7 +size 50143 diff --git a/marked/Rel-16/23_series/23379/1b893df61c2b73b7a85e65fc1f58e203_img.jpg b/marked/Rel-16/23_series/23379/1b893df61c2b73b7a85e65fc1f58e203_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7cd4b19300b3d0fa40e1ca73a3e25882af6ac165 --- /dev/null +++ b/marked/Rel-16/23_series/23379/1b893df61c2b73b7a85e65fc1f58e203_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37e8fe9fc193f696a694dc5212a0b9a55fa8fcfd1868d93cd003139aa08c92fd +size 51296 diff --git a/marked/Rel-16/23_series/23379/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/marked/Rel-16/23_series/23379/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13e4611d6d246f637652fe0bedfc737922d2b16a --- /dev/null +++ b/marked/Rel-16/23_series/23379/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:30023661643b802c1d8246209db58320a3e3248f6fa960d4e65edffcc8298f46 +size 69317 diff --git a/marked/Rel-16/23_series/23379/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg b/marked/Rel-16/23_series/23379/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58358194ed73105da2b0e99dcae95b1637c09382 --- /dev/null +++ b/marked/Rel-16/23_series/23379/23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a77c30de357ff33fc1ba92689701c43beec1410395e27667354834d1d45d970e +size 29898 diff --git a/marked/Rel-16/23_series/23379/23d9fcc2863a6b0548d6b4e8abf15106_img.jpg b/marked/Rel-16/23_series/23379/23d9fcc2863a6b0548d6b4e8abf15106_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8da7f623c04c31af5601a4e75b2304175c0061e --- /dev/null +++ b/marked/Rel-16/23_series/23379/23d9fcc2863a6b0548d6b4e8abf15106_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aec304844a1bfc059af16ebf1041c00d7484d42ae1f0dadb7c32b00a79184fe4 +size 56146 diff --git a/marked/Rel-16/23_series/23379/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg b/marked/Rel-16/23_series/23379/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..521683acc738fd2971eb24a7811c8048aebacc70 --- /dev/null +++ b/marked/Rel-16/23_series/23379/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dedba5c3d53d619aa7e9d02cfcfef11943fe4db212ea7715965f0655659d19b3 +size 51382 diff --git a/marked/Rel-16/23_series/23379/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/23_series/23379/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddf6d3ebb87d12a37d59c9128623795b5731a678 --- /dev/null +++ b/marked/Rel-16/23_series/23379/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad68d13219729eb0b1e986ac78c3af8b7b0eb384ab26cc57ef5c94881b0f3be4 +size 30647 diff --git a/marked/Rel-16/23_series/23379/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23379/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efcb5217110c6bb0da5f5df57e03f0f922ac6f45 --- /dev/null +++ b/marked/Rel-16/23_series/23379/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6cea1e372bd933abec8124b44d3ce8b94282ea58de089e78dbd7d3cadadbfc0 +size 74988 diff --git a/marked/Rel-16/23_series/23379/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-16/23_series/23379/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fdbd011e66ac8a4dd0ff4b8e2568edc36957c38 --- /dev/null +++ b/marked/Rel-16/23_series/23379/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7596e95edf241b5273e2d99e25c07547bf5aa28f7cd203745692256536b267b7 +size 36311 diff --git a/marked/Rel-16/23_series/23379/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23379/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b77e3d2c12b01b9391dfffd2b143dbe25ea7d1d6 --- /dev/null +++ b/marked/Rel-16/23_series/23379/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:488f9734da82ba1ffd0d38aa11b1b304f71016cf8befbce0513de0c7b86bc14e +size 67643 diff --git a/marked/Rel-16/23_series/23379/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-16/23_series/23379/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b04889a9df22714b773b627df8de8855e825db1e --- /dev/null +++ b/marked/Rel-16/23_series/23379/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23c74a47f32c6f023e78d1d20d811822df760887872a9f67e1701df1eef78e1e +size 54204 diff --git a/marked/Rel-16/23_series/23379/31ef15d175af5babdbf4d2fbac884c1b_img.jpg b/marked/Rel-16/23_series/23379/31ef15d175af5babdbf4d2fbac884c1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d6b25bc4e333f40adb920e91e933c5b75efba46 --- /dev/null +++ b/marked/Rel-16/23_series/23379/31ef15d175af5babdbf4d2fbac884c1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f84b486b40c9c6c8ae31d7e5ec32e054693e8fa380bd46646299565e570db829 +size 57189 diff --git a/marked/Rel-16/23_series/23379/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/23_series/23379/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2aef3e97737d00cad308ff87b874c0583ed7d6b4 --- /dev/null +++ b/marked/Rel-16/23_series/23379/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e0b35e00801b9b456024164976c46596ec6ee50fcdcddb5319f4a640f09f615 +size 113651 diff --git a/marked/Rel-16/23_series/23379/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg b/marked/Rel-16/23_series/23379/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b601dbf3fe59924a9311c20fc213e5d18a6ac9a7 --- /dev/null +++ b/marked/Rel-16/23_series/23379/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e2f2747c393c491fb173cdb5d461f9baf3be89b0084bb437d75367cf6efe7e9 +size 74905 diff --git a/marked/Rel-16/23_series/23379/3380dd0ed19bc6f4da5a9d8c55ba535d_img.jpg b/marked/Rel-16/23_series/23379/3380dd0ed19bc6f4da5a9d8c55ba535d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..deda1f8edd49996928708beab3ab80188d8d014e --- /dev/null +++ b/marked/Rel-16/23_series/23379/3380dd0ed19bc6f4da5a9d8c55ba535d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72a011e80447e3fc6257586d6fce54a6904430f9e7cbdbed16ac892061ccebf5 +size 58624 diff --git a/marked/Rel-16/23_series/23379/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg b/marked/Rel-16/23_series/23379/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0c84440b993b1519fca58070d89ac090dd6c03c --- /dev/null +++ b/marked/Rel-16/23_series/23379/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03d2490b4510cb90f90257c3c3ebb4c3a4a66100cce25337dd43e4e8d3ac2238 +size 148248 diff --git a/marked/Rel-16/23_series/23379/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-16/23_series/23379/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19d0aaabe8826c261499c83cb275cbafcbca01c3 --- /dev/null +++ b/marked/Rel-16/23_series/23379/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e032d8fc39e23eb2d5bfd61afc03e10165b97960b8bbae9e2471e53a2c3ff40e +size 25054 diff --git a/marked/Rel-16/23_series/23379/34f9874474c0f8f03423fce29f2c2ded_img.jpg b/marked/Rel-16/23_series/23379/34f9874474c0f8f03423fce29f2c2ded_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b0cc74171daf13cf2cae2af00a16615824a49bf --- /dev/null +++ b/marked/Rel-16/23_series/23379/34f9874474c0f8f03423fce29f2c2ded_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22a602100aa59a7b5f9271b7dedc4280cdade57ebd285737fd68b96d6d1a3e52 +size 17413 diff --git a/marked/Rel-16/23_series/23379/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/Rel-16/23_series/23379/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34ddaf4fbc80fd39d367cc5ebd5cac5c04f369d3 --- /dev/null +++ b/marked/Rel-16/23_series/23379/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7aa5b155e72abb65213d27230a23829116f2a62f5b79c491a73fbb8c4700e9f9 +size 77907 diff --git a/marked/Rel-16/23_series/23379/39536a630fa74c3bcfd1670ee2152809_img.jpg b/marked/Rel-16/23_series/23379/39536a630fa74c3bcfd1670ee2152809_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e78dd32555991d020687d47b167e08bfead55b3d --- /dev/null +++ b/marked/Rel-16/23_series/23379/39536a630fa74c3bcfd1670ee2152809_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e572444b27af7142ad8f30497b29e724bbfe98e8623a89f97fef26565d5005c +size 72527 diff --git a/marked/Rel-16/23_series/23379/408c4798ea60469e0728a7cbbd598668_img.jpg b/marked/Rel-16/23_series/23379/408c4798ea60469e0728a7cbbd598668_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cae2a1b27b7fd3445a46f876d4ebfe963638098 --- /dev/null +++ b/marked/Rel-16/23_series/23379/408c4798ea60469e0728a7cbbd598668_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:daaf8f5e4a99a8673e92495f401372178f83ebfe718b8ab82e412a14940a3742 +size 51029 diff --git a/marked/Rel-16/23_series/23379/4224f170b677d60f6f86ce95d8dc725a_img.jpg b/marked/Rel-16/23_series/23379/4224f170b677d60f6f86ce95d8dc725a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01d8a649cc92c592bd5db0b9a08e697eea8f3336 --- /dev/null +++ b/marked/Rel-16/23_series/23379/4224f170b677d60f6f86ce95d8dc725a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09b407aaf9eb702f7007784ddbb7aceea819caaeb29e894f4b0547dfa55b02fb +size 43425 diff --git a/marked/Rel-16/23_series/23379/4430c1d8e78ac97fda782321410349a9_img.jpg b/marked/Rel-16/23_series/23379/4430c1d8e78ac97fda782321410349a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3de989c5ca9a9613084e1e353d5d0013541fa65d --- /dev/null +++ b/marked/Rel-16/23_series/23379/4430c1d8e78ac97fda782321410349a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6275027214df9602d635495abd3270f17137fa5df991312b7a68f1617916abee +size 34482 diff --git a/marked/Rel-16/23_series/23379/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Rel-16/23_series/23379/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a150fcfecf8ec60436476edfa01bacc6c55421a8 --- /dev/null +++ b/marked/Rel-16/23_series/23379/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd8fc3037c1146afa498f28cff56ae68b931b3e5febaa2372171a49ed2ef3b85 +size 34689 diff --git a/marked/Rel-16/23_series/23379/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-16/23_series/23379/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..499e4964d032fd05f309ec63542cf9ea701fbfd1 --- /dev/null +++ b/marked/Rel-16/23_series/23379/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68e9bd7be1bfe5033a33030559cf9295d9c16a0075a747a0e258ede6340ce665 +size 31993 diff --git a/marked/Rel-16/23_series/23379/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-16/23_series/23379/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6f2d085988a798e81a6eaf138757417010bc535 --- /dev/null +++ b/marked/Rel-16/23_series/23379/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3564d0e6f91a34b3c36a5004c04be405e92e2ba34a719fce3ffd5273fe2828c +size 111500 diff --git a/marked/Rel-16/23_series/23379/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-16/23_series/23379/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a055aded4c6cfeebff0e8b5aa1f218a0fd6eadb2 --- /dev/null +++ b/marked/Rel-16/23_series/23379/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7ea48a2ffaf17f26ed3ceac218672ddfa4f7dab37a41a0e216bd578e3e73635 +size 88162 diff --git a/marked/Rel-16/23_series/23379/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-16/23_series/23379/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46573ea8297b4214688297962f5b4ddce0e94a64 --- /dev/null +++ b/marked/Rel-16/23_series/23379/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21f2c1b7906d8deb1fde48b77806bb301a688ea5c7bbe5f012f33a545324fe70 +size 83449 diff --git a/marked/Rel-16/23_series/23379/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg b/marked/Rel-16/23_series/23379/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eee750ff93baa1e688fb893a5fdf5f6a0daa734f --- /dev/null +++ b/marked/Rel-16/23_series/23379/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b57a5fb16c3b2b1f67a68e44a22960cf9a3164c981024324f6a2c66663254d5 +size 30106 diff --git a/marked/Rel-16/23_series/23379/6116b1a533010c170fc526ec513ba0b8_img.jpg b/marked/Rel-16/23_series/23379/6116b1a533010c170fc526ec513ba0b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4be03d8a1f281969395e4075d29f9d7dadd894a1 --- /dev/null +++ b/marked/Rel-16/23_series/23379/6116b1a533010c170fc526ec513ba0b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65a109ea265143308bcb3f5b7fabc32a8c3f3137de6eaa81bfc464d2eb48671d +size 43022 diff --git a/marked/Rel-16/23_series/23379/61520b710bffec2edcf998d1ed43beb9_img.jpg b/marked/Rel-16/23_series/23379/61520b710bffec2edcf998d1ed43beb9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..127740435225261de73cab0a13d003631c309100 --- /dev/null +++ b/marked/Rel-16/23_series/23379/61520b710bffec2edcf998d1ed43beb9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:768c06fc8d1ec1772197d539225acdbf7cc5e1c6cb1518aa46b79f526b30b47a +size 35908 diff --git a/marked/Rel-16/23_series/23379/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-16/23_series/23379/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3cf6ec4a50f3bf7a949e55e57848f8ba06ccc2dd --- /dev/null +++ b/marked/Rel-16/23_series/23379/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da6a6214aead7ab01f7c984b239e05319e00211b22a68cb77a3a3bf9d8c6043b +size 59471 diff --git a/marked/Rel-16/23_series/23379/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-16/23_series/23379/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36acb07bc8a5bac2d07e9cdd36a44bc5cb296280 --- /dev/null +++ b/marked/Rel-16/23_series/23379/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3646b91bc4bd475d8814219dfac1af9fb6374c63d3928aec876723216a031790 +size 17785 diff --git a/marked/Rel-16/23_series/23379/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-16/23_series/23379/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90134f5e8e468e5ebdb223f09952ba5aba17e04c --- /dev/null +++ b/marked/Rel-16/23_series/23379/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b733f45606d1d950894f0f0d7b2b6748b2f574d5cf8178225cd03d074ee6d7d +size 52175 diff --git a/marked/Rel-16/23_series/23379/747516f5861a0ddf31e3851da8e34b95_img.jpg b/marked/Rel-16/23_series/23379/747516f5861a0ddf31e3851da8e34b95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90b5d4ba18ab53d43c5c38dc921b42644665b320 --- /dev/null +++ b/marked/Rel-16/23_series/23379/747516f5861a0ddf31e3851da8e34b95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b56e92d56d9d03ebc613d9eb329864755f31eb5c236b6c4f5102c81fd76d9264 +size 95971 diff --git a/marked/Rel-16/23_series/23379/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg b/marked/Rel-16/23_series/23379/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4bbfba8a9f18be6cbca5acb1ba5a8c776245d73 --- /dev/null +++ b/marked/Rel-16/23_series/23379/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae006ca3e5c3acad0ff9cc4318809e39a92f5e7ba05181527a6ef942b3300823 +size 166795 diff --git a/marked/Rel-16/23_series/23379/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-16/23_series/23379/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bda8d2427e16825bd186fabe6302a4b2acd395e2 --- /dev/null +++ b/marked/Rel-16/23_series/23379/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92a8c325dc5310bab3f1febd8439e0cad6428a9674f51d7460f252bd55a3bb64 +size 79570 diff --git a/marked/Rel-16/23_series/23379/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/23_series/23379/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3fff835b65324540bf57b0fdaadd10c6195fe2a --- /dev/null +++ b/marked/Rel-16/23_series/23379/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:131df96024f045e80b5bfd8d30de862264e483c953c9d684a4100e847c6cd1c5 +size 40698 diff --git a/marked/Rel-16/23_series/23379/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/23_series/23379/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4eae001019432a0a22cdd30ef261b1f9ce9c840a --- /dev/null +++ b/marked/Rel-16/23_series/23379/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8997464fcea70c78dec825a2c63bbf67e6c75b92242e4ad80e95c76c396878f +size 75225 diff --git a/marked/Rel-16/23_series/23379/7c57192c514175021e4560a1a46126c1_img.jpg b/marked/Rel-16/23_series/23379/7c57192c514175021e4560a1a46126c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..487f0fd410aca25d0c22bcdd56a92f252892c660 --- /dev/null +++ b/marked/Rel-16/23_series/23379/7c57192c514175021e4560a1a46126c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:672a07d1e676049a200441b0d35d5ab89ed8174dd7b5fb9fc360d51b0ac8b68a +size 81621 diff --git a/marked/Rel-16/23_series/23379/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg b/marked/Rel-16/23_series/23379/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0c6715810b54e65b8024d925682a5991427dcfd --- /dev/null +++ b/marked/Rel-16/23_series/23379/7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:76f5d981f06294d639da391ae8d89a0ed447d28d331397e2920a60333babc4e2 +size 121009 diff --git a/marked/Rel-16/23_series/23379/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-16/23_series/23379/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34bed168e725299d98a041c274effe50c3f41452 --- /dev/null +++ b/marked/Rel-16/23_series/23379/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6aabb3a94c106409bf727cb6ae7c3ff12fa7343809714819946cd209784b63a4 +size 100720 diff --git a/marked/Rel-16/23_series/23379/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23379/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09d841b24d19d91b5cbfd6fbcc2adcefd024bff0 --- /dev/null +++ b/marked/Rel-16/23_series/23379/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0882ca5038c893e26ab382a7ca7fedc9dcb9891e2497bc0fb94451e042bc500 +size 50795 diff --git a/marked/Rel-16/23_series/23379/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-16/23_series/23379/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f6cfe97d28443d3c3b824ecd883e2f17ab1c9961 --- /dev/null +++ b/marked/Rel-16/23_series/23379/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c61de2a16c62bd77d1710fa0e884b2331e33d5020abed91d615286bdd300dff9 +size 61060 diff --git a/marked/Rel-16/23_series/23379/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23379/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c963b23405186b83003127d4ba054120a630852d --- /dev/null +++ b/marked/Rel-16/23_series/23379/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e616d5c85b5dc11d8183d2f7f57c5ad979fe9f60a3b6685c606c4f99b71bda4 +size 70575 diff --git a/marked/Rel-16/23_series/23379/896f6ec457b6252d4af32a634299218c_img.jpg b/marked/Rel-16/23_series/23379/896f6ec457b6252d4af32a634299218c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4546ad8552aa6aa7ca1f08a56494828c54ce21e1 --- /dev/null +++ b/marked/Rel-16/23_series/23379/896f6ec457b6252d4af32a634299218c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa32f651cdff6b0003f4e574f43836f0b718bf79f9b0deccac219c044525e5a4 +size 53649 diff --git a/marked/Rel-16/23_series/23379/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/23_series/23379/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f64d99566d04e39e817f885c728203a3978d9b8a --- /dev/null +++ b/marked/Rel-16/23_series/23379/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7e3767dc6a00b91ef1bb5111079860b0fe0a103b2d96047558f0826e71ae814 +size 67026 diff --git a/marked/Rel-16/23_series/23379/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23379/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78b639c0e838a8fe8b348216d6ef8439b94572b5 --- /dev/null +++ b/marked/Rel-16/23_series/23379/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39f0a55b5b4bcfa0a3a8a997d4ca43b53a2b0a2da1d3119778f2bda9e1097b5c +size 67827 diff --git a/marked/Rel-16/23_series/23379/99781d878388c3e0f359b1d6ce14119c_img.jpg b/marked/Rel-16/23_series/23379/99781d878388c3e0f359b1d6ce14119c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa5e1fb97435d4c1eac5737aa0a4d740eb5a2a1e --- /dev/null +++ b/marked/Rel-16/23_series/23379/99781d878388c3e0f359b1d6ce14119c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d95a2ce5366086ca437e9a7539344080b2fd4bb4e65762c78de68972da39085e +size 49511 diff --git a/marked/Rel-16/23_series/23379/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/23_series/23379/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efa3f0a8d64aea07c5ba5fbc9c4ba99875a9fb7a --- /dev/null +++ b/marked/Rel-16/23_series/23379/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20c61f8061b4ec3ad1cb4017204625945184511fd0b0d5d7824c19b4082dbae1 +size 67366 diff --git a/marked/Rel-16/23_series/23379/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/23_series/23379/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e6b7f25afbe94272510a2e8b025a50c446ee402 --- /dev/null +++ b/marked/Rel-16/23_series/23379/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:577e5ad05e48e581d6b795258003fcbdddd29f2aa6a929b19a181dce54ce5dcb +size 82441 diff --git a/marked/Rel-16/23_series/23379/9cd7ec4a653f07d02def283cb6f2309e_img.jpg b/marked/Rel-16/23_series/23379/9cd7ec4a653f07d02def283cb6f2309e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb22c894c8045458e96b3dd6a588c1c58c5f9315 --- /dev/null +++ b/marked/Rel-16/23_series/23379/9cd7ec4a653f07d02def283cb6f2309e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd8b8b783d09345df16df2dcbd66c516a9a8f99aa698c3c3b5a1f5093fc00be0 +size 48357 diff --git a/marked/Rel-16/23_series/23379/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/23_series/23379/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f97640d074fe24814f8b900b99ef6d35089164fd --- /dev/null +++ b/marked/Rel-16/23_series/23379/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d76ed59a58f2703ef1edf06b0b6cbda57b19858eb91aefbc9687fcecba2d33f9 +size 85311 diff --git a/marked/Rel-16/23_series/23379/9f50279046b74a4e66a1a0144c3b1d11_img.jpg b/marked/Rel-16/23_series/23379/9f50279046b74a4e66a1a0144c3b1d11_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3009a544d27e9b50eb7d0e0a91a2b1ccfc470fc --- /dev/null +++ b/marked/Rel-16/23_series/23379/9f50279046b74a4e66a1a0144c3b1d11_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff300159e7321d38dca2a7862bf51465c8f0502da650495c8b15391333d03931 +size 44838 diff --git a/marked/Rel-16/23_series/23379/a057800564be3506d2d87b6a4daee25b_img.jpg b/marked/Rel-16/23_series/23379/a057800564be3506d2d87b6a4daee25b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd9cc8e8f5d5c6d92862698eedb5febab26b9b55 --- /dev/null +++ b/marked/Rel-16/23_series/23379/a057800564be3506d2d87b6a4daee25b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46efee4084fb09c9a3776975d79db6dd9a0381e4c357f613cb63ef479abf4121 +size 31293 diff --git a/marked/Rel-16/23_series/23379/a7721892ae499a78173ff3dfdc4e65a9_img.jpg b/marked/Rel-16/23_series/23379/a7721892ae499a78173ff3dfdc4e65a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..610e11dcafeb76a3a8b9f5e627f4bad2a8e477e7 --- /dev/null +++ b/marked/Rel-16/23_series/23379/a7721892ae499a78173ff3dfdc4e65a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19041bee7a3c613b056cced3e5cccd930edb677b495c5d8051436638f24d66f5 +size 71869 diff --git a/marked/Rel-16/23_series/23379/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/23_series/23379/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44dd6240dc180b7b7e61ad724cf71dfb483f1f85 --- /dev/null +++ b/marked/Rel-16/23_series/23379/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e154e26be6257b8b820a409b2034245ad9379ed8fb99576226fb62284d64e2b3 +size 63746 diff --git a/marked/Rel-16/23_series/23379/af90aabfe3c8c65617da060d82bf99c5_img.jpg b/marked/Rel-16/23_series/23379/af90aabfe3c8c65617da060d82bf99c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77b51faa340fa3b4edaeef11eec63cf18c857156 --- /dev/null +++ b/marked/Rel-16/23_series/23379/af90aabfe3c8c65617da060d82bf99c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55b5662f0fc97bf910c17d81f5c9c646b78dc8db19fb235d00308a2f21d0e2fa +size 75381 diff --git a/marked/Rel-16/23_series/23379/b033fab424e6df728345cfa04df83fcc_img.jpg b/marked/Rel-16/23_series/23379/b033fab424e6df728345cfa04df83fcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d79ad43e57fd621fbf88d11a8a8d8d1e2aedf182 --- /dev/null +++ b/marked/Rel-16/23_series/23379/b033fab424e6df728345cfa04df83fcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ed5f0980ab501ab1f766737c782dc7d62cd5cf24e7f3b96bcca0ff2d76ff6a6 +size 116249 diff --git a/marked/Rel-16/23_series/23379/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/23_series/23379/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd852a1dd71c083e619389dfa0a0955a98b3a3e9 --- /dev/null +++ b/marked/Rel-16/23_series/23379/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:645fd35f51c6b3c46d3767cee1fb927138a30b22b5ea622a7b36681bab21c255 +size 127295 diff --git a/marked/Rel-16/23_series/23379/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23379/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0447beba98b495545b42712a7f2b232461d2b94e --- /dev/null +++ b/marked/Rel-16/23_series/23379/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:192e1f85f48f9b8857873252bb75644296babdf105de8247c8b83c16af5d9557 +size 51705 diff --git a/marked/Rel-16/23_series/23379/b4a7906eddfd40aaa750e19e56c94a8b_img.jpg b/marked/Rel-16/23_series/23379/b4a7906eddfd40aaa750e19e56c94a8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..942a7346d9f4eeaeba8460b41a1f885686e45187 --- /dev/null +++ b/marked/Rel-16/23_series/23379/b4a7906eddfd40aaa750e19e56c94a8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7baba54a64e74c4755b6dd6446e6e14d4ded214ff398a3c4a8461b2c1dafe7e4 +size 76054 diff --git a/marked/Rel-16/23_series/23379/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/23_series/23379/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af694ad5ac1bec91d65315625444f96328acec39 --- /dev/null +++ b/marked/Rel-16/23_series/23379/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1fa28310e8275cf48ccba3551a3c927f5f9c4bf6dbeac96488241fb7df33b32 +size 38797 diff --git a/marked/Rel-16/23_series/23379/b5987d63203a5fa601921039922ac520_img.jpg b/marked/Rel-16/23_series/23379/b5987d63203a5fa601921039922ac520_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db675136016a73856235bce0f78f17de94de45fa --- /dev/null +++ b/marked/Rel-16/23_series/23379/b5987d63203a5fa601921039922ac520_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e0b233460052845f0a57b00008bb19e4641de4964237153e5753e4d972633d7 +size 79312 diff --git a/marked/Rel-16/23_series/23379/b87818c8505328b198d035761bbc3f2d_img.jpg b/marked/Rel-16/23_series/23379/b87818c8505328b198d035761bbc3f2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87d8a805536235839f63316ca5de81cca2818d20 --- /dev/null +++ b/marked/Rel-16/23_series/23379/b87818c8505328b198d035761bbc3f2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d55248fb706f06b3d9894aa3f0956c0fcf5f6943b09e86a34df79d0579268e88 +size 55959 diff --git a/marked/Rel-16/23_series/23379/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/Rel-16/23_series/23379/b90144cfbb81a2d610d920240fda689d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09464be45c6983343e303c000b09abe99de8f3f9 --- /dev/null +++ b/marked/Rel-16/23_series/23379/b90144cfbb81a2d610d920240fda689d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dff4a7350ef4276b39bd1fae644b810d1e82466a05e3f786be0f17f466b550a1 +size 45146 diff --git a/marked/Rel-16/23_series/23379/bccc028d0e75bc30c41528056f581545_img.jpg b/marked/Rel-16/23_series/23379/bccc028d0e75bc30c41528056f581545_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7f2ce97bfbad7bfb2e6bd908b55bdc8ded59510 --- /dev/null +++ b/marked/Rel-16/23_series/23379/bccc028d0e75bc30c41528056f581545_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8fe89c623054319b8085c875dfe6f34789d7ff8caacfc87e80be9b5170a6c354 +size 73091 diff --git a/marked/Rel-16/23_series/23379/bdd96f20e71f079cad85240efb3d3f24_img.jpg b/marked/Rel-16/23_series/23379/bdd96f20e71f079cad85240efb3d3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f89681bdaa280338c7f161e08e49f8f29e95c2a2 --- /dev/null +++ b/marked/Rel-16/23_series/23379/bdd96f20e71f079cad85240efb3d3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2e0026aa695ab3d09ee0bbae1ba0491b70344509b816f4ad525ab52b43c47c8 +size 49263 diff --git a/marked/Rel-16/23_series/23379/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg b/marked/Rel-16/23_series/23379/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f7430cadcb3e6bd86978a3162a725c4a87500ed --- /dev/null +++ b/marked/Rel-16/23_series/23379/c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcefb39bb015aedfddf628dcb09eefca25b37ae8073a251af5a71a4342329da0 +size 74051 diff --git a/marked/Rel-16/23_series/23379/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Rel-16/23_series/23379/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23d64995e4efe59f79150378668795c13a8a3561 --- /dev/null +++ b/marked/Rel-16/23_series/23379/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:004758345cf155c2a28cc3772ea3f46873711552b4d21c957996f7c0888b223a +size 75994 diff --git a/marked/Rel-16/23_series/23379/c7e27041e661260fd0c8e89c763bb32e_img.jpg b/marked/Rel-16/23_series/23379/c7e27041e661260fd0c8e89c763bb32e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac3922f664ce9156af94fd6f5689d2ad5da7fe15 --- /dev/null +++ b/marked/Rel-16/23_series/23379/c7e27041e661260fd0c8e89c763bb32e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28ddbf0af44774c72033d2cfa24f2a1f474a228867ceaea025862009e6ce70e3 +size 40640 diff --git a/marked/Rel-16/23_series/23379/d0654bc33a544f31c1cb3e0cd77e0aab_img.jpg b/marked/Rel-16/23_series/23379/d0654bc33a544f31c1cb3e0cd77e0aab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d9ffee1f16e9ef0da278e60f41244eb4aacd594 --- /dev/null +++ b/marked/Rel-16/23_series/23379/d0654bc33a544f31c1cb3e0cd77e0aab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f9aa15868cc897aaf102d888071179fcc6cad6cd8f721c819cd18484f36fed1 +size 36000 diff --git a/marked/Rel-16/23_series/23379/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-16/23_series/23379/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e59c5ad043bc4a92598df847610908767e25cd7b --- /dev/null +++ b/marked/Rel-16/23_series/23379/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23e06975f3cb8f12398dd412947a5c231f9e2db8cda548ecf70d70ee752fd954 +size 67906 diff --git a/marked/Rel-16/23_series/23379/d6c377ae3e619ff992bd3647dbf43593_img.jpg b/marked/Rel-16/23_series/23379/d6c377ae3e619ff992bd3647dbf43593_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7281d412946906ac4308d1549f4eae667a079ff3 --- /dev/null +++ b/marked/Rel-16/23_series/23379/d6c377ae3e619ff992bd3647dbf43593_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ead287fe6e16b0b51ad06e8a103e43eb0898be5851320c405e3115fe824d3969 +size 38831 diff --git a/marked/Rel-16/23_series/23379/d6e51d738a5a275c98682adb31ba5f30_img.jpg b/marked/Rel-16/23_series/23379/d6e51d738a5a275c98682adb31ba5f30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..feb688854952e4bd2c3d895aa8843336df7fd4be --- /dev/null +++ b/marked/Rel-16/23_series/23379/d6e51d738a5a275c98682adb31ba5f30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a798eb17ee9670698ffa041acddf632c23be68fbba1bf457fbe48c2ed876761 +size 46940 diff --git a/marked/Rel-16/23_series/23379/da5a8f834706c8119a47c5eb732feabe_img.jpg b/marked/Rel-16/23_series/23379/da5a8f834706c8119a47c5eb732feabe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1fba1ef61db53ca848e66f55dd3e3ecb50f18cd6 --- /dev/null +++ b/marked/Rel-16/23_series/23379/da5a8f834706c8119a47c5eb732feabe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20d8be49dac01a618154e2c7450fb816950001523c2f5c5b3ba2fb0e7297615b +size 80762 diff --git a/marked/Rel-16/23_series/23379/da90447206621f137780272a2bf807a4_img.jpg b/marked/Rel-16/23_series/23379/da90447206621f137780272a2bf807a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c3f995bac7049710ecca4c940dca943820bab26 --- /dev/null +++ b/marked/Rel-16/23_series/23379/da90447206621f137780272a2bf807a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6f8be83f8ccc089b94bad76aa97a67939512d05ee48de3718601f86d404a459 +size 40939 diff --git a/marked/Rel-16/23_series/23379/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/23_series/23379/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6b033ee945cb4c7757ae48e15792f15d43372cf --- /dev/null +++ b/marked/Rel-16/23_series/23379/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3bc0aec40cc385a004035c5dbf9bdc93c642984145d0bf41dd71f71f1138c72 +size 76995 diff --git a/marked/Rel-16/23_series/23379/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/Rel-16/23_series/23379/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bd99365ba52aa9405d2993c02d378215535706e --- /dev/null +++ b/marked/Rel-16/23_series/23379/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d445ada142e98b41e7efe1474ac76eb2d6259f9d9d469ffba800025b32335c3 +size 83989 diff --git a/marked/Rel-16/23_series/23379/dc37a040cf9e2add7488c7c37cbf3687_img.jpg b/marked/Rel-16/23_series/23379/dc37a040cf9e2add7488c7c37cbf3687_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..513407001a14b3b8155cea43a70f401f40c9f10b --- /dev/null +++ b/marked/Rel-16/23_series/23379/dc37a040cf9e2add7488c7c37cbf3687_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a62be92a2bb2591cf4e6942e234d6e07fc89eb95ca3a5c5209c53c2ddfbeb76 +size 89580 diff --git a/marked/Rel-16/23_series/23379/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23379/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60316720806635c073675ed731311bdd79e1905f --- /dev/null +++ b/marked/Rel-16/23_series/23379/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fdd5cb65aada50806662a7fece262095e92d17a86383e3010b08ac6b6cb064b +size 86358 diff --git a/marked/Rel-16/23_series/23379/de98d4c97665a29427651680af184ff4_img.jpg b/marked/Rel-16/23_series/23379/de98d4c97665a29427651680af184ff4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b39665a46eeec5eca254dfc1a3de809683e70d5e --- /dev/null +++ b/marked/Rel-16/23_series/23379/de98d4c97665a29427651680af184ff4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be205ff936280d1d608c80c722a9905924d28b8f9726d79af1af5643972f67fb +size 52523 diff --git a/marked/Rel-16/23_series/23379/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/23_series/23379/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b91155939d12008910fc5f3f9d11331c06233e6 --- /dev/null +++ b/marked/Rel-16/23_series/23379/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cea5eaad300ef3952fd416bb44441c9a510ff8e94dabb5571cffbf567ed45e2 +size 41828 diff --git a/marked/Rel-16/23_series/23379/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23379/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f9bac330175f9ed25ad516b5c14ecbbf80c1300 --- /dev/null +++ b/marked/Rel-16/23_series/23379/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40b1864fe249d9381ff02e886df9a5bca34bb0d363d280ca17c27a3a589f8bef +size 46790 diff --git a/marked/Rel-16/23_series/23379/e5293502d8d5885d71defe1150aa12fc_img.jpg b/marked/Rel-16/23_series/23379/e5293502d8d5885d71defe1150aa12fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48c26dbc8590235c48d4ce5944f96dafb0547ea5 --- /dev/null +++ b/marked/Rel-16/23_series/23379/e5293502d8d5885d71defe1150aa12fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:534ae1025c76e88239907904f1075902b0d356362dbe8835aa27b71d4c83ee78 +size 38575 diff --git a/marked/Rel-16/23_series/23379/e53e04cbd5986eeb9e7faa71b3c9bb35_img.jpg b/marked/Rel-16/23_series/23379/e53e04cbd5986eeb9e7faa71b3c9bb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..921571c6d95508ad91cf24e0cbe4624739d39ee5 --- /dev/null +++ b/marked/Rel-16/23_series/23379/e53e04cbd5986eeb9e7faa71b3c9bb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86b48a130b6e0d5f9f620ca17e38db046cf161ae942b043bbb4e892529fb7bc5 +size 58620 diff --git a/marked/Rel-16/23_series/23379/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/23_series/23379/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ec85bbda7f2d915c8d4bb9fac4de6a20d421856 --- /dev/null +++ b/marked/Rel-16/23_series/23379/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1acd2147c4fde6c6ce7a5b65093f478c870f0aaf824b295159ec3101d6982db +size 72209 diff --git a/marked/Rel-16/23_series/23379/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/Rel-16/23_series/23379/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6598f24d28d2ef36bd5c1a6c1256a09d1bcbc69e --- /dev/null +++ b/marked/Rel-16/23_series/23379/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df1010ba641532f8df08d793fe50c508954b4c51d2ee65ff7af2b76beda066b6 +size 59044 diff --git a/marked/Rel-16/23_series/23379/e94cbc0895c6914a2bb53f150ab7495e_img.jpg b/marked/Rel-16/23_series/23379/e94cbc0895c6914a2bb53f150ab7495e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f985ab7d9b6d2949d680555e8e0c21ce942da302 --- /dev/null +++ b/marked/Rel-16/23_series/23379/e94cbc0895c6914a2bb53f150ab7495e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59f6adb2fe5c6cc7aaf16bd1929edf5c4bfdd8a6249e843545c86f8100aea099 +size 52594 diff --git a/marked/Rel-16/23_series/23379/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg b/marked/Rel-16/23_series/23379/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9297293dca9e289831d3fb5deccff179cc2bb2b7 --- /dev/null +++ b/marked/Rel-16/23_series/23379/eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1c363e0602bbeb0c9c7e1515e44fb56ba2e9a301aa764d7b529d1c50bede133 +size 50279 diff --git a/marked/Rel-16/23_series/23379/f06d7a2fad72d80fe12fca1b65fc805b_img.jpg b/marked/Rel-16/23_series/23379/f06d7a2fad72d80fe12fca1b65fc805b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd9d87db71fa36338b6645ad148f469b338b0051 --- /dev/null +++ b/marked/Rel-16/23_series/23379/f06d7a2fad72d80fe12fca1b65fc805b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de1e1489dca10b547cf80fd5bd1add2dedd4f81a6d64f5154ebd4f69db37c083 +size 91090 diff --git a/marked/Rel-16/23_series/23379/f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg b/marked/Rel-16/23_series/23379/f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19edb4c010b4d52802d65c2043f3992a0ebc8ee8 --- /dev/null +++ b/marked/Rel-16/23_series/23379/f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb43e0bc64889b33036dad6016386d15a53a76f55aad6d9aacd53359d52ef84f +size 70120 diff --git a/marked/Rel-16/23_series/23379/f43d225d8fed2845b8d7e5afecbfe636_img.jpg b/marked/Rel-16/23_series/23379/f43d225d8fed2845b8d7e5afecbfe636_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..345b483deeeaeebdf414227e1886b5ea99dba910 --- /dev/null +++ b/marked/Rel-16/23_series/23379/f43d225d8fed2845b8d7e5afecbfe636_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:075adb13b099cb6f262849e3c1426604afdf9dbfeb208e6de542db88cfe003b1 +size 54471 diff --git a/marked/Rel-16/23_series/23379/f9873201604e723ae0bafb7e389ef619_img.jpg b/marked/Rel-16/23_series/23379/f9873201604e723ae0bafb7e389ef619_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c53a536819d320be44f85468ff206eb0c6bd8519 --- /dev/null +++ b/marked/Rel-16/23_series/23379/f9873201604e723ae0bafb7e389ef619_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d57979acaf3aa58387bffdadc0ede6079f64426d128ba2b1f60036058e34c27 +size 44489 diff --git a/marked/Rel-16/23_series/23379/fc3e2b49a9f850951570e502393b697f_img.jpg b/marked/Rel-16/23_series/23379/fc3e2b49a9f850951570e502393b697f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f21216cc14605f3bdae4a26635524203fabcd7b --- /dev/null +++ b/marked/Rel-16/23_series/23379/fc3e2b49a9f850951570e502393b697f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5ad27cf8425af03ae51c4603d9f5be096d5cadb26755691dafa6cdb168152c5 +size 74100 diff --git a/marked/Rel-16/23_series/23379/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-16/23_series/23379/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eff9078fdc187871316b8064c00bf6328658fdef --- /dev/null +++ b/marked/Rel-16/23_series/23379/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fdaaba491bb8dd1660f2964ccfbcc229a79bb02dd0eb3b2dd92708e32245df0 +size 69778 diff --git a/marked/Rel-16/23_series/23379/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23379/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f259fe2db2aa8dd7a4aeac8057720905c1764e1 --- /dev/null +++ b/marked/Rel-16/23_series/23379/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7232d6d1f620cbfbb955bb8e2874b7a99744ef85bcb62eb35873b8eda44daab +size 35047 diff --git a/marked/Rel-16/23_series/23379/ff87509cc2b267501d910a2d9f9054ac_img.jpg b/marked/Rel-16/23_series/23379/ff87509cc2b267501d910a2d9f9054ac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..608e345353620afed2651bc7d0e4522b2eaca9cc --- /dev/null +++ b/marked/Rel-16/23_series/23379/ff87509cc2b267501d910a2d9f9054ac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be0a3d333a7232e0ff286b102c8753a36cdc1097b72ad41c739a856f3783035e +size 53869 diff --git a/marked/Rel-16/23_series/23379/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Rel-16/23_series/23379/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c89b4fb50368f6f34c10b558b41645a2904c14d --- /dev/null +++ b/marked/Rel-16/23_series/23379/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6f98cc087d7dfd8e041decfd9bcf96473e01d29794020f151142ba695085fee3 +size 58770 diff --git a/marked/Rel-16/23_series/23379/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/marked/Rel-16/23_series/23379/ffe0fef452a0ae9a20253c319c54e13c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c31cdcff29ef1e95309429768e5b02c7f46d2da0 --- /dev/null +++ b/marked/Rel-16/23_series/23379/ffe0fef452a0ae9a20253c319c54e13c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37256f01136e5050eebaad0466c7adaff7b4f18abbc69a50d1d0665f2a9b9357 +size 119774 diff --git a/marked/Rel-16/23_series/23379/raw.md b/marked/Rel-16/23_series/23379/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..283d5636c06a38b1913f2fe66c892049ba0f36de --- /dev/null +++ b/marked/Rel-16/23_series/23379/raw.md @@ -0,0 +1,9221 @@ +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 11 | +| 1 Scope..... | 12 | +| 2 References..... | 12 | +| 3 Definitions, symbols and abbreviations..... | 13 | +| 3.1 Definitions..... | 13 | +| 3.2 Symbols..... | 14 | +| 3.3 Abbreviations ..... | 15 | +| 4 Introduction..... | 16 | +| 5 Architectural requirements..... | 16 | +| 5.1 Media routing requirements ..... | 16 | +| 5.2 Requirements for user identity management..... | 16 | +| 5.3 MCPTT group affiliation and MCPTT group de-affiliation ..... | 17 | +| 5.4 MCPTT call requirements..... | 17 | +| 5.4.1 General ..... | 17 | +| 5.4.2 Group call requirements ..... | 17 | +| 5.5 GCS AS requirements for the MCPTT service..... | 17 | +| 5.6 Group selection ..... | 17 | +| 5.7 Bearer management..... | 17 | +| 5.7.1 General ..... | 17 | +| 5.7.2 EPS bearer considerations ..... | 17 | +| 5.7.2.1 Void ..... | 17 | +| 5.7.2.2 Void ..... | 17 | +| 5.7.3 EPS unicast bearer considerations for MCPTT ..... | 17 | +| 5.7.4 MBMS bearer management..... | 18 | +| 5.8 MCPTT system interconnect requirements..... | 18 | +| 6 Involved business relationships ..... | 18 | +| 7 Functional model..... | 18 | +| 7.1 General ..... | 18 | +| 7.2 Description of the planes..... | 19 | +| 7.3 Functional model description..... | 19 | +| 7.3.1 On-network functional model..... | 19 | +| 7.3.2 Off-network functional model..... | 20 | +| 7.4 Functional entities description ..... | 21 | +| 7.4.1 General ..... | 21 | +| 7.4.2 Application plane of MCPTT service..... | 21 | +| 7.4.2.1 General..... | 21 | +| 7.4.2.2 Common services core..... | 21 | +| 7.4.2.3 MCPTT application service ..... | 21 | +| 7.4.2.3.1 MCPTT client..... | 21 | +| 7.4.2.3.2 MCPTT server..... | 21 | +| 7.4.2.3.3 Floor participant ..... | 23 | +| 7.4.2.3.4 Floor control server ..... | 23 | +| 7.4.2.3.5 Media distribution function..... | 23 | +| 7.4.2.3.6 Media mixer ..... | 23 | +| 7.4.2.3.7 MCPTT user database..... | 24 | +| 7.4.2.3.8 MC gateway server..... | 24 | +| 7.4.3 Signalling control plane..... | 24 | +| 7.5 Reference points..... | 24 | +| 7.5.1 General reference point principle ..... | 24 | +| 7.5.2 Application plane of MCPTT service..... | 24 | +| 7.5.2.1 General..... | 24 | +| 7.5.2.2 Reference point MCPTT-1 (between the MCPTT client and the MCPTT server)..... | 24 | +| 7.5.2.3 Reference point MCPTT-2 (between the MCPTT server and the MCPTT user database) ..... | 25 | +| 7.5.2.4 Reference point MCPTT-3 (between the MCPTT server and the MCPTT server and between the MCPTT server and the MC gateway server)..... | 25 | + +| | | | +|-------------|---------------------------------------------------------------------------------------------------------------------|----| +| 7.5.2.5 | Reference point MCPTT-4 (unicast between the floor control server and the floor participant)..... | 25 | +| 7.5.2.6 | Reference point MCPTT-5 (between the media distribution function and the EPS) ..... | 25 | +| 7.5.2.7 | Reference point MCPTT-6 (between the MCPTT server and the EPS)..... | 25 | +| 7.5.2.8 | Reference point MCPTT-7 (unicast between the media distribution function and the media mixer)..... | 26 | +| 7.5.2.9 | Reference point MCPTT-8 (multicast between the media distribution function and the media mixer)..... | 26 | +| 7.5.2.10 | Reference point MCPTT-9 (multicast between the floor control server and the floor participant) ..... | 26 | +| 7.5.2.11 | Reference point IWF-1 (between the MCPTT server and the interworking function to legacy systems) ..... | 26 | +| 7.5.2.12 | Reference points of common services core used in the MCPTT service ..... | 26 | +| 7.5.2.13 | Reference point MCPTT-10 (between the MC gateway server and the MC gateway server in a different MCPTT system)..... | 26 | +| 8 | Identities..... | 26 | +| 9 | Application of functional model to deployments..... | 26 | +| 10 | Procedures and information flows ..... | 27 | +| 10.1 | MCPTT service configuration..... | 27 | +| 10.2 | User authentication and authorization for MCPTT service ..... | 27 | +| 10.3 | Affiliation and de-affiliation to/from MCPTT group(s) ..... | 28 | +| 10.3a | Activation and de-activation of/from functional alias(es)..... | 28 | +| 10.4 | MCPTT group selection..... | 28 | +| 10.4.1 | General ..... | 28 | +| 10.4.2 | Information flows for group selection..... | 28 | +| 10.4.2.1 | Group selection change request..... | 28 | +| 10.4.2.2 | Group selection change response..... | 28 | +| 10.4.2.3 | Group selection change notification ..... | 29 | +| 10.4.3 | Authorized user remotely changes another MCPTT user's selected MCPTT group – mandatory mode.... | 29 | +| 10.5 | Pre-established session (on-network)..... | 30 | +| 10.5.1 | General ..... | 30 | +| 10.5.2 | Information flows for pre-established session..... | 30 | +| 10.5.2.1 | Pre-established session establishment ..... | 30 | +| 10.5.2.2 | Pre-established session modification ..... | 31 | +| 10.5.2.3 | Pre-established session release - client initiated..... | 31 | +| 10.5.2.4 | Pre-established session release - server initiated..... | 32 | +| 10.5.2.5 | Pre-established session call connect request..... | 32 | +| 10.5.2.6 | Pre-established session call disconnect request ..... | 32 | +| 10.5.3 | Procedures ..... | 33 | +| 10.5.3.1 | General..... | 33 | +| 10.5.3.2 | Call connect and disconnect procedures using pre-established session ..... | 33 | +| 10.5.3.2.1 | Call connect over unicast ..... | 33 | +| 10.5.3.2.2 | Call disconnect over unicast..... | 34 | +| 10.6 | Group call..... | 34 | +| 10.6.1 | General ..... | 34 | +| 10.6.2 | On-network group call..... | 34 | +| 10.6.2.1 | General..... | 34 | +| 10.6.2.2 | Information flows for group call in on-network ..... | 34 | +| 10.6.2.2.1 | MCPTT emergency group call request ..... | 34 | +| 10.6.2.2.1a | MCPTT emergency group call response..... | 35 | +| 10.6.2.2.2 | MCPTT in-progress emergency group state cancel request..... | 35 | +| 10.6.2.2.2a | MCPTT in-progress emergency group state cancel response ..... | 36 | +| 10.6.2.2.3 | MCPTT emergency alert request ..... | 36 | +| 10.6.2.2.3a | MCPTT emergency alert response..... | 36 | +| 10.6.2.2.3b | MCPTT emergency alert area notification..... | 37 | +| 10.6.2.2.4 | MCPTT emergency alert cancel request ..... | 37 | +| 10.6.2.2.4a | MCPTT emergency alert cancel response..... | 37 | +| 10.6.2.2.5 | MCPTT imminent peril group call request ..... | 38 | +| 10.6.2.2.5a | MCPTT imminent peril group call response..... | 38 | +| 10.6.2.2.6 | MCPTT in-progress imminent peril group state cancel request ..... | 38 | +| 10.6.2.2.6a | MCPTT in-progress imminent peril group state cancel response..... | 39 | +| 10.6.2.2.7 | Group call request (MCPTT client – MCPTT server) ..... | 39 | + +| | | | +|--------------|---------------------------------------------------------------------------------------------------------------------------------------|----| +| 10.6.2.2.8 | Group call request (MCPTT server – MCPTT server) ..... | 39 | +| 10.6.2.2.9 | Group call request (MCPTT server – MCPTT client) ..... | 40 | +| 10.6.2.2.10 | Group call response (MCPTT server – MCPTT client)..... | 40 | +| 10.6.2.2.11 | Group call response (MCPTT server – MCPTT server)..... | 41 | +| 10.6.2.2.12 | Group call response (MCPTT client – MCPTT server)..... | 41 | +| 10.6.2.2.13 | Group call notify (MCPTT server – MCPTT client) ..... | 41 | +| 10.6.2.2.14 | Group call release request (MCPTT server – MCPTT client) ..... | 41 | +| 10.6.2.2.14a | Group call release request (MCPTT client – MCPTT server) ..... | 42 | +| 10.6.2.2.15 | Group call release request (MCPTT server – MCPTT server) ..... | 42 | +| 10.6.2.2.16 | Group call release response (MCPTT client – MCPTT server)..... | 42 | +| 10.6.2.2.17 | Group call release response (MCPTT server – MCPTT server)..... | 43 | +| 10.6.2.2.18 | Group call rejoin request (MCPTT client – MCPTT server)..... | 43 | +| 10.6.2.2.19 | Group call rejoin response (MCPTT server – MCPTT client)..... | 43 | +| 10.6.2.2.20 | Group join request..... | 44 | +| 10.6.2.2.21 | Group join response ..... | 44 | +| 10.6.2.2.22 | Group call leave request (MCPTT server – MCPTT client)..... | 44 | +| 10.6.2.2.22a | Group call leave request (MCPTT client – MCPTT server)..... | 45 | +| 10.6.2.2.23 | Group call leave response (MCPTT client – MCPTT server) ..... | 45 | +| 10.6.2.2.23a | Group call leave response (MCPTT server – MCPTT client) ..... | 45 | +| 10.6.2.2.24 | Group interrogate request (MCPTT server – MCPTT server)..... | 46 | +| 10.6.2.2.25 | Group interrogate response (MCPTT server – MCPTT server) ..... | 46 | +| 10.6.2.2.26 | Group-broadcast group call request (MCPTT client – MCPTT server) ..... | 46 | +| 10.6.2.2.27 | Group-broadcast group call request (MCPTT server – MCPTT client) ..... | 47 | +| 10.6.2.2.28 | Group-broadcast group call response (MCPTT client – MCPTT server)..... | 47 | +| 10.6.2.2.29 | Group-broadcast group call response (MCPTT server – MCPTT client)..... | 48 | +| 10.6.2.2.30 | Group-broadcast group call release request (MCPTT client – MCPTT server) ..... | 48 | +| 10.6.2.2.31 | Group-broadcast group call release request (MCPTT server – MCPTT client)..... | 48 | +| 10.6.2.2.32 | Group-broadcast group call release response (MCPTT server – MCPTT client)..... | 48 | +| 10.6.2.2.33 | Group-broadcast group call release response (MCPTT client – MCPTT server)..... | 49 | +| 10.6.2.2.34 | Preconfigured regroup request (MCPTT client – MCPTT server) ..... | 49 | +| 10.6.2.2.35 | Preconfigured regroup request (MCPTT server – MCPTT client) ..... | 49 | +| 10.6.2.2.36 | Preconfigured regroup request (MCPTT server – MCPTT server) ..... | 50 | +| 10.6.2.2.37 | Preconfigured regroup response (MCPTT client – MCPTT server)..... | 50 | +| 10.6.2.2.38 | Preconfigured regroup response (MCPTT server – MCPTT client)..... | 50 | +| 10.6.2.2.39 | Preconfigured regroup response (MCPTT server – MCPTT server)..... | 51 | +| 10.6.2.2.40 | Preconfigured regroup cancel request (MCPTT client – MCPTT server)..... | 51 | +| 10.6.2.2.41 | Preconfigured regroup cancel request (MCPTT server – MCPTT client)..... | 51 | +| 10.6.2.2.42 | Preconfigured regroup cancel request (MCPTT server – MCPTT server)..... | 51 | +| 10.6.2.2.43 | Preconfigured regroup cancel response (MCPTT client – MCPTT server)..... | 52 | +| 10.6.2.2.44 | Preconfigured regroup cancel response (MCPTT server – MCPTT client)..... | 52 | +| 10.6.2.2.45 | Preconfigured regroup cancel response (MCPTT server – MCPTT server)..... | 52 | +| 10.6.2.2.46 | Preconfigured regroup reject (MCPTT server – MCPTT client)..... | 52 | +| 10.6.2.2.47 | Preconfigured regroup reject (MCPTT server – MCPTT server)..... | 53 | +| 10.6.2.3 | Group call within one MCPTT system ..... | 53 | +| 10.6.2.3.1 | Group call models ..... | 53 | +| 10.6.2.3.1.1 | Pre-arranged group call ..... | 53 | +| 10.6.2.3.1.2 | Chat group call ..... | 58 | +| 10.6.2.3.2 | Exiting group call due to de-affiliation ..... | 64 | +| 10.6.2.3.3 | MCPTT user leaving a group call ..... | 65 | +| 10.6.2.4 | Group call involving groups from multiple MCPTT systems ..... | 66 | +| 10.6.2.4.1 | Group call for non-broadcast temporary groups across multiple MCPTT systems ..... | 66 | +| 10.6.2.4.1.1 | Group call setup..... | 66 | +| 10.6.2.4.1.2 | Group call release ..... | 69 | +| 10.6.2.4.2 | Group call for non-broadcast temporary group formed by group regroup procedure involving multiple MCPTT systems via trusted mode..... | 70 | +| 10.6.2.4.3 | Group call for an MCPTT group defined in the partner MCPTT system ..... | 72 | +| 10.6.2.4.3.1 | Pre-arranged group call setup procedure – initiating side ..... | 72 | +| 10.6.2.4.3.2 | Pre-arranged group call setup – terminating side ..... | 73 | +| 10.6.2.4.3.3 | Chat group call setup..... | 73 | +| 10.6.2.4.4 | Merging of groups involving multiple MCPTT systems ..... | 75 | +| 10.6.2.5 | Broadcast group call ..... | 76 | +| 10.6.2.5.1 | General ..... | 76 | + +| | | | +|---------------|-------------------------------------------------------------------------------------------------------------------|-----| +| 10.6.2.5.2 | Common broadcast group call procedure..... | 76 | +| 10.6.2.5.2.1 | Group-broadcast group call procedure ..... | 77 | +| 10.6.2.5.2.2 | Group-broadcast group call procedure when a subordinate group has an on-going MCPTT
emergency group call ..... | 79 | +| 10.6.2.5.2.3 | Group-broadcast group call release procedure ..... | 80 | +| 10.6.2.5.2.4 | Server-initiated broadcast group call release procedure..... | 81 | +| 10.6.2.5.3 | Void..... | 82 | +| 10.6.2.5.4 | Group call for broadcast temporary groups across multiple MCPTT systems ..... | 82 | +| 10.6.2.6 | Emergency and imminent peril procedures ..... | 83 | +| 10.6.2.6.1 | MCPTT emergency group call..... | 83 | +| 10.6.2.6.1.1 | MCPTT emergency group call commencement..... | 83 | +| 10.6.2.6.1.2 | MCPTT group call upgraded to an MCPTT emergency group call..... | 85 | +| 10.6.2.6.1.3 | MCPTT in-progress emergency group state cancel ..... | 87 | +| 10.6.2.6.2 | MCPTT imminent peril group call..... | 89 | +| 10.6.2.6.2.1 | MCPTT imminent peril group call commencement..... | 89 | +| 10.6.2.6.2.2 | Imminent peril group call upgrade ..... | 91 | +| 10.6.2.6.2.3 | MCPTT in-progress imminent peril group state cancel ..... | 93 | +| 10.6.2.6.3 | MCPTT emergency alert..... | 94 | +| 10.6.2.6.3.1 | MCPTT emergency alert initiation..... | 94 | +| 10.6.2.6.3.2 | MCPTT emergency alert cancel..... | 96 | +| 10.6.2.6.3.3 | Entering MCPTT emergency alert area..... | 97 | +| 10.6.2.6.3.4 | Leaving MCPTT emergency alert area ..... | 99 | +| 10.6.2.7 | Location of current talker ..... | 100 | +| 10.6.2.8 | Void ..... | 101 | +| 10.6.2.8.1 | Void..... | 101 | +| 10.6.2.8.2 | Void..... | 101 | +| 10.6.2.8.3 | Void..... | 101 | +| 10.6.2.9 | Group regroup with preconfigured group ..... | 101 | +| 10.6.2.9.1 | General ..... | 101 | +| 10.6.2.9.2 | Regroup procedures in single MCPTT system ..... | 101 | +| 10.6.2.9.2.1 | Regroup formation using preconfigured group in single MCPTT system ..... | 101 | +| 10.6.2.9.2.2 | Regroup cancellation in single MCPTT system..... | 103 | +| 10.6.2.9.3 | Regroup procedures in multiple MCPTT systems ..... | 104 | +| 10.6.2.9.3.1 | Regroup formation using preconfigured group in multiple MCPTT systems..... | 104 | +| 10.6.2.9.3.2 | Regroup cancellation using preconfigured group in multiple MCPTT systems ..... | 106 | +| 10.6.2.9.3.3 | Regroup rejection using preconfigured group in multiple MCPTT systems ..... | 108 | +| 10.6.2.9.4 | Adding newly affiliated user to preconfigured group regroup..... | 109 | +| 10.6.2.9.5 | Preconfigured regroup update procedures..... | 110 | +| 10.6.2.9.5.1 | MCPTT client PTTs on MCPTT group during an in-progress preconfigured group
regroup..... | 110 | +| 10.6.2.9.5.2 | MCPTT client PTTs on preconfigured regroup group after group regroup has been
cancelled..... | 111 | +| 10.6.2.10 | User regroup using group creation procedure..... | 112 | +| 10.6.2.10.1 | General ..... | 112 | +| 10.6.2.10.2 | Temporary group creation and broadcast group call by authorized user ..... | 113 | +| 10.6.2.10.3 | Temporary group deletion by authorized user ..... | 113 | +| 10.6.2.11 | Broadcast group regroup call using preconfigured group ..... | 114 | +| 10.6.2.11.1 | General ..... | 114 | +| 10.6.2.11.2 | Broadcast group regroup call procedure using preconfigured group in a single MCPTT
system..... | 114 | +| 10.6.2.12 | User regroup with preconfigured group..... | 115 | +| 10.6.2.12.1 | General ..... | 115 | +| 10.6.2.12.2 | User regroup procedures in a single MCPTT system ..... | 115 | +| 10.6.2.12.2.1 | User regroup formation in a single MCPTT system ..... | 115 | +| 10.6.2.12.2.2 | User regroup cancellation in single MCPTT system..... | 117 | +| 10.6.3 | Off-network group call ..... | 118 | +| 10.6.3.1 | General..... | 118 | +| 10.6.3.2 | Information flows for group call in off-network ..... | 118 | +| 10.6.3.2.1 | Group call announcement..... | 118 | +| 10.6.3.2.2 | MCPTT upgrade to emergency call ..... | 119 | +| 10.6.3.2.3 | MCPTT emergency group state cancel ..... | 119 | +| 10.6.3.2.4 | Response..... | 119 | + +| | | | +|--------------|-----------------------------------------------------------------------------------------------------|-----| +| 10.6.3.2.5 | MCPTT emergency alert announcement..... | 120 | +| 10.6.3.2.6 | MCPTT emergency alert cancel announcement ..... | 120 | +| 10.6.3.2.7 | MCPTT upgrade to imminent peril call ..... | 120 | +| 10.6.3.2.8 | MCPTT imminent peril group call cancel..... | 120 | +| 10.6.3.3 | Group call setup ..... | 121 | +| 10.6.3.4 | Passive join to group call ..... | 122 | +| 10.6.3.5 | Join to ongoing group call when new entry member initiates the call with on-going group call id.... | 123 | +| 10.6.3.6 | Immediate group call announcement to join an ongoing group call..... | 124 | +| 10.6.3.7 | Group call release due to inactivity ..... | 125 | +| 10.6.3.8 | Broadcast group call ..... | 125 | +| 10.6.3.9 | Emergency and imminent peril procedures ..... | 126 | +| 10.6.3.9.1 | Emergency group call..... | 126 | +| 10.6.3.9.2 | MCPTT imminent peril..... | 127 | +| 10.6.3.9.3 | MCPTT emergency alert..... | 127 | +| 10.6.3.9.3.1 | MCPTT emergency alert initiation..... | 127 | +| 10.6.3.9.3.2 | MCPTT emergency alert cancel..... | 129 | +| 10.7 | Private call..... | 130 | +| 10.7.1 | General ..... | 130 | +| 10.7.2 | Private call in on-network ..... | 130 | +| 10.7.2.1 | Information flows for private call in on-network ..... | 130 | +| 10.7.2.1.1 | MCPTT private call request (MCPTT client to MCPTT server)..... | 130 | +| 10.7.2.1.2 | MCPTT private call request (MCPTT server to MCPTT server)..... | 130 | +| 10.7.2.1.2a | MCPTT private call request (MCPTT server to MCPTT client)..... | 131 | +| 10.7.2.1.3 | MCPTT private call response (MCPTT client to MCPTT server)..... | 131 | +| 10.7.2.1.4 | MCPTT private call response..... | 132 | +| 10.7.2.1.4a | MCPTT private call end request ..... | 132 | +| 10.7.2.1.4b | MCPTT private call end response..... | 132 | +| 10.7.2.1.5 | MCPTT emergency private call request (MCPTT client to MCPTT server) ..... | 133 | +| 10.7.2.1.5a | MCPTT emergency private call request (MCPTT server to MCPTT client) ..... | 133 | +| 10.7.2.1.6 | MCPTT progress indication..... | 133 | +| 10.7.2.1.7 | MCPTT ringing..... | 134 | +| 10.7.2.2 | Private call within one MCPTT system..... | 134 | +| 10.7.2.2.1 | Private call setup in automatic commencement mode ..... | 134 | +| 10.7.2.2.2 | Private call setup in manual commencement mode ..... | 136 | +| 10.7.2.2.2.1 | Description ..... | 136 | +| 10.7.2.2.2.2 | Procedure ..... | 136 | +| 10.7.2.2.3 | Private call release..... | 138 | +| 10.7.2.2.3.1 | Client initiated ..... | 138 | +| 10.7.2.2.3.2 | Server initiated..... | 139 | +| 10.7.2.3 | Private call within several MCPTT systems..... | 140 | +| 10.7.2.3.1 | Private call setup in automatic commencement mode – MCPTT users in multiple MCPTT systems ..... | 140 | +| 10.7.2.3.2 | Private call setup in manual commencement mode – MCPTT users in multiple MCPTT systems ..... | 142 | +| 10.7.2.3.3 | Private call release – MCPTT users in multiple MCPTT systems..... | 144 | +| 10.7.2.4 | MCPTT emergency private call..... | 144 | +| 10.7.2.4.1 | MCPTT emergency private call commencement..... | 144 | +| 10.7.2.4.2 | MCPTT private call emergency upgrade ..... | 146 | +| 10.7.3 | Private call in off-network..... | 147 | +| 10.7.3.1 | Information flows for private call in off-network..... | 147 | +| 10.7.3.1.1 | Call setup request ..... | 147 | +| 10.7.3.1.2 | Call setup response..... | 147 | +| 10.7.3.1.3 | Call release request..... | 147 | +| 10.7.3.1.4 | Call release response ..... | 147 | +| 10.7.3.2 | Use of ProSe capability for private call ..... | 148 | +| 10.7.3.3 | Private call setup in automatic commencement mode..... | 148 | +| 10.7.3.4 | Private call setup in manual commencement mode..... | 149 | +| 10.7.3.5 | Private call release ..... | 150 | +| 10.7.3.6 | MCPTT emergency private call..... | 151 | +| 10.7.4 | MCPTT private call call-back request..... | 152 | +| 10.7.4.1 | Information flows for MCPTT private call call-back request ..... | 152 | +| 10.7.4.1.1 | MCPTT private call call-back request ..... | 152 | + +| | | | +|--------------|---------------------------------------------------------------------------------------------------------------------------|-----| +| 10.7.4.1.2 | MCPTT private call call-back response..... | 152 | +| 10.7.4.1.3 | MCPTT private call call-back cancel request ..... | 152 | +| 10.7.4.1.4 | MCPTT private call call-back cancel response..... | 152 | +| 10.7.4.2 | MCPTT private call call-back request within one MCPTT system..... | 153 | +| 10.7.4.3 | MCPTT private call call-back cancel request within one MCPTT system ..... | 154 | +| 10.7.4.4 | MCPTT private call call-back request fulfillment within one MCPTT system ..... | 155 | +| 10.7.5 | MCPTT call forwarding for private calls ..... | 155 | +| 10.7.5.1 | General..... | 155 | +| 10.7.5.1.1 | Void..... | 156 | +| 10.7.5.1.2 | MCPTT private call forwarding request (MCPTT server to MCPTT client) ..... | 156 | +| 10.7.5.1.3 | MCPTT private call forwarding response (MCPTT client to MCPTT server)..... | 156 | +| 10.7.5.2 | Procedures ..... | 156 | +| 10.7.5.2.1 | Update configuration for MCPTT private call forwarding ..... | 156 | +| 10.7.5.2.2 | MCPTT immediate private call forwarding..... | 156 | +| 10.7.5.2.3 | MCPTT private call forwarding no answer..... | 158 | +| 10.7.5.2.4 | Handling of multiple MCPTT private call forwardings..... | 160 | +| 10.8 | Simultaneous session for MCPTT calls (on-network)..... | 160 | +| 10.8.1 | General ..... | 160 | +| 10.9 | Floor control..... | 161 | +| 10.9.1 | Floor control for on-network MCPTT service ..... | 161 | +| 10.9.1.1 | General..... | 161 | +| 10.9.1.2 | Information flows for floor control for on-network..... | 161 | +| 10.9.1.2.1 | General ..... | 161 | +| 10.9.1.2.2 | Floor request..... | 161 | +| 10.9.1.2.3 | Floor granted ..... | 161 | +| 10.9.1.2.4 | Floor rejected..... | 162 | +| 10.9.1.2.5 | Floor request cancel ..... | 162 | +| 10.9.1.2.6 | Floor request cancel response ..... | 162 | +| 10.9.1.2.7 | Floor request cancel notify..... | 163 | +| 10.9.1.2.8 | Floor idle ..... | 163 | +| 10.9.1.2.9 | Floor release ..... | 163 | +| 10.9.1.2.9a | Multi-talker floor release..... | 164 | +| 10.9.1.2.10 | Floor taken..... | 164 | +| 10.9.1.2.10a | Multi-talker floor taken ..... | 164 | +| 10.9.1.2.11 | Floor revoked ..... | 164 | +| 10.9.1.2.12 | Floor acknowledgement..... | 165 | +| 10.9.1.2.13 | Queue position request..... | 165 | +| 10.9.1.2.14 | Queue position info ..... | 165 | +| 10.9.1.2.15 | Unicast media stop request..... | 166 | +| 10.9.1.2.16 | Unicast media resume request..... | 166 | +| 10.9.1.3 | Floor control within one MCPTT system..... | 166 | +| 10.9.1.3.1 | Floor request, floor granted and floor taken during an MCPTT session..... | 166 | +| 10.9.1.3.1a | Floor request, floor granted and multi-talker floor taken during an MCPTT session enhanced with multi-talker control..... | 168 | +| 10.9.1.3.2 | Floor override ..... | 169 | +| 10.9.1.3.2.1 | Floor override using floor revoked (also floor rejected) during an MCPTT session ..... | 169 | +| 10.9.1.3.2.2 | Floor override without using floor revoked during an MCPTT session ..... | 171 | +| 10.9.1.3.2.3 | Floor override using floor revoked (also floor rejected) during an MCPTT session enhanced with multi-talker control..... | 172 | +| 10.9.1.3.2.4 | Floor release during an MCPTT session enhanced with multi-talker control..... | 174 | +| 10.9.1.3.3 | Queue position during an MCPTT session ..... | 175 | +| 10.9.1.3.4 | Floor request cancellation from the floor request queue..... | 176 | +| 10.9.1.3.4.1 | Floor request cancellation from the queue – MCPTT user initiated ..... | 176 | +| 10.9.1.3.4.2 | Floor request cancellation from the queue - floor control server initiated ..... | 177 | +| 10.9.1.4 | Floor control involving groups from multiple MCPTT systems ..... | 178 | +| 10.9.1.4.1 | Partner MCPTT system routes all floor control messages to primary MCPTT system's floor control server..... | 178 | +| 10.9.1.4.2 | Partner MCPTT system performs filtering of floor control messages entering and leaving the partner MCPTT system..... | 180 | +| 10.9.1.5 | Floor control for audio cut-in enabled group..... | 183 | +| 10.9.1.6 | Unicast media stop and resume requests ..... | 185 | +| 10.9.2 | Floor control for off-network MCPTT service..... | 187 | + +| | | | +|-------------|--------------------------------------------------------------------------------------|-----| +| 10.9.2.1 | General..... | 187 | +| 10.9.2.2 | Information flows for floor control for off-network..... | 188 | +| 10.9.2.2.1 | General ..... | 188 | +| 10.9.2.2.2 | Floor granted ..... | 188 | +| 10.9.2.3 | Floor control during silence..... | 188 | +| 10.9.2.3.1 | Successful floor taken (No floor contention) ..... | 188 | +| 10.9.2.4 | Simultaneous floor requests..... | 189 | +| 10.9.2.5 | Floor request during speaking with queue..... | 190 | +| 10.9.2.6 | Floor request during speaking without queue..... | 191 | +| 10.9.2.7 | Override ..... | 192 | +| 10.9.2.8 | Floor queue status ..... | 193 | +| 10.10 | Use of MBMS transmission (on-network)..... | 194 | +| 10.10.1 | Information flows for MBMS Transmission..... | 194 | +| 10.10.1.1 | MapGroupToBearer..... | 194 | +| 10.10.1.2 | UnmapGroupFromBearer ..... | 195 | +| 10.10.1.3 | Application paging..... | 195 | +| 10.10.2 | Use of pre-established MBMS bearers..... | 195 | +| 10.10.3 | Use of dynamic MBMS bearer establishment..... | 195 | +| 10.10.4 | Call connect and disconnect over MBMS..... | 196 | +| 10.10.4.1 | General..... | 196 | +| 10.10.4.2 | Procedure ..... | 196 | +| 10.10.4.2.1 | Call connect over MBMS..... | 196 | +| 10.10.4.2.2 | Call disconnect over MBMS..... | 197 | +| 10.10.5 | Switching from MBMS bearer to unicast bearer..... | 198 | +| 10.10.6 | Enhanced MCPTT group call setup procedure with MBMS bearer ..... | 198 | +| 10.10.6.1 | Description..... | 198 | +| 10.10.6.2 | Procedure ..... | 199 | +| 10.11 | MCPTT resource management (on-network) ..... | 200 | +| 10.11.1 | General ..... | 200 | +| 10.11.2 | Request for unicast resources at session establishment..... | 200 | +| 10.11.3 | Request for modification of unicast resources ..... | 200 | +| 10.11.4 | Management of multicast media bearers..... | 200 | +| 10.11.5 | Request for resources with shared priority ..... | 200 | +| 10.11.5.1 | General..... | 200 | +| 10.11.5.2 | Procedure ..... | 200 | +| 10.12 | MCPTT media plane transmissions with partner MCPTT systems (on-network)..... | 200 | +| 10.13 | Location information (on-network)..... | 202 | +| 10.14 | Ambient listening call ..... | 202 | +| 10.14.1 | General ..... | 202 | +| 10.14.2 | Information flows for ambient listening call ..... | 202 | +| 10.14.2.1 | Ambient listening call request ..... | 202 | +| 10.14.2.2 | Ambient listening call response..... | 203 | +| 10.14.2.3 | Ambient listening call release request ..... | 203 | +| 10.14.2.4 | Ambient listening call release response..... | 203 | +| 10.14.2.5 | Ambient listening call release notification ..... | 204 | +| 10.14.3 | Ambient listening call procedures..... | 204 | +| 10.14.3.1 | Remotely initiated ambient listening call setup..... | 204 | +| 10.14.3.2 | Locally initiated ambient listening call setup ..... | 205 | +| 10.14.3.3 | Ambient listening call release – server initiated..... | 206 | +| 10.14.3.4 | Remotely initiated ambient listening call release – "listening" user initiated ..... | 207 | +| 10.14.3.5 | Ambient listening call release – "listened to" user initiated ..... | 208 | +| 10.15 | First-to-answer call setup ..... | 209 | +| 10.15.1 | Description ..... | 209 | +| 10.15.2 | Information flows for first-to-answer call ..... | 209 | +| 10.15.2.1 | MCPTT first-to-answer call request (MCPTT client to MCPTT server) ..... | 209 | +| 10.15.2.2 | MCPTT first-to-answer call request (MCPTT server to MCPTT client) ..... | 210 | +| 10.15.2.3 | MCPTT first-to-answer call response (MCPTT client to MCPTT server)..... | 210 | +| 10.15.2.4 | MCPTT first-to-answer call response (MCPTT server to MCPTT client)..... | 211 | +| 10.15.2.5 | MCPTT first-to-answer call cancel request (MCPTT server to MCPTT client)..... | 211 | +| 10.15.2.6 | MCPTT first-to-answer call cancel response (MCPTT client to MCPTT server)..... | 211 | +| 10.15.3 | Procedure..... | 212 | +| 10.16 | Remotely initiated MCPTT call ..... | 215 | + +| | | | +|--------------------------------------------------------------------|-------------------------------------------------------------------------------|------------| +| 10.16.1 | General ..... | 215 | +| 10.16.2 | Information flows for remotely initiated MCPTT call ..... | 215 | +| 10.16.2.1 | Remotely initiated MCPTT call request..... | 215 | +| 10.16.2.2 | Remotely initiated MCPTT call response ..... | 215 | +| 10.16.3 | Procedure ..... | 215 | +| 10.16.3.1 | Remotely initiated MCPTT call request ..... | 215 | +| 10.17 | Support for multiple devices ..... | 217 | +| 10.17.1 | General ..... | 217 | +| 10.18 | Subscription and notification for functional alias ..... | 217 | +| 10.18.1 | General ..... | 217 | +| 10.18.2 | Information flows for subscription and notification for functional alias..... | 217 | +| 10.18.2.1 | Subscribe functional alias request..... | 217 | +| 10.18.2.2 | Subscribe functional alias response ..... | 217 | +| 10.18.2.3 | Notify functional alias request..... | 218 | +| 10.18.2.4 | Notify functional alias response ..... | 218 | +| 10.18.3 | Procedure ..... | 218 | +| 10.18.3.1 | Subscription for functional alias procedure ..... | 218 | +| 10.18.3.2 | Notification for functional alias procedure ..... | 219 | +| Annex A (normative): MCPTT related configuration data ..... | | 220 | +| A.1 | General..... | 220 | +| A.2 | MCPTT UE configuration data..... | 221 | +| A.3 | MCPTT user profile configuration data..... | 221 | +| A.4 | MCPTT related group configuration data ..... | 228 | +| A.5 | MCPTT service configuration data..... | 232 | +| Annex B (informative): Local UE settings for MCPTT..... | | 235 | +| B.1 | Local UE settings for MCPTT ..... | 235 | +| Annex C (informative): Change history..... | | 236 | + +--- + +## Foreword + +This Technical Specification has been produced by the 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. + +--- + +# 1 Scope + +This document specifies the functional architecture, procedures and information flows needed to support the mission critical push to talk (MCPTT) service. The MCPTT service utilizes the common functional architecture to support MC services over LTE including the common services core defined in 3GPP TS 23.280 [16]. Support for both MCPTT group calls and MCPTT private calls operating in on-network and off-network modes of operation is specified. + +The corresponding service requirements are defined in 3GPP TS 22.179 [2] and 3GPP TS 22.280 [17]. + +The present document is applicable primarily to MCPTT voice service using E-UTRAN access based on the EPC architecture defined in 3GPP TS 23.401 [8]. Certain application functions of the MCPTT service such as dispatch and administrative functions could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access. + +The MCPTT service requires preferential handling compared to normal telecommunication services e.g. in support of police or fire brigade including the handling of prioritised MCPTT calls for emergency and imminent threats. + +The MCPTT service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways. + +In the present document, MCPTT calls between MCPTT users on different MCPTT systems are considered. + +--- + +# 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT)"; Stage 1. +- [3] 3GPP TS 23.002: "Network Architecture". +- [4] 3GPP TS 23.203: "Policy and charging control architecture". +- [5] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [6] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2". +- [7] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2". +- [8] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [9] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE\_LTE); Stage 2". +- [10] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE\_LTE); MB2 Reference Point; Stage 3". +- [11] Void +- [12] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". + +- [13] IETF RFC 5245 (April 2010): "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols". +- [14] void +- [15] void +- [16] 3GPP TS 23.280: "Common functional architecture to support mission critical services". +- [17] 3GPP TS 22.280: "Mission Critical Common Requirements (MCCoRe); Stage 1". +- [18] 3GPP TS 29.283: "Diameter data management applications". +- [19] 3GPP TS 33.180: "Security of the mission critical service". +- [20] 3GPP TS 23.283: "Mission Critical Communication Interworking with Land Mobile Radio Systems; Stage 2". + +--- + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Automatic commencement mode:** A mode in which the initiation of the private call does not require any action on the part of the receiving MCPTT user. + +**First-to-answer call:** A call that is started when the first MCPTT user among multiple potential target recipients' answers. This call requires the answering MCPTT user to answer manually; automatic answer is not allowed + +**Group call:** A mechanism by which an MCPTT user can make a one-to-many MCPTT transmission to other users that are members of MCPTT group(s). + +**Group home MCPTT system:** The MCPTT system where the MCPTT group is defined. + +**Group host MCPTT server:** The MCPTT server within an MCPTT system that provides centralised support for MCPTT services of an MCPTT group defined in a group home MCPTT system. + +**Manual commencement mode:** A mode in which the initiation of the private call requires the receiving MCPTT user to perform some action to accept or reject the call setup. + +**MCPTT client:** An instance of an MC service client that provides the client application function for the MCPTT service. + +**MCPTT group:** An MC service group configured for MCPTT service. + +**MCPTT group affiliation:** An MC service group affiliation for MCPTT. + +**MCPTT group de-affiliation:** An MC service group de-affiliation for MCPTT. + +**MCPTT ID:** An instance of an MC service ID within the MCPTT service. + +**MCPTT server:** An instance of an MC service server that provides the server application function for the MCPTT service. + +**On-network MCPTT service:** The collection of functions and capabilities required to provide MCPTT via EPS bearers using E-UTRAN to provide the last hop radio bearers. + +**Preconfigured MCPTT group:** an MCPTT group used only for regrouping that has been configured in advance of a group or user regrouping operation to serve as the source of regroup group configuration. + +**Pre-selected MCPTT user profile:** An instance of the pre-selected MC service user profile for MCPTT. + +**UE-to-network relay MCPTT service:** The collection of functions and capabilities required to provide MCPTT via a ProSe UE-to-network relay using ProSe direct communication paths to provide the last hop radio bearer(s). + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.179 [2] apply: + +**Dispatcher** +**Floor control** +**MCPTT administrator** +**MCPTT service** +**MCPTT system** +**MCPTT UE** +**MCPTT user** +**MCPTT User Profile** +**Mission Critical Organization** +**Mission Critical Push To Talk** +**Off-network MCPTT service** +**Partner MCPTT system** +**Primary MCPTT system** +**Private call** +**Multi-talker control** + +For the purposes of the present document, the following terms and definitions given in IETF RFC 5245 [13] apply: + +**Candidate** +**Candidate pair** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.280 [16] apply: + +**Active MC service user profile** +**MC service client** +**MC service group** +**MC service group affiliation** +**MC service group de-affiliation** +**MC service ID** +**MC service server** +**Pre-selected MC service user profile** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.280 [17] apply: + +**Functional alias** + +## 3.2 Symbols + +For the purposes of the present document, the following symbols given in 3GPP TS 22.179 [2] apply: + +**B1** +**B2** +**N2** +**N3** +**N4** +**N5** +**N6** +**N7** +**N10** +**N11** + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|------------|-------------------| +| APN | Access Point Name | +|------------|-------------------| + +| | | +|----------------|-----------------------------------------------------------------| +| ARP | Allocation and Retention Priority | +| BM-SC | Broadcast Multicast Service Centre | +| CHAP | Challenge-Handshake Authentication Protocol | +| CSCF | Call Server Control Function | +| DL | Downlink | +| DPF | Direct Provisioning Function | +| E-UTRAN | Evolved Universal Terrestrial Radio Access Network | +| E2EE | End to End Encryption | +| ECGI | E-UTRAN Cell Global Identifier | +| EPC | Evolved Packet Core | +| EPS | Evolved Packet System | +| GBR | Guaranteed Bit Rate | +| GCS AS | Group Communication Service Application Server | +| GCSE_LTE | Group Communication Service Enabler over LTE | +| GRUU | Globally Routable User agent URI | +| HLR | Home Location Register | +| HSS | Home Subscriber Server | +| HTTP | Hyper Text Transfer Protocol | +| I-CSCF | Interrogating CSCF | +| ICE | Interactive Connectivity Establishment | +| IM CN | IP Multimedia Core Network | +| IMPI | IP Multimedia Private Identity | +| IMPU | IP Multimedia PUblic identity | +| IMS | IP Multimedia Subsystem | +| ITSI | Individual TETRA Subscriber Identity | +| LMR | Land Mobile Radio | +| MBMS | Multimedia Broadcast and Multicast Service | +| MBSFN | Multimedia Broadcast multicast service Single Frequency Network | +| MC | Mission Critical | +| MC ID | Mission Critical user identity | +| MCPTT | Mission Critical Push To Talk | +| MCPTT AS | MCPTT Application Server | +| MCPTT group ID | MCPTT group identity | +| MCPTT ID | MCPTT user identity | +| NAT | Network Address Translation | +| PAP | Password Authentication Protocol | +| P-CSCF | Proxy CSCF | +| PCC | Policy and Charging Control | +| PCRF | Policy and Charging Rules Function | +| PLMN | Public Land Mobile Network | +| ProSe | Proximity-based Services | +| PSI | Public Service Identity | +| PTT | Push To Talk | +| QCI | QoS Class Identifier | +| QoS | Quality of Service | +| RAN | Radio Access Network | +| RF | Radio Frequency | +| RSI | Radio Set Identity | +| S-CSCF | Serving CSCF | +| SAI | Service Area Identifier | +| SDF | Service Data Flow | +| SIP | Session Initiated Protocol | +| SSL | Secure Sockets Layer | +| TLS | Transport Layer Security | +| TMGI | Temporary Mobile Group Identity | +| UM | Unacknowledged Mode | +| URI | Uniform Resource Identifier | +| USB | Universal Serial Bus | +| WLAN | Wireless Local Area Network | + +## 4 Introduction + +The MCPTT service supports communication between several users (i.e. group call), where each user has the ability to gain access to the permission to talk in an arbitrated manner. The MCPTT service also supports private calls between two users. + +The MCPTT architecture utilises the common functional architecture to support mission critical services over LTE defined in 3GPP TS 23.280 [16] and aspects of the IMS architecture defined in 3GPP TS 23.228 [5], the Proximity-based Services (ProSe) architecture defined in 3GPP TS 23.303 [7], the Group Communication System Enablers for LTE (GCSE\_LTE) architecture defined in 3GPP TS 23.468 [9] and the PS-PS access transfer procedures defined in 3GPP TS 23.237 [6] to enable support of the MCPTT service. + +The MCPTT UE primarily obtains access to the MCPTT service via E-UTRAN, using the EPS architecture defined in 3GPP TS 23.401 [8]. Certain application functions of MCPTT service such as dispatch and administrative functions can be supported using either MCPTT UEs in E-UTRAN or using MCPTT UEs via non-3GPP access networks. + +NOTE: Dispatch consoles and devices used by MCPTT service administrators are considered MCPTT UEs in the MCPTT architecture. + +MCPTT UEs that use non-3GPP access can only support a subset of the functionality specified in this specification that is supported by the non-3GPP access network. + +The MCPTT system provides the function to support interworking with LMR systems defined in 3GPP TS 23.283 [20]. + +## 5 Architectural requirements + +### 5.1 Media routing requirements + +The voice media flow for a private call shall be routed according to one of the following two options: + +- a) Option 1: + - 1) Through the primary MCPTT system if both users in the call belong to the same organisation; or + - 2) Through the primary MCPTT system of both users, if the users in the call do not belong to the same organisation. +- b) Option 2: The voice media flow may be routed locally, under the control of the primary MCPTT system, through an entity allowing the duplication of the media flow to the primary MCPTT system of each user. + +The voice media flow for a group call shall be routed to the group home MCPTT system. + +The routing of media flow shall be end-to-end from transmitter to receiver(s), except for the MCPTT control function. + +### 5.2 Requirements for user identity management + +To allow for confidentiality of user identities in various cases of business relationship as defined in clause 6, the MCPTT application may provide public user identities to the MCPTT UE, to be used by MCPTT UE for MCPTT services. + +### 5.3 MCPTT group affiliation and MCPTT group de-affiliation + +MCPTT group affiliation shall be as specified in clause 5.2.5 of 3GPP TS 23.280 [16]. In addition, the following requirements shall be fulfilled by the MCPTT service for MCPTT users affiliated to MCPTT groups: + +- MCPTT users receive notifications for MCPTT group call setup and invitations for their affiliated MCPTT group(s). +- MCPTT users receive media and events from their affiliated MCPTT group(s). + +## 5.4 MCPTT call requirements + +### 5.4.1 General + +The on-network MCPTT service shall support the use of pre-established sessions. + +### 5.4.2 Group call requirements + +The MCPTT service shall support the chat group (restricted) call model for MCPTT group call. + +The MCPTT service shall support the pre-arranged group call model for MCPTT group call. + +## 5.5 GCS AS requirements for the MCPTT service + +The GCS AS architecture requirements for MC services are specified in 3GPP TS 23.280 [16]. + +## 5.6 Group selection + +The following functionalities shall be supported by the MCPTT service. + +- a. The MCPTT user shall select an affiliated group to initiate a new group call or transmit media in an existing group call. +- b. An authorized MCPTT user (e.g., dispatcher) may remotely force or request to change other on-network MCPTT users' selected MCPTT group to a particular affiliated group. + +## 5.7 Bearer management + +### 5.7.1 General + +The MCPTT UE shall use the APNs as defined in subclause 5.2.7.0 of 3GPP TS 23.280 [16]. + +### 5.7.2 EPS bearer considerations + +The EPS bearer considerations specified in subclause 5.2.7.2 of 3GPP TS 23.280 [16] shall apply. + +5.7.2.1 Void + +5.7.2.2 Void + +### 5.7.3 EPS unicast bearer considerations for MCPTT + +For an MCPTT call session request, resources shall be requested utilising interaction with dynamic PCC. The MCPTT system shall request resources over Rx to a PCRF. The dedicated bearer for voice and MCPTT-4 reference point messaging shall utilise the QCI value of 65 (as specified in 3GPP TS 23.203 [4]). The request of resources over Rx shall include an application identifier for MCPTT in order for the PCRF to evaluate the correct QCI. + +The UE is required to support at minimum one UM bearer which is used for MCPTT voice (see annex A in 3GPP TS 36.331 [12]). + +Depending on operator policy: + +- the MCPTT system may be able to request modification of the priority (ARP) of an existing bearer without the need to initiate a new dedicated GBR bearer; or +- the EPS bearers for MCPTT call may enable pre-emption of lower priority EPS bearers if the maximum number of UM bearers has been reached in favour of MCPTT initiated EPS bearer, if the EPS bearer used for MCPTT call has higher priority level (ARP) than the UM bearer(s) used for other application(s) and if the bearers for non MCPTT application are pre-emptable. In this case, the EPS bearer for MCPTT call pre-empts one of the existing EPS bearers when the maximum number of bearers is established for other applications. + +NOTE 1: Operator policy takes into account regional/national requirements. + +The EPS bearer for MCPTT emergency call shall have highest priority level among MCPTT call types. The EPS bearer for MCPTT imminent peril call shall have higher priority level than one for MCPTT call. + +To ensure that the MCPTT service always has access to a dedicated bearer for MCPTT media, a pre-established session may be setup that includes a request for resources at the first MCPTT group affiliation. + +This means that the PCC may multiplex MCPTT media streams from multiple concurrent MCPTT calls into one EPS bearer on one shared network priority regardless of MCPTT call priority. + +NOTE 2: A single UM bearer is used to multiplex the media streams from multiple concurrent MCPTT calls. + +NOTE 3: The sharing of a single GBR bearer for voice means that different QCI and/or ARP values are not possible for different voice media streams. + +NOTE 4: Multi-talker control may require additional bearer resources if multiple audio streams are sent to the UE when the floor is granted to additional participants during an established MCPTT group session. + +## 5.7.4 MBMS bearer management + +The MBMS bearer management for MC services is specified in subclause 5.2.7.1 of 3GPP TS 23.280 [16]. + +## 5.8 MCPTT system interconnect requirements + +The architecture for interconnect between MCPTT systems is specified, allowing the affiliation of MCPTT users from an MCPTT system with MCPTT groups defined in another MCPTT system. When both MCPTT systems are served by different networks, interconnect of signalling and media is achieved using the interfaces defined for interconnect between PLMNs. + +--- + +## 6 Involved business relationships + +The description of the involved business relationships for the MCPTT service is contained in clause 6 of 3GPP TS 23.280 [16]. + +--- + +## 7 Functional model + +### 7.1 General + +The functional model for the support of MCPTT is defined as a series of planes to allow for the breakdown of the architectural description. + +### 7.2 Description of the planes + +The description of the planes and the relationship between the planes are contained in the common functional architecture to support MC services in 3GPP TS 23.280 [16]. + +### 7.3 Functional model description + +#### 7.3.1 On-network functional model + +Figure 7.3.1-1 shows the functional model for the application plane of the MCPTT service. + +![Functional model for application plane of the MCPTT service diagram](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +The diagram illustrates the functional model for the application plane of the MCPTT service. It shows the following components and their connections: + +- External Systems:** + - Other MCPTT server:** Connected to the MCPTT server via reference point **MCPTT-3**. + - MCPTT user database:** Connected to the MCPTT server via reference point **MCPTT-2**. + - Interworking function to legacy system:** Connected to the MCPTT server via reference point **IWF-1**. + - MC gateway server:** Connected to the MCPTT server via reference point **MCPTT-3**. It is also connected to an **Other MCPTT system** (represented by a dashed box) via reference point **MCPTT-10**. +- MCPTT server:** Contains two internal functions: + - Media distribution function:** Connected to the EPS via reference points **MCPTT-5** (labeled **Rx**), **MCPTT-6** (labeled **MB2C**), **MCPTT-7**, and **MCPTT-8**. + - Floor control server:** Connected to the EPS via reference points **MCPTT-1**, **MCPTT-4**, and **MCPTT-9**. +- EPS (Evolved Packet System):** Acts as a central communication hub between the MCPTT server and the MCPTT UE. +- MCPTT UE:** Contains an **MCPTT client** which includes: + - Media mixer:** Receives media from the media distribution function via **MCPTT-7** and **MCPTT-8**. + - Floor participant:** Communicates with the floor control server via **MCPTT-1**, **MCPTT-4**, and **MCPTT-9**. + +Functional model for application plane of the MCPTT service diagram + +**Figure 7.3.1-1: Functional model for application plane of the MCPTT service** + +In the model shown in figure 7.3.1-1, the following apply: + +- The MCPTT server is an instantiation of a MC service server in accordance with 3GPP TS 23.280 [16]. +- The MCPTT server is an instantiation of a GCS AS in accordance with 3GPP TS 23.468 [9]. +- MCPTT-9 carries multicast floor control signalling between the floor control server of the MCPTT server and the floor participant of the MCPTT UE. +- MCPTT-4 carries unicast floor control signalling between the floor control server of the MCPTT server and the floor participant of the MCPTT UE. +- MCPTT-7 carries unicast media between the media distribution function of the MCPTT server and the media mixer of the MCPTT UE. +- MCPTT-8 carries multicast media from the media distribution function of the MCPTT server to the media mixer of the MCPTT UE. + +Figure 7.3.1-2 shows the relationships between the reference points of the application plane and the signalling plane. + +![Diagram showing relationships between reference points of MCPTT application and signalling control planes. It includes MCPTT servers, SIP cores, an MCPTT client, and an 'Other MCPTT system' with various interfaces labeled SIP-1, SIP-2, SIP-3, HTTP-1, HTTP-2, and MCPTT-1 through MCPTT-10.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +The diagram illustrates the network architecture for MCPTT. At the top, two MCPTT servers are connected to a SIP core via SIP-2 and MCPTT-3 interfaces. Below this, another SIP core is connected to the first via SIP-3 and MCPTT-3. This second SIP core is connected to an MCPTT Client via SIP-1 and MCPTT-1, and to an MCPTT server via SIP-2 and MCPTT-3. It also connects to an MC gateway server via SIP-2. The second SIP core is further connected to a third SIP core via SIP-3 and MCPTT-10. This third SIP core is part of an 'Other MCPTT system' and is connected to another MC gateway server via SIP-2. The second SIP core also has connections labeled HTTP-1, HTTP-2. + +Diagram showing relationships between reference points of MCPTT application and signalling control planes. It includes MCPTT servers, SIP cores, an MCPTT client, and an 'Other MCPTT system' with various interfaces labeled SIP-1, SIP-2, SIP-3, HTTP-1, HTTP-2, and MCPTT-1 through MCPTT-10. + +Figure 7.3.1-2: Relationships between reference points of MCPTT application and signalling control planes + +### 7.3.2 Off-network functional model + +Figure 7.3.2-1 shows the functional model for off-network operation of MCPTT service. + +![Functional model for off-network operation of MCPTT service diagram showing two User Equipment (UE) blocks, UE1 and UE2, connected by Media (green line) and Signalling (red line) paths. Each UE contains an Application plane and a Signalling control plane. The Application plane includes Media mixer, Floor control server, Floor participant, MCPTT client, Configuration management client, and Group management client. The Signalling control plane includes a Signalling user agent client.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +The diagram illustrates the functional model for off-network operation of MCPTT service across two User Equipment (UE) blocks, UE1 and UE2. Each UE is composed of two main planes: the Application plane and the Signalling control plane. The Application plane within each UE contains six functional entities: Media mixer, Floor control server, Floor participant, MCPTT client, Configuration management client, and Group management client. The Signalling control plane contains a Signalling user agent client. A green horizontal line represents the Media path, and a red horizontal line represents the Signalling path, connecting the corresponding entities between UE1 and UE2. A legend at the bottom indicates that the green line represents Media and the red line represents Signalling. + +Functional model for off-network operation of MCPTT service diagram showing two User Equipment (UE) blocks, UE1 and UE2, connected by Media (green line) and Signalling (red line) paths. Each UE contains an Application plane and a Signalling control plane. The Application plane includes Media mixer, Floor control server, Floor participant, MCPTT client, Configuration management client, and Group management client. The Signalling control plane includes a Signalling user agent client. + +Figure 7.3.2-1: Functional model for off-network operation of MCPTT service + +## 7.4 Functional entities description + +### 7.4.1 General + +Each subclause is a description of a functional entity and does not imply a physical entity. + +### 7.4.2 Application plane of MCPTT service + +#### 7.4.2.1 General + +Entities within the application plane of MCPTT service provide application control, media control and distribution functions. + +#### 7.4.2.2 Common services core + +The description of the common services core entities are contained in common functional architecture to support MC services in 3GPP TS 23.280 [16]. + +#### 7.4.2.3 MCPTT application service + +##### 7.4.2.3.1 MCPTT client + +The MCPTT client functional entity acts as the user agent for all MCPTT application transactions. The client reports the information of where the client is currently located. + +##### 7.4.2.3.2 MCPTT server + +The MCPTT server functional entity provides centralised support for MCPTT services. + +All the MCPTT clients supporting users belonging to a single group are required to use the same MCPTT server for that group. An MCPTT client supporting a user involved in multiple groups can have relationships with multiple MCPTT servers. + +NOTE 1: Possible requirements for handling multiple distinct media on different MCPTT servers are not covered in this version of the document. + +The MCPTT server functional entity represents a specific instantiation of the GCS AS described in 3GPP TS 23.468 [9] to control multicast and unicast operations for group communications. + +The MCPTT server functional entity is supported by the SIP AS, HTTP client and HTTP server functional entities of the signalling control plane. + +By assuming the role of a GCS AS, the MCPTT server functional entity is responsible for: + +- requesting the allocation of multicast resources utilizing the media distribution function; +- announcing the association of multicast resources to calls to MCPTT UEs; +- determining for each MCPTT UE involved in a given call whether to use unicast or multicast transport; +- announcing the assignment of multicast transport for specific calls to MCPTT UEs; and +- informing the media distribution function of the media streams requiring support for a given call. + +The MCPTT server shall support the controlling role and the participating role. The MCPTT server may perform the controlling role for private calls and group calls. The MCPTT server performing the controlling role for a private call or group call may also perform a participating role for the same private call or group call. For each private call and group call, there shall be only one MCPTT server assuming the controlling role, while one or more MCPTT servers in participating role may be involved. + +The MCPTT server performing the controlling roles is responsible for: + +- call control (e.g. policy enforcement for participation in the MCPTT group calls) towards all the MCPTT users of the group call and private call; +- interfacing with the group management server for group policy and affiliation status information of this MCPTT server's served affiliated users; +- enforcing functional alias priority handling; +- managing floor control entity in a group call and private call; and +- managing media handling entity in call i.e. conferencing, transcoding. + +The MCPTT server performing the functional alias controlling role is responsible for: + +- interfacing with the functional alias management server for functional alias policy; +- functional alias activation, deactivation, take over and interrogation support for MCPTT user. + +The controlling roles for group call, private call and functional alias are independent with each other. + +The MCPTT server performing the participating roles is responsible for: + +- call control (e.g. authorization for participation in the MCPTT group calls) to its MCPTT users for group call and private call; +- group affiliation support for MCPTT user, including enforcement of maximum N2 number of simultaneous group affiliations by a user; +- enforcing functional alias priority handling; +- relaying the call control and floor control messages between the MCPTT client and the MCPTT server performing the controlling role; and +- media handling in call for its MCPTT users, i.e. transcoding, recording, lawful interception for both unicast and multicast media. + +NOTE 2: The MCPTT server in the controlling role and the MCPTT server in the participating role can belong to the same MCPTT system or to different MCPTT systems. + +For group regrouping involving multiple groups from primary and partner MCPTT systems, + +- the group host MCPTT server of the temporary group performs the controlling role and is responsible for the centralized floor control, and for arbitration according to the temporary group or user policies (e.g., priority); +- the group host MCPTT server of the constituent MCPTT group is responsible for providing call invitations to their group members, and for filtering between constituent group members' floor control requests according to the constituent group or user policies (e.g., priority); and +- the MCPTT server responsible for the constituent MCPTT group members performs the participating role. + +#### 7.4.2.3.3 Floor participant + +The floor participant functional entity is responsible for floor requests. This functional entity is located in the UE for both on-network and off-network operations. + +#### 7.4.2.3.4 Floor control server + +This functional entity provides support for centralised floor control for on-network and distributed floor control for off-network operation. It may provide arbitration between floor control requests between different users, grant the floor in response to successful requests, and provide queuing in cases of contention. For on-network operation, this functional entity is located with the MCPTT server. For off-network operation, this functional entity is located in the UE. + +#### 7.4.2.3.5 Media distribution function + +The media distribution function is responsible for the distribution of media to call participants. By means of information provided by the MCPTT server (e.g. IP addresses, transport layer ports), it will provide the following functionality: + +- provide for the reception of uplink MCPTT UE media transmission by means of the MCPTT-7 reference point; +- replicate the media as needed for distribution to those participants using unicast transport; +- distribute downlink media to MCPTT UEs by IP unicast transmission to those participants utilizing unicast transport by means of the MCPTT-7 reference point; +- distribute downlink media to MCPTT UEs using multicast downlink transport of media for the call by means of the MCPTT-8 reference point; and +- provide a media mixing function where multiple media streams are combined (e.g. multi-talker control) into a single media stream for transmission to the MCPTT UE. + +NOTE 1: If media mixing function occurs within the media distribution function, it operates independently of the media mixer in the UE. + +NOTE 2: A media mixing function within the media distribution function is not possible where the media is end to end encrypted. + +Group configuration data determines whether audio mixing for multi-talker control is applied by the media mixing function in the MCPTT server. + +NOTE 3: If media mixing in the network is utilized, care should be taken to minimize the feedback of the user's own voice from the mixed audio in order to avoid echoes. + +#### 7.4.2.3.6 Media mixer + +This functional entity exists on the UE and provides support for combining multiple media streams (e.g. multi-talker control) into one media stream through the enforcement of media policy information. Group configuration data determines whether audio mixing for multi-talker control is applied by the media mixing function in the UE. + +#### 7.4.2.3.7 MCPTT user database + +This functional entity contains information of the MCPTT user profile associated with an MCPTT ID that is held by the MCPTT service provider at the application plane. The MCPTT user profile is determined by the mission critical organization, the MCPTT service provider, and potentially the MCPTT user. + +### 7.4.2.3.8 MC gateway server + +The MC gateway server provides support for MCPTT interconnection services with a partner MCPTT system in a different trust domain whilst providing topology hiding. It acts as a proxy for one or more MCPTT servers in the partner MCPTT system without needing to expose the MCPTT servers in the primary MCPTT system outside the trusted domain of the primary MCPTT system. It may be a role of the MCPTT server described in subclause 7.4.2.3.2 of the present document. + +The MC gateway server is responsible for relaying call control and floor control signalling messages, and media between MCPTT servers within the MCPTT system and the interconnected MCPTT system. + +**Editor's note:** It is FFS whether the gateway MC server can act as a signalling proxy as defined in 3GPP TS 33.180 [25]. + +## 7.4.3 Signalling control plane + +The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [16]. + +## 7.5 Reference points + +### 7.5.1 General reference point principle + +The protocols on any reference point that is exposed for MCPTT service interoperability with other SIP core or other IMS entities in other systems shall be compatible with the protocols defined for the corresponding reference point defined in 3GPP TS 23.002 [3]. + +### 7.5.2 Application plane of MCPTT service + +#### 7.5.2.1 General + +The reference points for the application plane of MCPTT service are described in the following subclauses. + +#### 7.5.2.2 Reference point MCPTT-1 (between the MCPTT client and the MCPTT server) + +The MCPTT-1 reference point, which exists between the MCPTT client and the MCPTT server, is used for MCPTT application signalling for establishing a session in support of MCPTT. The MCPTT-1 reference point shall use the SIP-1 and SIP-2 reference points for transport and routing of SIP signalling. The MCPTT-1 reference point may use the HTTP-1 and HTTP-2 reference points. + +The TMGI is communicated between the MCPTT server and the MCPTT client using the MCPTT-1 reference point. + +Information that is reported to the MCPTT server from the MCPTT client shall be configurable at the application layer. This interface may include the area where a UE is currently located, described as ECGI of the serving and neighbouring cell(s), MBMS SAI, MBSFN Area ID. This information comes from the broadcast by the local cell, e.g. from SIB1 and SIB15 (see 3GPP TS 36.331 [12]) as decoded by the UE. + +**NOTE:** This reference point includes the GC1 reference point as described in 3GPP TS 23.468 [9]. It is assumed that the MCPTT server is performing the function of GCS AS. While 3GPP TS 23.468 [9] does not specify GC1 it does include high level descriptions of certain interactions on GC1, including those relating to the availability of multicast delivery for the application client. The MCPTT-1 reference point fulfils the requirements of the GC1 reference point for MCPTT. + +Messages supported on this interface may also include the MCPTT server providing the MCPTT client with information describing the mapping of transport resources to specific group calls. + +### 7.5.2.3 Reference point MCPTT-2 (between the MCPTT server and the MCPTT user database) + +The MCPTT-2 reference point, which exists between the MCPTT server and the MCPTT user database, is used by the MCPTT server to obtain information about a specific user. The MCPTT-2 reference point utilises a diameter management application protocol as defined in 3GPP TS 29.283 [18] and shall be intra-network. + +### 7.5.2.4 Reference point MCPTT-3 (between the MCPTT server and the MCPTT server and between the MCPTT server and the MC gateway server) + +The MCPTT-3 reference point exists between the MCPTT server and the MCPTT server and between the MCPTT server and the MC gateway server for MCPTT application signalling for establishing MCPTT sessions. The MCPTT-3 reference point shall use the SIP-2 reference point for transport and routing of signalling. If a pair of MCPTT servers, or an MCPTT server and an MC gateway server, are served by different SIP cores then the MCPTT-3 reference point shall also use the SIP-3 reference point for transport and routing of signalling. Floor control signalling and media are also transferred using the MCPTT-3 reference point. + +### 7.5.2.5 Reference point MCPTT-4 (unicast between the floor control server and the floor participant) + +The MCPTT-4 reference point, which exists between the floor control server in the MCPTT server and the floor participant in the MCPTT client, provides floor control signalling between the floor control server in the MCPTT server and the floor participant over a unicast bearer. The MCPTT-4 reference point uses the SGi reference point defined in 3GPP TS 23.002 [3]. + +### 7.5.2.6 Reference point MCPTT-5 (between the media distribution function and the EPS) + +The MCPTT-5 reference point, which exists between the media distribution function and the EPS, is used, subject to the conditions below, by the media distribution function of the MCPTT server to obtain unicast bearers with appropriate QoS from the EPS. It utilises the Rx interface of the EPS according to 3GPP TS 23.203 [4]. + +MCPTT-5 is not used when the MCPTT service provider and the PLMN operator do not have an operational agreement for QoS control to be provided directly from the MCPTT service provider domain. + +MCPTT-5 may be used when the MCPTT service provider and the PLMN operator have an operational agreement where QoS control is provided directly from the MCPTT service provider domain. + +NOTE: Any coordination between the P-CSCF use of Rx and the MCPTT server use of Rx (via MCPTT-5) from the MCPTT service provider domain is not specified in this release of this specification. + +### 7.5.2.7 Reference point MCPTT-6 (between the MCPTT server and the EPS) + +The MCPTT-6 reference point, which exists between the MCPTT server and the EPS, is used to request the allocation and activation of multicast transport resources for MCPTT application usage. The MCPTT-6 reference point uses the MB2-C interface as defined in 3GPP TS 29.468 [10]. + +### 7.5.2.8 Reference point MCPTT-7 (unicast between the media distribution function and the media mixer) + +The MCPTT-7 reference point, which exists between the media distribution function and the media mixer, is used to exchange unicast media between the media distribution function of the MCPTT server and the media mixer of the MCPTT client. The MCPTT-7 reference point uses the SGi reference point defined in 3GPP TS 23.002 [3]. + +### 7.5.2.9 Reference point MCPTT-8 (multicast between the media distribution function and the media mixer) + +The MCPTT-8 reference point, which exists between the media distribution function and the media mixer, is used by the media distribution function of the MCPTT server to send multicast media to the media mixer of the MCPTT client. The MCPTT-8 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [9]. + +#### 7.5.2.10 Reference point MCPTT-9 (multicast between the floor control server and the floor participant) + +The MCPTT-9 reference point, which exists between the floor control server and the floor participant, provides floor control signalling between the floor control server and the floor participant over a multicast bearer. The MCPTT-9 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [9]. + +#### 7.5.2.11 Reference point IWF-1 (between the MCPTT server and the interworking function to legacy systems) + +The IWF-1 reference point is specified in 3GPP TS 23.283 [20]. + +#### 7.5.2.12 Reference points of common services core used in the MCPTT service + +The descriptions for reference points of the common services core are contained in the common functional architecture to support MC services specified in 3GPP TS 23.280 [16]. + +#### 7.5.2.13 Reference point MCPTT-10 (between the MC gateway server and the MC gateway server in a different MCPTT system) + +The MCPTT-10 reference point, which exists between the MC gateway server and the MC gateway server in an interconnected MCPTT system for MCPTT application signalling for establishing MCPTT sessions, shall use the SIP-3 reference point for transport and routing of signalling. Floor control signalling and media are also transferred using the MCPTT-10 reference point between interconnected MCPTT systems. + +--- + +## 8 Identities + +The MCPTT service specific identities (e.g. MCPTT ID, MCPTT group ID) are described in clause 8 of 3GPP TS 23.280 [16]. + +--- + +## 9 Application of functional model to deployments + +The application of the functional model to deployments, and description of various deployment scenarios for the MCPTT service, can be found in clause 9 of 3GPP TS 23.280 [16]. + +--- + +## 10 Procedures and information flows + +### 10.1 MCPTT service configuration + +The MCPTT service shall support the procedures and related information flows as specified in subclause 10.1 of 3GPP TS 23.280 [16] with the following clarifications: + +- The MC service client is the MCPTT client; +- The MC service server is the MCPTT server; +- The MC service ID is the MCPTT ID; and +- The MC service user profile index is the MCPTT user profile index. + +### 10.2 User authentication and authorization for MCPTT service + +NOTE 1: Flow 10.2-1 is a high level user authentication and authorization flow. 3GPP TS 33.180 [19] defines the specific user authentication and authorization architecture required by the MCPTT service in order to realize the MCPTT user authentication and authorization requirements as defined in 3GPP TS 22.179 [2]. + +A procedure for user authentication is illustrated in figure 10.2-1. The user authentication is performed based on the procedure specified in 3GPP TS 23.280[16]. + +![Sequence diagram for MCPTT user authentication and registration, single domain. Lifelines: MCPTT client, Identity management client, Signalling user agent, SIP core, Identity management server, MCPTT server. Step 1: User Authentication based on 'General user authentication and authorization for MC services' (3GPP TS 23.280[18]). Step 2: MCPTT client performs service authorization with the MCPTT server.](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +The diagram is a sequence diagram showing the interaction between six entities: MCPTT client, Identity management client, Signalling user agent, SIP core, Identity management server, and MCPTT server. + Step 1: A message box spanning Identity management client, Signalling user agent, SIP core, and Identity management server contains the text: "1. User Authentication is based on the procedure – “General user authentication and authorization for MC services” specified in 3GPP TS 23.280[18].". Vertical lines connect this box to each of the four entities. + Step 2: A message box spanning MCPTT client and MCPTT server contains the text: "2. The MCPTT client performs the service authorization with the MCPTT server.". Vertical lines connect this box to both the MCPTT client and MCPTT server. + +Sequence diagram for MCPTT user authentication and registration, single domain. Lifelines: MCPTT client, Identity management client, Signalling user agent, SIP core, Identity management server, MCPTT server. Step 1: User Authentication based on 'General user authentication and authorization for MC services' (3GPP TS 23.280[18]). Step 2: MCPTT client performs service authorization with the MCPTT server. + +**Figure 10.2-1: MCPTT user authentication and registration, single domain** + +1. The user authentication is performed as per the general user authentication procedure specified in 3GPP TS 23.280[16]. +2. MCPTT client performs the MCPTT service authorization for the user. Step 2 utilizes the results of step 1. + +NOTE 2: The MCPTT server may reject a request for service authorization by an MCPTT user if the number of simultaneous service authorizations for that MCPTT user would be exceeded. + +### 10.3 Affiliation and de-affiliation to/from MCPTT group(s) + +The MCPTT service shall support the procedures and related information flows as specified in subclause 10.8 of 3GPP TS 23.280 [16] with the following clarifications: + +- The MC service client is the MCPTT client; +- The MC service server is the MCPTT server; +- The MC service group is the MCPTT group; +- The MC service ID is the MCPTT ID; and +- The MC service group ID is the MCPTT group ID. + +When an MCPTT user has affiliated to an MCPTT group then the MCPTT user can send and receive MCPTT related media for that MCPTT group. When an MCPTT user has de-affiliated from an MCPTT group then the MCPTT user cannot send and receive MCPTT related media to and from that MCPTT group. + +### 10.3a Activation and de-activation of/from functional alias(es) + +The MCPTT service shall support the procedures and related information flows as specified in subclause 10.13.4 and subclause 10.13.5 of 3GPP TS 23.280 [16]. + +- The MC service client is the MCPTT client; +- The MC service server is the MCPTT server; +- The MC service ID is the MCPTT ID. + +## 10.4 MCPTT group selection + +### 10.4.1 General + +When an MCPTT user wants to transmit on a MCPTT group, an affiliated MCPTT group shall be set as the selected MCPTT group to the MCPTT user. Only one MCPTT group can be set as the selected MCPTT group to an MCPTT user from one particular MCPTT UE at any given time. This sub-clause describes the detailed procedures for the MCPTT group selection. + +### 10.4.2 Information flows for group selection + +#### 10.4.2.1 Group selection change request + +Table 10.4.2.1-1 describes the information flow group selection change request from the MCPTT client to the MCPTT server. + +**Table 10.4.2.1-1: Group selection change request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| MCPTT ID | M | MCPTT user identity whose group selection information is to be changed | +| MCPTT group ID | M | MCPTT group identity for which the selection is made for the MCPTT ID | + +#### 10.4.2.2 Group selection change response + +Table 10.4.2.2-1 describes the information flow group selection change response from the MCPTT server to the MCPTT client. + +**Table 10.4.2.2-1: Group selection change response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| Result | M | Result indicates success or failure of group selection change | + +#### 10.4.2.3 Group selection change notification + +Table 10.4.2.3-1 describes the information flow group selection change notification from the MCPTT server to the MCPTT client. + +**Table 10.4.2.3-1: Group selection change notification** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| MCPTT ID | M | MCPTT user identity whose group selection information is to be changed | +| MCPTT group ID | M | MCPTT group identity for which the selection is made for the MCPTT ID | + +## 10.4.3 Authorized user remotely changes another MCPTT user's selected MCPTT group – mandatory mode + +Procedure for an authorized user to change other MCPTT users' selected MCPTT group without requiring target user's approval is described in figure 10.4.3-1. + +Pre-conditions: + +- The MCPTT client 1 has already been provisioned (statically or dynamically) with the target MCPTT user's information and its group information, that the selected MCPTT group of target MCPTT user 2 is allowed to be changed; + +![Sequence diagram illustrating the 'Remotely change MCPTT group selection – mandatory mode' procedure. The diagram shows three participants: MCPTT client 1 (authorized user 1), MCPTT server, and MCPTT client 2 (target user 2). The sequence of messages is: 1. MCPTT client 1 sends a 'Group selection change request' to the MCPTT server. 2. The MCPTT server performs an 'Authorization check based on subscription and affiliation relationship check based on the stored affiliation status'. 3. The MCPTT server then performs 'Remotely affiliate to the requested MCPTT group using procedure from subclause 10.3.5'. 4. The MCPTT server sends a 'Group selection change notification' to MCPTT client 2. 5. The MCPTT server sends a 'Group selection change response' back to MCPTT client 1. 6. MCPTT client 2 sends a message to notify the target user about the change of the selected MCPTT group.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 (authorized user 1) + participant MCPTT server + participant MCPTT client 2 (target user 2) + Note right of MCPTT server: 2. Authorization check based on subscription and affiliation relationship check based on the stored affiliation status + Note right of MCPTT server: 3. Remotely affiliate to the requested MCPTT group using procedure from subclause 10.3.5 + MCPTT client 1->>MCPTT server: 1. Group selection change request + MCPTT server-->>MCPTT client 2: 4. Group selection change notification + MCPTT server-->>MCPTT client 1: 5. Group selection change response + MCPTT client 2->>MCPTT client 2: 6. Notify target user the change of the selected MCPTT group + +``` + +Sequence diagram illustrating the 'Remotely change MCPTT group selection – mandatory mode' procedure. The diagram shows three participants: MCPTT client 1 (authorized user 1), MCPTT server, and MCPTT client 2 (target user 2). The sequence of messages is: 1. MCPTT client 1 sends a 'Group selection change request' to the MCPTT server. 2. The MCPTT server performs an 'Authorization check based on subscription and affiliation relationship check based on the stored affiliation status'. 3. The MCPTT server then performs 'Remotely affiliate to the requested MCPTT group using procedure from subclause 10.3.5'. 4. The MCPTT server sends a 'Group selection change notification' to MCPTT client 2. 5. The MCPTT server sends a 'Group selection change response' back to MCPTT client 1. 6. MCPTT client 2 sends a message to notify the target user about the change of the selected MCPTT group. + +**Figure 10.4.3-1: Remotely change MCPTT group selection – mandatory mode** + +1. When an authorized user changes other MCPTT users' selected MCPTT group, the MCPTT client 1 sends MCPTT group selection change request to the MCPTT server. The information (i.e. target MCPTT ID(s), MCPTT group ID(s)) used to set the requested MCPTT group as the selected MCPTT group of the target MCPTT user shall be included. +2. The MCPTT server shall check if the MCPTT user 1 is authorized to change the target MCPTT user's selected MCPTT group. The MCPTT server shall perform the affiliation relationship check based on the stored affiliation status. +3. If the MCPTT user 1 is authorized to change the target MCPTT user's selected MCPTT group, and if the target MCPTT user is not already affiliated to the requested MCPTT group, the remotely change of affiliation procedures in shall be performed (see subclause 10.8 in 3GPP TS 23.280 [16]). +4. The MCPTT server then shall send the MCPTT group selection change notification including the target user ID and the selected MCPTT group ID to the MCPTT client 2. +5. The group selection change response then returns to the MCPTT client 1. +6. Target MCPTT client 2 are notified about the change of its selected MCPTT group. + +## 10.5 Pre-established session (on-network) + +### 10.5.1 General + +The MCPTT server and client may use one or more pre-established sessions as defined in 3GPP TS 23.280 [16] for the following procedures for on-network: + +- Group calls (as specified in subclause 10.6.2.3 and subclause 10.6.2.4); +- Private calls (as specified in subclause 10.7.2.2 and subclause 10.7.2.3); +- MCPTT emergency group calls (as specified in subclause 10.6.2.6.1); +- MCPTT imminent peril group calls (as specified in subclause 10.6.2.6.2); +- MCPTT emergency private calls (as specified in subclause 10.7.2.4); and + +- MCPTT emergency alerts (as specified in subclause 10.6.2.6.3). + +For outgoing MCPTT call setup for a private call or a pre-arranged group call using a pre-established session, an MCPTT UE uses SIP procedures to establish the call. + +For incoming MCPTT call setup for a pre-arranged group call using a pre-established session, media plane control procedures are used to establish the call between the MCPTT server and client. + +For incoming MCPTT call setup for a private call using a pre-established session, SIP procedures are used to establish the call between the MCPTT client and server in manual commencement mode and media plane control procedures in automatic commencement mode. + +An MCPTT UE can join an MCPTT chat group using a pre-established session by sending a group join request using SIP procedures. + +NOTE: A chat group call is started and notified using floor control messages regardless of whether pre-established session is used. + +## 10.5.2 Information flows for pre-established session + +### 10.5.2.1 Pre-established session establishment + +Table 10.5.2.1-1 describes the information flow create pre-established session request from the MCPTT client to the MCPTT server, for the procedure defined in 3GPP TS 23.280 [16]. + +**Table 10.5.2.1-1: Create pre-established session request** + +| Information element | Status | Description | +|------------------------------------|--------|-----------------------------------------------------------------------------------------| +| MCPTT ID of requester (originator) | M | This element identifies the MCPTT user that wishes to create a pre-established session. | +| SDP offer | M | SDP with media information offered by client (e.g. ports, codec, protocol id). | + +Table 10.5.2.1-2 describes the information flow create pre-established session response from the MCPTT server to the MCPTT client, for the procedure defined in 3GPP TS 23.280 [16]. + +**Table 10.5.2.1-2: Create pre-established session response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------| +| SDP Answer | M | SDP with media information offered by server (e.g. ports, codec, protocol id) | +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | + +### 10.5.2.2 Pre-established session modification + +Table 10.5.2.2-1 describes the information flow modify pre-established session request from the MCPTT client to the MCPTT server, for the procedure defined in 3GPP TS 23.280 [16]. + +**Table 10.5.2.2-1: Modify pre-established session request** + +| Information element | Status | Description | +|------------------------------------|--------|-----------------------------------------------------------------------------------------| +| MCPTT ID of requester (originator) | M | This element identifies the MCPTT user that wishes to create a pre-established session. | +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | +| SDP offer | M | SDP with media information offered by client (e.g. ports, codec, protocol id). | + +Table 10.5.2.2-2 describes the information flow modify pre-established session response from the MCPTT server to the MCPTT client, for the procedure defined in 3GPP TS 23.280 [16]. + +**Table 10.5.2.2-2: Modify pre-established session response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------| +| SDP Answer | M | SDP with media information offered by server (e.g. ports, codec, protocol id). | +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | + +### 10.5.2.3 Pre-established session release - client initiated + +Table 10.5.2.3-1 describes the information flow release pre-established session request from the MCPTT client to the MCPTT server, for the procedure defined in 3GPP TS 23.280 [16]. + +**Table 10.5.2.3-1: Release pre-established session request - client initiated** + +| Information element | Status | Description | +|------------------------------------|--------|------------------------------------------------------------------------------------------| +| MCPTT ID of requester (originator) | M | This element identifies the MCPTT user that wishes to release a pre-established session. | +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | +| Release reason | M | This element indicates that reason for the session release. | + +Table 10.5.2.3-2 describes the information flow release pre-established session response from the MCPTT server to the MCPTT client, for the procedure defined in 3GPP TS 23.280 [16]. + +**Table 10.5.2.3-2: Release pre-established session response - client initiated** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------| +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | + +### 10.5.2.4 Pre-established session release - server initiated + +Table 10.5.2.4-1 describes the information flow release pre-established session request from the MCPTT server to the MCPTT client, for the procedure defined in 3GPP TS 23.280 [16]. + +**Table 10.5.2.4-1: Release pre-established session release request - server initiated** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------| +| MCPTT ID of target | M | This element identifies the MCPTT user that is the target of the for pre-established session release. | +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | +| Release reason | M | This element indicates the reason for the session release. | + +Table 10.5.2.4-2 describes the information flow release pre-established session response from the MCPTT client to the MCPTT server, for the procedure defined in 3GPP TS 23.280 [16]. + +**Table 10.5.2.4-2: Release pre-established session response - server initiated** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------| +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | + +### 10.5.2.5 Pre-established session call connect request + +Table 10.5.2.5-1 describes the information flow pre-established session call connect request from the MCPTT server to the MCPTT client, for the procedure defined in subclause 10.5.3.2.1 of the present document. + +**Table 10.5.2.5-1: Pre-established session call connect request** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------------| +| MCPTT group ID | O | Identity of the MCPTT group (NOTE) | +| MCPTT ID | O | MCPTT ID of the private call MCPTT user (NOTE) | +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | +| NOTE: Depending on type of connection either MCPTT group ID or MCPTT ID shall be present | | | + +## 10.5.2.6 Pre-established session call disconnect request + +Table 10.5.2.1.6-1 describes the information flow pre-established session call disconnect request from the MCPTT server to the MCPTT client, for the procedure defined in subclause 10.5.3.2.2 of the present document. + +**Table 10.5.2.6-1: Pre-established session call disconnect request** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------------| +| MCPTT group ID | O | Identity of the MCPTT group (NOTE) | +| MCPTT ID | O | MCPTT ID of the private call MCPTT user (NOTE) | +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | +| NOTE: Depending on type of connection either MCPTT group ID or MCPTT ID shall be present | | | + +## 10.5.3 Procedures + +### 10.5.3.1 General + +The MCPTT server and MCPTT client make use of the procedures defined in the following subclauses of the present document and the following procedures in 3GPP TS 23.280 [16]: + +- pre-established session establishment; +- pre-established session modification; and +- pre-established session release. + +### 10.5.3.2 Call connect and disconnect procedures using pre-established session + +#### 10.5.3.2.1 Call connect over unicast + +Call connect and disconnect information flows are sent over non-SIP media plane signalling using MCPTT-4 for including or releasing an MCPTT client in the call using a pre-established session. + +Figure 10.5.3.2.1-1 shows the high level procedure where a call connect information flow is sent by the MCPTT server to inform MCPTT client(s) using a pre-established session that the MCPTT client(s) has/have been connected to an MCPTT private call or group call. + +![Sequence diagram for the connect procedure. The diagram is titled 'Home MCPTT service provider' and shows four lifelines: MCPTT client A, Floor participant A, MCPTT server, and Floor control server. Step 1: A horizontal bar labeled '1. Pre-established session' spans from MCPTT client A to MCPTT server. Step 2: A box labeled '2. Include MCPTT client 1 in call' is on the MCPTT server lifeline. Step 3: An arrow labeled '3. Pre-established session call connect request' points from the MCPTT server to MCPTT client A.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +Sequence diagram for the connect procedure. The diagram is titled 'Home MCPTT service provider' and shows four lifelines: MCPTT client A, Floor participant A, MCPTT server, and Floor control server. Step 1: A horizontal bar labeled '1. Pre-established session' spans from MCPTT client A to MCPTT server. Step 2: A box labeled '2. Include MCPTT client 1 in call' is on the MCPTT server lifeline. Step 3: An arrow labeled '3. Pre-established session call connect request' points from the MCPTT server to MCPTT client A. + +**Figure 10.5.3.2.1-1: Connect procedure** + +1. Pre-established session exists between MCPTT client A and MCPTT server. +2. MCPTT server has determined to include MCPTT client A in the call e.g., upon receiving the request from another MCPTT client to include MCPTT client A in the call. +3. Pre-established session call connect request information flow is sent by the MCPTT server to inform MCPTT client A using a pre-established session that it has been connected to MCPTT private or group call. The floor control is established between floor participant A and floor control server. + +#### 10.5.3.2.2 Call disconnect over unicast + +Figure 10.5.3.2.2-1 shows the high level procedure where a disconnect information flow is sent by the MCPTT server to the MCPTT client A to indicate that the MCPTT private call or group call using a pre-established session has been released. + +![Sequence diagram for the disconnect procedure. The diagram is titled 'Home MCPTT service provider' and shows the same four lifelines as the previous diagram. Step 1: A horizontal bar labeled '1. Ongoing call in pre-established session with floor control' spans from MCPTT client A to Floor control server. Step 2: A box labeled '2. Call release' is on the MCPTT server lifeline. Step 3: An arrow labeled '3. Pre-established session call disconnect request' points from the MCPTT server to MCPTT client A.](1b893df61c2b73b7a85e65fc1f58e203_img.jpg) + +Sequence diagram for the disconnect procedure. The diagram is titled 'Home MCPTT service provider' and shows the same four lifelines as the previous diagram. Step 1: A horizontal bar labeled '1. Ongoing call in pre-established session with floor control' spans from MCPTT client A to Floor control server. Step 2: A box labeled '2. Call release' is on the MCPTT server lifeline. Step 3: An arrow labeled '3. Pre-established session call disconnect request' points from the MCPTT server to MCPTT client A. + +**Figure 10.5.3.2.2-1: Disconnect procedure** + +1. Floor control is ongoing within a private or group call established using pre-established session. +2. MCPTT server has determined to release MCPTT client A from the call e.g., due to call release. +3. Pre-established session call disconnect request message is sent by the MCPTT server to indicate to MCPTT client A that the MCPTT private call or group call using a pre-established session has been released. Pre-established session between MCPTT client A and MCPTT server remains for further use. + +## 10.6 Group call + +### 10.6.1 General + +Group calls are enabled in both on-network and off-network. + +### 10.6.2 On-network group call + +#### 10.6.2.1 General + +This subclause contains procedures for group call across a single and multiple MCPTT servers, and associated functions such as emergency call, broadcast call and others. + +Two variations of group call model are described in subclause 10.6.2.3, the pre-arranged group call and the chat group call. Each of the subsequent group call types in subclause 10.6.2.4 onwards are applicable to either call model. + +#### 10.6.2.2 Information flows for group call in on-network + +##### 10.6.2.2.1 MCPTT emergency group call request + +Table 10.6.2.2.1-1 describes the information flow MCPTT emergency group call request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.1-1 MCPTT emergency group call request information elements** + +| Information Element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Emergency indicator | M | Indicates that the group call request is an MCPTT emergency call | +| Alert indicator | M | Indicates whether an emergency alert is to be sent | +| Implicit floor request (NOTE) | O | Indicates that the originating client requests the floor. | +| Location | O | Location of the calling party | +| NOTE: This element shall be included only when this information flow is from the client to the server and the originating client requests the floor. | | | + +##### 10.6.2.2.1a MCPTT emergency group call response + +Table 10.6.2.2.1a-1 describes the information flow MCPTT emergency group call response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.1a-1 MCPTT emergency group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Result | M | Result of the MCPTT emergency group call request (success or failure) | + +### 10.6.2.2.2 MCPTT in-progress emergency group state cancel request + +Table 10.6.2.2.2-1 describes the information flow MCPTT in-progress emergency group state cancel request from the MCPTT client to the MCPTT server. + +NOTE: In Rel-14 and Rel-13 versions of this specification the name of this information flow is "MCPTT emergency group call cancel request". + +**Table 10.6.2.2.2-1: MCPTT in-progress emergency group state cancel request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the MCPTT in-progress emergency state is to be cancelled. | +| Alert indicator | O | Indicates whether the emergency alert of the cancelling party is to be cancelled | + +### 10.6.2.2.2a MCPTT in-progress emergency group state cancel response + +Table 10.6.2.2.2a-1 describes the information flow MCPTT in-progress emergency group state cancel response from the MCPTT server to the MCPTT client. + +NOTE: In Rel-14 and Rel-13 versions of this specification the name of this information flow is "MCPTT emergency group call cancel response". + +**Table 10.6.2.2.2a-1: MCPTT in-progress emergency group state cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the MCPTT in-progress emergency in-progress is to be cancelled. | + +### 10.6.2.2.3 MCPTT emergency alert request + +Table 10.6.2.2.3-1 describes the information flow MCPTT emergency alert request from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.3-1 MCPTT emergency alert request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| MCPTT ID | M | The identity of the alerting party | +| Functional alias | O | The functional alias of the alerting party | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | +| Location | O | The alerting MCPTT client's location | + +Table 10.6.2.2.3-2 describes the information flow MCPTT emergency alert request from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.3-2 MCPTT emergency alert request information elements** + +| Information Element | Status | Description | +|---------------------|--------|--------------------------------------------------------------| +| MCPTT ID | M | The identity of the alerting party | +| Functional alias | O | The functional alias of the alerting party | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | +| Organization name | M | The alerting MCPTT user's mission critical organization name | +| Location | O | The alerting MCPTT client's location | + +#### 10.6.2.2.3a MCPTT emergency alert response + +Table 10.6.2.2.3a-1 describes the information flow MCPTT emergency alert response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.3a-1 MCPTT emergency alert response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| MCPTT ID | M | The identity of the alerting party | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | + +#### 10.6.2.2.3b MCPTT emergency alert area notification + +Table 10.6.2.2.3b-1 describes the information flow MCPTT emergency alert area notification from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.3b-1 MCPTT emergency alert area notification information elements** + +| Information Element | Status | Description | +|--------------------------------|--------|---------------------------------------------------------------------------------------------------| +| MCPTT ID | M | MCPTT user identity of the party to be notified | +| Emergency Alert Area Indicator | M | An indicator that the MCPTT user is in an Emergency Alert Area or out of an Emergency Alert Area. | + +NOTE: Normally, the pre-defined area that triggers the emergency alert and the pre-defined area that triggers the out of MCPTT alert area notification are not the same. + +#### 10.6.2.2.4 MCPTT emergency alert cancel request + +Table 10.6.2.2.4-1 describes the information flow MCPTT emergency alert cancel request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.4-1 MCPTT emergency alert cancel request information elements** + +| Information Element | Status | Description | +|----------------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | MCPTT user identity of the cancelling party | +| MCPTT ID (NOTE) | O | MCPTT user identity whose emergency alert is to be cancelled | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | +| Group's in-progress emergency state cancel request | O | Requests cancellation of the in-progress emergency state of the group | +| NOTE: | | This information shall be present if the message is requesting cancellation of another MCPTT user's alert. If not present, then the alert of the MCPTT ID of the cancelling party is being cancelled | + +#### 10.6.2.2.4a MCPTT emergency alert cancel response + +Table 10.6.2.2.4a-1 describes the information flow MCPTT emergency alert cancel response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.4a-1 MCPTT emergency alert cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | + +#### 10.6.2.2.5 MCPTT imminent peril group call request + +Table 10.6.2.2.5-1 describes the information flow MCPTT imminent peril group call request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.5-1 MCPTT imminent peril group call request information elements** + +| Information Element | Status | Description | +|-------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Imminent peril indicator | M | Indicates that the group call request is an imminent peril call | +| Implicit floor request (NOTE) | O | Indicates that the originating client requests the floor | +| Location | O | Location of the calling party | +| NOTE: | | This element shall be included only when this information flow is from the client to the server and the originating client requests the floor. | + +#### 10.6.2.2.5a MCPTT imminent peril group call response + +Table 10.6.2.2.5a-1 describes the information flow MCPTT imminent peril group call response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.5a-1 MCPTT imminent peril group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Result | M | Result of the MCPTT imminent peril group call request (success or failure) | + +#### 10.6.2.2.6 MCPTT in-progress imminent peril group state cancel request + +Table 10.6.2.2.6-1 describes the information flow MCPTT in-progress imminent peril group state cancel request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +NOTE: In Rel-14 and Rel-13 versions of this specification the name of this information flow is "MCPTT imminent peril group call cancel request". + +**Table 10.6.2.2.6-1 MCPTT in-progress imminent peril group state cancel request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the imminent peril group state is to be cancelled | + +#### 10.6.2.2.6a MCPTT in-progress imminent peril group state cancel response + +Table 10.6.2.2.6a-1 describes the information flow MCPTT in-progress imminent peril group state cancel response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +NOTE: In Rel-14 and Rel-13 versions of this specification the name of this information flow is "MCPTT imminent peril group call cancel response". + +**Table 10.6.2.2.6a-1 MCPTT in-progress imminent peril group state cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the imminent peril group state is to be cancelled | + +#### 10.6.2.2.7 Group call request (MCPTT client – MCPTT server) + +Table 10.6.2.2.7-1 describes the information flow group call request from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.7-1 Group call request information elements** + +| Information Element | Status | Description | +|------------------------|--------|----------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | O | The MCPTT group ID of the group on which the call is requested | +| SDP offer | M | Media parameters of MCPTT clients | +| Implicit floor request | O | When originating client requests the floor, this element shall be included | +| Broadcast indicator | O | Indicates that the group call request is for a broadcast group call | +| Location information | O | Location of the calling party. | +| Requested priority | O | Application priority level requested for this call | + +#### 10.6.2.2.8 Group call request (MCPTT server – MCPTT server) + +Table 10.6.2.2.8-1 describes the information flow group call request between the MCPTT servers. + +**Table 10.6.2.2.8-1 Group call request information elements** + +| Information Element | Status | Description | +|-------------------------------|--------|-------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is initiated | +| SDP offer | M | Media parameters of MCPTT server | +| Broadcast indicator | O | Indicates that the group call request is for a broadcast group call | +| Implicit floor request (NOTE) | O | Indicates that the originating client requests the floor. | +| Location information | O | Location of the calling party | +| NOTE: | | This element shall be included only when the originating client requests the floor. | + +#### 10.6.2.2.9 Group call request (MCPTT server – MCPTT client) + +Table 10.6.2.2.9-1 describes the information flow group call request from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.9-1 Group call request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is initiated | +| SDP offer | M | Media parameters of MCPTT server | +| Broadcast indicator | O | Indicates that the group call request is for a broadcast group call | + +#### 10.6.2.2.10 Group call response (MCPTT server – MCPTT client) + +Table 10.6.2.2.10-1 describes the information flow group call response from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.10-1 Group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the group call request (success or failure) | + +#### 10.6.2.2.11 Group call response (MCPTT server – MCPTT server) + +Table 10.6.2.2.11-1 describes the information flow group call response between the MCPTT servers. + +**Table 10.6.2.2.11-1 Group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the target MCPTT group member | +| Functional alias | O | The functional alias of the target MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the group call request (success or failure) | + +#### 10.6.2.2.12 Group call response (MCPTT client – MCPTT server) + +Table 10.6.2.2.12-1 describes the information flow group call response from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.12-1 Group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the target MCPTT group member | +| Functional alias | O | The functional alias of the target MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is initiated | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the group call request (success or failure) | + +#### 10.6.2.2.13 Group call notify (MCPTT server – MCPTT client) + +Table 10.6.2.2.13-1 describes the information flow group call notify from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.13-1 Group call notify information elements** + +| Information Element | Status | Description | +|----------------------------------------------------|--------|-----------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| MCPTT ID list (see NOTE) | O | The list of the affiliated MCPTT group members who did not acknowledge the group call request | +| NOTE: Only applicable to acknowledged group calls. | | | + +#### 10.6.2.2.14 Group call release request (MCPTT server – MCPTT client) + +Table 10.6.2.2.14-1 describes the information flow group call release request from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.14-1 Group call release request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +#### 10.6.2.2.14a Group call release request (MCPTT client – MCPTT server) + +Table 10.6.2.2.14a-1 describes the information flow group call release request from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.14a-1 Group call release request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +#### 10.6.2.2.15 Group call release request (MCPTT server – MCPTT server) + +Table 10.6.2.2.15-1 describes the information flow group call release request between the MCPTT servers. + +**Table 10.6.2.2.15-1 Group call release request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +#### 10.6.2.2.16 Group call release response (MCPTT client – MCPTT server) + +Table 10.6.2.2.16-1 describes the information flow group call release response from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.16-1 Group call release response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +#### 10.6.2.2.17 Group call release response (MCPTT server – MCPTT server) + +Table 10.6.2.2.17-1 describes the information flow group call release response between the MCPTT servers. + +**Table 10.6.2.2.17-1 Group call release response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +#### 10.6.2.2.18 Group call rejoin request (MCPTT client – MCPTT server) + +Table 10.6.2.2.18-1 describes the information flow group call rejoin request from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.18-1 Group call rejoin request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the re-joining MCPTT group member | +| Functional alias | O | The functional alias of the re-joining MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is on-going | +| SDP offer | M | Media parameters of MCPTT client | + +#### 10.6.2.2.19 Group call rejoin response (MCPTT server – MCPTT client) + +Table 10.6.2.2.19-1 describes the information flow group call rejoin response from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.19-1 Group call rejoin response information elements** + +| Information Element | Status | Description | +|--------------------------|--------|-----------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member rejoining the group call | +| Functional alias | O | The functional alias of the MCPTT group member re-joining the group call | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is on-going | +| SDP answer | M | Media parameters selected | +| Emergency indicator | O | Indicates that the ongoing group call is an MCPTT emergency group call | +| Imminent peril indicator | O | Indicates that the ongoing group call is an MCPTT imminent peril group call | + +#### 10.6.2.2.20 Group join request + +Table 10.6.2.2.20-1 describes the information flow group join request from the MCPTT client to the MCPTT server and from the (MCPTT user's primary) MCPTT server to the group host MCPTT server. + +**Table 10.6.2.2.20-1 Group join request information elements** + +| Information Element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member joining the group communications for the group | +| Functional alias | O | The functional alias of the MCPTT group member joining the group communication for the group | +| MCPTT group ID | M | The MCPTT group ID of the group to which the group communication is requested | +| SDP offer | M | Media parameters of MCPTT client | +| Implicit floor request (NOTE) | O | Indicates that the originating client requests the floor. | +| Requested priority | O | Application priority level requested for this call | +| NOTE: This element shall be included only when the originating client requests the floor. | | | + +#### 10.6.2.2.21 Group join response + +Table 10.6.2.2.21-1 describes the information flow group join response from the MCPTT server to the MCPTT client and from the group host MCPTT server to the (MCPTT user's primary) MCPTT server. + +**Table 10.6.2.2.21-1 Group join response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member joining the group communications for the group | +| Functional alias | O | The functional alias of the MCPTT group member joining the group communication for the group | +| MCPTT group ID | M | The MCPTT group ID of the group to which the group communication is requested | +| SDP answer | M | Media parameters selected | + +#### 10.6.2.2.22 Group call leave request (MCPTT server – MCPTT client) + +Table 10.6.2.2.22-1 describes the information flow group call leave request from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.22-1 Group call leave request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member which has been de-affiliated | +| Functional alias | O | The functional alias of the MCPTT group member which has been de-affiliated | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is ongoing | + +#### 10.6.2.2.22a Group call leave request (MCPTT client – MCPTT server) + +Table 10.6.2.2.22a-1 describes the information flow group call leave request from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.22a-1 Group call leave request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member leaving the group call | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is on-going | + +#### 10.6.2.2.23 Group call leave response (MCPTT client – MCPTT server) + +Table 10.6.2.2.23-1 describes the information flow group call leave response from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.23-1 Group call leave response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member which has been de-affiliated | +| Functional alias | O | The functional alias of the MCPTT group member which has been de-affiliated | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is on-going | + +#### 10.6.2.2.23a Group call leave response (MCPTT server – MCPTT client) + +Table 10.6.2.2.23a-1 describes the information flow group call leave response from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.23a-1 Group call leave response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member leaving the group call | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is on-going | + +#### 10.6.2.2.24 Group interrogate request (MCPTT server – MCPTT server) + +Table 10.6.2.2.24-1 describes the information flow group interrogate request between two MCPTT servers. + +**Table 10.6.2.2.24-1 Group interrogate request information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester | +| MCPTT group ID | M | The MCPTT group ID of the group being interrogated | + +#### 10.6.2.2.25 Group interrogate response (MCPTT server – MCPTT server) + +Table 10.6.2.2.25-1 describes the information flow group interrogate response between two MCPTT servers. + +**Table 10.6.2.2.25-1 Group interrogate response information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester | +| MCPTT group ID | M | The MCPTT group ID of the group being interrogated | +| MCPTT ID list | M | List of the MCPTT IDs for the MCPTT group members that are members of the MCPTT group ID | + +#### 10.6.2.2.26 Group-broadcast group call request (MCPTT client – MCPTT server) + +Table 10.6.2.2.26-1 describes the information flow group-broadcast group call request from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.26-1 Group-broadcast group call request information elements** + +| Information Element | Status | Description | +|------------------------|--------|----------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| SDP offer | M | Media parameters of MCPTT clients | +| Implicit floor request | M | When originating client requests the floor, this element shall be included | +| Broadcast indicator | M | Indicates that the group call request is for a broadcast group call | +| Location information | O | Location of the calling party | +| Requested priority | O | Application priority level requested for this call | + +#### 10.6.2.2.27 Group-broadcast group call request (MCPTT server – MCPTT client) + +Table 10.6.2.2.27-1 describes the information flow group-broadcast group call request from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.27-1 Group-broadcast group call request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| SDP offer | M | Media parameters of MCPTT clients | +| Broadcast indicator | M | Indicates that the group call request is for a broadcast group call | + +### 10.6.2.2.28 Group-broadcast group call response (MCPTT client – MCPTT server) + +Table 10.6.2.2.28-1 describes the information flow group-broadcast group call response from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.28-1 Group-broadcast group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the target MCPTT group member | +| Functional alias | O | The functional alias of the target MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is initiated | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the group-broadcast group call request (success or failure) | + +### 10.6.2.2.29 Group-broadcast group call response (MCPTT server – MCPTT client) + +Table 10.6.2.2.29-1 describes the information flow group-broadcast group call response from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.29-1 Group-broadcast group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the group-broadcast group call request (success or failure) | + +### 10.6.2.2.30 Group-broadcast group call release request (MCPTT client – MCPTT server) + +Table 10.6.2.2.30-1 describes the information flow group-broadcast group call release request from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.30-1 Group-broadcast group call release request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +### 10.6.2.2.31 Group-broadcast group call release request (MCPTT server – MCPTT client) + +Table 10.6.2.2.31-1 describes the information flow group-broadcast group call release request from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.31-1 Group-broadcast group call release request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +#### 10.6.2.2.32 Group-broadcast group call release response (MCPTT server – MCPTT client) + +Table 10.6.2.2.32-1 describes the information flow group-broadcast group call release response from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.32-1 Group-broadcast group call release response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +#### 10.6.2.2.33 Group-broadcast group call release response (MCPTT client – MCPTT server) + +Table 10.6.2.2.33-1 describes the information flow group-broadcast group call release response from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.33-1 Group-broadcast group call release response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +#### 10.6.2.2.34 Preconfigured regroup request (MCPTT client – MCPTT server) + +Table 10.6.2.2.34-1 describes the information flow preconfigured regroup request from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.34-1 Preconfigured regroup request information elements** + +| Information Element | Status | Description | +|---------------------------------------------------|-----------------|---------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester | +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| MCPTT group ID | M | MCPTT group ID of the MCPTT group from which configuration is to be taken | +| MCPTT group ID list | O
(see NOTE) | List of MCPTT groups to be regrouped into the group regroup group | +| MCPTT user ID list | O
(see NOTE) | List of MCPTT users to be regrouped into the user regroup group | +| NOTE: One and only one of these shall be present. | | | + +#### 10.6.2.2.35 Preconfigured regroup request (MCPTT server – MCPTT client) + +Table 10.6.2.2.35-1 describes the information flow preconfigured regroup request from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.35-1 Preconfigured regroup request information elements** + +| Information Element | Status | Description | +|---------------------------------------------------|-----------------|---------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the target MCPTT group member | +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| MCPTT group ID | M | MCPTT group ID of the MCPTT group from which configuration is to be taken | +| MCPTT group ID list | O
(see NOTE) | List of MCPTT groups to be regrouped into the group regroup group | +| MCPTT user ID list | O
(see NOTE) | List of MCPTT users to be regrouped into the user regroup group | +| NOTE: One and only one of these shall be present. | | | + +#### 10.6.2.2.36 Preconfigured regroup request (MCPTT server – MCPTT server) + +Table 10.6.2.2.36-1 describes the information flow preconfigured regroup request from the MCPTT server to the MCPTT server. + +**Table 10.6.2.2.36-1 Preconfigured regroup request information elements** + +| Information Element | Status | Description | +|---------------------------------------------------|-----------------|---------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester | +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| MCPTT group ID | M | MCPTT group ID of the MCPTT group from which configuration is to be taken | +| MCPTT group ID list | O
(see NOTE) | List of MCPTT groups to be regrouped into the group regroup group | +| MCPTT user ID list | O
(see NOTE) | List of MCPTT users to be regrouped into the user regroup group | +| NOTE: One and only one of these shall be present. | | | + +### 10.6.2.2.37 Preconfigured regroup response (MCPTT client – MCPTT server) + +Table 10.6.2.2.37-1 describes the information flow preconfigured regroup response from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.37-1 Preconfigured regroup response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the responding MCPTT client | +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| Result | M | Result of the regrouping operation | + +### 10.6.2.2.38 Preconfigured regroup response (MCPTT server – MCPTT client) + +Table 10.6.2.2.38-1 describes the information flow preconfigured regroup response from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.38-1 Preconfigured regroup response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester of the regrouping operation | +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| Result | M | Result of the regrouping operation | + +### 10.6.2.2.39 Preconfigured regroup response (MCPTT server – MCPTT server) + +Table 10.6.2.2.39-1 describes the information flow preconfigured regroup response from the MCPTT server to the MCPTT server. + +**Table 10.6.2.2.39-1 Preconfigured regroup response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the responding MCPTT client | +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| Result | M | Result of the regrouping operation | + +### 10.6.2.2.40 Preconfigured regroup cancel request (MCPTT client – MCPTT server) + +Table 10.6.2.2.40-1 describes the information flow preconfigured regroup cancel request from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.40-1 Preconfigured regroup cancel request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester | +| MCPTT group ID | M | MCPTT group ID of the regroup group | + +### 10.6.2.2.41 Preconfigured regroup cancel request (MCPTT server – MCPTT client) + +Table 10.6.2.2.41-1 describes the information flow preconfigured regroup cancel request from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.41-1 Preconfigured regroup cancel request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the target MCPTT user or MCPTT group member | +| MCPTT group ID | M | MCPTT group ID of the regroup group | + +#### 10.6.2.2.42 Preconfigured regroup cancel request (MCPTT server – MCPTT server) + +Table 10.6.2.2.42-1 describes the information flow preconfigured regroup cancel request from the MCPTT server to the MCPTT server. + +**Table 10.6.2.2.42-1 Preconfigured regroup cancel request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester | +| MCPTT group ID | M | MCPTT group ID of the regroup group | + +#### 10.6.2.2.43 Preconfigured regroup cancel response (MCPTT client – MCPTT server) + +Table 10.6.2.2.43-1 describes the information flow preconfigured regroup cancel response from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.43-1 Preconfigured regroup cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the responding MCPTT client | +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| Result | M | Result of the regrouping operation | + +#### 10.6.2.2.44 Preconfigured regroup cancel response (MCPTT server – MCPTT client) + +Table 10.6.2.2.44-1 describes the information flow preconfigured regroup cancel response from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.44-1 Preconfigured regroup cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester of the regroup removal | +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| Result | M | Result of the regrouping operation | + +#### 10.6.2.2.45 Preconfigured regroup cancel response (MCPTT server – MCPTT server) + +Table 10.6.2.2.45-1 describes the information flow preconfigured regroup cancel response from the MCPTT server to the MCPTT server. + +**Table 10.6.2.2.45-1 Preconfigured regroup cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester of the regroup removal | +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| Result | M | Result of the regroup removal operation | + +#### 10.6.2.2.46 Preconfigured regroup reject (MCPTT server – MCPTT client) + +Table 10.6.2.2.46-1 describes the information flow preconfigured regroup reject from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.46-1 Preconfigured regroup reject information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester of the regrouping | +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| Reject reason | M | Reason for rejecting the regrouping operation | + +#### 10.6.2.2.47 Preconfigured regroup reject (MCPTT server – MCPTT server) + +Table 10.6.2.2.47-1 describes the information flow preconfigured regroup reject from the MCPTT server to the MCPTT server. + +**Table 10.6.2.2.47-1 Preconfigured regroup reject information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------| +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| Reject reason | M | Reason for rejecting the regrouping operation | + +### 10.6.2.3 Group call within one MCPTT system + +#### 10.6.2.3.1 Group call models + +##### 10.6.2.3.1.1 Pre-arranged group call + +###### 10.6.2.3.1.1.1 General + +A pre-arranged group call is initiated by one of the affiliated group members. The initiation of a pre-arranged group call results in all other affiliated group members being invited. Media plane resources are reserved (on-demand) or a pre-established session is associated during the group call setup procedure and released (if on-demand session) or de-associated (if pre-established session) when the call is released. SIP signalling is used to setup and release pre-arranged group calls. + +###### 10.6.2.3.1.1.2 Pre-arranged group call setup + +The procedure focuses on the case where an MCPTT client is initiating an MCPTT group call with unicast signalling for communicating with the affiliated MCPTT members of that group. + +Procedures in figure 10.6.2.3.1.1.2-1 are the signalling control plane procedures for the MCPTT client initiating establishment of an MCPTT group call with a pre-arranged group i.e., MCPTT users on client 1, client 2 and client 3 belong to the same group which is defined in the MCPTT group management server. + +Pre-conditions: + +1. A pre-arranged group is an MCPTT group that is pre-defined with MCPTT group ID and member list in the group management server. All members of the group belong to the same MCPTT system. +2. It is assumed that MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 are already registered for receiving MCPTT service and affiliated. Optionally, they may have an activated functional alias to be used during the group communication. +3. The MCPTT server may have subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram titled 'Home MCPTT service provider' showing the pre-arranged group call setup. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. Steps: 1. Initiate group call (client 1), 2. Group call request (client 1 to server), 3. Resolve group ID (server to GMS), 4a. Group call request (server to client 2), 4a. Notify group call (client 2), 4b. Group call request (server to client 3), 4b. Notify group call (client 3), 5. Group call response (client 2 to server), 5. Group call response (client 3 to server), 6. Group call response (server to client 1), 7. Group call notify (server to client 1), 8. Media plane and floor control establishment (all participants).](bccc028d0e75bc30c41528056f581545_img.jpg) + +Sequence diagram titled 'Home MCPTT service provider' showing the pre-arranged group call setup. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. Steps: 1. Initiate group call (client 1), 2. Group call request (client 1 to server), 3. Resolve group ID (server to GMS), 4a. Group call request (server to client 2), 4a. Notify group call (client 2), 4b. Group call request (server to client 3), 4b. Notify group call (client 3), 5. Group call response (client 2 to server), 5. Group call response (client 3 to server), 6. Group call response (server to client 1), 7. Group call notify (server to client 1), 8. Media plane and floor control establishment (all participants). + +**Figure 10.6.2.3.1.1.2-1: Pre-arranged group call setup** + +1. User at MCPTT client 1 would like to initiate an MCPTT group call with a selected group (identified by MCPTT group ID). The MC service user may select a functional alias, which is displayed to other MC service users. + +NOTE 1: MCPTT client 1 need not be aware of the affiliation status of other MCPTT clients to the group while initiating the group call. + +NOTE 2: The selected functional alias is not changed during the group call, i.e. a MCPTT client uses the same functional alias until the group call is released or the MCPTT client has left the group call. + +2. MCPTT client 1 sends a group call request towards the MCPTT server via the SIP core, which hosts the group selected by the user and identified by MCPTT group ID. The group call request also contains the MCPTT group ID and an SDP offer containing the MCPTT client media parameters. If there is a floor request to transmit, then the group call request contains an indication of an implicit floor request. If the MC service user of MCPTT client 1 has selected a functional alias, then the group call request contains that functional alias. If the group call request contains an implicit floor request it may also include location information. +3. The MCPTT server checks whether the user of MCPTT client 1 is authorized to initiate a group call for the selected group. If authorized and the group call is ongoing for that MCPTT group ID, the MCPTT server adds the requesting MCPTT client 1 to the existing MCPTT group call and notifies the MCPTT client 1 that the MCPTT group call is already in progress. Otherwise, MCPTT server resolves the MCPTT group ID to determine + +the members of that group and their affiliation status, based on the information from the group management server. The MCPTT server evaluates the applicable group call start criteria defined for this group (e.g. minimum number of affiliated members, specific members affiliated) and determines whether the group call setup can proceed. + +If present, the MCPTT server checks whether the provided functional alias is allowed to be used and has been activated for the user. + +If location information was included in the group call request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to other users on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking"). + +NOTE 3: MCPTT server can have already retrieved the user/group configuration data and locally cached. If the user/group configuration data is not locally cached on the MCPTT server then MCPTT server requests the user/group configuration data from the MCPTT user database/group management server. + +4. MCPTT server includes information that it communicates using MCPTT service, offers the same media parameters or a subset of the media parameters contained in the initial received request and sends the corresponding group call request via the SIP core towards the MCPTT clients of each of those affiliated group members. MCPTT users are notified about the incoming group call and the functional alias of the group call initiating user is displayed if present. The MCPTT server indicates whether acknowledgement is required for the call and the functional alias of the group call initiating MC service user may be displayed. +5. The receiving MCPTT clients accept the group call request, and a group call response is sent to the group host MCPTT server. This response may contain an acknowledgement. The conditions for sending acknowledgement may be based on configuration. The response may also contain a functional alias of the responding MC service user, which is verified (valid and activated for the user) by the MCPTT server. +6. MCPTT server sends the group call response including the selected media parameters to the MCPTT client 1 through the signalling path to inform about successful call establishment. The response may contain the functional alias, which may be displayed. + +NOTE 4: Step 6 can occur at any time following step 4b, and prior to step 7 depending on the conditions to proceed with the call. + +7. If the initiating MCPTT user requires the acknowledgement from affiliated MCPTT group members, and the required MCPTT group members do not acknowledge the call setup within a configured time (the "acknowledged call setup timeout"), then the MCPTT server may proceed with or abandon the call and then notify the initiating MCPTT user that the acknowledgements did not include all required members according to group policy. The MCPTT server may notify the initiating MCPTT user of all MCPTT group members who did not acknowledge the group call request within the configured time. This notification may be sent to the initiating MCPTT user by the MCPTT server more than once during the call when MCPTT users join or leave the MCPTT group call. +8. MCPTT client 1, client 2 and client 3 have successfully established media plane for communication. MCPTT floor participant 1, floor participant 2 and floor participant 3 exchange floor control information e.g., MCPTT client 1 receives the floor granted information over the established media plane assuming implicit floor control request from MCPTT client 1 while at the same time floor participants at other MCPTT client's receive floor taken information. MCPTT client 1 indicates to the MCPTT user that the floor is available to send media, while the other MCPTT clients in the group call will be receiving that media. If audio cut-in policy is enabled for the MCPTT group, floor arbitration follows the logic defined in subclause 10.9.1.5. + +NOTE 5: The clients use the same functional alias within floor control procedures as used during group call setup. + +#### 10.6.2.3.1.1.3 Release pre-arranged group call + +The procedure focuses on the case where an MCPTT server initiates the termination of an ongoing MCPTT group call for all the participants of that group call, since at least one of the termination conditions are met e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCPTT group members are not present. + +Procedures in figure 10.6.2.3.1.1.3-1 are the signalling control plane procedures for the MCPTT server initiating termination of an ongoing MCPTT group call. + +![Sequence diagram showing the release of a pre-arranged group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3. The process starts with an ongoing group call, followed by a release request from the server, notification of users, release responses, and finally resource release.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +Home MCPTT service provider + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + + Note over MCPTT client 1, MCPTT client 3: 1.Group call ongoing between MCPTT client 1, client 2 and client 3 + Note over MCPTT server: 2.Release group call + Note over MCPTT server: 3. Determine group call participants and generate group call release + MCPTT server->>MCPTT client 1: 4a.Group call release request + Note over MCPTT client 1: 5a.Notify user + MCPTT server->>MCPTT client 2: 4b.Group call release request + Note over MCPTT client 2: 5b.Notify user + MCPTT server->>MCPTT client 3: 4c.Group call release request + Note over MCPTT client 3: 5c.Notify user + MCPTT client 1->>MCPTT server: 6.Group call release response + MCPTT client 2->>MCPTT server: 6.Group call release response + MCPTT client 3->>MCPTT server: 6.Group call release response + Note over MCPTT client 1, MCPTT client 3: 7. Releasing floor control and media plane resources associated with the group call + +``` + +Sequence diagram showing the release of a pre-arranged group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3. The process starts with an ongoing group call, followed by a release request from the server, notification of users, release responses, and finally resource release. + +**Figure 10.6.2.3.1.1.3-1: Release pre-arranged group call** + +1. It is assumed that MCPTT users on MCPTT client 1, client 2 and client 3 are already part of the ongoing group call (e.g., as a result of pre-arranged group call setup). +2. MCPTT server would like to release the MCPTT group call which is ongoing e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCPTT group members are not present. +3. MCPTT server identifies the participants of the ongoing group call and generates group call release request to release ongoing session. +4. MCPTT server sends a group call release request via SIP core towards each participant of the ongoing group call. +5. MCPTT users are notified about the release of the group call. +6. MCPTT client(s) receiving group call release request, acknowledge towards the MCPTT server by sending a group call release response. +7. MCPTT client 1, client 2 and client 3 have successfully released the floor control and media plane resources associated with the group call that is terminated. + +#### 10.6.2.3.1.1.4 Late entry pre-arranged group call + +Procedures in figure 10.6.2.3.1.1.4-1 are the signalling control plane procedures for the MCPTT server requesting a newly affiliated member or a member coming back from out of coverage to join an ongoing MCPTT group call. + +NOTE: This procedure applies to all types of group call, including, for example, emergency call, imminent peril call and broadcast call. + +Pre-condition: + +1. MCPTT group is previously defined on the group management server with MCPTT users affiliated to that group. All members of the group belong to the same MCPTT system. +2. It is assumed that MCPTT users on MCPTT client 2 to MCPTT client n are on an ongoing call. Optionally, the MCPTT users may use activated functional aliases. + +![Sequence diagram for Late entry pre-arranged group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client n. The diagram shows the interaction for a late entry into an ongoing group call.](408c4798ea60469e0728a7cbbd598668_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client n + Note right of MCPTT server: 1. MCPTT client 1 is newly affiliated or coming back from out of network coverage + MCPTT server->>MCPTT client 1: 2. Group call request + Note left of MCPTT client 1: 3. Notify user + MCPTT client 1->>MCPTT server: 4. Group call response + Note over MCPTT client 1, MCPTT client n: 5. MCPTT client 1 is added to ongoing group call + MCPTT server->>MCPTT client 1: 6. Floor taken + +``` + +Sequence diagram for Late entry pre-arranged group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client n. The diagram shows the interaction for a late entry into an ongoing group call. + +**Figure 10.6.2.3.1.1.4-1: Late entry pre-arranged group call** + +1. MCPTT server determines that MCPTT client 1 which is newly affiliated or coming back from out of coverage has to be invited to join an ongoing group call (late entry). +2. MCPTT server generates group call request including the information such as MCPTT service identifier (possible for the SIP core to route the request to the MCPTT server), MCPTT group ID of the group invited to join, offer one or more media types and sends towards the MCPTT client 1 via SIP core. +3. MCPTT user at MCPTT client 1 is notified about the incoming group call. +4. Upon MCPTT user at MCPTT client 1 accepting the incoming group call request, MCPTT client 1 sends the group call response including the selected media types to the MCPTT server through the signalling path. If the incoming group call request is rejected by the MCPTT client 1, the MCPTT server should not resend the group call request. The group call response may also contain a functional alias of MCPTT client 1. +5. MCPTT client 1 is successfully added to the ongoing group call and MCPTT users at MCPTT client 1 to MCPTT client n may be notified about the MCPTT client 1 joining the group call and the functional alias of MCPTT client 1 may be displayed. +6. The floor taken with the information of the current talker is sent to MCPTT client 1. + +#### 10.6.2.3.1.1.5 Rejoining call + +Procedures in figure 10.6.2.3.1.1.5-1 are the signalling control plane procedures for the MCPTT client to rejoin an ongoing MCPTT group call (e.g. coming back from out of coverage). + +Pre-conditions: + +- It is assumed that MCPTT users on MCPTT client 2 to MCPTT client n are on an ongoing call. Optionally, the MCPTT users may use activated functional aliases. + +![Sequence diagram for 'Rejoin call' showing interactions between MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client n under the 'Home MCPTT service provider'.](0a06de972d61ab9bb901bd74dd4ff51f_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client n + Note over MCPTT client 1, MCPTT client n: Home MCPTT service provider + + MCPTT client 1->>MCPTT server: 1. Group call rejoin request + MCPTT server-->>MCPTT client 1: 2. Authorize + MCPTT server-->>MCPTT client 1: 3. Group call rejoin response + Note over MCPTT client 1, MCPTT client n: 4. MCPTT client 1 is added to ongoing group call + MCPTT server-->>MCPTT client 1: 5. Floor taken + +``` + +Sequence diagram for 'Rejoin call' showing interactions between MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client n under the 'Home MCPTT service provider'. + +**Figure 10.6.2.3.1.1.5-1: Rejoin call** + +1. MCPTT client 1 has necessary information for rejoining an ongoing group call, then the MCPTT client 1 initiates group call rejoin request including the ongoing group call information. The group call rejoin request may contain a functional alias of MCPTT client 1 as selected by the MC service user. +2. MCPTT server checks whether the MCPTT client 1 can rejoin the ongoing call (e.g. based upon affiliation status) and checks the functional alias, if present. +3. MCPTT client 1 is informed that the group call rejoin is successful by sending a group call rejoin response. If the ongoing group call is emergency or imminent peril group call, the response shall contain emergency or imminent peril indicator. +4. MCPTT client 1 is successfully added to the ongoing group call and MCPTT users at MCPTT client 1 to MCPTT client n may be notified about the MCPTT client 1 joining the group call and the functional alias of MCPTT client 1 may be displayed. +5. The floor taken with the information of the current talker is sent to MCPTT client 1. + +#### 10.6.2.3.1.2 Chat group call + +##### 10.6.2.3.1.2.1 General + +In a chat group (restricted) call model, the MCPTT user individually joins a group call without being invited. The establishment of a chat group (restricted) call does not result in other group members being invited. + +Figure 10.6.2.3.1.2.2-1 describes the basic procedure for the MCPTT client initiating an MCPTT group call which uses the chat group (restricted) call model. Restricted means that only users that have been configured as members of the given group are allowed to join the group communications for the given group. + +Chat group join mechanism: + +- Each MCPTT client sends a group join request when the MCPTT user wants to participate in the group communication for the group. (This message does not impact the MCPTT user's membership in the group; the MCPTT server will verify that the MCPTT user is an authorized member of the group.) +- The group join request may include a request to transmit. If the group join request includes a request to transmit it may also include location information. It is assumed that the group join request will be delivered from MCPTT client to MCPTT server using SIP. + +- If location information was included in the group join request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to other users on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking"). +- The group join request is used to indicate to the MCPTT server that the MCPTT user associated with the given MCPTT client wishes to participate i.e. begin to receive media from or send media to the group. +- The group join request shall cause the MCPTT server to generate an implicit affiliation for the MCPTT user to the group, if the user is not already affiliated to the group. +- The group join request contains the information needed to negotiate media parameters (on demand) or to associate a pre-established session between MCPTT server and MCPTT client for the group call. The group join request can take the form of a SIP invite. +- A selected functional alias is not changed by a MCPTT client during the whole participation within a chat group call, i.e. a MCPTT client uses the same functional alias selected when joining the chat group call until the chat group call is released or the MCPTT client leaves the chat group call. + +Subsequent participation in a group call when the group is using the chat model: + +- Once an MCPTT client successfully joins a group call which is using the chat model, the MCPTT client connects to the media plane for the call if the call is currently ongoing. +- If the MCPTT group call is not currently ongoing (i.e.: when MCPTT clients on the group call are not sending or receiving media, and the time out between floor control exchanges has expired) then the newly joined MCPTT client will only have pre-established its media parameters for the call. +- If the newly joined MCPTT user wishes to transmit media (start or re-start the call) to the other joined users of the group using the chat model, then the MCPTT client shall use a normal floor control procedure for requesting the floor. +- Since subsequent group call media transmissions are controlled using floor control signalling, additional SIP signalling messages may not be required for subsequent call stop and start. +- Each request to transmit from an MCPTT user could be viewed as a new instance of a group call for the given group when the floor idle timer expires and no media is present for an extended time. +- The MCPTT server may tear down the media plane between successive group calls using the chat model, or the MCPTT server may allow the media plane to remain up between successive group calls using the chat model depending on resources. + +Leaving and releasing a chat group: + +- When a user wants to leave a chat group call, the client shall send a group call leave request to the server and release the media plane. +- The server can release a chat group call by sending a group call release to all joined clients. A server initiated release also releases the media plane for all joined clients. + +#### 10.6.2.3.1.2.2 Chat group call setup + +MCPTT client 1, client 2, and client 3 are served by the home MCPTT service provider in figure 10.6.2.3.1.2.2-1. + +Pre-condition: + +1. MCPTT user 2 and MCPTT user 3 have previously joined (affiliated) to the group. MCPTT client 1, client 2, and client 3 are registered and all users (MCPTT user 1, user 2, and user 3) have been authenticated and authorized to use the MCPTT service. +2. MCPTT client 1, MCPTT client 2 and MCPTT client 3 may have activated functional alias(es) configured to be used during the group call communication. No call is currently in progress for the group. + +![Sequence diagram for MCPTT chat group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3. The sequence starts with MCPTT client 1 sending a '1a. Group join request' to the MCPTT server. The server responds with '1b. MCPTT server receives the group join request.' and '1c. Group join response'. Next, a message '2. MCPTT user 1 requests to transmit causing the media plane to be established (if not pre-established).' is shown. Finally, a wide double-headed arrow labeled '3. Media plane signaling using floor control' spans across all lifelines.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + Note right of MCPTT server: 1b. MCPTT server receives the group join request. + MCPTT client 1->>MCPTT server: 1a. Group join request + MCPTT server-->>MCPTT client 1: 1c. Group join response + Note over MCPTT client 1, MCPTT client 3: 2. MCPTT user 1 requests to transmit causing the media plane to be established (if not pre-established). + Note over MCPTT client 1, MCPTT client 3: 3. Media plane signaling using floor control + +``` + +Sequence diagram for MCPTT chat group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3. The sequence starts with MCPTT client 1 sending a '1a. Group join request' to the MCPTT server. The server responds with '1b. MCPTT server receives the group join request.' and '1c. Group join response'. Next, a message '2. MCPTT user 1 requests to transmit causing the media plane to be established (if not pre-established).' is shown. Finally, a wide double-headed arrow labeled '3. Media plane signaling using floor control' spans across all lifelines. + +**Figure 10.6.2.3.1.2.2-1: MCPTT chat group call** + +1. MCPTT user 1 indicates to join the group communication for the group. This may include a request to transmit. + - 1a. MCPTT client 1 sends a group join request with the MCPTT group ID of the desired group. It contains the MCPTT user's MCPTT ID, the MCPTT client media parameters and optionally a functional alias. If there is a request to transmit, then the group join request contains an indication of an implicit floor request. If the group join request includes an implicit floor request it may also include location information. + - 1b. The MCPTT server receives the group join request. MCPTT server generates an implicit affiliation (if the MCPTT user is not already affiliated to the group) and verifies that MCPTT user 1 is authorized to affiliate to the group by following the affiliation procedure (subclause 10.8.3 in 3GPP TS 23.280 [16]). + + +If present, the MCPTT server checks whether the provided functional alias is allowed to be used and has been activated for the user. + +If location information was included in the group join request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to other users on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking"). + - 1c. The MCPTT server replies with a group join response indicating the acceptance of the group join request and also returns the MCPTT server selected media parameters for the group call in the group join response. +2. If MCPTT user 1 requests to transmit, the MCPTT server establishes the media plane (if not already established) for the call. The associated floor participants for MCPTT client 1, client 2, and client 3 use the floor control procedure to initiate the call. E.g., the floor participant for MCPTT client 1 receives the MCPTT floor grant. The corresponding floor participants for MCPTT client 2 and MCPTT client 3 receive the MCPTT floor taken. If present, the functional alias of MCPTT client 1, MCPTT client 2 and MCPTT client 3 are displayed where appropriate. +3. Floor control will continue to be used by the floor participants associated with MCPTT client 1, MCPTT client 2 and MCPTT client 3 for the duration of the call. Media plane signalling using floor control will be used for subsequent calls for the group as long as one or more users are affiliated. If audio cut-in policy is enabled for the MCPTT group, floor arbitration follows the logic defined in subclause 10.9.1.5. + +### 10.6.2.3.1.2.3 Release chat group call + +The procedure describes the case where the MCPTT server releases an ongoing MCPTT group call for all the participants of that group call, since at least one of the conditions for release are met e.g. due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or the number of affiliated MCPTT group members is below the minimum number permitted. + +NOTE 1: The procedure for an MCPTT user leaving the group call is a different procedure. + +Procedures in figure 10.6.2.3.1.2.3-1 are the procedures for the MCPTT server initiating the release of an ongoing MCPTT group call. + +The following precondition applies: + +- A group call is ongoing between MCPTT clients 1, 2 and 3 + +![Sequence diagram titled 'Home MCPTT service provider' showing the release of a chat group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3. The sequence starts with the server performing internal steps 1 and 2. Step 3a sends a release request to client 1, which triggers 4a (Notify user) and 5 (response). Step 3b sends a release request to client 2, triggering 4b (Notify user) and 5 (response). Step 3c sends a release request to client 3, triggering 4c (Notify user) and 5 (response). Finally, step 6 releases floor control and media plane resources.](b5987d63203a5fa601921039922ac520_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + + Note right of MCPTT server: 1. Release group call + Note right of MCPTT server: 2. Determine group call participants and generate group call release request + + MCPTT server->>MCPTT client 1: 3a. Group call release request + Note left of MCPTT client 1: 4a. Notify user + MCPTT client 1-->>MCPTT server: 5. Group call release response + + MCPTT server->>MCPTT client 2: 3b. Group call release request + Note right of MCPTT client 2: 4b. Notify user + MCPTT client 2-->>MCPTT server: 5. Group call release response + + MCPTT server->>MCPTT client 3: 3c. Group call release request + Note right of MCPTT client 3: 4c. Notify user + MCPTT client 3-->>MCPTT server: 5. Group call release response + + Note bottom: 6. Release floor control and media plane resources associated with the group call + +``` + +Sequence diagram titled 'Home MCPTT service provider' showing the release of a chat group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3. The sequence starts with the server performing internal steps 1 and 2. Step 3a sends a release request to client 1, which triggers 4a (Notify user) and 5 (response). Step 3b sends a release request to client 2, triggering 4b (Notify user) and 5 (response). Step 3c sends a release request to client 3, triggering 4c (Notify user) and 5 (response). Finally, step 6 releases floor control and media plane resources. + +**Figure 10.6.2.3.1.2.3-1: Release chat group call** + +1. MCPTT server would like to release the MCPTT group call which is ongoing e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCPTT group members are not present. +2. MCPTT server identifies the participants of the ongoing group call and generates group call release request to release the ongoing session. +3. MCPTT server sends a group call release request towards each participant of the ongoing group call. + +NOTE 2: The group call release request can also be sent over SIP signalling on the signalling plane. + +4. MCPTT users are notified about the release of the group call. + 5. Optionally the MCPTT client(s) receiving group call release request, may send a group call release response to the MCPTT server. +- NOTE 3: The MCPTT client can send group call release response when the group call release request is sent using a unicast bearer. +6. MCPTT client 1, client 2 and client 3 release the floor control and media plane resources associated with the group call that is released. Successful release of the group call does not affect the status of affiliation of any of the clients. + +**10.6.2.3.1.2.4 Late entry chat group call, newly joined group member** + +Procedures in figure 10.6.2.3.1.2.4-1 are those for a group member entering an ongoing MCPTT group call, i.e. performing a late entry. + +Pre-conditions: + +1. MCPTT user 2 and MCPTT user 3 have previously joined to the group. MCPTT client 1, client 2, and client 3 are registered and all users (MCPTT user 1, user 2, and user 3) have been authenticated and authorized to use the MCPTT service. +2. MCPTT client 1, MCPTT client 2 and MCPTT client 3 may have activated functional alias(es) configured to be used during the group call communication. MCPTT users using MCPTT client 2 and MCPTT client 3 are in an ongoing group call. MCPTT client 1 has not yet joined the group call. Optionally, the MCPTT users may use activated functional aliases. +3. MCPTT user 1 indicates to join the group communication for the group. + +![Sequence diagram showing the interaction for late entry of a new group member. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3. Steps: 1. Group join request (client 1 to server); 2. Perform implicit affiliation and check user authorization (server internal); 3. Group join response (server to client 1); 4. Media plane establishment (client 1 to server); 5. Notify users (server to clients 2 and 3); 6. Floor taken (server to client 1); 7. Media plane signaling using floor control (server to all clients).](077f85b82901283b4657fd2b45fc0294_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + + Note right of MCPTT server: 2. Perform implicit affiliation and check user authorization + MCPTT client 1->>MCPTT server: 1. Group join request + MCPTT server-->>MCPTT client 1: 3. Group join response + MCPTT client 1->>MCPTT server: 4. Media plane establishment + Note right of MCPTT server: 5. Notify users + MCPTT server-->>MCPTT client 1: 6. Floor taken + Note right of MCPTT server: 7. Media plane signaling using floor control + +``` + +Sequence diagram showing the interaction for late entry of a new group member. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3. Steps: 1. Group join request (client 1 to server); 2. Perform implicit affiliation and check user authorization (server internal); 3. Group join response (server to client 1); 4. Media plane establishment (client 1 to server); 5. Notify users (server to clients 2 and 3); 6. Floor taken (server to client 1); 7. Media plane signaling using floor control (server to all clients). + +**Figure 10.6.2.3.1.2.4-1: Late entry of a newly joined group member** + +1. MCPTT client 1 sends a group join request with the MCPTT group ID of the desired group. It contains the MCPTT user's MCPTT ID, the MCPTT client media parameters and optionally a functional alias. If there is a request to transmit, then the group joint request contains an indication of an implicit floor request. + +2. The MCPTT server receives the group join request. MCPTT server generates an implicit affiliation (if the MCPTT user is not already affiliated to the group) and verifies that MCPTT user 1 is authorized to affiliate to the group. + +If present, the MCPTT server checks whether the provided functional alias is allowed to be used and has been activated for the user. + +3. The MCPTT server replies with a group join response indicating the acceptance of the group join request. +4. Media plane between MCPTT client 1 and MCPTT server is established using media plane control signalling. +5. MCPTT users at MCPTT client 2 and MCPTT client 3 may be notified about the MCPTT client 1 joining the group call. The functional aliases of MCPTT client 1 is displayed, if present. +6. The MCPTT server sends a floor taken (for the current talker) to MCPTT client 1. +7. Floor control will continue to be used by the floor participants associated with MCPTT client 1, MCPTT client 2 and MCPTT client 3. + +10.6.2.3.1.2.4a void + +10.6.2.3.1.2.4b void + +10.6.2.3.1.2.5 Late entry chat group call, MCPTT client coming back from out of coverage + +Procedures in figure 10.6.2.3.1.2.5-1 are those for an MCPTT client coming back from out of coverage during an ongoing MCPTT group call. + +Pre-conditions: + +1. MCPTT client 1, MCPTT client 2 and MCPTT client 3 may have activated functional alias(es) configured to be used during the group call communication. MCPTT users using MCPTT client 1, MCPTT client 2 and MCPTT client 3 are in an ongoing group call when MCPTT client1 goes out of radio coverage. +2. MCPTT client1 returns from out of coverage while the group call is still ongoing. + +![Sequence diagram showing the interaction between MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3. The steps are: 1. MCPTT client 1 returns from out of coverage; 2. Re-establish media plane; 3. Floor taken; 4. Notify users (dashed box); 5. Media plane signaling using floor control.](9cd7ec4a653f07d02def283cb6f2309e_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + + Note over MCPTT client 1, MCPTT server: 1. MCPTT client 1 returns from out of coverage + Note over MCPTT client 1, MCPTT server: 2. Re-establish media plane + MCPTT server->>MCPTT client 1: 3. Floor taken + Note over MCPTT server, MCPTT client 2, MCPTT client 3: 4. Notify users + Note over MCPTT client 1, MCPTT client 2, MCPTT client 3: 5. Media plane signaling using floor control + +``` + +Sequence diagram showing the interaction between MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3. The steps are: 1. MCPTT client 1 returns from out of coverage; 2. Re-establish media plane; 3. Floor taken; 4. Notify users (dashed box); 5. Media plane signaling using floor control. + +**Figure 10.6.2.3.1.2.5-1: Late entry of a MCPTT client returning from out of coverage** + +1. MCPTT client 1 or MCPTT server detects that MCPTT client 1 has returned from out of coverage. + +- NOTE 1: How the MCPTT client or MCPTT server detects that the client has returned from out of coverage is out of scope of the present document. +- Media plane between MCPTT client 1 and MCPTT server is re-established using media plane control signalling. +- NOTE 2: Depending on how long MCPTT client 1 was out of coverage, this step can include signalling from MCPTT client 1 to rejoin the chat group. +- MCPTT server sends a floor taken (for the current talker) to MCPTT client 1. + - MCPTT users at MCPTT client 2 and MCPTT client 3 may be notified about the MCPTT client 1 returning to the group call. The functional aliases of MCPTT client 1 is displayed, if present. + - Floor control will continue to be used by the floor participants associated with MCPTT client 1, MCPTT client 2 and MCPTT client 3. + +**10.6.2.3.2 Exiting group call due to de-affiliation** + +Procedures in figure 10.6.2.3.2-1 are the signalling control plane procedures for the MCPTT server requesting a newly de-affiliated member to leave an ongoing MCPTT group call. + +Pre-conditions: + +- MCPTT group is previously defined on the group management server with MCPTT users affiliated to that group. All members of the group belong to the same MCPTT system. +- MCPTT users on MCPTT client 1 to MCPTT client n are on an ongoing call. +- MCPTT client 1 has been de-affiliated from the MCPTT group. + +![Sequence diagram titled 'Home MCPTT service provider' showing the interaction between MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client n. The sequence starts with an ongoing group call (0). Step 1 shows MCPTT client 1 being de-affiliated. Step 2 shows the server sending a leave request to client 1. Step 3 shows client 1 notifying its user. Step 4 shows the user sending a leave response. Step 5 shows client 1 being removed from the call.](31ef15d175af5babdbf4d2fbac884c1b_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client n + Note right of MCPTT server: 0. Group call ongoing between MCPTT client 1 to client n + Note left of MCPTT server: 1. MCPTT client 1 has been de-affiliated from the MCPTT group + MCPTT server->>MCPTT client 1: 2. Group call leave request + Note left of MCPTT client 1: 3. Notify user + MCPTT client 1->>MCPTT server: 4. Group call leave response + Note right of MCPTT server: 5. MCPTT client 1 is removed from the ongoing group call + +``` + +Sequence diagram titled 'Home MCPTT service provider' showing the interaction between MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client n. The sequence starts with an ongoing group call (0). Step 1 shows MCPTT client 1 being de-affiliated. Step 2 shows the server sending a leave request to client 1. Step 3 shows client 1 notifying its user. Step 4 shows the user sending a leave response. Step 5 shows client 1 being removed from the call. + +**Figure 10.6.2.3.2-1: Exiting MCPTT group call due to de-affiliation** + +- MCPTT client 1 which has been de-affiliated is instructed to leave the ongoing group call. +- MCPTT server sends a group call leave request to MCPTT client 1. +- MCPTT user at MCPTT client 1 is notified about leaving the group call. + +4. MCPTT client 1 sends the group call leave response and leaves the group call. +5. MCPTT client 1 is now removed from the ongoing group call and MCPTT users at MCPTT client 2 to MCPTT client n may be notified that MCPTT client 1 has left the group call. + +### 10.6.2.3.3 MCPTT user leaving a group call + +Procedures in figure 10.6.2.3.3-1 are the signalling control plane procedures for the MCPTT user leaving an ongoing MCPTT group call. + +Pre-conditions: + +1. MCPTT group is previously defined on the group management server with MCPTT users affiliated to that group. All members of the group belong to the same MC system. +2. MCPTT users on MCPTT client 1 to MCPTT client n are on an ongoing call. +3. MCPTT user 1 indicates to leave the group call. + +![Sequence diagram illustrating the MCPTT user leaving a group call. The diagram shows four lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client n. The sequence of messages is: 1. MCPTT client 1 sends a 'Group call leave request' to the MCPTT server. 2. The MCPTT server sends a 'Group call leave response' back to MCPTT client 1. 3. MCPTT client 1 sends a 'Release media plane' message to the MCPTT server. 4. The MCPTT server sends a 'Notify users' message to MCPTT client 2 and MCPTT client n.](a057800564be3506d2d87b6a4daee25b_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client n + Note left of MCPTT client 1: 3. Release media plane + MCPTT client 1->>MCPTT server: 1. Group call leave request + MCPTT server-->>MCPTT client 1: 2. Group call leave response + Note right of MCPTT server: 4. Notify users + MCPTT server-->>MCPTT client 2: + MCPTT server-->>MCPTT client n: +``` + +Sequence diagram illustrating the MCPTT user leaving a group call. The diagram shows four lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client n. The sequence of messages is: 1. MCPTT client 1 sends a 'Group call leave request' to the MCPTT server. 2. The MCPTT server sends a 'Group call leave response' back to MCPTT client 1. 3. MCPTT client 1 sends a 'Release media plane' message to the MCPTT server. 4. The MCPTT server sends a 'Notify users' message to MCPTT client 2 and MCPTT client n. + +**Figure 10.6.2.3.3-1: MCPTT user leaving a group call** + +1. MCPTT client 1 sends a group call leave request to the MCPTT server. +2. MCPTT server sends a group call leave response to MCPTT client 1. +3. Release of floor control and media plane resources associated with the group call for MCPTT client 1. + +NOTE 1: MCPTT server checks if group call termination conditions are met, e.g. hang time expiry, last participant leaving, second last participant leaving, initiator leaving, minimum number of affiliated MCPTT group members are not present. If at least one of the group call termination conditions is met, the MCPTT server releases the group call for all participants (see subclauses 10.6.2.3.1.1.3 Release pre-arranged group call and 10.6.2.3.1.2.3 Release chat group call). + +4. MCPTT users at MCPTT client 2 to MCPTT client n may be notified that the MCPTT user of client 1 has left the group call. The functional alias of MCPTT client 1 is displayed, if present. + +NOTE 2: The MCPTT server does not perform late entry for MCPTT users that have left the group call. + +### 10.6.2.4 Group call involving groups from multiple MCPTT systems + +#### 10.6.2.4.1 Group call for non-broadcast temporary groups across multiple MCPTT systems + +##### 10.6.2.4.1.1 Group call setup + +###### 10.6.2.4.1.1.1 Group call setup procedure – originating side + +Figure 10.6.2.4.1.1.1-1 illustrates the originating side group call involving groups from multiple MCPTT systems. It considers the scenario for group hierarchies and non-broadcast temporary groups formed by group regroup. The protocol followed may be SIP. + +Pre-conditions: + +1. The security aspects of sharing the user information between primary and partner MCPTT systems shall be governed as per the service provider agreement between them. In this case, we consider the partner MCPTT system does not share their users' information to the primary MCPTT system. +2. The MCPTT user belongs to an MCPTT group hosted by the primary MCPTT system. +3. A non-broadcast temporary group is formed by authorized MCPTT user/dispatcher by the group regroup procedure (subclause 10.2.4.2 in 3GPP TS 23.280 [16]) and identified via a temporary MCPTT group ID. +4. The affiliated MCPTT group members of the constituent MCPTT groups have been implicitly affiliated to the temporary group. +5. The authorized MCPTT user/dispatcher created the temporary group on the MCPTT server of the primary MCPTT system. +6. The constituent groups of the temporary group may belong to MCPTT servers of the partner MCPTT systems. + +![Sequence diagram for group call setup involving non-broadcast temporary groups from multiple MCPTT systems (originating side).](bdd96f20e71f079cad85240efb3d3f24_img.jpg) + +``` + +sequenceDiagram + participant C as MCPTT client + participant SP as MCPTT server (primary) + participant GMS as Group management server (primary) + participant SK as MCPTT server (partner) + + C->>SP: 1. Group call request + Note over SP, GMS: 2. Get the group information and resolve the constituent groups information + Note over SP: 3. Call the accessible group members + SP->>SK: 4. Group call request + Note over SK: 5. Call the group members + SK->>SP: 6. Group call response + SP->>C: 7. Group call response + Note over C, SK: 8. Group call communication + +``` + +The diagram shows a sequence of 8 steps. Step 1 is a request from the client to the primary server. Step 2 is a dashed box indicating information retrieval between the primary server and the group management server. Step 3 is a solid box within the primary server's timeline for calling accessible members. Step 4 is a request from the primary server to the partner server. Step 5 is a solid box within the partner server's timeline for calling its group members. Step 6 is a response back to the primary server. Step 7 is the final response to the client. Step 8 is a wide horizontal bar across all participants representing the established communication. + +Sequence diagram for group call setup involving non-broadcast temporary groups from multiple MCPTT systems (originating side). + +**Figure 10.6.2.4.1.1.1-1: Group call setup involving non-broadcast temporary groups from multiple MCPTT systems (originating)** + +1. The affiliated MCPTT user via MCPTT client initiates a group call with an MCPTT group ID. A group call request message with the MCPTT group ID is routed to the MCPTT server of the primary MCPTT system, which owns the group and is where the authorized MCPTT user/dispatcher created the temporary group. If the group call is for a temporary group formed by the group regroup procedure, the MCPTT group ID will be a temporary MCPTT group ID. + +2. The MCPTT server of the primary MCPTT system gets the group information (either from group management server or itself) including the constituent MCPTT groups' identities, accessible group members list of the constituent groups, and other related data. +3. The MCPTT server of the primary MCPTT system initiates directly a call request to the accessible group members using the detailed user information and/or location information. The group members upon receipt of the call request may accept or reject the call. +4. The MCPTT server of the primary MCPTT system may not have access to group members' information of the constituent group belonging to the partner MCPTT system. For such group members, the MCPTT server of the primary MCPTT system initiates a group call request message to the MCPTT server of the partner MCPTT system with the target group's MCPTT group ID information. +5. The MCPTT server of the partner MCPTT system further initiates a call request to the constituent group's members as described in step 3. +6. The MCPTT server of the partner MCPTT system provides a group call response to the MCPTT server of the primary MCPTT system with success or failure result and/or detailed reason information if there is a failure. +7. The MCPTT server of the primary MCPTT system provides a group call response message to the MCPTT client of the affiliated MCPTT user upon receiving responses to the call requests sent to members of primary and partner MCPTT systems. The group call response message will consist of the success or failure result and/or detailed reason information if there is a failure. + +NOTE: The group call response message is triggered depending on the conditions to proceed with the call. + +8. Upon successful call setup completion a group call is established for the group members from constituent groups of multiple MCPTT servers. + +**10.6.2.4.1.1.2 Group call setup procedure – terminating side** + +The procedure in figure 10.6.2.4.1.1.2-1 illustrates the terminating side group call involving groups from multiple MCPTT systems. It considers the scenario for group hierarchies and non-broadcast temporary groups formed by group regroup. The protocol followed may be SIP. + +![Sequence diagram showing the terminating side group call setup procedure involving MCPTT server (Primary), MCPTT server (Partner), and MCPTT client (Affiliated MCPTT user).](2438c4dd81a8b76ec881d47d87b11fc3_img.jpg) + +``` + +sequenceDiagram + participant Primary as MCPTT server (Primary) + participant Partner as MCPTT server (Partner) + participant Client as MCPTT client (Affiliated MCPTT user) + + Note right of Partner: 2.Determine to forward the request + Primary->>Partner: 1.Group call request + Partner->>Client: 3.Group call request + Note right of Client: 4.Notify group call + Client->>Partner: 5.Group call response + Partner->>Primary: 6.Group call response + +``` + +Sequence diagram showing the terminating side group call setup procedure involving MCPTT server (Primary), MCPTT server (Partner), and MCPTT client (Affiliated MCPTT user). + +**Figure 10.6.2.4.1.1.2-1: Non-broadcast group call involving groups from multiple MCPTT systems (terminating)** + +1. The MCPTT server of the primary MCPTT system sends the group call request message to the MCPTT server(s) of the partner MCPTT system. +2. The MCPTT server of the partner MCPTT system determines whether to forward the group call request message to the MCPTT client(s) based on the user affiliation. +3. The MCPTT server of the partner MCPTT system forwards the group call request message to MCPTT client(s). The MCPTT server indicates whether acknowledgement is required for the call. +4. The MCPTT user is notified about the incoming MCPTT group call. +5. The receiving MCPTT client(s) accept the group call request and a group call response message is sent to the MCPTT server of the partner MCPTT system. This response may contain an acknowledgement. The conditions for sending acknowledgement may be based on configuration. +6. The MCPTT server of the partner MCPTT system forwards the group call response message to the MCPTT server of the primary MCPTT system (i.e. group hosting MCPTT server for the group call involving groups from multiple MCPTT systems). + +#### 10.6.2.4.1.2 Group call release + +The procedure focuses on the case where the group host MCPTT server releases an ongoing MCPTT group call for all the participants of that group call involving groups from multiple MCPTT systems, since at least one of the release conditions are met e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCPTT group members are not present. + +NOTE: The scenario of MCPTT user leaving the group call is not considered in this procedure. + +Figure 10.6.2.4.1.2-1 illustrates the procedure for the MCPTT server releasing an ongoing MCPTT group call involving groups from multiple MCPTT systems. + +Pre-conditions: + +1. The MCPTT server of the primary MCPTT system is controlling the group call involving groups from multiple MCPTT systems. +2. The MCPTT client 1 belongs to group of the MCPTT server of the primary MCPTT system and the MCPTT client 2 and client 3 belong to the groups of the MCPTT server of the partner MCPTT system. +3. The MCPTT users on MCPTT client 1, client 2 and client 3 are already part of the ongoing group call (e.g., as a result of group call setup involving groups from multiple MCPTT systems). + +![Sequence diagram illustrating the group call release process involving multiple MCPTT systems. Lifelines: MCPTT client 1, MCPTT server (Primary), MCPTT server (Partner), MCPTT client 2, MCPTT client 3. The process involves: 1. Release group call from Primary server; 2. Determine participants; 3. Release requests to clients and partner server; 4. User notifications; 5. Release responses; 6. Resource release.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server (Primary) + participant MCPTT server (Partner) + participant MCPTT client 2 + participant MCPTT client 3 + + Note right of MCPTT server (Primary): 1.Release group call + Note right of MCPTT server (Primary): 2.Determine group call participants and generate group call release + MCPTT server (Primary)->>MCPTT client 1: 3a.Group call release request + MCPTT server (Primary)->>MCPTT server (Partner): 3b.Group call release request + MCPTT client 1->>MCPTT server (Primary): 4a.Notify user + MCPTT server (Partner)->>MCPTT client 2: 3c-1.Group call release request + MCPTT server (Partner)->>MCPTT client 3: 3c-2.Group call release request + MCPTT client 2->>MCPTT server (Partner): 4b-1.Notify user + MCPTT client 3->>MCPTT server (Partner): 4b-2.Notify user + MCPTT client 1->>MCPTT server (Primary): 5a.Group call release response + MCPTT server (Partner)->>MCPTT client 2: 5b-1.Group call release response + MCPTT server (Partner)->>MCPTT client 3: 5b-2.Group call release response + MCPTT client 2->>MCPTT server (Partner): 5c.Group call release response + MCPTT client 3->>MCPTT server (Partner): 5c.Group call release response + Note right of MCPTT server (Partner): 6.Releasing floor control and media plane resources associated with the group call + +``` + +Sequence diagram illustrating the group call release process involving multiple MCPTT systems. Lifelines: MCPTT client 1, MCPTT server (Primary), MCPTT server (Partner), MCPTT client 2, MCPTT client 3. The process involves: 1. Release group call from Primary server; 2. Determine participants; 3. Release requests to clients and partner server; 4. User notifications; 5. Release responses; 6. Resource release. + +**Figure 10.6.2.4.1.2-1: Group call release involving groups from multiple MCPTT systems** + +1. The MCPTT server of primary MCPTT system would like to release the MCPTT group call which is ongoing e.g., due to hang timer expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCPTT group members are not present. +2. The MCPTT server of the primary MCPTT system identifies the participants of the ongoing group call and generates group call release message to release ongoing session. +3. The MCPTT server of the primary MCPTT system initiates a group call release request message via SIP core towards each accessible participant of the ongoing group call (3a). The MCPTT server of the primary MCPTT system may not have access to group members' information of the constituent group belonging to a partner MCPTT system. For such group members, the MCPTT server of the primary MCPTT system initiates a group call release request message (3b) to the MCPTT server(s) of the partner MCPTT system(s) with the target group's MCPTT group ID information. The MCPTT server(s) of the partner MCPTT system(s) further initiate group call release request messages (3c-1, 3c-2) to its group's users. +4. The MCPTT users are notified about the release of the group call. +5. The MCPTT client(s) receiving the group call release request messages provide group call release response to the MCPTT server of the primary MCPTT system. The MCPTT client(s) of the MCPTT users belonging to partner MCPTT system(s) route their responses via the MCPTT server(s) of the partner MCPTT system(s). +6. The MCPTT client 1, client 2 and client 3 have successfully released the floor control and media plane resources associated with the group call that is released. + +#### 10.6.2.4.2 Group call for non-broadcast temporary group formed by group regroup procedure involving multiple MCPTT systems via trusted mode + +Figure 10.6.2.4.2-1 illustrates a group call involving a non-broadcast temporary group formed by group regroup from multiple MCPTT systems. The protocol followed may be SIP. + +Pre-conditions: + +1. The security aspects of sharing the user information between primary and partner MCPTT systems shall be governed as per the service provider agreement between them. In this case, we consider the partner MCPTT system shares their users' information to the primary MCPTT system. + +2. The MCPTT user belongs to an MCPTT group hosted by the primary MCPTT system. +3. A non-broadcast temporary group is formed by authorized MCPTT user/dispatcher by the group regroup procedure (subclause 10.2.4.2 in 3GPP TS 23.280 [16]) and identified via a temporary MCPTT group ID. +4. The MCPTT group members of the constituent MCPTT groups belonging to the temporary group are affiliated to participate in a group call for the temporary group. +5. The authorized MCPTT user/dispatcher created the temporary group on the MCPTT server of the primary MCPTT system. +6. The constituent groups of the temporary group may belong to MCPTT servers of the partner MCPTT systems. + +![Sequence diagram illustrating a group call involving a non-broadcast temporary group formed from multiple MCPTT systems. The diagram shows interactions between an MCPTT client, a primary MCPTT server, a primary group management server, and a partner MCPTT server.](331afcb1534110b4c4f6ddf553a0f7e0_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server (primary) + participant Group management server (primary) + participant MCPTT server (partner) + + Note right of MCPTT server (primary): 2.Get the temporary group information and resolve to constituent groups #1 and #2 + + MCPTT client->>MCPTT server (primary): 1. Group call request + MCPTT server (primary)-->>MCPTT server (partner): 3. Group interrogate request + MCPTT server (partner)-->>MCPTT server (primary): 4. Group interrogate response + MCPTT server (primary)->>MCPTT client: 6. Group call response + Note left of MCPTT server (primary): 5.Call invite/notify members of groups #1 and #2 that satisfy hierarchical group policy + Note bottom: 7.Group call communication + +``` + +Sequence diagram illustrating a group call involving a non-broadcast temporary group formed from multiple MCPTT systems. The diagram shows interactions between an MCPTT client, a primary MCPTT server, a primary group management server, and a partner MCPTT server. + +**Figure 10.6.2.4.2-1: Group call involving non-broadcast temporary group formed by group regroup from multiple MCPTT systems** + +1. The affiliated MCPTT user via MCPTT client initiates a group call with an MCPTT group ID. A group call request message with the MCPTT group ID is routed to the MCPTT server of the primary MCPTT system, which owns the temporary group formed by group regroup procedure, and is also where the authorized MCPTT user/dispatcher has created the temporary group. The MCPTT group ID will be a temporary MCPTT group ID. +2. The MCPTT server of the primary MCPTT system gets the group information (either from group management server or itself) including the constituent MCPTT groups' identities, and other related data. +3. The MCPTT server of the primary MCPTT system may interrogate the MCPTT server of the partner MCPTT system for the affiliated group 2 members. +4. The MCPTT server of the partner MCPTT system responds with a list of the affiliated group members of group 2. + +NOTE 1: Steps 3 and 4 do not occur if the constituent groups' information is available and up to date at primary MCPTT system due to the procedure for temporary group formation as defined in subclause 10.2.4.2 in 3GPP TS 23.280 [16]. + +5. The MCPTT server of the primary MCPTT system verifies the commencement policies of the temporary group, and initiates a call invitation or call notification to the affiliated members of groups 1 and 2. +6. The MCPTT server of the primary MCPTT system provides group call response message to the MCPTT UE of authorized MCPTT user/dispatcher upon receiving responses to the call invitations sent to members of primary and partner MCPTT systems. The group call response will consist of the success or failure result and/or detailed reason information if there is a failure. +7. Upon successful call setup completion a group call is established for the group members belonging to constituent groups of multiple MCPTT systems. + +NOTE 2: MCPTT clients are generally aware that their (constituent) groups have been regrouped (e.g., see subclause 10.1.5.3 in 3GPP TS 23.280 [16]); however, if not, the partner MCPTT server of the constituent group can also respond to a group call request with a redirection response, such as "moved temporarily" that includes the group URI of the temporary group formed by group regroup procedure. + +### 10.6.2.4.3 Group call for an MCPTT group defined in the partner MCPTT system + +#### 10.6.2.4.3.1 Pre-arranged group call setup procedure – initiating side + +Figure 10.6.2.4.3.1-1 illustrates the pre-arranged group call setup procedure for an MCPTT group defined in the partner MCPTT system. + +Pre-conditions: + +1. MCPTT group is defined on the group management server which is located in the partner MCPTT system with MCPTT users affiliated to that group. +2. The members of the MCPTT group defined in partner MCPTT system belong to different MCPTT systems. + +![Sequence diagram showing the pre-arranged group call setup procedure. Lifelines: MCPTT client (Affiliated MCPTT user), MCPTT server (primary), MCPTT server (Group host MCPTT server) (partner), and Group management server. The sequence starts with a Group call request from the client to the primary server, followed by a determination of the group home server, forwarding the request to the partner server, resolving the group ID, calling members, and finally establishing communication.](de98d4c97665a29427651680af184ff4_img.jpg) + +``` + +sequenceDiagram + participant Client as MCPTT client (Affiliated MCPTT user) + participant PrimaryServer as MCPTT server (primary) + participant PartnerServer as MCPTT server (Group host MCPTT server) (partner) + participant GroupManagementServer as Group management server + + Note right of PrimaryServer: 2.Determine the group home MCPTT server based on the group id + Note right of PartnerServer: 4.Resolve group id + Note right of PartnerServer: 5.Call the affiliated group members + + Client->>PrimaryServer: 1.Group call request + PrimaryServer->>PartnerServer: 3.Group call request + PartnerServer->>GroupManagementServer: 4.Resolve group id + PartnerServer->>GroupManagementServer: 5.Call the affiliated group members + PartnerServer->>PrimaryServer: 6.Group call response + PrimaryServer->>Client: 7.Group call response + Note over Client, PrimaryServer, PartnerServer, GroupManagementServer: 8.Group call communication establishment + +``` + +Sequence diagram showing the pre-arranged group call setup procedure. Lifelines: MCPTT client (Affiliated MCPTT user), MCPTT server (primary), MCPTT server (Group host MCPTT server) (partner), and Group management server. The sequence starts with a Group call request from the client to the primary server, followed by a determination of the group home server, forwarding the request to the partner server, resolving the group ID, calling members, and finally establishing communication. + +**Figure 10.6.2.4.3.1-1: Pre-arranged group call setup for an MCPTT group defined in partner MCPTT system (initiating)** + +1. The affiliated MCPTT user via MCPTT client initiates a group call with an MCPTT group ID. A group call request message with the MCPTT group ID is routed to the MCPTT server of the primary MCPTT system. +2. The MCPTT server of the primary MCPTT system determines the group home MCPTT server where the MCPTT group is defined. +3. The MCPTT server of the primary MCPTT system forwards the group call request to the MCPTT server of the partner MCPTT system which owns the group and is where the authorized MCPTT user/dispatcher created the temporary group. + +4. The MCPTT server of the partner MCPTT system checks whether the user of MCPTT client is authorized for initiating the group call for the selected group. If authorized, it resolves the MCPTT group ID to determine the members of that group and their affiliation status, based on the information from group management server. +5. The MCPTT server of the partner MCPTT system initiates a call request to the group's affiliated members. +6. The MCPTT server of the partner MCPTT system provides a group call response message to the MCPTT server of the primary MCPTT system of the MCPTT client. The group call response message will consist of the success or failure result and/or detailed reason information if there is a failure. +7. The MCPTT server of the primary MCPTT system forwards the group call response message to the MCPTT client. +- 8 Upon successful call setup completion a group call is established for the group members. + +10.6.2.4.3.2 Pre-arranged group call setup – terminating side + +The procedure described in figure 10.6.2.4.3.2-1 is used for pre-arranged group call setup when acknowledgement is required from at least some of the call recipients. + +![Sequence diagram showing the pre-arranged group call setup process between a Partner MCPTT server, a Primary MCPTT server, and an MCPTT client.](d6c377ae3e619ff992bd3647dbf43593_img.jpg) + +``` + +sequenceDiagram + participant Partner MCPTT server (Group host MCPTT server) + participant Primary MCPTT server + participant MCPTT client (Affiliated MCPTT user) + + Note right of Primary MCPTT server: 2. Determine forward the request + Note right of MCPTT client: 4. Notify group call + + Partner MCPTT server->>Primary MCPTT server: 1. Group call request + Primary MCPTT server->>MCPTT client: 3. Group call request + MCPTT client->>Primary MCPTT server: 5. Group call response + Primary MCPTT server->>Partner MCPTT server: 6. Group call response + +``` + +Sequence diagram showing the pre-arranged group call setup process between a Partner MCPTT server, a Primary MCPTT server, and an MCPTT client. + +Figure 10.6.2.4.3.2-1: Pre-arranged group call setup for an MCPTT group defined in partner MCPTT system (terminating) + +1. MCPTT server of the partner MCPTT system sends the group call request message towards the MCPTT server of the primary MCPTT system of the MCPTT client. +2. The MCPTT server of the primary MCPTT system determines whether to forward the group call request message to the MCPTT client based on the user subscription. +3. The MCPTT server of the primary MCPTT system forwards the group call request message to MCPTT client. The MCPTT server indicates whether acknowledgement is required for the call. +4. MCPTT user is notified about the incoming group call. +5. The receiving MCPTT client accepts the group call and a response message is sent to the MCPTT server of the primary MCPTT system. This response may contain an acknowledgement. The conditions for sending acknowledgement may be based on configuration. +6. The MCPTT server of the primary MCPTT system forwards the response message to the MCPTT server of the partner MCPTT system (i.e. group hosting MCPTT server). + +### 10.6.2.4.3.3 Chat group call setup + +Figure 10.6.2.4.3.3-1 illustrates the group call setup procedure for an MCPTT chat group defined in the partner MCPTT system. + +Pre-conditions: + +1. The MCPTT users of MCPTT clients 1, 2 and 3 are members of a chat group that is defined in the partner MCPTT system. +2. MCPTT user 2 and MCPTT user 3 have previously joined (affiliated) to the group. MCPTT client 1, client 2, and client 3 are registered and all users (MCPTT user 1, user 2, and user 3) have been authenticated and authorized to use the MCPTT service. +3. MCPTT client 1, MCPTT client 2 and MCPTT client 3 may have activated functional alias(es) configured to be used during the group call communication. +4. No call is currently in progress for the group. + +![Sequence diagram illustrating the chat group call setup for an MCPTT group defined in a partner MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT server (primary), MCPTT server (Group host MCPTT server) (partner), MCPTT client 2, and MCPTT client 3.](f06d7a2fad72d80fe12fca1b65fc805b_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server (primary) + participant MCPTT server (Group host MCPTT server) (partner) + participant MCPTT client 2 + participant MCPTT client 3 + + Note right of MCPTT server (primary): 2. Check user authorization. Determine the group home MCPTT server based on the group id + Note right of MCPTT server (partner): 4. Check authorization. Affiliate the MCPTT user. + Note right of MCPTT server (primary): 6. Store group affiliation status + + MCPTT client 1->>MCPTT server (primary): 1. Group join request + MCPTT server (primary)->>MCPTT server (partner): 3. Group join request + MCPTT server (partner)->>MCPTT server (primary): 5. Group join response + MCPTT server (primary)->>MCPTT client 1: 7. Group join response + Note over MCPTT client 1, MCPTT client 3: 8. MCPTT user 1 requests to transmit causing the media plane to be established (if not pre-established). + Note over MCPTT client 1, MCPTT client 3: 9. Media plane signaling using floor control + +``` + +Sequence diagram illustrating the chat group call setup for an MCPTT group defined in a partner MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT server (primary), MCPTT server (Group host MCPTT server) (partner), MCPTT client 2, and MCPTT client 3. + +**Figure 10.6.2.4.3.3-1: Chat group call setup for an MCPTT group defined in partner MCPTT system** + +1. MCPTT client 1 sends a group join request with the MCPTT group ID of the desired group. If there is a request to transmit, then the group join request contains an indication of an implicit floor request. +2. The MCPTT server of the primary MCPTT system verifies that MCPTT user 1 is authorized to affiliate to the group by following the affiliation procedure (subclause 10.8.3.2 / 10.8.3.2a in 3GPP TS 23.280 [16]). The MCPTT server of the primary MCPTT system determines the group home MCPTT server where the MCPTT group is defined. +3. The MCPTT server of the primary MCPTT system forwards the group join request to the partner MCPTT server i.e. to the the group home MCPTT server. +4. The partner MCPTT server receives the group join request. The partner MCPTT server generates an implicit affiliation (if the MCPTT user 1 is not already affiliated to the group) and verifies that MCPTT user 1 is authorized to affiliate to the group by following the affiliation procedure (subclause 10.8.3 in 3GPP TS 23.280 [16]). + +If present, the MCPTT server checks whether the provided functional alias is allowed to be used and has been activated for the user. + +5. The MCPTT server of the partner MCPTT system replies with a group join response indicating the acceptance of the group join request and also including the MCPTT server selected media parameters for the group call. +6. The primary MCPTT server stores the affiliation status of the user for the requested MCPTT group. +7. The primary MCPTT server forwards the group join response to the MCPTT client. +8. The MCPTT user 1 requests to transmit, causing the media plane to be established (if not already established) for the call. +9. Floor control will continue to be used by the floor participants associated with MCPTT client 1, MCPTT client 2 and MCPTT client 3 for the duration of the call. Media plane signalling using floor control will be used for subsequent calls for the group as long as one or more users are affiliated. + +#### 10.6.2.4.4 Merging of groups involving multiple MCPTT systems + +Figure 10.6.2.4.4-1 below illustrates the merging of MCPTT clients in a newly formed temporary group with active group calls. + +Pre-conditions: + +1. The temporary group consists of group 1, which is hosted by the primary MCPTT system, and group 2, which is hosted by the partner MCPTT system. +2. Both group 1 and group 2 have active calls. +3. The group management client of the authorized MCPTT user belongs to the primary MCPTT system. + +![Sequence diagram illustrating the merging of groups involving multiple MCPTT systems. The diagram shows interactions between an MCPTT client (Authorized MCPTT user), a Primary MCPTT server, a Partner MCPTT server, and an MCPTT client n (Partner). The process involves temporary group formation, group call merge requests and responses, group combine requests and responses, transfer of group 2 clients and metadata, floor control for the temporary group, and a final merge notify.](a7721892ae499a78173ff3dfdc4e65a9_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client (Authorized MCPTT user) + participant MCPTT server (Primary) + participant MCPTT server (Partner) + participant MCPTT client n (Partner) + + Note over MCPTT client, MCPTT server (Partner): 1. Temporary group formation (see figure 10.4.4.2-1) + MCPTT client (Authorized MCPTT user)->>MCPTT server (Primary): 2. Group call merge request + MCPTT server (Primary)-->>MCPTT client (Authorized MCPTT user): 3. Group call merge response + MCPTT server (Primary)->>MCPTT server (Partner): 4. Group combine request + MCPTT server (Partner)-->>MCPTT server (Primary): 5. Group combine response (member details) + Note over MCPTT server (Primary), MCPTT client n (Partner): 6. Transfer group 2 MPCTT clients to temporary group call + Note over MCPTT server (Primary), MCPTT server (Partner): 7. Transfer group 2 meta data (e.g. queues, etc) to MCPTT server (group 1) + Note over MCPTT server (Primary), MCPTT client n (Partner): 8. Floor control temporary group + MCPTT server (Primary)-->>MCPTT client (Authorized MCPTT user): 9. Group call merge notify + +``` + +Sequence diagram illustrating the merging of groups involving multiple MCPTT systems. The diagram shows interactions between an MCPTT client (Authorized MCPTT user), a Primary MCPTT server, a Partner MCPTT server, and an MCPTT client n (Partner). The process involves temporary group formation, group call merge requests and responses, group combine requests and responses, transfer of group 2 clients and metadata, floor control for the temporary group, and a final merge notify. + +**Figure 10.6.2.4.4-1: Merging of groups involving multiple MCPTT systems** + +1. The temporary group formation - group regrouping involving multiple MCPTT systems, according to subclause 10.2.4.2 in 3GPP TS 23.280 [16], takes place. +2. The MCPTT client of the authorized MCPTT user requests group call merge operation to MCPTT server hosting group 1. The identities of the groups being combined are included in this message. +3. The MCPTT server (primary) responds with an OK response. + +4. The MCPTT server (primary) sends a group combine request to the MCPTT server (partner) that is hosting group 2. +5. The MCPTT server (partner) responds with a list members of group 2 and an indication of which members are affiliated and which are active in the call. +6. The MCPTT server (primary) contacts the active members of group 2 inviting them to join the temporary group call. +7. The MCPTT server (partner) transfers group 2's floor status data (including pending requests and queue positions) to the primary MCPTT server and combines this with the group 1's floor status data in order to create the temporary group's floor status data. +8. The MCPTT server (primary) performs floor control for the temporary group. +9. The MCPTT server (primary) notifies the MCPTT client of the authorised MCPTT user that the active calls have been merged. + +NOTE: The MCPTT server in primary system revokes and queues floor given to one of the two talkers based on the arbitration result for the temporary group. + +## 10.6.2.5 Broadcast group call + +### 10.6.2.5.1 General + +A broadcast group call is a special group call where the initiating MCPTT user expects no response from the other MCPTT users, so that when his transmission is complete, so is the call. + +### 10.6.2.5.2 Common broadcast group call procedure + +The group-broadcast group and the broadcast regrouped group are similar in structure (a collection of groups). Similarly the user-broadcast group and the pre-arranged group (a collection of users) are similar in structure. Only the call originator can transmit media during the broadcast group call and the broadcast group call is released when the transmission is complete, unless the call originator is overridden. + +Figure 10.6.2.5.2-1 illustrates the common procedure for group-broadcast group call, user-broadcast group call, and broadcast regrouped group call. + +Pre-conditions: + +1. MCPTT client 1 and MCPTT client 2 are members of a group-broadcast group/user-broadcast group/broadcast regroup group. +2. Optionally, MCPTT client 1 may have an activated functional alias for the group communication. +3. The MCPTT server may have subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for Broadcast group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2. The sequence is: 1. Broadcast group call setup (from client 1 to server and client 2), 2. Media transmission (from client 1 to server and client 2), 3. Broadcast group call release (from server to client 1 and client 2).](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note over MCPTT client 1, MCPTT server, MCPTT client 2: 1. Broadcast group call setup + Note over MCPTT client 1, MCPTT server, MCPTT client 2: 2. Media transmission + Note over MCPTT client 1, MCPTT server, MCPTT client 2: 3. Broadcast group call release + +``` + +Sequence diagram for Broadcast group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2. The sequence is: 1. Broadcast group call setup (from client 1 to server and client 2), 2. Media transmission (from client 1 to server and client 2), 3. Broadcast group call release (from server to client 1 and client 2). + +**Figure 10.6.2.5.2-1: Broadcast group call** + +1. MCPTT user at MCPTT client 1 initiates the broadcast group call setup procedure with the indication of broadcast group call. The signalling procedure is identical to the group call setup as described in subclause 10.6.2 with the inclusion of the parameter for broadcast group call indicator. The MCPTT user at MCPTT client 1 may include a functional alias used for the broadcast group call and the MCPTT server checks whether the provided functional alias can be used and has been activated for the MCPTT user. + +NOTE 1: Broadcast group call applies to both pre-arranged and chat group call model. In the chat group call model case, the broadcast group call setup procedure is done by floor control signalling. + +2. MCPTT client 1 starts to transmit media. + +NOTE 2: Only the call originating MCPTT user is allowed to transmit media on broadcast group call, unless overridden. + +NOTE 3: A broadcast group call transmitted on a user-broadcast group has priority over group calls involving users within the user hierarchy. A broadcast group call transmitted on a group-broadcast group has priority over group calls on its subordinate groups. + +3. If the media transmission from call originating MCPTT user is complete, the broadcast group call is released. + +#### 10.6.2.5.2.1 Group-broadcast group call procedure + +The group-broadcast group is defined as a set of groups, not a set of MCPTT users. The group-broadcast group is also defined with a hierarchy. It is expected that the MCPTT user that originates the group-broadcast group call is the only one transmitting media during the group-broadcast group call and that the group-broadcast group call is terminated when the transmission is complete. However, if the override feature is enabled, then the call originator may be overridden. + +Figure 10.6.2.5.2.1-1 illustrates the procedure for group-broadcast group call establishment. + +Pre-conditions: + +1. The group (e.g. A) to which MCPTT client 1 and MCPTT client 2 are members is a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group A as a subordinate group). +2. The group (e.g. A) currently has an on-going MCPTT group call that is not an MCPTT emergency group call. +3. The call initiator of the group-broadcast group is a member of another group (e.g., X, not group A) which is also a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group X as a subordinate group). +4. The group-broadcast group and its subordinated groups are defined in the same group management server and served by the same MCPTT server. + +5. Optionally, MCPTT client 3 may have an activated functional alias for the group communication. +6. The MCPTT server may have subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for Group-broadcast group call setup. Lifelines: MCPTT client 3, MCPTT server, Group management server, MCPTT client 1, MCPTT client 2. The process involves initiating a call, resolving the group ID, considering on-going calls, releasing existing calls if necessary, and then establishing the new group-broadcast call with media flow.](7c92fa3f1d1b465cc1d3c48a1a8728ff_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 3 + participant MCPTT server + participant Group management server + participant MCPTT client 1 + participant MCPTT client 2 + + Note left of MCPTT client 3: 1. Initiate group-broadcast group call + MCPTT client 3->>MCPTT server: 2. Group-broadcast group call request + MCPTT server->>Group management server: 3. Resolve (group-broadcast) group ID + Note right of MCPTT server: 4. Consider on-going calls on subordinate groups + MCPTT server-->>MCPTT client 1: 5a. Group call release request + MCPTT server-->>MCPTT client 2: 5b. Group call release request + Note right of MCPTT client 1: 6a. Notify user + Note right of MCPTT client 2: 6b. Notify user + MCPTT client 1-->>MCPTT server: 7a. Group call release response + MCPTT client 2-->>MCPTT server: 7b. Group call release response + MCPTT server->>MCPTT client 1: 8a. Group-broadcast group call request + MCPTT server->>MCPTT client 2: 8b. Group-broadcast group call request + Note right of MCPTT client 1: 9a. Notify group-broadcast group call + Note right of MCPTT client 2: 9b. Notify group-broadcast group call + MCPTT client 1-->>MCPTT server: 10a. Group-broadcast group call response + MCPTT client 2-->>MCPTT server: 10b. Group-broadcast group call response + MCPTT server-->>MCPTT client 3: 11. Group-broadcast group call response + Note left of MCPTT client 3: 12. Notify user + Note right of MCPTT client 3: Media Flow + Note right of MCPTT server: Media Flow + Note right of MCPTT client 1: Media Flow + +``` + +Sequence diagram for Group-broadcast group call setup. Lifelines: MCPTT client 3, MCPTT server, Group management server, MCPTT client 1, MCPTT client 2. The process involves initiating a call, resolving the group ID, considering on-going calls, releasing existing calls if necessary, and then establishing the new group-broadcast call with media flow. + +**Figure 10.6.2.5.2.1-1: Group-broadcast group call** + +1. MCPTT user at MCPTT client 3 initiates the group-broadcast group call setup procedure. +2. The MCPTT client 3 sends a group-broadcast group call request to the MCPTT server. The MCPTT user at MCPTT client 1 may include a functional alias used for the broadcast group call. +3. The MCPTT server checks whether the provided functional alias can be used and has been activated for the MCPTT user. The MCPTT server needs to resolve the group-broadcast group ID into its subordinate groups in order to contact the affiliated MCPTT users of those subordinate groups. +4. The MCPTT server then needs to consider any on-going group calls on those subordinate groups because this may affect the behaviour for what happens next. In this case a group call exists on a subordinate group. Thus, the MCPTT users involved in the group call on this subordinate group. +5. Optionally the on-going group call on a subordinate group may be terminated in which case the MCPTT client 1 and MCPTT client 2 need to be sent a Group call release request. +6. The MCPTT client 1 and MCPTT client 2 then notify their users of the group call release request. + +7. The MCPTT client 1 and MCPTT client 2 respond to the group call release request by sending a group call release response. +8. A group-broadcast group call request is sent to both the MCPTT client 1 and the MCPTT client 2. The request may contain the functional alias of the calling party. +9. MCPTT client 1 and MCPTT client 2 notify their users of the incoming group-broadcast group call. The functional alias of the calling party, if available, is presented to the users. +10. MCPTT client 1 and MCPTT client 2 respond to the group-broadcast group call request by sending a group-broadcast group call response. +11. The MCPTT server responds to MCPTT client 3 (the call initiator) that the group-broadcast group call has been established by sending a group-broadcast group call response. +12. The MCPTT client 3 notifies its user that the user can begin transmitting using the group-broadcast group call resources. + +Resources are now available for the transmission from MCPTT client 3 to MCPTT client 1 and MCPTT client 2. Once the user of MCPTT client 3 completes transmitting, the group-broadcast group call is released as are the resources. + +#### 10.6.2.5.2.2 Group-broadcast group call procedure when a subordinate group has an on-going MCPTT emergency group call + +The group-broadcast group is defined as a set of groups, not MCPTT users. The affiliated MCPTT group members of a subordinate group with an on-going MCPTT emergency group call are not interrupted by a group-broadcast group call. + +Figure 10.6.2.5.2.2-1 illustrates the procedure for group-broadcast group call when a subordinate group has an on-going MCPTT emergency group call. + +Pre-conditions: + +1. MCPTT The group (e.g. A) to which MCPTT client 1 and MCPTT client 2 are members is a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group A as a subordinate group). +2. The group (e.g. A) currently has an on-going MCPTT emergency group call. +3. The call initiator (user of MCPTT client 3) of the group-broadcast group is a member of another group (e.g., X, not group A) which is also a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group X as a subordinate group). + +![Sequence diagram for Figure 10.6.2.5.2.2-1: Group-broadcast group call when an emergency group call is on-going in one of the subordinate groups. The diagram shows interactions between MCPTT client 3, MCPTT server, Group management server, MCPTT client 1, and MCPTT client 2. The sequence starts with MCPTT client 3 initiating a group-broadcast group call. The MCPTT server resolves the group ID and considers on-going calls on subordinate groups. The MCPTT server then responds to MCPTT client 3, which notifies its user. A media flow is established between MCPTT client 3 and the MCPTT server.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 3 + participant MCPTT server + participant Group management server + participant MCPTT client 1 + participant MCPTT client 2 + + Note left of MCPTT client 3: 1. Initiate group-broadcast group call + MCPTT client 3->>MCPTT server: 2. Group-broadcast group call request + Note right of MCPTT server: 3. Resolve (group-broadcast) group ID + Note right of MCPTT server: 4. Consider on-going calls on subordinate groups + MCPTT server->>MCPTT client 3: 5. Group-broadcast group call response + Note left of MCPTT client 3: 6. Notify user + Note right of MCPTT client 3: Media Flow + +``` + +Sequence diagram for Figure 10.6.2.5.2.2-1: Group-broadcast group call when an emergency group call is on-going in one of the subordinate groups. The diagram shows interactions between MCPTT client 3, MCPTT server, Group management server, MCPTT client 1, and MCPTT client 2. The sequence starts with MCPTT client 3 initiating a group-broadcast group call. The MCPTT server resolves the group ID and considers on-going calls on subordinate groups. The MCPTT server then responds to MCPTT client 3, which notifies its user. A media flow is established between MCPTT client 3 and the MCPTT server. + +**Figure 10.6.2.5.2.2-1: Group-broadcast group call when an emergency group call is on-going in one of the subordinate groups** + +1. The MCPTT user at MCPTT client 3 initiates the group-broadcast group call setup procedure. +2. The MCPTT client 3 sends a group-broadcast group call request to the MCPTT server. +3. The MCPTT server needs to resolve the group-broadcast group ID into its subordinate groups in order to contact the affiliated MCPTT group members of those subordinate groups. +4. The MCPTT server then considers any on-going group calls on those subordinate groups (e.g. A) because this may effect the behaviour for what happens next. In this case an emergency group call exists on a subordinate group. + +NOTE: Not shown - The group-broadcast group call request is sent to the MCPTT clients of the MCPTT users who are affiliated members of any other subordinate groups of the group-broadcast group being set up + +5. The MCPTT server responds to the call initiator that the group-broadcast group call has been established. +6. The MCPTT client 3 notifies its user that the user can begin transmitting using the group-broadcast group call resources. + +Resources are now available for the transmission from MCPTT client 3 to the MCPTT clients (not shown) of other subordinate groups (i.e., not A). Once the user of MCPTT cleint 3 completes transmitting, the group-broadcast group call is releases as are the resources. + +### 10.6.2.5.2.3 Group-broadcast group call release procedure + +When the call originator has completed transmitting, the group-broadcast group call is terminated and resources released. + +Figure 10.6.2.5.2.3-1 illustrates the procedure for group-broadcast group call release. + +Pre-conditions: + +1. An on-going group-broadcast group call involving MCPTT client 1, MCPTT client 2, and MCPTT client 3 exists. + +![Sequence diagram for Figure 10.6.2.5.2.3-1: Group-broadcast group call transmission ended. The diagram shows the interaction between MCPTT client 3, MCPTT server, Group management server, MCPTT client 1, and MCPTT client 2. The sequence starts with MCPTT client 3 sending a '1. Finished transmitting' message to the MCPTT server. The MCPTT server then sends a '2. Group-broadcast group call release request' to the Group management server. The Group management server sends '3a. Group-broadcast group call release request' to MCPTT client 1 and '3b. Group-broadcast group call release request' to MCPTT client 2. MCPTT client 1 and MCPTT client 2 then send '4a. Notify user' and '4b. Notify user' messages respectively. They then send '5a. Group-broadcast group call release response' and '5b. Group-broadcast group call release response' to the MCPTT server. Finally, the MCPTT server sends '6. Group-broadcast group call release response' to MCPTT client 3.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 3 + participant MCPTT server + participant Group management server + participant MCPTT client 1 + participant MCPTT client 2 + + Note left of MCPTT client 3: 1. Finished transmitting + MCPTT client 3->>MCPTT server: 2. Group-broadcast group call release request + MCPTT server->>Group management server: 3a. Group-broadcast group call release request + MCPTT server->>MCPTT client 2: 3b. Group-broadcast group call release request + Note right of MCPTT client 1: 4a. Notify user + Note right of MCPTT client 2: 4b. Notify user + MCPTT client 1->>MCPTT server: 5a. Group-broadcast group call release response + MCPTT client 2->>MCPTT server: 5b. Group-broadcast group call release response + MCPTT server->>MCPTT client 3: 6. Group-broadcast group call release response + +``` + +Sequence diagram for Figure 10.6.2.5.2.3-1: Group-broadcast group call transmission ended. The diagram shows the interaction between MCPTT client 3, MCPTT server, Group management server, MCPTT client 1, and MCPTT client 2. The sequence starts with MCPTT client 3 sending a '1. Finished transmitting' message to the MCPTT server. The MCPTT server then sends a '2. Group-broadcast group call release request' to the Group management server. The Group management server sends '3a. Group-broadcast group call release request' to MCPTT client 1 and '3b. Group-broadcast group call release request' to MCPTT client 2. MCPTT client 1 and MCPTT client 2 then send '4a. Notify user' and '4b. Notify user' messages respectively. They then send '5a. Group-broadcast group call release response' and '5b. Group-broadcast group call release response' to the MCPTT server. Finally, the MCPTT server sends '6. Group-broadcast group call release response' to MCPTT client 3. + +**Figure 10.6.2.5.2.3-1: Group-broadcast group call transmission ended** + +1. MCPTT user on MCPTT client 3 finished transmitting. +2. A group-broadcast group call release request is sent to the MCPTT server of the group-broadcast group. +3. The MCPTT users of MCPTT client 1 and MCPTT client 2 of the group-broadcast group's subordinate groups are sent a group-broadcast group call release request +4. MCPTT client 1 and MCPTT client 2 notify their users that the group-broadcast group call has ended. +5. MCPTT client 1 and MCPTT client 2 respond to confirm the release of the group-broadcast group call by sending a group-broadcast group call release response. +6. The MCPTT server sends a group-broadcast group call release response indicating to the initiator that the call is now terminated. + +#### 10.6.2.5.2.4 Server-initiated broadcast group call release procedure + +In a broadcast group call, when the call originator has completed transmitting, the MCPTT client releases the floor. Upon receiving the floor release message the MCPTT server then determines if the broadcast call should be released. + +Figure 10.6.2.5.2.4-1 illustrates the procedure for server-initiated broadcast group call release. + +Pre-conditions: + +1. An on-going broadcast group call involving MCPTT client 1, MCPTT client 2, and MCPTT client 3 exists. +2. MCPTT client 3 is transmitting. + +![Sequence diagram for Server-initiated broadcast group call release. Lifelines: MCPTT client 3, MCPTT server, MCPTT client 1, MCPTT client 2. The sequence starts with MCPTT client 3 finishing transmitting, followed by a Floor release message to the server. The server evaluates the group type and hang time, then sends Group call release requests to all clients. Clients 1 and 2 notify their users, and all clients send Group call release responses back to the server.](18bb06865e2dada3656ea3d57f290f7f_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 3 + participant MCPTT server + participant MCPTT client 1 + participant MCPTT client 2 + + Note left of MCPTT client 3: 1. Finished transmitting + MCPTT client 3->>MCPTT server: 2. Floor release + Note right of MCPTT server: 3. Evaluate group type and hang time + MCPTT server->>MCPTT client 1: 4. Group call release request + MCPTT server->>MCPTT client 2: 4. Group call release request + MCPTT server->>MCPTT client 3: 4. Group call release request + Note right of MCPTT client 1: 5. Notify user + Note right of MCPTT client 2: 5. Notify user + MCPTT client 1->>MCPTT server: 6. Group call release response + MCPTT client 2->>MCPTT server: 6. Group call release response + MCPTT client 3->>MCPTT server: 6. Group call release response + +``` + +Sequence diagram for Server-initiated broadcast group call release. Lifelines: MCPTT client 3, MCPTT server, MCPTT client 1, MCPTT client 2. The sequence starts with MCPTT client 3 finishing transmitting, followed by a Floor release message to the server. The server evaluates the group type and hang time, then sends Group call release requests to all clients. Clients 1 and 2 notify their users, and all clients send Group call release responses back to the server. + +**Figure 10.6.2.5.2.4-1: Server-initiated broadcast group call release** + +1. MCPTT user on MCPTT client 3 finished transmitting. +2. MCPTT client 3 sends a Floor release message to the MCPTT server of the group. +3. The MCPTT Server determines that the group is a broadcast group and decides that the call should be released. + +NOTE 1: Whether the MCPTT server uses the Broadcast indicator in the originating group call request message or uses the configured Group call hang timer to determine whether the call should be released is left to implementation. + +4. The MCPTT server sends a Group call release request to MCPTT clients 1, 2, and 3. +5. MCPTT client 1 and MCPTT client 2 notify their users that the group call has ended. +6. MCPTT clients 1, 2, and 3 respond to confirm the release of the group call by sending a group call release response. + +NOTE 2: If the group call release request is sent from the MCPTT server via MBMS, no response is expected from the MCPTT clients. + +#### 10.6.2.5.3 Void + +#### 10.6.2.5.4 Group call for broadcast temporary groups across multiple MCPTT systems + +Figure 10.6.2.5.4-1 illustrates the procedure for broadcast temporary group calls across multiple MCPTT systems. + +Pre-conditions: + +1. The security aspects of sharing the user information between primary and partner MCPTT systems shall be governed as per the service provider agreement between them. In this case, we consider the partner MCPTT system does not share their users' information to the primary MCPTT system. + +2. A broadcast temporary group is formed on the MCPTT server of the primary MCPTT system by an authorized MCPTT user (e.g. dispatcher) by the group regroup procedure (subclause 10.2.4.2 in 3GPP TS 23.280 [16]) and identified via a temporary MCPTT group ID. +3. The affiliated MCPTT group members of the constituent MCPTT groups have been implicitly affiliated to the temporary group. +4. The MCPTT user of the MCPTT client is authorized to transmit on a broadcast temporary group. +5. One or more of the constituent groups of the temporary group may belong to MCPTT servers of partner MCPTT systems. + +![Sequence diagram illustrating a group call involving a broadcast temporary group across multiple MCPTT systems. The diagram shows interactions between an MCPTT client, a primary MCPTT server, a primary group management server, and a partner MCPTT server.](b87818c8505328b198d035761bbc3f2d_img.jpg) + +``` +sequenceDiagram + participant MCPTT client + participant MCPTT server (primary) + participant Group management server (primary) + participant MCPTT server (partner) + + Note right of MCPTT server (primary): 2. Get the group information and resolve the constituent groups information + Note right of MCPTT server (primary): 3. Call the accessible group members + Note right of MCPTT server (partner): 5. Call the group members + + MCPTT client->>MCPTT server (primary): 1. Group call request + MCPTT server (primary)->>Group management server (primary): 2. Get the group information and resolve the constituent groups information + MCPTT server (primary)->>MCPTT server (primary): 3. Call the accessible group members + MCPTT server (primary)->>MCPTT server (partner): 4. Group call request + MCPTT server (partner)->>MCPTT server (partner): 5. Call the group members + MCPTT server (partner)->>MCPTT server (primary): 6. Group call response + MCPTT server (primary)->>MCPTT client: 7. Group call response + Note right of MCPTT client: 8. Media transmission + Note right of MCPTT server (primary): 8. Media transmission + Note right of MCPTT server (primary): 9. Broadcast group call is released +``` + +Sequence diagram illustrating a group call involving a broadcast temporary group across multiple MCPTT systems. The diagram shows interactions between an MCPTT client, a primary MCPTT server, a primary group management server, and a partner MCPTT server. + +**Figure 10.6.2.5.4-1: Group call involving a broadcast temporary group across multiple MCPTT systems** + +1. The MCPTT user via MCPTT client initiates a group call for a broadcast temporary group with an MCPTT group ID, temporary group indicator, and the broadcast indicator. A group call request message with the MCPTT group ID is routed to the MCPTT server of the primary MCPTT system, which owns the group and is where the authorized MCPTT user/dispatcher created the broadcast temporary group. The MCPTT group ID is a temporary MCPTT group ID. +2. The MCPTT server of the primary MCPTT system obtains the temporary group information (either from group management server or itself) including the constituent MCPTT groups' identities, accessible group members list of the constituent groups, the broadcast group type, and other related data. +3. The MCPTT server of the primary MCPTT system initiates directly a call request to the accessible group members using the detailed user information and/or location information. The group members upon receipt of the call request may accept or reject the call. +4. The MCPTT server of the primary MCPTT system may not have access to group members' information of the constituent group belonging to the partner MCPTT system. For such group members, the MCPTT server of the primary MCPTT system initiates a group call request message to the MCPTT server of the partner MCPTT system with the target group's MCPTT group ID information. +5. The MCPTT server of the partner MCPTT system further initiates a call request to the clients of the constituent group's members as described in step 3. + +6. The MCPTT server of the partner MCPTT system provides a group call response to the MCPTT server of the primary MCPTT system with success or failure result and/or detailed reason information if there is a failure. +7. The MCPTT server of the primary MCPTT system provides a group call response message to the MCPTT client of the affiliated MCPTT user upon receiving responses to the call requests sent to members of primary and partner MCPTT systems. The group call response message will consist of the success or failure result and/or detailed reason information if there is a failure. + +NOTE 1: The group call response message is triggered depending on the conditions to proceed with the call. + +8. Upon successful call setup completion a broadcast group call is established for the group members from constituent groups of multiple MCPTT servers. The call originating MCPTT user starts transmitting media to other group call participants. The media is also distributed to the partner MCPTT system. + +NOTE 2: Only the call originating MCPTT user is allowed to transmit media on a broadcast temporary group call. + +9. At the completion of the media transmission, the broadcast temporary group call is released. + +## 10.6.2.6 Emergency and imminent peril procedures + +### 10.6.2.6.1 MCPTT emergency group call + +#### 10.6.2.6.1.1 MCPTT emergency group call commencement + +The procedure focuses on the case where an MCPTT client is initiating an MCPTT emergency group call with the affiliated MCPTT members of that MCPTT group. An MCPTT client in the MCPTT emergency state gains elevated access privilege for all of the MCPTT user's mission critical applications. + +Procedures in figure 10.6.2.6.1.1-1 are the signalling control plane procedures for the MCPTT client initiating establishment of an MCPTT emergency group call with an MCPTT group i.e., MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 belong to the same MCPTT group which is defined on MCPTT group management server. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group. +2. All members of the MCPTT group belong to the same MCPTT system. +3. The initiating MCPTT client 1 has been provisioned with an MCPTT group that has been designated via provisioning as the MCPTT emergency group. +4. Optionally, MCPTT client 1 may use an activated functional alias for the group communication. +5. The MCPTT server may have subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +NOTE 2: Alternatively, the client could have been provisioned for emergency behaviour on the selected group. + +![Sequence diagram for MCPTT emergency group call. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The sequence shows the initiation of an emergency group call from client 1, processing by the server and group management server, notification to clients 2 and 3, and a response back to client 1.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +Home MCPTT service provider + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note left of MCPTT client 1: 1. initiate MCPTT emergency group call + MCPTT client 1->>MCPTT server: 2. MCPTT emergency group call request + Note right of MCPTT server: 3. Affiliate user to group + Note right of MCPTT server: 4. Resolve group id + Note right of MCPTT server: 5. Bearer priority configuration + MCPTT server->>MCPTT client 2: 6. MCPTT emergency group call request + MCPTT server->>MCPTT client 3: 6. MCPTT emergency group call request + Note right of MCPTT client 2: 7. Notify MCPTT emergency group call + Note right of MCPTT client 3: 7. Notify MCPTT emergency group call + MCPTT client 2->>MCPTT server: 8. MCPTT emergency group call response + MCPTT client 3->>MCPTT server: 8. MCPTT emergency group call response + MCPTT server->>MCPTT client 1: 9. MCPTT emergency group call response + +``` + +Sequence diagram for MCPTT emergency group call. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The sequence shows the initiation of an emergency group call from client 1, processing by the server and group management server, notification to clients 2 and 3, and a response back to client 1. + +**Figure 10.6.2.6.1.1-1: MCPTT emergency group call** + +1. The user at the MCPTT client 1 initiates an MCPTT emergency group call. MCPTT client 1 sets its MCPTT emergency state. The MCPTT user at MCPTT client 1 may select a functional alias used for the call. The MCPTT emergency state is retained until explicitly cancelled. +2. MCPTT client 1 sends an MCPTT emergency group call request towards the MCPTT server. The MCPTT server records the identity of the MCPTT user that initiated the MCPTT emergency group call until the MCPTT emergency is cancelled. Once an MCPTT emergency call has been initiated, the MCPTT group is considered to be in an in-progress emergency state until cancelled. If configured to send an MCPTT emergency alert when initiating an MCPTT emergency group call, the request also contains an indication that an MCPTT emergency alert is to be initiated. The request may contain an indication of an implicit floor request. +3. The MCPTT server implicitly affiliates MCPTT client 1 to the emergency group if the client is not already affiliated. +4. MCPTT server checks whether the MCPTT user of MCPTT client 1 is authorized for initiation of MCPTT emergency calls on the indicated MCPTT group, and if authorized, it resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status, based on the information from group management server. The MCPTT server checks whether the provided functional alias, if present, can be used and has been activated for the user. +5. The MCPTT server configures the priority of the underlying bearers for all participants in the MCPTT group. + +NOTE 3: Successive calls during the MCPTT group's in-progress emergency state will all receive the adjusted bearer priority. + +6. MCPTT server sends the MCPTT emergency group call request towards the MCPTT clients of each of those affiliated MCPTT group members. The request contains an indication of the in-progress emergency. The request contains an indication of an MCPTT emergency alert if the request from the originator indicated MCPTT emergency alert. +7. MCPTT users are notified of the incoming MCPTT emergency group call. The functional alias of the group call initiating MCPTT user may be displayed. +8. The receiving MCPTT clients send the MCPTT emergency group call response to the MCPTT server to acknowledge the MCPTT emergency group call request. For a multicast call, these acknowledgements are not sent. The receiving MCPTT client check whether it is already involved in an MCPTT emergency group call when using this functional alias and whether the maximum number of parallel MCPTT emergency group calls when using this functional alias has been reached. +9. The MCPTT server sends the MCPTT emergency group call response to the MCPTT user 1 to inform the successful MCPTT emergency call establishment. + +NOTE 4: Step 9 can occur at any time following step 5, and prior to step 10 depending on the conditions to proceed with the call. + +MCPTT client 1, MCPTT client 2 and MCPTT client 3 have successfully established media plane for communication. MCPTT floor participant 1, floor participant 2 and floor participant 3 exchange floor control information e.g., MCPTT client 1 receives the floor granted information over the established media plane, while the other MCPTT client's receive floor taken information. MCPTT client 1 indicates to the MCPTT user that the floor is available to send media, while the other MCPTT clients in the MCPTT emergency group call will be receiving that media. MCPTT client 1 can override other clients in the call except those that are also in the MCPTT emergency state. + +#### 10.6.2.6.1.2 MCPTT group call upgraded to an MCPTT emergency group call + +The procedure focuses on the case where an authorized MCPTT user is upgrading an MCPTT group call to an MCPTT emergency group call while the MCPTT group call is already in progress. + +Procedures in figure 10.6.2.6.1.2-1 are the signalling control plane procedures for the MCPTT client upgrading an MCPTT group call on an MCPTT group to an MCPTT emergency group call. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group. +2. All members of the MCPTT group belong to the same MCPTT system. +3. An MCPTT group call is already in progress. +4. The initiating MCPTT client 1 has been configured to send an MCPTT emergency alert when upgrading an MCPTT emergency group call. + +![Sequence diagram showing the upgrade of an MCPTT group call to an emergency group call. The diagram is titled 'Home MCPTT service provider' and shows a 'Group call already in progress'. Lifelines include MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, and MCPTT client 3. The sequence of messages is: 1. Initiate group emergency (from client 1), 2. MCPTT emergency group call request (from client 1 to server), 3. Bearer priority adjustment (internal to server), 4. MCPTT emergency group call request (from server to clients 2 and 3), 5. Notify group emergency status (from clients 2 and 3), 6. MCPTT emergency group call response (from clients 2 and 3 to server), 7. MCPTT emergency group call response (from server to client 1).](c07e21a8d65991db04263322f859c94f_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note over MCPTT client 1, MCPTT client 3: Group call already in progress + + MCPTT client 1->>MCPTT server: 1. Initiate group emergency + MCPTT client 1->>MCPTT server: 2. MCPTT emergency group call request + Note over MCPTT server: 3. Bearer priority adjustment + MCPTT server->>MCPTT client 2: 4. MCPTT emergency group call request + MCPTT server->>MCPTT client 3: 4. MCPTT emergency group call request + Note over MCPTT client 2: 5. Notify group emergency status + Note over MCPTT client 3: 5. Notify group emergency status + MCPTT client 2->>MCPTT server: 6. MCPTT emergency group call response + MCPTT client 3->>MCPTT server: 6. MCPTT emergency group call response + MCPTT server->>MCPTT client 1: 7. MCPTT emergency group call response + +``` + +Sequence diagram showing the upgrade of an MCPTT group call to an emergency group call. The diagram is titled 'Home MCPTT service provider' and shows a 'Group call already in progress'. Lifelines include MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, and MCPTT client 3. The sequence of messages is: 1. Initiate group emergency (from client 1), 2. MCPTT emergency group call request (from client 1 to server), 3. Bearer priority adjustment (internal to server), 4. MCPTT emergency group call request (from server to clients 2 and 3), 5. Notify group emergency status (from clients 2 and 3), 6. MCPTT emergency group call response (from clients 2 and 3 to server), 7. MCPTT emergency group call response (from server to client 1). + +**Figure 10.6.2.6.1.2-1: MCPTT group call upgraded to an MCPTT emergency group call** + +1. The MCPTT user at MCPTT client 1 initiates a group emergency. MCPTT client 1 sets its MCPTT emergency state. The MCPTT emergency state is retained until explicitly cancelled. +2. MCPTT client 1 requests the MCPTT server to upgrade the MCPTT group to an in-progress emergency state by sending an MCPTT emergency group call request. If configured to send an MCPTT alert when initiating an MCPTT emergency upgrade, the request also contains an indication that an MCPTT alert is to be initiated. The request may contain an indication of an implicit floor request. + +3. The MCPTT server adjusts the priority of the underlying bearer for all or selected participants in the MCPTT group call that receive the communication over unicast. + +NOTE 2: The determination of the selected participants whose bearers have to be upgraded is left to implementation. + +4. MCPTT server sends the MCPTT emergency group call request towards the MCPTT clients of each of those affiliated MCPTT group members. The request contains an indication of an MCPTT emergency alert if the request from the originator indicated MCPTT emergency alert. +5. MCPTT users are notified of the in-progress emergency state of the MCPTT group. +6. The receiving MCPTT clients send the MCPTT emergency group call response to the MCPTT server to acknowledge the MCPTT group emergency request. For a multicast call, these acknowledgements are not sent. +7. The MCPTT server sends the MCPTT emergency group call response to the MCPTT user 1 to confirm the upgrade request. + +NOTE 3: Step 7 can occur at any time following step 3, and prior to step 8 depending on the conditions to proceed with the call. + +MCPTT client 1, MCPTT client 2 and MCPTT client 3 continue with the MCPTT group call, which has been transformed into an MCPTT emergency group call. MCPTT client 1 can override other clients in the call except those that are also in the MCPTT emergency state. + +#### 10.6.2.6.1.3 MCPTT in-progress emergency group state cancel + +NOTE 1: In Rel-14 and Rel-13 versions of this specification the title of this subclause is "MCPTT emergency group call cancel". + +The procedure focuses on the case where an MCPTT client cancels an MCPTT group's in-progress emergency. + +Procedures in figure 10.6.2.6.1.3-1 are the signalling control plane procedures for the MCPTT client cancelling an in-progress emergency of a group. + +NOTE 2: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +NOTE 3: The end of the MCPTT emergency group call does not cancel the MCPTT group's in-progress emergency state. It is explicitly cancelled by an authorized user using this procedure. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group. +2. All members of the MCPTT group belong to the same MCPTT system. +3. MCPTT group members have been notified about the in-progress emergency. +4. The MCPTT group is in the in-progress emergency state and has prioritized bearer support. +5. MCPTT client 1 previously initiated the in-progress emergency for the group. + +![Sequence diagram for MCPTT in-progress emergency group state cancel. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The process involves: 1. Client 1 initiates cancel; 2. Client 1 sends request to server; 3. Server resolves group ID; 4. Server adjusts bearer priority; 5. Server sends request to clients 2 and 3; 6. Clients 2 and 3 notify emergency cancel; 7. Clients 2 and 3 send response to server; 8. Server sends response to client 1.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +Home MCPTT service provider + +``` + +sequenceDiagram + participant Client1 as MCPTT client 1 + participant Server as MCPTT server + participant GMS as Group management server + participant Client2 as MCPTT client 2 + participant Client3 as MCPTT client 3 + + Note left of Client1: 1. Initiate in-progress emergency group state cancel + Client1->>Server: 2. MCPTT in-progress emergency group state cancel request + Note right of Server: 3. Resolve group id + Note right of Server: 4. Bearer priority adjustment + Server->>Client2: 5. MCPTT in-progress emergency group state cancel request + Server->>Client3: 5. MCPTT in-progress emergency group state cancel request + Note right of Client2: 6. Notify emergency cancel + Note right of Client3: 6. Notify emergency cancel + Client2-->>Server: 7. MCPTT in-progress emergency group state cancel response + Client3-->>Server: 7. MCPTT in-progress emergency group state cancel response + Server-->>Client1: 8. MCPTT in-progress emergency group state cancel response + +``` + +Sequence diagram for MCPTT in-progress emergency group state cancel. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The process involves: 1. Client 1 initiates cancel; 2. Client 1 sends request to server; 3. Server resolves group ID; 4. Server adjusts bearer priority; 5. Server sends request to clients 2 and 3; 6. Clients 2 and 3 notify emergency cancel; 7. Clients 2 and 3 send response to server; 8. Server sends response to client 1. + +**Figure 10.6.2.6.1.3-1: MCPTT in-progress emergency group state cancel** + +1. The user at the MCPTT client 1 initiates an MCPTT in-progress emergency group state cancel. + +NOTE 3: An MCPTT user authorized to cancel in-progress emergencies on the MCPTT group can also be authorised to cancel the MCPTT emergency alert in addition to the initiator. However, only the initiator can cancel the initiator's local MCPTT emergency state. + +2. MCPTT client 1 sends an MCPTT in-progress emergency group state cancel request to the MCPTT server. + +NOTE 4: When MCPTT emergency alerts are in effect together with an MCPTT in-progress emergency group state on the same MCPTT group, the MCPTT emergency alert can, under some circumstances be cancelled at the same time. In that case, the MCPTT in-progress emergency group state cancel request carries an indication that the alert is also being cancelled. + +3. MCPTT server resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status, based upon the information from group management server. +4. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required. The MCPTT server cancels/resets the emergency in-progress state of the MCPTT group. +5. The MCPTT server sends an MCPTT in-progress emergency group state cancel request to the MCPTT group members. +6. MCPTT group members are notified of the MCPTT in-progress emergency group state cancel. +7. The receiving MCPTT clients send the MCPTT in-progress emergency group state cancel response to the MCPTT server to acknowledge the MCPTT in-progress emergency group state cancel. For a multicast call scenario, these acknowledgements are not sent. + +8. The MCPTT server sends the MCPTT in-progress emergency group state cancel response to the MCPTT user 1 to confirm the MCPTT in-progress emergency group state cancel. If the MCPTT in-progress emergency group state cancel request (in step 2) contained the "Alert indicator" IE, the MCPTT client 1 resets its local emergency status. + +NOTE 5: Step 8 can occur at any time following step 4, depending on the conditions to proceed with the call. + +#### 10.6.2.6.2 MCPTT imminent peril group call + +##### 10.6.2.6.2.1 MCPTT imminent peril group call commencement + +The procedure focuses on the case where an authorized MCPTT user is initiating an imminent peril group call for communicating with the affiliated MCPTT members of that MCPTT group. This procedure will gain elevated access privilege for the MCPTT client if it is not already in that state. The access privilege for other applications will not necessarily be affected. + +Procedures in figure 10.6.2.6.2.1-1 are the signalling control plane procedures for the MCPTT client initiating establishment of an imminent peril group call with an MCPTT group i.e., MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 belong to the same MCPTT group which is defined on MCPTT group management server. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group. +2. All members of the MCPTT group belong to the same MCPTT system. +3. The initiating MCPTT client 1 has been provisioned with an MCPTT group that has been designated in the provisioning to be used for imminent peril communications. + +NOTE 1: Alternatively, the client could have been provisioned for imminent peril behaviour on the selected group. + +4. Optionally, MCPTT client 1 may use an activated functional alias for the group communication. +5. The MCPTT server may have subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for MCPTT imminent peril group call showing interactions between MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, and MCPTT client 3.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +Home MCPTT service provider + +``` + +sequenceDiagram + participant C1 as MCPTT client 1 + participant S as MCPTT server + participant GMS as Group management server + participant C2 as MCPTT client 2 + participant C3 as MCPTT client 3 + + Note over C1: 1. initiate imminent peril group call + C1->>S: 2. Imminent peril group call request + rect rgb(255, 255, 255) + Note over S, GMS: 3. Affiliate user to group + end + rect rgb(255, 255, 255) + S->>GMS: 4. Resolve group id + end + rect rgb(255, 255, 255) + Note over S: 5. Bearer priority configuration + end + S->>C2: 6. Imminent peril group call request + S->>C3: 6. Imminent peril group call request + Note over C2: 7. Notify immediate peril call + Note over C3: 7. Notify immediate peril call + S-->>C1: 9. Imminent peril group call response + Note over S, C2: 8. Imminent peril group call response + +``` + +Sequence diagram for MCPTT imminent peril group call showing interactions between MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, and MCPTT client 3. + +**Figure 10.6.2.6.2.1-1: MCPTT imminent peril group call** + +1. The user at the MCPTT client 1 initiates an imminent peril group call. The MCPTT user at MCPTT client 1 may select a functional alias used for the call. +2. MCPTT client 1 sends an MCPTT imminent peril group call request towards the MCPTT server. The request contains an indication of the in-progress imminent peril. The MCPTT server records the identity of the MCPTT user that initiated the imminent peril group call until the in-progress imminent peril state is cancelled. Once an imminent peril group call has been initiated, the MCPTT group is considered to be in an in-progress imminent peril state until cancelled. The request may contain an indication of an implicit floor request. If the group call request includes an implicit floor request it may also include location information. +3. The MCPTT server implicitly affiliates MCPTT client 1 to the imminent peril group if the client is not already affiliated. +4. MCPTT server checks whether the MCPTT user of MCPTT client 1 is authorized for initiation of imminent peril group calls on the indicated MCPTT group, and if authorized, it resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status, based on the information from group management server. The MCPTT server checks whether the provided functional alias, if present, can be used and has been activated for the user. +5. The MCPTT server configures the priority of the underlying bearers for all participants in the MCPTT group. + +NOTE 2: Successive calls during the in-progress imminent peril state will all receive the adjusted bearer priority. + +6. MCPTT server sends the imminent peril group call request towards the MCPTT clients of each of those affiliated MCPTT group members. The request contains an indication of the in-progress imminent peril. If location information was included in the imminent peril group call request, the MCPTT server checks the privacy policy + +of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to other users on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking"). + +7. MCPTT users are notified of the incoming imminent peril call. The functional alias of the group call initiating MCPTT user may be displayed. +8. The receiving MCPTT clients send the MCPTT imminent peril group call response to the MCPTT server to acknowledge the imminent peril call request. For a multicast call, these acknowledgements are not set. +9. The MCPTT server sends the MCPTT imminent peril group call response to the MCPTT user 1 to inform the successful imminent peril call establishment. + +NOTE 3: Step 9 can occur at any time following step 5, and prior to step 10 depending on the conditions to proceed with the imminent peril call. + +MCPTT client 1, MCPTT client 2 and MCPTT client 3 have successfully established media plane for communication. MCPTT floor participant 1, floor participant 2 and floor participant 3 exchange floor control information e.g., MCPTT client 1 receives the floor granted information over the established media plane, while the other MCPTT clients receive floor taken information. MCPTT client 1 indicates to the MCPTT user that the floor is available to send media, while the other MCPTT clients in the imminent peril call will be receiving that media. + +#### 10.6.2.6.2.2 Imminent peril group call upgrade + +The procedure focuses on the case where an authorized MCPTT user is upgrading an MCPTT group call to an imminent peril group call while the MCPTT group call is already in progress. + +Procedures in figure 10.6.2.6.2.2-1 are the signalling control plane procedures for the MCPTT client upgrading an MCPTT group call on an MCPTT group to an imminent peril group call. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 1, MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group. +2. All members of the MCPTT group belong to the same MCPTT system. +3. An MCPTT group call is already in progress. + +![Sequence diagram showing the upgrade of an MCPTT group call to an imminent peril group call. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The process involves a request from client 1, a bearer priority adjustment by the server, notification to other clients, and responses back to client 1.](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +MCPTT service provider + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note over MCPTT client 1: 1. User initiates imminent peril call + MCPTT client 1->>MCPTT server: 2. MCPTT imminent peril group call request + Note over MCPTT server: 3. Bearer priority adjustment + MCPTT server->>MCPTT client 2: 4. MCPTT imminent peril group call request + MCPTT server->>MCPTT client 3: 4. MCPTT imminent peril group call request + Note over MCPTT client 2: 5. Notify imminent peril status + Note over MCPTT client 3: 5. Notify imminent peril status + MCPTT client 2-->>MCPTT server: 6. MCPTT imminent peril group call response + MCPTT client 3-->>MCPTT server: 6. MCPTT imminent peril group call response + MCPTT server->>MCPTT client 1: 7. MCPTT imminent peril group call response + +``` + +Sequence diagram showing the upgrade of an MCPTT group call to an imminent peril group call. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The process involves a request from client 1, a bearer priority adjustment by the server, notification to other clients, and responses back to client 1. + +**Figure 10.6.2.6.2.2-1: MCPTT group call upgrade to an imminent peril group call** + +1. The MCPTT user at MCPTT client 1 initiates an imminent peril call. +2. MCPTT client 1 requests the MCPTT server to upgrade the MCPTT group to an in-progress imminent peril state by sending an MCPTT imminent peril group call request. The request may contain an indication of an implicit floor request. If the imminent peril group call request includes an implicit floor request it may also include location information. +3. The MCPTT server adjusts the priority of the underlying bearer for all participants in the MCPTT group. +4. The MCPTT server sends the MCPTT imminent peril group call request towards the MCPTT clients of the affiliated MCPTT group members. If location information was included in the imminent peril group call request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to other users on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking"). +5. MCPTT users are notified of the in-progress imminent peril state of the MCPTT group. +6. The receiving MCPTT clients send the MCPTT imminent peril group call response to the MCPTT server to acknowledge the MCPTT imminent peril group call request. For a multicast call, these acknowledgements are not set. +7. The MCPTT server sends the MCPTT imminent peril group call response to the MCPTT user 1 to confirm the upgrade request. + +NOTE: Step 7 can occur at any time following step 4, and prior to step 8 depending on the conditions to proceed with the call. + +MCPTT client 1, MCPTT client 2 and MCPTT client 3 continue with the MCPTT group call, which has been transformed into an imminent peril group call. + +### 10.6.2.6.2.3 MCPTT in-progress imminent peril group state cancel + +NOTE 1: In Rel-14 and Rel-13 versions of this specification the title of this subclause is "MCPTT imminent peril group call cancel". + +The procedure focuses on the case where an authorized MCPTT user cancels an MCPTT group's in-progress imminent peril state. + +Procedures in figure 10.6.2.6.2.3-1 are the signalling control plane procedures for the MCPTT client cancelling an MCPTT group's in-progress imminent peril state. + +NOTE 2: The end of the imminent peril call does not cancel the MCPTT group's in-progress imminent peril state. It is explicitly cancelled by an authorized user using this procedure. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 1, MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group. +2. All members of the MCPTT group belong to the same MCPTT system. +3. The MCPTT group is in an in-progress imminent peril state and has prioritized bearer support. +4. MCPTT group members have been notified about the MCPTT group's in-progress imminent peril state. +5. MCPTT client 1 previously initiated the in-progress imminent peril. + +![Sequence diagram for MCPTT in-progress imminent peril group state cancel. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The sequence shows the cancellation process initiated by client 1, involving bearer priority adjustment and group ID resolution by the server, followed by a cancel request to clients 2 and 3, and subsequent responses.](7c57192c514175021e4560a1a46126c1_img.jpg) + +MCPTT service provider + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note left of MCPTT client 1: 1. initiate in-progress imminent peril group state cancel + MCPTT client 1->>MCPTT server: 2. MCPTT in-progress imminent peril group state cancel request + Note right of MCPTT server: 3. Bearer priority adjustment + Note right of MCPTT server: 4. Resolve group id + MCPTT server->>MCPTT client 2: 5. MCPTT in-progress imminent peril group state cancel request + MCPTT server->>MCPTT client 3: 5. MCPTT in-progress imminent peril group state cancel request + Note right of MCPTT client 2: 6. Notify Imminent peril cancel + Note right of MCPTT client 3: 6. Notify Imminent peril cancel + MCPTT client 2-->>MCPTT server: 7. MCPTT in-progress imminent peril group state cancel response + MCPTT client 3-->>MCPTT server: 7. MCPTT in-progress imminent peril group state cancel response + MCPTT server-->>MCPTT client 1: 8. MCPTT in-progress imminent peril group state cancel response + +``` + +Sequence diagram for MCPTT in-progress imminent peril group state cancel. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The sequence shows the cancellation process initiated by client 1, involving bearer priority adjustment and group ID resolution by the server, followed by a cancel request to clients 2 and 3, and subsequent responses. + +**Figure 10.6.2.6.2.3-1: MCPTT in-progress imminent peril group state cancel** + +1. The user at the MCPTT client 1 initiates an in-progress imminent peril group state cancel. + +2. MCPTT client 1 sends an MCPTT in-progress imminent peril group state cancel request to the MCPTT server. +3. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required. The MCPTT server cancels/resets the in-progress imminent peril group state. +4. MCPTT server resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status, based upon the information from group management server. +5. The MCPTT server sends an MCPTT imminent peril group state cancel request to the MCPTT group members. +6. MCPTT group members are notified of the in-progress imminent peril group state cancel. +7. The receiving MCPTT group members send the MCPTT in-progress imminent peril group state cancel response to the MCPTT server to acknowledge the MCPTT in-progress imminent peril group state cancel request. For a multicast scenario, these acknowledgements are not set. +8. The MCPTT server sends the MCPTT in-progress imminent peril group state cancel response to the MCPTT user 1 to confirm the MCPTT in-progress imminent peril group state cancel request. + +NOTE 3: Step 8 can occur at any time following step 4, depending on the conditions to proceed with the call. + +### 10.6.2.6.3 MCPTT emergency alert + +**Editor's note: whether the following procedures for emergency alert initiation and emergency alert cancel remain in this specification is FFS.** + +#### 10.6.2.6.3.1 MCPTT emergency alert initiation + +The procedure focuses on the case where an MCPTT client is initiating an MCPTT emergency alert unicast signalling for communicating the alert with the affiliated MCPTT members of that MCPTT group. An MCPTT client in the MCPTT emergency state gains elevated access privilege for all of the MCPTT user's mission critical applications. This procedure will place the MCPTT client in the MCPTT emergency state if the MCPTT client is not already in that state. + +Procedures in figure 10.6.2.6.3.1-1 are the signalling control plane procedures for the MCPTT client initiating an MCPTT emergency alert with an MCPTT group i.e., MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 belong to the same MCPTT group which is defined on MCPTT group management server. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +Pre-conditions: + +1. The MCPTT group to be used for emergency communications by MCPTT client 1 is previously defined on the group management server and MCPTT client 2 and MCPTT client 3 are affiliated to that MCPTT group. + +NOTE 2: Alternatively, MCPTT client 1 could have been provisioned for emergency behaviour on the currently selected group. + +2. All members of the MCPTT group belong to the same MCPTT system. +3. The initiating MCPTT client 1 is affiliated with one or more MCPTT groups. +4. The initiating MCPTT client 1 may not have carried out an explicit affiliation procedure with the MCPTT group designated as the MCPTT emergency group. +5. Optionally, MCPTT client 1 may use an activated functional alias for the group communication. +6. The MCPTT server may have subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for MCPTT emergency alert. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The sequence starts with MCPTT client 1 initiating an emergency alert, followed by a request to the server, authorization checks, group ID resolution, and subsequent notifications to other clients.](1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note left of MCPTT client 1: 1. initiate emergency alert + MCPTT client 1->>MCPTT server: 2. MC service emergency alert request + Note right of MCPTT server: 3. Check alert authorization + Note right of MCPTT server: 4. Resolve group ID + MCPTT server-->>MCPTT client 1: 5. MC service emergency alert response + MCPTT server->>MCPTT client 2: 6. MC service emergency alert request + MCPTT server->>MCPTT client 3: 6. MC service emergency alert request + Note right of MCPTT client 2: 7. Notify emergency alert + Note right of MCPTT client 3: 7. Notify emergency alert + MCPTT client 2-->>MCPTT server: 8. MC service emergency alert response + MCPTT client 3-->>MCPTT server: 8. MC service emergency alert response + Note right of MCPTT server: 9. Affiliate to group + +``` + +Sequence diagram for MCPTT emergency alert. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The sequence starts with MCPTT client 1 initiating an emergency alert, followed by a request to the server, authorization checks, group ID resolution, and subsequent notifications to other clients. + +**Figure 10.6.2.6.3.1-1 MCPTT emergency alert** + +1. The MCPTT user at the MCPTT client 1 initiates an MCPTT emergency alert. MCPTT client 1 sets its MCPTT emergency state. The MCPTT user at MCPTT client 1 may select a functional alias used for the call. The MCPTT emergency state is retained by the MCPTT client 1 until explicitly cancelled. +2. MCPTT client 1 requests the MCPTT server to send an MCPTT emergency alert request to the MCPTT group designated as the MCPTT emergency group. +3. MCPTT server checks whether the MCPTT user of MCPTT client 1 is authorized for initiation of MCPTT emergency alerts for the indicated MCPTT group. The MCPTT server checks whether the provided functional alias, if present, can be used and has been activated for the user. +4. MCPTT server resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status, based on the information from group management server. +5. The MCPTT server sends the MCPTT emergency alert response to the MCPTT user 1 to confirm the MCPTT emergency alert request. MCPTT group calls made by the MCPTT client 1 will be sent as emergency calls until the emergency state on the MCPTT client 1 is cancelled. +6. The MCPTT server sends an MCPTT emergency alert request towards the MCPTT clients of each of those affiliated MCPTT group members. The MCPTT emergency alert request message shall contain the following information: Location, MCPTT ID and MCPTT group ID (i.e., MCPTT user's selected MCPTT group or dedicated MCPTT emergency group, as per user profile configuration) and the MCPTT user's mission critical organization name. If in step 2, the MCPTT client 1 does not include the location information in the MCPTT emergency alert request to the MCPTT server, the MCPTT server acquires the location information of the MCPTT user at the MCPTT client 1 from the location management server. If the location information is included in step 2, then the MCPTT server uses the location information from MCPTT client 1. +7. MCPTT users are notified of the MCPTT emergency alert. The functional alias of the group call initiating MCPTT user may be displayed. +8. For a unicast MCPTT emergency alert, the receiving MCPTT clients send the MCPTT emergency alert response to the MCPTT server to acknowledge the MCPTT emergency alert. For a multicast MCPTT emergency alert, these acknowledgements are not sent unless the MCPTT clients have been configured to do so. + +9. The MCPTT server implicitly affiliates MCPTT client 1 to the emergency group if the client is not already affiliated. + +NOTE 3: Sending the emergency alert without making a request to also start an emergency call does not put the group into the in-progress emergency state. + +NOTE 4: Sending the emergency alert does not put the other UEs in the group into an emergency state. + +NOTE 5: The MCPTT client 1 need not initiate a group call. For example, the MCPTT client can be configured to only allow alerts or the MCPTT user can choose not to make an MCPTT emergency group call. + +NOTE 6: It is configured whether MCPTT client 1 automatically triggers a subsequent MCPTT emergency group call. + +#### 10.6.2.6.3.2 MCPTT emergency alert cancel + +The procedure focuses on the case where an MCPTT client has initiated an MCPTT emergency alert and entered the emergency state, and wishes to cancel the alert, informing the MCPTT server and other group members of this cancellation. By doing so, the MCPTT client may also request the cancellation of the in-progress emergency state of the group. + +Procedures in figure 10.6.2.6.3.2-1 are the signalling control plane procedures for the MCPTT client cancelling an MCPTT emergency alert with an MCPTT group i.e., MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 belong to the same MCPTT group which is defined on MCPTT group management server. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +Pre-conditions: + +1. The MCPTT client 1 had previously successfully initiated an MCPTT emergency alert. +2. The MCPTT client 1 is still in the emergency state. +3. The initiating MCPTT client 1 has affiliated with the MCPTT group designated as the MCPTT emergency group. + +![Sequence diagram for MCPTT emergency alert cancel. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The process involves client 1 sending a cancel request to the server, the server resolving the group ID, responding to client 1, then sending requests to other clients (2 and 3), who notify their users and respond back to the server.](18003425d0e8638dde4acc9c5c468c5c_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note left of MCPTT client 1: 1. initiate emergency alert cancel + MCPTT client 1->>MCPTT server: 2. MCPTT emergency alert cancel request + MCPTT server->>Group management server: 3. Resolve group ID + MCPTT server-->>MCPTT client 1: 4. MCPTT emergency alert cancel response + MCPTT server->>MCPTT client 2: 5. MCPTT emergency alert cancel request + MCPTT server->>MCPTT client 3: 5. MCPTT emergency alert cancel request + MCPTT client 2->>MCPTT client 2: 6. Notify emergency alert cancel + MCPTT client 3->>MCPTT client 3: 6. Notify emergency alert cancel + MCPTT client 2-->>MCPTT server: 7. MCPTT emergency alert cancel response + MCPTT client 3-->>MCPTT server: 7. MCPTT emergency alert cancel response + +``` + +Sequence diagram for MCPTT emergency alert cancel. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The process involves client 1 sending a cancel request to the server, the server resolving the group ID, responding to client 1, then sending requests to other clients (2 and 3), who notify their users and respond back to the server. + +**Figure 10.6.2.6.3.2-1 MCPTT emergency alert cancel** + +1. The user at the MCPTT client 1 initiates an MCPTT emergency alert cancel. + +NOTE 2: The MCPTT emergency alert cancel request carries an indication to also request that the in-progress emergency is to be cancelled. The MCPTT server can accept or deny the request to cancel the in-progress emergency state of the group as a whole, separately from accepting or denying the request to cancel the emergency alert at MCPTT client 1. Additionally, an authorized user can cancel either or both the in-progress emergency state of the group and the initiator's local MCPTT emergency state. + +2. MCPTT client 1 requests the MCPTT server to send an MCPTT emergency alert cancel to the MCPTT group to which MCPTT client 1 had previously sent the emergency alert. +3. MCPTT server resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status, based on the information from group management server. +4. The MCPTT server sends the MCPTT emergency alert cancel response to the MCPTT client 1 to confirm the MCPTT emergency alert cancel request. MCPTT client 1 resets its emergency state. +5. The MCPTT server sends an MCPTT emergency alert cancel request towards the MCPTT clients of each of those affiliated MCPTT group members. +6. MCPTT users are notified of the MCPTT emergency alert cancellation of MCPTT client 1. +7. For a unicast MCPTT emergency alert cancel, the receiving MCPTT clients send the MCPTT emergency alert cancel response to the MCPTT server to acknowledge the MCPTT emergency alert cancel. For a multicast MCPTT emergency alert cancel, these acknowledgements are not sent unless the MCPTT clients have been configured to do so. + +### 10.6.2.6.3.3 Entering MCPTT emergency alert area + +**Editor's Note:** MCPTT emergency alert triggered by MCPTT client locally which stores the predefined area is another possible solution. How to define this procedure and how to combine the two solutions is FFS. + +The procedure focuses on the case where an MCPTT service emergency alert to be triggered when an MCPTT UE moves into a predefined area. This procedure will place the MCPTT client in the MCPTT emergency state if the MCPTT client is not already in that state. + +Procedures in figure 10.6.2.6.3.3-1 are the signalling control plane procedures for the MCPTT server triggering an MCPTT emergency alert with an MCPTT group i.e., MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 belong to the same MCPTT group which is defined on MCPTT group management server. + +NOTE: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group. +2. All members of the MCPTT group belong to the same MCPTT system. +3. An area in which the MCPTT client should send emergency alert is pre-defined in MCPTT server. + +![Sequence diagram illustrating the procedure for entering an MCPTT emergency alert area. The diagram shows interactions between MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, and MCPTT client 3. The steps are: 1. MCPTT server acquires location info from client 1; 2. MCPTT server checks if client 1 is in a predefined area; 3. MCPTT server sends an emergency alert area notification to client 1; 4. MCPTT client 1 notifies the user; 5. MCPTT client 1 initiates the emergency alert procedure.](02dfdcd208dbdc8fa4f645885e59dd17_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note right of MCPTT server: 1. Acquire latest location information of user at MCPTT client 1 + Note right of MCPTT server: 2. Check whether MCPTT client 1 has moved into a predefined area + MCPTT server->>MCPTT client 1: 3. MCPTT emergency alert area notification + Note left of MCPTT client 1: 4. Notify user + Note over MCPTT client 1, MCPTT client 3: 5. MCPTT emergency alert initiation procedure +``` + +Sequence diagram illustrating the procedure for entering an MCPTT emergency alert area. The diagram shows interactions between MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, and MCPTT client 3. The steps are: 1. MCPTT server acquires location info from client 1; 2. MCPTT server checks if client 1 is in a predefined area; 3. MCPTT server sends an emergency alert area notification to client 1; 4. MCPTT client 1 notifies the user; 5. MCPTT client 1 initiates the emergency alert procedure. + +Figure 10.6.2.6.3.3-1 Entering MCPTT emergency alert area + +1. The MCPTT server acquires the latest location information of the user at MCPTT client 1 from the location management server as described in subclause 10.9.3.6 in 3GPP TS 23.280[16]. +2. The MCPTT server checks whether MCPTT client 1 has moved into a predefined area. +3. If so, the MCPTT server sends an MCPTT emergency alert area notification, setting the Emergency Alert Area Indicator IE to in an Emergency Alert Area, to the MCPTT client 1 to notify that it has moved in to the area of potential danger. +4. The MCPTT client 1 notifies the MCPTT user that he/she has entered the emergency alert area. +5. The MCPTT client 1 initiates the MCPTT emergency alert procedure as described in 10.6.2.6.3.1. + +#### 10.6.2.6.3.4 Leaving MCPTT emergency alert area + +This procedure focuses on the case where a notification is sent when an MCPTT UE moves out of a pre-defined area. This procedure will notify the MCPTT client that it is now out of the pre-defined emergency alert area. It is up to the MCPTT user at that MCPTT client to determine if the emergency state is to be cleared or not. + +Procedures in figure 10.6.2.6.3.4-1 are the signalling control plane procedures for the MCPTT server sends an MCPTT emergency alert area notification. It is optional if the MCPTT user wants to initiate the MCPTT emergency alert cancel procedure to inform the members in the MCPTT group that **its emergency condition is over**. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group. This MCPTT group has been pre-defined for communicating the emergency alert in the user profile. +2. All members of the MCPTT group belong to the same MCPTT system. +3. An area in which the **emergency alert for** the MCPTT client should remain active is pre-defined in MCPTT server. + +![Sequence diagram illustrating the procedure for leaving an MCPTT emergency alert area. The diagram shows interactions between MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, and MCPTT client 3. The steps are: 1. MCPTT server acquires location info from Group management server; 2. MCPTT server checks if client 1 moved out of predefined area; 3. MCPTT server sends notification to client 1; 4. client 1 notifies user; 5. optional cancel procedure.](896f6ec457b6252d4af32a634299218c_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note right of MCPTT server: 1. Acquire latest location information of user at MCPTT client 1 + MCPTT server->>Group management server: Request location info + Note right of MCPTT server: 2. Check whether MCPTT client 1 has moved out a predefined area + MCPTT server->>MCPTT client 1: 3. MCPTT emergency alert area notification + Note left of MCPTT client 1: 4. Notify user + Note right of MCPTT client 1: 5. MCPTT emergency alert cancel procedure + +``` + +Sequence diagram illustrating the procedure for leaving an MCPTT emergency alert area. The diagram shows interactions between MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, and MCPTT client 3. The steps are: 1. MCPTT server acquires location info from Group management server; 2. MCPTT server checks if client 1 moved out of predefined area; 3. MCPTT server sends notification to client 1; 4. client 1 notifies user; 5. optional cancel procedure. + +**Figure 10.6.2.6.3.4-1 Leaving MCPTT emergency alert area** + +1. The MCPTT server acquires the latest location information of the user at MCPTT client 1 from the location management server as described in subclause 10.9.3.6 in 3GPP TS 23.280[16]. +2. The MCPTT server checks whether MCPTT client 1 has moved out of a predefined area. +3. If so, the MCPTT server sends an MCPTT emergency alert area notification, setting the Emergency Alert Area Indicator IE to out of an Emergency Alert Area, to MCPTT client 1 to notify that it has moved out of the area of potential danger. +4. MCPTT client 1 notifies the MCPTT user that he/she has left the emergency alert area. It is up to the MCPTT user of MCPTT client 1 to determine whether to clear his/her emergency state. +5. Optionally, the MCPTT user of MCPTT client 1 initiates the MCPTT emergency alert cancel procedure as described in 10.6.2.6.3.2. + +NOTE 2: It is up to the MCPTT user to clear the local emergency state on the client after the MCPTT UE has moved out of the emergency alert area. The MCPTT server cannot clear the client's local emergency state. + +### 10.6.2.7 Location of current talker + +Figure 10.6.2.7-1 shows the high level procedure to for MCPTT service to provide the location information about the current talking user to all the receiving MCPTT users. + +Precondition: + +1. There is on-going group call involving MCPTT client 1 and MCPTT client 2. +2. MCPTT client 1 is the current talking user. +3. MCPTT server has obtained the location information of MCPTT client 1 according to subclause 10.9 in 3GPP TS 23.280 [16]. + +![Sequence diagram showing the procedure for providing location information of the current talker. The diagram involves three lifelines: MCPTT server, MCPTT client 2, and MCPTT client 1. The sequence of messages is: 1. MCPTT client 1 acquires the floor for transmission; 2. MCPTT server checks users' privacy policy for sharing location information; 3. MCPTT server provides the location information of the current talker.](0f5c79ad7c317f14f16aa5a2c036e406_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note right of MCPTT client 1: 1.MCPTT client 1 acquires the floor for transmission + Note left of MCPTT server: 2.Check users' privacy policy for sharing location information + Note right of MCPTT server: 3.Provides the location information of the current talker +``` + +Sequence diagram showing the procedure for providing location information of the current talker. The diagram involves three lifelines: MCPTT server, MCPTT client 2, and MCPTT client 1. The sequence of messages is: 1. MCPTT client 1 acquires the floor for transmission; 2. MCPTT server checks users' privacy policy for sharing location information; 3. MCPTT server provides the location information of the current talker. + +**Figure 10.6.2.7-1: Providing location information of the current talker** + +1. MCPTT client 1 gets the floor to transmit voice media. +2. MCPTT server checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in Annex A.3) of the current talking MCPTT user to decide if the location information of MCPTT client 1 can be provided to other MCPTT users on the call. MCPTT server acquires the location of the current talker from the location management server as described in subclause 10.9.3.6 in 3GPP TS 23.280[16]. Optionally, the MCPTT server acquires the location of the current talker directly from the floor request received from MCPTT client 1 in step 1. +3. MCPTT server provides the location information of MCPTT client 1 to MCPTT client 2. Optionally, the location information may be provided in the floor taken message sent to MCPTT client 2 according to subclause 10.9.1.3.1. + +### 10.6.2.8 Void + +#### 10.6.2.8.1 Void + +#### 10.6.2.8.2 Void + +#### 10.6.2.8.3 Void + +### 10.6.2.9 Group regroup with preconfigured group + +#### 10.6.2.9.1 General + +A group regroup may be achieved by regrouping MCPTT groups into a new MCPTT regroup group which uses the configuration of a separate preconfigured MCPTT group. The MCPTT regroup group configuration needs to be provided to the relevant MCPTT group members of the MCPTT groups that will be regrouped in advance of the regrouping operation. + +NOTE 1: A preconfigured group which is intended only to provide configuration for the preconfigured regroup process is identified by a parameter in the group configuration described in 3GPP TS 23.280 [16]. + +NOTE 2: The configuration may alternatively be taken from any MCPTT group that has been configured in the user profile of all the relevant MCPTT users who will be regrouped. + +NOTE 3: Regroup groups may be defined according to the organizational structure of a mission critical organization, or by some other means which allows the MCPTT client of an authorized user to be aware of an appropriate regroup group for sets of MCPTT groups that will be regrouped together. + +The preconfigured MCPTT group that provides the configuration is not used as the MCPTT regroup group itself, it only provides configuration for one or more MCPTT regroup groups. The MCPTT group ID of the regroup group is provided by the authorized user when the preconfigured regrouping is carried out. + +The MCPTT regroup group can be specified to be a broadcast or non-broadcast type according to the configuration of the MCPTT group whose configuration is specified by the regroup request. The broadcast type of regroup is used for one-way communication where only an authorized MCX user is allowed to transmit and all other regroup members are only allowed to receive the communication (e.g. a call from a dispatcher to all regroup members). The non-broadcast type is used for two-way communication where all regroup members can transmit and receive (i.e. the regroup group call behaves like a normal non-broadcast group call). + +These procedures provide a regrouping service for MCPTT only and are independent of group regrouping procedures specified in 3GPP TS 23.280 [16]. If the MCPTT server has been notified by the group management server that one of the MCPTT groups that has been requested for regrouping by means of this procedure has already been regrouped by the group regrouping procedure specified in 3GPP TS 23.280 [16], the MCPTT server shall reject the request for regrouping described in the following procedure. + +**Editor's note: These procedures provide a regrouping service for MCPTT only; any issues arising from conflicts with similar regrouping operations for MCVideo and MCData are FFS.** + +#### 10.6.2.9.2 Regroup procedures in single MCPTT system + +##### 10.6.2.9.2.1 Regroup formation using preconfigured group in single MCPTT system + +Figure 10.6.2.9.2.1-1 illustrates the procedure to initiate a group regroup procedure using a preconfigured MCPTT group. The procedure takes place prior to the establishment of a group call to the regroup group. + +Pre-conditions: + +- MCPTT client 2 is an affiliated member of MCPTT group 1 and MCPTT client 3 is an affiliated member of MCPTT group 2. +- The MCPTT group identity and group configuration for the regroup MCPTT group have been preconfigured in MCPTT clients 2 and 3, and MCPTT clients 2 and 3 have received the relevant security related information to allow them to communicate in the regroup MCPTT group. +- MCPTT client 1 is authorized to initiate a preconfigured regroup procedure. + +- MCPTT client 1 is aware of a suitable preconfigured regroup group whose configuration has been preconfigured in the MCPTT UEs of the group members who will be regrouped. +- In order to be aware whether the group is regrouped, the MCPTT server is subscribed to the group configuration in GMS. +- The GMS has subscribed group dynamic data as specified in subclause 10.1.5.5.1 from the MCPTT server using the procedures defined in subclause 10.1.5.6 in TS 23.280 [16]. + +![Sequence diagram illustrating the regroup procedure using a preconfigured group in a single MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3 under the 'Home MCPTT service provider'.](c063ca3181a644e8ae4aebfd4cb1a2c3_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + Note over MCPTT client 1, MCPTT client 3: Home MCPTT service provider + + MCPTT client 1->>MCPTT server: 1. Initiate preconfigured regroup + MCPTT client 1->>MCPTT server: 2. Preconfigured regroup request + MCPTT server->>MCPTT server: 3. Check authorization and resolve group IDs + MCPTT server-->>MCPTT client 1: 4. Preconfigured regroup reject + MCPTT server->>MCPTT client 2: 5a. Preconfigured regroup request + MCPTT server->>MCPTT client 3: 5b. Preconfigured regroup request + MCPTT client 2->>MCPTT client 2: 6a. Notify user + MCPTT client 3->>MCPTT client 3: 6b. Notify user + MCPTT server-->>MCPTT client 2: 7a. Preconfigured regroup response + MCPTT server-->>MCPTT client 3: 7b. Preconfigured regroup response + MCPTT server->>MCPTT server: 8. Affiliate MCPTT clients to regroup group + MCPTT server-->>MCPTT client 1: 9. Preconfigured regroup response + +``` + +Sequence diagram illustrating the regroup procedure using a preconfigured group in a single MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3 under the 'Home MCPTT service provider'. + +**Figure 10.6.2.9.2.1-1: Regroup procedure using preconfigured group in single MCPTT system** + +1. The authorized user of MCPTT client 1 initiates the regroup procedure, specifying the list of MCPTT groups to be regrouped (MCPTT groups 1 and 2), the MCPTT group ID of the regroup group and the MCPTT group ID of the group from which configuration information for the regroup group is to be taken. +2. MCPTT client 1 sends the preconfigured regroup request to the MCPTT server. +3. The MCPTT server checks that MCPTT client 1 is authorized to initiate a preconfigured regroup procedure, and resolves the group identities of the MCPTT groups requested in step 1. The MCPTT server also checks which group members are affiliated to MCPTT groups 1 and 2. The MCPTT server may retrieve the configuration for the regroup group from the GMS if that configuration information is not already known to the MCPTT server. The MCPTT server also checks that none of the MCPTT groups that are requested for regrouping are already regrouped by any mechanism. + +NOTE 1: This procedure does not require that the authorized user of MCPTT client 1 is a group member of MCPTT groups 1 or 2, or that the authorized user of MCPTT client 1 is an affiliated group member of MCPTT groups 1 or 2. + +NOTE 2: The list of groups included in the regroup is held in dynamic data in the MCPTT server, and is not used to update group configuration information in the group management server. + +4. If the MCPTT server determines that any of the groups requested for regrouping, including the regroup group, have been regrouped by other group regrouping procedures, the MCPTT server then sends a preconfigured regroup reject back to MCPTT client 1 with a reject reason indicating that one of the groups has already been regrouped, and this procedure terminates. +5. If the preconfigured regroup request is not rejected, the MCPTT server sends the preconfigured regroup requests to MCPTT clients 2 and 3 in steps 5a and 5b respectively. + +NOTE 3: Only group members that are affiliated to the MCPTT groups that are to be regrouped are sent a preconfigured regroup request. + +6. MCPTT clients 2 and 3 notify their users of the regrouping in steps 6a and 6b respectively. +7. MCPTT clients 2 and 3 may send the preconfigured regroup response to the MCPTT server to acknowledge the regrouping action. These acknowledgements are not sent in response to a multicast transmission of the preconfigured regroup request. +8. The MCPTT server affiliates the regrouped MCPTT clients to the regroup group. +9. The MCPTT server sends a preconfigured regroup response to MCPTT client 1. + +After the group regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in 10.6.2.9.2.2. + +MCPTT client participation in the ongoing regroup persists until the MCPTT client is no longer affiliated to any of the regrouped groups (group 1 or 2 in this procedure). + +MCPTT client affiliation to the regroup group may cease when the UE's MCPTT service ceases, e.g. when the UE is powered down, or by performing a log-off operation. + +**Editor's note: Data persistence in the MCPTT client following a user log-off or power down needs further study.** + +#### 10.6.2.9.2.2 Regroup cancellation in single MCPTT system + +Figure 10.6.2.9.2.2-1 illustrates the procedure to cancel a regrouping that uses a preconfigured MCPTT group. + +Pre-conditions: + +- MCPTT clients 2 and 3 have been regrouped into an MCPTT regroup group. +- MCPTT client 1 is authorized to cancel a regrouping that uses a preconfigured MCPTT group. +- The GMS has subscribed to group dynamic data as specified in subclause 10.1.5.5.1 from the MCPTT server using the procedures defined in subclause 10.1.5.6 in TS 23.280 [16]. + +![Sequence diagram illustrating the 'Cancel preconfigured regroup procedure in single MCPTT system'. The diagram shows interactions between MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3 within a 'Home MCPTT service provider'.](fc3e2b49a9f850951570e502393b697f_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + Note left of MCPTT client 1: 1. Cancel preconfigured group regrouping + MCPTT client 1->>MCPTT server: 2. Preconfigured regroup cancel request + Note right of MCPTT server: 3. Check authorization + MCPTT server->>MCPTT client 2: 4a. Preconfigured regroup cancel request + MCPTT server->>MCPTT client 3: 4b. Preconfigured regroup cancel request + Note right of MCPTT client 2: 5a. Notify user + Note right of MCPTT client 3: 5b. Notify user + MCPTT client 2-->>MCPTT server: 6a. Preconfigured regroup cancel response + MCPTT client 3-->>MCPTT server: 6b. Preconfigured regroup cancel response + Note right of MCPTT server: 7. Deaffiliate MCPTT clients + MCPTT server->>MCPTT client 1: 8. Preconfigured regroup cancel response + +``` + +Sequence diagram illustrating the 'Cancel preconfigured regroup procedure in single MCPTT system'. The diagram shows interactions between MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3 within a 'Home MCPTT service provider'. + +**Figure 10.6.2.9.2.2-1: Cancel preconfigured regroup procedure in single MCPTT system** + +1. The authorized user of MCPTT client 1 initiates the cancellation of the regrouping that uses a preconfigured MCPTT group. +2. MCPTT client 1 sends the preconfigured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the regroup group. +3. The MCPTT server checks that MCPTT client 1 is authorized to cancel a regrouping that uses a preconfigured group regroup procedure. +4. The MCPTT server sends the preconfigured regroup cancel requests to MCPTT clients 2 and 3 (steps 4a and 4b respectively). +5. MCPTT clients 2 and 3 notify their users of the cancellation of the group regrouping in steps 5a and 5b respectively. +6. MCPTT clients 2 and 3 may send the preconfigured regroup cancel response to the MCPTT server to acknowledge the cancellation of the regrouping function. These acknowledgements are not sent in response to a multicast transmission of the preconfigured regroup cancel request. +7. The MCPTT server deaffiliates MCPTT clients 2 and 3 from the MCPTT regroup group. +8. The MCPTT server sends a preconfigured regroup cancel response to MCPTT client 1. + +### 10.6.2.9.3 Regroup procedures in multiple MCPTT systems + +#### 10.6.2.9.3.1 Regroup formation using preconfigured group in multiple MCPTT systems + +Figure 10.6.2.9.3.1-1 illustrates the procedure to initiate a regroup procedure using a preconfigured MCPTT group, where at least one of the groups to be regrouped is configured in a partner MCPTT system. The primary MCPTT system where the preconfigured group regrouping is initiated does not need to be aware of the list of group members belonging to groups whose group home system is the partner MCPTT system. If the group management server in the + +primary MCPTT of the regroup group shares the necessary security related parameters together with the group configuration of the MCPTT regroup group with the group management server in the partner MCPTT system and the group management server in the partner MCPTT system distributes this configuration including those security parameters to its served MCPTT users according to the procedures in 3GPP TS 23.280 [16] subclause 10.2.7, the primary MCPTT system does not need to be aware of the list of group members of the preconfigured regroup group that are receiving service in the partner MCPTT system. + +The procedure takes place prior to the establishment of a group call to the regroup group. + +In this procedure, any gateway MC servers in the primary or partner MCPTT systems are not shown. + +Pre-conditions: + +- MCPTT client 1 is authorized to initiate a preconfigured regroup procedure, and is receiving MCPTT service in the primary MCPTT system of MCPTT client 1. +- MCPTT client 2 is an affiliated member of MCPTT group 1 where MCPTT group 1 is defined in the partner MCPTT system and MCPTT client 2 is receiving service in the partner MCPTT system of MCPTT client 1. +- The MCPTT group identity and group configuration for the regroup MCPTT group have been preconfigured in MCPTT client 2, and MCPTT client 2 has received the relevant security related information to allow communication in the regroup MCPTT group. +- In order to be aware whether the group is regrouped, the MCPTT server is subscribed to the group configuration in GMS. +- The GMS has subscribed group dynamic data as specified in subclause 10.1.5.5.1 from the MCPTT server within the same MCPTT system using the procedures defined in subclause 10.1.5.6 in TS 23.280 [16]. + +![Sequence diagram of the regroup procedure using preconfigured group in multiple MCPTT systems.](da5a8f834706c8119a47c5eb732feabe_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server (primary) + participant MCPTT server (partner) + participant MCPTT client 2 + + Note left of MCPTT client 1: 1. Initiate preconfigured regroup + MCPTT client 1->>MCPTT server (primary): 2. Preconfigured regroup request + Note right of MCPTT server (primary): 3. Check authorization and resolve group IDs + MCPTT server (primary)->>MCPTT server (partner): 4. Preconfigured regroup request + Note right of MCPTT server (partner): 5. Check requested groups and identify affiliated group members + MCPTT server (partner)->>MCPTT client 2: 6. Preconfigured regroup request + Note right of MCPTT client 2: 7. Notify user + MCPTT client 2-->>MCPTT server (partner): 8. Preconfigured regroup response + Note right of MCPTT server (partner): 9. Affiliate MCPTT clients to regroup group + MCPTT server (partner)->>MCPTT server (primary): 10. Preconfigured regroup response + MCPTT server (primary)->>MCPTT client 1: 11. Preconfigured regroup response +``` + +The diagram illustrates the regroup procedure across two MCPTT service providers. On the left, the Primary MCPTT service provider contains MCPTT client 1 and MCPTT server (primary). On the right, the Partner MCPTT service provider contains MCPTT server (partner) and MCPTT client 2. The sequence of messages is as follows: 1. MCPTT client 1 initiates a preconfigured regroup. 2. MCPTT client 1 sends a preconfigured regroup request to MCPTT server (primary). 3. MCPTT server (primary) checks authorization and resolves group IDs. 4. MCPTT server (primary) sends a preconfigured regroup request to MCPTT server (partner). 5. MCPTT server (partner) checks requested groups and identifies affiliated group members. 6. MCPTT server (partner) sends a preconfigured regroup request to MCPTT client 2. 7. MCPTT client 2 notifies the user. 8. MCPTT client 2 sends a preconfigured regroup response to MCPTT server (partner). 9. MCPTT server (partner) affiliates MCPTT clients to the regroup group. 10. MCPTT server (partner) sends a preconfigured regroup response to MCPTT server (primary). 11. MCPTT server (primary) sends a preconfigured regroup response to MCPTT client 1. + +Sequence diagram of the regroup procedure using preconfigured group in multiple MCPTT systems. + +Figure 10.6.2.9.3.1-1: Regroup procedure using preconfigured group in multiple MCPTT systems + +1. The authorized user of MCPTT client 1 initiates the regroup procedure, specifying the list of MCPTT groups to be regrouped including MCPTT group 1, the MCPTT group ID of the regroup group and the MCPTT group ID of the group from which configuration information for the regroup group is to be taken. +2. MCPTT client 1 sends the preconfigured regroup request to the MCPTT server. +3. The MCPTT server checks that MCPTT client 1 is authorized to initiate a preconfigured regroup procedure, and resolves the group identities of the MCPTT groups requested in step 1. The MCPTT server also checks which group members are affiliated to the requested MCPTT groups that are homed in the primary MCPTT system. The MCPTT server identifies any partner systems which are the group home systems for MCPTT groups identified in the list of groups to be regrouped. The MCPTT server may retrieve the configuration for the regroup group from the GMS if that configuration information is not already known to the MCPTT server. + +NOTE 1: This procedure does not require that that the authorized user of MCPTT client 1 is a group member of the MCPTT groups listed in the regroup request, or that the authorized user of MCPTT client 1 is an affiliated group member of any of the listed MCPTT groups. + +4. The MCPTT server sends the preconfigured regroup requests to the MCPTT server in the partner MCPTT system. +5. The partner MCPTT server checks the status of any MCPTT groups hosted by that partner MCPTT server, and identifies affiliated group members of any of the identified MCPTT groups (both MCPTT groups that are hosted in the primary MCPTT system and MCPTT groups that are hosted in the partner MCPTT system) that are receiving MCPTT service in the partner MCPTT system, which include MCPTT client 2. +6. The partner MCPTT server sends the preconfigured regroup request to MCPTT client 2. + +NOTE 2: Only group members that are affiliated to the MCPTT groups that are to be regrouped are sent a preconfigured regroup request. + +7. MCPTT client 2 notifies the user of the regrouping. +8. MCPTT client 2 may send the preconfigured regroup response to the partner MCPTT server to acknowledge the regrouping action. This acknowledgement is not sent in response to a multicast transmission of the preconfigured regroup request. +9. The partner MCPTT server affiliates the regrouped MCPTT client 2 to the regroup group. +10. The MCPTT server sends a preconfigured regroup response to the primary MCPTT server. +11. The primary MCPTT server sends the preconfigured regroup response to MCPTT client 1. + +After the group regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in 10.6.2.9.3.2. + +MCPTT client participation in the ongoing regroup persists until the MCPTT client is no longer affiliated to any of the regrouped groups (group 1 or 2 in this procedure). + +MCPTT client affiliation to the regroup group may cease when the UE's MCPTT service ceases, e.g. when the UE is powered down, or by performing a log-off operation. + +**Editor's note: Data persistence in the MCPTT client following a user log-off or power down needs further study.** + +#### 10.6.2.9.3.2 Regroup cancellation using preconfigured group in multiple MCPTT systems + +Figure 10.6.2.9.3.2-1 illustrates the procedure to cancel a regrouping that uses a preconfigured MCPTT group where multiple MCPTT systems were involved in the regrouping. + +Pre-conditions: + +- MCPTT client 2 has been regrouped into an MCPTT regroup group, and is receiving MCPTT service in the partner MCPTT system of the regroup group. +- MCPTT client 1 is authorized to cancel a regrouping that uses a preconfigured MCPTT group, and is receiving MCPTT service in the primary MCPTT system of the regroup group. + +- The GMS has subscribed to group dynamic data as specified in subclause 10.1.5.5.1 from the MCPTT server within the same MCPTT system using the procedures defined in subclause 10.1.5.6 in TS 23.280 [16]. + +![Sequence diagram illustrating the 'Cancel preconfigured regroup procedure using preconfigured group in multiple MCPTT systems'. The diagram shows interactions between MCPTT client 1, MCPTT server (primary), MCPTT server (partner), and MCPTT client 2 across two service providers: Primary MCPTT service provider and Partner MCPTT service provider. The steps are: 1. Initiate preconfigured regroup (client 1 to server primary); 2. Preconfigured regroup cancel request (client 1 to server primary); 3. Check authorization (server primary internal); 4. Preconfigured regroup cancel request (server primary to server partner); 5. Preconfigured regroup cancel request (server partner to client 2); 6. Notify user (client 2 internal); 7. Preconfigured regroup cancel response (client 2 to server partner); 8. Deaffiliate MCPTT client 2 (server partner internal); 9. Preconfigured regroup cancel response (server partner to server primary); 10. Preconfigured regroup cancel response (server primary to client 1).](af90aabfe3c8c65617da060d82bf99c5_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server (primary) + participant MCPTT server (partner) + participant MCPTT client 2 + + Note left of MCPTT client 1: 1. Initiate preconfigured regroup + MCPTT client 1->>MCPTT server (primary): 2. Preconfigured regroup cancel request + Note right of MCPTT server (primary): 3. Check authorization + MCPTT server (primary)->>MCPTT server (partner): 4. Preconfigured regroup cancel request + MCPTT server (partner)->>MCPTT client 2: 5. Preconfigured regroup cancel request + Note right of MCPTT client 2: 6. Notify user + MCPTT client 2-->>MCPTT server (partner): 7. Preconfigured regroup cancel response + Note right of MCPTT server (partner): 8. Deaffiliate MCPTT client 2 + MCPTT server (partner)->>MCPTT server (primary): 9. Preconfigured regroup cancel response + MCPTT server (primary)->>MCPTT client 1: 10. Preconfigured regroup cancel response + +``` + +Sequence diagram illustrating the 'Cancel preconfigured regroup procedure using preconfigured group in multiple MCPTT systems'. The diagram shows interactions between MCPTT client 1, MCPTT server (primary), MCPTT server (partner), and MCPTT client 2 across two service providers: Primary MCPTT service provider and Partner MCPTT service provider. The steps are: 1. Initiate preconfigured regroup (client 1 to server primary); 2. Preconfigured regroup cancel request (client 1 to server primary); 3. Check authorization (server primary internal); 4. Preconfigured regroup cancel request (server primary to server partner); 5. Preconfigured regroup cancel request (server partner to client 2); 6. Notify user (client 2 internal); 7. Preconfigured regroup cancel response (client 2 to server partner); 8. Deaffiliate MCPTT client 2 (server partner internal); 9. Preconfigured regroup cancel response (server partner to server primary); 10. Preconfigured regroup cancel response (server primary to client 1). + +**Figure 10.6.2.9.3.2-1: Cancel preconfigured regroup procedure using preconfigured group in multiple MCPTT systems** + +1. The authorized user of MCPTT client 1 initiates the cancellation of the regrouping that uses a preconfigured MCPTT group. +2. MCPTT client 1 sends the preconfigured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the regroup group. +3. The MCPTT server checks that MCPTT client 1 is authorized to cancel a regrouping that uses a preconfigured group regroup procedure. +4. The primary MCPTT server sends the regroup cancel request to the partner MCPTT server. +5. The partner MCPTT server sends the preconfigured regroup cancel requests to MCPTT client 2. +6. MCPTT client 2 notifies the user of the cancellation of the group regrouping. +7. MCPTT client 2 may send the preconfigured regroup remove response to the partner MCPTT server to acknowledge the cancellation of the regrouping function. This acknowledgement is not sent in response to a multicast transmission of the preconfigured regroup cancel request. +8. The partner MCPTT server deaffiliates MCPTT client 2 from the MCPTT regroup group. +9. The partner MCPTT server sends the preconfigured regroup cancel response to the primary MCPTT server. +10. The primary MCPTT server sends a preconfigured regroup cancel response to MCPTT client 1. + +10.6.2.9.3.3 Regroup rejection using preconfigured group in multiple MCPTT systems + +Figure 10.6.2.9.3.3-1 illustrates the case where the procedure to initiate a regroup procedure with multiple MCPTT systems using a preconfigured MCPTT group described in subclause 10.6.2.9.3.1 commences, but where the request for the regroup is rejected by the partner MCPTT server, for example because one of the groups hosted by the partner MCPTT server is already regrouped by other group regrouping procedures. + +In this procedure, any gateway MC servers in the primary or partner MCPTT systems are not shown. + +Pre-conditions: + +- MCPTT client 1 is authorized to initiate a preconfigured regroup procedure, and is receiving MCPTT service in the primary MCPTT system of MCPTT client 1. + +![Sequence diagram showing regroup rejection. Lifelines: MCPTT client 1, MCPTT server (primary), MCPTT server (partner), MCPTT client 2. Steps: 1. Initiate preconfigured regroup; 2. Preconfigured regroup request; 3. Check authorization and resolve group IDs; 4. Preconfigured regroup request; 5. Check requested groups; 6. Preconfigured regroup reject; 7. Preconfigured regroup reject.](3380dd0ed19bc6f4da5a9d8c55ba535d_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server (primary) + participant MCPTT server (partner) + participant MCPTT client 2 + + Note left of MCPTT client 1: 1. Initiate preconfigured regroup + MCPTT client 1->>MCPTT server (primary): 2. Preconfigured regroup request + Note right of MCPTT server (primary): 3. Check authorization and resolve group IDs + MCPTT server (primary)->>MCPTT server (partner): 4. Preconfigured regroup request + Note right of MCPTT server (partner): 5. Check requested groups + MCPTT server (partner)->>MCPTT server (primary): 6. Preconfigured regroup reject + MCPTT server (primary)->>MCPTT client 1: 7. Preconfigured regroup reject + +``` + +Sequence diagram showing regroup rejection. Lifelines: MCPTT client 1, MCPTT server (primary), MCPTT server (partner), MCPTT client 2. Steps: 1. Initiate preconfigured regroup; 2. Preconfigured regroup request; 3. Check authorization and resolve group IDs; 4. Preconfigured regroup request; 5. Check requested groups; 6. Preconfigured regroup reject; 7. Preconfigured regroup reject. + +Figure 10.6.2.9.3.3-1: Regroup rejection using preconfigured group in multiple MCPTT systems + +1. The authorized user of MCPTT client 1 initiates the regroup procedure, specifying the list of MCPTT groups to be regrouped including MCPTT group 1, the MCPTT group ID of the regroup group and the MCPTT group ID of the group from which configuration information for the regroup group is to be taken. +2. MCPTT client 1 sends the preconfigured regroup request to the MCPTT server. +3. The MCPTT server checks that MCPTT client 1 is authorized to initiate a preconfigured regroup procedure, and resolves the group identities of the MCPTT groups requested in step 1. The MCPTT server also checks which group members are affiliated to the requested MCPTT groups that are homed in the primary MCPTT system. The MCPTT server identifies any partner systems which are the group home systems for MCPTT groups identified in the list of groups to be regrouped. The MCPTT server may retrieve the configuration for the regroup group from the GMS if that configuration information is not already known to the MCPTT server. + +NOTE: This procedure does not require that that the authorized user of MCPTT client 1 is a group member of the MCPTT groups listed in the regroup request, or that the authorized user of MCPTT client 1 is an affiliated group member of any of the listed MCPTT groups. + +4. The MCPTT server sends the preconfigured regroup requests to the MCPTT server in the partner MCPTT system. + +5. The partner MCPTT server checks the status of any MCPTT groups hosted by that partner MCPTT server, and determines that one or more requested MCPTT groups has already been regrouped by another group regrouping procedure. +6. The partner MCPTT server sends a preconfigured regroup reject to the primary MCPTT server, indicating the reason for rejection. +7. The primary MCPTT server sends a preconfigured regroup reject to MCPTT client 1, indicating the reason for rejection. + +**10.6.2.9.4 Adding newly affiliated user to preconfigured group regroup** + +Figure 10.6.2.9.4-1 illustrates the procedure to add a newly affiliated user to an in-progress preconfigured MCPTT group regroup operation. + +Pre-conditions: + +- The MCPTT client is a member of a MCPTT group that is part of an in-progress preconfigured group regroup operation. +- The MCPTT group identity and group configuration for the regroup MCPTT group has been preconfigured in the MCPTT client, and the MCPTT client has received the relevant security related information to allow it to communicate in the regroup MCPTT group. + +![Sequence diagram showing the procedure to add a newly affiliated user to a preconfigured regroup. Lifelines: MCPTT client, MCPTT server, Group management server. Steps: 1. Group affiliation procedure per TS 23.280 section 10.8.3.1; 2. Retrieve regroup information; 3. Preconfigured regroup request; 4. Notify user; 5. Preconfigured regroup response; 6. Affiliate MCPTT client to regroup group.](23d9fcc2863a6b0548d6b4e8abf15106_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant Group management server + Note over MCPTT client, Group management server: 1. Group affiliation procedure per TS 23.280 section 10.8.3.1 + Note over MCPTT server: 2. Retrieve regroup information + MCPTT server->>MCPTT client: 3. Preconfigured regroup request + Note left of MCPTT client: 4. Notify user + MCPTT client-->>MCPTT server: 5. Preconfigured regroup response + Note over MCPTT server: 6. Affiliate MCPTT client to regroup group + +``` + +Sequence diagram showing the procedure to add a newly affiliated user to a preconfigured regroup. Lifelines: MCPTT client, MCPTT server, Group management server. Steps: 1. Group affiliation procedure per TS 23.280 section 10.8.3.1; 2. Retrieve regroup information; 3. Preconfigured regroup request; 4. Notify user; 5. Preconfigured regroup response; 6. Affiliate MCPTT client to regroup group. + +**Figure 10.6.2.9.4-1: Procedure to add a newly affiliated user to a preconfigured regroup** + +1. The MCPTT client affiliates to an MCPTT group that is currently part of an in-progress preconfigured group regroup. The affiliation follows the procedure in section 10.8.3.1 of TS 23.280 [16]. +2. The MCPTT server retrieves the MCPTT group ID of the regroup group and the MCPTT group ID of the group from which configuration information for the regroup group is to be taken. +3. The MCPTT server sends the preconfigured regroup request to the MCPTT client. + +- 4. The MCPTT client notifies the user of the regrouping. +- 5. The MCPTT client may send the preconfigured regroup response to the MCPTT server to acknowledge the regrouping action. These acknowledgements are not sent in response to a multicast transmission of the preconfigured regroup request. +- 6. The MCPTT server affiliates the regrouped MCPTT client to the regroup group. + +Editor's Note: It is FFS whether this procedure can be generalized to apply to both preconfigured and GMS-based group regrouping. + +Editor's Note: Affiliations of the MCPTT client to the pre-configured regroup group in the MCPTT server and coordination to the MC System is FFS. + +10.6.2.9.5 Preconfigured regroup update procedures + +10.6.2.9.5.1 MCPTT client PTTs on MCPTT group during an in-progress preconfigured group regroup + +Figure 10.6.2.9.5.1-1 illustrates the procedure when a user attempts to setup an MCPTT group call on a group involved in an in-progress preconfigured MCPTT group regroup. + +Pre-conditions: + +- The MCPTT client is an affiliated member of MCPTT group A that is part of an in-progress preconfigured group regroup with MCPTT groups B and C. +- MCPTT group D is being used as the preconfigured regroup group. +- The MCPTT client has missed the preconfigured regroup request message (e.g. poor signalling conditions, race condition). + +![Sequence diagram showing the procedure for MCPTT client PTTs on MCPTT group during an in-progress preconfigured group regroup. The diagram involves three lifelines: MCPTT client, MCPTT server, and user. The sequence of messages is: 1. Group call request (client to server), 2. Check group regroup status (server internal), 3. Group call response (server to client), 4. Preconfigured regroup request (server to client), 5. Notify user (client internal), 6. Preconfigured regroup response (client to server), 7. Affiliate MCPTT client to regroup group (server internal).](f9873201604e723ae0bafb7e389ef619_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant user + Note right of MCPTT server: 2. Check group regroup status + MCPTT client->>MCPTT server: 1. Group call request + MCPTT server-->>MCPTT client: 3. Group call response + MCPTT server-->>MCPTT client: 4. Preconfigured regroup request + Note left of MCPTT client: 5. Notify user + MCPTT client->>MCPTT server: 6. Preconfigured regroup response + Note right of MCPTT server: 7. Affiliate MCPTT client to regroup group + +``` + +Sequence diagram showing the procedure for MCPTT client PTTs on MCPTT group during an in-progress preconfigured group regroup. The diagram involves three lifelines: MCPTT client, MCPTT server, and user. The sequence of messages is: 1. Group call request (client to server), 2. Check group regroup status (server internal), 3. Group call response (server to client), 4. Preconfigured regroup request (server to client), 5. Notify user (client internal), 6. Preconfigured regroup response (client to server), 7. Affiliate MCPTT client to regroup group (server internal). + +Figure 10.6.2.9.5.1-1: Procedure for MCPTT client PTTs on MCPTT group during an in-progress preconfigured group regroup + +1. The MCPTT client attempts to start a call on MCPTT group A. The MCPTT client sends a group call request message to the MCPTT server containing MCPTT group A as the target group. +2. The MCPTT server checks to see whether MCPTT group A is currently part of a preconfigured group regroup. In this case the group is part of an active preconfigured group regroup. +3. The MCPTT server sends a group call response to the MCPTT client indicating that the call setup is denied because the group is part of an in-progress group regroup. +4. The MCPTT server sends the preconfigured regroup request to the MCPTT client containing MCPTT group D, the group ID of the preconfigured group. + +NOTE 1: This message should be sent over unicast. + +5. The MCPTT client notifies the user of the group call setup failure and of the regrouping procedure. +6. The MCPTT client sends the preconfigured regroup response to the MCPTT server to acknowledge the regrouping action. +7. The MCPTT server affiliates the regrouped MCPTT client to the regroup group. + +NOTE 2: If there is a call currently in progress on the regroup group then this MCPTT client can be added to the call using the late entry procedure. If there is no call currently in progress, then the MCPTT user can retry the group call setup. + +10.6.2.9.5.2 MCPTT client PTTs on preconfigured regroup group after group regroup has been cancelled + +Figure 10.6.2.9.5.2-1 illustrates the procedure when a user attempts to setup a MCPTT group call on a preconfigured regroup group after the preconfigured MCPTT group regroup has been cancelled. + +Pre-conditions: + +- The MCPTT client is a member of MCPTT group A that was part of an in-progress preconfigured group regroup with MCPTT groups B and C that has been cancelled. MCPTT group D was used as the MCPTT regroup group. +- The MCPTT client has missed the preconfigured regroup cancel request message (e.g. poor signalling conditions, race condition). + +![Sequence diagram showing the procedure for MCPTT client PTTs on a regroup group after the group regroup has been cancelled. The diagram involves an MCPTT client and an MCPTT server. The sequence of messages is: 1. Group call request (client to server), 2. Check group regroup status (server internal), 3. Group call response (server to client), 4. Preconfigured regroup cancel request (server to client), 5. Notify user (client internal), 6. Preconfigured regroup cancel response (client to server).](61520b710bffec2edcf998d1ed43beb9_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + Note right of MCPTT server: 2. Check group regroup status + Note left of MCPTT client: 5. Notify user + MCPTT client->>MCPTT server: 1. Group call request + MCPTT server-->>MCPTT client: 3. Group call response + MCPTT server-->>MCPTT client: 4. Preconfigured regroup cancel request + MCPTT client-->>MCPTT server: 6. Preconfigured regroup cancel response + +``` + +Sequence diagram showing the procedure for MCPTT client PTTs on a regroup group after the group regroup has been cancelled. The diagram involves an MCPTT client and an MCPTT server. The sequence of messages is: 1. Group call request (client to server), 2. Check group regroup status (server internal), 3. Group call response (server to client), 4. Preconfigured regroup cancel request (server to client), 5. Notify user (client internal), 6. Preconfigured regroup cancel response (client to server). + +Figure 10.6.2.9.5.2-1: Procedure for MCPTT client PTTs on regroup group after the group regroup is cancelled + +1. The MCPTT client attempts to start a call on MCPTT group D, the MCPTT regroup group. The MCPTT client sends a group call request message to the MCPTT server containing MCPTT group D as the target group. +2. The MCPTT server checks to see whether MCPTT group D is currently being used as part of a preconfigured group regroup. In this case the preconfigured group regroup is no longer active. + +NOTE 1: The regroup group D can be a group in the MCPTT client's profile, and the MCPTT client can be a member of group D. + +3. The MCPTT server sends a group call response to the MCPTT client indicating that the call setup is denied because the group regroup is no longer active. + +NOTE 2: In the following, steps 4 and 6 are optional. + +4. The MCPTT server sends the preconfigured regroup cancel request to the MCPTT client. + +NOTE 3: This message should be sent over unicast. + +5. The MCPTT client notifies the user of the group call setup failure and of the regrouping cancellation. + +6. The MCPTT client sends the preconfigured regroup cancel response to the MCPTT server to acknowledge the regrouping cancellation. + +NOTE 4: If there is a call currently in progress on MCPTT group A that was previously part of the group regroup then this MCPTT client can be added to the call using the late entry procedure. If there is no call currently in progress then the MCPTT user can retry the group call setup on MCPTT group A. + +#### 10.6.2.10 User regroup using group creation procedure + +##### 10.6.2.10.1 General + +User regroup using the group creation procedure can be initiated by an authorized user creating a temporary group with a list of MCPTT users. The group ID for this temporary group can be provided at the time of group creation. The temporary group can be used by all MCPTT users in the list for two-way (non-broadcast) communication until deleted by an authorized user. Optionally, the group can be used for one-way (broadcast ) communication where the creator of the temporary group can make a broadcast group call, but the other MCPTT users can only listen to the group call and cannot respond. + +##### 10.6.2.10.2 Temporary group creation and broadcast group call by authorized user + +Figure 10.6.2.10.2-1 below illustrates the temporary group creation, and optional broadcast call setup procedure and temporary group deletion initiated by an authorized user. + +Pre-conditions: + +1. The authorized user is aware of the MCPTT users who will be included in the temporary group. + +![Sequence diagram showing the interaction between MCPTT UE 1 (Authorized User), Group management Server, MCPTT Server, MCPTT UE 2, and MCPTT UE 3. The sequence consists of three steps: 1. Group creation, 2. Broadcast group call, and 3. Group deletion.](d6e51d738a5a275c98682adb31ba5f30_img.jpg) + +``` + +sequenceDiagram + participant UE1 as MCPTT UE 1 (Authorized User) + participant GMS as Group management Server + participant MS as MCPTT Server + participant UE2 as MCPTT UE 2 + participant UE3 as MCPTT UE 3 + Note right of UE1: 1. Group creation + Note right of UE1: 2. Broadcast group call + Note right of UE1: 3. Group deletion + +``` + +Sequence diagram showing the interaction between MCPTT UE 1 (Authorized User), Group management Server, MCPTT Server, MCPTT UE 2, and MCPTT UE 3. The sequence consists of three steps: 1. Group creation, 2. Broadcast group call, and 3. Group deletion. + +Figure 10.6.2.10.2-1: User regroup using group creation procedure + +1. The authorized user of MCPTT UE 1 makes use of the group management client of MCPTT UE 1 to create the temporary group according to the group creation procedure in 3GPP TS 23.280 [16] subclause 10.2.3. The configuration identifies the group as a temporary group. As part of this procedure, the MCPTT users are notified + +of their membership to the temporary group, and the MCPTT server is notified about the creation of the group and the list of group members. + +The authorized user can create the group as a broadcast group by configuring it as a broadcast group. + +NOTE 1: After step 1 the temporary group can be used by all members of the group for two-way (non-broadcast) communication until deleted by an authorized user. + +NOTE 2: The following two steps are optional and can be used for broadcast communication where only the creator of the temporary group is allowed to transmit media on this temporary group. + +2. The creator of the temporary group, the authorized user of MCPTT UE 1, initiates a broadcast group call according to the procedure described in subclause 10.6.2.5.2 of the present document. The authorized user of MCPTT UE 1 is implicitly affiliated to the temporary group. The receiving MCPTT clients of MCPTT UEs 2 and 3 are implicitly affiliated to the group and are notified of this affiliation during the call setup. +3. The authorized user of MCPTT UE 1 ends the use of the temporary group according to the procedure for group deletion described in 3GPP TS 23.280 [16]. + +##### 10.6.2.10.3 Temporary group deletion by authorized user + +If the authorized user wishes to end the use of the temporary group, the procedure for group deletion described in 3GPP TS 23.280 [16] is followed. + +#### 10.6.2.11 Broadcast group regroup call using preconfigured group + +##### 10.6.2.11.1 General + +The temporary group created using a preconfigured group can be a broadcast group or a non-broadcast group. The broadcast regroup is used for one-way communication where only an authorized MCPTT user is allowed to transmit and all other regroup members are only allowed to receive the communication (e.g. a call from a dispatcher to all regroup members). The non-broadcast regroup is used for two-way communication where all regroup members can transmit and receive (i.e. the regroup group call behaves like a normal non-broadcast group call). The broadcast regroup satisfies the temporary group-broadcast group requirements defined in 3GPP TS 22.280 [2] and is an alternative to the "Temporary group – broadcast group call" procedure (10.6.2.5.3) defined in 3GPP TS 23.379 [16]. + +A broadcast group regroup call using preconfigured groups can be achieved by first regrouping MCPTT groups into an MCPTT regroup group, making the broadcast group call on the regroup group, and then cancelling the preconfigured group regroup. + +##### 10.6.2.11.2 Broadcast group regroup call procedure using preconfigured group in a single MCPTT system + +The broadcast group regroup call procedure using preconfigured group allows an authorized MCPTT user to initiate a broadcast call to a set of MCPTT groups, which are regrouped only for the duration of the broadcast call. The regroup is cancelled at the end of the broadcast call to prevent users from talking back on the regroup group. This procedure requires that the authorized MCPTT user is a group member of at least one of the MCPTT groups included in the regroup operation. + +Figure 10.6.2.11.2-1 illustrates the procedure to initiate a broadcast group regroup call using a preconfigured MCPTT group. + +Pre-conditions: + +- MCPTT clients 1, 2, and 3 are registered with the MCPTT service. +- The group configuration for the MCPTT regroup group have been preconfigured in MCPTT clients 1, 2, and 3, and MCPTT clients 1, 2 and 3 have received the relevant security related information to allow them to communicate in the regroup MCPTT group. +- MCPTT client 1 is authorized to initiate a group regroup using the preconfigured regroup procedure. +- MCPTT client 1 is aware of a suitable preconfigured group whose configuration has been preconfigured in the MC service UEs of the MCPTT users who will be regrouped. + +- MCPTT client 1 is affiliated to group 1, MCPTT client 2 is affiliated to group 2, and MCPTT client 3 is affiliated to group 3. Group 4 is used as the regroup group. + +![Sequence diagram showing a broadcast group regroup call using preconfigured group in a single MCPTT system. The diagram shows four entities: MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3, all under the 'Home MCPTT service provider'. The sequence of messages is: 1. Preconfigured group regroup procedure, 2. Broadcast group call, 3. Preconfigured group regroup cancellation.](163688ca8da9787f5d48edd68d8cc75b_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + Note over MCPTT client 1, MCPTT client 3: Home MCPTT service provider + MCPTT client 1->>MCPTT server: 1. Preconfigured group regroup procedure + MCPTT server-->>MCPTT client 1: + MCPTT client 1->>MCPTT server: 2. Broadcast group call + MCPTT server-->>MCPTT client 1: + MCPTT client 1->>MCPTT server: 3. Preconfigured group regroup cancellation + MCPTT server-->>MCPTT client 1: + +``` + +Sequence diagram showing a broadcast group regroup call using preconfigured group in a single MCPTT system. The diagram shows four entities: MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3, all under the 'Home MCPTT service provider'. The sequence of messages is: 1. Preconfigured group regroup procedure, 2. Broadcast group call, 3. Preconfigured group regroup cancellation. + +**Figure 10.6.2.11.2-1: Broadcast group regroup call using preconfigured group in a single MCPTT system** + +1. The authorized user of MCPTT client 1 initiates the group regroup formation procedure using preconfigured groups as specified in 10.6.2.9.2.1. MCPTT groups 1, 2, and 3 are regrouped into group 4. +2. The MCPTT user at MCPTT client 1 performs the broadcast group call procedure as specified in 10.6.2.5.2. +3. If the broadcast group call is made on the regroup group 4, the MCPTT client 1 initiates the preconfigured group regroup cancellation procedure as specified in 10.6.2.9.2.2. + +#### 10.6.2.12 User regroup with preconfigured group + +##### 10.6.2.12.1 General + +A user regroup may be achieved by regrouping MCPTT users into a new regroup group which uses the configuration of a separate preconfigured MCPTT group. The MCPTT regroup group configuration needs to be provided to the relevant MCPTT users who will be regrouped in advance of the regrouping operation. User regroup with preconfigured group satisfies user regroup requirements in 3GPP TS 22.180 [17], particularly [R-6.6.4.2-003]. + +NOTE 1: A preconfigured group which is intended only to provide configuration for the preconfigured regroup process is identified by a parameter in the group configuration described in 3GPP TS 23.280 [16]. + +NOTE 2: The configuration may alternatively be taken from any MCPTT group that has been configured in the user profile of all of the relevant MCPTT users who will be regrouped. + +**Editor's note:** These procedures provide a regrouping service for MCPTT only; any issues arising from conflicts with similar regrouping operations for MCVide and MCData are FFS. + +The preconfigured MCPTT group that provides the configuration is not used as the MCPTT regroup group itself, it only provides configuration for one or more MCPTT regroup groups. The MCPTT group ID of the regroup group is provided by the authorized user when the preconfigured regrouping is carried out. + +##### 10.6.2.12.2 User regroup procedures in a single MCPTT system + +###### 10.6.2.12.2.1 User regroup formation in a single MCPTT system + +Figure 10.6.2.12.2.1-1 illustrates the procedure to initiate a user regroup procedure using a preconfigured MCPTT group. The procedure takes place prior to the establishment of a group call to the MCPTT regroup group. + +Pre-conditions: + +- MCPTT clients 2 and 3 are registered with the MCPTT service. +- An MCPTT group that will be used for configuration of the temporary user regroup group has been preconfigured in MCPTT clients 2 and 3, and MCPTT clients 2 and 3 have received the relevant security related information to allow them to communicate in the temporary user regroup group. +- MCPTT client 1 is authorized to initiate a user regroup using the preconfigured regroup procedure. +- MCPTT client 1 is aware of a suitable preconfigured group whose configuration has been preconfigured in the MC service UEs of the MCPTT users who will be regrouped. + +![Sequence diagram of the user regroup procedure using a preconfigured group in a single MCPTT system.](f0bae10b54c4f3cf8d0e33f5e2fb7cfa_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + Note left of MCPTT client 1: 1. Initiate preconfigured User regroup + MCPTT client 1->>MCPTT server: 2. Preconfigured regroup request + Note right of MCPTT server: 3. Check authorizations + MCPTT server->>MCPTT client 2: 4a. Preconfigured regroup request + MCPTT server->>MCPTT client 3: 4b. Preconfigured regroup request + Note right of MCPTT client 2: 5a. Notify user + Note right of MCPTT client 3: 5b. Notify user + MCPTT client 2-->>MCPTT server: 6a. Preconfigured regroup response + MCPTT client 3-->>MCPTT server: 6b. Preconfigured regroup response + Note right of MCPTT server: 7. Affiliate MCPTT clients to regroup group + MCPTT server->>MCPTT client 1: 8. Preconfigured regroup response +``` + +The diagram illustrates the sequence of messages for the user regroup procedure. It starts with MCPTT client 1 initiating the procedure (step 1). Client 1 sends a preconfigured regroup request to the MCPTT server (step 2). The server checks authorizations (step 3). The server then sends preconfigured regroup requests to MCPTT clients 2 and 3 (steps 4a and 4b). MCPTT clients 2 and 3 notify their users (steps 5a and 5b). MCPTT clients 2 and 3 send preconfigured regroup responses to the server (steps 6a and 6b). The server affiliates MCPTT clients to the regroup group (step 7). Finally, the server sends a preconfigured regroup response to MCPTT client 1 (step 8). + +Sequence diagram of the user regroup procedure using a preconfigured group in a single MCPTT system. + +**Figure 10.6.2.12.2.1-1: User regroup procedure using preconfigured group in single MCPTT system** + +1. The authorized user of MCPTT client 1 initiates the user regroup procedure, specifying the list of MCPTT users to be regrouped (MCPTT clients 2 and 3), the MCPTT group ID of the regroup group, and the MCPTT group ID of the group from which configuration information for the regroup group is to be taken. +2. MCPTT client 1 sends the preconfigured regroup request to the MCPTT server. The request indicates the list of users to be included in the regroup operation. + +3. The MCPTT server checks that MCPTT client 1 is authorized to initiate a preconfigured regroup procedure. + +NOTE 1: MCPTT clients can be involved in multiple user and group regroups simultaneously. + +4. The MCPTT server sends the preconfigured regroup requests to MCPTT clients 2 and 3 in steps 4a and 4b respectively. + +NOTE 2: When using multicast, the MCPTT server can periodically rebroadcast the preconfigured regroup request. + +5. MCPTT clients 2 and 3 notify their users of the regrouping in steps 5a and 5b respectively. + +6. MCPTT clients 2 and 3 may send the preconfigured regroup response to the MCPTT server to acknowledge the regrouping action. These acknowledgements are not sent in response to a multicast transmission of the preconfigured regroup request. +7. The MCPTT server affiliates the regrouped MCPTT clients to the regroup group. +8. The MCPTT server sends a preconfigured regroup response to MCPTT client 1. + +NOTE 3: After the user regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in 10.6.2.12.2.2. + +###### **10.6.2.12.2.2 User regroup cancellation in single MCPTT system** + +Figure 10.6.2.12.2.2-1 illustrates the procedure to cancel a user regrouping that uses a preconfigured MCPTT group. + +Pre-conditions: + +- MCPTT clients 2 and 3 have been regrouped into an MCPTT regroup group. +- MCPTT client 1 is authorized to cancel a user regrouping that uses a preconfigured MCPTT group. + +![Sequence diagram titled 'Home MCPTT service provider' showing the 'Cancel preconfigured user regroup procedure in single MCPTT system'. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3. The sequence starts with a 'Cancel preconfigured user regroup' action on client 1, followed by a 'Preconfigured regroup cancel request' to the server. The server performs a 'Check authorization' and then sends 'Preconfigured regroup cancel request' messages to clients 2 and 3. Clients 2 and 3 notify their users and send 'Preconfigured regroup cancel response' messages back to the server. Finally, the server performs 'Deaffiliate MCPTT clients' and sends a 'Preconfigured regroup cancel response' back to client 1.](b4a7906eddfd40aaa750e19e56c94a8b_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MCPTT client 1 + participant Server as MCPTT server + participant Client2 as MCPTT client 2 + participant Client3 as MCPTT client 3 + + Note left of Client1: 1. Cancel preconfigured user regrouping + Client1->>Server: 2. Preconfigured regroup cancel request + Note right of Server: 3. Check authorization + Server->>Client2: 4a. Preconfigured regroup cancel request + Server->>Client3: 4b. Preconfigured regroup cancel request + Note right of Client2: 5a. Notify user + Note right of Client3: 5b. Notify user + Client2-->>Server: 6a. Preconfigured regroup cancel response + Client3-->>Server: 6b. Preconfigured regroup cancel response + Note right of Server: 7. Deaffiliate MCPTT clients + Server-->>Client1: 8. Preconfigured regroup cancel response + +``` + +Sequence diagram titled 'Home MCPTT service provider' showing the 'Cancel preconfigured user regroup procedure in single MCPTT system'. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3. The sequence starts with a 'Cancel preconfigured user regroup' action on client 1, followed by a 'Preconfigured regroup cancel request' to the server. The server performs a 'Check authorization' and then sends 'Preconfigured regroup cancel request' messages to clients 2 and 3. Clients 2 and 3 notify their users and send 'Preconfigured regroup cancel response' messages back to the server. Finally, the server performs 'Deaffiliate MCPTT clients' and sends a 'Preconfigured regroup cancel response' back to client 1. + +**Figure 10.6.2.12.2.2-1: Cancel preconfigured user regroup procedure in single MCPTT system** + +1. The authorized user of MCPTT client 1 initiates the cancellation of the user regrouping that uses a preconfigured MCPTT group. +2. MCPTT client 1 sends the preconfigured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the regroup group. +3. The MCPTT server checks that MCPTT client 1 is authorized to cancel a regrouping that uses a preconfigured user regroup procedure. +4. The MCPTT server sends the preconfigured regroup cancel requests to MCPTT clients 2 and 3 (steps 4a and 4b respectively). + +5. MCPTT clients 2 and 3 notify their users of the cancellation of the user regrouping in steps 5a and 5b respectively. +6. MCPTT clients 2 and 3 may send the preconfigured regroup cancel response to the MCPTT server to acknowledge the cancellation of the regrouping function. These acknowledgements are not sent in response to a multicast transmission of the preconfigured regroup cancel request. +7. The MCPTT server deaffiliates MCPTT clients 2 and 3 from the MCPTT regroup group. +8. The MCPTT server sends a preconfigured regroup cancel response to MCPTT client 1. + +### 10.6.3 Off-network group call + +#### 10.6.3.1 General + +Off-network group calls can use pre-defined configuration information provided to MCPTT clients prior to the off-network group call or configuration information that is transmitted to MCPTT clients during group call setup or late entry procedures. + +If off-network group configuration information is pre-defined (e.g. codec to be used) and provided to the MCPTT clients prior to the off-network group call (e.g. as part of group metadata), the MCPTT client will be able to participate in the off-network group call without needing to follow the group call setup or late joining procedures as they will be able to receive the media and signalling without the need for the announcement or invitation. + +If off-network group configuration information is not pre-defined or provided, call parameters need to be transmitted to MCPTT clients via group call announcement or invitation. + +NOTE: When the MCPTT client receives a message that is not addressed to either its MCPTT ID or to any MCPTT group of which the MCPTT client is an affiliated group member, the MCPTT client ignores the message. + +#### 10.6.3.2 Information flows for group call in off-network + +##### 10.6.3.2.1 Group call announcement + +Table 10.6.3.2.1-1 describes the information flow for the group call announcement from the MCPTT client to other MCPTT clients. + +**Table 10.6.3.2.1-1: Group call announcement** + +| Information Element | Status | Description | +|---------------------------|--------|-------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Media type | M | Type of the media to be used for the call | +| Media codec | M | The media codec to be used for the call | +| Multi-cast port | M | Multicast port number for media | +| Floor control port number | M | Port number for floor control protocol | +| Announcement period | M | Period of the group call announcement | +| Encryption parameters | O | Encryption parameters to be used for the call, if the call is to be encrypted | +| Confirm mode indicator | O | Indicates whether the MCPTT group call is to be confirmed | +| Emergency indicator | O | Indicates that the MCPTT group call is an MCPTT emergency call | +| Imminent peril indicator | O | Indicates that the MCPTT group call is an MCPTT imminent peril call | + +##### 10.6.3.2.2 MCPTT upgrade to emergency call + +Table 10.6.3.2.2-1 describes the information flow for the MCPTT upgrade to emergency call from the MCPTT client to other MCPTT clients. + +**Table 10.6.3.2.2-1: MCPTT upgrade to emergency call** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------| +| MCPTT ID | M | The identity of the upgrading party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | + +##### 10.6.3.2.3 MCPTT emergency group state cancel + +Table 10.6.3.2.3-1 describes the information flow for the MCPTT emergency group state cancel from the MCPTT client to other MCPTT clients. + +NOTE: In Rel-14 and Rel-13 versions of this specification the name of this information flow is "MCPTT emergency group cancel". + +**Table 10.6.3.2.3-1: MCPTT emergency group state cancel** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID which emergency state is to be cancelled | + +##### 10.6.3.2.4 Response + +Table 10.6.3.2.4-1 describes the information flow for the response. + +**Table 10.6.3.2.4-1: Response** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------| +| MCPTT ID | M | The identity of the called party | + +##### 10.6.3.2.5 MCPTT emergency alert announcement + +Table 10.6.3.2.5-1 describes the information flow for the MCPTT emergency alert announcement from the MCPTT client to the other MCPTT clients. + +**Table 10.6.3.2.5-1: MCPTT emergency alert announcement** + +| Information Element | Status | Description | +|---------------------|--------|--------------------------------------------------------| +| MCPTT ID | M | The identity of the alerting MCPTT user | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | +| Location | O | The alerting client's location, if known | +| Organization name | M | The alerting user's mission critical organization name | + +##### 10.6.3.2.6 MCPTT emergency alert cancel announcement + +Table 10.6.3.2.6-1 describes the information flow for the MCPTT emergency alert cancel announcement from the MCPTT client to other MCPTT clients. + +**Table 10.6.3.2.6-1: MCPTT emergency alert cancel announcement** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling MCPTT user | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | + +##### 10.6.3.2.7 MCPTT upgrade to imminent peril call + +Table 10.6.3.2.7-1 describes the information flow for the MCPTT upgrade to imminent peril call from the MCPTT client to other MCPTT clients. + +**Table 10.6.3.2.7-1: MCPTT upgrade to imminent peril call** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------| +| MCPTT ID | M | The identity of the upgrading party | +| MCPTT group ID | M | The MCPTT group ID of the group to be upgraded | + +##### 10.6.3.2.8 MCPTT imminent peril group call cancel + +Table 10.6.3.2.8-1 describes the information flow MCPTT imminent peril group call cancel from the MCPTT client to other MCPTT clients. + +**Table 10.6.3.2.8-1: MCPTT imminent peril group call cancel** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the imminent peril is to be cancelled | + +#### 10.6.3.3 Group call setup + +The flow in figure 10.6.3.3-1 illustrates the control plane procedures for MCPTT group call establishment for off-network. The procedure describes how an MCPTT client initiates an MCPTT group call with other MCPTT client within the off-network radio coverage and how the group call is established. + +Pre-conditions: + +- It is assumed that information for ProSe direct communications corresponding to the mappings of MCPTT group ID and ProSe Layer-2 Group ID (see subclause 8.1.3.2 in 3GPP TS 23.280 [16]) are pre-configured; +- It is assumed that a multicast IP address and port for the call setup signalling are pre-configured; +- All messages exchanged between the MCPTT clients for the MCPTT group follows ProSe direct communications as defined in 3GPP TS 23.303 [7]; and +- The MCPTT users of MCPTT client 1, 2 and 3 belong to the same MCPTT group. + +![Sequence diagram for Off-network group call setup. Lifelines: MCPTT client 1 (Call Originator), MCPTT client 2, and MCPTT client 3. The sequence shows: 1. Group call announcement from client 1 to clients 2 and 3. 2. Setting parameters for media plane from clients 2 and 3. 3. Response from clients 2 and 3 back to client 1. 4. A dashed box labeled 'checking participants' spanning all lifelines at the bottom.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 (Call Originator) + participant MCPTT client 2 + participant MCPTT client 3 + Note right of MCPTT client 1: 1. Group call announcement + MCPTT client 1->>MCPTT client 2: + MCPTT client 1->>MCPTT client 3: + Note right of MCPTT client 2: 2. Setting parameters for media plane + Note right of MCPTT client 3: 2. Setting parameters for media plane + MCPTT client 2->>MCPTT client 1: 3. Response + MCPTT client 3->>MCPTT client 1: 3. Response + Note over MCPTT client 1, MCPTT client 2, MCPTT client 3: 4. checking participants + +``` + +Sequence diagram for Off-network group call setup. Lifelines: MCPTT client 1 (Call Originator), MCPTT client 2, and MCPTT client 3. The sequence shows: 1. Group call announcement from client 1 to clients 2 and 3. 2. Setting parameters for media plane from clients 2 and 3. 3. Response from clients 2 and 3 back to client 1. 4. A dashed box labeled 'checking participants' spanning all lifelines at the bottom. + +**Figure 10.6.3.3-1: Off-network group call setup** + +- MCPTT client 1 as the group call originator sends group call announcement message to the group. This message contains the following parameters such as MCPTT group ID, group call originator identity, media type, media codec, multicast port number for media, port number for floor control protocol, period of group call announcement, and any encryption key for the media encryption if needed, and optionally confirm mode indication. + +NOTE 1: The group call announcement includes at least one common set of parameters and values for media transfer. Additional values per parameter will not be prohibited for the better user experience. + +NOTE 2: By using the ProSe Layer-2 Group ID mapping with the MCPTT group ID, ProSe layer ensures that the messages sent for the corresponding MCPTT group are only received by its group's members. + +- MCPTT client 2, 3 join the group call. The MCPTT clients configure the parameters for media delivery by making use of the received parameters in group call announcement. +- MCPTT client 2, 3 may send the response message to the group when the group call announcement from originator includes confirm mode indication. This message contains MCPTT ID. +- MCPTT client 2, 3 recognize the group call originator through the group call announcement and MCPTT client 1 checks the participants of the group call through the received response message. + +NOTE 3: Due to the movement of the participants (in and out of the radio coverage) during the off-network group call, the group call announcement message including parameters for media delivery is periodically sent. + +NOTE 4: The participating MCPTT clients do not need to respond to the periodic group call announcement. + +#### 10.6.3.4 Passive join to group call + +Figure 10.6.3.4-1 illustrates the control plane procedures for the passive MCPTT client to join the on-going MCPTT group call. The passive MCPTT client does not initiate to establish an MCPTT group call, but receives the group call announcement to be transferred periodically. When receiving the announcement message with parameters for media transfer, the passive MCPTT client configures the parameter to receive the voice and joins the announced MCPTT group call. + +This procedure happens after the MCPTT group call is established. The group call announcement including the parameters for the media transfer has been performed periodically, in order for the MCPTT client later to join the MCPTT group call. + +The MCPTT client 4 enters the coverage of the MCPTT group call lately. + +![Sequence diagram illustrating the passive join to group call procedure. Four lifelines are shown: MCPTT client 1, MCPTT client 2, MCPTT client 3, and MCPTT client 4. The process starts with 'Group call establishment' followed by 'Periodic group call announcement' from client 2. Client 4 enters coverage. Client 2 sends a '1. Periodic group call announcement' which is received by client 4. Client 4 performs '2. Setting parameters' and sends '3. Response'. Client 2 then sends a '4. Floor taken' message. Finally, another 'Periodic group call announcement' is shown.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCPTT client 1 + participant C2 as MCPTT client 2 + participant C3 as MCPTT client 3 + participant C4 as MCPTT client 4 + Note over C1, C3: Group call establishment + Note over C1, C3: Periodic group call announcement + Note right of C4: Entry + C2->>C4: 1. Periodic group call announcement + Note right of C4: 2. Setting parameters + C4-->>C2: 3. Response + C2->>C4: 4. Floor taken + Note over C1, C4: Periodic group call announcement + +``` + +Sequence diagram illustrating the passive join to group call procedure. Four lifelines are shown: MCPTT client 1, MCPTT client 2, MCPTT client 3, and MCPTT client 4. The process starts with 'Group call establishment' followed by 'Periodic group call announcement' from client 2. Client 4 enters coverage. Client 2 sends a '1. Periodic group call announcement' which is received by client 4. Client 4 performs '2. Setting parameters' and sends '3. Response'. Client 2 then sends a '4. Floor taken' message. Finally, another 'Periodic group call announcement' is shown. + +**Figure 10.6.3.4-1: Passive join to group call** + +1. MCPTT client 2 sends the group call announcement message. This message contains parameters such as MCPTT group ID, group call originator identity, media type, media codec, multicast port number for media, port number for floor control protocol, any encryption key for the media encryption if needed, and optionally confirm mode indication. + +NOTE 1: The group call announcement includes at least one common set of parameters and values for media transfer. Additional values per parameter will not be prohibited for the better user experience. + +2. MCPTT client 4 configures the parameters for media transfer by making use of the received parameters in group call announcement. +3. MCPTT client 4 may send the response message to the group when the periodic group call announcement includes confirm mode indication. This message contains the MCPTT ID. +4. MCPTT client 1, 2, 3 check through the received response message that the MCPTT client 4 joins the group call. The MCPTT client 2, as the floor control arbitrator, may send a floor taken message. + +NOTE 2: Due to the movement of the participants (in and out of the radio coverage) during the off-network group call, the group call announcement message including parameters for media delivery is periodically sent. + +NOTE 3: The participating MCPTT clients do not need to respond to the periodic group call announcement. + +#### 10.6.3.5 Join to ongoing group call when new entry member initiates the call with on-going group call id + +Figure 10.6.3.5-1 illustrates the control plane procedures for an MCPTT client to join an on-going MCPTT group call. When entering the coverage of on-going group call, new MCPTT client may send group call setup announcement message with on-going group call id. Upon receiving the group call setup announcement, the MCPTT client as a + +participant of on-going MCPTT group call sends parameters for media transfer to the newly entered MCPTT client (entrant) to join the on-going MCPTT group call. When receiving the parameters for media transfer of on-going MCPTT group call, the MCPTT client configures the parameters to receive the voice and becomes the participant of the on-going MCPTT group call. + +![Sequence diagram showing the interaction between four MCPTT clients (1, 2, 3, 4) for a late entry join. Clients 1, 2, and 3 are already in an 'On-going group call'. Client 4 sends an 'Entry' message. Client 4 then sends a 'Group call setup announcement' to clients 1, 2, and 3. Client 1 responds with 'Announcement of On-going call media parameters'. Client 4 replies with 'OK'. Finally, Client 4 sends 'Setting parameters' and joins the 'On-going group call'.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT client 3 + participant MCPTT client 4 + Note over MCPTT client 1, MCPTT client 3: On-going group call + Note right of MCPTT client 4: 1. Entry + Note right of MCPTT client 4: 2. Group call setup announcement + Note right of MCPTT client 1: 3. Announcement of On-going call media parameters + Note right of MCPTT client 4: 4. OK + Note right of MCPTT client 4: 5. Setting parameters + Note over MCPTT client 1, MCPTT client 3: On-going group call + +``` + +Sequence diagram showing the interaction between four MCPTT clients (1, 2, 3, 4) for a late entry join. Clients 1, 2, and 3 are already in an 'On-going group call'. Client 4 sends an 'Entry' message. Client 4 then sends a 'Group call setup announcement' to clients 1, 2, and 3. Client 1 responds with 'Announcement of On-going call media parameters'. Client 4 replies with 'OK'. Finally, Client 4 sends 'Setting parameters' and joins the 'On-going group call'. + +**Figure 10.6.3.5-1: Late entry join when receiving MCPTT group call announcement with on-going MCPTT group ID** + +1. MCPTT client 4 enters the coverage of the on-going MCPTT group call. +2. The new entry of MCPTT client 4 sends group call setup announcement with MCPTT group call id. +3. MCPTT client 1 as a participant of on-going MCPTT group call acknowledges that on-going MCPTT group call exists with MCPTT group call id sent by MCPTT client 4 and sends parameters for media transfer to MCPTT client 4. +4. MCPTT client 4 may send a response message. +5. MCPTT client 4 sets the parameters for media delivery in the on-going MCPTT group call. + +MCPTT client 4 joins and becomes participants of the on-going MCPTT group call. + +#### 10.6.3.6 Immediate group call announcement to join an ongoing group call + +Figure 10.6.3.6-1 illustrates the control plane procedures for an MCPTT client to immediately join an on-going MCPTT group call. Upon the detection of a new entrant, the MCPTT client that is the current talker (floor arbitrator) immediately sends the group call announcement. When receiving the group call announcement message with parameters for media transfer, that MCPTT client configures the parameters to receive the voice and joins the on-going MCPTT group call. + +Pre-conditions: + +1. There is on-going group call. MCPTT client 1 is the current talker and therefore the floor arbitrator. + +![Sequence diagram illustrating the immediate group call announcement to join an ongoing group call. The diagram shows four lifelines: MCPTT client 1, MCPTT client 2, MCPTT client 3, and MCPTT client 4. The sequence of events is: 1. Entry (MCPTT client 4), 2. New entrant is detected (MCPTT client 1), 3. Group call announcement (MCPTT client 1 to MCPTT client 4), 4. OK (MCPTT client 4 to MCPTT client 1), 5. Setting parameters (MCPTT client 4), and 6. On-going group call (MCPTT client 1 is current talker – floor arbitrator).](7f17c430b9598e4d748a8041457810b3_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT client 3 + participant MCPTT client 4 + Note right of MCPTT client 4: 1. Entry + Note over MCPTT client 1, MCPTT client 3: 2. New entrant is detected + MCPTT client 1->>MCPTT client 4: 3. Group call announcement + MCPTT client 4-->>MCPTT client 1: 4. OK + Note right of MCPTT client 4: 5. Setting parameters + Note over MCPTT client 1, MCPTT client 3: 6. On-going group call (MCPTT client 1 is current talker – floor arbitrator) +``` + +Sequence diagram illustrating the immediate group call announcement to join an ongoing group call. The diagram shows four lifelines: MCPTT client 1, MCPTT client 2, MCPTT client 3, and MCPTT client 4. The sequence of events is: 1. Entry (MCPTT client 4), 2. New entrant is detected (MCPTT client 1), 3. Group call announcement (MCPTT client 1 to MCPTT client 4), 4. OK (MCPTT client 4 to MCPTT client 1), 5. Setting parameters (MCPTT client 4), and 6. On-going group call (MCPTT client 1 is current talker – floor arbitrator). + +**Figure 10.6.3.6-1: Immediate group call announcement to join an ongoing group call** + +1. MCPTT client 4 enters the coverage of the on-going MCPTT group call. +2. The entry of MCPTT client 4 is detected by the current participants. +3. Since MCPTT client 1 is the current talker (floor arbitrator), MCPTT client 1 immediately sends the group call announcement with the call parameters to the group. +4. MCPTT client 4 may send a response message. +5. MCPTT client 4 sets the parameters for the group call. +6. All participants are now considered part of the on-going group call. + +#### 10.6.3.7 Group call release due to inactivity + +If the on-going MCPTT group call is inactive for a specific duration, the participating MCPTT clients release the MCPTT group call by themselves. + +NOTE: Inactivity time can be set according to the policy of MCPTT service provider. + +#### 10.6.3.8 Broadcast group call + +Group call on group-broadcast group and user-broadcast group are handled without distinction in off-network. + +Figure 10.6.3.8.1-1 illustrates the control plane procedures for broadcast group call in off-network. + +![Sequence diagram illustrating a broadcast group call in off-network. Three MCPTT clients (1, 2, and 3) are shown. Client 1 (Call Originator) initiates the process. The sequence consists of three main steps: 1. Group call setup, 2. Media transmission (indicated by a large blue arrow from Client 1 to Client 3), and 3. Group call release.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 (Call Originator) + participant MCPTT client 2 + participant MCPTT client 3 + Note over MCPTT client 1, MCPTT client 3: 1. Group call setup + Note over MCPTT client 1, MCPTT client 3: 2. Media transmission + Note over MCPTT client 1, MCPTT client 3: 3. Group call release + +``` + +Sequence diagram illustrating a broadcast group call in off-network. Three MCPTT clients (1, 2, and 3) are shown. Client 1 (Call Originator) initiates the process. The sequence consists of three main steps: 1. Group call setup, 2. Media transmission (indicated by a large blue arrow from Client 1 to Client 3), and 3. Group call release. + +**Figure 10.6.3.8.1-1: Broadcast group call in off-network** + +1. An authorized MCPTT client 1 initiates broadcast group call setup as described in subclause 10.6.3.3. The group call announcement message includes the indication of broadcast group call. + 2. The MCPTT client 1 initiating broadcast group call starts to transmit media. +- NOTE: Other clients of group member are not allowed to transmit media in broadcast group call. +3. The broadcast group call is released as described in subclause 10.6.3.7. + +#### 10.6.3.9 Emergency and imminent peril procedures + +##### 10.6.3.9.1 Emergency group call + +The off-network emergency group call is a special case of off-network (non-emergency) group call as defined in subclauses 10.6.3.2, 10.6.3.3, 10.6.3.4, 10.6.3.5, 10.6.3.6 and 10.6.3.7. The following are modifications to the aforementioned subclauses to support MCPTT emergency group calls: + +- As a pre-condition, the client initiating the emergency call has previously been provisioned with an MCPTT group designated as the MCPTT emergency group. The MCPTT client initiates MCPTT emergency group calls on this group. Alternatively, the MCPTT client could have been provisioned for emergency behaviour on the selected MCPTT group. +- The group call announcement contains an indication that the MCPTT group call is to be an MCPTT emergency call regardless of whether or not the MCPTT client is in call. Group call participants learn of the MCPTT group's in-progress emergency state from the indication. +- Every call initiated by the MCPTT client will be an emergency call while the MCPTT client is in MCPTT emergency state. +- The MCPTT client enters the MCPTT emergency state when initiating an MCPTT emergency call or MCPTT emergency alert. Only the MCPTT user of the MCPTT client can clear the client's local MCPTT emergency state. +- The MCPTT group in-progress emergency state is cancelled when the call ends. +- The MCPTT user who initiated an emergency call, or upgraded a group call to an emergency call, or an authorized user, may cancel the in-progress emergency state with an MCPTT emergency group state cancel message. The message is sent to the call participants. +- When the MCPTT group is no longer in the in-progress emergency state, every client returns its default value of ProSe Per Packet Priority. + +- An MCPTT group call in-progress is upgraded to an emergency group call when the periodic group call announcement contains the emergency indicator. +- The value of ProSe Per Packet Priority is upgraded according to emergency state of MCPTT group call. +- An MCPTT group call becoming an emergency group call does not affect the state of other MCPTT call(s) in the client. +- The MCPTT group remains in the in-progress emergency state until the emergency group call ends or the in-progress emergency state is cancelled. + +##### 10.6.3.9.2 MCPTT imminent peril + +The off-network imminent peril group call is a special case of off-network (non-imminent peril) group call as defined in subclauses 10.6.3.2, 10.6.3.3, 10.6.3.4, 10.6.3.5, 10.6.3.6 and 10.6.3.7. The following are modifications to the aforementioned subclauses to support MCPTT imminent peril calls: + +- As a pre-condition, the user initiating the imminent peril call has previously an MCPTT group to be used as the MCPTT imminent peril group. The MCPTT client initiates MCPTT imminent peril group calls on this group. +- The group call announcement contains an indication that the MCPTT group call is to be an MCPTT imminent peril call. Group call participants learn of the MCPTT group in-progress imminent peril condition from the indication. +- The MCPTT group in-progress imminent peril state is considered cancelled when the call ends. +- The originating MCPTT user of the in-progress imminent peril or an authorized user may cancel the in-progress imminent peril state with an MCPTT imminent peril group cancel. The message is sent to the call participants. +- When the MCPTT in-progress imminent peril is no longer in the in-progress imminent peril state, every MCPTT client returns its bearer to the priority it had prior to the in-progress imminent peril state. +- An MCPTT upgrade to imminent peril call is used to upgrade an MCPTT group call already in progress. The message is sent to all call participants so that they are aware of the in-progress imminent peril. +- The bearer is upgraded by all participants for the MCPTT group call already in progress when the MCPTT group call is upgraded to in-progress imminent peril state. +- An MCPTT imminent peril call puts the MCPTT group into the in-progress imminent peril state. + +##### 10.6.3.9.3 MCPTT emergency alert + +**Editor's note: whether the following procedures for emergency alert initiation and emergency alert cancel remain in this specification is FFS.** + +###### 10.6.3.9.3.1 MCPTT emergency alert initiation + +An MCPTT client initiates an MCPTT emergency alert to the members of an MCPTT group. This procedure will place the MCPTT client in the MCPTT emergency state if the MCPTT client is not already in that state. + +Procedures in figure 10.6.3.9.3.1-1 are the signalling control plane procedures for the MCPTT client initiating an MCPTT emergency alert with an MCPTT group i.e., MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 belong to the same MCPTT group. + +Pre-conditions: + +1. The pre-conditions for off-network group calls as described in subclause 10.6.3.3 apply. +2. The initiating MCPTT client 1 has been provisioned with an MCPTT group designated as the MCPTT emergency group. + +NOTE 1: Alternatively, MCPTT client 1 could have been provisioned for emergency behaviour on the currently selected group. + +3. MCPTT clients 2 and 3 belong to and are ready for off-network communications on the MCPTT group. + +![Sequence diagram for MCPTT emergency alert. Lifelines: MCPTT client 1 (Call Originator), MCPTT client 2, and MCPTT client 3. The sequence starts with '1. User initiates MCPTT emergency alert' on client 1. Client 1 sends '2. MCPTT Emergency alert announcement' to clients 2 and 3. Clients 2 and 3 each perform '3. Notify MCPTT emergency alert'. Both clients 2 and 3 send '4. Response' back to client 1. Finally, client 1 performs '5. checking participants'.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MCPTT client 1 (Call Originator) + participant Client2 as MCPTT client 2 + participant Client3 as MCPTT client 3 + Note left of Client1: 1. User initiates MCPTT emergency alert + Client1->>Client2: 2. MCPTT Emergency alert announcement + Client1->>Client3: 2. MCPTT Emergency alert announcement + Note right of Client2: 3. Notify MCPTT emergency alert + Note right of Client3: 3. Notify MCPTT emergency alert + Client2->>Client1: 4. Response + Client3->>Client1: 4. Response + Note left of Client1: 5. checking participants + +``` + +Sequence diagram for MCPTT emergency alert. Lifelines: MCPTT client 1 (Call Originator), MCPTT client 2, and MCPTT client 3. The sequence starts with '1. User initiates MCPTT emergency alert' on client 1. Client 1 sends '2. MCPTT Emergency alert announcement' to clients 2 and 3. Clients 2 and 3 each perform '3. Notify MCPTT emergency alert'. Both clients 2 and 3 send '4. Response' back to client 1. Finally, client 1 performs '5. checking participants'. + +**Figure 10.6.3.9.3.1-1: MCPTT emergency alert** + +1. The user at the MCPTT client 1 initiates an MCPTT emergency alert by sending an MCPTT emergency alert announcement to the other clients. MCPTT client 1 sets its MCPTT emergency state. The MCPTT emergency state is retained by the MCPTT client until explicitly cancelled. Once MCPTT client1 is in the MCPTT emergency state, any calls initiated by MCPTT client 1, group or private, shall be initiated as emergency calls and receive priority treatment. + +2. MCPTT client 1 sends an MCPTT emergency alert announcement to the other participants on the MCPTT emergency group. The MCPTT emergency alert announcement is sent periodically so that late joining MCPTT group members are notified. + +NOTE 2: Sending the emergency alert without making a request to also start an MCPTT emergency call does not put the group into the in-progress emergency state. + +3. MCPTT users are notified of the MCPTT emergency state of the originating MCPTT user. + +4. The receiving MCPTT clients acknowledge the MCPTT emergency alert to the originating MCPTT client. + +NOTE 3: Sending the emergency alert without making a request to also start an emergency call does not put the group into the in-progress emergency state. + +NOTE 4: The MCPTT client 1 needs not initiate a group call. For example, the MCPTT client can be configured to only allow alerts or the MCPTT user can choose not to make an MCPTT emergency group call. + +NOTE 5: MCPTT clients receiving subsequent MCPTT emergency alert announcements that are sent periodically need only respond to the first one that they receive. + +NOTE 6: It is configured if MCPTT client 1 will automatically trigger a subsequent MCPTT emergency group call. + +5. The originating MCPTT client 1 checks the responses and may inform the MCPTT user of the MCPTT group members whose MCPTT clients responded. + +###### 10.6.3.9.3.2 MCPTT emergency alert cancel + +An MCPTT client has initiated an MCPTT emergency alert, has entered the MCPTT emergency state and wishes to cancel the alert, informing the other MCPTT group members of the cancellation. As part of this process, the MCPTT client may also request the cancellation of the in-progress emergency state of the group if authorized to do so. + +Procedures in figure 10.6.3.9.3.2-1 are the signalling control plane procedures for the MCPTT client cancelling an MCPTT emergency alert with an MCPTT group i.e., MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 belong to the same MCPTT group. + +Pre-conditions: + +1. The pre-conditions for off-network group calls as described in subclause 10.6.3.3 apply. +2. The MCPTT client 1 had previously successfully initiated an MCPTT emergency alert. +3. The MCPTT client 1 is still in the MCPTT emergency state. +4. The initiating MCPTT client 1 and MCPTT clients 2 and 3 are still in off-network contact via the MCPTT group designated provisioned to MCPTT client 1 as the MCPTT emergency group. + +![Sequence diagram for MCPTT emergency alert cancel](b90144cfbb81a2d610d920240fda689d_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCPTT client 1 +(Call Originator) + participant C2 as MCPTT client 2 + participant C3 as MCPTT client 3 + + Note over C1: 1. User initiates +MCPTT emergency +alert cancel + C1->>C2: 2. MCPTT Emergency alert cancel announcement + C1->>C3: 2. MCPTT Emergency alert cancel announcement + Note over C2: 3. Notify MCPTT +emergency alert +cancel + Note over C3: 3. Notify MCPTT +emergency alert +cancel + C2->>C1: 4. Response + C3->>C1: 4. Response + +``` + +The diagram illustrates the signaling control plane procedures for an MCPTT emergency alert cancel. It features three lifelines: MCPTT client 1 (Call Originator), MCPTT client 2, and MCPTT client 3. The sequence of messages is as follows: 1. A local action on MCPTT client 1 where the user initiates the cancel. 2. MCPTT client 1 sends an announcement to both MCPTT client 2 and MCPTT client 3. 3. MCPTT client 2 and MCPTT client 3 each notify their respective MCPTT users. 4. Both MCPTT client 2 and MCPTT client 3 send a response back to MCPTT client 1. + +Sequence diagram for MCPTT emergency alert cancel + +**Figure 10.6.3.9.3.2-1 MCPTT emergency alert cancel** + +1. The user at the MCPTT client 1 initiates an MCPTT emergency alert cancel. +2. MCPTT client 1 sends an MCPTT emergency alert cancel announcement to the MCPTT group to which MCPTT client 1 had previously sent the emergency alert. +3. MCPTT users are notified of the MCPTT emergency alert cancellation by MCPTT client 1. +4. The receiving MCPTT clients acknowledge the MCPTT emergency alert cancel to the originating MCPTT client. + +**NOTE:** MCPTT clients that track the MCPTT emergency alerts of other MCPTT users, e.g. consoles that fail to receive subsequent periodic MCPTT emergency alert announcements after a configured timeout can consider the alert to be cancelled. + +## 10.7 Private call + +### 10.7.1 General + +Private calls are enabled in both on-network and off-network. + +Private calls can be setup in two different commencement modes, automatic commencement mode and manual commencement mode. + +Private calls in on-network can be with or without floor control. Private calls in off-network are with floor control. + +### 10.7.2 Private call in on-network + +#### 10.7.2.1 Information flows for private call in on-network + +##### 10.7.2.1.1 MCPTT private call request (MCPTT client to MCPTT server) + +Table 10.7.2.1.1-1 describes the information flow MCPTT private call request from the MCPTT client to the MCPTT server. + +**Table 10.7.2.1.1-1: MCPTT private call request (MCPTT client to MCPTT server) information elements** + +| Information Element | Status | Description | +|------------------------------|--------|-----------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Use floor control indication | M | This element indicates whether floor control will be used for the private call. | +| SDP offer | O | Media parameters of MCPTT client. | +| Requested commencement mode | O | An indication that is included if the user is requesting a particular commencement mode | +| Implicit floor request | O | An indication that the user is also requesting the floor. | +| Location information | O | Location of the calling party | +| Requested priority | O | Application priority level requested for this call | + +##### 10.7.2.1.2 MCPTT private call request (MCPTT server to MCPTT server) + +Table 10.7.2.1.2-1 describes the information flow MCPTT private call request from the MCPTT server to the MCPTT server. + +**Table 10.7.2.1.2-1: MCPTT private call request (MCPTT server to MCPTT server) information elements** + +| Information Element | Status | Description | +|------------------------------|--------|---------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Use floor control indication | M | This element indicates whether floor control will be used for the private call. | +| SDP offer | M | Media parameters of MCPTT client. | +| Requested commencement mode | O | An indication of the commencement mode to be used. | +| Implicit floor request | O | An indication that the user is also requesting the floor. | +| Location information | O | Location of the calling party | + +##### 10.7.2.1.2a MCPTT private call request (MCPTT server to MCPTT client) + +Table 10.7.2.1.2a describes the information flow MCPTT private call request from the MCPTT server to the MCPTT client. + +**Table 10.7.2.1.2a: MCPTT private call request (MCPTT server to MCPTT client) information elements** + +| Information Element | Status | Description | +|------------------------------|--------|---------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Use floor control indication | M | This element indicates whether floor control will be used for the private call. | +| SDP offer | M | Media parameters of MCPTT client. | +| Requested commencement mode | O | An indication of the commencement mode to be used. | +| Implicit floor request | O | An indication that the user is also requesting the floor. | + +##### 10.7.2.1.3 MCPTT private call response (MCPTT client to MCPTT server) + +Table 10.7.2.1.3-1 describes the information flow MCPTT private call response from the MCPTT client to the MCPTT server. + +**Table 10.7.2.1.3-1: MCPTT private call response (MCPTT client to MCPTT server) information elements** + +| Information Element | Status | Description | +|-----------------------------|--------|----------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | O | The MCPTT ID of the called party | +| SDP answer | M | Media parameters selected | +| Requested commencement mode | O | An indication of the commencement mode to be used. | + +##### 10.7.2.1.4 MCPTT private call response + +Table 10.7.2.1.4-1 describes the information flow MCPTT private call response from the MCPTT server to the MCPTT client. + +**Table 10.7.2.1.4-1: MCPTT private call response information elements** + +| Information Element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | O | The MCPTT ID of the called party | +| Acceptance confirmation | O | An indication whether the user has positively accepted the call. | +| SDP answer | M | Media parameters selected | + +###### 10.7.2.1.4a MCPTT private call end request + +Table 10.7.2.1.4a-1 describes the information flow MCPTT private call end request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.7.2.1.4a-1: MCPTT private call end request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | + +###### 10.7.2.1.4b MCPTT private call end response + +Table 10.7.2.1.4b-1 describes the information flow MCPTT private call end response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.7.2.1.4b-1: MCPTT private call end response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | In the direction MCPTT client to MCPTT server this shall be the MCPTT ID of the responding MCPTT client. In the direction MCPTT server to MCPTT client this shall be the MCPTT ID of the destination MCPTT client | + +##### 10.7.2.1.5 MCPTT emergency private call request (MCPTT client to MCPTT server) + +Table 10.7.2.1.5-1 describes the information flow MCPTT emergency private call request from the MCPTT client to the MCPTT server. + +**Table 10.7.2.1.5-1: MCPTT emergency private call request (MCPTT client to MCPTT server) information elements** + +| Information Element | Status | Description | +|-----------------------------|--------|--------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Emergency indicator | M | Indicates that the private call request is an MCPTT emergency call | +| Alert indicator | M | Indicates whether an emergency alert is to be sent | +| Requested commencement mode | O | An indication of the commencement mode to be used. | +| Implicit floor request | O | An indication that the user is also requesting the floor. | +| SDP offer | M | Media parameters of MCPTT client. | +| Location information | O | Location of the calling party | + +###### 10.7.2.1.5a MCPTT emergency private call request (MCPTT server to MCPTT client) + +Table 10.7.2.1.5a-1 describes the information flow MCPTT emergency private call request from the MCPTT server to the MCPTT client. + +**Table 10.7.2.1.5a-1: MCPTT emergency private call request (MCPTT server to MCPTT client) information elements** + +| Information Element | Status | Description | +|-----------------------------|--------|--------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Emergency indicator | M | Indicates that the private call request is an MCPTT emergency call | +| Alert indicator | M | Indicates whether an emergency alert is to be sent | +| Requested commencement mode | O | An indication of the commencement mode to be used. | +| Implicit floor request | O | An indication that the user is also requesting the floor. | +| SDP offer | M | Media parameters of MCPTT client. | + +##### 10.7.2.1.6 MCPTT progress indication + +Table 10.7.2.1.6-1 describes the information flow MCPTT progress indication from the MCPTT server to the MCPTT client. + +**Table 10.7.2.1.6-1: MCPTT progress indication information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Progress indication | O | Indication to the caller. | + +##### 10.7.2.1.7 MCPTT ringing + +Table 10.7.2.1.7-1 describes the information flow MCPTT ringing from the MCPTT client to the MCPTT server, from the MCPTT server to the MCPTT client, and from the MCPTT server to the MCPTT client. + +**Table 10.7.2.1.7-1: MCPTT ringing information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Ringing indication | O | Indication to the caller. | + +#### 10.7.2.2 Private call within one MCPTT system + +##### 10.7.2.2.1 Private call setup in automatic commencement mode + +The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call for communicating with another MCPTT user, with or without floor control enabled, in an automatic commencement mode. + +Procedures in figure 10.7.2.2.1-1 are the basic signalling control plane procedures for the MCPTT client initiating establishment of MCPTT private call with the chosen MCPTT user. + +Pre-conditions: + +1. The calling MCPTT user has selected automatic commencement mode for the call; or +2. The called MCPTT client is set to automatic commencement mode. +3. Optionally, MCPTT client 1 may use an activated functional alias for the call. +4. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram illustrating the private call setup in automatic commencement mode for MCPTT users in the same MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT server, and MCPTT client 2 under the 'Home MCPTT service provider'.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note over MCPTT client 1, MCPTT client 2: Home MCPTT service provider + Note right of MCPTT client 1: 2. initiate private call + MCPTT client 1->>MCPTT server: 3. MCPTT private call request + MCPTT server->>MCPTT client 1: 4. Authorize request + MCPTT server-->>MCPTT client 1: 5. MCPTT progress indication + MCPTT server->>MCPTT client 2: 6. MCPTT private call request + MCPTT client 2->>MCPTT server: 7. Notify call + MCPTT client 2-->>MCPTT server: 8. MCPTT private call response + MCPTT server-->>MCPTT client 1: 9. MCPTT private call response + Note over MCPTT client 1, MCPTT client 2: 10. Media plane established + +``` + +Sequence diagram illustrating the private call setup in automatic commencement mode for MCPTT users in the same MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT server, and MCPTT client 2 under the 'Home MCPTT service provider'. + +**Figure 10.7.2.2.1-1: Private call setup in automatic commencement mode– MCPTT users in the same MCPTT system** + +1. MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service, as per procedure in subclause 10.2. +2. User at MCPTT client 1 would like to initiate an MCPTT private call for the chosen MCPTT user. The MCPTT user at MCPTT client 1 may include a functional alias used within the MCPTT private call. For a private call with floor control, floor control is to be established. +3. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server (via SIP core) using a service identifier as defined in 3GPP TS 23.228 [5] for MCPTT, for establishing a private call with the chosen MCPTT user. The MCPTT private call request contains the MCPTT ID of invited user, an SDP offer containing one or more media types. For a private call with floor control, the MCPTT private call request also contains an element that indicates that MCPTT client 1 is requesting the floor. The MCPTT client 1 may include a Requested commencement mode that indicates that the call is to be established in automatic commencement mode if automatic commencement mode is requested by the initiating user. +4. MCPTT server checks whether the MCPTT user at MCPTT client 1 is authorized to initiate the private call, and that MCPTT user at MCPTT client 2 is authorized to receive the private call. MCPTT server verifies whether the provided functional alias, if present, can be used and has been activated for the user. If the MCPTT private call request requested automatic commencement mode then the MCPTT server also checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a private call in automatic commencement mode. +5. MCPTT server may provide a progress indication to MCPTT client 1 to indicate progress in the call setup process. + +NOTE: Step 5 can occur at any time following step 4, and prior to step 9. + +6. If authorized, MCPTT server includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request, includes the requested automatic commencement mode indication based on a requested automatic commencement mode by the calling user or based upon the setting of the called MCPTT client and sends the corresponding MCPTT private call request towards the MCPTT client 2, including the MCPTT ID and, if available, the functional alias of the calling MCPTT user 1. If the called MCPTT user has registered to the MCPTT service with multiple MCPTT UEs and has designated the MCPTT UE for receiving the private calls, then the incoming MCPTT private call request is delivered only to the designated MCPTT UE. +7. The receiving MCPTT client 2 notifies the user about the incoming private call and displays the functional alias of calling MCPTT user 1. + +8. The receiving MCPTT client 2 accepts the private call automatically, and an MCPTT private call response is sent to the MCPTT server (via SIP core). +9. Upon receiving the MCPTT private call response from MCPTT client 2 accepting the private call request, the MCPTT server informs the MCPTT client 1 about successful call establishment. +10. MCPTT client 1 and MCPTT client 2 have successfully established media plane for communication and either user can transmit media. For successful call establishment for private call with floor control request from MCPTT client 1, floor participant at MCPTT client 1 is granted floor by the floor control server, giving it permission to transmit. At the same time floor participant at MCPTT client 2 is informed by the floor control server that floor is taken. + +##### 10.7.2.2.2 Private call setup in manual commencement mode + +###### 10.7.2.2.2.1 Description + +Figure 10.7.2.2.2.2-1 describes the basic procedure for the MCPTT client initiating an MCPTT private call that uses manual commencement mode. The flow may use a floor request in the MCPTT private call request indicating that the originator will be given the floor when the call starts and eliminates the need for a separate initial floor request message during media plane establishment. Alternatively the call initiation may be sent without the floor request, which allows the called party to request the floor first. + +###### 10.7.2.2.2.2 Procedure + +Both clients are served by the primary MCPTT service provider in figure 10.7.2.2.2.2-1. + +Pre-conditions: + +1. The calling MCPTT user has selected manual commencement mode or has not specified a commencement mode for the call; and +2. The called MCPTT client is set to manual commencement mode. +3. Optionally, MCPTT client 1 may use an activated functional alias for the call. +4. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram of MCPTT private call in manual commencement mode. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2. The process starts with registration and authentication, followed by a private call request from client 1 to the server, which then verifies authorization and forwards the request to client 2. Client 2 rings, and the server rings client 1. Both clients send responses, and finally, the media plane is established.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + + Note over MCPTT client 1, MCPTT client 2: 1. MCPTT client 1 and MCPTT client 2 are both registered, their respective users are authenticated and authorized for the MCPTT Service + Note left of MCPTT client 1: 2. Initiate private call + MCPTT client 1->>MCPTT server: 3. MCPTT private call request + Note right of MCPTT server: 4. MCPTT server verifies that MCPTT client 1 and MCPTT client 2 are authorized to participate in the call + MCPTT server->>MCPTT client 2: 5. MCPTT private call request + MCPTT server-->>MCPTT client 1: 6. MCPTT progress indication + MCPTT server->>MCPTT client 2: 7a. MCPTT ringing + MCPTT client 2-->>MCPTT server: 8. MCPTT private call response + MCPTT server->>MCPTT client 1: 7b. MCPTT ringing + MCPTT client 1-->>MCPTT server: 9. MCPTT private call response + Note over MCPTT client 1, MCPTT client 2: 10. Media plane established + +``` + +Sequence diagram of MCPTT private call in manual commencement mode. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2. The process starts with registration and authentication, followed by a private call request from client 1 to the server, which then verifies authorization and forwards the request to client 2. Client 2 rings, and the server rings client 1. Both clients send responses, and finally, the media plane is established. + +**Figure 10.7.2.2.2.2-1: MCPTT private call in manual commencement mode– MCPTT users in the same MCPTT system** + +1. MCPTT client 1 and MCPTT client 2 are both registered and their respective users, MCPTT user 1 and MCPTT user 2, are authenticated and authorized to use the MCPTT service, as per procedure in subclause 10.2. +2. MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call for the selected MCPTT user. The MCPTT user at MCPTT client 1 may include a functional alias used within the MCPTT private call. For a private call with floor control, floor control is to be established. For private call without floor control, both users will have the ability to transmit without floor arbitration. +3. MCPTT client 1 sends an MCPTT private call request addressed to the MCPTT ID of MCPTT user 2 using an MCPTT service identifier as defined in 3GPP TS 23.228 [5] (possible for the SIP core to route the request to the MCPTT server). The MCPTT private call request contains the MCPTT ID of invited user and an SDP offer containing one or more media types. The MCPTT private call request may also contain a data element that indicates that MCPTT client 1 is requesting the floor, for a private call with floor control. The MCPTT client 1 may include a requested commencement mode that indicates that the call is to be established in manual commencement mode if manual commencement mode is requested by the initiating user. +4. The MCPTT server confirms that both MCPTT users are authorized for the private call. MCPTT server verifies whether the provided functional alias, if present, can be used and has been activated for the user. The MCPTT server checks the commencement mode setting of the called MCPTT client and also checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a call in manual commencement mode. +5. The MCPTT server includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request and sends an MCPTT private call request for the call to MCPTT client 2, including the MCPTT ID and, if available, the functional alias of the calling MCPTT user 1. If the called MCPTT user has registered to the MCPTT service with multiple MCPTT + +UEs and has designated the MCPTT UE for receiving the private calls, then the incoming MCPTT private call request is delivered only to the designated MCPTT UE. + +6. MCPTT server may provide a progress indication to MCPTT client 1 to indicate progress in the call setup process. + +NOTE: Step 6 can occur at any time following step 4, and prior to step 7b. + +- 7a. The MCPTT user is alerted and may display the functional alias of calling MCPTT user 1. MCPTT client 2 sends an MCPTT ringing to the MCPTT server. +- 7b. The MCPTT server sends an MCPTT ringing to MCPTT client 1, indicating that MCPTT client 2 is being alerted. +8. MCPTT user 2 has accepted the call using manual commencement mode (i.e., has taken some action to accept via the user interface) which causes MCPTT client 2 to send an MCPTT private call response to the MCPTT server. If MCPTT user 2 has not accepted the incoming call, the MCPTT client 2 sends a call failure response to the MCPTT server without adding reason for call failure. +9. The MCPTT server sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT user 2 has accepted the call, including the accepted media parameters. +10. The media plane for communication is established. Either user can transmit media individually when using floor control. For successful call establishment for private call with floor request from MCPTT client 1, the floor participant associated with MCPTT client 1 is granted the floor initially. At the same time the floor participant associated with MCPTT client 2 is informed that the floor is taken. The meaning of the floor request (give floor initially to originator [client 1], or give floor initially to target [client 2]) may be configurable. For a private call without floor control both users are allowed to transmit simultaneously. + +##### 10.7.2.2.3 Private call release + +###### 10.7.2.2.3.1 Client initiated + +The procedure focuses on the case where an MCPTT client is requesting to release an ongoing MCPTT private call (with or without floor control) and the call established in either of the two commencement modes (manual or automatic). + +Procedures in figure 10.7.2.2.3.1-1 are the basic signalling control plane procedures for the MCPTT client initiating the release of an ongoing MCPTT private call. + +![Sequence diagram for Private call release – client initiated. The diagram shows the interaction between MCPTT client 1, MCPTT server, and MCPTT client 2 under the 'Home MCPTT service provider'. The sequence starts with a note that both clients are registered and an ongoing private call exists. Client 1 sends a 'Release private call' request to the server. The server then sends an 'MCPTT private call end request' to Client 2. Client 2 sends a 'Notify call termination' response. The server then sends an 'MCPTT private call end response' back to Client 1. Finally, a note indicates that media plane resources are released.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCPTT client 1 + participant S as MCPTT server + participant C2 as MCPTT client 2 + Note over C1, C2: 1. MCPTT client 1 and MCPTT client 2 are registered for MCPTT service and private call is ongoing between them + Note left of C1: 2. Release private call + C1->>S: 3. MCPTT private call end request + S->>C2: 4. MCPTT private call end request + Note right of C2: 5. Notify call termination + C2->>S: 6. MCPTT private call end response + S->>C1: 7. MCPTT private call end response + Note over C1, C2: 8. Media plane resources released + +``` + +Sequence diagram for Private call release – client initiated. The diagram shows the interaction between MCPTT client 1, MCPTT server, and MCPTT client 2 under the 'Home MCPTT service provider'. The sequence starts with a note that both clients are registered and an ongoing private call exists. Client 1 sends a 'Release private call' request to the server. The server then sends an 'MCPTT private call end request' to Client 2. Client 2 sends a 'Notify call termination' response. The server then sends an 'MCPTT private call end response' back to Client 1. Finally, a note indicates that media plane resources are released. + +**Figure 10.7.2.2.3.1-1: Private call release – client initiated** + +1. It is assumed that MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service and are involved in private call with or without floor control established either in manual or automatic commencement mode, as described in subclause 10.7.2.2.1 and subclause 10.7.2.2.2. +2. User at MCPTT client 1 would like to release an ongoing MCPTT private call with MCPTT client 2. +3. MCPTT client 1 sends an MCPTT private call end request towards the MCPTT server (via SIP core), for tearing down the private call with the other client. +4. MCPTT server sends the corresponding MCPTT private call end request towards the MCPTT client specified in the original MCPTT private call end request. +5. MCPTT user is notified about the release of the private call. +6. The receiving MCPTT client 2 acknowledges the MCPTT private call end request with an MCPTT private call end response. +7. After receiving the MCPTT private call end response from MCPTT client 2, the MCPTT server generates an acknowledgement for the MCPTT client 1's MCPTT private call end request. +8. MCPTT clients release all the media plane resources used for the private call. Further, if the private call was established with floor control, floor control resources are released and MCPTT clients cannot make further requests for floor control or send media. + +###### 10.7.2.2.3.2 Server initiated + +The procedure focuses on the case where an MCPTT server is terminating an ongoing MCPTT private call (with or without floor control) and the call established in either of the two commencement modes (manual or automatic), upon conditions to terminate call e.g., MCPTT administrator configured maximum duration for MCPTT private calls has expired or timed out due to MCPTT private call without transmission/reception. + +Procedures in figure 10.7.2.2.3.2-1 are the basic signalling control plane procedures for the MCPTT server initiating termination of an ongoing MCPTT private call. + +![Sequence diagram titled 'Home MCPTT service provider' showing the 'End private call – server initiated' procedure. The diagram involves three lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2. The sequence of messages is: 1. Client 1 and client 2 are registered for MCPTT service and private call is ongoing between them. 2. Conditions to trigger terminate private call. 3. MCPTT server sends MCPTT private call end request to both clients. 4. Clients notify call termination. 5. Clients send MCPTT private call end response to the server. 6. Media plane resources are released.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MCPTT client 1 + participant Server as MCPTT server + participant Client2 as MCPTT client 2 + Note over Client1, Client2: 1. Client 1 and client 2 are registered for MCPTT service and private call is ongoing between them + Note over Server: 2. Conditions to trigger terminate private call + Server->>Client1: 3. MCPTT private call end request + Server->>Client2: 3. MCPTT private call end request + Client1->>Client1: 4. Notify call termination + Client2->>Client2: 4. Notify call termination + Client1->>Server: 5. MCPTT private call end response + Client2->>Server: 5. MCPTT private call end response + Note over Client1, Client2: 6. Media plane resources released + +``` + +Sequence diagram titled 'Home MCPTT service provider' showing the 'End private call – server initiated' procedure. The diagram involves three lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2. The sequence of messages is: 1. Client 1 and client 2 are registered for MCPTT service and private call is ongoing between them. 2. Conditions to trigger terminate private call. 3. MCPTT server sends MCPTT private call end request to both clients. 4. Clients notify call termination. 5. Clients send MCPTT private call end response to the server. 6. Media plane resources are released. + +**Figure 10.7.2.2.3.2-1: End private call – server initiated** + +1. It is assumed that MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service and are involved in private call with or without floor control established either in manual or automatic commencement mode. +2. Upon conditions to terminate call e.g., MCPTT administrator configured maximum duration for MCPTT private calls has expired or timed out due to MCPTT private call without transmission/reception, the MCPTT server decides to initiate termination of an ongoing MCPTT private call between MCPTT client 1 and MCPTT client 2. +3. MCPTT server sends an MCPTT private call end request towards the MCPTT clients 1 and 2 (via SIP core), for tearing down the private call between them. +4. MCPTT users at client 1 and client 2 are notified about the termination of the private call. +5. The MCPTT private call end request receiving MCPTT clients 1 and 2 acknowledge the request with an MCPTT private call end response. +6. MCPTT clients release all the media plane resources used for the private call. Further, if the private call was established with floor control, floor control resources are released and MCPTT clients cannot make further requests for floor control or send media. + +#### 10.7.2.3 Private call within several MCPTT systems + +##### 10.7.2.3.1 Private call setup in automatic commencement mode – MCPTT users in multiple MCPTT systems + +The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call (automatic commencement mode) for communicating with MCPTT user in another MCPTT system with or without floor control enabled. + +Procedures in figure 10.7.2.3.1-1 are the procedures for the MCPTT client initiating establishment of MCPTT private call with the chosen MCPTT user. + +Pre-conditions: + +1. The calling MCPTT user has selected automatic commencement mode for the call; or +2. The called MCPTT client is set to automatic commencement mode. + +![Sequence diagram illustrating the private call setup in automatic commencement mode between two MCPTT service providers. The diagram shows the interaction between MCPTT client 1, MCPTT server 1, MCPTT server 2, and MCPTT client 2. The process starts with registration, followed by call initiation, authorization, progress indication, and finally media plane establishment.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server 1 + participant MCPTT server 2 + participant MCPTT client 2 + + Note left of MCPTT client 1: 1. MCPTT client 1 registered for MCPTT service + Note right of MCPTT client 2: 1. MCPTT client 2 registered for MCPTT service + + Note left of MCPTT client 1: 2. initiate private call + MCPTT client 1->>MCPTT server 1: 3. MCPTT private call request + MCPTT server 1->>MCPTT server 2: 4. Authorize request + MCPTT server 1-->>MCPTT client 1: 5. MCPTT progress indication + MCPTT server 2->>MCPTT client 2: 6. MCPTT private call request + MCPTT server 2->>MCPTT server 1: 7. Authorize request + MCPTT server 1->>MCPTT client 2: 8. MCPTT private call request + Note right of MCPTT client 2: 9. Notify call + MCPTT client 2->>MCPTT server 2: 10. MCPTT private call response + MCPTT server 2->>MCPTT server 1: 11. MCPTT private call response + Note bottom: 12. Media plane established + +``` + +Sequence diagram illustrating the private call setup in automatic commencement mode between two MCPTT service providers. The diagram shows the interaction between MCPTT client 1, MCPTT server 1, MCPTT server 2, and MCPTT client 2. The process starts with registration, followed by call initiation, authorization, progress indication, and finally media plane establishment. + +**Figure 10.7.2.3.1-1: Private call setup in automatic commencement mode – users in multiple MCPTT systems** + +1. It is assumed that MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service to their respective MCPTT service provider, as per procedure in subclause 10.2. +2. MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call for the chosen MCPTT user. For a private call with floor control, floor control is to be established. +3. MCPTT client 1 sends an MCPTT private call request towards the home MCPTT server 1 (via SIP core) using a service identifier as defined in 3GPP TS 23.228 [5] for MCPTT, for establishing private call with the MCPTT client 2 registered at MCPTT service provider 2. The MCPTT private call request contains the MCPTT id of invited user and an SDP offer containing one or more media types. For a private call with floor control, the MCPTT private call request also contains an element that indicates that MCPTT client 1 is requesting the floor. If the private call request request the floor it may include location information. The MCPTT client 1 may include a requested commencement mode that indicates that the call is to be established in automatic commencement mode if automatic commencement mode is requested by the initiating user. +4. MCPTT server 1 checks whether the MCPTT user at MCPTT client 1 is authorized to initiate the private call. If the MCPTT private call request requested automatic commencement mode then the MCPTT server 1 also checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a call in automatic commencement mode. +5. MCPTT server 1 may provide a progress indication to MCPTT client 1 to indicate progress in the call setup process. + +NOTE: Step 5 can occur at any time following step 4, and prior to step 11. + +6. If authorized, MCPTT server 1 includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request, includes an automatic commencement mode indication if automatic commencement mode was requested by and authorised for the + +calling user and sends the corresponding MCPTT private call request towards the MCPTT system (via SIP core) of the MCPTT client specified in the original MCPTT private call request (MCPTT client 2) i.e., MCPTT server 2. If location information was included in the private call request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to the other user on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking"). + +7. MCPTT server 2 checks whether the MCPTT user at MCPTT client 2 is authorized to receive a private call. +8. MCPTT server 2 includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request, includes a requested automatic commencement mode indication based on a requested automatic commencement mode by the calling user or based upon the setting of the called MCPTT client and sends the received MCPTT private call request towards the MCPTT client specified in the received MCPTT private call request (i.e., MCPTT client 2). If the called MCPTT user has registered to the MCPTT service with multiple MCPTT UEs and has designated the MCPTT UE for receiving the private calls, then the incoming MCPTT private call request is delivered only to the designated MCPTT UE. +9. The receiving MCPTT client 2 notifies the user about the incoming private call. +10. The receiving MCPTT client 2 accepts the private call automatically, and an acknowledgement is sent to the MCPTT server 1 (via SIP core and MCPTT server 2). +11. Upon receiving the MCPTT private call response from MCPTT client 2 accepting the private call request, MCPTT client 1 is informed about successful call establishment. +12. MCPTT client 1 and MCPTT client 2 have successfully established media plane for communication and either user can transmit media. For successful call establishment of a private call with implicit floor control request from MCPTT client 1, floor participant at MCPTT client 1 is granted floor by the floor control server at MCPTT service provider 1, giving it permission to transmit. At the same time floor participant at MCPTT client 2 is informed by the floor control server at MCPTT service provider 1 that the floor is taken. + +##### 10.7.2.3.2 Private call setup in manual commencement mode – MCPTT users in multiple MCPTT systems + +The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call (manual commencement mode) for communicating with MCPTT user in another MCPTT system with or without floor control enabled. + +Procedures in figure 10.7.2.3.2-1 are the procedures for the MCPTT client initiating establishment of MCPTT private call with the selected MCPTT user. + +Pre-conditions: + +1. The calling MCPTT user has selected manual commencement mode or has not specified a commencement mode for the call; and +2. The called MCPTT client is set to manual commencement mode. + +![Sequence diagram illustrating the private call setup in manual commencement mode between two MCPTT service providers. The diagram shows the interaction between MCPTT clients and servers across two providers, leading to the establishment of a media plane.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server 1 + participant MCPTT server 2 + participant MCPTT client 2 + + Note left of MCPTT client 1: 1. MCPTT client 1 registered for MCPTT service + Note right of MCPTT client 2: 1. MCPTT client 2 registered for MCPTT service + + Note left of MCPTT client 1: 2. initiate private call + MCPTT client 1->>MCPTT server 1: 3. MCPTT private call request + MCPTT server 1->>MCPTT server 1: 4. Authorize request + MCPTT server 1->>MCPTT server 2: 5. MCPTT private call request + MCPTT server 2->>MCPTT server 2: 7. Authorize request + MCPTT server 2->>MCPTT client 2: 8. MCPTT private call request + MCPTT client 2->>MCPTT server 2: 9. MCPTT ringing + MCPTT server 2->>MCPTT server 1: 9. MCPTT ringing + MCPTT server 1->>MCPTT client 1: 10. MCPTT ringing + MCPTT client 2->>MCPTT server 2: 11. MCPTT private call response + MCPTT server 2->>MCPTT server 1: 11. MCPTT private call response + MCPTT server 1->>MCPTT client 1: 12. MCPTT private call response + + Note bottom: 13. Media plane established + +``` + +Sequence diagram illustrating the private call setup in manual commencement mode between two MCPTT service providers. The diagram shows the interaction between MCPTT clients and servers across two providers, leading to the establishment of a media plane. + +**Figure 10.7.2.3.2-1: Private call setup in manual commencement mode – users in multiple MCPTT systems** + +1. It is assumed that MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service to their respective MCPTT service provider, as per procedure in subclause 10.2. +2. MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call for the selected MCPTT user. For a private call with floor control, floor control is to be established. +3. MCPTT client 1 sends an MCPTT private call request towards the home MCPTT server 1 (via SIP core), for establishing private call with the MCPTT client 2 registered at MCPTT service provider 2. For a private call with floor control, the MCPTT private call request contains an element that indicates that MCPTT client 1 is requesting the floor. If the call request requests the floor the call request may include location information. The MCPTT client 1 may include a requested commencement mode that indicates that the call is to be established in manual commencement mode if manual commencement mode is requested by the initiating user. +4. MCPTT server 1 checks whether the MCPTT user at MCPTT client 1 is authorized to initiate the private call. The MCPTT server 1 also checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a call in manual commencement mode. +5. If authorized, MCPTT server 1 sends the corresponding MCPTT private call request towards the MCPTT system (via SIP core) of the MCPTT client specified in the original MCPTT private call request (MCPTT client 2) i.e., MCPTT server 2. If location information was included in the private call request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to the other user on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking"). +6. MCPTT server may provide a progress indication to MCPTT client 1 to indicate progress in the call setup process. + +NOTE: Step 6 can occur at any time following step 4, and prior to step 10. + +7. The MCPTT server 2 checks whether the MCPTT user at MCPTT client 2 is authorized to receive a private call and also checks the commencement mode setting of MCPTT client 2. +8. The MCPTT server 2 offers the same media types or a subset of the media types contained in the initial received request and sends an MCPTT private call request towards the MCPTT client specified in the received MCPTT private call request (i.e., MCPTT client 2). If the called MCPTT user has registered to the MCPTT service with multiple MCPTT UEs and has designated the MCPTT UE for receiving the private calls, then the incoming MCPTT private call request is delivered only to the designated MCPTT UE. +9. The MCPTT user is alerted. MCPTT client 2 sends an MCPTT ringing to the MCPTT server 1 (via server 2). +10. The MCPTT server 1 sends an MCPTT ringing to MCPTT client 1, indicating that MCPTT client 2 is being alerted. +11. MCPTT user 2 has accepted the call using manual commencement mode (i.e. has taken some action to accept via the user interface) which causes MCPTT client 2 to send an MCPTT private call response to the MCPTT server 1 (via SIP core and MCPTT server 2) +12. Upon receiving the MCPTT private call response from MCPTT client 2 accepting the private call request, MCPTT client 1 is informed about successful call establishment. +13. MCPTT client 1 and client 2 have successfully established media plane for communication and either user can transmit media. For successful call establishment of a private call with implicit floor control request from MCPTT client 1, floor participant at MCPTT client 1 is granted the floor by the floor control server at MCPTT service provider 1, giving it permission to transmit. At the same time floor participant at MCPTT client 2 is informed by the floor control server at MCPTT service provider 1 that the floor is taken. + +##### 10.7.2.3.3 Private call release – MCPTT users in multiple MCPTT systems + +The procedure in this subclause is for the case where an MCPTT client is requesting to release an ongoing MCPTT private call (with or without floor control) established in either of the two commencement modes (manual or automatic), and the MCPTT users are in multiple MCPTT systems. + +Procedures are similar to those described for private call release when MCPTT users are in single MCPTT system as in subclause 10.7.2.2.3.1, with the addition that the MCPTT call end request and the corresponding acknowledgement are routed through the MCPTT server in partner MCPTT system. + +#### 10.7.2.4 MCPTT emergency private call + +##### 10.7.2.4.1 MCPTT emergency private call commencement + +This procedure focuses on the case where an authorized MCPTT user is initiating an MCPTT emergency private call with unicast signalling for communicating with another MCPTT user. An MCPTT client in the MCPTT emergency state gains elevated access privilege for all of the MCPTT user's mission critical applications. + +Procedures in figure 10.7.2.4.1-1 are the signalling control plane procedures for the MCPTT client initiating establishment of an MCPTT emergency private call. + +Pre-conditions: + +1. Both members of the MCPTT private call belong to the same MCPTT system. +2. The initiating MCPTT client 1 has been configured to send an MCPTT emergency alert prior to initiating an MCPTT emergency private call. +3. Optionally, MCPTT client 1 may use an activated functional alias for the call. +4. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for MCPTT emergency private call. Lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2, all under the 'Home MCPTT service provider'. The sequence is: 1. initiate emergency call (client 1); 2. MCPTT emergency private call request (client 1 to server); 3. MCPTT emergency private call request (server to client 2); 4. Notify emergency call (client 2); 5. OK (client 2 to server); 6. Bearer priority adjustment (server); 7. OK (server to client 1); 8. Media plane and floor control establishment (client 1 and 2).](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note over MCPTT client 1, MCPTT server, MCPTT client 2: Home MCPTT service provider + + MCPTT client 1->>MCPTT server: 1. initiate emergency call + MCPTT client 1->>MCPTT server: 2. MCPTT emergency private call request + MCPTT server->>MCPTT client 2: 3. MCPTT emergency private call request + MCPTT client 2->>MCPTT client 2: 4. Notify emergency call + MCPTT client 2->>MCPTT server: 5. OK + MCPTT server->>MCPTT server: 6. Bearer priority adjustment + MCPTT server->>MCPTT client 1: 7. OK + MCPTT client 1->>MCPTT client 2: 8. Media plane and floor control establishment + +``` + +Sequence diagram for MCPTT emergency private call. Lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2, all under the 'Home MCPTT service provider'. The sequence is: 1. initiate emergency call (client 1); 2. MCPTT emergency private call request (client 1 to server); 3. MCPTT emergency private call request (server to client 2); 4. Notify emergency call (client 2); 5. OK (client 2 to server); 6. Bearer priority adjustment (server); 7. OK (server to client 1); 8. Media plane and floor control establishment (client 1 and 2). + +**Figure 10.7.2.4.1-1 MCPTT emergency private call** + +1. The user at the MCPTT client 1 initiates an MCPTT emergency private call. MCPTT client 1 sets its MCPTT emergency state. The MCPTT emergency state is retained until explicitly cancelled. +2. MCPTT client 1 sends an MCPTT emergency private call request towards the MCPTT server. The request contains an indication of the MCPTT emergency. MCPTT user at MCPTT client 1 may select a functional alias and the MCPTT server verifies whether the provided functional alias can be used. The MCPTT server records the identity of the MCPTT user that initiated the MCPTT emergency private call until the MCPTT emergency is cancelled. If the MCPTT client is configured to send an MCPTT emergency alert when initiating an MCPTT emergency private call, the request also contains an indication that an MCPTT emergency alert is to be initiated. +3. MCPTT server sends the MCPTT emergency private call request towards the target MCPTT client. The request contains an indication of the in-progress emergency. The request contains an indication of an MCPTT emergency alert if the request from the originator indicated MCPTT emergency alert. +4. The MCPTT user on MCPTT client 2 is notified of the incoming MCPTT emergency private call and may display the functional alias of MCPTT client 1. +5. The receiving MCPTT client acknowledges the MCPTT emergency private call request to the MCPTT server. +6. The MCPTT server adjusts the priority of the underlying bearer. +7. The MCPTT server informs MCPTT client 1 about the successful MCPTT emergency private call establishment. +8. MCPTT client 1 and MCPTT client 2 establish the media plane for communication. The MCPTT client 1 can override MCPTT client 2 unless MCPTT client 2 is also in the MCPTT emergency state. + +NOTE 1: The priority for the MCPTT emergency private call is retained until cancelled according to system policy (e.g. timeout or call end) or cancelled by an authorized MCPTT user. + +NOTE 2: The initiating MCPTT user's MCPTT emergency state is retained by the system until cancelled as in subclause 10.6.2.6.1.3. The initiating MCPTT user's MCPTT emergency state is also retained locally by the MCPTT client until explicitly cancelled by the MCPTT user. + +##### 10.7.2.4.2 MCPTT private call emergency upgrade + +This procedure focuses on the case where an authorized MCPTT user is upgrading a private call to an MCPTT emergency private call while the private call is already in progress. + +Procedures in figure 10.7.2.4.2-1 are the signalling procedures for the MCPTT client upgrading a private call to an MCPTT emergency private call. + +Pre-conditions: + +1. Both members of the private call belong to the same MCPTT system. +2. A private call is already in progress. + +![Sequence diagram for MCPTT private call upgrade. The diagram shows three lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2, all under the 'Home MCPTT service provider'. The process starts with 'Private call already in progress'. Step 1: 'User initiates emergency' (internal to client 1). Step 2: 'MCPTT emergency private call request' from client 1 to server. Step 3: 'MCPTT emergency private call request' from server to client 2. Step 4: 'Notify emergency status' (internal to client 2). Step 5: 'OK' from client 2 to server. Step 6: 'Bearer priority adjustment' (internal to server). Step 7: 'OK' from server to client 1. Step 8: 'Private call continues as a private emergency call' (internal to client 1).](1b893df61c2b73b7a85e65fc1f58e203_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note over MCPTT client 1, MCPTT client 2: Private call already in progress + Note left of MCPTT client 1: 1. User initiates emergency + MCPTT client 1->>MCPTT server: 2. MCPTT emergency private call request + MCPTT server->>MCPTT client 2: 3. MCPTT emergency private call request + Note right of MCPTT client 2: 4. Notify emergency status + MCPTT client 2->>MCPTT server: 5. OK + Note right of MCPTT server: 6. Bearer priority adjustment + MCPTT server->>MCPTT client 1: 7. OK + Note left of MCPTT client 1: 8. Private call continues as a private emergency call + +``` + +Sequence diagram for MCPTT private call upgrade. The diagram shows three lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2, all under the 'Home MCPTT service provider'. The process starts with 'Private call already in progress'. Step 1: 'User initiates emergency' (internal to client 1). Step 2: 'MCPTT emergency private call request' from client 1 to server. Step 3: 'MCPTT emergency private call request' from server to client 2. Step 4: 'Notify emergency status' (internal to client 2). Step 5: 'OK' from client 2 to server. Step 6: 'Bearer priority adjustment' (internal to server). Step 7: 'OK' from server to client 1. Step 8: 'Private call continues as a private emergency call' (internal to client 1). + +**Figure 10.7.2.4.2-1: MCPTT private call upgrade** + +1. The MCPTT user at MCPTT client 1 initiates an emergency. MCPTT client 1 sets its MCPTT emergency state. The MCPTT emergency state is retained until explicitly cancelled. +2. MCPTT client 1 requests the MCPTT server to upgrade the private call to in-progress emergency by sending an MCPTT emergency request. If configured to send an MCPTT alert when initiating an MCPTT emergency upgrade, the request also contains an indication that an MCPTT alert is to be initiated. The request may contain an indication of an implicit floor request. If the emergency private call request includes an implicit floor request it may also include location information. +3. The MCPTT server sends the MCPTT emergency request towards the MCPTT client of the other participant. If location information was included in the emergency private call request, the MCPTT server checks the privacy policy of the MCPTT user to decide if the location information of MCPTT client 1 can be provided to the other user on the call (refer to Annex A.3 "Authorisation to provide location information to other MCPTT users on a call when talking"). +4. The MCPTT user is notified of the in-progress emergency of the MCPTT emergency private call. +5. The receiving MCPTT client acknowledges the MCPTT emergency request to the MCPTT server. + +6. The MCPTT server adjusts the priority of the underlying bearer for both participants in the private call. The priority is retained until the call ends. +7. The MCPTT server confirms the upgrade request to MCPTT client 1. +8. MCPTT client 1 and MCPTT client 2 continue with the private call, which has been transformed into an MCPTT emergency private call. The MCPTT client 1 can override MCPTT client 2 unless MCPTT client 2 is also in the MCPTT emergency state. + +### 10.7.3 Private call in off-network + +#### 10.7.3.1 Information flows for private call in off-network + +##### 10.7.3.1.1 Call setup request + +Table 10.7.3.1.1-1 describes the information flow call setup request from one MCPTT client to another MCPTT client. + +**Table 10.7.3.1.1-1: call setup request** + +| Information element | Status | Description | +|----------------------------|--------|---------------------------------------------------| +| MCPTT ID of the caller | M | The identity of the calling party | +| MCPTT ID of the callee | M | The identity of the called party | +| SDP offer for private call | M | SDP with media information offered by (to) client | +| Location information | O | Location of the calling party | + +##### 10.7.3.1.2 Call setup response + +Table 10.7.3.1.2-1 describes the information flow call setup response from one MCPTT client to another MCPTT client. + +**Table 10.7.3.1.2-1: call setup response** + +| Information element | Status | Description | +|-----------------------------|--------|---------------------------------------------------| +| MCPTT ID of the caller | M | The identity of the calling party | +| MCPTT ID of the callee | M | The identity of the called party | +| SDP answer for private call | M | SDP with media information offered by (to) client | + +##### 10.7.3.1.3 Call release request + +Table 10.7.3.1.3-1 describes the information flow call release request from one MCPTT client to another MCPTT client. + +**Table 10.7.3.1.3-1: call release request** + +| Information element | Status | Description | +|-----------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID of the caller | M | The identity of the calling party | +| MCPTT ID of the callee | M | The identity of the called party | +| MCPTT private call release reason | O | This element indicates that reason for the private call release. e.g., Originating client requested, target client requested. | + +##### 10.7.3.1.4 Call release response + +Table 10.7.3.1.4-1 describes the information flow call release response from one MCPTT client to another MCPTT client. + +**Table 10.7.3.1.4-1: call release response** + +| Information element | Status | Description | +|-----------------------------------|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID of the caller | M | The identity of the calling party | +| MCPTT ID of the callee | M | The identity of the called party | +| MCPTT private call release reason | O | This element indicates that reason for the private call release. e.g., Originating client requested, target client requested, server requested. | + +#### 10.7.3.2 Use of ProSe capability for private call + +When an MCPTT user using a ProSe-enabled UE wants to communicate with a specific MCPTT user using a ProSe-enabled UE by a ProSe mechanism, the MCPTT client retrieves the ProSe discovery group ID and user info ID of the target MCPTT user from the "List of user(s) who can be called in private call" in the MCPTT user profile and requests the IP address of the MCPTT UE associated with the target MCPTT user from the ProSe layer. + +The MCPTT client enables the ProSe layer to determine IP address for the target MCPTT UE by providing the ProSe discovery group ID and user info ID (as defined in specification 3GPP TS 23.303 [7]) of the target MCPTT user. This may trigger the ProSe layer procedure (e.g. discovery). The user info ID of the target MCPTT user is used by the ProSe layer as the target info (as defined in specification 3GPP TS 23.303 [7]). + +The ProSe layer can then provide the IP address related to the target MCPTT user's MCPTT ID to the MCPTT client. + +NOTE: The ProSe procedures for one-to-one direct communications specified in 3GPP TS 23.303 [7] retrieves a layer-2 ID associated with the user info ID of the target MCPTT user by the discovery procedure to establish direct communications between ProSe users. + +#### 10.7.3.3 Private call setup in automatic commencement mode + +The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call for communicating with another MCPTT user when off-network using an automatic commencement mode. + +Procedures in figure 10.7.3.3-1 are the basic signalling procedures for the MCPTT client initiating establishment of an off-network MCPTT private call with the chosen MCPTT user. + +Pre-conditions: + +1. MCPTT user profile used for off-network operation mode is pre-provisioned in the MCPTT UEs. + +![Sequence diagram for Private call setup in automatic commencement mode](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + Note left of MCPTT client 1: 1. Initiate private call + MCPTT client 1->>MCPTT client 2: 2. Call setup request + Note right of MCPTT client 2: 3. Notify user + MCPTT client 2->>MCPTT client 1: 4. Call setup response + Note left of MCPTT client 1: 5. Media plane is established with floor control +``` + +The diagram illustrates the sequence of events for a private call setup in automatic commencement mode. It involves two MCPTT clients, MCPTT client 1 and MCPTT client 2. The process starts with MCPTT client 1 initiating a private call. MCPTT client 1 then sends a call setup request to MCPTT client 2. MCPTT client 2 notifies its user about the incoming private call. MCPTT client 2 then sends a call setup response to MCPTT client 1. Finally, the media plane is established with floor control, and MCPTT client 1 is automatically granted the floor. + +Sequence diagram for Private call setup in automatic commencement mode + +**Figure 10.7.3.3-1: Private call setup in automatic commencement mode** + +1. The MCPTT user at MCPTT client 1 would like to initiate a private call to the MCPTT user at MCPTT client 2. +2. The MCPTT client 1 sends a call setup request towards the MCPTT client 2. The call setup request contains an SDP offer, an automatic commencement mode indication, and an element that indicates that MCPTT client 1 is requesting the floor. If the private call request requests the floor it may include location information. +3. The MCPTT client 2 notifies the MCPTT user about the incoming private call. +4. The receiving MCPTT client 2 accepts the private call automatically, and a call setup response indicating the successful call establishment is sent to MCPTT client 1. If MCPTT client 2 rejected the incoming call, the MCPTT client 2 sends a call setup response indicating the failure reason to the MCPTT client 1. + +NOTE: Step 4 can also occur prior to step 3. + +5. The MCPTT client 1 and the MCPTT client 2 have successfully established the media plane for communication with floor control and the MCPTT client 1 is automatically granted the floor. + +#### 10.7.3.4 Private call setup in manual commencement mode + +The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call for communicating with another MCPTT user when off-network using a manual commencement mode. + +Procedures in figure 10.7.3.4-1 are the basic signalling procedures for the MCPTT client initiating establishment of an off-network MCPTT private call with the chosen MCPTT user. + +Pre-conditions: + +1. MCPTT user profile used for off-network operation mode is pre-provisioned in the MCPTT UEs. + +![Sequence diagram illustrating the private call setup in manual commencement mode between MCPTT client 1 and MCPTT client 2.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + Note left of MCPTT client 1: 1. Initiate private call + MCPTT client 1->>MCPTT client 2: 2. Call setup request + Note right of MCPTT client 2: 3. Notify user + MCPTT client 2->>MCPTT client 1: 4. MCPTT ringing + Note right of MCPTT client 2: 5. User answers + MCPTT client 2->>MCPTT client 1: 6. Call setup response + Note over MCPTT client 1, MCPTT client 2: 7. Media plane is established with floor control + +``` + +The diagram shows a sequence of interactions between MCPTT client 1 and MCPTT client 2. It begins with MCPTT client 1 initiating a private call. A 'Call setup request' is sent from client 1 to client 2. Client 2 then notifies its user. A 'MCPTT ringing' message is sent from client 2 back to client 1. The user at client 2 answers, and a 'Call setup response' is sent from client 2 to client 1. Finally, the media plane is established with floor control between the two clients. + +Sequence diagram illustrating the private call setup in manual commencement mode between MCPTT client 1 and MCPTT client 2. + +**Figure 10.7.3.4-1: Private call setup in manual commencement mode** + +1. The MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call to the MCPTT user at MCPTT client 2. + 2. The MCPTT client 1 sends a call setup request towards the MCPTT client 2. The MCPTT private call setup request contains an SDP offer, a manual commencement mode indication, and an element that indicates that MCPTT client 1 is requesting the floor. If the private call request requests the floor it may include location information. + 3. The receiving MCPTT client 2 notifies the MCPTT user about the incoming private call. + 4. The MCPTT client 2 sends MCPTT ringing message to the MCPTT client 1. +- NOTE: Step 4 can also occur prior to step 3. +5. The MCPTT user at the MCPTT client 2 has accepted the call using manual commencement mode (i.e., has taken some action to accept via the user interface). The MCPTT user may also reject or fail to answer the incoming call. + 6. The MCPTT client 2 sends a call setup response indicating the successful call establishment to MCPTT client 1. If the MCPTT client 2 rejected the call or the MCPTT user 2 rejected or failed to answer the incoming call, the MCPTT client 2 sends a call setup response indicating the failure reason to the MCPTT client 1. + 7. The MCPTT client 1 and the MCPTT client 2 have successfully established the media plane for communication with floor control and the MCPTT client 1 is automatically granted the floor. + +#### 10.7.3.5 Private call release + +The procedure focuses on the case where an MCPTT client is requesting to release an ongoing MCPTT private call whether the call was established using either of the two commencement modes (manual or automatic), as described in subclause 10.7.3.3 and subclause 10.7.3.4. Either MCPTT client can initiate the call release procedure. + +Procedures in figure 10.7.3.5-1 are the basic signalling control plane procedures for an MCPTT client initiating the release of an ongoing off-network MCPTT private call. + +Pre-conditions: + +1. Two MCPTT users are currently engaged in an off-network MCPTT private call. + +![Sequence diagram illustrating the private call release procedure between MCPTT client 1 and MCPTT client 2.](5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + Note left of MCPTT client 1: 1. Initiate private call release + MCPTT client 1->>MCPTT client 2: 2. Call release request + Note right of MCPTT client 2: 3. Notify user + MCPTT client 2->>MCPTT client 1: 4. Call release response + Note bottom: 5. Media plane resources are released +``` + +The diagram is a sequence diagram showing the interaction between two MCPTT clients, MCPTT client 1 and MCPTT client 2, for releasing a private call. The sequence of steps is as follows: 1. MCPTT client 1 initiates the private call release. 2. MCPTT client 1 sends a 'Call release request' to MCPTT client 2. 3. MCPTT client 2 notifies its user about the call release. 4. MCPTT client 2 sends a 'Call release response' back to MCPTT client 1. 5. Finally, both clients release their media plane resources. + +Sequence diagram illustrating the private call release procedure between MCPTT client 1 and MCPTT client 2. + +**Figure 10.7.3.5-1: Private call release** + +1. The MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call release to the MCPTT user at MCPTT client 2. + 2. The MCPTT client 1 sends a call release request towards the MCPTT client 2. + 3. The MCPTT client 2 notifies the MCPTT user about the private call release. + 4. The MCPTT client 2 sends a call release response indicating the successful call release to MCPTT client 1. +- NOTE: Step 4 can also occur prior to step 3. +5. The MCPTT client 1 and the MCPTT client 2 release all associated media plane resources. + +#### 10.7.3.6 MCPTT emergency private call + +The off-network emergency private call is a special case of off-network private call as defined in subclause 10.7.3. The following are modifications to the aforementioned subclause to support MCPTT private calls: + +- The call setup contains an indication that the MCPTT private call is to be an MCPTT emergency private call, +- the bearers of both MCPTT private call participants are given MCPTT emergency priority prior to media transfer, +- either participant in an MCPTT private call may upgrade the call to the MCPTT emergency state during the call by sending an MCPTT upgrade private emergency request, +- placing an MCPTT emergency private call places the MCPTT client in the MCPTT emergency state, +- the bearer priority of each participant is restored to the priority as it was prior to the MCPTT emergency private call initiation, when the call ends or when the MCPTT emergency priority is cancelled +- an authorized user or the originator of the call may cancel the MCPTT emergency priority of the call by sending an MCPTT cancel private emergency request and + +- the MCPTT emergency priority of the MCPTT private call may be cancelled when criteria established by the MCPTT Administrator are met (e.g., timeout). + +### 10.7.4 MCPTT private call call-back request + +#### 10.7.4.1 Information flows for MCPTT private call call-back request + +##### 10.7.4.1.1 MCPTT private call call-back request + +Table 10.7.4.1.1-1 describes the information flow MCPTT private call call-back request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.7.4.1.1-1: MCPTT private call call-back request information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Urgency indication | M | This element indicates the urgency (i.e., low, normal, high) of the call-back request. | + +##### 10.7.4.1.2 MCPTT private call call-back response + +Table 10.7.4.1.2-1 describes the information flow MCPTT private call call-back response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.7.4.1.2-1: MCPTT private call call-back response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Result | M | Result of the MCPTT call-back request – success or fail. | + +##### 10.7.4.1.3 MCPTT private call call-back cancel request + +Table 10.7.4.1.3-1 describes the information flow MCPTT private call call-back cancel request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.7.4.1.3-1: MCPTT private call call-back cancel request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | + +##### 10.7.4.1.4 MCPTT private call call-back cancel response + +Table 10.7.4.1.4-1 describes the information flow MCPTT private call call-back cancel response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.7.4.1.4-1: MCPTT private call call-back cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Result | M | Result of the MCPTT private call call-back cancel request – success or fail. | + +#### 10.7.4.2 MCPTT private call call-back request within one MCPTT system + +The MCPTT private call call-back request procedure includes the initial MCPTT private call call-back request from the MCPTT user and the indication to the receiving MCPTT user of the who called, the time when the call request was made, and the urgency indication. + +Procedures in figure 10.7.4.2-1 show the signalling control plane procedures for the MCPTT client initiating an MCPTT private call call-back request with the chosen MCPTT user. + +Pre-conditions: + +- MCPTT user 1 is the current user at MCPTT client 1 and MCPTT user 2 is the current user at MCPTT client 2; +- MCPTT client 1 and MCPTT client 2 are registered for MCPTT service. + +![Sequence diagram showing the MCPTT private call call-back request procedure between MCPTT client 1, MCPTT server, and MCPTT client 2.](eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note left of MCPTT client 1: 1. initiate MCPTT private call call-back + MCPTT client 1->>MCPTT server: 2. MCPTT private call call-back request + Note right of MCPTT server: 3. Authorize request + MCPTT server->>MCPTT client 2: 4. MCPTT private call call-back request + Note right of MCPTT client 2: 5. Store call-back request information + Note right of MCPTT client 2: 6. Notify user + MCPTT client 2->>MCPTT server: 7. MCPTT private call call-back response + MCPTT server->>MCPTT client 1: 8. MCPTT private call call-back response + +``` + +Sequence diagram showing the MCPTT private call call-back request procedure between MCPTT client 1, MCPTT server, and MCPTT client 2. + +**Figure 10.7.4.2-1: MCPTT private call call-back request – MCPTT users in the same MCPTT system** + +1. MCPTT user on MCPTT client 1 initiates an MCPTT private call call-back request to the MCPTT user of MCPTT client 2. +2. MCPTT client 1 sends an MCPTT private call call-back request towards the MCPTT server. +3. MCPTT server checks whether the MCPTT user 1 at MCPTT client 1 is authorized to initiate the MCPTT private call call-back request. +4. If authorized, MCPTT server sends the corresponding MCPTT private call call-back request towards the MCPTT client 2. + +5. The receiving MCPTT client 2 stores the MCPTT user who initiated the MCPTT private call call-back request, the time the MCPTT private call call-back request was received, and the urgency indication for the MCPTT private call call-back request. +6. The MCPTT client 2 notifies the MCPTT user 2 that there is an MCPTT private call call-back request awaiting his attention. +7. The receiving MCPTT client 2 sends an MCPTT private call call-back response to the MCPTT server. +8. Upon receiving the MCPTT private call call-back response from MCPTT client 2, the MCPTT server informs the MCPTT client 1 about successful call-back request. + +#### 10.7.4.3 MCPTT private call call-back cancel request within one MCPTT system + +Once an MCPTT private call call-back request has been successfully made and before the receiving MCPTT user has made an MCPTT private call to the calling MCPTT user, the calling MCPTT user may cancel the outstanding MCPTT private call request. + +Procedures in figure 10.7.4.3-1 show the signalling control plane procedures for the MCPTT client initiating an MCPTT private call call-back cancel request with the chosen MCPTT user. + +Pre-conditions: + +1. A previously successfully made MCPTT private call call-back request from MCPTT client 1 to MCPTT client 2. + +![Sequence diagram showing the MCPTT private call call-back cancel request process between MCPTT client 1, MCPTT server, and MCPTT client 2.](e94cbc0895c6914a2bb53f150ab7495e_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note left of MCPTT client 1: 1. Wants to cancel a previous call-back request + MCPTT client 1->>MCPTT server: 2. MCPTT private call call-back cancel request + Note right of MCPTT server: 3. Authorize cancel request + MCPTT server->>MCPTT client 2: 4. MCPTT private call call-back cancel request + Note right of MCPTT client 2: 5. Remove the stored call-back request information + MCPTT client 2->>MCPTT server: 6. MCPTT private call call-back cancel response + MCPTT server->>MCPTT client 1: 7. MCPTT private call call-back cancel response + +``` + +Sequence diagram showing the MCPTT private call call-back cancel request process between MCPTT client 1, MCPTT server, and MCPTT client 2. + +**Figure 10.7.4.3-1: MCPTT private call call-back cancel request – MCPTT users in the same MCPTT system** + +1. MCPTT user on MCPTT client 1 wants to cancel a previously created MCPTT private call call-back request to the MCPTT user 2 of MCPTT client 2. +2. MCPTT client 1 sends an MCPTT private call call-back cancel request towards the MCPTT server. +3. MCPTT server checks whether the MCPTT user 1 at MCPTT client 1 is authorized to cancel the previous MCPTT private call call-back request, if one exists. +4. If authorized, MCPTT server sends the corresponding MCPTT private call call-back cancel request towards the MCPTT client 2. + +5. The receiving MCPTT client 2 removes all stored information about the previous MCPTT private call call-back request from the MCPTT user 1 on MCPTT client 1. +6. The receiving MCPTT client 2 sends an MCPTT private call call-back cancel response to the MCPTT server. +7. Upon receiving the MCPTT private call call-back cancel response from MCPTT client 2, the MCPTT server informs the MCPTT client 1 about successful call-back request cancelation. + +#### 10.7.4.4 MCPTT private call call-back request fulfillment within one MCPTT system + +Once an MCPTT private call call-back request has been successfully made, it is expected that the receiving MCPTT user will make an MCPTT private call to the MCPTT user who sent the MCPTT private call call-back request. The procedures for establishing the MCPTT private call between the two users is the same as an MCPTT private call (10.7.2.2.2). + +Procedures in figure 10.7.4.4-1 show the signalling control plane procedures for the MCPTT client returning an MCPTT private call to the MCPTT user who initiated the MCPTT private call call-back request. + +Pre-conditions: + +1. A previously successfully made MCPTT private call call-back request from MCPTT client 1 to MCPTT client 2. + +![Sequence diagram showing MCPTT private call call-back request fulfillment. Lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2. Step 1: MCPTT private call in manual commencement mode procedures. Step 2: Remove stored call-back request information.](23b48e0b60d0b6deb0cc9862ff4b8ead_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note right of MCPTT client 2: 1. MCPTT private call in manual commencement mode procedures + Note right of MCPTT client 2: 2. Remove stored call-back request information + +``` + +Sequence diagram showing MCPTT private call call-back request fulfillment. Lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2. Step 1: MCPTT private call in manual commencement mode procedures. Step 2: Remove stored call-back request information. + +**Figure 10.7.4.4-1: MCPTT private call-back request fulfillment – MCPTT users in the same MCPTT system** + +1. MCPTT user 2 on MCPTT client 2 decides to initiate an MCPTT private call based on the stored MCPTT private call call-back request to the MCPTT user 1 on MCPTT client 1 using the MCPTT private call procedures of 10.7.2.2.2. +2. Once a successful MCPTT private call has been made between the MCPTT user 1 on MCPTT client 1 and MCPTT user 2, then the MCPTT client 2 removes the stored call-back request information. + +### 10.7.5 MCPTT call forwarding for private calls + +#### 10.7.5.1 General + +Call forwarding of MCPTT private calls allows users to configure forwarding of incoming private calls (with or without Floor control) to another MCPTT user depending on the following conditions: + +- Immediate +- No answer: If the incoming private call is a call with manual commencement mode and the MCPTT User does not answer within a configured period + +##### 10.7.5.1.1 Void + +##### 10.7.5.1.2 MCPTT private call forwarding request (MCPTT server to MCPTT client) + +Table 10.7.5.1.2-1 describes the information flow of the MCPTT private call forwarding request from the MCPTT server to the MCPTT client. + +**Table 10.7.5.1.2-1: MCPTT private call forwarding request (MCPTT server to MCPTT client) information elements** + +| Information Element | Status | Description | +|---------------------|--------|--------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the party to be forwarded | +| MCPTT ID | M | The target MCPTT ID of the call forwarding | + +##### 10.7.5.1.3 MCPTT private call forwarding response (MCPTT client to MCPTT server) + +Table 10.7.5.1.3-1 describes the information flow of the MCPTT private call forwarding response from the MCPTT client to the MCPTT server. + +**Table 10.7.5.1.3-1: MCPTT private call forwarding response (MCPTT client to MCPTT server) information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the party to be forwarded | +| MCPTT ID | M | The MCPTT ID of the target of the forwarding | +| Result | M | Result of the call forwarding request – success or fail | + +#### 10.7.5.2 Procedures + +##### 10.7.5.2.1 Update configuration for MCPTT private call forwarding + +An authorized user can update the call forwarding related parameters stored in the user profile using the procedures as defined in 3GPP TS 23.280 [8] subclause 10.1.4.5. + +##### 10.7.5.2.2 MCPTT immediate private call forwarding + +Figure 10.7.5.2.2-1 below illustrates the procedure of immediate call forwarding of MCPTT private calls. + +Pre-conditions: + +1. MCPTT client 2 is authorized to use call forwarding and has immediate call forwarding enabled with the destination MCPTT client 3. +2. MCPTT client 1 is authorized to make private calls to client 2. +3. The redirection counter is below the limit. +4. MCPTT client 1 has the necessary security information to initiate a private call with MCPTT client 2 and MCPTT client 3 if end2end encryption is required for the private call. + +![Sequence diagram for call forwarding immediate for private calls between MCPTT Client 1, MCPTT Server, MCPTT Client 2, and MCPTT Client 3.](32ff77da4286b58c4778033acaa10836_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Server + participant MCPTT Client 2 + participant MCPTT Client 3 + + Note right of MCPTT Server: 2. MCPTT server checks if client 2 has immediate call forwarding enabled + Note right of MCPTT Server: 3. MCPTT server checks limit of redirection counter. MCPTT server increments counter for immediate forwardings. + + MCPTT Client 1->>MCPTT Server: 1. MCPTT private call request + MCPTT Server->>MCPTT Client 1: 4. MCPTT private call forwarding request + Note left of MCPTT Client 1: 5. Notify user + MCPTT Client 1->>MCPTT Server: 6. MCPTT private call forwarding response + MCPTT Client 1->>MCPTT Server: 7. MCPTT private call request + Note right of MCPTT Server: 8. MCPTT server verifies that client 1 has been authorized to complete the call forwarding + MCPTT Server->>MCPTT Client 3: 9. MCPTT private call request + MCPTT Server-->>MCPTT Client 1: 10. MCPTT progress indication + MCPTT Client 3-->>MCPTT Server: 11. MCPTT ringing + MCPTT Server-->>MCPTT Client 1: 12. MCPTT ringing + MCPTT Client 3->>MCPTT Server: 13. MCPTT private call response + MCPTT Server->>MCPTT Client 1: 14. MCPTT private call response + Note over MCPTT Client 1, MCPTT Client 3: 15. Media plane established between client 1 and 3 + +``` + +Sequence diagram for call forwarding immediate for private calls between MCPTT Client 1, MCPTT Server, MCPTT Client 2, and MCPTT Client 3. + +**Figure 10.7.5.2.2-1: Call forwarding immediate for private calls** + +1. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server. + 2. The MCPTT server detects that MCPTT client 2 has immediate call forwarding enabled. + 3. The MCPTT server checks that the limit of immediate forwardings is not reached. The MCPTT server increments the redirection counter for immediate forwardings. + 4. The MCPTT server sends a MCPTT private call forwarding request towards MCPTT client 1. +- NOTE: The target MCPTT ID is based on the entry in the user profile for call forwarding immediate. +5. The user at MCPTT client 1 is notified that a call forwarding is in process. + +6. MCPTT client 1 sends a MCPTT private call forwarding response back to the MCPTT server. +7. MCPTT client 1 sends a MCPTT private call request towards the MCPTT server that includes a call forwarding indication set to true. MCPTT client 1 and MCPTT client 3 set up a security association if end-to-end encryption is used for this call. +8. The MCPTT server verifies that client 1 is authorized to perform the MCPTT private call as a result of the MCPTT private call forwarding request. The MCPTT server verifies that the MCPTT private call request contains MCPTT client 3 that is the authorized target from step 4, and the forwarding indication is set to true. +9. The MCPTT server sends a MCPTT private call request towards MCPTT client 3. +10. Optionally the MCPTT server sends a MCPTT progress indication to MCPTT client 1. +11. The user at MCPTT client 3 is alerted. MCPTT client 3 sends an MCPTT ringing to the MCPTT server. This step is not required in case of automatic commencement mode. +12. The MCPTT server sends an MCPTT ringing to MCPTT client 1. This step is not required in case of automatic commencement mode. +13. MCPTT client 3 sends an MCPTT private call response to the MCPTT server. In manual commencement mode this occurs after the user at MCPTT client 3 has accepted the call. +14. The MCPTT server sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT client 3 has accepted the call. +15. The media plane for communication between MCPTT client 1 and MCPTT client 3 is established. + +##### 10.7.5.2.3 MCPTT private call forwarding no answer + +Figure 10.7.5.2.3-1 below illustrates the procedure of call forwarding no answer of MCPTT private calls. + +NOTE 1: The condition no answer covers both the cases in which the user does not answer because he is not reachable, as well as the case in which he is reachable but does not answer. + +Pre-conditions: + +1. MCPTT client 2 is authorized to use call forwarding and has call forwarding no reply enabled with the destination MCPTT client 3. +2. MCPTT client 1 is authorized to make private calls to MCPTT client 2. +3. No forwarding with no answer has so far occurred in this call. +4. MCPTT client 1 has the necessary security information to initiate a private call with MCPTT client 2 and MCPTT client 3 if end2end encryption is required for the private call. + +![Sequence diagram for Call forwarding no answer for private call. Lifelines: MCPTT Client 1, MCPTT Server, MCPTT Client 2, MCPTT Client 3. The sequence shows Client 1 sending a request to the server, which checks Client 2's status, sends a manual request to Client 2, receives no answer, verifies forwarding conditions, and then forwards the call to Client 3. The media plane is established between Client 1 and Client 3.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCPTT Client 1 + participant S as MCPTT Server + participant C2 as MCPTT Client 2 + participant C3 as MCPTT Client 3 + + Note right of S: 2. The MCPTT server checks if MCPTT client 2 has call forwarding no answer enabled. A timer with for the no answer timeout is started + Note right of S: 6. MCPTT client 2 does not answer within the specified time interval + Note right of S: 7. MCPTT server verifies that no other forwarding with the condition no answer has occured so far + Note right of S: 12. MCPTT server verifies that client 1 has been authorized to complete the call forwarding + + C1->>S: 1. MCPTT private call request + S->>C2: 3. MCPTT private call request (manual commencement) + C2-->>S: 4. MCPTT ringing + S-->>C1: 5. MCPTT ringing + S->>C1: 8. MCPTT private call forwarding request + Note left of C1: 9. Notify user + C1->>S: 10. MCPTT private call forwarding response + C1->>S: 11. MCPTT private call request + S->>C3: 13. MCPTT private call request + S-->>C1: 14. MCPTT progress indication + S-->>C3: 15. MCPTT ringing + S-->>C1: 16. MCPTT ringing + C3-->>S: 17. MCPTT private call response + S-->>C1: 18. MCPTT private call response + Note right of S: 19. Media Plane Established between client 1 and 3 + +``` + +Sequence diagram for Call forwarding no answer for private call. Lifelines: MCPTT Client 1, MCPTT Server, MCPTT Client 2, MCPTT Client 3. The sequence shows Client 1 sending a request to the server, which checks Client 2's status, sends a manual request to Client 2, receives no answer, verifies forwarding conditions, and then forwards the call to Client 3. The media plane is established between Client 1 and Client 3. + +**Figure 10.7.5.2.3-1: Call forwarding no answer for private call** + +1. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server. +2. The MCPTT server checks if MCPTT client 2 has call forwarding no answer enabled. If the MCPTT server detects that MCPTT client 2 is not registered, the procedure continues with step 7. Otherwise the MCPTT server starts a timer with the configured no answer timeout. +3. The MCPTT server sends a MCPTT private call request in manual commencement mode towards MCPTT client 2. If the MCPTT server detects that MCPTT client 2 is not reachable, the procedure continues with step 7. +4. The user at MCPTT client 2 is alerted. MCPTT client 2 sends an MCPTT ringing to the MCPTT server. +5. The MCPTT server sends an MCPTT ringing to the MCPTT client 1. This step is not required in case of automatic commencement mode. +6. The MCPTT server detects that MCPTT client 2 does not answer within the specified time interval. +7. The MCPTT server verifies that no other forwarding with the condition no answer has occurred so far. +8. The MCPTT server sends a MCPTT private call forwarding request towards MCPTT client 1. + +NOTE 2: The target MCPTT ID is based on the entry in the user profile for call forwarding no answer. + +9. The user at MCPTT client 1 is notified that a call forwarding is in process. +10. MCPTT client 1 sends a MCPTT private call forwarding response back to the MCPTT server. +11. MCPTT client 1 sends a MCPTT private call request towards the MCPTT server that includes a call forwarding indication set to true. MCPTT client 1 and MCPTT client 3 set up a security association if end-to-end encryption is used for this call. +12. The MCPTT server verifies that client 1 is authorized to perform the MCPTT private call as a result of the MCPTT private call forwarding request. The MCPTT server verifies that the MCPTT private call request contains MCPTT client 3 that is the authorized target from step 8, and the forwarding indication is set to true. +13. The MCPTT server sends a MCPTT private call request towards MCPTT client 3. +14. Optionally the MCPTT server sends a MCPTT progress indication to MCPTT client 1. +15. The user at MCPTT client 3 is alerted. MCPTT client 3 sends an MCPTT ringing to the MCPTT server. This step is not required in case of automatic commencement mode. +16. The MCPTT server sends an MCPTT ringing to MCPTT client 1. This step is not required in case of automatic commencement mode. +17. MCPTT client 3 sends an MCPTT private call response to the MCPTT server. In manual commencement mode this occurs after the user at MCPTT client 3 has accepted the call. +18. The MCPTT server sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT client 3 has accepted the call. +19. The media plane for communication between MCPTT client 1 and MCPTT client 3 is established. + +##### 10.7.5.2.4 Handling of multiple MCPTT private call forwardings + +If the target of the MCPTT private call forwarding has also any kind of MCPTT call forwarding activated generally the additional forwardings are performed sequentially. However, to avoid excessive numbers of forwardings and in particular to avoid indefinite loops in the forwarding a limit for immediate forwardings is defined in the service configuration. The MCPTT server keeps track of the number of forwardings, if the limit is exceeded, the call will be released. For forwarding no answer, only one forwarding is allowed, and in case of no answer on the first forwarding the MCPTT server will release the call. + +## 10.8 Simultaneous session for MCPTT calls (on-network) + +### 10.8.1 General + +An MCPTT client and MCPTT server may use a simultaneous session as defined in 3GPP TS 23.280 [16] for MCPTT calls. The MCPTT client becomes involved in a simultaneous session for MCPTT calls by inviting, joining or accepting more than one MCPTT call, or affiliating to a group. + +NOTE: An MCPTT client affiliating to multiple MCPTT groups with active calls will result in the MCPTT client being invited simultaneously to multiple MCPTT calls. + +The MCPTT client can also still handle multiple MCPTT calls in parallel at the same time i.e. using multiple dialogs. + +The simultaneous session is established during either an originating on-demand call establishment or during pre-established session establishment or a modification of an already established pre-established session or on-demand call. + +It is possible to change the prioritisation while the MCPTT client is engaged in multiple MCPTT calls. The setting of the priority can be made at MCPTT call setup or by performing a modification after the MCPTT call is established. This may result in more than one media bearer. + +## 10.9 Floor control + +### 10.9.1 Floor control for on-network MCPTT service + +#### 10.9.1.1 General + +The procedure is for providing a floor control to MCPTT UE in an on-network case and applies for both private call and group call. Floor control is performed by using floor control information flows between the floor participant and the floor control server. + +#### 10.9.1.2 Information flows for floor control for on-network + +##### 10.9.1.2.1 General + +When the floor control server receives a floor request from the floor participant, it decides whether to give a grant or not based on, e.g., the session status (i.e., whether the grant is given to another user or not), user profile, priority. The result is informed to the requesting floor participant. When the floor participant receives a floor granted message, it can send voice media over the uplink bearer established beforehand. The floor revoked message can be used as part of override. The floor queue status request can be used to know current position in the queue for floor. + +Some floor control information flows can also piggyback call control information flows to provide efficient call setup and clearing: + +- Call setup request is optionally carried in floor request (uplink) or floor taken (downlink, can be broadcast); and +- Call release request is optionally carried in floor release (uplink) or floor idle (downlink, can be broadcast). + +##### 10.9.1.2.2 Floor request + +Table 10.9.1.2.2-1 describes the information flow floor request, from the floor participant to the floor control server and from the floor control server to the floor control server, which is used to request the floor for media transfer. This information flow is sent in unicast to the floor control server. + +**Table 10.9.1.2.2-1: Floor request** + +| Information element | Status | Description | +|----------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Requester identity | +| Functional alias | O | Functional alias of the requester | +| Floor priority | M | Priority of the request | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Location Information | O | Location information | + +##### 10.9.1.2.3 Floor granted + +Table 10.9.1.2.3-1 describes the information flow floor granted, from the floor control server to the floor participant and from the floor control server to the floor control server or MC gateway server, which is used to indicate that a request for floor is granted and media transfer is possible. This information flow is sent in unicast (to the granted floor participant). + +**Table 10.9.1.2.3-1: Floor granted** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Granted party identity | +| Functional alias | O | Functional alias of the requester | +| Duration | M | The time for which the granted party is allowed to transmit | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +##### 10.9.1.2.4 Floor rejected + +Table 10.9.1.2.4-1 describes the information flow floor rejected, from the floor control server to the floor participant and from the floor control server to the floor control server or MC gateway server, which is used to indicate that a request for the floor is rejected. This information flow is sent in unicast (to the refused floor participant). + +**Table 10.9.1.2.4-1: Floor rejected** + +| Information element | Status | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID (see NOTE) | O | Rejected party identity | +| Functional alias (see NOTE) | O | Functional alias of the requester | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Rejection cause | O | Indicates the cause for floor rejection | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | +| NOTE: MCPTT ID is present, and functional alias may be present, in messages between the floor control servers in different MCPTT systems, and between floor control server and MC gateway server. | | | + +##### 10.9.1.2.5 Floor request cancel + +Table 10.9.1.2.5-1 describes the information flow floor request cancel, from the floor participant to the floor control server, which is used to request cancelling the floor request from the floor request queue. This information flow is sent in unicast to the floor control server. + +**Table 10.9.1.2.5-1: Floor request cancel** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity for the requester | +| Functional alias | O | Functional alias for the requester | +| List of MCPTT IDs | M | Target identity (Identities) whose floor request is to be cancelled | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 10.9.1.2.6 Floor request cancel response + +Table 10.9.1.2.6-1 describes the information flow floor request cancel response, from the floor control server to the floor control participant and from the floor control server to the floor control server or MC gateway server, which is used to indicate the response for the floor request cancellation. This information flow is sent in unicast. + +**Table 10.9.1.2.6-1: Floor request cancel response** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of party that initiated the cancellation request | +| Functional alias | O | Functional alias of the requester | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +##### 10.9.1.2.7 Floor request cancel notify + +Table 10.9.1.2.7-1 describes the information flow floor request cancel notify, from the floor control server to the floor control participant, which is used to indicate the floor request is cancelled by the administrator/floor control server. This information flow is sent in unicast or broadcast. + +**Table 10.9.1.2.7-1: Floor request cancel notify** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of the administrator | +| Functional alias | O | Functional alias of the administrator | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +##### 10.9.1.2.8 Floor idle + +Table 10.9.1.2.8-1 describes the information flow floor idle, from the floor control server to the floor participant, which is used to indicate that a session is in idle status, i.e. the floor is not granted to any party. This information flows is sent in unicast or broadcast. + +**Table 10.9.1.2.8-1: Floor idle** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +##### 10.9.1.2.9 Floor release + +Table 10.9.1.2.9-1 describes the information flow floor release, from the floor participant to the floor control server, which is used to indicate the media transfer is completed and floor is released. This information flow is sent in unicast to the floor control server. + +**Table 10.9.1.2.9-1: Floor release** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of party that initiated the cancellation request | +| Functional alias | O | Functional alias of the requester | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 10.9.1.2.9a Multi-talker floor release + +Table 10.9.1.2.9a-1 describes the information elements of floor release for multi-talker control, from the floor control server to the floor participants, which is used to indicate the media transfer is completed and floor is released. This information flow is sent in unicast from the floor control server. + +**Table 10.9.1.2.9a-1: Multi-talker floor release** + +| | | | +|---------------------------------------------------------------------------|---|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID (NOTE) | M | Identity of participant releasing the floor | +| List of functional aliases (NOTE) | O | Functional alias(es) of participant releasing the floor | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| NOTE: One or more functional aliases may be associated with the MCPTT ID. | | | + +##### 10.9.1.2.10 Floor taken + +Table 10.9.1.2.10-1 describes the information flow floor taken, from the floor control server to the floor participant, which is used to indicate the floor is granted to another MCPTT user. This information flows is sent in unicast or broadcast. + +**Table 10.9.1.2.10-1: Floor taken** + +| Information element | Status | Description | +|---------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity for the granted party | +| Functional alias | O | Functional alias for the granted party | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Permission to request the floor | O | Indicates whether receiving parties are allowed to request the floor or not (e.g. broadcast call). | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | +| Location Information | O | Location information | + +##### 10.9.1.2.10a Multi-talker floor taken + +Table 10.9.1.2.10a-1 describes the information elements of floor taken for multi-talker control, from the floor control server to the floor participant, which is used to indicate when the floor is simultaneously granted to multiple MCPTT users. The multi-talker floor taken is sent in unicast or broadcast. + +**Table 10.9.1.2.10a-1: Multi-talker floor taken** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| List of MCPTT IDs (NOTE) | M | Identity (identities) of the granted participant(s) | +| List of functional aliases (NOTE) | O | Functional alias(es) of the granted participant(s) | +| List of source identifiers (NOTE) | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | +| NOTE: One or more functional aliases and one source identifier may be associated with an MCPTT ID. | | | + +##### 10.9.1.2.11 Floor revoked + +Table 10.9.1.2.11-1 describes the information flow floor revoked, from the floor control server to the floor participant and from the floor control server to the floor control server or MC gateway server, which is used to indicate the floor is revoked from its current holder (the floor participant who was granted the floor). This information flows is sent in unicast (to the revoked floor participant). + +**Table 10.9.1.2.11-1: Floor revoked** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Revoked party identity | +| Functional alias | O | Functional alias of the requester | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +##### 10.9.1.2.12 Floor acknowledgement + +Table 10.9.1.2.12-1 describes the information flow floor acknowledgement, from the floor participant to the floor control server, which is used to provide an acknowledgement if the acknowledgement is required in the received floor control message. + +NOTE: The floor acknowledgement flow can be sent by the floor participant after each floor control information flow that includes an indication that an acknowledgement is required. The procedures defined in subclauses 10.9.1.3 to 10.9.1.5 do not explicitly illustrate all scenarios when floor acknowledgement can be used. + +**Table 10.9.1.2.12-1: Floor acknowledgement** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------| +| MCPTT ID | M | Identity of the sender. | +| Functional alias | O | Functional alias of the sender. | + +##### 10.9.1.2.13 Queue position request + +Table 10.9.1.2.13-1 describes the information flow queue position request, from the floor participant to the floor control server and from the floor control server to the floor control server or MC gateway server, which is used to request the position in the floor request queue. The MCPTT server and the MCPTT client support queuing of the floor control requests shall support this information flow. This information flow is sent in unicast to the floor control server. + +**Table 10.9.1.2.13-1: Queue position request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of party whose floor position is requested | +| Functional alias | O | Functional alias of the requester | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 10.9.1.2.14 Queue position info + +Table 10.9.1.2.14-1 describes the information flow queue position info, from the floor control server to the floor participant and from the floor control server to the floor control server or MC gateway server, which is used to indicate the floor request is queued and the queue position to the floor requesting UE. The MCPTT server and the MCPTT client support queuing of the floor control requests shall support this information flow. This information flow is sent in unicast (to the queued floor participant). + +**Table 10.9.1.2.14-1: Queue position info** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of party whose floor position is provided | +| Functional alias | O | Functional alias of the requester | +| Queue position info | M | Position of the queued floor request in the queue | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +##### 10.9.1.2.15 Unicast media stop request + +Table 10.9.1.2.15-1 describes the information flow unicast media stop request from the floor participant to the floor control server, which is used by the floor participant to indicate that the unicast media flow of the designated communication does not need to be sent to the MCPTT client. + +**Table 10.9.1.2.15-1: Unicast media stop request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of the requester | +| Functional alias | O | Functional alias for the requester | +| Source identifier | O | Identifies the communication whose media flow is to be stopped, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 10.9.1.2.16 Unicast media resume request + +Table 10.9.1.2.16-1 describes the information flow unicast media resume request from the floor participant to the floor control server, which is used by the floor participant to request that the unicast media flow of the designated communication is to be sent to the MCPTT client. + +**Table 10.9.1.2.16-1: Unicast media resume request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of the requester | +| Functional alias | O | Functional alias of the requester | +| Source identifier | O | Identifies the communication whose media flow is to be resumed, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +#### 10.9.1.3 Floor control within one MCPTT system + +##### 10.9.1.3.1 Floor request, floor granted and floor taken during an MCPTT session + +Figure 10.9.1.3.1-1 shows the high level procedure that the floor control is conducted for the MCPTT session already established between the floor participant and the floor control server. Only two UEs involved in the session are shown for the simplicity. + +Pre-condition: + +1. MCPTT session is established between MCPTT clients (client A and client B) and MCPTT server. + +![Sequence diagram illustrating floor control during an MCPTT session. Lifelines: Floor participant A, Floor control server, Floor participant B. The sequence shows steps 1 through 11b, including floor request, arbitration, granting, and queuing.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +MCPTT Service Provider + +``` + +sequenceDiagram + participant A as Floor participant A + participant S as Floor control server + participant B as Floor participant B + Note over A, S, B: 1. Floor control is established between floor participants and floor control server. + Note left of A: 2. User wants to talk + A->>S: 3. Floor request + Note right of S: 4. Based on arbitration result e.g., considering floor priority + S-->>A: 5a. Floor granted + S-->>B: 5b. Floor taken + A-->>S: 5c. Floor acknowledgement + B-->>S: 5d. Floor acknowledgement + Note left of A: 6a. Grant notification + Note right of B: 6b. Talker notification + Note over A, S, B: 7. Voice media + Note right of B: 8. User wants to talk + B->>S: 9. Floor request + Note right of S: 10. Floor request queued + S-->>B: 11a. Queue position info + B-->>S: 11b. Floor acknowledgement + +``` + +Sequence diagram illustrating floor control during an MCPTT session. Lifelines: Floor participant A, Floor control server, Floor participant B. The sequence shows steps 1 through 11b, including floor request, arbitration, granting, and queuing. + +**Figure 10.9.1.3.1-1: Floor request, floor granted, floor taken during an MCPTT session** + +1. The floor control is established between the floor participants and floor control server. It is assumed that the floor is now in idle status. +2. Floor participant A wants to send voice media over the session. +3. Floor participant A sends a floor request message to floor control server which includes floor priority and other information as necessary. +4. Floor control server makes the determination on what action (grant, deny, or queue) to take on the request based on criteria (e.g., floor priority, participant type) and determines to accept the floor request from floor participant A. The floor control server may limit the time a user talks (hold the floor) as allowed by the configuration. +- 5a. Floor control server responds with a floor granted message to floor participant A including the maximum floor granted duration e.g., if no other floor participant has the permission for transmission. +- 5b. Floor control server sends a floor taken message to the other floor participant (floor participant B) including information about who is granted the floor. +- 5c. Floor participant A sends a floor acknowledgement if indicated to do so by the floor granted message. +- 5d. Floor participant B sends a floor acknowledgement if indicated to do so by the floor taken message. + +- 6a. The floor granted shall cause the user of UE A where the floor participant A is located to be notified. +- 6b. The receipt of the floor taken may be used to inform the user of UE B where the floor participant B is located. +- 7. Floor participant A starts sending voice media over the session established beforehand. + +NOTE: Voice media can continue to be sent while steps 8 through 11 occur. + +- 8. Suppose there are one or more users requesting to talk at this time, the floor request(s) are queued as decided by floor control server e.g., based on floor priority. +- 9. Floor participant B sends a floor request message. +- 10. Floor control server queues the request of floor participant B. +- 11a. Floor control server sends queue position info to floor participant B. +- 11b. Floor participant B sends a floor acknowledgement if indicated to do so by the queue position info message. + +##### **10.9.1.3.1a Floor request, floor granted and multi-talker floor taken during an MCPTT session enhanced with multi-talker control** + +Figure 10.9.1.3.1a-1 shows the high level procedure that allows several participants to talk simultaneously in a MCPTT session already established between the floor participant and the floor control server. Three UEs involved in the session are shown for simplicity. + +Pre-conditions: + +- 1. The MCPTT group is configured to support multi-talker control and audio mixing by the network is applied. +- 2. MCPTT session is established between MCPTT clients (client A, client B and client C) and MCPTT server. +- 3. Participants and A and B have the permission to talk to all other participants and the floor is granted to floor participant B. + +![Sequence diagram showing the interaction between MCPTT client A (New Talker), MCPTT server, MCPTT client B (Talker), and MCPTT client C (Listener). The diagram illustrates the process of floor request, floor granted, and multi-talker floor taken. It starts with voice media from B to server and then to A and C. When A wants to talk, it sends a floor request. The server arbitrates and grants the floor to B (multi-talker floor taken). Notifications are sent to A, B, and C. Finally, voice media from both A and B are sent to the server and then mixed and sent to C.](dc37a040cf9e2add7488c7c37cbf3687_img.jpg) + +``` + +sequenceDiagram + participant ClientA as MCPTT client A (New Talker) + participant Server as MCPTT server + participant ClientB as MCPTT client B (Talker) + participant ClientC as MCPTT client C (Listener) + + Note left of ClientA: 2. User A wants to talk + ClientB->>Server: 1. Voice media (B) + Server->>ClientA: 1. Voice media (B) + Server->>ClientC: 1. Voice media (B) + ClientA->>Server: 3. Floor request + Note right of Server: 4. Based on arbitration result e.g., considering floor priority, maximum number of simultaneous talkers + Server->>ClientA: 5a. Floor granted + Server->>ClientB: 5b. Multi-talker floor taken + Server->>ClientC: 5c. Multi-talker floor taken + Note left of ClientA: 6a. Grant notification + Note right of ClientB: 6b. Multi-talker floor taken notification without floor revoked + Note right of ClientC: 6c. Multi-talker floor taken notification + ClientA->>Server: 7. Voice media (A) + ClientB->>Server: 7. Voice media (B) + Server->>ClientC: 7. Voice media (A and B) + +``` + +Sequence diagram showing the interaction between MCPTT client A (New Talker), MCPTT server, MCPTT client B (Talker), and MCPTT client C (Listener). The diagram illustrates the process of floor request, floor granted, and multi-talker floor taken. It starts with voice media from B to server and then to A and C. When A wants to talk, it sends a floor request. The server arbitrates and grants the floor to B (multi-talker floor taken). Notifications are sent to A, B, and C. Finally, voice media from both A and B are sent to the server and then mixed and sent to C. + +**Figure 10.9.1.3.1a-1: Floor request, floor granted and multi-talker floor taken during an MCPTT session** + +- 1. Floor participant B is talking and is sending the voice media. + +2. Floor participant A wants to send voice media over the session. +3. Floor participant A sends a floor request message to the floor control server which includes the necessary information, e.g. floor priority. +4. Based on applicable criteria (e.g. floor priority, participant type, allowance to transmit, maximum number of simultaneous talkers) floor control server determines what action (grant, deny, or queue) shall be applied to the request. In this case, the floor request from floor participant A will be accepted. Simultaneous floor requests to transmit are handled in a sequential order. Based on the group configuration repository data, the floor control server may limit the time a floor participant is allowed to talk. +- 5a. Floor control server responds with a floor granted message to floor participant A. +- 5b. Floor control server sends a multi-talker floor taken message to floor participant B. +- 5c. Floor control server sends a multi-talker floor taken message to floor participant C. +- 5d. Floor control server may send a multi-talker floor taken message to floor participant A. +- 6a. The floor granted shall cause the user of UE A, where the floor participant A is located, to be notified. +- 6b. The multi-talker floor taken shall inform the user of UE B, that the floors are granted to other floor participants, but the floor is not revoked. +- 6c. The multi-talker floor taken shall inform the user of UE C floor participants list the floor are currently granted to. +7. Floor participant A starts sending voice media over the session established beforehand, i.e. participants A and B receive and transmit voice media; participant C only receives voice media. + +NOTE: Floor control is independent from whether audio mixing is performed by the MCPTT server or by the UE. + +##### 10.9.1.3.2 Floor override + +###### 10.9.1.3.2.1 Floor override using floor revoked (also floor rejected) during an MCPTT session + +Figure 10.9.1.3.2.1-1 shows the high level procedure that the floor control is conducted for the MCPTT session already established between the floor participant (with floor granted to floor participant B) and the floor control server (with an override based on priority). Only two UEs involved in the session are shown for the simplicity. + +![Sequence diagram illustrating floor override using floor revoked (also floor rejected) during an MCPTT session. The diagram shows interactions between Floor participant A, Floor control server, and Floor participant B. The process starts with an established session where floor is granted to participant B. Participant A then requests the floor, which is granted after arbitration, revoking the floor from participant B. Participant A then transmits voice media. Later, participant B requests the floor, which is rejected, and participant A continues to transmit voice media.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +Home MCPTT Service Provider + +``` + +sequenceDiagram + participant A as Floor participant A + participant S as Floor control server + participant B as Floor participant B + Note over A, B: 1. Session is established, Floor control is established between floor participant and floor control server. Floor granted to floor participant B + Note left of A: 2. User wants to talk + A->>S: 3. Floor request + Note over S: 4. Based on arbitration result e.g., considering priority + S->>B: 4. Floor revoked + Note right of B: 5. Revoke notification + S->>A: 6. Floor granted + S->>B: 6. Floor Taken + Note left of A: 7. Grant notification + Note right of B: 7. Talker notification + A->>S: 8. Voice media + S->>B: 8. Voice media + Note right of B: 9. User wants to talk + B->>S: 10. Floor request + Note over S: 11. Based on arbitration result e.g., considering priority + S->>B: 12. Floor rejected + Note right of B: 13. Reject notification + +``` + +Sequence diagram illustrating floor override using floor revoked (also floor rejected) during an MCPTT session. The diagram shows interactions between Floor participant A, Floor control server, and Floor participant B. The process starts with an established session where floor is granted to participant B. Participant A then requests the floor, which is granted after arbitration, revoking the floor from participant B. Participant A then transmits voice media. Later, participant B requests the floor, which is rejected, and participant A continues to transmit voice media. + +**Figure 10.9.1.3.2.1-1: Floor override using floor revoked (also floor rejected) during an MCPTT session** + +1. It is assumed that floor participant B has been given floor and is transmitting voice media. +2. Floor participant A having a priority which is relatively higher than that of floor participant B wants to send voice media over the session. +3. Floor participant A sends a floor request message to the floor control server. +4. The floor control server determines to accept the floor request from floor participant A based on arbitration result e.g., according to the priority information that is received in the floor request message. The floor control server sends a floor revoked message to floor participant B stopping the voice media transmission from floor participant B. +5. The user of floor participant B may be notified that the floor is revoked. +6. The Floor control server sends a floor granted message to floor participant A, while sending a floor taken message to floor participant B with information of who is granted the floor. +7. The user of floor participant A may be notified that he is granted the floor. Similarly, the user of floor participant B may be notified who is granted the floor. +8. Floor participant A starts sending voice media over the session established beforehand. +9. Now floor participant B may want the floor to start sending voice media. +10. Floor participant B sends a floor request message to floor control server which may include priority information. + +11. Floor control server determines whether to accept the floor request from floor participant B based on arbitration result e.g., according to the priority information that is received in the floor request message. +12. The floor control server responds with a floor rejected message to floor participant B. +13. Floor participant B may be notified that he is rejected. + +###### 10.9.1.3.2.2 Floor override without using floor revoked during an MCPTT session + +Figure 10.9.1.3.2.2-1 shows the high level procedure that the floor control is conducted for the MCPTT session already established between the floor participants (with floor granted to floor participant B) and the floor control server (with an override based on priority and configured to permit the transmission of the overridden floor participant B to continue). Only two UEs involved in the session are shown for the simplicity. + +###### Pre-conditions + +- The floor control server has been configured to support override. +- The override supported in this case permits both the overridden floor participant and the overriding floor participant to be transmitting. + +![Sequence diagram illustrating floor override during an MCPTT session. The diagram shows interactions between Floor participant A, Floor control server, and Floor participant B. The process starts with an established session where the floor is granted to participant B. Participant A then sends a floor request. The server arbitrates and grants the floor to A while taking the floor from B. Both A and B then receive notifications, and voice media from both participants is transmitted.](39536a630fa74c3bcfd1670ee2152809_img.jpg) + +``` + +sequenceDiagram + participant A as Floor participant A + participant S as Floor control server + participant B as Floor participant B + Note over A, S, B: 1. Session is established. Floor control is established between floor participants and floor control server. Floor granted to floor participant B. + Note left of A: 2. User wants to talk + A->>S: 3. Floor request + Note right of S: 4. Based on arbitration result e.g., considering floor priority + S->>A: 5a. Floor granted + S->>B: 5b. Floor taken + Note left of A: 6a. Grant notification + Note right of B: 6b. Override notification + Note over A, B: 7. Voice media + +``` + +Sequence diagram illustrating floor override during an MCPTT session. The diagram shows interactions between Floor participant A, Floor control server, and Floor participant B. The process starts with an established session where the floor is granted to participant B. Participant A then sends a floor request. The server arbitrates and grants the floor to A while taking the floor from B. Both A and B then receive notifications, and voice media from both participants is transmitted. + +**Figure 10.9.1.3.2.2-1: Floor override (overridden continues to transmit) during an MCPTT session** + +1. It is assumed that floor participant B has been given the floor and is transmitting voice media. +2. Floor participant A having a floor priority which is relatively higher than that of floor participant B wants to send voice media over the session. +3. Floor participant A sends a floor request message to the floor control server. +4. The floor control server determines to accept the floor request from floor participant A based on arbitration result e.g., according to the floor priority information that is received in the floor request message. +- 5a. Floor control server responds with a floor granted message to floor participant A. +- 5b. Floor control server sends a floor taken message to the other floor participants (including floor participant B). Floor participant B continues transmitting the (overridden) voice media transmission. + +NOTE 1: All other floor participants (not shown) that are part of this group call receive a floor taken message, so that the other floor participants learn who the newly granted talker (overriding) is. + +- 6a. The floor granted causes the user of floor participant A to be notified. +- 6b. The user of floor participant B is notified of the status that the floor is now taken by floor participant A. +7. Floor participant A (overriding) starts sending voice media over the session established beforehand. + +NOTE 2: Floor participant B is still sending voice (overridden). The list of floor participants that receive the overriding, overridden, or both transmissions is based on configuration. + +###### 10.9.1.3.2.3 Floor override using floor revoked (also floor rejected) during an MCPTT session enhanced with multi-talker control + +Figure 10.9.1.3.2.3-1 shows the high-level procedure that the floor control allows several participants to talk simultaneously in a MCPTT session already established between the floor participant (with floor granted to floor participant B) and the floor control server. Only two UEs involved in the session are shown for the simplicity. + +Pre-conditions: + +1. The MCPTT group is configured to support multi-talker control. +2. MCPTT session is established between MCPTT clients (client A, client B and client C) and MCPTT server. +3. The maximum number of simultaneous talkers is set to 2. +4. The floor priority of floor participant A is higher than of floor participant B. +5. The floor is granted to floor participant B and floor participant C. + +![Sequence diagram illustrating floor override using floor revoked (also floor rejected) during an MCPTT session. The diagram shows interactions between MCPTT client A (New Talker), MCPTT server, MCPTT client B (Talker), and MCPTT client C (Talker).](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +``` + +sequenceDiagram + participant Client A as MCPTT client A (New Talker) + participant Server as MCPTT server + participant Client B as MCPTT client B (Talker) + participant Client C as MCPTT client C (Talker) + + Note right of Client B: 1. Voice media (B) + Note right of Client C: 1. Voice media (C) + Server-->Client A: 1. Voice media (B and C) + Note right of Client B: 1. Voice media (B) + Note right of Client C: 1. Voice media (C) + + Note left of Client A: 2. User A wants to talk + Client A->>Server: 3. Floor request + Note right of Server: 4. Based on arbitration result e.g., considering floor priority, maximum number of simultaneous talkers + Server-->>Client B: 5. Floor revoked + Note right of Client B: 6. Revoke notification + + Server-->>Client A: 7. Floor granted + Note left of Client A: 8. Grant notification + Server-->>Client B: 7. Multi-talker floor taken + Note right of Client B: 8. Multi-talker notification + Server-->>Client C: 7. Multi-talker floor taken + Note right of Client C: 8. Multi-talker notification + + Note right of Client A: 9. Voice media (A) + Note right of Client B: 9. Voice media (C) + Note right of Client C: 9. Voice media (A and C) + Note right of Client A: 9. Voice media (C) + Note right of Client B: 9. Voice media (A) + Note right of Client C: 9. Voice media (A) + + Note right of Client B: 10. User B wants to talk + Client B->>Server: 11. Floor request + Note right of Server: 12. Based on arbitration result e.g., considering floor priority, maximum number of simultaneous talkers + Server-->>Client B: 13. Floor rejected + Note right of Client B: 14. Reject notification + +``` + +Sequence diagram illustrating floor override using floor revoked (also floor rejected) during an MCPTT session. The diagram shows interactions between MCPTT client A (New Talker), MCPTT server, MCPTT client B (Talker), and MCPTT client C (Talker). + +**Figure 10.9.1.3.2.3-1: Floor override using floor revoked (also floor rejected) during an MCPTT session** + +1. Floor participant B and floor participant C are sending voice media over the session established. +2. Floor participant A wants to send voice media over the session. +3. Floor participant A wants to talk (i.e. send voice media) over the session. Floor participant A sends a floor request message to the floor control server. +4. Based on an arbitration result (e.g. per the priority information that is received in the floor request message), the floor control server determines to accept the floor request from floor participant A. The maximum number of simultaneous talkers in the MCPTT group has been reached, the floor control server decides to apply the override mechanism. +5. The floor control server sends a floor revoked message to floor participant B stopping the voice media transmission of floor participant B. +6. The user of floor participant B may be notified that the floor is revoked. +7. The Floor control server sends a floor granted message to floor participant A, while sending a multi-talker floor taken message to floor participant B and floor participant C including the information to whom the floor has been granted. +8. The user of floor participant A may be notified that the floor has been granted to him. Similarly, the user of floor participant B and floor participant C may be notified to whom the floor has been granted. + +9. Floor participant A starts sending voice media over the session established beforehand. +10. Now floor participant B may want the floor to start sending voice media. +11. Floor participant B sends a floor request message to floor control server that may include participant priority information. +12. Based on arbitration result, e.g. per the priority information that is received in the floor request message, and if the number of MCPTT Users has already reached the maximum number of simultaneous talkers in the group, the floor control server determines whether to accept or reject the floor request from floor participant B. Due to lower priority of participant B and the applicable limitation of simultaneous talkers, the floor control server rejects the floor request. +13. The floor control server responds with a floor rejected message to floor participant B. +14. Floor participant B may be notified about the floor rejection. + +NOTE: Floor control procedure is independent from whether audio mixing is performed by the MCPTT server or by the UE. + +###### 10.9.1.3.2.4 Floor release during an MCPTT session enhanced with multi-talker control + +Figure 10.9.1.3.2.4-1 shows the high-level procedure where the floor controller allows a participant to release the floor while other participants continue to talk simultaneously in a MCPTT session already established between the floor participants and the floor control server. Only three UEs involved in the session are shown for simplicity. + +Pre-conditions: + +1. The MCPTT group is configured to support multi-talker control and audio mixing by the network is applied. +2. MCPTT session is established between MCPTT clients (client A, client B, and client C) and the MCPTT server. +3. Participants A, B, and C have the permission to talk to all other participants, and the floor is granted to floor participants A, B, and C. + +![Sequence diagram illustrating floor release during an MCPTT session. Lifelines: MCPTT client A (Talker), MCPTT server, MCPTT client B (Talker), MCPTT client C (Talker). The sequence shows voice media exchange, a floor release request from A, server notifications to B and C, and subsequent voice media exchange between B and C.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +``` + +sequenceDiagram + participant A as MCPTT client A (Talker) + participant S as MCPTT server + participant B as MCPTT client B (Talker) + participant C as MCPTT client C (Talker) + + Note left of A: Error! No + Note right of C: Error! No text of specified style in + + A->>S: 1. Voice media (A) + S->>B: 1. Voice media (B) + S->>C: 1. Voice media (C) + S->>A: 1. Voice media (B and C) + S->>B: 1. Voice media (A and B) + Note left of A: 2. User A stops talking + A->>S: 3. Floor release + S->>B: 4. Multi-talker floor release + S->>C: 4. Multi-talker floor release + Note right of B: 4a. Multi-talker floor release notification + Note right of C: 4a. Multi-talker floor release notification + S->>B: 5. Voice media (B) + S->>C: 5. Voice media (C) + S->>A: 5. Voice media (B and C) + S->>B: 5. Voice media (B) + S->>C: 5. Voice media (C) + +``` + +Sequence diagram illustrating floor release during an MCPTT session. Lifelines: MCPTT client A (Talker), MCPTT server, MCPTT client B (Talker), MCPTT client C (Talker). The sequence shows voice media exchange, a floor release request from A, server notifications to B and C, and subsequent voice media exchange between B and C. + +**Figure 10.9.1.3.2.4-1: Floor release during an MCPTT session** + +1. Floor participants A, B and C are sending voice media over the established session. +2. User A stops talking and wants to stop sending voice media over the session. +3. Floor participant A sends a floor release message to the floor control server. +4. The floor control server accepts the floor release from floor participant A and sends a multi-talker floor release message to floor participant B and floor participant C. +- 4a. The users of floor participant B and floor participant C may be notified that floor participant A has released the floor. +5. Floor participants B and C continue sending voice media over the established session. + +NOTE: Floor control procedures are independent from whether audio mixing is performed by the MCPTT server or by the UE. + +##### 10.9.1.3.3 Queue position during an MCPTT session + +Figure 10.9.1.3.3-1 shows the high level procedure that the floor control is conducted for the MCPTT session already established between MCPTT clients (with floor granted to floor participant B) and server (with an override based on priority at floor control server). Only two UEs involved in the session are shown for the simplicity. + +![Sequence diagram showing queue status during an MCPTT session. Lifelines: Floor participant A, Floor control server, Floor participant B. The diagram shows a session establishment where floor participant B is granted the floor and many others, including A, are queued. Floor participant A then sends a queue position request to the server, which responds with the current queue position, informing the user.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +MCPTT Service Provider + +``` + +sequenceDiagram + participant A as Floor participant A + participant S as Floor control server + participant B as Floor participant B + Note right of B: 1. Session is established. Floor control is established between floor participants and floor control server. Floor granted to floor participant B. Many floor participants requested floor (including floor participant A) which got queued. + Note left of A: 2. User wants to know queue position + A->>S: 3. Queue position request + Note right of S: 4. Current queue position for floor participant A + S->>A: 5. Queue position info + Note left of A: 6. User informed about queue position + +``` + +Sequence diagram showing queue status during an MCPTT session. Lifelines: Floor participant A, Floor control server, Floor participant B. The diagram shows a session establishment where floor participant B is granted the floor and many others, including A, are queued. Floor participant A then sends a queue position request to the server, which responds with the current queue position, informing the user. + +**Figure 10.9.1.3.3-1: Queue status during an MCPTT session** + +1. It is assumed that floor participant B has been given a floor granted and is transmitting voice media. There are several other floor participants (including floor participating A) requesting floor which get queued at the floor control server. +2. Floor participant A would like to know its current position in the floor request queue. +3. Floor participant A sends a queue position request message to the floor control server. +4. Floor control server determines the current queue position of floor participant A from the floor request queue. +5. Floor control server responds with the current position in queue position info message. +6. User at floor participant A is informed about the current queue position. + +##### 10.9.1.3.4 Floor request cancellation from the floor request queue + +###### 10.9.1.3.4.1 Floor request cancellation from the queue – MCPTT user initiated + +Figure 10.9.1.3.4.1-1 illustrates the procedure for floor request cancellation from the floor queue initiated by the MCPTT user. The MCPTT user may be an authorized user who has rights to cancel the floor requests of other MCPTT users, whose floor requests are in floor control queue. + +Pre-conditions: + +- It is assumed that floor participant B has been granted the floor and is transmitting voice media. There are several other floor participants (including floor participant A and floor participant C) requesting the floor which have been queued at the floor control server. + +![Sequence diagram for floor request cancellation from queue initiated by MCPTT user. The diagram shows four lifelines: Floor participant A (or MCPTT Dispatcher), Floor control server, Floor participant B, and Floor participant C. A box at the top indicates that floor control is established, floor is granted to participant B, and requests from A and C are in the queue. The sequence of messages is: 1. User wants to cancel a floor request (internal to participant A), 2. Floor request cancel (A to server), 3. Authorization check and remove from queue (internal to server), 4. Floor request cancel notify (server to participant C), 5. Floor request cancel response (server to participant A).](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +Home MCPTT service provider + +``` + +sequenceDiagram + participant A as Floor participant A (or MCPTT Dispatcher) + participant S as Floor control server + participant B as Floor participant B + participant C as Floor participant C + + Note right of A: Floor control established between floor participants and floor control server. Floor is granted to participant B, and floor requests of floor participant A and floor participant C are in the floor queue. + + Note left of A: 1. User wants to cancel a floor request from the floor request queue + A->>S: 2. Floor request cancel + Note right of S: 3. Authorization check, and remove floor request from the floor queue + S-->>C: 4. Floor request cancel notify + S-->>A: 5. Floor request cancel response + +``` + +Sequence diagram for floor request cancellation from queue initiated by MCPTT user. The diagram shows four lifelines: Floor participant A (or MCPTT Dispatcher), Floor control server, Floor participant B, and Floor participant C. A box at the top indicates that floor control is established, floor is granted to participant B, and requests from A and C are in the queue. The sequence of messages is: 1. User wants to cancel a floor request (internal to participant A), 2. Floor request cancel (A to server), 3. Authorization check and remove from queue (internal to server), 4. Floor request cancel notify (server to participant C), 5. Floor request cancel response (server to participant A). + +**Figure 10.9.1.3.4.1-1: Floor request cancellation from queue initiated by MCPTT user** + +1. The floor participant A wants to remove the floor request from the floor request queue. If floor participant A is an authorized MCPTT user with the rights to cancel another MCPTT user's floor request, the authorized MCPTT user may request floor request cancellation for one or more floor participants, whose floor request needs to be removed from the floor queue. +2. The floor participant A sends a floor request cancel (initiating MCPTT ID) message to the floor control server. If the floor participant A wants to remove the floor request(s) of other participant(s), the target participant(s)' MCPTT ID should be included in this message. +3. The floor control server shall check whether the requesting floor participant has authorization to cancel the floor request(s). If authorized, the floor request(s) will be removed from the floor request queue. When current transmission is completed, floor control server will process the floor request from the updated floor request queue. +4. If the floor request cancel in step 3 is sent by an authorized user (e.g., dispatcher) to cancel the floor request(s) of other participant(s) from the floor request queue, the floor request cancel notify message is sent to the floor participant whose floor request was cancelled from the floor queue. +5. The floor control server provides a floor request cancel response to the floor participant A when the floor cancellation is completed. Optionally, the new queue position information may be notified to the floor participants whose floor requests are in the floor request queue (not shown in the figure). + +###### 10.9.1.3.4.2 Floor request cancellation from the queue - floor control server initiated + +Figure 10.9.1.3.4.2-1 illustrates the procedure for floor request cancellation from the queue initiated by the floor control server. Only two UEs involved in the session are shown for the simplicity. + +Pre-conditions: + +- It is assumed that floor participant B has been granted the floor and is transmitting voice media. There are several other floor participants (including floor participant A and participant C) requesting the floor which have been queued at the floor control server. + +![Sequence diagram showing floor request cancellation from queue initiated by floor control server. The diagram shows three participants: Floor participant A, Floor control server, and Floor participant C. A message box indicates that floor control is established, the floor is granted to participant B, and requests from A and C are queued. The floor control server then performs three steps: 1. Remove the floor request from the floor request queue based on policy; 2. Send a floor request cancel notify to participant A; 3. Send queue position info to participant C.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +Home MCPTT service provider + +``` + +sequenceDiagram + participant A as Floor participant A + participant FCS as Floor control server + participant C as Floor participant C + Note right of FCS: Floor control established between floor participants and floor control server. Now floor is granted to participant B, and floor participant A and participant C have sent floor requests being put into queue. + FCS->>A: 2.Floor request cancel notify + FCS-->>C: 3.Queue position info + Note left of FCS: 1.Remove the floor request from the floor request queue based on policy + +``` + +Sequence diagram showing floor request cancellation from queue initiated by floor control server. The diagram shows three participants: Floor participant A, Floor control server, and Floor participant C. A message box indicates that floor control is established, the floor is granted to participant B, and requests from A and C are queued. The floor control server then performs three steps: 1. Remove the floor request from the floor request queue based on policy; 2. Send a floor request cancel notify to participant A; 3. Send queue position info to participant C. + +**Figure 10.9.1.3.4.2-1: Floor request cancellation from queue initiated by floor control server** + +1. The floor control server removes the floor request from the floor request queue based on policy. e.g., expiration of a timer. In the case when floor control server receives repeated floor requests from a floor participant while the floor is occupied, the new floor request is accepted and added into the floor queue and the existing/former floor request is removed from the floor queue or the new floor request is rejected and the existing/former floor request of this floor participant is retained in the floor request queue. +2. The floor control server sends a floor request cancel notify to the floor participant(s) whose floor request is removed from the floor request queue. +3. Optionally, the newly queue position information is notified to the other floor participants whose floor requests are queued. + +#### 10.9.1.4 Floor control involving groups from multiple MCPTT systems + +##### 10.9.1.4.1 Partner MCPTT system routes all floor control messages to primary MCPTT system's floor control server + +The MCPTT users belonging to different groups in multiple MCPTT systems will participate in MCPTT media services (group communication, private calls, etc.) in scenarios like group hierarchies and temporary groups formed by group regroup. In this service delivery model involving multiple groups from different MCPTT systems, the floor control arbitration resides with the primary MCPTT system. This is determined in the group call setup stage. The MCPTT users of groups involved in the call session will transmit their floor control messages through the partner MCPTT systems to which they belong. In this scenario, the partner MCPTT systems request the floor control for its MCPTT user(s) from the floor control server of the primary MCPTT system. The protocol used for media plane signalling is non-SIP like RTCP. + +Figure 10.9.1.4.1-1 describes the procedure for floor control involving groups from multiple MCPTT systems. + +Pre-conditions: + +1. The security aspects of sharing the user information between primary and partner MCPTT systems shall be governed as per the service provider agreement between them. In this case, we consider the partner MCPTT system does not share all information of their users' to the primary MCPTT system (public information would still need to be shared). +2. The group 1 is hosted by primary MCPTT system and group 2 and 3 are hosted by the partner MCPTT system. +3. The floor participant 1 corresponds to the MCPTT user of group 1. The floor participant 2 corresponds to the MCPTT user of group 2. The floor participant 3 corresponds to the MCPTT user of group 3. The floor control server 1 belongs to primary MCPTT system. The floor control server 2 belongs to partner MCPTT system. + +4. The floor control server 1 is the floor arbitrator of the MCPTT group call. The floor control server 2 routes all floor control messages to and from the floor participants 2 and 3 and then floor control server 1. + +![Sequence diagram illustrating floor control (partner MCPTT system forwarding) involving groups from multiple MCPTT systems. The diagram shows interactions between Floor participant 1 (primary), Floor control server 1 (primary), Floor control server 2 (partner), Floor participant 2 (partner), and Floor participant 3 (partner).](74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg) + +MCPTT Service Provider + +``` + +sequenceDiagram + participant FP1 as Floor participant 1 (primary) + participant FCS1 as Floor control server 1 (primary) + participant FCS2 as Floor control server 2 (partner) + participant FP2 as Floor participant 2 (partner) + participant FP3 as Floor participant 3 (partner) + + Note over FP1, FP3: 1. Session is established. Floor control is established among floor participants and floor control servers. + + Note left of FP1: 2. User wants to talk + Note right of FP2: 2. User wants to talk + Note right of FP3: 2. User wants to talk + + FP1->>FCS1: 3. Floor request + FCS1->>FCS2: 4. Floor request + FCS2->>FCS1: 3. Floor request + FCS2->>FCS1: 4. Floor request + + Note over FCS1, FCS2: 5. Group call arbitration according to policy (floor priority or order) + + FCS1->>FCS2: 6. Floor granted + FCS2->>FP2: 7. Floor granted + + Note right of FP2: 8. Grant notification + + Note left of FCS1: 9a.1. Floor rejected + FCS1->>FCS2: 9a.2. Floor rejected + Note right of FCS2: 9a.3. Reject notification + Note right of FP3: 9a.3. Reject notification + + Note left of FCS1: 9b.1. Queue position info + FCS1->>FCS2: 9b.2. Queue position info + Note right of FCS2: 9b.3. User informed about queue position + Note right of FP3: 9b.3. User informed about queue position + + Note left of FP1: 10a.1. Floor rejected + Note left of FP1: 10a.2. Reject notification + Note left of FP1: 10b.1. Queue position info + Note left of FP1: 10b.2. User informed about queue position + + FP1->>FCS1: 11a. Floor taken + FCS1->>FCS2: 11b.1. Floor taken + FCS2->>FP2: 11b.2. Floor taken + + Note left of FP1: 12. Talker notification + Note right of FP3: 12. Talker notification + + Note over FP1, FP3: 13. Voice media + +``` + +Sequence diagram illustrating floor control (partner MCPTT system forwarding) involving groups from multiple MCPTT systems. The diagram shows interactions between Floor participant 1 (primary), Floor control server 1 (primary), Floor control server 2 (partner), Floor participant 2 (partner), and Floor participant 3 (partner). + +**Figure 10.9.1.4.1-1: Floor control (partner MCPTT system forwarding) involving groups from multiple MCPTT systems** + +1. An MCPTT group call involving group1, group 2 and group 3 is setup and active. +2. The MCPTT users want to talk. +3. The floor participants initiate a floor request to the floor control server of their corresponding MCPTT systems. (The requests may or may not occur at the same time). + +4. If only one floor request is received, or floor control server 2 handles the floor request sequentially, there is no arbitration performed and the corresponding floor request is forwarded to the floor control server 1. If the floor control server 2 receives multiple floor requests at the same time or during an interval, then it forwards the floor requests to the floor control server 1 (floor arbitrator for the MCPTT group call). As the floor participant information shall not be exposed, the floor priority related information or/and group information to be used by floor control server 1 should be included in the forwarded request. + 5. The floor control server 1 performs floor arbitration for the MCPTT group call and determines the floor request to be accepted. + 6. If the floor request from floor participant 2 of the partner MCPTT system is accepted, a floor granted is sent with permission to talk. The floor control messages from floor control server 1 are routed to floor participant 2 via the floor control server 2. + 7. When the floor control server 2 (partner) receives the floor granted, the floor control server 2 sends a floor granted message on to floor participant 2. + 8. The floor granted shall cause the user of the UE where the floor participant 2 is located to be notified. + 9. The primary floor control server 1 may (9a.1) send a floor rejected message, or (9b.1) send a queue position info message for each non-granted received floor requests forwarded from the floor control server 2 (partner). When the floor control server 2 (partner) receives the floor rejected message, then the floor control server 2 (partner) (9a.2) sends a floor rejected message to the appropriate floor participant. When the floor control server 2 (partner) receives the queue position info, then the floor control server 2 (partner) (9b.2) sends a queue position info message to the appropriate floor participant. +- 10a.1 If floor control server 1 rejects the floor request from floor participant 1, then a floor reject message is sent. + - 10a.2 Upon this being received the user of the UE where floor participant 1 is located may be notified. + - 10b.1 If floor control server 1 supports floor queue, queue position info message is sent to the floor participant 1. + - 10b.2 Upon this being received the user of the UE where floor participant 1 is located may be notified. +- NOTE 1: Steps 10a.1 through 10b.2 are optional as indicated by the dashed box enclosing them. However if this box is implemented then either information flow 10a or 10b would occur. +11. Since the floor is granted to floor participant 2 of the partner MCPTT system, then a floor taken is sent to all other floor participants ((11a) floor participant 1 and (11b.1) to floor control server 2 (partner) for forwarding to (11b.2) floor participant 3. + 12. The receipt of the floor taken may be used to inform the users of the UEs where the floor participant entity 1 and floor participant 3 are located to be notified. + 13. Upon successful floor granted, the group call media transmission occurs. + +NOTE 2: The media flow between the media gateways of primary and partner MCPTT systems have not been depicted in the figure for clarity. + +##### 10.9.1.4.2 Partner MCPTT system performs filtering of floor control messages entering and leaving the partner MCPTT system + +The MCPTT users belonging to different groups in multiple MCPTT systems will participate in MCPTT media services (group communication, private calls, etc.) in scenarios like group hierarchies and temporary groups formed by group regroup. In this service delivery model involving multiple groups from different MCPTT systems, the floor control arbitration resides with the primary MCPTT system. This is determined in the group call setup stage. The MCPTT users of groups involved in the call session will transmit their floor control messages through the partner MCPTT systems to which they belong. In this scenario, the partner MCPTT system filters its MCPTT users' floor requests before communicating with the floor control server of the primary MCPTT system. The protocol used for media plane signalling is non-SIP like RTCP. + +Figure 10.9.1.4.2-1 describes the procedure for floor control involving groups from multiple MCPTT systems. + +Pre-conditions: + +1. The security aspects of sharing the user information between primary and partner MCPTT systems shall be governed as per the service provider agreement between them. In this case, we consider the partner MCPTT system does not share all information of their users to the primary MCPTT system (public information would still need to be shared). +2. The group 1 is hosted by primary MCPTT system and group 2 and 3 are hosted by the partner MCPTT system. +3. The floor participant 1 corresponds to the MCPTT user of group 1. The floor participant 2 corresponds to the MCPTT user of group 2. The floor participant 3 corresponds to the MCPTT user of group 3. The floor control server 1 belongs to primary MCPTT system. The floor control server 2 belongs to partner MCPTT system. +4. The floor control server 1 is the floor arbitrator of the MCPTT group call. The floor control server 2 does floor control filtering with its floor participants 2 and 3 before communicating with the floor control server 1. + +![Sequence diagram illustrating floor control (filtering by partner MCPTT system) involving groups from multiple MCPTT systems. The diagram shows interactions between Floor participant 1 (primary), Floor control server 1 (primary), Floor control server 2 (partner), Floor participant 2 (partner), and Floor participant 3 (partner).](343e05a9fd8a8c8743428fa4ae6e2736_img.jpg) + +MCPTT Service Provider + +``` + +sequenceDiagram + participant FP1 as Floor participant 1 (primary) + participant FCS1 as Floor control server 1 (primary) + participant FCS2 as Floor control server 2 (partner) + participant FP2 as Floor participant 2 (partner) + participant FP3 as Floor participant 3 (partner) + + Note over all: 1. Session is established. Floor control is established among floor participants and floor control servers. + + Note left of FP1: 2. User wants to talk + FP1->>FCS1: 3. Floor request + Note left of FP2: 2. User wants to talk + FP2->>FCS2: 3. Floor request + Note left of FP3: 2. User wants to talk + FP3->>FCS2: 3. Floor request + Note right of FCS2: 4. Floor control filtering according to policy (floor priority or order) + FCS2-->>FP3: 5. Floor rejected + Note right of FP3: 6. Reject notification + FCS2->>FCS1: 7. Floor request + Note right of FCS1: 8. Group call arbitration according to policy (floor priority or order) + FCS1->>FCS2: 9. Floor granted + Note left of FCS1: 10a.1. Floor rejected + Note left of FCS1: 10a.2. Reject notification + Note left of FCS1: 10b.1. Queue position info + Note left of FCS1: 10b.2. User informed about queue position + FCS1->>FP1: 11. Floor taken + Note left of FP1: 12. Talker notification + Note right of FCS2: 13. Floor control filtering + FCS2->>FP2: 14. Floor granted + Note right of FP2: 15. Grant notification + FCS2->>FP3: 16. Floor taken + Note right of FP3: 17. Talker notification + Note over FP1, FP2: 18. Voice media + +``` + +Sequence diagram illustrating floor control (filtering by partner MCPTT system) involving groups from multiple MCPTT systems. The diagram shows interactions between Floor participant 1 (primary), Floor control server 1 (primary), Floor control server 2 (partner), Floor participant 2 (partner), and Floor participant 3 (partner). + +**Figure 10.9.1.4.2-1: Floor control (filtering by partner MCPTT system) involving groups from multiple MCPTT systems** + +1. An MCPTT group call involving group 1, group 2 and group 3 is setup and active. + +2. The MCPTT users want to talk +3. The floor participants initiate a floor request to the floor control server of their corresponding MCPTT systems. (The requests may or may not occur at the same time). +4. Floor control server 2 receives a floor request from floor participant 2 and from participant 3 at the same time or during an interval, then the floor control server 2 (partner) performs filtering of the floor requests received according to its local policy such as priority or order based on its own users, and forwards the selected floor request (floor participant 2) to the floor control server 1 (floor arbitrator for the MCPTT group call). As the floor participant information shall not be exposed, the priority related information or/and group information to be used by floor control server 1 should be included in the forwarded request. +5. The floor control server 2 (partner) may send a floor rejected towards the floor participant 3, since its floor request was not chosen to be forwarded on to the floor control server 1. + +6. The user on the UE where the floor participant 3 is located may be notified of the rejection. + +NOTE 1: Steps 5 and 6 can occur any time between step 4 and step 16. + +7. The floor control server 2 (partner) forwards the floor request of floor participant 2 to the floor server 1. +8. The floor control server 1 performs floor arbitration for the MCPTT group call and determines the floor request to be accepted. The floor request message from floor participant 2 of the partner system is accepted by the floor control server 1 (arbitrator) and is determined that a floor granted is sent with permission to talk. +9. The floor granted message from floor control server 1 is routed to floor participant 2 via the floor control server 2 (partner). + +10. Since floor participant 1 sent a floor request but was not granted, + +- 10a.1 the primary floor control server may send a floor rejected message to floor participant 1. + +- 10a.2 The user of the UE where the floor participant 1 is located may be notified of the rejection. + +- 10b.1 if floor control server supports floor queuing, send a queue position info message to floor participant 1. + +- 10b.2 The user of the UE where the floor participant 1 is located may be notified of the queue position. + +NOTE 2: Steps 10a.1 through 10b.2 are optional as indicated by the dashed box enclosing them. However if this box is implemented then either information flow 10a or 10b would occur. + +11. A floor taken message is sent to floor participant 1. + +12. The user of the UE where the floor participant 1 is located may be notified. + +NOTE 3: Step 10 through Step 12 can occur any time between step 8 and step 18. + +13. Since the floor control server 2 (partner) filters floor requests, when the floor control server 2 (partner) receives the floor granted for floor participant 2 from floor control server 1, the floor control server 2 (partner) needs to use the information received to generate the floor taken which will be sent to all other floor participants (floor control participant 3). +14. The floor control server 2 (partner) sends a floor granted message to floor participant 2. +15. The user of the UE where the floor participant 2 is located is notified. +16. The floor control server 2 (partner) sends a floor taken message to all other floor participants (floor participant 3). +17. The user of the UE where the floor participant 1 is located may be notified. +18. Upon successful floor grant, the group call media transmission occurs. + +NOTE 4: The media flow between the media gateways of primary and partner MCPTT systems have not been depicted in the figure for clarity. + +#### 10.9.1.5 Floor control for audio cut-in enabled group + +Figure 10.9.1.5-1 shows the procedure for audio cut-in for the session already established between the floor participants from same MCPTT service provider. Floor participants may request the floor while Floor Participant B is transmitting voice media. Floor control server grants floor immediately to the floor request received. + +**Editor's note: Configuration parameter for queue depth is FFS.** + +Pre-conditions: + +- The floor control server has been configured to support audio cut-in. +- It is assumed that the floor has been granted to floor participant B and floor participant B is transmitting voice media. There are several other floor participants (including floor participant A). + +![Sequence diagram showing floor control for audio cut-in. The diagram involves three main entities: Floor participant A, Floor control server, and Floor participant B. The process starts with an established session where Floor participant B has the floor. Floor participant A sends a 'Floor Request' to the server. The server applies an 'Audio cut-in policy', revokes the floor from participant B, and grants it to participant A. Participant B receives a 'Revoke notification' and participant A receives a 'Grant notification'. Both then transmit 'Voice media'. Later, participant B wants to talk and sends another 'Floor Request'. The server again applies the policy, revokes the floor from participant A, and grants it to participant B. Participant A receives a 'Revoke notification' and participant B receives a 'Grant notification'. Both then transmit 'Voice media' again.](b033fab424e6df728345cfa04df83fcc_img.jpg) + +Home MCPTT Service Provider + +``` + +sequenceDiagram + participant A as Floor participant A + participant S as Floor control server + participant B as Floor participant B + Note over A, B: 1. Session is established, Floor control is established between floor participant and floor control server. Floor granted to floor participant B + Note left of A: 2. User wants to talk + A->>S: 3. Floor Request + Note over S: 4. Audio cut-in policy is applied. + S->>B: 5. Floor Revoked + Note right of B: 6. Revoke notification + S->>A: 7. Floor Granted + S->>B: 7. Floor Taken + Note left of A: 8. Grant notification + Note right of B: 8. Talker notification + A->>S: 9. Voice media + B->>S: 9. Voice media + Note right of B: 10. User wants to talk + B->>S: 11. Floor Request + Note over S: 12. Audio cut-in policy is applied. + S->>A: 13. Floor Revoked + Note left of A: 14. Revoke notification + S->>B: 15. Floor Granted + S->>A: 15. Floor Taken + Note right of B: 16. Grant notification + Note left of A: 16. Talker notification + B->>S: 17. Voice media + A->>S: 17. Voice media + +``` + +Sequence diagram showing floor control for audio cut-in. The diagram involves three main entities: Floor participant A, Floor control server, and Floor participant B. The process starts with an established session where Floor participant B has the floor. Floor participant A sends a 'Floor Request' to the server. The server applies an 'Audio cut-in policy', revokes the floor from participant B, and grants it to participant A. Participant B receives a 'Revoke notification' and participant A receives a 'Grant notification'. Both then transmit 'Voice media'. Later, participant B wants to talk and sends another 'Floor Request'. The server again applies the policy, revokes the floor from participant A, and grants it to participant B. Participant A receives a 'Revoke notification' and participant B receives a 'Grant notification'. Both then transmit 'Voice media' again. + +**Figure 10.9.1.5-1: Floor control for audio cut-in enabled group in single MCPTT system** + +1. Floor participant B has been given floor and is transmitting voice media. + +2. Floor participant A wants to send voice media over the session. +3. Floor participant A sends a floor request message to the floor control server. +4. The floor control server applies the audio cut-in policy with floor queue disabled i.e., floor is immediately granted to the floor participant A, and revoked from floor participant B. +5. The floor control server sends a floor revoked message to floor participant B stopping the voice media transmission from floor participant B. +6. The user of floor participant B may be notified that the floor is revoked. +7. The Floor control server sends a floor granted message to floor participant A, and sends a floor taken message to floor participant B with information of who is granted the floor. The floor control server may limit the time a user talks (holds the floor). +8. The user of floor participant A may be notified that he is granted the floor. Similarly, the user of floor participant B may be notified who is granted the floor. +9. Floor participant A starts sending voice media over the session established. +10. Now floor participant B may want the floor to start sending voice media. +11. Floor participant B sends a floor request message to floor control server. +12. The floor control server applies the audio cut-in policy with floor queue disabled. +13. The floor control server sends a floor revoked message to floor participant A stopping the voice media transmission from floor participant A. +14. The user of floor participant A may be notified that the floor is revoked. +15. The Floor control server sends a floor granted message to floor participant B, and sends a floor taken message to floor participant A with information of who is granted the floor. The floor control server may limit the time a user talks (holds the floor). +16. The user of floor participant B may be notified that he is granted the floor. Similarly, the user of floor participant A may be notified who is granted the floor. +17. Floor participant B starts sending voice media over the session established. + +#### 10.9.1.6 Unicast media stop and resume requests + +Figure 10.9.1.6-1 shows the procedure for a floor participant to indicate to the floor control server that the unicast media flow of an active MCPTT group call can be stopped. + +Pre-condition: + +1. An MCPTT session is established between MCPTT client A and MCPTT server for an MCPTT group call. Other participants to the call are not shown in the figure for simplicity. +2. The floor control is established between the floor participant and the floor control server. + +![Sequence diagram illustrating the unicast media stop request during an MCPTT session. The diagram shows interactions between Floor participant A and Floor control server. The sequence is: 1. Floor taken (server to participant), 2. Unicast media flow (server to participant), 3. User indicates that media for the call is not needed (participant internal), 4. Unicast media stop request (participant to server), 5. Server stops the unicast media flow (server internal).](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` +sequenceDiagram + participant FCS as Floor control server + participant FPA as Floor participant A + Note right of FPA: 3. User indicates that media for the call is not needed + FCS->>FPA: 1. Floor taken + FCS->>FPA: 2. Unicast media flow + FPA->>FCS: 4. Unicast media stop request + Note right of FCS: 5. Server stops the unicast media flow +``` + +Sequence diagram illustrating the unicast media stop request during an MCPTT session. The diagram shows interactions between Floor participant A and Floor control server. The sequence is: 1. Floor taken (server to participant), 2. Unicast media flow (server to participant), 3. User indicates that media for the call is not needed (participant internal), 4. Unicast media stop request (participant to server), 5. Server stops the unicast media flow (server internal). + +**Figure 10.9.1.6-1: Unicast media stop request during an MCPTT session** + +1. Another floor participant has requested and has been granted the floor. The floor control server sends a floor taken message to floor participant A. The floor taken message may include an identifier of the associated media flow. +2. Floor control server sends the voice media flow to floor participant A over unicast. +3. Floor participant A gets the information, e.g. from the user, that media for the call is not needed. +4. Floor participant A sends a unicast media stop request to floor control server, identifying the media flow to be stopped. +5. Floor control server stops sending that unicast media flow to floor participant A. Associated bearer resources may be de-allocated by the MCPTT server. + +Figure 10.9.1.6-2 shows the procedure for a floor participant to request from the floor control server that the unicast media flow of an active MCPTT group call be restarted. + +Pre-condition: + +1. An MCPTT session is established between MCPTT client A and MCPTT server for an MCPTT group call. Other participants to the call are not shown in the figure for simplicity +2. The floor control is established between the floor participant and the floor control server. +3. Floor participant A has previously indicated to the floor control server that unicast media flow for that call should be stopped, using the procedure described in Figure 10.9.1.6-1. + +![Sequence diagram illustrating the unicast media resume request during an MCPTT session. The diagram shows two lifelines: 'Floor participant A' and 'Floor control server'. The sequence of messages is: 1. Floor control server sends 'Floor taken' to Floor participant A. 2. Floor participant A receives a message from the user indicating media is needed. 3. Floor participant A sends 'Unicast media resume request' to Floor control server. 4. Floor control server sends 'Unicast media flow' back to Floor participant A.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +``` + +sequenceDiagram + participant FCS as Floor control server + participant FPA as Floor participant A + Note right of FPA: 2. User indicates that media for the call is needed + FCS->>FPA: 1. Floor taken + FPA->>FCS: 3. Unicast media resume request + FCS->>FPA: 4. Unicast media flow + +``` + +Sequence diagram illustrating the unicast media resume request during an MCPTT session. The diagram shows two lifelines: 'Floor participant A' and 'Floor control server'. The sequence of messages is: 1. Floor control server sends 'Floor taken' to Floor participant A. 2. Floor participant A receives a message from the user indicating media is needed. 3. Floor participant A sends 'Unicast media resume request' to Floor control server. 4. Floor control server sends 'Unicast media flow' back to Floor participant A. + +**Figure 10.9.1.6-2: Unicast media resume request during an MCPTT session** + +1. Another floor participant has requested and has been granted the floor. The floor control server sends a floor taken message to floor participant A. The floor taken message may include an identifier of the associated media flow. +2. Floor participant A gets the information, e.g. from the user, that media for the call is needed again. +3. Floor participant A sends a unicast media resume request to floor control server, identifying the media flow to be re-started. +4. Floor control server starts sending that unicast media flow to floor participant A. This may need new bearer resources to be allocated. + +NOTE 1: The identifier of the flow to be stopped or resumed is known by the floor participant from the floor control information flows associated with that MCPTT session. + +NOTE 2: Stopping a media flow is not leaving the session and subsequent floor control messages will still be sent by the floor control server to the floor participant which has requested a unicast media stop. + +NOTE 3: Both requests have no effect on a possible ongoing transmission of the media flow over MBMS. In particular, they are not interpreted by the MCPTT server as MBMS listening status reports. + +### 10.9.2 Floor control for off-network MCPTT service + +#### 10.9.2.1 General + +The procedures defined in this subclause provide floor control to MCPTT UEs in off-network operation. The procedures apply to both private calls and group calls. + +In off-network, floor control is performed by using floor control messages among the MCPTT clients without centralized MCPTT server. The MCPTT client can transmit voice packets once it is granted the right to speak, either locally in the UE or by reception of a floor granted message from another MCPTT client. + +In off-network, the MCPTT client currently speaking performs the temporary floor arbitrator during speaking since there is no centralized MCPTT floor control server. The floor arbitrator controls the floor whether or not queue is supported, and when floor is requested with override. If queue is supported, the MCPTT client performing floor arbitrator grants the right to speak to the next speaker and transfers the floor arbitrator role after completing the voice transfer and releasing the floor. For group calls, the floor arbitrator also transfers the floor control queue when granting + +the floor. The next MCPTT client receiving the right to speak becomes the new floor arbitrator and, for group calls, has the floor control queue. + +For group calls, the floor control message is delivered in multicast based communication and can be monitored by all the members within the MCPTT group. + +The following information flows apply among MCPTT clients. + +- Floor request (from the floor participants to the floor arbitrator): used to request a floor for voice transfer. +- Floor release (from the floor arbitrator to the floor participants): used to inform that the voice transfer is completed and the floor is released. +- Floor granted (from the floor arbitrator to a floor participant): used to indicate that the request for floor is granted, that voice transfer is possible and the current queue list. +- Queue position request (from the floor participant to the floor arbitrator): used to request the position in the floor request queue. +- Queue position info (from the floor arbitrator to the floor participant): used to indicate the floor request is queued and the current queue status. +- Floor rejected (from the floor arbitrator to the floor participant): used to indicate that a request for the floor is rejected. +- Floor taken (from the floor arbitrator to the floor participant): used to indicate the floor is granted to another MCPTT user. + +#### 10.9.2.2 Information flows for floor control for off-network + +##### 10.9.2.2.1 General + +For floor control for off-network, the information flows defined under subclause 10.9.1.2 apply unless it is explicitly defined under this subclause. + +##### 10.9.2.2.2 Floor granted + +Table 10.9.2.2.2-1 describes the information flow floor granted, from the floor participant to the floor participant, which is used to indicate that a request for floor is granted and media transfer is possible. + +**Table 10.9.2.2.2-1: Floor granted** + +| Information element | Status | Description | +|--------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Requester identity | +| Duration | M | The time for which the granted party is allowed to transmit | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only in case of media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +#### 10.9.2.3 Floor control during silence + +##### 10.9.2.3.1 Successful floor taken (No floor contention) + +If a floor arbitrator still exists, the expected behaviour for floor requests during periods of silence is described in subclauses 10.9.2.5 and 10.9.2.6 (with the exception that no media was being generated prior to the floor request). + +If a floor arbitrator does not exist, figure 10.9.2.3.1-1 shows the successful high level floor control procedure during periods when there is no detectable talker. + +NOTE 1: The description also applies to private calls. + +Pre-conditions: + +1. An off-network group call had been established and all MCPTT clients have the call parameters. No participant is currently talking and no floor arbitrator is identified. + +![Sequence diagram illustrating the successful floor taken flow with no floor contention. Four MCPTT clients (1, 2, 3, 4) are shown. Client 1 sends a 'Floor request' to the group. A box labeled 'No speech' spans across the top. Client 1 then receives a 'No contention detected' message. Client 1 sends a 'Floor taken' message to the group. A box labeled 'User notification' is shown for Client 1. Finally, Client 1 begins a 'Media flow' to the group.](9f50279046b74a4e66a1a0144c3b1d11_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT client 3 + participant MCPTT client 4 + Note right of MCPTT client 4: No speech + MCPTT client 1->>MCPTT client 2: 1. Floor request + Note left of MCPTT client 1: 2. No contention detected + MCPTT client 1->>MCPTT client 2: 3. Floor taken + Note left of MCPTT client 1: 4. User notification + MCPTT client 1->>MCPTT client 2: 5. Media flow +``` + +Sequence diagram illustrating the successful floor taken flow with no floor contention. Four MCPTT clients (1, 2, 3, 4) are shown. Client 1 sends a 'Floor request' to the group. A box labeled 'No speech' spans across the top. Client 1 then receives a 'No contention detected' message. Client 1 sends a 'Floor taken' message to the group. A box labeled 'User notification' is shown for Client 1. Finally, Client 1 begins a 'Media flow' to the group. + +**Figure 10.9.2.3.1-1: Successful floor taken flow (No floor contention)** + +1. The MCPTT client 1 sends the floor request message to the MCPTT group. +2. The MCPTT client 1 does not detect any floor contention. Floor contention occurs when multiple floor requests may exist simultaneously. + +NOTE 2: The mechanism for detecting floor contention is out of scope of the present document. + +3. The MCPTT client 1 sends the floor taken message to the MCPTT group. +4. The user gets a notification that the floor request was successful (the floor has been granted). +5. The MCPTT client 1 begins voice transmission. + +#### 10.9.2.4 Simultaneous floor requests + +If a floor arbitrator does not exist, figure 10.9.2.4.1-1 shows the expected behaviour in case of simultaneous floor requests are generated when there is no detectable talker. + +Pre-conditions: + +1. An off-network group call is established and all MCPTT clients have the call parameters. No participant is currently talking and no floor arbitrator is identified. +2. MCPTT client 1 has higher priority than MCPTT client 2. + +![Sequence diagram illustrating simultaneous floor requests among four MCPTT clients. The diagram shows a 'No speech' state, followed by parallel floor requests from client 1 and client 2. Client 1 then compares priority, determines it has higher priority, sends a 'Floor taken' message, and receives a user notification.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT client 3 + participant MCPTT client 4 + Note over all: No speech + Note left of MCPTT client 1: 1a. Floor request + MCPTT client 1->>MCPTT client 2: + Note left of MCPTT client 2: 1b. Floor request + MCPTT client 2->>MCPTT client 3: + Note left of MCPTT client 1: 2. Compare priority + Note left of MCPTT client 2: 2. Compare priority + Note left of MCPTT client 1: 3. Floor taken + MCPTT client 1->>MCPTT client 2: + Note left of MCPTT client 1: 4. User notification + +``` + +Sequence diagram illustrating simultaneous floor requests among four MCPTT clients. The diagram shows a 'No speech' state, followed by parallel floor requests from client 1 and client 2. Client 1 then compares priority, determines it has higher priority, sends a 'Floor taken' message, and receives a user notification. + +**Figure 10.9.2.4.1-1: Simultaneous floor requests** + +1a. The MCPTT client 1 sends the floor request message to the MCPTT group. + +1b. The MCPTT client 2 sends the floor request message to the MCPTT group. + +NOTE 1: Step 1a and 1b happen in parallel + +2. On receiving a floor request message, while waiting for a response to the sent floor request message, the MCPTT client compares its floor priority with the floor priority indicated in the received floor request message. + +3. On determining that it has higher floor priority than the received floor request message(s), and no response to the sent floor request message is received, the MCPTT client 1 sends the floor taken message to the MCPTT group. + +4. The user at MCPTT client 1 gets notification that the floor request was successful (the floor has been granted). + +NOTE 2: If the floor priority in the received floor request message is same as its own floor priority, the MCPTT client can use another scheme to decide who gets the floor. + +#### 10.9.2.5 Floor request during speaking with queue + +Figure 10.9.2.5-1 shows the high level procedure that the floor control is conducted when the MCPTT off-network session is already established among MCPTT floor participants and while voice media is transmitting. In the case, MCPTT clients should support queue function. The current speaking MCPTT client acting as the floor arbitrator put the floor request into the queue list when receiving the floor request from other MCPTT clients. This procedure happens while voice media is transmitting. In the flow, MCPTT client 1 transmits the voice media to the MCPTT group and acts as the floor arbitrator. + +NOTE: The description only applies to group calls. + +![Sequence diagram showing floor request during speaking with queue. Lifelines: MCPTT client 1, MCPTT client 2, MCPTT client 3, MCPTT client 4. The diagram is divided into three phases: Initial state, 'During speech', and 'Ending Transmission'. 1. Media flow from client 1 to 2, 3, and 4. 2. Floor request from client 2 to 1, 3, and 4. 3. Queuing at client 1. 4. Queue position info from client 1 to 2, 3, and 4. 5. Floor granted from client 1 to 2, 3, and 4. 6. Media flow from client 2 to 1, 3, and 4.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCPTT client 1 + participant C2 as MCPTT client 2 + participant C3 as MCPTT client 3 + participant C4 as MCPTT client 4 + + Note left of C1: During speech + C1->>C2: 1. Media flow + C1->>C3: 1. Media flow + C1->>C4: 1. Media flow + C2->>C1: 2. Floor request + Note left of C1: 3. Queuing + C1->>C2: 4. Queue position info + C1->>C3: 4. Queue position info + C1->>C4: 4. Queue position info + Note left of C1: Ending Transmission + C1->>C2: 5. Floor granted + C1->>C3: 5. Floor granted + C1->>C4: 5. Floor granted + C2->>C1: 6. Media flow + C2->>C3: 6. Media flow + C2->>C4: 6. Media flow + +``` + +Sequence diagram showing floor request during speaking with queue. Lifelines: MCPTT client 1, MCPTT client 2, MCPTT client 3, MCPTT client 4. The diagram is divided into three phases: Initial state, 'During speech', and 'Ending Transmission'. 1. Media flow from client 1 to 2, 3, and 4. 2. Floor request from client 2 to 1, 3, and 4. 3. Queuing at client 1. 4. Queue position info from client 1 to 2, 3, and 4. 5. Floor granted from client 1 to 2, 3, and 4. 6. Media flow from client 2 to 1, 3, and 4. + +Figure 10.9.2.5-1: Floor request during speaking with queue + +1. MCPTT client 1 is transmitting voice media to the MCPTT group. +2. MCPTT client 2 sends the floor request message to the MCPTT group. +3. MCPTT client 1 acting as the floor arbitrator put the floor request of MCPTT client 2 into the queue list. +4. MCPTT client 1 sends the queue position info message with the queuing status regarding the floor request of MCPTT client 2 in order to inform the floor request is queued. +5. MCPTT client 1 sends the floor granted message to the MCPTT group when releasing the floor. The message contains the MCPTT ID to be granted to send the voice media, and queue list, if any. MCPTT client 1 may include the maximum duration that MCPTT client 2 transmits in the floor granted message. +6. MCPTT client 2 sends the voice media when receiving the floor granted message and being granted as next speaker in the floor granted message. In addition, MCPTT client 2 becomes the floor arbitrator. + +#### 10.9.2.6 Floor request during speaking without queue + +Figure 10.9.2.6-1 shows the high level procedure that the floor control is conducted when the MCPTT off-network session is already established among MCPTT floor participants. In the case, MCPTT clients do not support queue function. The current speaking MCPTT client acting as the floor arbitrator controls the floor request when receiving the floor request from other MCPTT clients. This procedure happens while voice media is transmitting. In the flow, MCPTT client 1 transmits the voice media to the MCPTT group and acts as the floor arbitrator. + +NOTE: The description also applies to private calls. + +![Sequence diagram illustrating floor request during speaking without queue. Four MCPTT clients (1, 2, 3, 4) are shown. Client 1 is the floor arbitrator. The diagram shows three messages: 1. Floor request from client 2 to client 1; 2. Floor rejected from client 1 to client 2; 3. Floor release from client 1 to client 2. The 'During speech' phase ends after the floor release, and the 'No speech' phase begins.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT client 3 + participant MCPTT client 4 + + Note left of MCPTT client 1: During speech + MCPTT client 2->>MCPTT client 1: 1. Floor request + MCPTT client 1-->>MCPTT client 2: 2. Floor rejected + Note left of MCPTT client 1: Floor release + MCPTT client 1->>MCPTT client 2: 3. Floor release + Note left of MCPTT client 1: No speech + +``` + +Sequence diagram illustrating floor request during speaking without queue. Four MCPTT clients (1, 2, 3, 4) are shown. Client 1 is the floor arbitrator. The diagram shows three messages: 1. Floor request from client 2 to client 1; 2. Floor rejected from client 1 to client 2; 3. Floor release from client 1 to client 2. The 'During speech' phase ends after the floor release, and the 'No speech' phase begins. + +**Figure 10.9.2.6-1: Floor request during speaking without queue** + +1. MCPTT client 2 sends the floor request message to the MCPTT group. +2. MCPTT client 1 acting as the floor arbitrator rejects the floor request from MCPTT client 2 if no queue function is supported and sends the floor rejected message to the MCPTT group. +3. MCPTT client 1 sends the floor release message to the MCPTT group when releasing the floor, in order to indicate that MCPTT client 1 finishes to send the voice media and releases the floor. + +When the floor release message is transmitted, there are no voice media in the MCPTT group until an MCPTT client requests the floor as described in subclause 10.9.2.3. + +#### 10.9.2.7 Override + +Figure 10.9.2.7-1 shows the high level procedure that the floor control is conducted when the MCPTT off-network session is already established among MCPTT floor participants and while voice media is transmitting. When the currently speaking MCPTT floor participant receives the floor request message from another floor participant who is authorized to revoke the active transmission (e.g. higher hierarchy), the current speaking MCPTT floor participant immediately stops sending the audio media and then grants the permission to that authorized floor participant. + +NOTE: The description also applies to private calls. + +Pre-condition: + +- MCPTT client 1, who acts as the floor arbitrator, transmits the audio media to the MCPTT group. + +![Sequence diagram illustrating floor request with override authorization among four MCPTT clients.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +The diagram shows a sequence of interactions between four MCPTT clients (1, 2, 3, and 4). At the top, thick grey arrows labeled 'Media flow' point from client 1 to 2, 2 to 3, and 3 to 4. A vertical dashed line extends from client 2, labeled '1. Floor request'. A rectangular box labeled 'During speech' contains a sub-box '2. Processing Floor request' on client 1's timeline. A vertical dashed line extends from client 1, labeled '3. Floor granted'. At the bottom, thick grey arrows labeled 'Media flow' point from client 2 to 1, 3 to 2, and 4 to 3. + +Sequence diagram illustrating floor request with override authorization among four MCPTT clients. + +**Figure 10.9.2.7-1: Floor request with override authorization** + +1. MCPTT client 2 sends the floor request message with override criteria (e.g., priority level) to the MCPTT group. +2. MCPTT client 1 acting as the floor arbitrator determines if the floor is to be revoked based on override criteria. If this is the case, MCPTT client 1 revokes its right of the floor and stops sending the voice media immediately. +3. MCPTT client 1 sends the floor granted message to the MCPTT group. The floor granted message contains the MCPTT ID to be granted, the floor and the floor control queue (if supported). MCPTT client 1 may also include the maximum duration that MCPTT client 2 can transmit voice in the floor granted message. + +MCPTT client 2 who has revoked the floor is the new floor arbitrator and transmits the audio media to the MCPTT group. + +#### 10.9.2.8 Floor queue status + +Figure 10.9.2.8-1 shows the high level procedure that the floor control is conducted when the MCPTT off-network session is already established among MCPTT floor participants and while voice media is transmitting. If the floor control queueing is supported by the floor control mechanism, the current speaking MCPTT group member who is acting as the floor arbitrator collects the information about the queue status based on the received request(s) from the MCPTT group participant(s). The current speaker can then share information about the queue status of the MCPTT floor participant upon request. + +NOTE: The description only applies to group calls. + +Pre-condition: + +- MCPTT client 1, who acts as the floor arbitrator, transmits the audio media to the MCPTT group. + +![Sequence diagram showing MCPTT client 2 sending a queue position request to MCPTT client 1 (floor arbitrator) during a speech. The diagram includes four MCPTT clients (1-4) and three media flows. The sequence is: 1. Queue position request from client 2 to client 1; 2. Processing request from client 1; 3. Queue position info from client 1 to client 2. Media flows are shown above and below the sequence.](18bb06865e2dada3656ea3d57f290f7f_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT client 3 + participant MCPTT client 4 + Note left of MCPTT client 1: During speech + MCPTT client 2->>MCPTT client 1: 1. Queue position request + Note left of MCPTT client 1: 2. Processing request + MCPTT client 1->>MCPTT client 2: 3. Queue position info + +``` + +Sequence diagram showing MCPTT client 2 sending a queue position request to MCPTT client 1 (floor arbitrator) during a speech. The diagram includes four MCPTT clients (1-4) and three media flows. The sequence is: 1. Queue position request from client 2 to client 1; 2. Processing request from client 1; 3. Queue position info from client 1 to client 2. Media flows are shown above and below the sequence. + +**Figure 10.9.2.8-1: Queue status request** + +1. MCPTT client 2 sends the queue position request message targeted to MCPTT client 1 i.e. the floor arbitrator by broadcasting the message to the MCPTT group to get its queue status. +2. Since the queue function is assumed to be supported in this call flow, MCPTT client 1 i.e. the floor arbitrator processes the queue position request to find out the status of MCPTT client 1 in the queue. +3. MCPTT client 1 constructs the queue position info message containing the MCPTT client 2's queue status and sends it toward MCPTT client 2 by broadcasting the message to the MCPTT group. + +MCPTT client1 continues being the floor arbitrator and transmits the audio media to the MCPTT group. + +## 10.10 Use of MBMS transmission (on-network) + +### 10.10.1 Information flows for MBMS Transmission + +#### 10.10.1.1 MapGroupToBearer + +Table 10.10.1.1-1 describes the information flow to associate a MCPTT group call to a MBMS bearer. It is sent from the MCPTT server to the MCPTT client. + +**Table 10.10.1.1-1: MapGroupToBearer** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT group ID | M | This element identifies the MCPTT group, in which the call is started. | +| Media stream identifier | M | This element identifies the media stream of the SDP used for the group call (e.g. MBMS subchannel). | +| TMGI (NOTE) | O | The MBMS bearer identifier if the media of the MCPTT group call is not sent on the same MBMS bearer as this MapGroupToBearer message. | +| Call acknowledgement indicator | O | Indication that the MCPTT group call requires acknowledgement from receiving MCPTT clients. | +| NOTE: TMGI shall be present if this message is sent over a different MBMS bearer than the media of the group call; TMGI may be present if this message is sent over the same MBMS bearer as the media of the group call. | | | + +#### 10.10.1.2 UnmapGroupFromBearer + +Table 10.10.1.2-1 describes the information flow to disconnect a MCPTT group call from a MBMS bearer. It is sent from the MCPTT server to the MCPTT client. + +**Table 10.10.1.2-1: UnmapGroupFromBearer** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------| +| MCPTT group ID | M | This element identifies the MCPTT group which will no longer use the MBMS bearer. | + +#### 10.10.1.3 Application paging + +Table 10.10.1.3-1 describes the information flow application paging from the MCPTT server to the MCPTT clients. + +**Table 10.10.1.3-1: Application paging** + +| Information element | Status | Description | +|-----------------------------------------------------|--------|-------------------------------------------------------------------------------------------| +| MCPTT Group ID (NOTE) | O | This element identifies the MCPTT group which is paged by the application. | +| MCPTT ID (NOTE) | O | Identity of the MCPTT user which is paged by the application for the private call. | +| Cause | M | The cause for this message being sent (e.g. for the use in group calls or private calls). | +| NOTE: Either MCPTT Group ID or MCPTT ID is present. | | | + +### 10.10.2 Use of pre-established MBMS bearers + +The MCPTT service shall support the procedure for using pre-established MBMS bearers as specified 3GPP TS 23.280 [16]. The MCPTT service shall use the MCPTT-1, MCPTT-6, MCPTT-8 and MCPTT-9 reference points for this procedure. + +MCPTT may use pre-established MBMS bearer for the different types of MCPTT group calls. Both pre-arranged group calls and chat group calls can use the pre-established MBMS bearer for distributing the media. The MBMS bearer can be used by any group. Depending on the capacity of the MBMS bearer, the bearer can be used to broadcast one or more group calls in parallel. + +Both the media packets as well as the floor control messages to the receiving users are sent on the MBMS bearer. Optionally a separate MBMS bearer could be used for the floor control messages, due to different bearer characteristic requirements. + +When using the pre-established procedure for MCPTT, the MCPTT server perform the procedure of call connect and disconnect over MBMS as defined in subclause 10.10.4 at the group communication session establishment step. + +### 10.10.3 Use of dynamic MBMS bearer establishment + +The MCPTT service shall support the procedure for using dynamic MBMS bearers as specified 3GPP TS 23.280 [16]. The MCPTT service shall use the MCPTT-1, MCPTT-4, MCPTT-6, MCPTT-7, MCPTT-8 and MCPTT-9 reference points for this procedure. + +MCPTT may use dynamic MBMS bearer establishment for the different types of MCPTT group calls. Both pre-arranged group calls and chat group calls can use the dynamic MBMS bearer for distributing the media. + +Both the media packets as well as the floor control messages to the receiving users are sent on the MBMS bearer. + +When using the procedures for dynamic MBMS bearer establishment for MCPTT, the MCPTT server perform the procedure of call connect and disconnect over MBMS as defined in subclause 10.10.4 at the group communication session establishment step. + +### 10.10.4 Call connect and disconnect over MBMS + +#### 10.10.4.1 General + +MBMS bearer can be used for MCPTT group calls. One MBMS bearer is not permanently associated to one specific group or group call. Before sending media packets of a group call over MBMS bearer, the MCPTT server shall send the association information between group call and the MBMS bearer. The group call setup procedure indicates the media stream within one MBMS bearer that is used for the specific group call. When the group call over the MBMS bearer is finished, this temporary association information of an MCPTT group call to specific resources on a MBMS bearer is undone. The procedure in figure 10.10.4.2.1-1 requires that the group session is setup before the call start. This eliminates the need for the receiving clients to continuously use a unicast bearer. Prior to this the MBMS bearer is activated and announced to the MCPTT clients. + +#### 10.10.4.2 Procedure + +##### 10.10.4.2.1 Call connect over MBMS + +In figure 10.10.4.2.1-1 the MCPTT client 1 is the client that initiate an MCPTT chat group call and also the transmitting client. MCPTT client 1 may, but does not have to be in an MBMS service area. The MCPTT client 2 and MCPTT client 3 represents MCPTT clients receiving the MCPTT call over an MBMS bearer. There may be other receiving clients both over unicast bearers and over this or other MBMS bearer(s), however they are not illustrated in this figure. + +The same procedure as for chat group call can also be applied for pre-arranged calls. However that requires that the pre-arranged sessions are already active. If a pre-arranged group session is initiated the use of pre-established sessions are required. + +Pre-conditions: + +- All users participating in the MCPTT group call are already affiliated to the group. +- All participating users have joined the group session. + +![Sequence diagram showing the call connect procedure over MBMS. Lifelines: MCPTT client 1, MCPTT server, MCPTT Client 2, MCPTT Client 3. The sequence starts with activation and announcement of the MBMS bearer from the server to clients 2 and 3. Client 1 sends an initial floor request to the server, which responds with floor granted. The server then maps the group to the bearer and informs clients 2 and 3 that the floor is taken. Finally, a media flow is established: uplink unicast from client 1 to the server, and downlink MBMS from the server to clients 2 and 3.](99781d878388c3e0f359b1d6ce14119c_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT Client 2 + participant MCPTT Client 3 + + Note right of MCPTT server: 1. Activation and announcement of MBMS bearer + MCPTT client 1->>MCPTT server: 2. Initial floor request + MCPTT server-->>MCPTT Client 2: 3. MapGroupToBearer + MCPTT server-->>MCPTT client 1: 4. Floor granted + MCPTT server-->>MCPTT Client 3: 5. Floor taken + Note left of MCPTT server: 6. Media flow (uplink unicast) + Note right of MCPTT server: 6. Media flow (downlink MBMS) + +``` + +Sequence diagram showing the call connect procedure over MBMS. Lifelines: MCPTT client 1, MCPTT server, MCPTT Client 2, MCPTT Client 3. The sequence starts with activation and announcement of the MBMS bearer from the server to clients 2 and 3. Client 1 sends an initial floor request to the server, which responds with floor granted. The server then maps the group to the bearer and informs clients 2 and 3 that the floor is taken. Finally, a media flow is established: uplink unicast from client 1 to the server, and downlink MBMS from the server to clients 2 and 3. + +Figure 10.10.4.2.1-1: Chat group call connect on MBMS bearer + +1. Activation and announcement of MBMS bearer availability. + +NOTE 1: The procedure does not include the steps for MCPTT client location reporting, or for MBMS capability information exchange. + +2. MCPTT client 1 initiate the MCPTT group call by sending an initial floor request over a unicast bearer to the MCPTT server (reference point MCPTT-4). +3. The MCPTT server will send a MapGroupToBearer message over a previously activated MBMS bearer to all users that will receive the call over an MBMS bearer. The MapGroupToBearer message includes association information between the group call and MBMS bearer. The MapGroupToBearer message includes MCPTT group ID and information about the media stream identifier of the activated MBMS bearer and may include the identifier (i.e. the TMGI) of the MBMS bearer broadcasting the call. The message is sent over reference point MCPTT-9. + +NOTE 2: Step 3 can be deferred until step 5 and the MapGroupToBearer message can then be included in the floor taken message. + +4. The MCPTT server grants the right to transmit for MCPTT client 1 and by that sends a floor granted message to the MCPTT client 1. This message is sent over a unicast bearer (reference point MCPTT-4). +5. A floor taken message is sent from the MCPTT server to all receiving users. This message includes the MCPTT ID of the transmitting MCPTT client as well as the MCPTT group ID. The message is sent over a MBMS bearer to all users that have previously been setup to receive calls over the MBMS bearer. The message is sent over reference point MCPTT-9. +6. The media is sent from MCPTT client 1 to the MCPTT server over unicast bearer and from the MCPTT server to the MCPTT client 2 and MCPTT client 3 over MBMS bearer. + +NOTE 3: Additional floor request messages in the same call will not trigger the MapGroupToBearer message to be sent. + +##### 10.10.4.2.2 Call disconnect over MBMS + +Figure 10.10.4.2.2-1 shows the high level procedure where an UnmapGroupFromBearer message is sent by the MCPTT server to the MCPTT clients to indicate that the MCPTT group call is being dissociated from the MBMS bearer. + +![Sequence diagram illustrating the call disconnect over MBMS procedure. The diagram shows four lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3. Step 1 shows a media flow (uplink, unicast) from client 1 to the server, which then becomes a media flow to clients 2 and 3. Step 2 shows the server making a decision to disconnect the call or dissociate from the MBMS bearer. Step 3 shows the server sending a disconnect / UnmapGroupFromBearer message to clients 2 and 3.](4430c1d8e78ac97fda782321410349a9_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + Note right of MCPTT server: 2. Decision to disconnect the call or dissociate from the MBMS bearer + MCPTT client 1->>MCPTT server: 1. Media flow (uplink, unicast) + MCPTT server->>MCPTT client 2: 1. Media flow + MCPTT server->>MCPTT client 3: 1. Media flow + MCPTT server->>MCPTT client 2: 3. Disconnect / UnmapGroupFromBearer + MCPTT server->>MCPTT client 3: 3. Disconnect / UnmapGroupFromBearer + +``` + +Sequence diagram illustrating the call disconnect over MBMS procedure. The diagram shows four lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3. Step 1 shows a media flow (uplink, unicast) from client 1 to the server, which then becomes a media flow to clients 2 and 3. Step 2 shows the server making a decision to disconnect the call or dissociate from the MBMS bearer. Step 3 shows the server sending a disconnect / UnmapGroupFromBearer message to clients 2 and 3. + +**Figure 10.10.4.2.2-1: Chat group call disconnect on MBMS bearer** + +1. An MCPTT group call is ongoing; the media is broadcasted over MBMS bearer to MCPTT client 2 and MCPTT client 3. +2. MCPTT server has determined to disconnect the call over the MBMS bearer for the MCPTT clients +3. An UnmapGroupFromBearer message is sent by the MCPTT server to MCPTT client 2, MCPTT client 3 and possibly to MCPTT client 1 (if in MBMS coverage area) on MBMS bearer(s). + +NOTE 4: The UnmapGroupFromBearer message can be sent as part of other messages. + +NOTE 5: The UnmapGroupFromBearer message and the MapGroupToBearer message can be combined, to facilitate switching bearers in one signalling step, as necessary. + +### 10.10.5 Switching from MBMS bearer to unicast bearer + +The MCPTT service shall support the procedure for switching from MBMS bearer to unicast bearer as specified 3GPP TS 23.280 [16]. The MCPTT service shall use the MCPTT-1, MCPTT-4, MCPTT-7, MCPTT-8 and MCPTT-9 reference points for this procedure. + +### 10.10.6 Enhanced MCPTT group call setup procedure with MBMS bearer + +#### 10.10.6.1 Description + +When the MCPTT server initiates a new MCPTT call, the MCPTT server shall decide to use unicast bearers or broadcast bearers for the downlink media. A similar decision may also be made for other types of media communication e.g. MCVideo. To decide to use broadcast or unicast involves a number of aspects. The figure 10.10.6.1-1 specifies a procedural flow to perform such decision. + +The flow described evaluates which bearer type to use for a new MCPTT group call. It is assumed that if an MBMS bearer is active it is also announced to the MCPTT client. + +When using an MBMS bearer for application level control signalling, the announcement of an already active MBMS bearer could be part of the MCPTT group call setup, however that will have an impact on the call setup time. + +![Flowchart titled 'MBMS bearer decision flow' showing the logic for selecting between unicast and MBMS bearers for an MCPTT group call.](747516f5861a0ddf31e3851da8e34b95_img.jpg) + +``` + +graph TD + Start[New MCPTT group call setup applicable for multicast transmission] --> Q1{Is there an active MBMS bearer to use?} + Q1 -- No --> U1[Use Unicast bearers for the MCPTT group call] + Q1 -- Yes --> Q2{Does the bearer have capacity for a new call?} + Q2 -- No --> Q3{Any ongoing call that can be moved to unicast?} + Q3 -- Yes --> T1[Initiate transfer of ongoing call to unicast bearer] + T1 --> Q4{Does the call require ack from receiving users?} + Q3 -- No --> M1[Use the MBMS bearer for call setup message] + M1 --> U2[Use unicast bearer for the media. Optionally queue the call until resources become available.] + Q2 -- Yes --> Q4 + Q4 -- No --> M2[Use the MBMS bearer for the new call] + Q4 -- Yes --> M3[Use the MBMS bearer for the call and indicate on the MBMS bearer that an acknowledgment is needed] + +``` + +Flowchart titled 'MBMS bearer decision flow' showing the logic for selecting between unicast and MBMS bearers for an MCPTT group call. + +Figure 10.10.6.1-1: MBMS bearer decision flow + +On a high level the procedure outcome is to use unicast or broadcast bearers for the new MCPTT group call. For an enhanced group call setup procedure, the MBMS bearer may be used to trigger the use of a unicast bearer. + +#### 10.10.6.2 Procedure + +The procedure in figure 10.10.6.2-1 can be used in the following scenarios: + +- Initiate a new call on unicast bearer +- Transfer an ongoing call from broadcast bearer to unicast bearers + +Pre-conditions: + +- There must be an active and announced MBMS bearer + +![Sequence diagram for Application paging over an MBMS bearer between MCPTT client and MCPTT server.](4224f170b677d60f6f86ce95d8dc725a_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + Note right of MCPTT server: 1. Decision to start new +call on unicast or +transfer an ongoing call +to unicast + MCPTT server->>MCPTT client: 2. Application paging + Note left of MCPTT client: 3. Trigger UE to enter +connected mode + Note right of MCPTT server: 4. Stop sending media +over MBMS bearer + MCPTT server->>MCPTT client: 5. DL media over unicast + +``` + +Sequence diagram for Application paging over an MBMS bearer between MCPTT client and MCPTT server. + +**Figure 10.10.6.2-1: Application paging over an MBMS bearer** + +1. The MCPTT server initiates a new MCPTT group call on unicast or decides to transfer an ongoing call to unicast, or may initiate an MCPTT private call. + 2. The MCPTT sends an application paging message on the MBMS bearer to inform the MCPTT client that the MCPTT server will initiate media transmission over a unicast bearer. +- NOTE: The application paging message is sent with the assumption that there are UEs in idle mode. Furthermore, this message is an application level paging message and does not replace the normal paging procedure executed by EPC and RAN. +3. In the case that the UE is in idle mode the UE will initiate a service request to transfer the UE to connected mode. + 4. The MCPTT server stops sending the media over an MBMS bearer. This step is only performed if transferring an ongoing call. + 5. The MCPTT server initiates the media transmission over the unicast bearer. + +Step 4-5 may be performed in parallel with step 2-3. Step 5 will trigger a normal paging in EPC and RAN if the client is still in idle mode. + +## 10.11 MCPTT resource management (on-network) + +### 10.11.1 General + +Procedures for resource management are defined in subclause 10.11 of 3GPP TS 23.280 [16]. + +### 10.11.2 Request for unicast resources at session establishment + +Void + +### 10.11.3 Request for modification of unicast resources + +Void + +### 10.11.4 Management of multicast media bearers + +Void + +### 10.11.5 Request for resources with shared priority + +#### 10.11.5.1 General + +Void + +#### 10.11.5.2 Procedure + +Void + +## 10.12 MCPTT media plane transmissions with partner MCPTT systems (on-network) + +The MCPTT user is able to receive MCPTT media services (e.g. group communication, private calls) from partner MCPTT systems in normal and roaming conditions. In this service delivery model, the media plane transmissions between the MCPTT UE of the user and the partner MCPTT system can be achieved directly or via the primary MCPTT system, selected by the PLMN operator's policy. The protocol used for media plane signalling is non-SIP like RTCP. + +Figure 10.12-1 provides the procedure for media related signalling. + +Figure 10.12-2 provide the procedure for the media transmission (directly) between MCPTT UE of the user and the partner MCPTT system. + +Figure 10.12-3 provides the procedure for the media transmission (via the primary MCPTT system) between MCPTT UE of the user and the partner MCPTT system. + +Pre-conditions: + +1. The MCPTT group is defined in the partner MCPTT system, where the MCPTT client of user receives the MCPTT service. +2. An MCPTT group call is set up and active. +3. The partner MCPTT system is the group host MCPTT server that is hosting the MCPTT group. The corresponding floor control server manages the media corresponding to the group call. +4. Protocol used for signalling of media plane is non-SIP, it can be protocol like RTCP. +5. Media related signalling is sent via the primary MCPTT system. +6. The path for media between the MCPTT UE and partner MCPTT system has been selected to be sent directly to the partner MCPTT system or via the primary MCPTT system based on PLMN operator's policy. + +![Sequence diagram for Figure 10.12-1: Media related signalling communication. Lifelines: Floor participant (MCPTT user), Floor control server (Primary MCPTT system), Floor control server (Partner MCPTT system). Steps: 1. Want to talk, 2. Floor request, 3. Authorization and arbitration, 4. Floor granted.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +``` + +sequenceDiagram + participant User as Floor participant (MCPTT user) + participant PrimaryServer as Floor control server (Primary MCPTT system) + participant PartnerServer as Floor control server (Partner MCPTT system) + Note left of User: 1.Want to talk + User->>PrimaryServer: 2.Floor request + PrimaryServer->>PartnerServer: 2.Floor request + PartnerServer->>PartnerServer: 3.Authorization and arbitration + PartnerServer->>PrimaryServer: 4.Floor granted + PrimaryServer->>User: 4.Floor granted + +``` + +Sequence diagram for Figure 10.12-1: Media related signalling communication. Lifelines: Floor participant (MCPTT user), Floor control server (Primary MCPTT system), Floor control server (Partner MCPTT system). Steps: 1. Want to talk, 2. Floor request, 3. Authorization and arbitration, 4. Floor granted. + +Figure 10.12-1: Media related signalling communication + +![Sequence diagram for Figure 10.12-2: Media communication direct. Lifelines: MCPTT client (MCPTT user), Media distribution function (Primary MCPTT system), Media distribution function (Partner MCPTT system). Steps: 5. Uplink media, 6. Downlink media to send, 7. Downlink media.](d0654bc33a544f31c1cb3e0cd77e0aab_img.jpg) + +``` + +sequenceDiagram + participant Client as MCPTT client (MCPTT user) + participant PrimaryMDF as Media distribution function (Primary MCPTT system) + participant PartnerMDF as Media distribution function (Partner MCPTT system) + Note right of Client: 5.Uplink media + Client->>PartnerMDF: 5.Uplink media + PartnerMDF->>PartnerMDF: 6.Downlink media to send + PartnerMDF->>Client: 7.Downlink media + +``` + +Sequence diagram for Figure 10.12-2: Media communication direct. Lifelines: MCPTT client (MCPTT user), Media distribution function (Primary MCPTT system), Media distribution function (Partner MCPTT system). Steps: 5. Uplink media, 6. Downlink media to send, 7. Downlink media. + +Figure 10.12-2: Media communication direct + +![Sequence diagram for Figure 10.12-3: Media communication via primary MCPTT system. Lifelines: MCPTT client (MCPTT user), Media distribution function (Primary MCPTT system), Media distribution function (Partner MCPTT system). Steps: 5. Uplink media, 6. Downlink media to send, 7. Downlink media.](da90447206621f137780272a2bf807a4_img.jpg) + +``` + +sequenceDiagram + participant Client as MCPTT client (MCPTT user) + participant PrimaryMDF as Media distribution function (Primary MCPTT system) + participant PartnerMDF as Media distribution function (Partner MCPTT system) + Note right of Client: 5.Uplink media + Client->>PrimaryMDF: 5.Uplink media + PrimaryMDF->>PartnerMDF: 5.Uplink media + PartnerMDF->>PartnerMDF: 6.Downlink media to send + PartnerMDF->>PrimaryMDF: 7.Downlink media + PrimaryMDF->>Client: 7.Downlink media + +``` + +Sequence diagram for Figure 10.12-3: Media communication via primary MCPTT system. Lifelines: MCPTT client (MCPTT user), Media distribution function (Primary MCPTT system), Media distribution function (Partner MCPTT system). Steps: 5. Uplink media, 6. Downlink media to send, 7. Downlink media. + +Figure 10.12-3: Media communication via primary MCPTT system + +For media related signalling communication: + +1. An MCPTT user wants to talk. +2. The floor participant corresponding to the MCPTT user sends a floor request message to floor control server (partner MCPTT system) to get the authorization and/or permission to talk. +3. The floor control server (partner MCPTT system) performs the authorization and arbitrates between requests that are in contention (i.e., floor control). +4. If the floor control server (partner MCPTT system) allows the floor participant to talk, a floor granted is provided with permission granted to talk. + +For media communication: + +5. The MCPTT client can now send uplink media data to the media distribution function of the MCPTT server (partner MCPTT system). +6. The media distribution function of the MCPTT server (partner MCPTT system) has downlink media data to transfer. +7. The media distribution function of the MCPTT server (partner MCPTT system) transfers the downlink media to the MCPTT client of the MCPTT user. + +## 10.13 Location information (on-network) + +The MCPTT system makes use of all of the procedures for location management as specified in 3GPP TS 23.280 [16], utilising the CSC-14 reference point between the location management client and location management server and the CSC-15 reference point between the MCPTT server and location management server. + +- The MC service client is the MCPTT client; +- The MC service server is the MCPTT server; +- The MC service group is the MCPTT group; +- The MC service ID is the MCPTT ID; and +- The MC service group ID is the MCPTT group ID. + +## 10.14 Ambient listening call + +### 10.14.1 General + +The ambient listening call is a type of a private MCPTT call that only allows a "listened to" user to transmit media to a "listening" user such that there is no indication on the MCPTT UE of the "listened to" user about the call and the media transmission. + +NOTE 1: "listened to" user refers to the user who is transmitting media in an ambient listening call. + +NOTE 2: "listening" user refers to the user who is receiving media in an ambient listening call. + +There are two types of ambient listening call as below: + +- Remotely initiated ambient listening is initiated by the authorized user (e.g., dispatcher) who wants to listen to another user. In this case, the "listened to" user is the called party, and shall automatically accept the call without causing any indication about the call and transmit the media to the "listening" user. +- Locally initiated ambient listening is initiated by an authorized user who wants another user to listen to the MCPTT UE communication. In this case, the "listened to" user is the calling party and shall automatically transmit the media to the "listening" user without causing any indication about the call processing and media transmission. + +### 10.14.2 Information flows for ambient listening call + +#### 10.14.2.1 Ambient listening call request + +Table 10.14.2.1-1 describes the information flow ambient listening call request from the MCPTT client to the MCPTT server and MCPTT server to the MCPTT client. + +**Table 10.14.2.1-1: Ambient listening call request** + +| Information Element | Status | Description | +|------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the "listening" user | +| MCPTT ID | M | The MCPTT ID of the "listened to" user | +| SDP offer | M | Media parameters of MCPTT client. | +| Ambient listening type | M | The ambient listening type indicates remotely initiated ambient listening call or locally initiated ambient listening call. | + +#### 10.14.2.2 Ambient listening call response + +Table 10.14.2.2-1 describes the information flow ambient listening call response from the MCPTT client to the MCPTT server and MCPTT server to the MCPTT client. + +**Table 10.14.2.2-1: Ambient listening call response** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------| +| MCPTT ID | M | The MCPTT ID of the "listening" user | +| MCPTT ID | M | The MCPTT ID of the "listened to" user | +| SDP answer | M | Media parameters selected | + +#### 10.14.2.3 Ambient listening call release request + +Table 10.14.2.3-1 describes the information flow ambient listening call release request from the MCPTT client to the MCPTT server and MCPTT server to the MCPTT client. + +**Table 10.14.2.3-1: Ambient listening call release request** + +| Information Element | Status | Description | +|------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the "listening" user | +| MCPTT ID | M | The MCPTT ID of the "listened to" user | +| Ambient listening type | M | The ambient listening type indicates a remotely initiated ambient listening call or a locally initiated ambient listening call. | + +#### 10.14.2.4 Ambient listening call release response + +Table 10.14.2.4-1 describes the information flow ambient listening call release response from the MCPTT client to the MCPTT server and MCPTT server to the MCPTT client. + +**Table 10.14.2.4-1: Ambient listening call release response** + +| Information Element | Status | Description | +|------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the "listening" user | +| MCPTT ID | M | The MCPTT ID of the "listened to" user | +| Ambient listening type | M | The ambient listening type indicates a remotely initiated ambient listening call or a locally initiated ambient listening call. | + +#### 10.14.2.5 Ambient listening call release notification + +Table 10.14.2.5-1 describes the information flow ambient listening call release notification from the MCPTT server to the MCPTT client. + +**Table 10.14.2.5-1: Ambient listening call release notification** + +| Information Element | Status | Description | +|------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the "listening" user | +| MCPTT ID | M | The MCPTT ID of the "listened to" user | +| Call release reason | M | The reason for call release by the MCPTT server | +| Ambient listening type | M | The ambient listening type indicates a remotely initiated ambient listening call or a locally initiated ambient listening call. | + +### 10.14.3 Ambient listening call procedures + +#### 10.14.3.1 Remotely initiated ambient listening call setup + +The MCPTT service provides the capability for an authorised user to initiate a remotely initiated ambient listening call at an MCPTT client. + +Figure 10.14.3.1-1 illustrates the information flow for remotely initiated ambient listening call setup. + +Pre-conditions: + +- MCPTT client 1 is the client of the authorized user who is authorized to invoke a remotely initiated ambient listening call to be set up at the requested MCPTT client 2. +- MCPTT user 1 is the "listening" user at MCPTT client 1, and MCPTT user 2 is the "listened to" user at MCPTT client 2. + +![Sequence diagram illustrating the remotely initiated ambient listening call setup. The diagram shows interactions between MCPTT client 1, MCPTT server, and MCPTT client 2. The steps are: 1. MCPTT client 1 sends an 'Ambient listening call request' to the MCPTT server. 2. The MCPTT server sends an 'Authorize ambient listening call request' to MCPTT client 1. 3. The MCPTT server sends an 'Ambient listening call request' to MCPTT client 2. 4. MCPTT client 2 sends an 'Ambient listening call response' to the MCPTT server. 5. The MCPTT server sends an 'Ambient listening call response' to MCPTT client 1. 6. The MCPTT server sends a 'Floor granted' message to MCPTT client 2. 7. The MCPTT server sends a 'Floor taken' message to MCPTT client 1. 8. A 'Media flow' is established between MCPTT client 1 and MCPTT client 2 via the MCPTT server.](e53e04cbd5986eeb9e7faa71b3c9bb35_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note right of MCPTT server: 2.Authorize ambient listening call request + MCPTT client 1->>MCPTT server: 1.Ambient listening call request + MCPTT server->>MCPTT client 1: 2.Authorize ambient listening call request + MCPTT server->>MCPTT client 2: 3.Ambient listening call request + MCPTT client 2->>MCPTT server: 4.Ambient listening call response + MCPTT server->>MCPTT client 1: 5.Ambient listening call response + MCPTT server->>MCPTT client 2: 6.Floor granted + MCPTT server->>MCPTT client 1: 7.Floor taken + Note left of MCPTT server: 8.Media flow + Note right of MCPTT server: 8.Media flow + +``` + +Sequence diagram illustrating the remotely initiated ambient listening call setup. The diagram shows interactions between MCPTT client 1, MCPTT server, and MCPTT client 2. The steps are: 1. MCPTT client 1 sends an 'Ambient listening call request' to the MCPTT server. 2. The MCPTT server sends an 'Authorize ambient listening call request' to MCPTT client 1. 3. The MCPTT server sends an 'Ambient listening call request' to MCPTT client 2. 4. MCPTT client 2 sends an 'Ambient listening call response' to the MCPTT server. 5. The MCPTT server sends an 'Ambient listening call response' to MCPTT client 1. 6. The MCPTT server sends a 'Floor granted' message to MCPTT client 2. 7. The MCPTT server sends a 'Floor taken' message to MCPTT client 1. 8. A 'Media flow' is established between MCPTT client 1 and MCPTT client 2 via the MCPTT server. + +**Figure 10.14.3.1-1: Remotely initiated ambient listening call** + +1. MCPTT client 1 initiates a remotely initiated ambient listening call by sending the ambient listening call request to the MCPTT server. The remotely initiated ambient listening call type is included. +2. The MCPTT server performs an authorization check for the authorized user 1 for the remotely initiated ambient listening call. If authorization fails, the MCPTT server provides a failure response to MCPTT client 1. +3. The MCPTT server sends the ambient listening call request to MCPTT client 2. +4. MCPTT client 2 returns the ambient listening call response to the MCPTT server. +5. MCPTT server provides an ambient listening call response to MCPTT client 1, indicating whether the call is set up successfully or not. +6. The floor control server of the MCPTT server then sends a floor granted to MCPTT client 2 according to the ambient listening type received in step 1. +7. Accordingly, the floor control server of the MCPTT server sends a floor taken to MCPTT client 1. +8. After receiving the floor granted message at the MCPTT client 2, the media is transmitted from MCPTT client 2 to MCPTT client 1. + +NOTE: MCPTT client 2 does not provide any indication of the ambient listening call release to its user. + +#### 10.14.3.2 Locally initiated ambient listening call setup + +The MCPTT service provides the capability for an authorised user to initiate a locally initiated ambient listening call at an MCPTT client. + +Figure 10.14.3.2-1 illustrates the information flow for locally initiated ambient listening call setup. + +Pre-conditions: + +- MCPTT client 2 is the client of the authorized user who is authorized to invoke a locally initiated ambient listening call to be set up at the requested MCPTT client 1. +- MCPTT user 1 is the "listening" user at MCPTT client 1, and MCPTT user 2 is the "listened to" user at MCPTT client 2. + +![Sequence diagram for locally initiated ambient listening call setup. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2. The sequence starts with MCPTT client 2 sending an 'Ambient listening call request' to the MCPTT server. The server performs an 'Authorize ambient listening call request' (shown in a sub-box). Then, the server sends an 'Ambient listening call request' to MCPTT client 1. MCPTT client 1 responds with an 'Ambient listening call response' to the server. The server then sends an 'Ambient listening call response' to MCPTT client 2. Next, the server sends a 'Floor granted' message to MCPTT client 2 and a 'Floor taken' message to MCPTT client 1. Finally, a 'Media flow' is established from MCPTT client 2 to MCPTT client 1 via the server.](f43d225d8fed2845b8d7e5afecbfe636_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 2 + participant MCPTT server + participant MCPTT client 1 + + Note right of MCPTT server: 2.Authorize ambient listening call request + MCPTT client 2->>MCPTT server: 1.Ambient listening call request + MCPTT server->>MCPTT client 1: 3.Ambient listening call request + MCPTT client 1->>MCPTT server: 4.Ambient listening call response + MCPTT server->>MCPTT client 2: 5.Ambient listening call response + MCPTT server->>MCPTT client 2: 6. Floor granted + MCPTT server->>MCPTT client 1: 7. Floor taken + Note left of MCPTT server: 8.Media flow + Note right of MCPTT server: 8.Media flow + +``` + +Sequence diagram for locally initiated ambient listening call setup. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2. The sequence starts with MCPTT client 2 sending an 'Ambient listening call request' to the MCPTT server. The server performs an 'Authorize ambient listening call request' (shown in a sub-box). Then, the server sends an 'Ambient listening call request' to MCPTT client 1. MCPTT client 1 responds with an 'Ambient listening call response' to the server. The server then sends an 'Ambient listening call response' to MCPTT client 2. Next, the server sends a 'Floor granted' message to MCPTT client 2 and a 'Floor taken' message to MCPTT client 1. Finally, a 'Media flow' is established from MCPTT client 2 to MCPTT client 1 via the server. + +Figure 10.14.3.1-1: Locally initiated ambient listening call + +1. MCPTT client 2 initiates a locally initiated ambient listening call by sending the ambient listening call request to the MCPTT server. The locally initiated ambient listening call type is included. + +2. The MCPTT server performs an authorization check for the authorized user 2 for the locally initiated ambient listening call. If authorization fails, the MCPTT server provides a failure response to MCPTT client 2. +3. The MCPTT server sends the ambient listening call request to MCPTT client 1. +4. MCPTT client 1 returns the ambient listening call response to the MCPTT server. +5. MCPTT server provides an ambient listening call response to MCPTT client 2, indicating whether the call is set up successfully or not. +6. The floor control server of the MCPTT server then sends a floor granted to MCPTT client 2 according to the ambient listening type received in step 1. +7. Accordingly, the floor control server of the MCPTT server sends a floor taken to MCPTT client 1. +8. After receiving the floor granted message at the MCPTT client 2, the media is transmitted from MCPTT client 2 to MCPTT client 1. + +NOTE: MCPTT client 2 does not provide any indication of the ambient listening call release to its user. + +#### 10.14.3.3 Ambient listening call release – server initiated + +Figure 10.14.3.3-1 illustrates the information flow for ambient listening call release – server initiated when trigger by the MCPTT administrator. This procedure is applied for both remotely initiated ambient listening call and the locally initiated ambient listening call. + +Pre-conditions: + +- MCPTT client 1 is the MCPTT client of the authorized user, who initiated the ambient listening call at MCPTT client 2. +- There is an ongoing ambient listening call between MCPTT client 2 and MCPTT client 1. +- MCPTT user 1 is the current user at MCPTT client 1 who is listening, and MCPTT user 2 is the current user at MCPTT client 2 who is being listened to. + +![Sequence diagram showing the ambient listening call release process. Lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2. The process starts with '1.Ambient listening call release Is triggered' on the server. The server sends '2.Ambient listening call release request' to client 2. Client 2 performs '3. Stop transmitting media' and sends '4.Ambient listening call release response' back to the server. The server then sends '5. Ambient listening call release notification' to client 1, which leads to '6.Notify user' on client 1.](6116b1a533010c170fc526ec513ba0b8_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note right of MCPTT server: 1.Ambient listening call release Is triggered + MCPTT server->>MCPTT client 2: 2.Ambient listening call release request + Note right of MCPTT client 2: 3. Stop transmitting media + MCPTT client 2->>MCPTT server: 4.Ambient listening call release response + MCPTT server->>MCPTT client 1: 5. Ambient listening call release notification + Note left of MCPTT client 1: 6.Notify user + +``` + +Sequence diagram showing the ambient listening call release process. Lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2. The process starts with '1.Ambient listening call release Is triggered' on the server. The server sends '2.Ambient listening call release request' to client 2. Client 2 performs '3. Stop transmitting media' and sends '4.Ambient listening call release response' back to the server. The server then sends '5. Ambient listening call release notification' to client 1, which leads to '6.Notify user' on client 1. + +**Figure 10.14.3.3-1: Ambient listening call release – server initiated** + +1. The ambient listening call release is triggered by the MCPTT administrator or by one of the following events: + - the MCPTT server receives MCPTT call requests towards MCPTT client 2; or + - the MCPTT client 2 initiates MCPTT call requests; +2. The MCPTT server sends an ambient listening call release request to MCPTT client 2. +3. MCPTT client 2 stops transmitting media to MCPTT client 1. + +NOTE: MCPTT client 2 does not provide any indication of the ambient listening call release to its user. + +4. MCPTT client 2 provides an ambient listening call release response to the MCPTT server. +5. The MCPTT server sends an ambient listening call release notification to MCPTT client 1 together with a reason code identifying that the call was released. +6. MCPTT client 1 notifies the authorized user 1. + +#### 10.14.3.4 Remotely initiated ambient listening call release – "listening" user initiated + +Figure 10.14.3.4-1 illustrates the information flow for ambient listening call release – "listening" user initiated. This procedure is applied for both remotely initiated ambient listening call and the locally initiated ambient listening call. + +Pre-conditions: + +- MCPTT client 1 is the MCPTT client of the authorized user, who is authorized to release the ambient listening call at MCPTT client 2. +- There is an ongoing ambient listening call between MCPTT client 2 and MCPTT client 1. +- MCPTT user 1 is the "listening" user at MCPTT client 1, and MCPTT user 2 is the "listened to" user at MCPTT client 2. + +![Sequence diagram for ambient listening call release – 'listening' user initiated. The diagram shows five steps: 1. MCPTT client 1 sends an 'Ambient listening call release request' to the MCPTT server. 2. The MCPTT server sends an 'Ambient listening call release request' to MCPTT client 2. 3. MCPTT client 2 sends a 'Stop transmitting media' message. 4. MCPTT client 2 sends an 'Ambient listening call release response' to the MCPTT server. 5. The MCPTT server sends an 'Ambient listening call release response' to MCPTT client 1.](e5293502d8d5885d71defe1150aa12fc_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note right of MCPTT client 2: 3.Stop transmitting media + MCPTT client 1->>MCPTT server: 1.Ambient listening call release request + MCPTT server->>MCPTT client 2: 2.Ambient listening call release request + MCPTT client 2->>MCPTT server: 4.Ambient listening call release response + MCPTT server->>MCPTT client 1: 5.Ambient listening call release response + +``` + +Sequence diagram for ambient listening call release – 'listening' user initiated. The diagram shows five steps: 1. MCPTT client 1 sends an 'Ambient listening call release request' to the MCPTT server. 2. The MCPTT server sends an 'Ambient listening call release request' to MCPTT client 2. 3. MCPTT client 2 sends a 'Stop transmitting media' message. 4. MCPTT client 2 sends an 'Ambient listening call release response' to the MCPTT server. 5. The MCPTT server sends an 'Ambient listening call release response' to MCPTT client 1. + +**Figure 10.14.3.4-1: Ambient listening call release – "listening" user initiated** + +1. The authorized user 1 at MCPTT client 1 initiates the ambient listening call release by sending an ambient listening call release request to the MCPTT server. +2. The MCPTT server provides an ambient listening call release request to MCPTT client 2. +3. MCPTT client 2 stops transmitting media to MCPTT client 1. + +NOTE: MCPTT client 2 does not provide any indication of the ambient listening call release to its user. + +4. MCPTT client 2 provides an ambient listening call release response to the MCPTT server. +5. The MCPTT server provides the ambient listening call release response to MCPTT client 1. + +#### 10.14.3.5 Ambient listening call release – "listened to" user initiated + +Figure 10.14.3.5-1 illustrates the information flow for ambient listening call release – "listened to" user initiated. This procedure is only applied for the locally initiated ambient listening call. + +Pre-conditions: + +- There is an ongoing ambient listening call between MCPTT client 1 and MCPTT client 2. + +- MCPTT user 1 is the "listening" user at MCPTT client 1, and MCPTT user 2 is the "listened to" user at MCPTT client 2. +- MCPTT client 2 is the MCPTT client of the authorized user, who is authorized to release the locally initiated ambient listening call at MCPTT client 2. + +![Sequence diagram for Ambient listening call release – 'listened to' user initiated. The diagram shows three lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2. The sequence of messages is: 1. MCPTT client 2 sends an 'Ambient listening call release request' to the MCPTT server. 2. The MCPTT server sends an 'Ambient listening call release request' to MCPTT client 1. 3. MCPTT client 1 sends a 'Notify user' message to itself. 4. MCPTT client 1 sends an 'Ambient listening call release response' to the MCPTT server. 5. The MCPTT server sends an 'Ambient listening call release response' to MCPTT client 2. 6. MCPTT client 1 sends a 'Stop transmitting media' message to itself.](c7e27041e661260fd0c8e89c763bb32e_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 2 + participant MCPTT server + participant MCPTT client 1 + Note left of MCPTT client 1: 3.Notify user + Note right of MCPTT client 2: 6.Stop transmitting media + MCPTT client 2->>MCPTT server: 1.Ambient listening call release request + MCPTT server->>MCPTT client 1: 2.Ambient listening call release request + MCPTT client 1->>MCPTT client 1: 3.Notify user + MCPTT client 1->>MCPTT server: 4.Ambient listening call release response + MCPTT server->>MCPTT client 2: 5.Ambient listening call release response + MCPTT client 1->>MCPTT client 1: 6.Stop transmitting media + +``` + +Sequence diagram for Ambient listening call release – 'listened to' user initiated. The diagram shows three lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2. The sequence of messages is: 1. MCPTT client 2 sends an 'Ambient listening call release request' to the MCPTT server. 2. The MCPTT server sends an 'Ambient listening call release request' to MCPTT client 1. 3. MCPTT client 1 sends a 'Notify user' message to itself. 4. MCPTT client 1 sends an 'Ambient listening call release response' to the MCPTT server. 5. The MCPTT server sends an 'Ambient listening call release response' to MCPTT client 2. 6. MCPTT client 1 sends a 'Stop transmitting media' message to itself. + +**Figure 10.14.3.5-1: Ambient listening call release – "listened to" user initiated** + +1. The authorized user 2 at MCPTT client 2 initiates the ambient listening call release by sending an ambient listening call release request to the MCPTT server. +2. The MCPTT server provides an ambient listening call release request to MCPTT client 1. +3. MCPTT client 1 is notified about the ambient listening call release. +4. MCPTT client 1 provides an ambient listening call release response to the MCPTT server. +5. The MCPTT server provides the ambient listening call release response to MCPTT client 2. +6. MCPTT client 1 stops transmitting media to MCPTT client 2. + +NOTE: MCPTT client 1 does not provide any indication of the ambient listening call release to its user. + +## 10.15 First-to-answer call setup + +### 10.15.1 Description + +Figure 10.15.3-1 describes the basic procedure for the MCPTT client initiating MCPTT first-to-answer call. The flow may use a floor request in the MCPTT call request indicating that the originator will be given the floor when the call starts and eliminates the need for a separate initial floor request message during media plane establishment. Alternatively, the call initiation may be sent without the floor request, which allows the called party to request the floor first. For a MCPTT first-to-answer call without floor control, floor control is not established. + +Figure 10.15.3-1 also describes the handling of private calls when a functional alias replaces the MCPTT ID as target address. A functional alias can be simultaneously used by more than one MCPTT user, i.e. multiple MCPTT clients can activate the same functional alias. + +### 10.15.2 Information flows for first-to-answer call + +#### 10.15.2.1 MCPTT first-to-answer call request (MCPTT client to MCPTT server) + +Table 10.15.2.1-1 describes the information flow MCPTT first-to-answer call request from the MCPTT client to the MCPTT server. + +**Table 10.15.2.1-1: MCPTT first-to-answer call request (MCPTT client to MCPTT server) information elements** + +| Information Element | Status | Description | +|----------------------------------------------|--------|---------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT ID list (see NOTE) | O | The list of MCPTT IDs of the called party | +| Functional alias (see NOTE) | O | The functional alias of the called party | +| Use floor control indication | M | This element indicates whether floor control will be used for the private call. | +| SDP offer | O | Media parameters of MCPTT client. | +| Implicit floor request | O | An indication that the user is also requesting the floor. | +| Location information | O | Location of the calling party | +| NOTE: At least one identity must be present. | | | + +#### 10.15.2.2 MCPTT first-to-answer call request (MCPTT server to MCPTT client) + +Table 10.15.2.2-1 describes the information flow MCPTT first-to-answer call request from the MCPTT server to the MCPTT client. + +**Table 10.15.2.2-1: MCPTT first-to-answer call request (MCPTT server to MCPTT client) information elements** + +| Information Element | Status | Description | +|------------------------------|--------|---------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Functional alias | O | The functional alias of the called party | +| Use floor control indication | M | This element indicates whether floor control will be used for the private call. | +| SDP offer | M | Media parameters of MCPTT client. | +| Implicit floor request | O | An indication that the user is also requesting the floor. | + +#### 10.15.2.3 MCPTT first-to-answer call response (MCPTT client to MCPTT server) + +Table 10.15.2.3-1 describes the information flow MCPTT first-to-answer call response from the MCPTT client to the MCPTT server. + +**Table 10.15.2.3-1: MCPTT first-to-answer call response (MCPTT client to MCPTT server) information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------| +|---------------------|--------|-------------| + +| | | | +|------------------|---|-------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Functional alias | O | The functional alias of the called party | +| SDP answer | M | Media parameters selected | + +#### 10.15.2.4 MCPTT first-to-answer call response (MCPTT server to MCPTT client) + +Table 10.15.2.4-1 describes the information flow MCPTT first-to-answer call response from the MCPTT server to the MCPTT client. + +**Table 10.15.2.4-1: MCPTT first-to-answer call response (MCPTT server to MCPTT client) information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Functional alias | O | The functional alias of the called party | +| SDP answer | M | Media parameters selected | + +#### 10.15.2.5 MCPTT first-to-answer call cancel request (MCPTT server to MCPTT client) + +Table 10.15.2.5-1 describes the information flow MCPTT first-to-answer call cancel request from the MCPTT server to the MCPTT client. + +**Table 10.15.2.5-1: MCPTT first-to-answer call cancel request (MCPTT server to MCPTT client) information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | + +#### 10.15.2.6 MCPTT first-to-answer call cancel response (MCPTT client to MCPTT server) + +Table 10.15.2.6-1 describes the information flow MCPTT first-to-answer call cancel response from the MCPTT client to the MCPTT server. + +**Table 10.15.2.6-1: MCPTT first-to-answer call cancel response (MCPTT client to MCPTT server) information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------| +| MCPTT ID | M | The MCPTT ID of the called party | + +### 10.15.3 Procedure + +All clients are served by the primary MCPTT service provider in figure 10.15.3-1. + +Pre-conditions: + +1. The calling MCPTT user has selected first-to-answer call. +2. MCPTT clients 1 to n are registered and their respective users, MCPTT user 1 to MCPTT user n, are authenticated and authorized to use the MCPTT service, as per procedure in subclause 10.2. +3. MCPTT clients 2 to n have activated the same functional alias. +4. The MCPTT server has subscribed to the MCPTT functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for MCPTT first-to-answer call within the same MCPTT system. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3, MCPTT client n. The process involves a request from client 1, server authorization, notification of other clients, and subsequent responses and cancellations.](ffe0fef452a0ae9a20253c319c54e13c_img.jpg) + +Home MCPTT service provider + +``` + +sequenceDiagram + participant C1 as MCPTT client 1 + participant S as MCPTT server + participant C2 as MCPTT client 2 + participant C3 as MCPTT client 3 + participant Cn as MCPTT client n + + Note left of C1: 1. initiate first-to-answer call + C1->>S: 2. MCPTT first-to-answer call request + Note right of S: 3. Authorize request + Note right of S: 4. Determine the list of users to send +request based on request in step 2 + S->>C2: 5a. MCPTT first-to-answer call request + Note right of C2: 6a. Notify call + S->>C3: 5b. MCPTT first-to-answer call request + Note right of C3: 6b. Notify call + S->>Cn: 5c. MCPTT first-to-answer call request + Note right of Cn: 6c. Notify call + C2->>S: 7. MCPTT first-to-answer call response + S->>C1: 8. MCPTT first-to-answer call response + S->>C3: 9a. MCPTT first-to-answer call cancel request + Note right of C3: 9b. Notify call cancel + S->>Cn: 10a. MCPTT first-to-answer call cancel request + Note right of Cn: 10b. Notify call cancel + Note over C1,C2: 11. Media plane established + C3->>S: 12. MCPTT first-to-answer call cancel response + Cn->>S: 13. MCPTT first-to-answer call cancel response + +``` + +Sequence diagram for MCPTT first-to-answer call within the same MCPTT system. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3, MCPTT client n. The process involves a request from client 1, server authorization, notification of other clients, and subsequent responses and cancellations. + +**Figure 10.15.3-1: MCPTT first-to-answer call – MCPTT users in the same MCPTT system** + +1. MCPTT user at MCPTT client 1 would like to establish a MCPTT first-to-answer call indicating a set of potential target recipients or by calling a functional alias. For a MCPTT first-to-answer call with floor control, floor control is to be established. For first-to-answer call without floor control, both users will have the ability to transmit without floor arbitration. +2. MCPTT client 1 sends an MCPTT first-to-answer call request including a set of potential target recipients to the MCPTT server (via the SIP core as defined in 3GPP TS 23.228 [5]), using either a list of MCPTT IDs or a functional alias. The MCPTT first-to-answer call request contains the MCPTT ID and may contain the functional alias of originating user and an SDP offer containing one or more media types. The MCPTT first-to-answer call request may also contain a data element that indicates that MCPTT client 1 is requesting the floor, for a first-to- + +answer call with floor control. The MCPTT client 1 includes a first-to-answer call indication that the call is to be established only to the first answering user. + +3. The MCPTT server confirms that MCPTT users are authorized for the call and whether the MCPTT user at MCPTT client 1 is authorized to initiate a first-to-answer call. The MCPTT server checks whether the provided functional alias of the calling user, if present, can be used and has been activated for the MCPTT user. +4. The MCPTT server determines the list of MCPTT users to send MCPTT first-to-answer call request, based on a set of potential target recipients obtained from the request from MCPTT client 1. Alternatively, when a functional alias is used as target address, the MCPTT server resolves the functional alias to a corresponding list of related MCPTT IDs of MCPTT client 2 to MCPTT client n who have activated the functional alias. The functional alias must have been activated to identify the MCPTT IDs of the called users. + +**Editor's note: Whether the MCPTT server shall proceed only with those MCPTT IDs which are allowed to be called by MCPTT client 1 is FFS.** + +5a, 5b, 5c. The MCPTT server includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request and sends similar MCPTT first-to-answer call request to each potential target recipient, including the MCPTT ID and, if present, the functional alias of the calling MCPTT user at MCPTT client 1. If one or more called MCPTT users have registered to the MCPTT service with multiple MCPTT UEs and has designated the MCPTT UE for receiving the calls, then the incoming MCPTT first-to-answer call request is delivered only to the designated MCPTT UE. Otherwise MCPTT first-to-answer call request may be delivered to all the registered MCPTT UEs. If a functional alias is present and more than one MCPTT client has activated that functional alias, then the MCPTT server sends an MCPTT first-to-answer call request to each MCPTT client. + +6a, 6b, 6c. The MCPTT users are alerted, regardless of the commencement mode. + +7. MCPTT user at MCPTT client 2 accepted the call which causes MCPTT client 2 to send an MCPTT first-to-answer call response to the MCPTT server. + +NOTE 1: MCPTT server does not divert MCPTT first-to-answer call to voicemail if MCPTT user at MCPTT client 2 has not accepted the incoming call. + +8. The MCPTT server sends an MCPTT first-to-answer call response to MCPTT client 1 indicating that MCPTT user at MCPTT client 2 has accepted the call, including the accepted media parameters. + +9a. The MCPTT server sends a MCPTT first-to-answer call cancel request to MCPTT client 3. + +9b. Optionally, MCPTT client 3 notifies the user. + +10a. The MCPTT server sends a MCPTT first-to-answer call cancel request to MCPTT client n. + +10b. Optionally, MCPTT client n notifies the user. + +11. The media plane for communication is established. Either user can transmit media individually when using floor control. For successful call establishment for first-to-answer call with floor request from MCPTT client 1, the floor participant associated with MCPTT client 1 is granted the floor initially. At the same time the floor participant associated with MCPTT client 2 is informed that the floor is taken. For a first-to-answer call without floor control both users are allowed to transmit simultaneously. + +NOTE 2: Prior to media plane establishment, MCPTT client 1 and MCPTT client 2 set up a security association for the media, if end-to-end encryption is used for this call. + +**Editor's note: It is assumed that MCPTT client 1 initiates the set up as is done for private calls, but the details for the media security establishment are FFS and are in the scope of SA3. Results provided by SA3 may require changes in the procedure.** + +NOTE 3: The steps 9a, 10a and 11 can occur in any order and can also be performed in parallel. + +12. MCPTT client 3 sends an MCPTT first-to-answer cancel call response. + +13. MCPTT client n sends an MCPTT first-to-answer cancel call response. + +## 10.16 Remotely initiated MCPTT call + +### 10.16.1 General + +A remotely initiated MCPTT call allows an authorized user to cause a remote MCPTT UE to initiate a call by itself, without its user explicitly initiating the call. + +### 10.16.2 Information flows for remotely initiated MCPTT call + +#### 10.16.2.1 Remotely initiated MCPTT call request + +Table 10.16.2.1-1 describes the information flow remotely initiated MCPTT call request from the MCPTT client to the MCPTT server and from the MCPTT server to MCPTT client. + +**Table 10.16.2.1-1: remotely initiated MCPTT call request information elements** + +| Information Element | Status | Description | +|--------------------------------------------------------|----------|------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the called party (remote) | +| Notification to remote user of remotely initiated call | M | Use to determine whether the called party (remote) receives any indication of the remotely initiated MCPTT call. | +| MCPTT ID | O (NOTE) | For a remotely initiated MCPTT private call the MCPTT User ID to be called | +| MCPTT Group | O (NOTE) | For a remotely initiated MCPTT group call to use. | +| NOTE: One and only one of these shall be present. | | | + +#### 10.16.2.2 Remotely initiated MCPTT call response + +Table 10.16.2.2-1 describes the information flow remotely initiated MCPTT call response from the MCPTT client to the MCPTT server and from the MCPTT server to MCPTT client. + +**Table 10.16.2.2-1: Remotely initiated MCPTT call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Result | M | Result of the remotely initiated MCPTT call request – success or fail. | + +### 10.16.3 Procedure + +#### 10.16.3.1 Remotely initiated MCPTT call request + +The remotely initiated MCPTT call request procedure includes the initial remotely initiated MCPTT call request from the MCPTT user to the remote UE and either the MCPTT private call procedures or the MCPTT group call procedures originating at the remote UE. + +Procedures in figure 10.16.3.1-1 show the signalling control plane procedures for the MCPTT client initiating a remotely initiated MCPTT call request with the chosen MCPTT user. + +Pre-conditions: + +1. If the MCPTT user on MCPTT client 1 wants the resulting remotely initiated MCPTT call to be: + - a. an MCPTT group call, then MCPTT user 2 on MCPTT client 2 is an affiliated MCPTT group member of the MCPTT group that is the target of the remotely initiated MCPTT call. Otherwise prior to these procedures + +the MCPTT user 1 on MCPTT client 1 can use existing procedures (e.g., remotely change MCPTT group affiliation (10.3.5.1.1), if authorized, to satisfy the necessary preconditions for the MCPTT user 2 on MCPTT client 2 to initiate a MCPTT group call from that MCPTT group. + +- b. an MPCTT private call, then the MCPTT user 2 on MCPTT client 2 is permitted to initiate an MCPTT private call to the identified MCPTT user. + +![Sequence diagram illustrating the 'Remotely initiated MCPTT call request' process between MCPTT client 1, MCPTT server, and MCPTT client 2.](ff87509cc2b267501d910a2d9f9054ac_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note left of MCPTT client 1: 1. Remotely initiated MCPTT call + MCPTT client 1->>MCPTT server: 2. Remotely initiated MCPTT call request + Note right of MCPTT server: 3. Authorize request + MCPTT server->>MCPTT client 2: 4. Remotely initiated MCPTT call request + Note right of MCPTT client 2: 5. Notify user + MCPTT client 2-->>MCPTT server: 6. Remotely initiated MCPTT call response + MCPTT server-->>MCPTT client 1: 7. Remotely initiated MCPTT call response + Note right of MCPTT client 1: 8. Initiate MCPTT call +``` + +The diagram is a sequence diagram with three lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2. The sequence of messages is as follows: 1. A self-message on MCPTT client 1 labeled '1. Remotely initiated MCPTT call'. 2. A solid arrow from MCPTT client 1 to MCPTT server labeled '2. Remotely initiated MCPTT call request'. 3. A self-message on MCPTT server labeled '3. Authorize request'. 4. A solid arrow from MCPTT server to MCPTT client 2 labeled '4. Remotely initiated MCPTT call request'. 5. A dashed self-message on MCPTT client 2 labeled '5. Notify user'. 6. A dashed arrow from MCPTT client 2 to MCPTT server labeled '6. Remotely initiated MCPTT call response'. 7. A dashed arrow from MCPTT server to MCPTT client 1 labeled '7. Remotely initiated MCPTT call response'. 8. A solid arrow from MCPTT client 1 to MCPTT client 2 labeled '8. Initiate MCPTT call'. + +Sequence diagram illustrating the 'Remotely initiated MCPTT call request' process between MCPTT client 1, MCPTT server, and MCPTT client 2. + +**Figure 10.16.3.1-1: Remotely initiated MCPTT call request** + +1. MCPTT user on MCPTT client 1 initiates a remotely initiated MCPTT call request to the MCPTT user of MCPTT client 2. +2. MCPTT client 1 sends a remotely initiated MCPTT call request towards the MCPTT server. +3. MCPTT server checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a remotely initiated MCPTT call request. +4. If authorized, MCPTT server sends the corresponding remotely initiated MCPTT call request towards the MCPTT client 2. +5. Based on the received information the receiving MCPTT client 2 may notify the user of the remotely initiated MCPTT call request. +6. Optionally the receiving MCPTT client 2 sends a remotely initiated MCPTT call response to the MCPTT server. +7. After receiving the remotely initiated MCPTT call response from MCPTT client 2, the MCPTT server informs the MCPTT client 1 about successful remotely initiated MCPTT call request. + +NOTE 1: Step 6 and step 7 might not be sent, since it could be determined that the remotely initiated MCPTT call was successful by receiving the MCPTT call initiated by MCPTT client 2. + +8. Based on the received information the MCPTT client 2 initiates an MCPTT call (either an MCPTT group call or an MCPTT private call) using the normal MCPTT call establishment procedures (10.6.2.3.1.1.2 or 10.7.2.2) with implicit floor request. + +NOTE 2: Step 6 and step 7 are received in this order. However, step 6 or step 7 or both might occur before or after step 8. + +The result of these procedures is an on-going MCPTT (group or private) call which includes MCPTT client 1. + +## 10.17 Support for multiple devices + +### 10.17.1 General + +An MCPTT user may be authorized to use the MCPTT service from multiple MCPTT UEs as per the procedure in subclause 10.2. + +If an MCPTT server receives a service authorization request for an MCPTT user who is previously MCPTT service authorized on another MCPTT UE, then the MCPTT server shall process this service authorization request as described in subclause 10.2. In the MCPTT service authorization response to the MCPTT user, the MCPTT server shall also indicate that the MCPTT user is already MCPTT service authorized from another MCPTT UE. + +**Editor's Note:** How to log off remotely from MCPTT clients on one or more other MCPTT UEs that the MCPTT user is already MCPTT service authorized from is FFS. + +## 10.18 Subscription and notification for functional alias + +### 10.18.1 General + +The MCPTT server obtains the list of MCPTT users who have activated a functional alias from the functional alias controlling MCPTT server via subscription and notification mechanisms. + +**Editor's note:** It is FFS whether this procedure is general to all the MC services and can be moved to 3GPP TS 23.280. + +### 10.18.2 Information flows for subscription and notification for functional alias + +#### 10.18.2.1 Subscribe functional alias request + +Table 10.18.2.1-1 describes the information flow subscribe functional alias request from the MCPTT server to the functional alias controlling MCPTT server. + +**Table 10.18.2.1-1: Subscribe functional alias request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------| +| Functional alias | M | The functional alias for which subscription is requested by the MCPTT server. | + +#### 10.18.2.2 Subscribe functional alias response + +Table 10.18.2.2-1 describes the information flow subscribe functional alias response from the functional alias controlling MCPTT server to the MCPTT server. + +**Table 10.18.2.2-1: Subscribe functional alias response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------| +| Functional alias | M | The functional alias for which subscription is requested by the MCPTT server. | +| Status | M | Success or failure of the request | + +#### 10.18.2.3 Notify functional alias request + +Table 10.18.2.3-1 describes the information flow notify functional alias request from the functional alias controlling MCPTT server to the MCPTT server. + +**Table 10.18.2.3-1: Notify functional alias request** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------| +| Functional alias | M | The functional alias subscribed to by the MCPTT server | +| MCPTT ID list (NOTE) | M | The list of MCPTT IDs that is activated for the functional alias | +| NOTE: The MCPTT ID list can be an empty list if no MCPTT user activates the functional alias. | | | + +#### 10.18.2.4 Notify functional alias response + +Table 10.18.2.4-1 describes the information flow notify functional alias response from the MCPTT server to the functional alias controlling MCPTT server. + +**Table 10.18.2.4-1: Notify functional alias response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------------------| +| Functional alias | M | The functional alias for which a list of MCPTT users who activate the functional alias is requested. | + +### 10.18.3 Procedure + +#### 10.18.3.1 Subscription for functional alias procedure + +The procedure for subscription for functional alias is described in figure 10.18.3.1-1. + +Pre-conditions: + +- The functional alias controlling MCPTT server holds a list of MCPTT users who has activated the functional alias. + +![Sequence diagram for Subscription for functional alias procedure. It shows two lifelines: MCPTT server and MCPTT Server (Functional alias controlling). The MCPTT server sends a '1. Subscribe functional alias request' to the functional alias controlling MCPTT server, which responds with '2. Subscribe functional alias response'.](34f9874474c0f8f03423fce29f2c2ded_img.jpg) + +``` + +sequenceDiagram + participant MCPTT server + participant MCPTT Server (Functional alias controlling) + Note left of MCPTT server: Pre-conditions: The functional alias controlling MCPTT server holds a list of MCPTT users who has activated the functional alias. + MCPTT server->>MCPTT Server (Functional alias controlling): 1. Subscribe functional alias request + MCPTT Server (Functional alias controlling)-->>MCPTT server: 2. Subscribe functional alias response + +``` + +Sequence diagram for Subscription for functional alias procedure. It shows two lifelines: MCPTT server and MCPTT Server (Functional alias controlling). The MCPTT server sends a '1. Subscribe functional alias request' to the functional alias controlling MCPTT server, which responds with '2. Subscribe functional alias response'. + +**Figure 10.18.3.1-1: Subscription for functional alias** + +1. The MCPTT server sends a subscribe functional alias request to the functional alias controlling MCPTT server in order to receive notifications about the list of MCPTT users who has activated the function alias. +2. The functional alias controlling MCPTT server provides a subscribe functional alias response to the MCPTT server indicating success or failure of the request. + +#### 10.18.3.2 Notification for functional alias procedure + +The procedure for notification for functional alias as shown in figure 10.18.3.2-1 is used by the functional alias controlling MCPTT server to inform the MCPTT server about MCPTT users who activate of the functional alias. + +Pre-conditions: + +- The MCPTT server has subscribed to the functional alias +- The list of MCPTT users who has activated the functional alias is changed at functional alias controlling MCPTT server due to activation, deactivation or taken over. + +![Sequence diagram showing notification for functional alias between two MCPTT servers.](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +``` +sequenceDiagram + participant MCPTT Server (Functional alias controlling) + participant MCPTT server + Note left of MCPTT Server: MCPTT Server (Functional alias controlling) + Note right of MCPTT server: MCPTT server + MCPTT Server (Functional alias controlling)-->>MCPTT server: 1. Notify functional alias request + MCPTT server-->>MCPTT Server (Functional alias controlling): 2. Notify functional alias response +``` + +The diagram is a sequence diagram with two lifelines. The lifeline on the left is labeled "MCPTT server". The lifeline on the right is labeled "MCPTT Server (Functional alias controlling)". A message arrow labeled "1. Notify functional alias request" points from the right lifeline to the left lifeline. A return message arrow labeled "2. Notify functional alias response" points from the left lifeline to the right lifeline. + +Sequence diagram showing notification for functional alias between two MCPTT servers. + +**Figure 10.18.3.2-1: Notification for the functional alias** + +1. The functional alias controlling MCPTT server provides the list of MCPTT users who has activated the functional alias in the notify functional alias request to the call controlling MCPTT server. +2. The call controlling MCPTT server provides a notify functional alias response to the functional alias controlling MCPTT server. + +# Annex A (normative): MCPTT related configuration data + +## A.1 General + +This Annex provides information about the static data needed for configuration for the MCPTT service, which belongs to one of the following categories: + +- MCPTT UE configuration data (see subclause A.2); +- MCPTT user profile configuration data (see subclause A.3); +- MCPTT related group configuration data (see subclause A.4); and +- MCPTT service configuration data (see subclause A.5). + +For each configuration category, data is split between configuration data that is applicable to both on-network and off-network, configuration data that is applicable to on-network only, and configuration data that is applicable to off-network only. The configuration data in each configuration category corresponds to a single instance of the category type i.e. the MCPTT UE, MCPTT group, MCPTT user and MCPTT service configuration data refers to the information that will be stored against each MCPTT UE, MCPTT group, MCPTT user and MCPTT service. This means that the three separate tables (on-network and off-network, on-network only, off-network only) for each configuration category represent the complete set of data for each configuration data category element. + +The columns in the tables have the following meanings: + +- Reference: the reference of the corresponding requirement in 3GPP TS 22.179 [2] or 3GPP TS 22.280 [17] or 3GPP TS 23.280 [16] or the corresponding subclause from the present document. +- Parameter description: A short definition of the semantics of the corresponding item of data, including denotation of the level of the parameter in the configuration hierarchy. +- When it is not clear to which functional entities the parameter is configured, then one or more columns indicating this are provided where the following nomenclature is used: + - "Y" to denote "Yes" i.e. the parameter denoted for the row needs to be configured to the functional entity denoted for the column. + - "N" to denote "No" i.e. the parameter denoted for the row does not need to be configured to the functional entity denoted for the column. + +Parameters within a set of configuration data have a level within a hierarchy that pertains only to that configuration data. The hierarchy of the configuration data is common across all three tables of on-network and off-network, on network only and off network only. The level of a parameter within the hierarchy of the configuration data is denoted by use of the character ">" in the parameter description field within each table, one per level. Parameters that are at the top most level within the hierarchy have no ">" character. Parameters that have one or more ">" characters are child parameters of the first parameter above them that has one less ">" character. Parent parameters are parameters that have one or more child parameters. Parent parameters act solely as a "grouping" of their child parameters and therefore do not contain an actual value themselves i.e. they are just containers for their child parameters. + +Each parameter that can be configured online shall only be configured through one online reference point. Each parameter that can be configured offline shall only be configured through one offline reference point. The most recent configuration data made available to the MCPTT UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism. + +## A.2 MCPTT UE configuration data + +The general aspects of UE configuration are specified in 3GPP TS 23.280 [16]. Data in tables A.2-1 and A.2-2 have to be known by the MCPTT UE after MCPTT authorization. + +Data in table A.2-1 can be configured offline using the CSC-11 reference point. Table A.2-2 contains the UE configuration required to support the use of off-network MCPTT service. + +**Table A.2-1: UE configuration data (on and off network)** + +| Reference | Parameter description | +|--------------------------------------|--------------------------------------------------| +| [R-5.4.2-002] of 3GPP TS 22.280 [17] | Maximum number of simultaneous group calls (Nc4) | +| [R-5.4.2-003] of 3GPP TS 22.280 [17] | Maximum number of transmissions (Nc5) in a group | +| [R-5.5.2-007] of 3GPP TS 22.280 [17] | Maximum number of private calls (N10) | + +**Table A.2-2: UE configuration data (on network)** + +| Reference | Parameter description | +|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------| +| Subclause 5.2.3 of 3GPP TS 23.280 [16] | Relay service (Y/N) | +| Subclause 5.2.3 of 3GPP TS 23.280 [16] | List of allowed relayed MCPTT groups and their relay service code (as specified in 3GPP TS 23.303 [7]) (optional) (see NOTE) | +| | > MCPTT group ID | +| | > Relay service code (as specified in 3GPP TS 23.303 [7]) | +| NOTE: | When the value of the parameter Relay service is N, this parameter and its child parameters are not needed. | + +## A.3 MCPTT user profile configuration data + +The general aspects of MC service user profile configuration data are specified in 3GPP TS 23.280 [16]. The MCPTT user profile configuration data is stored in the MCPTT user database. The MCPTT server obtains the MCPTT user profile configuration data from the MCPTT user database (MCPTT-2). + +Tables A.3-1 and A.3-2 contain the MCPTT user profile configuration required to support the use of on-network MCPTT service. Tables A.3-1 and A.3-3 contain the MCPTT user profile configuration required to support the use of off-network MCPTT service. Data in table A.3-1 and A.3-3 can be configured offline using the CSC-11 reference point. + +**Table A.3-1: MCPTT user profile data (on and off network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Configuration management server | MCPTT user database | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|----------|--------------|---------------------------------|---------------------| +| Subclause 8.1.2 of 3GPP TS 23.280 [16] | MCPTT user identity (MCPTT ID) | Y | Y | Y | Y | +| 3GPP TS 33.180 [19] | KMSUri for security domain of MCPTT ID (see NOTE 4) | Y | Y | Y | Y | +| Subclause 5.2.4 of 3GPP TS 23.280 [16] | Pre-selected MCPTT user profile indication (see NOTE 3) | Y | Y | Y | Y | +| Subclause 5.2.4 of 3GPP TS 23.280 [16] | MCPTT user profile index | Y | Y | Y | Y | +| Subclause 5.2.4 of 3GPP TS 23.280 [16] | MCPTT user profile name | Y | Y | Y | Y | +| [R-5.19-007], [R-6.13.4-002] of 3GPP TS 22.280 [17] | User profile status (enabled/disabled) | | Y | Y | Y | +| [R-5.8-001], [R-6.9-003] of 3GPP TS 22.280 [17] | Authorised to create and delete aliases of an MCPTT User and its associated user profiles. | | | Y | Y | +| [R-5.8-002], [R-6.9-003] of 3GPP TS 22.280 [17] | Alphanumeric aliases of user | Y | Y | Y | Y | +| [R-5.10-001] of 3GPP TS 22.280 [17] | Participant type of the user | Y | Y | Y | Y | +| [R-5.3-002], [R-5.10-001] of 3GPP TS 22.280 [17] | User's Mission Critical Organization (i.e. which organization a user belongs to) | Y | Y | Y | Y | +| [R-5.5.2-008] of 3GPP TS 22.280 [17] | Maximum number of simultaneously received group calls (Nc5) | | Y | Y | Y | +| [R-5.6.5-004] of 3GPP TS 22.179 [2] | Authorised to make a private call | Y | Y | Y | Y | +| [R-5.6.5-001] of 3GPP TS 22.179 [2] | Authorised to make a private call with manual commencement | Y | Y | Y | Y | +| [R-5.6.5-003] of 3GPP TS 22.179 [2]
[R-6.7.3-007] of 3GPP TS 22.280 [17] | List of user(s) who can be called in private call | | | | | +| | > MCPTT ID | Y | Y | Y | Y | +| | > User info ID | Y | N | Y | Y | +| | > ProSe discovery group ID | Y | N | Y | Y | +| 3GPP TS 33.180 [19] | > KMSUri for security domain of MCPTT ID (see NOTE 4) | Y | Y | Y | Y | +| [R-6.7.4-004] of 3GPP TS 22.280 [17] | > Presentation priority relative to other users and groups (see NOTE 2) | Y | Y | Y | Y | +| [R-5.6.5-003] of 3GPP TS 22.179 [2] | Authorised to make a private call to users not included in "list of user(s) who can be called in private call" | Y | Y | Y | Y | +| [R-5.6.5-002] of 3GPP TS 22.179 [2] | Authorised to make a private call with automatic commencement | Y | Y | Y | Y | +| [R-5.6.3-011], [R-6.7.4-010] of 3GPP TS 22.179 [2] | Authorisation of user to force automatic answer for a private call | Y | Y | Y | Y | +| [R-5.6.5-006], [R-6.7.5-002] of 3GPP TS 22.179 [2] | Authorised to restrict the provision of a notification of call failure reason for private call | Y | Y | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | Authorisation to protect confidentiality and integrity of media in a private call (see NOTE 1) | Y | Y | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | Authorisation to protect confidentiality and integrity of floor control signalling in a private call (see NOTE 1) | Y | Y | Y | Y | +| [R-5.6.2.2.1-001] of 3GPP TS 22.280 [17] | Authorisation to make an MCPTT emergency group call functionality enabled for user | Y | Y | Y | Y | + +| | | | | | | +|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------|---|---|---|---| +| [R-5.6.2.4.1-001] of 3GPP TS 22.280 [17] | Group used on initiation of an MCPTT emergency group call (see NOTE 7) | Y | Y | Y | Y | +| [R-5.6.2.4.1-001] of 3GPP TS 22.280 [17] | Recipient for an emergency private MCPTT call (see NOTE 7) | | | | | +| | > MCPTT ID | Y | Y | Y | Y | +| 3GPP TS 33.180 [19] | > KMSUri for security domain of MCPTT ID (see NOTE 4) | Y | Y | Y | Y | +| [R-5.6.2.2.2-005] of 3GPP TS 22.280 [17] | Authorisation to cancel an in progress emergency associated with a group | Y | Y | Y | Y | +| [R-5.6.2.2.3-001] of 3GPP TS 22.280 [17] | Authorised to make an Imminent Peril group call | Y | Y | Y | Y | +| [R-5.6.2.2.3-009] of 3GPP TS 22.280 [17] | Group used on initiation of an MCPTT imminent peril group call (see NOTE 8) | Y | Y | Y | Y | +| [R-5.6.2.2.2-002] of 3GPP TS 22.280 [17] | Authorised for imminent in- peril cancellation | Y | Y | Y | Y | +| [R-5.6.2.3.1-001] of 3GPP TS 22.179 [2] | Authorised to make an emergency private call | Y | Y | Y | Y | +| [R-5.6.2.3.2-001] of 3GPP TS 22.179 [2] | Authorised to cancel emergency priority in a private emergency call by an authorized user | Y | Y | Y | Y | +| [R-5.6.2.4.1-002] of 3GPP TS 22.280 [17] | Authorised to activate emergency alert | Y | Y | Y | Y | +| [R-5.6.2.4.1-013] of 3GPP TS 22.280 [17] | Automatically trigger a MCPTT emergency communication after initiating the MCPTT emergency alert | Y | Y | Y | Y | +| [R-5.6.2.4.2-002] of 3GPP TS 22.280 [17] | Authorisation to cancel an MCPTT emergency alert | Y | Y | Y | Y | +| [R-5.1.7-002] of 3GPP TS 22.280 [17] | Priority of the user for initiating/receiving calls | | Y | Y | Y | +| [R-5.2.2-003] of 3GPP TS 22.280 [17] | Authorisation to create a group-broadcast group | | | Y | Y | +| [R-5.2.2-003] of 3GPP TS 22.280 [17] | Authorisation to create a user-broadcast group | | | Y | Y | +| [R-5.3-003], [R-6.12-001], [R-7.2-005] of 3GPP TS 22.280 [17] | Authorisation to provide location information to other MCPTT users on a call when talking | | Y | Y | Y | +| 3GPP TS 23.283 [20] | Authorised to use LMR E2EE for interworking | Y | Y | Y | Y | +| 3GPP TS 23.283 [20] | > List of supported LMR technology types | | | | | +| 3GPP TS 23.283 [20] | >> LMR technology type (P25, TETRA etc.) | Y | N | Y | Y | +| 3GPP TS 23.283 [20] | >> URI of LMR key management functional entity (see NOTE 6) | Y | N | Y | Y | +| 3GPP TS 23.283 [20] | >> LMR specific identity (RSI for P25 or ITS I for TETRA) (see NOTE 5) | Y | N | Y | Y | +| 3GPP TS 23.283 [20] | >> LMR specific security information (see NOTE 5) | Y | N | Y | Y | + +NOTE 1: Security mechanisms are specified in 3GPP TS 33.180 [11]. + +NOTE 2: The use of this parameter by the MCPTT UE is outside the scope of the present document. + +NOTE 3: As specified in 3GPP TS 23.280 [16], for each MCPTT user's set of MCPTT user profiles, only one MCPTT user profile shall be indicated as being the pre-selected MCPTT user profile. + +NOTE 4: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [16]. + +NOTE 5: This is an LMR specific parameter with no meaning within MC services. + +NOTE 6: The LMR key management functional entity is part of the LMR system and is outside the scope of the present document. + +NOTE 7: This parameter is used for the emergency communication and also used as a target of the emergency alert request. At most one of them is configured; i.e. emergency communication will go to either a group or a user. If both are not configured the MCPTT user's currently selected group will be used. + +NOTE 8: This group, if configured, will be used for imminent peril communication. If not configured the MCPTT user's currently selected group will be used. + + + +**Table A.3-2: MCPTT user profile data (on network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Configuration management server | MCPTT user database | +|----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|----------|--------------|---------------------------------|---------------------| +| [R-5.1.5-001],
[R-5.1.5-002],
[R-5.10-001],
[R-6.4.7-002],
[R-6.8.1-008] of
3GPP TS 22.280 [17] | List of on-network MCPTT groups for use by an MCPTT user | | | | | +| | > MCPTT Group ID | Y | Y | Y | Y | +| | > Application plane server identity information of group management server where group is defined | | | | | +| | >> Server URI | Y | N | Y | Y | +| | > Application plane server identity information of identity management server which provides authorization for group (see NOTE 1) | | | | | +| | >> Server URI | Y | N | Y | Y | +| 3GPP TS 33.180 [19] | > KMSUri for security domain of group (see NOTE 3) | Y | Y | Y | Y | +| | > Presentation priority of the group relative to other groups and users (see NOTE 2) | Y | Y | Y | Y | +| [R-6.2.3.7.2-006] of
3GPP TS 22.179 [2] | > Authorisation of an MCPTT user to change the maximum number of simultaneous talkers | Y | Y | Y | Y | +| Subclause 5.2.5 of
3GPP TS 23.280 [16] | List of groups user implicitly affiliates to after MCPTT service authorization for the user | | | | | +| | > MCPTT Group IDs | Y | Y | Y | Y | +| [R-6.4.2-006] of
3GPP TS 22.280 [17] | Authorisation of an MCPTT user to request a list of which groups an MCPTT user has affiliated to | | Y | Y | Y | +| [R-6.4.6.1-002],
[R-6.4.6.1-003] of
3GPP TS 22.280 [17] | Authorisation to change affiliated groups of other specified user(s) | | Y | Y | Y | +| [R-6.4.6.2-001],
[R-6.4.6.2-002] of
3GPP TS 22.280 [17] | Authorisation to recommend to specified user(s) to affiliate to specific group(s) | | Y | Y | Y | +| [R-6.6.1-004] of
3GPP TS 22.280 [17] | Authorisation to perform regrouping | Y | Y | Y | Y | +| [R-6.7.2-001] of
3GPP TS 22.280 [17] | Presence status is available/not available to other users | Y | Y | Y | Y | +| [R-6.7.1-002],
[R-6.7.2-002] of
3GPP TS 22.280 [17] | List of MCPTT users that an MCPTT user is authorised to obtain presence of | | | | | +| | > MCPTT IDs | Y | Y | Y | Y | +| [R-6.7.2-003] of
3GPP TS 22.280 [17] | User is able/ unable to participate in private calls | Y | Y | Y | Y | +| [R-6.7.1-004],
[R-6.7.2-003],
[R-6.7.2-004] of
3GPP TS 22.280 [17] | Authorisation to query whether MCPTT User is available for private calls | | Y | Y | Y | +| [R-6.7.1-010] of
3GPP TS 22.179 [2] | Authorisation to override transmission in a private call | Y | Y | Y | Y | +| [R-6.7.1-013] of
3GPP TS 22.179 [2] | Authorisation to restrict provision of private call set-up failure cause to the caller | | Y | Y | Y | +| [R-6.7.6-001] of
3GPP TS 22.179 [2] | Authorized to make a private call-back request | Y | Y | Y | Y | +| [R-6.7.6-004] of
3GPP TS 22.179 [2] | Authorized to cancel a private call-back request | Y | Y | Y | Y | + +| | | | | | | +|---------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|---|---|---|---| +| [R-6.8.7.4.2-001], [R-6.8.7.4.2-002] of 3GPP TS 22.280 [17] | Authorisation of an MCPTT user to cancel an emergency alert on any MCPTT UE of any MCPTT user | | Y | Y | Y | +| [R-6.13.4-001] of 3GPP TS 22.280 [17] | Authorisation for a MCPTT user to enable/disable an MCPTT user | | Y | Y | Y | +| [R-6.13.4-003], [R-6.13.4-005], [R-6.13.4-006], [R-6.13.4-007] of 3GPP TS 22.280 [17] | Authorisation for an MCPTT user to (permanently /temporarily) enable/disable a UE | | Y | Y | Y | +| [R-6.2.3.4-001] of 3GPP TS 22.179 [2] | Authorisation to revoke permission to transmit | | Y | Y | Y | +| [R-7.14-002], [R-7.14-003] of 3GPP TS 22.280 [17] | Authorization for manual switch to off-network while in on-network | Y | Y | Y | Y | +| [R-5.1.5-004] of 3GPP TS 22.280 [17] | Limitation of number of affiliations per user (N2) | N | Y | Y | Y | +| [R-5.5.2-009] of 3GPP TS 22.179 [2] | Maximum number of simultaneous transmissions received in one group call for override (N7) | | Y | Y | Y | +| [R-6.4.6.1-001], [R-6.4.6.1-004] of 3GPP TS 22.280 [17] | List of MCPTT users whose selected groups are authorized to be remotely changed | | | | | +| | > MCPTT IDs | Y | Y | Y | Y | +| Subclause 10.15.3 | Authorization to make a first-to-answer call | Y | Y | Y | Y | +| [R-6.15.2.2.2-001] of 3GPP TS 22.280 [17] | Authorization to make a remotely initiated ambient listening private call | Y | Y | Y | Y | +| [R-6.15.2.2.3-001] of 3GPP TS 22.280 [17] | Authorization to make a locally initiated ambient listening private call | Y | Y | Y | Y | +| [R-6.15.3.2-001] of 3GPP TS 22.280 [17] | Authorization to make a remotely initiated private call | Y | Y | Y | Y | +| [R-6.15.3.2-003] of 3GPP TS 22.280 [17] | Authorization to make a remotely initiated group call | Y | Y | Y | Y | +| [R-5.9a-013] of 3GPP TS 22.280 [17] | Authorised to request association between active functional alias(es) and MCPTT ID(s) | | Y | Y | Y | +| [R-5.9a-012] of 3GPP TS 22.280 [17] | Authorised to take over a functional alias from another MCPTT user | | Y | Y | Y | +| | List of functional alias(es) of the MCPTT user | | | | | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | > Functional alias | Y | Y | Y | Y | +| [R-5.4.2-007a] of 3GPP TS 22.280 [17] | >> Maximum number of parallel emergency group calls | Y | | Y | Y | +| [R-5.9a-018] of 3GPP TS 22.280 [17] | >> Criteria for automatic activation by the MCPTT server (see NOTE 6) | N | Y | Y | Y | +| [R-5.9a-017], [R-5.9a-018] of 3GPP TS 22.280 [17] | >> Criteria for automatic de-activation by the MCPTT server (see NOTE 6) | N | Y | Y | Y | +| [R-5.9a-019] of 3GPP TS 22.280 [17] | >> Location criteria for activation | Y | | Y | Y | +| [R-5.9a-019] of 3GPP TS 22.280 [17] | >> Location criteria for de-activation | Y | | Y | Y | +| | >> Manual de-activation is not allowed if the location criteria are met | Y | | Y | Y | +| [R-6.7.3-007a] of 3GPP TS 22.280 [17] | List of user(s) from which private calls can be received | | | | | + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|---|---|---|---| +| | > MCPTT ID | Y | Y | Y | Y | +| 3GPP TS 33.180 [19] | > KMSUri for security domain of MCPTT ID | Y | Y | Y | Y | +| [R-6.7.4-004] of 3GPP TS 22.280 [17] | > Presentation priority relative to other users and groups | Y | Y | Y | Y | +| | Authorised to receive private calls from any other MCPTT ID (see NOTE 7) | Y | Y | Y | Y | +| Subclause 5.2.9 of 3GPP TS 23.280 [16] | List of partner MCPTT systems in which this profile is valid for use during migration | | | | | +| Subclause 5.2.9 of 3GPP TS 23.280 [16] | > Identity of partner MCPTT system | Y | Y | Y | Y | +| Subclause 10.1.1 of 3GPP TS 23.280 [16] | > Access information for partner MCPTT system (see NOTE 4) | Y | | Y | Y | +| Subclause 10.6.2.9 | Authorized to initiate or cancel group regrouping using a preconfigured regroup group | Y | Y | Y | Y | +| [R-6.6.4.2-002a] and [R-6.6.4.2-002b] of 3GPP TS 22.280 [17] | List of groups the client affiliates/de-affiliates when one or multiple criteria are met | | | | | +| | > MCPTT Group ID | Y | Y | Y | Y | +| | >> Criteria for affiliation (see NOTE 5) | Y | Y | Y | Y | +| | >> Criteria for de-affiliation (see NOTE 5) | Y | Y | Y | Y | +| | >> Manual de-affiliation is not allowed if the criteria for affiliation are met | Y | Y | Y | Y | +| [R-6.6.4.2-002] of 3GPP TS 22.280 [17] | List of groups the client affiliates after receiving an emergency alert | | | | | +| | > MCPTT Group ID | Y | Y | Y | Y | +| | >> Manual de-affiliation is not allowed if the criteria for affiliation are met | Y | Y | Y | Y | +| [R-5.6.3-015], [R-6.7.4-016] of 3GPP TS 22.179 [2] | Allow private call forwarding | | Y | Y | Y | +| [R-5.6.3-015], [R-6.7.4-016] of 3GPP TS 22.179 [2] | Call Forwarding NoAnswer Timeout | | Y | Y | Y | +| [R-5.6.3-015], [R-6.7.4-016] of 3GPP TS 22.179 [2] | Call forwarding turned on | | Y | Y | Y | +| R-5.6.3-015], [R-6.7.4-016] of 3GPP TS 22.179 [2] | Target MCPTT ID | | Y | Y | Y | +| R-5.6.3-015], [R-6.7.4-016] of 3GPP TS 22.179 [2] | Condition | | Y | Y | Y | +| NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [16]. | | | | | | +| NOTE 2: The use of this parameter by the MCPTT UE is outside the scope of the present document. | | | | | | +| NOTE 3: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [16]. | | | | | | +| NOTE 4: Access information for each partner MCPTT system comprises the list of information required for initial UE configuration to access an MCPTT system, as defined in table A.6-1 of 3GPP TS 23.280 [16] | | | | | | +| NOTE 5: The criteria may consist of conditions such as the MCPTT user location or the active functional alias of the MCPTT user. | | | | | | +| NOTE 6: The criteria may consist of conditions such MCPTT user location or time. | | | | | | +| NOTE 7: This parameter only applies to MCPTT users which are in the same security domain. | | | | | | + +**Table A.3-3: MCPTT user profile data (off network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Configuration management server | MCPTT user database | +|---------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|----------|--------------|---------------------------------|---------------------| +| [R-7.2-003], [R-7.6-004] of 3GPP TS 22.280 [17] | List of off-network MCPTT groups for use by an MCPTT user | Y | N | Y | Y | +| | > MCPTT Group ID | Y | N | Y | Y | +| | > Application plane server identity information of group management server where group is defined | | | | | +| | >> Server URI | Y | N | Y | Y | +| | > Application plane server identity information of identity management server which provides authorization for group (see NOTE 1) | | | | | +| | >> Server URI | Y | N | Y | Y | +| 3GPP TS 33.180 [19] | > KMSUri for security domain of group (see NOTE 3) | Y | N | Y | Y | +| | > Presentation priority of the group relative to other groups and users (see NOTE 2) | Y | N | Y | Y | +| [R-7.3.3-008] of 3GPP TS 22.179 [2] | Allowed listening of both overriding and overridden | Y | N | Y | Y | +| [R-7.3.3-006] of 3GPP TS 22.179 [2] | Allowed transmission for override (overriding and/or overridden) | Y | N | Y | Y | +| [R-7.8.1-001] of 3GPP TS 22.280 [17] | Authorization for participant to change an off-network group call in-progress to off-network emergency group call | Y | N | Y | Y | +| [R-7.8.3.1-003] of 3GPP TS 22.280 [17] | Authorization for participant to change an off-network group call in-progress to off-network imminent peril group call | Y | N | Y | Y | +| [R-7.12-002], [R-7.12-003] of 3GPP TS 22.280 [17] | Authorization for off-network services | Y | N | Y | Y | +| Subclause 10.7.2 | User info id (as specified in 3GPP TS 23.303 [7]) | Y | N | Y | Y | + +NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [16]. + +NOTE 2: The use of this parameter by the MCPTT UE is outside the scope of the present document. + +NOTE 3: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [16]. + +## A.4 MCPTT related group configuration data + +The general aspects of group configuration are specified in 3GPP TS 23.280 [16]. + +Parameters specified in table A.4-1 are child parameters of the "MCPTT configuration" parameter specified in table A.4-1 in 3GPP TS 23.280 [16]. Parameters specified in table A.4-2 are child parameters of the "MCPTT configuration" parameter specified in table A.4-2 in 3GPP TS 23.280 [16]. Parameters specified in table A.4-3 are child parameters of the "MCPTT configuration" parameter specified in table A.4-3 in 3GPP TS 23.280 [16]. + +**Table A.4-1: Group configuration data (on and off network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Group management server | +|-----------------------------------------------------------------|---------------------------------------------------------------------------------|-----------------|---------------------|--------------------------------| +| [R-6.4.9-006] of 3GPP TS 22.280 [17] | >> Preferred voice codecs for MCPTT group | Y | Y | Y | +| [R-5.7.2.1.1-013], [R-5.7.2.4.1-008] of 3GPP TS 22.280 [17] | >> Indication whether emergency group call is permitted on the MCPTT group | Y | Y | Y | +| [R-5.7.2.2.1-009] of 3GPP TS 22.280 [17] | >> Indication whether imminent peril group call is permitted on the MCPTT group | Y | Y | Y | +| [R-5.7.2.4.1-012] of 3GPP TS 22.280 [17] | >> Indication whether emergency alert is possible on the MCPTT group | Y | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | >> Media confidentiality and integrity protection (see NOTE) | Y | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | >> Floor control confidentiality and integrity protection (see NOTE) | Y | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | >> Group media protection security material (see NOTE) | Y | N | Y | +| NOTE: Security mechanisms are specified in 3GPP TS 33.180 [19]. | | | | | + +**Table A.4-2: Group configuration data (on-network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Group management server | +|---------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|----------|--------------|-------------------------| +| [R-5.7.2.1.2-002] of 3GPP TS 22.280 [17] | >> Timeout value for the cancellation of an in-progress emergency for an on-network group call | N | Y | Y | +| [R-5.7.2.2.2-004] of 3GPP TS 22.280 [17] | >> Timeout value for the cancellation of an in progress imminent-peril group call for an on-network group call | N | Y | Y | +| [R-6.2.4-003], [R-6.4.9-002] of 3GPP TS 22.179 [2] | >> Group call hang timer | N | Y | Y | +| [R-6.4.9-003] of 3GPP TS 22.280 [17] | >> Maximum duration of group calls | N | Y | Y | +| Subclause 10.6.2 | >> Group call model used for group (chat/ pre-arranged) | Y | Y | Y | +| [R-6.2.1-004], [R-6.2.1-007] of 3GPP TS 22.179 [2] | >> Minimum number of affiliated group members acknowledging before start of audio transmission | N | Y | Y | +| [R-6.2.1-007] of 3GPP TS 22.179 [2] | >> List of group members which, if affiliated, have to acknowledge before start of audio transmission | | | | +| | >>>MCPTT IDs | N | Y | Y | +| [R-6.2.1-006], [R-6.2.1-007] of 3GPP TS 22.179 [2] | >> Geographical area where acknowledgement of all affiliated group members is required before start of audio transmission | N | Y | Y | +| [R-6.2.1-008], [R-6.2.1-009] of 3GPP TS 22.179 [2] | >> Timeout for acknowledgement of required group members | N | Y | Y | +| [R-6.2.1-008], [R-6.2.1-009], [R-6.2.1-012] of 3GPP TS 22.179 [2] | >> Action upon failure to receive acknowledgement from required group members before call timeout (proceed or abandon) | N | Y | Y | +| [R-6.2.1-001a] of 3GPP TS 22.179 [2] | >> Minimum number of group members which must be affiliated to allow the start of the group call | N | Y | Y | +| [R-6.2.1-001b] of 3GPP TS 22.179 [2] | >> List of group members which must be affiliated to allow the start of the group call | | | | +| | >>>MCPTT IDs | N | Y | Y | +| [R-6.4.9-004] of 3GPP TS 22.280 [17] | >> List of group members with receive-only capability (see NOTE 1) | | | | +| | >>>MCPTT IDs | N | Y | Y | +| [R-6.4.5-001], [R-6.4.5-003] of 3GPP TS 22.280 [17] | >> Authorisation of a user to request a list of affiliated members of a group | Y | Y | Y | +| [R-5.1.7-002], [R-6.2.2-001], [R-6.6.2.2-006], [R-6.8.6.2-003] of 3GPP TS 22.280 [17] | >> Priority of the group | N | Y | Y | +| [R-6.8.6.2-003] of 3GPP TS 22.280 [17] | >> Pre-emption capability | Y | Y | Y | +| [R-6.8.6.2-003] of 3GPP TS 22.280 [17] | >> Pre-empted capability | Y | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | >> Group floor control protection security material for multicast use (see NOTE 2) | Y | Y | Y | +| [R-6.2.3.6.2-001] of 3GPP TS 22.179 [2] | >> Audio cut-in policy (enabled/disabled) | N | Y | Y | +| [R-6.2.3.7.2-001] of 3GPP TS 22.179 [2] | >> Support of multi-talker control | Y | Y | Y | +| [R-6.2.3.7.2-005] of 3GPP TS 22.179 [2] | >> Maximum number of simultaneous talkers applicable for multi-talker control | N | Y | Y | + +| | | | | | +|---------------------------------------------|--------------------------------------------------------------------------------------------------|---|---|---| +| Subclause 7.4.2.3.5 and subclause 7.4.2.3.6 | >> Audio mixing is performed in the UE or in the network to support multi-talker control | Y | Y | Y | +| [R-6.2.3.7.2-003] of 3GPP TS 22.179 [2] | >> List of group members which are allowed to talk (see NOTE 1) | | | | +| | >>> MCPTT IDs | N | Y | Y | +| Subclause 10.2.7 of 3GPP TS 23.280 [16] | >> List of partner MCPTT systems where system specific configuration applies for interconnection | | | | +| | >>> MC system identity of partner MCPTT system | N | Y | Y | +| [R-6.4.9-004] of 3GPP TS 22.280 [17] | >>> List of group members with receive-only capability (see NOTE 1) | | | | +| | >>>>MCPTT IDs | N | Y | Y | +| [R-6.2.3.7.2-003] of 3GPP TS 22.179 [2], | >>> List of group members which are allowed to talk (see NOTE 1) | | | | +| | >>>> MCPTT IDs | N | Y | Y | +| 3GPP TS 23.283 [20] | >> Indication whether use of LMR E2EE is permitted on the MCPTT group | Y | N | Y | +| 3GPP TS 23.283 [20] | >> LMR specific identity for MCPTT group (see NOTE 3) | Y | N | Y | +| 3GPP TS 23.283 [20] | >> Group to key binding (see NOTE 3) | Y | N | Y | + +NOTE 1: A group member shall not be listed in both the list of group members with receive only capability and the list of group members which are allowed to talk. + +NOTE 2: The details of security related elements are specified in 3GPP TS 33.180 [19]. + +NOTE 3: This is an LMR specific parameter with no meaning within MC services. + +**Table A.4-3: Group configuration data (off-network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Group management server | +|------------------------------------------|-----------------------------------------------------------------------------------------------------------------|----------|--------------|-------------------------| +| [R-5.7.2.1.2-002] of 3GPP TS 22.280 [17] | >> Timeout value for the cancellation of an in-progress emergency for an off-network group call | Y | N | Y | +| [R-5.7.2.2.2-004] of 3GPP TS 22.280 [17] | >> Timeout value for the cancellation of an in progress imminent-peril group call for an off-network group call | Y | N | Y | +| [R-7.4-002] of 3GPP TS 22.179 [2] | >> Group call hang timer | Y | N | Y | +| [R-7.4-003] of 3GPP TS 22.280 [17] | >> Max duration of group calls | Y | N | Y | +| Subclause 10.6.3.9.1 | >> Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values | | | | +| | >>> MCPTT group call signalling | Y | N | Y | +| | >>> MCPTT group call media | Y | N | Y | +| | >>> MCPTT emergency group call signalling | Y | N | Y | +| | >>> MCPTT emergency group call media | Y | N | Y | +| | >>> MCPTT imminent peril group call signalling | Y | N | Y | +| | >>> MCPTT imminent peril group call media | Y | N | Y | + +## A.5 MCPTT service configuration data + +The general aspects of MC service configuration are specified in 3GPP TS 23.280 [16]. The MCPTT service configuration data is stored in the MCPTT server. + +Tables A.5-1 and A.5-2 describe the configuration data required to support the use of on-network MCPTT service. Tables A.5-1 and A.5-3 describe the configuration data required to support the use of off-network MCPTT service. Data in tables A.5-1 and A.5-3 can be configured offline using the CSC-11 reference point. + +**Table A.5-1: MCPTT service configuration data (on and off network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Configuration management server | +|--------------------------------------|-----------------------------------------------------------------------------------------------------|----------|--------------|---------------------------------| +| [R-5.2.2-001] of 3GPP TS 22.280 [17] | Levels of group hierarchy for group-broadcast groups (Bc1) | Y | Y | Y | +| [R-5.2.3-001] of 3GPP TS 22.280 [17] | Levels of user hierarchy for user-broadcast groups (Bc2) | Y | Y | Y | +| [R-5.8-002] of 3GPP TS 22.280 [17] | Minimum length (Nc3) of an alphanumeric identifier (i.e. alias) assigned by an MCPTT administrator. | Y | N | Y | + +**Table A.5-2: MCPTT service configuration data (on-network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Configuration management server | +|--------------------------------------------------------|-----------------------------------------------------------------------------------------------|----------|--------------|---------------------------------| +| [R-5.7.2.3.2-002] of 3GPP TS 22.179 [2] | Timeout value for the cancellation of an in-progress emergency for an on-network private call | N | Y | Y | +| [R-5.7.2.1.2-002] of 3GPP TS 22.280 [17] | Time limit for an in-progress emergency related to an on-network MCPTT group | N | Y | Y | +| [R-5.6.5-004] of 3GPP TS 22.179 [2] | Max on-network private call (with floor control) duration | N | Y | Y | +| [R-6.2.4-003] of 3GPP TS 22.179 [2] | Hang timer for private calls | N | Y | Y | +| [R-6.7.2-008] of 3GPP TS 22.280 [17] | Max duration of private call (without floor control) | N | Y | Y | +| [R-6.2.3.3.1-001] of 3GPP TS 22.179 [2] | Hierarchy of participant rights to override | N | Y | Y | +| [R-6.2.3.5-002] of 3GPP TS 22.179 [2] | Transmit time limit from a single request to transmit in a group or private call transmission | N | Y | Y | +| [R-6.2.3.5-003], [R-6.2.3.5-004] of 3GPP TS 22.179 [2] | Configuration of warning time before time limit of transmission is reached (on-network) | N | Y | Y | +| [R-6.2.4-005] of 3GPP TS 22.179 [2] | Configuration of warning time before call hang time (on-network) | N | Y | Y | +| [R-6.2.3.2-006] of 3GPP TS 22.179 [2] | Depth of floor control queue | N | Y | Y | +| [R-6.2.3.2-012] of 3GPP TS 22.179 [2] | Max time for a user's floor control request to be queued | N | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | Protect confidentiality of signalling (see NOTE 1) | Y | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | Protect integrity of signalling (see NOTE 1) | Y | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | Use signalling protection between MCPTT servers (see NOTE 1) | N | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | Use floor control protection between MCPTT servers (see NOTE 1) | N | Y | Y | +| | List of functional alias identities | | | | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | > Functional alias | N | Y | Y | +| [R-5.9a-016] of 3GPP TS 22.280 [17] | > Communication priority (see NOTE 2) | N | Y | Y | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | > Limit number of simultaneous activations | N | Y | Y | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | > This functional alias can be taken over | N | Y | Y | +| | > List of users | | | | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | >> MCPTT ID | N | Y | Y | +| [R-5.6.3-015], [R-6.7.4-016] of 3GPP TS 22.179 [2] | Max number immediate forwardings | N | Y | Y | +| [R-5.10-001a] of 3GPP TS 22.280 [17] | Maximum number of successful simultaneous service authorizations of clients from a user | N | Y | Y | + +NOTE 1: Security mechanisms are specified in 3GPP TS 33.180 [19]. + +NOTE 2: The usage of this parameter by the MCPTT server is up to implementation. + +**Table A.5-3: MCPTT service configuration data (off-network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Configuration management server | +|--------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|----------|--------------|---------------------------------| +| [R-5.7.2.3.2-002] of 3GPP TS 22.179 [2] | Timeout value for the cancellation of an in-progress emergency for an off-network private call | Y | N | Y | +| [R-5.7.2.1.2-002] of 3GPP TS 22.280 [17] | Time limit for an in-progress emergency related to an off-network MCPTT group | Y | N | Y | +| [R-5.6.5-004] of 3GPP TS 22.179 [2] | Max off-network private call (with floor control) duration | Y | N | Y | +| [R-7.4-002] of 3GPP TS 22.179 [2]
[R-7.4-003] of 3GPP TS 22.280 [17] | Hang timer for private calls in off-network | Y | N | Y | +| [R-7.3.3-001], [R-7.3.3-002], [R-7.3.3-003] of 3GPP TS 22.179 [2] | Priority hierarchy for floor control override in off-network | Y | N | Y | +| [R-7.3.5-001], [R-7.3.5-002], [R-7.3.5-003] of 3GPP TS 22.179 [2] | Transmit time limit from a single request to transmit in a group or private call. | Y | N | Y | +| [R-7.3.5-001], [R-7.3.5-004] of 3GPP TS 22.179 [2] | Configuration of warning time before time limit of transmission is reached (off-network) | Y | N | Y | +| [R-7.4-004] of 3GPP TS 22.280 [17] | Configuration of warning time before hang time is reached (off-network) | Y | N | Y | +| [R-7.7-001], [R-7.7-003] of 3GPP TS 22.280 [17]
[R-7.7-002] of 3GPP TS 22.179 [2] | Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values | | | | +| | > MCPTT private call signalling | Y | N | Y | +| | > MCPTT private call media | Y | N | Y | +| | > MCPTT Emergency private call signalling | Y | N | Y | +| | > MCPTT Emergency private call media | Y | N | Y | +| [R-7.15-001], [R-7.7-003] of 3GPP TS 22.280 [17] | Configuration of metadata to log | Y | N | Y | + +# Annex B (informative): Local UE settings for MCPTT + +## B.1 Local UE settings for MCPTT + +Table B.1-1 details local UE settings for MCPTT that represent important functionalities that may be required by MCPTT UEs, however these functionalities do not require central configuration like the parameters in annex A, so these are detailed in this annex for information to UE vendors interested in producing MCPTT UEs. The various columns in the tables have the following meanings: + +- Reference: Is the reference of the corresponding requirement in 3GPP TS 22.179 [2]. +- Definition: A short definition of the local UE setting. + +**Table B.1-1: Local UE settings for MCPTT** + +| Reference | Definition | +|------------------------------------------|---------------------------------------------------------------------------| +| [R-5.1.1-003] of 3GPP TS 22.280 [17] | Call reception signalling method | +| [R-5.1.1-004] of 3GPP TS 22.280 [17] | Disabling of call reception signalling | +| [R-5.8-003] of 3GPP TS 22.280 [17] | Configuration of display of MCPTT ID (on/off) | +| [R-5.8-003] of 3GPP TS 22.280 [17] | Configuration of display of aliases associated with the MCPTT ID (on/off) | +| [R-5.8-003] of 3GPP TS 22.280 [17] | Configuration of display of Selected MCPTT Group (on/off) | +| [R-5.8-003] of 3GPP TS 22.280 [17] | Configuration of display of Mission Critical Organization name (on/off) | +| [R-6.8.7.4.1-003] of 3GPP TS 22.280 [17] | Configuration of the notification of an emergency alert | + +# --- Annex C (informative): Change history + +| Date | Meeting | TDoc | CR | R ev | Cat | Subject/Comment | New | +|---------|---------|-----------|------|------|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2016-04 | | | | | | Initial version. | 0.0.0 | +| 2016-04 | | | | | | Alignment with the following Rel-13 CRs agreed at SA6#10:
CR0053(S6-160271), CR0055(S6-160307),
CR0057(S6-160312), CR0058(S6-160289),
CR0059(S6-160346), CR0060(S6-160335),
CR0061(S6-160268), CR0062(S6-160333),
CR0067(S6-160274), CR0069(S6-160313),
CR0071(S6-160199), CR0072(S6-160334),
CR0075(S6-160331), CR0076(S6-160269),
CR0078(S6-160284), CR0079(S6-160360),
CR0080(S6-160297), CR0081(S6-160332),
CR0085(S6-160361), CR0088(S6-160291),
CR0089(S6-160347), CR0090(S6-160310),
CR0093(S6-160293), CR0094(S6-160294),
CR0099(S6-160342) | 0.1.0 | +| 2016-06 | | | | | | Implemented the following pCRs approved during SA6#11:
S6-160414, S6-160475, S6-160497, S6-160499,
S6-160501, S6-160508, S6-160514, S6-160518,
S6-160530, S6-160532, S6-160568, S6-160571,
S6-160581, S6-160584, S6-160588, and merged
relevant content from S6-160489.
Editorial changes: renumbering subclauses as
needed; added top level subclauses where needed
with editor's notes; added a few missing subclauses
at level 2 with editor's notes; use actual TS numbers
made available at SA plenary: 23.379 and 23.280. | 0.2.0 | +| 2016-09 | | | | | | Implemented the following pCRs approved during SA6#12:
S6-160681, S6-160698, S6-160707, S6-160790,
S6-160802, S6-160828, S6-160873, S6-160908,
S6-160909, S6-160921, S6-160925.
Editorial changes: renumbering subclauses as
needed; added a few missing headings at level 2
and level 3 with editor's notes for consistency. | 0.3.0 | +| 2016-10 | | | | | | Implemented the following pCRs approved during SA6#13:
S6-160961, S6-161016, S6-161112, S6-161113,
S6-161116, S6-161124, S6-161210, S6-161211,
S6-161212, S6-161219, S6-161231, S6-161249,
S6-161251, S6-161258, S6-161268
Editorial changes: renumbering subclauses as
needed. | 0.4.0 | +| 2016-11 | | | | | | Implemented the following pCRs approved during SA6#14:
S6-161330, S6-161522, S6-161538, S6-161564,
S6-161572, S6-161584, S6-161591, S6-161595,
S6-161596, S6-161597, S6-161598, S6-161607.
Editorial changes: renumbering subclauses as
needed. | 0.5.0 | +| 2016-12 | SA#74 | SP-160876 | | | | Submitted for Approval at SA#74 | 1.0.0 | +| 2016-12 | SA#74 | SP-160876 | | | | MCC Editorial update for publication after TSG SA approval (SA#74) | 14.0.0 | +| 2017-03 | SA#75 | SP-170068 | 0003 | 1 | F | Alignment of definitions | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0004 | 2 | F | Alignment of group affiliation and de-affiliation requirements | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0005 | 1 | F | Alignment of bearer management | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0006 | 1 | F | Resolve editor's note in clause 10.6.2.8.1 | 14.1.0 | +| 2017-03 | SA#75 | SP-170069 | 0008 | 1 | F | Store and update affiliation status in the GMS | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0009 | 2 | F | Duplicated reference remove | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0011 | 1 | F | Corrections to MCPTT UE configuration data | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0013 | 1 | D | Correction of references | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0016 | 1 | D | Message title alignment | 14.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------|--------| +| 2017-03 | SA#75 | SP-170068 | 0017 | 3 | F | Resolve group ID issue for temporary group call – user regroup | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0018 | 1 | F | Addition of definition for MCPTT ID | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0019 | | F | Correction of requirement reference for list of implicitly affiliated groups in MCPTT user profile config | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0020 | 2 | F | Simultaneous floor requests | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0021 | 2 | F | Correction on floor control | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0022 | 2 | F | Miscellaneous corrections on term | 14.1.0 | +| 2017-06 | SA#76 | SP-170389 | 0042 | 1 | F | Miscellaneous corrections to configuration | 14.2.0 | +| 2017-06 | SA#76 | SP-170389 | 0043 | 6 | F | Addition of identity management server address per group | 14.2.0 | +| 2017-06 | SA#76 | SP-170389 | 0049 | 1 | F | Correction in Ambient Listening | 14.2.0 | +| 2017-06 | SA#76 | SP-170389 | 0050 | 1 | F | Clarifications on response in off-network | 14.2.0 | +| 2017-06 | SA#76 | SP-170389 | 0062 | 2 | F | Inclusion of KMSUri to allow multiple security domains | 14.2.0 | +| 2017-06 | SA#76 | SP-170389 | 0068 | 1 | F | Corrections to configuration for ambient listening | 14.2.0 | +| 2017-06 | SA#76 | SP-170389 | 0069 | 1 | F | Correction to configuration for first-to-answer call | 14.2.0 | +| 2017-06 | SA#76 | SP-170389 | 0070 | | F | Corrections to Group configuration data for all MC services | 14.2.0 | +| 2017-06 | SA#76 | SP-170340 | 0044 | 1 | B | MCPTT unicast media flow stop and resume | 15.0.0 | +| 2017-06 | SA#76 | SP-170398 | 0063 | 1 | D | Editorial corrections in call back cancel request | 15.0.0 | +| 2017-06 | SA#76 | SP-170340 | 0066 | 1 | C | Resource Management enhancements for MCPTT | 15.0.0 | +| 2017-06 | SA#76 | SP-170340 | 0067 | 2 | C | Addition of Floor acknowledgement | 15.0.0 | +| 2017-09 | SA#77 | SP-170685 | 0074 | 2 | B | Updating IWF-1 description | 15.1.0 | +| 2017-09 | SA#77 | SP-170678 | 0075 | 2 | A | CR on MapGroupToBearer message | 15.1.0 | +| 2017-09 | SA#77 | SP-170678 | 0077 | 1 | A | Corrections for configuration references | 15.1.0 | +| 2018-01 | SA#78 | SP-170895 | 0079 | 3 | B | Functional model for MCPTT interconnection | 15.2.0 | +| 2018-01 | SA#78 | SP-170896 | 0086 | 2 | B | Introduction of the multi-talker control | 15.2.0 | +| 2018-01 | SA#78 | SP-170896 | 0087 | 3 | B | Introduction of Functional alias(es) | 15.2.0 | +| 2018-01 | SA#78 | SP-170896 | 0089 | 1 | C | Multi-talker floor release message and procedure | 15.2.0 | +| 2018-01 | SA#78 | SP-170886 | 0101 | 2 | A | Rejection of group call | 15.2.0 | +| 2018-01 | SA#78 | SP-170886 | 0103 | 2 | A | MCPTT server PSI configuration | 15.2.0 | +| 2018-01 | SA#78 | SP-170886 | 0110 | 1 | A | authorization for remotely initiated MCPTT call | 15.2.0 | +| 2018-01 | SA#78 | SP-170890 | 0090 | 2 | F | Renaming of MCPTT emergency group call cancel | 15.2.0 | +| 2018-01 | SA#78 | SP-170890 | 0091 | 1 | F | Renaming of MCPTT "emergency condition" | 15.2.0 | +| 2018-01 | SA#78 | SP-170890 | 0093 | 2 | F | Renaming of MCPTT imminent peril group call cancel | 15.2.0 | +| 2018-01 | SA#78 | SP-170890 | 0094 | 2 | F | Renaming Off-network MCPTT emergency group cancel | 15.2.0 | +| 2018-01 | SA#78 | SP-170890 | 0095 | 2 | F | Adding implicit floor request IE to MCPTT emergency group call request | 15.2.0 | +| 2018-01 | SA#78 | SP-170890 | 0096 | 3 | B | Server-initiated Broadcast group call release procedure | 15.2.0 | +| 2018-01 | SA#78 | SP-170890 | 0107 | 2 | F | Renaming of "MCPTT emergency state cancel" and corrections to information flow | 15.2.0 | +| 2018-04 | SA#79 | SP-180146 | 0112 | 1 | A | Correction of security specification references | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0113 | 1 | A | User profile for MCPTT migration | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0114 | 4 | B | MCPTT specific group configuration for interconnection | 15.3.0 | +| 2018-04 | SA#79 | SP-180155 | 0115 | 3 | B | LMR E2EE user profile and group parameters | 15.3.0 | +| 2018-04 | SA#79 | SP-180158 | 0116 | 2 | F | Introduction of MCPTT call end response message | 15.3.0 | +| 2018-04 | SA#79 | SP-180150 | 0117 | 1 | F | Update of references to stage 1 specifications | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0119 | | B | Definition of MCPTT-3 | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0120 | | D | Editorial correction to gateway server entity | 15.3.0 | +| 2018-06 | SA#80 | SP-180365 | 0123 | 3 | A | Addition of implicit floor request IEs | 15.4.0 | +| 2018-06 | SA#80 | SP-180365 | 0125 | 1 | A | Corrections to implicit floor request handling | 15.4.0 | +| 2018-06 | SA#80 | SP-180373 | 0129 | 1 | F | Correction of referenced subclauses | 15.4.0 | +| 2018-06 | SA#80 | SP-180365 | 0133 | | A | Clarification for presentation priority in MCPTT UE configuration | 15.4.0 | +| 2018-06 | SA#80 | SP-180369 | 0134 | 2 | F | Update of MCPTT emergency alert for multicast | 15.4.0 | +| 2018-06 | SA#80 | SP-180369 | 0135 | 1 | F | Correction of Group call rejoin response | 15.4.0 | +| 2018-09 | SA#81 | SP-180672 | 0137 | 1 | F | Emergency Alert Area Trigger | 15.5.0 | +| 2018-09 | SA#81 | SP-180672 | 0138 | 1 | C | Location of Current Talker via Floor Request | 15.5.0 | +| 2018-09 | SA#81 | SP-180671 | 0140 | 2 | A | Removal of temporary regroup procedures | 15.5.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|------------------------------------------------------------------------------------|--------| +| 2018-09 | SA#81 | SP-180672 | 0141 | | F | 23.379 Table A.3-1 duplicate note 4 | 15.5.0 | +| 2018-09 | SA#81 | SP-180672 | 0142 | 1 | F | Correction to Chat group call pre-condition | 15.5.0 | +| 2018-09 | SA#81 | SP-180672 | 0145 | 1 | F | Removal of group call notify from normal group call setup | 15.5.0 | +| 2018-09 | SA#81 | SP-180672 | 0147 | | F | Correction to chat group join mechanism | 15.5.0 | +| 2018-09 | SA#81 | SP-180678 | 0143 | 1 | B | Interconnection chat group call | 16.0.0 | +| 2018-09 | SA#81 | SP-180676 | 0146 | 1 | F | Issues with temporary regroup procedures | 16.0.0 | +| 2019-01 | SA#82 | SP-181177 | 0148 | | F | Correction of intended mandatory call participants | 16.1.0 | +| 2019-01 | SA#82 | SP-181177 | 0149 | 3 | C | Completing availability of talker location with floor control request | 16.1.0 | +| 2019-01 | SA#82 | SP-181177 | 0150 | 4 | C | MCPTT add location to emergency and imminent peril | 16.1.0 | +| 2019-01 | SA#82 | SP-181177 | 0151 | 3 | B | User regroup procedure | 16.1.0 | +| 2019-01 | SA#82 | SP-181177 | 0152 | 1 | F | Late entry pre-arranged group call corrections for emergency | 16.1.0 | +| 2019-01 | SA#82 | SP-181177 | 0161 | 4 | F | Late entry for chat group call | 16.1.0 | +| 2019-01 | SA#82 | SP-181177 | 0162 | 5 | B | Application paging | 16.1.0 | +| 2019-01 | SA#82 | SP-181177 | 0163 | | D | Spelling of ProSe | 16.1.0 | +| 2019-01 | SA#82 | SP-181177 | 0164 | 4 | B | Regroup using preconfigured group | 16.1.0 | +| 2019-01 | SA#82 | SP-181177 | 0166 | 2 | F | Corrections to 'general' subclause for pre-arranged and chat group call | 16.1.0 | +| 2019-01 | SA#82 | SP-181177 | 0168 | 1 | F | Pre-established session corrections | 16.1.0 | +| 2019-03 | SA#83 | SP-190073 | 0170 | 2 | B | Broadcast group regroup | 16.2.0 | +| 2019-03 | SA#83 | SP-190073 | 0171 | 2 | F | Corrections to MCPTT chat group call late entry procedures | 16.2.0 | +| 2019-03 | SA#83 | SP-190073 | 0172 | 2 | C | Procedure for MCPTT user leaving a group call | 16.2.0 | +| 2019-03 | SA#83 | SP-190075 | 0174 | 1 | F | MCPTT ID in interconnection floor control | 16.2.0 | +| 2019-03 | SA#83 | SP-190073 | 0175 | 2 | C | Broadcast user regroup | 16.2.0 | +| 2019-03 | SA#83 | SP-190073 | 0176 | 2 | B | Group regroup broadcast and rejection using preconfigured group | 16.2.0 | +| 2019-03 | SA#83 | SP-190073 | 0177 | 1 | F | Broadcast user regroup | 16.2.0 | +| 2019-06 | SA#84 | SP-190484 | 0180 | 3 | B | Adding newly affiliated user to preconfigured group regroup | 16.3.0 | +| 2019-06 | SA#84 | SP-190484 | 0182 | 3 | B | Broadcast group regroup call using preconfigured group | 16.3.0 | +| 2019-06 | SA#84 | SP-190484 | 0183 | 3 | B | Preconfigured regroup exception cases | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0186 | 1 | B | Restricting incoming private communications | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0187 | 1 | B | Support of functional aliases in private calls and private emergency calls | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0188 | 3 | B | Support of functional aliases in emergency and imminent peril groups calls | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0189 | 3 | B | Support of functional aliases via broadcast group calls | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0190 | 2 | B | Support of multiple functional alias use in private calls | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0191 | 4 | B | Provide list of MCPTT group members who did not acknowledge the group call request | 16.3.0 | +| 2019-06 | SA#84 | SP-190484 | 0192 | 3 | C | Preconfigured regroup cancellation on log off | 16.3.0 | +| 2019-06 | SA#84 | SP-190482 | 0194 | | A | Clarifications on functional alias controlling role | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0195 | 2 | B | User configuration for functional alias information query for MCPTT | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0196 | 1 | B | User requested priority in 23.379 | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0200 | 2 | B | Functional alias call | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0202 | 4 | B | Criteria based automatic group affiliation and deaffiliation | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0203 | 1 | B | MCPTT configuration for implicit functional alias activation/deactivation | 16.3.0 | +| 2019-06 | SA#84 | SP-190484 | 0206 | 2 | F | MCPTT ID list in Group call notify | 16.3.0 | +| 2019-06 | SA#84 | SP-190484 | 0207 | 2 | F | Preconfigured regroup usage | 16.3.0 | +| 2019-06 | SA#84 | SP-190484 | 0208 | 2 | F | Remove the duplicated MCPTT server URI in UE configuration table | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0210 | 2 | B | Add configuration for call forwarding for MCPTT private calls | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0211 | 3 | B | Add call forwarding for MCPTT private calls | 16.3.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------|--------| +| 2019-06 | SA#84 | SP-190488 | 0213 | 1 | B | MCPTT server limits the number of simultaneous successful service authorisations | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0214 | 1 | B | Additional commencement modes for group calls | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0215 | | B | Triggering an emergency group communication after an emergency alert automatically | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0216 | | B | MCPTT client performs automatic activation and deactivation of functional aliases based on location | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0217 | 2 | B | Communication priority for functional aliases | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0218 | | F | Information flows for the first-to-answer call procedure | 16.3.0 | +| 2019-06 | SA#84 | SP-190484 | 0220 | 2 | B | User regroup using group creation and using preconfigured group | 16.3.0 | +| 2019-06 | SA#84 | SP-190484 | 0222 | 4 | C | Preconfigured regrouping enhancements | 16.3.0 | +| 2019-09 | SA#85 | SP-190731 | 0223 | 1 | F | Correct the error message is sent in the MCPTT emergency group call procedures | 16.4.0 | +| 2019-09 | SA#85 | SP-190731 | 0224 | 3 | F | Correct the configuration parameters for the MCPTT emergency procedures | 16.4.0 | +| 2019-09 | SA#85 | SP-190731 | 0227 | 3 | F | Corrections to MCPTT emergency alert procedures | 16.4.0 | +| 2019-09 | SA#85 | SP-190732 | 0228 | 1 | F | Add condition "not reachable" to call forwarding for MCPTT private calls | 16.4.0 | +| 2019-09 | SA#85 | SP-190732 | 0235 | 1 | F | Making functional alias optional in floor control messages | 16.4.0 | +| 2019-12 | SA#86 | SP-191109 | 0236 | 1 | F | Corrections to preconfigured regroup procedures | 16.5.0 | +| 2019-12 | SA#86 | SP-191110 | 0242 | 1 | F | Receiving a private call from any other user | 16.5.0 | +| 2019-12 | SA#86 | SP-191109 | 0244 | 1 | F | Removal of temporary regroup procedures | 16.5.0 | +| 2020-07 | SA#88 | SP-200339 | 0251 | 3 | F | Clarification on target recipients in first-to-answer calls | 16.6.0 | +| 2020-07 | SA#88 | SP-200339 | 0253 | 3 | F | Media security for MCPTT private call forwarding | 16.6.0 | +| 2020-07 | | | | | | Correction of the implementation of CR0253r3 | 16.6.1 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23632/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg b/marked/Rel-16/23_series/23632/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0755a8cf5e20ec3d8b40cc13bad2237403b9a419 --- /dev/null +++ b/marked/Rel-16/23_series/23632/04f51626e2e10a16e3eb2c4b33cb2742_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c004ed6c6828513c2951acd82d366a0ae9c7e7e60fa1e68e3feb354127b3db6 +size 81180 diff --git a/marked/Rel-16/23_series/23632/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/23_series/23632/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..042d7fed0495ddb9a099e3cde9458174c7fbc642 --- /dev/null +++ b/marked/Rel-16/23_series/23632/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:740105b40456e6b72caaeeaeb7c4c7d10debf9f9a0a823400d4c9dcf8d4fc3b9 +size 93228 diff --git a/marked/Rel-16/23_series/23632/06da11ab76cacc38bbcd714e437797ea_img.jpg b/marked/Rel-16/23_series/23632/06da11ab76cacc38bbcd714e437797ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9fe19717dacec249402ea17dd140b7491e659f0e --- /dev/null +++ b/marked/Rel-16/23_series/23632/06da11ab76cacc38bbcd714e437797ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0045f98460abfcdd68049debca951ea50091921d06373c95023cdcfc86241f9 +size 29161 diff --git a/marked/Rel-16/23_series/23632/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/Rel-16/23_series/23632/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22ced499e7df007457732704c32f99f3dca9354e --- /dev/null +++ b/marked/Rel-16/23_series/23632/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4050321885a136b7f26e6873152eb268ce10178135314f3779ab84b7cc2335e +size 66348 diff --git a/marked/Rel-16/23_series/23632/171115f072e42b379238ed0dd438e9d7_img.jpg b/marked/Rel-16/23_series/23632/171115f072e42b379238ed0dd438e9d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b53123a844065f4e4b3ad281a5631b739cb9f3be --- /dev/null +++ b/marked/Rel-16/23_series/23632/171115f072e42b379238ed0dd438e9d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0a74ae07dd9427b8ad56a80cf014df1bf13a27f7678829ba947e629e7b90f0e +size 86086 diff --git a/marked/Rel-16/23_series/23632/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg b/marked/Rel-16/23_series/23632/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bd8319a26d679dff009628ff8b80d77bffd95b8 --- /dev/null +++ b/marked/Rel-16/23_series/23632/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c13452f39c8ee300fbdc4d16da606057cc2683f911f0a4e1cdc84d81353d7fec +size 76189 diff --git a/marked/Rel-16/23_series/23632/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/23_series/23632/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b98e6fe44754d668f479ab59eb9c0fe009eb70a7 --- /dev/null +++ b/marked/Rel-16/23_series/23632/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8917a0b45a31e1fecff8f20072f9cbd1ccf7b21dca521676565f0b48dec75c9f +size 93399 diff --git a/marked/Rel-16/23_series/23632/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/23_series/23632/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9306b2fb4bb3d3066239da2503fea057cc7121f1 --- /dev/null +++ b/marked/Rel-16/23_series/23632/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec9f9f15e145cd34f7b322b88579d44a6ad162c80b3ec54bc792cd082ea375b0 +size 88070 diff --git a/marked/Rel-16/23_series/23632/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23632/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff3606628a8dd0dbc83e99bc704a69277aabdaac --- /dev/null +++ b/marked/Rel-16/23_series/23632/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8d4df70ffb4b06b72b5f96b90befa51bfb0f63aaae615a9841edd360d93d0b6 +size 43840 diff --git a/marked/Rel-16/23_series/23632/43979979715bb3304389a0cb18f34444_img.jpg b/marked/Rel-16/23_series/23632/43979979715bb3304389a0cb18f34444_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..563dff2f79717487688ad7e181736497e6c62d6a --- /dev/null +++ b/marked/Rel-16/23_series/23632/43979979715bb3304389a0cb18f34444_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:518b1b356a78f9017ea797e73f534db5a37860b7374b69e30c26e5d36d1f36c7 +size 68240 diff --git a/marked/Rel-16/23_series/23632/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Rel-16/23_series/23632/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..785afaf5785205262f83f96816dabc55c87d8503 --- /dev/null +++ b/marked/Rel-16/23_series/23632/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7ae5f37221b20a25add77f0c7dc15c96fddfb2740bba196df14f23f08ae249d1 +size 96040 diff --git a/marked/Rel-16/23_series/23632/4f148853ae68fdcf5e43f7604cab457d_img.jpg b/marked/Rel-16/23_series/23632/4f148853ae68fdcf5e43f7604cab457d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27f3fb5186ed62e3e89a622c038d478137db24e7 --- /dev/null +++ b/marked/Rel-16/23_series/23632/4f148853ae68fdcf5e43f7604cab457d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c8de6edcd8f03568f75f99acb673a45ccf0a7f3fda1a7c84c82e5b04edf0c65 +size 27543 diff --git a/marked/Rel-16/23_series/23632/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg b/marked/Rel-16/23_series/23632/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bbd3803b7cc0bdaa099254dafbe72b4a9e71db3 --- /dev/null +++ b/marked/Rel-16/23_series/23632/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:745e6a9bb0e2ca8c8779bcab6ba2e36c1e1ae327d5d11e12c5be3059615a9ef1 +size 36835 diff --git a/marked/Rel-16/23_series/23632/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23632/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29b9760b3cebbb36666dd3ebe3c40978969ae26c --- /dev/null +++ b/marked/Rel-16/23_series/23632/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5db4bd1475561a80839e6c6a3feaff2236397f3a466637b84a38c18b0aa30fb9 +size 63886 diff --git a/marked/Rel-16/23_series/23632/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg b/marked/Rel-16/23_series/23632/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f935c0731da9c7e52443150cedc1d98b01003730 --- /dev/null +++ b/marked/Rel-16/23_series/23632/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99de0ca1df352072faa82ff8231c3e759437750a67bedbf58b44fe14b35e5b7b +size 38279 diff --git a/marked/Rel-16/23_series/23632/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/23_series/23632/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79274df3163528e9c1fd9fd9580f07d0201f0034 --- /dev/null +++ b/marked/Rel-16/23_series/23632/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0003e77e69332dfee1f8b2d4a9f0f400f9f63b6e44cc0a24e46405b6bf28a8b8 +size 9832 diff --git a/marked/Rel-16/23_series/23632/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/23_series/23632/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..979ab5ed2f141a80a6573663c4391398b6f02798 --- /dev/null +++ b/marked/Rel-16/23_series/23632/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1f097b70375dc7ee19ecdb77df186c7991bc929cad5d5f4263ab827dc7ece02 +size 5806 diff --git a/marked/Rel-16/23_series/23632/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/23_series/23632/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c70ad239b62f2ad39c2b6c8239fa5cea81bef83b --- /dev/null +++ b/marked/Rel-16/23_series/23632/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:432af276cdf4497aa2e58aa67bc22704475270c5c12884179e12e396e21329cf +size 77844 diff --git a/marked/Rel-16/23_series/23632/66c2bf11a8f117cddf67eff92d4c736c_img.jpg b/marked/Rel-16/23_series/23632/66c2bf11a8f117cddf67eff92d4c736c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1441c0d0e50d01c3e4e23846bee9063ac7f08b96 --- /dev/null +++ b/marked/Rel-16/23_series/23632/66c2bf11a8f117cddf67eff92d4c736c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a02167a79c1b31cbd69b247bcbb02cec854b53503fa244f0b16f26d85f71820 +size 47504 diff --git a/marked/Rel-16/23_series/23632/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/Rel-16/23_series/23632/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bc8f76314f89434f776118ed4801ef5027ff156 --- /dev/null +++ b/marked/Rel-16/23_series/23632/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8defa05760589a33262d34fee856690a96ff63ecf2d5dff7106bd91d4c82c957 +size 77414 diff --git a/marked/Rel-16/23_series/23632/70de8885bd7de15723aaad5eb5c5febf_img.jpg b/marked/Rel-16/23_series/23632/70de8885bd7de15723aaad5eb5c5febf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0251352051474a0e3ea518256593d2b8afa78bca --- /dev/null +++ b/marked/Rel-16/23_series/23632/70de8885bd7de15723aaad5eb5c5febf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0865e0c4e45f995b50abc5361f2e882eec8e97a9c2f3d1eb580ad37b3701beb6 +size 56457 diff --git a/marked/Rel-16/23_series/23632/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23632/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1285a7c490d77490fffaf949d4e0558276b30eaf --- /dev/null +++ b/marked/Rel-16/23_series/23632/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:734f52c4a48366f624f230e481c2a6584009e12d701e3a0dd8fbb58b5c53375f +size 61436 diff --git a/marked/Rel-16/23_series/23632/875c6f4f441fdd3ca7e1908fd1582983_img.jpg b/marked/Rel-16/23_series/23632/875c6f4f441fdd3ca7e1908fd1582983_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82ee755f778ac89ec323037f45dc5c355a6c4542 --- /dev/null +++ b/marked/Rel-16/23_series/23632/875c6f4f441fdd3ca7e1908fd1582983_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:983e6fce393a71fc09c82ca3345597d486ada0796f0185da59f4c982d5b4b327 +size 81886 diff --git a/marked/Rel-16/23_series/23632/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23632/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c25b26c01c57834ef2a46b9407d0a24cf9a32c5 --- /dev/null +++ b/marked/Rel-16/23_series/23632/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d08cfc91e9438d5bed76e66b3f47b6daa5475e51dd3c6b710245819a6914c79 +size 87285 diff --git a/marked/Rel-16/23_series/23632/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23632/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d93f43cd5bd6bcfcec90ae3c72847eb76f90ca2c --- /dev/null +++ b/marked/Rel-16/23_series/23632/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3a50456eaeab7db459aff161fe2a6021812bd5f1bd077d20f7ad707f1cf9820 +size 35680 diff --git a/marked/Rel-16/23_series/23632/a3472689858b068ef469213682965325_img.jpg b/marked/Rel-16/23_series/23632/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a0f24e71bd0fdc09271769459c5b90694d42a42 --- /dev/null +++ b/marked/Rel-16/23_series/23632/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f38cdfb2808b11c7b121bc29371e0a572d3a322208dc196fb15a5278d2a86e6c +size 39847 diff --git a/marked/Rel-16/23_series/23632/aa9441a5971655a79987d70fc551b26a_img.jpg b/marked/Rel-16/23_series/23632/aa9441a5971655a79987d70fc551b26a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99431dab4a25e94b2a4382d1b774c5059bd4649b --- /dev/null +++ b/marked/Rel-16/23_series/23632/aa9441a5971655a79987d70fc551b26a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b891e9e8010210c2ebdc744fd348c55135c9b720bd179d016eef0674e09000c +size 32686 diff --git a/marked/Rel-16/23_series/23632/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/marked/Rel-16/23_series/23632/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8777f9f397d5f3d88f4db9c5d6697cec32bdafe --- /dev/null +++ b/marked/Rel-16/23_series/23632/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6b4759208f4a7ce5966944f2d749e20987ddae4d03f3426d61e6cbaaddd551c +size 90692 diff --git a/marked/Rel-16/23_series/23632/b2f5606b9c7184c1c6070a290080a3e3_img.jpg b/marked/Rel-16/23_series/23632/b2f5606b9c7184c1c6070a290080a3e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..042b346037f43986235866b9acad9131141bea55 --- /dev/null +++ b/marked/Rel-16/23_series/23632/b2f5606b9c7184c1c6070a290080a3e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8f816fb37e8113ecf6cafaf016d8dd14f3785089f4dc7221f8bd2476f0a8818 +size 33751 diff --git a/marked/Rel-16/23_series/23632/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/23_series/23632/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a50fd4ee58cf66e507f7e696c40e3346fa1de3f --- /dev/null +++ b/marked/Rel-16/23_series/23632/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78a46e26dba3e10d5a1a561937dbc26b6ae2274aba022c4b30717f6c614532c2 +size 84869 diff --git a/marked/Rel-16/23_series/23632/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/23_series/23632/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ba95cc67d103e3eadf108a772964df493375a7f --- /dev/null +++ b/marked/Rel-16/23_series/23632/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:431f65add8ba06ed63a70611660752e1adba365391c00e1d4f306a5550d8fb56 +size 47779 diff --git a/marked/Rel-16/23_series/23632/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/Rel-16/23_series/23632/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7bcbb647c9d8429a854fd88e09d2b524b04e3e8 --- /dev/null +++ b/marked/Rel-16/23_series/23632/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ecde110fc44f0742f5c1631fc29d831ec69e60b10824df809f7c1c08e1a4b0a3 +size 52965 diff --git a/marked/Rel-16/23_series/23632/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23632/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8570b750761f385240920f36a32714256f3899a3 --- /dev/null +++ b/marked/Rel-16/23_series/23632/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95402e9edd0c5173557f8b0e1022b349f6c7c148728211e861a87d57261c62f0 +size 87727 diff --git a/marked/Rel-16/23_series/23632/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/Rel-16/23_series/23632/e636d7ccca0ad14c6b95201404324823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca57bb092dad2f1587b15e048a2131fb28785a60 --- /dev/null +++ b/marked/Rel-16/23_series/23632/e636d7ccca0ad14c6b95201404324823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89ab289fff57d848e9c835e7068fb850d9837eb4b5a653d77ae671a2729b15fc +size 45052 diff --git a/marked/Rel-16/23_series/23632/f2ea0f64a770b22b902820457d262265_img.jpg b/marked/Rel-16/23_series/23632/f2ea0f64a770b22b902820457d262265_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb2663f7f04656cf6405cd48075879f2e56e4656 --- /dev/null +++ b/marked/Rel-16/23_series/23632/f2ea0f64a770b22b902820457d262265_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d92be1d0dc9be8d05d6b0eac71e30d9dcff895be2e2985aa518edb8bd10c175 +size 71807 diff --git a/marked/Rel-16/23_series/23632/raw.md b/marked/Rel-16/23_series/23632/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6c72758de8297625be1cc3e47a9e9e63be37451f --- /dev/null +++ b/marked/Rel-16/23_series/23632/raw.md @@ -0,0 +1,2207 @@ + + +# 3GPP TS 23.632 V16.6.0 (2022-06) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; User data interworking, coexistence and migration; Stage 2; (Release 16)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5" and "G" are three green curved lines representing signal waves. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. Below the "P" is a red signal icon. Underneath the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, all-caps, sans-serif font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2022, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions of terms, symbols and abbreviations..... | 7 | +| 3.1 Terms..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 System architecture ..... | 7 | +| 4.1 Architecture for direct UDM-HSS interworking ..... | 7 | +| 4.2 Reference points for direct UDM-HSS interworking..... | 8 | +| 4.3 Service based interfaces for direct UDM-HSS interworking ..... | 8 | +| 4.4 Subscription Identifiers ..... | 8 | +| 4.5 HSS Discovery and Selection ..... | 9 | +| 4.6 UDM Discovery and Selection ..... | 9 | +| 4.7 Subscription Profiles ..... | 9 | +| 5 System procedures ..... | 10 | +| 5.1 General ..... | 10 | +| 5.2 Authentication ..... | 10 | +| 5.2.1 General ..... | 10 | +| 5.2.2 Vector Generation in HSS ..... | 10 | +| 5.2.3 Vector Generation in UDM/ARPF ..... | 11 | +| 5.2.4 HSS using the Nudr SBI..... | 13 | +| 5.3 5GC-EPC Mobility Scenarios ..... | 14 | +| 5.3.1 General ..... | 14 | +| 5.3.2 Mobility from 5GC to EPC ..... | 14 | +| 5.3.3 Mobility from EPC to 5GC ..... | 15 | +| 5.4 Scenarios of Interworking with IMS ..... | 21 | +| 5.4.1 T-ADS ..... | 21 | +| 5.4.2 P-CSCF Restoration ..... | 23 | +| 5.4.3 Network Provided Location Information Request..... | 24 | +| 5.4.4 User State Retrieval..... | 25 | +| 5.4.5 UE Reachability..... | 27 | +| 5.4.6 IMEI Retrieval..... | 29 | +| 5.4.7 SRVCC: IMS AS obtaining SRVCC data..... | 30 | +| 5.4.8 SRVCC: IMS AS obtaining SRVCC data – HSS using Nudr..... | 30 | +| 5.4.9 SRVCC: IMS AS updating STN-SR..... | 31 | +| 5.5 SMS Support ..... | 32 | +| 5.5.1 General ..... | 32 | +| 5.5.2 MT-SMS Routing Information Retrieval ..... | 32 | +| 5.5.3 MT-SMS Delivery Failure ..... | 33 | +| 5.5.4 SMS Alerting..... | 35 | +| 5.5.5 MT-SMS Routing Information Retrieval Over Nudr ..... | 37 | +| 5.5.6 Support for SMS over IP ..... | 37 | +| 5.5.6.1 General..... | 37 | +| 5.5.6.2 IP-SM-GW registration and SMS routing information retrieval in 5GC only deployments..... | 37 | +| 5.5.6.3 MT SMS delivery failure in 5GC only deployments..... | 39 | +| 5.5.6.4 Alert Service Centre in 5GC only deployments ..... | 40 | +| 5.6 Common Network Exposure Scenarios ..... | 41 | +| 5.6.1 General ..... | 41 | +| 5.6.2 Configuration of Monitoring Events in MME..... | 42 | +| 5.6.3 Synchronization of Status of Monitoring Event between HSS and UDM ..... | 43 | +| 6 Network Function Service procedures..... | 45 | +| 6.1 HSS Services ..... | 45 | + +| | | | +|---------|------------------------------------------------------------|----| +| 6.1.1 | General ..... | 45 | +| 6.1.2 | Nhss_UEAuthentication service..... | 45 | +| 6.1.2.1 | Nhss_UEAuthentication_Get service operation ..... | 45 | +| 6.1.3 | Nhss_UECM service ..... | 45 | +| 6.1.3.1 | Nhss_UECM_SNDeregistration service operation ..... | 45 | +| 6.1.3.2 | Nhss_UECM_Update service operation..... | 46 | +| 6.1.4 | Nhss_SDM service ..... | 46 | +| 6.1.4.2 | Nhss_SDM_Notification service operation ..... | 46 | +| 6.1.4.3 | Nhss_SDM_Subscribe service operation..... | 46 | +| 6.1.4.4 | Nhss_SDM_Unsubscribe service operation ..... | 47 | +| 6.1.5 | Nhss_EE service..... | 47 | +| 6.1.5.1 | Nhss_EE_Subscribe service operation ..... | 47 | +| 6.1.5.2 | Nhss_EE_Unsubscribe service operation..... | 47 | +| 6.1.5.3 | Nhss_EE_Notify service operation..... | 47 | +| 6.2 | UDM Services ..... | 48 | +| 6.2.1 | General ..... | 48 | +| 6.2.2 | Nudm_UECM service operation ..... | 48 | +| 6.2.2.1 | Nudm_UECM_P-CscfRestorationTrigger service operation ..... | 48 | +| 6.2.2.2 | Nudm_UECM_Get service operation..... | 48 | +| 6.2.2.3 | Nudm_UECM_AMFDeregistration service operation..... | 48 | +| 6.2.2.4 | Nudm_UECM_Update service operation..... | 49 | +| 6.2.3 | Nudm_MT Service ..... | 49 | +| 6.2.3.1 | Nudm_MT_ProvideDomainSelectionInfo Service..... | 49 | +| 6.2.3.2 | Nudm_MT_ProvideUserState service operation ..... | 49 | +| 6.2.3.3 | Nudm_MT_ProvideLocationInfo service operation..... | 49 | +| 6.2.3.4 | Nudm_MT_Provide5GSRVCCInfo Operation ..... | 49 | +| 6.2.4 | Nudm_EE Service ..... | 50 | +| 6.2.4.1 | Nudm_EventExposure_Subscribe service operation..... | 50 | +| 6.2.4.2 | Nudm_EventExposure_Notify service operation ..... | 50 | +| 6.2.5 | Nudm_UEAuthentication service..... | 50 | +| 6.2.5.1 | Nudm_UEAuthentication_GetHssAv service operation ..... | 50 | +| 6.2.6 | Nudm_SDM service operations ..... | 50 | +| 6.2.6.1 | Nudm_SDM_Get service operation..... | 50 | +| 6.2.6.2 | Nudm_SDM_Subscribe service operation..... | 50 | +| 6.2.6.3 | Nudm_SDM_Unsubscribe service operation ..... | 50 | +| 6.2.6.4 | Nudm_SDM_Notify service operation..... | 50 | +| 6.2.7 | Nudm_PP service operations..... | 51 | +| 6.2.7.1 | Nudm_PP_Update service operation ..... | 51 | +| 6.3 | UDR Services..... | 51 | + +| | | +|---------------------------------------------------|-----------| +| Annex A (informative): Change history..... | 52 | +|---------------------------------------------------|-----------| + +# Foreword + +This Technical Specification has been produced by the 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. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# --- 1 Scope + +The present document defines the Stage 2 architecture, procedures, flows and Network Function Services for User Data Interworking, Coexistence and Migration within the 5G System. + +# --- 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [3] 3GPP TS 23.002: "Network Architecture". +- [4] 3GPP TS 23.380: "IMS Restoration Procedures". +- [5] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [6] 3GPP TS 33.501: "Security Architecture and Procedures for 5G System". +- [7] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [8] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture". +- [9] 3GPP TS 33.402: "3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses". +- [10] 3GPP TS 33.203: "3G security; Access security for IP-based services". +- [11] 3GPP TS 33.220: "3G security; Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA)". +- [12] 3GPP TS 24.080: "Mobile radio interface layer 3 supplementary services specification - Formats and coding". +- [13] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity". +- [14] 3GPP TS 23.008: "Organization of subscriber data". +- [15] 3GPP TS 29.328: "IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents". + +- [16] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications; Stage 2". +- [17] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)". +- [18] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2". + +# 3 Definitions of terms, symbols and abbreviations + +## 3.1 Terms + +For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +## 3.2 Symbols + +Void + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|---------|----------------------------| +| 5GS UDR | 5G Unified Data Repository | +| EPS UDR | EPS User Data Repository | + +# 4 System architecture + +## 4.1 Architecture for direct UDM-HSS interworking + +Figure 4.1-1 shows the reference architecture for direct UDM-HSS interworking. + +![Figure 4.1-1: Architecture for Direct UDM-HSS interworking. The diagram shows a central HSS connected to various network functions (NFs) and data repositories. At the top, three NFs connect via 'other 5GC SBA interfaces'. The UDM connects via 'Nudm' and 'Nhss' interfaces. The HSS connects to the UDM via 'Nhss' and to the NFs via 'IMS SBA interfaces'. Below the HSS, 'SBA IMS network nodes' connect via 'IMS SBA interfaces' and 'non-SBA network nodes' connect via 'Non-SBA interfaces'. On the right, a dashed box contains '5GS-UDR' and 'EPS-UDR', which connect to the HSS via 'Ud' and 'Nudr' interfaces.](06da11ab76cacc38bbcd714e437797ea_img.jpg) + +Figure 4.1-1: Architecture for Direct UDM-HSS interworking. The diagram shows a central HSS connected to various network functions (NFs) and data repositories. At the top, three NFs connect via 'other 5GC SBA interfaces'. The UDM connects via 'Nudm' and 'Nhss' interfaces. The HSS connects to the UDM via 'Nhss' and to the NFs via 'IMS SBA interfaces'. Below the HSS, 'SBA IMS network nodes' connect via 'IMS SBA interfaces' and 'non-SBA network nodes' connect via 'Non-SBA interfaces'. On the right, a dashed box contains '5GS-UDR' and 'EPS-UDR', which connect to the HSS via 'Ud' and 'Nudr' interfaces. + +**Figure 4.1-1: Architecture for Direct UDM-HSS interworking** + +Non-SBA interfaces between the HSS and non-SBA network nodes include interfaces to / from the SMS-GMSC/IWMSC and SMS Router. In the Architecture for direct UDM-HSS interworking, as a deployment option, these Non-SBA interfaces may either be supported by the HSS or by the UDM. + +Figure 4.1-2 shows the reference architecture for direct UDM-HSS interworking using the reference point representation. + +![Figure 4.1-2: Architecture for Direct UDM-HSS interworking in reference point representation. The diagram shows a hierarchy of network functions. At the top, 5GS-UDR and EPS-UDR are shown in a dashed box. Below them, UDM and HSS are shown in another dashed box. At the bottom, 5GC, EPC, and IMS are shown. Reference points are indicated by lines with labels: N35 between 5GS-UDR and UDM; NU2 between 5GS-UDR and HSS; NU1 between UDM and HSS; Ud between EPS-UDR and HSS; N8/N10/N13/N21/N52/NL6 between UDM and 5GC; S6a/S6d/SWx/... between HSS and EPC; Cx/Sh N70/N71 between HSS and IMS; and N26 between 5GC and EPC.](d0abac95583b52a3b35f74a215567334_img.jpg) + +Figure 4.1-2: Architecture for Direct UDM-HSS interworking in reference point representation. The diagram shows a hierarchy of network functions. At the top, 5GS-UDR and EPS-UDR are shown in a dashed box. Below them, UDM and HSS are shown in another dashed box. At the bottom, 5GC, EPC, and IMS are shown. Reference points are indicated by lines with labels: N35 between 5GS-UDR and UDM; NU2 between 5GS-UDR and HSS; NU1 between UDM and HSS; Ud between EPS-UDR and HSS; N8/N10/N13/N21/N52/NL6 between UDM and 5GC; S6a/S6d/SWx/... between HSS and EPC; Cx/Sh N70/N71 between HSS and IMS; and N26 between 5GC and EPC. + +**Figure 4.1-2: Architecture for Direct UDM-HSS interworking in reference point representation** + +The 5GS-UDR (Unified Data Repository) and EPS-UDR (User Data Repository) may be collocated, forming a common repository. + +NOTE: The HSS is only using the NU2 reference point for the purpose of interworking with 5GS, i.e. NU2 is not a replacement of the Ud interface. + +## 4.2 Reference points for direct UDM-HSS interworking + +The following reference points are realized by service-based interfaces: + +- NU1:** Reference point between the HSS and the UDM. +- NU2:** Reference point between the HSS and the 5GS-UDR. + +For a list of other SBA reference points supported in 5GC see 3GPP TS 23.501 [2]. + +For a list of IMS reference points, including SBA IMS reference points, see 3GPP TS 23.228 [7]. + +For a list of Non-SBA reference points and Network Nodes interfacing the HSS see 3GPP TS 23.002 [3]. + +The HSS makes use of the Ud reference point to interact with the EPS-UDR. The UDM makes use of the N35 reference point to interact with the 5GS-UDR. + +## 4.3 Service based interfaces for direct UDM-HSS interworking + +- Nudm:** Service-based interface exhibited by UDM. +- Nhss:** Service-based interface exhibited by HSS. + +The HSS shall make use of Nudm services as described in clause 6.2 and may make use of Nudr services as described in clause 6.3. + +The UDM shall make use of Nhss services and Nudr services as described in clauses 6.1 and 6.3. + +## 4.4 Subscription Identifiers + +As defined in 3GPP TS 23.501 [2], for interworking with the EPC, the SUPI allocated to the 3GPP UE shall always be based on an IMSI to enable the UE to present an IMSI to the EPC. + +The subscription identifier used over NU1 reference point in Nhss services shall be an IMSI. The UDM extracts the IMSI from the user's SUPI. + +The subscription identifier used over NU1 reference point in Nudm services shall be a SUPI based on an IMSI. The HSS creates a SUPI from the user's IMSI or the IMSI associated to the user's public identifier in the EPS or IMS domain (e.g. user's MSISDN or IMPU). + +## 4.5 HSS Discovery and Selection + +This clause defines the procedures for HSS discovery and selection by the UDM. The procedures for HSS discovery and selection by SBI capable IMS entities is defined in 3GPP TS 23.228 [7]. + +The UDM performs HSS discovery to discover an HSS that manages the user subscriptions in EPC. + +The UDM shall utilize the NRF to discover the HSS instance(s) unless the information about HSS instances is available by other means, e.g. locally configured on the UDM. The HSS selection function in UDM selects an HSS instance based on the available HSS instances (obtained from the NRF or locally configured). + +When the NRF is used for HSS discovery, the HSS registers in the NRF using the Nnrf\_NFManagement\_NFRegister Request message as defined in 3GPP TS 23.502 [5]. + +Different HSS instances managing different sets of IMSI/MSISDN ranges may be deployed in a given PLMN. In this case, the HSS instances register in NRF using either different ranges of IMSI/MSISDN and/or HSS Group IDs. + +NOTE 1: In deployments where simple IMSI/MSISDN ranges are not suitable to describe the IMSI/MSISDN sets served by HSS instances, it is expected the HSS instances only register HSS Group IDs. + +When NRF is used for HSS discovery, the UDM sends a Nnrf\_NFDiscovery\_Request to NRF as defined in 3GPP TS 23.502 [5] to discover HSS instances within a given PLMN. The UDM may store all returned HSS instances and their NF profiles for subsequent use, including, if applicable, supported IMSI/MSISDN ranges, and/or HSS Group IDs. + +The UDM may use Nnrf\_NFStatusSubscribe/Unsubscribe service operations with NRF as defined in 3GPP TS 23.502 [5] to receive Nnrf\_NFStatusNotify service operation for updates to the NF profiles of HSS instances registered in NRF. + +The UDM always selects an HSS within its own PLMN. The HSS selection should consider one of the following factors when available to the UDM entity: + +1. HSS Group ID of the UE's IMSI. +2. IMSI; the UDM selects an HSS instance based on the IMSI range the UE's IMSI belongs to or based on the results of a discovery procedure with NRF using the UE's IMSI as input for HSS discovery. + +NOTE 2: In this release of the specification there is not identified need for the UDM to be able to select the HSS based on IMS identifiers (IMPI, IMPU) neither based on MSISDN or External Group ID. + +## 4.6 UDM Discovery and Selection + +The HSS performs UDM discovery and selection as described in 3GPP TS 23.501 [2]. + +## 4.7 Subscription Profiles + +In the context of Mobility, IMS and SMS use cases, the HSS initiates interworking with the UDM only for UEs which have a 5G subscription that is known to be active in 5GC. + +NOTE: The HSS may be aware that a 5G subscription for the UE exists based on the Core Network Type restrictions defined for the UE (i.e. If restriction for Core Network Type indicates that the UE can access to 5GC, it implies that the UE has 5G subscription data). Additionally, the HSS may be aware that a UE for which 5G subscription data exist is not active in 5GC e.g. when the HSS has not yet received an Nhss\_UECM\_SNDeregistration request from the UDM for that UE (see clause 5.3.3 step 3). + +# 5 System procedures + +## 5.1 General + +Procedures involving communication between HSS and UDM comprise Authentication, Mobility, IMS interworking, and SMS support. + +## 5.2 Authentication + +### 5.2.1 General + +A subscriber's authentication subscription data, including the subscriber's long-term key(s) and sequence number, shall be stored in a single repository so that a single sequence number can be maintained for the subscriber. + +The subscriber's long-term key(s) shall not be transferred over the NU1 reference point between HSS and UDM. Also it is not expected that the UDM has direct standardized access to the EPS-UDR. Therefore, the following options exist for subscribers with both 5G and EPS subscription: + +- 1) Authentication subscription data are stored in the EPS-UDR and all authentication vectors are calculated in the HSS. Subscription data stored in the 5GS-UDR or locally configured in the UDM indicate that the UDM needs to consume the Nhss\_UEAuthentication\_Get service operation to retrieve a 5G vector from the HSS. See clause 5.2.2 for details. +- 2) Authentication subscription data are stored in the 5GS-UDR and all authentication vectors are calculated in the UDM. Subscription data stored in the EPS-UDR or locally configured in the HSS indicate that the HSS needs to consume the Nudm\_UEAuthentication\_GetHssAv service operation to retrieve an EPS vector from the UDM. See clause 5.2.3 for details. +- 3) Authentication subscription data are stored in the 5GS-UDR, 5G vectors are calculated in the UDM and EPS vectors are calculated in the HSS. Subscription data stored in the EPS-UDR or locally configured in the HSS indicate that the HSS needs to consume the Nudr\_DM\_Query service operation to retrieve authentication subscription data from the 5GS-UDR. See clause 5.2.4 for details. + +The following clauses specify the system procedures for these different alternatives. + +### 5.2.2 Vector Generation in HSS + +This clause specifies the procedures for authentication vector request when the subscriber's authentication subscription data is stored at the EPS-UDR. In this case, the UDM requests the generation of the Authentication Vector for 5GS to the HSS. + +NOTE: The HSS acts as ARPF rather than as AuC and it is required to generate authentication vectors as defined in 3GPP TS 33.501 [6]. + +When the UDM receives an authentication information Request from the AUSF it shall check (by means of an 5GS-UDR query or local configuration in the UDM) whether the subscribed authentication method is 5G\_AKA or EAP\_AKA\_PRIME and if so whether 5G authentication vector generation for the identified subscriber shall be done in the HSS. If so, the UDM shall make use of the Nhss\_UEAuthentication\_Get service operation to retrieve a 5G authentication vector from the HSS. + +Figure 5.2.2-1 shows the scenario where the authentication vector request for a 5G subscriber who also has an EPS subscription is received by the UDM. + +![Sequence diagram for 5G subscriber authentication with AV generation in HSS. Lifelines: AUSF, 5GS-UDR, UDM, HSS, EPS-UDR. The sequence shows the UDM requesting an authentication vector from the HSS, which then generates it and updates the EPS-UDR before returning it to the UDM and then the AUSF.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` + +sequenceDiagram + participant AUSF + participant 5GS-UDR + participant UDM + participant HSS + participant EPS-UDR + Note right of HSS: 5. Generate AV in AuC + + AUSF->>UDM: 1. Nudm_UEAuthentication Get req + UDM->>5GS-UDR: 2. Nudr_DM_Query + UDM->>HSS: 3. Nhss_UEAuthentication Get req + HSS->>EPS-UDR: 4. Read + Note right of HSS: 5. Generate AV in AuC + HSS->>UDM: 6. Nhss_UEAuthentication Get resp + HSS->>EPS-UDR: 7. Update + UDM->>AUSF: 8. Nudm_UEAuthentication Get resp + +``` + +Sequence diagram for 5G subscriber authentication with AV generation in HSS. Lifelines: AUSF, 5GS-UDR, UDM, HSS, EPS-UDR. The sequence shows the UDM requesting an authentication vector from the HSS, which then generates it and updates the EPS-UDR before returning it to the UDM and then the AUSF. + +**Figure 5.2.2-1: Authentication for 5G subscriber with authentication vector generation in HSS** + +1. The UDM receives an Authentication Vector request, containing the identity of the user (SUPI or SUCI). If SUCI is received, the UDM performs SUCI to SUPI de-concealment. For details of the Nudm\_UEAuthentication Service see 3GPP TS 23.502 [5] and 3GPP TS 33.501 [6]. +2. If the 5GS-UDR is used, the UDM queries the 5GS-UDR using the SUPI to retrieve Authentication Subscription Information. In this scenario the Authentication Subscription Information contains a subscribed authentication method of 5G\_AKA or EAP\_AKA\_PRIME and an indicator indicating that authentication vector generation shall be performed in the HSS. Optionally, the indication that the authentication vector generation shall be performed in the HSS could be locally configured at the UDM/ARPF. +3. The UDM uses the Nhss\_UEAuthentication\_Get service operation to retrieve an authentication vector from the HSS. The request contains the IMSI the authentication method and serving network name. +4. The HSS reads authentication subscription data from the EPS-UDR. This step is omitted if all relevant authentication subscription data are stored locally in the HSS. +5. The HSS (AuC/ARPF) calculates the requested authentication vector taking into account the serving network name and authentication method received in step 3 and the authentication subscription information retrieved from the EPS-UDR. +6. The calculated authentication vector is sent to the UDM. +7. The HSS updates the EPS-UDR with the new sequence number. This step is omitted if the sequence number is stored locally in the HSS. +8. The UDM forwards the authentication vector to the AUSF. + +### 5.2.3 Vector Generation in UDM/ARPF + +This clause specifies the procedures for authentication vector request when the subscriber's authentication subscription data is stored at the 5GS-UDR. In this case, the HSS requests the generation of the Authentication Vector for EPS and/or IMS to the UDM. + +NOTE: The UDM acts as AuC rather than as ARPF and it is required to generate authentication vectors as defined in 3GPP TS 33.401 [8], 3GPP TS 33.402 [9], 3GPP TS 33.203 [10] and 3GPP TS 33.220 [11]. + +When the HSS receives an authentication vector request from a serving node (e.g. MME, SGSN, VLR, S-CSCF, BSF) it shall check (by means of an EPC-UDR query) whether authentication vector generation for the identified subscriber shall be done in the UDM. If so, the HSS shall make use of the Nudm\_UEAuthentication\_GetHssAv service operation to retrieve authentication vectors from the UDM. + +Figure 4.2.3-1 shows the scenario where an authentication vector request for a subscriber is received by the HSS and subscription data stored in the EPS-UDR indicate that for the subscriber authentication vector generation is to be performed in the UDM. + +![Sequence diagram for authentication with vector generation in UDM. Lifelines: Serving Node, EPS-UDR (connected to HSS via Ud), HSS, UDM, and 5GS-UDR. The sequence starts with the Serving Node sending an 'Authentication Vector Request' to the HSS. The HSS sends a 'Read' message to the EPS-UDR. The HSS then sends a 'Nudm_UEAuthentication_GetHssAv Req' to the UDM. The UDM sends a 'Nudr_DM_Query' to the 5GS-UDR. The 5GS-UDR returns data to the UDM, which performs 'Generate AV in ARPF'. The UDM sends a 'Nudm_UEAuthentication_GetHssAv Resp' back to the HSS. Finally, the HSS sends an 'Authentication Vector Response' to the Serving Node, and the UDM sends an 'Update' message to the 5GS-UDR.](08441fa90c5fd11994626f662ac13f19_img.jpg) + +``` + +sequenceDiagram + participant SN as Serving Node + participant EPS-UDR as EPS-UDR + participant HSS as HSS + participant UDM as UDM + participant 5GS-UDR as 5GS-UDR + + Note right of EPS-UDR: Ud + SN->>HSS: 1. Authentication Vector Request + HSS->>EPS-UDR: 2. Read + HSS->>UDM: 3. Nudm_UEAuthentication_GetHssAv Req + UDM->>5GS-UDR: 4. Nudr_DM_Query + Note right of UDM: 5. Generate AV in ARPF + UDM->>HSS: 6. Nudm_UEAuthentication_GetHssAv Resp + HSS->>SN: 8. Authentication Vector Response + UDM->>5GS-UDR: 7. Update + +``` + +Sequence diagram for authentication with vector generation in UDM. Lifelines: Serving Node, EPS-UDR (connected to HSS via Ud), HSS, UDM, and 5GS-UDR. The sequence starts with the Serving Node sending an 'Authentication Vector Request' to the HSS. The HSS sends a 'Read' message to the EPS-UDR. The HSS then sends a 'Nudm\_UEAuthentication\_GetHssAv Req' to the UDM. The UDM sends a 'Nudr\_DM\_Query' to the 5GS-UDR. The 5GS-UDR returns data to the UDM, which performs 'Generate AV in ARPF'. The UDM sends a 'Nudm\_UEAuthentication\_GetHssAv Resp' back to the HSS. Finally, the HSS sends an 'Authentication Vector Response' to the Serving Node, and the UDM sends an 'Update' message to the 5GS-UDR. + +**Figure 5.2.3-1: Authentication for a subscriber with authentication vector generation in UDM** + +1. The HSS receives an Authentication Vector request, containing the identity of the user (IMSI, or Public User Identity and/or Private User Identity). +2. The HSS queries the EPS-UDR using the identity of the user to retrieve Authentication Subscription Information. In this scenario the Authentication Subscription Information contains an indicator indicating that authentication vector generation shall be performed in the UDM. +3. The HSS uses the Nudm\_UEAuthentication\_GetHssAv service operation to retrieve an authentication vector from the UDM. The request contains the identity of the user, the type of the requested vector (E-UTRAN/UTRAN or GERAN/ IMS-AKA and when available the visited PLMN-ID). +4. The UDM reads authentication subscription data from the 5GS-UDR. +5. The UDM (ARPF) calculates the requested authentication vectors taking into account the information received in step 3 and the authentication subscription information retrieved from the 5GS-UDR. +6. The calculated authentication vectors are sent to the HSS. +7. The UDM updates the 5GS-UDR with the new sequence number. +8. The HSS forwards the authentication vectors to the serving node. + +### 5.2.4 HSS using the Nudr SBI + +When the HSS receives an S6a-AIR from the MME, it may check (by means of an EPC-UDR query) whether the subscriber has a 5G subscription. If so, the HSS can use of the Nudr\_DM\_Query Get service operation to retrieve the authentication subscription data from the 5GS UDR and generate the authentication vector. + +Figure 5.2.4-1 shows the scenario where the authentication vector request for a 5G subscriber who also has an EPS subscription is received by the UDM. + +![Sequence diagram for authentication of a 5G subscriber with EPS subscription. Lifelines: MME, HSS, 5GS-UDR, EPC-UDR. The sequence shows the HSS checking the EPC-UDR for 5G subscription info, then querying the 5GS-UDR for authentication data, generating an authentication vector, returning it to the MME, and updating the 5GS-UDR.](ddc7460821484f1ae2835c67955c554c_img.jpg) + +``` +sequenceDiagram + participant MME + participant HSS + participant 5GS-UDR + participant EPC-UDR + Note right of HSS: 4. Generate AV in AuC + + MME->>HSS: 1. S6a-AIR + HSS->>EPC-UDR: 2. Ud Read + HSS->>5GS-UDR: 3. Nudr_DM_Query + Note right of HSS: 4. Generate AV in AuC + HSS->>MME: 5. S6a-AIA + HSS->>5GS-UDR: 6. Nudr_DM_Update +``` + +Sequence diagram for authentication of a 5G subscriber with EPS subscription. Lifelines: MME, HSS, 5GS-UDR, EPC-UDR. The sequence shows the HSS checking the EPC-UDR for 5G subscription info, then querying the 5GS-UDR for authentication data, generating an authentication vector, returning it to the MME, and updating the 5GS-UDR. + +**Figure 5.2.4-1: Authentication for 5G subscriber with EPS subscription** + +1. The HSS receives an Authentication Vector request containing the identity of the user (IMSI). + 2. The HSS queries the EPC-UDR using the IMSI to retrieve Authentication Subscription Information. Since the subscriber is a 5G subscriber the response indicates that the subscriber's authentication information is stored in the 5GS UDR. +- NOTE: Local configuration in the HSS may indicate that authentication subscription data for all subscribers can be obtained from the 5G UDR and thus this step may be omitted. +3. The HSS uses the Nudr\_DM\_Query Get service operation to retrieve the authentication subscription data from the 5GS UDR. The request contains the IMSI formatted as a SUPI. + 4. The HSS (AuC) calculates the requested authentication vector taking into account the serving network name and authentication method received in step 1 and the authentication subscription information retrieved from the 5GS-UDR in step 3. + 5. The calculated authentication vector is returned to the MME. + 6. The HSS updates the 5GS-UDR with the new sequence number. + +## 5.3 5GC-EPC Mobility Scenarios + +### 5.3.1 General + +As defined in 3GPP TS 23.501 [2], when interworking procedures with N26 are used, the UE operates in single-registration mode. For the 3GPP access, either the AMF or the MME is registered in the HSS+UDM. This implies that: + +- The registration of an MME in HSS for a UE that is capable to access the 5GC, triggers the cancellation of the AMF address for 3GPP access registered in the UDM, if any. +- The registration of an AMF in UDM for a UE that is capable to access the EPC, triggers the cancellation of the MME address registered in the HSS, if any. + +Interworking procedures without N26 do not require that the HSS+UDM cancels the location of the old serving node in the old access domain. However, the UDM may request from the HSS the cancellation of the SGSN. + +Additionally, upon mobility from GERAN/UTRAN to 5GS, the previously registered SGSN needs to be cancelled from HSS/HLR, otherwise the incoming session can fail. + +Additionally, IP address preservation for PDU sessions that support interworking is provided to UEs during inter-system mobility procedures by storing and fetching the PGW-C+SMF FQDN for S5/S8 interface per APN/DNN via the HSS+UDM. + +### 5.3.2 Mobility from 5GC to EPC + +Figure 5.3.2-1 shows the interaction between the HSS and UDM in an interworking scenario when the UE attaches to the EPC. + +![Sequence diagram showing mobility from 5GC to EPC. The diagram illustrates the interaction between AMF, UDM, HSS, and MME. The sequence of messages is: 1. S6a-ULR from MME to HSS; 2. S6a-ULA from HSS to MME; 3. Nudm_UECM_AMFDeregistration Request from HSS to UDM; 4. Nudm_UECM_AMFDeregistration Response from UDM to HSS; 5. Nudm_UECM_DeregistrationNotification from UDM to AMF (dashed line).](66c2bf11a8f117cddf67eff92d4c736c_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant UDM + participant HSS + participant MME + Note right of MME: 1. S6a-ULR + MME->>HSS: 1. S6a-ULR + Note right of HSS: 2. S6a-ULA + HSS->>MME: 2. S6a-ULA + Note right of HSS: 3. Nudm_UECM_AMFDeregistration Request + HSS->>UDM: 3. Nudm_UECM_AMFDeregistration Request + Note right of UDM: 4. Nudm_UECM_AMFDeregistration Response + UDM->>HSS: 4. Nudm_UECM_AMFDeregistration Response + Note right of UDM: 5. Nudm_UECM_DeregistrationNotification + UDM-->>AMF: 5. Nudm_UECM_DeregistrationNotification + +``` + +Sequence diagram showing mobility from 5GC to EPC. The diagram illustrates the interaction between AMF, UDM, HSS, and MME. The sequence of messages is: 1. S6a-ULR from MME to HSS; 2. S6a-ULA from HSS to MME; 3. Nudm\_UECM\_AMFDeregistration Request from HSS to UDM; 4. Nudm\_UECM\_AMFDeregistration Response from UDM to HSS; 5. Nudm\_UECM\_DeregistrationNotification from UDM to AMF (dashed line). + +Figure 5.3.2-1: Mobility from 5GC to EPC + +1. The HSS receives an S6a ULR request containing the IMSI of the subscriber. + +The HSS stores the new MME address. If the EPC UDR is used, the HSS updates the EPS-UDR with the new MME address and reads the subscription information related to the IMSI from the EPS-UDR. + +The UE's subscription may include restriction for Core Network Type (5GC). If restriction for Core Network Type indicates that the UE can access to 5GC, it implies that the UE has 5G subscription data. + +2. The HSS responds to the MME with an S6a-ULA. +3. If the dual registration 5GS indicator is not set in the S6a ULR request and the subscription information related to the IMSI does not indicate that 5GC is restricted, then the HSS uses the Nudm\_UECM\_AMFDeregistration service operation to request the UDM to cancel the registration of the user in 5GC for 3GPP access, if any. The HSS includes the user's IMSI received in step 1 as the user's SUPI in this request. + +If the S6a ULR request includes the initial attach indicator set, the HSS indicates to the UDM that the deregistration reason is due to "Initial Registration". When the initial attach indicator is not set, the HSS indicates to the UDM that the deregistration reason is due to 5GS to EPS mobility. + +NOTE: If the dual registration 5GS indicator is set in the S6a ULR request, the HSS is not required to request the UDM to cancel the location of the UE in AMF if any. + +4. The UDM responds to the HSS. + +The UDM checks if the user is registered in 5GC over 3GPP access. The UDM may use the 5GS-UDR to retrieve the address of the AMF for 3GPP access registered in UDM for that user, if any. If the user is registered at an AMF for 3GPP access, step 5 is executed. + +5. If there is an AMF address for 3GPP access found for the user, the UDM cancels the user registration in 5GC by sending a Nudm\_UECM\_DeregistrationNotification to the AMF. + +### 5.3.3 Mobility from EPC to 5GC + +Figure 5.3.3-1 shows the interaction between the UDM and the HSS in an interworking scenario when the UE attaches to the 5GC. + +![Sequence diagram showing mobility from EPC to 5GC. The diagram illustrates the interaction between AMF, UDM, HSS, and MME/SGSN. The sequence of messages is: 1. Nudm_UECM_Registration Request from AMF to UDM; 2. Nudm_UECM_Registration Response from UDM to AMF; 3. Nhss_UECM_SNDeregistration Request from UDM to HSS; 4. Nhss_UECM_SNDeregistration Response from HSS to UDM; 5. S6a/S6d-CLR/CLA or MAP Cancel loc from HSS to MME/SGSN.](70de8885bd7de15723aaad5eb5c5febf_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant UDM + participant HSS + participant MME/SGSN + Note left of AMF: UE attaches to 5GC + AMF->>UDM: 1. Nudm_UECM_Registration Request + UDM-->>AMF: 2. Nudm_UECM_Registration Response + UDM->>HSS: 3. Nhss_UECM_SNDeregistration Request + HSS-->>UDM: 4. Nhss_UECM_SNDeregistration Response + HSS-->>MME/SGSN: 5. S6a/S6d-CLR/CLA or MAP Cancel loc + +``` + +Sequence diagram showing mobility from EPC to 5GC. The diagram illustrates the interaction between AMF, UDM, HSS, and MME/SGSN. The sequence of messages is: 1. Nudm\_UECM\_Registration Request from AMF to UDM; 2. Nudm\_UECM\_Registration Response from UDM to AMF; 3. Nhss\_UECM\_SNDeregistration Request from UDM to HSS; 4. Nhss\_UECM\_SNDeregistration Response from HSS to UDM; 5. S6a/S6d-CLR/CLA or MAP Cancel loc from HSS to MME/SGSN. + +Figure 5.3.3-1: Mobility from EPC to 5GC + +1. The UDM receives a Nudm\_UECM\_Registration request for 3GPP access containing the SUPI of the subscriber. In this case the SUPI shall be based on an IMSI. + +The UDM stores the new AMF address for 3GPP access. If the 5GS-UDR is used, the UDM updates the 5GS-UDR with the new AMF address for 3GPP access and reads the subscription information related to the SUPI from the 5GS-UDR. + +The UE's subscription may include restriction for Core Network Type (EPC). If restriction for Core Network Type indicates that the UE can access to EPC, it implies that the UE has EPC subscription data and that the UE may also be able to access via GERAN/UTRAN. + +2. The UDM responds to the AMF with a Nudm\_UECM\_Registration Response. +3. If the dual registration and the initial registration flags are not set in the Nudm\_UECM\_Registration request and the subscription information related to the SUPI does not indicate that EPC is restricted, then the UDM uses the Nhss\_UECM\_SNDeregistration service operation indicating that the deregistration reason is due to EPS to 5GS mobility to request the HSS to cancel the MME/SGSN registration of the user in EPC, if any. The UDM includes the IMSI based on SUPI received in step 1 as the user's IMSI in this request. + +If the dual registration flags is set in the Nudm\_UECM\_Registration request and the subscription information related to the SUPI does not indicate that EPC is restricted, then the UDM uses the Nhss\_UECM\_SNDeregistration service operation indicating that the deregistration reason is due to Initial and + +Dual Registration to request the HSS to cancel the SGSN registration of the user in EPC, if any. The UDM includes the IMSI based on SUPI received in step 1 as the user's IMSI in this request. + +If the dual registration flag is not set and the initial registration flag is set in the Nudm\_UECM\_Registration request and the subscription information related to the SUPI does not indicate that EPC is restricted, then the UDM uses the Nhss\_UECM\_SNDeregistration service operation indicating that the deregistration reason is due to Initial and Single Registration to request the HSS to cancel the MME/SGSN registrations of the user in EPC, if any. The UDM includes the IMSI based on SUPI received in step 1 as the user's IMSI in this request. + +4. The HSS responds to the UDM. + +The HSS checks if the user is registered in EPC. The HSS may use the EPS-UDR to retrieve the address of the MME or SGSN registered in the HSS for that user, if any. If the user is registered at an MME or SGSN, step 5 is executed. + +5. If there is an MME address found for the user and the deregistration reason in the Nhss\_UECM\_SNDeregistration service operation indicated "Initial and Single Registration" or "EPS to 5GS mobility", the HSS cancels the attachment of the IMSI in the MME by sending a CLR via the S6a interface setting the cancellation type to MME Update Procedure, and if a VLR number was found in the HSS for the user, the HSS also cancels attachment of the IMSI in this MSC/VLR by sending the MAP Cancel Location (IMSI) to the MSC/VLR via the D interface. + +If there is an SGSN address found for the user and the deregistration reason in the Nhss\_UECM\_SNDeregistration service operation indicated "Initial and Single Registration", the HSS cancels the attachment of the IMSI in the SGSN by sending a CLR via the S6d interface or by sending the MAP Cancel Loc via the Gr interface setting the cancellation type to SGSN Update Procedure. When deregistration reason indicated "Initial and Dual Registration" or "EPS to 5GS Mobility", the HSS cancels the attachment of the IMSI in the SGSN by sending a CLR via the S6d interface setting the cancellation type to SGSN Update Procedure. + +### 5.3.4 Support for PDU session continuity during intersystem mobility procedures + +When the UE is connected to 5GS or 5GC-N3IWF, the PGW-C+SMF may store in UDM the PGW-C+SMF FQDN for S5/S8/S2b interface, within the UE context in SMF data, when the PGW-C+SMF registers in UDM. The AMF serving 3GPP access may also notify the UDM to store the association between DNN and PGW-C+SMF FQDN which supports EPS interworking as Intersystem continuity context. + +During mobility from 5GC to EPC or EPC/ePDG, or mobility from 5GC-N3IWF to EPC, or mobility from EPC/ePDG to EPC, the HSS uses the Nudm\_SDM\_Get service operation to retrieve the PGW-C+SMF FQDN for S5/S8/S2b interface from UDM, and subscribes to be notified using Nudm\_SDM\_Subscribe when the Intersystem continuity context data or the UE context in SMF data are modified. The HSS retrieves both the UE context in SMF data and the Intersystem continuity context data from UDM. The HSS checks the Intersystem continuity context first. If no PGW-C+SMF FQDN associated with the APN exists in Intersystem continuity context, the HSS selects one of the PGW-C+SMF FQDN for the APN from the UE context in SMF data based on operator's policy. + +During UE registration for the scenario when ePDG is connected to SMF+PGW-C and S6b is not used, the HSS subscribes to be notified from the UDM using Nudm\_SDM\_Subscribe when the UE context in SMF data is modified as new PDU sessions established in the ePDG are not updated in the HSS via the SWx interface. + +Figure 5.3.4-1 shows the interaction between the HSS and the UDM in an interworking scenario when the UE attaches to the EPC or EPC/ePDG. + +![Sequence diagram illustrating PDU session continuity during mobility from 5GC to EPC. The diagram shows interactions between AMF/SMF, UDM, HSS, and MME/AAA. Step 0: AMF/SMF sends Nudm_UECM_Registration/Update to UDM. Step 1: HSS sends S6a-ULR / SWx-SAR to UDM. Step 2: UDM sends Nudm_SDM_Get Request to HSS. Step 3: HSS sends Nudm_SDM_Get Response to UDM. Step 4: UDM sends Nudm_SDM_Subscribe to HSS. Step 5: HSS sends Nudm_SDM_Subscribe Response to UDM. Step 6: HSS sends S6a-ULA / SWx-SAA to MME/AAA.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant AMF/SMF + participant UDM + participant HSS + participant MME/AAA + + Note left of AMF/SMF: 0. Nudm_UECM_Registration/Update + AMF/SMF-->>UDM: 0. Nudm_UECM_Registration/Update + + Note right of HSS: 1. S6a-ULR / SWx-SAR + HSS-->>UDM: 1. S6a-ULR / SWx-SAR + + Note left of UDM: 2. Nudm_SDM_Get Request + UDM-->>HSS: 2. Nudm_SDM_Get Request + + Note right of HSS: 3. Nudm_SDM_Get Response + HSS-->>UDM: 3. Nudm_SDM_Get Response + + Note left of UDM: 4. Nudm_SDM_Subscribe + UDM-->>HSS: 4. Nudm_SDM_Subscribe + + Note right of HSS: 5. Nudm_SDM_Subscribe Response + HSS-->>UDM: 5. Nudm_SDM_Subscribe Response + + Note right of HSS: 6. S6a-ULA / SWx-SAA + HSS-->>MME/AAA: 6. S6a-ULA / SWx-SAA + +``` + +Sequence diagram illustrating PDU session continuity during mobility from 5GC to EPC. The diagram shows interactions between AMF/SMF, UDM, HSS, and MME/AAA. Step 0: AMF/SMF sends Nudm\_UECM\_Registration/Update to UDM. Step 1: HSS sends S6a-ULR / SWx-SAR to UDM. Step 2: UDM sends Nudm\_SDM\_Get Request to HSS. Step 3: HSS sends Nudm\_SDM\_Get Response to UDM. Step 4: UDM sends Nudm\_SDM\_Subscribe to HSS. Step 5: HSS sends Nudm\_SDM\_Subscribe Response to UDM. Step 6: HSS sends S6a-ULA / SWx-SAA to MME/AAA. + +**Figure 5.3.4-1: PDU session continuity during mobility from 5GC to EPC** + +0. While the UE is connected to the 5GC, the AMF and/or SMF may store in UDM the association between DNN and PGW-C+SMF FQDN which supports EPS interworking. + +If the 5GS UDR is used, the UDM updates the 5GS-UDR with the DNN and PGW-C+SMF FQDN association. + +1. The HSS receives an S6a ULR or SWx SAR request containing the IMSI of the subscriber. + +The HSS reads the subscription information related to the IMSI. If the EPC-UDR is used, the HSS retrieves the subscription information from the EPS-UDR. The UE's subscription may include subscribed APNs that support interworking with 5GS. + +2. If the subscription information related to the IMSI includes subscribed APNs that support interworking with 5GS, then the HSS uses the Nudm\_SDM\_Get service operation to fetch the UE context in SMF data and the Intersystem continuity context data for the user in AMF data, if any. The HSS includes the user's IMSI received in step 1 as the user's SUPI in this request. + +3. The UDM responds to the HSS. + +The HSS checks the Intersystem continuity context first. If no PGW-C+SMF FQDN associated with an DNN exists in Intersystem continuity context, the HSS selects one of the PGW-C+SMF FQDN for the APN from the UE context in SMF data based on operator's policy. + +- 4-5. The HSS subscribes to be notified using Nudm\_SDM\_Subscribe service operation when the Intersystem continuity context data or the UE context in SMF data are modified. + +6. The HSS responds to the MME with an S6a-ULA response or to the AAA with an SWx-SAA response including the PGW-C+SMF FQDN associated with subscribed APNs that support interworking with 5GS, if any. This step may happen at any time after step 3, not necessarily after steps 4-5. + +If an S6a ULR is received, the HSS performs steps 3 and 4 of clause 5.3.2. + +Figure 5.3.4-2 shows the interaction between the HSS and the UDM when the HSS receives notification from the UDM when the data requested is modified. + +![Sequence diagram showing the notification of PGW-C+SMF FQDN from UDM to HSS. The diagram involves four lifelines: AMF/SMF, UDM, HSS, and MME/AAA. The sequence of messages is: 0. Nudm_UECM_Registration/Deregistration/Update (dashed arrow from AMF/SMF to UDM); 1. Nudm_SDM_Notification (solid arrow from UDM to HSS); 2. Nudm_SDM_Notification Response (solid arrow from HSS to UDM); 3. S6a-Insert Subscriber Data SWx-User Profile Update (dashed arrow from HSS to MME/AAA).](4356776ca004ecba5d599667a155d7d4_img.jpg) + +Sequence diagram showing the notification of PGW-C+SMF FQDN from UDM to HSS. The diagram involves four lifelines: AMF/SMF, UDM, HSS, and MME/AAA. The sequence of messages is: 0. Nudm\_UECM\_Registration/Deregistration/Update (dashed arrow from AMF/SMF to UDM); 1. Nudm\_SDM\_Notification (solid arrow from UDM to HSS); 2. Nudm\_SDM\_Notification Response (solid arrow from HSS to UDM); 3. S6a-Insert Subscriber Data SWx-User Profile Update (dashed arrow from HSS to MME/AAA). + +**Figure 5.3.4-2: Notification of PGW-C+SMF FQDN from UDM to HSS** + +0. The AMF and/or SMF may add or remove or update the association between DNN and PGW-C+SMF FQDN stored in the UDM. + +If the 5GS UDR is used, the UDM updates the 5GS-UDR with the DNN and PGW-C+SMF FQDN association. + +1. If the UDM finds the UE context in SMF data or the Intersystem continuity context is changed, and the active subscription from the HSS exists for the UE to be notified on the change of the UE context in SMF data or the Intersystem continuity context, then the UDM uses the Nudm\_SDM\_Notification service operation to notify the HSS. As part of this notification the UDM informs the HSS whether the SMF indicated that the access to 5GC was via an ePDG. + +2. The HSS responds to the UDM. + +The HSS checks the change of the association between APN and PGW-C+SMF FQDN. If multiple PGW-C+SMF FQDN exists in the UE context in SMF data, the HSS selects one of the PGW-C+SMF FQDN for the APN based on operator's policy. + +3. The HSS may further trigger PDN GW Identify Notification procedure, as defined in clause 12.1.4 and clause 12.1.5 in TS 23.402. + +Figure 5.3.4-3 shows the interaction between the HSS and the UDM when the HSS unsubscribes from the UDM to be notified when the data requested is modified. + +![Sequence diagram showing the unsubscribe of PGW-C+SMF FQDN Notification from HSS to UDM. The diagram involves three lifelines: UDM, HSS, and MME/AAA. The sequence of messages is: 0. S6a-PUR/PUA SWx-SAR/SAA (dashed arrow from MME/AAA to HSS); 1. Nudm_SDM_Unsubscribe (solid arrow from HSS to UDM); 2. Nudm_SDM_Unsubscribe Response (solid arrow from UDM to HSS).](aa9441a5971655a79987d70fc551b26a_img.jpg) + +Sequence diagram showing the unsubscribe of PGW-C+SMF FQDN Notification from HSS to UDM. The diagram involves three lifelines: UDM, HSS, and MME/AAA. The sequence of messages is: 0. S6a-PUR/PUA SWx-SAR/SAA (dashed arrow from MME/AAA to HSS); 1. Nudm\_SDM\_Unsubscribe (solid arrow from HSS to UDM); 2. Nudm\_SDM\_Unsubscribe Response (solid arrow from UDM to HSS). + +**Figure 5.3.4-3: Unsubscribe of PGW-C+SMF FQDN Notification from HSS to UDM** + +0. The HSS checks the conditions to unsubscribe the notification of the UE context in SMF data or the Intersystem continuity context from the UDM, when the UE's 3GPP access or Non-3GPP access registration in EPC is not + +valid. For example, when the MME performs purge UE procedure, or the AAA performs UE deregistration towards the HSS, or the registration of the user in EPC is cancelled due to mobility from EPC to 5GC. + +1. The HSS unsubscribes to be notified using Nudm\_SDM\_Unsubscribe service operation towards the UDM. +2. The UDM responds to the HSS. + +When the UE is connected to EPC, the MME stores in HSS the PGW-C+SMF FQDN for S5/S8 interface via S6a reference point. When the UE is connected to EPC via an ePDG, and the S6b reference point is deployed between the PGW-C+SMF and AAA, the AAA stores in HSS the PGW-C+SMF FQDN for S5/S8 interface via SWx reference point. + +NOTE: When S6b is not deployed between the PGW-C+SMF and AAA, the registration and de-registration of the PDN GW address is performed in the UDM using the N10 interface instead. In this case, for interworking between EPC/ePDG and 5GS the UDM is not required to contact the HSS to fetch the PDN GW address. + +During mobility from EPC or EPC/ePDG to 5GC, or mobility from EPC to 5GC-N3IWF, the UDM uses the Nhss\_SDM\_Get service operation to retrieve the PGW-C+SMF FQDN for S5/S8 interface from HSS and subscribes to be notified using Nhss\_SDM\_Subscribe when the data requested is modified. + +Figure 5.3.4-4 shows the interaction between the HSS and the UDM in an interworking scenario when the UE moves from EPC or EPC/ePDG to 5GC. + +![Sequence diagram illustrating PDU session continuity during mobility from EPC/ePDG to 5GC. The diagram shows interactions between AMF, UDM, HSS, and MME/AAA. The sequence starts with the AMF sending a Nudm_UECM_Registration to the UDM. The UDM then sends a Nudm_SDM_Get Request to the HSS via the Nhss_SDM_Get Request. The HSS responds with Nhss_SDM_Get Response, which the UDM relays as Nudm_SDM_Get Response to the AMF. Next, the AMF sends a Nudm_SDM_Subscribe to the UDM, which in turn sends an Nhss_SDM_Subscribe to the HSS. The HSS responds with Nhss_SDM_Subscribe Response, which the UDM relays as Nudm_SDM_Subscribe Response to the AMF. A separate interaction is shown where the MME/AAA sends an S6a-ULR/ULA or SWx-SAR/SAA message to the HSS.](04f51626e2e10a16e3eb2c4b33cb2742_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant UDM + participant HSS + participant MME/AAA + + MME/AAA->>HSS: 0. S6a-ULR/ULA / SWx-SAR/SAA + AMF->>UDM: 1. Nudm_UECM_Registration + AMF->>UDM: 2. Nudm_SDM_Get Request + UDM->>HSS: 3. Nhss_SDM_Get Request + HSS-->>UDM: 4. Nhss_SDM_Get Response + UDM-->>AMF: 5. Nudm_SDM_Get Response + AMF->>UDM: 6. Nudm_SDM_Subscribe + UDM->>HSS: 7. Nhss_SDM_Subscribe + HSS-->>UDM: 8. Nhss_SDM_Subscribe Response + UDM-->>AMF: 9. Nudm_SDM_Subscribe Response + +``` + +Sequence diagram illustrating PDU session continuity during mobility from EPC/ePDG to 5GC. The diagram shows interactions between AMF, UDM, HSS, and MME/AAA. The sequence starts with the AMF sending a Nudm\_UECM\_Registration to the UDM. The UDM then sends a Nudm\_SDM\_Get Request to the HSS via the Nhss\_SDM\_Get Request. The HSS responds with Nhss\_SDM\_Get Response, which the UDM relays as Nudm\_SDM\_Get Response to the AMF. Next, the AMF sends a Nudm\_SDM\_Subscribe to the UDM, which in turn sends an Nhss\_SDM\_Subscribe to the HSS. The HSS responds with Nhss\_SDM\_Subscribe Response, which the UDM relays as Nudm\_SDM\_Subscribe Response to the AMF. A separate interaction is shown where the MME/AAA sends an S6a-ULR/ULA or SWx-SAR/SAA message to the HSS. + +Figure 5.3.4-4: PDU session continuity during mobility from EPC/ePDG to 5GC + +0. While the UE is connected to the EPC or EPC/ePDG, the MME or the AAA informs the HSS of the PGW-C+SMF address and associated APN. + +1. UE moves to 5G coverage, the AMF registers with the UDM using Nudm\_UECM\_Registration for 3GPP access. + +The UDM performs steps 3 and 4 in clause 5.3.3. + +2. The AMF retrieves the Access and Mobility Subscription data, SMF Selection Subscription data and UE context in SMF data using Nudm\_SDM\_Get. +3. If the subscription information related to the SUPI includes subscribed DNNs that support interworking with EPS, then the UDM uses the Nhss\_SDM\_Get service operation to fetch the PGW-C+SMF information. The UDM includes the user's IMSI derived from SUPI. +4. The HSS responds to the UDM. +5. The UDM includes the PGW-C+SMF address associated with subscribed DNNs that support interworking with EPS, if any, as UE context in SMF data in Nudm\_SDM\_Get\_Response. +6. After a successful response is received, the AMF subscribes to be notified when the data requested is modified using Nudm\_SDM\_Subscribe service operation. +7. If the UE context in SMF data is subscribed to be notified, the UDM subscribes towards the HSS (if not already subscribed, for the same UE) to be notified when the PGW-C+SMF information is modified using Nhss\_SDM\_Subscribe service operation. +8. The HSS responds to the UDM. +9. The UDM responds to the AMF. + +Figure 5.3.4-5 shows the interaction between the HSS and the UDM when the UDM receives notification from the HSS when the data requested is modified. + +![Sequence diagram showing the notification of PGW-C+SMF FQDN from HSS to UDM. The diagram involves four lifelines: AMF, UDM, HSS, and MME/AAA. The sequence of messages is: 0. S6a-NOR/NOA (MME/AAA to HSS), SWx-SAR/SAA (HSS to MME/AAA); 1. Nhss_SDM_Notification (HSS to UDM); 2. Nhss_SDM_Notification Response (UDM to HSS); 3. Nudm_SDM_Notification (UDM to AMF); 4. Nudm_SDM_Notification Response (AMF to UDM).](e636d7ccca0ad14c6b95201404324823_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant UDM + participant HSS + participant MME/AAA + Note right of MME/AAA: 0. S6a-NOR/NOA +SWx-SAR/SAA + HSS->>UDM: 1. Nhss_SDM_Notification + UDM-->>HSS: 2. Nhss_SDM_Notification Response + UDM-->>AMF: 3. Nudm_SDM_Notification + AMF-->>UDM: 4. Nudm_SDM_Notification Response + +``` + +Sequence diagram showing the notification of PGW-C+SMF FQDN from HSS to UDM. The diagram involves four lifelines: AMF, UDM, HSS, and MME/AAA. The sequence of messages is: 0. S6a-NOR/NOA (MME/AAA to HSS), SWx-SAR/SAA (HSS to MME/AAA); 1. Nhss\_SDM\_Notification (HSS to UDM); 2. Nhss\_SDM\_Notification Response (UDM to HSS); 3. Nudm\_SDM\_Notification (UDM to AMF); 4. Nudm\_SDM\_Notification Response (AMF to UDM). + +**Figure 5.3.4-5: Notification of PGW-C+SMF FQDN from HSS to UDM** + +0. The MME or the AAA may add or update the association between APN and PGW-C+SMF FQDN stored in the HSS. +1. If the HSS finds the association between APN and PGW-C+SMF FQDN is changed, and the active subscription from the UDM exists for the UE to be notified on the change of the data requested, then the HSS uses the Nhss\_SDM\_Notification service operation to notify the UDM. +2. The UDM responds to the HSS. +- 3 - 4. If the UDM finds the association between DNN and PGW-C+SMF FQDN is changed, and the active subscription from the AMF exists for the UE to be notified on the change of the UE context in SMF data, then the UDM notifies the AMF using the Nudm\_SDM\_Notification service operation. + +Figure 5.3.4-6 shows the interaction between the HSS and the UDM when the UDM unsubscribes from the HSS to be notified when the data requested is modified. + +![Sequence diagram showing the interaction between AMF, UDM, HSS, and MME/AAA for unsubscribing from PGW-C+SMF FQDN notification.](a3472689858b068ef469213682965325_img.jpg) + +``` +sequenceDiagram + participant AMF + participant UDM + participant HSS + participant MME/AAA + Note left of AMF: 1. Nudm_SDM_Unsubscribe + AMF->>UDM: 1. Nudm_SDM_Unsubscribe + Note left of UDM: 2. Nudm_SDM_Unsubscribe Response + UDM-->>AMF: 2. Nudm_SDM_Unsubscribe Response + Note left of UDM: 3. Nhss_SDM_Unsubscribe + UDM->>HSS: 3. Nhss_SDM_Unsubscribe + Note left of HSS: 4. Nhss_SDM_Unsubscribe Response + HSS-->>UDM: 4. Nhss_SDM_Unsubscribe Response +``` + +The diagram illustrates a sequence of four messages between four network functions: AMF, UDM, HSS, and MME/AAA. The sequence starts with the AMF sending a 'Nudm\_SDM\_Unsubscribe' message to the UDM. The UDM responds with a 'Nudm\_SDM\_Unsubscribe Response' message. Next, the UDM sends an 'Nhss\_SDM\_Unsubscribe' message to the HSS. The HSS responds with an 'Nhss\_SDM\_Unsubscribe Response' message. The MME/AAA is shown as a participant but does not send or receive any messages in this sequence. + +Sequence diagram showing the interaction between AMF, UDM, HSS, and MME/AAA for unsubscribing from PGW-C+SMF FQDN notification. + +**Figure 5.3.4-6: Unsubscribe of PGW-C+SMF FQDN Notification from UDM to HSS** + +- 1 - 2. The AMF unsubscribes to be notified using Nudm\_SDM\_Unsubscribe service operation. +3. If the UE context in SMF data is unsubscribed, and no other AMF has subscribed to the same data (UE context in SMF) for the same UE, the UDM unsubscribes towards the HSS to be notified when the PGW-C+SMF information is modified using Nhss\_SDM\_Unsubscribe service operation. +4. The HSS responds to the UDM. + +## 5.4 Scenarios of Interworking with IMS + +### 5.4.1 T-ADS + +Figure 5.4.1-1 shows the scenario where the HSS receives a T-ADS request from the AS for a subscriber who has a 5GC subscription. + +![Sequence diagram for T-ADS request for 5G subscriber. Lifelines: AMF, 5GS-UDR, UDM, HSS, EPS-UDR, AS. The HSS receives a request from the AS, reads data from the EPS-UDR, performs T-ADS info retrieval in the EPC, sends a request to the UDM, which queries the 5GS-UDR and returns info to the AMF, which then returns it to the UDM, which finally returns it to the HSS, which sends the response to the AS.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +sequenceDiagram + participant AS + participant EPS-UDR + participant HSS + participant UDM + participant 5GS-UDR + participant AMF + + Note right of HSS: 3. perform T-ADS info retrieval in EPC + + AS->>HSS: 1. Sh/Nhss – T-ADS Request + HSS->>EPS-UDR: 2. Read + HSS->>UDM: 4. Nudm_MT_ProvideDomainSelectionInfo Request + UDM->>5GS-UDR: 5. Nudr_DM_Query + UDM->>AMF: 6. Namf_MT_ProvideDomainSelectionInfo + AMF->>UDM: 7. Namf_MT_ProvideDomainSelectionInfo resp + UDM->>HSS: 8. Nudm_MT_ProvideDomainSelectionInfo Resp + HSS->>AS: 9. Sh/Nhss – T-ADS Response + +``` + +Sequence diagram for T-ADS request for 5G subscriber. Lifelines: AMF, 5GS-UDR, UDM, HSS, EPS-UDR, AS. The HSS receives a request from the AS, reads data from the EPS-UDR, performs T-ADS info retrieval in the EPC, sends a request to the UDM, which queries the 5GS-UDR and returns info to the AMF, which then returns it to the UDM, which finally returns it to the HSS, which sends the response to the AS. + +**Figure 5.4.1-1: T-ADS request for 5G subscriber** + +1. The HSS receives a T-ADS request from the AS. The request includes the user's IMPU or MSISDN and optionally the user's IMPI. + +NOTE: An SBA capable IMS-AS makes use of Nhss\_ImS SDM service to interact with the HSS for this operation as defined in 3GPP TS 23.228 [7]. Otherwise the IMS-AS makes use of Diameter Sh-UDR/UDA command. + +2. If the EPS-UDR is used, the HSS reads subscription data from the EPS-UDR. The HSS, retrieves the user's IMSI associated with the user's identifiers received in step 1. The subscription data may contain an indication that the user has a 5GC subscription. +3. The HSS performs T-ADS info retrieval in the EPC. This may include contacting the MME and/or SGSN. +4. If the HSS detects in step 2 that the user has a 5GC subscription and unless the user is known not to be registered in 5GC (e.g. in case the user is registered in EPC and the HPLMN is working in single registration mode with N26), the HSS uses the Nudm\_MT\_ProvideDomainSelection service operation to retrieve T-ADS information from the UDM. The HSS includes the user's IMSI associated with the user's identifiers received in step 1 as the SUPI in this request. +5. The UDM reads data from the 5GS-UDR to see whether the registered AMF(s) support IMS voice over PS. +- 6-7. If support/non-support of IMS voice is not homogeneous for the User in the AMF for 3GPP access, the UDM retrieves domain selection information from the AMF. +8. The UDM provides the 5G domain selection info to the HSS. + +- The HSS combines the 5G domain selection info with the EPS domain selection info from step 3 and sends the result to the AS. + +### 5.4.2 P-CSCF Restoration + +Figure 5.4.2-1 shows the scenario where the HSS receives a P-CSCF restoration indication from the S-CSCF for a subscriber who has a 5GC subscription. + +![Sequence diagram for P-CSCF Restoration for 5G subscriber. Lifelines: AMF/SMF, 5GS-UDR, UDM, HSS, EPS-UDR, S-CSCF. The sequence shows the HSS receiving a request from the S-CSCF, reading data from the EPS-UDR, sending a trigger request to the UDM, querying the 5GS-UDR, receiving a response from the UDM, sending a notification to the AMF/SMF, and receiving a response from the AMF/SMF. A box indicates 'perform P_CSCF restoration in EPC' between steps 3 and 4.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) + +``` + +sequenceDiagram + participant S-CSCF + participant HSS + participant EPS-UDR + participant UDM + participant 5GS-UDR + participant AMF/SMF + + Note right of HSS: perform P_CSCF restoration in EPC + + S-CSCF->>HSS: 1. Cx/Nhss - P-CSCF Restoration Request + HSS->>EPS-UDR: 2. Read + HSS->>S-CSCF: 3. Cx/Nhss - P-CSCF Restoration Response + HSS->>UDM: 5. Nudm_UECM_P-CscfRestorationTrigger Req + UDM->>5GS-UDR: 6. Nudr_DM_Query + 5GS-UDR->>UDM: 7. Nudm_UECM_P-CscfRestorationTrigger Resp + UDM->>AMF/SMF: 8. Nudm_UECM_P-CscfRestorationNotification + AMF/SMF->>UDM: 9. Nudm_UECM_P-CscfRestorationNotif resp + +``` + +Sequence diagram for P-CSCF Restoration for 5G subscriber. Lifelines: AMF/SMF, 5GS-UDR, UDM, HSS, EPS-UDR, S-CSCF. The sequence shows the HSS receiving a request from the S-CSCF, reading data from the EPS-UDR, sending a trigger request to the UDM, querying the 5GS-UDR, receiving a response from the UDM, sending a notification to the AMF/SMF, and receiving a response from the AMF/SMF. A box indicates 'perform P\_CSCF restoration in EPC' between steps 3 and 4. + +**Figure 5.4.2-1: P-CSCF Restoration for 5G subscriber** + +- The HSS receives a P-CSCF Restoration indication from the S-CSCF. The request includes the user's IMPU and IMPI. + +NOTE: An SBA capable S-CSCF makes use of Nhss\_ImSUECM service to interact with the HSS for this operation as defined in 3GPP TS 23.228 [7]. Otherwise the S-CSCF makes use of Diameter Cx-SAR/SAA command. + +- If the EPS-UDR is used, the HSS reads subscription data from the EPS-UDR. The HSS, retrieves the user's IMSI associated with the user's identifiers received in step 1. The subscription data may contain an indication that the user has a 5GC subscription. +- The HSS acknowledges receipt of the request and performs P-CSCF restoration in the EPC. For details see 3GPP TS 23.380 [4] clause 5.4.2.1. + +5. If the HSS detects in step 2 that the user has a 5GC subscription and unless the user is known not to be registered in 5GC (e.g. in case the user is registered in EPC and the HPLMN is working in single registration mode with N26), the HSS uses the Nudm\_UECM\_P-CscfRestorationTrigger service operation to trigger P-CSCF restoration in 5GC. See also 3GPP TS 23.380 [4] clause 5.8.4. The HSS includes the user's IMSI associated with the user's identifiers received in step 1 as the SUPI in this request +6. The UDM reads data from the 5GS-UDR to see which NFs have subscribed to P-CSCF Restoration Notifications (implicitly during registration). +7. The UDM acknowledges receipt of Nudm\_UECM\_PCscfRestorationTrigger to the HSS. +- 8-9. The UDM sends a notification to one of the subscribed NFs (either the AMF or the SMF). + +### 5.4.3 Network Provided Location Information Request + +Figure 5.4.3-1 shows the scenario where the HSS receives a Location Information retrieval request from the IMS-AS for a subscriber who has a 5GC subscription. + +![Sequence diagram for Figure 5.4.3-1: Location Information retrieval request for 5G subscriber. The diagram shows interactions between AMF, 5GS-UDR, UDM, HSS, EPS-UDR, and IMS-AS. The HSS receives a request from the IMS-AS, reads data from the EPS-UDR, performs location info retrieval in the EPC, sends a Nudm_MT_ProvideLocationInfo Request to the UDM, which then queries the 5GS-UDR. The UDM sends a response to the HSS, which then sends a response to the IMS-AS. The UDM also sends a notification to the AMF.](171115f072e42b379238ed0dd438e9d7_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant 5GS-UDR + participant UDM + participant HSS + participant EPS-UDR + participant IMS-AS + + Note right of HSS: Ud + IMS-AS->>HSS: 1. Sh/Nhss – NPLI Request + HSS->>EPS-UDR: 2. Read + Note right of HSS: 3. perform Location Info Retrieval in EPC + HSS->>UDM: 4. Nudm_MT_ProvideLocationInfo Request + UDM->>5GS-UDR: 5. Nudr_DM_Query + UDM->>AMF: 6. Namf_Location_ProvideLocationInfo Request + AMF->>UDM: 7. Namf_Location_ProvideLocationInfo Resp + UDM->>HSS: 8. Nudm_MT_ProvideLocationInfo Resp + HSS->>IMS-AS: 9. Sh/Nhss – NPLI Response + +``` + +Sequence diagram for Figure 5.4.3-1: Location Information retrieval request for 5G subscriber. The diagram shows interactions between AMF, 5GS-UDR, UDM, HSS, EPS-UDR, and IMS-AS. The HSS receives a request from the IMS-AS, reads data from the EPS-UDR, performs location info retrieval in the EPC, sends a Nudm\_MT\_ProvideLocationInfo Request to the UDM, which then queries the 5GS-UDR. The UDM sends a response to the HSS, which then sends a response to the IMS-AS. The UDM also sends a notification to the AMF. + +**Figure 5.4.3-1: Location Information retrieval request for 5G subscriber** + +1. The HSS receives a Location Information retrieval request (requested nodes includes AMF) from the IMS-AS. + +NOTE: An SBA capable IMS-AS makes use of Nhss\_ImS SDM service to interact with the HSS for this operation as defined in 3GPP TS 23.228 [7]. Otherwise the IMS-AS makes use of Diameter Sh-UDR/UDA command. + +2. The HSS reads subscription data from the EPS-UDR. +3. The HSS performs Location Information Retrieval from other nodes if so requested. This may include contacting the MME and/or SGSN. +4. If the HSS detects in step 2 that the user has a 5GC subscription and unless the user is known not to be registered in 5GC, the HSS uses the Nudm\_MT\_ProvideLocationInfo service operation to retrieve 5GS Location Information. The service request includes indicators for Current Location, Serving Node Indication, Local Time Zone Indication, and RAT-Type requested as has been received in step 1. +5. The UDM reads data from the 5GS-UDR to get the AMF and SMSF for 3GPP Access Registration Information. If the Serving Node Indication was received in step 4, steps 6-7 shall be skipped. +- 6-7. The UDM retrieves location information from the AMF (for 3GPP access) by means of the Namf\_Location\_ProvideLocationInfo service operation . +8. The UDM provides the 5GS location information info to the HSS. +9. The HSS provides the requested location information to the IMS-AS. + +### 5.4.4 User State Retrieval + +Figure 5.4.4-1 shows the scenario where the HSS receives a PS User State retrieval request from the IMS-AS for a subscriber who has a 5GC subscription. + +![Sequence diagram for PS User State retrieval request for 5G subscriber. Lifelines: AMF, 5GS-UDR, UDM, HSS, EPS-UDR, IMS-AS. The sequence starts with the IMS-AS sending a Sh/Nhss - PS User State Request to the HSS. The HSS sends a Read request to the EPS-UDR. A box labeled '3. perform PS User State Retrieval in EPC' is shown. The HSS then sends a Nudm_MT_ProvideUserState Request to the UDM. The UDM sends a Nudr_DM_Query to the 5GS-UDR. The UDM then sends a Namf_EventExposure Subscribe to the AMF. The AMF responds with a Namf_EventExposure Subscribe resp. The UDM sends a Nudm_MT_ProvideUserState Resp to the HSS. Finally, the HSS sends a Sh/Nhss - PS User State Response to the IMS-AS.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant IMS-AS + participant HSS + participant EPS-UDR + participant UDM + participant 5GS-UDR + participant AMF + + Note right of HSS: 3. perform PS User State Retrieval in EPC + + IMS-AS->>HSS: 1. Sh/Nhss – PS User State Request + HSS->>EPS-UDR: 2. Read + Note right of HSS: 3. perform PS User State Retrieval in EPC + HSS->>UDM: 4. Nudm_MT_ProvideUserState Request + UDM->>5GS-UDR: 5. Nudr_DM_Query + UDM->>AMF: 6. Namf_EventExposure Subscribe + AMF->>UDM: 7. Namf_EventExposure Subscribe resp + UDM->>HSS: 8. Nudm_MT_ProvideUserState Resp + HSS->>IMS-AS: 9. Sh/Nhss – PS User State Response + +``` + +Sequence diagram for PS User State retrieval request for 5G subscriber. Lifelines: AMF, 5GS-UDR, UDM, HSS, EPS-UDR, IMS-AS. The sequence starts with the IMS-AS sending a Sh/Nhss - PS User State Request to the HSS. The HSS sends a Read request to the EPS-UDR. A box labeled '3. perform PS User State Retrieval in EPC' is shown. The HSS then sends a Nudm\_MT\_ProvideUserState Request to the UDM. The UDM sends a Nudr\_DM\_Query to the 5GS-UDR. The UDM then sends a Namf\_EventExposure Subscribe to the AMF. The AMF responds with a Namf\_EventExposure Subscribe resp. The UDM sends a Nudm\_MT\_ProvideUserState Resp to the HSS. Finally, the HSS sends a Sh/Nhss - PS User State Response to the IMS-AS. + +**Figure 5.4.4-1: PS User State retrieval request for 5G subscriber** + +1. The HSS receives a PS User State retrieval request (requested nodes includes AMF) from the IMS-AS. + +NOTE 1: An SBA capable IMS-AS makes use of Nhss\_ImsSDM service to interact with the HSS for this operation as defined in 3GPP TS 23.228 [7]. Otherwise the IMS-AS makes use of Diameter Sh-UDR/UDA command. + +2. The HSS reads subscription data from the EPS-UDR. +3. The HSS performs PS User State Retrieval from other nodes if so requested. This may include contacting the MME and/or SGSN. +4. If the request includes AMF as requested node and if the HSS detects in step 2 that the user has a 5GC subscription and unless the user is known not to be registered in 5GC, the HSS uses the Nudm\_MT\_ProvideUserState service operation to retrieve the 5GS User State. Otherwise, continue with step 9. +5. The UDM reads data from the 5GS-UDR to get the AMF for 3GPP Access Registration Information. +- 6-7. The UDM retrieves the user state from the AMF (for 3GPP access) by means of the Namf\_EventExposure Subscribe service operation (one time immediate report requested). +8. The UDM provides the 5GS PS User State to the HSS. +9. The HSS provides the requested user state to the IMS-AS. + +NOTE 2: If the IMS-AS supports 5G SBI it may make use of the Nhss-ims service instead of Sh. + +### 5.4.5 UE Reachability + +Figure 5.4.5-1 shows the scenario where the HSS receives a Subscription to notification request for UE-reachability from the IMS-AS for a subscriber who has a 5GC subscription. + +![Sequence diagram for Figure 5.4.5-1: Subscription to UE reachability for 5G subscriber. The diagram shows interactions between AMF, 5GS-UDR, UDM, HSS, EPS-UDR, and IMS-AS. The process involves the HSS receiving a subscription request from the IMS-AS, reading data from the EPS-UDR, performing UE reachability subscription in the EPC, sending a Nudm_EE_Subscribe Request to the UDM, which then queries the 5GS-UDR and subscribes to the AMF. Finally, the HSS sends a response to the IMS-AS and updates the EPS-UDR.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +``` + +sequenceDiagram + participant IMS-AS + participant EPS-UDR + participant HSS + participant UDM + participant 5GS-UDR + participant AMF + + Note right of HSS: Ud + IMS-AS->>HSS: 1. Sh/Nhss – Subscription to UE Reachability Notification Request + HSS->>EPS-UDR: 2. Read + Note right of HSS: 3. perform UE reachability subscription in EPC + HSS->>UDM: 4. Nudm_EE_Subscribe Request + UDM->>5GS-UDR: 5. Nudr_DM_Query + UDM->>AMF: 6. Namf_EventExposure_Subscribe Request + AMF->>UDM: 7. Namf_EventExposure_Subscribe Resp + UDM->>5GS-UDR: 8. Nudr_DM_Update + UDM->>HSS: 9. Nudm_EE_Subscribe Resp + HSS->>IMS-AS: 10. Sh/Nhss – Subscription to UE Reachability Notification Response + HSS->>EPS-UDR: 11. Update + +``` + +Sequence diagram for Figure 5.4.5-1: Subscription to UE reachability for 5G subscriber. The diagram shows interactions between AMF, 5GS-UDR, UDM, HSS, EPS-UDR, and IMS-AS. The process involves the HSS receiving a subscription request from the IMS-AS, reading data from the EPS-UDR, performing UE reachability subscription in the EPC, sending a Nudm\_EE\_Subscribe Request to the UDM, which then queries the 5GS-UDR and subscribes to the AMF. Finally, the HSS sends a response to the IMS-AS and updates the EPS-UDR. + +**Figure 5.4.5-1: Subscription to UE reachability for 5G subscriber** + +1. The HSS receives a Subscribe request for UE reachability for IP from the IMS-AS. + +NOTE: An SBA capable IMS-AS makes use of Nhss\_ImsSDM service to interact with the HSS for this operation as defined in 3GPP TS 23.228 [7]. Otherwise the IMS-AS makes use of Diameter Sh-SNR/SNA command. + +2. The HSS reads subscription data from the EPS-UDR. +3. The HSS sets the UE Reachability flags for EPC and if the UE is registered in EPC contacts the registered MME and SGSN to get notified when the UE becomes reachable. +4. If the HSS detects in step 2 that the user has a 5GC subscription, the HSS uses the Nudm\_EventExposure\_Subscribe service operation (one time immediate report requested) to get notified when the UDM detects UE reachability for SMS over IP. Otherwise, continue with step 10. +5. The UDM sets the URRP-AMF flag in the 5GS-UDR and reads data from the 5GS-UDR to get the AMF for 3GPP Access Registration Information and the AMF for non-3GPP Access Registration Information if any. +- 6-7. [Conditional] If an AMF is registered in UDM for the target UE and the UDM has not already subscribed in AMF due to a previous subscription from a different NF, the UDM subscribes to UE reachability notifications at + +the registered AMFs by means of the Namf\_EventExposure\_Subscribe service operation (see 3GPP TS 23.502 [5]). + +8. The UDM updates the 5GS-UDR with the EE-Subscription for the HSS. +9. The UDM acknowledges the EE Subscription to the HSS. +10. The HSS acknowledges the Sh subscription to the IMS-AS. +11. The HSS updates the EPS-UDR with the Sh subscription for the IMS-AS. + +Figure 5.4.5-2 shows the scenario where the UDM detects UE reachability for SMS over IP and notifies the HSS that has previously subscribed. + +![Sequence diagram for UE reachability notification for 5G subscriber. Lifelines: AMF, 5GS-UDR, UDM, HSS, EPS-UDR, IMS-AS. The sequence shows the UDM receiving a notification from the AMF, querying the 5GS-UDR, and then notifying the HSS. The HSS reads from the EPS-UDR and notifies the IMS-AS. The UDM updates the 5GS-UDR, and the HSS updates the EPS-UDR.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant 5GS-UDR + participant UDM + participant HSS + participant EPS-UDR + participant IMS-AS + + AMF->>UDM: 1. Namf_EventExposure_Notify or Nudm_UECM_Registration + UDM->>5GS-UDR: 2. Nudr_DM_Query + 5GS-UDR-->>UDM: 3. response + UDM->>HSS: 4. Nudm_EE_Notify Request + HSS->>EPS-UDR: 5. Read + EPS-UDR-->>HSS: 6. Nudm_EE_Notify Resp + UDM->>5GS-UDR: 7. Nudr_DM_Update + HSS->>IMS-AS: 8. Sh/Nhss – UE Reachability Notification + IMS-AS-->>HSS: 9. Sh/Nhss – UE Reachability Notification Answer + HSS->>EPS-UDR: 10. Update + +``` + +Sequence diagram for UE reachability notification for 5G subscriber. Lifelines: AMF, 5GS-UDR, UDM, HSS, EPS-UDR, IMS-AS. The sequence shows the UDM receiving a notification from the AMF, querying the 5GS-UDR, and then notifying the HSS. The HSS reads from the EPS-UDR and notifies the IMS-AS. The UDM updates the 5GS-UDR, and the HSS updates the EPS-UDR. + +**Figure 5.4.5-2: UE reachability notification for 5G subscriber** + +1. The UDM receives a Notification or Registration from the AMF. +2. The UDM reads subscription data from the 5GS-UDR. +3. The UDM acknowledges step 1 towards the AMF. If an old AMF is registered in the UDM, the UDM sends a Nudm\_UECM\_DeregistrationNotification service operation to the old AMF. +4. The UDM notifies the HSS (and any other NF that has subscribed) about the reachability of the UE. +5. The HSS reads data from the EPS-UDR to see whether an IMS-AS has subscribed do reachability notification. +6. The HSS acknowledges step 4. +7. The UDM updates the 5GS-UDR to delete the EE-Subscription(s). +8. The HSS notifies the IMS-AS about UE reachability for IP. + +NOTE: An SBA capable IMS-AS receives the notification from HSS using the Nhss\_ImSDM service as defined in 3GPP TS 23.228 [7]. Otherwise the IMS-AS receives the notification via a Diameter Sh-PNR/PNA command. + +9. The IMS-AS acknowledges step 8. + +10. The HSS updates the EPS-UDR to delete the IMS-AS's subscription. + +### 5.4.6 IMEI Retrieval + +A pre-requisite for the retrieval of the IMEI when requested by an IMS-AS is that the IMEI for a given UE stored in HSS and UDM is always synchronized. This is, when the HSS detects that the IMEI for a UE changes (e.g. during an Update Location in EPS), the HSS informs the UDM about the IMEI change which stores the new IMEI accordingly. Similarly, when UDM detects that the IMEI changes, the UDM informs the HSS about the IMEI change which stores the new IMEI accordingly. + +This allows that the retrieval of the IMEI for a given UE requested by an IMS-AS from HSS via Sh can be executed locally by HSS without the need of additional interworking between the HSS and the UDM + +Figure 5.4.6-1 shows the scenario where the HSS receives an IMEI retrieval request from the IMS-AS for a subscriber who has a 5GC subscription. + +![Sequence diagram for IMEI retrieval request for 5G subscriber. Lifelines: AMF, UDM, HSS, MME, IMS-AS. The diagram shows two main synchronization paths: one where HSS detects an IMEI change from MME and updates UDM, and another where UDM detects a PEI change from AMF and updates HSS. Finally, IMS-AS requests the IMEI from HSS via Sh/Nhss.](f2ea0f64a770b22b902820457d262265_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant UDM + participant HSS + participant MME + participant IMS-AS + + Note right of HSS: 1. S6a ULR/ULA, NOR/NOA + HSS->>MME: 1. S6a ULR/ULA, NOR/NOA + Note right of HSS: 2. HSS detects IMEI in request is different from IMEI previously stored in EPS-UDR. HSS stores new IMEI in EPS-UDR + HSS->>UDM: 3. Nudm_UECM_Update + Note right of UDM: 4. UDM stores new PEI/IMEI in 5GS-UDR. + UDM->>AMF: 5. Nudm_UECM Registration/Update + Note right of UDM: 6. UDM detects PEI in request is different from PEI previously stored in 5GS-UDR. UDM stores new PEI in 5GS-UDR + UDM->>HSS: 7. Nhss_UECM_Update + Note right of HSS: 8. HSS stores new IMEI in EPS-UDR. + Note right of IMS-AS: 9. Sh/Nhss – IMEI Request + IMS-AS->>HSS: 9. Sh/Nhss – IMEI Request + Note right of HSS: 10. HSS reads IMEI in EPS-UDR. + HSS->>IMS-AS: 11. Sh/Nhss – IMEI Response + +``` + +Sequence diagram for IMEI retrieval request for 5G subscriber. Lifelines: AMF, UDM, HSS, MME, IMS-AS. The diagram shows two main synchronization paths: one where HSS detects an IMEI change from MME and updates UDM, and another where UDM detects a PEI change from AMF and updates HSS. Finally, IMS-AS requests the IMEI from HSS via Sh/Nhss. + +**Figure 5.4.6-1: IMEI retrieval request for 5G subscriber** + +Steps 1 to 4 are executed when the HSS detects a change in the IMEI for a given UE (IMSI). + +1. The HSS receives a request from the MME including an IMEI for the UE (e.g. Update Location Request or Notify Request). +2. The HSS detects that the IMEI received in the request is different from the previously stored in the EPS-UDR. The HSS stores the new IMEI in the EPS-UDR. +3. The HSS informs the UDM about the new PEI (IMEI) using the Nudm\_UECM\_Update service operation. +4. The UDM stores the new PEI for the UE. + +Steps 5 to 8 are executed when the UDM detects a change in the PEI for a given UE (SUPI). + +5. The UDM receives a request from the AMF including a PEI for the UE (e.g. Nudm\_UECM\_Registration/Update). +6. The UDM detects that the PEI received in the request is different from the previously stored in the 5GS-UDR. The UDM stores the new IMEI in the 5GS-UDR. +7. The UDM informs the HSS about the new IMEI using the Nhss\_UECM\_Update service operation. + +8. The HSS stores the new IMEI for the UE. + +Steps 9 to 11 are executed when the HSS receives an IMEI retrieval request from the IMS-AS for a subscriber who has a 5GC subscription. + +9. The HSS receives a request from IMS-AS to retrieve the IMEI for a UE. +10. The HSS reads the IMEI stored in the EPS-UDR. +11. The HSS replies to the IMS-AS with the users IMEI. Since the IMEI for the UE has been synchronized between HSS and UDM at every IMEI/PEI change event as in steps 1 to 4 or 5 to 8, the HSS can reply to the IMS-AS without any additional interworking with the UDM. + +### 5.4.7 SRVCC: IMS AS obtaining SRVCC data + +Figure 5.4.7-1 shows the scenario where the HSS communicates with the IMS-AS in support of (5G) SRVCC for a subscriber who has a 5GC subscription. An operator shall be able to control whether the interaction between HSS and UDM is performed based on local policy. + +![Sequence diagram showing the interaction between 5GS-UDR, UDM, HSS, EPS-UDR, and IMS-AS for SRVCC data retrieval. The sequence is: 1. IMS-AS sends Sh/Nhss - Pull Request to HSS; 2. HSS sends Read to EPS-UDR; 3. HSS sends Nudm_MT_Provide5GSRVCCInfo to UDM; 4. UDM sends Nudr_DM_Query to 5GS-UDR; 5. UDM sends Nudm_MT_Provide5GSRVCCInfo Resp to HSS; 6. HSS sends Sh/Nhss - Pull Response to IMS-AS.](5b6e139e89c6ce90107ea7d7d77620a0_img.jpg) + +``` + +sequenceDiagram + participant IMS-AS + participant HSS + participant EPS-UDR + participant UDM + participant 5GS-UDR + + IMS-AS->>HSS: 1. Sh/Nhss - Pull Request + HSS->>EPS-UDR: 2. Read + HSS->>UDM: 3. Nudm_MT_Provide5GSRVCCInfo + UDM->>5GS-UDR: 4. Nudr_DM_Query + 5GS-UDR-->>UDM: 5. Nudm_MT_Provide5GSRVCCInfo Resp + UDM-->>HSS: 5. Nudm_MT_Provide5GSRVCCInfo Resp + HSS->>IMS-AS: 6. Sh/Nhss - Pull Response + +``` + +Sequence diagram showing the interaction between 5GS-UDR, UDM, HSS, EPS-UDR, and IMS-AS for SRVCC data retrieval. The sequence is: 1. IMS-AS sends Sh/Nhss - Pull Request to HSS; 2. HSS sends Read to EPS-UDR; 3. HSS sends Nudm\_MT\_Provide5GSRVCCInfo to UDM; 4. UDM sends Nudr\_DM\_Query to 5GS-UDR; 5. UDM sends Nudm\_MT\_Provide5GSRVCCInfo Resp to HSS; 6. HSS sends Sh/Nhss - Pull Response to IMS-AS. + +Figure 5.4.7-1: IMS AS obtaining data related to (5G) SRVCC and updating STN-SR + +1. As described in 3GPP TS 23.237 [13], the IMS-AS sends Sh-Pull message to the UDM/HSS in order to know the SRVCC capability indicated by the UE in the EPS, and to retrieve the STN-SR stored in the UDM/HSS. +2. The HSS reads STN-SR and UE SRVCC Capability data from the EPS-UDR. The HSS reads the C-MSISDN bound to the IMS Private User Identity. +3. The HSS, based on operator policy, may query UDM to retrieve SRVCC parameters. The HSS uses the Nudm\_MT\_Provide5GSRVCCInfo service operation to retrieve the STN-SR and the UE SRVCC Capability indicated by the UE in the 5GS (see 3GPP TS 23.008 [14]). +4. The UDM reads the STN-SR and this UE SRVCC Capability data from the 5GS-UDR. +5. The UDM provides the C-MSISDN, STN-SR and UE SRVCC Capability data to the HSS. +6. The HSS provides a single C-MSISDN, a single STN-SR and UE SRVCC Capability data to the IMS-AS, as follows: + - if the C-MSISDN from the HSS and the C-MSISDN from the UDM are empty, the HSS indicates an empty C-MSISDN to the SCC AS. The HSS indicates a non-empty C-MSISDN, otherwise; + - if the STN-SR from the HSS or the STN-SR from the UDM is empty, it indicates the user is not subscribed to (5G) SRVCC. If the HSS and the UDM indicate the user is not subscribed to (5G) SRVCC, the HSS indicates an empty STN-SR to the SCC AS. The HSS indicates a non-empty STN-SR, otherwise. + +### 5.4.8 SRVCC: IMS AS obtaining SRVCC data – HSS using Nudr + +When the HSS receives an S6a-AIR from the MME, it may check (by means of an EPC-UDR query) whether the subscriber has a 5G subscription. If so, the HSS can use of the Nudr\_DM\_Query Get service operation to retrieve the 5G SRVCC subscription data from the 5GS UDR. + +Figure 5.4.8-1 shows the scenario where the HSS communicates with the IMS-AS in support of (5G) SRVCC for a subscriber who has a 5GC subscription. An operator shall be able to control whether the interaction between HSS and 5GS-UDR is performed based on local policy. + +![Sequence diagram for Figure 5.4.8-1: IMS AS obtaining data related to (5G) SRVCC – HSS using the Nudr. The diagram shows four messages: 1. Sh/Nhss – Pull Request from IMS-AS to HSS; 2. Read from HSS to EPS-UDR; 3. Nudr_DM_Query from HSS to 5GS-UDR; 4. Sh/Nhss – Pull Response from HSS to IMS-AS.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +``` + +sequenceDiagram + participant IMS-AS + participant HSS + participant EPS-UDR + participant 5GS-UDR + Note right of HSS: Ud + IMS-AS->>HSS: 1. Sh/Nhss – Pull Request + HSS->>EPS-UDR: 2. Read + HSS->>5GS-UDR: 3. Nudr_DM_Query + HSS->>IMS-AS: 4. Sh/Nhss – Pull Response + +``` + +Sequence diagram for Figure 5.4.8-1: IMS AS obtaining data related to (5G) SRVCC – HSS using the Nudr. The diagram shows four messages: 1. Sh/Nhss – Pull Request from IMS-AS to HSS; 2. Read from HSS to EPS-UDR; 3. Nudr\_DM\_Query from HSS to 5GS-UDR; 4. Sh/Nhss – Pull Response from HSS to IMS-AS. + +**Figure 5.4.8-1: IMS AS obtaining data related to (5G) SRVCC – HSS using the Nudr** + +- As described in 3GPP TS 23.237 [13], the IMS-AS sends Sh-Pull message to the UDM/HSS in order to know the SRVCC capability indicated by the UE in the EPS, and to retrieve the STN-SR stored in the UDM/HSS. +- The HSS reads STN-SR and this UE SRVCC Capability data from the EPS-UDR. The HSS reads the C-MSISDN bound to the IMS Private User Identity. +- The HSS, based on operator policy, may query 5G-UDR to retrieve SRVCC parameters. The HSS uses the Nudr\_DM\_Query service operation to retrieve the STN-SR and the UE SRVCC Capability indicated by the UE in the 5GS (see 3GPP TS 23.008 [14]) from the 5GS-UDR. +- The HSS provides a single C-MSISDN, a single STN-SR and UE SRVCC Capability data to the IMS-AS, as follows: + - if the C-MSISDN from the HSS and the C-MSISDN from the UDM are empty, the HSS indicates an empty C-MSISDN to the SCC AS. The HSS indicates a non-empty C-MSISDN, otherwise; + - if the STN-SR from the HSS or the STN-SR from the UDM is empty, it indicates the user is not subscribed to (5G) SRVCC. If the HSS and the UDM indicate the user is not subscribed to (5G) SRVCC, the HSS indicates an empty STN-SR to the SCC AS. The HSS indicates a non-empty STN-SR, otherwise. + +### 5.4.9 SRVCC: IMS AS updating STN-SR + +Figure 5.4.9-1 shows the scenario where the IMS-AS updates the STN-SR at the HSS. An operator shall be able to control whether the interaction between HSS and UDM is performed based on local policy. + +![Sequence diagram for Figure 5.4.9-1: Updating STN-SR. The diagram shows six messages: 1. Sh/Nhss – Update Request from IMS-AS to HSS; 2. Update from HSS to EPS-UDR; 3. Nudm_PP_Update from HSS to UDM; 4. Nudr_DM_Update from UDM to 5GS-UDR; 5. Nudm_PP_Update Resp from UDM to HSS; 6. Sh/Nhss – Update Response from HSS to IMS-AS.](5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg) + +``` + +sequenceDiagram + participant IMS-AS + participant HSS + participant EPS-UDR + participant UDM + participant 5GS-UDR + Note right of HSS: Ud + IMS-AS->>HSS: 1. Sh/Nhss – Update Request + HSS->>EPS-UDR: 2. Update + HSS->>UDM: 3. Nudm_PP_Update + UDM->>5GS-UDR: 4. Nudr_DM_Update + UDM->>HSS: 5. Nudm_PP_Update Resp + HSS->>IMS-AS: 6. Sh/Nhss – Update Response + +``` + +Sequence diagram for Figure 5.4.9-1: Updating STN-SR. The diagram shows six messages: 1. Sh/Nhss – Update Request from IMS-AS to HSS; 2. Update from HSS to EPS-UDR; 3. Nudm\_PP\_Update from HSS to UDM; 4. Nudr\_DM\_Update from UDM to 5GS-UDR; 5. Nudm\_PP\_Update Resp from UDM to HSS; 6. Sh/Nhss – Update Response from HSS to IMS-AS. + +**Figure 5.4.9-1: Updating STN-SR** + +- As described in 3GPP TS 23.237 [13], the IMS-AS can use Sh-Update to provide the STN-SR received from the ATCF to the UDM/HSS in order to replace the STN-SR at the UDM/HSS. + +2. While this updated STN-SR is a transient value and subject to the user being subscribed to SRVCC, the HSS can update the STN-SR at the EPS-UDR. If the user is subscribed to SRVCC, the HSS updates the STN-SR at the EPS-UDR and at the MME/SGSN (not shown). +3. The HSS, based on operator policy, may update UDM: the HSS updates the STN-SR at the UDM. +4. While this updated STN-SR is a transient value, the UDM can update the STN-SR at the 5GS-UDR using Nudr\_DM\_Update. The UDM updates the STN-SR at the AMF using Nudm\_SDM\_Notification service operation (not shown). +5. The UDM responds to the request to update the STN-SR. +6. The HSS responds by sending Sh-Update Response message to the IMS AS. + +## 5.5 SMS Support + +### 5.5.1 General + +Potential MT-SMS target nodes in the EPS are the MME/MSC and the SGSN registered at the HSS, while in 5GS MT-SMS target nodes are the 3GPP-SMSF and the Non3GPP-SMSF registered at the UDM. For the role of SMS-Router and IP-SM-GW see 3GPP TS 23.040 [12]. + +### 5.5.2 MT-SMS Routing Information Retrieval + +Figure 5.5.2-1 shows the interaction when the SMS-GMSC retrieves routing information from the HSS for MT-SMS delivery. + +![Sequence diagram for SMS Routing Info Retrieval showing interactions between UDM, 5GS-UDR, EPS-UDR, HSS, and SMS-GMSC.](1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg) + +``` + +sequenceDiagram + participant UDM + participant 5GS-UDR + participant EPS-UDR + participant HSS + participant SMS-GMSC + + Note over EPS-UDR, HSS: Ud + SMS-GMSC->>HSS: 1. MAP-SRI_SM or S6c-SRR + HSS->>EPS-UDR: 2. Read + HSS->>UDM: 3. Nudm_UECM_Get + UDM->>5GS-UDR: 4. Nudr_DM_Query + 5GS-UDR->>UDM: 5. Nudr_DM_Query resp. + UDM->>HSS: 6. Nudm_UECM_Get resp. + HSS->>SMS-GMSC: 7. MAP-SRI_SM resp and Inform-SC, or S6c-SRA + HSS->>EPS-UDR: 8. Update + HSS->>UDM: 9. Nudm_EE_Subscribe + UDM->>5GS-UDR: 10. Nudr_DM_Update + UDM->>HSS: 11. Nudm_EE_Subscribe resp. + +``` + +Sequence diagram for SMS Routing Info Retrieval showing interactions between UDM, 5GS-UDR, EPS-UDR, HSS, and SMS-GMSC. + +Figure 5.5.2-1: SMS Routing Info Retrieval + +1. The HSS receives a request for routing information from the SMS-GMSC via MAP or S6c. +2. The HSS queries the EPS-UDR via Ud to read the registered MME/MSC, the registered SGSN, and the UE-not-reachable flags for SMS in MME/MSC, SGSN and UDM. +3. If the UE-not-reachable flag for SMS in UDM is not set and unless the user is known not to be registered in 5GC, the HSS retrieves the registered SMSF addresses for 3GPP and non-3GPP accesses (if any) from the UDM. +- 4-5. The UDM retrieves the requested information from the 5GS-UDR. +6. The UDM forwards the retrieved addresses to the HSS if any. If the UE is not reachable for MT-SMS in 5GS for a given access type (e.g. there is no SMSF registered for the UE or SMSF registration exists but UE is known not to be reachable in 5GS based on URRP flag), the UDM provides a negative response (Absent Subscriber SM) to the HSS. + +If SMS over NAS is not allowed for the user in 5GS based on subscription data, e.g. SMS teleservice is not provisioned or SMS is barred, the UDM indicates in the response to the HSS the corresponding error condition. + +If SMS over NAS is not allowed for the user in 5GS based on subscription data, e.g. SMS teleservice is not provisioned or SMS is barred, the UDM indicates in the response to the HSS the corresponding error condition. + +7. The HSS returns the relevant MT-SMS target node addresses registered in HSS and/or UDM to the SMS-GMSC and the procedure is terminated. + +Otherwise, if there is no MT-SMS target node address registered in HSS nor in UDM, a negative response (Absent Subscriber SM) is sent to the SMS-GMSC and the procedure continues with steps 8 to 11. + +8. The HSS includes the SMSC address to the Message Waiting Data (MWD) stored in the EPS-UDR and informs the SMSC as defined in TS 23.040 [12]. The relevant UE-not-reachable flags are set in the EPS-UDR. + +If SMS is not allowed for the user in 5GS according to subscription data as indicated in step 6, steps 9 to 11 are not executed so that the HSS does not subscribe to notifications about reachability for SMS in the UDM, and the procedure is terminated. + +9. The HSS subscribes in UDM to be notified when the UE becomes reachable for SMS (i.e. when the UE gets in radio contact with the AMF while an SMSF actually is registered, or when an SMSF gets registered) by using the Nudm\_EE\_Subscribe service operation (SUPI, UE Reachability for SMS event) as defined in 3GPP TS 23.502 [5]. +10. The UDM stores the EE-subscription (Reachability for SMS) in the 5G-UDR. +11. The UDM acknowledges the subscription to the HSS. + +### 5.5.3 MT-SMS Delivery Failure + +Figure 5.5.3-1 shows the interaction when the SMS-GMSC sends Report-SM-Delivery-Status to the HSS. + +![Sequence diagram for MT-SMS Delivery Failure. Lifelines: AMFs, UDM, 5GS-UDR, EPS-UDR, HSS, SMS-GMSC. The sequence shows the HSS receiving a delivery status report, reading/updating the EPS-UDR, subscribing to UE reachability at the UDM, checking the 5GS-UDR, and finally subscribing to the AMF.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +sequenceDiagram + participant AMFs + participant UDM + participant 5GS-UDR + participant EPS-UDR + participant HSS + participant SMS-GMSC + + Note right of EPS-UDR: Ud + SMS-GMSC->>HSS: 1. MAP/S6c Report-SM-Delivery-Status + HSS->>EPS-UDR: 2. Read + HSS->>EPS-UDR: 3. Update + EPS-UDR->>HSS: 4. MAP/S6c RSDS response + HSS->>UDM: 5. Nudm_EE_Subscribe + UDM->>5GS-UDR: 6. Nudr_DM_Query + 5GS-UDR->>UDM: 7. Nudr_DM_Query resp. + UDM->>AMFs: 8. Namf_EE_Subscribe + AMFs->>UDM: 9. Namf_EE_subscribe resp. + UDM->>5GS-UDR: 10. Nudr_DM_Update + 5GS-UDR->>UDM: 11. Nudr_DM_Update resp. + UDM->>HSS: 12. Nudm_EE_Subscribe resp. + +``` + +Sequence diagram for MT-SMS Delivery Failure. Lifelines: AMFs, UDM, 5GS-UDR, EPS-UDR, HSS, SMS-GMSC. The sequence shows the HSS receiving a delivery status report, reading/updating the EPS-UDR, subscribing to UE reachability at the UDM, checking the 5GS-UDR, and finally subscribing to the AMF. + +**Figure 5.5.3-1: MT-SMS Delivery Failure** + +1. The HSS receives a Report-SM-Delivery-Status from the SMS-GMSC indicating the MT-SMS target nodes at which MT-SMS delivery was unsuccessful. + +2-3. The HSS reads and updates the Message Waiting Data stored in the EPS-UDR. + +4. The HSS acknowledges the receipt of the delivery status to the SMS-GMSC. + +5. If during step 3 the UE-not-reachable flag for UDM was modified from false to true, the HSS subscribes to notification on UE-Reachability for SMS at the UDM, using the Nudm\_EE\_Subscribe service operation as defined in 3GPP TS 23.502 [5]. + +6-7. The UDM checks that the UE is registered in an AMF and SMSF for 3GPP and non-3GPP accesses. The UDM then queries the 5GS-UDR to see whether the UE-Reachability event has already been subscribed at the registered AMF(s) (i.e. whether URRP-AMF flag is set). + +8-9. If not already subscribed, the UDM subscribes to UE-Reachability notification at the AMF(s) using the Namf\_EE service. + +NOTE: As defined in 3GPP TS 23.502 [5], the UDM can trigger UE Reachability Notification Request procedure with two different AMFs for a UE which is connected to 5G Core Network over 3GPP access and non-3GPP access simultaneously. + +10-11. The UDM stores the received EE-Subscription in the 5GS-UDR and if steps 8-9 were performed, the UDM sets the relevant URRP-AMF flags in the 5GS-UDR. + +12. The UDM acknowledges the subscription to the HSS. + +### 5.5.4 SMS Alerting + +Figure 5.5.4-1 shows the interaction when the UE becomes available. + +![Sequence diagram for SMS Alerting showing interactions between AMF/SMSF, UDM, 5GS-UDR, EPS-UDR, HSS, and SMS-GMSC(s).](875c6f4f441fdd3ca7e1908fd1582983_img.jpg) + +``` + +sequenceDiagram + participant AMF/SMSF + participant UDM + participant 5GS-UDR + participant EPS-UDR + participant HSS + participant SMS-GMSC(s) + + Note right of EPS-UDR: Ud + AMF/SMSF->>UDM: 1. Namf_EE_Notify or Nudm_UECM_Registration + UDM->>5GS-UDR: 2. Nudr_DM_Query + 5GS-UDR-->>UDM: 3. Nudr_DM_Query resp. + UDM->>AMF/SMSF: 4. Response + UDM->>HSS: 5. Nudm_EE_Notify + UDM->>5GS-UDR: 6. Nudr_DM_Update + 5GS-UDR-->>UDM: 7. Nudr_DM_Update resp. + EPS-UDR->>HSS: 8. Read + HSS->>SMS-GMSC(s): 9. MAP/S6c-Alert-SC + SMS-GMSC(s)-->>HSS: 10. Response + HSS->>EPS-UDR: 11. Update + HSS->>UDM: 12. Nudm_EE_Notify resp. + +``` + +Sequence diagram for SMS Alerting showing interactions between AMF/SMSF, UDM, 5GS-UDR, EPS-UDR, HSS, and SMS-GMSC(s). + +**Figure 5.5.4-1: SMS Alerting** + +1. The UDM receives a Notification from the AMF or an SMSF Registration. + +2-3. The UDM queries the 5GS-UDR to see whether any NF (e.g. the HSS) has subscribed to notifications on UE-reachability for SMS events. + +4. The UDM acknowledges the message received in step 1. + +5. If the HSS has subscribed to UE reachability for SMS notification, the UDM notifies the HSS as described in 3GPP TS 23.502 [5]. + +6-7. The UDM updates (clears) the relevant reachability flag. And, if the HSS has been notified in step 5, the UDM also deletes the (one-time) EE-subscriptions of UE reachability for SMS in the 5GS-UDR. + +Steps 8 to 11 are skipped if the HSS has not been notified in step 5. + +8. The HSS reads Message Waiting Data from the EPS-UDR. + +9-10. The HSS sends Alert-SC to all SMS-GMSCs stored in the MWD. + +11. The HSS removes the SMS-GMSCs from the MWD stored in the EPS-UDR and clears the relevant UE-not-reachable flags from the EPS-UDR. + +12. The HSS acknowledges receipt of the Notification to the UDM. + +### 5.5.5 MT-SMS Routing Information Retrieval Over Nudr + +Figure 5.5.5-1 shows the interaction when the SMS-GMSC retrieves routing information from the HSS for MT-SMS delivery when the HSS uses the Nudr SBI. + +![Sequence diagram for MT-SMS Routing Information Retrieval Over Nudr. Lifelines: 5GS-UDR, EPS-UDR, HSS, and SMS-GMSC. The sequence starts with the SMS-GMSC sending a MAP-SRI_SM or S6c-SRR request to the HSS. The HSS then sends a Read request to the EPS-UDR via the Ud interface. The EPS-UDR sends a Nudr_DM_Query to the 5GS-UDR. The 5GS-UDR returns a Nudr_DM_Query response to the EPS-UDR. Finally, the HSS sends a MAP-SRI_SM resp or S6c-SRA response to the SMS-GMSC.](b2f5606b9c7184c1c6070a290080a3e3_img.jpg) + +``` + +sequenceDiagram + participant SMS-GMSC + participant HSS + participant EPS-UDR + participant 5GS-UDR + Note right of EPS-UDR: Ud + SMS-GMSC->>HSS: 1. MAP-SRI_SM or S6c-SRR + HSS->>EPS-UDR: 2. Read + EPS-UDR->>5GS-UDR: 3. Nudr_DM_Query + 5GS-UDR-->>EPS-UDR: 4. Nudr_DM_Query resp. + HSS->>SMS-GMSC: 5. MAP-SRI_SM resp or S6c-SRA + +``` + +Sequence diagram for MT-SMS Routing Information Retrieval Over Nudr. Lifelines: 5GS-UDR, EPS-UDR, HSS, and SMS-GMSC. The sequence starts with the SMS-GMSC sending a MAP-SRI\_SM or S6c-SRR request to the HSS. The HSS then sends a Read request to the EPS-UDR via the Ud interface. The EPS-UDR sends a Nudr\_DM\_Query to the 5GS-UDR. The 5GS-UDR returns a Nudr\_DM\_Query response to the EPS-UDR. Finally, the HSS sends a MAP-SRI\_SM resp or S6c-SRA response to the SMS-GMSC. + +**Figure 5.5.5-1: SMS Routing Info Retrieval over Nudr** + +1. The HSS receives a request for routing information from the SMS-GMSC via MAP or S6c. +2. The HSS queries the EPS-UDR via Ud to read the registered MME/MSC, the registered SGSN and the UE-not-reachable flags for MME/MSC, SGSN and UDM. +- 3-4. If the UE-not-reachable flag for UDM is not set and unless the user is known not to be registered in 5GC, the HSS retrieves the registered SMSF addresses for 3GPP and non-3GPP accesses (if any) from the 5GS-UDR. +5. The HSS returns the relevant MT-SMS target node addresses registered in HSS and/or UDM to the SMS-GMSC and the procedure is terminated. + +Otherwise, if there is no MT-SMS target node address registered in HSS nor in UDM, a negative response (Absent Subscriber SM) is sent to the SMS-GMSC and the procedure continues with steps 8 to 11 in figure 5.5.2-1. + +### 5.5.6 Support for SMS over IP + +#### 5.5.6.1 General + +In deployment scenarios where 2G/3G/4G accesses are available, SMS over IP is supported as described in 3GPP TS 23.204 [18], and the interactions between HSS and UDM are those defined in clauses 5.5.2, 5.5.3 and 5.5.4. + +For MT-SMS delivery over 5G NAS in deployment scenarios where support for SMS over IP is also required but 2G/3G/4G accesses are not supported, the MAP-C and/or Diameter S6c reference points with the SMS-GMSC and the MAP-J and/or Diameter S6c reference points with the IP-SM-GW are exposed by the UDM. The UDM and the HSS (IMS) need to interact for the registration of the IP-SM-GW address as defined in clause 5.5.6.2. Clauses 5.5.6.3 and 5.5.6.4 define the interworking between the UDM and the HSS (IMS) during delivery failure and alert procedures. + +#### 5.5.6.2 IP-SM-GW registration and SMS routing information retrieval in 5GC only deployments + +Figure 5.5.6.2-1 shows the interaction for the registration of the IP-SM-GW address in the UDM and subsequent SMS routing information retrieval. + +![Sequence diagram showing IP-SM-GW registration in UDM and SMS routing info retrieval in 5GC only deployments. The diagram involves four participants: IP-SM-GW, HSS (IMS), UDM, and SMS-GMSC. The sequence starts with the IP-SM-GW sending a Sh-Update to the HSS (IMS). The HSS (IMS) then sends a Nudm_UECM_IPSMGWRegistration Request to the UDM, which responds with a Nudm_UECM_IPSMGWRegistration Response. Next, the SMS-GMSC sends a 4a. MAP-SRI_SM or S6c-SRR request to the UDM. The UDM then sends a 4b. MAP-SRI_SM req/resp or S6c-SRR/SRA response to the IP-SM-GW, which in turn sends a 4c. MAP-SRI_SM resp or S6c-SRA response to the SMS-GMSC. There are two optional paths: 4d. Skip interrogation (from UDM to SMS-GMSC) and 4e. MAP-SRI_SM or S6c-SRR (from UDM to SMS-GMSC), followed by 4f. MAP-SRI_SM resp or S6c-SRA (from SMS-GMSC to UDM).](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +``` + +sequenceDiagram + participant IP-SM-GW + participant HSS (IMS) + participant UDM + participant SMS-GMSC + + Note left of IP-SM-GW: 1. Sh-Update + IP-SM-GW->>HSS (IMS): 1. Sh-Update + Note right of HSS (IMS): 2. Nudm_UECM_IPSMGWRegistration Request + HSS (IMS)->>UDM: 2. Nudm_UECM_IPSMGWRegistration Request + Note right of UDM: 3. Nudm_UECM_IPSMGWRegistration Response + UDM->>HSS (IMS): 3. Nudm_UECM_IPSMGWRegistration Response + + Note right of SMS-GMSC: 4a. MAP-SRI_SM or S6c-SRR + SMS-GMSC->>UDM: 4a. MAP-SRI_SM or S6c-SRR + Note left of UDM: 4b. MAP-SRI_SM req/resp or S6c-SRR/SRA + UDM->>IP-SM-GW: 4b. MAP-SRI_SM req/resp or S6c-SRR/SRA + Note left of IP-SM-GW: 4c. MAP-SRI_SM resp or S6c-SRA + IP-SM-GW->>SMS-GMSC: 4c. MAP-SRI_SM resp or S6c-SRA + + Note right of UDM: Or: 4d. Skip interrogation + UDM->>SMS-GMSC: 4d. Skip interrogation + + Note right of UDM: Or: 4e. MAP-SRI_SM or S6c-SRR + UDM->>SMS-GMSC: 4e. MAP-SRI_SM or S6c-SRR + Note left of SMS-GMSC: 4f. MAP-SRI_SM resp or S6c-SRA + SMS-GMSC->>UDM: 4f. MAP-SRI_SM resp or S6c-SRA + +``` + +Sequence diagram showing IP-SM-GW registration in UDM and SMS routing info retrieval in 5GC only deployments. The diagram involves four participants: IP-SM-GW, HSS (IMS), UDM, and SMS-GMSC. The sequence starts with the IP-SM-GW sending a Sh-Update to the HSS (IMS). The HSS (IMS) then sends a Nudm\_UECM\_IPSMGWRegistration Request to the UDM, which responds with a Nudm\_UECM\_IPSMGWRegistration Response. Next, the SMS-GMSC sends a 4a. MAP-SRI\_SM or S6c-SRR request to the UDM. The UDM then sends a 4b. MAP-SRI\_SM req/resp or S6c-SRR/SRA response to the IP-SM-GW, which in turn sends a 4c. MAP-SRI\_SM resp or S6c-SRA response to the SMS-GMSC. There are two optional paths: 4d. Skip interrogation (from UDM to SMS-GMSC) and 4e. MAP-SRI\_SM or S6c-SRR (from UDM to SMS-GMSC), followed by 4f. MAP-SRI\_SM resp or S6c-SRA (from SMS-GMSC to UDM). + +**Figure 5.5.6.2-1: IP-SM-GW registration in UDM and SMS routing info retrieval in 5GC only deployments** + +1. The IP-SM-GW registers its address in HSS (IMS) via Sh as defined in 3GPP TS 23.204 [18]. If the EPS-UDR is used, the HSS (IMS) stores the IP-SM-GW address in the EPS-UDR. +2. The HSS forwards the IP-SM-GW registration to the UDM using a Nudm\_UECM\_IPSMGWRegistration request. The request includes the address of the IP-SM-GW to be registered in the UDM. If the 5GS-UDR is used, the UDM stores the IP-SM-GW address in the 5GS-UDR. +3. The UDM confirms the IP-SM-GW registration with a successful Nudm\_UECM\_IPSMGWRegistration response. After successful registration of the IP-SM-GW address, the UDM checks whether message waiting data are stored and alerts all SCs using procedures described in 3GPP TS 23.204 [18]. +4. The UDM receives a request for routing information from the SMS-GMSC via MAP or Diameter. If the 5GS-UDR is used, the UDM queries the 5GS-UDR to read the registered SMSF and/or IP-SM-GW, if any. Routing information is provided to SMS-GMSC from IP-SM-GW or UDM. + +The options shown are based on the options for MT SMS procedure described in clause 6.4 of 3GPP TS 23.204 [18], considering a 5GC only deployment where UDM is present and HLR/HSS serving 2G/3G/4G accesses is not deployed. Steps 4a-4c correspond to 3a-3c; step 4d corresponds to 3d; and steps 4e-4f correspond to 3e-3f, respectively, as shown in figure 6.4 of 3GPP TS 23.204 [18]. + +Figure 5.5.6.2-2 shows the interaction for the deregistration of the IP-SM-GW address in the UDM. + +![Sequence diagram showing IP-SM-GW deregistration in UDM and SMS routing info retrieval in 5GC only deployments. The diagram involves four entities: IP-SM-GW, HSS (IMS), UDM, and SMS-GMSC. The sequence of messages is: 1. Sh-Update from IP-SM-GW to HSS (IMS); 2. Nudm_UECM_IPSMGWDeregistration Request from HSS (IMS) to UDM; 3. Nudm_UECM_IPSMGWDeregistration Response from UDM to HSS (IMS); 4. MAP-SRI_SM or S6c-SRR from SMS-GMSC to UDM; 5. MAP-SRI_SM resp or S6c-SRA from UDM to SMS-GMSC.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` +sequenceDiagram + participant IP-SM-GW + participant HSS (IMS) + participant UDM + participant SMS-GMSC + Note left of IP-SM-GW: 1. Sh-Update + IP-SM-GW->>HSS (IMS): 1. Sh-Update + Note right of HSS (IMS): 2. Nudm_UECM_IPSMGWDeregistration Request + HSS (IMS)->>UDM: 2. Nudm_UECM_IPSMGWDeregistration Request + Note right of UDM: 3. Nudm_UECM_IPSMGWDeregistration Response + UDM->>HSS (IMS): 3. Nudm_UECM_IPSMGWDeregistration Response + Note right of SMS-GMSC: 4. MAP-SRI_SM or S6c-SRR + SMS-GMSC->>UDM: 4. MAP-SRI_SM or S6c-SRR + Note right of UDM: 5. MAP-SRI_SM resp or S6c-SRA + UDM->>SMS-GMSC: 5. MAP-SRI_SM resp or S6c-SRA +``` + +Sequence diagram showing IP-SM-GW deregistration in UDM and SMS routing info retrieval in 5GC only deployments. The diagram involves four entities: IP-SM-GW, HSS (IMS), UDM, and SMS-GMSC. The sequence of messages is: 1. Sh-Update from IP-SM-GW to HSS (IMS); 2. Nudm\_UECM\_IPSMGWDeregistration Request from HSS (IMS) to UDM; 3. Nudm\_UECM\_IPSMGWDeregistration Response from UDM to HSS (IMS); 4. MAP-SRI\_SM or S6c-SRR from SMS-GMSC to UDM; 5. MAP-SRI\_SM resp or S6c-SRA from UDM to SMS-GMSC. + +**Figure 5.5.6.2-2: IP-SM-GW deregistration in UDM and SMS routing info retrieval in 5GC only deployments** + +1. The IP-SM-GW deregisters its address in HSS (IMS) via Sh as defined in 3GPP TS 23.204 [18]. If the EPS-UDR is used, the HSS (IMS) removes the IP-SM-GW address from the EPS-UDR. +2. The HSS forwards the IP-SM-GW deregistration request to the UDM using a Nudm\_UECM\_IPSMGWDeregistration request. If the 5GS-UDR is used, the UDM removes the IP-SM-GW address from the 5GS-UDR. +3. The UDM confirms the IP-SM-GW deregistration with a successful Nudm\_UECM\_IPSMGWDeregistration response. +- 4 - 5. If the UDM receives a request for routing information from the SMS-GMSC via MAP or Diameter, the UDM checks if there is an IP-SM-GW address registered for the UE. If the 5GS-UDR is used, the UDM queries the 5GS-UDR to read the registered SMSF and/or IP-SM-GW, if any. If an IP-SM-GW address is not present, the UDM follows the MT SMS procedures defined in clause 4.13.3 of 3GPP TS 23.502 [5] and 3GPP TS 23.040 [17]. + +#### 5.5.6.3 MT SMS delivery failure in 5GC only deployments + +Figure 5.5.6.3-1 shows the interactions for the unsuccessful MT SMS delivery case in a 5GC only deployment requiring SMSoIP. + +![Sequence diagram showing MT SMS delivery failure in 5GC only deployments supporting SMSoIP. The diagram illustrates the interaction between SMS-GMSC, UDM, HSS (IMS), IP-SM-GW, S-CSCF, SMSF, AMF, and UE. The process starts with an SM termination procedure, followed by a delivery report failure from IP-SM-GW to S-CSCF, then to SMSF, and finally to UE. The IP-SM-GW then sends a delivery report failure to SMS-GMSC, which in turn sends a MAP/S6c Report_SM_Delivery_Status to UDM. The UDM then sends a Sh-Subs-Notif (UE Reachability) to HSS (IMS), followed by Nudm_EE_Subscribe req and Namf_EE_Subscribe req to AMF. The AMF responds with Namf_EE_Subscribe resp, which the UDM forwards as Nudm_EE_Subscribe resp to HSS (IMS). Finally, the SMS-GMSC sends another MAP/S6c Report_SM_Delivery_Status to UDM.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` + +sequenceDiagram + participant SMS-GMSC + participant UDM + participant HSS (IMS) + participant IP-SM-GW + participant S-CSCF + participant SMSF + participant AMF + participant UE + + Note over SMS-GMSC, UE: 1. SM termination procedure + IP-SM-GW->>S-CSCF: 2. Delivery report (failure) + S-CSCF->>IP-SM-GW: 3. Report Ack + IP-SM-GW->>SMSF: 4. Message transfer + SMSF-->>AMF: 5. Message transfer + SMSF-->>UE: 5. Message transfer + AMF-->>SMSF: 6. Delivery report (failure) + SMSF-->>IP-SM-GW: 6. Delivery report (failure) + IP-SM-GW-->>SMS-GMSC: 7. Delivery report (failure) + SMS-GMSC->>UDM: 8. MAP/S6c Report_SM_Delivery_Status + UDM->>HSS (IMS): 9. Sh-Subs-Notif (UE Reachability) + HSS (IMS)->>UDM: 10. Nudm_EE_Subscribe req + UDM->>AMF: 11. Namf_EE_Subscribe req + AMF->>UDM: 12. Namf_EE_Subscribe resp + UDM->>HSS (IMS): 13. Nudm_EE_Subscribe resp + SMS-GMSC->>UDM: 14. MAP/S6c Report_SM_Delivery_Status + +``` + +Sequence diagram showing MT SMS delivery failure in 5GC only deployments supporting SMSoIP. The diagram illustrates the interaction between SMS-GMSC, UDM, HSS (IMS), IP-SM-GW, S-CSCF, SMSF, AMF, and UE. The process starts with an SM termination procedure, followed by a delivery report failure from IP-SM-GW to S-CSCF, then to SMSF, and finally to UE. The IP-SM-GW then sends a delivery report failure to SMS-GMSC, which in turn sends a MAP/S6c Report\_SM\_Delivery\_Status to UDM. The UDM then sends a Sh-Subs-Notif (UE Reachability) to HSS (IMS), followed by Nudm\_EE\_Subscribe req and Namf\_EE\_Subscribe req to AMF. The AMF responds with Namf\_EE\_Subscribe resp, which the UDM forwards as Nudm\_EE\_Subscribe resp to HSS (IMS). Finally, the SMS-GMSC sends another MAP/S6c Report\_SM\_Delivery\_Status to UDM. + +**Figure 5.5.6.3-1: MT SMS delivery failure in 5GC only deployments supporting SMSoIP** + +- 1 - 7. The message delivery fails after the IP-SM-GW has tried all selectable domains, and the IP-SM-GW forwards the received unsuccessful Delivery report to the SMS-GMSC, as described in steps 1-16 in clause 6.5a of 3GPP TS 23.204 [18]. +8. The IP-SM-GW sends a Report SM Delivery Status message to the UDM with accurate results from different domains. If the 5GS-UDR is used, the UDM records the corresponding MWD in the 5GS-UDR. +9. The IP-SM-GW subscribes to the HSS (IMS) for a one-time notification of the UE being reachable again. +10. The HSS (IMS) records the subscription and subscribes to notification on UE Reachability for SMS over IP event at the UDM, using the Nudm\_EE\_Subscribe service operation. +- 11 - 12. The UDM checks whether UE Reachability has already been subscribed at the registered AMF(s) (i.e. whether URRP-AMF flag is set), querying 5GS-UDR if applicable. If not already subscribed, the UDM subscribes to UE Reachability notification at the AMF(s) using the Namf\_EE service. +If 5GS-UDR is used, the UDM stores the received EE-Subscription from HSS (IMS) in the 5GS-UDR, and if subscription to AMF is performed in this step, the UDM sets the relevant URRP-AMF flag in the 5GS-UDR. +13. The UDM acknowledges the subscription of the HSS (IMS). +14. The SMS-GMSC sends a Report SM Delivery Status message to the UDM. The UDM shall ignore the information provided in this report. + +#### 5.5.6.4 Alert Service Centre in 5GC only deployments + +Figure 5.5.6.4-1 shows the interactions when the UE becomes available in a 5GC only deployment requiring SMSoIP. + +![Sequence diagram illustrating the Alert Service Centre procedure in 5GC only deployments supporting SMSoIP. The diagram shows interactions between SMS-IWMSC, SMS-SC, SMS-GMSC, UDM, HSS (IMS), IP-SM-GW, S-CSCF, AMF, and UE. The procedure starts with an 'Unsuccessful SM termination procedure' (1) between SMS-SC and UE. This is followed by 'IMS registration' (2a) between UE and AMF. The AMF then sends 'Namf_UECM_Registration' (2b) to the UDM. The UDM sends 'Nudm_UECM_Notify' (2c) to the HSS (IMS). The HSS (IMS) sends 'Sh-Notif (UE reachability)' (2d) to the IP-SM-GW. The IP-SM-GW sends 'SM Ready message' (2e) to the UDM. The UDM then sends 'Alert Service Centre' (3) to the SMS-IWMSC. The SMS-IWMSC sends 'Alert Service Centre' (4) to the SMS-SC. Finally, the SMS-SC performs a 'Successful SM termination procedure' (5) with the UE.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` + +sequenceDiagram + participant SMS-IWMSC + participant SMS-SC + participant SMS-GMSC + participant UDM + participant HSS as HSS (IMS) + participant IP-SM-GW + participant S-CSCF + participant AMF + participant UE + + Note over SMS-SC, UE: 1. Unsuccessful SM termination procedure + Note over UE, AMF: 2a. IMS registration + AMF-->>UDM: 2b. Namf_UECM_Registration + UDM-->>HSS: 2c. Nudm_UECM_Notify + HSS-->>IP-SM-GW: 2d. Sh-Notif (UE reachability) + IP-SM-GW-->>UDM: 2e. SM Ready message + UDM-->>SMS-IWMSC: 3. Alert Service Centre + SMS-IWMSC-->>SMS-SC: 4. Alert Service Centre + Note over SMS-SC, UE: 5. Successful SM termination procedure + +``` + +Sequence diagram illustrating the Alert Service Centre procedure in 5GC only deployments supporting SMSoIP. The diagram shows interactions between SMS-IWMSC, SMS-SC, SMS-GMSC, UDM, HSS (IMS), IP-SM-GW, S-CSCF, AMF, and UE. The procedure starts with an 'Unsuccessful SM termination procedure' (1) between SMS-SC and UE. This is followed by 'IMS registration' (2a) between UE and AMF. The AMF then sends 'Namf\_UECM\_Registration' (2b) to the UDM. The UDM sends 'Nudm\_UECM\_Notify' (2c) to the HSS (IMS). The HSS (IMS) sends 'Sh-Notif (UE reachability)' (2d) to the IP-SM-GW. The IP-SM-GW sends 'SM Ready message' (2e) to the UDM. The UDM then sends 'Alert Service Centre' (3) to the SMS-IWMSC. The SMS-IWMSC sends 'Alert Service Centre' (4) to the SMS-SC. Finally, the SMS-SC performs a 'Successful SM termination procedure' (5) with the UE. + +**Figure 5.5.6.4-1: Alert Service Centre procedure in 5GC only deployments supporting SMSoIP** + +The steps described below are based on the procedure described in clause 6.5b of 3GPP TS 23.204 [18], considering a 5GC only deployment. + +1. MT SMS procedure is unsuccessful as described in clause 5.5.6.3. +2. At any time after the unsuccessful SM termination procedure, the UE may become available due to registration in IMS (step 2a). After the IMS registration is finished, the procedure continues as described in step 3. + +At any time after the unsuccessful SM termination procedure, the UDM can receive a notification from AMF indicating that the UE is reachable again or an AMF registration (step 2b). The UDM checks whether any NF (e.g. the HSS) has subscribed to notification on UE Reachability for SMS over IP events, querying 5GS-UDR if applicable. If the HSS has subscribed to such notification, the UDM notifies the HSS (step 2c). As the IP-SM-GW has subscribed to the event of UE being reachable again as described in clause 5.5.6.3, the HSS shall notify the IP-SM-GW (step 2d). If the UE is already registered in IMS, the IP-SM-GW shall then send a Ready for SM message to the UDM (step 2e) and the procedure continues as described in step 3. Otherwise, the IP-SM-GW discards the notification message. + +3. The UDM checks the user's MWD. If MWD is not null, the UDM sends an Alert Service Centre message to the SMS-IWMSC. +4. The SMS-IWMSC forwards the Alert Service Centre procedure to the SMS-SC. +5. Upon receipt of the Alert Service Centre message, the SMS-SC re-attempts to send the stored Short Message. + +## 5.6 Common Network Exposure Scenarios + +### 5.6.1 General + +As specified in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [5], a combined SCEF+NEF can configure monitoring events applicable to both EPC and 5GC using only 5GC procedures towards UDM. In this case, the SCEF+NEF indicates that + +the monitoring event is also applicable to EPC together with the SCEF identity, i.e. the event must be reported both by 5GC and EPC. + +If the HSS and UDM are deployed as separate network entities as defined in this specification, UDM uses HSS services to configure the monitoring event in EPC. For events requiring reporting from MME towards SCEF or HSS, the UDM requests the configuration of the monitoring event in the EPC to the HSS as defined in clause 5.6.2. The status of specific monitoring events that are detected locally at the HSS and UDM (e.g. IMEI/PEI change, roaming status change) is kept synchronized between UDM and HSS as defined in clause 5.6.3. + +### 5.6.2 Configuration of Monitoring Events in MME + +Figure 5.6.2-1 shows the scenario where the UDM receives a request from a combined SCEF+NEF to configure a monitoring event that needs to be reported by EPC (e.g. location change). + +![Sequence diagram illustrating the configuration of monitoring events in MME. The diagram shows four main entities: SCEF+NEF, UDM, HSS, and MME. The sequence of messages is as follows: 1. SCEF+NEF sends a Nudm_EE_Subscribe Req to UDM. 2. UDM configures the monitoring event in 5GC. 3. UDM sends an Nhss_EE_Subscribe Req to HSS. 4. HSS configures the monitoring event in EPC. 5. HSS sends an Nhss_EE_Subscribe Resp to UDM. 6. UDM sends a Nudm_EE_Subscribe Resp to SCEF+NEF. 7. A monitoring event is detected in EPC. 8. The monitoring event is notified.](43979979715bb3304389a0cb18f34444_img.jpg) + +``` + +sequenceDiagram + participant SCEF+NEF + participant UDM + participant HSS + participant MME + + Note right of UDM: 2. UDM configures monitoring event in 5GC. + Note right of HSS: 4. HSS configures monitoring event in EPC. + Note right of MME: 7. Monitoring event is detected in EPC + + SCEF+NEF->>UDM: 1. Nudm_EE_Subscribe Req + UDM->>HSS: 3. Nhss_EE_Subscribe Req + HSS->>UDM: 5. Nhss_EE_Subscribe Resp + UDM->>SCEF+NEF: 6. Nudm_EE_Subscribe Resp + + Note left of SCEF+NEF: 8. Monitoring event is notified + +``` + +Sequence diagram illustrating the configuration of monitoring events in MME. The diagram shows four main entities: SCEF+NEF, UDM, HSS, and MME. The sequence of messages is as follows: 1. SCEF+NEF sends a Nudm\_EE\_Subscribe Req to UDM. 2. UDM configures the monitoring event in 5GC. 3. UDM sends an Nhss\_EE\_Subscribe Req to HSS. 4. HSS configures the monitoring event in EPC. 5. HSS sends an Nhss\_EE\_Subscribe Resp to UDM. 6. UDM sends a Nudm\_EE\_Subscribe Resp to SCEF+NEF. 7. A monitoring event is detected in EPC. 8. The monitoring event is notified. + +**Figure 5.6.2-1: Configuration of Monitoring Events in MME** + +1. The UDM receives a request from a combined SCEF+NEF to configure a monitoring event for a UE. The request indicates that the subscription applies also to EPC and the monitoring event is to be reported by the MME (e.g. location change). The request includes the notification addresses of both the NEF and the SCEF. +2. The UDM configures the monitoring event for the UE in 5GC. If the 5GS UDR is used, the UDM stores the configuration of the monitoring event for the UE in the 5GS-UDR. The UDM contacts the corresponding NF within the 5GC (e.g. AMF, SMF) as required by the monitoring event. +3. Unless the subscription information related to the UE indicates that the UE has no EPC subscription data, then the UDM requests the HSS to configure the monitoring event for the UE in EPC using a Nhss\_EventExposure\_Subscribe operation. In addition to the UDM notification address, the UDM provides the SCEF notification address (i.e. SCEF Id). +4. The HSS configures the monitoring event for the UE in EPC using the procedures defined in 3GPP TS 23.682 [16]. +5. The HSS replies to the UDM with the result of the subscription request. +6. The UDM replies to the combined SCEF+NEF including confirmation that the subscription was also successful in EPC domain. +7. At a later stage, the monitoring event is detected for the UE in the EPC domain. The event may be detected at the MME (e.g. location change) or at the HSS (e.g. UE reachability for SMS). + +8. The monitoring event is reported to the SCEF+NEF. The MME notifies the event as defined in 3GPP TS 23.682 [16] by using the SCEF notification address provided by the HSS in step 4, if applicable. If the monitoring event is detected at the HSS or reported by the MME to the HSS, the HSS notifies the monitoring event to UDM using the Nhss\_EE\_Notify service operation. The UDM then notifies NEF using the Nudm\_EE\_Notify service operation. + +NOTE: The notification of monitoring events from HSS (e.g. reachability for SMS) using SBA interfaces supersedes the option of HSS using diameter S6t. Only the events reported by MME will keep diameter T6a interface towards SCEF. + +### 5.6.3 Synchronization of Status of Monitoring Event between HSS and UDM + +The status of some specific monitoring events that are detected locally at the HSS and UDM (e.g. IMEI(SV)/PEI change, roaming status change) is kept synchronized between UDM and HSS as defined in this clause. This is, when the HSS detects e.g. that the IMEI(SV) for a UE changes (e.g. during an Update Location in EPS), the HSS informs the UDM about the IMEI(SV) change which stores the new IMEI(SV)/PEI accordingly. + +NOTE: The synchronization of the status of these monitoring events can be disabled in HSS and UDM based on local policies, e.g. if common exposure is not supported or last known IMEI is not required in HSS/UDM. + +This allows that the subscriptions to these specific monitoring events are applied in both domains. The UDM is capable of notifying these events taking place in EPS to the combined SCEF+NEF using SBI procedures. + +Figure 5.6.3-1 shows the scenario where the UDM receives a request from a combined SCEF+NEF to subscribe to a monitoring event in 5GC and EPC that is reported by the UDM. + +![Sequence diagram showing the synchronization of monitoring events between SCEF+NEF, UDM, and HSS. The process involves subscription, configuration, detection, update, and notification steps across the three entities.](32ff77da4286b58c4778033acaa10836_img.jpg) + +``` + +sequenceDiagram + participant SCEF+NEF + participant UDM + participant HSS + + SCEF+NEF->>UDM: 1. Nudm_EE_Subscribe Req + Note over UDM: 2. UDM configures monitoring +event. + UDM-->>SCEF+NEF: 3. Nudm_EE_Subscribe Resp + Note over HSS: 4. HSS detects +monitoring event + HSS->>UDM: 5. Nudm_UECM_Update + Note over UDM: 6. UDM stores information from HSS +UDM checks subscribed monitoring events + UDM-->>SCEF+NEF: 7. Nudm_EE_Notify + Note over UDM: 8. UDM detects monitoring event + UDM-->>SCEF+NEF: 9. Nudm_EE_Notify + UDM->>HSS: 10. Nhss_UECM_Update + Note over HSS: 11. HSS stores +info from UDM + +``` + +Sequence diagram showing the synchronization of monitoring events between SCEF+NEF, UDM, and HSS. The process involves subscription, configuration, detection, update, and notification steps across the three entities. + +**Figure 5.6.3-1: Synchronization of Status of Monitoring Events between HSS and UDM** + +1. The UDM receives a request from a combined SCEF+NEF to configure a monitoring event for a UE. The request indicates that the subscription applies also to EPC (e.g. IMEI(SV)/PEI change) and UDM is expected to report the event. + 2. The UDM stores in the 5GS-UDR the monitoring event together with the notification address (e.g., the NEF notification address) of the combined SCEF+NEF. + 3. The UDM replies to the combined SCEF+NEF including a confirmation that the configuration of the event was also successful in EPC domain. +- NOTE: A UDM that supports interworking with EPC relies on the HSS to synchronize the status of these monitoring events in the EPC domain with the UDM (i.e. the UDM does not need to subscribe to the monitoring event towards the HSS) for UEs that have subscription data in EPC and 5GC. +4. At a later stage, the HSS detects the event (e.g. IMEI(SV) change) for the UE in the EPC domain (e.g. during an Update Location Request procedure). + 5. The HSS synchronizes with the UDM about the event using the Nudm\_UECM\_Update service operation. + 6. The UDM stores the information received from HSS (e.g. a new PEI for the UE) in the 5GS-UDR and checks if a related subscription to the related monitoring event exists. + 7. The UDM notifies the NEF accordingly. + 8. Alternatively, the monitoring event may be detected by the UDM. + 9. The UDM notifies the NEF accordingly. + +10. The UDM synchronizes with the HSS about the event using the Nhss\_UECM\_Update service operation. +11. The HSS stores the status of the monitoring event received from the UDM in the EPS-UDR. + +# 6 Network Function Service procedures + +## 6.1 HSS Services + +### 6.1.1 General + +The following table illustrates the HSS Services. + +**Table 6.1.1-1: NF services provided by HSS** + +| NF service | Service Operations | Operation Semantics | Example Consumer(s) | +|-------------------|--------------------|---------------------|---------------------| +| UE Authentication | Get | Request/Response | UDM | +| UECM | SNDeregistration | Request/Response | UDM | +| | Update | Request/Response | UDM | +| SDM | Get | Request/Response | UDM | +| | Subscribe | Subscribe/Notify | UDM | +| | Unsubscribe | | | +| | Notify | | | +| EE | Subscribe | Subscribe/Notify | UDM | +| | Unsubscribe | | | +| | Notify | | | + +### 6.1.2 Nhss\_UEAuthentication service + +#### 6.1.2.1 Nhss\_UEAuthentication\_Get service operation + +**Service operation name:** Nhss\_UEAuthentication\_Get + +**Description:** Requester NF gets the authentication vector from HSS. For AKA based authentication, this operation can be also used to recover from synchronization failure situations. + +**Inputs, Required:** IMSI, authentication method, serving network name. + +**Inputs, Optional:** Synchronization Failure indication and related information (i.e. RAND/AUTS). + +**Outputs, Required:** Authentication vector. + +**Outputs, Optional:** None. + +### 6.1.3 Nhss\_UECM service + +#### 6.1.3.1 Nhss\_UECM\_SNDeregistration service operation + +**Service operation name:** Nhss\_UECM\_SNDeregistration. + +**Description:** The NF consumer requests the HSS to initiate cancel location to the Serving Node registered in HSS serving the UE in EPS and/or PS, if any. + +**Inputs, Required:** IMSI, deregistration reason. + +**Inputs, Optional:** None. + +**Outputs, Required:** Result Indication. + +**Outputs, Optional:** None. + +#### 6.1.3.2 Nhss\_UECM\_Update service operation + +**Service operation name:** Nhss\_UECM\_Update. + +**Description:** The NF consumer informs the HSS about an update in the UE Context (e.g. a change in the IMEI). + +**Inputs, Required:** IMSI. + +**Inputs, Optional:** IMEI(SV), serving PLMN. + +**Outputs, Required:** Result Indication. + +**Outputs, Optional:** None. + +### 6.1.4 Nhss\_SDM service + +#### 6.1.4.1 Nhss\_SDM\_Get service operation + +**Service operation name:** Nhss\_SDM\_Get + +**Description:** The consumer NF gets the subscriber data indicated by the requested data type from HSS. In this release, only the PGW-C+SMF FQDN for S5/S8/S2b interface information is supported as requested data type. + +**Inputs, Required:** IMSI, requested data. + +**Inputs, Optional:** None. + +**Outputs, Required:** The consumer NF gets the requested subscription data + +**Outputs, Optional:** None. + +#### 6.1.4.2 Nhss\_SDM\_Notification service operation + +**Service or service operation name:** Nhss\_SDM\_Notification + +**Description:** The HSS notifies NF consumer of the updates of the subscriber data indicated by the "subscription data Type" input. In this release, only the PGW-C+SMF FQDN for S5/S8/S2b interface information is supported as subscription data type. + +**Inputs, Required:** IMSI, Subscription data type(s). + +**Inputs, Optional:** None. + +**Outputs, Required:** Result Indication. + +The HSS invokes this service operation under the following cases: + +- When the PGW-C+SMF FQDN for S5/S8/S2b interface information is updated at the HSS, the updated information is notified to the NF consumer that has subscribed for the specific subscription data type to be notified. + +**Outputs, Optional:** None. + +#### 6.1.4.3 Nhss\_SDM\_Subscribe service operation + +**Service operation name:** Nhss\_SDM\_Subscribe + +**Description:** The NF consumer subscribes for updates to the subscriber data indicated by the 'subscription data type' input. The HSS shall check the requested consumer is authorized to subscribe to requested updates. In this release, only the PGW-C+SMF FQDN for S5/S8/S2b interface information is supported as subscription data type. + +**Inputs, Required:** IMSI, Subscription data type(s). + +**Inputs, Optional:** None. + +**Outputs, Required:** None. + +**Outputs, Optional:** None. + +#### 6.1.4.4 Nhss\_SDM\_Unsubscribe service operation + +**Service operation name:** Nhss\_SDM\_Unsubscribe + +**Description:** The NF consumer unsubscribes from updates to the subscriber data indicated by the 'subscription data type' input. In this release, only the PGW-C+SMF FQDN for S5/S8 interface information is supported as subscription data type. + +**Inputs, Required:** IMSI, Subscription data type(s). + +**Inputs, Optional:** None. + +**Outputs, Required:** None. + +**Outputs, Optional:** None. + +### 6.1.5 Nhss\_EE service + +#### 6.1.5.1 Nhss\_EE\_Subscribe service operation + +**Service operation name:** Nhss\_EE\_Subscribe. + +**Description:** The NF consumer request the HSS to subscribe to notifications for monitoring events as described in 3GPP TS 23.682 [16] (e.g. location change). + +**Inputs, Required:** IMSI, monitoring event type(s), notification address. + +**Inputs, Optional:** - + +**Outputs, Required:** Result Indication, Subscription ID. + +**Outputs, Optional:** None. + +#### 6.1.5.2 Nhss\_EE\_Unsubscribe service operation + +**Service operation name:** Nhss\_EE\_Unsubscribe. + +**Description:** The NF consumer request the HSS to delete the subscription of a monitoring event. + +**Inputs, Required:** Subscription ID. + +**Inputs, Optional:** - + +**Outputs, Required:** Operation execution result indication. + +**Outputs, Optional:** None. + +#### 6.1.5.3 Nhss\_EE\_Notify service operation + +**Service operation name:** Nhss\_EE\_Notify. + +**Description:** The HSS reports the monitoring event to the consumer that has previously subscribed. + +**Inputs, Required:** Event ID, Notification Correlation Information, time stamp. + +**Inputs, Optional:** Event specific parameters list. + +**Outputs, Required:** None. + +**Outputs, Optional:** None. + +## 6.2 UDM Services + +### 6.2.1 General + +The following table illustrates the UDM Services. + +**Table 6.2.1-1: NF services provided by UDM** + +| NF service | Service Operations | Operation Semantics | Example Consumer(s) | +|---------------|----------------------------|---------------------|---------------------| +| UECM | P-CscfRestorationTrigger | Request/Response | HSS | +| | Get | Request/Response | HSS | +| | AMFDeregistration | Request/Response | HSS | +| | Update | Request/Response | HSS | +| MT | ProvideDomainSelectionInfo | Request/Response | HSS | +| | ProvideUserState | Request/Response | HSS | +| | ProvideLocationInfo | Request/Response | HSS | +| | Provide5GSRVCCInfo | Request/Response | HSS | +| EventExposure | Subscribe | Subscribe/Notify | HSS | +| | Notify | | | +| UEAU | GetHssAv | Request/Response | HSS | +| SDM | Get | Request/Response | HSS | +| | Subscribe | Subscribe/Notify | HSS | +| | Unsubscribe | | | +| | Notify | | | +| PP | Update | Request/Response | HSS | + +### 6.2.2 Nudm\_UECM service operation + +#### 6.2.2.1 Nudm\_UECM\_P-CscfRestorationTrigger service operation + +**Service operation name:** Nudm\_UECM\_P-CscfRestorationTrigger + +**Description:** Requester NF (HSS) triggers the UDM to notify all NFs (AMF, SMF) that have previously subscribed to receive notifications for P-CSCF restoration. + +**Inputs, Required:** SUPI. + +**Inputs, Optional:** None. + +**Outputs, Required:** None. + +**Outputs, Optional:** None. + +#### 6.2.2.2 Nudm\_UECM\_Get service operation + +See 3GPP TS 23.502 [5] clause 5.2.3.2.4. + +#### 6.2.2.3 Nudm\_UECM\_AMFDeregistration service operation + +**Service operation name:** Nudm\_UECM\_AMFDeregistration. + +**Description:** The NF consumer requests the UDM to initiate deregistration of the AMF serving the UE, if any. + +**Inputs, Required:** SUPI, deregistration reason. + +**Inputs, Optional:** None. + +**Outputs, Required:** Result Indication. + +**Outputs, Optional:** None. + +#### 6.2.2.4 Nudm\_UECM\_Update service operation + +See 3GPP TS 23.502 [5] clause 5.2.3.2.5. + +### 6.2.3 Nudm\_MT Service + +#### 6.2.3.1 Nudm\_MT\_ProvideDomainSelectionInfo Service + +**Service operation name:** Nudm\_MT\_ProvideDomainSelectionInfo + +**Description:** Provides the UE information for terminating domain selection of IMS voice in 5G to the consumer NF (HSS). + +**Inputs, Required:** SUPI. + +**Inputs, Optional:** None. + +**Outputs, Required:** Success/Failure indication. + +**Outputs, Optional:** Indication of supporting IMS voice over PS Session or not, Time stamp of the last radio contact with the UE, Current RAT type. + +#### 6.2.3.2 Nudm\_MT\_ProvideUserState service operation + +**Service operation name:** Nudm\_MT\_ProvideUserState + +**Description:** Provides the UE's 5GS PS User State to the consumer NF (HSS). + +**Inputs, Required:** SUPI. + +**Inputs, Optional:** None. + +**Outputs, Required:** Success/Failure indication. + +**Outputs, Optional:** 5GS User State. + +#### 6.2.3.3 Nudm\_MT\_ProvideLocationInfo service operation + +**Service operation name:** Nudm\_MT\_ProvideLocationInfo + +**Description:** Provides the UE's 5GS location information to the consumer NF (HSS). + +**Inputs, Required:** SUPI, Current Location Indicator, Serving Node Indication, Local Time Zone Indication, and RAT-Type requested Indicator. + +**Inputs, Optional:** None. + +**Outputs, Required:** Success/Failure indication. + +**Outputs, Optional:** 5GS location information. + +#### 6.2.3.4 Nudm\_MT\_Provide5GSRVCCInfo Operation + +**Service operation name:** Nudm\_MT\_ProvideSRVCCInfo + +**Description:** Provides the UE PS to CS SRVCC capability for the UE to the consumer NF (HSS). + +**Inputs, Required:** SUPI. + +**Inputs, Optional:** None. + +**Outputs, Required:** Success/Failure indication. + +**Outputs, Optional:** Indication of the UE supporting SRVCC capability or not, If the 5GS supports 5G-SRVCC, an STN-SR and a C-MSISDN. + +### 6.2.4 Nudm\_EE Service + +#### 6.2.4.1 Nudm\_EventExposure\_Subscribe service operation + +See 3GPP TS 23.502 [5] clause 5.2.3.5.2. + +When used by the HSS in MT-SMS delivery failure scenarios (see clause 4.6.3) the subscribe request shall be a one-time subscription for UE-reachability for SMS and shall indicate whether it is applicable to 3GPP access, Non3GPP access or both. + +#### 6.2.4.2 Nudm\_EventExposure\_Notify service operation + +See 3GPP TS 23.502 [5] clause 5.2.3.5.4. + +When used by the HSS in SMS Alerting scenarios (see clause 4.6.4) the notify request shall indicate whether it is applicable to 3GPP access or Non3GPP access. + +### 6.2.5 Nudm\_UEAuthentication service + +#### 6.2.5.1 Nudm\_UEAuthentication\_GetHssAv service operation + +**Service operation name:** Nudm\_UEAuthentication\_GetHssAv + +**Description:** Requester NF gets the authentication vector from UDM. For AKA based authentication, this operation can be also used to recover from synchronization failure situations. + +**Inputs, Required:** SUPI, authentication method (e.g. EAP-AKA', EPS-AKA, IMS-AKA, GBA-AKA), serving network name. + +**Inputs, Optional:** Synchronization Failure indication and related information (i.e. RAND/AUTS). + +**Outputs, Required:** Authentication vector. + +**Outputs, Optional:** None. + +### 6.2.6 Nudm\_SDM service operations + +#### 6.2.6.1 Nudm\_SDM\_Get service operation + +See 3GPP TS 23.502 [5] clause 5.2.3.3.2. + +#### 6.2.6.2 Nudm\_SDM\_Subscribe service operation + +See 3GPP TS 23.502 [5] clause 5.2.3.3.4. + +#### 6.2.6.3 Nudm\_SDM\_Unsubscribe service operation + +See 3GPP TS 23.502 [5] clause 5.2.3.3.5. + +#### 6.2.6.4 Nudm\_SDM\_Notify service operation + +See 3GPP TS 23.502 [5] clause 5.2.3.3.3. + +### 6.2.7 Nudm\_PP service operations + +#### 6.2.7.1 Nudm\_PP\_Update service operation + +**Service operation name:** Update + +**Description:** Removes, provides or modifies the STN-SR, CMSISDN, if the 5GS support 5G-SRVCC. + +**Inputs, Required:** None. + +**Inputs, Optional:** SUPI, STN-SR, CMSISDN. + +**Outputs, Required:** Success/Failure indication. + +**Outputs, Optional:** None. + +## 6.3 UDR Services + +The UDM and optionally the HSS shall make use of the Nudr\_DataRepository Query service operations specified in 3GPP TS 23.502 [5] to retrieve Authentication Subscription Data. If the subscribed authentication method is 5G\_AKA or EAP\_AKA\_PRIME, the AuthenticationSubscriptionData shall include an indicator indicating whether for the identified subscriber authentication vector generation is to be performed by the HSS. + +# Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------|-------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 2019-04 | CT4#90 | C4-191319 | | | | Skeleton | 0.1.0 | | +| 2019-04 | CT4#90 | C4-191320 | | | | Scope | 0.2.0 | | +| 2019-04 | CT4#90 | C4-191321 | | | | Reference Architecture | 0.2.0 | | +| 2019-05 | CT4#91 | C4-192135 | | | | Removal of Editor's Note | 0.3.0 | | +| 2019-05 | CT4#91 | C4-192402 | | | | P-CSCF Restoration | 0.3.0 | | +| 2019-05 | CT4#91 | C4-192403 | | | | T-ADS | 0.3.0 | | +| 2019-05 | CT4#91 | C4-192405 | | | | SMS | 0.3.0 | | +| 2019-05 | CT4#91 | C4-192462 | | | | Authentication | 0.3.0 | | +| 2019-05 | CT4#91 | C4-192098 | | | | Authentication – HSS using Nudr | 0.3.0 | | +| 2019-09 | CT4#93 | C4-193134 | | | | System Architecture | 0.4.0 | | +| 2019-09 | CT4#93 | C4-193137 | | | | IMS procedures | 0.4.0 | | +| 2019-09 | CT4#93 | C4-193829 | | | | Mobility procedures | 0.4.0 | | +| 2019-09 | CT4#93 | C4-193556 | | | | Authentication vector generation in UDM | 0.4.0 | | +| 2019-09 | CT4#93 | C4-193297 | | | | MT-SMS Routing Information Retrieval Over Nudr | 0.4.0 | | +| 2019-09 | CT4#93 | C4-193617 | | | | Location Info Retrieval | 0.4.0 | | +| 2019-09 | CT4#93 | C4-193618 | | | | UE reachability | 0.4.0 | | +| 2019-09 | CT4#93 | C4-193619 | | | | User State Info Retrieval | 0.4.0 | | +| 2019-10 | CT4#94 | C4-194347 | | | | ProvideLocationInformation | 0.5.0 | | +| 2019-10 | CT4#94 | C4-194348 | | | | Document cleanup | 0.5.0 | | +| 2019-10 | CT4#94 | C4-194350 | | | | IMS Use Cases Correction | 0.5.0 | | +| 2019-10 | CT4#94 | C4-194252 | | | | N26 Editor's Note Removal | 0.5.0 | | +| 2019-11 | CT4#95 | C4-195416 | | | | HSS to 5GS-UDR reference point | 0.6.0 | | +| 2019-11 | CT4#95 | C4-195020 | | | | P-CSCF restoration | 0.6.0 | | +| 2019-11 | CT4#95 | C4-195420 | | | | Clarification on Mobility, IMS and SMS | 0.6.0 | | +| 2019-11 | CT4#95 | C4-195137 | | | | P-CSCF Restoration Procedure | 0.6.0 | | +| 2019-11 | CT4#95 | C4-195138 | | | | Nudm_UEAuthentication service operations | 0.6.0 | | +| 2019-11 | CT4#95 | C4-195428 | | | | Nudm_SDM Service | 0.6.0 | | +| 2019-11 | CT4#95 | C4-195429 | | | | SMS Procedures | 0.6.0 | | +| 2019-12 | CT#86 | CP-193066 | | | | TS presented for information and approval | 1.0.0 | | +| 2019-12 | CT#86 | CP-193296 | | | | A title corrected | 1.0.1 | | +| 2019-12 | CT#86 | | | | | TS was approved | 16.0.0 | | +| 2020-03 | CT#87e | CP-200227 | 0008 | 2 | F | Reference Points | 16.1.0 | | +| 2020-03 | CT#87e | CP-200019 | 0001 | 1 | F | HSS can be consumer of Nudr | 16.1.0 | | +| 2020-03 | CT#87e | CP-200019 | 0002 | 1 | F | UserState retrieval | 16.1.0 | | +| 2020-03 | CT#87e | CP-200019 | 0004 | 2 | B | PGW-C+SMF Information Notification Procedure | 16.1.0 | | +| 2020-03 | CT#87e | CP-200019 | 0011 | - | B | IMEI Retrieval | 16.1.0 | | +| 2020-03 | CT#87e | CP-200022 | 0006 | 4 | B | Introduce 5G SRVCC support | 16.1.0 | | +| 2020-06 | CT#88e | CP-201033 | 0003 | 2 | F | SMS | 16.2.0 | | +| 2020-06 | CT#88e | CP-201033 | 0013 | - | F | Authentication Options | 16.2.0 | | +| 2020-06 | CT#88e | CP-201033 | 0014 | 2 | B | Common Network Exposure | 16.2.0 | | +| 2020-06 | CT#88e | CP-201033 | 0015 | 6 | F | UDM and HSS not Aware of N26 | 16.2.0 | | +| 2020-06 | CT#88e | CP-201033 | 0016 | - | F | Association between APN and PGW-C+SMF FQDN in HSS | 16.2.0 | | +| 2020-06 | CT#88e | CP-201033 | 0018 | 1 | F | SMS Interfaces | 16.2.0 | | +| 2020-06 | CT#88e | CP-201033 | 0019 | - | B | Support of SMSIoP | 16.2.0 | | +| 2020-06 | CT#88e | CP-201036 | 0017 | - | F | Remove Editor's Note regarding multiple SRVCC capabilities per system | 16.2.0 | | +| 2020-09 | CT#89e | CP-202111 | 0022 | - | F | Removal Of Editor's Notes | 16.3.0 | | +| 2020-09 | CT#89e | CP-202111 | 0023 | - | F | Missing error conditions in SMSF registration information retrieval | 16.3.0 | | +| 2020-12 | CT#90e | CP-203049 | 0024 | - | F | Inconsistency between in text and in figure clean up | 16.4.0 | | +| 2020-12 | CT#90e | CP-203049 | 0025 | - | F | SN Deregistration | 16.4.0 | | +| 2020-12 | CT#90e | CP-203049 | 0026 | - | F | UE Reachability for IP | 16.4.0 | | +| 2021-03 | CT#91e | CP-210042 | 0027 | - | F | Removal of SMSF registration notification flag | 16.5.0 | | +| 2021-03 | CT#91e | CP-210042 | 0028 | - | F | P-CSCF Restoration | 16.5.0 | | +| 2021-03 | CT#91e | CP-210042 | 0029 | 1 | F | Cancellation Type sent to MME/SGSN when UE registers in 5G | 16.5.0 | | +| 2021-03 | CT#91e | CP-210053 | 0031 | - | F | Cancellation Type for mobility from EPC to 5GC | 16.5.0 | | +| 2022-06 | CT#96 | CP-210062 | 0037 | - | F | UECM Get for retrieval of SMSF registrations | 16.6.0 | | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23725/0019f09403376d6444ee323591fa2e98_img.jpg b/marked/Rel-16/23_series/23725/0019f09403376d6444ee323591fa2e98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..548a74f6e021d901cfc2dd18549e8583342219cd --- /dev/null +++ b/marked/Rel-16/23_series/23725/0019f09403376d6444ee323591fa2e98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7df72f74254e501b8816ea8df3872a1167a829b58624fbde9bc02c569f58a4d4 +size 45162 diff --git a/marked/Rel-16/23_series/23725/052543d8c9c0643b05b3ce45c6decca1_img.jpg b/marked/Rel-16/23_series/23725/052543d8c9c0643b05b3ce45c6decca1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d89094040a371af173421cc8279fd6e77e087aa --- /dev/null +++ b/marked/Rel-16/23_series/23725/052543d8c9c0643b05b3ce45c6decca1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de8a68aa011e58bf09a3fd4c60802ad00d92cd0de2bc238357f6c496b2a42da1 +size 22099 diff --git a/marked/Rel-16/23_series/23725/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-16/23_series/23725/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54892e1dcadffc30024f28e7bcd96ec0663a6ab0 --- /dev/null +++ b/marked/Rel-16/23_series/23725/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34b036fec87d853b02846b392a8aa394f54b74e0fa749143538660b270bcadbe +size 43292 diff --git a/marked/Rel-16/23_series/23725/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/marked/Rel-16/23_series/23725/0c80c383f76034e117adf5e5eaadaaf3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1a886ac51bf64db5d7a7186708d3ca871f8e0b3 --- /dev/null +++ b/marked/Rel-16/23_series/23725/0c80c383f76034e117adf5e5eaadaaf3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12b6143f715ba5c0a4cc5de899ce76fa2b219bef7f00ea7c625c4e0432b85742 +size 41725 diff --git a/marked/Rel-16/23_series/23725/164fae2c6490ee9f4cbf3c05758ecc57_img.jpg b/marked/Rel-16/23_series/23725/164fae2c6490ee9f4cbf3c05758ecc57_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..431249a7264849e117635b0a64b47ce21d0d377d --- /dev/null +++ b/marked/Rel-16/23_series/23725/164fae2c6490ee9f4cbf3c05758ecc57_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8a938ea0973d736e0a1c8e939bed40dcf5dc046b0ad5f825abd474cef481c268 +size 89491 diff --git a/marked/Rel-16/23_series/23725/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/marked/Rel-16/23_series/23725/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e58e781d511b3a0ce01773521f7621db1aeb9bad --- /dev/null +++ b/marked/Rel-16/23_series/23725/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f1dd915285b4822f130d83108746b9043785a6d78cd46e0b3fce2cca8177f9c +size 128647 diff --git a/marked/Rel-16/23_series/23725/24a89bcaba787f2bc1721356480a4a01_img.jpg b/marked/Rel-16/23_series/23725/24a89bcaba787f2bc1721356480a4a01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4927558c1b5fcd3b96ca2318327c3872ca2e8482 --- /dev/null +++ b/marked/Rel-16/23_series/23725/24a89bcaba787f2bc1721356480a4a01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b05fd7456fcbd5c253dc81ab49622134b567e62e6c05e646a1f9240105d75499 +size 47314 diff --git a/marked/Rel-16/23_series/23725/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/23_series/23725/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61f035306fc7bdbe39b49253b0ca16b3d8f9a8d2 --- /dev/null +++ b/marked/Rel-16/23_series/23725/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a04b680104c8b3e0ca9b1996cc912f2b6b4cd214f5308362e4fa3d44669a205 +size 46632 diff --git a/marked/Rel-16/23_series/23725/34b047489058d6400b412cd0ae2334ba_img.jpg b/marked/Rel-16/23_series/23725/34b047489058d6400b412cd0ae2334ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..613e65645a56155985070a29728f04b8233f5fb3 --- /dev/null +++ b/marked/Rel-16/23_series/23725/34b047489058d6400b412cd0ae2334ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54d97e735af9dd4629442181dfffb98cd0ec3c4a41bb9719451d00337ca9e9da +size 187247 diff --git a/marked/Rel-16/23_series/23725/35127fe87029df6f5f0b2ee85f6193f1_img.jpg b/marked/Rel-16/23_series/23725/35127fe87029df6f5f0b2ee85f6193f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..703b882d79ce994e51c59e9ed4876737ed834724 --- /dev/null +++ b/marked/Rel-16/23_series/23725/35127fe87029df6f5f0b2ee85f6193f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0405e4c0537394b11f4d43d2a8e7247c016b3799567b4bd279fba2eb3690eac9 +size 85443 diff --git a/marked/Rel-16/23_series/23725/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/marked/Rel-16/23_series/23725/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ffd7395ef2d6abe11ce9843a9401d81451295d24 --- /dev/null +++ b/marked/Rel-16/23_series/23725/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b34053afca34d620e56b7300f5a05238c76f152a04f47e1b42490e3c5010ad1 +size 137038 diff --git a/marked/Rel-16/23_series/23725/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/marked/Rel-16/23_series/23725/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef816d7c98f6d33eea97633948975d83152ce58e --- /dev/null +++ b/marked/Rel-16/23_series/23725/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e38cff39731365579a46f18ea3d483c3add902f7750f022d7f9f8e63ab3cf325 +size 87161 diff --git a/marked/Rel-16/23_series/23725/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg b/marked/Rel-16/23_series/23725/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a6ee44d4107d7eb2c0af3fe94b84614f3567a24 --- /dev/null +++ b/marked/Rel-16/23_series/23725/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec89154345bd53d7662a97d49e6b47ece196bda0b0b54df9347e1ac05e023e1e +size 53780 diff --git a/marked/Rel-16/23_series/23725/474a819357587e34949a3e110ff19b30_img.jpg b/marked/Rel-16/23_series/23725/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c452bebb05068e7168c7af1ea3f2fc2d7c7ee92 --- /dev/null +++ b/marked/Rel-16/23_series/23725/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd2abe6a63003a490e07bcbd1bbc32421c6195de223f626251bc0e95c561b781 +size 50536 diff --git a/marked/Rel-16/23_series/23725/4d7f667796a8cdcdd745e953ac11e289_img.jpg b/marked/Rel-16/23_series/23725/4d7f667796a8cdcdd745e953ac11e289_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8dab5731b3227772d3b0341f7a9f359604e8fd4 --- /dev/null +++ b/marked/Rel-16/23_series/23725/4d7f667796a8cdcdd745e953ac11e289_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:752c9aa6c7efbd1d9c4f549f121fac9922ae194cf738c77af0419677479b6493 +size 72148 diff --git a/marked/Rel-16/23_series/23725/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/23_series/23725/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..319e42ad359a8cf721dc50c00e16cc8453891f27 --- /dev/null +++ b/marked/Rel-16/23_series/23725/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82257ee3259950815c85ea5c21e718d119081ca26449bb3155832e0a81fe2502 +size 102894 diff --git a/marked/Rel-16/23_series/23725/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/23_series/23725/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d63711bb550607e36ba6d842ebe894d803b139a2 --- /dev/null +++ b/marked/Rel-16/23_series/23725/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e07060b2b8d7c90bf7d52497cec6e67afc50770d5e87d7b637fd48d1cefbd9d4 +size 24121 diff --git a/marked/Rel-16/23_series/23725/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg b/marked/Rel-16/23_series/23725/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfa7803f5ff7a4b55f1b02995c0b8bf5bf8ed89c --- /dev/null +++ b/marked/Rel-16/23_series/23725/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0279e1041916c1cad16a9d0c9111cb0aff208834393f043ac127832d22260e3 +size 47114 diff --git a/marked/Rel-16/23_series/23725/7a1dee155822446f7828dcb055c465c3_img.jpg b/marked/Rel-16/23_series/23725/7a1dee155822446f7828dcb055c465c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d2d52f8a80ab6f5004d398cfaaa1fe2437ba961 --- /dev/null +++ b/marked/Rel-16/23_series/23725/7a1dee155822446f7828dcb055c465c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63309ad84d1ca1ed807008c17ea31ba94e8d1bede6e94aa43e341253f79182d9 +size 41117 diff --git a/marked/Rel-16/23_series/23725/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23725/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84a00d7b4c2ed64472cd402879da0e3697dd23c7 --- /dev/null +++ b/marked/Rel-16/23_series/23725/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db7126f3f8667c3a56e8e6506bcaf4dcbed46e91b461593969cf9e9aa337a414 +size 29591 diff --git a/marked/Rel-16/23_series/23725/803776dff64331076ffc951fc95358ee_img.jpg b/marked/Rel-16/23_series/23725/803776dff64331076ffc951fc95358ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dab4bdfcdceddae6a3687c336361694a364f67b0 --- /dev/null +++ b/marked/Rel-16/23_series/23725/803776dff64331076ffc951fc95358ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4b1e2ff7bee1b383b667f12f680c7ccb69dffa4661a66bd77d62ca8103f859f +size 45701 diff --git a/marked/Rel-16/23_series/23725/80ec3bf791fd8eb41f73a420c2122529_img.jpg b/marked/Rel-16/23_series/23725/80ec3bf791fd8eb41f73a420c2122529_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c24d5ebadff257a1ad4b2a296188a93f3ab3fba --- /dev/null +++ b/marked/Rel-16/23_series/23725/80ec3bf791fd8eb41f73a420c2122529_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bc7d7b8f0ab9d5dfef66cab960c7ee2a3cba11e468ea7d1248109ee9d8e9ef9 +size 20323 diff --git a/marked/Rel-16/23_series/23725/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23725/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1b79e73dd87e58ed16aa9623db7ca2ea1ee5439 --- /dev/null +++ b/marked/Rel-16/23_series/23725/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48615070792c569dc9274f21dd9172b481dfcddd1bdcf0bc5d856ee8f92c4198 +size 43386 diff --git a/marked/Rel-16/23_series/23725/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23725/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d9bb85150dc54736eac9aa1d2f026b0e8f88f35 --- /dev/null +++ b/marked/Rel-16/23_series/23725/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bbf977f01df73d6c4b3fbba7b9bc05b0e092ad3a708fc797e303bd59a53db03 +size 115592 diff --git a/marked/Rel-16/23_series/23725/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/marked/Rel-16/23_series/23725/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4c71e0f47459a97c4a987329cb5a1ab3cb25b82 --- /dev/null +++ b/marked/Rel-16/23_series/23725/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c315e8f133c59f28744c420dc5bca096594a29b51f8ff60734ac69fac303933 +size 133950 diff --git a/marked/Rel-16/23_series/23725/9ff1b32449ea068bba9647d71904bd59_img.jpg b/marked/Rel-16/23_series/23725/9ff1b32449ea068bba9647d71904bd59_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ba331b5c51055a0f75942a0b56c2b5e18a5e9b3a --- /dev/null +++ b/marked/Rel-16/23_series/23725/9ff1b32449ea068bba9647d71904bd59_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72fb09a3187fbc0a06e5bcdd6259c3421d51b1e30399553470434eebe6da45cd +size 152058 diff --git a/marked/Rel-16/23_series/23725/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Rel-16/23_series/23725/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..099913383b99a43acf106f9ef542a2fc2463de84 --- /dev/null +++ b/marked/Rel-16/23_series/23725/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bc1f13781623e910c4aa69bf1651454ea67fb10aa569b5cb40e9aaced9b07dd +size 94365 diff --git a/marked/Rel-16/23_series/23725/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23725/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5739655fb6306b676a0c0a800eec8791708cef60 --- /dev/null +++ b/marked/Rel-16/23_series/23725/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c7aa52d0389beab4df79012990c873d1b0fcd047bd93a5ef70761c4c4007a21 +size 36786 diff --git a/marked/Rel-16/23_series/23725/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/23_series/23725/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c84c45603ab444881994fa367e9cd32c94993d73 --- /dev/null +++ b/marked/Rel-16/23_series/23725/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2c3c370b09d67de88089e590549819298b53d5e1b4324b2969aaff8ecfb6aff +size 28714 diff --git a/marked/Rel-16/23_series/23725/b904ac2472cab80892d1e783e6230d6e_img.jpg b/marked/Rel-16/23_series/23725/b904ac2472cab80892d1e783e6230d6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8d4cf8d4fae6ba7065d6b0649de897fc7ed2ec0 --- /dev/null +++ b/marked/Rel-16/23_series/23725/b904ac2472cab80892d1e783e6230d6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1a6667d65181b8299348e59812ed14d1c00184dd5b774f2c9293fadd2a0bc08 +size 36840 diff --git a/marked/Rel-16/23_series/23725/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/Rel-16/23_series/23725/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e60067fd4f022275bf5657ae9177c76cc9ce2cc --- /dev/null +++ b/marked/Rel-16/23_series/23725/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a76fe84df40999122f5603e1a123e4c1d0b77f599b2b6431c0ffa39306e9099 +size 74907 diff --git a/marked/Rel-16/23_series/23725/c036e2540a94b31357ceb0002f0cacab_img.jpg b/marked/Rel-16/23_series/23725/c036e2540a94b31357ceb0002f0cacab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a1ebc1278ebaff3d298481b7fc7a05ea0e56c16 --- /dev/null +++ b/marked/Rel-16/23_series/23725/c036e2540a94b31357ceb0002f0cacab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c78d9598c4dca2160e9d3a18c95a85837a2c3f540f9301e4ecb3a985995de1e1 +size 21254 diff --git a/marked/Rel-16/23_series/23725/d6015fcef74bce83d04acd2e17b4fc15_img.jpg b/marked/Rel-16/23_series/23725/d6015fcef74bce83d04acd2e17b4fc15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b5fbec635f7d17729dad5409aef59138264fe10e --- /dev/null +++ b/marked/Rel-16/23_series/23725/d6015fcef74bce83d04acd2e17b4fc15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3567c838a16aa43e7ab5351f04727a5ff8b746515997537d98ed0e6ef6f52c09 +size 49372 diff --git a/marked/Rel-16/23_series/23725/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23725/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8ca59b68acf44c496d7bf0b23085b549c75ce42 --- /dev/null +++ b/marked/Rel-16/23_series/23725/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e911aa347f697df1ee8aaf61522446ff76ff26c21b6fe6091dba6d7e89069c49 +size 128489 diff --git a/marked/Rel-16/23_series/23725/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/Rel-16/23_series/23725/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15cae8a05013522931610c0989480925fb79d1af --- /dev/null +++ b/marked/Rel-16/23_series/23725/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51c384d90656f566e78b63e1e2000545c7a49681025b93acc3f0e2e11d0cc45f +size 19626 diff --git a/marked/Rel-16/23_series/23725/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg b/marked/Rel-16/23_series/23725/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60b598bc0c44c00cd2b175fdc61cfce4da104595 --- /dev/null +++ b/marked/Rel-16/23_series/23725/df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6974bc588f87473de240b7e7712856a0a986caca7117198791c5ac97e285883d +size 46002 diff --git a/marked/Rel-16/23_series/23725/e05c1a13b44ab41505609d82b00cf4df_img.jpg b/marked/Rel-16/23_series/23725/e05c1a13b44ab41505609d82b00cf4df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3aef0cba4c9df87cc0dd9246e83134a63e57c0ee --- /dev/null +++ b/marked/Rel-16/23_series/23725/e05c1a13b44ab41505609d82b00cf4df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebfe37a34dc23d66d7d2c839b440689eb60f91995b59d4c25945ef744b52e7a4 +size 25647 diff --git a/marked/Rel-16/23_series/23725/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23725/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef998b4ce9951c533092bba10ab8e44079c77265 --- /dev/null +++ b/marked/Rel-16/23_series/23725/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c62c159d1a6848fb8f2940c229220cd2b9cc0ac797b0c5a94054258bc1bd3865 +size 32197 diff --git a/marked/Rel-16/23_series/23725/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/Rel-16/23_series/23725/e636d7ccca0ad14c6b95201404324823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99de94443f167d38f408d8ae2b2f965212a6df07 --- /dev/null +++ b/marked/Rel-16/23_series/23725/e636d7ccca0ad14c6b95201404324823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65cfaf7cb57a3d2bdf129dcf5d83c3d05a7ab1e2faa10c197872510f096cee44 +size 29413 diff --git a/marked/Rel-16/23_series/23725/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/23_series/23725/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f911e3fb0759a122a2b7e15149a2a165259c31c7 --- /dev/null +++ b/marked/Rel-16/23_series/23725/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a6d5565ac9c07cc639035babd94aaa4bc0daffe5d2bc388071ac01c0b84ba99 +size 177295 diff --git a/marked/Rel-16/23_series/23725/f1fbb1287d999c7034742de35bdab836_img.jpg b/marked/Rel-16/23_series/23725/f1fbb1287d999c7034742de35bdab836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd4fc5fca8034e86815b82787a9404efead73194 --- /dev/null +++ b/marked/Rel-16/23_series/23725/f1fbb1287d999c7034742de35bdab836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11b35a54a6a326436f5fa731c36d39302dcd09af9b8ca411405d494d9e67ef51 +size 22631 diff --git a/marked/Rel-16/23_series/23725/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23725/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5ee22020e61ea471ea0393e6f24d8ce757a5c00 --- /dev/null +++ b/marked/Rel-16/23_series/23725/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb602cc2ae759c8ec646ab29cdf0d2410219d208a5ea9eb7274d19b1a972def2 +size 28341 diff --git a/marked/Rel-16/23_series/23725/raw.md b/marked/Rel-16/23_series/23725/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..92e39f01769add598bbd0139d564f0d4f64fc1e6 --- /dev/null +++ b/marked/Rel-16/23_series/23725/raw.md @@ -0,0 +1,3377 @@ +# Contents + +| | | +|------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions and abbreviations ..... | 9 | +| 3.1 Definitions..... | 9 | +| 3.2 Abbreviations ..... | 9 | +| 4 Architecture Assumptions..... | 9 | +| 5 Key Issues ..... | 10 | +| 5.1 Key Issue #1: Supporting high reliability by redundant transmission in user plane..... | 10 | +| 5.1.1 General description..... | 10 | +| 5.2 Key Issue #2: Supporting low latency and low jitter during handover procedure..... | 10 | +| 5.2.1 General description..... | 10 | +| 5.3 Key Issue #3: Enhancement of Session Continuity during UE Mobility..... | 11 | +| 5.3.1 General Description..... | 11 | +| 5.4 Key Issue #4: QoS Monitoring to Assist URLLC Service..... | 11 | +| 5.4.1 General description..... | 11 | +| 5.5 Key Issue #5: Supporting low latency without requiring that the UE to always be in RRC_Connected Mode..... | 11 | +| 5.5.1 General description..... | 11 | +| 5.6 Key Issue #6: Division of E2E PDB ..... | 12 | +| 5.6.1 Description ..... | 12 | +| 5.7 Key Issue #7: Automatic GBR service recovery after handover ..... | 12 | +| 5.7.1 General description..... | 12 | +| 6 Solutions..... | 12 | +| 6.1 Solution #1 for Key Issue #1: Redundant user plane paths based on dual connectivity..... | 12 | +| 6.1.1 Description ..... | 12 | +| 6.1.2 Procedures ..... | 16 | +| 6.1.3 Impacts on Existing Nodes and Functionality..... | 18 | +| 6.1.4 Solution Evaluation ..... | 19 | +| 6.2 Solution #2 for Key Issue #1: Multiple UEs per device for user plane redundancy..... | 20 | +| 6.2.1 Description ..... | 20 | +| 6.2.2 Procedures ..... | 23 | +| 6.2.3 Impacts on Existing Nodes and Functionality..... | 24 | +| 6.2.4 Solution Evaluation ..... | 25 | +| 6.3 Solution #3 for Key Issue #1: Supporting redundant data transmission via single UPF and two RAN nodes..... | 25 | +| 6.3.1 Description ..... | 25 | +| 6.3.1a User Plane Protocol Stack options ..... | 27 | +| 6.3.1a.1 Option 1: Enhancement of PDCP and GTP-U protocols..... | 27 | +| 6.3.1a.2 Option2: HRP protocol layer ..... | 28 | +| 6.3.2 Procedures ..... | 29 | +| 6.3.2.1 Activate Redundant Transmission during PDU Session Establishment procedure..... | 29 | +| 6.3.2.2 Activate Redundant Transmission during PDU Session Modification procedure ..... | 30 | +| 6.3.2.3 Handover procedure..... | 30 | +| 6.3.3 Impacts on Existing Nodes and Functionality..... | 31 | +| 6.3.4 Solution Evaluation ..... | 32 | +| 6.4 Solution #4 for Key Issue #1: Supporting redundant data transmission via single UPF and single RAN node..... | 32 | +| 6.4.1 Description ..... | 32 | +| 6.4.2 Procedures ..... | 34 | +| 6.4.3 Impacts on Existing Nodes and Functionality..... | 34 | +| 6.4.4 Solution Evaluation ..... | 35 | + +| | | | +|-----------|-------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 6.5 | Solution #5 for Key Issue #2: Duplication of user plane tunnelling during HO..... | 35 | +| 6.5.1 | Functional Description ..... | 35 | +| 6.5.2 | Procedures ..... | 36 | +| 6.5.2.1 | PDU session establishment or modification ..... | 36 | +| 6.5.2.2 | Enhanced N2 based Handover..... | 37 | +| 6.5.2.3 | Enhanced Handover with Xn..... | 38 | +| 6.5.3 | Impact on existing entities and interfaces..... | 39 | +| 6.5.4 | Solution Evaluation ..... | 40 | +| 6.6 | Solution #6 for Key Issue #3: Forwarding tunnel between source and target UL CL..... | 40 | +| 6.6.1 | Description ..... | 40 | +| 6.6.2 | Procedures ..... | 42 | +| 6.6.3 | Impacts on Existing Nodes and Functionality..... | 43 | +| 6.6.4 | Solution Evaluation ..... | 43 | +| 6.7 | Solution #7 for Key Issue #1: Replication framework in 3GPP System ..... | 44 | +| 6.7.1 | Description ..... | 44 | +| 6.7.2 | Procedures ..... | 46 | +| 6.7.2.1 | Downlink User Plane Transmission ..... | 46 | +| 6.7.2.2 | Activate Redundant Transmission during PDU Session Establishment procedure..... | 46 | +| 6.7.3 | Impacts on Existing Nodes and Functionality..... | 47 | +| 6.7.4 | Solution Evaluation ..... | 47 | +| 6.8 | Solution #8 for Key Issue #4: QoS Monitoring ..... | 47 | +| 6.8.1 | Description ..... | 47 | +| 6.8.1.1 | QoS Monitoring Activation ..... | 47 | +| 6.8.1.2 | Enforce QoS Monitoring ..... | 48 | +| 6.8.1.2.1 | Option 1: Using newly defined packet as monitoring packets..... | 48 | +| 6.8.1.2.2 | Option 2: Using actual service packets as monitoring packets..... | 49 | +| 6.8.1.2.3 | Option 3: Using newly defined packets based on time synchronization..... | 50 | +| 6.8.1.2.4 | Option 4: Using actual service packets based on time synchronization ..... | 50 | +| 6.8.1.3 | QoS Monitoring Policy..... | 51 | +| 6.8.2 | Procedures ..... | 51 | +| 6.8.2.1 | QoS Monitoring Procedure..... | 51 | +| 6.8.2.2 | QoS Monitoring Event Report by UPF..... | 53 | +| 6.8.3 | Impacts on Existing Nodes and Functionality..... | 53 | +| 6.8.4 | Solution Evaluation ..... | 54 | +| 6.9 | Solution #9 for Key Issue 5, supporting low latency for initial data delivery without requiring that the UE to always be in RRC_Connected State ..... | 54 | +| 6.9.1 | Description ..... | 54 | +| 6.9.2 | Procedures ..... | 55 | +| 6.9.3 | Impacts on Existing Nodes and Functionality..... | 56 | +| 6.9.4 | Solution Evaluation ..... | 56 | +| 6.10 | Solution #10 for Key Issue #1: Multiple UEs per device for user plane redundancy with broadcast Network Reliability Group..... | 56 | +| 6.10.1 | Description ..... | 56 | +| 6.10.2 | Procedures ..... | 57 | +| 6.10.3 | Impacts on Existing Nodes and Functionality..... | 57 | +| 6.10.4 | Solution Evaluation ..... | 57 | +| 6.11 | Solution #11 for Key Issue #3: Anchor change for Ethernet PDU Session..... | 58 | +| 6.11.1 | Description ..... | 58 | +| 6.11.2 | Procedures ..... | 59 | +| 6.11.3 | Impacts on Existing Nodes and Functionality..... | 61 | +| 6.11.4 | Solution Evaluation ..... | 62 | +| 6.12 | Solution #12 for Key Issue #3: Ethernet PDU Session Anchor Relocation..... | 62 | +| 6.12.1 | Description ..... | 62 | +| 6.12.2 | Procedures ..... | 63 | +| 6.12.3 | Impacts on Existing Nodes and Functionality..... | 64 | +| 6.12.4 | Solution Evaluation ..... | 65 | +| 6.13 | Solution #13 for Key Issue #3: Session continuity enhancement based on the coordination between AF and 5GC..... | 65 | +| 6.13.1 | General Description..... | 65 | +| 6.13.2 | Procedures ..... | 66 | + +| | | | +|----------|----------------------------------------------------------------------------------------------------------------|----| +| 6.13.2.1 | Procedure of Enhancing SSC mode 3 PDU Session Anchor Change with Multiple PDU Sessions ..... | 66 | +| 6.13.2.2 | Procedure of Session Continuity Enhancement for a PDU Session with UL/CL or BP ..... | 67 | +| 6.13.2 | Impacts on Existing Nodes and Functionality..... | 68 | +| 6.13.3 | Solution Evaluation ..... | 69 | +| 6.14 | Solution #14 for Key Issue #2: Lossless handover by timing coordination with multiple UEs per device ..... | 69 | +| 6.14.1 | Description ..... | 69 | +| 6.14.2 | Procedures ..... | 70 | +| 6.14.3 | Impacts on Existing Nodes and Functionality..... | 70 | +| 6.14.4 | Solution Evaluation ..... | 70 | +| 6.15 | Solution #15 for Key Issue #6: Division of E2E PDB..... | 71 | +| 6.15.1 | Description ..... | 71 | +| 6.15.2 | Procedures ..... | 71 | +| 6.15.2.1 | PDB provisioning during PDU Session Establishment /Modification or Service Request procedure ..... | 71 | +| 6.15.3 | Impacts on Existing Nodes and Functionality..... | 72 | +| 6.15.4 | Solution Evaluation ..... | 72 | +| 6.16 | Solution #16 for Key Issue #7: Automatic GBR service recovery after handover ..... | 72 | +| 6.16.1 | Description ..... | 72 | +| 6.16.2 | Procedures ..... | 73 | +| 6.16.3 | Impacts on Existing Nodes and Functionality..... | 73 | +| 6.16.4 | Solution Evaluation ..... | 74 | +| 6.17 | Solution #17 for Key Issue #6: Configuration of CN PDB in NG-RAN ..... | 74 | +| 6.17.1 | Description ..... | 74 | +| 6.17.2 | Impacts on Existing Nodes and Functionality..... | 74 | +| 6.17.3 | Solution Evaluation ..... | 74 | +| 6.18 | Solution #18 for Key Issue #6: Deterministic solution based accurate time stamping of packets in downlink..... | 74 | +| 6.18.1 | Description ..... | 74 | +| 6.18.2 | Procedures ..... | 75 | +| 6.18.3 | Impacts on Existing Nodes and Functionality..... | 75 | +| 6.18.4 | Solution Evaluation ..... | 75 | +| 6.19 | Solution #19 for Key Issue #4: Using control plane procedure on Uu interface for QoS Monitoring ..... | 75 | +| 6.19.1 | Description ..... | 75 | +| 6.19.1.1 | QoS Monitoring ..... | 75 | +| 6.19.2 | Procedures ..... | 76 | +| 6.19.3 | Impacts on Existing Nodes and Functionality..... | 76 | +| 6.19.4 | Solution Evaluation ..... | 77 | +| 6.20 | Solution #20 for Key Issue #7: SMF starts the pending timer for the non-accepted GBR QoS flow ..... | 77 | +| 6.20.1 | Description ..... | 77 | +| 6.20.2 | Procedures ..... | 77 | +| 6.20.3 | Impacts on Existing Nodes and Functionality..... | 77 | +| 6.21 | Solution #21 for Key Issue #7: Extending notification control for QoS flow setup and handover ..... | 78 | +| 6.21.1 | Description ..... | 78 | +| 6.21.2 | Procedures ..... | 78 | +| 6.21.3 | Impacts on Existing Nodes and Functionality..... | 78 | +| 6.21.4 | Solution Evaluation ..... | 79 | +| 6.22 | Solution #22 for Key Issue #7: Automatic GBR service recovery after handover ..... | 79 | +| 6.22.1 | Description ..... | 79 | +| 6.22.2 | Procedures ..... | 79 | +| 6.22.2.1 | QNC request for GBR Service Recovery during handover..... | 79 | +| 6.22.2.2 | QNC request for GBR Service Recovery after handover ..... | 81 | +| 6.22.3 | Impacts on Existing Nodes and Functionality..... | 81 | +| 6.22.4 | Solution Evaluation ..... | 82 | +| 6.23 | Solution #23 for Key Issue #7: Always On control for URLLC GBR QoS Flow ..... | 82 | +| 6.23.1 | Description ..... | 82 | +| 6.23.2 | Procedures ..... | 83 | +| 6.23.3 | Impacts on Existing Nodes and Functionality..... | 83 | +| 6.23.4 | Solution Evaluation ..... | 83 | + +| | | | +|-----------------|------------------------------------------------------------------------------------------------------------------------|-----------| +| 6.24 | Solution #24 for Key Issues #4 and #6: Accumulated packet delay estimation for QoS monitoring and division of PDB..... | 83 | +| 6.24.0 | General ..... | 83 | +| 6.24.2 | Procedures ..... | 85 | +| 6.24.3 | Impacts on Existing Nodes and Functionality..... | 86 | +| 6.24.4 | Solution Evaluation ..... | 87 | +| 7 | Overall Evaluation ..... | 87 | +| 7.1 | Evaluation for key issue 3 ..... | 87 | +| 8 | Conclusions..... | 88 | +| 8.1 | Key Issue #1: Supporting high reliability by redundant transmission in user plane..... | 88 | +| 8.2 | Key Issue #3: Enhancement of Session Continuity during UE Mobility..... | 88 | +| 8.3 | Key Issue #5: Supporting low latency without requiring that the UE to always be in RRC_Connected Mode..... | 88 | +| 8.4 | Key Issue #6: Division of E2E PDB ..... | 88 | +| 8.5 | Key Issue #4: QoS Monitoring to Assist URLLC Service..... | 89 | +| 8.6 | Key Issue #2: Supporting low latency and low jitter during handover procedure ..... | 90 | +| Annex A: | Overview of IEEE TSN Frame Replication and Elimination for Reliability..... | 91 | +| Annex B: | A summary of the IETF DetNet activity ..... | 92 | +| Annex C: | Change history..... | 93 | + +# --- Foreword + +This Technical Report has been produced by the 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. + +# --- 1 Scope + +The objective of this Technical Report is to study and perform an evaluation of potential architecture enhancements for supporting URLLC services in 5G System (5GS). Specifically, the following aspects are covered: + +- Investigate the key issues for meeting the URLLC requirements on latency, jitter and reliability in 5G System as defined in TS 22.261 [5]. +- Study how to minimize the impacts of UE mobility to the latency and jitter between AN and CN, and within CN. +- Study how to realize transmission with reliability higher than the reliabilities of single user plane tunnel of N3 and N9 and NFs in the user plane path. +- Study how to monitor the QoS of the QoS flow with URLLC requirement. +- Study potential impacts to charging and policy control. + +# --- 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.501: "System Architecture for the 5G System". +- [3] 3GPP TS 23.502: "Procedures for the 5G System". +- [4] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System". +- [5] 3GPP TS 22.261: "Service requirements for the 5G system". +- [6] IEEE 802.1CB-2017: IEEE Standard for Local and metropolitan area networks--Frame Replication and Elimination for Reliability, . +- [7] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity". +- [8] ETSI GS MEC 003: "Mobile Edge Computing (MEC); Framework and Reference Architecture". +- [9] draft-ietf-detnet-architecture-06 (June 2018): "Deterministic Networking Architecture". +- [10] IEEE 802.1Q: "IEEE Standard for Local and metropolitan area networks -- Bridges and Bridged Networks". +- [11] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2". +- [12] 3GPP TS 38.420: "NG-RAN; Xn general aspects and principles". +- [13] 3GPP TS 38.415: "NG-RAN; PDU Session User Plane protocol". +- [14] 3GPP TS 23.734: "Study on 5GS Enhanced support of Vertical and LAN Services". +- [15] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements". +- [16] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services". + +[17] 3GPP TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|-------|---------------------------------------------------| +| C-TAG | Customer VLAN Tag | +| CU | Central Unit | +| DC | Dual Connectivity | +| DU | Distributed Unit | +| EDT | Early Data Transmission | +| FRER | Frame Replication and Elimination for Reliability | +| GARP | Gratuitous ARP | +| HRP | High Reliability Protocol | +| LLC | Low Latency Communication | +| MCG | Master Cell Group | +| MgNB | Master gNB | +| MO | Mobile Originated | +| M-RAN | Master RAN | +| MT | Mobile Terminated | +| NDP | Neighbor Discovery Protocol | +| NRG | Network Reliability Group | +| PDB | Packet Delay Budget | +| PDCP | Packet Data Convergence Protocol | +| QMP | QoS Monitoring Packet | +| RFSP | RAT/Frequency Selection Priority | +| RG | Reliability Group | +| RHF | Redundancy Handling Function | +| RNA | RAN Notification Area | +| RSN | Redundancy Sequence Number | +| RTT | Round-trip Time | +| SCG | Secondary Cell Group | +| SgNB | Secondary gNB | +| S-RAN | Secondary RAN | +| S-TAG | Service VLAN Tag | +| STP | Spanning Tree Protocol | +| TSN | Time Sensitive Network | +| URLLC | Ultra-Reliable and Low Latency Communication | +| URR | Usage Reporting | + +# --- 4 Architecture Assumptions + +The following architectural assumptions are applicable for all potential solutions: + +- 1) The 5GS defined in TS 23.501 [2] is used as the baseline network architecture for URLLC. +- 2) For QoS flows with low latency requirement, at least one user plane path between the application and UE that be able to satisfy the requirement for latency should exist in the network. + +3) For QoS flows with ultra-high reliability requirement, there is no assumption on whether each NF or connection segment is able to meet the reliability requirements. + +NOTE 1: For some QoS flows, there might be only one of the requirements on low latency and high reliability. + +NOTE 2: Interworking between 5GS and EPS is out of scope in this study. + +# --- 5 Key Issues + +## 5.1 Key Issue #1: Supporting high reliability by redundant transmission in user plane + +### 5.1.1 General description + +In order to ensure the high reliability which can hardly be achieved by single path on user plane, redundant transmission in 5GS may be supported. Depending on the condition of network deployment, e.g., which NFs or segments cannot meet the requirements of reliability, the redundant transmission may be applied on the user plane path between the UE and the network. The following aspects need to be studied for this key issue: + +- How to establish, modify or release multiple tunnels for redundant data transmission on N3 and N9. +- How to support handover procedure for PDU session using redundant transmission. +- How to ensure the multiple tunnels on N3, N6 and N9 for redundant transmission to be transferred over separate transport layer paths in case single transport layer path cannot support the reliability requirements. +- How to make decision on enabling redundant transmission or not for a specific QoS flow. +- How to replicate the data packets in UE/RAN/UPF, when needed. + +NOTE: This does not intend to study mechanism on air interface. + +- How to eliminate the replicates received from different paths in UE/RAN/UPF, when needed. +- Identify the impact to protocol stack of user plane to support redundant transmission. + +## 5.2 Key Issue #2: Supporting low latency and low jitter during handover procedure + +### 5.2.1 General description + +In current handover procedure defined in TS 23.502 [3], for the QoS flow that requires lossless handover, the direct /indirect data forwarding tunnel is used to forward packets from the source RAN node to the target RAN node. This forwarding tunnel introduces additional latency and jitter within RAN and CN. Furthermore, if no forwarding tunnel is used, the DL path will be interrupted during HO execution until the establishment of GTP-U tunnel towards the target RAN node finished. + +The optimization of handover procedure need to be considered to guarantee low latency and low jitter to the URLLC services. In this key issue, the following aspects will be studied: + +- How to fulfil URLLC requirement during UE handover procedure. + +## 5.3 Key Issue #3: Enhancement of Session Continuity during UE Mobility + +### 5.3.1 General Description + +This key issue focuses on enhancing session continuity while maintaining UP efficiency. The follow problems are to be studied. + +- How to enable runtime coordination between AF and 5GC for supporting application relocation without breaking upper layer session and service continuity. + +When application relocates to a new DNAI, N6 connection is re-established with the new DNAI. To support upper layer session and service continuity, application traffic should be routed over the new N6 connection only after it is fully ready. This requires the 5GC to know when the end of N6 connection in the DN is ready before it switches to the new N6 connection. In Rel-15, such runtime coordination is not supported yet. + +- How to handle ULCL relocation or PSA relocation (for SSC mode 3) for URLLC services, and how the traffic routing on N6 interface is fulfilled are FFS. + +NOTE: The solutions to this key issue should reuse, if possible, functions of the 5GC developed in Rel-15. + +## 5.4 Key Issue #4: QoS Monitoring to Assist URLLC Service + +### 5.4.1 General description + +For URLLC services, E2E stringent QoS requirements include very low latency and very high reliability. This poses some challenges to the 5G System as several factors could affect the E2E QoS performance such as wireless coverage, 3GPP network node (UPF/RAN/UE) resources, and transport network. + +The current 5GS QoS Notification Control is supported in 5G-AN to monitor the GBR QoS flow status in the 5G-AN. This mechanism only supports GBR monitoring may not be sufficient for E2E URLLC services where packet latency, jitter, packet loss parameters are the key requirements. + +In order to achieve requirements of URLLC services, the following aspects should be studied: + +- Study solutions for the specific UE with URLLC services to improve the monitoring of QoS, such as packet delay, jitter and packet error rate to assist to achieve URLLC services and identify the relevant NF(s) and entities (e.g. 5GC, third party AF). +- Study means to better control the monitoring of QoS for URLLC e.g. means whether or not to trigger the above solution(s). If triggered, how to use the exposed QoS monitoring result to fulfil the QoS requirement of the URLLC service when the threshold that required QoS of URLLC services will not be satisfied is reached. + +## 5.5 Key Issue #5: Supporting low latency without requiring that the UE to always be in RRC\_Connected Mode + +### 5.5.1 General description + +To efficient support event driven low latency scenarios, this key issue shall study ways to reduce usage of network radio resources and power consumption in the UE. This key issue shall include scenarios when the UE is able to avoid Connected Mode between low latency data transmissions. The specific areas we need to study is when: + +- the UE transitioning from RRC\_Inactive Mode to RRC\_Connected Mode under an NG RAN node that is different from the NG RAN node storing the UE context within the same RAN Notification Area (RNA). + +NOTE: Dependent of the solution, the main work is expected to be done in RAN WG but in this study the 5GC may need to indicate to RAN that this is an LLC PDU Session to allow RAN to handle it accordingly. + +## 5.6 Key Issue #6: Division of E2E PDB + +### 5.6.1 Description + +E2E PDB is composed of AN part delay and CN part delay. In Rel-15, the PDB received by NG-RAN is the end-to-end delay (from UE to anchor UPF), and there are notes under the table in clause 5.7.4 in TS 23.501 [2], which clarify the RAN can assume CN PDBs are fixed for different 5QIs. + +In different deployments, the delay between RAN nodes and PSA UPFs can be different. Currently the PDB is not considering the deployment variety. The key issue investigates if and how to flexibly differentiate CN PDB subtraction towards different PSA UPFs (e.g. DNs). + +## 5.7 Key Issue #7: Automatic GBR service recovery after handover + +### 5.7.1 General description + +When a machine needs a Guaranteed Bit Rate service, it is likely to need that quality level in order to do its job. Hence if the QoS level cannot be maintained (e.g. handover into a congested cell; temporary cell overload due to higher priority services; etc), the QoS level should be restored as soon as possible, and, without a storm of signalling messages. + +Release 15 5GC has partially solved this issue by introducing a "notification" mechanism that allows the core network to request the RAN to not release the radio bearer/QoS Flow when the QoS guarantee cannot be met, but, instead to notify the Core Network when the QoS drops, AND, when the RAN has restored the QoS level. This allows the controller of the machine (e.g. car/train) to adapt its behaviour (e.g. reduce speed) and ensures that the RAN continues to try to restore the QoS level while the device is in that cell. + +However, at Xn or N2 handover, the target RAN node applies admission control and if it cannot support the required GBR QoS, the target RAN node does not establish that QoS Flow. In such a case, if, e.g. due to movement of the UE, the source RAN node has no choice but to handover to that target RAN node, then the target RAN node will complete the handover but will NOT notify the CN if and when the GBR QoS can be supplied to that UE. + +As the machine needs to have its GBR service restored as soon as possible, the CN needs to repeatedly attempt to re-establish the GBR service. These re-attempts involve a considerable number of signalling messages, and are sent without any awareness of RAN congestion or potential link quality. + +This is an inadequate solution for any mobile "non-human device" that needs to maintain a GBR data link during mobility (e.g. a car, a train, robots moving around a factory). + +# --- 6 Solutions + +## 6.1 Solution #1 for Key Issue #1: Redundant user plane paths based on dual connectivity + +### 6.1.1 Description + +The solution will enable a terminal device to set up two redundant PDU Sessions over the 5G network, so that the network will attempt to make the paths of the two redundant PDU sessions independent whenever that is possible. It is out of scope of this specific 3GPP solution to how to make use of the duplicate paths for redundant traffic delivery end-to-end. It is possible to rely on upper layer protocols, such as the IEEE TSN (Time Sensitive Networking) FRER (Frame Replication and Elimination for Reliability), to manage the replication and elimination of redundant packets/frames over the duplicate paths which can span both the 3GPP segments and possibly fixed network segments as well. Refer to Annex A for more details on how the IEEE TSN solution can make use of two independent networking paths. Other upper layer protocols, including IP based ones such as a DetNet based solution as described in Annex B, can also be possible for redundant packet transmission over multiple paths or for managing a backup path in addition to the active path. + +The overall solution is shown in the Figure below. The 3GPP network provides two paths from the device: the first PDU Session spans from the UE via gNB1 to UPF1 acting as the PDU Session Anchor, and the second PDU Session spans from the UE via gNB2 to UPF2 acting as the PDU Session Anchor. Based on these two independent PDU Sessions, two independent paths are set up, which may span even beyond the 3GPP network. In the example shown in the Figure below, we have two paths set up between Host A in the device and Host B, with some (optional) fixed intermediate nodes. The Redundancy Handling Function, RHF entities (out of 3GPP scope) that reside in Host A and Host B make use of the independent paths. The IEEE TSN FRER mentioned above is an example for a RHF. For Host A within the device, the two PDU Sessions appear as different networking interfaces, making the host multi-homed. Note that in the network side, other solutions are also possible, where redundancy spans only up to an intermediate node and not to the endhost. + +![Figure 6.1.1-1: High level architecture with single device. The diagram shows Host A (containing RHF and UE) connected to two gNBs (gNB1 and gNB2). gNB1 is connected to UPF1, which is connected to a Fixed node. gNB2 is connected to UPF2, which is connected to another Fixed node. Both Fixed nodes are connected to Host B (containing RHF).](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +graph LR + HostA[Host A] --- gNB1[gNB1] + HostA --- gNB2[gNB2] + gNB1 --- UPF1[UPF1] + gNB2 --- UPF2[UPF2] + UPF1 --- FixedNode1[Fixed node] + UPF2 --- FixedNode2[Fixed node] + FixedNode1 --- HostB[Host B] + FixedNode2 --- HostB[Host B] + +``` + +Figure 6.1.1-1: High level architecture with single device. The diagram shows Host A (containing RHF and UE) connected to two gNBs (gNB1 and gNB2). gNB1 is connected to UPF1, which is connected to a Fixed node. gNB2 is connected to UPF2, which is connected to another Fixed node. Both Fixed nodes are connected to Host B (containing RHF). + +**Figure 6.1.1-1: High level architecture with single device** + +This solution is based on the Dual Connectivity feature that is supported both by LTE and NR. The Figure 6.1.1-2 below illustrates the architecture view of the solution. A single UE has user plane connectivity with both a Master gNB (MgNB) and a Secondary gNB (SgNB). The RAN control plane and N1 are handled via the MgNB. The MgNB controls the selection of SgNB and the setup of the dual connectivity feature via the Xn interface. The UE sets up two PDU Sessions, one via MgNB to UPF1 acting as the PDU Session anchor, and another one via SgNB to UPF2 acting as the PDU session anchor. UPF1 and UPF2 connect to the same Data Network (DN), even though the traffic via UPF1 and UPF2 might be routed via different user plane nodes within the DN. UPF1 and UPF2 are controlled by SMF1 and SMF2, respectively, where SMF1 and SMF2 may coincide depending on operator configuration of the SMF selection. (Other 3GPP entities not relevant for this solution are not shown in the figure). + +![Figure 6.1.1-2: Solution architecture. The diagram shows a UE connected to an MgNB and an SgNB via an Xn interface. The MgNB is connected to an AMF (N2) and a UPF1 (N3). The SgNB is connected to a UPF2 (N3). The AMF is connected to SMF1 (N4) and SMF2 (N4). The UPF1 and UPF2 are connected to a DN (N6).](ddc7460821484f1ae2835c67955c554c_img.jpg) + +``` + +graph TD + UE[UE] --- MgNB[MgNB] + UE --- SgNB[SgNB] + MgNB --- Xn[Xn] --- SgNB + MgNB --- AMF[N2] + MgNB --- UPF1[N3] + SgNB --- UPF2[N3] + AMF --- SMF1[N4] + AMF --- SMF2[N4] + UPF1 --- DN[N6] + UPF2 --- DN[N6] + +``` + +Figure 6.1.1-2: Solution architecture. The diagram shows a UE connected to an MgNB and an SgNB via an Xn interface. The MgNB is connected to an AMF (N2) and a UPF1 (N3). The SgNB is connected to a UPF2 (N3). The AMF is connected to SMF1 (N4) and SMF2 (N4). The UPF1 and UPF2 are connected to a DN (N6). + +**Figure 6.1.1-2: Solution architecture** + +The solution differs from the RAN based PDCP packet duplication function (see TS 38.300 [11] clause 16.1.3) which is internal to RAN, and the packet duplication takes place between the UE and the MgNB. In this solution, the redundant paths span the whole system including RAN, CN, and can possibly extend to Data Network beyond 3GPP scope as well. + +The solution has a number of assumptions to be applicable. + +- RAN supports dual connectivity, and RAN coverage is sufficient for dual connectivity in the target area. +- UEs support dual connectivity. +- The core network UPF deployment is aligned with RAN deployment and supports redundant user plane paths. +- The underlying transport topology is aligned with the RAN and UPF deployment and supports redundant user plane paths. +- The physical network topology and geographical distribution of functions also supports the redundant user plane paths to the extent deemed necessary by the operator. +- The operation of the redundant user plane paths is made sufficiently independent, to the extent deemed necessary by the operator, e.g., independent power supplies. + +NOTE 1: The redundant network deployment aspects mentioned above are within the responsibility of the operator and are not subject to 3GPP standardization. + +Two options are provided for the selection of the UPFs and the gNBs. A static approach for UPF selection that takes place before the SgNB is selected in RAN; this is applicable to both IP based and Ethernet based PDU sessions. In addition, a dynamic approach for UPF selection, which enhances the Static approach taking into account the SgNB selected in RAN - this is applicable to Ethernet PDU Sessions. + +The solution is illustrated showing two SMFs, though the solution is also applicable using single SMF. The solution does not affect SMF selection, and the solution can be applied no matter whether the same or different SMFs are chosen, even though the existing mechanisms based on the DNN or S-NSSAI may be used to influence whether different SMFs are selected or whether the same SMF is selected. In case of two SMFs are used, the SMFs are aware the sessions are redundant (two distinct sessions). In case of multiple SMFs are used, the SMFs are configured to have different UPF pool in order to avoid reuse of same UPF by different SMFs. + +SMF(s) are aware of redundant sessions based on a new indication, Redundancy Sequence Number (RSN) provided by the UE in the PDU Session Establishment Request message. The presence of the RSN indicates redundant handling, and the value of the RSN indicates whether the first or the second PDU session is being established. As a fallback solution when the RSN is not provided by the UE, the SMF may also use the DNN or the S-NSSAI in combination with operator configuration to determine whether the first or second PDU session is being established for redundancy. The SMF uses the knowledge about whether the first or second PDU session is being established in combination with proper provisioning during UPF selection. + +#### Static approach: + +This applies to both IP and Ethernet PDU sessions. The solution is illustrated in the Figure below: + +![Diagram illustrating Static UPF selection. A UE is connected to an AMF. The AMF is connected to two SMFs, SMF1 and SMF2. SMF1 is connected to UPF1, and SMF2 is connected to UPF2. UPF1 and UPF2 are connected to a DN (Data Network). The diagram shows two PDU sessions: PDU Session 1 is established via the MgNB and UPF1, and PDU Session 2 is established via the SgNB and UPF2. The transition from PDU Session 1 to PDU Session 2 is labeled 'Before DC setup' and 'After DC setup'.](c036e2540a94b31357ceb0002f0cacab_img.jpg) + +The diagram shows a UE connected to an AMF. The AMF is connected to two SMFs, SMF1 and SMF2. SMF1 is connected to UPF1, and SMF2 is connected to UPF2. UPF1 and UPF2 are connected to a DN (Data Network). The diagram illustrates two PDU sessions: PDU Session 1 is established via the MgNB and UPF1, and PDU Session 2 is established via the SgNB and UPF2. The transition from PDU Session 1 to PDU Session 2 is labeled 'Before DC setup' and 'After DC setup'. + +Diagram illustrating Static UPF selection. A UE is connected to an AMF. The AMF is connected to two SMFs, SMF1 and SMF2. SMF1 is connected to UPF1, and SMF2 is connected to UPF2. UPF1 and UPF2 are connected to a DN (Data Network). The diagram shows two PDU sessions: PDU Session 1 is established via the MgNB and UPF1, and PDU Session 2 is established via the SgNB and UPF2. The transition from PDU Session 1 to PDU Session 2 is labeled 'Before DC setup' and 'After DC setup'. + +Figure 6.1.1-3: Static UPF selection + +- The UPF selection is based on existing mechanisms, with the extension that it is known in the SMF, based on UE indication of the RSN or network configuration based on the DNN or S-NSSAI, whether the UE is establishing the first or second PDU session. This information may be used as an input to the UPF selection. +- When the PDU Sessions are established, it is explicitly requested that RAN handles the first PDU Session at the MgNB and the second PDU Session at the SgNB using dual connectivity. +- Initially, the two PDU Sessions use the same MgNB, but as soon as dual connectivity is set up in RAN, the second PDU Session's user plane connection is moved to the SgNB, and the user plane tunnelling is switched to go via the SgNB. + +#### Dynamic approach: + +This applies to Ethernet PDU Sessions. The solution is illustrated in the Figure below: + +![Diagram illustrating Dynamic UPF Selection: anchor change after DC setup for Ethernet PDU Sessions. The diagram shows a UE connected to an AMF, which is connected to an SMF (SMF2). The SMF is connected to a UPF (UPF1). The UE is also connected to an MgNB and an SgNB. The MgNB is connected to the UPF (UPF2A) and the SgNB is connected to the UPF (UPF2B). The UPF (UPF2A) and the UPF (UPF2B) are connected to an ETH subnet. The diagram shows two PDU Sessions: PDU Session 1 and PDU Session 2. PDU Session 1 is established before DC setup, and PDU Session 2 is established after DC setup. The UPF (UPF2B) is updated with ETH forwarding information.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +The diagram illustrates the network architecture for dynamic UPF selection. At the top, three circles represent the AMF, SMF2 (with an 'ETH cntxt' label), and SMF1. Below them, a cloud represents the 'ETH subnet', containing three rectangular UPF blocks: UPF1, UPF2A (with an 'ETH cntxt' label), and UPF2B (with an 'ETH cntxt' label). On the left, a 'UE' block is connected to an 'AMF' block. The 'AMF' block is connected to both the 'SMF2' and 'SMF1' blocks. The 'UE' block is also connected to 'MgNB' and 'SgNB' blocks. The 'MgNB' block is connected to the 'UPF2A' block, and the 'SgNB' block is connected to the 'UPF2B' block. Two dashed lines represent PDU sessions: 'PDU Session 1' from the 'SMF2' to the 'UPF1' block, and 'PDU Session 2' from the 'SMF2' to the 'UPF2B' block. Text labels indicate 'Before DC setup' for the first session and 'After DC setup' for the second session. A yellow box at the bottom right of the subnet contains the text 'Update ETH forwarding'. + +Diagram illustrating Dynamic UPF Selection: anchor change after DC setup for Ethernet PDU Sessions. The diagram shows a UE connected to an AMF, which is connected to an SMF (SMF2). The SMF is connected to a UPF (UPF1). The UE is also connected to an MgNB and an SgNB. The MgNB is connected to the UPF (UPF2A) and the SgNB is connected to the UPF (UPF2B). The UPF (UPF2A) and the UPF (UPF2B) are connected to an ETH subnet. The diagram shows two PDU Sessions: PDU Session 1 and PDU Session 2. PDU Session 1 is established before DC setup, and PDU Session 2 is established after DC setup. The UPF (UPF2B) is updated with ETH forwarding information. + +**Figure 6.1.1-4: Dynamic UPF Selection: anchor change after DC setup for Ethernet PDU Sessions** + +- UPF selection for the first PDU Session and initial UPF selection for the second PDU session is based on existing mechanisms as described above for the Static approach. +- When dual connectivity is established and the SgNB is added in RAN for the second PDU Session, this may result in a change in the UPF acting as the PSA, using Solution #11 described in clause 6.11 on Anchor change for Ethernet PDU Sessions. + +The solution takes the following main steps. + +- The UE requests the establishment of a first and a second PDU Session. The UE also indicates the RSN in the PDU Session Establishment Request message; alternatively the UE uses different DNN and/or S-NSSAIs for the PDU Sessions so that the SMF can determine, considering operator configuration, whether the first or second PDU session is established. +- The SMF determines that the PDU Session establishment is for a redundant PDU Session. This determination may be based on the RSN indication from the UE, or it may be based on network configuration considering the DNN or the S-NSSAI. +- UPF selection can take into account the identity of the MgNB and also the information about whether the first or second PDU session is being established for redundancy for a given UE. The proper operator configuration of the UPF selection can ensure that the UPF selected for the first and second PDU Session are different, and that they are selected close to the MgNB. It is up to operator configuration to consider the independence of the paths also in the transport network. +- While the PDU Sessions are being established, dual connectivity handling of these PDU Sessions is not yet set up in RAN. When the two redundant PDU Sessions are initially established, both PDU Sessions go via the MgNB. The second PDU Session will be handed over to SgNB when the dual connectivity handling in RAN can be established. +- To enable a UE to send and receive frames with the same MAC address but different VLAN IDs in different PDU sessions to the same DNN, e.g. to allow for Redundancy Handling Functions like IEEE 802.1CB [6] (FRER) to ensure separate paths by means of IEEE 802.1Q [10] the following applies: +- In configurations where more than one PDU Session to the same DNN (e.g. for more than one UE) corresponds to the same N6 interface (see TS 23.501 [2] clause 5.16.10.2), the UPF acting as PDU session anchor (PSA) learns MAC addresses and VLAN IDs (S-TAG VID field and/or C-TAG VID fields depending on which tags are present in the frame) used by a UE in UL direction and uses the combination of VLAN ID and MAC address to determine the target PDU session for downlink switching of Ethernet frames; +- MAC address reporting mechanism from UPF to SMF and SMF to PCF/BSF is enhanced to also report VLAN IDs used by the UE to support session binding in presence of Ethernet frames tagged using IEEE 802.1Q [10]; +- The MgNB is informed by the SMF about the two PDU Sessions which need to be handled redundantly using the RSN. The SMF determines the RSN either based on the UE indication, or based on the DNN/S-NSSAI settings considering operator configuration. The SMF then provides the RSN to RAN via the AMF at user plane + +establishment for the PDU session. RSN=1 indicates that the given session is requested to be handled by the MgNB; RSN=2 indicates that the given session is requested to be handled by the SgNB. When there is at least one session with RSN=1 and at least one session with RSN=2 indicates to RAN that CN is requesting dual connectivity to be set up with the RSN=1 session(s) handled by MgNB and RSN=2 session(s) handled by SgNB. Based on the RSN indication, the MgNB sets up dual connectivity in such a way that both the MgNB and the SgNB have an independent PDCP entity for handling the two independent user plane paths (i.e. setup of MCG bearer and SCG bearer for MgNB and SgNB, respectively). The second PDU Session's user plane is switched to the SgNB, and in this way both the RAN node and the UPF can be different for the two redundant PDU Sessions. + +NOTE 2: The decision to set up dual connectivity remains in RAN as defined today. RAN takes into account the additional request for the dual connectivity setup provided by the CN. + +NOTE 3: There may also be other sessions for which redundancy is not applied and for which RSN is not set; RAN can select on its own whether those sessions are handled by MgNB or SgNB (or both), as today. Use of RSN values 1 and 2 also allows indication of which PDU Session is handled by MgNB and which is handled by SgNB. + +- In the case of Ethernet PDU Sessions, the SMF has the possibility to change the UPF (acting as the PSA) and select a new UPF based on the identity of the SgNB for the second PDU Session in case the SgNB is modified (or added/released) while the PDU Session remains established, according to Solution #11 described in clause 6.11. This makes it possible to dynamically select the UPF close to the SgNB for the second PDU Session, and in that way further optimize the second PDU Sessions UPF selection. +- The SMF sends the RSN to the PCF as part of the session parameters. This allows the PCF to configure different policy or charging rules for the two redundant PDU sessions. + +Regarding the mobility handling of the solution, it is important to separate the case whether mobility takes place below an unchanged PSA (PDU Session Anchor), or whether mobility involves the change of the PSA as well. + +- Mobility below unchanged PSA. This is supported by the solution; mobility below the PSA is hidden from external mechanisms handling the multiple end to end paths. Note however that handovers may introduce interruptions (though RAN mechanisms may reduce such interruptions). In case the SgNB is changed but the MgNB remains unchanged, the path via the MgNB remains uninterrupted though. Note also that the handovers may also lead to a change in the end to end delay. +- Mobility involving change of the PSA. This is the case with SSC mode 2 or SSC mode 3 procedures, or a change of the PSA for Ethernet PDU Sessions. A change of the PSA is possible, but we note that external mechanisms for setting up redundant paths, such as IEEE TSN FRER described in Annex A, would need to support the change of the PSA as well. Based on current IEEE TSN FRER specifications, support of PSA change is possible as long as the necessary configuration (such as VLAN configuration and resource reservation) along the new path is ensured. + +### 6.1.2 Procedures + +The setup of the two PDU Sessions and the subsequent establishment of dual connectivity takes place as follows in the static approach. + +![Sequence diagram illustrating the procedure based on a static approach for dual connectivity. The diagram shows four main steps: 1. Establish PDU Session 1, 2. Establish PDU Session 2, 3. Establish DC in RAN, and 4. Path switch for PDU Session 2. Lifelines involved are UE, MgNB, SgNB, UPF1, UPF2, AMF, SMF1, and SMF2. Step 1 shows UE sending a request to MgNB, which goes to AMF, then SMF1. SMF1 selects UPF1 and sends a response back through AMF to MgNB. User data for Session 1 is then shown being sent from UPF1 to MgNB. Step 2 is similar but for Session 2, with SMF2 selecting UPF2. Step 3 shows MgNB sending an SN Addition Request to SgNB, which responds with an SN Addition Request Ack. MgNB then sends an RRC Reconfig/RA to UE. Step 4 shows the path switch for Session 2, where user data for Session 2 is forwarded from MgNB to SgNB, and then to UPF2.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MgNB + participant SgNB + participant UPF1 + participant UPF2 + participant AMF + participant SMF1 + participant SMF2 + + Note right of SMF1: 1: Establish PDU Session 1 + UE->>MgNB: Request + MgNB->>AMF: Request + AMF->>SMF1: Request + SMF1->>UPF1: Select UPF1 + UPF1->>SMF1: Response + SMF1->>AMF: Response + AMF->>MgNB: Response + Note right of MgNB: User data + MgNB->>UPF1: User data + + Note right of SMF2: 2: Establish PDU Session 2 + UE->>MgNB: Request + MgNB->>AMF: Request + AMF->>SMF2: Request + SMF2->>UPF2: Select UPF2 + UPF2->>SMF2: Response + SMF2->>AMF: Response + AMF->>MgNB: Response + Note right of MgNB: User data + MgNB->>UPF2: User data + + Note right of MgNB: 3: Establish DC in RAN + MgNB->>SgNB: SN Addition Request + SgNB->>MgNB: SN Addition Request Ack + MgNB->>UE: RRC Reconfig/RA + Note right of MgNB: DL data forwarding + MgNB->>SgNB: DL data forwarding + Note right of MgNB: UL data + SgNB->>MgNB: UL data + + Note right of SMF2: 4: Path switch for PDU Session 2 + MgNB->>AMF: Request + AMF->>SMF2: Request + SMF2->>UPF2: Request + UPF2->>SMF2: Response + SMF2->>AMF: Response + AMF->>MgNB: Response + Note right of MgNB: User data + MgNB->>SgNB: User data + SgNB->>UPF2: User data + +``` + +Sequence diagram illustrating the procedure based on a static approach for dual connectivity. The diagram shows four main steps: 1. Establish PDU Session 1, 2. Establish PDU Session 2, 3. Establish DC in RAN, and 4. Path switch for PDU Session 2. Lifelines involved are UE, MgNB, SgNB, UPF1, UPF2, AMF, SMF1, and SMF2. Step 1 shows UE sending a request to MgNB, which goes to AMF, then SMF1. SMF1 selects UPF1 and sends a response back through AMF to MgNB. User data for Session 1 is then shown being sent from UPF1 to MgNB. Step 2 is similar but for Session 2, with SMF2 selecting UPF2. Step 3 shows MgNB sending an SN Addition Request to SgNB, which responds with an SN Addition Request Ack. MgNB then sends an RRC Reconfig/RA to UE. Step 4 shows the path switch for Session 2, where user data for Session 2 is forwarded from MgNB to SgNB, and then to UPF2. + +**Figure 6.1.2-1: Procedure based on static approach** + +1. PDU Session 1 is established according to TS 23.502 [3] clause 4.3.2.2. SMF1 determines based on the RSN provided by the UE, or based on the DNN or S-NSSAI and corresponding network configuration that the PDU Session is to be handled redundantly and this is the first PDU Session. SMF1 selects UPF1, where SMF1 may take into account in the selection that the current RAN node is MgNB and this is the first PDU session in the redundant handling. An indication is sent to RAN that this PDU Session is the first in the redundant handling that is requesting dual connectivity. +2. Similarly, PDU Session 2 is established according to TS 23.502 [3] clause 4.3.2.2. SMF2 determines based on the RSN provided by the UE, or based on the DNN or S-NSSAI and corresponding network configuration that the PDU Session is to be handled redundantly and this is the second PDU session. SMF2 selects UPF2, where SMF2 may take into account in the selection that the current RAN node is MgNB and this is the second PDU session in the redundant handling. An indication is sent to RAN that this PDU Session is the second in the redundant handling that is requesting dual connectivity. + +After step 2, the user plane of both PDU sessions still go via MgNB. + +3. If feasible based on RAN conditions as evaluated by the MgNB, dual connectivity is established in RAN according to TS 37.340 [7], clause 10.2.2. RAN should observe the requests sent in steps 1 and 2 and set up dual connectivity in such a way that the user plane of PDU Session 2 will be handled in SgNB as a SCG bearer, while the user plane of PDU Session 1 will be handled in the MgNB as a MCG bearer. As part of the dual connectivity setup, data forwarding can be started from MgNB to SgNB for the data of PDU Session 2. + +If dual connectivity is not possible to be set up in RAN as requested by the CN, then an appropriate indication is sent from RAN for both PDU Sessions via the AMF to the appropriate SMFs. The SMFs may decide whether to release the given PDU Sessions. + +- 4. The user plane path of PDU Session 2 is switched from MgNB to SgNB according to TS 23.502 [3] clause 4.9.1.2.2. + +As a result, the user plane of PDU Session 1 and PDU Session 2 now take independent paths both in RAN and in the CN. + +The dynamic approach for Ethernet PDU Sessions is illustrated in the figure below. + +![Sequence diagram illustrating the procedure based on dynamic approach for Ethernet PDU Sessions. The diagram shows five steps: 1. Establish PDU Session 1, 2. Establish PDU Session 2, 3. Establish DC in RAN, 4. Path switch with anchor change for PDU Session 2, and 5. Select UPF2B. Lifelines include UE, MgNB, SgNB, UPF1, UPF2A, UPF2B, AMF, SMF1, and SMF2. Solid arrows represent signaling, and dashed arrows represent user data flow.](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg) + +The diagram illustrates the dynamic approach for Ethernet PDU Sessions across five steps: + +- 1: Establish PDU Session 1**: UE sends a request to MgNB, which is forwarded to AMF. AMF selects UPF1 via SMF1. User data flows from UE to UPF1. +- 2: Establish PDU Session 2**: UE sends a request to MgNB, which is forwarded to AMF. AMF selects UPF2 via SMF2. User data flows from UE to UPF2A. +- 3: Establish DC in RAN**: MgNB sends an SN Addition Request to SgNB, which responds with an SN Addition Request Ack. RRC Reconfig/RA is sent to the UE. DL data forwarding and UL data flow between MgNB and SgNB. +- 4: Path switch with anchor change for PDU Session 2**: AMF initiates the path switch. UPF2B is selected via SMF2. User data flows from UE to SgNB and then to UPF2B. +- 5: Select UPF2B**: This step is part of the path switch procedure, where UPF2B is selected to handle the traffic. + +Sequence diagram illustrating the procedure based on dynamic approach for Ethernet PDU Sessions. The diagram shows five steps: 1. Establish PDU Session 1, 2. Establish PDU Session 2, 3. Establish DC in RAN, 4. Path switch with anchor change for PDU Session 2, and 5. Select UPF2B. Lifelines include UE, MgNB, SgNB, UPF1, UPF2A, UPF2B, AMF, SMF1, and SMF2. Solid arrows represent signaling, and dashed arrows represent user data flow. + +**Figure 6.1.2-2: Procedure based on dynamic approach** + +Steps 1-3 are as described above for the static approach. + +- 4. Path switch is performed in combination with an anchor change for PDU Session 2, which is performed according to the Anchor change for Ethernet PDU Sessions solution described in clause 6.11. + +### 6.1.3 Impacts on Existing Nodes and Functionality + +SMF impacts: + +- Determine, based on the UE indication of the RSN or based on the DNN or S-NSSAI and corresponding network configuration, whether a PDU session is to be handled redundantly. + +- Select UPF based on the identity of the MgNB and whether it is the first and second PDU session. +- Report not only MAC addresses but also VLAN IDs used by a UE from SMF to PCF; + +#### UPF impacts: + +- Support VLAN ID and MAC address learning in case of configurations and uses the combination of VLAN ID and MAC address to determine the target PDU session for downlink switching of Ethernet frames for configurations where more than one PDU Session to the same DNN (e.g. for more than one UE) corresponds to the same N6 interface (see TS 23.501 [2], clause 5.16.10.2). +- Report not only MAC addresses but also VLAN IDs used by a UE in UL frames to SMF. + +#### PCF/BSF impacts: + +- Support session binding based on MAC address and VLAN ID. + +#### RAN impacts: + +- Attempt to establish and maintain dual connectivity when the need for redundant user planes are indicated for a pair of PDU Sessions. +- Set up dual connectivity in such a way that both the MgNB and the SgNB have an independent PDCP entity for handling the two independent user plane paths. + +#### AMF impacts: + +- Forward the relevant indications between RAN and SMF. + +#### UE impacts: + +- Based on device configuration, trigger the setup of redundant PDU Session, with RSN or DNN/S-NSSAI setting indicating the need for redundant handling. +- An upper layer solution for the handling of the duplicate redundant paths with a corresponding configuration mechanism, both are out of 3GPP scope. Additionally, UE configuration mechanisms may be applied to trigger the establishment of duplicate PDU Sessions. + +### 6.1.4 Solution Evaluation + +- The solution can provide disjoint redundant user plane paths through the 3GPP system including RAN and CN. +- The solution uses IEEE FRER on upper layer between UE and DN. +- The solution does not impact the application itself, as replication can be performed by a networking protocol such as IEEE TSN FRER (see Annex A) which operates at an intermediate Ethernet switch or at the Ethernet layer of the endhost. Other protocols for replication are also applicable, such as DetNet (see Annex B) or proprietary protocols. +- The solution can be integrated with end to end redundancy solutions. +- The solution can provide the same level of redundancy as typically applied for fixed industrial deployments today. +- The solution requires already existing dual connectivity feature to be available. +- By reusing existing DC principle it is easy to deploy in the networks and terminals. +- The solution extends the dual connectivity by a CN trigger to request dual connectivity setup on a per session basis. +- The solution uses a single UE in the terminal, hence it does not provide redundant UEs. + +## 6.2 Solution #2 for Key Issue #1: Multiple UEs per device for user plane redundancy + +### 6.2.1 Description + +The solution will enable a terminal device to set up multiple redundant PDU Sessions over the 5G network, so that the network will attempt to make the paths of the multiple redundant PDU sessions independent whenever that is possible. It is out of scope of this specific 3GPP solution to how to make use of the multiple paths for redundant traffic delivery end-to-end. It is possible to rely on upper layer protocols, such as the IEEE TSN (Time Sensitive Networking), to manage the replication and elimination of redundant packets/frames over the multiple paths which can span both the 3GPP segments and possibly fixed network segments as well. Refer to Annex A for more details on how the IEEE TSN solution can make use of the independent networking paths. Other upper layer protocols, including IP based ones such as a DetNet based solution as described in Annex B, can also be possible for redundant packet transmission over multiple paths or for managing a backup path in addition to the active path. + +The solution is shown in the Figure below for the case when the terminal device is equipped with two UEs. The first PDU Session spans from the UE1 via gNB1 to UPF1, while the second PDU Session spans from the UE2 via gNB2 to UPF2. Based on these two independent PDU Sessions, two independent paths are set up, which may span even beyond the 3GPP network. In the example shown in the Figure below, we have two paths set up between Host A in the device and Host B, with some (optional) fixed intermediate nodes. The Redundancy Handling Function, RHF entities (out of 3GPP scope) that reside in Host A and Host B make use of the independent paths. The IEEE TSN FRER mentioned above is an example for a RHF. For Host A within the device, the two UEs provide different networking interfaces, making the host redundantly connected. Note that in the network side, other solutions are also possible, where redundancy spans only up to an intermediate node and not to the endhost. + +![Diagram illustrating the solution architecture with two UEs in a host. Host A (containing FRER) connects to two UEs, which connect to gNB1 and gNB2 respectively. gNB1 connects to UPF1, and gNB2 connects to UPF2. Both UPF1 and UPF2 connect to a Switch ch, which then connects to Host B (containing FRER).](e636d7ccca0ad14c6b95201404324823_img.jpg) + +``` +graph LR; subgraph HostA [Host A]; FRER_A[FRER]; UE1[UE]; UE2[UE]; end; subgraph HostB [Host B]; FRER_B[FRER]; end; HostA --> UE1 --> gNB1 --> UPF1 --> Switch[Switch ch]; HostA --> UE2 --> gNB2 --> UPF2 --> Switch; Switch --> HostB; +``` + +Diagram illustrating the solution architecture with two UEs in a host. Host A (containing FRER) connects to two UEs, which connect to gNB1 and gNB2 respectively. gNB1 connects to UPF1, and gNB2 connects to UPF2. Both UPF1 and UPF2 connect to a Switch ch, which then connects to Host B (containing FRER). + +Figure 6.2.1-1: Solution architecture with two UEs in a host + +This solution makes use of the integration of multiple UEs into the device, and assumes a RAN deployment where redundant coverage by multiple gNBs is generally available. Multiple PDU Sessions are set up from the UEs, which use independent RAN (gNB) and CN (UPF) entities. The Figure 6.2.1-2 below illustrates the architecture view of the solution. UE1 and UE2 are connected to gNB1 and gNB2, respectively and UE1 sets up a PDU Session via gNB1 to UPF1, and UE2 sets up a PDU Session via gNB2 to UPF2. UPF1 and UPF2 connect to the same Data Network (DN), even though the traffic via UPF1 and UPF2 might be routed via different user plane nodes within the DN. UPF1 and UPF2 are controlled by SMF1 and SMF2, respectively. (Other 3GPP entities not relevant for this solution are not shown in the figure). + +![Figure 6.2.1-2: Solution architecture mapped into 3GPP. The diagram shows a network architecture with two User Equipment (UE) units, UE1 and UE2, connected to a gNB1 and gNB2 respectively. These gNBs are connected to AMF1 and AMF2. AMF1 and AMF2 are connected to SMF1 and SMF2. SMF1 and SMF2 are connected to UPF1 and UPF2. UPF1 and UPF2 are connected to a Data Network (DN). The diagram also shows various interfaces: N1 (UE to AMF), N2 (gNB to AMF), N3 (gNB to UPF), N4 (SMF to UPF), N5 (AMF to SMF), and N6 (UPF to DN).](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +graph TD + subgraph Device + UE1[UE1] + UE2[UE2] + end + UE1 -- N1 --> AMF1[AMF1] + UE2 -- N1 --> AMF2[AMF2] + gNB1[gNB1] -- N2 --> AMF1 + gNB2[gNB2] -- N2 --> AMF2 + gNB1 -- N3 --> UPF1[UPF1] + gNB2 -- N3 --> UPF2[UPF2] + AMF1 -- N5 --> SMF1[SMF1] + AMF2 -- N5 --> SMF2[SMF2] + SMF1 -- N4 --> UPF1 + SMF2 -- N4 --> UPF2 + UPF1 -- N6 --> DN[DN] + UPF2 -- N6 --> DN + +``` + +Figure 6.2.1-2: Solution architecture mapped into 3GPP. The diagram shows a network architecture with two User Equipment (UE) units, UE1 and UE2, connected to a gNB1 and gNB2 respectively. These gNBs are connected to AMF1 and AMF2. AMF1 and AMF2 are connected to SMF1 and SMF2. SMF1 and SMF2 are connected to UPF1 and UPF2. UPF1 and UPF2 are connected to a Data Network (DN). The diagram also shows various interfaces: N1 (UE to AMF), N2 (gNB to AMF), N3 (gNB to UPF), N4 (SMF to UPF), N5 (AMF to SMF), and N6 (UPF to DN). + +**Figure 6.2.1-2: Solution architecture mapped into 3GPP** + +The solution has a number of assumptions to be applicable. + +The solution uses separate gNBs to achieve user plane redundancy over the 3GPP system. It is however up to operator deployment and configuration whether separate gNBs are available and used. If separate gNBs are not available for a device, the solution may still be applied to provide user plane redundancy in the rest of the network as well as between the device and the gNB using multiple UEs. + +- Terminal devices integrate multiple UEs which can connect to different gNBs independently. +- RAN coverage is redundant in the target area: it is possible to connect to multiple gNBs from the same location. To ensure that the two UEs connect to different gNBs, the gNBs need to operate such that the selection of gNBs can be distinct from each other (e.g. gNBs operating in different frequencies etc.). +- The core network UPF deployment is aligned with RAN deployment and supports redundant user plane paths. +- The underlying transport topology is aligned with the RAN and UPF deployment and supports redundant user plane paths. +- The physical network topology and geographical distribution of functions also supports the redundant user plane paths to the extent deemed necessary by the operator. +- The operation of the redundant user plane paths is made sufficiently independent, to the extent deemed necessary by the operator, e.g., independent power supplies. + +NOTE 1: The redundant network deployment aspects mentioned above are within the responsibility of the operator and are not subject to 3GPP standardization. + +The solution comprises the following main components. + +- gNB selection: The selection of different gNBs for the UEs in the same device is realized by defining UE Reliability Groups (RG) for the UEs and also for the cells of gNBs. By grouping the UEs in the device and cells of gNBs in the network into more than one reliability group and preferably selecting cells in the same reliability group as the UE, it is ensured that UEs in the same device can be assigned different gNBs for redundancy as illustrated in Figure 6.2.1-3 below, where UE1 and the cells of gNB1 belong to reliability group A, and UE2 and the cells of gNB2 belong to reliability group B. + +![Diagram illustrating the reliability group-based redundancy concept in RAN. A device contains two UEs (UE1 and UE2) connected to gNB1 and gNB2 respectively. gNB1 is part of Reliability Group A and gNB2 is part of Reliability Group B. Both gNBs are connected to AMF1 and AMF2 via N2 interfaces. AMF1 and AMF2 are connected to SMF1 and SMF2 via N4 interfaces. SMF1 and SMF2 are connected to UPF1 and UPF2 via N3 interfaces. UPF1 and UPF2 are connected to DN via N6 interfaces. The diagram shows that each UE is connected to a specific gNB, which is then connected to a specific UPF, which is then connected to the DN. The reliability groups are indicated by dashed boxes around the UEs and gNBs.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +graph TD + subgraph Device + UE1[UE1] --- gNB1[gNB1] + UE2[UE2] --- gNB2[gNB2] + subgraph ReliabilityGroupA [Reliability Group A] + gNB1 + end + subgraph ReliabilityGroupB [Reliability Group B] + gNB2 + end + end + gNB1 -- N2 --> AMF1[AMF1] + gNB2 -- N2 --> AMF2[AMF2] + AMF1 -- N4 --> SMF1[SMF1] + AMF2 -- N4 --> SMF2[SMF2] + SMF1 -- N3 --> UPF1[UPF1] + SMF2 -- N3 --> UPF2[UPF2] + UPF1 -- N6 --> DN[DN] + UPF2 -- N6 --> DN + Namf --- AMF1 + Namf --- AMF2 + Nsmf --- SMF1 + Nsmf --- SMF2 + +``` + +Diagram illustrating the reliability group-based redundancy concept in RAN. A device contains two UEs (UE1 and UE2) connected to gNB1 and gNB2 respectively. gNB1 is part of Reliability Group A and gNB2 is part of Reliability Group B. Both gNBs are connected to AMF1 and AMF2 via N2 interfaces. AMF1 and AMF2 are connected to SMF1 and SMF2 via N4 interfaces. SMF1 and SMF2 are connected to UPF1 and UPF2 via N3 interfaces. UPF1 and UPF2 are connected to DN via N6 interfaces. The diagram shows that each UE is connected to a specific gNB, which is then connected to a specific UPF, which is then connected to the DN. The reliability groups are indicated by dashed boxes around the UEs and gNBs. + +**Figure 6.2.1-3: Reliability group-based redundancy concept in RAN** + +For determining the reliability grouping of a UE, one of the following methods or a combination of them can be used: + +- It could be configured explicitly to the UE and sent in a Registration Request message to the network using an existing parameter (such as an S-NSSAI in the Requested NSSAI where the SST is URLLC) or a new parameter. +- It could be part of the subscription. +- It could also be derived from other system parameters (e.g., SUPI, PEI, S-NSSAI, RFSP) based on operator configuration. + +The Reliability Group of each UE is sent from AMF to RAN when the RAN context is established, and maintained as part of the RAN context, so each gNB has knowledge about the reliability group of the connected UEs. + +NOTE 2: Whether the UE RG parameter sent to RAN is defined as a new parameter or encoded into the already existing RFSP parameter can be determined as part of stage 3 work. + +The reliability group of the RAN (cells of gNBs) entities are pre-configured by the O&M system in RAN. It is possible for gNBs to learn the reliability group neighbouring cells as the Xn connectivity is set up. + +In the case of connected mode mobility, the serving gNB down-prioritizes candidate target cells that belong to different reliability group than the UE. It follows that normally the UE is handed over only to cells in the same reliability group. If cells in the same reliability group are not available (UE is out of the coverage of cells of its own reliability group or link quality is below a given threshold) the UE may be handed over to a cell in another reliability group as well. + +In case the UE connects to a cell in the wrong reliability group, the gNB initiates a handover to a cell in the appropriate reliability group whenever such a suitable cell is available. + +If redundant RAN coverage is available at a certain location, then UEs that belong to the same terminal device will connect to different gNBs based on the reliability group classification using the connected mode mobility scheme described above. + +If no cells in the same reliability group as the UE is available, then the UE may connect to a cell in another RGs. + +- Selection of different UPFs for the individual UEs within the device. Existing mechanisms can be used to select different UPFs for the two UEs. The selection may be based either on UE configuration or network configuration of different DNNs, or different slices for the two UEs. Optionally, it may also be possible to use the UE's RG, described above, as an input to the UPF selection. +- The solution may also apply different control plane entities for the individual UEs within the device, even though this is optional and not necessary for the key issue. This may be achieved by using: + - different (possibly decorated) DNNs for the individual UEs within the device to select different SMFs, + +- or applying different slices for the individual UEs within the device either based on UE configuration or network subscription, to select different AMFs and/or SMFs, +- or selecting different PLMNs (within single Operator) for the individual UEs within the device. As operators may have limited possibilities for assigning new PLMN numbers, this case may be difficult to apply in practice. Should an operator deploy networks with multiple PLMN numbers, it is up to current PLMN selection mechanisms to manage UE mobility and coordinated PLMN selection in such deployments. The solution does not introduce new mechanisms for the handling of such deployments. Current described solution is based on both PDU sessions by the two UEs belonging to single PLMN and operator's network configuration ensuring that the two UEs select two different entities in the network. +- To enable a UE to send and receive frames with the same MAC address but different VLAN IDs in different PDU sessions to the same DNN, e.g. to allow for Redundancy Handling Functions like IEEE 802.1CB [6] (FRER) to ensure separate paths by means of IEEE 802.1Q [10] the following applies: +- in configurations where more than one PDU Session to the same DNN (e.g. for more than one UE) corresponds to the same N6 interface (see TS 23.501 [2] clause 5.16.10.2), the UPF acting as PDU session anchor (PSA) learns MAC addresses and VLAN IDs (S-TAG VID field and/or C-TAG VID fields depending on which tags are present in the frame) used by a UE in UL direction and uses the combination of VLAN ID(s) and MAC address to determine the target PDU session for downlink switching of Ethernet frames; +- MAC address reporting mechanism from UPF to SMF and SMF to PCF/BSF is enhanced to also report VLAN IDs used by the UE to support session binding in presence of Ethernet frames tagged using IEEE 802.1Q [10]; +- The UEs belonging to the same terminal device request the establishment of PDU Sessions that use independent RAN and CN network resources using the mechanisms outlined above. +- The proper operator configuration of the UPF selection can ensure that the path of the PDU Sessions of UE1 and UE2 are independent. + +Regarding mobility handling of the multiple UEs, the solution defined in Solution #14 to Key Issue#2 achieves co-ordination of the handovers of the UEs so that packet losses during handover can be avoided. + +Regarding the mobility handling, it is important to separate the case whether mobility takes place below an unchanged PSA (PDU Session Anchor), or whether mobility involves the change of the PSA as well. + +- Mobility below unchanged PSA. This is supported by the solution; mobility below the PSA is hidden from external mechanisms handling the multiple end to end paths. Note that handovers may lead to a change in the end to end delay. +- Mobility involving change of the PSA. This is the case with SSC mode 2 or SSC mode 3 procedures, or a change of the PSA for Ethernet PDU Sessions. A change of the PSA is possible, but we note that external mechanisms for setting up redundant paths, such as IEEE TSN FRER described in Annex A, would need to support the change of the PSA as well. Based on current IEEE TSN FRER specifications, support of PSA change is possible as long as the necessary configuration (such as VLAN configuration and resource reservation) along the new path is ensured. + +### 6.2.2 Procedures + +- The UE can optionally provide its UE RG (Reliability Group) in the Registration Request message, either using a newly defined parameter, or using an existing parameter such as an S-NSSAI of the Requested NSSAI. +- The UE RG may also be part of the subscription. +- Based on the combination of the above information and possible local configuration, the AMF determines the UE RG and stores it in the UE Context. +- When the UE transitions to connected state, the UE RG is sent to RAN and will be maintained in the RAN context of the UE. + +RAN has its own RAN RG parameter configured into the gNBs on a per cell basis. gNBs may be pre-configured with the RAN RG parameter of the neighbouring cells or may learn that information. + +The RAN connected mode mobility handling is extended as follows. + +- RAN node down-prioritizes handover targets for a UE to cells whose RG is different from the UE RG. +- In case the UE connects to a cell in the wrong reliability group (i.e., UE RG is different from the RAN RG), the gNB initiates a handover to the appropriate reliability group when a suitable gNB is available as a handover target. + +In case of an idle UE, it is possible to use the existing cell (re-)selection priority mechanism, with a priori UE config using dedicated signalling (in the *RRCConnectionRelease* message during transition from connected to idle mode) to configure the UE to reselect the cells of the appropriate reliability group for camping in deployments where the cell reliability groups use different sets of frequencies. + +Existing mechanisms are used select different UPFs for the two UEs. The selection may be based either on UE configuration or network configuration of different DNNs, or different slices for the two UEs. Optionally, it may also be possible to use the UE's RG as an input to the UPF selection. + +The solution may be realized with or without standards changes to the signalling messages. + +- With standards changes, using new parameters. The following are added to existing signalling messages. + - A new parameter, UE RG, is added to the Registration Request message to indicate the UE's configured Reliability Group. + - The UE RG may also be part of the subscription. + - The UE RG, as determined by the AMF from the UE indication and possibly other information such as subscription or local configuration, is conveyed from the AMF to the SMF in the *Nsmf\_PDUSession\_Create\_SMContext* Request when the PDU Session is established so that the SMF can consider the information for UPF selection. + - The UE RG, as determined by the AMF, is sent to the RAN node when the RAN context is established during transition to connected mode. +- Without standards changes, using existing parameters. + - The UE's RG is set per the S-NSSAI, e.g. decided by the SD part, which is conveyed from the UE to the AMF, and is used for SMF selection, and also conveyed from the AMF to the SMF and is used for UPF selection. + - The UE's Allowed NSSAI is used as input to select the RFSP index value for the UE. The RAN node uses the RFSP for RRM purposes and can based on local configuration determine the UE's RG based on the S-NSSAI in Allowed NSSAI and/or S-NSSAI for the PDU Session(s). + +The benefit of avoiding standards changes is easier deployment. The benefit of adding standards changes is easier network operation (because we do not overload a single parameter with multiple meanings, creating a configuration burden), and better scalability (because a single parameter carrying multiple meanings may have a lot more values to interpret). + +### 6.2.3 Impacts on Existing Nodes and Functionality + +SMF impacts: + +- Determine, based on a combination of UE and network information, which PDU sessions to handle redundantly. +- Select UPF such that user plane redundancy is achieved. +- Report not only MAC addresses but also VLAN IDs used by a UE from SMF to PCF; + +UPF impacts: + +- Support VLAN ID and MAC address learning in case of configurations and uses the combination of VLAN ID and MAC address to determine the target PDU session for downlink switching of Ethernet frames for configurations where more than one PDU Session to the same DNN (e.g. for more than one UE) corresponds to the same N6 interface (see TS 23.501 [2] clause 5.16.10.2). + +- Report not only MAC addresses but also VLAN IDs used by a UE in UL frames to SMF. + +PCF/BSF impacts: + +- Support session binding based on MAC address and VLAN ID. + +RAN impacts: + +- O&M configuration of the RAN RGs on a per cell level. +- Prioritization of the handover of the UE to a cell whose RAN RG coincides with the UE RG, when such a suitable target cell is available. + +Subscription impacts: + +- In case such a new parameter is defined include the UE RG parameter. + +AMF impacts: + +- In case new parameters are defined, forward the relevant indications between RAN and SMF. +- Determine the UE RG to be sent to RAN (using new or existing parameter) based on one or more of UE indication, subscription information or local configuration based on other information elements. + +UE impacts: + +- Support of multiple UEs per device. +- Optional configuration of the UE RG for the UEs in the device. +- An upper layer solution for the handling of the multiple paths with a corresponding configuration mechanism, both are out of 3GPP scope. Additionally, UE configuration mechanisms may be applied to set the UE identification and trigger the establishment of the redundant PDU Sessions. + +### 6.2.4 Solution Evaluation + +- The solution can provide disjoint redundant user plane paths through the 3GPP system including RAN and CN. +- The solution depends on IEEE FRER on upper layer between UE and DN. +- The solution can provide the same level of redundancy as typically applied for fixed industrial deployments today. +- If desired by the operator, the solution can also be used for redundant control plane handling. +- The solution uses multiple UEs in the terminal, hence it also provides redundant UEs. +- The solution requires device manufacturers to integrate multiple UEs. + +## 6.3 Solution #3 for Key Issue #1: Supporting redundant data transmission via single UPF and two RAN nodes + +### 6.3.1 Description + +This solution addresses the KI#1 of How to "Supporting high reliability by redundant transmission in user plane". + +This solution focuses on how to realize the reliability of user plane between UPF and UE. For control plane network functions, the existing network device failure recovery mechanisms, e.g. N+1 resilience, should be enough to fulfil the high reliability requirements on control plane. Though the failover may cause a very short interrupt (typically on xx ms level), but this control plane failover will not impact the traffic routing on user plane. + +Typically telecom-level equipments are able to provide up to five-nine reliability. However, in many cases the end-to-end reliability of real deployed network might be lower than that considering the susceptible deployment environments, especially in the last-mile. + +To realize ultra-high reliability for URLLC services in the commercial deployed network, this solution proposes to use redundant transmission over different physical transport paths in CN and RAN to enhance the reliability of upper layer service. + +Whether redundant transmission need to be activated for a QoS Flow can be decided by the SMF based on local policies for the DNN and/or S-NSSAI, or by the PCF based on its QoS requirement, UE's subscription and condition of network deployment. + +**Editor's note:** It is FFS whether and how to coordinate with other redundancy mechanisms if such mechanisms were used in DN. + +**Editor's note:** It is FFS how the UE becomes aware which flows redundancy should be applied to. + +In this solution, it is assumed that the reliability of UPF and CP NFs are high enough to fulfill the reliability requirement of URLLC services served by these NFs, and the UE is under overlapping coverage of the two RAN nodes. The reliabilities of these NFs can be realized based on implementation (e.g. redundant mechanisms provided by NFV platform), which is out of scope of this solution. However a single RAN node cannot provide enough reliability in air interface for the QoS flow, so the redundant packets will be transferred between UPF and UE via two independent N3 tunnel and two RAN nodes to enhance the reliability of service. + +To ensure the two N3 tunnels can be transferred via disjointed transport layer paths, the M-RAN (Master RAN) node, SMF or UPF may provide different routing information in the tunnel information (e.g. different IP addresses or different Network Instances), and these routing information will be mapped to disjoint transport layer paths according to network deployment configuration. + +The redundant transmission is based on the DC architecture, except that same PDU is transferred via both M-RAN and S-RAN (Secondary RAN) nodes. With two different NG-RAN nodes, separate transport layer paths are used for redundant data transmission in user plane. + +![Figure 6.3.1-1: Redundant transmission with two N3 tunnels between a UPF and two NG-RAN nodes. The diagram shows a UE connected to two RAN nodes, M-RAN and S-RAN, which are connected to a UPF via separate N3 tunnels. The UPF is connected to a DN. The AMF is connected to the SMF, which is connected to the PCF. The AMF is also connected to the M-RAN via an N2 interface. The SMF is connected to the UPF via an N4 interface. The M-RAN and S-RAN are connected to each other via an Xn interface.](f1fbb1287d999c7034742de35bdab836_img.jpg) + +``` + +graph TD + UE[UE] --- MRAN[M-RAN] + UE --- SRAN[S-RAN] + MRAN --- Xn((Xn)) --- SRAN + MRAN -- N3 --> UPF[UPF] + SRAN -- N3 --> UPF + UPF -- N6 --> DN((DN)) + AMF[AMF] -- N11 --> SMF[SMF] + SMF -- N7 --> PCF[PCF] + AMF -- N2 --> MRAN + SMF -- N4 --> UPF + +``` + +Figure 6.3.1-1: Redundant transmission with two N3 tunnels between a UPF and two NG-RAN nodes. The diagram shows a UE connected to two RAN nodes, M-RAN and S-RAN, which are connected to a UPF via separate N3 tunnels. The UPF is connected to a DN. The AMF is connected to the SMF, which is connected to the PCF. The AMF is also connected to the M-RAN via an N2 interface. The SMF is connected to the UPF via an N4 interface. The M-RAN and S-RAN are connected to each other via an Xn interface. + +**Figure 6.3.1-1: Redundant transmission with two N3 tunnels between a UPF and two NG-RAN nodes** + +![Figure 6.3.1-2: Redundant transmission with two N3 and N9 tunnels between a UPF and two NG-RAN nodes. The diagram shows a UE connected to two RAN nodes, M-RAN and S-RAN, which are connected to intermediate UPFs (I-UPF) via N3 tunnels. These I-UPFs are then connected to a central UPF via N9 tunnels. The central UPF is connected to a DN. The AMF is connected to the SMF, which is connected to the PCF. The AMF is also connected to the M-RAN via an N2 interface. The SMF is connected to the central UPF via an N4 interface.](e05c1a13b44ab41505609d82b00cf4df_img.jpg) + +``` + +graph TD + UE[UE] --- MRAN[M-RAN] + UE --- SRAN[S-RAN] + MRAN -- N3 --> IUPF1[I-UPF] + SRAN -- N3 --> IUPF2[I-UPF] + MRAN --- Xn((Xn)) --- SRAN + IUPF1 -- N9 --> UPF[UPF] + IUPF2 -- N9 --> UPF + UPF -- N6 --> DN((DN)) + AMF[AMF] -- N11 --> SMF[SMF] + SMF -- N7 --> PCF[PCF] + AMF -- N2 --> MRAN + SMF -- N4 --> UPF + +``` + +Figure 6.3.1-2: Redundant transmission with two N3 and N9 tunnels between a UPF and two NG-RAN nodes. The diagram shows a UE connected to two RAN nodes, M-RAN and S-RAN, which are connected to intermediate UPFs (I-UPF) via N3 tunnels. These I-UPFs are then connected to a central UPF via N9 tunnels. The central UPF is connected to a DN. The AMF is connected to the SMF, which is connected to the PCF. The AMF is also connected to the M-RAN via an N2 interface. The SMF is connected to the central UPF via an N4 interface. + +**Figure 6.3.1-2: Redundant transmission with two N3 and N9 tunnels between a UPF and two NG-RAN nodes** + +In deployments where the M-RAN/S-RAN needs to connect to the anchor UPF via intermediate UPF nodes, one or two Intermediate UPFs (I-UPFs) may be inserted between the anchor UPF and the M-RAN/S-RAN nodes separately to support the redundant transmission with one or two N3 and N9 tunnels, as shown in figure 6.3.1-2. + +NOTE 1: The I-UPFs on the leg of the redundant paths shall not behave in an UL CL or Branching Point role anymore. + +For DL traffic, without changing sequence number in GTP-U packet, the two I-UPFs receive the traffic duplicated by the anchor UPF via N9 tunnels and without any further duplication forward them to the M-RAN and S-RAN via N3 tunnels separately. In case of UL traffic, by keeping sequence number in GTP-U packet unchanged, the two I-UPFs without any further duplication forward the traffic received from the M-RAN and S-RAN via N3 tunnels to the anchor UPF via N9 tunnels separately. + +![Figure 6.3.1-3: Redundant transmission with two NG-RAN nodes in HR roaming scenario. The diagram shows a UE connected to M-RAN and S-RAN. M-RAN and S-RAN are connected to I-UPF nodes via N3 tunnels. The I-UPF nodes are connected to a central UPF via N9 tunnels. The central UPF is connected to a DN (Data Network) via N6. The AMF is connected to the M-RAN and S-RAN via N2. The AMF is also connected to the V-SMF via N11. The V-SMF is connected to the H-SMF via N7. The V-SMF is also connected to the I-UPF nodes via N4. The V-PCF is connected to the AMF via N15. The H-PCF is connected to the H-SMF via N24. The diagram is divided into VPLMN and HPLMN by a dashed vertical line. The VPLMN contains the UE, M-RAN, S-RAN, I-UPF nodes, V-SMF, and V-PCF. The HPLMN contains the H-SMF, H-PCF, and the central UPF.](088921fa3f5a44c8551815122517eefd_img.jpg) + +Figure 6.3.1-3: Redundant transmission with two NG-RAN nodes in HR roaming scenario. The diagram shows a UE connected to M-RAN and S-RAN. M-RAN and S-RAN are connected to I-UPF nodes via N3 tunnels. The I-UPF nodes are connected to a central UPF via N9 tunnels. The central UPF is connected to a DN (Data Network) via N6. The AMF is connected to the M-RAN and S-RAN via N2. The AMF is also connected to the V-SMF via N11. The V-SMF is connected to the H-SMF via N7. The V-SMF is also connected to the I-UPF nodes via N4. The V-PCF is connected to the AMF via N15. The H-PCF is connected to the H-SMF via N24. The diagram is divided into VPLMN and HPLMN by a dashed vertical line. The VPLMN contains the UE, M-RAN, S-RAN, I-UPF nodes, V-SMF, and V-PCF. The HPLMN contains the H-SMF, H-PCF, and the central UPF. + +Figure 6.3.1-3: Redundant transmission with two NG-RAN nodes in HR roaming scenario + +As shown in figure 6.3.1-3, in home routed roaming scenario, the M-RAN/S-RAN nodes are connected to the anchor UPF in the HPLMN via two intermediate UPF nodes in the VPLMN separately to support redundant transmission with two N3 and N9 tunnels. The V-SMF selects the two intermediate UPFs and setup the redundant transmission tunnels on N3 and N9 in case it receive two CN tunnel info for a URLLC QoS flow from H-SMF. + +NOTE 2: Supporting the above HR redundant transmission requests two disjointed transport paths exist between the two I-UPFs and PSA UPF. + +### 6.3.1a User Plane Protocol Stack options + +#### 6.3.1a.1 Option 1: Enhancement of PDCP and GTP-U protocols + +In this option, PDCP protocol and GTP-U protocol are enhanced to support packet replication and elimination function. + +![Figure 6.3.1a.1-1: User Plane Protocol Stack - Option1. This diagram illustrates the protocol stack for User Plane traffic. On the left, the UE stack includes Application, PDU Layer, SDAP, PDCP, RLC, MAC, and L1. In the middle, the 5G-AN stack includes a 'Relay' block that splits traffic into two parallel paths: one with SDAP, PDCP, RLC, MAC, and L1; the other with GTP-U, UDP/IP, L2, and L1. These two paths converge at the N3 interface. On the right, the UPF stack includes PDU Layer, GTP-U, UDP/IP, L2, and L1, leading to the N6 interface. The diagram shows how the 5G-AN performs packet replication and elimination using the enhanced PDCP and GTP-U protocols.](803776dff64331076ffc951fc95358ee_img.jpg) + +Figure 6.3.1a.1-1: User Plane Protocol Stack - Option1. This diagram illustrates the protocol stack for User Plane traffic. On the left, the UE stack includes Application, PDU Layer, SDAP, PDCP, RLC, MAC, and L1. In the middle, the 5G-AN stack includes a 'Relay' block that splits traffic into two parallel paths: one with SDAP, PDCP, RLC, MAC, and L1; the other with GTP-U, UDP/IP, L2, and L1. These two paths converge at the N3 interface. On the right, the UPF stack includes PDU Layer, GTP-U, UDP/IP, L2, and L1, leading to the N6 interface. The diagram shows how the 5G-AN performs packet replication and elimination using the enhanced PDCP and GTP-U protocols. + +Figure 6.3.1a.1-1: User Plane Protocol Stack - Option1 + +In this option, it is required there is only one QoS Flow per DRB. + +**Editor's note:** It is FFS how the limitation of one QoS flow per DRB is known and enforced in RAN. It is FFS whether the limitation of one QoS flow per DRB imply also a limitation on the number of QoS flows, and if so, how is that limitation known in the core network? + +In this option, for DL traffic, the UPF replicates the packet received from the DN and includes the same sequence number in GTP-U headers of the replicates for the redundant transmission. When the M-RAN and S-RAN receive the packets from UPF, they set the DL PDCP sequence number of the PDCP packet according to the sequence number in the GTP-U headers received from UPF. With that, the two PDCP packets that UE received from M-RAN and S-RAN carries same PDCP sequence number, so that the UE can eliminate the duplicated packets at PDCP layer based on the PDCP sequence number. + +**NOTE:** The detail of how to map SNs between GTP-U and PDCP packets can be decided in stage 3. Each QoS Flow have an individual GTP-U SN space. One possible way is to reuse GTP-U extension header "PDCP PDU number" together with QFI to directly carry the PDCP sequence number per QoS Flow in the GTP-U packet. + +For UL traffic, the UE replicates the packet and assigns the same PDCP sequence number to them for the redundant transmission. One of these packets is transmitted to the M-RAN, and the other to the S-RAN. The sequence number in GTP-U header for the packet sent to the UPF is assigned by the M-RAN and S-RAN based on the PDCP sequence number received from UE. The UPF eliminates the duplicated packets at GTP-U layer based on the sequence number in GTP-U header. + +#### 6.3.1a.2 Option2: HRP protocol layer + +In this option, a HRP (High Reliability Protocol) layer is implemented on the UE and UPF to support packet replication and elimination function. + +![Figure 6.3.1a.2-1: User Plane Protocol Stack - Option2. The diagram shows the protocol stack for User Plane traffic across three entities: UE, 5G-AN, and UPF, separated by N3 and N6 interfaces. The stack layers from top to bottom are: Application, PDU Layer, HRP, SDAP, PDCP, RLC, MAC, and L1. In the 5G-AN, there is a 'Relay' box that splits traffic between SDAP and GTP-U. The UPF stack includes PDU Layer, HRP, GTP-U, UDP/IP, L2, and L1.](7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg) + +| | | | | +|-------------|-------|--------|-----------| +| Application | | | | +| PDU Layer | | | PDU Layer | +| HRP | | | HRP | +| SDAP | Relay | | GTP-U | +| PDCP | PDCP | GTP-U | UDP/IP | +| RLC | RLC | UDP/IP | L2 | +| MAC | MAC | L2 | L1 | +| L1 | L1 | L1 | | +| UE | 5G-AN | | UPF | + +N3                      N6 + +Figure 6.3.1a.2-1: User Plane Protocol Stack - Option2. The diagram shows the protocol stack for User Plane traffic across three entities: UE, 5G-AN, and UPF, separated by N3 and N6 interfaces. The stack layers from top to bottom are: Application, PDU Layer, HRP, SDAP, PDCP, RLC, MAC, and L1. In the 5G-AN, there is a 'Relay' box that splits traffic between SDAP and GTP-U. The UPF stack includes PDU Layer, HRP, GTP-U, UDP/IP, L2, and L1. + +**Figure 6.3.1a.2-1: User Plane Protocol Stack - Option2** + +In this option, for DL traffic, the UPF replicates the DL packet and assigns the same HRP sequence number to them for the redundant transmission. When the UE receives the replicates from M-RAN and S-RAN, it eliminates the duplicated packets at HRP layer based on the HRP sequence number. + +For UL traffic, the UE replicates the packet and assigns the same HRP sequence number to them for the redundant transmission. The UPF eliminates the duplicated packets at HRP layer based on the HRP sequence number. + +**NOTE:** In this option, the HRP layer may cause additional delay for internal handlings within UE and UPF. + +### 6.3.2 Procedures + +#### 6.3.2.1 Activate Redundant Transmission during PDU Session Establishment procedure + +The redundant transmission will be established during a PDU Session establishment procedure or a PDU Session Modification procedure. + +Figure 6.3.2.1-1 depicts the establishment of redundant transmission during the PDU session establishment procedure in the non-roaming and roaming with local breakout cases. + +![Sequence diagram showing the activation of redundant transmission during PDU session establishment. The diagram involves eight participants: UE, Master NG-RAN, Secondary NG-RAN (dashed box), AMF, UPF, SMF, UDM, and PCF. The sequence is divided into three main parts: 1. Steps 1-12 of UE requested PDU Session Establishment in clause 4.3.2.2.1 in TS 23.502; 2. Secondary NG-RAN Addition procedure (enclosed in a dashed box); 3. Steps 14-20 of UE requested PDU Session Establishment in clause 4.3.2.2.1 in TS 23.502.](474a819357587e34949a3e110ff19b30_img.jpg) + +Sequence diagram showing the activation of redundant transmission during PDU session establishment. The diagram involves eight participants: UE, Master NG-RAN, Secondary NG-RAN (dashed box), AMF, UPF, SMF, UDM, and PCF. The sequence is divided into three main parts: 1. Steps 1-12 of UE requested PDU Session Establishment in clause 4.3.2.2.1 in TS 23.502; 2. Secondary NG-RAN Addition procedure (enclosed in a dashed box); 3. Steps 14-20 of UE requested PDU Session Establishment in clause 4.3.2.2.1 in TS 23.502. + +**Figure 6.3.2.1-1: Activate Redundant Transmission during PDU Session Establishment procedure** + +1. Steps 1-12 from clause 4.3.2.2.1(UE requested PDU Session Establishment) in TS 23.502 [3] are performed with the following differences: + +In step 7b, the PCF indicates the SMF and the NG-RAN to activate redundant transmission for the QoS flow by the 5QI if the UE requested PDU Session Establishment procedure is initiated for a URLLC service. + +In step 10, the SMF then initiates an N4 Session Establishment procedure with the selected UPF and CN Tunnel Info 1& CN Tunnel Info 2 are allocated by the SMF or UPF. + +In step 11, the N2 SM information includes the QFI(s), QoS Profile(s), CN Tunnel Info 1& CN Tunnel Info 2 corresponding to each N3 tunnel. + +2. RRC Connection Reconfiguration takes place with the UE establishing the necessary NG-RAN resources related to the QoS Rules for the PDU Session request. The Secondary NG-RAN node Addition procedure is performed as defined in TS 37.340 [7]. + +3. Steps 14-20 from clause 4.3.2.2.1(UE requested PDU Session Establishment) in TS 23.502 [3] are performed with the following differences: + +The AN Tunnel Info provided by the NG-RAN includes AN Tunnel Info 1 and AN Tunnel Info 2. Each AN Tunnel Info includes a tunnel endpoint for each involved NG-RAN node, and the QFIs assigned to each tunnel endpoint. The M-RAN node assigns the appropriate CN tunnel information to each of the NG-RAN nodes. + +The SMF provides AN Tunnel Info 1 and AN Tunnel Info 2 to the UPF as well as the corresponding forwarding rules. The forwarding rules indicates the UPF to replicate the downlink packets and send each replicate via one of DL N3 tunnels separately to NG-RAN, and eliminate the duplicate uplink packets received from the two UL N3 tunnels. + +During the course of PDU Session Establishment procedure, in case N2 PDU Session Request message contains one CN Tunnel Info, based on radio resource, wireless conditions or local policy, if the NG-RAN may determine to send N2 PDU Session Failure Response to the SMF via the AMF with the cause indicating redundant transmission establishment. Considering it, the SMF may initiates redundant transmission with two CN Tunnel Info, or the SMF may report subscribed event to the PCF, it is up to the PCF to determine whether redundant transmission needs to be activated. + +NOTE: The above mechanism may apply to PDU Session Modification and mobility procedure. + +Editor's note: whether the NG-RAN can trigger the 5GC to initiate redundant transmission is FFS. + +#### 6.3.2.2 Activate Redundant Transmission during PDU Session Modification procedure + +Figure 6.3.2.2-1 depicts the establishment of redundant transmission during the UE or network requested PDU session modification procedure in the non-roaming and roaming with local breakout cases. + +![Sequence diagram showing the activation of redundant transmission during PDU Session Modification procedure. The diagram involves eight participants: UE, Master NG-RAN, Secondary NG-RAN (dashed box), AMF, UPF, SMF, UDM, and PCF. The sequence is divided into three horizontal sections: 1. Steps 1-4 of UE or network requested PDU Session Modification in clause 4.3.3.2 in TS 23.502; 2. Secondary NG-RAN Addition procedure (enclosed in a dashed box); 3. Steps 6-12 of UE or network requested PDU Session Modification in clause 4.3.3.2 in TS 23.502.](dd5771673aececa53d42ece89218299d_img.jpg) + +Sequence diagram showing the activation of redundant transmission during PDU Session Modification procedure. The diagram involves eight participants: UE, Master NG-RAN, Secondary NG-RAN (dashed box), AMF, UPF, SMF, UDM, and PCF. The sequence is divided into three horizontal sections: 1. Steps 1-4 of UE or network requested PDU Session Modification in clause 4.3.3.2 in TS 23.502; 2. Secondary NG-RAN Addition procedure (enclosed in a dashed box); 3. Steps 6-12 of UE or network requested PDU Session Modification in clause 4.3.3.2 in TS 23.502. + +**Figure 6.3.2.2-1: Activate Redundant Transmission during PDU Session Modification procedure** + +1. Steps 1-4 from clause 4.3.3.2 (UE or network requested PDU Session Modification) in TS 23.502 [3] are performed with the following differences: + +The PDU Session Modification procedure is triggered by the UE or the SMF to add a QoS flow for a URLLC service. + +In step 1b or step 2, the PCF indicates the SMF to activate redundant transmission for the QoS flow by the 5QI. + +The SMF initiates an N4 Session modification procedure with the UPF and a new CN Tunnel for redundant transmission may be allocated by the SMF or UPF. + +In step 4, the N2 SM information includes the QFI(s), QoS Profile(s) for each N3 tunnel, and the CN Tunnel Info corresponding to the new N3 tunnel. + +2. RRC Connection Reconfiguration takes place with the UE establishing the necessary NG-RAN resources related to the QoS Rules for the PDU Session request. The Secondary NG-RAN node Addition procedure can be performed as defined in TS 37.340 [7]. + +3. Steps 6-12 from clause 4.3.3.2 (UE or network requested PDU Session Modification) in TS 23.502 [3] are performed with the following differences: + +The AN Tunnel Info for the redundant transmission is provided by the NG-RAN. The AN Tunnel Info includes a tunnel endpoint for the NG-RAN node used for redundant transmission, and the QFIs assigned to the tunnel endpoint. + +The SMF provides AN Tunnel Info to the UPF as well as the corresponding forwarding rules. The forwarding rules indicates the UPF to replicate the downlink packets and send each replicate via one of DL N3 tunnels separately to NG-RAN, and eliminate the duplicate uplink packets received from the two UL N3 tunnels. + +#### 6.3.2.3 Handover procedure + +In this solution, the UE can connect to two NG-RAN nodes simultaneously when redundant transmission is used. Either the M-RAN node or the S-RAN node may perform handover at a time. + +In the case that the S-RAN node handover, the M-RAN Node will initiates a Secondary Node Change procedure as defined in TS 37.340 [7]. The transmission between UE and UPF via M-RAN node will not be impacted during the handover procedure. + +In the case that the M-RAN node handover, the Master Node handover without Secondary Node change procedure will be applied as defined in TS 37.340 [7]. The transmission between UE and UPF via S-RAN node will not be impacted during the handover procedure. + +In the case that both M-RAN node and S-RAN node handover, it follows the procedures defined in TS 37.340 [7]. + +### 6.3.3 Impacts on Existing Nodes and Functionality + +PCF: + +- The PCF can determine whether redundant transmission needs to be activated for a QoS Flow based on its QoS requirement, UE's subscription and condition of network deployment. + +AMF: + +- No impact in this solution. + +#### **SMF:** + +- The SMF can determine whether redundant transmission needs to be activated for a QoS Flow based on local policies for the DNN and/or S-NSSAI. +- In case the SMF allocates CN Tunnel Info, it shall provide the CN Tunnel Info for two tunnels of the redundant transmission paths. +- The SMF shall indicate the UPF to replicate the downlink packet and send the duplicate packets to the two N3 tunnels, and indicate the UPF to eliminate the duplicate uplink packets. + +#### **UPF:** + +- In case the UPF allocates CN Tunnel Info, it shall provide the CN Tunnel Info for two tunnels of the redundant transmission paths. +- The UPF shall be able to replicate the downlink packet and send the duplicate packets to the two N3 tunnels, and eliminate the duplicate uplink packets, based on either sequence numbering in GTP-U header (option 1) or a new protocol (option 2). + +#### **RAN:** + +- The RAN node shall support redundant transmission via DC architecture with two N3 tunnels. +- In case protocol stack option 1 is adopted, RAN need to ensure there is only one QoS Flow per DRB, and map or reuse PDCP SN and sequence number in GTP-U header. +- RAN needs to be able to combine dual connectivity setup with the establishment or modification of radio bearers within the session management procedures. + +#### **UE:** + +- The UE shall be able to replicate the uplink packets and eliminate the downlink packets for a URLLC service. +- The UE can determine whether to replicate the uplink packets for a QoS Flow based on its QoS profile. +- In case of option 1, UE needs to support a new variant of PDCP replication and elimination compared to the existing RAN PDCP duplication mechanism. +- In case of option 2, UE needs to support a new protocol for replication and elimination. + +### 6.3.4 Solution Evaluation + +This solution provides high reliability transporting mechanism by performing redundant transmission between Anchor UPF and UE via disjointed CN tunnels and two different RAN nodes. The solution has the following properties: + +- The solution provides the same level of redundancy on the air interface as the existing PDCP packet duplication function in Rel-15 (see TS 38.300 [11] clause 16.1.3). +- The solution avoids the MgNB being a single point of failure in the user plane. +- UPF is a single point of failure in the user plane. In case of UPF failure, the session is completely lost. +- The operator can control the activation of redundant transmission or not by PCC mechanism. +- This solution has no dependency on the protocol used in application layer, which is out of control of the operator. +- The redundant transmission can be activated on demand per QoS Flow but limits to single QoS Flow per DRB. +- Current existing PDU session/QoS Flow management mechanisms are reused in this solution with limited extensions shown in 6.3.3. No further impact on existing CN control plane mechanisms, however RAN is impacted by the need to be able to combine dual connectivity setup with the establishment or modification of radio bearers within the session management procedures. + +- If protocol stack option 1 is adopted, there is no additional replication protocol defined for the UE. If protocol stack option 2 is adopted, there is no additional replication protocol functionality for the RAN node. But interactions with existing Rel-16 RAN PDCP duplication is not investigated yet. + +## 6.4 Solution #4 for Key Issue #1: Supporting redundant data transmission via single UPF and single RAN node + +### 6.4.1 Description + +This solution addresses the KI#1 of How to "Supporting high reliability by redundant transmission in user plane". It focuses on the redundant transmission between RAN and UPF. + +In this solution, it is assumed that the reliability of NG-RAN node, UPF and CP NFs are high enough to fulfil the reliability requirement of URLLC services served by these NFs. The reliabilities of these NFs can be realized based on implementation (e.g. redundant mechanisms provided by NFV platform), which is out of scope of this solution. However, the reliability of single N3 tunnel is considered not high enough, e.g. due to the deployment environment of backhaul network, so the redundant packets will be transferred between UPF and RAN via two independent N3 tunnels, which are associated with a single PDU Session, over different transport layer path to enhance the reliability of service. + +To ensure the two N3 tunnels can be transferred via disjointed transport layer paths, the NG-RAN node, SMF or UPF will provide different routing information in the tunnel information (e.g. different IP addresses or different Network Instances), and these routing information will be mapped to disjoint transport layer paths according to network deployment configuration. + +This solution supports the redundant transmission based on two N3 tunnels between a single NG-RAN node and the UPF. The RAN node and UPF shall support the packet replication and elimination function. + +![Diagram illustrating redundant transmission with two N3 tunnels between the UPF and a single NG-RAN node. The diagram shows the following components and connections: UE connected to NG-RAN; NG-RAN connected to AMF via N2; AMF connected to SMF via N11; SMF connected to PCF via N7; SMF connected to UPF via N4; NG-RAN connected to UPF via two parallel N3 tunnels (N3 Tunnel 1 and N3 Tunnel 2); UPF connected to DN via N6.](80ec3bf791fd8eb41f73a420c2122529_img.jpg) + +``` + +graph LR + UE[UE] --- NG-RAN[NG-RAN] + NG-RAN -- N2 --> AMF[AMF] + AMF -- N11 --> SMF[SMF] + SMF -- N7 --> PCF[PCF] + SMF -- N4 --> UPF[UPF] + NG-RAN -- "N3 Tunnel 1" --> UPF + NG-RAN -- "N3 Tunnel 2" --> UPF + UPF -- N6 --> DN((DN)) + +``` + +Diagram illustrating redundant transmission with two N3 tunnels between the UPF and a single NG-RAN node. The diagram shows the following components and connections: UE connected to NG-RAN; NG-RAN connected to AMF via N2; AMF connected to SMF via N11; SMF connected to PCF via N7; SMF connected to UPF via N4; NG-RAN connected to UPF via two parallel N3 tunnels (N3 Tunnel 1 and N3 Tunnel 2); UPF connected to DN via N6. + +**Figure 6.4.1-1: Redundant transmission with two N3 tunnels between the UPF and a single NG-RAN node** + +Packet replication and elimination can be realized by modifying the GTP-U protocol. In case of DL traffic, the UPF replicates the packet from the DN and assigns the same GTP-U sequence number to them for the redundant transmission. These packets are transmitted to the NG-RAN via the N3 Tunnel 1 and the N3 Tunnel 2 separately. In order to eliminate the duplicated packet, the NG-RAN forwards the packet received first from either tunnel to the UE and drops the replicated packet which has the same GTP-U sequence number as the forwarded packet. + +In case of UL traffic, the NG-RAN replicates the packet and assigns the same GTP-U sequence number to them and the UPF eliminates the duplicated packet based on the GTP-U sequence number. + +One of the N3 Tunnels is determined as main transport path during the GTP-U tunnel establishment. For those QoS Flows of the same PDU session that don't need redundant transmission, this main N3 Tunnel is used. + +NOTE 1: The RAN node capability to support the solution can be configured in the SMF per network slice or per SMF service area. + +The solution can be extended by inserting two Intermediate UPFs (I-UPFs) between the UPF acting as the PDU Session Anchor and the NG-RAN to support the redundant transmission based on two N3 and N9 tunnels between a single NG-RAN node and the UPF. The RAN node and UPF shall support the packet replication and elimination function. + +![Figure 6.4.1-2: Two N3 and N9 tunnels between NG-RAN and UPF for redundant transmission. The diagram shows a UE connected to an NG-RAN. The NG-RAN is connected to an AMF via N2. The AMF is connected to an SMF via N11. The SMF is connected to a PCF via N7. The SMF is also connected to two intermediate UPFs (I-UPF1 and I-UPF2) via N4. The I-UPFs are connected to a UPF via N9 tunnels (N9 Tunnel 1 and N9 Tunnel 2). The UPF is connected to a DN via N6. The NG-RAN is also connected to the I-UPFs via N3 tunnels (N3 Tunnel 1 and N3 Tunnel 2).](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +Figure 6.4.1-2: Two N3 and N9 tunnels between NG-RAN and UPF for redundant transmission. The diagram shows a UE connected to an NG-RAN. The NG-RAN is connected to an AMF via N2. The AMF is connected to an SMF via N11. The SMF is connected to a PCF via N7. The SMF is also connected to two intermediate UPFs (I-UPF1 and I-UPF2) via N4. The I-UPFs are connected to a UPF via N9 tunnels (N9 Tunnel 1 and N9 Tunnel 2). The UPF is connected to a DN via N6. The NG-RAN is also connected to the I-UPFs via N3 tunnels (N3 Tunnel 1 and N3 Tunnel 2). + +**Figure 6.4.1-2 Two N3 and N9 tunnels between NG-RAN and UPF for redundant transmission** + +In figure 6.4.1.2, there are two N3 and N9 tunnels between NG-RAN and UPF for redundant transmission. The UPF interfacing the DN and acting as the Traffic Distributor for DL traffic duplicates the packet of the URLLC service from the DN and assigns the same GTP-U sequence number to them. These duplicated packets are transmitted to I-UPF1 and I-UPF2 via N9 Tunnel 1 and N9 Tunnel 2 separately. Each I-UPF forwards the packet with the same GTP-U sequence number which receives from the UPF to NG-RAN via N3 Tunnel 1 and N3 Tunnel 2 respectively. The NG-RAN eliminates the duplicated packet based on the GTP-U sequence number. In case of UL traffic, the NG-RAN acting as the Traffic Distributer for UL traffic duplicates the packet of the URLLC service for the UE and the UPF eliminates the duplicated packet. + +NOTE 2: The I-UPFs inserted on one leg of the redundant paths shall not behave in an UL CL or Branching Point role. + +![Figure 6.4.1-3: Redundant transmission with one NG-RAN node in HR roaming scenario. The diagram shows a UE connected to a RAN. The RAN is connected to an AMF via N2. The AMF is connected to a V-SMF via N11. The V-SMF is connected to a H-SMF via N7. The V-SMF is also connected to an I-UPF via N4. The I-UPF is connected to a UPF via N9 tunnels (N9 Tunnel 1 and N9 Tunnel 2). The UPF is connected to a DN via N6. The RAN is also connected to the I-UPF via N3 tunnels (N3 Tunnel 1 and N3 Tunnel 2). The diagram is divided into two sections: VPLMN (left) and HPLMN (right) by a dashed vertical line. The AMF is also connected to a V-PCF via N15, and the V-PCF is connected to an H-PCF via N24.](b904ac2472cab80892d1e783e6230d6e_img.jpg) + +Figure 6.4.1-3: Redundant transmission with one NG-RAN node in HR roaming scenario. The diagram shows a UE connected to a RAN. The RAN is connected to an AMF via N2. The AMF is connected to a V-SMF via N11. The V-SMF is connected to a H-SMF via N7. The V-SMF is also connected to an I-UPF via N4. The I-UPF is connected to a UPF via N9 tunnels (N9 Tunnel 1 and N9 Tunnel 2). The UPF is connected to a DN via N6. The RAN is also connected to the I-UPF via N3 tunnels (N3 Tunnel 1 and N3 Tunnel 2). The diagram is divided into two sections: VPLMN (left) and HPLMN (right) by a dashed vertical line. The AMF is also connected to a V-PCF via N15, and the V-PCF is connected to an H-PCF via N24. + +**Figure 6.4.1-3: Redundant transmission with one NG-RAN node in HR roaming scenario** + +As shown in figure 6.4.1-3, in home routed roaming scenario, the NG RAN node is connected to the anchor UPF in the HPLMN via an intermediate UPF node in the VPLMN to support redundant transmission with two N3 and N9 tunnels. The V-SMF selects the two intermediate UPFs and setup the redundant transmission tunnels on N3 and N9 in case it receive two CN tunnel info for a URLLC QoS flow from H-SMF. + +NOTE 3: Supporting the above HR redundant transmission requests two disjointed transport paths exist between I-UPF and PSA UPF. + +### 6.4.2 Procedures + +The Procedures for activate redundant transmission during PDU session establishment/modification are same as corresponding procedures shown in clause 6.3.2 except for both of two AN tunnels are terminated on M-RAN nodes and S-RAN node addition is not needed. + +The handover procedures in this solution can refer to the handover procedures defined in TS 23.502 [3]. The only difference is that the NG RAN node shall provide the CN with the AN Tunnel Info for the two N3 tunnels and the CN will also provide the NG RAN node with the CN Tunnel Info for the two N3 tunnels. + +### 6.4.3 Impacts on Existing Nodes and Functionality + +PCF: + +- The PCF can determine whether redundant transmission need to be activate for a QoS Flow based on its QoS requirement, UE's subscription and condition of network deployment. + +#### **AMF:** + +- No impact in this solution. + +#### **SMF:** + +- The SMF can determine whether redundant transmission need to be activated for a QoS Flow based on local policies for the DNN or S-NSSAI. +- In case the SMF allocates CN Tunnel Info, it shall provide the CN Tunnel Info for two tunnels of the redundant transmission paths. +- The SMF shall indicate the UPF to replicate the downlink packet and send the duplicate packets to the two N3 tunnels, and indicate the UPF to eliminate the duplicate uplink packets. + +#### **UPF:** + +- In case the UPF allocates CN Tunnel Info, it shall provide the CN Tunnel Info for two tunnels of the redundant transmission paths. +- The UPF shall be able to replicate the downlink packet and send the duplicate packets to the two N3 tunnels, and eliminate the duplicate uplink packets. + +#### **RAN:** + +- The RAN shall be able to replicate the uplink packet and send the duplicate packets to the two N3 tunnels, and eliminate the duplicate downlink packets. + +#### **UE:** + +- No impact in this solution. + +### 6.4.4 Solution Evaluation + +This solution provides high reliability transporting mechanism by performing redundant transmission between Anchor UPF and RAN node via disjointed CN tunnels. The solution has the following properties: + +- The operator can control the activation of redundant transmission or not by PCC mechanism. +- Use of certain transport network (e.g. TSN) in the backhaul (i.e. over N3/N9) can address this issue. +- The solution provides a 3GPP solution for setting up redundant paths on N3 in case transport layer cannot meet the reliability requirement. +- The UPF is a single point of failure in the user plane. In case of UPF failure, the session is lost. +- This solution has no dependency on the protocol used in application layer, which is out of control of the operator. +- The redundant transmission can be activated on demand per QoS Flow. +- Current existing PDU session/QoS Flow management mechanisms are reused in this solution with limited extensions shown in 6.4.3. No further impact on existing control plane mechanisms. +- No impact on air interface and UE. + +## 6.5 Solution #5 for Key Issue #2: Duplication of user plane tunnelling during HO + +### 6.5.1 Functional Description + +This solution addresses Key Issue#2 (supporting low latency and low jitter during HO). The basic idea is that the user plane tunnel will be established and used to transmit data as long as the DRB is established during handover procedure, which is called "enhanced handover", so as to avoid the additional latency and jitter brought by data forwarding and/or data path switch on CN side. + +The "enhanced handover" is defined per [S-NSSAI, DNN]. It can be dynamically provisioned to SMF from UDM or PCF during PDU session procedure, or statically preconfigured in SMF. Then SMF determines if apply this "enhanced handover" for each PDU session and store the association of the "enhanced handover" and PDU session id. + +When handover is triggered by source RAN node, the SMF will duplicate the tunnel for the PDU session which is associated to "enhanced handover", and send the downlink data to both source and target RAN node until the handover is completed. + +NOTE: This solution needs to be checked with RAN2/RAN3 before final conclusion. + +### 6.5.2 Procedures + +#### 6.5.2.1 PDU session establishment or modification + +![Sequence diagram for PDU session establishment or modification for 'enhanced handover' provisioning. The diagram shows four participants: UE, RAN, SMF, and PCF. The sequence of messages is: 1. UE sends a PDU Session Establishment/Modification Request to SMF. 2. SMF sends a Session Management Policy Establishment or Modification request to PCF. 3. SMF determines if apply 'enhanced handover' to this PDU session. Following these steps, the process continues with 'Following existed steps'.](df6b7ae63e53e5f93dbd0a70acdae4a6_img.jpg) + +``` +sequenceDiagram + participant UE + participant RAN + participant SMF + participant PCF + Note right of SMF: 3. SMF determines if apply "enhanced handover" to this PDU session + UE->>SMF: 1. PDU Session Establishment/Modification Request + SMF->>PCF: 2. Session Management Policy Establishment or Modification + Note right of SMF: Following existed steps +``` + +Sequence diagram for PDU session establishment or modification for 'enhanced handover' provisioning. The diagram shows four participants: UE, RAN, SMF, and PCF. The sequence of messages is: 1. UE sends a PDU Session Establishment/Modification Request to SMF. 2. SMF sends a Session Management Policy Establishment or Modification request to PCF. 3. SMF determines if apply 'enhanced handover' to this PDU session. Following these steps, the process continues with 'Following existed steps'. + +**Figure 6.5.2.1-1: PDU session establishment or modification for "enhanced handover" provisioning** + +In step3, based on the "enhanced handover" policy provided from PCF or static policy stored in SMF, the SMF determines if the PDU session should be applied for "enhanced handover" and store the association between PDU session id and "enhanced handover" indication. + +NOTE: The SMF may add an indicator to the PDU Session create/update message sent from SMF to RAN to indicate if the PDU session data needs data forwarding when handover happens. + +#### 6.5.2.2 Enhanced N2 based Handover + +![Sequence diagram for Enhanced N2 based Handover showing interactions between UE, Source RAN Node, Target RAN Node, AMF, SMF, and UPF.](1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source RAN Node + participant Target RAN Node + participant AMF + participant SMF + participant UPF + + Note left of UE: Uplink data + Note right of UE: Downlink data + Source RAN Node->>AMF: 1. Handover Required (PDU Session ID, Target Node ID) + AMF->>SMF: 2. Session Update Request (PDU Session ID) + SMF->>UPF: 3. Session modification (create the secondary tunnel for the PDU session marked "enhanced handover" using the same IP address) + UPF-->>SMF: 4. Session Update Request Ack + SMF->>Target RAN Node: 5. Handover Request + Target RAN Node-->>SMF: 6. Handover Request Ack + SMF->>AMF: 7. Session Update Request + AMF-->>SMF: 8. Session Modification + SMF->>AMF: 9. Session Update Request Ack + AMF->>Source RAN Node: 10. Handover Command + Note right of UPF: 11. After step-8, UPF send duplicated downlink data to Target RAN + Source RAN Node-->>Target RAN Node: Indication of the start of redundant transmission + Source RAN Node-->>Target RAN Node: Downlink data + Target RAN Node-->>Source RAN Node: Downlink data + Note left of UE: 12a. Handover procedure in radio interface + Note right of Target RAN Node: 12b. Target RAN receive and cache the downlink data and send to UE when DR is established + Target RAN Node-->>UE: Downlink data + UE-->>Target RAN Node: Uplink data + Note left of UE: 13. UE reorders data from source and target Node simultaneously + UE->>Target RAN Node: 14. handover completed + Target RAN Node->>SMF: 15. Handover notify + SMF->>UPF: 16. Session modification (release the CN tunnel to source RAN) + +``` + +Sequence diagram for Enhanced N2 based Handover showing interactions between UE, Source RAN Node, Target RAN Node, AMF, SMF, and UPF. + +Figure 6.5.2.2-1: Enhanced N2 based handover + +The procedure reuse existing N2 based handover, with the following characteristics: + +1. The UL/DL SN mapping relation between PDCP and GTP-U can be used for redundancy elimination, and if so the source RAN node needs to add the mapping relation when sending handover required and it is forwarded to target RAN node in step-5. +3. During session modification, the SMF establish the secondary tunnel for PDU sessions marked as "enhanced handover" which sharing the same IP address with the original tunnel within the same PDU session. +11. When the secondary tunnel is finished (after step-8), the UPF begins to duplicate the downlink data and send to both source and target RAN node simultaneously. An indication can be included in the GTP-U header of the first duplicated packet to the source RAN to indicate the start of duplicated transmission. After receiving the indication, the source RAN will trigger handover command. +- 12a. The source RAN will send handover command to UE once it receives the indication for the start of redundant transmission and finishes the transmission of the packets received before the indication. +- 12b. Before the target DRBs are not established, the target RAN node cache the downlink data from UPF. As long as the target DRBs are established, the UL and DL data transmission will be performed. + +13. As long as the DRBs in target RAN node are established, UE will transmit the UL and DL data via target RAN node before the handover procedure is totally finished (UE sending handover complete). In dual radio based handover case, the UE will transmit the data via source and target RAN nodes simultaneously before the handover procedure is totally finished. + +UE performs the redundancy elimination of DL data from source and/or target RAN node using the DL PDCP SN for URLLC QoS flow. UPF performs the redundancy elimination of UL data from RAN node using the GTP-U SN for URLLC QoS flow. + +**NOTE 1:** It is assumed there is a 1 to 1 mapping between DRB and URLLC QoS flow. The size of GTP-U SN and the size of PDCP SN are aligned. + +**NOTE 2:** Since there may be a few UL/DL of packets transmitted between the HO triggering and target N3 tunnel established, the SN value will be increased comparing to the SN value when triggering HO, so the target RAN node needs to derive the DL PDCP SN and/or UL GTP-U SN value for the packets transmitted in the target path. + +15-16: When receiving handover notify, the core network release the tunnel in source RAN side. + +#### 6.5.2.3 Enhanced Handover with Xn + +![Sequence diagram for Enhanced Handover with Xn showing interactions between UE, Source RAN Node, Target RAN Node, AMF, SMF, and UPF during handover preparation, execution, and path switch phases.](9ff1b32449ea068bba9647d71904bd59_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source as Source RAN Node + participant Target as Target RAN Node + participant AMF + participant SMF + participant UPF + + Note over UE, UPF: Uplink data / Downlink data (Initial state) + rect rgb(240, 240, 240) + Note over UE, Source: 1. Handover preparation in RAN side + end + Source->>AMF: 2a. N2 message for handover (PDU Session IDs to be switched, the list of accepted QoS Flows) + AMF->>SMF: 2b. Session Update Request (PDU Session IDs to be switched, the list of accepted QoS Flows) + SMF->>UPF: 2c. Session modification (create the secondary tunnel for certain PDU session) + UPF->>AMF: 2d. Session Update Request ACK + AMF->>Source: 2e. Handover Command + + Source-->>Target: Indication of the start of redundant transmission + Note right of UPF: 3. UPF duplicates the data in the same PDU Session + UPF-->>Source: Downlink data + UPF-->>Target: Downlink data + + rect rgb(240, 240, 240) + Note over UE, Target: 4. Handover execution in RAN side + end + rect rgb(240, 240, 240) + Note over Target: 5. Target Node cache the downlink data + end + rect rgb(240, 240, 240) + Note over UE, Target: 6. As long as the user-plane in target Node is established, target Node sends the downlink data including cached data + end + Target-->>UE: Downlink data + UE-->>UPF: Uplink Data + + rect rgb(240, 240, 240) + Note over UE: 7. UE reorders data from source and target RAN node + end + UE->>Target: Handover completed + Target->>AMF: 8. Path Switch + AMF->>SMF: 9. Session Update Request + SMF->>UPF: 10. Session Modification (release the original tunnel in source node) + UPF->>AMF: 11. Session Update Request ACK + AMF->>Target: 12. Path Switch ACK + Target->>Source: 13. Release Resources + +``` + +Sequence diagram for Enhanced Handover with Xn showing interactions between UE, Source RAN Node, Target RAN Node, AMF, SMF, and UPF during handover preparation, execution, and path switch phases. + +**Figure 6.5.2.3-1: Enhanced handover with Xn** + +The procedure reuse existing Xn based handover, with the following new features. + +- 1-2. When the handover in radio interface is ongoing, the source RAN node sends N2 message for handover to SMF to establish the secondary tunnel in target side for the PDU session. The step 2 will be triggered during the handover procedure in radio interface. + +If SMF determines an intermediate UPF (I-UPF) is needed in the secondary tunnel, then, SMF selects an intermediate UPF (I-UPF) to update PDU session. + +The UL/DL SN mapping relation between PDCP and GTP-U can be used for the redundancy elimination, and if so the source RAN node needs to tell the target RAN node the mapping relation via Xn in step 1 (e.g. in handover request). + +3. When the secondary tunnel is finished (after step-2b), the UPF begin to send duplicate the downlink data and send to both source and target RAN node simultaneously. An indication can be included in the GTP-U header of the first duplicated packet to the source RAN to indicate the start of duplicated transmission. After receiving the indication, the source RAN will trigger Uu handover. + +In case of the I-UPF insertion, the UPF sends the downlink data to the target RAN node via the I-UPF. + +5. Before the DRB is established, the target RAN node cache the downlink data from UPF. +6. As long as the DRBs in target Node are established, the target RAN node, UE will transmit the UL and DL data via target RAN node before the handover procedure is totally finished (UE sending handover complete). In dual radio based handover case, the UE will transmit the data via source and target RAN nodes simultaneously before the handover procedure is totally finished. + +UE eliminates the redundancy of the DL data from both source and target RAN node using the DL PDCP SN for URLLC QoS flow. UPF eliminates the redundancy of the UL data from RAN node using the GTP-U SN for URLLC QoS flow. + +NOTE 1: It is assumed there is a 1 to 1 mapping between DRB and URLLC QoS flow. The size of GTP-U SN and the size of PDCP SN are aligned. + +NOTE 2: Since there may have been a few UL/DL of packets transmitted between the HO triggering and target N3 tunnel established, the SN value will be increased comparing to the SN value when triggering HO, so the target RAN node needs to derive the DL PDCP SN and/or UL GTP-U SN value for the packets transmitted in the target path. + +- 8-13. When receiving path switch request, the core network release the N3 tunnel to source RAN. The target RAN node triggers the release of resources with the source RAN node if it confirms success of the handover by receiving the path switch request ACK. + +### 6.5.3 Impact on existing entities and interfaces + +UE: + +For duplicated transmission during HO, + +- if redundancy elimination is performed in application layer, UE shall support this redundancy elimination in upper layer (out of 3GPP scope); or +- if redundancy elimination is performed in 3GPP layer, UE shall eliminate the DL data redundancy using the DL PDCP SN. + +NG-RAN: + +For the source RAN node: + +- If the packets redundancy elimination is performed in 3GPP layer, the source RAN node needs to notify the target RAN node the UL/DL SN mapping relation between PDCP and GTP-U. +- The source RAN will send handover command to UE when it receives the indication for the start of redundant transmission. + +For the target RAN node: + +- If the packets redundancy elimination is performed in 3GPP layer, the target RAN node needs to derive the UL GTP-U SN and DL PDCP SN based on the mapping relation received from source RAN node; +- Before the target DRBs are not established, the target RAN node cache the downlink data from UPF. As long as the target DRBs are established, the UL and DL data transmission will be performed. + +SMF: + +- Determine which PDU session or flow needs the "enhanced handover". +- During HO procedure preparation, the SMF establishes the target N3 tunnel for PDU sessions marked as "enhanced handover" which sharing the same IP address with the original tunnel within the same PDU session. + +UPF: + +- When the target N3 tunnel is established, the UPF begins to duplicate the downlink data and send to both source and target RAN node simultaneously. +- UPF shall perform redundancy elimination of the UL data from RAN node using the GTP-U SN for URLLC QoS flow. + +### 6.5.4 Solution Evaluation + +This solution is to avoid additional latency incurred by data forwarding via Xn in case of handover scenario. With this enhancement, it helps to realize a relatively stable e2e transmission time during UE mobility because the additional latency due to data forwarding will be avoided. It has the following advantages: + +- The procedure of this solution is decoupled to the RAN solution, i.e. either existing handover or the enhanced handover (e.g. "make before break" handover) in radio interface can be fitted into this solution. +- The latency due to data forwarding will be avoided and the transmission time will be stable even in case of UE mobility. +- The existing N2 and Xn based handover procedure will be enhanced with minimum impact to existing system. +- For the method to performing redundant transmission, it follows the same method as the agreement for KI#1. +- The duplication of user plane tunneling to avoid data forwarding latency is determined in operator's network based on existing parameters e.g. S-NSSAI and/or DNN. + +## 6.6 Solution #6 for Key Issue #3: Forwarding tunnel between source and target UL CL + +### 6.6.1 Description + +Consider the architecture depicted in Figure 6.6.1-1. Initially UE is connected to Source RAN (S-RAN) and has a PDU Session established with a remote PDU Session Anchor (PSA1). The network has inserted an Uplink Classifier (S-ULCL) that directs selected traffic to a local PDU Session Anchor (PSA2). The traffic flows exchanged via PSA-2 are terminated in a Source Application Server (S-AS) which is a user plane entity (e.g. content distribution server) that is controlled by an AF via an interface that is outside of 3GPP scope (e.g. ETSI MEC architecture as defined in ETSI ISG MEC GS MEC-003 [8] is an example illustrating the split into a control and user plane entity in the context of edge computing; other architectures are also possible). + +At some point UE is handed over to the Target RAN (T-RAN). This solution proposes that upon instantiation of the Target Uplink Classifier (T-ULCL) a N9 forwarding tunnel is created between the Source Uplink Classifier (S-ULCL) and the T-ULCL, as depicted in Figure 6.6.1-1. + +![Figure 6.6.1-1: Architecture with N9 forwarding tunnel between source and target ULCL. The diagram shows two User Equipment (UE) units. The top UE is connected to a T-RAN, which is connected to a UPF (T-ULCL). The bottom UE is connected to an S-RAN, which is connected to a UPF (S-ULCL). A red dashed line represents an N9 forwarding tunnel between T-ULCL and S-ULCL. From T-ULCL, a green dashed line (N9) leads to a UPF (PSA-3), which is connected via an N6 line to a T-AS (Target Application Server) in a DN (Data Network). From S-ULCL, a blue dashed line (N9) leads to a UPF (PSA-2), which is connected via an N6 line to an S-AS (Source Application Server) in a DN. Both T-AS and S-AS are connected to an AF (Application Function). A solid black line (N9) also connects T-ULCL to a UPF (PSA-1), which is connected to the AF via an N6 line. A legend at the top right indicates that a solid black line represents traffic 'Out of 3GPP scope'.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +Figure 6.6.1-1: Architecture with N9 forwarding tunnel between source and target ULCL. The diagram shows two User Equipment (UE) units. The top UE is connected to a T-RAN, which is connected to a UPF (T-ULCL). The bottom UE is connected to an S-RAN, which is connected to a UPF (S-ULCL). A red dashed line represents an N9 forwarding tunnel between T-ULCL and S-ULCL. From T-ULCL, a green dashed line (N9) leads to a UPF (PSA-3), which is connected via an N6 line to a T-AS (Target Application Server) in a DN (Data Network). From S-ULCL, a blue dashed line (N9) leads to a UPF (PSA-2), which is connected via an N6 line to an S-AS (Source Application Server) in a DN. Both T-AS and S-AS are connected to an AF (Application Function). A solid black line (N9) also connects T-ULCL to a UPF (PSA-1), which is connected to the AF via an N6 line. A legend at the top right indicates that a solid black line represents traffic 'Out of 3GPP scope'. + +**Figure 6.6.1-1: Architecture with N9 forwarding tunnel between source and target ULCL** + +The N9 forwarding tunnel is maintained until all active traffic flowing on it ceases to exist for a configurable period of time. + +T-ULCL is configured with packet filters that: + +- force uplink traffic from existing sessions (between UE and Source AS) on the following path: T-RAN - T-ULCL - S-ULCL - PSA2. Similarly, S-ULCL is configured to forward all downlink traffic for this UE coming from S-AS into the N9 forwarding tunnel towards T-ULCL. +- force any new DNS requests (relating to the local DN) to go to the new local DN (via PSA3). +- force any traffic related to the Target Application Server (T-AS) in the new local DN (e.g. identified by a match between the destination IP address of uplink packets and the IP address of T-AS) to go to the new local DN (via PSA3). +- let any remaining traffic go to the remote PDU Session Anchor (PSA1). + +SMF may send a Late Notification to AF to inform it about the DNAI change (i.e. change of local PSA). Based on this notification the AF triggers the S-AS to use upper layer (e.g. IP level or HTTP level) mechanisms to redirect the ongoing traffic sessions towards a server in the new local DN (i.e. towards Target AS). If target AS, located in local data network, is associated with local AF instance (called T-AF), then below steps are in response to Late Notification from SMF to AF: + +- AF acknowledges receipt of late notification, and also provides N6 traffic routing details (i.e. due to change to T-AS in local data network) and T-AF identifier. +- SMF/AF cancels earlier subscribed user plane management event notifications. +- SMF configures PSA-3 with received N6 traffic routing information. +- T-AF subscribes to user plane management event notifications. +- SMF sends late notification to T-AF, along with PSA-3 details and AF request ID. + +NOTE: Communication between AF and T-AF and AF behaviours on handling service relocation are out of scope of this study. + +### 6.6.2 Procedures + +Depicted in Figure 6.6.2-1 is an example call flow illustrating how the overall solution works. + +![Sequence diagram illustrating the overall call flow for a PDU session modification due to UE mobility. The diagram shows the interaction between UE, Source (R)AN, Target (R)AN, SMF, Source ULCL, Target ULCL, Source UPF (PSA2), Target UPF (PSA3), and Remote UPF (PSA1). The process starts with an established PDU session and involves steps like SMF establishing Target ULCL, updating Target RAN, updating Remote UPF, establishing Target UPF, late notification, redirection, detection of no active traffic, and releasing Source ULCL and Source UPF.](34b047489058d6400b412cd0ae2334ba_img.jpg) + +The sequence diagram illustrates the overall call flow for a PDU session modification due to UE mobility. The participants involved are: UE, Source (R)AN, Target (R)AN, SMF, Source ULCL, Target ULCL, Source UPF (PSA2), Target UPF (PSA3), and Remote UPF (PSA1). The process begins with a message indicating that the UE has an established PDU session with Source ULCL, Source UPF, and Remote UPF. Data flows are shown between the UE and Source (R)AN, and between Source (R)AN and Source ULCL. A message indicates that the NG-RAN initiates an Xn based Inter 5G RAN handover, with data forwarding and downlink/uplink data transfer. The SMF then performs several steps: 1. SMF establishes Target ULCL and tunnel between T-ULCL and S-ULCL; 2. SMF updates Target RAN for uplink traffic; 3. SMF updates Remote UPF For downlink traffic; 4. SMF establishes Target UPF. Additional components S-AS and AF are involved in 5. Late Notification, 6a. Redirection, and 6b. Redirection. The process concludes with 7. Detection of no active traffic and 8. SMF releases Source ULCL and Source UPF. + +Sequence diagram illustrating the overall call flow for a PDU session modification due to UE mobility. The diagram shows the interaction between UE, Source (R)AN, Target (R)AN, SMF, Source ULCL, Target ULCL, Source UPF (PSA2), Target UPF (PSA3), and Remote UPF (PSA1). The process starts with an established PDU session and involves steps like SMF establishing Target ULCL, updating Target RAN, updating Remote UPF, establishing Target UPF, late notification, redirection, detection of no active traffic, and releasing Source ULCL and Source UPF. + +**Figure 6.6.2-1: Overall call flow** + +1. At some point SMF decides to change the UL CL due to UE mobility. This may be e.g. the AMF notifying the SMF that the target (R)AN has sent an N2 Path Switch Request message to an AMF. The SMF selects a UPF and using N4 establishes the Target UL CL for the PDU Session and also establishes an N9 forwarding tunnel towards S-AS via the UPF acting as Source UL CL. SMF provides the T-ULCL with the necessary uplink forwarding rules towards PSA1, PSA3 and the N9 forwarding tunnel (i.e. towards S-ULCL), including the Tunnel Info for each UPF. In addition, the AN Tunnel Info to target (R)AN is provided to T-ULCL for downlink + +forwarding. The SMF provides traffic filters indicating what traffic shall be forwarded towards PSA1, PSA3 and S-ULCL, respectively. SMF provides the CN Tunnel Info to Source ULCL for downlink traffic. At this point, the downlink traffic goes through S-ULCL, T-ULCL and Target (R)AN. + +2. The SMF updates (R)AN via N2 SM information over N11. It provides the new CN Tunnel Info corresponding to the Target UL CL. At this point all uplink and downlink traffic between UE and PSA2, as well as between UE and PSA1, is forwarded via the N9 forwarding tunnel between S-ULCL and T-ULCL. + +NOTE 1: Alternatively, an N9 interface can be established directly between UPF acting as T-ULCL and PSA-2. + +3. The SMF updates the PSA1 via N4. It provides the PDU Session CN Tunnel Info for the downlink traffic. At this point all uplink and downlink traffic between UE and PSA1 are exchanged on the direct path between T-ULCL and PSA1. + +NOTE 2: At this stage, the UPF acting as S-ULCL only acts as an intermediate UPF. + +4. The SMF selects a local Target UPF (PSA3) and using N4 establishes the local Target UPF for the PDU Session. + +NOTE 3: In case the Target UL CL and the PSA3 are co-located in a single UPF then step 4 is merged into step 1. + +5. The SMF sends a Late Notification to the AF indicating a change of DNAI (i.e. a change of the local PSA). The message may optionally include an identifier (IP address or FQDN) pointing to a Target AS. Alternatively the target AS IP address can be configured at the AF and the AF can include T-AS address using the Application Function influence on traffic routing described in clause 4.3.6 in TS 23.502 [3], which help the SMF generate the routing rule on the T-ULCL to PSA3 (i.e. towards target AS). +6. The AF triggers S-AS to redirect the UE towards a Target AS using upper layer (e.g. IP-level or HTTP-level) redirection mechanisms that are out of the scope of 3GPP. The redirection may point to a specific Target AS as indicated in step 5. Based on this redirection the UE starts using a new destination IP address (with or without prior DNS resolution) which leads the T-ULCL to force the traffic towards PSA3. +7. Detection of no active traffic over the N9 forwarding tunnel during a preconfigured time interval. The detection can be done by either S-ULCL or T-ULCL, either of which can notify the SMF. +8. The SMF releases the UPF acting as Source UL CL and the Source UPF (PSA2). + +NOTE 4: As an alternative to the detection of no active traffic in step 7, the AF can send an explicit notification to the SMF when traffic to/from this UE ceases to exist, leading the SMF to release the Source UL CL and the Source UPF (PSA2). + +### 6.6.3 Impacts on Existing Nodes and Functionality + +UPF is impacted so that the UL CL function needs to support temporary N9 tunnel forwarding to/from another UL CL, in addition to forwarding packets to/from the local PSA and to/from the remote PSA. + +### 6.6.4 Solution Evaluation + +The solution primarily addresses an aspect of Key Issue #3 ("How to handle ULCL relocation ... for URLLC services, and how the traffic routing on N6 interface is fulfilled are FFS"). + +While the study is carried out under the URLLC umbrella, the solution also addresses an acknowledged issue with the ULCL relocation defined in Rel-15. Namely, when the ULCL is relocated in the Rel-15 5GS architecture, the Stage 2 specifications do not provide any hint as to how service continuity is provided in a seamless manner. + +The solution relies on temporary tunnel forwarding from old ULCL to new ULCL and on upper layer redirection. The UE is involved in the upper layer redirection, but only at the "upper layers" that are outside 3GPP scope. + +The solution applies to PDU Session of IP and Unstructured type. + +- for PDU Session of IP type the redirection can be performed e.g. using HTTP redirect or via unspecified application-level redirection message triggered from the old network server. +- for PDU Session of Unstructured type the trailing forwarding tunnel provided by this solution is useful for collecting the in-flight downlink data that were directed to the old network server. + +## 6.7 Solution #7 for Key Issue #1: Replication framework in 3GPP System + +### 6.7.1 Description + +This solution addresses the KI#1 of How to "Supporting high reliability by redundant transmission in user plane". + +This solution introduces a replicator that allows the 3GPP system to be aware (e.g. detect or have explicit information) that two or more "streams" of replicated packets belong together, and guide the lower layers to ensure these packets get an optimized treatment in the 3GPP system depending on whether the streams are terminated in a single UE or by two different UEs that belong together within the same hub-solution (e.g. TSN hub with two or more redundant 5G modems). This is to specifically ensure that 3GPP features are used optimally to ensure that latency/availability/reliability requirements and expectations of external duplication methods are fulfilled (e.g. including hybrid access solutions, IEEE 802.1CB, etc.). Additionally, the replicator is applicable to any external multi-path mechanism even if the multiple paths are not used in a redundancy fashion (i.e., duplicating each packet on all paths) but for partly or fully disjoint data transmission. + +Replicator functionality can be supported within the 5GS without making any assumption on support for IEEE FRER in the application layer (DN only) at the same time it can be introduced without much impact on the UE, UPF, NG-RAN rather isolated to the replicator framework (e.g. it can be realized by integrating IEEE FRER within the 3GPP system) that can be integrated within 3GPP system. + +Replicator functionality within 3GPP system helps avoid blind replication irrespective of the type of application. If the application does not support replication of traffic stream but requires lowest latency and high availability, replicator within 5GS can perform replication of the traffic stream. If the application supports replication of traffic stream in order to support lowest possible latency, replicator within 5GS can avoid further replication of the traffic stream. + +In short, the main principles of the solution are as follows: + +1. An entity/functionality in the 3GPP system, refer to it as replicator functionality, is able to detect multiple related flows, and whether they are utilized for redundant packets, of incoming IP/Ethernet flows at the transmitter side. Control plane aspects necessary for the replicator functionality resides in the SMF and the User plane aspects necessary for the replicator functionality resides in the UPF and the NG-RAN. +2. The replicator guides the lower layers to ensure their corresponding latency/availability/reliability requirements are fulfilled. + - a. Case 1: Based on the application requirement to support lowest latency and the need to support replication within 5G System (within the domain of 3GPP System), the replicator framework replicates the packets towards the lower layers. + - b. Case 2: Based on the application functionality to support redundancy by default, replication framework within 5G System (within the domain of 3GPP System), replicator framework can eliminate further replication rather it can transmit the packet stream just once towards the lower layers. +3. For case 1, to ensure the two N3 tunnels can be transferred via disjointed transport layer paths, the NG-RAN node, SMF or UPF will provide different routing information in the tunnel information (e.g. different IP addresses or different Network Instances), and the routing information will be mapped to disjoint transport layer paths according to network deployment configuration. +4. At the receiver side, the receiver translates and forwards the internal streams to the corresponding external application either in the UE side or in the network side. To make it transparent to the external application, further combine/remove/replicate operations may be applied to "reverse" the operations in step 2b. The replicator at the receiver can use the header information (or share explicit information with the replicator entity at the other end) to translate/re-build packets according to the external application requirements. +5. Following are the main 5G System impacts and principles: + - a. 5G System can have an API or direct interaction with external management system to become aware of the expected application behaviour with regards to replication functionality. UPF can also perform data inspection in the UPF (with replicator) for autonomous discovery of multiple related flows (e.g. it can detect if the MPTCP layer is duplicating the flows). + +- b. Based on policies, the SMF determines whether a particular PDU Session is subject to replication, selects an UPF with replicator functionality; It also provides the necessary replicator information as part of rules to the selected UPF. +- c. Based on the rules received from SMF, UPF activates replicator functionality for the User plane traffic. For DL traffic, UPF can perform further replication and provide an indication (e.g. GTP-U header) to the RAN. If the UPF duplicates the traffic, it transmits over multiple tunnels (using disjoint transport path) towards the RAN. +- d. The replicator functionality in the RAN can take potential actions such as eliminate the received duplicated DL data prior to transmitting it to the UE. Other potential actions are also listed in 6.7.2.1 bullet 2). +- e. If the UE with the replicator functionality receives duplicated packets, it can re-assemble the packets to ensure transparency to the application layer. The replicator at the receiver forwards the received data to one or more output ports, as expected by the application layer protocol. + +Figure 6.7.1-1 below shows an example of the user-plane system architecture of the proposed solution. The Replicator functionality may be a part of the UPF (or collocated with the UPF) for user plane functionality and SMF for control plane functionality. We consider a multi-UE transceiver that encompasses various UEs with independent hardware and protocol stacks. Each gNB can also consist of multiple distributed units (DU) attached to a central unit (CU). + +![Architecture diagram for a single UE/UPF case (Case 1).](0c80c383f76034e117adf5e5eaadaaf3_img.jpg) + +This diagram illustrates the user-plane system architecture for a single UE/UPF case. On the left, 'Host A: UE' contains an 'Application (802.1CB, etc.)' connected to a 'Replication Protocol', which is connected to a 'UE'. The 'UE' connects to a 'gNB' (containing an 'RP' unit). The 'gNB' connects to an 'UPF' (containing a 'Replication Protocol'). Above the 'gNB' and 'UPF' are the 'AMF' and 'SMF', which are connected to a 'PCF'. The 'AMF' connects to the 'gNB', and the 'SMF' connects to the 'UPF'. The 'UPF' connects to a 'DN' (Data Network), which in turn connects to 'Host B' containing an 'Application (802.1CB, etc.)'. Dashed lines represent control plane connections, and solid lines represent user plane connections. + +Architecture diagram for a single UE/UPF case (Case 1). + +**Figure 6.7.1-1 Architecture with Replication Framework - Single UE/UPF case (Case 1)** + +![Architecture diagram for a dual UE/dual UPF case (Case 2).](24a89bcaba787f2bc1721356480a4a01_img.jpg) + +This diagram illustrates the user-plane system architecture for a dual UE/dual UPF case. On the left, 'Host A: UE' contains an 'Application (802.1CB, etc.)' connected to a 'Replication Protocol', which is connected to a 'UE'. The 'UE' connects to two 'gNB' units, 'gNB1' and 'gNB2'. 'gNB1' connects to an 'UPF', and 'gNB2' connects to another 'UPF'. Above 'gNB1' and its 'UPF' are the 'AMF' and 'SMF', which are connected to a 'PCF'. The 'AMF' connects to 'gNB1', and the 'SMF' connects to the first 'UPF'. Below 'gNB2' and its 'UPF' are another 'AMF' and 'SMF'. The second 'UPF' connects to a 'Replication Protocol (KxL)', which connects to a 'DN' (Data Network). The 'DN' connects to 'Host B' containing an 'Application (802.1CB, etc.)'. Dashed lines represent control plane connections, and solid lines represent user plane connections. + +Architecture diagram for a dual UE/dual UPF case (Case 2). + +**Figure 6.7.1-2 Architecture with Replication Framework - Dual UE/Dual UPF case (Case 2)** + +### 6.7.2 Procedures + +#### 6.7.2.1 Downlink User Plane Transmission + +We use a downlink traffic flow example where redundant data (e.g. generated by 802.1 standard) enter the 3GPP system and must be reliable received at the UE receiver: + +##### 1) Discovery of multiple "streams" of packets. + +The replicator functionality in the 3GPP system is introduced to be aware that two or more "streams" of packets belong together. This can be achieved with an API or direct communication with an external management system. + +Data inspection in the UP can also be applied to some extent for autonomous discovery of multiple related flows. + +The replicator informs the lower-layers (e.g. SDAP at the gNB/UE) of the detected redundant packets. As an option, it can also manipulate the incoming data, e.g. merging two packets into a single packet but mapping it and indicating the higher reliability needs for the packet. It should also ensure that the packets requiring higher reliability are transported via disjoint transport layer paths according to network configuration (i.e. different IP address configurations). + +#### 6.7.2.2 Activate Redundant Transmission during PDU Session Establishment procedure + +The replicator functionality can be activated during a PDU Session establishment procedure as described in this clause. + +Figure 6.7.2.2-1 depicts the establishment of during the PDU session establishment procedure in the non-roaming and roaming with local breakout cases for case 1) with single UE and single UPF. + +![Sequence diagram showing the activation of replicator functionality during PDU Session Establishment. The diagram involves seven participants: UE, NG-RAN, AMF, UPF, SMF, UDM, and PCF. The process is divided into three main steps: 1. Steps 1-12 of UE requested PDU Session Establishment (TS 23.502); 2. Replication Framework Activation (indicated by a dashed box); 3. Steps 14-20 of UE requested PDU Session Establishment (TS 23.502).](d6015fcef74bce83d04acd2e17b4fc15_img.jpg) + +| UE | NG-RAN | AMF | UPF | SMF | UDM | PCF | +|-------------------------------------------------------------------------------------------|--------|-----|-----|-----|-----|-----| +| 1. Steps 1-12 of UE requested PDU Session Establishment in clause 4.3.2.2.1 in TS 23.502 | | | | | | | +| 2. Replication Framework Activation | | | | | | | +| 3. Steps 14-20 of UE requested PDU Session Establishment in clause 4.3.2.2.1 in TS 23.502 | | | | | | | + +Sequence diagram showing the activation of replicator functionality during PDU Session Establishment. The diagram involves seven participants: UE, NG-RAN, AMF, UPF, SMF, UDM, and PCF. The process is divided into three main steps: 1. Steps 1-12 of UE requested PDU Session Establishment (TS 23.502); 2. Replication Framework Activation (indicated by a dashed box); 3. Steps 14-20 of UE requested PDU Session Establishment (TS 23.502). + +**Figure 6.7.2.2-1: Activate Replicator functionality during PDU Session Establishment procedure** + +1. Steps 1-12 from clause 4.3.2.2.1(UE requested PDU Session Establishment) in TS 23.502 [3] are performed with the following differences: + +In Step 1, the UE initiates the UE Requested PDU Session Establishment procedure by the transmission of a NAS message containing a PDU Session Establishment Request within the N1 SM container and it can include its capability to support replicator protocol (but not required). The UE can also indicate a specific DNN and S-NSSAI. + +In step 7b, the PCF indicates to the SMF and the NG-RAN to activate replicator functionality for the QoS flow by the 5QI if the UE requested PDU Session Establishment procedure is initiated for a URLLC service (based on parameters provided by the UE). + +The SMF then initiates an N4 Session Establishment procedure with the selected UPF (with replicator functionality) and CN Tunnel ID(s) are allocated by the SMF or UPF. + +In step 11, the N2 SM information includes the QFI(s), QoS Profile(s), CN Tunnel Information corresponding to each N3 tunnel. + +2. RRC Connection Reconfiguration takes place with the UE establishing the necessary NG-RAN resources related to Replicator functionality. +3. Steps 14-20 from clause 4.3.2.2.1(UE requested PDU Session Establishment) in TS 23.502 [3] are performed with the following differences: + +The AN Tunnel Info provided by the NG-RAN includes AN Tunnel ID(s) for replicated paths. Each AN Tunnel Information includes a tunnel endpoint for each involved NG-RAN node, and the QFIs assigned to each tunnel endpoint. The SMF provides AN Tunnel Information for each tunnel to the UPF. + +For case 2), main addition to the above procedure would be for the two UE(s) to provide a parameter (e.g. SD part of the S-NSSAI has a commonly configured value, support for replicator functionality) in the PDU Session Establishment request that gives a hint to the network for selecting the same UPF or two UPF(s) with access to the same replicator functionality towards the DN. + +### 6.7.3 Impacts on Existing Nodes and Functionality + +UE: + +- Optional support for replicator functionality. + +NG-RAN: + +- Access to replicator functionality support. Replicator in the RAN has the capability to replicate packets over N3 and/or eliminate further replication of packets over Uu/N3. + +SMF: + +- Based on parameters (e.g. DNN, S-NSSAI, replicator support) provided by the UE in the PDU Session request, ability for SMF to select UPF with access to replicator functionality and also activate replicator functionality in the NG-RAN as part of N2 SM context activation. + +UPF: + +- Access to replicator functionality support. Replicator in the UPF has the capability to replicate packets and/or eliminate further replication of packets. + +### 6.7.4 Solution Evaluation + +**Editor's note:** This clause provides an evaluation of this solution. + +## 6.8 Solution #8 for Key Issue #4: QoS Monitoring + +### 6.8.1 Description + +Based on the TS 22.261 [5], clause 6.23 (QoS Monitoring), the vertical applications may want to be aware of the real time latency (e.g., UL, DL or Round trip latency) of the URLLC service in 5G system, and the trouble shooting could be done based on the real time latency as the input. QoS Notification Control is performed to monitoring the GFBR on RAN side only, to achieve the E2E QoS monitoring, the real time packet delay in 5GC and 5G-AN can be jointly monitored to achieve the E2E QoS monitoring by sending the monitoring packets periodically when QoS monitoring activated. There are two ways to monitor packet delay: round-trip time (RTT) delay and one-way delay. + +#### 6.8.1.1 QoS Monitoring Activation + +The QoS monitoring could be activated dynamically by the 5GC for certain UEs, UE group, or network slice instance, based on the subscription, the request from the AF, or the command from the OAM system, etc. + +During the PDU Session Establishment or Modification procedure, the PCF may send QoS Monitoring Policy to the SMF based on subscription or AF request. The QoS Monitoring policy contains the QoS parameters to be monitored, event report triggers, the validity timer length for round trip monitoring, the threshold of QoS parameters and the relevant actions when threshold is exceeded are also included in the QoS Monitoring policy. The QoS Monitoring Policy can also be pre-configured at SMF by the operator. When receiving the QoS Monitoring Policy from the PCF, The SMF maps the QoS Monitoring Policy in the URRs to the UPF, the URR includes QoS parameters to be monitored, threshold, the validity timer length for round trip monitoring and relevant action, and event report for specific QoS flows. The SMF notifies the RAN and UE to enable the QoS Monitoring for the QoS Flow via the Namf\_Communication\_N1N2MessageTransfer message and PDU Session Modification Command message. + +When the event reports is triggered, e.g. when the round trip or UL/DL packet delay is longer than the threshold, or when the UPF does not receive the round trip monitoring respond packet within the length of the validity timer, the UPF + +can report the events via N4 interface, respectively. After receiving the QoS monitoring events report from UPF, the SMF may forward the report to e.g. PCF. The detailed procedure for QoS Monitoring activation is defined in the clause 6.8.2. + +#### 6.8.1.2 Enforce QoS Monitoring + +##### 6.8.1.2.1 Option 1: Using newly defined packet as monitoring packets + +The monitoring packet is using the same QoS flow as the URLLC service packet data to be monitored. To distinguish the GTP-Us delivering the monitoring packets from the ones delivering the service packets, a new payload type QMP (QoS Monitoring Packet) in GTP-U header (between UPF and RAN) is introduced. + +![Diagram illustrating packet delay measurement between RAN and UPF. The diagram shows two protocol stacks. The left stack is labeled 'RAN' and the right stack is labeled 'UPF'. Both stacks have four layers: GTP-U (new type, Sequence Number) at the top, followed by UDP/IP, L2, and L1. Arrows indicate packet transmission: T1 (UPF to RAN) and T2 (RAN to UPF) for the GTP-U header; T5 (RAN to UPF) and T6 (UPF to RAN) for the UDP/IP layer. The GTP-U header is shown in orange, while the other layers are in white.](052543d8c9c0643b05b3ce45c6decca1_img.jpg) + +| GTP-U (new type,
Sequence Number) | T2 ← —————— ← T1
————————————————
T5 → —————— → T6 | GTP-U (new type,
Sequence Number) | +|--------------------------------------|----------------------------------------------------------|--------------------------------------| +| UDP/IP | | UDP/IP | +| L2 | | L2 | +| L1 | | L1 | +| RAN | | UPF | + +Diagram illustrating packet delay measurement between RAN and UPF. The diagram shows two protocol stacks. The left stack is labeled 'RAN' and the right stack is labeled 'UPF'. Both stacks have four layers: GTP-U (new type, Sequence Number) at the top, followed by UDP/IP, L2, and L1. Arrows indicate packet transmission: T1 (UPF to RAN) and T2 (RAN to UPF) for the GTP-U header; T5 (RAN to UPF) and T6 (UPF to RAN) for the UDP/IP layer. The GTP-U header is shown in orange, while the other layers are in white. + +**Figure 6.8.1.2.1-1: Packet delay measurement** + +The round trip latency could be monitored by sending the round trip monitoring packets between the UE and UPF. + +When the packet delay monitoring is activated by the network, the UPF creates and sends the monitoring packets to the RAN: + +- **Step1.** UPF generates the monitoring request packets and assigns a relevant sequence number with each packet. UPF encapsulates the GTP-U header with QFI, TEID and QMP indicator. The UPF records the local time T1 and starts validity timers for each monitoring packet with the length provided as the validity timer length for round trip monitoring after sending out the packets to the RAN successfully. +- **Step2.** When receiving the monitoring request packets, RAN records the sequence number and the local time T2, initiates packet delay measurement between RAN and UE. + +The length of the monitoring packet could be defined equal to the typical packet size of the actual URLLC service packet. The length of the monitoring packet could be contained in the QoS Monitoring policy. + +NOTE: QoS monitoring mechanisms adopted in RAN part depends on RAN conclusion. + +- **Step3.** When receiving the monitoring response packet from UE, RAN encapsulates QMP indicator in the GTP-U header of the measurement response packet and send it out to the UPF. RAN also includes the corresponding sequence number, the one way (UL and DL) packet delay result of Uu interface, local time T5 the response packet sent out, together with the T2 in step2 in the response packet. +- **Step4.** UPF records the local time T6 and gets the one way (UL and DL) packet delay result of Uu interface when receiving the monitoring response packet identified by the sequence number. In case the UPF does not receive a monitoring respond packet before the corresponding timer is ended, the UPF take that monitoring respond packet as lost. + +The UPF calculates the latency as the following: + +- RTT1: Round trip latency between the RAN and UPF: $(T6-T1) - (T5-T2)$ . +- RTT2: Round trip latency between the RAN and UE: Calculated by RAN based on the packet delay mechanism of Uu interface. +- RTT3: Round trip latency between the UPF and UE: $RTT1+RTT2$ . +- In case the monitoring respond packet is lost, Round trip latency is set to the length of the corresponding validity timer. + +It is assumed that the time synchronization precision between the UE and RAN achieves to microsecond level and the network latency between the RAN and UPF is regarded as symmetric, so we suggest approximate one way latency could also be calculated: + +- One way delay 1: DL or UL between the RAN and UE: Calculated by RAN based on the packet delay mechanism of Uu interface. +- One way delay 2: DL or UL between the RAN and UPF: $[(T6-T1) - (T5-T2)]/2$ +- One way delay 3: DL or UL between the UE and UPF: One way delay1 + One way delay2 + +The UPF and RAN could encapsulate the sequence number timestamp in the monitoring packets to calculate the one way or RTT packet delay between the RAN and UPF. + +##### 6.8.1.2.2 Option 2: Using actual service packets as monitoring packets + +The monitoring packet is sampled from the service packets of URLLC service by UE and UPF based on the measurement period in the QoS Monitoring policy. If the round trip packet delay is requested to be measured, it is proposed that the UL one way packet delay plus DL one way packet delay could be regarded equal to the round trip packet delay. To distinguish the GTP-U packets for QoS Monitoring from the ones delivering the service packets, a new payload type QMP (QoS Monitoring Packet) in GTP-U header (between UPF and RAN) and in SDAP/PDCP header (between UE and RAN) is introduced. + +When the DL one way packet delay monitoring is activated by the network, the UPF samples the DL service packets of the QoS Flow as monitoring packet and sends it to the RAN: + +- Step1. UPF samples the DL service packets of the QoS Flow based on the measurement period as monitoring packet. The UPF encapsulates the GTP-U header with QFI, TEID, sequence number and QMP indicator. The UPF sends the monitoring packets to the RAN. The UPF records the local time T1 after sending out the packets to the RAN successfully. +- Step2. When receiving the monitoring packets, RAN records the sequence number in the GTP-U header and the local time T2, initiates packet delay measurement between RAN and UE. + +NOTE 1: How RAN and UE measure the DL packet delay of Uu interface depends on RAN decision. + +- Step3. When getting the DL packet delay result of Uu interface, RAN encapsulates QMP indicator in the GTP-U header of the measurement response packet and sends it to the UPF. RAN also includes the corresponding sequence number, DL one way packet delay result of Uu interface ( $T_{DL-Uu}$ ), local time T5 when the response packet sent out, together with the T2 recorded in step 2, in the response packet. + +NOTE 2: RAN can send a new defined message as the monitoring response packet to the UPF, or the RAN could utilize the UL G-PDU which delivering the service packets as the monitoring response packet. If the G-PDU is used, the information in step 3 is contained in the GTP-U extended header. + +- Step4. UPF records the local time T6 and gets the DL one way packet delay of Uu interface when receiving the monitoring response packet identified by the sequence number. + +It is assumed that the packet delay between the RAN and UPF is regarded as symmetric, so approximate one way latency of N3 interface could be calculated based on the round trip packet delay of N3 interface. The round trip packet delay of N3 interface could be calculated by UPF as $T_{RTT-N3} = (T6-T1) - (T5-T2)$ . + +The E2E DL one way packet delay could be calculated by UPF as $T_{PDB-DL} = T_{DL-Uu} + (T_{RTT-N3} / 2)$ . + +When the UL one way packet delay monitoring is activated by the network: + +- Step 1. UE samples the UL service packets of the QoS Flow based on the measurement period as monitoring packet. UE encapsulates the SDAP/PDCP header with QMP indicator. The UE sends the monitoring packets to the RAN. +- Step 2. When receiving the monitoring packets, RAN would calculate the UL packet delay of Uu interface. + +NOTE 3: The detailed QoS Monitoring mechanisms adopted in RAN part depends on RAN decision. + +- Step 3. RAN encapsulates QMP indicator in the GTP-U header of the UL G-PDU packet and send it to the UPF. RAN also includes the UL one way packet delay result ( $T_{UL-Uu}$ ) of Uu interface in the GTP-U extended header. +- Step 4. UPF gets the UL one way packet delay of Uu interface when receiving the monitoring packet. + +The E2E UL one way packet delay is calculated by UPF as $T_{PDB-UL} = T_{UL-Uu} + (T_{RTT-N3} / 2)$ . + +NOTE 4: RAN can encapsulate both DL and UL packet delay of Uu interface in the GTP-U extended header of the same UL G-PDU packet in step 3. + +##### 6.8.1.2.3 Option 3: Using newly defined packets based on time synchronization + +This solution assumes the 5G internal system clock or external system clock (e.g. TSN network domain) is made available to all user plane nodes in the 5G system. The one way packet delay of Uu interface could be measured by UE and RAN based on time synchronization mechanism between UE and RAN, and the one way packet delay of N3 interface could be measured by RAN and UPF directly according to the time stamp information carried by the measurement packet, if UPF is time synchronized with RAN and UE. This solution is quite similar as option 1, with the following exceptions: + +When the packet delay monitoring is activated by the network: + +- The UPF records the local time T1 when creating the monitoring packets and encapsulates the time stamp T1 in the monitoring packets (e.g. in the GTP-U header or in the monitoring packets body). +- When receiving the monitoring packets from UPF, RAN records local time T2, and calculates the DL packet delay of N3 interface as $T_{DL-N3} = T2 - T1$ . +- When receiving the monitoring response packets from UE, RAN encapsulates local time T5 when sending the response packet to the UPF, together with the $T_{DL-N3}$ in step 2 in the response packet. +- When receiving the monitoring packets from RAN, the UPF records local time T6, and calculates the UL packet delay of N3 interface as $T_{UL-N3} = T6 - T5$ . + +NOTE: How the UPF get the UL and DL packet delay of Uu interface refers to option 1. + +##### 6.8.1.2.4 Option 4: Using actual service packets based on time synchronization + +This solution assumes the 5G internal system clock or external system clock (e.g. TSN network domain) is made available to all user plane nodes in the 5G system. The one way packet delay of Uu interface could be measured by UE and RAN based on time synchronization mechanism between UE and RAN, and the one way packet delay of N3 interface could be measured by RAN and UPF directly according to the time stamp information carried by the measurement packet, if UPF is time synchronized with RAN and UE. This solution is quite similar as option 2, with the following exceptions: + +When the one way packet delay monitoring for DL is activated by the network: + +- The UPF samples the DL service packets of the QoS Flow as monitoring packet. The UPF encapsulates time stamp T1 when sampling the DL service packets in the GTP-U header (other parameters encapsulated in the GTP-U header refer to option 2). +- When receiving the monitoring packets, RAN records the local time T2, and calculates the DL packet delay of N3 interface as $T_{DL-N3} = T2 - T1$ . +- When getting the DL packet delay result of Uu interface, the RAN encapsulates the $T_{DL-Uu}$ and $T_{DL-N3}$ in the packet sent to the UPF. +- The E2E DL one way packet delay is calculated by the UPF as $T_{PDB-DL} = T_{DL-Uu} + T_{DL-N3}$ . + +NOTE 1: How the UPF gets the DL packet delay of Uu interface refers to option 2. + +When the one way packet delay monitoring for UL is activated by the network: + +- When receiving the monitoring packets from UE, RAN encapsulates the $T_{UL-Uu}$ and the time stamp T5 when sending out the UL G-PDU packet in the GTP-U extended header. +- When receiving the monitoring packets from RAN, the UPF records local time T6, and calculates the UL packet delay of N3 interface as $T_{UL-N3} = T6 - T5$ . +- The E2E UL one way packet delay is calculated by UPF as $T_{PDB-UL} = T_{UL-Uu} + T_{UL-N3}$ . + +NOTE 2: How UPF gets the UL packet delay of Uu interface refers to option 2. + +#### 6.8.1.3 QoS Monitoring Policy + +The QoS Monitoring Policy is created by the PCF. The PCF sends the QoS Monitoring policy via Session Management Policy Modification procedure to the SMF, and instructs the SMF to initiate QoS Monitoring for the QoS Flow. The QoS Monitoring Policy provides round trip and/or one-way packet delay to be monitored and monitoring periodicity, optionally the corresponding threshold to trigger the reporting of the packet delay. Besides, the PCF also instructs the QoS Monitoring events report method in the QoS Monitoring policy, e.g. immediate report when the monitored QoS KPI cannot be fulfilled or reach certain threshold, or non-real time report. If the option 1 is adopted, the length of the monitoring packet may be included in the QoS Monitoring policy. + +NOTE: The non-real-time report can be sent according to one of the following configured events: Periodic report, when the UE enters CM-IDLE state, when the UE enters RRC-INACTIVE state, when the PDU Session is released. The PCF should also indicate the report period if periodic report is required. + +### 6.8.2 Procedures + +#### 6.8.2.1 QoS Monitoring Procedure + +Procedure in Figure 6.8.2-1 is used to activate QoS Monitoring. The QoS Monitoring can be triggered by the AF and PCF. + +![Sequence diagram for QoS Monitoring Activation procedure. The diagram shows interactions between UE, RAN, AMF, SMF, UPF, PCF, and AF. The process starts with the AF sending a request to the PCF, which then triggers a series of messages through the SMF, AMF, and RAN to the UE to activate the monitoring. The PCF also sends a response back to the AF.](164fae2c6490ee9f4cbf3c05758ecc57_img.jpg) + +``` + +sequenceDiagram + participant AF + participant PCF + participant SMF + participant AMF + participant RAN + participant UE + participant UPF + + Note right of AF: 0. Npcf_Policy_Authorization_Create/Update request + AF->>PCF: 0. Npcf_Policy_Authorization_Create/Update request + Note right of PCF: 1. Session Management Policy Modification + PCF-->>SMF: 1. Session Management Policy Modification + Note right of SMF: 2. Namf_Communication_N1N2 message transfer + SMF->>AMF: 2. Namf_Communication_N1N2 message transfer + Note right of AMF: 3. N2 Session Request + AMF->>RAN: 3. N2 Session Request + Note right of RAN: 4. AN-specific resource modification (including PDU Session Modification Command/Ack) + RAN-->>UE: 4. AN-specific resource modification (including PDU Session Modification Command/Ack) + Note right of RAN: 5. N2 Session Response + RAN->>AMF: 5. N2 Session Response + Note right of AMF: 6. Nsmf_PDUSession_UpdateSMContext Request + AMF->>SMF: 6. Nsmf_PDUSession_UpdateSMContext Request + Note right of SMF: 7. Nsmf_PDUSession_UpdateSMContext Response + SMF-->>AMF: 7. Nsmf_PDUSession_UpdateSMContext Response + Note right of SMF: 8. N4 Session modification request + SMF->>UPF: 8. N4 Session modification request + Note right of UPF: 9. N4 Session modification response + UPF-->>SMF: 9. N4 Session modification response + Note right of SMF: 10. Session Management Policy Modification + SMF-->>PCF: 10. Session Management Policy Modification + Note right of PCF: 11. Npcf_Policy_Authorization_Create/Update response + PCF-->>AF: 11. Npcf_Policy_Authorization_Create/Update response + +``` + +Sequence diagram for QoS Monitoring Activation procedure. The diagram shows interactions between UE, RAN, AMF, SMF, UPF, PCF, and AF. The process starts with the AF sending a request to the PCF, which then triggers a series of messages through the SMF, AMF, and RAN to the UE to activate the monitoring. The PCF also sends a response back to the AF. + +Figure 6.8.2.1-1 Procedure for QoS Monitoring Activation + +0. The AF could trigger the QoS Monitoring procedure or subscribe for QoS Event Report by sending the Npcf\_Policy\_Authorization\_Create/Update request message directly to the PCF or via NEF which is based on local configuration. +1. Based on the service subscription and/or the request from the AF, the PCF determines to activate QoS Monitoring for the QoS Flow and generates the QoS Monitoring policy for the QoS Flow. The PCF sends the + +QoS Monitoring policy via Session Management Policy Modification procedure to the SMF, and instructs the SMF to initiate QoS Monitoring for the QoS Flow. + +2. When the SMF receives the QoS Monitoring policy via the Session Management Policy Modification procedure, the SMF indicates to the RAN to start QoS Monitoring via AMF in the Namf\_Communication\_N1N2 message transfer message. The SMF may indicate to the RAN via AMF to report the DL and UL packet delay result of Uu interface to the UPF. If option 2 is adopted, the SMF also includes the QoS Monitoring policy in the PDU Session Modification Command message sent to UE. + 3. The AMF forwards the QoS Monitoring indication received from SMF to the RAN via N2 Session Request message. + 4. The RAN forwards the PDU Session Modification Command message to UE. + 5. The RAN sends the N2 Session Response to the AMF. The RAN indicates whether the QoS Monitoring is accepted or not in this message. +- NOTE: RAN could reject the QoS Monitoring request for the QoS Flow based on RAN situation, e.g. when the load of RAN node is close to its capacity. +6. The AMF sends the Nsmf\_PDUSession\_UpdateSMContext Request to the SMF to indicate whether the QoS Monitoring policy is accepted or not by RAN. + 7. SMF sends Nsmf\_PDUSession\_UpdateSMContext Response to the AMF. + 8. The SMF determines the QoS parameters and QoS Monitoring events which need to be monitored and reported by UPF, e.g., one-way/round trip packet delay, and optionally the corresponding threshold and/or reporting period, and sends them to UPF via N4 Session modification request. + 9. When the UPF receives the QoS Monitoring policy of the QoS Flow, the UPF initiates QoS Monitoring. + 10. The SMF indicates the QoS Monitoring policy activation result to the PCF via the Session Management Policy Modification procedure. + 11. If QoS Monitoring activation is initiated by AF, the PCF sends the Npcf\_Policy\_Authorization\_Create/Update response to the AF to indicate the QoS Monitoring policy activation result. + +#### 6.8.2.2 QoS Monitoring Event Report by UPF + +Procedure in Figure 6.8.2.2-1 is used for UPF to report QoS Monitoring Event to the SMF. + +![Sequence diagram showing the procedure for QoS Monitoring Event Report by UPF. The diagram involves four participants: SMF, UPF, PCF, and AF. The sequence of messages is: 1. UPF sends a 'Trigger to QoS Monitoring Event Report' to SMF; 2a. UPF sends an 'N4 Report' to SMF; 2b. SMF sends an 'N4 Report ACK' to UPF; 3. SMF sends an 'Npcf_SMPolicyControl_Update(QoS Monitoring Event Report)' to PCF; 4. PCF sends an 'Npcf_PolicyAuthorization_Notify(QoS Monitoring Event Notification)' to AF.](7a1dee155822446f7828dcb055c465c3_img.jpg) + +``` + +sequenceDiagram + participant SMF + participant UPF + participant PCF + participant AF + Note right of UPF: 1. Trigger to QoS Monitoring Event Report + UPF->>SMF: 2a. N4 Report + SMF->>UPF: 2b. N4 Report ACK + SMF->>PCF: 3. Npcf_SMPolicyControl_Update(QoS Monitoring Event Report) + PCF->>AF: 4. Npcf_PolicyAuthorization_Notify(QoS Monitoring Event Notification) + +``` + +Sequence diagram showing the procedure for QoS Monitoring Event Report by UPF. The diagram involves four participants: SMF, UPF, PCF, and AF. The sequence of messages is: 1. UPF sends a 'Trigger to QoS Monitoring Event Report' to SMF; 2a. UPF sends an 'N4 Report' to SMF; 2b. SMF sends an 'N4 Report ACK' to UPF; 3. SMF sends an 'Npcf\_SMPolicyControl\_Update(QoS Monitoring Event Report)' to PCF; 4. PCF sends an 'Npcf\_PolicyAuthorization\_Notify(QoS Monitoring Event Notification)' to AF. + +**Figure 6.8.2.2-1: Procedure for QoS Monitoring Event Report by UPF** + +1. When the QoS Monitoring event is triggered, the UPF initiates QoS Monitoring events report via the N4 Session report procedure. + +- 2a. The UPF sends N4 Report to the SMF carrying the QoS Monitoring Event Report: Timestamp of event, Name of event, measured value of QoS parameter, PDU Session ID, QFI. If the cell ID can be obtained by the UPF, the cell ID may also be included in the report message. +- 2b. The SMF sends N4 Report ACK to the UPF. +3. The SMF forwards the QoS Monitoring Event Report to the PCF by using Npcf\_SMPolicyControl\_Update service. The message includes Timestamp of event, reporting function ID (RAN ID or UPF ID), Name of event, measured value of QoS parameter, UE ID (GPSI), and optionally the cell ID. +4. The PCF sends QoS Monitoring Event Notification to the subscribed AF by using Npcf\_PolicyAuthorization\_Notify service. The QoS Monitoring Event Notification include Timestamp of event, Name of event, measured value of QoS parameter(s), UE ID (GPSI). + +### 6.8.3 Impacts on Existing Nodes and Functionality + +- AF: AF may send request message to trigger the 5GC to initiate QoS Monitoring for the URLLC service of the UE. The monitored QoS parameters may be included in the request message. +- PCF: Based on the subscription and/or AF's request, PCF creates the QoS Monitoring policy. PCF provides the QoS Monitoring policy to the SMF and instructs the SMF to initiate QoS Monitoring for the QoS Flow. +- SMF: SMF decomposes the QoS Monitoring policy received from the PCF, and triggers the QoS Monitoring in the UPF, RAN and UE respectively. +- UPF: Initiates QoS Monitoring for the QoS Flow based on the QoS Monitoring policy received via N4 message. When the QoS Monitoring events match the reporting condition, the UPF reports the QoS Monitoring events to the SMF. + +If all user plane nodes of 5G system are time synchronized, the UPF sends the DL monitoring packet to RAN, which carrying the time stamp when sampling the service packet as the monitoring packet. The UPF may calculate the UL packet delay of N3 interface based on the time stamp received from RAN and the local time when receiving the monitoring packet if the RAN sends the DL packet delay report to the UPF. + +- RAN: When receiving the monitoring packet from UPF and UE, RAN initiates the DL and UL packet delay measurement for Uu interface. RAN provides the packet delay of Uu interface to the UPF via a new GTP-U packet or via the UL GTP-U data packet. + +If all user plane nodes of 5G system are time synchronized, the RAN sends the UL monitoring packet to UPF, which carries the time stamp when sending out the monitoring packet. The RAN calculates the DL packet delay of N3 interface based on the time stamp received from UPF and the local time when receiving the monitoring packet. + +- UE: If option 1 is adopted, the UE cooperates with RAN to measure the DL and UL packet delay of Uu interface. If option 2 is adopted, the UE initiates QoS Monitoring for the QoS Flow based on the QoS Monitoring policy received via N1 message. + +### 6.8.4 Solution Evaluation + +**Editor's note:** As indicated by RAN2 in LS from RAN2 S2-1812451 the RAN aspects fall within scope of the planned Rel-16 WI/SI "RAN-centric Data Collection and Utilization for NR" that will start in Feb. 2019. + +## 6.9 Solution #9 for Key Issue 5, supporting low latency for initial data delivery without requiring that the UE to always be in RRC\_Connected State + +### 6.9.1 Description + +This solution applies to key Issue 5 when the UE change state from RRC\_Inactive to RRC\_Connected in another NG-RAN node than the one that has the UE context, where the nodes are within the same RAN Notification Area, and there are MO or MT data that need to be delivered with ultra low latency or with low jitter. + +This solution allows the UE to deliver initial ultra low latency data to the existing DNN via the Xn interface without having the network to reconfigure the N3 and possible also the N6 interface. + +CM-CONNECTED with RRC Inactive is used for URLLC User Data with following enhancement: + +- RAN uses at least the QoS information to detect if URLLC is requested. +- RAN receives an indication from the UE if a URLLC PDU Session shall be resumed. +- When the UE send RRC\_Resume request to a NG-RAN Node that does not have the UE Context then RAN may decide that the anchor NG-RAN Node will not do a path switch of N3 to the new NG-RAN Node immediately. + +NOTE: It is up to RAN to decide when to start the transfer of user data to the Anchor RAN Node in relation to the procedure to retrieve the UE Context from the Anchor RAN Node. RAN may decide to only deliver the first EDT from the UE and then perform N3 path switch or, temporary setup a data forwarding tunnel of the PDU session over the Xn interface (TS 38.420 [12] and TS 38.415 [13]) or not to switching N3 path to serving NG-RAN to avoid unnecessary N2 signalling if it is limited size of URLLC user data. If the path switch was executed then the new NG-RAN node will become the new anchor NG-RAN node. + +- When the UE is handed over from one non-anchor RAN node to another within the same RAN Notification Area (RNA), the RAN anchor node may decide to defer re-anchoring. + +Editor's note: It is FFS how N2 control plane signalling is to be handled for a UE for which the path switch is deferred. + +### 6.9.2 Procedures + +The procedure below shows the ultra low latency solution where the user data is delivered over Xn. + +![Sequence diagram illustrating ultra low latency user data delivery. The diagram shows interactions between UE, Non-anchor RAN node 1, Anchor RAN node, UPF, and DN. The process starts with an RRC_Resume Request from the UE to Non-anchor RAN node 1. The Non-anchor RAN node 1 then performs UE Context Retrieval & Forward Tunnel Establishment with the Anchor RAN node. The Anchor RAN node responds with an RRC resume message to the UE, which then sends an RRC_Connected message. The UE then sends MO and MT ultra low latency User Data to the Non-anchor RAN node 1, which is forwarded to the Anchor RAN node. The UE is then handed over from Non-anchor RAN node 1 to Non-anchor RAN node 2. The Anchor RAN node then sends MO and MT ultra low latency User Data to the UPF, which is then delivered to the DN. The Non-anchor RAN node 2 also sends MO and MT ultra low latency User Data to the UPF, which is then delivered to the DN.](4d7f667796a8cdcdd745e953ac11e289_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Non-anchor RAN node 1 + participant Anchor RAN node + participant UPF + participant DN + Note right of Non-anchor RAN node 1: Non-anchor RAN node 2 + + UE->>Non-anchor RAN node 1: 1. RRC_Resume Request + Non-anchor RAN node 1->>Anchor RAN node: 2. UE Context Retrieval & Forward Tunnel Establishment + Anchor RAN node->>Non-anchor RAN node 1: 3. RRC resume + Non-anchor RAN node 1->>UE: 4. RRC_Connected + UE->>Non-anchor RAN node 1: 5. MO and MT ultra low latency User Data + Non-anchor RAN node 1->>Anchor RAN node: 5. MO and MT ultra low latency User Data + UE->>Non-anchor RAN node 1: 6. UE handed over from Non-anchor RAN node 1 to Non-anchor RAN node 2 + Non-anchor RAN node 1->>Anchor RAN node: 6. UE handed over from Non-anchor RAN node 1 to Non-anchor RAN node 2 + Anchor RAN node->>UPF: 7. MO and MT ultra low latency User Data + UPF->>DN: 7. MO and MT ultra low latency User Data + Non-anchor RAN node 2->>UPF: 7. MO and MT ultra low latency User Data + UPF->>DN: 7. MO and MT ultra low latency User Data + +``` + +Sequence diagram illustrating ultra low latency user data delivery. The diagram shows interactions between UE, Non-anchor RAN node 1, Anchor RAN node, UPF, and DN. The process starts with an RRC\_Resume Request from the UE to Non-anchor RAN node 1. The Non-anchor RAN node 1 then performs UE Context Retrieval & Forward Tunnel Establishment with the Anchor RAN node. The Anchor RAN node responds with an RRC resume message to the UE, which then sends an RRC\_Connected message. The UE then sends MO and MT ultra low latency User Data to the Non-anchor RAN node 1, which is forwarded to the Anchor RAN node. The UE is then handed over from Non-anchor RAN node 1 to Non-anchor RAN node 2. The Anchor RAN node then sends MO and MT ultra low latency User Data to the UPF, which is then delivered to the DN. The Non-anchor RAN node 2 also sends MO and MT ultra low latency User Data to the UPF, which is then delivered to the DN. + +Figure 6.9.2.1: Ultra low latency user data delivery + +0. Precondition is that the UE successfully done a PDU Session Establishment Procedure according to clause 4.3.2.2.1 in TS 23.502 [3] and that SMF indicates in the N2 SM container using QoS information to the anchor NG-RAN Node that the PDU Session is used for URLLC. + +1. UE to NG-RAN: RRC Resume Request (Resume ID, Indicator) according to existing procedure under Non-anchor NG-RAN node 1. + +NOTE 1: A UE may have many PDU sessions established before entering RRC\_Inactive. Therefore, the UE need to indicate whether the Resume Request is linked to an URLLC PDU session or not. RAN needs to decide the format of this indication e.g. simple flag or PDU session ID. + +2. The new NG-RAN node (Non-anchor NG-RAN node 1) uses the Resume ID to identify the anchor NG-RAN node and request to retrieve the UE Context from the anchor NG-RAN Node. In case of EDT the UE context retrieval may also include the early data. If the resumed PDU Session is an URLLC PDU Session, the anchor NG-RAN Node may decide to configure the Non-anchor NG-RAN Node as a relay for that UE. In that case the Non-anchor NG-RAN Node 1 will relay future MO & MT user data between the UE and the Anchor RAN Node. + +NOTE 2: RAN needs to decide messages and procedures to support Xn forwarding tunnel feature. + +3. The Non-anchor RAN Node 1 sends the RRC Resume message to the UE. +4. The UE Enter RRC\_Connected state. +5. All MO user data will be transferred from the UE to the Non-anchor NG-RAN Node 1 and then over Xn to the anchor NG-RAN Node and further transported via existing N3 & N6 to the DNN and the low latency application service. MT user data will be sent in the opposite direction. +6. Due to UE mobility the UE is handed over from Non-anchor NG-RAN node 1 to Non-anchor NG-RAN node 2. The Anchor NG-RAN node decides to remain as anchor and defer any re-anchoring to later. +7. All MO and MT data between NG-RAN node 2 and the CN are relayed via the Anchor NG-RAN node. + +NOTE 3: Keeping the Anchor RAN node unchanged for UE in RRC\_CONNECTED state can be beneficial for low-latency communication by avoiding delays associated with traffic forwarding of traffic upon handover between Non-anchor RAN node 1 and Non-anchor RAN node 2 (either directly or via the Anchor RAN node). It is assumed that it is used in conjunction with RAN-level mechanisms for low-latency communication that are out of scope of this TR. The benefits of this specific aspect of the solution need to be evaluated. + +### 6.9.3 Impacts on Existing Nodes and Functionality + +RAN: + +- RAN, based on if the PDU Session is an URLLC PDU Session received from the SMF, may decide to establish a forwarding tunnel between the new NG-RAN and anchor NG-RAN during the Resume procedure or, RAN may decide to only forward the EDT user data included in RRC\_Resume\_Request in the UE Context Retrieval request and allow the Anchor NG-RAN Node to deliver the EDT user data over existing N3 without any N3 path switch. + +UE: + +- Indication of whether the Resume Request is linked to an URLLC PDU session or not. + +### 6.9.4 Solution Evaluation + +**Editor's note:** This clause provides an evaluation of this solution. + +## 6.10 Solution #10 for Key Issue #1: Multiple UEs per device for user plane redundancy with broadcast Network Reliability Group + +### 6.10.1 Description + +This solution is a variant of Solution #2 for Key Issue #1 (see clause 6.2). Only the differences compared to Solution #2 are described in this clause. + +To enable the UEs in the same device to select cells not sharing the same physical infrastructure (e.g. site, power supply, backhaul links), reliability groups are defined and configured by the operator, but (unlike Solution #2), these pertain only to the network and are broadcast by the gNBs in System Information. They are called Network Reliability Group (NRG). The operator may define a large number of NRGs (e.g. one NRG correspond to a set of cells either sharing their backhaul link), and each of the UEs in the device is not bound to a specific NRG. The UEs in the device coordinate with each other so that they do not camp on cells broadcasting the same NRG. + +NRG are assigned according to the risk modelling of the network infrastructure. When two cells have different NRG values, the network operator provides the guaranty that there no shared risk in the infrastructure. When two cells have + +the same NRG value, there is a possibility of shared risk / common point of failure in the network infrastructure, e.g. a shared backhaul link. + +The assumptions of Solution #2 apply, expect the following: + +- To ensure that the two UEs connect to different gNBs, the gNBs need to operate such that the selection of gNBs can be distinct from each other (e.g. gNBs operating in different frequencies etc.). + +The NRG of the RAN (cells of gNBs) entities are configured by the OAM system in RAN. It is possible for gNBs to learn the reliability group neighbouring cells as the Xn connectivity is set up. + +The NRG parameter of each cell is broadcast by the gNB, and each UE in the device stores this information and communicates it to the other UEs in the same device, so each UE in the device has knowledge about the NRG used by the other UEs. Each UE then provides NRG about the other UEs and its own to its RAN node via RRC. This will avoid selecting a cell broadcasting one of these NRGs, for initial Registration and idle-mode mobility. + +At device manufacture, the UEs in the device are assigned a rank: e.g. UE1, UE2, UE3, etc. When the device is started, first UE1 performs network selection normally. Then UE2 performs network selection and down-prioritizes cells broadcasting the NRG selected by UE1. Then UE3 performs network selection and down-prioritizes cells broadcasting any of the NRGs selected by UE1 or UE2. Etc. + +It follows that the device is always using cells belonging to different NRGs (as long as redundant RAN coverage is available), without the need for the gNB to redirect the UE to another cell. + +For connected mode mobility, each UE of the device informs the serving gNB of the NRG used by other UEs of the same device (e.g. along with measurement reports), and the serving gNB down-prioritizes candidate target cells that belong to NRGs already used by the device. It follows that the UE is preferably handed over only to cells in a way to preserve the diversity of NRGs for the device. + +### 6.10.2 Procedures + +RAN has its own NRG parameter configured into the gNBs on a per cell basis and broadcasts it in System Information. gNBs may learn the RAN NRG parameter of the neighbouring cells. + +The Registration procedure is unchanged. + +The RAN connected mode mobility handling is extended as follows. + +- UE informs the serving gNB of the NRGs used by other UEs of the same device (e.g. along with measurement reports). +- RAN node down-prioritizes handover targets whose NRG is used by other UEs of the device. + +### 6.10.3 Impacts on Existing Nodes and Functionality + +SMF, UPF, PCF/BSF impacts: see clause 6.2.3. + +RAN impacts: + +- OAM configuration of the NRG on a per cell level. +- Addition of NRG to System Information. +- RRC: gNB obtains the NRGs used by other UEs of the same device (e.g. along with measurement reports). +- gNB down-prioritizes handover targets whose NRG is used by other UEs of the device. + +Subscription impacts: none. + +AMF impacts: + +- Forward the relevant indications between RAN and SMF (not related to NRG but to Solution 2). + +UE impacts: + +- Support of multiple UEs per device. + +- UE reads the NRG in System Information. +- UE interacts with other UEs in the device so that each UE knows the NRGs already used by other UEs. +- UE selects the cell based on NRG information. +- UE informs the serving gNB of the NRGs used by other UEs of the same device (e.g. along with measurement reports). + +### 6.10.4 Solution Evaluation + +- The solution can provide disjoint redundant user plane paths through the 3GPP system including UE, RAN and CN. +- The solution ensures that the redundant user plane paths do not share the same risks, whenever possible. +- The solution uses IEEE FRER on upper layer between UE and DN. +- The solution does not impact the application itself, as replication can be performed by a networking protocol such as IEEE TSN FRER (see Annex A) which operates at an intermediate Ethernet switch or at the Ethernet layer of the endhost. Other protocols for replication are also applicable, such as DetNet (see Annex B) or proprietary protocols. +- The solution can be integrated with end to end redundancy solutions. +- The solution can provide the same level of redundancy as typically applied for fixed industrial deployments today. +- The solution is under control of the terminals. +- The solution uses multiple UEs in the terminal, hence it provides redundant UEs. +- The solution enables a flexible deployment as it can be deployed by defining NRGs based on the already deployed network without requiring the deployment of fully disjoint RANs or CNs. +- In certain deployments, this solution might require the UE(s) to be aware of the frequencies supported by gNB(s). + +Editor's note: need for gNB to be aware of neighbour node's support for NRG to make it usable in certain deployment scenarios is FFS. + +## 6.11 Solution #11 for Key Issue #3: Anchor change for Ethernet PDU Session + +### 6.11.1 Description + +The solution allows for Ethernet PDU Sessions to change the PDU Session Anchor (PSA) while the session remains set up. Originally the Ethernet PDU Session goes via the Source UPF acting as the PSA. The Source UPF maintains an Ethernet context which includes the MAC address of the UE (and possibly its VLAN tag) that the Source UPF has learned. It is possible to store multiple MAC addresses (with their VLAN tags) in case multiple MAC addresses are reachable via the UE. The Ethernet context is replicated in the SMF. + +![Figure 6.11.1-1: Solution architecture diagram showing the transition of a UE's data path during an Ethernet PDU Session anchor relocation. The diagram illustrates the network components (UDM, PCF, NEF, NRF, AMF, SMF) and the transition from a Source gNB to a Target gNB, with corresponding Source and Target UPFs. The Source UPF is connected to an ETH subnet cloud, and the Target UPF is shown with an 'Update ETH forwarding' callout.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +The diagram illustrates the solution architecture for Ethernet PDU Session anchor relocation. At the top, a Service Based Interface (SBI) connects the UDM, PCF, and NEF to the NRF, AMF, and SMF. The SMF contains an 'ETH cnxnt' (Ethernet context) box. Below this, the UE is shown with two states: 'Before HO' (Handover) and 'After HO'. In the 'Before HO' state, the UE is connected to a Source gNB, which is connected to a Source UPF. The Source UPF is connected to an 'ETH subnet' cloud. In the 'After HO' state, the UE is connected to a Target gNB, which is connected to a Target UPF. The Target UPF is also connected to the 'ETH subnet' cloud. A yellow callout box labeled 'Update ETH forwarding' points to the Target UPF, indicating that the Target UPF may take action to update the Ethernet forwarding in the data network. + +Figure 6.11.1-1: Solution architecture diagram showing the transition of a UE's data path during an Ethernet PDU Session anchor relocation. The diagram illustrates the network components (UDM, PCF, NEF, NRF, AMF, SMF) and the transition from a Source gNB to a Target gNB, with corresponding Source and Target UPFs. The Source UPF is connected to an ETH subnet cloud, and the Target UPF is shown with an 'Update ETH forwarding' callout. + +**Figure 6.11.1-1: Solution architecture** + +The SMF determines that a serving PDU Session anchor needs to be changed. Specific event triggers are not specified; hence the SMF has the flexibility to change the anchor according to the needs of various use cases. UE idle and connected mode mobility may be a frequent trigger for changing the anchor point, however other events should not be excluded. For example, the SMF could decide to relocate an Ethernet PDU Session anchor for load balancing or rebalancing, because a different UPF provides a data path with greater reliability, because a different UPF is more suitable for meeting QoS requirements, for maintenance, or for other reasons. The SMF determines the need for changing the anchor, selects the Target UPF when necessary, and establishes the N4 session at the Target UPF. The Ethernet context is also sent to the Target UPF. Based on the information in the Ethernet context, the Target UPF may take action to update the Ethernet forwarding in the data network. + +- If the Ethernet subnetwork uses forwarding based on MAC learning, then the fast update of the Ethernet forwarding can be achieved via a variety of mechanisms the use of which are specific to the DN and the specification of which are out-of-scope for 3GPP. The UPF may for example issue a Gratuitous ARP (GARP) containing the MAC address(es) of the UE that has switched to the new anchor. Alternatively, the UPF may send an unsolicited Neighbor Discovery Protocol (NDP) Neighbor Advertisement message indicating the UE MAC addresses, the UPF may generate a user plane frame with the UE's MAC addresses (and possibly its VLAN tag) and configurable payload which will be dropped by the endhosts, or the UPF may send another message compatible with DN protocols. Note that the Ethernet forwarding would eventually be updated without these techniques, when the UE sends an uplink Ethernet frame; but in that case the update of the forwarding is slower and prior to the sending of the uplink frame from the UE, downlink frames would be forwarded to the source UPF. +- If the Ethernet subnetwork uses forwarding based on a centralized controller setting the forwarding rules of the Ethernet switches, then the update of the Ethernet forwarding rules can be achieved by the Target UPF also acting as an Ethernet switch notifying the central controller that the given MAC address is now reachable at the new address. + +When the Ethernet context includes multiple MAC addresses, the above is performed for each MAC address. After the Target UPF is set up for the given UE, the RAN is notified about the change in the UPF, and the Source UPF can be released. + +### 6.11.2 Procedures + +This procedure for Ethernet PDU Session Anchor relocation is shown in figure 6.11.2-1. It greatly simplifies release 15 mechanisms for Ethernet PDU session re-anchoring while maintaining flexible triggering of the SMF to select a new anchor UPF for any reason. Unlike SSC Mode 2 or SSC Mode 3 procedures, the UE is not impacted by signaling or by the allocation of a new address. + +When the SMF decides that an anchor relocation is necessary, it establishes an N4 session with the new UPF. The RAN is informed of the new N3 GTP tunnel endpoint, and switches the uplink path to the new UPF. The SMF may subsequently instruct the UPF to assist with update of DN switch forwarding tables. + +![Sequence diagram for Figure 6.11.2-1: Procedure for anchor change. The diagram shows the interaction between UE, Source RAN, Target RAN, Source UPF, Target UPF, AMF, and SMF. It details the signaling for an anchor change, including N4 reports, N2 path switches, and PDU session modifications. The process is divided into 'In case of handover' and 'In case of no handover, connected mode'.](e6df2733626a85205c1db682e6259c46_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source RAN + participant Target RAN + participant Source UPF + participant Target UPF + participant AMF + participant SMF + + Note left of UE: User data + Source UPF->>SMF: 1. N4 Report Update ETH context + SMF-->>Source UPF: 2. N4 Report Ack + + Note left of Source RAN: In case of handover + Note left of Source RAN: 3. Handover preparation and execution + Target RAN->>AMF: 4. N2 Path Switch Request + AMF->>SMF: 5. Nsmf_PDUSession_UpdateSMContext Request + Note right of SMF: 6. Select new UPF + SMF->>Target UPF: 7. N4 Session Establishment Request + Target UPF-->>SMF: 8. N4 Session Establishment Response + SMF->>AMF: 9. Nsmf_PDUSession_UpdateSMContext Response + AMF-->>Target RAN: 10. N2 Path Switch Request Ack + + Note left of Target RAN: In case of no handover, connected mode + SMF->>Target RAN: 11. PDU Session Modify Request + Target RAN-->>SMF: 12. PDU Session Modify Response + + Note left of Target RAN: UL User data + Target RAN->>Target UPF: 13. N4 Session Modification Request Set Ethernet context + Target UPF-->>SMF: 14. N4 Session Modification Response + Note right of Target UPF: 15: Update ETH forwarding in subnet + + Note left of UE: UL+DL User data + SMF->>Target UPF: 16. N4 Session Release Request + Target UPF-->>SMF: 17. N4 Session Release Response + +``` + +Sequence diagram for Figure 6.11.2-1: Procedure for anchor change. The diagram shows the interaction between UE, Source RAN, Target RAN, Source UPF, Target UPF, AMF, and SMF. It details the signaling for an anchor change, including N4 reports, N2 path switches, and PDU session modifications. The process is divided into 'In case of handover' and 'In case of no handover, connected mode'. + +**Figure 6.11.2-1: Procedure for anchor change** + +Initially, the Ethernet PDU Session is established with the user data going via the Source UPF. The Source UPF acts as the PSA. + +1. The Source UPF informs the SMF about the Ethernet context, i.e. any information maintained related to the Ethernet network that the UPF interfaces with. Specifically, this contains the MAC address (or addresses) , and possibly the VLAN tag that the UPF has learned from the UE side. In case of any changes in the Ethernet context, the change is updated to the SMF so that the SMF maintains an up-to-date copy of the Ethernet context in the UPF. This signaling may be realized based on the N4 reporting procedure. Note that SMF notification about the MAC address in use is already defined for Ethernet PDU Sessions. As specified in TS 23.501 [2], clause 5.8.2.5: "The SMF may ask to get notified with the source MAC addresses used by the UE and provide UPF with corresponding forwarding rules related with these MAC addresses." The solution here works no matter whether the MAC forwarding rules are provided to the UPF by SMF or not. + +2. The UPF's report is acknowledged. +- 3-5. Handover procedure may take place, including path switch signalling to the AMF and corresponding signalling to SMF. +6. The SMF decides that the PSA is to be changed for the Ethernet PDU Session, and selects the Target UPF that will act as the new PSA. The decision may be triggered by a mobility event, such as receiving the message in step 5. +7. The Target UPF N4 session is established. The SMF provides the N3 tunnel endpoint used by RAN. +8. The establishment of the new N4 session is acknowledged from the Target UPF to the SMF. The UPF provides its N3 tunnel endpoint. +- 9-10. In case of a handover, the SMF signals to the gNB via the AMF to provide the Path Switch Request Ack, which includes the update of the uplink N3 tunnel endpoint to the target UPF. +- 11-12. If there is no handover, but the UE is in connected mode, the SMF sends PDU Session Modify Request message to the RAN via the AMF, which includes the update of the uplink N3 tunnel endpoint to the target UPF. The RAN acknowledges the message. + +After steps 9-10 or 11-12, uplink frames pass via the target UPF. Downlink frames may continue to be delivered from the source UPF to the gNB. In case of handover, the frames are forwarded from the source gNB to the target gNB. + +- 13-14. The SMF sends an N4 Session Modification Request to the Target UPF which includes the Ethernet context that serves as a trigger for the next step 15. The Target UPF acknowledges by an N4 Session Modification Response. +15. The Target UPF may assist update of Ethernet forwarding tables in the DN via a variety of mechanisms, the use of which are specific to the DN and the specification of which are out-of-scope for 3GPP. The UPF may for example issue a Gratuitous ARP (GARP) containing the MAC address(es) of the UE that has switched to the new anchor, or the UPF may send an unsolicited Neighbor Discovery Protocol (NDP) Neighbor Advertisement message indicating the UE MAC addresses, or the UPF may generate a user plane frame with the UE's MAC addresses (and possibly its VLAN tag) and configurable payload which will be dropped by endhosts, or the UPF may send another message or frame compatible with DN protocols. + +In the case of a central controller in the Ethernet network which sets the forwarding tables, the central controller may be instructed that the given MAC address is reachable at the new location. When multiple MAC addresses are present in the Ethernet context, this step may be repeated for each MAC address. + +16. The N4 session is released at the Source UPF. The source UPF may wait for a configurable period before it stops delivering downlink frames for the given PDU Session. +17. The N4 session release is acknowledged from the Source UPF to the SMF. + +NOTE: The procedure does not send an end marker to RAN. RAN should be configured such that it does not expect such an end marker and may decide to deliver downlink frames coming on the new user plane path even before the end of downlink frames on the old path. + +### 6.11.3 Impacts on Existing Nodes and Functionality + +The solution has the following impact on the nodes: + +SMF: + +- Store the Ethernet context including one or more MAC addresses based on reporting from the UPF. +- Decide to establish new PSA and release old PSA for the Ethernet PDU Session. + +UPF: + +- Report the Ethernet context including one or more MAC addresses. + +- Update the Ethernet forwarding in the Ethernet subnetwork after the SMF has established a new N4 session at a new UPF and the Ethernet context has been sent to the new UPF. + +RAN: + +- Be configured not to expect an end marker for the Ethernet PDU Session. + +### 6.11.4 Solution Evaluation + +**Editor's note:** This clause provides an evaluation of this solution. + +## 6.12 Solution #12 for Key Issue #3: Ethernet PDU Session Anchor Relocation + +### 6.12.1 Description + +**NOTE:** This solution has been merged into Solution #11. It will not be updated anymore. + +This solution addresses Key Issue #3: Enhancement of Session Continuity during UE Mobility, which "focuses on enhancing session continuity while maintaining UP efficiency". To achieve low latency for URLLC, close proximity between the PDU Session Anchor and the access node is required. Maintaining this proximity as the UE moves will at times require re-anchoring of the PDU session. The solution also supports Key Issue #1: Supporting high reliability by redundant transmission in user plane, as the ability to re-anchor a PDU session facilitates establishing and maintaining multiple paths to the UE. + +In Release 15, procedures were defined in TS 23.502 [3] to allow for change of the PDU session anchor according to the PDU Session SSC Mode. For SSC mode 2, the network may trigger the release of a PDU session and then instruct the UE to immediately establish a new PDU Session to the same DN, at which point a new PDU Session anchor may be selected. For SSC mode 3, the network allows the establishment of UE connectivity via a new PDU Session Anchor to the same DN before connectivity between the UE and the previous PDU Session Anchor is released. In both cases the PDU session anchor is transferred to a new UPF as illustrated in Figure 6.12.1-1. For IP PDU Sessions the UE is allocated an IP address corresponding to the prefix/subnet of the PDU session anchor. When the anchor changes, the old IP address may be released and a new one assigned to the UE. The process is message intensive (as many as 30+, counting optional messages) and requires signaling with the UE. + +![Diagram illustrating Ethernet PDU Session Anchor Relocation. At the top, a cloud labeled 'SMF Decides to Relocate a Ethernet PDU Session Anchor of the UE' is connected to three boxes labeled 'AMF', 'SMF', and 'PCF'. Below this, a central cloud labeled 'Ethernet DN' is shown. To the left, a 'Local Cluster' contains several UE icons and an 'Old UPF' box. To the right, another 'Local Cluster' contains UE icons and a 'New UPF' box. A large red arrow points from the 'Old UPF' to the 'New UPF', indicating the relocation of the PDU session anchor.](0019f09403376d6444ee323591fa2e98_img.jpg) + +Diagram illustrating Ethernet PDU Session Anchor Relocation. At the top, a cloud labeled 'SMF Decides to Relocate a Ethernet PDU Session Anchor of the UE' is connected to three boxes labeled 'AMF', 'SMF', and 'PCF'. Below this, a central cloud labeled 'Ethernet DN' is shown. To the left, a 'Local Cluster' contains several UE icons and an 'Old UPF' box. To the right, another 'Local Cluster' contains UE icons and a 'New UPF' box. A large red arrow points from the 'Old UPF' to the 'New UPF', indicating the relocation of the PDU session anchor. + +**Figure 6.12.1-1: Ethernet PDU Session Anchor Relocation** + +For Ethernet PDU sessions, a PDU Session re-anchor does not require a UE address change as the UE MAC address is not tied to the network topology. Forwarding of Ethernet frames is based on MAC learning or other mechanisms to update the forwarding tables of switches in the DN. Re-anchor of Unstructured Data PDU Sessions in which UE identifiers are not associated with the PDU Session anchor also does not impact the UE. Hence for these non-IP PDU Sessions, altering a data path to a new PDU session anchor may be achieved by updating forwarding tables rather than through 3GPP signaling. For Ethernet PDU sessions, well established protocols to update switch paths may be used. + +Observation 1: PDU session anchor change for Ethernet PDU Sessions does not require signaling with the UE. + +In current TS 23.502 [3] procedures, the SMF determines that the serving PDU Session anchor needs to be changed. Specific event triggers are not specified; hence the SMF has the flexibility to change the anchor according to the needs of various use cases. For URLLC, UE mobility may be a frequent trigger for changing the anchor point, however other events should not be excluded. For example, the SMF could decide to relocate an Ethernet PDU Session anchor for load balancing or rebalancing, because a different UPF provides a data path with greater reliability, because a different UPF is more suitable for meeting QoS requirements, for maintenance, because a UPF resides in a specific jurisdiction, or for other reasons. + +Observation 2: Currently any event can trigger the SMF to relocate a PDU session anchor. A variety of triggers can be useful for URLLC Ethernet PDU Sessions. + +For switches upstream of the UPF, normal Ethernet networking applies after a PDU session anchor has relocated to a new UPF. When a new UPF sends a DN switch an uplink packet containing a UE MAC address, the switch updates its forwarding table so that downlink packets are forwarded to the new UPF. In the absence of uplink packets from the UE, the downlink path may still be updated by having the new UPF issue Gratuitous ARPs (ARP Requests) containing the MAC address(es) of the UE that has switched to the new anchor. The MAC address(es) may be obtained via 3GPP signalling from the old UPF. The switch table updated changes the downlink path from the old UPF to the new UPF. Note that the gratuitous ARP is sent by the UPF only towards the DN. + +Observation 3: Ethernet PDU Session relocation may be further optimized by the new UPF issuing to the DN, an ARP containing MAC address(es) of the UE. The ARP updates switch forwarding tables so that in the absence of an uplink packet from the UE, downlink packets are sent to the new UPF. + +For IPv6 networks Neighbor Discovery Protocol (NDP) Neighbor Advertisement messages (unsolicited) may be used in place of ARP. + +### 6.12.2 Procedures + +This solution proposes Ethernet PDU Session Anchor relocation that eliminates signaling with the UE. The procedure is greatly simplified compared to release 15 while flexible triggering of the SMF to select a new anchor UPF for any reason is maintained. Because signalling is not required with the UE, a procedure for SSC Mode 2, where the old PDU session anchor is released before a new anchor is setup, is no longer needed. + +When the SMF decides that an anchor relocation is necessary, it establishes an N4 session with the new UPF. The RAN is informed of the new N3 GTP tunnel endpoint, which switches the uplink path to the new UPF. The SMF may then obtain from the old UPF, the UE MAC addresses of packets sent via the old path. The SMF subsequently requests that the new UPF issue a gratuitous ARP for the MAC addresses of the UE. + +The sequence is shown in Figure 6.12.2-1. + +#### Ethernet PDU Session Reanchor + +![Sequence diagram for Ethernet PDU Session Reanchor showing interactions between UE, RAN, AMF, UPF1, UPF2, and SMF.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant UPF1 + participant UPF2 + participant SMF + + Note right of SMF: 1. SMF Determines UPF Relocation needs to be performed + SMF->>UPF2: 2a. N4 Session Establishment Request + UPF2-->>SMF: 2b. N4 Session Establishment Response + SMF->>RAN: 3a. Namf_Communication_N1N2MessageTransfer + RAN-->>SMF: 3b. UP Path Switch Req. (UPF2 N3 TED) + SMF->>RAN: 3c. UP Path Switch Response + RAN-->>SMF: 3d. Namf_Communication_N1N2MessageTransfer Response + Note left of SMF: UL Ethernet Data + SMF->>UPF1: 4a. N4 Anchor Change Notification + UPF1-->>SMF: 4b. N4 Anchor Change Notification Response + Note left of SMF: DL Data Forwarding + SMF->>UPF2: 5. N4 DN Update Request + UPF2->>DN: 7.6. ARP, NDP Advert or UP Packet + Note left of SMF: DL Ethernet Data + +``` + +Sequence diagram for Ethernet PDU Session Reanchor showing interactions between UE, RAN, AMF, UPF1, UPF2, and SMF. + +**Figure 6.12.2-1: Ethernet PDU Session Relocation** + +1. The SMF determines that the UE will be better served by UPF2. +2. The SMF sets up the new Ethernet PDU Session Anchor in UPF2 by sending an N4 Session Establishment Request, providing UPF2 with the RAN N3 tunnel endpoint of the PDU Session. +3. The SMF sends a UPF Path Switch Request to the RAN. The SMF provides the RAN with the IP@ and TEID for UPF2. The RAN sends uplink packets through the tunnel to the new PDU Session anchor in UPF2. Responses to those packets are sent back to UPF2 (e.g. via switch data plane learning in the DN). +4. The SMF sends UPF1 an N4 Anchor Change Notification. +- 4b. UPF1 responds to the SMF with a N4 Anchor Change Notification Ack. The Ack contains UE MAC Address(es) learned from packets that traversed the UPF1 PDU session anchor. From this point onwards, UPF1 forwards DL data towards UPF2 for delivering towards the UE (for a preconfigured duration). The UPF1 releases the resources after data forwarding complete (for a preconfigured duration). +5. The SMF sends UPF2 a DN Update Request containing the UE MAC Addresses received in Step 5. +6. In order to ensure DN switches will forward downlink packets to UPF2 instead of UPF1, UPF2 sends to the DN a Gratuitous ARP, an unsolicited NDP Neighbor Advertisement or other message compatible with DN protocols. + +NOTE: Gratuitous ARP/ND assumes that the SMF/UPF can detect that the PDU Session of Ethernet type is used for IP traffic based on User plane traffic inspection. + +Editor's note: whether STP (spanning tree protocol) or some other protocol is used for informing the DN regarding PSA anchor change is FFS. + +Editor's note: how UPF relocation can be integrated along with HO procedure is FFS. + +### 6.12.3 Impacts on Existing Nodes and Functionality + +The solution has the following impact on the nodes. + +UE: No Impact. + +AMF: No Impact - messages to SMF are sent via transparent container. + +SMF: + +- Request MAC addresses from old UPF and Transport it to a new UPF. + +UPF: + +- Record/Store UE MAC addresses for each PDU Session and send them on N4 when requested by SMF. +- Send a Gratuitous ARP or UL Packet on N6 informing upstream switches to update their forwarding tables to the new UPF. + +### 6.12.4 Solution Evaluation + +**Editor's note:** This clause provides an evaluation of this solution. + +## 6.13 Solution #13 for Key Issue #3: Session continuity enhancement based on the coordination between AF and 5GC + +### 6.13.1 General Description + +This solution addresses the problem in the key issue 3 regarding "How to enable runtime coordination between AF and 5GC for supporting application relocation without breaking upper layer session and service continuity". + +In order to enable low latency service in the 5GC, a UE may establish a SSC mode 3 PDU session, or a PDU session with UL CL or branch point. In this case, if the PDU sessions anchor (PSA) needs to be relocated due to UE mobility, the SMF needs to select a new PSA. + +In order to avoid or minimize service interruption during PSA relocation, the solution proposes that, after the SMF prepares the UP path towards the new PSA, the SMF does not activate the UP path toward the new PSA immediately. Instead, the SMF sends a notification to the Application Function (AF). Before the UP path toward the new PSA is activated, application traffic data (if any exists) is routed through the old PSA.. + +The notification sent from the SMF to the AF indicates UP path management events as described in the TS 23.502 [3], such as 'PSA change' or 'DNAI change'. The AF can determine whether application relocation is needed according to the notification. If not, the AF can send a positive response to the notification, indicating application layer is ready, to the SMF immediately; otherwise, the AF sends the positive response after application relocation is completed or a negative response if the AF determines that the application relocation cannot be completed on time (e.g. due to temporary congestion). Once the SMF receives the positive AF response, the SMF activates the UP path toward the new PSA. After the UP path toward the new PSA is activated, data is routed through the new PSA. If the SMF receives a negative response, the SMF can cancel the PSA relocation. + +The SMF can assume according to local policy a negative response if a response is expected and but not received from the AF within a certain time window. + +### 6.13.2 Procedures + +#### 6.13.2.1 Procedure of Enhancing SSC mode 3 PDU Session Anchor Change with Multiple PDU Sessions + +![Sequence diagram illustrating the procedure of Enhancing SSC mode 3 PDU Session Anchor Change with Multiple PDU Sessions. The diagram shows interactions between UE, Target RAN, UPF (PSA1), UPF (PSA2), SMF, and AFs. The steps are: 1. Handover complete; 2. SMF decides to select target UPF based on UE location/DNAI; 3a. Early Notification from SMF to AFs, followed by Application Relocation and 3b. Notification Ack (Response) from AFs to SMF; 4. SSC mode 3 PDU Session anchor change as specified in clause 4.3.5.2 in TS 23.502; 5a. Late Notification from SMF to AFs, followed by Application Relocation and 5b. Notification Response from AFs to SMF; 6. PDU session release procedure.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Target RAN + participant UPF1 as UPF (PSA1) + participant UPF2 as UPF (PSA2) + participant SMF + participant AFs + + Note over UE, SMF: 1. Handover complete + Note right of SMF: 2. SMF decides to select target UPF based on UE location/DNAI + SMF-->>AFs: 3a. Early Notification + Note right of AFs: Application Relocation + AFs-->>SMF: 3b. Notification Ack (Response) + Note over UE, SMF: 4. SSC mode 3 PDU Session anchor change as specified in clause 4.3.5.2 in TS 23.502 + SMF-->>AFs: 5a. Late Notification + Note right of AFs: Application Relocation + AFs-->>SMF: 5b. Notification Response + Note over UE, SMF: 6. PDU session release procedure + +``` + +Sequence diagram illustrating the procedure of Enhancing SSC mode 3 PDU Session Anchor Change with Multiple PDU Sessions. The diagram shows interactions between UE, Target RAN, UPF (PSA1), UPF (PSA2), SMF, and AFs. The steps are: 1. Handover complete; 2. SMF decides to select target UPF based on UE location/DNAI; 3a. Early Notification from SMF to AFs, followed by Application Relocation and 3b. Notification Ack (Response) from AFs to SMF; 4. SSC mode 3 PDU Session anchor change as specified in clause 4.3.5.2 in TS 23.502; 5a. Late Notification from SMF to AFs, followed by Application Relocation and 5b. Notification Response from AFs to SMF; 6. PDU session release procedure. + +**Figure 6.13.2.1-1: Procedure of Enhancing SSC mode 3 PDU Session Anchor Change with Multiple PDU Sessions** + +1-2. The SMF determines to select a new target UPF as the new PSA based on the UE location or DNAIs received from an AF, e.g. after the handover. + +NOTE 1: While providing the DNAIs via PCF and NEF as specified in Clause 4.3.6 TS 23.502, according to the local policies, the AF may also indicate a preference of maintaining UE IP address. The SMF may take this indication into account to determine whether PSA change is needed. + +3. In the case of early notification, the SMF send a notification indicating PSA change and/or DNAI change for a UE (identified by the IP address/prefix of the UE or the MAC address used by the UE) to the AF. The AF determines whether the application layer service needs to be relocated for the UE based on the info of new PSA or DNAI, if not, the AF can send back a positive response immediately, otherwise, the AF responds the SMF with an ACK (a positive response) after the application relocation is completed successfully. If the AF sends a negative response, the SMF may decide to cancel the following PSA relocation. + +NOTE 2: The SMF determines according to local policy whether to wait for a response from the AF before continuing with the procedure of PSA relocation. + +NOTE 3: The AF behaviours on handling application relocation are out of scope of this study. However, target AS, located in target data network may be associated with local AF instance (called T-AF). In such cases, SMF/AF cancels earlier subscribed user plane management event notifications and T-AF subscribes to user plane management event notifications. + +4. SMF starts the procedure for change of SSC mode 3 PDU session anchor with multiple PDU sessions as defined in clause 4.3.5.2 in TS 23.502 [3]. +5. In the case of late notification, the SMF send notification indicating PSA change or DNAI change for the UE to the AF. The AF determines whether application relocation is required for the UE based on the info of new PSA or DNAI, if not, the AF can send back a positive response immediately, otherwise, the AF responds the SMF with an ACK (a positive response) after the application relocation is completed successfully. +6. SMF releases the old PDU session after the new PDU session is established and a positive response is received from the AF. + +NOTE 4: The SMF can assume according to local policy a negative response if a response is expected and but not received from the AF within a certain time window at the step 3 or step 5. + +#### 6.13.2.2 Procedure of Session Continuity Enhancement for a PDU Session with UL/CL or BP + +Figure 6.13.2.2-1 illustrates the procedure of using the coordination between AF and 5GC to enhance the session continuity for a PDU session with UL CL or BP. + +![Sequence diagram illustrating the procedure of Session Continuity Enhancement for a PDU Session with UL/CL or BP. The diagram shows interactions between UE, Target RAN, Old UPF (BP/UL CL), New UPF (BP/UL CL), UPF (PSA1), UPF (PSA2), SMF, and AFs. It details two cases: UL CL Case and BP Case, showing steps for handover, SMF decision, early notification, N4 session establishment, late notification, N4 session modification, N2 SM info, N2 SM info, late notification, N4 session modification, IPv6 prefix allocation, N4 session release, and N4 session release.](36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant TR as Target RAN + participant OUPF as Old UPF (BP/UL CL) + participant NUPF as New UPF (BP/UL CL) + participant PSA1 as UPF (PSA1) + participant PSA2 as UPF (PSA2) + participant SMF + participant AFs + + Note right of SMF: 2.SMf decides to select target UPF based on UE location/DNAI + + TR->>SMF: 1.Handover complete + SMF->>AFs: 3a.Early Notification + AFs-->>SMF: 3b.Notification Ack (Response) + SMF->>PSA2: 4.N4 Session establishment + PSA2-->>NUPF: 5.N4 Session establishment + Note right of AFs: Application Relocation + + Note left of TR: UL CL Case + SMF->>AFs: 6a.Late Notification + AFs-->>SMF: 6b.Notification Ack (Response) + Note right of AFs: Application Relocation + SMF->>AFs: 7.Notification ACK + SMF->>PSA2: 8.N4 Session modification + PSA2-->>TR: 9.N2 SM info (PDU session ID, CN tunnel info on new UL CL) + + Note left of TR: BP Case + SMF->>PSA2: 10.N2 SM info (PDU session ID, CN tunnel info on new BP) + PSA2-->>TR: 10.N2 SM info (PDU session ID, CN tunnel info on new BP) + SMF->>AFs: 11a.Late Notification + AFs-->>SMF: 11b.Notification Ack (Response) + Note right of AFs: Application Relocation + SMF->>AFs: 12.Notification ACK + SMF->>PSA2: 13.N4 Session modification + PSA2-->>TR: 14.IPV6 Prefix allocation + PSA1->>SMF: 12.N4 Session Release + SMF->>OUPF: 13.N4 Session Release + +``` + +Sequence diagram illustrating the procedure of Session Continuity Enhancement for a PDU Session with UL/CL or BP. The diagram shows interactions between UE, Target RAN, Old UPF (BP/UL CL), New UPF (BP/UL CL), UPF (PSA1), UPF (PSA2), SMF, and AFs. It details two cases: UL CL Case and BP Case, showing steps for handover, SMF decision, early notification, N4 session establishment, late notification, N4 session modification, N2 SM info, N2 SM info, late notification, N4 session modification, IPv6 prefix allocation, N4 session release, and N4 session release. + +Figure 6.13.2.2-1: Session continuity enhancement based on the coordination between AF and 5GC + +NOTE 1: The remote PDU session anchor exists but is not shown in the Figure 6.13.2.2-1. + +1-2. The SMF determines to select a new target UPF as the new PSA based on the UE location or DNAI, e.g. after the handover. + +3. In the case of early notification, the SMF send a notification indicating PSA change and/or DNAI change for a UE (identified by the IP address/prefix of the UE or the MAC address used by the UE) to the AF. The AF determines whether the application layer service needs to be relocated for the UE based on the info of new PSA or DNAI, if not, the AF can send back a positive response immediately, and then step 7 or 12 is not executed. If the AF sends a negative response in step 3b, the SMF may decide to cancel the following PSA relocation. + +NOTE 2: The SMF determines according to local policy whether to wait for a response from the AF before proceeding to configure the UP path toward the new PSA. + +NOTE 3: The AF behaviours on handling application relocation are out of scope of this study. However, target AS, located in target data network may be associated with local AF instance (called T-AF). In such cases, SMF/AF cancels earlier subscribed user plane management event notifications and T-AF subscribes to user plane management event notifications. + +4-5. Based on the new selected PSA, if UL CL or BP is used, the SMF may also determine to select a new UPF to act as UL CL or BP, and then selects a new UL CL or BP further. The SMF establishes CN tunnel between the new UL CL or BP and the new PSA if UL CL or BP is used. + +Steps 6 to 9 are only applied to UL CL case: + +6. In the case of late notification, the SMF send notification indicating PSA change or DNAI change for the UE to the AF. The AF determines whether application relocation is required for the UE based on the info of new PSA or DNAI, if not, the AF can send back a positive response immediately and step 7 is not executed. + +NOTE 4: The SMF determines according to local policy whether to wait for a response from the AF before proceeding to configure the UP path toward the new PSA. + +7. (Optional) In the case of application relocation, if the application relocation is completed successfully, the AF responds the SMF with an ACK (a positive response) which may include N6 traffic routing information, otherwise, the AF sends a negative response, and the SMF cancels the following PSA relocation without configuring the UP path toward the new PSA. + +8. Once the SMF receives the positive response in step 7 from the AF, the SMF updates the new PSA using the received N6 traffic routing information, and activates the UP path toward the new PSA (PSA2). + +9. The SMF activates the UP path toward the new PSA by sending N3 CN tunnel info of new UL CL to the RAN node, which is similar as the step 6 in Figure 4.3.5.4-1 in TS 23.502 [3]. + +Steps 10 to 14 are only applied to BP case: + +10. The SMF sends CN tunnel info of the new BP to the RAN node to establish the CN tunnel between the RAN and the BP, which is similar as the step 6 in Figure 4.3.5.4-1 in TS 23.502 [3]. + +11-13. Similar as steps 6 - 8. + +14. The SMF activates the UP path toward the new PSA by providing new allocated IPv6 prefix to the UE. + +15-16. The SMF release the UP path toward the old PSA. + +NOTE 5: The SMF can assume according to local policy a negative response if a response is expected and but not received from the AF within a certain time window after the step 3a, step 6a or step 11a. + +### 6.13.2 Impacts on Existing Nodes and Functionality + +In the SMF: + +- Wait for a response from the AF according to local policy after sending a UP path management event notification to the AF. +- Maintain old UP path while waiting for the response and take actions according to the response: activate the new UP path (including configuring N6 traffic routing info received in the AF response into PSA) or cancel the PSA relocation. + +In the AF: + +- Indicate an AF preference of maintaining UE IP address to the 5GC. + +### 6.13.3 Solution Evaluation + +This solution relies on runtime coordination between the SMF and the AF to enable the SMF to maintain the old UP path and switch traffic to new UP path only after being confirmed by the AF that the application layer is ready, which ensures session continuity and minimizes service interruption. + +## 6.14 Solution #14 for Key Issue #2: Lossless handover by timing coordination with multiple UEs per device + +### 6.14.1 Description + +This solution is an extension of Solution #2 described in clause 6.2 which provides redundancy against failures using two UEs in the device by setting up two independent paths via different gNBs in RAN. The solution provided here extends Solution #2 to protect against handover losses in order to address also Key Issue #2 in addition to addressing Key Issue #1. + +The two redundant paths can help improve the handover performance, since even if one of the paths suffers from a period of disruption during handover, the other path can still deliver the packets uninterrupted. For this, it is necessary to co-ordinate the handover timing at the gNBs where the UEs of the devices are connected. + +The Reliability Grouping concept in solution #2 is extended for handover timing co-ordination: each Reliability Group is assigned with preferred time periods for handover, so that these periods are disjoint for the Reliability Group. A UE in given reliability group will therefore be preferably scheduled for handover at a different time than a UE in another reliability group. E.g., periods of 100ms can be defined, so that for UEs in reliability group 1 handover are preferably started at odd periods, while for UEs in reliability group 2 handovers are preferably started at even periods. Note that the solution defines preferences, and in typical circumstances it can be possible to defer the handover for a short duration; but in cases where the radio link quality is quickly deteriorating, it is more important to perform handover as soon as possible and in such circumstances the preference may be ignored. + +The proposed handover coordination solution provides a simple extension to enhance then handover performance without applying complex signalling sequences and introducing additional handover timing coordination functionality. The extension allows the mobile operator to make good use of the redundant paths in a mobile system. While such redundant paths are set up to provide redundancy against node and link failures, in a mobile system the volatile handover process may be the one which is could most often actually cause disruption, hence the mechanisms for redundant user plane paths are made good use of. + +The figure below shows the solution architecture, with the Redundancy Grouping 1 (green) and 2. Using Solution #2, it is ensured that both UE1 and UE2 connect to gNBs in the same group. In the example shown below, UE1 performs handover from gNB1.1 to gNB1.2, while UE2 performs handover from gNB2.1 to gNB2.2. The solution relies on pre-configured schedules in the gNBs on when the handover for a UE in group 1 or in group 2 can be started. By keeping these schedules, the handover times of the UEs within the same device can be made different. + +![Diagram illustrating the reliability group-based redundancy concept in RAN. It shows two User Equipment (UE) units, UE1 and UE2, connected to a central Device. UE1 is connected to two gNBs, gNB1.1 and gNB1.2, which are both connected to a UPF1. UE2 is connected to two gNBs, gNB2.1 and gNB2.2, which are both connected to a UPF2. Both UPF1 and UPF2 are connected to a DN (Data Network). The diagram also shows the connection to AMF1, SMF1, AMF2, and SMF2, with interfaces N1, N2, N3, N4, and N6. Red circles with numbers 1 and 2 indicate the redundancy concept for UE1 and UE2 respectively.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +The diagram illustrates a network architecture with two User Equipment (UE) units, UE1 and UE2, connected to a central Device. UE1 is connected to two gNBs, gNB1.1 and gNB1.2, which are both connected to a UPF1. UE2 is connected to two gNBs, gNB2.1 and gNB2.2, which are both connected to a UPF2. Both UPF1 and UPF2 are connected to a DN (Data Network). The diagram also shows the connection to AMF1, SMF1, AMF2, and SMF2, with interfaces N1, N2, N3, N4, and N6. Red circles with numbers 1 and 2 indicate the redundancy concept for UE1 and UE2 respectively. + +Diagram illustrating the reliability group-based redundancy concept in RAN. It shows two User Equipment (UE) units, UE1 and UE2, connected to a central Device. UE1 is connected to two gNBs, gNB1.1 and gNB1.2, which are both connected to a UPF1. UE2 is connected to two gNBs, gNB2.1 and gNB2.2, which are both connected to a UPF2. Both UPF1 and UPF2 are connected to a DN (Data Network). The diagram also shows the connection to AMF1, SMF1, AMF2, and SMF2, with interfaces N1, N2, N3, N4, and N6. Red circles with numbers 1 and 2 indicate the redundancy concept for UE1 and UE2 respectively. + +**Figure 6.14.1-1: Reliability group-based redundancy concept in RAN** + +### 6.14.2 Procedures + +The solution consists of the following steps. + +- A priori configuration is used to configure preferred handover periods in each gNB for each reliability group. These preferred handover periods should be sufficiently long to allow handovers to be completed, and should be possible to be kept by the gNBs given the existing time synchronization; yet the preferred handover periods should not be too long to avoid having to wait too long with handovers. +- When a gNB determines that handover needs to take place for a UE which is a member of a reliability group (hence, we know that the UE is in a device equipped with multiple UEs), the gNB, whenever possible, schedules the handover in a preferred handover period corresponding to the reliability group (RG) of the given UE. That is, if the start of the handover would not be within the preferred handover period for the given RG, the gNB defers the handover until the start of the next preferred handover period for the given UE's RG. The deferral only applies to the execution of the handover, while the handover preparation can be done immediately. The RG of the UE is stored in the UE context based on information received from the CN. + +### 6.14.3 Impacts on Existing Nodes and Functionality + +In addition to the solution described in Key Issue #1, Solution #2, the following additional implementation impacts occur from this solution. + +RAN impacts: + +- Pre-configuration of preferred handover timing periods for each reliability group. +- Possible deferral of the handover so that it falls within a preferred handover period whenever possible. + +### 6.14.4 Solution Evaluation + +- Low impact extension of Solution #2 for Key Issue #1 provides a solution also for Key Issue #2 in a single solution framework. +- No need for additional RAN signalling for handover co-ordination. +- Possibility for limited deferral of the handover even if other UE of the same device does not perform handover. +- Lossless communication can be ensured even when the handover would imply temporary disruption. + +- Lossless communication can be ensured even when one of the UEs experiences radio link failure. + +## 6.15 Solution #15 for Key Issue #6: Division of E2E PDB + +### 6.15.1 Description + +This solution applies to key Issue #6. In the solution, besides of current PDB (i.e. PDB between UE and PSA UPF), the SMF will provide the RAN with the PDB between the PSA UPF and the RAN (i.e. PSA-RAN PDB), so that the RAN nodes can take it into account when deriving AN PDB. + +NOTE: Operator shall ensure the backhaul delay can satisfy the PSA-RAN PDB configured on the SMF. + +The SMF is locally configured by the OAM with the packet delay budgets between a specific RAN node and an PSA UPF (i.e. PSA-RAN PDB) for different 5QIs. The SMF can provide the RAN with the PSA-RAN PDB for a QoS Flow during the PDU Session Establishment procedure, the PDU Session Modification procedure or the Service Request procedure. + +### 6.15.2 Procedures + +#### 6.15.2.1 PDB provisioning during PDU Session Establishment /Modification or Service Request procedure + +Figure 6.15.2.1-1 depicts the enhanced PDB provision for a URLLC QoS Flow during PDU Session Establishment /Modification procedure and Service Request procedure. + +![Sequence diagram showing enhanced PDB provisioning for a URLLC QoS Flow. The diagram illustrates the interaction between UE, NG-RAN, AMF, UPF, SMF, NRF, UDM, and PCF. The process is divided into four steps: 1. UE triggered Service Request or PDU Session Establishment/Modification; 2a. Nsmf_PDUSession_UpdateSMContext Response from SMF to AMF; 2b. Namf_Communication_N1N2MessageTransfer from AMF to SMF; 3. N2 Session Request from SMF to NG-RAN; 4. Completion of the initial procedure steps.](35127fe87029df6f5f0b2ee85f6193f1_img.jpg) + +| UE | NG-RAN | AMF | UPF | SMF | NRF | UDM | PCF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|---------------------------------------------------------------------------------------------|-----|-----|-----|-----|-----| +| 1. Steps 1-10 of UE triggered Service Request procedure in clause 4.2.3.2 in TS 23.502, or steps 1- 10 of UE requested PDU Session Establishment procedure in clause 4.3.2.2.1 in TS 23.502, or steps 1a-3a of UE or network requested PDU Session Modification procedure in clause 4.3.3.2 in TS 23.502 | | | | | | | | +| | | 2a. Nsmf_PDUSession_UpdateSMContext Response (N2 SM Info (QFI, PDB, PSA-RAN PDB)) | | | | | | +| | | 2b. Namf_Communication_N1N2MessageTransfer (N2 SM Info, N2 SM Info (QFI, PDB, PSA-RAN PDB)) | | | | | | +| | 3. N2 Session Request (N2 SM Info (QFI, PDB, PSA-RAN PDB)) | | | | | | | +| 4. Steps 13-22b of UE triggered Service Request procedure in clause 4.2.3.2 in TS 23.502, or steps 13 - 20 of UE requested PDU Session Establishment Procedure in clause 4.3.2.2.1 in TS 23.502, or steps 5-13 of UE or network requested PDU Session Modification procedure in clause 4.3.3.2 in TS 23.502 | | | | | | | | + +Sequence diagram showing enhanced PDB provisioning for a URLLC QoS Flow. The diagram illustrates the interaction between UE, NG-RAN, AMF, UPF, SMF, NRF, UDM, and PCF. The process is divided into four steps: 1. UE triggered Service Request or PDU Session Establishment/Modification; 2a. Nsmf\_PDUSession\_UpdateSMContext Response from SMF to AMF; 2b. Namf\_Communication\_N1N2MessageTransfer from AMF to SMF; 3. N2 Session Request from SMF to NG-RAN; 4. Completion of the initial procedure steps. + +**Figure 6.15.2.1-1: Enhanced PDB provisioning for a URLLC QoS Flow** + +During UE triggered Service Request procedure, steps 1-22b from clause 4.2.3.2 in TS 23.502 [3] are performed with the following differences: + +- In steps 11-12, the PSA-RAN PDB together with PDB for each QoS Flow may be included in the N2 SM information and provided to the RAN node as depicted in step 2a and step 3 in Figure 6.15.2.1-1. + +During Network triggered Service Request procedure, steps 1-7 from clause 4.2.3.3 in TS 23.502 [3] are performed with the following differences: + +- In step 3a, the PSA-RAN PDB together with PDB for each QoS Flow may be included in the N2 SM information and sent to the AMF via Namf\_Communication\_N1N2MessageTransfer request as depicted in step 2b in Figure 6.15.2.1-1. +- In step 4a, when the steps 12 to 22 in UE Triggered Service Request procedure in clause 4.2.3.2 in TS 23.502 [3] are invoked, the PSA-RAN PDB together with PDB for each QoS Flow may be included in the N2 SM information and sent to the RAN node via N2 Session Request as depicted in step 3 in Figure 6.15.2.1-1. +- In step 6, when the steps in UE Triggered Service Request procedure in clause 4.2.3.2 in TS 23.502 [3] are invoked, the PSA-RAN PDB together with PDB for each QoS Flow may be included in the N2 SM information and provided to the RAN node as depicted in step 2a and step 3 in Figure 6.15.2.1-1. + +During UE requested PDU Session Establishment procedure, steps 1-20 from clause 4.3.2.2.1 in TS 23.502 [3] are performed with the following differences: + +- In steps 11-12, the PSA-RAN PSA-RAN PDB together with PDB for each QoS Flow may be included in the N2 SM information and provided to the RAN node as depicted in step 2b and step 3 in Figure 6.15.2.1-1. + +During UE or network requested PDU Session Modification procedure, steps 1-13 from clause 4.3.3.2 in TS 23.502 [3] are performed with the following differences: + +- In step 3a, 3b and step 4, the PSA-RAN PSA-RAN PDB together with PDB for each QoS Flow may be included in the N2 SM information and provided to the RAN node as depicted in step 2a, 2b and step 3 in Figure 6.15.2.1-1. + +After RAN receive PSA-RAN PSA-RAN PDB and PDB for the QoS Flow, RAN can derive PDB for RAN part of this QoS Flow accordingly. + +NOTE 1: If standardized 5QI is used for the QoS Flow, the PDB in the N2 information is omitted, but the PSA-RAN PDB may still be included. + +NOTE 2: The PSA-RAN PDB is only apply to QoS Flows of Delay Critical GBR resource type. + +### 6.15.3 Impacts on Existing Nodes and Functionality + +SMF: + +- The SMF provides PSA-RAN PDB for a QoS Flow to the NG-RAN node during PDU session establishment/modification or service request procedures. + +RAN: Derive the PDB of RAN part based on the received PDB and PSA-RAN PDB. + +### 6.15.4 Solution Evaluation + +With this solution, SMF needs to be configured with PSA-RAN PDB and RAN node can obtain PSA-RAN PDB for a specific QoS Flow via N2 information from SMF, so that RAN can derive PDB for RAN part by taking it into account. If PSA-RAN PDB is not used in N2 signalling the PSA-RAN PDB decided as in existing Rel-15 PDB mechanism. + +## 6.16 Solution #16 for Key Issue #7: Automatic GBR service recovery after handover + +### 6.16.1 Description + +During the Handover Preparation phase, an additional attribute "GBR required as soon as possible" is proposed to be sent by the Source RAN node to the Target RAN node in the Xn/N2 interface signalling when the existing "notification control" QoS attribute is sent. + +With this new QoS attribute, at handover, the Target RAN node will perform admission control for the GBR flow. If the GBR admission control fails, the Target RAN node performs admission control for that flow as a 'best effort' (e.g. QFI=8) flow. + +The signalling from the Target RAN to the Source RAN node is extended to indicate which GBR flows are able to be established with the correct target QoS, and which GBR flows are accepted with a best effort QoS. + +If the GBR flow(s) could not be admitted with the proper GBR QoS, the Source RAN node can consider whether other candidate Target RAN nodes are available. The Source RAN may then perform Handover Preparation with other candidate Target RAN nodes, and if successful, the Source RAN node cancels the earlier handover attempt. + +Upon handover completion in a congested RAN node the new RAN node notifies the CN that the GBR QoS cannot be met and sends another notification when the GBR QoS can again be guaranteed for that flow. + +In the handover instruction that the target RAN node prepares for the source RAN node to send to the UE, the target RAN node may map the GBR QFI (that is accepted with a best effort QoS) to a Logical Channel Identifier that is not shared with other flows, or, may make a different choice. After the UE accesses the target RAN Node: + +- in the latter case, an RRC Reconfiguration is likely to be needed when the GBR QoS is subsequently restored; +- in the former case the RAN node can choose whether or not to allocate any uplink resources; +- in both cases, the RAN can choose whether or not to allocate any downlink resources to that GBR QFI. If downlink resources are not going to be allocated, then, as an option, the SMF could be requested (via a notification command) to request the UPF to discard the downlink packets (and may record corresponding information on the CDR). + +The target RAN node to UE signalling may also carry an RRC indication that is to be passed to the UE's NAS layer to inform the UE's NAS that the GBR QoS will not be immediately available. After the handover, when the GBR QoS is able to be restored, the RAN node sends an indication of the restoration of QoS to the UE, e.g. using new Rel-16 RRC signalling. + +NOTE: The above new Rel-16 RAN signalling functionality that informs the UE's NAS layer about N2 interface GBR Notification signalling should be extended to also cover the non-handover 'Notification' situations that exist in Rel-15. + +### 6.16.2 Procedures + +These are readily derivable from the above description. + +### 6.16.3 Impacts on Existing Nodes and Functionality + +#### AMF: + +- no impact unless the "Notification of lack of GBR QoS" is piggy-backed on the Path Switch Request rather than being sent immediately afterwards. + +#### PCF: + +- no impact if this is developed as an extension of Rel-15 Notification Control. Impact expected if this is developed as an alternative to Rel-15 Notification Control. + +#### SMF + +- Impact expected if this is developed as an alternative to Rel-15 Notification Control. + +Impact also expected if RAN wants SMF to get UPF to discard downlink packets. + +#### UPF: + +- existing data forwarding functionality can probably be re-purposed if the RAN wishes to have the core network discard downlink packets. + +#### RAN: + +- a) the main "radio resource scheduler" functionality is common with Rel-15. +- b) NG-RAN implementation will be impacted (For example, updates to the "controller" of the admission control process are needed, e.g. to re-run the admission control process once every 500 ms for UE's with "notified" (suspended) GBR QoS Flows.) +- c) new RRC signalling to keep the UE's NAS aligned with the Notification status in the Core Network. +- d) additional parameter in Xn/N2 signalling to indicate to the source RAN node the new handling of this GFBR flow at the target RAN node. + +#### UE (that co-exists with Rel-15 Notifications sent for GBR flows) + +- a) new RRC signalling to keep the UE's NAS aligned with the Notification status in the Core Network. + +### 6.16.4 Solution Evaluation + +Editor's note: This clause provides an evaluation of this solution. + +## 6.17 Solution #17 for Key Issue #6: Configuration of CN PDB in NG-RAN + +### 6.17.1 Description + +This solution applies to key Issue #6. In the solution, the PLMN operator with OAM configure locally at the NG-RAN the packet delay budgets between a specific RAN node and PSA UPF for different 5QIs in RAN node. The configuration can be based on a variety of inputs: IP address of the N3 UPF, TEID range etc. There is no normative SA WG2 work for this option. + +### 6.17.2 Impacts on Existing Nodes and Functionality + +RAN: Configure the PDB between a specific RAN node and PSA UPF with O&M. The configuration can be based on a variety of inputs: IP address of the N3 UPF, TEID range etc + +### 6.17.3 Solution Evaluation + +If there is no direct connection between PSA UPF and N3 UPF and I-UPF is inserted for the PDU session, the RAN cannot be aware of the transient delays. In that case the SMF can select the specific I-UPF and the operator can also evaluate the PDB between the RAN node and PSA UPF with I-UPF and configure the value in the NG-RAN based on statistical analysis of the average I-UPF to PSA UPF delay. + +While this configuration, based solution is still not deterministic since the transport delays cannot be accurately predicted, the benefit of RAN configuration is that there is no impact to SMF and N2 signalling message, there is no normative work in SA WG2 since the configuration can be done locally in the RAN using O&M methods. The benefit of this solution compared to what is supported in Rel-15 (standardised CN PDB per 5QI) is that it allows somewhat more accurate prediction of the CN PDB between the specific NG-RAN node and specific PSA UPF. + +## 6.18 Solution #18 for Key Issue #6: Deterministic solution based accurate time stamping of packets in downlink + +### 6.18.1 Description + +This solution applies to Key Issue #6. + +In this solution, it is assumed that time synchronisation using TSN is applied between RAN and PSA UPF e.g. as defined in solutions 8 and 11 of TR 23.734 [14]. + +When the DL PDB monitoring is activated, the PSA that is time synchronised using TSN adds the accurate time stamping in GTP-U header for the DL packets. SMF activates the PDB monitoring in PSA according to the request from PCF or local policy configured in SMF. If the PDB monitoring is created by PCF, the PCF sends the PDB Monitoring policy via Session Management Policy Modification procedure to the SMF and instructs the SMF to initiate PDB monitoring for the QoS Flow. + +RAN node calculates the PDB between RAN and PSA UPF according to the received time stamping in GTP-U header and the current time that received the DL packet. + +In UL this solution requires some predetermined UL CN PDB either signalled from SMF or locally configured in NG-RAN as defined in other solutions for key issue #6. + +### 6.18.2 Procedures + +Editor's note: This clause describes services and related procedures for the solution. + +### 6.18.3 Impacts on Existing Nodes and Functionality + +SMF: + +- The SMF activates the PDB monitoring for a QoS Flow. + +UPF: + +- When the DL PDB monitoring is activated, UPF adds the accurate time stamping in GTP-U header of packets. +- Time synchronisation using TSN is applied between RAN and UPF. + +RAN: + +- Calculate the PDB between RAN and UPF according to the time stamping in GTP-U header of DL packets. +- Time synchronisation using TSN is applied in RAN and UPF. + +### 6.18.4 Solution Evaluation + +This solution provides deterministic calculation of the "remaining" PDB to RAN for DL packets since the incoming packets are time-stamped. It requires all UP CN nodes and transport to be time synchronised using the same TSN GM. + +The solution can use the same approach as other solutions for UL. + +## 6.19 Solution #19 for Key Issue #4: Using control plane procedure on Uu interface for QoS Monitoring + +### 6.19.1 Description + +The E2E QoS monitoring can be divided into packet delay on Uu interface and packet delay on N3/N9 interface. The UL/DL packet delay on Uu interface is in the scope of "RAN-centric Data Collection and Utilization for LTE and NR" SI. The same mechanism that defined by RAN can be reused to collect the packet delay on Uu interface. A user plane based solution is used to collect the packet delay on N3/N9 interface. + +#### 6.19.1.1 QoS Monitoring + +If the delay is requested to be measured, SMF activates the QoS Monitoring to UPF and RAN respectively. + +SMF indicates to the RAN to start QoS Monitoring via AMF in the Namf\_Communication\_N1N2 message transfer message. The SMF indicates to the RAN via AMF to report the DL and UL packet delay result of Uu interface. SMF may also indicates to the RAN to activate the N3 delay monitoring procedure. + +The SMF determines the QoS parameters and QoS Monitoring events which need to be monitored and reported by UPF, e.g. one-way/round trip packet delay, and optionally the corresponding threshold and/or reporting period, and sends them to UPF via N4 Session modification request. + +RAN initiates the measurement procedure of DL and UL packet delay on Uu interface. + +NOTE 5: How does the RAN initiates the DL and UL packet delay procedure depends on RAN decision. + +RAN reports the DL and UL packet delay results of Uu interface to the CN. + +**Option 1:** RAN reports the packet delay results of Uu interface to SMF + +For this option, RAN reports the DL and UL packet delay with the 5QI to SMF via N2 signalling. Which N2 signalling is used depends on RAN3's decision. + +**Option 2:** RAN reports the packet delay results of Uu interface to UPF + +For this option, RAN includes the DL/UL packet delay in the GTP-U header of the UL data packet as described in solution#8. + +UPF activates the QoS Monitoring by using newly defined packet as monitoring packets as option 1 in clause 6.8.1.2.1 or actual service packets as monitoring packets as option 2 in clause 6.8.1.2.2. + +According to description in option 1 and option 2, the round trip packet delay of N3 interface could be calculated by UPF as $TRTT-N3 = (T6-T1) - (T5-T2)$ . + +For option 1, UPF sends the TRTT-N3 to SMF with the 5QI. SMF calculates the One way delay and Round trip delay for the 5QI. + +For option 2, UPF receives both the packet delay on Uu interface and TRTT-N3. UPF calculates the One way delay and Round trip delay. + +The packet delays for the 5QI are calculated as below: + +- One way delay 1: DL between the RAN and UE: Calculated by RAN based on the packet delay mechanism of Uu interface. +- One way delay 2: UL between the RAN and UE: Calculated by RAN based on the packet delay mechanism of Uu interface. +- One way delay 3: DL or UL between the RAN and UPF: $[(T6-T1) - (T5-T2)]/2$ +- One way delay 4: DL or UL between the UE and UPF: One way delay 1+One way delay 3 or One way delay 2+One way delay 3. +- Round Trip Delay 1: Round trip latency between the UPF and UE: One way delay 1+One way delay 2+TRTT-N3. + +### 6.19.2 Procedures + +**Editor's note:** This clause describes services and related procedures for the solution. + +### 6.19.3 Impacts on Existing Nodes and Functionality + +SMF: + +- SMF triggers the QoS Monitoring in the UPF and RAN respectively: + - For option 1, SMF receives the DL and UL packet delay results of Uu interface with the 5QI from RAN. SMF receives the packet delay of N3 interface with 5QI from UPF. + - For option 1, SMF calculates the One way delay and Round trip delay for the 5QI. + +UPF: + +- Initiates QoS Monitoring for the QoS Flow based on the QoS Monitoring policy received via N4 message. When the QoS Monitoring events match the reporting condition, the UPF reports the QoS Monitoring events to the SMF. + +RAN: + +- When receiving the monitoring packet delay request, RAN initiates the DL and UL packet delay measurement for Uu interface: + - For option 1, RAN sends the DL and UL packet delay measurement result with 5QI to SMF. + - For option 2, RAN includes the DL and UL packet delay measurement report in the GTP-U header. + +UE: + +- The impacts to UE is depend on RAN's decision about DL and UL packet delay measurement of Uu interface. + +### 6.19.4 Solution Evaluation + +**Editor's note:** This clause provides an evaluation of this solution. + +## 6.20 Solution #20 for Key Issue #7: SMF starts the pending timer for the non-accepted GBR QoS flow + +### 6.20.1 Description + +During the Handover Preparation phase, Target RAN node performs admission control for the QoS flow. If the GBR QoS flow is not accepted by the admission control, Target RAN node rejects the GBR QoS flows. + +Target RAN node sends the non-accepted GBR QoS flow to SMF during handover procedure. For Xn based HO, the non-accepted GBR QoS flow is included in the Path Switch Request message. For N2 based HO, the non-accepted GBR QoS flow is included in the Handover Request ACK message. AMF forwards the information to the associated SMF. + +SMF activates a pending timer based on local configuration for the non-accepted GBR QoS flow. All new QoS establishment request for the non-accepted GBR QoS flow is rejected by the SMF when the pending timer is running. SMF can send the QoS re-establishment request for the non-accepted GBR QoS flow after the timer expiration. + +RAN stores the QoS profile for the non-accepted GBR QoS flow. If RAN recovers from congestion state, RAN informs the SMF(s) using QoS notification control message. If pending timer is running in SMF, SMF stops the pending timer and re-establishes the non-accepted GBR QoS flow for the data transmission by local policy or QoS rule received from PCF. + +### 6.20.2 Procedures + +**Editor's note:** This clause describes services and related procedures for the solution. + +### 6.20.3 Impacts on Existing Nodes and Functionality + +SMF: + +- SMF activates a pending timer for the non-accepted QoS flow based on local configuration. +- SMF maintains context for non-accepted QoS flow until the pending timer expires. +- SMF rejects the new QoS flow establishment when the pending timer is running. +- SMF establishes the QoS flow for the non-accepted QoS after the pending timer expiration or receiving the information that RAN is recovery. + +RAN: + +- RAN maintains the QoS profile for the non-accepted GBR QoS flow. + +## 6.21 Solution #21 for Key Issue #7: Extending notification control for QoS flow setup and handover + +### 6.21.1 Description + +The current notification control mechanism is used after the related QoS flow setting up successfully. Admission control function is performed during QoS flow setup or handover procedure without taking the notification control parameter into account. In this solution, we extend the notification control parameter to be used for the admission control function. + +After the interaction with PCF, SMF provides a QoS profile including notification control parameter to AN to setup a new QoS Flow. With the notification control parameter, AN performs admission control but will not reject the QoS Flow due to radio resource limitation. AN responds to SMF that the QoS Flow is setup successfully, and whether the GFBR can be guaranteed. If the GFBR can't be guaranteed, SMF may further modify or release the QoS Flow after the interaction with PCF. AN keeps trying to allocate radio resource for this QoS Flow, once the radio resource is efficient, AN indicates to SMF and the related service can be used immediately. + +During a handover, the notification control parameter is provided by the Source RAN to the Target RAN node in the QoS profile, the Target RAN node performs admission control but will not reject the QoS Flow due to radio resource limitation. The Target RAN indicates to the Source RAN and CN that the QoS Flow is setup successfully, and whether the GFBR can be guaranteed. If the GFBR can't be guaranteed, SMF may further modify or release the QoS Flow after the interaction with PCF. The Target RAN keeps trying to allocate radio resource for this QoS Flow, once the radio resource is efficient, The Target RAN indicates to SMF and the related service can be used immediately. + +### 6.21.2 Procedures + +The PDU session establishment procedure as described in TS 23.502 [3], clause 4.3.2.2 is reused with the difference that AN may indicate to SMF at step 14 and step15 that the QoS Flow is setup successfully but the GFBR can't be guaranteed. + +The PDU session modification procedure as described in TS 23.502 [3], clause 4.3.3.2 is reused with the difference that AN may indicate to SMF at step 6 and step7a that the QoS Flow is setup successfully but the GFBR can't be guaranteed. + +The Xn based inter NG-RAN handover procedure as described in TS 23.502 [3], clause 4.9.1.2 is reused with the difference that at handover preparation phase, the Target RAN may indicate to the Source RAN that the QoS Flow is setup successfully, but the GFBR can't be guaranteed. The Target RAN may indicate to SMF at step 1 and step2 that the QoS Flow is setup successfully but the GFBR can't be guaranteed. + +The inter NG-RAN node N2 based handover procedure as described in TS 23.502 [3], clause 4.9.1.3 is reused with the difference that the Target RAN may indicate to the Source RAN that the QoS Flow is setup successfully, but the GFBR can't be guaranteed. The Target RAN may indicate to SMF at step 10 and step11a, clause 4.9.1.3.2, that the QoS Flow is setup successfully but the GFBR can't be guaranteed. + +### 6.21.3 Impacts on Existing Nodes and Functionality + +The current notification control parameter is extended to be considered for admission control. + +NG-RAN: + +- Performs admission control with taking the notification control parameter into account. +- Indicates to the source RAN and SMF that QoS Flow is setup successfully, and whether the GFBR can be guaranteed. + +SMF: + +- Receiving the indication from NG-RAN that the QoS Flow is setup successfully, and whether the GFBR can be guaranteed. If the GFBR can't be guaranteed, SMF follows the current notification control mechanism. + +### 6.21.4 Solution Evaluation + +**Editor's note:** This clause provides an evaluation of this solution. + +## 6.22 Solution #22 for Key Issue #7: Automatic GBR service recovery after handover + +### 6.22.1 Description + +This solution applies to key Issue #7 "Automatic GBR service recovery after handover". + +At Xn or N2 handover, the target NG-RAN applies admission control and if it cannot support the required GBR QoS, the target NG-RAN does not establish that QoS Flow. The QoS Flow that was not accepted in the target NG-RAN, i.e. its establishment was failed, is informed to the SMF during the handover procedure. + +In this solution, for the non-accepted GBR QoS Flow(s), the SMF requests the target NG-RAN to enable QoS Notification Control (QNC) which is called "QNC for GBR Service Recovery". This request can be made during Xn or N2 handover procedure or PDU Session Modification procedure after the handover is complete. The SMF shall request this QNC when the QoS Notification Control parameter is set in the PCC rule (received from the PCF) that is bound to + +the non-accepted QoS Flow. During the Xn or N2 handover procedure, the target NG-RAN does not send a notification informing the SMF that the GFBR cannot be guaranteed for the non-accepted GBR QoS Flow(s). + +The proposed QNC is not for GBR QoS Flow successfully established but for non-accepted GBR QoS Flow and is to recover the non-accepted GBR QoS Flow fast and in a signal-efficient way when the target NG-RAN is considered to establish the QoS Flow, e.g. due to congestion resolved. + +When the target NG-RAN receives the request about QNC for GBR Service Recovery for any non-accepted QoS Flow from the SMF, the NG-RAN performs the following: + +- maintains QoS parameters related to the QoS Flow targeted for QNC for GBR Service Recovery only for QNC purpose (e.g. QoS Flow level QoS parameters); +- enables QNC for the QoS Flow; and +- sends a notification informing the SMF that the GFBR can be guaranteed for the QoS Flow when the NG-RAN determines that the GFBR can be guaranteed for the QoS Flow. + +When the SMF receives the notification from the NG-RAN, the SMF requests the NG-RAN to establish the QoS Flow, i.e. to add the QoS Flow to the PDU Session, by triggering a PDU Session Modification procedure. At this time, the SMF provides the UE with a PDU Session Modification Command to add the QoS Flow to the PDU Session. This SMF operation may be based on interaction with PCF. When the NG-RAN receives the QoS Flow establishment request from the SMF, the NG-RAN establishes the QoS Flow, i.e. associates the QoS Flow with a DRB of the PDU session. + +**Editor's note:** It is FFS whether and how the UE's NAS layer is informed that GBR radio resource has not been allocated for the GBR QoS Flow non-accepted in the target NG-RAN. + +### 6.22.2 Procedures + +#### 6.22.2.1 QNC request for GBR Service Recovery during handover + +Figure 6.22.2.1-1 shows that a request related to QNC for GBR Service Recovery is made by the SMF during handover. + +![Sequence diagram illustrating the QNC request for GBR Service Recovery during handover. The diagram shows interactions between UE, Source NG-RAN, Target NG-RAN, AMF, SMF, and UPF. The process involves handover steps, SMF context updates, and subsequent notification and modification procedures.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source NG-RAN + participant Target NG-RAN + participant AMF + participant SMF + participant UPF + + Note over UE, UPF: 1. Steps 1-5 of Xn based inter NG-RAN handover without UPF re-allocation in clause 4.9.1.2.2 of TS 23.502; +OR +Inter NG-RAN node N2 based handover, Preparation phase in clause 4.9.1.3.2 and +steps 1-10 of inter NG-RAN node N2 based handover, execution phase in clause 4.9.1.3.3 of TS 23.502 + SMF->>AMF: 2. Nsmf_PDUSession_UpdateSMContext Response (N2 SM info (QFI, QNC for GBR Service Recovery)) + AMF->>Target NG-RAN: 3. N2 Session Request (N2 SM info (QFI, QNC for GBR Service Recovery)) + Note over UE, UPF: 4. Steps 8-9 of Xn based inter NG-RAN handover without UPF re-allocation in clause 4.9.1.2.2 of TS 23.502; +OR +steps 12-15 of inter NG-RAN node N2 based handover, execution phase in clause 4.9.1.3.3 of TS 23.502 + Note over Target NG-RAN: 5. NG-RAN determines that the GFBR can be guaranteed for the QoS Flow + Target NG-RAN->>SMF: 6. Notification (QFI) + Note over UE, UPF: 7. Network requested PDU Session Modification procedure + +``` + +Sequence diagram illustrating the QNC request for GBR Service Recovery during handover. The diagram shows interactions between UE, Source NG-RAN, Target NG-RAN, AMF, SMF, and UPF. The process involves handover steps, SMF context updates, and subsequent notification and modification procedures. + +**Figure 6.22.2.1-1: QNC request for GBR Service Recovery during handover** + +1. During the Xn based inter NG-RAN handover without UPF re-allocation procedure, steps 1-5 from clause 4.9.1.2.2 in TS 23.502 [3] are performed. The figure only shows one of Xn based handover procedures and other Xn based handover procedures in TS 23.502 [3] apply. + +OR + +All steps of the Inter NG-RAN node N2 based handover, Preparation phase procedure defined in clause 4.9.1.3.2 of TS 23.502 [3] are performed and during the inter-NG-RAN node N2 based handover, execution phase procedure, steps 1-10 from clause 4.9.1.3.3 of TS 23.502 [3] are performed. + +2. When sending Nsmf\_PDUSession\_UpdateSMContext Response to the AMF, the SMF requests the target NG-RAN to enable QNC for GBR Service Recovery for the non-accepted GBR QoS Flow(s) as described in clause 6.22.1. The SMF maintains context for the QNC requested GBR QoS Flow(s) only for QNC purpose (e.g. QoS Flow level QoS parameters). + 3. The QNC request for GBR Service Recovery is transferred to the target NG-RAN. + 4. Steps 8-9 of Xn based inter NG-RAN handover without UPF re-allocation procedure defined in clause 4.9.1.2.2 of TS 23.502 [3] are performed. +- OR +- Steps 12-15 of inter NG-RAN node N2 based handover, execution phase procedure defined in clause 4.9.1.3.3 of TS 23.502 [3] are performed. +5. At some point after the handover, the NG-RAN determines that the GFBR can be guaranteed for the QoS Flow bounded to the QNC for GBR Service Recovery. + 6. The NG-RAN sends a notification informing the SMF that the GFBR can be guaranteed for the QoS Flow. + 7. The SMF triggers PDU Session Modification procedure to add the QoS Flow to the PDU Session. + +#### 6.22.2.2 QNC request for GBR Service Recovery after handover + +Figure 6.22.2.2-1 shows that a request related to QNC for GBR Service Recovery is made by the SMF after handover. + +![Sequence diagram illustrating the QNC request for GBR Service Recovery after handover. The diagram shows interactions between UE, Source NG-RAN, Target NG-RAN, AMF, SMF, and UPF. The sequence starts with an Xn or N2 handover procedure. The SMF then sends a Namf_Communication_N1N2MessageTransfer to the AMF with N2 SM info (QFI, QNC for GBR Service Recovery). The AMF sends an N2 Session Request to the Target NG-RAN. The rest of the PDU Session Modification procedure is performed. The Target NG-RAN determines that the GFBR can be guaranteed for the QoS Flow and sends a Notification (QFI) to the SMF. Finally, the SMF triggers the Network requested PDU Session Modification procedure.](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant Source NG-RAN + participant Target NG-RAN + participant AMF + participant SMF + participant UPF + + Note over UE, UPF: 1. Xn or N2 handover procedure + Note over UE, UPF: 2. Namf_Communication_N1N2MessageTransfer (N2 SM info (QFI, QNC for GBR Service Recovery)) + Note over UE, UPF: 3. N2 Session Request (N2 SM info (QFI, QNC for GBR Service Recovery)) + Note over UE, UPF: 4. The rest of the PDU Session Modification procedure + Note over UE, UPF: 5. NG-RAN determines that the GFBR can be guaranteed for the QoS Flow + Note over UE, UPF: 6. Notification (QFI) + Note over UE, UPF: 7. Network requested PDU Session Modification procedure + +``` + +Sequence diagram illustrating the QNC request for GBR Service Recovery after handover. The diagram shows interactions between UE, Source NG-RAN, Target NG-RAN, AMF, SMF, and UPF. The sequence starts with an Xn or N2 handover procedure. The SMF then sends a Namf\_Communication\_N1N2MessageTransfer to the AMF with N2 SM info (QFI, QNC for GBR Service Recovery). The AMF sends an N2 Session Request to the Target NG-RAN. The rest of the PDU Session Modification procedure is performed. The Target NG-RAN determines that the GFBR can be guaranteed for the QoS Flow and sends a Notification (QFI) to the SMF. Finally, the SMF triggers the Network requested PDU Session Modification procedure. + +**Figure 6.22.2.2-1: QNC request for GBR Service Recovery after handover** + +1. Xn or N2 handover procedure is performed. +2. For the non-accepted GBR QoS Flow(s) in the target NG-RAN as a result of handover, the SMF initiates PDU Session Modification procedure in order to request the NG-RAN to enable QNC for GBR Service Recovery for the non-accepted GBR QoS Flow(s) as described in clause 6.22.1. Therefore, the SMF includes the request in Namf\_Communication\_N1N2MessageTransfer. The SMF maintains context for the QNC requested GBR QoS Flow(s) only for QNC purpose (e.g. QoS Flow level QoS parameters). +3. The QNC request for GBR Service Recovery is transferred to the target NG-RAN. +4. The rest of the PDU Session Modification procedure is performed. +5. At some point, the NG-RAN determines that the GFBR can be guaranteed for the QoS Flow bounded to the QNC for GBR Service Recovery. +6. The NG-RAN sends a notification informing the SMF that the GFBR can be guaranteed for the QoS Flow. +7. The SMF triggers PDU Session Modification procedure to add the QoS Flow to the PDU Session. + +### 6.22.3 Impacts on Existing Nodes and Functionality + +SMF: + +- For the non-accepted GBR QoS Flow(s) in the target NG-RAN as a result of handover, the SMF requests the target NG-RAN to enable QNC for GBR Service Recovery and maintains context for the QNC requested GBR QoS Flow(s) only for QNC purpose (e.g. QoS Flow level QoS parameters). +- When the SMF receives the notification from the NG-RAN for the QoS Flow bounded to QNC for GBR Service Recovery, the SMF triggers PDU Session Modification procedure to add the QoS Flow to the PDU Session. + +NG-RAN: + +- For the non-accepted GBR QoS Flow(s) as a result of handover, the NG-RAN enables QNC for GBR Service Recovery per request from the SMF. For this, the NG-RAN maintains context for the QNC requested GBR QoS Flow(s) only for QNC purpose (e.g. QoS Flow level QoS parameters). +- When the NG-RAN determines that the GFBR can be guaranteed for the QoS Flow bounded to the QNC for GBR Service Recovery, the NG-RAN sends a notification informing the SMF about that. + +### 6.22.4 Solution Evaluation + +**Editor's note:** This clause will provide evaluation of different solutions. + +## 6.23 Solution #23 for Key Issue #7: Always On control for URLLC GBR QoS Flow + +### 6.23.1 Description + +The QoS Parameter Always On control indicates whether the NG-RAN keeps the QoS Flow when the GFBR can no longer (or can again) be guaranteed because of radio resource admission control (e.g. the ARP priority level of the QoS Flow is higher value than a MPS/Emergency Service QoS Flow or during the handover procedure) for a QoS Flow during the lifetime of the QoS Flow. Always On control may be used for a GBR QoS Flow if the application traffic is able to adapt to the change in the QoS (e.g. if the AF is capable to trigger rate adaptation or trigger application to change its behaviours). + +The SMF shall only enable Always On control when the QoS Always On Control parameter is set in the PCC rule (received from the PCF) that is bound to the QoS Flow. The Always On control parameter is signalled to the NG-RAN as part of the QoS profile and to the UE with the QoS rule. If, for a given GBR QoS Flow, Always On control is enabled and the NG-RAN determines that the GFBR can no longer be guaranteed because of radio resource admission control, then the NG-RAN may: + +- initiate a Xn/N2 handover to move the UE to a target NG-RAN in order to keep the QoS Flow in the target NG-RAN if the target NG-RAN can provide the required radio resource (the source NG-RAN can try different NG-RAN to handover). or +- send an Always On notification towards SMF, e.g. if handover to target NG-RAN is not possible (e.g. no suitable neighbour cell). After the SMF receives the Always On notification from the RAN, the SMF may: + - a) request to change the QoS Flow from (DC)GBR type to non-GBR type, the NG-RAN still try to guarantee the GFBR again before the QoS Flow changed to the non-GBR QoS Flow, or + - b) perform the selective DRB deactivation for the GBR QoS Flow and rejects any DL packet for this QoS Flow . After the selective DRB deactivation, the UE will reject any UL packet of the QoS Flow without DRB and does not initiate Service Request to activate the DRB for the QoS Flow with Always On Control. + +**NOTE:** The PCF will decide the QoS parameters (e.g. 5QI and ARP) for the target non-GBR QoS Flow. + +Upon receiving an Always On notification from the NG-RAN that the GFBR can no longer be guaranteed because of radio resource admission control, the SMF forwards the Always On notification to the PCF. 5GC may initiate N1 and N2 signalling to modify the QoS Flow into a non-GBR QoS Flow with a higher ARP priority level than the GBR QoS Flow or performs the selective DRB deactivation for the GBR QoS Flow. With changing to non-GBR QoS Flow, the SMF also indicates whether the NG-RAN and UE keeps the GBR QoS Flow QoS parameter and Always On control. If the GBR QoS Flow is DRB deactivated, the SMF will reject the UE initialled SM procedure and reject any DL packet for this QoS Flow. + +When the NG-RAN (this NG-RAN can be the Target NG-RAN after handover) determines that the GFBR can be guaranteed again for a QoS Flow with Always On control for which the GBR QoS Flow is DRB deactivated or has been changed to a non-GBR QoS Flow with Always On control), the NG-RAN sends an Always On notification with the stored previous GBR QoS parameters , informing the SMF that the GFBR can be guaranteed again and the SMF may forward the notification to the PCF. The SMF decides to activate the DRB if the DRB is deactivated or may decide to change the non-GBR QoS Flow with Always On control back into the GBR QoS Flow with the required GBR QoS and Always On control. + +During the handover procedure, the NG-RAN will transfer the QoS Profile of the QoS Flow with Always On control to the target NG-RAN with the original GBR QoS Flow QoS parameter (if available) and current QoS Flow QoS parameter and Always On control attribute. After handover, the target NG-RAN continues to try to guarantee radio resource and continues the Always On control for this QoS flow as described in this clause. + +### 6.23.2 Procedures + +**Editor's note:** This clause describes services and related procedures for the solution. + +### 6.23.3 Impacts on Existing Nodes and Functionality + +UE: + +- For the QoS Flow with Always On Control, the UE rejects any UL packet and does not initiate Service Request for the Always On Control QoS Flow with no DRB. +- The UE needs to support the selective DRB deactivation and activation. + +SMF: + +- During the QoS Flow with Always On Control establishment procedure, the SMF provides Always On control to the UE and NG-RAN. +- After the SMF receives the Always On notification from the RAN, the SMF may change the QoS Flow between (DC)GBR type and non-GBR type. +- After the SMF receives the Always On notification from the RAN, the SMF may perform the selective DRB deactivation/activation for the GBR QoS Flow and request the UPF to reject/forward any DL packet for this QoS Flow. +- The SMF needs to support the selective DRB deactivation and activation. + +NG-RAN: + +- The NG-RAN continues to guarantee the radio resource for the QoS Flow with Always On Control. +- When the GFBR of the QoS Flow with Always On Control can no longer be guaranteed, the NG-RAN may initiate a Xn/N2 handover to move the UE to a target NG-RAN in order to keep the QoS Flow in the target NG-RAN if the target NG-RAN can provide the required radio resource +- When the GFBR of the QoS Flow with Always On Control can be again (or no longer be) guaranteed, the NG-RAN may send an Always On notification towards SMF. +- The NG-RAN needs to support the selective DRB deactivation and activation. + +### 6.23.4 Solution Evaluation + +**Editor's note:** This clause provides an evaluation of this solution. + +## 6.24 Solution #24 for Key Issues #4 and #6: Accumulated packet delay estimation for QoS monitoring and division of PDB + +### 6.24.0 General + +This solution uses monitoring of packets on the GTP-U to determine the delay budget between gNB and UPF. + +#### Alternative 1: + +This alternative solution proposes enhancements GTP-U protocol and GTP-U end-points functionalities for the purposes of QoS monitoring and end-to-end packet delay budget division on user plane path in uplink and downlink. In this solution, a GTP-U sender performs an estimation of RTT to the next hop GTP-U receiver by sending Echo messages and measuring time that elapses between the transmission of Echo Request message and the reception of Echo Response message. A GTP-U sender is also expected to estimate its user plane processing time as a general value or a + +user plane processing time related to a particular QoS requirement of existing QoS flow. A GTP-U sender computes an estimated accumulated packet delay by adding RTT/2, the processing time and, if available, an estimated accumulated packet delay from an upstream GTP-U sender (i.e. an immediately preceding GTP-U sender in user plane path) thus the estimated accumulated delay represents an estimated elapsed time since a user plane packet entered 3GPP domain. More specifically, the first GTP-U sender in the uplink direction (i.e. gNB-DU or gNB) computes the estimated packet delay by adding RTT/2, its estimated processing time and estimated/measured Uu delay. In the downlink direction, the first GTP-U sender is PSA UPF for which the estimated packet delay is the sum of RTT/2 and its processing delay. + +It is expected that a GTP-U sender estimates RTT periodically in order to detect changes in transport delays. + +A GTP-U sender may send the estimated packet delay that it accumulated to the next hop GTP-U receiver + +- in every header of GTP-U PDU (e.g. G-PDU); +- in a header of one or more GTP-U PDUs (e.g. G-PDU) and a GTP-U receiver is assumed to store the received value; +- in a header of one or more GTP-U PDUs that are sent first to a GTP-U receiver within a given QoS flow; or +- in a GTP-U signalling message. + +QoS monitoring is performed by network nodes that receive and store QoS with a requested packet delay budget for QoS flow by comparing a received accumulated packet delay with a requested packet delay budget possibly also taking into the account the estimated/measured next hop transmission delay and node's processing time. If the node determines that the packet delay exceeds the requested packet delay budget then the node triggers QoS monitoring alert signalling to a control plane network function, e.g. SMF. + +Echo Request message and Echo Response message are sent outside GTP-U tunnels (the messages are using TEID set to 0). If underlaying transport is using QoS differentiation (e.g. IP DiffServ) then it is up to the implementation to ensure that the Echo messages are classified correctly and receive similar treatment by the underlaying transport as GTP-U G-PDUs carrying QoS flows (user data). + +#### Alternative 2: + +This alternative solution provides means for QoS monitoring for URLLC on the N3 interface between the UPF and NG-RAN as well as on the N9 interface between the UPF (PSA) and the I-UPF. The solution is based on the specification of the measurements specified for GTP based N3 interface in TS 28.552 [15]. + +NOTE: Measurements defined in TS 28.552 [15] includes estimated gNB internal delays which is provided to the OAM and as such is included to the measurement data. + +This measurement provides the average (arithmetic mean) GTP packet delay on the N3 and N9 interface. The measurement is optionally split into subcounters per QoS level (5QI). In the below sequence, when the measurement is to be obtained for the N9 interface, the gNB is replaced by I-UPF and the UPF is replaced by UPF (PSA). + +1. This measurement is obtained as: the time when receiving a GTP Echo Response message from the gNB at the egress GTP termination, minus time when sending the GTP Echo Request to gNB at the GTP ingress termination and divides it by two. OAM adjusts the N3 delay measurements by removal of the internal delay time in gNB as defined in TS 28.552 [15]. +2. Each measurement is an integer representing the mean delay in microseconds. The number of measurements is equal to one. If the optional QoS level measurement is performed, the number of measurements is equal to the number of QoS level parameters. +3. Measurement is taken at UPF. + +As in alternative 1, GTP Echo Request message and GTP Echo Response message are sent outside GTP-U tunnels (the messages are using TEID set to 0). If underlaying transport is using QoS differentiation (e.g. IP DiffServ) and the 5QIs associated with the relevant QoS Flows are provided to the UPF over N4 then it is up to the implementation in UPF to ensure that the Echo messages are classified correctly and receive similar treatment by the underlaying transport as GTP-U G-PDUs carrying QoS flows (user data). + +### 6.24.2 Procedures + +#### Alternative 1: + +![Sequence diagram illustrating the procedure for accumulated packet delay estimation for QoS monitoring and division of PDB in downlink. The diagram shows interactions between UE, NG-RAN, AMF, SMF, I-UPF, PSA UPF, and DN. The process involves RTT measurements and accumulated packet delay computations at the PSA UPF and I-UPF, leading to a QoS monitoring alert and the determination of available PDB at the NG-RAN.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant I-UPF + participant PSA UPF + participant DN + + Note right of PSA UPF: 1: RTT measurement + PSA UPF->>I-UPF: Echo Request + I-UPF-->>PSA UPF: Echo Response + PSA UPF->>I-UPF: Echo Request + I-UPF-->>PSA UPF: Echo Response + + Note right of PSA UPF: 2: Compute accumulated packet delay + PSA UPF->>I-UPF: 3: Accumulated packet delay + + Note right of I-UPF: 4: RTT measurement + I-UPF->>NG-RAN: Echo Request + NG-RAN-->>I-UPF: Echo Response + I-UPF->>NG-RAN: Echo Request + NG-RAN-->>I-UPF: Echo Response + + Note right of I-UPF: 5: Compute accumulated packet delay + I-UPF->>AMF: 6: QoS monitoring alert + AMF-->>NG-RAN: 7: Accumulated packet delay + + Note left of NG-RAN: 8: Determine available PDB + NG-RAN-->>SMF: 9: QoS monitoring alert + +``` + +Sequence diagram illustrating the procedure for accumulated packet delay estimation for QoS monitoring and division of PDB in downlink. The diagram shows interactions between UE, NG-RAN, AMF, SMF, I-UPF, PSA UPF, and DN. The process involves RTT measurements and accumulated packet delay computations at the PSA UPF and I-UPF, leading to a QoS monitoring alert and the determination of available PDB at the NG-RAN. + +**Figure 6.24.2.1: Accumulated packet delay estimation for QoS monitoring and division of PDB in downlink** + +NOTE: I-UPF is shown in the figure just to show irrespective of number of UPFs in the path, the same approach can be used however presence of I-UPF is not a pre-requisite for the packet delay estimation. + +The procedure of accumulated packet delay estimation for QoS monitoring and division of PDB in downlink is illustrated in Figure 6.24.2.1. + +1. PSA UPF sends one or more Echo Request messages to measure RTT to I-UPF. +2. PSA UPF computes an accumulated packet delay by adding the half of measured RTT and estimated user plane processing time at PSA UPF that may be QoS flow specific. +3. PSA UPF sends the accumulated packet delay to I-UPF in GTP-U PDU (e.g. G-PDU or a signalling message). +4. I-UPF measures RTT to NG-RAN by sending one or more Echo Request messages. +5. An accumulated packet delay at I-UPF is computed by adding the value of accumulated packet delay received from PSA UPF, the half of RTT between I-UPF and NG-RAN and estimated user plane processing time at I-UPF. +6. I-UPF sends the accumulated packet delay computed at I-UPF to NG-RAN. +7. As an option, NG-RAN can determine the remaining available PDB by subtracting the accumulated packet delay from the allowed PDB for the given 5QI. The available PDB defines the PDB split between RAN and 5GC. +8. NG-RAN can measure delay encountered in the air interface (Uu) based on "*RAN centric data collection and utilization for LTE and NR SI*" + +The above call flow is an illustration to perform QoS monitoring. This can also be performed in the Uplink direction with the RAN performing one-way delay estimation over Uu, then delay estimation over N3 and N9 can be performed + +by I-UPF/PSA UPF. In this case, the PSA UPF can perform total accumulated delay estimation (one-way delay of Uu, RTT for N3, N9 user plane path). + +#### Alternative 2: + +This measurement provides the average (arithmetic mean) GTP packet delay on the N3 and N9 interface. In the below sequence, when the measurement is to be obtained for the N9 interface, the gNB is replaced by I-UPF and the UPF is replaced by UPF (PSA). + +1. This measurement is obtained as: the time when receiving a GTP Echo Response message from the gNB at the egress GTP termination, minus time when sending the GTP Echo Request to gNB at the GTP ingress termination. +2. Each measurement is an integer representing the mean delay in microseconds. The number of measurements is equal to one. +3. Measurement is taken at UPF. +4. UPF provides the measurement results to OAM. OAM adjusts the N3 delay measurements by removal of the internal delay time in gNB as defined in TS 28.552 [15]. + +NOTE 1: Measurements defined in TS 28.552 [15] includes estimated gNB internal delays which is provided to the OAM and as such is included to the measurement data. + +NOTE 2: Providing Delay measurement from UPF to OAM requires SA5 involvement. + +NOTE 3: QoS monitoring within NG-RAN and between NG-RAN and UE (Uu) will be specified by RAN WGs. + +GTP Echo Request message and GTP Echo Response message are sent outside GTP-U tunnels (the messages are using TEID set to 0). If underlaying transport is using QoS differentiation (e.g. IP DiffServ) and the 5QIs associated with the relevant QoS Flows are provided to the UPF over N4, then it is up to the implementation to ensure that the Echo messages are classified correctly and receive similar treatment by the underlaying transport as GTP-U G-PDUs carrying QoS flows (user data). + +### 6.24.3 Impacts on Existing Nodes and Functionality + +#### Alternative 1: + +The transmission of Echo Request message is implementation specific. However, TS 29.281 [17] currently imposes a restriction on the frequency with which Echo Request messages may be sent. An Echo Request shall not be sent more often than every 60 seconds on each path. This doesn't prevent resending an Echo Request with the same sequence number according to the T3-RESPONSE timer. It should be noted that an Echo Request with the same sequence number should not be resended if an Echo Request is used to measure RTT. More frequent sending of Echo Request may be necessary with a possible exceptional treatment of T3-RESPONSE timer. + +This solution requires definition of either a new GTP-U extension header or a signalling message. + +#### Alternative 2: + +The gNB (I-UPF) provides GTP Echo Response to the UPF. The UPF calculates the GTP packet delay and makes it available to OAM. + +To provide 5QI level of measurement, the 5QIs associated with the relevant QoS Flows (QFIs) are provided over N4 to UPF at relevant procedures. + +### 6.24.4 Solution Evaluation + +#### Alternative 1: + +This solution provides a method that allows the system to determine PDB split dynamically and perform QoS monitoring with minimum changes to GTP-U protocol. Moreover, this solution does not require precise time synchronization amongst system entities. + +This solution performs packet delay estimation without considering 5QI for a given QoS flow rather it performs Echo Request / Echo Response in the corresponding user plane path outside GTP-U tunnels. + +As an implementation option, GTP-U receiver can also use this method to estimate packet delay and determine the remaining PDB available in user plane path (e.g. 5G-AN part of PDB). Remaining PDB is determined by subtracting the accumulated packet delay from the allowed PDB for the given 5QI that corresponds to the QoS flow. + +#### Alternative 2: + +This solution provides a method that allows the system to perform QoS monitoring for URLLC with minimum changes applying already specified measurements for GTP based N3 interface in TS 28.552 [15]. This solution does not require precise synchronization among system entities. This solution does not support standardized means of AF enabled dynamic QoS monitoring for URLLC. + +# --- 7 Overall Evaluation + +**Editor's note:** This clause will provide evaluation of different solutions. + +## 7.1 Evaluation for key issue 3 + +For QoS flows with low latency requirements: + +- 1) The server supporting the UE's applications needs to be kept geographically and topologically close to the UE, e.g. within a transmission latency of 0.1 ms to 1 ms from the radio base station site. + - 2) The low latency targets can be supported with triggering the anchor relocation after the mobility event to target NG-RAN node takes place. +- NOTE: This assumption means that transient delays can be afforded since the UE can be temporarily connected to a "suboptimal" UPF until the UPF is relocated. +- 3) The SMF that will trigger the anchor relocation, does not have to anticipate in advance the mobility event, before the actual mobility event occurs. + +Regarding how to enable runtime coordination between AF and 5GC and how to route traffic on N6 interface for case of PSA relocation, solution 6 and 13 touch the issues: + +- Solution 6 utilizes late notification to inform AF that DNAI is changed or PSA is changed after the PSA relocation is completed. If application relocation happens, the AF responds the notification with N6 traffic routing details, so that the SMF can configure the new PSA with received N6 traffic routing information. +- Solution 13 supports both early notification and late notification for SSC mode 3 PDU session, UL CL and Branch point cases. If early notification, the SMF sends the notification to the AF before establishing a new UP path towards new PSA, and waits for an acknowledgement from the AF before switching traffic to new UP path. If late notification, the SMF prepares the new UP path before sending the notification to the AF, the SMF also waits for the acknowledgement from the AF before switching traffic to new UP path. In case of application relocation, the acknowledgement from the AF may include N6 traffic routing information, so that the SMF can configure the new PSA to route the traffic on N6 interface correctly. + +For handling ULCL relocation: + +- 1) Forwarding tunnel needs to be established between source UL CL and target UL CL for routing leftover DL traffic from the source PSA to the UE. + +For handling PSA relocation and fulfilling traffic routing on N6 interface: + +- 1) The SMF can receive Ethernet context from source PSA and configures it into target PSA. +- 2) Target PSA can assist the DN in updating Ethernet forwarding configuration in the DN. +- 3) If the above two bullets apply, RAN needs to be configured not to expect End marker from source PSA. + +# --- 8 Conclusions + +## 8.1 Key Issue #1: Supporting high reliability by redundant transmission in user plane + +It is recommended that normative work proceed as follows: + +- Focusing on backhaul reliability improvements only i.e. without changes to the radio interface and associated protocols; and +- Requiring single UE only i.e. no UE redundancy shall be specified; and +- Introducing enablers in the network for: + - a) Redundancy of network nodes (UPF and gNB) and associated interface (N3), and concurrent PDU Sessions (see Solution #1); and + - b) GTP-U / TRANSPORT LAYER redundancy over N3 with single network nodes i.e. UPF and gNB (see Solutions #4, #7). No UE impact; + - c) Enablers to support appropriate gNB/UPF selection as applicable for a) and b). + +UE impact with a) shall be minimized. + +NOTE: An informative annex will be created during the normative work to document UE redundancy option with no 3GPP specification impact as enabled with Solution #2. + +## 8.2 Key Issue #3: Enhancement of Session Continuity during UE Mobility + +Agreement on Key Issue #3: Enhancement of Session Continuity during UE Mobility: + +- Solution 6 is selected as baseline for handling ULCL relocation in Rel-16 normative phase. +- Solution 11 is selected as baseline for handling PSA relocation for Ethernet PDU session type in Rel-16 normative phase. +- Solution 13 is selected as baseline for the runtime coordination between AF and 5GC in Rel-16 normative phase. + +## 8.3 Key Issue #5: Supporting low latency without requiring that the UE to always be in RRC\_Connected Mode + +For Key Issue #5, it is recommended to not continue with Solution #9: "Supporting low latency for initial data delivery without requiring that the UE to always be in RRC\_Connected State" for normative work in the Rel-16. + +## 8.4 Key Issue #6: Division of E2E PDB + +Agreements on Key Issue #6: + +- Solution #17 is selected as the solution for the PDU sessions that RAN directly connects to the PSA UPF, i.e. no I-UPF is used between. For this solution, there is no impact to 5GS NFs except for enhancements of RAN configuration. +- Solution #15 is selected as the solution for the PDU sessions that RAN directly connects to the PSA UPF, or I-UPF/ULCL is used. For the former case, the operator can decide whether to use solution A# or solution 15# based on operator policy. +- No normative work for Solution #18 in Rel-16. + +## 8.5 Key Issue #4: QoS Monitoring to Assist URLLC Service + +Agreements on Key Issue #4: + +NOTE 1: SA WG2 might revisit the following conclusions according to the outcome of RAN WG2/RAN WG3 study. SA2 will not proceed to normative work until receiving feedback from RAN WGs. + +The QoS Monitoring can be performed on different levels of granularities, i.e. per QoS Flow per UE level, or per node level, subject to the operators' configuration, and/or 3rd party application request, and/or PCF policy control for the URLLC services. Accordingly, two alternative solutions are concluded. + +**Method #1:** The following principles are concluded for normative work for the cases a real time QoS Monitoring and/or an update/refresh rate for QoS Monitoring within a specified time (e.g. at least 1 per second) per QoS Flow per UE level is requested, e.g. by 3rd party application, needs to be performed: + +- Using some of the actual service packets for QoS Monitoring between the PSA UPF and RAN node. +- The UL/DL packet delay between UE and PSA UPF for per UE per QoS Flow is a combination of the UL/DL packet delay between UE and RAN node, relying on RAN support, and the UL/DL packet delay between RAN node and PSA UPF. +- The SMF sends the QoS Monitoring policy for the QoS Flow to the PSA UPF and RAN via the PDU Session Establishment or Modification procedure. The PSA UPF initiates DL packet delay measurement between RAN node and PSA UPF for the QoS Flow and RAN node initiates the packet delay measurement of UL/DL packet delay on Uu interface, based on the QoS Monitoring policy received from the SMF. +- RAN node provides the UL/DL packet delay measurement result of Uu interface to the PSA UPF via the N3 interface. The RAN node may send a dummy UL packet as the monitoring response packet to the UPF in case there is no UL service packet. +- The PSA UPF calculates the UL/DL packet delay of N3 interface based on the time stamps provided by RAN node via N3 interface. If all user plane nodes of 5G system are time synchronized, the UL/DL packet delay of N3 interface could be calculated by PSA UPF and RAN respectively based on the received time stamp and the local time stamp when receiving the measurement packets. +- The PSA UPF calculates the UL/DL packet delay between UE and PSA UPF per QoS Flow based on the UL/DL packet delay result of Uu and N3 interface, and reports QoS Monitoring result to the SMF based on some specific conditions, e.g. when thresholds for reporting to SMF are reached. +- The PCC framework is used to activate or deactivate the QoS Monitoring for the QoS Flow when receiving the request from AF. RAN node could reject the QoS Monitoring for the QoS Flow based on the RAN's conditions (e.g. load situation). + +NOTE 2: The a) DL packet delay between UE and PSA UPF and b) the UL packet delay between UE and PSA UPF are calculated independently. + +NOTE 3: The QoS Monitoring requests RAN node to provide UL/DL packet delay of Uu interface between UE and RAN node. How to measure the UL/DL packet delay of Uu interface between UE and RAN node depends on RAN decision. The impact on RAN will be evaluated by RAN, and SA2 will consider the RAN feedback on the impact, if received. + +NOTE 4: Whether the above time synchronized based solution can be supported will rely on the final conclusion of Time Sync solution as part of FS\_Vertical\_LAN study. Furthermore, how to transport the time stamp might be reconsidered during the normative phase. + +**Method #2:** The following principles are concluded for normative work if per node level QoS Monitoring needs to be performed. + +- Packet delay estimation is performed by using GTP-U Echo Request/Response, as defined in the TS 28.552 [15], in the corresponding user plane transport path(s), independent of the corresponding PDU Session and the 5QI for a given QoS flow, for a specific URLLC service. + +**For Alternative 1, solution#24:** + +- RAN node provides the UL/DL packet delay measurement result of Uu interface to the PSA UPF via the N3 interface. +- The PSA UPF calculates the UL/DL packet delay of N3 interface based on the time stamps provided by RAN node via N3 interface. +- The PSA UPF calculates the UL/DL packet delay between UE and PSA UPF based on the UL/DL packet delay result of Uu and N3 interface, and reports QoS Monitoring result to the SMF based on some specific conditions, e.g. when thresholds for reporting to SMF are reached. +- The UPF performing the monitoring estimation can provide the corresponding {Network instance, DSCP} along with the estimated packet delay for the corresponding transport path. Based on this, SMF can determine QoS flow mapping to the appropriate {Network instance, DSCP} considering {5QI, QoS characteristics, ARP} for the given QoS flow. + +### **For Alternative 2, solution #24:** + +- RAN node provides the UL/DL packet delay measurement result of Uu interface to OAM directly. +- For 28.552 [15] based approach, UPF (or I-UPF) takes measurement on N3 (or N9) interface and provide the information to the OAM system. OAM has the rest of the measurements from NG-RAN (including delays between the UE and NG-RAN as well as NG-RAN internal delays) and can take appropriate actions to mitigate any unwanted situation. +- For GTP Echo/Response mechanism, the UPF performing the monitoring estimation can provide the corresponding {Network instance, DSCP} along with the estimated packet delay for the corresponding transport path. At PDU Session Establishment/Modification the SMF provides the 5QI associated with a given QFI to the UPF over N4. Based on this, UPF can determine QoS flow mapping to the appropriate {Network instance, DSCP} considering {5QI, QoS characteristics, ARP} for the given QoS flow and provide it to OAM. + +NOTE 5: Alternative 2 of method 2 does not provide means for measurements per AF request to dynamically trigger QoS monitoring. +Alternative 2 of method 2 reuses existing principles already available. + +NOTE 6: The system behaviour with the monitored information, will be worked out during normative phase. + +## 8.6 Key Issue #2: Supporting low latency and low jitter during handover procedure + +No normative work for the Key Issue#2 is needed in Rel-16 URLLC work item. + +# Annex A: Overview of IEEE TSN Frame Replication and Elimination for Reliability + +Following Annex describes IEEE TSN overview and possible applicability to 3GPP networks. + +IEEE 802.1 has been standardizing Time Sensitive Networking (TSN) to provide low and bounded end to end latency as well as high reliability. As part of this standards effort, the IEEE 802.1CB Frame Replication and Elimination for Reliability (FRER) [6] is the standard to provide high reliability, primarily for Ethernet networks. + +This standard provides identification and replication of frames for redundant transport over multiple paths. When received, the duplicate frames can be identified based on sequence numbering, and the duplicates are eliminated. + +The Figure below illustrates the FRER solution in an example. At switch N1, the frames are duplicated, and sequence numbers are added to the frame headers. The different copies of the frames are forwarded via disjoint paths in the network. At switch N2, the duplicates are identified based on the sequence numbers, and only one copy is forwarded, the redundant copies are eliminated. The ordering of the frames can also be maintained at N2 based on the sequence numbering. Generally speaking, FRER can be considered as a per frame level 1+n redundancy solution. + +![Diagram illustrating IEEE TSN Replication and Elimination function. A frame flow enters switch N1 (Replication), where it is duplicated onto two disjoint paths (green and red). Each path carries a frame with sequence numbers 16, 15, and 14. At switch N2 (Elimination), the frames are received, and only one copy is forwarded, eliminating the duplicates.](4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg) + +The diagram shows a network cloud containing two switches, N1 and N2. A 'frame flow' enters N1 from the left. At N1, the 'Replication' function duplicates the frame. Two 'disjoint paths' (one green, one red) lead to N2. Each path carries a frame with sequence numbers 16, 15, and 14. At N2, the 'Elimination' function receives both frames, identifies them as duplicates based on sequence numbers, and forwards only one copy to the right. The sequence numbers 16, 15, and 14 are shown in colored boxes (orange, blue, brown) above the frames on both paths. + +Diagram illustrating IEEE TSN Replication and Elimination function. A frame flow enters switch N1 (Replication), where it is duplicated onto two disjoint paths (green and red). Each path carries a frame with sequence numbers 16, 15, and 14. At switch N2 (Elimination), the frames are received, and only one copy is forwarded, eliminating the duplicates. + +**Figure A-1: Illustration of IEEE TSN Replication and Elimination function** + +The solution can be configured in a flexible way. It is possible to apply more than two paths for additional redundancy. A FRER entity can play the replication role and the elimination role at the same time for the two different directions. + +In typical deployments, the FRER functionality is set up using management protocols, and controlled by a centralized entity. Note that it is possible to set up FRER functionality both at intermediate switches, or at end hosts, even though the central controller and the management protocol may differ. There can be multiple replication and elimination points defined for a flow depending on the requirements and the network characteristics. The set up of the FRER functionality by means of a central controller is not part of the 802.1CB standard. IEEE P802.1Qcc specifies centralized TSN configuration both for bridges and end hosts, including FRER. + +The FRER, as defined by IEEE, adds 6 bytes to the Ethernet header, what is called Redundancy tag, or just "R-tag". The R-tag consists of 2 bytes for the EtherType which identifies the tag as an R-tag, 2 bytes for the actual sequence number, and 2 bytes reserved for future versions of the protocol. + +# --- Annex B:A summary of the IETF DetNet activity + +The IETF Deterministic Networking (DetNet) Working Group focuses on deterministic data paths that operate over Layer 2 bridged and Layer 3 routed segments, where such paths can provide bounds on latency, packet delay variation (jitter), and loss. The Working Group addresses Layer 3 aspects in support of applications requiring deterministic networking. The Working Group collaborates with the IEEE 802.1 Time Sensitive Networking (TSN) Task Group, which is responsible for Layer 2 operations, to define a common architecture for both Layer 2 and Layer 3. + +The Working Group initially focuses on solutions for networks that are under a single administrative control or within a closed group of administrative control; these include not only campus-wide networks but also can include private WANs. + +DetNet is concerned solely with worst-case values for the end-to-end latency. The DetNet Quality of Service can be expressed in terms of minimum and maximum end-to-end latency from source to destination, and probability of loss of a packet. Three techniques are used by DetNet to provide these qualities of service: + +- Congestion protection. Congestion protection greatly reduces, or even eliminates entirely, packet loss due to output packet congestion within the network. DetNet achieves congestion protection and bounded delivery latency by reserving bandwidth and buffer resources at every hop along the path of the DetNet flow. The actual queuing and shaping mechanisms are typically provided by the underlying subnet layers, e.g., MPLS or Ethernet bridging. For example, the IEEE 802.1 WG has specified (and is specifying) a set of queuing, shaping, and scheduling algorithms that enable each transit node (bridge or router). While these techniques are currently embedded in Ethernet and bridging standards, we can note that they are all, except perhaps for packet preemption, equally applicable to other media than Ethernet, and to routers as well as bridges. +- Explicit routes DetNet includes mechanisms to ensure that fixed paths are provided for DetNet flows. These explicit paths do not normally suffer temporary interruptions caused by the convergence of routing or bridging protocols. +- Service protection, as discussed below. + +After congestion, the most important contributions to packet loss are typically from random media errors and equipment failures. Service protection is the name for the mechanisms used by DetNet to address these losses. Both causes of packet loss can be greatly reduced by spreading the data in a packet over multiple transmissions. Packet replication and elimination is the most capable service protection mechanism for DetNet, and a major point of discussions during DetNet standardization work. It involves four capabilities: + +- Providing sequencing information, once, at or near the source, to the packets of a DetNet compound flow. This may be done by adding a sequence number as part of DetNet, or may be inherent in the packet, e.g. in a transport protocol, or associated to other physical properties such as the precise time (and radio channel) of reception of the packet. +- Replicating these packets into multiple DetNet member flows and, typically, sending them along at least two different paths to the destination(s). +- Eliminating duplicated packets. This may be done at any step along the path to save network resources further down, in particular when multiple Replication points exist. But the most common case is to perform this operation at the very edge of the DetNet network, preferably in or near the receiver. +- Re-ordering a DetNet flow's packets that are received out of order. + +In the simplest case, this amounts to replicating each packet in a source that has two interfaces, and conveying them through the network, along separate paths, to the similarly dual-homed destinations, that discard the extras. This ensures that one path (with zero congestion loss) remains, even if some intermediate node fails. The sequence numbers can also be used for loss detection and for re-ordering. + +More information on DetNet is available as defined in draft-ietf-detnet-architecture-06 [9]. + +# Annex C: Change history + +| Change history | | | | | | | | | +|----------------|---------|-----------|------|-----|-----|-----------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2018-09 | SP#81 | SP-180745 | - | - | - | MCC editorial update for presentation to TSG SA#81 for information | | 1.0.0 | +| 2018-12 | SP#82 | SP-81106 | - | - | - | MCC editorial update for presentation to TSG SA#82 for approval | | 2.0.0 | +| 2018-12 | SP#82 | - | - | - | - | MCC editorial update for publication after approval at TSG SA#82 (Release 16) | | 16.0.0 | +| 2019-03 | SP#83 | SP-190178 | 0001 | 1 | F | Evaluation of Solution#15 on PDB division | | 16.1.0 | +| 2019-03 | SP#83 | SP-190178 | 0004 | 1 | B | Solution 8 Updates for QoS monitoring solution based on time synchronization | | 16.1.0 | +| 2019-03 | SP#83 | SP-190178 | 0006 | 1 | B | Update solution #15 for Key issue 6 | | 16.1.0 | +| 2019-03 | SP#83 | SP-190178 | 0007 | 2 | B | Accurate time stamping based solution for Key issue #6 | | 16.1.0 | +| 2019-03 | SP#83 | SP-190178 | 0008 | 2 | F | Update solution#8 for Key Issue #4: QoS Monitoring | | 16.1.0 | +| 2019-03 | SP#83 | SP-190178 | 0010 | 2 | B | New Solution for Key Issue #7 | | 16.1.0 | +| 2019-03 | SP#83 | SP-190178 | 0011 | 2 | B | KI#7: Extending notification control for QoS flow setup and handover | | 16.1.0 | +| 2019-03 | SP#83 | SP-190178 | 0013 | 2 | B | New solution for KI#7 | | 16.1.0 | +| 2019-03 | SP#83 | SP-190178 | 0015 | 2 | B | New Solution for Key Issue #7-URLLC Always on Control for the GBR QoS Flow | | 16.1.0 | +| 2019-03 | SP#83 | SP-190178 | 0017 | 2 | F | Updates to Solution #16 for automated GBR service recovery after handover into congested cell | | 16.1.0 | +| 2019-03 | SP#83 | SP-190178 | 0023 | 1 | B | Conclusion proposal for Key Issue #6 | | 16.1.0 | +| 2019-03 | SP#83 | SP-190178 | 0028 | 2 | B | Accumulated packet delay estimation for QoS monitoring and division of PDB | | 16.1.0 | +| 2019-06 | SP#84 | SP-190432 | 0005 | 10 | B | Conclusion proposal for Key Issue #4 | | 16.2.0 | +| 2019-06 | SP#84 | SP-190432 | 0034 | 5 | C | Simplified version of solution #24 QoS monitoring for URLLC | | 16.2.0 | +| 2019-06 | SP#84 | SP-190432 | 0035 | 2 | F | Conclusion on KI#2 Supporting low latency and low jitter during handover procedure | | 16.2.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23740/0236eff05bcb8f3a343ea7933aaa306b_img.jpg b/marked/Rel-16/23_series/23740/0236eff05bcb8f3a343ea7933aaa306b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c1a715ab3affbb51d1260dcd42d635faf54a616 --- /dev/null +++ b/marked/Rel-16/23_series/23740/0236eff05bcb8f3a343ea7933aaa306b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1dc7dcdf158c84198f832783566fe7dc951b49ee0a0803c98438655dd163625a +size 55858 diff --git a/marked/Rel-16/23_series/23740/07b17a620c75522d53916a11e12d1bff_img.jpg b/marked/Rel-16/23_series/23740/07b17a620c75522d53916a11e12d1bff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a80353753e85d8529f5e68c1e20a67af84fe135 --- /dev/null +++ b/marked/Rel-16/23_series/23740/07b17a620c75522d53916a11e12d1bff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:970f19f9801bc05d5f9dfdecbea3066790d5fb1882e22b829e70b12240908d09 +size 31310 diff --git a/marked/Rel-16/23_series/23740/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/marked/Rel-16/23_series/23740/1439cb942d9e363bbb3161b5540dd8c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5411145f759cdc52277c4df79ba66045aadcaaa5 --- /dev/null +++ b/marked/Rel-16/23_series/23740/1439cb942d9e363bbb3161b5540dd8c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49588d87016356c270f9078762003bc174a2c095a65c3a5322cfe421bbd1ac13 +size 171732 diff --git a/marked/Rel-16/23_series/23740/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23740/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71cb95bb016b35e93aaaa047991c9860d5016049 --- /dev/null +++ b/marked/Rel-16/23_series/23740/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4ba4bb4fbf4a149bcd5c1748c32eddbe60ec3d7ead3e5536c0149742a824b73 +size 190771 diff --git a/marked/Rel-16/23_series/23740/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/Rel-16/23_series/23740/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e66420b7d639e1da48f29c791a136c3e71c6b16c --- /dev/null +++ b/marked/Rel-16/23_series/23740/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50e4acbcc9a3d8204a59e4cb2aa51f22693d5ddb6961e22dfd1fb2fa243c2dc9 +size 110650 diff --git a/marked/Rel-16/23_series/23740/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23740/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb85792253d1ccab1abfb77ba90fd76a154495e5 --- /dev/null +++ b/marked/Rel-16/23_series/23740/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f76bdab1d95a0f552bf67ffc226ee55150082f266075ec8198c1995611d62ae +size 196108 diff --git a/marked/Rel-16/23_series/23740/2df09d249c38abee55dbf0526dd6da0a_img.jpg b/marked/Rel-16/23_series/23740/2df09d249c38abee55dbf0526dd6da0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d907ffb2688461b6a1dce2d279a7eb9f030c81a --- /dev/null +++ b/marked/Rel-16/23_series/23740/2df09d249c38abee55dbf0526dd6da0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a428bbb3f20aac5a45a9e4d9112fc7aa13781e5ae2fd90377dc24020f611fb5 +size 187703 diff --git a/marked/Rel-16/23_series/23740/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/Rel-16/23_series/23740/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d13a32e6a1262e3647d95824b5b52d421fc6a1a --- /dev/null +++ b/marked/Rel-16/23_series/23740/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4c30dc6e6290ef253a018272cefe32575482c7ea46d59224d3e6ce5bddcc9a2 +size 168686 diff --git a/marked/Rel-16/23_series/23740/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/Rel-16/23_series/23740/3da1a07cb87051bf616c9876db958cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43258ebfae6d37ec0d3fa6de7f5f92f9e16d0641 --- /dev/null +++ b/marked/Rel-16/23_series/23740/3da1a07cb87051bf616c9876db958cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c1c37406d341372eb03dd201bc7ce3fd2241e64289c56a9830b7122facbc010 +size 25043 diff --git a/marked/Rel-16/23_series/23740/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23740/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24f0f78bcda4df5c59cbdb68b53cc4c79a452676 --- /dev/null +++ b/marked/Rel-16/23_series/23740/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a76d6c77515e4fe000b2658a3de156190fecdb047f1d0078f98a3a1d2892e67 +size 161169 diff --git a/marked/Rel-16/23_series/23740/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg b/marked/Rel-16/23_series/23740/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..185b04bcff27992f952a24c5ef7e6980fa578807 --- /dev/null +++ b/marked/Rel-16/23_series/23740/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0106ef4e2025c695599edb2f2d18f516d84599a2a086e05427d0fad576ea62c2 +size 29534 diff --git a/marked/Rel-16/23_series/23740/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-16/23_series/23740/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22869682186ac090d584ee8cd4f18207dfba6420 --- /dev/null +++ b/marked/Rel-16/23_series/23740/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce5c7dadcc8f5cf50b9dd340b81049652367808057a218784f7d101bc804e4f8 +size 82966 diff --git a/marked/Rel-16/23_series/23740/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg b/marked/Rel-16/23_series/23740/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..043ca9b0a99ba87069eca9429796d61e965d43dd --- /dev/null +++ b/marked/Rel-16/23_series/23740/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09e57b139fa0684d58f8d714d86dd4d146b0b96120cb79cb8144afb376fdfe32 +size 83057 diff --git a/marked/Rel-16/23_series/23740/55136bc716146672fc680fa05989f1d2_img.jpg b/marked/Rel-16/23_series/23740/55136bc716146672fc680fa05989f1d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fd2ab3121511a4606864805596e05b4ddbe7c3d --- /dev/null +++ b/marked/Rel-16/23_series/23740/55136bc716146672fc680fa05989f1d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b63649d1d505cc4bd6653d52cb2905af6a87807182ec2752717456383d61633 +size 33595 diff --git a/marked/Rel-16/23_series/23740/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23740/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9be0d8540f0e0232e319c420fe2b5c44a6c13e8f --- /dev/null +++ b/marked/Rel-16/23_series/23740/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e60351725de63c1948042574acf706f0463ca015787905346b50d07bb00fd450 +size 122062 diff --git a/marked/Rel-16/23_series/23740/90ddf538ef276510e2b631f7b96654e6_img.jpg b/marked/Rel-16/23_series/23740/90ddf538ef276510e2b631f7b96654e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d65691966de1c311c163d3c0015715f581e6847 --- /dev/null +++ b/marked/Rel-16/23_series/23740/90ddf538ef276510e2b631f7b96654e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:339769abc8c28e0e130cc70ff67f2ec948c181a876d3be6c8c69458e962d48f5 +size 130965 diff --git a/marked/Rel-16/23_series/23740/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23740/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8a30eaf54986a80b1e0344d751d61d836870a88 --- /dev/null +++ b/marked/Rel-16/23_series/23740/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5b07348ba1370e22306ee30ccf726b4f574071a3eb830cdc4057314f561ea5c +size 84469 diff --git a/marked/Rel-16/23_series/23740/d79d33da852cb7bca3e87b400a15c3e8_img.jpg b/marked/Rel-16/23_series/23740/d79d33da852cb7bca3e87b400a15c3e8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0700ba53b3cc6e9d4629f4cf40f740fa11755018 --- /dev/null +++ b/marked/Rel-16/23_series/23740/d79d33da852cb7bca3e87b400a15c3e8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:054ab3bc71ce36b2c70a9d735c1763b28fdb3ba0605fbb928b3374c79f5da4b2 +size 84704 diff --git a/marked/Rel-16/23_series/23740/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23740/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f159867fc9a8a6429d7d609d9612550e5a34844 --- /dev/null +++ b/marked/Rel-16/23_series/23740/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03152f1be43fe71565c1b6f08abb40b1f1568d137f86857dffacecb0ce92e743 +size 139749 diff --git a/marked/Rel-16/23_series/23740/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Rel-16/23_series/23740/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd6426c1422679e8bf331a3a8e4250a3314a1b00 --- /dev/null +++ b/marked/Rel-16/23_series/23740/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7dc6b8fb446d3fc8bf7d7f66caae64254c77413255b9dfe3f2c8f4b7db955a69 +size 123186 diff --git a/marked/Rel-16/23_series/23740/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/Rel-16/23_series/23740/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1de0d7b4fef0c7bc00c5fdada43e2cc0eecbd0d1 --- /dev/null +++ b/marked/Rel-16/23_series/23740/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c680167b9fdf76614297822871c1ebe0a8195441a55b7e70c8fe56aebe18f30 +size 57103 diff --git a/marked/Rel-16/23_series/23740/raw.md b/marked/Rel-16/23_series/23740/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..cfdd700019929461d52eb37d6918a7d503a9ca74 --- /dev/null +++ b/marked/Rel-16/23_series/23740/raw.md @@ -0,0 +1,2371 @@ +# Contents + +| | | +|---------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 Architectural Assumptions and Requirements..... | 8 | +| 5 Key Issues ..... | 8 | +| 5.1 Key Issue#1: Mutually exclusive access to Network Slices ..... | 8 | +| 5.1.1 Description ..... | 8 | +| 5.2 Key issue#2: Enabling interworking for slicing between EPC and 5GC..... | 9 | +| 5.2.1 Description ..... | 9 | +| 5.3 Key Issue#3: Access to specific Network Slices authorized and authenticated through additional User Identifiers ..... | 9 | +| 5.3.1 Description ..... | 9 | +| 6 Solutions..... | 10 | +| 6.1 Solutions for KI#1 ..... | 10 | +| 6.1.1 Solution #1.1: Mutually Exclusive Access to Network Slices via the use of URSP..... | 10 | +| 6.1.1.1 Introduction..... | 10 | +| 6.1.1.2 Functional description ..... | 10 | +| 6.1.1.3 Procedures ..... | 11 | +| 6.1.1.4 Impacts on existing entities and interfaces..... | 11 | +| 6.1.1.5 Evaluation..... | 11 | +| 6.1.2 Solution #1.2: Mutually Exclusive Access to Network Slices via UE configuration ..... | 11 | +| 6.1.2.1 Introduction..... | 11 | +| 6.1.2.2 Functional description..... | 12 | +| 6.1.2.3 Procedures..... | 12 | +| 6.1.2.4 Impacts on existing entities and interfaces ..... | 12 | +| 6.1.2.5 Evaluation ..... | 13 | +| 6.1.3 Solution #1.3: Solution to Key issue#1: Mutual exclusion awareness in UE. .... | 13 | +| 6.1.3.1 Introduction..... | 13 | +| 6.1.3.2 Functional description..... | 14 | +| 6.1.3.3 Procedures..... | 15 | +| 6.1.3.4 Impacts on existing entities and interfaces ..... | 18 | +| 6.1.3.5 Evaluation ..... | 18 | +| 6.1.4 Solution#1.4: Slicing Group Support for Mutually Exclusive Access to Network Slices ..... | 19 | +| 6.1.4.1 Introduction..... | 19 | +| 6.1.4.1.1 Design principles..... | 19 | +| 6.1.4.1.2 Working Assumptions and Concepts of Mutually Exclusive Access Slicing Group ..... | 19 | +| 6.1.4.2 Functional description..... | 20 | +| 6.1.4.2.1 Concepts of Mutually Exclusive Access Slicing Group ..... | 20 | +| 6.1.4.2.2 Identification of Mutually Exclusive Access Slicing Group..... | 21 | +| 6.1.4.2.3 UE Support for Mutually Exclusive Access Slicing Group..... | 22 | +| 6.1.4.2.4 Roaming Support for Mutually Exclusive Access Slicing Group..... | 22 | +| 6.1.4.2.5 URSP/NSSP Support for Mutually Exclusive Access Slicing Group..... | 23 | +| 6.1.2.4.6 AMF Support for Mutually Exclusive Access Slicing Group..... | 23 | +| 6.1.4.3 Procedures..... | 25 | +| 6.1.4.3.1 UE Registration with Mutually Exclusive Access Slicing Group..... | 25 | +| 6.1.4.4 Impacts on existing entities and interfaces ..... | 28 | +| 6.1.4.5 Evaluation ..... | 28 | +| 6.1.5 Solution #1.5: Mutually Exclusive Access to Network Slices using existing mechanisms..... | 28 | +| 6.1.5.1 Introduction..... | 28 | +| 6.1.5.2 Functional description..... | 28 | +| 6.1.5.2.1 General assumptions ..... | 28 | +| 6.1.5.2.2 Applying proposed logic to an example..... | 29 | + +| | | | +|---------------|----------------------------------------------------------------------------------------------------|----| +| 6.1.5.3 | Procedures..... | 31 | +| 6.1.5.3.1 | General ..... | 31 | +| 6.1.5.3.2 | Signalling within the network ..... | 31 | +| 6.1.5.3.3 | Interactions with Rel-15 usage of Allowed NSSAI ..... | 31 | +| 6.1.5.3.4 | Characteristics of the solution..... | 31 | +| 6.1.5.4 | Impacts on existing entities and interfaces ..... | 31 | +| 6.1.5.5 | Evaluation ..... | 32 | +| 6.1.6 | Solution #1.6: Enabling access control to network slices that cannot be access simultaneously..... | 32 | +| 6.1.6.1 | Introduction..... | 32 | +| 6.1.6.1.1 | Design Principles..... | 32 | +| 6.1.6.1.2 | Working Assumptions..... | 32 | +| 6.1.6.1.3 | Network Slice Access Exclusion Rules ..... | 33 | +| 6.1.6.2 | High-level Description..... | 35 | +| 6.1.6.2.1 | Services and Illustrated Procedures..... | 35 | +| 6.1.6.2.1.1 | Registration Procedure ..... | 35 | +| 6.1.6.2.1.2 | Enforcement of mutually exclusive rules ..... | 36 | +| 6.1.6.2.1.2.1 | PDU Establishment..... | 37 | +| 6.1.6.3 | Impacts on existing services and interfaces..... | 37 | +| 6.1.6.4 | Evaluation ..... | 38 | +| 6.1.7 | Solution #1.7: Solutions for MEANS via Slicing Group Indication ..... | 38 | +| 6.1.7.1 | Introduction..... | 38 | +| 6.1.7.2 | Functional description..... | 38 | +| 6.1.7.2.1 | UE configuration ..... | 38 | +| 6.1.7.2.2 | UE subscription..... | 38 | +| 6.1.7.2.3 | Operations ..... | 38 | +| 6.1.7.2.4 | Roaming support ..... | 39 | +| 6.1.7.3 | Procedures..... | 40 | +| 6.1.7.3.1 | RAN configuration..... | 40 | +| 6.1.7.3.2 | Registration procedure ..... | 40 | +| 6.1.7.4 | Impacts on existing entities and interfaces ..... | 41 | +| 6.1.7.5 | Evaluation ..... | 42 | +| 6.1.8 | Solution #1.8: Solution to Key issue#1: Access to new group of Network Slices..... | 42 | +| 6.1.8.1 | Introduction..... | 42 | +| 6.1.8.2 | Functional description..... | 42 | +| 6.1.8.3 | Procedures..... | 42 | +| 6.1.8.4 | Impacts on existing entities and interfaces ..... | 42 | +| 6.1.8.5 | Evaluation ..... | 43 | +| 6.2 | Solutions for KI#2 ..... | 43 | +| 6.2.1 | Solution#2.1: Network slice instance selection in initial AMF..... | 43 | +| 6.2.1.1 | Introduction..... | 43 | +| 6.2.1.2 | Functional description..... | 43 | +| 6.2.1.3 | EPS to 5GS handover Procedures..... | 44 | +| 6.2.1.4 | Impacts on existing entities and interfaces ..... | 45 | +| 6.2.1.5 | Evaluation ..... | 45 | +| 6.2.2 | Solution #2.2: Slice-aware mobility from EPC to 5GC ..... | 45 | +| 6.2.2.1 | Introduction..... | 45 | +| 6.2.2.2 | Functional description..... | 45 | +| 6.2.2.2.1 | Idle Mode Mobility from EPC to 5GC..... | 45 | +| 6.2.2.2.2 | Connected Mode Mobility from EPC to 5GC..... | 46 | +| 6.2.2.3 | Procedures..... | 47 | +| 6.2.2.4 | Impacts on existing entities and interfaces ..... | 47 | +| 6.2.2.5 | Evaluation ..... | 47 | +| 6.2.3 | Solution #2.3: Inter RAT mobility Slice support ..... | 47 | +| 6.2.3.1 | Introduction..... | 47 | +| 6.2.3.2 | Functional description..... | 47 | +| 6.2.3.3 | Procedures..... | 49 | +| 6.2.3.3.1 | Registration with AMF and V-SMF change during CONNECTED state mobility..... | 49 | +| 6.2.3.3.2 | Registration with AMF and V-SMF change during IDLE state mobility..... | 50 | +| 6.2.3.4 | Impacts on existing entities and interfaces ..... | 50 | +| 6.2.3.5 | Evaluation ..... | 51 | +| 6.2.4 | Solution #2.4: Connected mode mobility from EPC to 5GC ..... | 51 | +| 6.2.4.1 | Introduction..... | 51 | + +| | | | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------|----| +| 6.2.4.2 | Functional description..... | 51 | +| 6.2.4.3 | Procedures..... | 52 | +| 6.2.4.3.1 | Enhancement to PDN connection establishment ..... | 52 | +| 6.2.4.3.1 | Enhancement to handover preparation from EPC to 5GC ..... | 52 | +| 6.2.4.4 | Impacts on existing entities and interfaces ..... | 53 | +| 6.2.4.5 | Evaluation ..... | 53 | +| 6.2.5 | Solution#2.5: Using the NF discovery to find the S-NSSAI..... | 53 | +| 6.2.5.1 | Introduction..... | 53 | +| 6.2.5.2 | Functional description..... | 53 | +| 6.2.5.3 | Procedures..... | 54 | +| 6.2.5.3.1 | EPS to 5GS handover using N26 interface ..... | 54 | +| 6.2.5.4 | Impacts on existing entities and interfaces ..... | 55 | +| 6.2.5.5 | Evaluation ..... | 55 | +| 6.3 | Solutions for KI#3 ..... | 55 | +| 6.3.1 | Solution #3.1: Slice Specific Authentication and Authorization using non 3GPP credentials based on secondary authentication ..... | 55 | +| 6.3.1.1 | Introduction..... | 55 | +| 6.3.1.2 | Functional description..... | 56 | +| 6.3.1.3 | Procedures..... | 57 | +| 6.3.1.3.1 | Slice authentication at first PDU session establishment for the S-NSSAI..... | 57 | +| 6.3.1.4 | Impacts on existing entities and interfaces ..... | 58 | +| 6.3.1.5 | Evaluation ..... | 58 | +| 6.3.2 | Solution #3.2: Solution to KI#3 on Slice Specific Authentication and Authorization using non 3GPP credentials..... | 58 | +| 6.3.2.1 | Introduction..... | 58 | +| 6.3.2.2 | Functional description..... | 59 | +| 6.3.2.3 | Procedures..... | 60 | +| 6.3.2.3.1 | Secondary Authentication and Authorization During Registration ..... | 60 | +| 6.3.2.3.2 | Secondary Re-Authentication and Re-Authorization after Registration..... | 63 | +| 6.3.2.4 | Impacts on existing entities and interfaces ..... | 63 | +| 6.3.2.5 | Evaluation ..... | 63 | +| 6.3.3 | Solution #3.3: Solution for configuration of network slice authentication ..... | 64 | +| 6.3.3.1 | Introduction..... | 64 | +| 6.3.3.2 | Functional description..... | 64 | +| 6.3.3.3 | Procedures..... | 64 | +| 6.3.3.4 | Impacts on existing entities and interfaces ..... | 64 | +| 6.3.3.5 | Evaluation ..... | 64 | +| 7 | Evaluation ..... | 64 | +| 7.1 | Evaluations Criteria for KI#1: Mutually Exclusive Access to Network Slices ..... | 64 | +| 7.2 | Evaluations for KI#2: Enabling interworking for slicing between EPC and 5GC..... | 66 | +| 8 | Conclusions..... | 67 | +| 8.1 | Conclusions for key issue #1 - Mutually exclusive access to Network Slices..... | 67 | +| 8.1.1 | Enhancements for change of a set of Network Slices ..... | 68 | +| 8.2 | Conclusions for key issue #2 - Enabling interworking for slicing between EPC and 5GC..... | 69 | +| 8.3 | Conclusions for key issue #3 - Access to specific Network Slices authorized and authenticated through additional User Identifiers..... | 69 | +| Annex A: | Change history..... | 70 | + +# --- Foreword + +This Technical Report has been produced by the 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. + +# --- 1 Scope + +The scope of this Technical Report is: + +- Identify, prioritize and study the practical non-roaming and roaming deployment scenarios and system impacts when the 5GS is not able to support all possible combination of S-NSSAIs for the UE, and the aspects of mutually exclusive access to Network Slices. +- Study the possible enhancement for the Network Slicing interworking with EPC for Connected and Idle modes. +- Study how to provide Network Slice Access authentication and authorization specific for the Network Slice Access authorization that uses User Identities and Credentials different from the 3GPP SUPI and that takes place after the primary authentication which is still required between the UE and the 5GS for PLMN access authorization and authentication. + +# --- 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". +- [3] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [4] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2". +- [5] 3GPP TS 38.300: "NR and NG-RAN Overall Description; Stage 2". +- [6] 3GPP TS 33.501: "Security architecture and procedures for 5G system". +- [7] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Mutually Exclusive Access to Network Slices:** The access to Network Slices is considered to be mutually exclusive for a UE when their respective S-NSSAIs are both present in the UE's subscription and the UE is prevented from accessing both S-NSSAIs simultaneously. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] apply. + +# --- 4 Architectural Assumptions and Requirements + +For Mutually Exclusive Access to Network Slices the following assumptions apply: + +- It is assumed that the support of mutually exclusive access to network slices uses Rel-15 network slicing feature as the baseline. +- Support of the Mutually Exclusive Access to Network Slices in a PLMN shall not impact Rel-15 5G UEs' behaviour. +- The network operator shall be able to ensure that the UE is prevented to access Network Slices which are mutually exclusive for that UE. +- It is assumed that a UE supporting mutually exclusive access to network slices shall be able to operate in a Rel-15 5GS. +- Rel-16 5G UE and core may support Mutually Exclusive Access to Network Slices. + +For interworking for slicing between EPC and 5GC the following assumptions apply: + +- It is assumed that the interworking for slicing between EPC and 5GC uses Rel-15 solution as the basis. +- The interworking for slicing between EPC and 5GC shall not impact Rel-15 5G UEs behaviour. +- The system shall support slicing interworking between EPC and 5GC for roaming case when the PGW-C+SMF is Rel-15. + +# --- 5 Key Issues + +## 5.1 Key Issue#1: Mutually exclusive access to Network Slices + +### 5.1.1 Description + +Several scenarios addressing access control to mutually exclusive Network Slices have been identified, i.e. due to deployment, regulation or per SLA, some UEs may be restricted from using two services (S-NSSAIs) simultaneously. + +Such scenarios can include (but not limited to): + +- by internal regulation (of the subscriber, of the employer, of the operator, etc): for example, it might be forbidden for a UE to access "regular" services and "specific" services, e.g. a UE used by a government officer might be restricted to be either in "off-duty" (regular) or "on-duty" (specific) mode. It is forbidden by regulation for the UE to access simultaneously the off-duty services and the on-duty services. +- by network capability: for example, a factory device may have two modes of operations: "maintenance mode" (used to perform updates, e.g. blueprints upload, check the status of the devices, monitoring and maintenance, etc) and a "ultra-low latency factory mode", where the device receives URLLC commands to perform its duty. In that case, the AMF instance used for the URLLC factory slice may be tailored specifically to that duty, and not be able to support other services such as file database access, etc. In that case, the device may have to select either mode and not connect to both simultaneously. + +To address the above mentioned scenarios this key issue will: + +- 1) Identify whether existing Release 15 System procedures are able to allow access control to mutually exclusive Network Slices. +- 2) Identify whether improvements to existing Release 15 System procedures are needed when controlling the access to mutually exclusive Network Slices, including aspects of both UE and network. + +To achieve those results this key issue will answer (not limited to) the following questions: + +- Which information is used to support mutually exclusive access to Network Slices in the UE and/or in the network? +- How to support the UE to select the particular network slice(s) that can serve the UE simultaneously? +- How the above information is used to support mutually exclusive access to Network Slices both in the non-roaming and in the roaming case? +- In roaming cases, how the solutions would work when the Serving PLMN supports mutually exclusive Network Slices, whereas the HPLMN does not (and vice versa)? +- Which network functions are involved in determining/providing the above information, and how? +- Should the above information be pre-configured in the UE or dynamically handled by the network for the UE? +- How can mutually exclusive access to Network Slices be enforced by the network? +- What are the System impacts, if any, to existing Release 15 procedures to enable the network to control simultaneous access from a UE to different Network Slices? +- How to ensure that introduction of support for mutually exclusive Network Slices does not disrupt the normal operation of Release 15 UEs? + +## 5.2 Key issue#2: Enabling interworking for slicing between EPC and 5GC + +### 5.2.1 Description + +In Rel-15, when the UE has a set of PDN connections active in the EPC (for which the UE has been given a corresponding S-NSSAI by the CN), when the UE moves to the 5GC the serving AMF is not selected considering the slices associated to the active PDN connections. This may lead to scenarios where the AMF may not be able to serve all the PDU sessions that the UE intends to move to the 5GC. It is desirable for Rel-16 to study whether solutions are possible and worthwhile to minimize the impact of mobility procedures from EPC to 5GC on the slices corresponding to the PDN connections active in the EPC. + +The key issue aims at addressing at least the following open aspects when the UE moves between EPC and 5GC, or vice versa: + +- Selecting an AMF based on the slices associated to the active PDN connections the UE has in the EPC. +- Selecting an appropriate V-SMF based on the slices associated to the active PDN connections the UE has in the EPC. +- Transferring (in both idle and connected modes) multiple simultaneous PDU Sessions to the same DNN that are associated to different slices and served by different (H-)SMFs. + +## 5.3 Key Issue#3: Access to specific Network Slices authorized and authenticated through additional User Identifiers + +### 5.3.1 Description + +This key issue will study how to provide Network Slice Access authentication and authorization specific for the Network Slice Access authorization that uses User Identities and Credentials different from the 3GPP SUPI and that takes place after the primary authentication which is still required between the UE and the 5GS for PLMN access authorization and authentication. + +In particular, the KI will address: Access control to Network Slices that require additional authorization and authentication: + +- How do the UE and the Network know that additional authorization and authentication is required for a Network Slice? + +- How is the additional authorization and authentication triggered and performed? E.g. which procedures are used and when. + +# --- 6 Solutions + +## 6.1 Solutions for KI#1 + +### 6.1.1 Solution #1.1: Mutually Exclusive Access to Network Slices via the use of URSP + +#### 6.1.1.1 Introduction + +This is a solution to Key Issue #1, "Mutually Exclusive Access to Network Slices" (MEANS). This solution assumes the following: + +- It is assumed that the network deployments in the home and the visited networks are designed according to the requirements for MEANS, and that the "mutually exclusive" network slices are not sharing resources (including no common AMF Set). This ensures that the NSSF will never grant access to both network slices simultaneously even if a UE requests it (e.g. due to SIM swap). As in Rel-15, NSSF internal policies dictate which network slice would be selected in this case. +- It is assumed that the "mutual exclusivity" of network slices is per network deployment, and is common to all UEs subscribed to both network slices. +- It is assumed that the UE has internal logic (e.g. MMI, or software support) to understand which applications are needed at a given time (e.g. "on duty" vs "off duty", "maintenance" vs "factory", etc), which is beyond the scope of this solution to address. If a SIM swap happens to a UE not understanding the purpose of the applications, it is expected that the UE would not use these applications anyway. +- This solution assumes that the supporting UE would parse the URSP to determine the S-NSSAIs to include in the Requested NSSAI. This behaviour is not required in Rel-15. +- It is assumed that PLMN are going to deploy their network slices in their networks so that all the services available to the users can be used simultaneously (i.e. there will be at least a set of network slice instances in the home network that can offer all the services (S-NSSAIs) that the UE can request simultaneously in its home network), except for network slices that are intended to be under mutually exclusive access by UEs. +- It is assumed that PLMNs are going to organise their SLAs so that network slices in the roaming partners' networks are going to offer all services available to the users simultaneously (i.e. there will be at least a set of network slice instances in the roaming partner network that can offer all the services (S-NSSAIs) that the UE can request simultaneously in that network), except for network slices that are intended to be under mutually exclusive access by UEs. +- This means that the enforcement of the MEANS in roaming scenarios is enforced via SLA (the roaming partner would not allow a UE to access MEANS slices simultaneously, e.g. via sharing the same AMF), and that when UEs needing MEANS in roaming partners' networks not supporting such SLA requirements would not receive the Subscribed S-NSSAIs of the UE that could result in such violation of the MEANS. + +#### 6.1.1.2 Functional description + +This solution proposes to introduce a new (optional, to be ignored if not understood) sub-field, the S-NSSAI Group, in the URSP, as part of the Network Slice Selection field of the Route Selection component, with the following use: + +- If an S-NSSAI value in the URSP is associated with an S-NSSAI Group, all instances of this S-NSSAI in the URSP shall be associated with the same S-NSSAI Group value. +- If the UE includes in the Requested NSSAI (or its associated mapping) an S-NSSAI value in the URSP is associated with an S-NSSAI Group, the UE shall not include in the Requested NSSAI another S-NSSAI value associated with a different S-NSSAI Group. + +NOTE: This solution does not propose a specific encoding or limitation to the S-NSSAI Group, however, it is expected that very few groups will be needed, therefore an encoding allowing up to 2 ~ 8 group values is expected to be sufficient. + +#### 6.1.1.3 Procedures + +No new procedures are required with this solution. + +#### 6.1.1.4 Impacts on existing entities and interfaces + +UE impact: + +- This solution only impacts UE supporting the feature. UEs not supporting the feature should not receive such URSP information (by design: since they do not need the "exclusion service", they do not need to receive configuration for such "exclusion"), and should ignore it if received nonetheless. The supporting UE would need to parse the URSP in order to fill the Requested NSSAI. + +Network impact (serving and home): + +- This solution does **not** impact the roaming 5GC networks, and can work in Rel-15 5GC networks. It is expected that supporting roaming partners will properly configure their networks to fulfil their SLAs. Enforcement of MEANS in the network is using the Rel-15 NSSF/AMF functionality for determining an appropriate set of S-NSSAI for the Allowed NSSAI. +- This solution does **not** impact the home 5GC network beyond the ability to send to the relevant UEs the URSP with the added field (i.e. it impacts the PCF and the UDR). It is expected that the home network operator will configure its network to fulfil the subscription requirements. Enforcement of MEANS in the network is using the Rel-15 NSSF/AMF functionality for determining an appropriate set of S-NSSAI for the Allowed NSSAI. + +In this solution, Mutually Exclusive Access to Network Slices in the network is already supported in Rel-15 and does not require any further changes. Actual isolation of resources between network slices is supported by the underlying virtualisation environment and OAM (see SA5 specifications). + +#### 6.1.1.5 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +### 6.1.2 Solution #1.2: Mutually Exclusive Access to Network Slices via UE configuration + +#### 6.1.2.1 Introduction + +This is a solution to Key Issue #1, "Mutually Exclusive Access to Network Slices" (MEANS). + +This solution incorporates parts of solution #5, in clause 6.1.5. + +This solution assumes the following: + +- It is assumed that the network deployments in the home and the visited networks are designed according to the requirements for MEANS, and that the "mutually exclusive" network slices are not sharing resources (including no common AMF Set). This ensures that the NSSF will never grant access to both network slices simultaneously even if a UE requests it (e.g. due to SIM swap). As in Rel-15, NSSF internal policies dictate which network slice would be selected in this case. +- It is assumed that the "mutual exclusivity" of network slices is per network deployment, and is common to all UEs subscribed to both network slices. +- It is assumed that the UE used for mutually exclusive network slices: + - either has internal logic (e.g. MMI, or software support) to understand which applications are needed at a given time (e.g. "on duty" vs "off duty", "maintenance" vs "factory", etc), which is beyond the scope of this solution to address. If a SIM swap happens to a UE not understanding the purpose of the applications, it is + +expected that the UE would not use these applications anyway. As this is UE local configuration, the network can update the information by existing means for UE local configuration, or can rely on application logic to update and perform the choice between two sets of network slices. + +- or has internal logic (e.g. software support) to sort the S-NSSAIs to put in the Requested NSSAI in priority order. +- A UE not supporting the feature (e.g. with no application/MMI to perform the selection between several sets of slices or no internal logic to sort S-NSSAIs in priority order), but nonetheless subscribed to network slices that are mutually exclusive with each other will rely on the Rel-15 slice rejection mechanism.- It is assumed that PLMN are going to deploy their network slices in their networks so that all the services available to the users can be used simultaneously (i.e. there will be at least a set of network slice instances in the home network that can offer all the services (S-NSSAIs) that the UE can request simultaneously in its home network), except for network slices that are intended to be under mutually exclusive access by UEs. +- It is assumed that the PLMN's internal logic for NSSF/AMF network slice selection can include a mechanism to take in account the S-NSSAIs from the Requested NSSAI in priority order during the network slice selection. +- It is assumed that PLMNs are going to organise their SLAs so that network slices in the roaming partners' networks are going to offer all services available to the users simultaneously (i.e. there will be at least a set of network slice instances in the roaming partner network that can offer all the services (S-NSSAIs) that the UE can request simultaneously in that network), except for network slices that are intended to be under mutually exclusive access by UEs. +- This means that the enforcement of the MEANS in roaming scenarios is enforced via SLA (the roaming partner would not allow a UE to access MEANS slices simultaneously, e.g. via sharing the same AMF), and that when UEs needing MEANS in roaming partners' networks not supporting such SLA requirements would not receive the Subscribed S-NSSAIs of the UE that could result in such violation of the MEANS. + +#### 6.1.2.2 Functional description + +This solution proposes that the UE expected to be able to select between network slices is configured (by mechanisms not to be defined in the specification, e.g. part of application configuration) in such a way that the UE knows whether two given S-NSSAIs can be requested simultaneously in the Requested NSSAI, or how to sort the S-NSSAIs in the Requested NSSAI in priority order (see solution #5, in clause 6.1.5, for more details).. + +The solution proposes that the (not specified) internal logic of the AMF/NSSF regarding network slice selection can decide to consider the S-NSSAIs in the Requested NSSAI in priority order. + +#### 6.1.2.3 Procedures + +No new procedures are required with this solution. + +#### 6.1.2.4 Impacts on existing entities and interfaces + +Impacts compared to Rel-15: + +- This solution has no normative specification impacts. It is already supported by Rel-15 specifications. Only a few informative statements are expected (e.g. a few notes) to clarify the expected behaviour of the UE and the network.. + +UE impact: + +- This solution only impacts UE supporting the feature as part of the overall UE design and application configuration (i.e. no specification impact). UEs not supporting the feature would not need to be configured in such a way. The UE would need to understand its own configuration. + +Network impact (serving and home): + +- This solution does **not** impact the roaming 5GC networks, and can work in Rel-15 5GC networks. It is expected that supporting roaming partners will properly configure their networks to fulfil their SLAs. Enforcement of MEANS in the network is using the Rel-15 NSSF/AMF functionality for determining an appropriate set of S-NSSAI for the Allowed NSSAI. + +- This solution does **not** impact the home 5GC network, and can work in home Rel-15 5GC network. It is expected that the home network operator will configure its network to fulfil the subscription requirements. Enforcement of MEANS in the network is using the Rel-15 NSSF/AMF functionality for determining an appropriate set of S-NSSAI for the Allowed NSSAI. + +In this solution, Mutually Exclusive Access to Network Slices in the network is already supported in Rel-15 and does not require any further changes. Actual isolation of resources between network slices is supported by the underlying virtualisation environment and OAM (see SA5 specifications). + +The impact to the specification work is expected to be as follows: + +- An explanation that, the UE can optionally be locally (pre-)configured with information (by mechanisms not specified in 3GPP specifications) regarding the S-NSSAIs that can (or cannot) be requested simultaneously by the UE; +- An explanation that, the UE can optionally be locally configured (by mechanisms not specified in 3GPP specifications) to sort S-NSSAIs in the Requested NSSAI in a priority order; +- An explanation that the AMF/NSSF, when receiving a Requested NSSAI with S-NSSAIs that cannot be allowed simultaneously, can decide to consider the S-NSSAIs in the Requested NSSAI in priority order; and +- Possibly, an explanation how these mechanisms can allow an operator to fulfil the KI#1 scenarios. + +It is expected that this work can be completed via a single CR to TS 23.501 [2]. + +#### 6.1.2.5 Evaluation + +### 6.1.3 Solution #1.3: Solution to Key issue#1: Mutual exclusion awareness in UE. + +#### 6.1.3.1 Introduction + +As per definition of Mutually exclusive Network Slices: + +*The access to Network Slices is considered to be mutually exclusive for a UE when their respective S-NSSAIs are both present in the UE's subscription and the UE is prevented from accessing both S-NSSAIs simultaneously.* + +The case exists a UE may attempt to request in a Registration Request e.g. two S-NSSAIs in the Requested NSSAI are not compatible. It is assumed the network then detects this is an incorrect NSSAI, accepts the Registration request, places the UE in default slices as subscribed by the UE (possibly this causes a AMF change, and as a reminder the default NSSAIs must be mutually compatible), and indicates to the UE that there were incompatible S-NSSAIs. The automatic UE configuration procedures ought to also get triggered as per the existing TS 23.501 [2]. + +It is clear however that if the UE is not provided by the network with the exact S-NSSAIs that were incompatible and assuming the UE may subsequently request a number of S-NSSAIs >2, before the UE can eventually form a mutually compatible set of S-NSSAIs in a Requested NSSAIs, including one of the S-NSSAIs that were detected as incompatible, it may take a number of trials and errors. This would be the result of allowing a current Rel-15 UE to be provisioned with some S-NSSAIs that are mutually incompatible. + +Hence, unless Rel-15 is updated e.g. in the late drop, in Rel-15 a UE cannot be provisioned with mutually incompatible S-NSSAIs unless the operator is ready to accept that a suboptimal behaviour and a number of trial and errors may be involved in using certain slices. However, these trials and errors may be unacceptable for the correct operation of a mutually exclusive slice (e.g. a public safety slice may not welcome a trial and error phase before some mission critical data or media can be exchanged over the public safety slice, but this slice may have to coexist with e.g. a V2X slice on a police car). + +For this reason we need to specify some means by which: + +- 1) A properly configured UE never requests mutually exclusive slices in a requested NSSAI. +- 2) Error cases can be handled in a way that the network can provide the UE with the rules that avoid future repetition of the error, for UEs that are compliant to the solution proposed. + +- 3) There are no trial end errors once 1 and 2 are implemented in the system. + +Whether a late Rel-15 change needs to be considered (aligned with the late Rel-15 drop) will be part of the conclusions of the study. + +**Editor's note:** Compatibility with Rel-15 UEs and network needs to be assessed. + +#### 6.1.3.2 Functional description + +It is proposed that for each S-NSSAI in the UE subscription, Configured NSSAI and Default Configured NSSAI, a Mutual Exclusion Class Information is associated. This information identifies whether a certain S-NSSAI can be used with other S-NSSAIs and rules to define such coexistence. + +It is proposed that in Rel-16 these classes of mutual exclusion are identified by means of Mutual Exclusion Class Information, which identifies classes of slices that can be used simultaneously: + +**Table 6.1.3.2-1: Mutual Exclusion Class Information** + +| S-NSSAI
Mutual exclusion
class | Rule | +|--------------------------------------|-------------------------------------------------------------------------| +| 0 | No constraint defined for the S-NSSAI | +| 1 | S-NSSAI can be used alongside S-NSSAIs with same SST field value | +| 2 | S-NSSAI can be used alongside S-NSSAIs with same SD field value | +| 3 | S-NSSAI cannot be used alongside any other S-NSSAI | +| 4 | S-NSSAI can be used only alongside class 4 S-NSSAIs (Operator defined) | +| 5 | S-NSSAI can be used only alongside class 5 S-NSSAIs (Operator defined) | +| 6 | S-NSSAI can be used only alongside class 6 S-NSSAIs (Operator defined) | +| 7 | S-NSSAI can be used only alongside class 7 S-NSSAIs (Operator defined) | +| 8 | S-NSSAI can be used only alongside class 8 S-NSSAIs (Operator defined) | +| 9 | S-NSSAI can be used only alongside class 9 S-NSSAIs (Operator defined) | +| 10 | S-NSSAI can be used only alongside class 10 S-NSSAIs (Operator defined) | +| 11 | S-NSSAI can be used only alongside class 11 S-NSSAIs (Operator defined) | +| 12 | S-NSSAI can be used only alongside class 12 S-NSSAIs (Operator defined) | +| 13 | S-NSSAI can be used only alongside class 13 S-NSSAIs (Operator defined) | +| 14 | S-NSSAI can be used only alongside class 14 S-NSSAIs (Operator defined) | +| 15 | S-NSSAI can be used only alongside class 15 S-NSSAIs (Operator defined) | + +Classes 0-3 are standardised, and offer global interoperability. They identify the obvious classes of slices that are compatible with any other slice, those that are isolated (so not compatible with any other slice) and: + +- Those slices that can be used simultaneously with any other slice of the same type in the UE and share same dedicated AMFs for the SST in the CN. +- Those slices that can be used simultaneously with any other slice of the same SD field (e.g. all slices from same tenant, e.g. from same vertical customer) by the UE and e.g. can share same AMF dedicated for the SD in the CN. + +Classes 4-15 are operator specific. They define coexistence classes valid across a PLMN. + +An S-NSSAI cannot be used simultaneously with S-NSSAIs that do not belong to the same Mutual Exclusion Class or do not meet the related standardised Mutual Exclusion Class definition if applicable. + +Based on the above proposal, it follows that there can be 12 operator specific coexistence classes and 4 standardised ones. If more (or fewer) classes were deemed needed can be discussed and so the total number can be decided in normative phase. + +A VPLMN can decide, for inbound roamers, that some of the HPLMN coexistence classes are modified to other operator-specific values in VPLMN, and this information can be sent together with the configured NSSAI or Allowed NSSAI for the VPLMN, as long as this is consistent with the intended behaviour by the HPLMN (i.e. Network Slices that are incompatible in HPLMN, remain so in the VPLMN). + +If the mutual exclusion rules specified in the S-NSSAI Mutual Exclusion Class Information, which the serving PLMN receives from the UDM as part of the UE subscription data, are not met by a Requested NSSAI in a Registration + +Request message, the Requested NSSAI is considered as not valid and the AMF shall return in the Registration accept to the UE (which includes only default S-NSSAIs in Allowed NSSAI, alongside their coexistence class information which is the same as all the Default S-NSSAIs shall be enabled to be used at the same time) a cause code indicating that the UE has provided an invalid Requested NSSAI due to Mutual Exclusion reasons, but the S-NSSAIs in the Requested NSSAI shall not be stored as Rejected S-NSSAIs unless the AMF detected some of them were not supported in the TA or in the PLMN for the UE, in which case these S-NSSAIs are indicated by the AMF as rejected S-NSSAIs. + +Then, this triggers the UE configuration to be updated, e.g. the registration accept may also provide a Configured NSSAI including the UE the Mutual Exclusion class Information. + +If a HPLMN requires the Mutual Exclusion to be supported while the UE is roaming, in a Rel-15 network, this can be supported by provisioning in the UE a Configured NSSAI for the HPLMN with the Mutual Exclusion Class Information for each S-NSSAI. and the UE shall respect these rules when using the S-NSSAIs in the Rel-15 network, with the standing assumption Rel-15 network can always support any set of S-NSSAIs. However the HPLMN cannot rely on the VPLMN to enforce the Mutual exclusion rules, or expect that the VPLMN is respecting the Mutual Exclusion by allocating dedicated functions (e.g. AMF) that are e.g. handling only S-NSSAIs belonging to the same Mutual exclusion class. + +The Rel-15 VPLMN is also not able to use the Mutual exclusion information in the UE subscription. + +#### 6.1.3.3 Procedures + +This solution impacts existing procedures end to end by inclusion of the Mutual Exclusion Class Information in association of every S-NSSAI in the configured NSSAI when this is provided to the UE by the AMF in Registration Accept or in the UE Configuration Update. The Default Configured NSSAI S-NSSAIs, shall also be associated to Mutual Exclusion Class Information. The Association can be done e.g. with a separate new information element providing the mapping of each S-NSSAI in the (Default)Configured NSSAI to a Mutual Exclusion Class. Other than this, there is no impact except behavioural (as described in clause 6.2.3) in the nodes which have to evaluate this information: e.g. the Mutual Exclusion Class information to e.g. generate the Allowed NSSAI from the Requested and subscribed NSSAI in the network, of the UE that needs to evaluate this information in the Configured NSSAI or Default Configured NSSAI to form a Requested NSSAI with compatible slices only. + +If the UE does not indicate any NSSAI in registration request, the Default S-NSSAIs received in the Allowed NSSAI has no Mutual exclusion class information. The S-NSSAIs in the allowed NSSAI are by definition compatible with one another. + +Mutual Exclusion Class Information is also provided alongside subscriber information in the interaction between UDM and AMF, and between AMF and NSSF, for the determination of suitable allowed NSSAI which complies to Mutual exclusion constraints that are part of Subscriber data. + +If a roaming partner network is known to not support rel-16, the HPLMN shall only provide subscription information to those PLMNs with S-NSSAIs that are mutually compatible. + +A Rel-15 UE cannot use the Mutual Exclusion Class Information. If a subscription including this information is used for a Rel-15 UE, then the mutual exclusion of slice is not respected by this UE. It is therefore expected that a baseline subscription of compatible slices that can be used in a Rel-15 UE or a Rel-15 network or UE is defined for the event a rel-15 UE is used or a rel-15 network is used by a roaming partner. It is expected an explicit Indication of support of this feature is required by all UEs in rel-16 in the registration procedure. + +The following procedures impacts are further clarified: + +![Sequence diagram for Registration with AMF re-allocation procedure. Lifelines: UE, (R)AN, New AMF, Old AMF, PCF, SMF, AUSF, UDM. The diagram shows the interaction between these entities during a registration process involving AMF re-allocation.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant NewAMF as New AMF + participant OldAMF as Old AMF + participant PCF + participant SMF + participant AUSF + participant UDM + + Note right of RAN: 2. AMF selection + Note right of NewAMF: 8. AUSF selection + Note right of OldAMF: EIR + Note right of NewAMF: 13. UDM selection + Note right of NewAMF: 15. PCF selection + Note right of SMF: N3IWF + + UE->>RAN: 1. Registration Request + RAN->>NewAMF: 3. Registration Request + NewAMF->>OldAMF: 4 Namf_Communication_UEContextTransfer + OldAMF-->>NewAMF: 5 Namf_Communication_UEContextTransfer response + NewAMF-->>UE: 6. Identity Request + UE-->>NewAMF: 7. Identity Response + Note left of NewAMF: 9. Authentication/Security + Note right of OldAMF: EIR + Note right of NewAMF: 10. Namf_Communication_RegistrationCompleteNotify + OldAMF-->>NewAMF: 10. Namf_Communication_RegistrationCompleteNotify + NewAMF-->>UE: 11. Identity Request/Response + NewAMF->>OldAMF: 12. N5g-eir_EquipmentIdentityCheck_Get + OldAMF-->>NewAMF: 12. N5g-eir_EquipmentIdentityCheck_Get + Note right of NewAMF: 13. UDM selection + NewAMF->>UDM: 14a. Nudm_UECM_Registration + NewAMF->>UDM: 14b. Nudm_SDM_Get + NewAMF->>UDM: 14c. Nudm_SDM_Subscribe + OldAMF-->>UDM: 14d. Nudm_UCM_DeregistrationNotify + Note right of NewAMF: 15. PCF selection + OldAMF-->>PCF: 14e. Nudm_SDM_Unsubscribe + PCF-->>UDM: 14e. Nudm_SDM_Unsubscribe + NewAMF->>PCF: 16.AM Policy Association Establishment during Registration + PCF-->>NewAMF: 16.AM Policy Association Establishment during Registration + NewAMF->>SMF: 17. Nsmf_PDUSession_UpdateSMContext / Nsmf_PDUSession_ReleaseSMContext + SMF-->>NewAMF: 17. Nsmf_PDUSession_UpdateSMContext / Nsmf_PDUSession_ReleaseSMContext + Note right of SMF: N3IWF + NewAMF->>OldAMF: 18. N2 AMF Mobility Request + OldAMF-->>NewAMF: 19. N2 AMF MobilityResponse + NewAMF->>UE: 21. Registration Accept + UE-->>NewAMF: 22. Registration Complete + OldAMF-->>PCF: 20. AMF-Initiated AM Policy Association Termination + PCF-->>OldAMF: 20. AMF-Initiated AM Policy Association Termination + NewAMF-->>UDM: 23. Nudm_SDM_Info + +``` + +Sequence diagram for Registration with AMF re-allocation procedure. Lifelines: UE, (R)AN, New AMF, Old AMF, PCF, SMF, AUSF, UDM. The diagram shows the interaction between these entities during a registration process involving AMF re-allocation. + +**Figure 6.1.3.3-1: Registration with AMF re-allocation procedure** + +Step 1: the UE includes indication of support of the Mutual exclusivity feature and forms the Requested NSSAI based also on the Mutual Exclusion Class Information if available for the S-NSSAIs in the Configured NSSAI or Default Configured NSSAI. + +Step 14: the UE subscription data includes the Mutual Exclusion Class Information. + +Step 21: The Registration Accept message may include a Configured NSSAI with the Mutual Exclusion Class Information if the UE has sent a requested NSSAI with incompatible S-NSSAIs. + +![Sequence diagram for Registration with AMF re-allocation procedure. Lifelines: (R)AN, Initial AMF, Target AMF, NSSF, NRF, UDM, Old AMF. The diagram shows the flow of messages between these entities, including initial UE messages, slice selection data requests, and N2/NAS message exchanges.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +``` + +sequenceDiagram + participant (R)AN + participant Initial AMF + participant Target AMF + participant NSSF + participant NRF + participant UDM + participant Old AMF + + (R)AN->>Initial AMF: 1. Initial UE message + rect rgb(255, 255, 255) + Note over (R)AN, Target AMF: 2. Optionally steps 4-9a of figure 4.2.2.2.2-1. + end + Initial AMF->>UDM: 3a. Nudm_SDM_Get(Slice Selection Subscription data) + UDM-->>Initial AMF: 3b. Nudm_SDM_Get response + Initial AMF->>NSSF: 4a. Nnssf_NSSelection_Get + NSSF-->>Initial AMF: 4b. Nnssf_NSSelection_Get response + Initial AMF->>Old AMF: 5 Namf_Communication_RegistrationCompleteNotify + Initial AMF->>NRF: 6a. Nnrf_NFDiscovery_Request + NRF-->>Initial AMF: 6b. Nnrf_NFDiscovery_Request Response + Initial AMF->>Target AMF: 7a. Namf_Communication_N1MessageNotify + + Note over (R)AN, Target AMF: (A) + Target AMF->>(R)AN: 7b. N2 message + (R)AN->>Target AMF: 7c. N2 message + + Note over (R)AN, Target AMF: (B) + Target AMF->>(R)AN: 7a. Reroute NAS message + (R)AN->>Target AMF: 7b. Initial UE message + + rect rgb(255, 255, 255) + Note over (R)AN, Target AMF: 8. Steps 4-22 of figure 4.2.2.2.2-1 or +Steps 8-22 of figure 4.2.2.2.2-1 + end + +``` + +Sequence diagram for Registration with AMF re-allocation procedure. Lifelines: (R)AN, Initial AMF, Target AMF, NSSF, NRF, UDM, Old AMF. The diagram shows the flow of messages between these entities, including initial UE messages, slice selection data requests, and N2/NAS message exchanges. + +**Figure 6.1.3.3-2: Registration with AMF re-allocation procedure** + +Step 4a: the AMF provides the NSSF with the Mutual Exclusion Class information to aid the NSSF to determine the Allowed NSSAI, in a network that supports Mutual Exclusion feature, if the UE supports the Mutual exclusion feature. If the UE does not support the Mutual exclusion feature, then the AMF only provides to the NSSF the Slices that are part of the basic set of compatible S-NSSAIs part of the UE subscription. If the network is rel-15, the HPLMN has passed to it no Mutual Exclusion Class Information and only the basic set of compatible S-NSSAIs part of the UE subscription, So, there is no particular action taken in a rel-15 network. + +![Sequence diagram of UE Configuration Update procedure for access and mobility management related parameters. Lifelines: UE, NG-RAN, AMF, SMF, UDM. The diagram shows steps 0 through 4, with steps 3a, 3b, 3c, 3d, and 4 being optional or conditional.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant UE + participant NG-RAN + participant AMF + participant SMF + participant UDM + + Note over all: 0. AMF decides update of UE configuration or need for re-registration + AMF->>UE: 1. UE Configuration Update Command + UE-->>AMF: 2. UE Configuration Update Complete + + Note right of UE: 3a. UE initiates Registration procedure in CM-CONNECTED state as described in clause 4.2.2.2. +Steps 3b, 3c, 3d and 4 are skipped + Note right of AMF: 3b. AMF does not trigger AN Release procedure as described in clause 4.2.6 in 23.502. Steps 3c and 3d are skipped + Note right of AMF: 3c. AMF triggers AN Release procedure unless there are PDU Session(s) associated with emergency services. Step 3d is skipped + Note right of AMF: 3d. AMF triggers AN Release procedure unless there are PDU Session(s) associated with emergency services. + + Note right of UE: 4. UE initiates Registration procedure after UE enters CM-IDLE state + +``` + +Sequence diagram of UE Configuration Update procedure for access and mobility management related parameters. Lifelines: UE, NG-RAN, AMF, SMF, UDM. The diagram shows steps 0 through 4, with steps 3a, 3b, 3c, 3d, and 4 being optional or conditional. + +**Figure 6.1.3.3-3: Refer to TS 23.502 [3], Figure 4.2.4.2-1: UE Configuration Update procedure for access and mobility management related parameters** + +Step 1: The Configured NSSAI may be provided alongside a Mutual Exclusion Class information if applicable. If the UE is not indicating support of the Mutual exclusion feature, the configured NSSAI only includes the S-NSSAIs corresponding to the basic set of compatible S-NSSAIs. + +#### 6.1.3.4 Impacts on existing entities and interfaces + +- UE: support of Mutual Exclusion Class Information and procedures that include it for its configuration in the UE from the network. +- AMF: enforcement of the Mutual Exclusion Class Information received from UDM and/or inclusion in NSSF queries as part of sending the Subscribed S-NSSAIs. +- NSSF: enforcement of the Mutual Exclusion Class Information. +- UDM: Handling of the Mutual Exclusion Class Information. + +#### 6.1.3.5 Evaluation + +### 6.1.4 Solution#1.4: Slicing Group Support for Mutually Exclusive Access to Network Slices + +The intent of this solution is to support mutually exclusive access of network slices in 5GS as shown in Figure-6.4.2.1-1 below. Within a group of network slices, each network slice can serve the UE simultaneously with other network + +slice(s) within the 5GS. However, network slices that are not in the same group cannot serve the UE simultaneously within the 5GS. + +#### 6.1.4.1 Introduction + +##### 6.1.4.1.1 Design principles + +The design principles of the proposed solution to support Mutually Exclusive Access of network slices are as follows: + +- Minimum impact to the existing Rel-15 network slicing signalling procedures between the UE and the network: + - Minimum impact to the UE's registration and PDU Session Management procedures. + - Minimum impact to the slice selection procedure. +- No impact to Rel-15 UE. +- No impact to other basic system procedures such as the Mobility Management procedure, UE Configuration Update procedures, etc. +- No impact to Rel-15 roaming procedure. +- No impact to Rel-15 URSP/NSSP support for network slicing service mapping. + +##### 6.1.4.1.2 Working Assumptions and Concepts of Mutually Exclusive Access Slicing Group + +- 1) In this proposal, it assumes that different Mutually Exclusive Access Slicing Groups do NOT share the same serving AMF. Such assumption complies to the definition as defined in clause 3.1 of TR 23.740. +- 2) Given the consideration of the network slicing feature should be end-to-end, in the roaming scenario, this proposal expects that, UE, VPLMN and HPLMN are required to support Mutually Exclusive slicing access in order to enable Mutually Exclusive Slicing Access support in Rel-16. +- 3) For the Rel-16 UE, UE will be configured with UE capability to indicate whether it supports Mutually Exclusive Access to Network Slices. +- 4) For the Rel-16 5GC, if it does not support Mutually Exclusive Access to Network Slices, even when the Rel-16 UE presents its support for Mutually Exclusive Access to Network Slices during the UE Registration, such capability will be ignored by the Rel-16 5GC and no Mutually Exclusive Access to Network Slices are assigned to the UE. +- 5) Two scenarios when provisioning/configuring S-NSSAI(s) to the UE: + - A. Provisioning/configuring S-NSSAIs to the UEs for the Network Slices that all serve the UE simultaneously if the UE does not support Mutually Exclusive Access to Network Slices. + - B. Provisioning/configuring S-NSSAIs to the UEs for the Network Slices that do NOT all serve the UE simultaneously if the UE supports Mutually Exclusive Access to Network Slices. + +Same as in today Rel-15, during the UE Registration, the UDM may provide the Rel-16 serving PLMN all or some of the UE's subscriptions, according to the local policy and/or SLA in case of roaming, the serving PLMN determines the applicable S-NSSAI(s) to be provided to the UE. + +For the scenario A. above, there is only one set of provisioned/configured S-NSSAIs that all can serve the UE simultaneously. + +For the scenario B. above, the set of provisioned/configured S-NSSAI configured by the HPLMN will be composed of two or more set of S-NSSAIs that do NOT serve the UE simultaneously. In case of roaming, the corresponding mapping S-NSSAI(s) configured by the VPLMN will also be composed of two or more set of S-NSSAIs that do not serve the UE simultaneously in the VPLMN. + +#### 6.1.4.2 Functional description + +##### 6.1.4.2.1 Concepts of Mutually Exclusive Access Slicing Group + +The S-NSSAIs within the same Mutually Exclusive Access Slicing Group can serve the UE simultaneously, but not with the S-NSSAI(s) from different slicing groups. + +The Figure-6.4.2.1-1 below presents the concept on how the serving PLMN organizes the Mutually Exclusive Access Slicing Groups, and how the Allowed NSSAI and the corresponding serving AMF are derived from the Mutually Exclusive Access Slicing groups. + +During the Rel-16 UE registration with the Rel-16 5GC that supports Mutually Exclusive Access to Network Slices, the following four main scenarios to consider: + +- 1) If the UE does not provide the Requested NSSAI and the UE's capability indicates that, the UE is capable of supporting Mutually Exclusive Access to Network Slices, if there is more than one Mutually Exclusive Access Slicing Groups configured for the UE according to UE's subscription as described in scenario B above, based on the local and/or the roaming policy, the serving PLMN (via serving AMF or NSSF) will select a particular slicing group and derive the Allowed NSSAI for the UE from the selected slicing group, and if applicable, any associated S-NSSAI mappings with the HPLMN are also determined. The unselected Mutually Exclusive Access Slicing Groups and the associated mappings with the HPLMN, if applicable, will also be provided to the UE as the Configured NSSAI as in Rel-15. The associated slicing group information is also included for each S-NSSAI in the Configured NSSAI as well as in the associated mapping, if applicable. +- 2) If the UE provides the Requested NSSAI during the UE registration and the UE's capability indicates that, the UE is capable of supporting Mutually Exclusive Access to Network Slices, the serving PLMN decides the Allowed NSSAI based on the Requested NSSAI as in Rel-15. In addition, if there is more than one Mutually Exclusive Access Slicing Groups configured for the UE according to the UE's subscription as described in scenario B. above, the unselected Mutually Exclusive Access Slicing Groups and the associated mappings with the HPLMN, if applicable, will also be provided to the UE as the Configured NSSAI as in Rel-15. The associated slicing group information is also included for each S-NSSAI in the Configured NSSAI as well as in the associated mapping, if applicable. +- 3) If the there is no indication that the UE is capable of supporting Mutually Exclusive Access to Network Slices, the serving network shall only provide the UE for the Allowed NSSAI and/or Configured NSSAI with the S-NSSAIs as described in scenario A. above, and, if applicable, the associated mappings with the HPLMN that call all be served by the same AMF simultaneously. + +Fundamentally, Mutually Exclusive Access to Network Slices, if supported, is end-to-end. + +Table 6.1.4.2.1-1 summarizes the end-to-end considerations for supporting the Mutually Exclusive Access for Network Slicing in Rel-16 network. + +**Table 6.1.4.2.1-1: Summary of Considerations End-to-end Mutually Exclusive Access Support for Network Slicing** + +| UE Mutually Exclusive Access Slicing capability | | Serving PLMN Mutually Exclusive Access Slicing capability | Home PLMN Mutually Exclusive Access Slicing capability | End-to-end Mutually Exclusive Access Support | +|-------------------------------------------------|-----|-----------------------------------------------------------|--------------------------------------------------------|----------------------------------------------| +| Rel-15 UE | N/A | N/A | N/A | No | +| Rel-16 UE | No | N/A | N/A | No | +| | Yes | No | No | No | +| | Yes | No | Yes | No | +| | Yes | Yes | No | No | +| | Yes | Yes | Yes | Yes | + +**NOTE:** The serving AMF is part of the network slice, same AMF/AMF Set cannot serve two different Mutually Exclusive Access Slicing Groups. Different Allowed NSSAIs from different Mutually Exclusive Access Slicing Groups are served by different AMF/AMF Set. Hence, once the UE is registered, the serving AMF is corresponding to the Allowed NSSAI for particular Mutually Exclusive Access Slicing Group. If UE, that supports Mutually Exclusive Access to Network Slices, wants to activate service not belonging to the same Mutually Exclusive Access Slicing Group, then the UE is required to re-register with the new Requested NSSAI that includes the S-NSSAIs from the Configured NSSAI corresponding to the target service, and any existing PDU session, if any, will be released according to clause 5.15.5.2.2 in TS 23.501 [2] before the UE is registered with the new set of S-NSSAI(s) in the new Mutually Exclusive Access Slicing Group. + +Once Allowed NSSAI is identified, the subsequent PDU Session Establishment procedure is the similar to today Rel-15 procedures as described in clause 5.15.5 in TS 23.501 [2], except for the following: + +- The UE should only include the S-NSSAI from the Allowed NSSAI in the Requested NSSAI for UE registration; and if using the S-NSSAI from the Configured NSSAI, it shall have the same Slicing Group ID as the S-NSSAI in the Allowed NSSAI. +- The serving AMF shall verify the Slicing Group ID of the S-NSSAI in the Requested NSSAI is the same as the Allowed NSSAI that has been provided to the UE. Otherwise, the PDU Session Establishment request will be rejected with the proper cause to indicate the inappropriate Slicing Group ID of the S-NSSAI in the Requested NSSAI. + +![Diagram illustrating the concepts of Mutually Exclusive Access Slicing Groups and their Corresponding NSSAIs. The diagram shows a horizontal bar at the top labeled 'Groups of S-NSSAIs from PLMN-n' containing several colored boxes: 'Slice Inclusive Group-A (AMF Set A)' (yellow), 'Slice Inclusive Group-B (AMF Set B)' (orange), 'Slice Inclusive Group-C (AMF Set C)' (pink), 'Slice Inclusive Group-D (AMF Set D)' (light blue), 'Slice Inclusive Group-E (AMF Set E)' (purple), 'Slice Inclusive Group-Y (AMF Set Y)' (blue), and 'Slice Inclusive Group-Z (AMF Set Z)' (green). Below this bar, a vertical dashed line separates the network side (top) from the UE side (bottom). On the network side, there are four colored boxes representing network slices. Red arrows point from the top bar to these network slices. A red text annotation states: 'Network Slice corresponding to S-NSSAI k is the subset of Slice Inclusive Group-Z'. Another red text annotation states: 'Network Slice corresponding to S-NSSAI x is the subset of Slice Inclusive Group-B'. On the UE side, below the dashed line, there is a box labeled 'Mutually Exclusive Access Slicing Groups (A, B, Y and Z) corresponding to UE's Configured NSSAIs from PLMN-n'. Below this box, a text annotation states: 'UE's ](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +Diagram illustrating the concepts of Mutually Exclusive Access Slicing Groups and their Corresponding NSSAIs. The diagram shows a horizontal bar at the top labeled 'Groups of S-NSSAIs from PLMN-n' containing several colored boxes: 'Slice Inclusive Group-A (AMF Set A)' (yellow), 'Slice Inclusive Group-B (AMF Set B)' (orange), 'Slice Inclusive Group-C (AMF Set C)' (pink), 'Slice Inclusive Group-D (AMF Set D)' (light blue), 'Slice Inclusive Group-E (AMF Set E)' (purple), 'Slice Inclusive Group-Y (AMF Set Y)' (blue), and 'Slice Inclusive Group-Z (AMF Set Z)' (green). Below this bar, a vertical dashed line separates the network side (top) from the UE side (bottom). On the network side, there are four colored boxes representing network slices. Red arrows point from the top bar to these network slices. A red text annotation states: 'Network Slice corresponding to S-NSSAI k is the subset of Slice Inclusive Group-Z'. Another red text annotation states: 'Network Slice corresponding to S-NSSAI x is the subset of Slice Inclusive Group-B'. On the UE side, below the dashed line, there is a box labeled 'Mutually Exclusive Access Slicing Groups (A, B, Y and Z) corresponding to UE's Configured NSSAIs from PLMN-n'. Below this box, a text annotation states: 'UE's + +**Figure-6.1.4.2.1-1: Concepts of Mutually Exclusive Access Slicing Groups and their Corresponding NSSAIs** + +##### 6.1.4.2.2 Identification of Mutually Exclusive Access Slicing Group + +In order to differentiate different slicing groups for mutually exclusive access, there are two options to consider: + +- (1) Reserving portion of the SD field from S-NSSAI as the Slicing Group Identifier. For example, as shown in Figure-6.1.4.2.2-1 below, the SD field could be extended to indicate the support for mutually exclusive access slicing group. + +Pros: + +- The Group identifier is imbedded into the S-NSSAI and no need for introducing new identifier. +- Significantly lesser impact to the existing interface and the slicing related procedures by the UE and by the Network given the Group Identifier is imbedded into the S-NSSAI and hence, no new parameter is needed. + +Cons: + +- The size of the SD field is reduced and hence, the number of slice descriptors are reduced. +- (2) Introducing an additional Slicing Group Identifier which is used to associate with the S-NSSAI. +- Pros: +- No need to modify the S-NSSAI and hence, the size of the SD field are not impacted. +- Cons: +- Need to introduce additional identifier for the slicing group id. + - More significant impact to the existing interface and the slicing procedures given new parameter is needed to indicate the Group Identifier to be associated with the S-NSSAI for coordination. + +The Mutually Exclusive Access Slicing Group ID is per PLMN. In case of roaming, Slicing Group ID in the serving PLMN may have different value from the home PLMN. This is no different in Rel-15, where serving PLMN and home PLMN will have own respective S-NSSAI for the given network slice. Similar to Rel-15, there will be SLA agreement on the mapping for the S-NSSAIs between the serving PLMN and home PLMN to support Mutually Exclusive Access. + +This proposal does not preclude the scenario that operator may configure one or more S-NSSAI(s) that can serve the UE simultaneously together with any Mutually Exclusive Access Slicing Group. In this case, such S-NSSAI(s) are not tied to any specific slicing group and there should be special Slicing Group ID defined for such kind of S-NSSAI. + +The exact definition on how to partition the SD field or to introduce new additional identifier to support slicing group identification is determined by the CT group. If option (1) approach is taken, only the SD field is affected, hence, there is no impact to the Standardized SST value. Therefore, operator can organize the given S-NSSAIs with Standardized SST values by leveraging the SD field to support the grouping for Mutually Exclusive Access to Network Slices. + +![Diagram of S-NSSAI Identifier structure showing Slice Service Type (SST) and Slice Descriptor (SD) fields, with an arrow pointing to the SD field labeled 'n#'s of bits Reserved for Slicing Group ID'.](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +**S-NSSAI Identifier** + +The diagram illustrates the structure of an S-NSSAI Identifier. It is a horizontal bar divided into two main sections: 'Slice Service Type (SST)' on the left and 'Slice Descriptor (SD)' on the right. The SST section is further divided into three sub-fields: 'Slice Service Type (SST)' (highlighted in purple), 'Slice Service Type (SST)' (highlighted in light green), and 'Slice Service Type (SST)' (highlighted in light green). The SD section is divided into 'Slice Descriptor (SD)' (highlighted in light green) and 'n#'s of bits Reserved for Slicing Group ID' (highlighted in light green). An arrow points from the 'Slice Descriptor (SD)' sub-field to the 'n#'s of bits Reserved for Slicing Group ID' sub-field. + +Diagram of S-NSSAI Identifier structure showing Slice Service Type (SST) and Slice Descriptor (SD) fields, with an arrow pointing to the SD field labeled 'n#'s of bits Reserved for Slicing Group ID'. + +**Figure-6.1.4.2.2-1: Example of extending SD to identify the Mutually Exclusive Access Slicing Group** + +##### 6.1.4.2.3 UE Support for Mutually Exclusive Access Slicing Group + +For the Rel-15 UE or the Rel-16 UE that is not capable of supporting Mutually Exclusive Slicing Access attaches to the Rel-16 5GC that is capable to support Mutually Exclusive Access to network slicing, such UE will be provided with S-NSSAI(s) that can serve the UE simultaneously (see clause 6.1.4. 1.2 working assumptions above). There is no impact to Rel-15 UE. + +For the Rel-16 UE that is capable of supporting Mutually Exclusive Slicing Access, and if the network supports also the Mutually Exclusive Slicing Access, the UE shall include the S-NSSAIs that are in the same Mutually Exclusive Access Slicing Group in the Requested NSSAI during the UE's registration and also during the UE Session Establishment procedures. + +This proposal does not require any changes to clause 5.15.4, TS 23.501 [2] for the NSSAI storage aspects in the UE. + +##### 6.1.4.2.4 Roaming Support for Mutually Exclusive Access Slicing Group + +In case of roaming, in order to enable Mutually Exclusive Access, this proposal expects UE, serving network and home network are all capable of supporting Mutually Exclusive Slicing Access. Based on such working assumption, the serving and the home PLMN would have to coordinate the mapping of the S-NSSAI(s) with their respective Mutually Exclusive Access Slicing Group IDs according to the SLA and their respective local policy. + +##### 6.1.4.2.5 URSP/NSSP Support for Mutually Exclusive Access Slicing Group + +The URSP/NSSP in Rel-15 provides the service mapping between the Allowed/Configured S-NSSAIs in the UE to the UE's applications (refer to clause 6.6.2 in TS 23.503 [4] for more details). The same service mapping practice remains unchanged for Rel-16 as in Rel-15. + +As described in 6.1.4.1.2 working assumption above, there are two scenarios of S-NSSAIs to be provisioned/configured by the Mutually Exclusive Access capable 5GC to the UEs dependent on UE's Mutually Exclusive Access capable and not capable. + +In the case that the Mutually Exclusive Access capable UE is moving from Mutually Exclusive Access capable 5GC to incapable 5GC or vice versa, during the UE re-registration, the prior Allowed and Configured NSSAIs stored in the UE will be completely replaced by a new set of S-NSSAIs by following the procedures as described in clause 5.15.4 in TS 23.501 [2]. As a result, the UE will refer to the new set of S-NSSAI(s) (i.e. either scenario A. or scenario B. above) and the revised URSP/NSSP updated by the serving PCF for the service mapping to support the subsequent PDU Session Establishment procedures. + +In the case that the UE replaces its SIM card from Rel-15 to Rel-16 which supports Mutually Exclusive Access to Network Slices while attaching to the same serving 5GC (in case of roaming, including both VPLMN and HPLMN): + +- if the serving 5GC supports Mutually Exclusive Access to Network Slice, then the Mutually Exclusive Access support is enabled. The prior Allowed and Configured NSSAIs stored in the UE will be completely replaced by S-NSSAIs that support Mutually Exclusive Access by following the same procedures as described in clause 5.15.4 in TS 23.501 [2]. As a result, the UE will refer to the revised URSP/NSSP for the service mapping when initiating PDU Session Establishment procedures. +- if the serving 5GC does not support Mutually Exclusive Access to Network Slice, then the Mutually Exclusive Access support is not enabled. The prior Allowed and Configured NSSAIs stored in the UE may be replaced by S-NSSAI(s) that do not apply for Mutually Exclusive Access following the same procedures as described in clause 5.15.4 in TS 23.501 [2]. + +In the case that the UE replaces its SIM card from Rel-15 to Rel-16 which does not support Mutually Exclusive Access to Network Slices while attaching to the same serving 5GC (in case of roaming, including both VPLMN and HPLMN), irrespective the attached serving system supports Mutually Exclusive Access or not, the prior Allowed and Configured NSSAIs stored in the UE may be replaced by S-NSSAI(s) that do not apply for Mutually Exclusive Access by following the same procedures as described in clause 5.15.4 in TS 23.501 [2]. + +In the case that the UE replaces its SIM card from Rel-16 to Rel-15 while attaching to the same serving 5GC (in case of roaming, including both VPLMN and HPLMN), irrespective the attached serving 5GC supports Mutually Exclusive Access or not, the prior Allowed and Configured NSSAIs stored in the UE may be updated with S-NSSAI(s) that do not apply for Mutually Exclusive Access by following the same procedures as described in clause 5.15.4 in TS 23.501 [2]. + +In summary, the existing URSP/NSSP related procedures are unchanged, and this proposal makes no impact to the URSP/NSSP as defined in Rel-15. + +##### 6.1.2.4.6 AMF Support for Mutually Exclusive Access Slicing Group + +The following procedures are based on clause 5.15.5.2.1, in TS 23.501 [2] with the changes shown in italic fonts and the changes are based on the use of option (1) in clause 6.4.2.2 above for the identification of Mutually Exclusive Access Slicing Group. + +**(A)** *During the UE's initial registration, once the UE's subscriptions for the network slicing are obtained from UDM, depending on AMF local configuration, the AMF may be allowed to determine whether it can serve the UE, and the following is performed:* + +- AMF checks whether it can serve all the S-NSSAI(s) from the Requested NSSAI present in the Subscribed S-NSSAIs (potentially using configuration for mapping S-NSSAI values between HPLMN and Serving PLMN), or all the S-NSSAI(s) marked as default in the Subscribed S-NSSAIs in the case that no Requested NSSAI was provided or none of the S-NSSAIs in the Requested NSSAI were present in the Subscribed S-NSSAIs (see clause 5.15.3 in TS 23.501 [2]). +- *If Mutually Exclusive Access to Network Slices is supported and there is more than one slicing groups marked as default in the Subscribed S-NSSAIs, based on the operator's configuration, the AMF will then decide which particular Slicing Group is to be selected.* + +- If the AMF can serve the S-NSSAIs in the Requested NSSAI, the AMF remains the serving AMF for the UE. The Allowed NSSAI is then composed of the list of S-NSSAI(s) in the Requested NSSAI permitted based on the Subscribed S-NSSAIs, or, if no Requested NSSAI was provided, all the S-NSSAI(s) marked as default in the Subscribed S-NSSAIs, *and if Mutually Exclusive Access to Network Slices is supported, the default Subscribed S-NSSAIs for the selected Slicing Group*. The AMF also determines the mapping if the S-NSSAI(s) included in the Allowed NSSAI needs to be mapped to Subscribed S-NSSAI(s) values. + +If no Allowed NSSAI is determined from above, the AMF based on the Subscribed S-NSSAI(s) and operator's configuration may also determine the Configured NSSAI for the Serving PLMN or/and the associated mapping of the Configured NSSAI to the Configured NSSAI for the HPLMN, so these can be configured in the UE. Then Step (C) below is executed. + +- *Otherwise*, the AMF queries the NSSF (see (B) below). + +(B) When required as described above, the AMF needs to query the NSSF, and the following is performed: + +- The AMF queries the NSSF, with Requested NSSAI, mapping of Requested NSSAI to Configured NSSAI for the HPLMN, the Subscribed S-NSSAIs (with an indication if marked as default S-NSSAI), any Allowed NSSAI it might have for the other Access Type (including its mapping to the Configured NSSAI for the HPLMN), PLMN ID of the SUPI and UE's current Tracking Area(s). + +NOTE 1: When more than one UE's Tracking Area is indicated, the UE is using more than one Access Type. + +- Based on this information, local configuration, and other locally available information including RAN capabilities in the current Tracking Area for the UE or load level information for a network slice instance provided by the NWDAF, the NSSF does the following: + - It verifies which S-NSSAI(s) in the Requested NSSAI are permitted based on comparing the Subscribed S-NSSAIs with the S-NSSAIs in the mapping of Requested NSSAI to Configured NSSAI for the HPLMN. It considers the S-NSSAI(s) marked as default in the Subscribed S-NSSAIs in the case that no S-NSSAI from the Requested NSSAI are present in the Subscribed S-NSSAIs. + - It selects the Network Slice instance(s) to serve the UE. When multiple Network Slice instances in the UE's Tracking Areas are able to serve a given S-NSSAI, based on operator's configuration, the NSSF may select one of them to serve the UE, or the NSSF may defer the selection of the Network Slice instance until a NF/service within the Network Slice instance needs to be selected. + - It determines the target AMF Set to be used to serve the UE, or, based on configuration, the list of candidate AMF(s), possibly after querying the NRF. + - It determines the Allowed NSSAI(s) for the applicable Access Type(s), taking also into account the availability of the Network Slice instances as described in clause 5.15.8 in TS 23.501 [2] that are able to serve the S-NSSAI(s) in the Allowed NSSAI in the current UE's Tracking Areas. *If there is more than one slicing groups in the Subscribed S-NSSAIs, based on the operator's configuration and local policy, the NSSF will then decide which particular Slicing Group is to be selected as the Allowed NSSAI(s) for the applicable Access Type(s)*. + - It also determines the mapping of each S-NSSAI of the Allowed NSSAI(s) to the Subscribed S-NSSAIs if necessary. + - Based on operator configuration, the NSSF may determine the NRF(s) to be used to select NFs/services within the selected Network Slice instance(s). + - Additional processing to determine the Allowed NSSAI(s) in roaming scenarios and the mapping to the Subscribed S-NSSAIs, as described in clause 5.15.6 in TS 23.501 [2]. + - If no Allowed NSSAI is determined from above, the NSSF based on the Subscribed S-NSSAI(s) and operator configuration may derive the Configured NSSAI for the Serving PLMN or/and the associated mapping of the Configured NSSAI to the Configured NSSAI for the HPLMN, so these can be configured in the UE. +- The NSSF returns to the current AMF the Allowed NSSAI for the applicable Access Type(s), the mapping of each S-NSSAI of the Allowed NSSAI to the Subscribed S-NSSAIs if determined and the target AMF Set, or, based on configuration, the list of candidate AMF(s). The NSSF may return the NRF(s) to be used to select NFs/services within the selected Network Slice instance(s), and the NRF to be used to determine the list of candidate AMF(s) from the AMF Set. The NSSF may return NSI ID(s) to be associated to the Network Slice + +instance(s) corresponding to certain S-NSSAIs. NSSF may return the rejected S-NSSAI(s) as described in clause 5.15.4.1 *in TS 23.501 [2]*. The NSSF may return the Configured NSSAI for the Serving PLMN and the associated mapping of the Configured NSSAI to the Configured NSSAI for the HPLMN. + +- Depending on the available information and based on configuration, the AMF may query the appropriate NRF (e.g. locally pre-configured or provided by the NSSF) with the target AMF Set. The NRF returns a list of candidate AMFs. +- If rerouting to a target serving AMF is necessary, the current AMF reroutes the Registration Request to a target serving AMF as described in clause 5.15.5.2.3 *in TS 23.501 [2]*. +- Step (C) is executed. + +(C) The serving AMF shall determine a Registration Area such that all S-NSSAIs of the Allowed NSSAI for this Registration Area are available in all Tracking Areas of the Registration Area (and also considering other aspects as described in clause 5.3.2.3 *in TS 23.501 [2]*) and then return to the UE this Allowed NSSAI and the mapping of the Allowed NSSAI to the Subscribed S-NSSAIs if provided. The AMF may return the rejected S-NSSAI(s) as described in clause 5.15.4.1 *in TS 23.501 [2]*. + +NOTE 2: As there is a single distinct Registration Area for Non-3GPP access in a PLMN, the S-NSSAIs in the Allowed NSSAI for this Registration Area (i.e. for Non-3GPP access) are available homogeneously in the PLMN. + +When no Requested NSSAI was included, or when the mapping of the S-NSSAIs in Requested NSSAI to the corresponding values in the Configured NSSAI for the HPLMN is incorrect, or when an S-NSSAI was rejected in the PLMN, the AMF may update the UE slice configuration information for the PLMN as described in clause 5.15.4.2 *in TS 23.501 [2]*. + +#### 6.1.4.3 Procedures + +##### 6.1.4.3.1 UE Registration with Mutually Exclusive Access Slicing Group + +The following procedures are based on clause 4.2.2.2.3, *in TS 23.502 [3] v15.2* with the changes shown in italic fonts and the changes are based on the use of option (1) in clause 6.4.2.2 above for the identification of Mutually Exclusive Access Slicing Group. + +When an AMF receives a Registration request, the AMF may need to reroute the Registration request to another AMF, e.g. when the initial AMF is not the appropriate AMF to serve the UE. The Registration with AMF re-allocation procedure, described in figure 4.2.2.2.3-1 of TS 23.502 [3], is used to reroute the NAS message of the UE to the target AMF during a Registration procedure. + +![Sequence diagram illustrating UE Registration Procedures to support Mutually Exclusive Access. Lifelines: (R)AN, Initial AMF, Target AMF, NSSF, NRF, UDM, Old AMF. The diagram shows the flow of messages between these entities, including Initial UE message, Nudm_SDM_Get, Nnssf_NSSelection_Get, Nnamf_Communication_RegistrationCompleteNotify, Nnrf_NFDiscovery_Request, and N2 messages. It also includes optional steps and conditional branches (A and B).](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant (R)AN + participant Initial AMF + participant Target AMF + participant NSSF + participant NRF + participant UDM + participant Old AMF + + Note left of (R)AN: 1. Initial UE message + (R)AN->>Initial AMF: 1. Initial UE message + Note left of Initial AMF: 2. Optionally steps 4-9a of figure 4.2.2.2.2-1 in TS 23.502. + Note right of Initial AMF: 3a. Nudm_SDM_Get(Slice Selection Subscription data) + Initial AMF->>UDM: 3a. Nudm_SDM_Get(Slice Selection Subscription data) + Note right of UDM: 3b. Nudm_SDM_Get response + UDM-->>Initial AMF: 3b. Nudm_SDM_Get response + Note right of Initial AMF: 4a. Nnssf_NSSelection_Get + Initial AMF->>NSSF: 4a. Nnssf_NSSelection_Get + Note right of NSSF: 4b. Nnssf_NSSelection_Get response + NSSF-->>Initial AMF: 4b. Nnssf_NSSelection_Get response + Note right of Initial AMF: 5 Nnamf_Communication_RegistrationCompleteNotify + Initial AMF->>Old AMF: 5 Nnamf_Communication_RegistrationCompleteNotify + Note right of Old AMF: 6a. Nnrf_NFDiscovery_Request + Old AMF->>NRF: 6a. Nnrf_NFDiscovery_Request + Note right of NRF: 6b. Nnrf_NFDiscovery_Request Response + NRF-->>Old AMF: 6b. Nnrf_NFDiscovery_Request Response + Note right of Old AMF: 7a. Nnamf_Communication_N1MessageNotify + Old AMF->>Initial AMF: 7a. Nnamf_Communication_N1MessageNotify + Note left of Initial AMF: (A) 7b. N2 message + Initial AMF-->>(R)AN: 7b. N2 message + Note left of Initial AMF: 7c. N2 message + Initial AMF->>Target AMF: 7c. N2 message + Note left of Target AMF: (B) 7a. Reroute NAS message + Target AMF-->>Initial AMF: 7a. Reroute NAS message + Note left of Initial AMF: 7b. Initial UE message + Initial AMF->>Target AMF: 7b. Initial UE message + Note left of Target AMF: 8. Steps 4-22 of figure 4.2.2.2.2-1 or Steps 8-22 of figure 4.2.2.2.2-1 in TS 23.502 + +``` + +Sequence diagram illustrating UE Registration Procedures to support Mutually Exclusive Access. Lifelines: (R)AN, Initial AMF, Target AMF, NSSF, NRF, UDM, Old AMF. The diagram shows the flow of messages between these entities, including Initial UE message, Nudm\_SDM\_Get, Nnssf\_NSSelection\_Get, Nnamf\_Communication\_RegistrationCompleteNotify, Nnrf\_NFDiscovery\_Request, and N2 messages. It also includes optional steps and conditional branches (A and B). + +**Figure 6.1.4.3.1-1: UE Registration Procedures to support Mutually Exclusive Access** + +1. Steps 1 and 2 of figure 4.2.2.2.2-1 in TS 23.502 [3] have occurred, and the (R)AN sends the Registration request message within an Initial UE message to the initial AMF; and in case the UE is to re-register with Requested NSSAI corresponding to a different Mutually Exclusive Access Slicing Group, the UE shall not provide the 5G-GUTI in Access Stratum signalling when performing a Registration procedure. The Initial UE message may or may not include the Requested NSSAI, and the Initial UE message and re-registration message may or may not include the UE MM Core Network Capability that indicates its support for Mutually Exclusive Access to network slices. +2. If the AMF needs the SUPI and/or UE's subscription information to decide whether to reroute the Registration Request or if the Registration Request was not sent integrity protected or integrity protection is indicated as failed, then AMF performs steps 4 to 9a of figure 4.2.2.2.2-1 in TS 23.502 [3]. +- 3a. [Conditional] Initial AMF to UDM: Nudm\_SDM\_Get (SUPI, Slice Selection Subscription data). + +If the initial AMF needs UE's subscription information to decide whether to reroute the Registration Request and UE's slice selection subscription information was not provided by old AMF, then initial AMF request UE's Slice Selection Subscription data from UDM by invoking the Nudm\_SDM\_Get (see clause 5.2.3.3.1 in TS 23.502 [3]) service operation. UDM may get this information from UDR by Nudr\_UDM\_Query(SUPI, Subscribed S-NSSAIs). In addition, if the serving PLMN, and in case of roaming, the HPLMN and the UE are capable of + +*supporting the Mutually Exclusive Access to Network Slices, the initial AMF includes also the UE's capability in Nudm\_SDM\_Get service operation.* + +- 3b. UDM to initial AMF: Response to Nudm\_SDM\_Get. The AMF gets the Slice Selection Subscription data including Subscribed S-NSSAIs. The UDM may provide indication that the subscription data for network slicing is updated for the UE. + +UDM responds with slice selection data to initial AMF *with the consideration for the support for the Mutually Exclusive Access to Network Slices in the serving PLMN, in the UE (i.e. indicated by the UE MM Core Network Capability provided by the initial AMF), and in case of roaming, in the Home PLMN.* + +- 4a. [Conditional] Initial AMF to NSSF: Nnssf\_NSSelection\_Get (Requested NSSAI, [Mapping Of Requested NSSAI], Subscribed S-NSSAI(s) with the default S-NSSAI indication, TAI, Allowed NSSAI for the other access type (if any), [Mapping of Allowed NSSAI], PLMN ID of the SUPI). + +If there is a need for slice selection, (see clause 5.15.2.1 of TS 23.501 [2]), e.g. the initial AMF cannot serve all the S-NSSAI(s) from the Requested NSSAI permitted by the subscription information, the initial AMF invokes the Nnssf\_NSSelection\_Get service operation from the NSSF by including Requested NSSAI, optionally Mapping Of Requested NSSAI, Subscribed S-NSSAIs with the default S-NSSAI indication, Allowed NSSAI for the other access type (if any), Mapping of Allowed NSSAI, PLMN ID of the SUPI and the TAI of the UE. + +- 4b. [Conditional] NSSF to Initial AMF: Response to Nnssf\_NSSelection\_Get (AMF Set or list of AMF addresses, Allowed NSSAI for the first access type, [Mapping Of Allowed NSSAI], [Allowed NSSAI for the second access type], [Mapping of Allowed NSSAI], [NSI ID(s)], [NRF(s)], [List of rejected (S-NSSAI(s), cause value(s))], [Configured NSSAI for the Serving PLMN], [Mapping Of Configured NSSAI]). + +The NSSF performs the steps specified in point (B) *in clause 6.2.4.6 above*. The NSSF returns to initial AMF the Allowed NSSAI for the first access type, optionally the Mapping Of Allowed NSSAI, the Allowed NSSAI for the second access type (if any), optionally the Mapping of Allowed NSSAI and the target AMF Set or, based on configuration, the list of candidate AMF(s). The NSSF may return NSI ID(s) associated to the Network Slice instance(s) corresponding to certain S-NSSAI(s). The NSSF may return the NRF(s) to be used to select NFs/services within the selected Network Slice instance(s). It may return also information regarding rejection causes for S-NSSAI(s) not included in the Allowed NSSAI. The NSSF may return Configured NSSAI for the Serving PLMN, and possibly the associated mapping of the Configured NSSAI. + +NOTE 1: The NRF(s) is returned by the NSSF, if any, belong to any level of NRF (see clause 6.2.6 of TS 23.501 [2]) according to the deployment decision of the operator. + +5. [Conditional] Initial AMF to old AMF: Namf\_Communication\_RegistrationCompleteNotify (failure cause). + +The initial AMF decides to reroute the NAS message to another AMF. The initial AMF sends a reject indication to the old AMF telling that the UE Registration procedure did not fully complete at the initial AMF. The old AMF continues as if the Namf\_Communication\_UEContextTransfer had never been received. + +- 6a. [Conditional] Initial AMF to NRF: Nnrf\_NFDiscovery\_Request (NF type, AMF Set). + +If the initial AMF does not locally store the target AMF address, and if the initial AMF intends to use direct reroute to target AMF or the reroute via (NG-R)AN message needs to include AMF address, then the initial AMF invokes the Nnrf\_NFDiscovery\_Request service operation from the NRF to find a proper target AMF which has required NF capabilities to serve the UE. The NF type is set to AMF. The AMF Set is included in the Nnrf\_NFDiscovery\_Request. + +- 6b. [Conditional] NRF to AMF: Response to Nnrf\_NFDiscovery\_Request (list of (AMF pointer, AMF address, plus additional selection rules and NF capabilities)). + +The NRF replies with the list of potential target AMF(s). The NRF may also provide the details of the services offered by the candidate AMF(s) along with the notification end-point for each type of notification service that the selected AMF had registered with the NRF, if available. As an alternative, it provides a list of potential target AMFs and their capabilities, and optionally, additional selection rules. Based on the information about registered NFs and required capabilities, a target AMF is selected by the initial AMF. + +If the initial AMF is not part of the target AMF set, and is not able to get a list of candidate AMF(s) by querying the NRF with the target AMF set (e.g. the NRF locally pre-configured on AMF does not provide the requested information, the query to the appropriate NRF provided by the NSSF is not successful, or the initial AMF has knowledge that the initial AMF is not authorized as serving AMF etc.) then the initial AMF shall forward the + +NAS message to the target AMF via (R)AN executing step 7(B); the Allowed NSSAI and the AMF Set are included to enable the (R)AN to select the target AMF. + +- 7(A). If the initial AMF, based on local policy and subscription information, decides to forward the NAS message to the target AMF directly, the initial AMF invokes the Namf\_Communication\_N1MessageNotify to the target AMF, carrying the rerouted NAS message. The Namf\_Communication\_N1MessageNotify service operation includes the information enabling (R)AN to identify the N2 terminating point and the NAS message carried at step 1, and the UE's SUPI and MM Context if available. If the initial AMF has obtained the information from the NSSF as described at step 4b, that information except the AMF Set or list of AMF addresses is included. The target AMF then updates the (R)AN with a new updated N2 termination point for the UE (step 7b), the (R)AN acknowledges the updated N2 termination point (step 7c). Step 7(B) is skipped. + +NOTE 2: Steps 7b and 7c can occur separately or as part of the first subsequently required N2 interaction. + +- 7(B). If the initial AMF, based on local policy and subscription information, decides to forward the NAS message to the target AMF via (R)AN, the initial AMF sends a Reroute NAS message to the (R)AN (7a). The Reroute NAS message includes the information about the target AMF and the Registration Request message carried at step 1. If the initial AMF has obtained the information as described at step 4b, that information is included. The (R)AN sends the Initial UE message to the target AMF (7b) indicating reroute due to slicing including the information from step 4b that the NSSF provided. + +8. After receiving the Registration Request message transmitted at step 7(A)a or step 7(B)b, if no UE context is received from the initial AMF, the target AMF, based on rerouting due to slicing, continues with the Registration procedure from step 4 until 22 of figure 4.2.2.2.2-1 in TS 23.501 [2] (with the target AMF corresponding to the new AMF). If the UE context is received from the initial AMF, the target AMF continues with the Registration procedure from step 8 or 9b (depending on whether it decides to reauthenticate the UE) until step 22 of figure 4.2.2.2.2-1 in TS 23.501 [2], skipping step 10. + +#### 6.1.4.4 Impacts on existing entities and interfaces + +- UE: Support of Mutual Exclusive Access Group Information and procedures that include it for its configuration in the UE from the network. +- AMF: Enforcement of the Mutual Exclusive Access Group Information received from UDM and/or inclusion in NSSF queries as part of sending the Subscribed S-NSSAIs. +- NSSF: Enforcement of the Mutual Exclusive Access Group Information. +- UDM: Provision of the Mutual Exclusive Access Group Information in the UE based on UE's Mutually Exclusive Access capability and if applicable, the SLA roaming agreement with the UE's HPLMN. + +#### 6.1.4.5 Evaluation + +### 6.1.5 Solution #1.5: Mutually Exclusive Access to Network Slices using existing mechanisms + +#### 6.1.5.1 Introduction + +This is a solution to Key Issue #1, "Mutually Exclusive Access to Network Slices". + +This solution is based on existing Rel-15 slice selection mechanisms and does not require any protocol impacts. + +#### 6.1.5.2 Functional description + +##### 6.1.5.2.1 General assumptions + +This solution assumes the following: + +- It is assumed that the UE has internal logic (e.g. MMI, or software support) to understand which applications are needed at a given time, and is able to prioritize the applications requiring different S-NSSAIs. The UE also orders the S-NSSAIs in the Requested NSSAI according to their priority from how the UE wants to use them (i.e. when an application is of highest priority the associated S-NSSAI is derived, e.g. from the URSP, and the S- + +NSSAI is put first in the Requested NSSAI). The UE continues to derive the priority of the subsequent S-NSSAIs based on the importance of the applications and places the resulting S-NSSAIs in priority order in the Requested NSSAI. The UE derives S-NSSAIs for all the applications the UE wants to use, and the UE should derive the priority order for all of the S-NSSAIs. + +- It is assumed that the AMF/NSSF leverage on the understanding that the Requested NSSAI is sorted in a priority order, and that the AMF/NSSF does not include in the Allowed NSSAI S-NSSAIs of lower priority which are Mutually Exclusive from higher priority S-NSSAIs. +- The UE understands that an S-NSSAI requested (i.e. it exists in the Configured NSSAI for the serving PLMN) which is not rejected nor in the Allowed NSSAI is mutually exclusive to one or more of the S-NSSAIs in the Allowed NSSAI. If the UE wants to access such an S-NSSAI, the UE puts it with high priority in a new Requested NSSAI. + +##### 6.1.5.2.2 Applying proposed logic to an example + +Example Network Configuration: + +![Diagram showing eight network slices (A-H) arranged in a 2x2 grid. Each slice is in a dashed oval. Slice A and B are in the top-left oval, C and D in the top-right, E and F in the bottom-left, and G and H in the bottom-right. This illustrates that slices within the same oval are mutually exclusive.](55136bc716146672fc680fa05989f1d2_img.jpg) + +Diagram showing eight network slices (A-H) arranged in a 2x2 grid. Each slice is in a dashed oval. Slice A and B are in the top-left oval, C and D in the top-right, E and F in the bottom-left, and G and H in the bottom-right. This illustrates that slices within the same oval are mutually exclusive. + +**Figure 6.1.5.2.2-1: Example Network configuration for Mutually Exclusive Network Slices** + +Example UE configuration: + +- Configured NSSAI: Slice A, B, C, D, E, F, G, H. +- URSP/NSSP: App1a, App1b, App1c->Slice A, App2a, App2b->Slice B, App3a, App3b->Slice C, App4->Slice D, App5->Slice E, App6->Slice F, App7->Slice G, App8->Slice H. + +Scenario 1: + +1. The UE wants to use 3 applications with priority App1a, App3a, App2a. +2. Requested NSSAI (Slice A, Slice C, Slice B). +3. Allowed NSSAI (Slice A, Slice B): + - The network does not include Slice C in the Allowed NSSAI as it is not allowed to be accessed at the same time as the higher prioritized Slice A. +4. From the Allowed NSSAI, the UE understands that Slice C may be mutually exclusive from Slice A. +5. Time pass and the UE wants to use App3a i.e. the UE puts the Slice C with higher priority: Requested NSSAI (Slice C, Slice A, Slice B). +6. Allowed NSSAI (Slice C): + - UE anticipated that Slice A and Slice C would not be accepted into the Allowed NSSAI but included them anyway to make network aware of UE wanted slices. + +In the above scenario the optimal Network Slice configuration is achieved immediately. + +Scenario 2: + +1. The UE wants to use 6 applications App1a, App1b, App2a, App2b, App3a, App5 and highest priority is App1a. From URSP UE derives that App1a is to use Slice A and so is App1b. Second priority is App2a, and from URSP + +the UE derives the slice to be used and also that App2b is to use the same slice. The UE has no further preferences on priority between the other applications but derives the slices to be used and places these in the Requested NSSAI after the prioritized slices. + +2. Requested NSSAI (Slice A, Slice B, Slice C, Slice E): + - The network handles the Requested NSSAI as the S-NSSAIs are in priority order. +3. Allowed NSSAI (Slice A, Slice B): + - The network does not include Slice C and Slice E in the Allowed NSSAI as it is not allowed to be accessed at the same time as the higher prioritized Slice A and Slice B. +4. From the Allowed NSSAI, the UE understands that Slice C and Slice E may be mutually exclusive from Slice A and Slice B. +5. Time pass and the UE wants to use App3a, and sends a new Requested NSSAI (Slice C, Slice A, Slice B). +6. Allowed NSSAI (Slice C): + - The network does not include Slice A and Slice B in the Allowed NSSAI as they are not allowed to be accessed at the same time as the higher prioritized Slice C. + +###### Scenario 3: + +1. The UE wants to use 1 application App1a. +2. Requested NSSAI (Slice A). +3. Allowed NSSAI (Slice A). +4. The UE establishes a PDU Session using Slice A. +5. Time pass and the UE wants to use App3a i.e. two options exist: + - Option 1: + - the UE need to use App3a, but the current App1a is more important: Requested NSSAI (Slice A, Slice C); + - Allowed NSSAI (Slice A): + - the UE knows that Slice A and Slice C may be mutually exclusive and to be able to use App3 the UE needs to put Slice C with higher priority than Slice A. + - Option 2: + - the UE really need to use App3a, i.e. it is more important than current App1a (even though it has an established PDU Session): Requested NSSAI (Slice C, Slice A). + - Allowed NSSAI (Slice C) and the network released the current PDU Session for Slice A as the PDU Session shall not be allowed to be used when UE is registered to the Slice C. + - the UE knows that Slice A and Slice C may be mutually exclusive. + - the UE establishes a PDU Session for Slice C. + +In the above scenario the optimal Network Slice configuration is achieved immediately for both options. + +The options 1 and 2 shows how to handle already established PDU Sessions. + +It is unlikely that there are already deployed Rel-15 UEs, but if there are then it can be assumed that these UEs either can be updated to apply the logic described above or that these UEs simply add S-NSSAIs to the end of the Requested NSSAI and then there is no issue as they are seen as lower priority by the network. + +#### 6.1.5.3 Procedures + +##### 6.1.5.3.1 General + +No new procedures are required with this solution. + +##### 6.1.5.3.2 Signalling within the network + +In principle this solution is independent from how information is signalled within the network, i.e. this solution can be combined with any other solution addressing the required signalling within the network. + +NSSF and AMF are possible decision points. HPLMN and VPLMN input needed. + +For V-NSSF, no need for any signalling for VPLMN considerations. + +When AMF is the decision point, the VPLMN considerations is likely achieved by O&M in the AMF as otherwise why decide in AMF? + +For HPLMN input, one may consider SLA or VPLMN getting input from UDM, H-PCF or H-NSSF. + +Consequently, the only new signalled information that may be required is the signalling of HPLMN policies towards the VPLMN (unless derived by SLA). The most straightforward option seems to be to signal the HPLMN input from UDM to the AMF, and then if decision point is NSSF the AMF forwards the HPLMN input to the NSSF. + +##### 6.1.5.3.3 Interactions with Rel-15 usage of Allowed NSSAI + +In Rel-15, the S-NSSAIs that the UE proposed in the Requested NSSAI which were not included in the Allowed NSSAI nor rejected are subscribed S-NSSAIs (as included in the Configured NSSAI) but currently not available for usage (e.g. not available in the RA). The UE does not have more information than that why the S-NSSAI was not registered, i.e. there is no defined procedure in Rel-15 for allowing the UE to discover when an S-NSSAI becomes available in the new area for the UE. One could propose a similar logic as for LADN, in which the UE gets notified which LADNs are available for the UE in the new RA. Such logic could be seen as new functionality and therefore not agreeable. + +Under current circumstances, as the UE does not know when an S-NSSAI becomes available the UE has no other choice than to propose the same S-NSSAI again in the Requested NSSAI. Combining the proposed logic for handling mutually exclusive slices, it would mean that the UE should propose the S-NSSAI in the order of priority the UE wants the S-NSSAI to be registered. + +##### 6.1.5.3.4 Characteristics of the solution + +This solution has no impacts to the protocol towards the UE, and in case SLA covers the agreements of MEANS for Network Slices then there is no need for any signalling within the network. In case SLA is not enough as a solution, then signalling of HPLMN requirement for MEANS to VPLMN would be required, and that is assumed to be covered by another solution. + +The solution achieves an optimal combination of network slice configuration for a UE without the need to signal any additional MEANS information from the network to the UE. + +The logic that the UE order the S-NSSAIs in priority order could be efficient when the information the UE has available is outdated, i.e. the solution can be used also when MEANS information is standardized as to allow a network decision already before sending the updated MEANS information to the UE. + +The UE does not know whether the Slices really are mutually exclusive, but there is no need for the UE to know as the UE can act the same way independently. + +The Requested NSSAI becomes larger than necessary as the UE always provides the slices the UE wants to use (derived by wanted applications and the URSP), but thereby the network gets aware of which slices the UE really wants to access and the network operator may try to address the customer needs by creating new slice configuration accordingly (MEANS groups). + +#### 6.1.5.4 Impacts on existing entities and interfaces + +Impacts compared to Rel-15: + +- This solution has no protocol impacts, but only a few logical assumptions. + +UE impact: + +- The UE provides the list of S-NSSAIs in the Requested NSSAI in priority order. +- The UE understands that an S-NSSAI requested (i.e. it exists in the Configured NSSAI for the serving PLMN) which is not rejected nor in the Allowed NSSAI is mutual exclusive to one or more of the S-NSSAIs in the Allowed NSSAI. If the UE wants to access such an S-NSSAI, the UE puts it with high priority in a new Requested NSSAI. + +5GC impact (serving and home): + +- The AMF/NSSF assumes that the UE provides the list of S-NSSAIs in the Requested NSSAI in priority order. +- If the Requested NSSAI includes Mutually Exclusive S-NSSAIs, then the AMF/NSSF does not include the S-NSSAIs of lower priority in the Allowed NSSAI until all S-NSSAIs of the Allowed NSSAI are allowed to be access together. +- Impacts to make VPLMN aware of HPLMN policies for MEANS and for applying VPLMN policies in the VPLMN. + +In this solution, Mutually Exclusive Access to Network Slices in the network is already supported in Rel-15 and does not require any further changes. Actual isolation of resources between network slices is supported by the underlying virtualisation environment and OAM (see SA5 specifications). + +#### 6.1.5.5 Evaluation + +### 6.1.6 Solution #1.6: Enabling access control to network slices that cannot be access simultaneously + +#### 6.1.6.1 Introduction + +##### 6.1.6.1.1 Design Principles + +The following consideration constitute the Design Principles substantiating this solution: + +- It should be possible for an operator to decide whether two or more Network Slices can be configured to be accessed within the same PLMN and whether they can be accessed simultaneously or not on a per UE basis. +- The current Rel-15 Configured NSSAI concept, which establishes that a Configured NSSAI "may either be configured by a Serving PLMN and apply to the Serving PLMN, or may be a Default Configured NSSAI configured by the HPLMN and that applies to any PLMN" should be preserved. +- Rel-15 baseline should be used for basic enforcement of Access to Network Slices whereby a UEs use the Requested NSSAI to signal what Network Slices the UE is requesting to access in the current PLMN. As such the Requested NSSAI should be based on the (Default) Configured NSSAI and Allowed NSSAI when available. + +##### 6.1.6.1.2 Working Assumptions + +Operator defined Access to Network Slices: The proposal assumes that an operator should be able to determine what Network Slices should or should not be accessed together at all and what Network Slices can be accessed within the same PLMN but not simultaneously on a per UE basis. + +During the Registration procedure the UE is provided with an Allowed NSSAI, and information on whether two or more S-NSSAIs in the Configured NSSAI cannot be supported by the 5GS to serve the UE simultaneously and information whether two or more S-NSSAIs, contained in the Allowed NSSAI can be used simultaneously. This information is provided as part of the Registration Accept message and in this proposal, this information is referred to as Network Slice exclusion rules. The UE can then use this information (i.e., Network Slice exclusion rules, Configured NSSAI and Allowed NSSAI) to determine whether the 5GS supports a combination of S-NSSAIs from the Configured NSSAI which the UE uses when constructing the Requested NSSAI. In addition, the UE can determine whether two or more Network Slices can be used simultaneously, when requesting access to UP resources, e.g. through a PDU Session Establishment procedure or a CP resources, e.g., through a Service Request procedure. + +Network Slice exclusion rules proposed in this solution also supports the case where an operator chooses to configure an AMF or NSSF to provide only non-mutually exclusive Network Slices in the Allowed NSSAI, if it is so desired. + +The solution sticks to current Rel. 15 definition of Allowed NSSAI: "NSSAI provided by the Serving PLMN during e.g. a Registration procedure, indicating the S-NSSAIs values the UE could use in the Serving PLMN for the current registration area" + +Therefore, the solution assumes an operator may configure the AMF to include the Allowed NSSAI combinations of S-NSSAIs that are allowed in the current registration area but that may or may not be used simultaneously, in contrast with the Allowed NSSAI used in Rel-15 where Network Slices can always be used simultaneously. + +The enforcement of mutually exclusive rules, e.g. when the Allowed NSSAI includes combinations of S-NSSAIs referring to Network Slices that may and may not be used simultaneously, takes place during PDU Session Establishment and Service Request procedures. + +As per Rel-15 principles, upon the establishment of a NAS Signalling connection, a single N1 termination point is located in the AMF and the AMF may keep the NAS signalling connection until the UE de-registers from the network. The AMF is therefore in the position to enforce exclusion rules for messages intended to Network Slices that that should not be used simultaneously with other already serving Network Slices. + +The solution assumes that different Network Slice exclusion rules affecting the same set of slices could be provided to different UEs. + +The solution assumes that a common AMF may be shared by two or more Network Slices that are configured so that they cannot be accessed simultaneously. + +NOTE: It is FFS whether solutions should address Network Slice exclusion aspects of all procedures that take place prior to the establishment of a PDU Session. + +**Editor's note:** This solutions focuses on the FS\_eNS Objective pertaining to "Identify, prioritize and study the practical non-roaming and roaming deployment scenarios and system impacts when the 5GS is not able to support all possible combination of S-NSSAIs for the UE". The solution addresses this aspect by providing Network Slice exclusion rules for all S-NSSIs from the Subscribed S-NSSAIs. In addition, this solution allows the enforcing of Network Slice exclusion rules for S-NSSAIs referring to Network Slices that cannot be accessed simultaneously, during a PDU Session Establishment procedure and Service Request procedure to prevent simultaneous use of Network Slices that are mutually exclusive but which S-NSSAI combination can still be supported by the 5GS. These rules may be configured at the AMF or NSSF + +The solution assumes during the SMF selection, that the NSSF (or AMF if configured accordingly) is configured to apply Network Slice exclusion rules. The application of relevant Network Slice exclusion rules will ensure that the UE only accesses slices that can be access simultaneously according to the Network Slice exclusion rules. If a UE, which requests access to a Network Slice that is mutually exclusive to slices that are already accessed, the Network (i.e., the AMF) will reject the request with an appropriate code. A UE may request access to Network Slices that are mutually exclusive e.g. due to USIM swap. + +##### 6.1.6.1.3 Network Slice Access Exclusion Rules + +Exclusion rules are configured in the subscriber record within the UDM on a per S-NSSAI basis. The exclusion rule can be either preconfigure in the UE or provided via the Registration procedure or Configuration Update procedure. The exclusion rules provided to the UE convey the following information on a per S-NSSAI basis: + +- 1) S-NSSAIs that are mutually exclusive to this S-NSSAI. This effectively yields combinations of S-NSSAI that can be accessed simultaneously. This combination can be configured or tagged as groups but the proposals does not mandate this. +- 2) Whether a mutually exclusive S-NSSAI can be used sequentially (if a two mutually exclusive S-NSSAI are included in the Allowed NSSAI, this indicates that two or more Network Slices can be sequentially used without the need to re-register as long as they are not accessed simultaneously. When no entries in the Allowed are mutually exclusive as per the provided exclusion rules, the UE can use all entries in the Allowed NSSAI simultaneously. + +NOTE: This proposal assumes that exclusion rules are provided as a separate information element (e.g., not necessarily part of the Configured NSSAI). Furthermore, the proposal does not mandate that non-mutually exclusive S-NSSAI be grouped but it does not precluded grouping. This is left to Stage 3 to decide. + +A S-NSSAI that is not defined/tagged as mutually exclusive to any other S-NSSAI can be used in simultaneously with any other S-NSSAI. If grouping were to be used this would correspond to the case where such an S-NSSAI would be part of all Non-Mutually Exclusive groups. Likewise, a S-NSSAI for which all other S-NSSAI have marked it as mutually exclusive, would correspond to a single S-NSSAI group. + +**Editor's note:** Need further clarification on the practicality of your proposal to justify the support for mutually exclusive access in Rel-16 5GS when a S-NSSAI that is not tagged. Per the descriptions above, it can be used simultaneously with any other S-NSSAI, especially such S-NSSAI is the one to be used by the Rel-15 UE. Does it imply that Rel-15 UE can actually get better services than the Rel-16 UE if it is capable of supporting mutually exclusive access? + +###### 6.1.6.1.3.1 Roaming Consideration + +Exclusion rules follow the same Rel-15 model with regards to roaming scenarios, whereby S-NSSAI information in the visited network is mapped to the Home counterpart. As such, exclusion rules from HPLMN are mapped to exclusion rules from VPLMN based on operators Service Level Agreement dictating the treatment of S-NSSAI information in the visited PLMNs. + +The use of Exclusion rules by the VPLMN specifying whether S-NSSAI can be used sequentially can be mapped to HPLMN rules. However local policies in the VPLMN may prohibit the use of S-NSSAI in the Allowed NSSI that are mutually exclusive. + +#### 6.1.6.2 High-level Description + +##### 6.1.6.2.1 Services and Illustrated Procedures + +###### 6.1.6.2.1.1 Registration Procedure + +![Sequence diagram of the Registration procedure showing interactions between UE, R(AN), New AMF, Old AMF, PCF, SMF, AUSF, and UDM.](2df09d249c38abee55dbf0526dd6da0a_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as R(AN) + participant NewAMF as New AMF + participant OldAMF as Old AMF + participant PCF + participant SMF + participant AUSF + participant UDM + participant EIR + participant N3IWF + + Note left of UE: 1. Registration Request + UE->>RAN: 1. Registration Request + Note right of RAN: 2. AMF Selection + RAN->>NewAMF: 3. Registration Request + Note right of NewAMF: 4. Namf_Communication_UEContextTransfer + NewAMF-->>OldAMF: 4. Namf_Communication_UEContextTransfer + Note right of OldAMF: 5. Namf_Communication_UEContextTransfer response + OldAMF-->>NewAMF: 5. Namf_Communication_UEContextTransfer response + Note right of NewAMF: 6. Identify Request + NewAMF-->>UE: 6. Identify Request + Note right of UE: 7. Identify Response + UE-->>NewAMF: 7. Identify Response + Note right of NewAMF: 8. Authentication + Note right of EIR: 9. Authentication/Security + Note right of AUSF: 10. Namf_Communication_RegistrationCompleteNotify + Note right of OldAMF: 11. Identify Request/Response + Note right of EIR: 12. N5g-eir_EquipmentIdentityCheck_Get + Note right of NewAMF: 13. UDM selection + Note right of UDM: 14a.Nudm_UECM_Registration + Note right of UDM: 14b.Nudm_SDM_Get + Note right of UDM: 14c.Nudm_SDM_Subscribe + Note right of NewAMF: 15. PCF selection + Note right of PCF: 14c.Nudm_UECM_DeregistrationNotify + Note right of UDM: 14d.Nudm_SDM_Unsubscribe + Note right of PCF: 16. Policy Association Establishment during Registration + Note right of PCF: 17. Namf_EventExposure_Subscribe + Note right of SMF: 18. Nsmf_PDUSession_UpdateSMContext/ +Nsmf_PDUSession_ReleaseSMContext + Note right of N3IWF: 19. N2 AMF Mobility Request + Note right of N3IWF: 20. N2 AMF Mobility Response + Note right of N3IWF: 21. N2 AMF Mobility Response + Note right of RAN: 22. Registration Accept (Allowed +NSSAI and Network Slice exclusion +rules) + RAN-->>UE: 22. Registration Accept (Allowed +NSSAI and Network Slice exclusion +rules) + Note right of UE: 23. Registration Complete + UE-->>NewAMF: 23. Registration Complete + +``` + +Sequence diagram of the Registration procedure showing interactions between UE, R(AN), New AMF, Old AMF, PCF, SMF, AUSF, and UDM. + +Figure 6.1.6.2.1-1: Registration procedure + +1-21. As per current specification. + +22. The Network (AMF if configured to do so or NSSF) derives the set of Network Slices that can and cannot be accessed simultaneously and/or the combination(s) of Network Slices that are not supported in the 5GS. + +If the Allowed NSSAI contains S-NSSAIs that may or may not be configured to be used simultaneously as specified in the exclusion rules, the UE then uses these Network Slice exclusion rules to determine what Network Slices can be accessed during a PDU Session Establishment of Service Request procedure. + +- NOTE 1: If the Network Slice Exclusion rules provided to the UE in the Registration Accept message do not indicate any Network Slice combination that cannot be used simultaneously, that means that all S-NSSAIs in the Allowed NSSAI correspond to Network Slices that the UE can access at any time. + +Network Slice Exclusion rules for Network Slices that cannot be accessed simultaneously (i.e. through the same AMF) apply to the S-NSSAIs within the Allowed NSSAI provided to the UE by the current AMF and they may also apply to S-NSSAIs entries in the Configured NSSAI, which the UE uses to construct a Requested NSSAI. + +In roaming scenarios, the use of exclusion rules by the VPLMN specifying whether S-NSSAI can be used sequentially can be mapped to HPLMN rules. However local policies in the VPLMN may prohibit the use of S-NSSAI in the Allowed NSSI that are mutually exclusive. + +If the UE wants to request access to Network Slices, corresponding to S-NSSAIs not present in the Allowed NSSAI, the UE applies Network Slice exclusion rules applicable to all S-NSSAIs included UE in the Configured NSSAI and UE re-registers without providing the 5G GUTI in the AS message. + +- NOTE 2: Similar to the derivation and construction of the Allowed NSSAI which is provided upon successful registration, a new set of Network Slice exclusion rules may also be provided at any time, e.g. upon a successful Registration procedure or through a UCU procedure. + +###### 6.1.6.2.1.2 Enforcement of mutually exclusive rules + +For the case when the Allowed NSSAI includes S-NSSAIs that are mutually exclusive, the following cases apply: + +- 1) The UE attempts to establish a PDU Session on a Network Slices that is mutually exclusive (clause 6.1.6.2.1.2.1 applies. + +- NOTE: If the NAS transaction is not network slice specific (e.g. Sending of SMS over NAS) the solution assumes that all slices are applicable for this this transaction. + +###### 6.1.6.2.1.2.1 PDU Establishment + +![Sequence diagram for PDU Establishment showing interactions between UE, R(AN), AMF, UPF, SMF, PCF, UDM, and DN. The diagram is divided into three horizontal sections: Step 0 (UE selects S-NSSAI), Step 1 (UE releases conflicting sessions), and Step 2 (UE establishes new session).](53f1f7d17b3e7aae62169c41d2a88a77_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as R(AN) + participant AMF + participant UPF + participant SMF + participant PCF + participant UDM + participant DN + + Note left of UE: 0. UE Selects S-NSSAI(s) where PDU Establishment is to be requested, considering exclusion rules + Note right of UE: 1. Based on exclusion rules, the UE may release PDU Sessions served by network slices that are mutually exclusive with the network slice where the PDU Session is to be established + Note right of UE: 2. The UE establishes a new PDU Session using S-NSSAI selected in step 0 + +``` + +Sequence diagram for PDU Establishment showing interactions between UE, R(AN), AMF, UPF, SMF, PCF, UDM, and DN. The diagram is divided into three horizontal sections: Step 0 (UE selects S-NSSAI), Step 1 (UE releases conflicting sessions), and Step 2 (UE establishes new session). + +**Figure 6.1.6.2.1.2-1: PDU Establishment** + +0. Based on the Allowed NSSAI, URSP/NSSP rules (e.g., Network Slice exclusion rules from VPLMN received during Registration procedure) and local configuration, the UE can select S-NSSAIs to form Allowed NSSAI request the establishment of a PDU Session, considering the S-NSSAI Network Slice exclusion rules from VPLMN. +1. If in Step 0 the UE chooses a S-NSSAI that cannot be used simultaneously (according to the Network Slice exclusion rules from VPLMN) with other S-NSSAI(s) where PDU Sessions are already established, the UE initiates a PDU Session Release procedure of those PDU Sessions selected in step 0. +2. The UE initiates a PDU Session Establishment procedure, providing the S-NSSAIs for PDU Session to be established selected in step 0. + +**Editor's note:** PDU Session Release has nothing to do with the NAS session connectivity over the N1. Need further clarification on how the network prevents the UE to access the other mutually exclusive slices simultaneously while the NAS (the control plane) remains active to communicate with all slices which are served by the same AMF. + +#### 6.1.6.3 Impacts on existing services and interfaces + +The AMF/NSSF may determine that set of rules the UE needs to follow when selecting slices that are mutually exclusive. The Network (the AMF) sends this rules during the Registration procedure or through a Configuration Update procedure. + +The AMF may invoke PDU Session Release operation (Nsmf\_PDUSession\_ReleaseSMContext) to release PDU Session on network slices that are mutually exclusive. + +**Editor's note:** PDU Session Release has nothing to do with the NAS session connectivity over the N1. Need further clarification on how the network prevents the UE to access the other mutually exclusive slices simultaneously while the NAS (the control plane) remains active to communicate with all slices which are served by the same AMF. + +**Editor's note:** Need further clarification on the impacts to specific functional elements + +#### 6.1.6.4 Evaluation + +### 6.1.7 Solution #1.7: Solutions for MEANS via Slicing Group Indication + +#### 6.1.7.1 Introduction + +This is a solution to Key Issue #1, "Mutually Exclusive Access to Network Slices" (MEANS). + +In this solution, each Network Slice is deployed to belonging to a Mutually Exclusive Access Network Slice Group (MEAG). Each Mutually Exclusive Access Network Slice Group represents a set of network slices which can share a common AMF. + +#### 6.1.7.2 Functional description + +##### 6.1.7.2.1 UE configuration + +The UE is configured with Configured NSSAI and MEAG IDs associated with each S-NSSAI from the Configured NSSAI. Figure 6.1.7.2.1-1 shows the UE configuration. Rel 15 UE not supporting MEANS feature can ignore the MEAG IDs and uses Configured NSSAI only when it generates Requested NSSAI. Rel 16 UE supporting MEANS feature can interpret MEAG IDs as well as Configured NSSAI and considers both information when it generates Requested NSSAI. + +![Diagram showing the configuration of S-NSSAIs and MEAG IDs for Rel-15 and Rel-16 UEs. The table lists five S-NSSAIs and their corresponding MEAG IDs. Below the table, a bracket labeled 'Rel-15 UE' spans the first four S-NSSAIs (S-NSSAI1 to S-NSSAI4), indicating that these are used by Rel-15 UEs. Another bracket labeled 'Rel-16 UE' spans all five S-NSSAIs (S-NSSAI1 to S-NSSAI5), indicating that these are used by Rel-16 UEs.](43fec6623ab9cb223a9ff74e2d2a4402_img.jpg) + +| Configured NSSAI | MEAG ID | +|------------------|---------| +| S-NSSAI1 | MEAG#1 | +| S-NSSAI2 | MEAG#1 | +| S-NSSAI3 | MEAG#2 | +| S-NSSAI4 | MEAG#2 | +| S-NSSAI5 | MEAG#3 | + +Diagram showing the configuration of S-NSSAIs and MEAG IDs for Rel-15 and Rel-16 UEs. The table lists five S-NSSAIs and their corresponding MEAG IDs. Below the table, a bracket labeled 'Rel-15 UE' spans the first four S-NSSAIs (S-NSSAI1 to S-NSSAI4), indicating that these are used by Rel-15 UEs. Another bracket labeled 'Rel-16 UE' spans all five S-NSSAIs (S-NSSAI1 to S-NSSAI5), indicating that these are used by Rel-16 UEs. + +Figure 6.1.7.2.1-1: S-NSSAI and MEAG associated with the S-NSSAI + +**Editor's note:** It is FFS whether a S-NSSAI including SD field in the S-NSSAI can belong to multiple MEAGs or not belong to any MEAG. + +##### 6.1.7.2.2 UE subscription + +The UE subscription in UDM also includes subscribed S-NSSAIs and MEAG IDs associated with each subscribed S-NSSAI. + +##### 6.1.7.2.3 Operations + +When a UE requests network slices during registration, the UE shall generate Requested NSSAI including S-NSSAIs only belonging to the same MEAG, i.e. not include S-NSSAIs belonging to different MEAGs. The UE also provides MEAG ID together with Requested NSSAI. The Allowed NSSAI provided to the UE during registration procedure shall not include S-NSSAIs from different MEAGs in Allowed NSSAI, together. + +5G CN may configure a UE with Configured NSSAI which includes S-NSSAI(s) with associated MEAG IDs during registration or update Configured NSSAI for the UE after registration at any time. Specifically in Registration Request, if UE does not include Requested NSSAI or UE includes S-NSSAIs from different MEAGs in Requested NSSAI, 5G CN should configure a UE with S-NSSAI(s) with associated MEAG IDs. + +When AMF is selected for supporting network slice, the selected AMF can be shared with other S-NSSAIs of same MEAG but not shared with other S-NSSAIs from different MEAGs. + +The Allowed NSSAI provided to the UE during registration procedure shall not include S-NSSAIs from different MEAGs together. + +When UE requests S-NSSAI different from MEAG which current active network slice is belonging to, UE shall deregister from current network slice, first. + +###### 6.1.7.2.3.1 Coexistence with Rel-15 UE + +Figure 6.1.7.2.3.1-1 shows MEANS deployment in a PLMN. The left side of the figure illustrates Rel-15 Network Slice deployments. In Rel-15 network, it is assumed that AMF can support all S-NSSAIs provided by the PLMN and requested by a UE. The right side of the figure illustrates Rel-16 Network Slice deployments with MEANS feature. The set of S-NSSAIs supported in the Rel 15 network on the left side of the figure is considered as one MEAG (i.e. Rel-15 MEAG) in Rel16 network because it seems not reasonable to say that the set of S-NSSAIs which can be supported at the same time in Rel 15 network becomes no longer supported at the same time in Rel 16 network. When a Rel-15 UE registers to a Rel.16 network, it will not include MEAG ID in Requested NSSAI and the gNB will select AMF based on the received Requested NSSAI. + +![Figure 6.1.7.2.3.1-1: MEANS deployment diagram showing the evolution from Rel-15 to Rel-16 network slice deployments.](0236eff05bcb8f3a343ea7933aaa306b_img.jpg) + +The diagram illustrates the deployment of MEANS (Multi-Access Edge Network Slice Aggregation) in a PLMN, showing the transition from Rel-15 to Rel-16 network slice deployments. The diagram is divided into two main sections: Rel-15 Network (left) and Rel-16 Network (right), with an arrow indicating an upgrade from Rel-15 to Rel-16. + +**Rel-15 Network (Left):** This section shows a Rel-15 UE connected to a gNB, which is connected to an AMF. The AMF is connected to two network slices, S-NSSAI#1 and S-NSSAI#2. Each slice contains a UPF and an SMF. The AMF is shown supporting both slices. + +**Rel-16 Network (Right):** This section shows the network after an upgrade. The Rel-15 UE is still connected to the gNB, which is connected to the AMF. The AMF is now connected to two MEAGs: MEAG #1 (Rel-15 MEAG) and MEAG #2. MEAG #1 contains S-NSSAI#1 and S-NSSAI#2, with their respective UPFs and SMFs. MEAG #2 contains S-NSSAI#3, which is not accessible for Rel-15 UEs. A Rel-16 UE is shown connected to the gNB, which is connected to the AMF. The AMF is shown supporting both MEAGs. + +Figure 6.1.7.2.3.1-1: MEANS deployment diagram showing the evolution from Rel-15 to Rel-16 network slice deployments. + +Figure 6.1.7.2.3.1-1: MEANS deployment + +##### 6.1.7.2.4 Roaming support + +When UE performs registration procedure in roaming, if it has neither Configured NSSAI nor Allowed NSSAI for the PLMN, it does not provide Requested NSSAI in the Registration Request. When a gNB in VPLMN receives a Registration Request without Requested NSSAI, it may select a default AMF for forwarding the Registration Request message. In this case, NSSF is assumed to provide Configured NSSAI and MEAG IDs associated with the S-NSSAI of the Configured NSSAI for the serving PLMN if Mutually Exclusive Access for network slices are supported; otherwise, only Configured NSSAI without MEAG ID is provided. When NSSF is not deployed, it is assumed that the selected default AMF is capable of providing Configured NSSAI and MEAG IDs associated with the S-NSSAI of the Configured NSSAI for the serving PLMN if Mutually Exclusive Access for network slices are supported; otherwise, only Configured NSSAI without MEAG ID is provided. + +When a default AMF receives Registration Request, it may determine the Configured NSSAI and/or the Allowed NSSAI which may include the associated MEAG ID(s) and the mapping information. When an AMF different from the default AMF is selected as a serving AMF, the default AMF may forward the Configured NSSAI, and mapping information and possible the MEAG IDs for the UE to the new serving AMF; alternately, the new serving AMF, which may be supported by NSSF, determines the Configured and/or the Allowed NSSAI that may include the associated MEAG ID(s) if Mutually Exclusive Access for network slices are supported. And the serving AMF provides the Configured and/or the Allowed NSSAI, the mapping information and possible the MEAG IDs to the UE in the Registration Accept. + +For roaming case, Serving PLMN may provide Configured NSSAI including associated MEAG ID per included S-NSSAI for roamer UE and mapping of each S-NSSAI in the Configured NSSAI in Serving PLMN to corresponding S-NSSAI(s) values for the HPLMN. + +When Serving PLMN provides Configured NSSAI including MEAG ID for each S-NSSAI, it shall be kept that S-NSSAIs belonging to corresponding MEAGs in HPLMN. + +When UE supporting MEANS roams to the network not supporting MEANS (e.g. Rel-15), the UE will be aware of the serving network not supporting MEANS based on capability negotiation during registration and the UE will be + +configured only with NSSAIs without MEAG. When the UE compose Requested NSSAI based on Configured NSSAI, the UE shall include NSSAIs belonging to the same MEAG which was assigned in HPLMN. + +#### 6.1.7.3 Procedures + +##### 6.1.7.3.1 RAN configuration + +NG setup procedure between gNB and AMF is specified in clause 16.4.3 of TS 38.300 [5]. The gNB and the AMF exchange the list of supported S-NSSAIs. In addition to clause 16.4.3 of TS 38.300 [5], the AMF provides to the RAN the MEAG ID along with the list of supported S-NSSAIs as shown in Figure 6.1.7.3.1-1. + +![Sequence diagram of the RAN configuration procedure between RAN and AMF.](07b17a620c75522d53916a11e12d1bff_img.jpg) + +``` +sequenceDiagram + participant RAN + participant AMF + Note right of AMF: 2. Store the list of S-NSSAIs supported by RAN + RAN->>AMF: 1. Connection Setup Request (List of supported S-NSSAIs) + AMF-->>RAN: 3. Connection Setup Response (MEAG ID, List of supported S-NSSAIs) + Note left of RAN: 4. Store MEAG ID and the list of S-NSSAIs supported by AMF +``` + +The diagram illustrates the RAN configuration procedure between the RAN and the AMF. It consists of four steps: 1. The RAN sends a Connection Setup Request (List of supported S-NSSAIs) to the AMF. 2. The AMF stores the list of S-NSSAIs supported by the RAN. 3. The AMF sends a Connection Setup Response (MEAG ID, List of supported S-NSSAIs) to the RAN. 4. The RAN stores the MEAG ID and the list of S-NSSAIs supported by the AMF. + +Sequence diagram of the RAN configuration procedure between RAN and AMF. + +Figure 6.1.7.3.1-1: RAN configuration procedure + +##### 6.1.7.3.2 Registration procedure + +Figure 6.1.7.3.2-1 shows a Registration procedure. + +Error! No + +9 + +Error! No text of specified style in + +![Sequence diagram of the Registration procedure. Lifelines: UE, RAN, AMF, NSSF, UDM. The process involves: 1. UE generates Requested NSSAI; 2. UE sends Registration Request to RAN; 3. RAN selects AMF; 4. RAN sends Registration Request to AMF; 5. AMF performs subscription check; 6. AMF may reallocate within the same slice group; 7. AMF sends Registration Accept to RAN; 8. RAN sends Registration Accept to UE.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant AMF + participant NSSF + participant UDM + + Note left of UE: 1. generate Requested NSSAI based on Configured NSSAI with MEAG IDs + UE->>RAN: 2. Registration Request (MEAG ID, Requested NSSAI) + Note right of RAN: 3. select AMF based on Requested NSSAI and the MEAG ID + RAN->>AMF: 4. Registration Request (MEAG ID, Requested NSSAI) + Note over AMF, NSSF, UDM: 5. Subscription check + Note over AMF, NSSF: 6. AMF reallocation within the same Slice Group + AMF->>RAN: 7. Registration Accept (Allowed NSSAI, Configured NSSAI with MEAG IDs) + RAN->>UE: 8. Registration Accept (Allowed NSSAI, Configured NSSAI with MEAG IDs) + +``` + +Sequence diagram of the Registration procedure. Lifelines: UE, RAN, AMF, NSSF, UDM. The process involves: 1. UE generates Requested NSSAI; 2. UE sends Registration Request to RAN; 3. RAN selects AMF; 4. RAN sends Registration Request to AMF; 5. AMF performs subscription check; 6. AMF may reallocate within the same slice group; 7. AMF sends Registration Accept to RAN; 8. RAN sends Registration Accept to UE. + +**Figure 6.1.7.3.2-1: Registration procedure** + +The Registration procedure is performed as defined in TS 23.502 [3] with the following additions: + +1. The UE generates Requested NSSAI including S-NSSAIs only within the same MEAG ID. The Slice Group ID is also included along with the Requested NSSAI in Registration Request message. + +3. The RAN selects AMF based on Requested NSSAI as specified in TS 23.502 [3]. If the RAN is not able to find an AMF which can support all S-NSSAIs in the Requested NSSAI, then it forwards the message to an AMF belonging to the requested MEAG ID. + +6. AMF reallocation may happen within the same slice group. + +The AMF or NSSF may verify whether all S-NSSAIs in the Requested NSSAI are correctly associated with the same MEAG ID. If some of the S-NSSAIs in the Requested NSSAI are not belonging to the same MEAG ID, then AMF or NSSF considers that the UE configuration is not up-to-date and triggers UE configuration update. + +7. If UE configuration update is required as described in step 6, the Registration Accept message includes Configured NSSAI and the associated MEAG IDs. + +#### 6.1.7.4 Impacts on existing entities and interfaces + +To support MEANS, below are the impacted entities and interfaces listed: + +- Support for UE generating Requested NSSAI within a same slice group and providing MEAG ID in Registration Request. +- Support for RAN selecting AMF based on MEAG ID. +- Support for AMF triggering UE configuration update by verifying the Requested NSSAI against the MEAG ID. + +- Support for NSSF reallocating AMF within a same slice group. + +Impacted interfaces: N1, N2. + +#### 6.1.7.5 Evaluation + +### 6.1.8 Solution #1.8: Solution to Key issue#1: Access to new group of Network Slices. + +#### 6.1.8.1 Introduction + +There are several solutions in the TR addressing the key issue#1. Most solution in some way provides the UE with information about which MEANS (different names in the different solutions) group a Network Slice belongs to. + +#### 6.1.8.2 Functional description + +In Rel-15 a UE likely will simply try to add another S-NSSAI from the Configured NSSAI while the UE is in CM-CONNECTED or from CM-IDLE while still indicating the valid GUAMI. However, MEANS seems to drive the need for the UE to access the network again from CM-IDLE without indicating GUAMI from old registration as to allow the 5G-AN to select 5GC based on Requested NSSAI. The other option would be to allow re-allocation to new slices while the UE is in state CM-CONNECTED which is not yet fully functional. The FS\_ETSUN study may solve it (or other studies), but it seems uncertain whether that will be enabled in Rel-16. Independent if it is enabled by FS\_ETSUN, it is not certain that such functionality will be possible to use for moving a UE between MEANS groups e.g. in case isolation between MEANS groups is required. + +However, as to not requiring the UEs to go through CM-IDLE when re-allocation of slices are possible while in CM-CONNECTED it is proposed that the network should be able to indicate whether the UE shall request access to other MEANS group from CM-IDLE without indicating GUAMI or 5G-S-TMSI in 5G-AN signalling (i.e. to trigger the 5G-AN to do the selection) or whether UE can request it while in CM-CONNECTED (i.e. as 5GS will enable re-allocation even if e.g. PDU Session for another MEANS group is established). The indication is either provided together with information about the MEANS groups provided to the UE (i.e. see each solution for the key issue#1), or the indication can be sent by the AMF separately. If sent separately the information could be to which MEANS group(s) the UE may use the more efficient change while being connected to the current AMF i.e. while in CM-CONNECTED. + +Such indication can be used together with any of the existing solutions in the TR i.e. it should be seen as an add on (complement) to any available solution (unless the specific solution explicitly addresses the issue). + +#### 6.1.8.3 Procedures + +The procedure for the main adopted solution applies, and together with that adopted solution additional information/indication can be sent as whether the MEANS group can or shall be accessed while in CM-IDLE without indicating GUAMI or 5G-S-TMSI in 5G-AN signalling. + +As an option or additional enhancement, the network, e.g. AMF, may indicate to which MEANS groups the UE can use the more efficient re-allocation while staying in CM-CONNECTED for the current Registration (Allowed NSSAI). The network, e.g. AMF, may provide such information as part of the Registration Accept message or as part of UE Configuration Update procedure. + +#### 6.1.8.4 Impacts on existing entities and interfaces + +- UE: Impacts as per main solution to be adopted by the study, and in addition receiving indication whether an S-NSSAI or group of network slices supports being accessed via CM-CONNECTED (or UE needs to do it from CM-IDLE without indicating GUAMI/5G-S-TMSI in 5G-AN signalling). +- Network: Impacts as per main solution to be adopted by the study and in addition sending to the UE an indication or information whether an S-NSSAI or group of network slices (MEANS group) supports being accessed via CM-CONNECTED (or UE needs to do it from CM-IDLE without indicating GUAMI/5G-S-TMSI in 5G-AN signalling). + +#### 6.1.8.5 Evaluation + +This solution is complementing any of the existing solutions in the TR. The solution enables the UE to know whether an efficient re-allocation/change of Network Slices (e.g. changing the Requested NSSAI compared to Allowed NSSAI by e.g. adding more S-NSSAIs from the Configured NSSAI) or MEANS group can be enabled while the UE is in CM-CONNECTED or whether the UE has to go through CM-IDLE state. + +## 6.2 Solutions for KI#2 + +### 6.2.1 Solution#2.1: Network slice instance selection in initial AMF + +#### 6.2.1.1 Introduction + +This solution address the key issue#2: Enabling interworking for slicing between EPC and 5GC. + +#### 6.2.1.2 Functional description + +The PGW-C+SMF knows the S-NSSAI or each PDN connection. In connected mode, Initial AMF uses the Nsmf\_PDUSessionCreateSMContext service operation with the PGW-C+SMF that returns the S-NSSAI and PDU Session ID to the Initial AMF selected by the source MME. Then the Initial AMF determines the set of network slices supported for the UE, and, if required, selects the Target AMF and forward the handover message to the target AMF . The rest are same procedure as normal EPS to 5GS handover procedure using N26 interface. + +For IDLE mode mobility from EPS to 5GS using N26 interface, the Target AMF uses the Nsmf\_PDUSessionCreateSMContext service operation with the PGW-C+SMF to retrieve the S-NSSAI of the transferred PDU Connection. The S-NSSAI of the PDU session returned by PGW-C+SMF is used to select a correct V-SMF as described in clause 4.11.1.3.3 of TS 23.502 [3]. + +NOTE 1: This solution uses existing solution in Release 15 to correlate the EBI and S-NSSAI of the PDU session as described in clause 4.11.1.2.2 and clause 4.11.1.3.3 in TS 23.502 [3]. The AMF sends UE EPS PDN Connection received from MME to SMF and the SMF return the EBI information and the S-NSSAI of the PDU session. + +#### 6.2.1.3 EPS to 5GS handover Procedures + +![Sequence diagram of EPS to 5GS handover using N26 interface. The diagram shows the interaction between UE, eNodeB, 5G-AN, MME, Initial AMF, Target AMF, V-SMF1, V-UPF1, V-SMF2, V-UPF2, PGW-C+SMF, and PGW-U+UPF. The process starts with UE establishing a PDU connection in 4G EPC (step 1). The handover is triggered by eNodeB (step 2), followed by a Relocation Request from MME to Initial AMF (step 3). The Initial AMF sends a Nsmf_PDUSession_CreateSMContext Request to V-SMF1 (step 4). V-SMF1 performs N4 Session Establishment with V-UPF1 (step 5) and N4 Session modification with PGW-C+SMF (step 6). V-SMF1 sends a response to Initial AMF (step 7). Initial AMF performs network slice selection (step 8) and sends a Namf_Communication_CreateUEContext Request to Target AMF (step 9). Target AMF sends a Nsmf_PDUSession_CreateSMContext Request to V-SMF2 (step 10). V-SMF2 performs N4 Session Establishment with V-UPF2 (step 11) and sends a response to Target AMF (step 12). Target AMF sends a Handover Request to 5G-AN (step 13). 5G-AN sends a Handover Request ACK to Target AMF (step 14). Target AMF sends a Nsmf_PDUSession_UpdateSMContext Request to V-SMF2 (step 15). V-SMF2 performs N4 Session modification with V-UPF2 (step 16) and sends a response to Target AMF (step 17). Target AMF sends a Namf_Communication_CreateUEContext Response to Initial AMF (step 18). Initial AMF performs UE context removal in initial AMF and V-SMF1/V-UPF1 (step 19). Initial AMF sends a Forward Relocation Response to MME (step 20). MME sends a Handover Command to eNodeB (step 21). eNodeB sends a Handover Command to UE (step 22). UE sends a Handover to 5G-RAN Confirm to eNodeB (step 23). eNodeB sends a Handover Notify to 5G-AN (step 24). 5G-AN sends a Forward Relocation Complete notification to Target AMF (step 25). Target AMF sends a Forward Relocation Complete notification ACK to 5G-AN (step 26). Target AMF sends a Nsmf_PDUSession_UpdateSMContext Request to V-SMF2 (step 27). V-SMF2 performs N4 Session modification with V-UPF2 (step 28) and sends a response to Target AMF (step 29). Target AMF performs EPS to 5GS Registration procedure (step 30). MME performs Resource cleanup in EPC (step 31).](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) + +Sequence diagram of EPS to 5GS handover using N26 interface. The diagram shows the interaction between UE, eNodeB, 5G-AN, MME, Initial AMF, Target AMF, V-SMF1, V-UPF1, V-SMF2, V-UPF2, PGW-C+SMF, and PGW-U+UPF. The process starts with UE establishing a PDU connection in 4G EPC (step 1). The handover is triggered by eNodeB (step 2), followed by a Relocation Request from MME to Initial AMF (step 3). The Initial AMF sends a Nsmf\_PDUSession\_CreateSMContext Request to V-SMF1 (step 4). V-SMF1 performs N4 Session Establishment with V-UPF1 (step 5) and N4 Session modification with PGW-C+SMF (step 6). V-SMF1 sends a response to Initial AMF (step 7). Initial AMF performs network slice selection (step 8) and sends a Namf\_Communication\_CreateUEContext Request to Target AMF (step 9). Target AMF sends a Nsmf\_PDUSession\_CreateSMContext Request to V-SMF2 (step 10). V-SMF2 performs N4 Session Establishment with V-UPF2 (step 11) and sends a response to Target AMF (step 12). Target AMF sends a Handover Request to 5G-AN (step 13). 5G-AN sends a Handover Request ACK to Target AMF (step 14). Target AMF sends a Nsmf\_PDUSession\_UpdateSMContext Request to V-SMF2 (step 15). V-SMF2 performs N4 Session modification with V-UPF2 (step 16) and sends a response to Target AMF (step 17). Target AMF sends a Namf\_Communication\_CreateUEContext Response to Initial AMF (step 18). Initial AMF performs UE context removal in initial AMF and V-SMF1/V-UPF1 (step 19). Initial AMF sends a Forward Relocation Response to MME (step 20). MME sends a Handover Command to eNodeB (step 21). eNodeB sends a Handover Command to UE (step 22). UE sends a Handover to 5G-RAN Confirm to eNodeB (step 23). eNodeB sends a Handover Notify to 5G-AN (step 24). 5G-AN sends a Forward Relocation Complete notification to Target AMF (step 25). Target AMF sends a Forward Relocation Complete notification ACK to 5G-AN (step 26). Target AMF sends a Nsmf\_PDUSession\_UpdateSMContext Request to V-SMF2 (step 27). V-SMF2 performs N4 Session modification with V-UPF2 (step 28) and sends a response to Target AMF (step 29). Target AMF performs EPS to 5GS Registration procedure (step 30). MME performs Resource cleanup in EPC (step 31). + +**Figure-6.2.1.3-1: EPS to 5GS handover using N26 interface** + +1. Step 1 to step 6 are same as normal EPS to 5GS handover using N26 interface. + +**Editor's note:** Step 4 must be aligned with TS 23.502 [3] to use **CreateSMContext**. + +7. The SMF + PGW-C sends a **Nsmf\_PDUSessionCreateSMContext Response** (PDU Session ID, N2 SM Information (PDU Session ID, QoS Rules, EPS Bearer Setup List, H-CN Tunnel-Info, S-NSSAI), S-NSSAI) to the initial AMF. SMF includes mapping between QoS flows and EPS bearers as part of N2 SM Information container. +8. The Initial AMF performs network slice instance selection and the target AMF based on the S-NSSAI received in step 7. + +In home-routed roaming case, if the VPLMN and HPLMN have an SLA to support non-standard S-NSSAI values in the VPLMN, the Initial AMF uses the NSSF of the VPLMN to map the S-NSSAI values to the respective S-NSSAI values to be used in the VPLMN. + +9. The Initial AMF sends **Namf\_Communication\_CreateUEContext** service operation (Target 5GAN Node ID, Source to Target Transparent Container, EPS MM Context, EPS Bearer Context(s), N2 SM Information received in step 7, S-NSSAI received in step 7) message to the target AMF. Based on the S-NSSAI the target AMF may + +reselect a new V-SMF2. In case of no change of V-SMF, step 10-12 are skipped and in step 13 the target AMF uses the N2 SM Information received in step 7. + +10. If the Target AMF reselects a new V-SMF2, it sends Nsmf\_PDUSessionCreateSMContext Request(UE EPS PDN Connection, N2 SM Information) to V-SMF2. +- 11-12. The V-SMF2 establishes the N4 session with V-UPF2. The V-UPF2 allocates CN tunnel information. The V-SMF2 updates N2 SM Information with the S-NSSAI and the CN tunnel information of V-UPF2. The V-SMF2 then sends Nsmf\_PDUSessionCreateSMContext Response (PDU Session ID, N2 SM Information) towards target AMF. +- 13-31. Step 13 to step 31 are same procedure as normal EPS to 5GS handover procedure using N26 interface in clause 4.11.1.2.2 of TS 23.502 [3]. In additional, in step 19, the initial AMF initiates resource release of V-SMF1 and V-UPF. The Forward Relocation Complete notification message is relayed by an initial AMF in case that the target AMF does not support N26 interface. + +#### 6.2.1.4 Impacts on existing entities and interfaces + +No impact on EPC. + +No impacts on UE. + +In connected mode, the Initial AMF selects the target network slice instance and the target AMF based on the S-NSSAI received from the PGW-C+SMF. Then it sends the Namf\_Communication\_CreateUEContext service operation with the EPS MM Context , EPS Bearer Context(s) and the N2 SM Info received from V-SMF1 to target AMF. The initial AMF removes the resources in V-SMF1 and V-UPF1 after the UE context has been transferred to target AMF. + +The target AMF sends N2 SM Info received from initial AMF to V-SMF2 if new V-SMF2 is selected. + +The V-SMF2 updates the N2 SM Info received from target AMF with S-NSSAI and CN tunnel information of V-UPF2 and sends the new N2 SM Info to the 5G-AN. + +#### 6.2.1.5 Evaluation + +This solution is based on Rel-15 solution and can provide slicing interworking between EPC and 5GC for both Rel-15 UE and Rel-16 UE. This solution has no impact on the PGW-C+SMF, therefore it can also work for roaming case when the PGW-C+SMF is Rel-15. + +Additional enhancement (i.e. network slicing selection) is introduced in handover preparation phase which may add more handover latency. However the additional enhancement is within the VPLMN, i.e. no need for interaction across PLMNs. + +The solution requires Rel-16 AMF and Rel-16 V-SMF. + +### 6.2.2 Solution #2.2: Slice-aware mobility from EPC to 5GC + +#### 6.2.2.1 Introduction + +The solution addresses key issue number 2. + +#### 6.2.2.2 Functional description + +For mobility from EPC to 5GC, IDLE mode and CONNECTED mode mobility are addressed separately. + +##### 6.2.2.2.1 Idle Mode Mobility from EPC to 5GC + +The SM context in the EPC that is provided to the 5GC in case of mobility from EPC to 5GC does not contain any slicing information. This applies regardless if the UE initially registers and establishes connectivity in 5GC and then moves to EPC, or the UE initially registers and establishes connectivity in EPC. + +As a result, when the UE moves to the 5GC from EPC, the AMF will have no information about the slice (identified by S-NSSAI) associated the UE's PDN connections moved from EPC. Consequently, the AMF will also not be able to verify whether the AMF selected during the mobility from EPC to 5GC is appropriate for the slices that the UE is connected to for its active PDU sessions. + +To address this scenario, a solution is proposed based on the following. + +###### 6.2.2.2.1.1 Usage of slice mapping information for single-registration mode UEs + +The solution uses the mapping of slices to PDN Connections. The UE determines the slice mapping per current release 15 mechanisms: + +- For PDU sessions originally established over 5GC (i.e. before the UE has moved to EPC) the UE applied NSSP to determine S-NSSAI and DNN. When moving to EPC, the UE locally keeps the S-NSSAI information for those PDU sessions moved from 5GC. +- For PDN connections established over EPC, during PDN connection establishment in the EPC, the UE is provided by the PGW-C+SMF via PCO the S-NSSAI associated with the PDN connection, together with a PLMN ID that the S-NSSAI relates to. The UE stores this S-NSSAI and the PLMN ID associated with the PDN connection. + +When moving from EPC to 5GC, for each PDU session single-registration mode UEs provide the AMF with slice mapping information containing the S-NSSAIs associated to the PDU Sessions active in the UE, together with the EPS bearer identity of the default EPS bearer corresponding to the PDN connection. The UE sends the slice mapping information in the Registration request when mobility from EPC to 5GC mobility happens. + +The UE sends the slice mapping information and in the roaming case: + +- In the AMF: When the AMF receives the slice mapping information from the UE in the Registration request, the AMF maps S-NSSAIs sent by the UE to S-NSSAIs for the Serving PLMN. AMF selects V-SMFs and V-UPFs based on slice mapping information (instead of default V-SMFs / default V-UPFs as in Rel-15). +- In the UE: When the UE receives the Configured NSSAI for the Serving PLMN (which includes the S-NSSAI values which can be used in the Serving PLMN and a mapping to the corresponding S-NSSAI values in the Configured NSSAI for the HPLMN) in the Registration Accept from the AMF, the UE updates the S-NSSAIs locally stored for sessions created in EPC to reflect the correct S-NSSAI for the current PLMN. + +##### 6.2.2.2.2 Connected Mode Mobility from EPC to 5GC + +Selecting the target AMF, and by that a set of network slices, based on information available at the source MME introduces a risk that the UE gets served by an AMF that is not appropriate and possibly by network slice(s) that are not in the UE's subscription. Even though this is corrected by a subsequent Registration procedure, if network slice isolation is supported it gets violated, and there may be service interruption for the UE. It is necessary to select an AMF that supports the network slices (S-NSSAI) associated to the UE's PDN connections and allowed by the UE's subscription. This requires information on the UE's subscribed S-NSSAIs, and network slices (S-NSSAI) associated to the UE's PDN connections which the MME does not have. + +It is therefore proposed that: + +- for each active PDN connection the UE associates an S-NSSAI with the EPS Bearer ID for the default bearer of the PDN connection. The UE then sends to the serving MME a transparent handover container comprising, for each PDN connection, the EPS Bearer ID for the default bearer of the PDN connection (which identifies the PDN connection) and the associated S-NSSAI per each created PDN connection. The UE sends the information to the MME during an Attach procedure, if PDN connections were established in the 5GS, Tracking Area Update procedures, and upon establishment of a PDN connection in the EPS. +- At handover from EPS to a 5GS network, the source MME select an AMF based on current mechanisms and ensuring the selected AMF is capable of performing AMF selection (e.g. based on appropriate DNS configuration). The MME provides the transparent handover container to the AMF selected by the MME. The AMF selected by the MME, together with the NSSF, selects a target AMF and forwards the signalling from the source MME to the target AMF. The target AMF is selected considering the S-NSSAIs associated to PDN connections that are in the transparent handover container. The UE does not get registered in the AMF selected by the MME, but only by the target AMF. The target AMF selects V-SMFs and V-UPFs based on slice mapping information provided by the MME (instead of default V-SMFs / default V-UPFs as in Rel-15). + +#### 6.2.2.3 Procedures + +#### 6.2.2.4 Impacts on existing entities and interfaces + +Impacts on EPC: MME must be enhanced to support the transfer of transparent handover container from UE in EPC Attach and Tracking Area Update procedures. The MME must be enhanced to store the transparent handover container to the UE context and update the container whenever updated by the UE. The MME must be enhanced to support the transfer of transparent handover container in S10 interface to the Target MME or Initial AMF. + +Impacts on UE: The UE must be enhanced to include the association of default EPS Bearer ID and S-NSSAI in transparent handover container in EPC Attach and Tracking Area Update request. The UE must send the updated transparent handover container in Tracking Area Update request to MME whenever a new PDN connection has been established, or the old one has been released. The UE must be enhanced to include the association of default EPS Bearer ID and S-NSSAI in Registration Request. + +The AMF must be enhanced to support the reception of S-NSSAI and default EPS Bearer ID from MME (connected mode) and from UE (idle-mode). The Initial/Target AMF uses the default EPS Bearer ID to map the S-NSSAI to the PDN Connection(s) received from the MME. + +#### 6.2.2.5 Evaluation + +The proposed solution supports deployments with and without Decor/eDecor. + +The solution requires Rel-16 UE, Rel-16 MME and Rel-16 AMF. + +### 6.2.3 Solution #2.3: Inter RAT mobility Slice support + +#### 6.2.3.1 Introduction + +The solution solves the key issue #2, especially on the below item: + +- Selecting an AMF based on the slices associated to the active PDN connections the UE has in the EPC. +- Selecting an appropriate V-SMF based on the slices associated to the active PDN connections the UE has in the EPC. + +#### 6.2.3.2 Functional description + +##### **AMF/V-SMF selection during CONNECTED state mobility:** + +An interim AMF is selected by MME during handover phase as in Rel-15. The interim AMF/SMF can connect to all possible slices that support interworking with EPS. After handover is completed, the UE initiates the registration procedure. The interim AMF selects the final AMF based on S-NSSAI of established PDN connections. And the AMF is relocated during the registration procedure if it is needed. + +The interim AMF gets the S-NSSAI of serving PLMN of established PDN connection either from PGW-C during handover procedure (LBO or non Roaming case), or from UE in registration request (HR case). For home routed roaming case, if the AMF is not provided with S-NSSAI of VPLMN by the UE, based on received S-NSSAI of HPLMN from PGW-C+SMF, the AMF determines the S-NSSAI of VPLMN itself via local mapping information exist or NSSF. + +The registration procedure needs to be enhanced to support AMF relocation as well as V-SMF change in CM-CONNECTED state. + +##### **AMF selection during IDLE state mobility:** + +In idle mobility, the UE has S-NSSAI and the associated PLMN of established PDN connections sent by the PGW-C+SMF. In local breakout roaming case or non-roaming case, i.e. the associated PLMN is the serving PLMN, the UE can include the S-NSSAI of established PDN connections in RRC message. 5G AN selects correct AMF based on the S-NSSAI of established PDN connections in RRC message. + +In case the PDN connection is home routed, i.e. the associated PLMN is the home PLMN, the S-NSSAI provided by PGW-C to UE is S-NSSAI in HPLMN. In this case, UE sends the S-NSSAI in HPLMN to AMF in NAS. The AMF determine the corresponding S-NSSAI in VPLMN, e.g. via local provision mapping information or query from NSSF, and select a final AMF, which may be different from the one selected by 5G AN, based on the S-NSSAI (in VPLMN) of established PDN connections. + +##### **V-SMF selection during IDLE state mobility:** + +With N26 case: + +The UE includes the S-NSSAI of corresponding PDN connection together with default EBI into registration request. The Context retrieved from MME includes default EBI. Thus, the AMF can correlate the S-NSSAI with corresponding PDN connection. + +For home routed roaming case, the UE provides the S-NSSAI of HPLMN to AMF in NAS and the AMF determines the S-NSSAI of VPLMN, e.g. via local provision information or NSSF. + +The AMF selects the V-SMF(s) based on the S-NSSAI(s) of the VPLMN associated with the established PDN connection(s). + +Without N26 case: + +The UE includes HPLMN value of S-NSSAI(s) associated to the PDU Session ID of each established PDN connection(s) in registration request. The AMF determines its corresponding VPLMN value of the S-NSSAI, e.g. via NSSF or local provision information. In Registration Accept message, the AMF includes the VPLMN value of the S-NSSAI(s) associated to PDU Session ID of each established PDU Session(s) in the message. Hence, UE knows VPLMN value of S-NSSAI associated to each established PDU Session, and can include S-NSSAI in PDU Session Establishment Request. The AMF selects V-SMF based on S-NSSAI received in PDU Session Establishment Request. + +#### 6.2.3.3 Procedures + +##### 6.2.3.3.1 Registration with AMF and V-SMF change during CONNECTED state mobility + +![Sequence diagram for AMF/V-SMF relocation during registration procedure when UE is in CM-CONNECTED state. The diagram shows interactions between UE, gNB, Interim AMF, Final AMF, Interim V-SMF, Interim V-UPF, Final V-SMF, Final V-UPF, PGW-C +SMF, PGW-U +UPF, UDM, and NSSF. The process involves registration request, slice selection, AMF selection, session context transfer, and session modification.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant gNB + participant Interim AMF + participant Final AMF + participant Interim V-SMF + participant Interim V-UPF + participant Final V-SMF + participant Final V-UPF + participant PGW-C +SMF + participant PGW-U +UPF + participant UDM + participant NSSF + + Note left of UE: 1. Registration Request (Requested NSSAI) + UE->>gNB: 1. Registration Request (Requested NSSAI) + gNB-->>Interim AMF: 1. Registration Request (Requested NSSAI) + Interim AMF->>Interim V-SMF: 2. Nudm_SDM_Get(Slice Selection Subscription data) + Interim V-SMF->>UDM: 2. Nudm_SDM_Get(Slice Selection Subscription data) + UDM-->>Interim V-SMF: 2. Nudm_SDM_Get(Slice Selection Subscription data) + Interim V-SMF->>NSSF: 3. Nnsf_NSSelection_Get + NSSF-->>Interim V-SMF: 3. Nnsf_NSSelection_Get + Interim V-SMF->>Interim AMF: 4. Namf_Communication_N1MessageNotify + Interim AMF-->>Final AMF: 4. Namf_Communication_N1MessageNotify + Note right of Final AMF: 5. TS23.502 Steps 4-16 of figure 4.2.2.2.2-1 or Steps 8-16 of figure 4.2.2.2.2-1 without performing step 10 + Note left of Final AMF: 6. V-SMF Selection + Final AMF->>Final V-SMF: 7. Nsmf_PDUSession_CreateSMContext Request + Final V-SMF->>Interim V-SMF: 8. Retrieve PDU Session Context + Interim V-SMF-->>Final V-SMF: 8. Retrieve PDU Session Context + Final V-SMF->>Final V-UPF: 9. N4 Session Establishment + Final V-UPF-->>Final V-SMF: 9. N4 Session Establishment + Final V-SMF-->>Final AMF: 10. Nsmf_PDUSession_CreateSMContext Response + Final AMF->>Interim AMF: 11. Namf_Communication_N1N2MessageTransfer(SM N2 Request) + Interim AMF-->>gNB: 12. SM N2(Target UPF tunnel) + gNB-->>Final AMF: 13. SM N2 Response + Note right of gNB: Uplink Packet + gNB-->>Final V-UPF: Uplink Packet + Note left of Final AMF: 14. Nsmf_PDUSession_UpdateSMContext Request + Final AMF->>Final V-SMF: 14. Nsmf_PDUSession_UpdateSMContext Request + Final V-SMF->>PGW-C +SMF: 15. Nsmf_PDUSession_Update Request (Target UPF tunnel) + PGW-C +SMF-->>Final V-UPF: 16. N4 session modification + Final V-UPF-->>PGW-C +SMF: 16. N4 session modification + Note right of gNB: End Marker + gNB-->>Interim V-UPF: End Marker + Note right of gNB: Downlink Packet + gNB-->>Final V-UPF: Downlink Packet + Final V-SMF-->>Final AMF: 17. Nsmf_PDUSession_Update Response + Final AMF-->>Interim AMF: 18. Nsmf_PDUSession_CreateSMContext Response + Note right of Final AMF: 19. Steps 18-20 of figure 4.2.2.2.2-1 + Note left of UE: 20. Registration Accept + Final AMF-->>UE: 20. Registration Accept + Final AMF->>Interim AMF: 21. Namf_Communication_RegistrationCompleteNotify + Interim AMF-->>Final AMF: 21. Namf_Communication_RegistrationCompleteNotify + Final AMF->>Interim V-SMF: 22. Nsmf_PDUSession_DeleteSMContext Request + Interim V-SMF-->>Final V-SMF: 23. N4 Session Release + Final V-SMF-->>Interim V-SMF: 23. N4 Session Release + Final AMF-->>Interim AMF: 24. Nsmf_PDUSession_DeleteSMContext Response + +``` + +Sequence diagram for AMF/V-SMF relocation during registration procedure when UE is in CM-CONNECTED state. The diagram shows interactions between UE, gNB, Interim AMF, Final AMF, Interim V-SMF, Interim V-UPF, Final V-SMF, Final V-UPF, PGW-C +SMF, PGW-U +UPF, UDM, and NSSF. The process involves registration request, slice selection, AMF selection, session context transfer, and session modification. + +**Figure 6.2.3.3.1-1: AMF/V-SMF relocation during registration procedure when UE is in CM-CONNECTED state** + +1. UE sends Registration request to the interim AMF. The UE includes HPLMN value of S-NSSAI(s) associated with established PDN connection(s) and its corresponding default EBI in Registration request. This is for the case that the UE get the S-NSSAI from the HPLMN and not able to map it to the S-NSSAI of VPLMN. +3. A final AMF is selected by interim AMF based on subscribed S-NSSAI(s), S-NSSAI(s) associated with established PDN connection(s) which can be the S-NSSAI of HPLMN, and UE requested NSSAI. The interim AMF may query NSSF or based on the local provision mapping information for Allowed S-NSSAI determination. If the interim AMF is not provided with VPLMN value of S-NSSAI(s) associated with established PDN connection(s) by the UE, the interim AMF provides the HPLMN value of S-NSSAI(s) + +associated with established PDN connection(s) to NSSF, and NSSF will provide its corresponding VPLMN value to the interim AMF in response. + +4. The interim AMF forwards the registration request to final AMF as in step 7a of figure 4.2.2.2.3-1 in clause 4.2.2.2.3 of TS 23.502 [3], with the following enhancement: + +An indication is included in the message to indicate that the registration is in CM-CONNECTED state, so that the final AMF will not retrieve UE context based on mapped GUTI in the registration request. + +5. TS 23.502 [3] Steps 4 ~ 16 of figure 4.2.2.2.2-1 or step 8~16 of figure 4.2.2.2.2-1, excluding step 10, are performed. +6. The final AMF selects the final V-SMF(s) based on VPLMN value of S-NSSAI(s) associated with the established PDN connection(s). +7. For each established PDU Session, the final AMF determine the related final V-SMF based on the VPLMN value of S-NSSAI. If the selected final V-SMF is different from the interim V-SMF, the final AMF invokes Nsmf\_PDUSession\_CreateSMContext to the selected final V-SMF, including the interim V-SMF ID in the message. +8. The final V-SMF retrieves SM context from interim V-SMF based on V-SMF ID received from AMF. +- 10~16. Handover the PDU session user plane path to the final V-UPF. After step 12, the uplink path has been switched, and after step 15, the downlink path has been switched. The PGW-U+UPF sends end marker via interim V-SMF after step 15. + +**Editor's note:** The exact procedure how to relocate the V-SMF should be aligned with the conclusions in ETSUN study. + +**Editor's note:** whether the AMF need to be relocated when the UE initiates a new PDU Session that is not using any of the existing S-NSSAI(s) is FFS. + +21. The final AMF notifies the interim AMF by invoking Namf\_Communication\_RegistrationCompleteNotify after the sessions have been switched to final V-SMF/V-UPF. The interim AMF can release session in interim V-SMF and V-UPF. + +##### 6.2.3.3.2 Registration with AMF and V-SMF change during IDLE state mobility + +See the related description in clause 6.2.3.2. + +In addition, if the UE does not include the S-NSSAI of corresponding PDN connection together with default EBI into registration request (i.e. Rel-15 UE), the AMF reselects V-SMF based on S-NSSAI received from PGW-C+SMF, and triggers V-SMF change. For home routed roaming case, the AMF first maps the S-NSSAI value of HPLMN received from PGW-C+SMF to S-NSSAI value of VPLMN, and selects V-SMF based on S-NSSAI value of VPLMN. + +#### 6.2.3.4 Impacts on existing entities and interfaces + +AMF: + +- AMF is enhanced to support the AMF reallocation. +- Based on the default EBI and the associated S-NSSAI. +- In the Registration Request message and a new indication to the final AMF for not to retrieve UE context based on mapped GUTI. +- For each PDU Session, at the Registration Accept message, the associated S-NSSAI of VPLMN is returned to UE. +- AMF must be enhanced to support V-SMF relocation procedures. + +UE: + +- The UE must include the default EBI and the associated S-NSSAI, which can be either the HPLMN value or serving PLMN value, in the Registration Request message. + +SMF: + +- SMF must be enhanced to support V-SMF relocation procedures. + +**Editor's note:** The exact procedure how to relocate the V-SMF should be aligned with the conclusions in ETSUN study. + +#### 6.2.3.5 Evaluation + +### 6.2.4 Solution #2.4: Connected mode mobility from EPC to 5GC + +#### 6.2.4.1 Introduction + +Key issue 2 raises questions on AMF selection and V-SMF selection during the mobility procedure from EPC to 5GC. As there is no assumption that the mechanisms of AMF selection and V-SMF selection for Idle state UE and Connected state UE are same, this solution only considers Connected mode mobility from EPC to 5GC. + +#### 6.2.4.2 Functional description + +In order to select appropriate AMF and V-SMF based on the information of network slices that the UE is using, this solution makes following assumptions: + +- The S-NSSAIs that the UE is using need to be known by the NF that executes the selection. +- Legacy EPC nodes are not required to be enhanced to support S-NSSAI-based AMF or V-SMF selection. +- Current EPC and 5GC interworking procedure should be used as the baseline. + +Based on such assumptions, this solution proposes an S-NSSAI based AMF and V-SMF selection mechanism. + +In this solution, it is assumed that only combo nodes in EPC are allowed to be enhanced, i.e. PGW-C+SMF and HSS+UDM. + +During the PDN connectivity establishment procedure, as described in current specification TS 23.501 [2], the PGW-C+SMF will receive from the UE an ePCO containing PDU session ID, and determines the S-NSSAI corresponding to the PDN connection based on the operator policies, e.g. PGW address and APN. Therefore, the PGW-C+SMF can know the information of the slice the UE is accessing. In order to let the 5GC NFs obtain such information, this solution proposes to store the default EPS Bearer ID and S-NSSAI associated with the PDU Session ID into the HSS+UDM. + +When the inter-system handover from EPC to 5GC is performed, during the handover preparation phase, the MME selects AMF as defined in the TS 23.502 [3] (Rel 15). The selected AMF firstly fetches UE subscription data containing pairs of default EPS bearer ID and S-NSSAI associated with the PDU Session ID from the HSS+UDM, and then determines whether it can serve all slices identified by S-NSSAIs fetched from the HSS+UDM. If the selected AMF can not serve all S-NSSAIs, it requests NSSF to select a target AMF/AMF set based on the S-NSSAIs. + +After the target AMF is determined, the old selected AMF initiates an AMF relocation procedure as specified in the TS 23.502 [3]. The old selected AMF also provide the target AMF the pair of default EBI and S-NSSAI information. The target AMF can select a correct V-SMF based on S-NSSAI for each PDU session which is anchored in another PLMN. + +#### 6.2.4.3 Procedures + +##### 6.2.4.3.1 Enhancement to PDN connection establishment + +![Sequence diagram for PDN connection establishment enhancement. Lifelines: UE, MME, PGW-C+SMF, HSS+UDM. The sequence starts with UE sending a PDN Connectivity Request to MME. MME sends a Create Session Request to PGW-C+SMF. PGW-C+SMF sends a Create Session Response to MME. MME sends a PDN Connectivity Accept to UE. PGW-C+SMF also sends a Notify(default EPS bearer ID, S-NSSAI) to HSS+UDM.](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MME + participant PGW-C+SMF + participant HSS+UDM + UE->>MME: PDN Connectivity Request + MME->>PGW-C+SMF: Create Session Request + PGW-C+SMF-->>MME: Create Session Response + MME-->>UE: PDN Connectivity Accept + PGW-C+SMF->>HSS+UDM: Notify(default EPS bearer ID, S-NSSAI) + +``` + +Sequence diagram for PDN connection establishment enhancement. Lifelines: UE, MME, PGW-C+SMF, HSS+UDM. The sequence starts with UE sending a PDN Connectivity Request to MME. MME sends a Create Session Request to PGW-C+SMF. PGW-C+SMF sends a Create Session Response to MME. MME sends a PDN Connectivity Accept to UE. PGW-C+SMF also sends a Notify(default EPS bearer ID, S-NSSAI) to HSS+UDM. + +**Figure 6.2.4.3.1-1: PDN connection establishment enhancement** + +For each PDN connection, after the PGW-C+SMF determines the associated S-NSSAI based on operator policies, it registers with the UDM and stores the identity of the PDN connection (default EPS Bearer ID) and the S-NSSAI associated with the PDN PDU Session ID into the HSS+UDM. + +The S-NSSAI stored in the HSS+UDM will be used for AMF selection and V-SMF selection. + +##### 6.2.4.3.1 Enhancement to handover preparation from EPC to 5GC + +The enhancement to the handover procedure is quite similar as the AMF relocation procedure defined in the clause 4.2.2.2.3 in TS 23.502 [3]. + +![Sequence diagram for handover preparation from EPC to 5GC. Lifelines: MME, Initial AMF, Target AMF, NSSF, UDM+HSS, PGW-C+SMF. The sequence starts with an external 'Handover Required' message to MME. MME sends a Forward Relocation Request to Initial AMF. Initial AMF sends a Nudm_SDM_Get (SUPI, slice IWK subscription data) to UDM+HSS. UDM+HSS responds with Nudm_SDM_Response (pairs of EBI and S-NSSAI). Initial AMF sends an Nnssf_NSSelection_Get to NSSF. NSSF responds with Nnssf_NSSelection_Response (AMF set). Initial AMF sends a Namf_Communication_N1MessageNotify to Target AMF. Target AMF performs 'V-SMF selection based on the S-NSSAI' and sends an Nsmf_PDUSession_UpdateSMContext Request (PDN connection) to PGW-C+SMF. PGW-C+SMF responds with Nsmf_PDUSession_UpdateSMContext Response. Target AMF performs 'Handover prepare on the target side' and sends a Forward Relocation Response (old AMF ID) back to MME. A 'Handover execution' phase follows.](d79d33da852cb7bca3e87b400a15c3e8_img.jpg) + +``` + +sequenceDiagram + participant MME + participant Initial AMF + participant Target AMF + participant NSSF + participant UDM+HSS + participant PGW-C+SMF + Note left of MME: Handover Required + MME->>Initial AMF: Forward Relocation Request + Initial AMF->>UDM+HSS: Nudm_SDM_Get (SUPI, slice IWK subscription data) + UDM+HSS-->>Initial AMF: Nudm_SDM_Response (pairs of EBI and S-NSSAI) + Initial AMF->>NSSF: Nnssf_NSSelection_Get + NSSF-->>Initial AMF: Nnssf_NSSelection_Response (AMF set) + Initial AMF->>Target AMF: Namf_Communication_N1MessageNotify + Note right of Target AMF: V-SMF selection based on the S-NSSAI + Target AMF->>PGW-C+SMF: Nsmf_PDUSession_UpdateSMContext Request (PDN connection) + PGW-C+SMF-->>Target AMF: Nsmf_PDUSession_UpdateSMContext Response + Note right of Target AMF: Handover prepare on the target side + Target AMF-->>MME: Forward Relocation Response (old AMF ID) + Note bottom: Handover execution + +``` + +Sequence diagram for handover preparation from EPC to 5GC. Lifelines: MME, Initial AMF, Target AMF, NSSF, UDM+HSS, PGW-C+SMF. The sequence starts with an external 'Handover Required' message to MME. MME sends a Forward Relocation Request to Initial AMF. Initial AMF sends a Nudm\_SDM\_Get (SUPI, slice IWK subscription data) to UDM+HSS. UDM+HSS responds with Nudm\_SDM\_Response (pairs of EBI and S-NSSAI). Initial AMF sends an Nnssf\_NSSelection\_Get to NSSF. NSSF responds with Nnssf\_NSSelection\_Response (AMF set). Initial AMF sends a Namf\_Communication\_N1MessageNotify to Target AMF. Target AMF performs 'V-SMF selection based on the S-NSSAI' and sends an Nsmf\_PDUSession\_UpdateSMContext Request (PDN connection) to PGW-C+SMF. PGW-C+SMF responds with Nsmf\_PDUSession\_UpdateSMContext Response. Target AMF performs 'Handover prepare on the target side' and sends a Forward Relocation Response (old AMF ID) back to MME. A 'Handover execution' phase follows. + +**Figure 6.2.4.3.1-1: Enhancement for Handover preparation from EPC to 5GC** + +According to the existing handover procedure from EPC to 5GC, the MME selects an AMF and sends Forward Relocation Request to the AMF. This AMF is called initial AMF in this solution. + +In order to determine a suitable serving AMF, the initial AMF uses the step 3 of "Registration with AMF re-allocation" procedure in TS 23.502 [3] to fetch slice interworking related subscription data first, i.e. pairs of EBI and S-NSSAI associated with the PDU Session ID, and then the initial AMF knows the S-NSSAIs that the UE is using. The initial AMF selects the target AMF based on these S-NSSAIs. + +The target AMF completes the handover preparation in the target side, and responds the MME with a Forward Relocation Response. + +#### 6.2.4.4 Impacts on existing entities and interfaces + +No impact on EPC. + +No impacts on UE. + +The Initial AMF uses the Nudm\_SDM\_Get service operation to retrieve the S-NSSAI associated with the default Bearer ID and the PDU Session ID. + +The PGW-C+SMF must register to UDM for each PDN Connection established in EPC. The PGW-C+SMF updates the default EPS Bearer ID and the S-NSSAI associated with the PDU Session ID to the HSS+UDM. + +HSS+UDM must be enhanced to support the storage of default EPS Bearer ID and the associated S-NSSAI. + +#### 6.2.4.5 Evaluation + +Extra step is required in the handover preparation to retrieve the S-NSSAI from the UDM. + +The solution requires Rel-16 AMF, Rel-16 PGW-C+SMF, and Rel-16 HSS+UDM. + +### 6.2.5 Solution#2.5: Using the NF discovery to find the S-NSSAI. + +#### 6.2.5.1 Introduction + +This solution addresses the key issue#2: Enabling interworking for slicing between EPC and 5GC, and especially how to select the target AMF and V-SMF based on the S-NSSAI of the ongoing PDN connection in mobility from EPC to 5GC. + +#### 6.2.5.2 Functional description + +The solution is based on following principles on how to find out the S-NSSAI for the ongoing PDN connections: + +As specified in Rel-15, when the UE moves from EPC to 5GC, the AMF uses the Nnrf\_NFDiscovery service operation and PGW-C address (FQDN) as an input parameter to discover the corresponding SMF address (FQDN or IP address). + +In this solution, the NRF is used to map the PGW-C address to SMF address and corresponding S-NSSAI. For example, the NF discovery service (Nnrf\_NFDiscovery) is enhanced to include also the S-NSSAI that is served by the SMF. The NRF returns the S-NSSAI of the SMF, along the SMF address, when the AMF discovers the SMF via Nnrf\_NFDiscovery service operation. As the Nnrf\_NFDiscovery service operation is generic, it could return the S-NSSAI also in general SMF discovery not related to EPC interworking. In this case, the S-NSSAI is not used. + +As it may be the SMF serves multiple S-NSSAIs, the mapping of S-NSSAI may be based on following methods: + +Option#A: The PGW-C may be configured with TEID ranges, one TEID range per S-NSSAI served by the SMF. The NRF is configured with the mapping from PGW-C address and TEID range to SMF address and S-NSSAI. The AMF uses the PGW-C address and TEID received from MME as an input to find out the corresponding SMF address and S-NSSAI. Nnrf\_NFDiscovery service operation is enhanced to include also the PGW-C TEID as an input parameter for SMF discovery. + +Option#B: The different PGW-U+UPF IP address might be associated with different S-NSSAI. The NRF is configured with the mapping from PGW-U+UPF IP address to the S-NSSAI, the mapping information between PGW-U+UPF IP address and the corresponding S-NSSAI shall be provided to the NRF by the UPF or OA&M. The PGW-C+SMF selects PGW-U+UPF based on S-NSSAI associated with a PDN connection, and the AMF uses the PGW-U+UPF IP address received from MME as an input parameter to find out the corresponding S-NSSAI. + +Rest of the procedures follow the principles in Solutions 2.1 and 2.2 on how to select the Target AMF and V-SMF: + +- In connected mode, the MME selects the AMF as currently specified in Rel-15. This AMF then acts as an Initial AMF and uses the above procedure to find out the S-NSSAI for each PDN Connection. Based on the list of S-NSSAIs, the Initial AMF can select the Target AMF, using the NSSF service as in Rel-15. The Initial AMF forwards the list of PDN Connections associated with the S-NSSAI and SMF address to the Target AMF. In home-routed roaming case, the Target AMF selects the V-SMF based on the S-NSSAI received from the Initial AMF. +- In idle mode, in home-routed roaming case, once the Target AMF has used the above procedure to find out the S-NSSAI for each PDN connection it received from the MME, the Target AMF selects the V-SMF based on the S-NSSAI. + +It should be noted, that although the above description uses the NRF for SMF discovery, depending on the conclusions in FS\_eSBA, also the common Service Framework may be used for service instance discovery. + +#### 6.2.5.3 Procedures + +##### 6.2.5.3.1 EPS to 5GS handover using N26 interface + +![Sequence diagram for EPS to 5GS handover using N26 interface. The diagram shows the interaction between UE, eNodeB, 5G-AN, MME, Initial AMF, Target AMF, V-SMF, V-UPF, PGW-C+SMF, and PGW-U+UPF. The process starts with UE establishing a PDN connection in 4G EPC. The handover process involves several steps: 1. UE establish PDN Connection in 4G EPC; 2. Handover Required; 3. Forward Relocation Request; 4. Target AMF selection; 5. Namf_Communication_CreateUEContext Request; 6. Nsmf_PDUSession_CreateSMContext Request; 7. N4 Session Establishment; 8. Nsmf_PDUSession_CreateSMContext Response; 9. N4 Session Establishment; 10. Handover Request; 11. Handover Request ACK; 12. Nsmf_PDUSession_UpdateSMContext Request; 13. N4 Session modification; 14. Nsmf_PDUSession_UpdateSMContext Response; 15. Namf_Communication_CreateUEContext Response; 16. Forward Relocation Response; 17. Handover Command; 18. Handover Command; 19. Handover to 5G-RAN Confirm; 20. Handover Notify; 21. Forward Relocation Complete notification; 22. Forward Relocation Complete notification ACK; 23. Nsmf_PDUSession_UpdateSMContext Request; 24. N4 Session modification; 25. Nsmf_PDUSession_UpdateSMContext Response; 26. Resource cleanup in EPC by MME; 27. EPS to 5GS Registration procedure.](90ddf538ef276510e2b631f7b96654e6_img.jpg) + +Sequence diagram for EPS to 5GS handover using N26 interface. The diagram shows the interaction between UE, eNodeB, 5G-AN, MME, Initial AMF, Target AMF, V-SMF, V-UPF, PGW-C+SMF, and PGW-U+UPF. The process starts with UE establishing a PDN connection in 4G EPC. The handover process involves several steps: 1. UE establish PDN Connection in 4G EPC; 2. Handover Required; 3. Forward Relocation Request; 4. Target AMF selection; 5. Namf\_Communication\_CreateUEContext Request; 6. Nsmf\_PDUSession\_CreateSMContext Request; 7. N4 Session Establishment; 8. Nsmf\_PDUSession\_CreateSMContext Response; 9. N4 Session Establishment; 10. Handover Request; 11. Handover Request ACK; 12. Nsmf\_PDUSession\_UpdateSMContext Request; 13. N4 Session modification; 14. Nsmf\_PDUSession\_UpdateSMContext Response; 15. Namf\_Communication\_CreateUEContext Response; 16. Forward Relocation Response; 17. Handover Command; 18. Handover Command; 19. Handover to 5G-RAN Confirm; 20. Handover Notify; 21. Forward Relocation Complete notification; 22. Forward Relocation Complete notification ACK; 23. Nsmf\_PDUSession\_UpdateSMContext Request; 24. N4 Session modification; 25. Nsmf\_PDUSession\_UpdateSMContext Response; 26. Resource cleanup in EPC by MME; 27. EPS to 5GS Registration procedure. + +**Figure-6.2.5.3.1-1: EPS to 5GS handover using N26 interface** + +1. Step 1 to step 3 are the same as in Rel-15 EPS to 5GS handover using N26 interface. The AMF selected by the MME becomes an Initial AMF in this solution. +4. The Initial AMF uses the PGW-C address and TEID in PDN Connections received from the MME as an input parameter to NRF (e.g. Nnrf\_NFDiscovery) service to discover the SMF address. The NRF returns also the S-NSSAI for the SMF for each PDN Connection. + +If the Initial AMF cannot serve all the S-NSSAI(s), the Initial AMF invokes the Nnssf\_NSSelection\_Get service operation from the NSSF to select the Target AMF. + +In home-routed roaming case, if the VPLMN and HPLMN have an SLA to support non-standard S-NSSAI values in the VPLMN, the Initial AMF uses the NSSF of the VPLMN to map the S-NSSAI values to the respective S-NSSAI values to be used in the VPLMN. + +5. In case the Target AMF is different to Initial AMF, the Initial AMF sends Namf\_Communication\_CreateUEContext service operation (Target 5GAN Node ID, Source to Target Transparent Container, EPS MM Context, EPS Bearer Context(s), , list of S-NSSAI(s) and SMF addresses received in step 4) message to the Target AMF. In home-routed roaming case, the Target AMF selects the V-SMF based on the S-NSSAI associated with the PDN Connection. + +Steps 6-27 are the same as in Rel-15 EPS to 5GS handover procedure using N26 interface in clause 4.11.1.2.2 of TS 23.502 [3]. + +#### 6.2.5.4 Impacts on existing entities and interfaces + +No impact on EPC. + +No impacts on UE. + +The Initial AMF uses the NRF, e.g. Nnrf\_NFDiscovery service to map the PGW-C address and TEID to SMF address and the S-NSSAI. + +For example, the Nnrf\_NFDiscovery service operation is enhanced to include also the S-NSSAI that is served by the SMF. The NRF returns the S-NSSAI of the SMF, along the SMF address, when the AMF discovers the SMF via Nnrf\_NFDiscovery service operation. + +If the SMF serves multiple S-NSSAIs, then the PGW-C must be configured with TEID ranges, one TEID range per S-NSSAI served by the SMF. In this case, the NRF is configured with the association from PGW-C address and TEID range to SMF address and S-NSSAI. + +Option#B: The different PGW-U+UPF IP address might be associated with different S-NSSAI, the AMF need to extract the IP address from the EPS bearer context. + +#### 6.2.5.5 Evaluation + +The solution requires Rel-16 AMF and Rel-16 PGW-C+SMF. + +## 6.3 Solutions for KI#3 + +### 6.3.1 Solution #3.1: Slice Specific Authentication and Authorization using non 3GPP credentials based on secondary authentication + +#### 6.3.1.1 Introduction + +The solution addresses key issue#3. + +The 5GS system has introduced secondary authentication at the establishment of a PDU session. Specifically, during the establishment of a PDU session, Release 15 has defined that a DN-specific identity (TS 33.501 [6]) of a UE may be authenticated/authorized by the DN, via a DN-AAA server that may belong to the 5GC or to the DN. This solution assumes that the secondary authentication is performed between the 5GC and the external DN-AAA server with the support the NEF. + +The procedure allows both the authentication triggering by the UE (with the UE providing authentication information during the Establishment of the PDU Session), or by the SMF that can reject the PDU Session Establishment if the UE has not provided authentication/authorization information. At any time, a DN-AAA server may revoke the authorization for a PDU Session or update DN authorization data for a PDU Session. According to the request from DN-AAA server, the SMF may release the PDU Session. + +Such secondary authentication takes place in 5GS in addition to (and after) the 5GC access authentication handled by AMF. + +In this solution it is assumed that connectivity to a slice implies the establishment of at least one PDU session. + +#### 6.3.1.2 Functional description + +It is proposed to re-use the secondary authentication introduced in Release 15 to enable slice authentication. + +Specifically, the secondary authentication is used and enhanced as follows: + +- If access to a specific network slice (i.e. a specific S-NSSAI) needs to be authenticated based on non 3GPP network slice credentials, the slice provider/customer provisions such network slice credentials (slice-specific User ID and security credentials) to the UE with mechanisms out of scope of this solution. +- If access to a specific network slice (i.e. a specific S-NSSAI) needs to be authenticated based on non 3GPP network slice credentials, at the establishment of the first PDU session corresponding to the S-NSSAI that requires authentication, the UE provides the non 3GPP credentials required for the authentication. If the UE does not provide such credentials and the SMF determines that the PDU session corresponding to the S-NSSAI needs to be authenticated, the SMF retrieves the credentials from the UE with an EAP Identity Request as defined in TS 33.501 [6]. +- The SMF authenticates just the first PDU session established corresponding to an S-NSSAI with a Slice-AAA function which, similarly to the DN-AAA for UE secondary authentication, may be in the 5GC network or external. + - The SMF may authenticate all the PDU sessions corresponding to the S-NSSAI, depending on network policies. +- When the SMF performs the authentication for a PDU session establishment corresponding to an S-NSSAI, the GPSI itself is used as external UE identifier and is provided to the Slice-AAA. This can be achieved by allocating a GPSI to any UE for which, based on subscription information, UE secondary authentication is required for one of the subscribed S/NSSAI(s)/DNN(s). +- During the UE secondary authentication, the authentication SMF (H-SMF or V-SMF for LBO) provides the GPSI, S-NSSAI, and optionally PDU Session ID to the Slice-AAA in addition to the information currently provided. This enables an external Slice-AAA to create a context related to the authentication of a slice that may have one or more PDU sessions for triggering re-authentication and de-authorization. +- When secondary authentication is performed successfully, the Slice-AAA subscribes with the NEF (with GPSI, S-NSSAI, and PDU Session ID) for notification of the change of SMF the SMF should contact to enable re-authentication. This is needed in order to ensure that the Slice-AAA contacts the correct SMF considering that a slice may have multiple PDU sessions which may be activated and released while the UE is authenticated for a slice (i.e. the PDU session that triggered the authentication may be released, and the Slice-AAA should be able to reach a different SMF for a PDU session corresponding to the S-NSSAI to trigger re-authentication). +- for Rel. 15 secondary authentication, the information on a successful secondary authentication/authorization between a UE and an SMF may be saved in SMF and/or UDM. In this solution, it is assumed that the information on successful authentication of a slice is stored in the UDM, and contains both the information on a previous successful authentication for a slice (S-NSSAI) and for a DN. +- Upon establishment of a PDU session corresponding to an S-NSSAI, the SMF checks whether the UE has already been authenticated and/or authorized for the same S-NSSAI by an SMF, in addition of checking if the UE has already been authenticated and/or authorized for the same DN. +- if DNN authentication/authorization is required in addition to slice authentication, the secondary authentication is executed twice by the SMF within the same PDU session establishment procedure, based on the network slice credentials first, and based on the DNN-specific secondary authentication information. The SMF shall not authorize the PDU session establishment unless both authentication/and authorization succeed. If both authentications are needed, the UE in addition to the current SM PDU DN request container provides also the network slice credentials. +- The slice-AAA may be part of the 5GC or may belong to the DN of the service provider offering the slice services. +- De-authorization of a slice by the slice-AAA will trigger the PDU session release of all the PDU sessions corresponding to the slice. + +- When the Slice-AAA indicates revocation of a slice authorization, the Slice-AAA sends an indication to the NEF associated to the received GPSI, which in turn informs the SMF(s) serving the slice, and the PDU session(s) corresponding to that slice, that the PDU session(s) needs to be released. +- A failed slice authentication or a slice de-authentication triggers the SMF to inform the AMF that the S-NSSAI corresponding to one or more PDU sessions is not authorized. The AMF decides based on local policies whether to update the Allow NSSAI and indicate to the UE that the S-NSSAI is rejected. + +#### 6.3.1.3 Procedures + +##### 6.3.1.3.1 Slice authentication at first PDU session establishment for the S-NSSAI + +![Sequence diagram illustrating PDU Session Establishment authentication/authorization by a DN-AAA server. The diagram shows interactions between UE, AMF, SMF, UDM, AUSF, NEF, and AAA. Steps include UE Registration, Primary Authentication, PDU Session Establishment Request, Secondary Authentication for Slice, Secondary Authentication for DN (optional), Subscribe to event notification (change of PSA), Additional PDU Session Establishment Request, Verify Slice Authentication Status, and Secondary Authentication (optional).](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant SMF + participant UDM + participant AUSF + participant NEF + participant AAA + + Note left of AMF: 1. UE Registration + UE->>AUSF: 1a. Primary Authentication + Note left of SMF: 2. PDU Session Establishment Request + UE->>SMF: 2. PDU Session Establishment Request + Note left of SMF: 3. Secondary Authentication for Slice + SMF->>UDM: 3. Secondary Authentication for Slice + Note left of SMF: 4. Secondary Authentication for DN + SMF->>AAA: 4. Secondary Authentication for DN + Note left of NEF: 5. Subscribe to event notification (change of PSA) + SMF->>NEF: 5. Subscribe to event notification (change of PSA) + Note left of SMF: 6. Additional PDU Session Establishment Request + UE->>SMF: 6. Additional PDU Session Establishment Request + Note left of SMF: 7. Verify Slice Authentication Status + SMF->>UDM: 7. Verify Slice Authentication Status + Note left of SMF: 8. Secondary Authentication + SMF->>AAA: 8. Secondary Authentication + +``` + +Sequence diagram illustrating PDU Session Establishment authentication/authorization by a DN-AAA server. The diagram shows interactions between UE, AMF, SMF, UDM, AUSF, NEF, and AAA. Steps include UE Registration, Primary Authentication, PDU Session Establishment Request, Secondary Authentication for Slice, Secondary Authentication for DN (optional), Subscribe to event notification (change of PSA), Additional PDU Session Establishment Request, Verify Slice Authentication Status, and Secondary Authentication (optional). + +**Figure 4.3.2.3-1: PDU Session Establishment authentication/authorization by a DN-AAA server** + +1. The UE registers with the network. Primary authentication is performed during the registration procedure. +2. The UE triggers PDU session establishment for an S-NSSAI (or for none and one is selected by the network). +3. The SMF determines that slice authentication is required and triggers secondary UE authentication for the S-NSSAI. Upon successful authentication, the SMF stores in the UDM for the S-NSSAI the status of the slice authentication and the SMF ID as the slice authenticator. +4. [Optional] If DN authentication is also needed, the UE secondary authentication for the DNN is performed upon successful slice authentication. +5. The Slice AAA server subscribes for event notification via the NEF to be informed of a change of SMF, in order to enable the AAA server to reach the correct entity for re-authentication and de-authorization. +6. The UE may establish an additional PDU session for the same S-NSSAI. + +7. Since the SMF for this PDU session may be different from the SMF of previous PDU sessions for the same S-NSSAI, the SMF checks the slice authentication status in the UDM. If no slice authentication is required, the SMF ID is stored in the UDM as serving the S-NSSAI in addition to other SMF IDs serving the same S-NSSAI. +8. [Optional] If slice authentication or DN authentication is needed, the SMF triggers the secondary authentication. + +#### 6.3.1.4 Impacts on existing entities and interfaces + +Impacted functions: + +- UE: + - support of S-NSSAI-based secondary authentication in addition/parallel to secondary authentication for a DN. + - provisioning of multiple SM PDU containers at PDU session establishment to support both slice authentication and DNN authentication, when needed. +- AMF: if slice authentication fails, SMF may inform AMF that the authentication for the S-NSSAI failed and the AMF may, based on local policies, remove the S-NSSAI from the Allowed NSSAI. +- SMF: support slice authentication in addition to secondary authentication for DN. SMF to verify slice authentication status in UDM to avoid unnecessarily re-authenticating a slice if authentication took place at a previous PDU session establishment. +- AAA server: support of interaction with NEF for subscription to slice and DN related events (e.g. change of PSA) in order to allow the AA server to be up to date with the PSA where to send re-authentication requests or de-authorization requests. + +#### 6.3.1.5 Evaluation + +The solution does not require a slice to which the UE may never connect (i.e. establish connectivity to via a PDU session) to be authorized/authenticated until the UE requires the connectivity. + +The solution does not impact the registration procedure in terms of MM timers, e.g. in case of failed authentications/retries due to EAP failure. + +The solution re-uses existing NAS signalling. The solution re-uses the existing architecture and existing interfaces. + +### 6.3.2 Solution #3.2: Solution to KI#3 on Slice Specific Authentication and Authorization using non 3GPP credentials + +#### 6.3.2.1 Introduction + +The scenario considered for the solution is that there is an Authentication, Authorisation and Accounting Server (AAA-S) deployed in a PLMN or in a third-party network that allows Slice-Specific secondary authentication and authorisation of users who have the right of access to certain slices. The AAA Server handles the User IDs and credentials for a Secondary authentication at a non 3GPP User ID level, after the UE has been authenticated by the 3GPP system for PLMN access. A AAA proxy function (AAA-F) is also defined to provide a single point of interaction from the PLMN with the third parties. The AAA-F can be a standalone or its services could be supported by other NFs (i.e. AUSF or NEF). + +#### 6.3.2.2 Functional description + +If a UE subscription includes an S-NSSAI of a slice that requires Slice-Specific Secondary Authentication and Authorisation, the UDM stores a flag indicating that this step is needed for the S-NSSAI. The IP address or FQDN/realm of the AAA Server that would perform the authentication and authorisation may be stored in the AAA-F per S-NSSAI. Alternately, if the User ID in the third party is defined as a NAI (see RFC 4282 [8]), i.e. the User ID is in the form user@domain, the IP Address is not needed in AAA-F and the correct AAA-S is derived at AAA-F by resolving the domain part of the NAI. + +When a UE performs a registration request which includes S-NSSAI(s) in the Requested NSSAI which needs Slice-Specific Secondary Authentication and Authorisation (as detected based on the subscription information, as outlined above), the AMF executes on top of any required PLMN specific Authentication and Authorization step, an + +Authentication and Authorization step that is run with the UE and involves the AAA Server for the specific S-NSSAI(s). In the worst case, one such step is needed for each S-NSSAI. In general, there can be a mix of slices requiring Slice-Specific Secondary Authentication and Authorisation, and slices that do not require this. + +For the S-NSSAIs which require Slice-Specific Secondary Authentication and Authorisation, the UE needs to be provided with the necessary credentials and algorithms necessary to authenticate itself with the AAA Server. This aspect is left out of the scope of this solution. + +In addition, the UE includes a security capability indicating its support for Slice-Specific Secondary Authentication and Authorisation in the registration request facilitating the AMF to determine whether it can execute Slice-Specific Secondary Authentication and Authorisation or not. If the security capability is not included in the registration request (e.g. in case of Rel-15 UEs), the AMF shall not allow UE to access to any Network Slice for which Slice-specific Secondary authentication is required. + +The proposal assumes that the assumed transport protocol is EAP and is summarized by the following figure: + +![Sequence diagram illustrating the registration process with Slice-Specific Secondary Authentication and Authorization. The diagram shows five steps between a UE, AMF, AUSF, AAA-F, and AAA-S. Step 1: UE sends a Registration Request (Requested NSSAI, Security capability) to AMF. Step 2: AMF initiates security procedures for PLMN access (AMF Authenticator, AUSF is auth server). Step 3: AMF checks subscription data and UE's security capability to determine if extra authentication is needed for a certain S-NSSAI. Step 4: AMF performs Secondary Authentication for Slice access (if applicable for a S-NSSAI) based on EAP. Step 5: AMF sends a Registration Accept (Allowed NSSAI) to UE.](e29665b8abcea967ef289c6aff07ae4c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant AUSF + participant AAA-F + participant AAA-S + + Note right of AMF: 2. Security procedures PLMN access (AMF Authenticator, AUSF is auth server) + Note right of AMF: 3. AMF checks subscription data and UE's security capability on whether to apply extra level of authentication and / or authentication for a certain S-NSSAI + + UE->>AMF: 1. Registration Req (Requested NSSAI, Security capability) + AMF->>AUSF: + AMF->>AAA-F: + AMF->>AAA-S: + AAA-S-->>AAA-F: + AAA-F-->>AUSF: + AUSF-->>AMF: + AMF->>UE: 5. Registration Accept (Allowed NSSAI) + +``` + +Sequence diagram illustrating the registration process with Slice-Specific Secondary Authentication and Authorization. The diagram shows five steps between a UE, AMF, AUSF, AAA-F, and AAA-S. Step 1: UE sends a Registration Request (Requested NSSAI, Security capability) to AMF. Step 2: AMF initiates security procedures for PLMN access (AMF Authenticator, AUSF is auth server). Step 3: AMF checks subscription data and UE's security capability to determine if extra authentication is needed for a certain S-NSSAI. Step 4: AMF performs Secondary Authentication for Slice access (if applicable for a S-NSSAI) based on EAP. Step 5: AMF sends a Registration Accept (Allowed NSSAI) to UE. + +**Figure 6.3.2.2-1: Registration with Slice-Specific Secondary Authentication and Authorisation for Slice Access (high level concept)** + +Step 4 is conditional to both the UE security capability and the S-NSSAI subscription data, checked at step 3, including a flag that indicates Slice-Specific Secondary Authentication and Authorisation is needed. If this is needed and UE supports it, this step is executed. The start of this step suspends the current Registration procedure timer. This timer is restarted when all the pending EAP procedure for slices that are subject to Slice-Specific Secondary Authentication are completed. + +**Editor's note:** This approach needs to be checked whether it is acceptable by CT1 and based on the feedback changes to the solution may be done in normative phase to align with the preferred way to handle NAS and EAP timers interaction. + +Once it is executed, status can be kept by the AMF in the UE context, so extra authentication is not repeated at subsequent registrations until a re-authentication is required by the AAA Server or the PLMN, based on policy. If this is needed but UE does not support it, this step is skipped and the AMF shall not include an NSSAI to the Allowed NSSAI in step 5. + +Explicit challenges used to re-authenticate the UE, or a request to revoke the authorization of the UE may come from the AAA Server and the AAA-F routes to the current serving AMF based on a binding between the User ID and the GPSI of the UE established when the UE is authorised. The AAA Server keeps a coupling between the User ID of the UE and the UE GPSI so it can pinpoint the UE for the User ID when it needs to be re-authenticated or its authorization status changes and needs to be revoked. + +Once step 4 is executed successfully, and the registration accepted, the UE, after optional NSSF interaction (not explicitly shown above), is provided an allowed NSSAI including the slices that were successfully authorised. SM procedures can take place in the authorised slices for the UE. + +If the UE fails Slice-Specific Secondary Authentication, and this results in the UE not having any Allowed NSSAI, the UE may be Accepted, as per rel-15 behaviour in the case of a misconfigured UE, with no Allowed NSSAI and, depending on operator policy, remain registered with operator-specific service restriction in the same AMF or it may be re-allocated to a specific AMF which applies specific service restrictions. The AMF then may e.g. deregister the UE after a certain time configurable by the operator. + +If the UE fails Slice-Specific Secondary Authentication for a specific slice, how the UE obtains fresh/valid credentials from third parties is outside the scope of 3GPP. + +NOTE: A UE may gain access to a slice that needs Slice-Specific Secondary Authentication and Authorisation and not trigger any PDU session establishment (e.g. SMS only device) or require a PDU session only after SMS trigger after it is assigned an Allowed NSSAI and is successfully registered. + +#### 6.3.2.3 Procedures + +##### 6.3.2.3.1 Secondary Authentication and Authorization During Registration + +During the registration procedure, before step 15 occurs, in figure 6.3.2.3.1-1, the AMF knows whether some S-NSSAIs require Slice-Specific Secondary Authentication and Authorisation based on information from the UDM. + +![Sequence diagram of the Registration procedure (Figure 6.3.2.3.1-1: TS 23.502 [3] Figure 4.2.2.2.2-1).](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN as (R)AN + participant NewAMF as New AMF + participant OldAMF as Old AMF + participant PCF + participant SMF + participant AUSF + participant UDM + + Note right of RAN: 2. AMF selection + Note right of NewAMF: 8. AUSF selection + Note right of OldAMF: EIR + Note right of NewAMF: 13. UDM selection + Note right of NewAMF: 15. PCF selection + Note right of SMF: N3IWF + + UE->>RAN: 1. Registration Request + RAN->>NewAMF: 3. Registration Request + NewAMF->>OldAMF: 4 Namf_Communication_UEContextTransfer + OldAMF-->>NewAMF: 5 Namf_Communication_UEContextTransfer response + NewAMF-->>UE: 6. Identity Request + UE-->>NewAMF: 7. Identity Response + Note right of NewAMF: 9. Authentication/Security + Note right of AUSF: 9. Authentication/Security + Note right of UDM: 9. Authentication/Security + NewAMF-->>OldAMF: 10. Namf_Communication_RegistrationCompleteNotify + NewAMF-->>UE: 11. Identity Request/Response + NewAMF->>OldAMF: 12. N5g-eir_EquipmentIdentityCheck_Get + OldAMF-->>NewAMF: 12. N5g-eir_EquipmentIdentityCheck_Get response + Note right of NewAMF: 14a. Nudm_UECM_Registration + Note right of NewAMF: 14b. Nudm_SDM_Get + Note right of NewAMF: 14c. Nudm_SDM_Subscribe + Note right of NewAMF: 14d. Nudm_UCM_DeregistrationNotify + Note right of NewAMF: 14e. Nudm_SDM_Unsubscribe + Note right of NewAMF: 15. PCF selection + Note right of NewAMF: 16. AM Policy Association Establishment during Registration + Note right of SMF: 17. Nsmf_PDUSession_UpdateSMContext / Nsmf_PDUSession_ReleaseSMContext + Note right of SMF: 18. N2 AMF Mobility Request + Note right of SMF: 19. N2 AMF MobilityResponse + Note right of OldAMF: 20. AMF-Initiated AM Policy Association Termination + NewAMF->>RAN: 21. Registration Accept + RAN->>UE: 22. Registration Complete + NewAMF-->>UDM: 23. Nudm_SDM_Info + +``` + +Sequence diagram of the Registration procedure (Figure 6.3.2.3.1-1: TS 23.502 [3] Figure 4.2.2.2.2-1). + +**Figure 6.3.2.3.1-1: TS 23.502 [3] Figure 4.2.2.2.2-1: Registration procedure** + +If the AMF detects the need to execute the Slice-Specific Secondary Authentication and Authorisation, the steps marked as "2" in Figure 6.3.2.3.1-2 are executed. In the event the Allowed NSSAI needs to be computed and potential new AMF determined by a NSSF, then these Authentication and Authorization steps are executed upfront so that the NSSF receives from the AMF only the authorized by Slice-Specific Secondary Authentication and Authorisation and subscribed-to slices. + +![Sequence diagram for Registration with third party Authentication and Authorisation. Lifelines: UE, AMF, AUSF, AAA-F, AAA-S. The diagram shows the interaction between these entities during registration, including steps 1-14 (TS 23.502 clause 4.2.2.2.2), steps 2.a through 2.l, and step 3 (AMF determining allowed NSSAI).](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant AMF + participant AUSF + participant AAA-F + participant AAA-S + + Note over UE, AMF, AUSF, AAA-F, AAA-S: 1. Steps 1-14 registration procedure in TS 23.502 clause 4.2.2.2.2: US is authenticated in AMF using 3GPP credentials and the AMF has subscription information for UE. The AMF knows also for which S-NSSAI execute steps 2 + + Note right of AMF: 2.a NAS message (EAP ID request, S-NSSAI) + UE-->>AMF: 2.a NAS message (EAP ID request, S-NSSAI) + Note right of AMF: 2.b NAS message (EAP ID Response, S-NSSAI) + AMF-->>UE: 2.b NAS message (EAP ID Response, S-NSSAI) + Note right of AMF: 2.c Auth Request (EAP ID Response, AAA server addr, GPSI, S-NSSAI) + AMF-->>AAA-F: 2.c Auth Request (EAP ID Response, AAA server addr, GPSI, S-NSSAI) + Note right of AAA-F: 2.d Auth Request (EAP ID Response, GPSI, S-NSSAI) + AAA-F-->>AAA-S: 2.d Auth Request (EAP ID Response, GPSI, S-NSSAI) + Note right of AAA-S: 2.e Auth Response (EAP) + AAA-S-->>AAA-F: 2.e Auth Response (EAP) + Note right of AAA-F: 2.f Auth Response (EAP) + AAA-F-->>AMF: 2.f Auth Response (EAP) + Note right of AMF: 2.g NAS message (EAP, S-NSSAI) + AMF-->>UE: 2.g NAS message (EAP, S-NSSAI) + Note right of AMF: 2.h NAS message (EAP, S-NSSAI) + AMF-->>UE: 2.h NAS message (EAP, S-NSSAI) + Note right of AMF: 2.i Auth Req.(EAP) + AMF-->>AAA-F: 2.i Auth Req.(EAP) + Note right of AAA-F: 2.j Auth Req.(EAP) + AAA-F-->>AAA-S: 2.j Auth Req.(EAP) + Note right of AAA-S: 2.k Auth Response (EAP success) + AAA-S-->>AAA-F: 2.k Auth Response (EAP success) + Note right of AAA-F: 2.l Auth Response (EAP success) + AAA-F-->>AMF: 2.l Auth Response (EAP success) + Note right of AMF: 2.m NAS message (EAP success, S-NSSAI) + AMF-->>UE: 2.m NAS message (EAP success, S-NSSAI) + + Note right of AMF: 3. AMF knows the list of authorised and subscribed S-NSSAIs and can proceed to determine allowed NSSAI (incl. NSSF interaction) and selection of AMF. Change of AMF may take place + + Note over UE, AMF, AUSF, AAA-F, AAA-S: 4. registration completes and the Ue is provided with allowed NSSAI + +``` + +Sequence diagram for Registration with third party Authentication and Authorisation. Lifelines: UE, AMF, AUSF, AAA-F, AAA-S. The diagram shows the interaction between these entities during registration, including steps 1-14 (TS 23.502 clause 4.2.2.2.2), steps 2.a through 2.l, and step 3 (AMF determining allowed NSSAI). + +**Figure 6.3.2.3.1-2: Registration with third party Authentication and Authorisation** + +1. Steps 1-14 of the Registration procedure. Steps 2 are not executed if no S-NSSAI in the UE subscription is requiring Slice-Specific Secondary Authentication and Authorization or the UE does not have a security capability. +- 2a. [Conditional] The AMF requests the UE User ID for the S-NSSAI. The NAS message includes the S-NSSAI value so the right Network Slice authentication is executed and so the related User ID and credentials are used by the UE. The AMF may start in parallel several such authentication and Authorisations procedures if more than one S-NSSAI is subject to Secondary Slice-Specific Authentication and Authorisation. This step suspends the current Registration procedure timer, which is resumed when all the pending EAP interactions for Slice-Specific Secondary Authentication complete. +- Editor's note: This approach needs to be checked whether it is acceptable by CT1 and based on the feedback changes to the solution may be done in normative phase to align with the preferred way to handle NAS and EAP timers interaction. +- 2b. [Conditional] The UE provides the User ID for the S-NSSAI alongside the S-NSSAI. +- 2c-2d. [Conditional] The AMF contacts the AAA Server via AAA-F. It includes also the S-NSSAI and the UE GPSI for binding of Network Slice User ID to the UE GPSI (so the AAA Server is allowed to contact the UE for further reauthentication based on its policy, or to revoke the UE authorisation, or to optimise future Authorisations based on the AAA server trusting the GPSI presented by the PLMN. If the AAA Server trusts the GPSI provided, by the PLMN, and it had if it had a previous mapping of the GPSI to the User ID, the AAA Server may go directly to step 2k. +- 2e-2j. [Conditional] The UE EAP based authentication happens. The number of steps is indicative, more may occur. + +- 2k-2m. [Conditional] The EAP authentication completes successfully. Optionally, in steps 2k and 2l the AAA Server and the AAA-F convey to the AMF a list of S-NSSAIs the successful Authentication and Authorisation applies to, so the AMF can avoid executing multiple Authentications and Authorisations towards the same AAA Server for the same User ID for the S-NSSAIs in the list. This option should not be used if the AAA-s intends to collect accounting information for S-NSSAI usage by the UE. +3. The AMF stores in the UE context the outcome of steps 2 and if a list of S-NSSAIs was provided sharing the same User ID, then the AMF stores that also. The AMF can now determine, assisted by NSSF if needed, the Allowed NSSAI and this may trigger selection of another AMF. +4. The registration completes, and eventually a Registration Accept is sent to the UE including the Allowed NSSAI and the GUTI allocated by the target AMF if the AMF is relocated in step 3. + +##### 6.3.2.3.2 Secondary Re-Authentication and Re-Authorization after Registration + +The AAA-S may, based on application layer event, prompt the network to Re-authenticate and Re-authorize the user by sending a request to the AAA-F. For example, the AAA-S may initiate the request based on security policies, in order to revoke the User's authorization to access the slice. + +In response to the request from the AAA-S, the AAA-F will initiate re-authentication and re-authorization by sending a request to the AMF. Upon receiving the request, the AMF initiates step 2 of Figure 6.3.2.3.1-2. If the purpose of the request is to revoke the User's authorization to access the slice, then the UE's Allowed NSSAI is updated accordingly via a Configuration Update per clause 4.2.4.2 of TS 23.502 [3]. + +#### 6.3.2.4 Impacts on existing entities and interfaces + +Impacted functions: + +UE: to be able to participate in Slice-Specific Secondary Authentication and Authorisation per S-NSSAI. Indicating UE's security capability to support the Slice-Specific Secondary Authentication and Authorisation. + +AMF: triggering of Secondary Authentication and Authorisation per slice and ability to store outcome and any list of S-NSSAIs sharing the same authorised User ID. The Change of AMF happens to match the allowed NSSAI may happen after evaluation of the Secondary Authorisation Status. This happens after the UE is detected to be authorised for 3GPP access in the source AMF. The AMF takes into account of UE's security capability to trigger the Slice-Specific Secondary Authentication and Authorisation towards the UE. + +UDM: Slice-Specific Support of Secondary Authentication info. + +#### 6.3.2.5 Evaluation + +This solution describes slice-based authentication/authorisation when UE requests registration to the associated S-NSSAI (e.g. during Registration procedure). The network (e.g. AMF) determines if the requested S-NSSAI(s) are subject to Slice-Specific Secondary Authentication and Authorisation. It allows for upfront determination whether the requested S-NSSAI is allowed to be used, and thus, the network grants Allowed NSSAI to the UE before any PDU session is established. + +Considering that a Serving AMF is part of the used network slices (i.e. slices part of the Allowed NSSAI), this solution allows to selection a serving AMF after the successful slice-based authentication/authorisation. + +The approach of nesting EAP interactions for Slice-Specific Secondary Authentication in the registration procedure NAS procedure needs to be checked whether it is acceptable by CT1 for the aspect of the interaction of EAP and NAS timers as described in the proposed solution. Based on the feedback, changes to the solution may be done in normative phase to align with the preferred way to handle NAS and EAP timers interaction. + +### 6.3.3 Solution #3.3: Solution for configuration of network slice authentication + +#### 6.3.3.1 Introduction + +This solution applies to Key Issue 3 (Access to specific Network Slices authorized and authenticated through additional User Identifiers). + +It is assumed that particular application(s) or service(s) in the UE has been configured with User ID and security credentials for slice authentication and authorization. Also, the network has been configured that a particular Network Slices(s) require authentication and authorization. + +#### 6.3.3.2 Functional description + +The main feature of this solution is the dynamic configuration for Network Slice authentication and authorisation in the network. In order to allow dynamic configuration update, the network may expose a service API (e.g. via North Bound APIs or via N33 interface) which supports provisioning of Network Slice authentication required indication from a service provider application function (SP-AF, similar to SCS/AS from TS 23.682 [7]). + +**Editor's note:** It is FFS whether the configuration for Network Slice authentication in the network is performed per service/SP-AF (meaning per S-NSSAI), or per UE, or both. + +The UE usually stores the User ID and the security information (e.g. security credentials) at the application layer (e.g. in a particular application). The application should register with the NAS layer (or EAP client) in order to bind the User ID with the particular S-NSSAI. + +#### 6.3.3.3 Procedures + +#### 6.3.3.4 Impacts on existing entities and interfaces + +#### 6.3.3.5 Evaluation + +**Editor's note:** This clause provides an evaluation of the solution. + +# --- 7 Evaluation + +## 7.1 Evaluations Criteria for KI#1: Mutually Exclusive Access to Network Slices + +The following set of evaluation criteria are used to evaluate the proposed solutions for KI#1 to support UE for mutually exclusive accessing to network slices: + +- 1) Comply to the definition of Mutually Exclusive Access to Network Slices as described in clause 3.1. +- 2) Comply to the working assumptions and requirements as described in clause 4. +- 3) Address all the objectives of the KI#1 as described in clause 5.1. +- 4) Impact to the UE, the serving PLMN, the home PLMN, e.g. AMF, NSSF, UDM, SMF, PCF in term of signalling interfaces, control flows and internal logic etc. including changes to the semantics of existing services/parameters. +- 5) Impact to (R)AN. + +## 7.2 Evaluations for KI#2: Enabling interworking for slicing between EPC and 5GC + +There are 5 solutions (Solutions 2.1 – 2.5) for Key Issue #2 (Enabling interworking for slicing between EPC and 5GC). + +**Table 7.2-1: Key impacts of the solutions** + +| | Solution 2.1 | Solution 2.2 | Solution 2.3 | Solution 2.4 | Solution 2.5 | +|-------------------------|------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UE impact | Idle:
N/A.

Connected:
No impact. | Idle:
Yes (default EBI in registration request)

Connected:
Yes (send S-NSSAI to MME as container) | Idle:
Yes (default EBI in registration request)

Connected:
No impact | Idle:
N/A.

Connected:
No impact | Idle:
No impact.

Connected:
No impact | +| EPC impact | Idle:
N/A.

Connected:
No impact. | Idle:
No impact.

Connected:
Yes (UE send S-NSSAI to MME, and from MME to AMF) | Idle:
No impact.

Connected:
No impact | Idle:
N/A.

Connected:
No impact. | Idle:
No impact.

Connected:
No impact. | +| PGW-C+SMF impact | Idle:
N/A.

Connected:
No impact. | Idle:
No impact

Connected:
No impact | Idle:
No impact.

Connected:
No impact | Idle:
N/A.

Connected:
Yes (S-NSSAI storing to UDM) | Idle:
No impact.

Connected:
Yes (allocated TEID-C based on S-NSSAI) | +| V-SMF impact | Idle:
N/A.

Connected:
No impact. | Idle:
No impact.

Connected:
No impact. | Idle:
No impact.

Connected:
Yes (V-SMF relocation, depending on ETSUN conclusion). | Idle:
N/A.

Connected:
No impact. | Idle:
No impact.

Connected:
No impact. | +| AMF impact | Idle:
N/A.

Connected:
Yes (retrieve S-NSSAI from PGW-C, AMF selection and redirection during preparation phase) | Idle:
Yes (receive default EBI from UE)

Connected:
Yes (AMF selection and redirection during preparation phase, also impact N26) | Idle:
Yes (receive default EBI from UE)

Connected:
Yes (reselect and redirect AMF during registration procedure after handover) | Idle:
N/A

Connected:
Yes (retrieve S-NSSAI from UDM, AMF selection and redirection during preparation phase) | Idle:
No impact.

Connected:
Yes (retrieve S-NSSAI from NRF, and AMF selection/redirection during preparation phase) | +| UDM impact | Idle:
N/A

Connected:
No impact | Idle:
No impact.

Connected:
No impact | Idle:
No impact.

Connected:
No impact | Idle:
N/A

Connected:
Yes (S-NSSAI storing to UDM) | Idle:
No impact.

Connected:
No impact | +| NRF impact | Idle:
N/A.

Connected:
No impact. | Idle:
No impact

Connected:
No impact. | Idle:
No impact

Connected:
No impact. | Idle:
N/A.

Connected:
No impact. | Idle:
Yes, (the PGW-C+SMF TEID or UPF plane information need be stored)

Connected:
(the PGW-C+SMF TEID or UPF plane information need be stored) | + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|---------------------------------------|---------------------------------------------------------------------------------------|----------------------------------------------|---------------------------------------| +| Extra delay in handover preparation | Yes (S-NSSAI query from SMF, AMF reselection/redirection) | Yes (AMF reselection and redirection) | No impact (since, UE is moved to final AMF after the handover) | Yes (UDM query, AMF reselection/redirection) | Yes (AMF reselection and redirection) | +| Relocation after handover | no | no | Yes(first select default AMF, then it may be reallocated to the final dedicated AMF ) | no | No | +| NOTE: The "Idle" in the table means the Idle state mobility. The "Connected" in the table means the Connected state mobility. | | | | | | + +None of the listed solutions avoids the need for default 5GS default NF resources while complying to assumptions for the key issue. The solution 2.1 complies with the assumptions and it has limited impacts, but the solution adds some delay to the HO procedure and while it avoids default V-SMF resources it does not avoid default AMF resources. + +# 8 Conclusions + +## 8.1 Conclusions for key issue #1 - Mutually exclusive access to Network Slices + +Editor's note: For the Key Issue#1, Mutually exclusive access to Network Slices, the conclusions of the study and the resulting normative specifications should describe whether and how the following aspects are covered: + +- Whether the standard support the possibility for a Network Slice (S-NSSAI) to be associated to more than one group of Network Slices for which the access to the group of Network Slices are Mutually Exclusive from each other. +- Whether it is possible to deploy an AMF Set which supports Network Slices that are mutually exclusive from each other. + +Editor's note: START of INTERIM Table for evaluation. + +| Key attributes | Approach 1 (Soln 3,4,7) | Approach 2+3 (Soln 2+5) | +|------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Handling of UE requesting incompatible slices | New cause code is needed for rel-16 to signal that some S-NSSAIs are rejected due to incompatibility | The AMF uses existing rel-15 procedures. | +| How is the UE aware of compatibility among S-NSSAIs so it forms a correct Requested NSSAI from the outset. | The CN configures the UE with information that the UE uses to assess whether a S-NSSAI is compatible with other S-NSSAIs on the configured NSSAI.
The UE shall have the same per S-NSSAI compatibility information as the CN, so it can locally (e.g. by local MMI interaction outside the scope of 3GPP) form a compatible and acceptable by the user set of requested S-NSSAIs before it is sent to the network. | The UE is preconfigured with method outside the scope of 3GPP if needed. Otherwise, can sort S-NSSAIs in priority order. | +| How does the Serving PLMN understand the requested S-NSSAIs are compatible | Identify compatibility as a subscription attribute of the S-NSSAI so roaming partners and a PLMN can define which S-NSSAIs are compatible and map these to the Allowed NSSAI provided by NSSF to AMF or by an AMF, even if the AMF supports more S-NSSAIs the UE also subscribes to. In other words, the incompatibility among slices should not impose AMF Set deployment constraints. | AMF sets are deployed to match each and every compatibility groups. | +| Compatibility between UE and network | The UE signals to the network whether it support Mutually incompatible slices handling. If the UE does not support incompatible slices handling the UE is configured only with compatible Slices.
The subscription information shall include a basic set of compatible Network Slices S-NSSAIs to be used if the UE the subscriber uses does not signal support of mutually incompatible slices. | It is assuming using rel-15 compliant UE and Rel-15 compliant network | +| Support in roaming to PLMNs that are not upgraded to support handling of incompatible slices | The subscription information sent to PLMNs of roaming partners which do not support incompatible slices handling shall only contain mutually compatible Network Slices S-NSSAIs. | As per Rel-15 The deployment of the VPLMN has to match requirements from HPLMN as per an SLA (i.e. the VPLMN deploys AMF Sets that satisfy the SLA for compatibility Groups of the inbound roamers) | + +Editor's note: END of INTERIM Table for evaluation. + +### 8.1.1 Enhancements for change of a set of Network Slices + +It is recommended to, during normative phase, address the issue of how the UE performs a change of S-NSSAIs in the Requested NSSAI e.g. whether the UE does it always from CM-IDLE or also from CM-CONNECTED. + +## 8.2 Conclusions for key issue #2 - Enabling interworking for slicing between EPC and 5GC + +Connected Mode: + +- The solution 2.1 is recommended as basis for normative specifications. + +NOTE: It is assumed that ETSUN will develop mechanisms to allow re-selection of V-SMFs which can be re-used for re-selecting a V-SMF dedicated to a Network Slice. + +Idle Mode: + +- To support Rel-15 UE, the AMF may reselect a V-SMF based on S-NSSAI received from PGW-C+SMF. For the V-SMF reallocation, the same mechanism defined at the ETSUN can be reused. + +## 8.3 Conclusions for key issue #3 - Access to specific Network Slices authorized and authenticated through additional User Identifiers + +For KI#3 it is concluded that Solution in clause 6.3.2 shall be the basis of normative work. + +**Editor's note:** Solution 6.3.2 has an open issue that needs resolution in normative phase with CT WG1 interactions. Base on the outcome of these interactions it will be possible to update the procedure, but the guiding principle is that this is based on AMF-UE interaction with no SMF interaction. + +# Annex A: Change history + +| Change history | | | | | | | | | +|----------------|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----|-----|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2018-04 | SA2#127 | S2-183922 | - | - | - | TR skeleton (approved in S2-183922) | | 0.0.0 | +| 2018-04 | SA2#127 | S2-183921
S2-183923
S2-184594 | - | - | - | S2-183921
S2-183923
S2-184594 | | 0.1.0 | +| 2018-06 | SA2#127
bis | S2-186275
S2-186276 | | | | S2-186275
S2-186276 | | 0.2.0 | +| 2018-07 | SA2#128 | S2-186450
S2-187247
S2-187248
S2-187249
S2-187288
S2-187251 | | | | S2-186450
S2-187247
S2-187248
S2-187249
S2-187288
S2-187251 | | 0.3.0 | +| 2018-07 | SA2#128 | S2-187177
S2-187178
S2-187179
S2-187180 | | | | S2-187177
S2-187178
S2-187179
S2-187180 | | 0.4.0 | +| 2018-08 | SA2#128
bis | S2-188410
S2-188471
S2-188472
S2-188486
S2-188414
S2-188485
S2-189004
S2-188484
S2-188222
S2-188483
S2-188317
S2-189056 | | | | S2-188410
S2-188471
S2-188472
S2-188486
S2-188414
S2-188485
S2-189004
S2-188484
S2-188222
S2-188483
S2-188317
S2-189056 | | 0.5.0 | +| 2018-10 | SA2#129 | S2-1810324
S2-1810724
S2-1811059
S2-1811060
S2-1811168
S2-1811169
S2-1811170
S2-1811171
S2-1811199
S2-1811200
S2-1811205
S2-1811206
S2-1811445
S2-1811598
S2-1811599
S2-1811600 | | | | S2-1810324
S2-1810724
S2-1811059
S2-1811060
S2-1811168
S2-1811169
S2-1811170
S2-1811171
S2-1811199
S2-1811200
S2-1811205
S2-1811206
S2-1811445
S2-1811598
S2-1811599
S2-1811600 | | 0.6.0 | +| 2018-12 | SA2#129
bis | S2-1812153
S2-1812819
S2-1813209
S2-1813210
S2-1813354
S2-1813356
S2-1813360
S2-1813380 | | | | S2-1812153
S2-1812819
S2-1813209
S2-1813210
S2-1813354
S2-1813356
S2-1813360
S2-1813380 | | 0.7.0 | +| 2018-12 | SP#82 | SP-181103 | - | - | - | MCC editorial update for presentation to TSG SA#82 | | 1.0.0 | +| 2018-12 | SP#82 | - | - | - | - | MCC editorial update for publication after approval at TSG SA#82 (Release 16) | | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23778/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/Rel-16/23_series/23778/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d08025ee3a975e27f84e3050738c17a7a681e2d --- /dev/null +++ b/marked/Rel-16/23_series/23778/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26ffddf6967e29df3eb4188db1546911b5db5475e125563d69121c1b4cb9b2f5 +size 125060 diff --git a/marked/Rel-16/23_series/23778/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23778/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf67db394be6e752e5e28f413aefeb026066f97e --- /dev/null +++ b/marked/Rel-16/23_series/23778/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06295ec32aa3c98e98e3fa647f927f77fd1d60cfa30df36060a3d02b4c35f628 +size 31932 diff --git a/marked/Rel-16/23_series/23778/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23778/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7009bc5010363b1cdb0ffe413c0ac99ffdd8bc44 --- /dev/null +++ b/marked/Rel-16/23_series/23778/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35aca6286a112ea71f300af4b92fde716adc7ab4306c15437664f5b121a33370 +size 117463 diff --git a/marked/Rel-16/23_series/23778/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23778/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddf15688dbae4acf32816d60dc161a5abf3d79bf --- /dev/null +++ b/marked/Rel-16/23_series/23778/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d34d10e88ef7702cc6dbfe6904ab151e502244dcd57619707920a7e8b17ade56 +size 58893 diff --git a/marked/Rel-16/23_series/23778/77464a47f104d0d647b2414591137b64_img.jpg b/marked/Rel-16/23_series/23778/77464a47f104d0d647b2414591137b64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db43dc58735a9bea59b65e297b313f98d79e0ea2 --- /dev/null +++ b/marked/Rel-16/23_series/23778/77464a47f104d0d647b2414591137b64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9064a1f7c31bb87c89cfd7d5f7889790d0cbbd407593dc8313d6ad43ba257af5 +size 43825 diff --git a/marked/Rel-16/23_series/23778/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/23_series/23778/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa2cedda86615229b4c8a7f1938df86990c91cfe --- /dev/null +++ b/marked/Rel-16/23_series/23778/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52c8082569856f9ba63340959354c5ddd3c830a2a17f60799691d903bc70a730 +size 148285 diff --git a/marked/Rel-16/23_series/23778/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23778/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e904ba52b9c2af41e8a64fcb316d7a9808c017e4 --- /dev/null +++ b/marked/Rel-16/23_series/23778/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92ff6bc6bbcb6412bc7a86d79648d23ba6abb0ecb31c9bee78985170aa010d2d +size 71445 diff --git a/marked/Rel-16/23_series/23778/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/Rel-16/23_series/23778/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd57c19d1e92bdb3b6acd8ea5492b999345710e9 --- /dev/null +++ b/marked/Rel-16/23_series/23778/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:388e00c39a18bb24f356f3ff2c7f12d58e885f7506ab2bd59d4cbb345cc84f33 +size 35811 diff --git a/marked/Rel-16/23_series/23778/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23778/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5015c312fe9d7a8ca35e7a00eaa1b74adf89dee7 --- /dev/null +++ b/marked/Rel-16/23_series/23778/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c12620bdb59c92fc5fca2737ce9f7dc8e7463046b354a59922a12eb121b8080a +size 138005 diff --git a/marked/Rel-16/23_series/23778/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/marked/Rel-16/23_series/23778/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d1704d3745c99a83b38e7b5c18ee71c51cc2a22 --- /dev/null +++ b/marked/Rel-16/23_series/23778/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5704349d1e6a00734fa216e643c5d08f679f0b890f3f8713538a14182d52d4b +size 121453 diff --git a/marked/Rel-16/23_series/23778/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23778/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f51cddaa970c7db4e66bde41be34366546f7be2c --- /dev/null +++ b/marked/Rel-16/23_series/23778/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc7f2bdcd6ca3fa2cd47cd689f7d94f317f84b15191e940b054631355ef839e9 +size 75882 diff --git a/marked/Rel-16/23_series/23778/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23778/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b7802ac4fddb9572ec82ed4f2083ca7016d6541 --- /dev/null +++ b/marked/Rel-16/23_series/23778/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eee4c5be0373b970a031cf15f53d082b944ef648cd74f3a84cc5fff681316fd3 +size 134508 diff --git a/marked/Rel-16/23_series/23778/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/Rel-16/23_series/23778/df82d77a0d2637cbf2da9ea920a554fa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66ed467b1620b1c0c34226ef8b2fcf49ade9d864 --- /dev/null +++ b/marked/Rel-16/23_series/23778/df82d77a0d2637cbf2da9ea920a554fa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73ee1f967d9024b35aa9c60aac7042d2297b2d9f151e6d19cbcc43de4d6e8b00 +size 129725 diff --git a/marked/Rel-16/23_series/23778/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23778/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4dd3489f82873da6b6d254b4b5b609fa7bd49e7b --- /dev/null +++ b/marked/Rel-16/23_series/23778/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ce509e0ced8e0fd1f4ea9ad586dabeee8aab5911071f97bc8eff0c34e8820b3 +size 36204 diff --git a/marked/Rel-16/23_series/23778/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23778/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8be40266bbdee7b07f4b6c6ddaa1f88bb944d091 --- /dev/null +++ b/marked/Rel-16/23_series/23778/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:000b41694edb57e5911c4cfa7a17ab982dfa8ba3a4131929cfd4bd9dde54ce80 +size 93008 diff --git a/marked/Rel-16/23_series/23778/raw.md b/marked/Rel-16/23_series/23778/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8f16d1687ce73ad8bac947afecf45a1ddca056d3 --- /dev/null +++ b/marked/Rel-16/23_series/23778/raw.md @@ -0,0 +1,957 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 Key issues ..... | 7 | +| 4.1 IOPS related key issues..... | 7 | +| 4.1.1 Key issue 2-1 MC system configuration data synchronization ..... | 7 | +| 4.1.1.1 Description..... | 7 | +| 4.1.2 Key issue 2-2 MC service client configuration for IOPS..... | 8 | +| 4.1.2.1 Description..... | 8 | +| 4.1.3 Key issue 2-3 on how to handle an MC UE switching to/from an IOPS MC system..... | 8 | +| 4.1.3.1 Description..... | 8 | +| 4.1.4 Key issue 2-4 IOPS architecture..... | 8 | +| 4.1.4.1 Description..... | 8 | +| 4.1.5 Key issue 2-5 on ongoing communication continuity when backhaul is recovered ..... | 9 | +| 4.1.5.1 Description..... | 9 | +| 4.1.6 Key issue 2-6 on support MBMS in IOPS ..... | 9 | +| 4.1.6.1 Description..... | 9 | +| 4.1.7 Key issue 2-7 on determining a list of MC users connected to the IOPS MC system ..... | 10 | +| 4.1.7.1 Description..... | 10 | +| 5 Architectural requirements..... | 10 | +| 5.1 IOPS related requirements ..... | 10 | +| 6 Solutions..... | 11 | +| 6.1 Solution 1: UE and user data synchronization ..... | 11 | +| 6.1.1 Description ..... | 11 | +| 6.1.2 Impacts on existing nodes and functionality ..... | 13 | +| 6.1.3 Solution evaluation..... | 13 | +| 6.2 Solution 2: Functional model for IOPS based on a switchable standalone MC system ..... | 13 | +| 6.2.1 Description ..... | 13 | +| 6.2.2 Solution evaluation..... | 14 | +| 6.3 Solution 3: Functional model for IOPS based on an always-on partner MC system..... | 14 | +| 6.3.1 Description ..... | 14 | +| 6.3.2 Solution evaluation..... | 15 | +| 6.4 Solution 4: Functional model for IOPS MC system based on only IP connectivity ..... | 15 | +| 6.4.1 Description ..... | 15 | +| 6.4.1.1 General..... | 15 | +| 6.4.1.2 IOPS-based discovery procedure..... | 17 | +| 6.4.1.3 IOPS-based IP connectivity communication ..... | 19 | +| 6.4.2 Impacts on existing nodes and functionality ..... | 23 | +| 6.4.3 Solution evaluation..... | 23 | +| 6.5 Solution 5: Functional model for IOPS based on an always-on participating server ..... | 23 | +| 6.5.1 Description ..... | 23 | +| 6.5.2 Solution evaluation..... | 25 | +| 6.6 Solution 6: Procedure for switching from the primary MC system to an IOPS MC system ..... | 25 | +| 6.6.1 Description ..... | 25 | +| 6.6.2 Procedure..... | 25 | +| 6.6.3 Solution evaluation..... | 27 | +| 6.7 Solution 7: IOPS notification to MC UEs..... | 27 | +| 6.7.1 Description ..... | 27 | +| 6.7.2 Impacts on existing nodes and functionality ..... | 28 | + +| | | | +|----------|-----------------------------------------------------------------------------------------|----| +| 6.7.3 | Solution evaluation ..... | 28 | +| 6.8 | Solution 8: MC service client configuration for IOPS ..... | 29 | +| 6.8.1 | Description ..... | 29 | +| 6.8.2 | Solution evaluation ..... | 29 | +| 6.9 | Solution 9: Functionality for determining the MC user registration status in IOPS ..... | 29 | +| 6.9.1 | Description ..... | 29 | +| 6.9.2 | Solution evaluation ..... | 32 | +| 7 | Overall evaluation ..... | 33 | +| 7.1 | General ..... | 33 | +| 7.2 | Architecture evaluation ..... | 33 | +| 7.3 | Key issue and solution evaluation ..... | 34 | +| 8 | Conclusions ..... | 35 | +| Annex A: | Change history ..... | 36 | + +# --- Foreword + +This Technical Report has been produced by the 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. + +# --- Introduction + +Mission critical services can be provided even in the case of a backhaul failure or a nomadic EPS deployment based on the availability of Isolated E-UTRAN Operations for Public Safety (IOPS). IOPS provides local connectivity to the public safety users that are within the communication range of the radio base station(s) that supports the IOPS mode of operation, as described in 3GPP TS 23.401 Annex K [10]. + +This study focuses on identifying application architecture solutions needed to support mission critical services during the IOPS mode of operation. + +# --- 1 Scope + +This technical report is a study of mission critical service access aspects. The present document identifies architecture enhancements needed to support mission critical services delivered over IOPS, based on the stage 1 requirements, including 3GPP TS 22.179 [2], 3GPP TS 22.280 [3], 3GPP TS 22.281 [4], 3GPP TS 22.282 [5] and 3GPP TS 22.346 [6]. + +This document provides recommendations for normative work. + +# --- 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1". +- [3] 3GPP TS 22.280: "Mission Critical Services Common Requirements". +- [4] 3GPP TS 22.281: "Mission Critical Video services". +- [5] 3GPP TS 22.282: "Mission Critical Data services". +- [6] 3GPP TS 22.346: "Isolated Evolved Universal Terrestrial Radio Access Network (E-UTRAN) operation for public safety; Stage 1". +- [7] 3GPP TS 23.280 "Common functional architecture to support mission critical services; Stage 2" +- [8] 3GPP TS 23.282 "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2" +- [9] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2" +- [10] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access" + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**IOPS MC system:** The collection of applications, services and enabling capabilities that provides MC services in an IOPS network. + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.401 [10] apply: + +**Local EPC** +**IOPS network** +**Macro EPC** + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +            + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +IOPS                    Isolated E-UTRAN Operations for Public Safety + +# --- 4 Key issues + +## 4.1 IOPS related key issues + +### 4.1.1 Key issue 2-1 MC system configuration data synchronization + +#### 4.1.1.1 Description + +An MC service operating in an IOPS mode is completely or partly isolated from the network and application infrastructure normally utilized. This requires that MC system configuration data in the IOPS MC system needs to be up to date with MC system configuration data in the primary MC system. The invocation of the MC service in IOPS mode is in most scenarios unpredictable, which also stipulate strong requirements on data synchronization between the IOPS MC system and the primary MC system. + +To define an efficient MC system configuration data synchronization process, the following areas should be further studied: + +- What parts of the MC system configuration data needs to be synchronized between the IOPS MC system and primary MC systems before, during and after operating in IOPS mode. +- Triggers of data synchronizations +- Service limitations due to data synchronization issues + +### 4.1.2 Key issue 2-2 MC service client configuration for IOPS + +#### 4.1.2.1 Description + +IOPS MC system is completely or partly isolated from the network and application infrastructure normally utilized. For the MC service client to access the IOPS MC system, the client shall be configured with access information (e.g. server addresses) of the IOPS MC system. This introduce challenges when configuring MC service clients with access information to all IOPS capable eNBs in a network. + +To define procedures for MC service client and UE configuration of IOPS MC system access data, the following areas should be further studied: + +- What MC service client and UE data are required to be configured for accessing a IOPS MC system. +- How should this configuration be done. +- How to handle migrating users from partner system. +- Any differences from a procedural perspective in IOPS mode due to backhaul failure or limited backhaul or in IOPS mode in nomadic deployments. + +### 4.1.3 Key issue 2-3 on how to handle an MC UE switching to/from an IOPS MC system + +#### 4.1.3.1 Description + +IOPS MC system is completely or partly isolated from the network and application infrastructure normally utilized. When MC users are located within the coverage or in proximity of an eNB in IOPS mode, the MC users may experience an unpredictable user experience, if MC UEs are switching between the IOPS enabled eNB and an eNB that is connected to the primary MC system. + +This issue may be common when the IOPS enabled eNB is a macro site, and there are several smaller cells in the area of the coverage of the macro site. It is important to have a mechanism in place to get an optimize user experience when MC UEs are switching to and from the IOPS MC system. + +Further study is needed to: + +- Optimize the benefit for mission critical functionality to MC UEs in overlapping primary MC system and IOPS MC system operational areas. + +### 4.1.4 Key issue 2-4 IOPS architecture + +#### 4.1.4.1 Description + +The IOPS MC system can be used through a local EPS both during backhaul failure as well as in nomadic deployment (e.g. in cell on wheel configuration). However, the IOPS MC system may be accessed by an MC UE both during IOPS operation mode and during non IOPS mode (i.e. this system may be operational already before entering IOPS mode) and in that scenario through the primary EPS or other access network. To support this, different architectural requirements and solutions should be evaluated. + +Further study is needed to: + +- Evaluate different architecture alternatives for an IOPS MC system +- Define the functional model used in the IOPS MC system. +- Conclude on architectural requirements for the IOPS MC system. + +### 4.1.5 Key issue 2-5 on ongoing communication continuity when backhaul is recovered + +#### 4.1.5.1 Description + +When the backhaul of an eNB to Macro EPC is broken, the eNB enters IOPS mode and connects to the Local EPC, and the MC users served by this eNB will connect to the IOPS MC system. + +After some time, the backhaul is recovered, then this eNB switches back to normal mode and re-connects to the Macro EPC, and the users served by this eNB will re-connect to the Primary MC system. This scenario is illustrated in Figure 1. At the transition time, there is a call ongoing in the IOPS MC system. Re-connecting to the Primary MC system will likely cause the termination of the ongoing communication in the IOPS MC system. However, it is beneficial to minimize the disruption to ongoing communication during the transition. + +![Diagram illustrating ongoing communication continuity when backhaul is recovered. The diagram shows two states: before and after the backhaul is recovered. In the 'before' state (left), the IOPS MC system (controlling role) is disconnected from the Primary MC system (participating role) by a red 'X'. The Local EPC is connected to the IOPS MC system, and the Macro EPC is connected to the Primary MC system. The eNB is in IOPS mode, connected to the Local EPC, and Group A members are connected to the eNB. The Macro EPC is in Normal mode, connected to the eNB. A green arrow labeled 'Backhaul is recovered' points to the 'after' state. In the 'after' state (right), the IOPS MC system (controlling role) is connected to the Primary MC system (participating role) by a green checkmark. The Local EPC is connected to the IOPS MC system, and the Macro EPC is connected to the Primary MC system. The eNB is in Normal mode, connected to the Macro EPC, and Group A members are connected to the eNB. The Local EPC is in Normal mode, connected to the eNB.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +Diagram illustrating ongoing communication continuity when backhaul is recovered. The diagram shows two states: before and after the backhaul is recovered. In the 'before' state (left), the IOPS MC system (controlling role) is disconnected from the Primary MC system (participating role) by a red 'X'. The Local EPC is connected to the IOPS MC system, and the Macro EPC is connected to the Primary MC system. The eNB is in IOPS mode, connected to the Local EPC, and Group A members are connected to the eNB. The Macro EPC is in Normal mode, connected to the eNB. A green arrow labeled 'Backhaul is recovered' points to the 'after' state. In the 'after' state (right), the IOPS MC system (controlling role) is connected to the Primary MC system (participating role) by a green checkmark. The Local EPC is connected to the IOPS MC system, and the Macro EPC is connected to the Primary MC system. The eNB is in Normal mode, connected to the Macro EPC, and Group A members are connected to the eNB. The Local EPC is in Normal mode, connected to the eNB. + +**Figure 4.2.5.1-1: Ongoing communication continuity when backhaul is recovered** + +Further study is needed: + +- Understand how communications are re-established in the Primary MC system including how group members join group communications in progress in the Primary MC system; +- How to handle call collisions if calls are ongoing in the same group in both the Primary MC system and IOPS MC system; +- How the ongoing communication continuity can be achieved when transitioning from IOPS mode to Macro mode. + +### 4.1.6 Key issue 2-6 on support MBMS in IOPS + +#### 4.1.6.1 Description + +eMBMS is an important feature for mission critical service to improve transmission efficiency. The eMBMS principle that an eNB is served by a single MCE and the different MCE deployments (i.e., distributed MCE architecture and centralized) in 3GPP TS 36.300 may impact the eMBMS usage in IOPS MC system. + +IOPS MC system is based on IOPS network. The support of eMBMS is up to local operator policy and configuration as indicated in TS 23.401 : + +*'The support by IOPS network entities of S1-flex and/or eMBMS is up to local operator policy and configuration.'* + +Further study is needed: + +- How to support MBMS feature in IOPS network; +- How the MCE deployments will impact the eMBMS usage in IOPS MC system; and +- How to minimize the delay in setting up eMBMS bearer when transitioning to IOPS. + +### 4.1.7 Key issue 2-7 on determining a list of MC users connected to the IOPS MC system + +#### 4.1.7.1 Description + +When the IOPS operation is initiated due to a backhaul failure, it becomes a key issue for the MC users being served by the IOPS system to get informed about which other MC users are also registered within the IOPS system. For the implementation of a MC service system connected to the IOPS system, the MC users within the same MC service group can get informed about the affiliation status of others MC users in the group. However, it may not be possible for an MC service user to determine which other MC service users are also registered to the IOPS MC system during the IOPS operation, e.g. a list of users which have indicated that their registration status cannot be shared with other users in IOPS. + +As described in the IOPS requirements in TS 22.346, the IOPS system shall be capable of informing served MC users about which other MC users are also served by the IOPS system. Thus, the MC users are notified of which other MC users they may perform a MC service communication with. + +Further study is needed to identify how to support determining a list of MC users connected to the IOPS MC system after a backhaul failure has occurred. + +# --- 5 Architectural requirements + +## 5.1 IOPS related requirements + +This subclause defines the architectural and functional requirements related to MC services in IOPS mode. + +[MCSAA-REQ-1] The following MCPTT features shall be supported in IOPS + +- MCPTT group call +- MCPTT emergency call +- MCPTT private call + +[MCSAA-REQ-2] The following MCData features shall be supported in IOPS + +- MCData short data service + +**Editor's Note:** The list of features may be updated in the future. + +[MCSAA-REQ-3] The MC services shall be supported in IOPS with no backhaul connectivity. + +NOTE: Annex K in TS 23.401 does not specify any deployment option with limited backhaul. IOPS with limited backhaul is therefore subject for further work in SA2. + +# --- 6 Solutions + +## 6.1 Solution 1: UE and user data synchronization + +### 6.1.1 Description + +This solution addresses part of key issue 2-1 MC system configuration data synchronization. In the MC service configuration procedure as described in 3GPP TS 23.280 [7] subclause 10.1, the UE retrieves the initial UE configuration after the bootstrap. After the user authentication, the UE retrieves: + +- UE configuration +- MC service user profile configuration +- Group configuration + +The solution described in this clause covers the above configuration data with one exception. The Group configuration that resides in the group management system is not synchronized with this solution. + +It is assumed that the initial UE configuration (e.g. APN details) can be kept as is and that there is no need to synchronize this data with the IOPS MC system. The initial UE configuration is provisioned by offline methods over reference point CSC-11. + +It is assumed that the UE configuration data (e.g. MCPTT server URI) is of static nature and can be synchronized at system start up or reboot operation. + +The MC service user profile data is dynamic data (e.g. contact lists) and may be updated daily which makes the synchronization of the data a challenge. + +This solution proposes to synchronize the MC service user profile with the current (or IOPS tagged) profile that is currently active and downloaded in the MC service client. The procedure in figure 6.1.1-1 updates the MC service user profile for the MC service user in the IOPS MC system. + +With this solution the MC service client is used to provide synchronization of the user data stored in the primary configuration management server with the configuration management server in the IOPS MC system. + +Pre-conditions: + +- The user must be defined in the IOPS MC system. +- The MC service client is authenticated and authorized by the IOPS MC system. + +![Sequence diagram showing the interaction between a Configuration management client and a Configuration management server within an IOPS MC System. The client triggers the process, sends a request, and receives a response, while the server stores the data.](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +``` + +sequenceDiagram + participant Client as Configuration management client + participant Server as Configuration management server + Note right of Server: IOPS MC System + + Note left of Client: 1. Triggered to store current MC service user profile data + Client->>Server: 2. Create or update MC service user profile data request + Note right of Server: 3. Store MC service user profile data + Server-->>Client: 4. Update MC service user profile data response + +``` + +Sequence diagram showing the interaction between a Configuration management client and a Configuration management server within an IOPS MC System. The client triggers the process, sends a request, and receives a response, while the server stores the data. + +**Figure 6.1.1-1: MC service user updates MC service user profile data to the MC IOPS system** + +1. The configuration management client is triggered (e.g. by detecting an MC IOPS system) to store or update the MC service user profile data on the configuration management server in the MC IOPS system. + +NOTE: Step 1 could be triggered by the configuration management server. + +2. The configuration management client sends create or update MC service user profile data request to the configuration management server, which includes the MC service user profile data to be updated. +3. The configuration management server stores the received MC service user profile data. +4. The configuration management server sends update MC service user profile data response to the configuration management client to confirm the MC service user profile data update is complete. + +To avoid user data conflicts between IOPS MC system and the primary MC system, changes to MC service user profiles should not be allowed during IOPS mode by the IOPS MC system. + +There is one disadvantage of this solution. Some parameters in the MC service user profile are not known by the UE. It is proposed to not use these parameters in an IOPS MC system. In the current version of 3GPP TS 23.379 [9] the following parameters are not downloaded to the UE: + +- User profile status +- Authorised to create and delete aliases of an MCPTT User and its associated user profiles. +- Maximum number of simultaneously received group calls (Nc5) +- Priority of the user for initiating/receiving calls +- Authorisation to create a group-broadcast group +- Authorisation to create a user-broadcast group + +- Authorisation to provide location information to other MCPTT users on a call when talking +- Authorisation of an MCPTT user to request a list of which groups an MCPTT user has affiliated to +- Authorisation to change affiliated groups of other specified user(s) +- Authorisation to recommend to specified user(s) to affiliate to specific group(s) +- Authorisation to query whether MCPTT User is available for private calls +- Authorisation to restrict provision of private call set-up failure cause to the caller +- Authorisation of an MCPTT user to cancel an emergency alert on any MCPTT UE of any MCPTT user +- Authorisation for a MCPTT user to enable/disable an MCPTT user +- Authorisation for an MCPTT user to (permanently /temporarily) enable/disable a UE +- Authorisation to revoke permission to transmit +- Maximum number of simultaneous transmissions received in one group call for override (N7) +- Authorised to interrogate the functional alias(es) active for another MCPTT user +- Authorised to take over a functional alias from another MCPTT user + +Editor's note: How to handle the above parameters is FFS. + +### 6.1.2 Impacts on existing nodes and functionality + +Editor's Note: Capture impacts on existing 3GPP nodes and functional elements. + +### 6.1.3 Solution evaluation + +This solution does not prevent offline synchronization between MCPTT user databases or configuration management systems in primary MC system and IOPS MC system. The IOPS MC system has to validate service requests made by the MC UE against configuration data provided by the MC UE, which is a security concern as the system cannot prove whether the MC UE is requesting a service to which it is entitled. + +## 6.2 Solution 2: Functional model for IOPS based on a switchable standalone MC system + +### 6.2.1 Description + +One solution for the architecture of IOPS MC system is to deploy a standalone system that is in standby during normal operations. The functional model of the IOPS MC system is illustrated in figure 6.2.1-1. The functional model includes the necessary functional entities for MC services in IOPS. The description of each functional entities is found in 3GPP TS 23.379 [9], 3GPP TS 23.280 [7] and 3GPP TS 23.282 [8]. + +![Functional model for an IOPS MC system during IOPS mode. The diagram shows a central 'Common services core' containing five servers: Group management server, Configuration management server, Identity management server, Key management server, and Location management server. These servers are connected to an 'MC service UE' on the right via reference points CSC-2, CSC-4, CSC-1, CSC-8, and CSC-14 respectively. The UE contains 'MC service clients' (MCPTT, MCData, MCVideo). On the left, 'MC service user database(s)' are connected to the servers via CSC-13, CSC-9, and CSC-15. At the top, 'MC service servers' (MCPTT, MCData, MCVideo) are connected to the core via CSC-3 and CSC-5. A 'Local EPC' is shown on the right side of the UE.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Functional model for an IOPS MC system during IOPS mode. The diagram shows a central 'Common services core' containing five servers: Group management server, Configuration management server, Identity management server, Key management server, and Location management server. These servers are connected to an 'MC service UE' on the right via reference points CSC-2, CSC-4, CSC-1, CSC-8, and CSC-14 respectively. The UE contains 'MC service clients' (MCPTT, MCData, MCVideo). On the left, 'MC service user database(s)' are connected to the servers via CSC-13, CSC-9, and CSC-15. At the top, 'MC service servers' (MCPTT, MCData, MCVideo) are connected to the core via CSC-3 and CSC-5. A 'Local EPC' is shown on the right side of the UE. + +**Figure 6.2.1-1: Functional model for an IOPS MC system during IOPS mode** + +The following parts have been removed in the IOPS MC system functional entities + +- Migration management server +- Reference points to other MC services servers, group management server, configuration management server. + +### 6.2.2 Solution evaluation + +This solution would provide a minor deviation from the functional model in a primary MC system. A few functional entities and reference points can be removed since they are not needed in the IOPS MC system. User and service data synchronization must be performed in all nodes that include permanent data. + +The storage of duplicate configuration and security parameters in the IOPS MC system may cause security concerns. + +## 6.3 Solution 3: Functional model for IOPS based on an always-on partner MC system + +### 6.3.1 Description + +One solution for the architecture of IOPS MC system is to have a fully functional and active MC system used during normal operations as a partner system to which the users may migrate based on MC service provider policies. The functional model of the IOPS MC system is illustrated in figure 6.3.1-1. For simplicity some of the internal reference points are not illustrated in the figure. + +![Figure 6.3.1-1: Functional model for an IOPS MC system based on migration of users. The diagram shows two main systems: IOPS MC System and Primary MC System. The IOPS MC System includes an MC service UE with clients (MCPTT, MCData, MCVideo), connected via CSC-3 to MC service servers (MCPTT, MCData, MCVideo). These servers are connected to a 'Common services core' (dashed box) containing Group, Configuration, Migration, Identity, Key, and Location management servers. The Primary MC System has a similar structure. Clients in the IOPS MC System (Group, Configuration, Identity, Key, Location) are connected to the Local EPS and then to the servers in the Common services core via reference points CSC-2, CSC-4, CSC-13, CSC-1, CSC-8, and CSC-14. Servers in the Common services core are interconnected via CSC-16, CSC-17, and CSC-18. The Primary MC System's servers are connected to the EPS and then to the clients via the same reference points.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Figure 6.3.1-1: Functional model for an IOPS MC system based on migration of users. The diagram shows two main systems: IOPS MC System and Primary MC System. The IOPS MC System includes an MC service UE with clients (MCPTT, MCData, MCVideo), connected via CSC-3 to MC service servers (MCPTT, MCData, MCVideo). These servers are connected to a 'Common services core' (dashed box) containing Group, Configuration, Migration, Identity, Key, and Location management servers. The Primary MC System has a similar structure. Clients in the IOPS MC System (Group, Configuration, Identity, Key, Location) are connected to the Local EPS and then to the servers in the Common services core via reference points CSC-2, CSC-4, CSC-13, CSC-1, CSC-8, and CSC-14. Servers in the Common services core are interconnected via CSC-16, CSC-17, and CSC-18. The Primary MC System's servers are connected to the EPS and then to the clients via the same reference points. + +**Figure 6.3.1-1: Functional model for an IOPS MC system based on migration of users** + +In this functional model the users may be migrated based on the UE location and the MC service provider policy, and by that receive the MC services from the IOPS MC system. This takes place prior that the IOPS mode is triggered by backhaul failure. + +### 6.3.2 Solution evaluation + +This solution provides a minor deviation from the functional model in a primary MC system. A few functional entities and reference points can be removed since they are not needed in the IOPS MC system. The users using the IOPS MC system need to migrate to the IOPS MC system prior to the transition to IOPS mode. User and service data synchronization is limited to users that have migrated to the IOPS MC system prior to a backhaul failure. There may be an issue in providing service to users who are not configured in the IOPS MC system, or who have not migrated to the IOPS MC system prior to the backhaul failure as their configuration data will not be accessible during the backhaul failure. This solution is not the preferred solution in a nomadic deployment. + +## 6.4 Solution 4: Functional model for IOPS MC system based on only IP connectivity + +### 6.4.1 Description + +#### 6.4.1.1 General + +This solution addresses key issue 2-4. One functional model for an IOPS MC system is to only utilize the IP connectivity that the local EPS provides, and by that only provide that MC services from the UEs. + +The functional model of the IOPS MC system based on only IP connectivity is based on the off-network functional model and it is illustrated in figure 6.4.1.1-1. + +![Functional model for an IOPS MC system based on only IP connectivity. The diagram shows two User Equipment (UE) blocks, UE1 and UE2, connected via a central 'Local EPS' block. Each UE contains an 'Application plane' and a 'Signalling control plane'. The Application plane includes a Media mixer, Floor control server, Floor participant, MC service client, Configuration management client, and Group management client. The Signalling control plane includes a Signalling user agent client. A green line represents Media traffic, and a red line represents Signalling traffic, both passing through the Local EPS.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +The diagram illustrates the functional model for an IOPS MC system based on only IP connectivity. It features two User Equipment (UE) blocks, UE1 and UE2, connected via a central 'Local EPS' block. Each UE contains an 'Application plane' and a 'Signalling control plane'. The Application plane includes a Media mixer, Floor control server, Floor participant, MC service client, Configuration management client, and Group management client. The Signalling control plane includes a Signalling user agent client. A green line represents Media traffic, and a red line represents Signalling traffic, both passing through the Local EPS. + +Functional model for an IOPS MC system based on only IP connectivity. The diagram shows two User Equipment (UE) blocks, UE1 and UE2, connected via a central 'Local EPS' block. Each UE contains an 'Application plane' and a 'Signalling control plane'. The Application plane includes a Media mixer, Floor control server, Floor participant, MC service client, Configuration management client, and Group management client. The Signalling control plane includes a Signalling user agent client. A green line represents Media traffic, and a red line represents Signalling traffic, both passing through the Local EPS. + +**Figure 6.4.1.1-1: Functional model for an IOPS MC system based on only IP connectivity** + +In this functional model the users do not obtain the MC services from a local MC service server. The local EPS network only provide IP connectivity. The configuration management client and the group management client needs must retrieve the configuration from the configuration management server and the group management server over CSC-4 and CSC-2 while the users are connected to the primary MC system. + +This functional model allows communication between the MC users via the IOPS system, where the MC services are provided by the MC service clients and the IOPS system only relays the IP traffic. On the application layer most of the off-network procedures could be reused or taken as a reference. This type of MC communication in IOPS is defined as the IOPS-based IP connectivity communication. + +**Editor's note: It is FFS to define which procedures and protocols are utilized for the IOPS-based IP connectivity communication** + +Therefore, as part of this solution, an IOPS MC connectivity status function is implemented to be connected to the local EPC of the IOPS system to support discovering all MC users being served by the IOPS system. This procedure is defined as the IOPS-based discovery procedure. Also, an IOPS packet distribution function is implemented together with the IOPS MC connectivity status function and with connectivity to the IOPS system to handle IP packets received from the MC UEs and targeting other MC UEs being served by the IOPS system. In other words, the IOPS packet distribution function supports the IOPS-based IP connectivity communication by performing the IP relaying. The IP packets to be relayed contain the MC service related application data such as signalling control data or application data (control and media) generated by the MC service clients based on the IOPS-based IP connectivity communication. Figure 6.4.1.1-2 depicts the two new application functional entities in the IOPS MC system to provide IP connectivity to the MC users being served by the system. These new functional entities and related procedures are described further below. + +![Diagram of IOPS MC system based on only IP connectivity. At the top, a box labeled 'IOPS MC system' contains two server icons: 'IOPS MC connectivity status function' and 'IOPS packet distribution function'. Below this box is a 'Local EPC' box. A dashed red line represents a network boundary. Inside this boundary, there are four mobile user equipment (UE) icons labeled 'MC UE1', 'MC UE2', 'MC UE3', and 'MC UE4'. Two base station icons are shown; one is connected to the Local EPC and the other is labeled 'IOPS-capable eNB'. MC UE1 and MC UE2 are connected to the first base station, while MC UE3 and MC UE4 are connected to the IOPS-capable eNB.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Diagram of IOPS MC system based on only IP connectivity. At the top, a box labeled 'IOPS MC system' contains two server icons: 'IOPS MC connectivity status function' and 'IOPS packet distribution function'. Below this box is a 'Local EPC' box. A dashed red line represents a network boundary. Inside this boundary, there are four mobile user equipment (UE) icons labeled 'MC UE1', 'MC UE2', 'MC UE3', and 'MC UE4'. Two base station icons are shown; one is connected to the Local EPC and the other is labeled 'IOPS-capable eNB'. MC UE1 and MC UE2 are connected to the first base station, while MC UE3 and MC UE4 are connected to the IOPS-capable eNB. + +**Figure 6.4.1.1-2 IOPS MC system based on only IP connectivity** + +#### 6.4.1.2 IOPS-based discovery procedure + +The IOPS-based discovery procedure is based on the publication, subscription and notification of connectivity information. + +Once the MC UEs are being served by the IOPS system, the MC service clients initiates the discovery procedure by publishing their connectivity information to the IOPS MC connectivity status function. It is assumed that the IOPS MC connectivity status function also includes mechanisms to authenticate and authorize the MC users to register to the IOPS MC system. + +The connectivity information may include some of the MC service configuration data available in the MC service clients when the IOPS mode of operation is initiated. For instance, if a MC user intends to utilize the MCPTT service while connected to the IOPS system, the connectivity information may include the following parameters (described in TS 23.379 Annex A.3 and TS 23.280 Annex A.4): MCPTT user identity (MCPTT ID), list of off-network MCPTT groups for use by an MCPTT user (MCPTT Group ID(s)), and ProSe group IP multicast address per MCPTT Group ID. Also, the connectivity information includes the IP address assigned to the MC UE by the local EPC for the IOPS-based IP connectivity communication (to be based on the IOPS APN). Furthermore, the connectivity information may include a parameter to indicate if the MC user connectivity information is available or not to be shared with other MC users connected to the IOPS system. + +Upon reception of the publish requests, the IOPS MC connectivity status function stores the MC user connectivity information and defines the associated MC users as discovered, i.e. MC users that can be reached by other MC users via the IOPS system. How the received parameters within the connectivity information are managed by the IOPS MC connectivity status function is implementation specific. + +When the MC users are discovered by the IOPS MC connectivity status function, the MC users subscribe to be notified about the connectivity status of other relevant discovered MC users. Relevant MC users can be other MC users connected to the IOPS system or a sub-set of users, e.g., other users which are within the list of users who can be called in private call or users which belong to the same MC service group. + +Based on the received connectivity information, when the IOPS MC connectivity status function identifies that MC users associated to received subscriptions are discovered within the IOPS system, the IOPS MC connectivity status function notifies the MC users about the connectivity status of their relevant MC users, respectively. The connectivity status indicates if the relevant MC users are connected or not to the IOPS system and it provides information about how to establish an IOPS-based IP connectivity communication with other relevant MC users, e.g. the related IP address to communicate with another specific MC user. + +The IOPS MC connectivity status function may periodically request to the discovered MC users to publish their connectivity status. Hence, the IOPS MC connectivity status function is aware of connectivity status changes of the discovered MC users and can notify the MC users with active subscriptions about these changes, respectively. + +Figure 6.4.1.2-1 below describes the IOPS-based discovery procedure considering, as an example, two users, MC user 1 (UE1) and MC user 2 (UE2), where the MC UEs are attached and being served by the IOPS system. The MC users + +publish their connectivity information and the MC user 1 subscribes to receive notifications about the MC user 2 connectivity status. + +![Sequence diagram titled 'IOPS system (IOPS-capable eNB(s), Local EPC)'. Lifelines: MC user 1 (MC service client 1), MC user 2 (MC service client 2), IOPS System, and IOPS MC connectivity status function. The sequence shows: 1. MC service clients initiate the IOPS-based discovery procedure. 2a. MC user 1 publishes connectivity info. 2b. MC user 2 publishes connectivity info. 3. Connectivity info is stored and users discovered. 4a. OK received by MC user 1. 4b. OK received by MC user 2. 5. MC user 1 subscribes for MC user 2. 6. Subscription activated. 7. OK received by MC user 1. 8. NOTIFY MC user 2 connectivity status. 9. MC user 1 notified. 10. OK received by MC user 1.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) + +``` +sequenceDiagram + participant MC user 1 (MC service client 1) + participant MC user 2 (MC service client 2) + participant IOPS System + participant IOPS MC connectivity status function + + Note over MC user 1, MC user 2: The MC UEs are attached and being served by the IOPS system + Note over MC user 1, MC user 2: 1. MC service clients initiate the IOPS-based discovery procedure + MC user 2->>IOPS MC connectivity status function: 2a. PUBLISH of connectivity information + MC user 2->>IOPS MC connectivity status function: 2b. PUBLISH of connectivity information + Note right of IOPS MC connectivity status function: 3. Connectivity information is stored. MC users are discovered + IOPS MC connectivity status function-->>MC user 1: 4a. OK (connectivity information received) + IOPS MC connectivity status function-->>MC user 2: 4b. OK (connectivity information received) + MC user 1->>IOPS MC connectivity status function: 5. SUBSCRIBE (relevant MC user: MC user 2) + Note right of IOPS MC connectivity status function: 6. Subscription is activated + IOPS MC connectivity status function-->>MC user 1: 7. OK (subscription activated) + IOPS MC connectivity status function->>MC user 1: 8. NOTIFY (MC user 2 connectivity status) + Note left of MC user 1: 9. MC user 1 is notified about the MC user 2 connectivity status + MC user 1-->>IOPS MC connectivity status function: 10. OK (notification received) +``` + +Sequence diagram titled 'IOPS system (IOPS-capable eNB(s), Local EPC)'. Lifelines: MC user 1 (MC service client 1), MC user 2 (MC service client 2), IOPS System, and IOPS MC connectivity status function. The sequence shows: 1. MC service clients initiate the IOPS-based discovery procedure. 2a. MC user 1 publishes connectivity info. 2b. MC user 2 publishes connectivity info. 3. Connectivity info is stored and users discovered. 4a. OK received by MC user 1. 4b. OK received by MC user 2. 5. MC user 1 subscribes for MC user 2. 6. Subscription activated. 7. OK received by MC user 1. 8. NOTIFY MC user 2 connectivity status. 9. MC user 1 notified. 10. OK received by MC user 1. + +Figure 6.4.1.2-1: IOPS-based discovery procedure + +- 1. After the MC UEs are attached and being served by the IOPS system, the MC service clients initiate the IOPS-based discovery procedure +- 2. The MC user 1 at the MC service client 1 (2a) and the MC user 2 at the MC service client 2 (2b) publish their connectivity information to the IOPS MC connectivity status function + +3. The IOPS MC connectivity status function stores the connectivity information of each MC user and defines the MC users as discovered +4. The IOPS MC connectivity status function may confirm to the MC service clients the reception of the publish requests. +5. The MC user 1 defines the MC user 2 as a relevant MC user, e.g. because the MC user 2 is within the MC user 1's list of users who can be called in private call, and subscribes to be notified about the connectivity status of the MC user 2. +6. The IOPS MC connectivity status function activates the subscription for the MC user 1. +7. The IOPS MC connectivity status function may confirm to the MC service client 1 the reception of the subscription request. +8. The IOPS MC connectivity status function, based on the received connectivity information, notifies the MC service client 1 about the connectivity status of the MC user 2. The connectivity status indicates that the MC user 2 is connected to the IOPS system and it contains information about how to establish an IOPS-based IP connectivity communication, e.g. the related IP address to communicate with the MC user 2. +9. The MC service client 1 notifies the MC user 1 about the connectivity status of the MC user 2. +10. The MC service client 1 may confirm to the IOPS MC connectivity status function the reception of the notification message. + +#### 6.4.1.3 IOPS-based IP connectivity communication + +In order to transmit the IP packets via the IOPS system, the MC service clients operating on the MC UEs implement for the transmission of the IP packets (containing the MC service related application data such as signalling control data or application data) an IP layer supporting IP encapsulation within IP (IETF RFC 2003), i.e. the IP packets are encapsulated with an inner IP header and an outer IP header. The inner IP header includes as IP address destination the related IP address of the targeted MC users(s). For the case of, e.g., a private call the related IP address destination is received within the notification message related to the relevant MC user. For the case of, e.g., a group call the related IP address destination to be utilized may be the pre-configured ProSe Group IP multicast address associated to the respective MC service group ID. On the other hand, the outer IP header includes as IP address destination the IP address of the IOPS packet distribution function. The MC UEs may be either pre-configured with the IP address of the IOPS packet distribution function for the IOPS operation or it may also be included in the notification messages as part of the discovery procedure. + +The outgoing IP packets are sent to the MC UE's lower layers to be transmitted via the IOPS system to the IOPS packet distribution function for IP relaying. Figure 6.4.1.3-1 depicts the IP encapsulation of the application data for the IOPS-based IP connectivity communication. + +![Diagram illustrating the IP encapsulation process for IOPS-based IP connectivity communication. Application data generated by the MC service client is processed through the IP Layer, which splits into Upper and Lower IP Layers. The Upper IP Layer creates an Upper-layer-IP-Packet with IP Payload and IP Header 1 (Inner IP Header 1 pointing to Targeted MC UE IP Address or Group IP Multicast). The Lower IP Layer creates a Lower-layer-IP-Packet with IP Payload, IP Header 1, and IP Header 2 (Outer IP Header 2 pointing to IOPS packet distribution function IP Address). Both packets are then sent to the IOPS system.](77464a47f104d0d647b2414591137b64_img.jpg) + +The diagram shows the flow of data from the MC service client through the IP layer. The 'Application Data generated by the MC service client' enters the 'IP Layer'. From the 'IP Layer', the data is split into two paths: one through the 'Upper IP Layer' and another through the 'Lower IP Layer'. The 'Upper IP Layer' produces an 'Upper-layer-IP-Packet' consisting of 'IP Payload' and 'IP Header 1'. A note indicates that 'Inner IP Header 1' points to the 'Targeted MC UE IP Address or Group IP Multicast'. The 'Lower IP Layer' produces a 'Lower-layer-IP-Packet' consisting of 'IP Payload', 'IP Header 1', and 'IP Header 2'. A note indicates that 'Outer IP Header 2' points to the 'IOPS packet distribution function IP Address'. Both packets are then sent 'To the IOPS system' via the 'Lower Layers'. + +Diagram illustrating the IP encapsulation process for IOPS-based IP connectivity communication. Application data generated by the MC service client is processed through the IP Layer, which splits into Upper and Lower IP Layers. The Upper IP Layer creates an Upper-layer-IP-Packet with IP Payload and IP Header 1 (Inner IP Header 1 pointing to Targeted MC UE IP Address or Group IP Multicast). The Lower IP Layer creates a Lower-layer-IP-Packet with IP Payload, IP Header 1, and IP Header 2 (Outer IP Header 2 pointing to IOPS packet distribution function IP Address). Both packets are then sent to the IOPS system. + +**Figure 6.4.1.3-1 MC UE's IP encapsulation of application data for the IOPS-based IP connectivity communication** + +When the IOPS packet distribution function receives the IP packets for relaying, it decapsulates them to get the IP packet containing the inner IP header, i.e. the related IP address of the targeted MC user(s). The IOPS packet distribution function resolves if that IP address destination is related to a Group IP multicast address (i.e. related to a + +MC service group ID) or to a unicast IP address (i.e. related to, e.g., a called MC user in a private call). Thus, and based on information stored in the IOPS MC connectivity status function, the packet distribution function transmits/relays the IP packets to the targeted MC UE(s) via the local EPS. + +**Editor's note: How the IOPS packet distribution function manages and relays the IP packets targeting a group of MC users is FFS** + +In the following, two examples are presented to describe the IOPS-based IP connectivity communication. The first example depicted in Figure 6.4.1.3-2 is the case of a MCPTT private call between two MC users (MC user 1 and MC user 2). The second example depicted in Figure 6.4.1.3-3 is the case of a MCPTT group call between three users (MC user 1, MC user 2, and MC user 3). The MC users are assumed to be defined as relevant to each other, e.g. the MC users belong to the same MC service group ID or are within the list of users who can be called in a private call. + +For both examples, it is assumed that the MC UEs are being served by the IOPS system, the MC users have already performed the IOPS-based discovery procedure with the IOPS MC connectivity status function and the MC users support the IOPS-based IP connectivity communication. This means, the MC users have been already notified about the connectivity status of the other relevant discovered MC users within the IOPS system. + +![Sequence diagram illustrating IOPS-based IP connectivity communication for a MCPTT Private Call example. The diagram shows the interaction between MC user 1 (MCPTT client 1), MC user 2 (MCPTT client 2), the IOPS system (IOPS-capable eNB(s), Local EPC), the IOPS MC connectivity status function, and the IOPS packet distribution function. The process involves call setup, packet relaying, media plane establishment, and call release.](12de9b926df0384ec07702671827c9cd_img.jpg) + +The diagram illustrates the sequence of events for a MCPTT private call between MC user 1 and MC user 2, facilitated by the IOPS system. The participants are MC user 1 (MCPTT client 1), MC user 2 (MCPTT client 2), the IOPS system (IOPS-capable eNB(s), Local EPC), the IOPS MC connectivity status function, and the IOPS packet distribution function. + +The sequence of messages is as follows: + +- MC user 1 initiates a private call with MC user 2. +- Call setup request (IP destination: Packet distribution function) is sent from MC user 1 to the IOPS packet distribution function. +- Handling and relaying of IP packets occurs at the IOPS packet distribution function. +- Call setup request (IP destination: MC UE2) is sent from the IOPS packet distribution function to MC user 2. +- MC user 2 gets notified about incoming private call. +- Call setup response (IP destination: Packet distribution function) is sent from MC user 2 to the IOPS packet distribution function. +- Handling and relaying of IP packets occurs at the IOPS packet distribution function. +- Call setup response (IP destination: MC UE1) is sent from the IOPS packet distribution function to MC user 1. +- Media plane and floor control establishment between MC user 1 and MC user 2. +- Release private call (media plane resources released). + +A note at the top of the sequence indicates: "MC UEs are being served by the IOPS system and the MC users are discovered by the IOPS MC connectivity status function". + +Sequence diagram illustrating IOPS-based IP connectivity communication for a MCPTT Private Call example. The diagram shows the interaction between MC user 1 (MCPTT client 1), MC user 2 (MCPTT client 2), the IOPS system (IOPS-capable eNB(s), Local EPC), the IOPS MC connectivity status function, and the IOPS packet distribution function. The process involves call setup, packet relaying, media plane establishment, and call release. + +**Figure 6.4.1.3-2 IOPS-based IP connectivity communication – MCPTT Private Call example** + +1. The MC user 1 at the MCPTT client 1 (operating on the MC UE 1) would like to initiate an MCPTT private call to the MC user 2 at the MCPTT client 2 (operating on MC UE 2). + +2. The MCPTT client 1 sends a call setup request towards the MCPTT client 2. The call setup request is based on the procedures to be defined for the IOPS-based IP connectivity communication. For that, at the MC UE 1, the IP encapsulation within IP procedure is performed and the IP packets are sent to the MC UE 1's lower layers to be transmitted via the IOPS system to the IOPS packet distribution function. +3. The IOPS packet distribution function receives the IP packets from the IOPS system and performs the IP decapsulation. The IOPS packet distribution function resolves that the IP address destination is a unicast IP address of other MC UE within the IOPS system, i.e. MC UE 2. +4. The IOPS packet distribution function relays the IP packets related to the call setup request via the IOPS system towards the MC UE 2. +5. The MCPTT client 2 notifies the MC user 2 about the incoming private call. +6. The receiving MCPTT client 2 accepts the private call and a call setup response indicating the successful call establishment is sent to the MCPTT client 1. As described in step 2, the MC UE 2 also transmits the response IP packets via the IOPS system to the IOPS packet distribution function. +7. As described in step 3, the IOPS packet distribution function resolves that the IP address destination is a unicast IP address of other MC UE within the IOPS system, i.e. MC UE 1. +8. The IOPS packet distribution function relays the IP packets related to the call setup response via the IOPS system towards the MC UE 1. +9. The MCPTT client 1 and the MCPTT client 2 have successfully established the communication media plane based on the IOPS-based IP connectivity communication, i.e. all media plane data are also transmitted via the IOPS system and the IOPS packet distribution function. +- 10 It is assumed that the call has ended. Therefore, any of the MC users initiates a private call release based on the procedures to be defined for the IOPS-based IP connectivity communication. The MCPTT client 1 and the MCPTT client 2 release all associated media plane resources. + +![Sequence diagram illustrating IOPS-based IP connectivity communication for an MCPTT Group Call example. The diagram shows interactions between MC users (1, 2, 3), the IOPS System, IOPS MC connectivity status function, and IOPS packet distribution function. The process involves group call initiation, announcement, response, media plane establishment, and call release.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +sequenceDiagram + participant MC user 1 (MCPTT client 1) + participant MC user 2 (MCPTT client 2) + participant MC user 3 (MCPTT client 3) + participant IOPS System + participant IOPS MC connectivity status function + participant IOPS packet distribution function + + Note over MC user 1, IOPS System: MC UEs are being served by the IOPS system and the MC users are discovered by the IOPS MC connectivity status function + + MC user 1->>IOPS System: 1. MC user 1 initiates a group call with MC user 2 and MC user 3 + IOPS System->>IOPS packet distribution function: 2. Group call announcement (IP destination: Packet distribution function) + IOPS packet distribution function->>IOPS System: 3. Handling and relaying of IP packets + IOPS System->>MC user 2: 4a. Group call announcement (destination: MC UE2) + IOPS System->>MC user 3: 4b. Group call announcement (destination: MC UE3) + MC user 2->>MC user 1: 5. MC users get notified about incoming group call + MC user 3->>MC user 1: 5. MC users get notified about incoming group call + MC user 2->>IOPS packet distribution function: 6a. Group call response (IP destination: Packet distribution function) + MC user 3->>IOPS packet distribution function: 6b. Group call response (IP destination: Packet distribution function) + IOPS packet distribution function->>IOPS System: 7. Handling and relaying of IP packets + IOPS System->>MC user 1: 8a. Group call response(s) from MC user 2 and MC user 3 (IP destination: MC UE1) + IOPS System->>MC user 2: 8b. Group call response from MC user 3 (IP destination: MC UE2) + IOPS System->>MC user 3: 8c. Group call response from MC user 2 (IP destination: MC UE3) + Note over MC user 1, MC user 3: 9. Media plane and floor control establishment between MC user 1, MC user 2 and MC user 3 + Note over MC user 1, MC user 3: 10. Release group call (media plane resources released) + +``` + +Sequence diagram illustrating IOPS-based IP connectivity communication for an MCPTT Group Call example. The diagram shows interactions between MC users (1, 2, 3), the IOPS System, IOPS MC connectivity status function, and IOPS packet distribution function. The process involves group call initiation, announcement, response, media plane establishment, and call release. + +**Figure 6.4.1.3-3 IOPS-based IP connectivity communication – MCPTT Group Call example** + +1. The MC user 1 at the MCPTT client 1 (operating on the MC UE 1) would like to initiate a group call with the MCPTT group, i.e. a group call targeting the MC user 2 at the MCPTT client 2 (operating on MC UE 2) and the MC user 3 at the MCPTT client 3 (operating on MC UE 3). +2. The MCPTT client 1 as the group call originator sends a group call announcement to the MCPTT group. The group call announcement is based on the procedures to be defined for the IOPS-based IP connectivity communication. For that, at the MC UE 1, the IP encapsulation within IP procedure is performed and the IP packets are sent to the MC UE 1's lower layers to be transmitted via the IOPS system to the IOPS packet distribution function. +3. The IOPS packet distribution function receives the IP packets from the IOPS system and performs the IP decapsulation. The IOPS packet distribution function resolves that the IP address destination is a Group IP address involving other discovered MC users within the IOPS system. +4. The IOPS packet distribution function relays the IP packets related to the group call announcement via the IOPS system towards all the other related MC users within the MCPTT group, i.e. the MC UE 2 and MC UE 3. +5. The MCPTT clients notify the MC users, respectively, about the incoming group call announcement. + +6. The MCPTT clients 2 and 3 send the group call response to the MCPTT group. As described in step 2, the MC UEs also transmit the response packets via the IOPS system to the IOPS packet distribution function. +7. As described in step 3, the IOPS packet distribution function resolves that the IP address destination is a Group IP multicast address involving other MC users within the IOPS system. +8. The IOPS packet distribution function relays the IP packets related to the group call responses via the IOPS system towards all the other related MC users within the MCPTT group, i.e. the MC UE 1, MC UE 2 and MC UE 3, respectively. +9. The MCPTT clients have successfully established the communication media plane based on the IOPS-based IP connectivity communication, i.e. all media plane data are also transmitted via the IOPS system and the IOPS packet distribution function. +- 10 It is assumed that any of the users initiates the termination of the ongoing group call release based on the procedures to be defined for the IOPS-based IP connectivity communication. The MCPTT clients release all associated media plane resources. + +### 6.4.2 Impacts on existing nodes and functionality + +The reference points, procedures and protocols to be utilized for the IOPS-based discovery procedure and the IOPS-based IP connectivity communication need to be specified. + +### 6.4.3 Solution evaluation + +This solution provides a minimal deployment in each IOPS MC system. The IOPS MC system only requires that the IOPS-capable eNB(s) are connected to a local EPC, providing connectivity to the IOPS MC connectivity status function and packet distribution function. Challenges related to security requirements and data synchronization between the IOPS system and the primary MC system is by this functional mode minimized. The solution requires that all MC service clients are pre-provisioned with necessary MC service configuration and group configuration. This solution provides considerably better coverage and capacity when the user communication is based on the IOPS EPS IP connectivity compared to an off-network communication utilizing ProSe. Furthermore, a lower operational complexity can be achieved by the implementation of an IOPS MC connectivity status function and a packet distribution function compared to supporting an on-network based MC service server over an IOPS system. This considering that there is no need for synchronization of data between the central MC service server and all distributed MC servers over IOPS systems. + +On the other hand, which procedures and protocols are utilized for the IOPS-based IP connectivity communication are FFS and require their specification. + +## 6.5 Solution 5: Functional model for IOPS based on an always-on participating server + +### 6.5.1 Description + +This solution addresses key issue 2-4. One architectural solution for an IOPS MC system is to have a fully functional and active MC system used during normal operations. In the IOPS MC system the MC service server only execute the participating role during normal operating conditions and the primary MC system execute the controlling role. When the connection between the IOPS MC system and the primary system breaks the IOPS MC system execute both participating and controlling role of the MC service server. + +Figure 6.5.1-1 below illustrates the deployment where several MC service servers assigned the participating role within one MC system are used for multiple UE based on their location. When the backhaul failure occurs, the IOPS MC system performs both the participating and controlling function. + +![Figure 6.5.1-1: IOPS MC system providing the participating function. This diagram shows the network architecture. At the top, two boxes represent the 'IOPS MC system part function' and the 'Primary MC system part + cont function', connected by a horizontal line. Below the IOPS MC part is a 'Local EPC' box, and below the Primary MC part is an 'EPC' box. Four User Equipment (UE) icons, labeled UE1, UE2, UE3, and UE4, are shown. UE1 is connected to the EPC. UE2, UE3, and UE4 are connected to the Local EPC. A dashed red line encircles UE2, UE3, and UE4, indicating they are part of the IOPS MC system's participating function.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Figure 6.5.1-1: IOPS MC system providing the participating function. This diagram shows the network architecture. At the top, two boxes represent the 'IOPS MC system part function' and the 'Primary MC system part + cont function', connected by a horizontal line. Below the IOPS MC part is a 'Local EPC' box, and below the Primary MC part is an 'EPC' box. Four User Equipment (UE) icons, labeled UE1, UE2, UE3, and UE4, are shown. UE1 is connected to the EPC. UE2, UE3, and UE4 are connected to the Local EPC. A dashed red line encircles UE2, UE3, and UE4, indicating they are part of the IOPS MC system's participating function. + +**Figure 6.5.1-1: IOPS MC system providing the participating function** + +The functional model of the IOPS MC system is illustrated in figure 6.5.1-2. For simplicity some of the internal reference points are not illustrated in the figure. + +![Figure 6.5.1-2: Functional model for an IOPS MC system based on always on participating server. This diagram is a functional model showing two main systems: 'IOPS MC System' on the left and 'Primary MC System' on the right. The IOPS MC System contains an 'MC service UE' with clients (MCPTT, MCData, MCVideo) and a set of 'MC service servers' (MCPTT, MCData, MCVideo) with 'Controlling function' and 'Participating function'. The Primary MC System contains a similar 'MC service UE' and 'MC service servers'. Both systems connect to a 'Common services core' (dashed box) which includes 'Group management server', 'Configuration management server', 'Identity management server', 'Key management server', and 'Location management server'. Reference points CSC-1, CSC-2, CSC-3, CSC-4, CSC-8, CSC-13, and CSC-14 are shown between the UEs, servers, and the common core. The IOPS MC system is also connected to a 'Local EPS'.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) + +Figure 6.5.1-2: Functional model for an IOPS MC system based on always on participating server. This diagram is a functional model showing two main systems: 'IOPS MC System' on the left and 'Primary MC System' on the right. The IOPS MC System contains an 'MC service UE' with clients (MCPTT, MCData, MCVideo) and a set of 'MC service servers' (MCPTT, MCData, MCVideo) with 'Controlling function' and 'Participating function'. The Primary MC System contains a similar 'MC service UE' and 'MC service servers'. Both systems connect to a 'Common services core' (dashed box) which includes 'Group management server', 'Configuration management server', 'Identity management server', 'Key management server', and 'Location management server'. Reference points CSC-1, CSC-2, CSC-3, CSC-4, CSC-8, CSC-13, and CSC-14 are shown between the UEs, servers, and the common core. The IOPS MC system is also connected to a 'Local EPS'. + +**Figure 6.5.1-2: Functional model for an IOPS MC system based on always on participating server** + +In this functional model the users may be transferred to the IOPS MC system and actively use the MC service server's participating function. This trigger to transfer the users may be based on the UE location and the MC service provider policy, and by that receive part of the MC services from the IOPS MC system. This takes place prior that the IOPS mode is triggered by backhaul failure. + +In the normal operation i.e. the backhaul transmission works, the common services core in the IOPS MC system is not used, instead the MC service client and the MC service server in the IOPS MC system is connected to the common services core in the primary MC system. The common services core still needs to be kept in sync with the primary MC + +system's common service core. When there is a backhaul failure the common services core in the IOPS MC system is used instead. + +### 6.5.2 Solution evaluation + +This solution provides a minor deviation from the functional model in a primary MC system. A few functional entities and reference points can be removed since they are not needed in the IOPS MC system. The users using the IOPS MC system need to switch to use the participating function of the MC service server in the IOPS MC system prior to the transition to IOPS mode. User and service data synchronization is limited to users that are using the IOPS MC system prior to a backhaul failure. There may be an issue in providing service to users who have not been transferred to the IOPS MC system prior to the backhaul failure as their configuration data will not be accessible during the backhaul failure. For these users there must be another data synchronization solution in place prior these users may enjoy MC services in IOPS mode. + +This solution is not the preferred solution in a nomadic deployment. + +## 6.6 Solution 6: Procedure for switching from the primary MC system to an IOPS MC system + +### 6.6.1 Description + +This solution address key issue 2-3. The solution utilizes the architecture defined in solution 5. In the procedure defined in this subclause the MC service client is triggered to re-register to the IOPS MC system and use the participating function in the MC service server in the IOPS MC system and the controlling function in the MC service server in the primary MC system. + +### 6.6.2 Procedure + +Figure 6.6.2-1 below specify the procedure for switching an MC service client from the primary MC system to the IOPS MC system. It requests the user to re-register in the IOPS MC system, while keeping part of the functionality (the controlling function) in the primary MC system. + +Pre-conditions: + +- The MC service client is authenticated and authorized by the primary MC system. +- The MC service client must be registered in the primary MC system. +- The MC service client has affiliated to one or several MC service groups. + +![Sequence diagram illustrating the switching from the primary MC system to an IOPS MC system. The diagram shows the interaction between an MC service client, a Primary MC System (containing MC service server with Participating and Controlling functions), and an IOPS MC system (containing eNB, Local EPC, and Local MC service server with Participating and Controlling functions). The sequence of steps is: 1. Group communication is handled by the Primary MC system; 2. MC system detects that the MC service client is in proximity of an IOPS MC system; 3. Re-registration request (dashed arrow from Primary MC System to MC service client); 4. User authentication and registration to Local MC service server (solid arrow from MC service client to Local MC service server); 5. Group affiliations (solid arrow from Local MC service server to Primary MC System); 6. Group communication handled by local MC service server participating function and the primary MC system controlling function; 7. Link failure to PLMN EPC (dashed arrow from Primary MC System to IOPS MC system); 8. Group communication in IOPS MC system.](26d664119ad25250780f554633444e54_img.jpg) + +Sequence diagram illustrating the switching from the primary MC system to an IOPS MC system. The diagram shows the interaction between an MC service client, a Primary MC System (containing MC service server with Participating and Controlling functions), and an IOPS MC system (containing eNB, Local EPC, and Local MC service server with Participating and Controlling functions). The sequence of steps is: 1. Group communication is handled by the Primary MC system; 2. MC system detects that the MC service client is in proximity of an IOPS MC system; 3. Re-registration request (dashed arrow from Primary MC System to MC service client); 4. User authentication and registration to Local MC service server (solid arrow from MC service client to Local MC service server); 5. Group affiliations (solid arrow from Local MC service server to Primary MC System); 6. Group communication handled by local MC service server participating function and the primary MC system controlling function; 7. Link failure to PLMN EPC (dashed arrow from Primary MC System to IOPS MC system); 8. Group communication in IOPS MC system. + +**Figure 6.6.2-1: Switching from the primary MC system to an IOPS MC system.** + +1. Group communication is handled by the primary MC system solely. +2. The MC client or the MC service server in the primary MC system detects that the MC client is in proximity of an IOPS MC system. How this is detected is implementation specific. + +NOTE 1: Step 2 could be triggered by detecting that the cell that the UE is currently attached to is IOPS capable or that the MC service server knows that a neighbouring cell to the currently attached cell is IOPS capable. + +3. In the scenario that the MC service server in the primary MC system decides that the MC services client shall be transferred to the IOPS MC system, the MC service server sends a re-registration request to the MC service client. + +4. The MC service client performs the authentication and registration procedure as defined in 3GPP TS 23.280 [7]. + +NOTE 2: Step 4 causes service interruption and is therefore preferably avoided during active communication. + +5. The MC service client affiliates to the MC service groups of interest, that request for affiliation is forwarded to the controlling function in the MC service server both in the IOPS MC system and the primary MC system. + +6. Group communication is handled by the participating function in the IOPS MC system and the controlling function in the primary MC system. +7. The connectivity between the IOPS MC system and the primary MC system breaks. +8. Group communication is handled by the IOPS MC system solely. When the connectivity between the IOPS MC system and primary MC system is restored the group communication may continue, utilizing the primary MC systems controlling function. In this case any group affiliations that was done during IOPS mode must be forwarded to the primary MC system's MC service server. + +**Editor's note:** It is FFS how the MC client switches from the participating function in the IOPS MC system to the participating function in the primary MC system or another IOPS MC system when the MC service client moves to area which is outside of proximity of current IOPS MC system. + +### 6.6.3 Solution evaluation + +This solution provides an efficient way to transfer ongoing calls from a primary MC system to an IOPS MC system when there is a failure in the connectivity between the IOPS MC system and the primary MC system. + +This solution will utilize the existing stage-2 and stage-3 procedures for call setup procedures floor control for procedures involving one single system. The solution does not need to use the more complex procedures involving multiple MC service servers. + +Users that has not been transferred to the IOPS MC system prior the failure needs to perform the authentication procedures (according to 3GPP TS 23.280 [7]) before accessing the service. + +## 6.7 Solution 7: IOPS notification to MC UEs + +### 6.7.1 Description + +This solution addresses key issue 2-3 in how to optimize the user experience when MC UEs are switching to and from an IOPS MC system. An IOPS MC system does not have any connectivity to the primary MC system and therefore it cannot inform users that are not in the coverage of the IOPS system or even other MC system about the existence of the IOPS MC system. Since MC users are moving around and may enter or leave the IOPS system, the user experience will be unpredictable in terms of group constellations and delays during the switching time from the primary MC system served by one PLMN id to the IOPS MC system served by another PLMN id. + +The procedure defined in this solution provides a notification to users that are likely to enter the IOPS MC system, which can improve the switching time and also give an indication to the user that the current active users in a group is impacted by the presence of the local IOPS MC system. + +Preconditions: + +- There is an IOPS MC system active and the neighbouring cells to the IOPS MC system is part of the primary MC system. +- The user has been defined in and registered to the IOPS MC system. +- The MC service client was authenticated and authorized by the IOPS MC system. + +![Sequence diagram illustrating the IOPS notification procedure to MC UEs in proximity of the IOPS MC system. The diagram shows interactions between MC service client 1, Local MC service server (IOPS MC system), MC service client 2, and MC service server (Primary MC system).](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +``` + +sequenceDiagram + participant MCSC1 as MC service client 1 + participant LMSS as Local MC service server + participant MCSC2 as MC service client 2 + participant MSS as MC service server + + Note over MCSC1, LMSS: 1. Group communication is handled by the IOPS MC system + Note over MCSC1: 2. The MC service client 1 leaves the IOPS MC system + MCSC1->>MSS: 3. IOPS presence message to the primary MC system + Note over MSS: 4. MC service server acts on IOPS situation + MSS->>MCSC2: 5. IOPS notification message + +``` + +Sequence diagram illustrating the IOPS notification procedure to MC UEs in proximity of the IOPS MC system. The diagram shows interactions between MC service client 1, Local MC service server (IOPS MC system), MC service client 2, and MC service server (Primary MC system). + +**Figure 6.7.1-1: IOPS notification procedure to MC UEs in proximity of the IOPS MC system** + +1. Group communication is handled by the IOPS MC system. +2. The MC service client moves out of the coverage of the IOPS MC system and enters the primary MC system. +3. The MC service client sends a message to the primary MC system to inform the primary MC system about the existence of the IOPS MC system in the area. This message may also include geographical information, PLMN IDs, frequency bands and addresses to the local MC service servers. +4. The primary MC server may use the received information to take measures to optimize the provided MC service based on the changed conditions. +5. The primary MC system sends a message to all MC service clients in proximity of the IOPS MCS system to notify of the existence of a system. It may also include information that will improve the switching time when new MC UE's are moving into the MC IOPS system. This information may be e.g. geographical area / identified cells, IOPS users and groups, identified service degradation, PLMN IDs, frequency bands and addresses to the local MC service servers – the most important is dynamic information that else cannot be known by the Primary MC system. This message can preferably be sent on an MBMS bearer. + +NOTE: Some parameters including PLMN ID may already be known by configuration + +### 6.7.2 Impacts on existing nodes and functionality + +**Editor's Note:** Capture impacts on existing 3GPP nodes and functional elements. + +### 6.7.3 Solution evaluation + +This contribution presents a solution for discovering that there is an active IOPS system operational. Based on this both the centralized MC service server and the MC service clients may take measures to provide a better user experience for users and better system performance. With knowledge of the IOPS situation and key parameters clients can make better mobility decisions between the centralized system and the IOPS system. The IOPS situation can also be notified to the end user, giving the end user an opportunity to actively move to or from the IOPS covered area based on increased situational awareness. + +## 6.8 Solution 8: MC service client configuration for IOPS + +### 6.8.1 Description + +This solution addresses Key Issue 2-2 on how to prepare an MC service client for receiving an IOPS provided MC service. + +An IOPS solution, according to Annex K in TS 23.401 [10] has a dedicated PLMN identity. + +Procedures for retrieval of initial MC service UE configuration data, as specified in TS 23.280 [7] Annex A.6, can be re-used. The MC service UE is provided with initial UE configuration via a bootstrap procedure that provides the MC service UE's with critical information needed to connect to the MC system, as specified in TS 23.280 [7], subclause 10.1.1.1. This configuration includes HPLMN ID, an optional list of VPLMN IDs, APN, server URIs etc. The HPLMN parameter should be extended to a list of HPLMNs to support IOPS PLMN IDs. + +The MC service client can then retrieve MC service UE Configuration according to TS 23.280 [7], subclause 10.1.3. + +### 6.8.2 Solution evaluation + +This solution is to a large extent already supported by existing specifications, efficiently reducing the complexity. The solution is dependent on that UE configuration data has been successfully synchronized to the IOPS MC System (Key Issue 2-1). Since Initial UE configuration will be the same regardless if registering to the Primary MC system or an IOPS MC system this means that APN, server URIs etc needs to be the same in these systems. + +## 6.9 Solution 9: Functionality for determining the MC user registration status in IOPS + +### 6.9.1 Description + +This solution addresses the key issue 2-7 on determining a list of MC users connected to the IOPS MC system when a backhaul failure has occurred. For that, one solution for the architecture of the IOPS MC system is to have a functionality in the IOPS MC system to manage dynamic data related to the registration status of MC users being served by the IOPS MC system. + +The registration status function is implemented within the IOPS MC service system to provide mechanisms for the MC users being served by the IOPS MC system to query about which other MC users, or whether a particular MC user, are also registered to the IOPS MC system. Since an IOPS system provides local connectivity to only MC users, any MC user may be authorized to make such a query while connected to the IOPS MC system. + +The MC service user profile may include new parameters to indicate if an MC user is authorized to query about the registration status of other MC users on the IOPS system as well as to indicate if the MC user registration status on the IOPS MC system is available or not to other MC users making such a query. For the later case, an MC user may publish to the IOPS MC system if the MC user's registration status becomes available or not to other users. + +As the IOPS MC system may not identify when an MC user has left the IOPS system coverage area, the MC users may be requested to periodically publish that they are within the IOPS system. For that, the MC users may periodically publish that their registration status on the IOPS system is available to other MC users. Thus, the IOPS MC system can maintain the registration status of the MC users updated. + +MC users which are interested to get informed about the registration status of other MC user(s) on the IOPS MC system subscribe to receive notifications of users which are relevant to them. MC users may be interested to subscribe to receive the registration status of all users connected to the IOPS MC system or just a sub-set of users, e.g. users which are within the list of users who can be called in private call or for users which belong to the same MC service group. + +The MC users with active subscriptions receive the registration status of their relevant MC users via notification messages. These notifications can be sent by the IOPS MC system based on different triggers, e.g. any registration status change of the relevant MC users or as periodic notification messages defined by the IOPS MC system. For + +instance, when a particular relevant MC user is not anymore registered to the IOPS MC system, the IOPS MC system notifies all MC users with active subscriptions associated to that particular relevant MC user. + +Figure 6.9.1-2 depicts an example of an IOPS MC system providing MCPTT services and supporting the registration status function. In this example, it is assumed that the registration status function is implemented as part of the MCPTT server. Also, the MC user 1 at the MCPTT client 1 defines the MC user 2 at the MCPTT client 2 as a relevant MC user, assuming that the MC user 2 is within the list of users who can be called via an MCPTT private call by the MC user 1. + +![Sequence diagram showing MC user 1, MCPTT server, and MC user 2 interactions for registration and notification.](dd5771673aececa53d42ece89218299d_img.jpg) + +**IOPS MC service system** + +``` +sequenceDiagram + participant MC user 1 (MCPTT client 1) + participant MCPTT server (Registration status function) + participant MC user 2 (MCPTT client 2) + + Note over MC user 1, MC user 2: 1. MC user 1 and MC user 2 are registered to the IOPS MC system + MC user 1->>MCPTT server: 1a. PUBLISH (registration status available) + MC user 2->>MCPTT server: 1b. PUBLISH (registration status available) + Note left of MC user 1: 2. MC user 1 defines MC user 2 as a relevant-user + MC user 1->>MCPTT server: 3. SUBSCRIBE (relevant-user: MC user 2) + MCPTT server-->>MC user 1: 4. OK (subscription activated) + MCPTT server->>MC user 1: 5. NOTIFY (MC user 2 registration status) + Note left of MC user 1: 6. MC user 1 is notified about MC user 2 registration status + MC user 1->>MCPTT server: 7. OK (notification received) + Note right of MC user 2: 8. MC user 2 becomes disconnected from the IOPS MC system + MCPTT server->>MC user 1: 9. NOTIFY (MC user 2 registration status changed) + Note left of MC user 1: 10. MC user 1 is notified about MC user 2 registration status + MC user 1->>MCPTT server: 11. OK (notification received) + Note right of MC user 2: 12. MC user 2 is registered again to the IOPS MC system + MCPTT server->>MC user 1: 13. NOTIFY (MC user 2 registration status changed) + Note left of MC user 1: 14. MC user 1 is notified about MC user 2 registration status + MC user 1->>MCPTT server: 15. OK (notification received) + Note over MC user 1, MC user 2: 16. MC user 1 at MCPTT client 1 initiates and establishes a private call with the MC user 2 at the MCPTT client 2 +``` + +The sequence diagram illustrates the interaction between two MC users (MC user 1 and MC user 2) and the IOPS MC service system (MCPTT server). The process begins with both users registering to the system. MC user 1 then defines MC user 2 as a relevant-user and subscribes to their registration status. The server responds with an OK and sends an initial NOTIFY. MC user 1 receives the notification and responds with OK. Subsequently, MC user 2 disconnects from the system, triggering a NOTIFY from the server to MC user 1. MC user 1 receives this notification and responds with OK. MC user 2 then re-registers, causing another NOTIFY to MC user 1, who again responds with OK. Finally, MC user 1 initiates a private call with MC user 2. + +Sequence diagram showing MC user 1, MCPTT server, and MC user 2 interactions for registration and notification. + +**Figure 6.9.1-2: Publication, subscription and notification for determining the MC user registration status of MC users on the IOPS MC system** + +1. The MC users at the MCPTT clients are registered to the IOPS MC system for the MCPTT service. + +NOTE 1: The MC users may publish if their registration status on the IOPS MC system is available or not to other MC users. + +2. MC user 1 defines the MC user 2 as a relevant MC user. + 3. MC user 1 at the MCPTT client 2 sends a SUBSCRIBE request to the IOPS MC system to receive registration status notifications about the MC user 2. + 4. The IOPS MC system may confirm the subscription request. + 5. The IOPS MC system sends a NOTIFY message to the MC user 1 with the registration status of the MC user 2. + 6. The MCPTT client 1 notifies the MC user 1 about the registration status of the MC user 2. Thereby, the MC user 1 knows that MC user 2 is within the IOPS system. + 7. The MCPTT client 1 may confirm to the IOPS MC system the reception of the notification message. + 8. The MC user 2 becomes disconnected from the IOPS MC system, e.g. because the MC UE 2 where the MC user 2 at the MCPTT client 2 is operating on, has left the IOPS system. + 9. The IOPS MC system sends a NOTIFY message to the MC user 1 informing that the registration status of the MC user 2 has changed to disconnected. + - 10 The MCPTT client 1 notifies the MC user 1 about the registration status change of the MC user 2. Thereby, the MC user 1 knows that MC user 2 is not anymore within the IOPS system. +- NOTE 2: Based on the MC user 1 subscription, the MC user 1 might get notified once the MC user 2 is again connected to the IOPS system. +11. The MCPTT client 1 may confirm to the IOPS MC system the reception of the notification message. + 12. The MC user 2 at the MCPTT client 2 is again registered to the IOPS MC system. + 13. The IOPS MC system sends a NOTIFY message to the MC user 1 informing that the registration status of the MC user 2 has changed to registered. + 14. The MCPTT client 1 notifies the MC user 1 about the registration status change of the MC user 2. Thereby, the MC user 1 knows that MC user 2 is again within the IOPS system. + - 15 The MCPTT client 1 may confirm to the IOPS MC system the reception of the notification message. + 16. As the MC user 1 is aware that it can reach out to the MC user 2, the MC user 1 initiates and establishes an MCPTT private call with the MC user 2. + +### 6.9.2 Solution evaluation + +This solution provides a mechanism to handle dynamic data related to the registration status of the MC users on the IOPS MC system. Thus, the MC users registered to the IOPS MC system can query the registration status of other MC users connected to the IOPS MC system. + +This solution proposes that all MC users which are already registered to the IOPS MC service system may be authorized to query the registration status of other MC users within the IOPS system. Also, the MC service user profile may include new parameters to indicate if an MC user is authorized to query about the registration status of other MC users on the IOPS system as well as to indicate if the MC user registration status on the IOPS MC system is available or not to other MC users making such a query. For the later, the MC user may publish if its registration status becomes or not available to other MC users. Furthermore, MC users can subscribe to receive notification about the registration status of other MC users connected to the IOPS MC system. + +# 7 Overall evaluation + +## 7.1 General + +The following subclauses contain an overall evaluation of the solutions presented in this technical report, and their applicability to the identified key issues. + +- Subclause 7.2 provides an evaluation of the functional model solutions for the MC service architecture to be used during the IOPS mode of operation; and +- Subclause 7.3 provides an evaluation of the introduced solutions for the key issues including the impact on other working groups that will need consideration. + +## 7.2 Architecture evaluation + +The functional model solutions studied in this technical report are based on the on-network and off-network functional models described in 3GPP TS 23.280. The functional model solutions based on the on-network functional model include having a fully functional IOPS MC system, which can be either in standby (standalone system) or active (acting as a partner system) during normal operation. On the other hand, the functional model solution based on the off-network functional model is a model where the IOPS MC system only provides IP connectivity to the served MC users. + +A summary of the functional model solutions studied in this technical report are listed in table 7.2-1. + +**Table 7.2-1: Architecture evaluation – Functional model solutions in IOPS** + +| Architecture solution | Applicable key issues (subclause reference) | Evaluation (subclause reference) | Dependency on other working groups | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------|----------------------------------|------------------------------------| +| Solution 2 - Functional model for IOPS based on a switchable standalone MC system | Key issue specified in subclauses: 4.1.4 (Key issue 2-4) | 6.2.2 | (see NOTE 1) | +| Solution 3 - Functional model for IOPS based on an always-on partner MC system | Key issue specified in subclauses: 4.1.4 (Key issue 2-4) | 6.3.2 | (see NOTE 1) | +| Solution 4 - Functional model for IOPS MC system based on only IP connectivity | Key issue specified in subclauses: 4.1.4 (Key issue 2-4) | 6.4.3 | (see NOTE 1)
(see NOTE 2) | +| Solution 5 - Functional model for IOPS based on an always-on participating server | Key issue specified in subclauses: 4.1.4 (Key issue 2-4) | 6.5.2 | (see NOTE 1) | +| NOTE 1: This solution shall include mechanisms to authorize and authenticate MC users to be served by the IOPS MC system. Such mechanisms need to be addressed and defined by SA3. | | | | +| NOTE 2: This solution includes new entities in the application architecture. The definition of the EPC interfaces to be used for these new entities might involve other working groups, e.g. SA2. | | | | + +The functional model of solutions 2, 3, and 5 are based on the on-network functional model. These solutions require that all available IOPS MC systems maintain a fully user and service data synchronization with the primary MC system before the occurrence of a backhaul failure. As described in the key issue 2-1, the user and service configuration data synchronization between the (on-network based) IOPS MC systems and the primary MC system is relevant to support MC services during the IOPS mode of operation. The implementation of such a mechanism, however, implies a high operational complexity to guarantee that all the available IOPS MC system within the network are fully synchronized with the primary MC system before a backhaul failure. Besides, it involves the distribution and storage of all service and user related data in all available IOPS MC systems within a network which may involve further security issues. + +The functional model of solution 4 is based on the off-network functional model. This MC-service-server-less functional model allows communication between the MC users via the IOPS MC system, where the MC services are provided by the MC service clients and the IOPS system only relays the IP traffic. For that, two (new) functional entities in the IOPS MC system are required to provide the IP connectivity functionality to the served MC users. This solution does not require configuration data synchronization between the primary MC system and all available IOPS MC systems. Therefore, a lower operational complexity can be achieved and security issues can also be mitigated. + +## 7.3 Key issue and solution evaluation + +All the key issues and solutions specified in this technical report are listed in table 7.3-1. It includes the mapping of the key issues (clause 4) to the solutions and corresponding solution evaluations. Also, it lists the dependency on other working groups that need consideration during the Rel-17 normative phase. + +**Table 7.3-1: Key issue and solution evaluation** + +| Key issues | Solution | Evaluation (subclause reference) | Dependency on other working groups | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------|------------------------------------| +| Key issue 2-1 - MC system configuration data synchronization | Solution 1 - UE and user data synchronization | 6.1.3 | None | +| Key issue 2-2 - MC service client configuration for IOPS | Solution 8 - MC service client configuration for IOPS | 6.8.2 | None | +| Key issue 2-3 - on how to handle an MC UE switching to/from an IOPS MC system | Solution 6 - Procedure for switching from the primary MC system to an IOPS MC system
Solution 7 - IOPS notification to MC UEs | 6.6.3, 6.7.3 | None | +| Key issue 2-4 - IOPS architecture | (see NOTE 1) | | | +| Key issue 2-5 - on ongoing communication continuity when backhaul is recovered | (see NOTE 2) | | | +| Key issue 2-6 - on support MBMS in IOPS | (see NOTE 3) | | | +| Key issue 2-7 - on determining a list of MC users connected to the IOPS MC system | Solution 9 - Functionality for determining the MC user registration status in IOPS | 6.9.2 | None | +| NOTE 1: The evaluation of the solutions related to key issue 2-4 is described in subclause 7.2. | | | | +| NOTE 2: There was no solution addressing key issue 2-5. However, based on how the IOPS mode of operation is defined in 3GPP TS 23.401 Annex K, when the IOPS mode of operation ceases the MC UEs are moved to Idle mode. Therefore, the MC UEs are required to reselect the normal PLMN and attach again to the macro EPC. So, ongoing communication continuity cannot be achieved based on the current definition of the IOPS mode of operation. | | | | +| NOTE 3: MBMS support in IOPS has not been addressed during this study. However, it can be addressed as part of the normative phase. | | | | + +Solutions 7, 8 and 9 addressing key issues 2-3, 2-2 and 2-7, respectively, can be implemented for both on-network and off-network based IOPS MC systems. + +Solution 1 addressing key issue 2-1 is based on an on-network functional model. As described in clause 6.1, this solution entails an issue about how an on-network based MC IOPS system can handle missing user and service parameters that are not available at the MC clients and required for a normal on-network operation. This means that the IOPS MC system cannot be fully based on the specified on-network procedures. Instead, new mechanisms need to be considered for the operation of the IOPS MC system under the situation of these missing parameters. This can be translated to a high standardization impact. Also, this can lead to a high implementation and operational complexity for an on-network based MC system being able to operate under normal operation as well as IOPS mode of operation. + +Also, considering that an IOPS solution may include the availability and deployment of several IOPS MC systems within a network, the required footprint and complexity to implement and deploy on-network based IOPS MC systems will be much higher than off-network based IOPS MC systems. + +On the other hand, as described in subclause 7.2, in an off-network based IOPS MC system, i.e. solution 4, the key issue 2-1 is mitigated. This requires, however, that the already specified off-network protocol and related procedures are enhanced, so that the off-network application can be used regardless which transport is utilized. Hence, the off-network application can be enabled to operate over different (3GPP and non-3GPP) IP-based transports, e.g. over LTE ProSe (as defined today), over the IOPS MC system (based on solution 4), and others (e.g. 5G). + +# --- 8 Conclusions + +This technical report fulfills the objectives of the study on mission critical services access aspects (MCSAA), including the following: + +- 1) Identification of key issues (clause 4) and architecture requirements (clause 5). +- 2) Identification of architectural requirements. +- 3) Application architecture solutions and individual solutions (clause 6) addressing the key issues (clause 4). +- 4) Overall evaluation (clause 7) of the solutions. + +The results from the study have identified the following observations: + +- The implementation of a synchronization mechanism between all available IOPS MC systems and the primary MC system implies a high operational complexity. +- The need of service and user related data synchronization between all the IOPS MC systems and the primary MC system may represent further security issues. +- An off-network functional model based solution does not require configuration data synchronization between the primary MC system and all available IOPS MC systems. Also, it mitigates security issues. +- An on-network based IOPS MC system where the configuration data is provisioned by the MC service clients will need the specification of new procedures and mechanisms to operate under the situation of having missing required parameters. This can lead to a high implementation and operational complexity for an on-network based MC system being able to operate under normal operation as well as IOPS mode of operation. +- The required footprint and complexity to implement and deploy on-network based IOPS MC systems will be much higher than off-network based IOPS MC systems. +- The off-network application can be enhanced, so that they are enabled to operate over different (3GPP and non-3GPP) IP-based transports, e.g. over LTE ProSe (as defined today), over the IOPS MC system (based on solution 4), and others (e.g. 5G). + +NOTE: The solutions identified in this study are based on the IOPS mode of operation described in 3GPP TS 23.401 Annex K. However, for the case of a backhaul failure the access network aspects, e.g. security aspects at the network layer, need to be further addressed. + +The results from the study will be considered for the follow-up normative work in Release 17, as follows: + +- 1) The support of MC services on IOPS will be based on an IOPS MC system functional model that does not require configuration data synchronization with the primary MC system. +- 2) The off-network based solution 4 (subclause 6.4) is the preferred option to be considered as the baseline functional model for the support of MC services during the IOPS mode of operation, including: + - a. Enhancing, if required, the off-network application related procedures to enable them to operate over LTE ProSe (as today) as well as over IOPS. +- 3) Key issues (clause 4) and individual solutions (clause 6) will be considered, but not limited to, as candidate solutions for the support of MC services during the IOPS mode of operation. + +The dependencies to other 3GPP groups have been identified in the overall evaluation (clause 7). + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|----|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-03 | SA6#22 | | | | | TR skeleton | 0.0.0 | +| 2018-03 | SA6#22 | | | | | TR Skeleton agreed in SA6#22: S6-180316
Implemented pCR approved in SA6#22: S6-180432, S6-180495
Editorial changes by rapporteur | 0.1.0 | +| 2018-04 | SA6#23 | | | | | Implemented pCR approved in SA6#23: S6-180664, S6-180704, S6-180705, S6-180717
Editorial changes by the rapporteur | 0.2.0 | +| 2018-05 | SA6#24 | | | | | Implemented pCR approved in SA6#24: S6-180901, S6-180902, S6-180962, S6-180963

Editorial changes by the rapporteur | 0.3.0 | +| 2018-07 | SA6#25 | | | | | Implemented pCR approved in SA6#25: S6-181189, S6-181254

Editorial changes by the rapporteur | 0.4.0 | +| 2018-10 | SA6#26 | | | | | Implemented pCRs approved in SA6#15: S6-181545, S6-181564, S6-181590
Editorial changes by the rapporteur | 0.5.0 | +| 2018-12 | SA6#27 | | | | | Implemented pCR approved in SA6#27: S6-181842 | 0.6.0 | +| 2018-12 | SA#82 | SP-181143 | | | | Presentation for information at SA#82 | 1.0.0 | +| 2019-12 | SA6#28 | | | | | Implemented pCR approved in SA6#28: S6-190270 | 1.1.0 | +| 2019-03 | SA6#29 | S6-190516 | | | | Approved pCR on IOPS discovery procedure | 1.2.0 | +| 2019-04 | SA6#30 | | | | | Implemented pCRs approved in SA6#30: S6-190574, S6-190731, S6-190732, S6-190733, S6-190735, S6-190870, S6-190871
Editorial changes by the rapporteur | 1.3.0 | +| 2019-05 | SA6#31 | | | | | Implemented pCRs approved in SA6#31: S6-191086, S6-191197, S6-191198.
Editorial changes by the rapporteur | 1.4.0 | +| 2019-05 | SA#84 | SP-190470 | | | | Presentation for Approval at SA#84 | 2.0.0 | +| 2019-06 | SA#84 | SP-190470 | | | | MCC Editorial update for publication after TSG SA approval (SA#84) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23783/01141eb99b707de5aead56f84afe3b1f_img.jpg b/marked/Rel-16/23_series/23783/01141eb99b707de5aead56f84afe3b1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2870d66c784bf2b8023f31cc5ec3c8d600c1fd28 --- /dev/null +++ b/marked/Rel-16/23_series/23783/01141eb99b707de5aead56f84afe3b1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:032e0678b8fde6e3502c5a7d31541edc70b8b6d8d3473e1d38b7e38a0915c0b3 +size 53986 diff --git a/marked/Rel-16/23_series/23783/02e16c8e8e61c2706b5c0129674884a8_img.jpg b/marked/Rel-16/23_series/23783/02e16c8e8e61c2706b5c0129674884a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8756f24caac0c97b1bd338acc2aead1e91a13606 --- /dev/null +++ b/marked/Rel-16/23_series/23783/02e16c8e8e61c2706b5c0129674884a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5d33d8252015ff5d1abe3099d83df708c194da035b9550cb97182d99f023fa8 +size 62552 diff --git a/marked/Rel-16/23_series/23783/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg b/marked/Rel-16/23_series/23783/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ad762b579e96e12d8041637fc3624cbd88cfb44 --- /dev/null +++ b/marked/Rel-16/23_series/23783/03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4ee19ea092a4abc3d7757db672129789d36c35c946c1666a1c6002730868491 +size 40009 diff --git a/marked/Rel-16/23_series/23783/04867b54e8cdb31a034edbb472a41162_img.jpg b/marked/Rel-16/23_series/23783/04867b54e8cdb31a034edbb472a41162_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4de1c621f203c8252cb194e83c5dca1eb75a24de --- /dev/null +++ b/marked/Rel-16/23_series/23783/04867b54e8cdb31a034edbb472a41162_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4acedf8d36bef09c3fd62a0aed0a446edaa774cc67404c42a4077d4a3d2430d9 +size 37448 diff --git a/marked/Rel-16/23_series/23783/04f7b8f64493f6d83188232f10f86fe2_img.jpg b/marked/Rel-16/23_series/23783/04f7b8f64493f6d83188232f10f86fe2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ba265e2e6fd079b7741b31b5bd70f7fb9f37c91 --- /dev/null +++ b/marked/Rel-16/23_series/23783/04f7b8f64493f6d83188232f10f86fe2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:016ba284453e2bd96c4af0cd0f58f92b92aa0de4aefa8e7b5f93f2f99e297374 +size 34936 diff --git a/marked/Rel-16/23_series/23783/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/23_series/23783/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9b7d1855f49db69c6b760913c91236612834f63 --- /dev/null +++ b/marked/Rel-16/23_series/23783/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4bfdbd612a5626cef6cb26d7f9234d8e052ff188e454974e76f991b40d796e0 +size 60764 diff --git a/marked/Rel-16/23_series/23783/06da11ab76cacc38bbcd714e437797ea_img.jpg b/marked/Rel-16/23_series/23783/06da11ab76cacc38bbcd714e437797ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c3a692ca322a7dc038f6ad22b1551948a11f3bc --- /dev/null +++ b/marked/Rel-16/23_series/23783/06da11ab76cacc38bbcd714e437797ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d483be22e2f87df13dfa36b178a275c1921fb54b54ee11374a779dfc107a539 +size 48699 diff --git a/marked/Rel-16/23_series/23783/070352b751dd0711b8ac6ddfa6df1d98_img.jpg b/marked/Rel-16/23_series/23783/070352b751dd0711b8ac6ddfa6df1d98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a698012d71f104c8a63eac47e7d665e336dde8b9 --- /dev/null +++ b/marked/Rel-16/23_series/23783/070352b751dd0711b8ac6ddfa6df1d98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40b5b62455b220fd692dd673fcc795e69709cafc40bc74d99f9818a2f73a4a9d +size 35451 diff --git a/marked/Rel-16/23_series/23783/08f6ace0c83e7394657fa372b47aec04_img.jpg b/marked/Rel-16/23_series/23783/08f6ace0c83e7394657fa372b47aec04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37e2dfd1fcba29a14a1e17e14369329aad31d725 --- /dev/null +++ b/marked/Rel-16/23_series/23783/08f6ace0c83e7394657fa372b47aec04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1229a6483886f9ca797599834fa5581789b1d79c3a382870ad1be0794a5c5fc5 +size 48490 diff --git a/marked/Rel-16/23_series/23783/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-16/23_series/23783/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ef0c3f7f1565df196a9a0f8ffbaee9a6294b190 --- /dev/null +++ b/marked/Rel-16/23_series/23783/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d9e18aa27678c1feabe2610dc2580f2465b11c8c7ef4b69fdd3de849b9262551 +size 37778 diff --git a/marked/Rel-16/23_series/23783/0997dbaa9dfecedd60029d70b53327b8_img.jpg b/marked/Rel-16/23_series/23783/0997dbaa9dfecedd60029d70b53327b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9a43246650d658da99458a34d700a6b3a8c6bad --- /dev/null +++ b/marked/Rel-16/23_series/23783/0997dbaa9dfecedd60029d70b53327b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aeccf0492d0aa426be9e010881d17ab754679513d7aa3d74c9148a75e0ffe890 +size 44808 diff --git a/marked/Rel-16/23_series/23783/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg b/marked/Rel-16/23_series/23783/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f73deb3cfa022a620445fb7d7d1095818eaecc7 --- /dev/null +++ b/marked/Rel-16/23_series/23783/0a3ab80d35c138cc4038b5758f6ff34d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66576c43c54e25f4beb75cdfc371e34f630d1667409f52c9db819c381bbf72e4 +size 43129 diff --git a/marked/Rel-16/23_series/23783/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-16/23_series/23783/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c01def21953980f745e1386fe306a08e57e642ea --- /dev/null +++ b/marked/Rel-16/23_series/23783/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c72eea1ebc3786e89b4b29bae5aff2fb5bfbdfb0dceb92dc9b32a3950adf86b1 +size 26737 diff --git a/marked/Rel-16/23_series/23783/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-16/23_series/23783/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbd0726ec06d5f3f60af8c1415a6a5037361441d --- /dev/null +++ b/marked/Rel-16/23_series/23783/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc81d657f9eecc836c7e9d39c9b22d172850e5e5794caedb5e3c90861ffb0476 +size 44966 diff --git a/marked/Rel-16/23_series/23783/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg b/marked/Rel-16/23_series/23783/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1acd842f940fa3c046defdd226a253058f45cd74 --- /dev/null +++ b/marked/Rel-16/23_series/23783/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49b87fcee0e71a2a23f7d5afd081e18cf8d9b53fa7b8815e74c274040c7c1ed4 +size 44610 diff --git a/marked/Rel-16/23_series/23783/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-16/23_series/23783/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c15f38de1b34ae4c4dfd1029e67ce47435e19b8a --- /dev/null +++ b/marked/Rel-16/23_series/23783/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7d3254e000b2a267e19d6d7a66b916659fec6ab85e880b748c5fd753fe4d581 +size 60951 diff --git a/marked/Rel-16/23_series/23783/0ff19975027a3c5177519975f9af055f_img.jpg b/marked/Rel-16/23_series/23783/0ff19975027a3c5177519975f9af055f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78509e494e955213cb063263b8fac9bf4e78a37d --- /dev/null +++ b/marked/Rel-16/23_series/23783/0ff19975027a3c5177519975f9af055f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff0e3f763c58816891787d7c882cce55ee9eb584c9d75e2034ab044c372a1dcb +size 53339 diff --git a/marked/Rel-16/23_series/23783/1018d0db7bb02c169f646cb9cc244dc6_img.jpg b/marked/Rel-16/23_series/23783/1018d0db7bb02c169f646cb9cc244dc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..386eab0ddd1ded9aae97c7623cc1c298335ca98c --- /dev/null +++ b/marked/Rel-16/23_series/23783/1018d0db7bb02c169f646cb9cc244dc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b11ba4eb7d44624d96de139be3b9ea4997182907acd7839d37d9f7deb38bf1ac +size 65755 diff --git a/marked/Rel-16/23_series/23783/10bf8762a8e8d9385609cc6fb11061fe_img.jpg b/marked/Rel-16/23_series/23783/10bf8762a8e8d9385609cc6fb11061fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d6bd459afae1d39278a376cf95d3070740fa9d8d --- /dev/null +++ b/marked/Rel-16/23_series/23783/10bf8762a8e8d9385609cc6fb11061fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:290d203689cb7999b4ecc2b6e1d6aada2f174dbf79528b2b29a9b556b419b3cd +size 29561 diff --git a/marked/Rel-16/23_series/23783/10cc1e74f2b71404f021bb8b3cec0ff0_img.jpg b/marked/Rel-16/23_series/23783/10cc1e74f2b71404f021bb8b3cec0ff0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26aca00e777b1194ff87e30b3850facfd60d1ccb --- /dev/null +++ b/marked/Rel-16/23_series/23783/10cc1e74f2b71404f021bb8b3cec0ff0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ad8ec3c15abdd49baf2eafe0a2e60bbc87b21861f31b0b7682fee25096b3481 +size 63439 diff --git a/marked/Rel-16/23_series/23783/114902bbeea56bda01b64b43fad41920_img.jpg b/marked/Rel-16/23_series/23783/114902bbeea56bda01b64b43fad41920_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91186e17542877265a419a4d85bf595c9e7d8df9 --- /dev/null +++ b/marked/Rel-16/23_series/23783/114902bbeea56bda01b64b43fad41920_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:266574cfbf761cda466fa4da2354e869a6f53a812202106e8ff26044adf0b399 +size 49789 diff --git a/marked/Rel-16/23_series/23783/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/Rel-16/23_series/23783/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fe57ee23b91831cb1b54406ff1c7af57e7a4736 --- /dev/null +++ b/marked/Rel-16/23_series/23783/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6b8f3042f3160189a244eb7daee97a66e7d16a76c9803ed5cf07613447a53c56 +size 66370 diff --git a/marked/Rel-16/23_series/23783/1316d63eca7b84e13c27f55f0027b7b5_img.jpg b/marked/Rel-16/23_series/23783/1316d63eca7b84e13c27f55f0027b7b5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f98699b80b0f153fc7eaf1c6e27a9ad51da8447c --- /dev/null +++ b/marked/Rel-16/23_series/23783/1316d63eca7b84e13c27f55f0027b7b5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23aa95fc44b1ff565ded38eae0ca913ca44f36646797ae953f56a7fbb9c21623 +size 73809 diff --git a/marked/Rel-16/23_series/23783/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg b/marked/Rel-16/23_series/23783/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54038dfddeda3ce71a6f9cda1e5716a4f741effd --- /dev/null +++ b/marked/Rel-16/23_series/23783/145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09e64bf7153d9c2ccca10feb919d6a6a0c5b0c7bb2b74775a441824093854601 +size 50637 diff --git a/marked/Rel-16/23_series/23783/17439b945bd5156395c7ba15bf04f8fb_img.jpg b/marked/Rel-16/23_series/23783/17439b945bd5156395c7ba15bf04f8fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f89681bdaa280338c7f161e08e49f8f29e95c2a2 --- /dev/null +++ b/marked/Rel-16/23_series/23783/17439b945bd5156395c7ba15bf04f8fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2e0026aa695ab3d09ee0bbae1ba0491b70344509b816f4ad525ab52b43c47c8 +size 49263 diff --git a/marked/Rel-16/23_series/23783/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/23_series/23783/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cafef63d0620bb966f8053e2032474a03937da61 --- /dev/null +++ b/marked/Rel-16/23_series/23783/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23228d4899e6bb7d67a7117ee3627440dea958451f4f976d6654584788c3ea9e +size 34997 diff --git a/marked/Rel-16/23_series/23783/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg b/marked/Rel-16/23_series/23783/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45ea8e1e94660564558f21c6bf075e054c429396 --- /dev/null +++ b/marked/Rel-16/23_series/23783/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4240d1304c7936b350f4554228e614a24b0271924321e28b6043d7f32bdeeed5 +size 46311 diff --git a/marked/Rel-16/23_series/23783/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/marked/Rel-16/23_series/23783/19a59d6b53059ebd27b13c98793f88e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e12d62ac8505bdb1880b41bb45646236714d3ac --- /dev/null +++ b/marked/Rel-16/23_series/23783/19a59d6b53059ebd27b13c98793f88e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:409c8026466e9bca9855c115b048cb6133712dd752165ca50d2e7ee76551cace +size 78383 diff --git a/marked/Rel-16/23_series/23783/19a5f0db57a21a0e82a7f326083e96fd_img.jpg b/marked/Rel-16/23_series/23783/19a5f0db57a21a0e82a7f326083e96fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4814fff48d66e231ea78030e78ca08dc1fcdd155 --- /dev/null +++ b/marked/Rel-16/23_series/23783/19a5f0db57a21a0e82a7f326083e96fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af47cf0569f7c134b9be212ab95008f26331920200aef7b0a5fbc5f71fb0b02f +size 55431 diff --git a/marked/Rel-16/23_series/23783/1a1484a99fee36bd3ca4e40fe1538bf8_img.jpg b/marked/Rel-16/23_series/23783/1a1484a99fee36bd3ca4e40fe1538bf8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..094a62ee6dc6c9404207483213b9ae45c539ebeb --- /dev/null +++ b/marked/Rel-16/23_series/23783/1a1484a99fee36bd3ca4e40fe1538bf8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00d9ce31a23d97e12d5ec81318711bc19b5c1f06f46c1eca8d8ff5e33fca9f25 +size 71092 diff --git a/marked/Rel-16/23_series/23783/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23783/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c592539406351ed4b8e95edafe536e61deda3f54 --- /dev/null +++ b/marked/Rel-16/23_series/23783/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba70e66ddeaed919450ad73886bd00a68d8c25a4b7eb6cf05aaa0d1dff7b222c +size 82281 diff --git a/marked/Rel-16/23_series/23783/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg b/marked/Rel-16/23_series/23783/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d26af3329b511da218c943d697d62b95e9fe8483 --- /dev/null +++ b/marked/Rel-16/23_series/23783/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b512632f07afc103cf7287fa74e58e4eb85e553b2ac35d87ed472a4223f030a1 +size 43900 diff --git a/marked/Rel-16/23_series/23783/1c79f31a718d63814feb28ab46f64f19_img.jpg b/marked/Rel-16/23_series/23783/1c79f31a718d63814feb28ab46f64f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..561206b6913c7c6fc3fa2d14d601318bdbc1fd3c --- /dev/null +++ b/marked/Rel-16/23_series/23783/1c79f31a718d63814feb28ab46f64f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9122b479048cd058dcefded3537af31f010bfdf36db9fe70b67f02d4f3712b57 +size 19834 diff --git a/marked/Rel-16/23_series/23783/1ca688982d625c3b8a8e382b675de466_img.jpg b/marked/Rel-16/23_series/23783/1ca688982d625c3b8a8e382b675de466_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..96b2c6b281ff0eecfdda7de85725a36f1b7e3d28 --- /dev/null +++ b/marked/Rel-16/23_series/23783/1ca688982d625c3b8a8e382b675de466_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2ad6589fb317964ab4042e6487b3b8a225ddd48c7015481c897e825c4f93f1e +size 20353 diff --git a/marked/Rel-16/23_series/23783/1ce027dfd26183da52137cf990213724_img.jpg b/marked/Rel-16/23_series/23783/1ce027dfd26183da52137cf990213724_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..476bf308703cd50189c4528f321feb9632df0462 --- /dev/null +++ b/marked/Rel-16/23_series/23783/1ce027dfd26183da52137cf990213724_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b69848b46f39473f9a8d918c83d1aa5dbb20f828fc775f62e7897b12d366309 +size 73506 diff --git a/marked/Rel-16/23_series/23783/212c50c4e3d043c989037a01e13c1a98_img.jpg b/marked/Rel-16/23_series/23783/212c50c4e3d043c989037a01e13c1a98_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e4a3c24f8f7893f9cfc21ec7ead3704758b62db --- /dev/null +++ b/marked/Rel-16/23_series/23783/212c50c4e3d043c989037a01e13c1a98_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78e19f036fbb8a7339c38cfd21ece06559eab69328c9de8842fc4953956ff2e9 +size 47303 diff --git a/marked/Rel-16/23_series/23783/2226ff0a3945d72d56b5150c5618e71c_img.jpg b/marked/Rel-16/23_series/23783/2226ff0a3945d72d56b5150c5618e71c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5c64b6dd686fad0242e5bd775b7937a2ad966920 --- /dev/null +++ b/marked/Rel-16/23_series/23783/2226ff0a3945d72d56b5150c5618e71c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:370685b6892b9fd2a042b6f9dd5a8669f1891a6259882c2cc8c45fb44a3205dd +size 17871 diff --git a/marked/Rel-16/23_series/23783/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg b/marked/Rel-16/23_series/23783/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..821185e7a99cd48f7ce790cbf3cbf29c2f4d8119 --- /dev/null +++ b/marked/Rel-16/23_series/23783/2438c4dd81a8b76ec881d47d87b11fc3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd7b6cc21f500891c198fe2f3b9dede6ff65541551b4359edcbacd967eecf9c6 +size 47528 diff --git a/marked/Rel-16/23_series/23783/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23783/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d0d30726c535d6fccd07f185f3d4883082dbce1 --- /dev/null +++ b/marked/Rel-16/23_series/23783/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c76b20f03aaace6a0d85bf774835b16d304c75b9819e9afbc842b870f4a451d +size 42289 diff --git a/marked/Rel-16/23_series/23783/279ae82c0ef66d5fb9a204a4218a78dc_img.jpg b/marked/Rel-16/23_series/23783/279ae82c0ef66d5fb9a204a4218a78dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c44bfb445e5fa538a314dc47d30acb2cf30d8720 --- /dev/null +++ b/marked/Rel-16/23_series/23783/279ae82c0ef66d5fb9a204a4218a78dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:896a1a70967feef7c9c71d43e70339bc87992d0c844a2aa7a7dfabc5e55f2f16 +size 52427 diff --git a/marked/Rel-16/23_series/23783/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23783/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7919e6fc204cf8eea3b1d6635305dda6982c4624 --- /dev/null +++ b/marked/Rel-16/23_series/23783/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3ca1aa690e7dd3496f48d290d65a65e5a04ced22cb22fd06aafb9deb6a800c0 +size 51539 diff --git a/marked/Rel-16/23_series/23783/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/23_series/23783/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b0c9f6d665a58affd523aaf412778d3b4666a98 --- /dev/null +++ b/marked/Rel-16/23_series/23783/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc87db94319a0eed00b8e60f3f328e471f046d10ee9619e81531486d0cb8b5c8 +size 120841 diff --git a/marked/Rel-16/23_series/23783/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23783/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccabf227a60ebb8e2520f95801e4a44c3de60452 --- /dev/null +++ b/marked/Rel-16/23_series/23783/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88c8e7300eade62e38921b9abf952c4ef854bee9a59616fe6e158fe19c642edd +size 94520 diff --git a/marked/Rel-16/23_series/23783/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-16/23_series/23783/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..875bbd204014abbd33d91bd789d52e5dbafb7d87 --- /dev/null +++ b/marked/Rel-16/23_series/23783/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e291c691e2eaec95f0d0f3343ed3b51459e8fa981611703b363f177e28cada35 +size 81257 diff --git a/marked/Rel-16/23_series/23783/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23783/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f833ddccd7cb28902066c395cfd37b1d678016a --- /dev/null +++ b/marked/Rel-16/23_series/23783/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:851bce699e7b5625fea00b2162783eecaba338f391a8818ca222ac9422ec9a62 +size 91023 diff --git a/marked/Rel-16/23_series/23783/2bc39576969969ffe6d3f3d5264bba75_img.jpg b/marked/Rel-16/23_series/23783/2bc39576969969ffe6d3f3d5264bba75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f8dc6bbe8de14a5682988136c3ef085d4522601 --- /dev/null +++ b/marked/Rel-16/23_series/23783/2bc39576969969ffe6d3f3d5264bba75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbff985903e993ff2f96e6e55a9607205eb54943ba4f43fb0a8101a84a90da97 +size 17249 diff --git a/marked/Rel-16/23_series/23783/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-16/23_series/23783/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27e84404173c543bbf5f38089360a97d6ca2efc4 --- /dev/null +++ b/marked/Rel-16/23_series/23783/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5a8e3622320457a07757e17fb74179c191149a0a74eaf415515130795e65de1 +size 66131 diff --git a/marked/Rel-16/23_series/23783/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/Rel-16/23_series/23783/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7310266647370f1e6b501aa8b16a0ad4198821de --- /dev/null +++ b/marked/Rel-16/23_series/23783/2f587210e4f97c32758c5972e2e83d20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17bdb11451b93c5a68ec00310eb309525dbe77a5b7898b4c8e0838014033192c +size 80233 diff --git a/marked/Rel-16/23_series/23783/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/marked/Rel-16/23_series/23783/315bdbeafb39026e19b77c26b19d9d1f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e603e490eefef1281439eaf9b8e8b1495d377553 --- /dev/null +++ b/marked/Rel-16/23_series/23783/315bdbeafb39026e19b77c26b19d9d1f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7dcb8ba21a9d679d8a2cdfde37b9b7f5c03aed8a934e608bc8280e428331c666 +size 56379 diff --git a/marked/Rel-16/23_series/23783/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-16/23_series/23783/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c61120d033d1ce5dc6c110a52b927d161643f1ce --- /dev/null +++ b/marked/Rel-16/23_series/23783/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:907fa586a5f03bf050d512175d84e557ed4b7a0b085b7b4f93983a2972cdc927 +size 79238 diff --git a/marked/Rel-16/23_series/23783/3263a25e110201638bda790456af2909_img.jpg b/marked/Rel-16/23_series/23783/3263a25e110201638bda790456af2909_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7ea66e032ac76a0106b8c15ac6866894d899562 --- /dev/null +++ b/marked/Rel-16/23_series/23783/3263a25e110201638bda790456af2909_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b6eb39806457d3fa122a800ebcecc8bd3d49a159584475a05ee6c832023aaa8 +size 83696 diff --git a/marked/Rel-16/23_series/23783/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/23_series/23783/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1cd8fa8ea4293593764e45f62b6937987568d2b --- /dev/null +++ b/marked/Rel-16/23_series/23783/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d48f7352779e59c333e1f18be2dd697ae5660091626840edba3954435f0a455e +size 60838 diff --git a/marked/Rel-16/23_series/23783/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/23_series/23783/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b90dcf630848c9b3304cf6dd380258550d4ec25 --- /dev/null +++ b/marked/Rel-16/23_series/23783/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a6826bd3807c6e5e5f54f95629d98da710bd9749c203d10fa9f387989032683 +size 59368 diff --git a/marked/Rel-16/23_series/23783/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-16/23_series/23783/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bc6d3e46f0b5edf01bdd5c6690d48f835f0aa3a --- /dev/null +++ b/marked/Rel-16/23_series/23783/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbecfbe09a2500fca0af955b775e6e646d3439ce81871a09dfd6fd706df74e56 +size 63172 diff --git a/marked/Rel-16/23_series/23783/333992a0b3b7a9d826f72f7bf199221b_img.jpg b/marked/Rel-16/23_series/23783/333992a0b3b7a9d826f72f7bf199221b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..170128dd4ccc5ed4a04da6b77b0bed418863ca69 --- /dev/null +++ b/marked/Rel-16/23_series/23783/333992a0b3b7a9d826f72f7bf199221b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f41a027048c9a4c5841e40bcc3535ad27aba48322bdeb73a34a316fc3d67292 +size 94859 diff --git a/marked/Rel-16/23_series/23783/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/23_series/23783/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eff9078fdc187871316b8064c00bf6328658fdef --- /dev/null +++ b/marked/Rel-16/23_series/23783/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fdaaba491bb8dd1660f2964ccfbcc229a79bb02dd0eb3b2dd92708e32245df0 +size 69778 diff --git a/marked/Rel-16/23_series/23783/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-16/23_series/23783/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eeb2086cd6f3f03fcef58dd42099fe0353535df6 --- /dev/null +++ b/marked/Rel-16/23_series/23783/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1a12a54b67ecac7c7492f1ac31d5cc1b060f9d5bb7e2cb72fdab91024e78792 +size 101274 diff --git a/marked/Rel-16/23_series/23783/367378559e35017a5e1a6f5c30798c5a_img.jpg b/marked/Rel-16/23_series/23783/367378559e35017a5e1a6f5c30798c5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b70d5ccc49008ce4cc2e3bffa2b07582238da12 --- /dev/null +++ b/marked/Rel-16/23_series/23783/367378559e35017a5e1a6f5c30798c5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0315c381a98c09b57a2c6642a96677b4173f1759510357a168404eb49209f85f +size 116429 diff --git a/marked/Rel-16/23_series/23783/376f80eb8a41369e87da63a0210d173e_img.jpg b/marked/Rel-16/23_series/23783/376f80eb8a41369e87da63a0210d173e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..775a93292bb7a6759f053dff1bf0116a17ad5b29 --- /dev/null +++ b/marked/Rel-16/23_series/23783/376f80eb8a41369e87da63a0210d173e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:733a7736ce5a155d35c022a7d3a92d61202cb078758b198cba6d76aaa3b4a4a1 +size 61971 diff --git a/marked/Rel-16/23_series/23783/37a6ab1d23efb9dc00cfae09d353b1da_img.jpg b/marked/Rel-16/23_series/23783/37a6ab1d23efb9dc00cfae09d353b1da_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71f22d23e5630d021d4db465bd73bea0f0c9aad1 --- /dev/null +++ b/marked/Rel-16/23_series/23783/37a6ab1d23efb9dc00cfae09d353b1da_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08854073579c738c594783f4e462d791e2412e0217c150ab09ae3eabff7263d1 +size 49559 diff --git a/marked/Rel-16/23_series/23783/387a5f91aee45a659456a67b070bc047_img.jpg b/marked/Rel-16/23_series/23783/387a5f91aee45a659456a67b070bc047_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db0f931d8d126e04799849fea0e2d97d7c31e5bd --- /dev/null +++ b/marked/Rel-16/23_series/23783/387a5f91aee45a659456a67b070bc047_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4297257b0a31e6812562e8af07fae51fad91cf3f32e9c8e2d92f36fa812861b +size 31358 diff --git a/marked/Rel-16/23_series/23783/3a6bf5d7dd794e6f7fb608b797c92fe7_img.jpg b/marked/Rel-16/23_series/23783/3a6bf5d7dd794e6f7fb608b797c92fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d920bfaddc3aa30757ac356a2a739bbc040dc9f3 --- /dev/null +++ b/marked/Rel-16/23_series/23783/3a6bf5d7dd794e6f7fb608b797c92fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f69a7c613adf4c18de9660a3d4d7711edfaadada9b5f993d778a5e9c1de6ff15 +size 24742 diff --git a/marked/Rel-16/23_series/23783/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg b/marked/Rel-16/23_series/23783/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..435ca6289b3a03c27fb79314b97c8685a9bf77c1 --- /dev/null +++ b/marked/Rel-16/23_series/23783/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:56a3793d7bde9dc54f78b8b5310b84eeb64c004ab316e51df1a772f4b2fb240a +size 43234 diff --git a/marked/Rel-16/23_series/23783/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg b/marked/Rel-16/23_series/23783/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..589061ae6394ba96c5b392c1e8e97382cde2bc82 --- /dev/null +++ b/marked/Rel-16/23_series/23783/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6190dd54f95d94e5674669139a17f95f9ef59a16c3a721930f2c4aefd13301d2 +size 80573 diff --git a/marked/Rel-16/23_series/23783/408c4798ea60469e0728a7cbbd598668_img.jpg b/marked/Rel-16/23_series/23783/408c4798ea60469e0728a7cbbd598668_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c1749db38ded9114eba86b805fafbf3a738f5aa --- /dev/null +++ b/marked/Rel-16/23_series/23783/408c4798ea60469e0728a7cbbd598668_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81a5f69d01d64742b711873f9c81c3b5aae43fc9a7322a6823fe0e2ddbef9490 +size 39121 diff --git a/marked/Rel-16/23_series/23783/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-16/23_series/23783/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f95e4b3a51e8a262b480cc3107be5779cbb8834d --- /dev/null +++ b/marked/Rel-16/23_series/23783/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d8d27427a165ab6a443fde4d6534eeb2f2238cd6fd00fc8044dc9537f91ba17 +size 51792 diff --git a/marked/Rel-16/23_series/23783/410562339ce067fdc6fa41940c118658_img.jpg b/marked/Rel-16/23_series/23783/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd403a8527a9c03faee6c11324a74cdd317d7343 --- /dev/null +++ b/marked/Rel-16/23_series/23783/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c28d16cca15b195772563e4866da6c1143ee03eb75f310ec6694a18dc442d79a +size 23948 diff --git a/marked/Rel-16/23_series/23783/42f0611a8a2766c986ff45551918ca5d_img.jpg b/marked/Rel-16/23_series/23783/42f0611a8a2766c986ff45551918ca5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e74de3444ae357af3a47080fbc0a5d5d3e309d89 --- /dev/null +++ b/marked/Rel-16/23_series/23783/42f0611a8a2766c986ff45551918ca5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2937e4d025f197a2a0d0e6af23ff39defb2582501dcf259402b0be55df2fe7c4 +size 16363 diff --git a/marked/Rel-16/23_series/23783/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23783/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..104ddb4b3743cfbb0e991e67eb8061fab40e5560 --- /dev/null +++ b/marked/Rel-16/23_series/23783/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7aa0f593587c7edb252a934a1a4a410ba8561d8e27af31ce21fb52ef160edbda +size 40281 diff --git a/marked/Rel-16/23_series/23783/443ee770f0d3d98d7411497a3191e2e0_img.jpg b/marked/Rel-16/23_series/23783/443ee770f0d3d98d7411497a3191e2e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dde7a147b179ca6604d200d97c4404cc503838d3 --- /dev/null +++ b/marked/Rel-16/23_series/23783/443ee770f0d3d98d7411497a3191e2e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:96ea536912094c5e8b7e0a4ac15bf8f1cdfe96939ede6ac8d16fb940318ad66e +size 49664 diff --git a/marked/Rel-16/23_series/23783/453a1dc18dd2dd3334d19f453b04d11b_img.jpg b/marked/Rel-16/23_series/23783/453a1dc18dd2dd3334d19f453b04d11b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3aca66ebe0e5c9b539dbf8378158a0f6d65bb8b3 --- /dev/null +++ b/marked/Rel-16/23_series/23783/453a1dc18dd2dd3334d19f453b04d11b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e75f10e0f7ce2da94fade2756c518b64a5f3ef8966710f3612afd45510328ea4 +size 70238 diff --git a/marked/Rel-16/23_series/23783/4636adff5682a064f0ae5f13a1d464a6_img.jpg b/marked/Rel-16/23_series/23783/4636adff5682a064f0ae5f13a1d464a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f89b58d7417493989557ff9c9027f1a16a79585 --- /dev/null +++ b/marked/Rel-16/23_series/23783/4636adff5682a064f0ae5f13a1d464a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:965de961c621574267df94bec14f73d1b256af56ec8f2d7bb8c2d314652c200f +size 21856 diff --git a/marked/Rel-16/23_series/23783/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg b/marked/Rel-16/23_series/23783/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da479d9c272a2b267ffc735c2b41d0ce3ea8374b --- /dev/null +++ b/marked/Rel-16/23_series/23783/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a48642ea146acee559a2d5fb67a1050b487f9b7731f4fc4da719d492a85ca147 +size 103748 diff --git a/marked/Rel-16/23_series/23783/4767b6e106f34fe8b63a6838810bf913_img.jpg b/marked/Rel-16/23_series/23783/4767b6e106f34fe8b63a6838810bf913_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8d1a049d37bc71c7d630680c6b0da744891c86f --- /dev/null +++ b/marked/Rel-16/23_series/23783/4767b6e106f34fe8b63a6838810bf913_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a421bebdcbfdd2cc690d3f70f2f7b93819829e61140bf53e2eae3be5a9fc92e +size 29017 diff --git a/marked/Rel-16/23_series/23783/476fddf3a7afd9a5f77639c39a7aeeac_img.jpg b/marked/Rel-16/23_series/23783/476fddf3a7afd9a5f77639c39a7aeeac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03d03284a79521398a2f7cd4503ef9d90360ddfe --- /dev/null +++ b/marked/Rel-16/23_series/23783/476fddf3a7afd9a5f77639c39a7aeeac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2afc1eaeb95e3b050d8dca47b4587dd1ae8eb2d18c5800df777ec62cc8759b59 +size 19053 diff --git a/marked/Rel-16/23_series/23783/4806f9f95fff13a30d6523bd6ffeac63_img.jpg b/marked/Rel-16/23_series/23783/4806f9f95fff13a30d6523bd6ffeac63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..93eda8d4dd1745615117bbd985aef9f8d2d752ef --- /dev/null +++ b/marked/Rel-16/23_series/23783/4806f9f95fff13a30d6523bd6ffeac63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d6a079d001265cee547e5879945f0ac0ab0c87a4ee34f95eac1f934ba4cece1b +size 122879 diff --git a/marked/Rel-16/23_series/23783/48f209b7c0c1f91af40cfc3466dbd534_img.jpg b/marked/Rel-16/23_series/23783/48f209b7c0c1f91af40cfc3466dbd534_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..664597de1f58c93756860d832f0401a60a53d1f3 --- /dev/null +++ b/marked/Rel-16/23_series/23783/48f209b7c0c1f91af40cfc3466dbd534_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f4337c962d2cccd1b8ffa055d26a4e275a16a72637374a9b91003c66ce69e1e +size 51633 diff --git a/marked/Rel-16/23_series/23783/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg b/marked/Rel-16/23_series/23783/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d31e2b4e2c160e38a92691090fa2efa1e7ce2dd7 --- /dev/null +++ b/marked/Rel-16/23_series/23783/49a49278cad196bdfe0db6b4dd1be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5797db77b259182ba0964c52faca01dd0180d3c8909f3637a1f6f4a00807293 +size 30937 diff --git a/marked/Rel-16/23_series/23783/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Rel-16/23_series/23783/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06ae3b449cdf88c22bea5d0ba23dcb822c81ff50 --- /dev/null +++ b/marked/Rel-16/23_series/23783/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef1cee6f7e463abeb921c92c699b11849e838195132a509b959e55b3c68c1bf2 +size 41297 diff --git a/marked/Rel-16/23_series/23783/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-16/23_series/23783/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..857d736c3cdfc69ba1eabdf283d54704726f625d --- /dev/null +++ b/marked/Rel-16/23_series/23783/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9b7e0262cbc89990d93c37fef598701a6a0162cddbffbbb4d9cf78f437b4c42 +size 63338 diff --git a/marked/Rel-16/23_series/23783/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg b/marked/Rel-16/23_series/23783/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d75c1da410dcb85b04452e15993574a3c9e6412c --- /dev/null +++ b/marked/Rel-16/23_series/23783/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0529a648aa24f282d156fc592ba1c81f8804e07a6df92c0aba9ff019c6c67615 +size 74709 diff --git a/marked/Rel-16/23_series/23783/4f148853ae68fdcf5e43f7604cab457d_img.jpg b/marked/Rel-16/23_series/23783/4f148853ae68fdcf5e43f7604cab457d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..705c1e4cfd502b0d0f7fa5a6df674a1de847e54c --- /dev/null +++ b/marked/Rel-16/23_series/23783/4f148853ae68fdcf5e43f7604cab457d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abff77844bd42a81273feac93935d4bc25ec606d63b9049acf8738ad3a3a3299 +size 49813 diff --git a/marked/Rel-16/23_series/23783/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/marked/Rel-16/23_series/23783/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5af2efdd49477347eeeb697f1bfdd69c97521868 --- /dev/null +++ b/marked/Rel-16/23_series/23783/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0de14581d2df09759a15e4d62db908db8f04e448523b68b616a7ef083b9f8d7 +size 71532 diff --git a/marked/Rel-16/23_series/23783/5152ddc7d77f41ae1eaf931aaac810eb_img.jpg b/marked/Rel-16/23_series/23783/5152ddc7d77f41ae1eaf931aaac810eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a09d306fe369e4689048eceb69e40ad742afbb24 --- /dev/null +++ b/marked/Rel-16/23_series/23783/5152ddc7d77f41ae1eaf931aaac810eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a199bd2ce2ff922caeb3a2573dbd28c92b7f14884e88ba76c4a85a7f6695425b +size 79674 diff --git a/marked/Rel-16/23_series/23783/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg b/marked/Rel-16/23_series/23783/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e59c5ad043bc4a92598df847610908767e25cd7b --- /dev/null +++ b/marked/Rel-16/23_series/23783/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23e06975f3cb8f12398dd412947a5c231f9e2db8cda548ecf70d70ee752fd954 +size 67906 diff --git a/marked/Rel-16/23_series/23783/5492fadb32a8df1ee9f2528a053c9862_img.jpg b/marked/Rel-16/23_series/23783/5492fadb32a8df1ee9f2528a053c9862_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c48cb7d97ea9c6059007635617e10c826a79aa2 --- /dev/null +++ b/marked/Rel-16/23_series/23783/5492fadb32a8df1ee9f2528a053c9862_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50238dee1963707f4c63230ac12aa8aaa450c517f85b8728136a17a52531ca88 +size 57670 diff --git a/marked/Rel-16/23_series/23783/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/marked/Rel-16/23_series/23783/54fabc351eda5228d2fa28cd9ba07971_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62b97548a912e1196d7d21f5be036b69a73f1d9e --- /dev/null +++ b/marked/Rel-16/23_series/23783/54fabc351eda5228d2fa28cd9ba07971_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa8a7e3fd8657d266a771adf5c262af53bef6f7cab5f46d804282c83edf2d664 +size 48156 diff --git a/marked/Rel-16/23_series/23783/552328a9daaf3bc0069424b500025880_img.jpg b/marked/Rel-16/23_series/23783/552328a9daaf3bc0069424b500025880_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4bd43d8fb413ac1f9300998d713c8476bbb441c --- /dev/null +++ b/marked/Rel-16/23_series/23783/552328a9daaf3bc0069424b500025880_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba07a2d6d7e2be665a5e56622d98b2a62f9fc69f2c0979a99c093dba388feb71 +size 41495 diff --git a/marked/Rel-16/23_series/23783/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-16/23_series/23783/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd5861effe6352a84fda4d99e62b1cd923a9fec5 --- /dev/null +++ b/marked/Rel-16/23_series/23783/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfa7047dd0af6cbca964e70ae63bb702b178a53081fc0df2955ca2306c6d9ca9 +size 35132 diff --git a/marked/Rel-16/23_series/23783/573c8f9e728e343b6864e1070c14b8cf_img.jpg b/marked/Rel-16/23_series/23783/573c8f9e728e343b6864e1070c14b8cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77036b4eb99d071187c108f70423f42d37c589da --- /dev/null +++ b/marked/Rel-16/23_series/23783/573c8f9e728e343b6864e1070c14b8cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e080f86f0c326576883d9a81312a946f4876b540455c89c134a07b5c8cb1e13 +size 60795 diff --git a/marked/Rel-16/23_series/23783/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-16/23_series/23783/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c6cde34393c3901293b905cd355ceaf35b765c8 --- /dev/null +++ b/marked/Rel-16/23_series/23783/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:193fe4f997cba730b027faad1f582cfa535ff37d00024f182290f775d0bbea8a +size 82801 diff --git a/marked/Rel-16/23_series/23783/57939c16065211317c5442cf2a4009e0_img.jpg b/marked/Rel-16/23_series/23783/57939c16065211317c5442cf2a4009e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27a32a0d97bf5026b4da8d45f35a2d29a9aa26b4 --- /dev/null +++ b/marked/Rel-16/23_series/23783/57939c16065211317c5442cf2a4009e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1483339dc0d61797e6a50be57ecd3d79b74c9b3bf1f6411cabbe7c7dfd7a2bc3 +size 41487 diff --git a/marked/Rel-16/23_series/23783/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-16/23_series/23783/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5803019d52b03df1e25c123751e0efd7e66a15c9 --- /dev/null +++ b/marked/Rel-16/23_series/23783/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e32c226dde2f760a537a7a679ffc06a950f9b1ac8c55f81292697d9ffadb1a5 +size 53062 diff --git a/marked/Rel-16/23_series/23783/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23783/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1d6ed041237012e0ae0dfbb28d59ce6c237354b --- /dev/null +++ b/marked/Rel-16/23_series/23783/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c677e2fa1a7c5ea559117f41bdef6fbbb10970b69f56b1d316c5c66718e6c910 +size 52178 diff --git a/marked/Rel-16/23_series/23783/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg b/marked/Rel-16/23_series/23783/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..823003f10b805d814a06e948ed6b08d9dfc78bac --- /dev/null +++ b/marked/Rel-16/23_series/23783/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e289ffdae31ce23caf77fa2ee609a3e8eac53303fc3d86ea10137c03dcf81dc +size 59705 diff --git a/marked/Rel-16/23_series/23783/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/Rel-16/23_series/23783/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b399b7b8a2e749bea669180e143b54f626c45049 --- /dev/null +++ b/marked/Rel-16/23_series/23783/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48754af53b7dcba0b9b74fcb595872df76238253124bec2f38dc2ce42b89f337 +size 36489 diff --git a/marked/Rel-16/23_series/23783/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg b/marked/Rel-16/23_series/23783/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a45d610ae7e4355d38321a845ab0149017ba593 --- /dev/null +++ b/marked/Rel-16/23_series/23783/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88a81cd241ae7008cf7318740fb7068c3c2e40cadbca70f3e5dcebb08fd207ee +size 75365 diff --git a/marked/Rel-16/23_series/23783/5dfc130b129ace4df375839020a5700d_img.jpg b/marked/Rel-16/23_series/23783/5dfc130b129ace4df375839020a5700d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc1257270b49e59334735ca20ffa253adf1cddef --- /dev/null +++ b/marked/Rel-16/23_series/23783/5dfc130b129ace4df375839020a5700d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b2d9eaf6c5fef232f4c5c9f02773ead4ea65f619d1dcb55c4a683ca087256c12 +size 21222 diff --git a/marked/Rel-16/23_series/23783/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-16/23_series/23783/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a83a6820ab715c8bcc308ab8ac6ad2996d8506e --- /dev/null +++ b/marked/Rel-16/23_series/23783/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df275989e874be7bb42b1922b0dce9409dfec8627a8b4d7b008020ebd5e44fcc +size 65131 diff --git a/marked/Rel-16/23_series/23783/5ec2b6e9c9133bfbb26789d85dc49774_img.jpg b/marked/Rel-16/23_series/23783/5ec2b6e9c9133bfbb26789d85dc49774_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67ed98b2297260e574e12e2fde98acd69cefea39 --- /dev/null +++ b/marked/Rel-16/23_series/23783/5ec2b6e9c9133bfbb26789d85dc49774_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc239a55084e50652b90f798fc587468c2f108b4d2cb5e66ed6e78de160b8a95 +size 20550 diff --git a/marked/Rel-16/23_series/23783/605ad256780bc1b6022dfb65a6e24a3b_img.jpg b/marked/Rel-16/23_series/23783/605ad256780bc1b6022dfb65a6e24a3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c9f40d5b5a072ddbc80c99678884c47f494f07c --- /dev/null +++ b/marked/Rel-16/23_series/23783/605ad256780bc1b6022dfb65a6e24a3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b337c12d5cfe27218017b8ae65b8cad803365f33f40b538440fca556557055c +size 74112 diff --git a/marked/Rel-16/23_series/23783/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg b/marked/Rel-16/23_series/23783/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a862b296c52ca1475d41e49e9a480049d0e9f125 --- /dev/null +++ b/marked/Rel-16/23_series/23783/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e021761cbb2d82a182ed723936e38b1ea73feabad46f800bea30ed5d52eb729 +size 22106 diff --git a/marked/Rel-16/23_series/23783/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-16/23_series/23783/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cfd332e0032e23d1617889cc6c3793abef09dd0 --- /dev/null +++ b/marked/Rel-16/23_series/23783/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:562937c6a7d7c6c7fc3535f24eb18237b0abe0e9841a2d72157fb3a18b97e02b +size 52988 diff --git a/marked/Rel-16/23_series/23783/61d6d7aae4cc4d0310bdf9ec29e221c5_img.jpg b/marked/Rel-16/23_series/23783/61d6d7aae4cc4d0310bdf9ec29e221c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fcb28e2a6776db1135ea009827c28b9ce56e2e6 --- /dev/null +++ b/marked/Rel-16/23_series/23783/61d6d7aae4cc4d0310bdf9ec29e221c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8064ad85c4662f907bfa16a30822479e70c502a01180a357fec4aec393a4e8bb +size 51222 diff --git a/marked/Rel-16/23_series/23783/62e0e858742d9a9ea4cfdc52e448e8bb_img.jpg b/marked/Rel-16/23_series/23783/62e0e858742d9a9ea4cfdc52e448e8bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1a2219cb63ea0dd42ee965d73b27bfac5078b16 --- /dev/null +++ b/marked/Rel-16/23_series/23783/62e0e858742d9a9ea4cfdc52e448e8bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac984550f5f6a0fc84744fb8e786303fc7b6fe83c7ec8db2d449fb738c1b8c0d +size 43614 diff --git a/marked/Rel-16/23_series/23783/62ee64afa2d368d732de66628cf2c841_img.jpg b/marked/Rel-16/23_series/23783/62ee64afa2d368d732de66628cf2c841_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fef278ca4b33fe2304f1467f3b2418b65c94073f --- /dev/null +++ b/marked/Rel-16/23_series/23783/62ee64afa2d368d732de66628cf2c841_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c91de0dd36466a6d38fd7040c704fade8157d4761953e279f1aca1b6b36f30c +size 52943 diff --git a/marked/Rel-16/23_series/23783/6334c962f5e106e3331e59946e4d166e_img.jpg b/marked/Rel-16/23_series/23783/6334c962f5e106e3331e59946e4d166e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..445c3703d16777debea1ac8a9db802d102df4e32 --- /dev/null +++ b/marked/Rel-16/23_series/23783/6334c962f5e106e3331e59946e4d166e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:141612e638ffd479f81789c21390ba0fe6838a3731dd455e236c0c71698b624c +size 38443 diff --git a/marked/Rel-16/23_series/23783/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg b/marked/Rel-16/23_series/23783/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe39e26dae6deb950db8ebd4f28a9c5fad6cc564 --- /dev/null +++ b/marked/Rel-16/23_series/23783/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3173751d53be06ddc1be05c54e2f8b204b2c13cae01eda32c18d61b77e888321 +size 50658 diff --git a/marked/Rel-16/23_series/23783/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-16/23_series/23783/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6b033ee945cb4c7757ae48e15792f15d43372cf --- /dev/null +++ b/marked/Rel-16/23_series/23783/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3bc0aec40cc385a004035c5dbf9bdc93c642984145d0bf41dd71f71f1138c72 +size 76995 diff --git a/marked/Rel-16/23_series/23783/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/23_series/23783/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5138f39b1eba9d3020643ff17d0d81ea524ec3ec --- /dev/null +++ b/marked/Rel-16/23_series/23783/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3051213642a933cf52e7a6ed4d44fb368541f19ba2dde053d78cde9c764407fe +size 69559 diff --git a/marked/Rel-16/23_series/23783/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-16/23_series/23783/694df81535f89c7bfb9ef0df6f130dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b19d5befa73eebc68d704f35958be0b1cd0dd136 --- /dev/null +++ b/marked/Rel-16/23_series/23783/694df81535f89c7bfb9ef0df6f130dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7c00c1190f455c6c15ab10ba4f96ff71a0265cf06f1a350e2f01d7afd950a67 +size 85019 diff --git a/marked/Rel-16/23_series/23783/69edc2887e907309499ac95b47ab6905_img.jpg b/marked/Rel-16/23_series/23783/69edc2887e907309499ac95b47ab6905_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..390e256c23af8f1fa932815ee61ba80b885295e7 --- /dev/null +++ b/marked/Rel-16/23_series/23783/69edc2887e907309499ac95b47ab6905_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fef415a606ac72bfaa97bc1afc1b1d6be82d713baa03a7695f5f241ccee558c8 +size 51689 diff --git a/marked/Rel-16/23_series/23783/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-16/23_series/23783/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8d55d94c54756e40644a361649aba6babf54d07 --- /dev/null +++ b/marked/Rel-16/23_series/23783/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b98a9a52ccac7a0d109a0ad66090e327740d91c3801e070f5e065859dff2287b +size 118233 diff --git a/marked/Rel-16/23_series/23783/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/23_series/23783/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c05caed8a0ae36c2fe0450c6b8fade4efbdb5e8c --- /dev/null +++ b/marked/Rel-16/23_series/23783/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:883c4e377fc615117e10e2e0f6b77ec745923614957a5090de57c55be7a9f9a8 +size 76320 diff --git a/marked/Rel-16/23_series/23783/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-16/23_series/23783/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40626d2aeb2dae9cb33d1403d8dd1c7d06400fc5 --- /dev/null +++ b/marked/Rel-16/23_series/23783/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6fefd8fac66f568eb3a326c997e046c456c51066d4fa0b8155335acfdf40027 +size 82886 diff --git a/marked/Rel-16/23_series/23783/72bc1a2b64dd6bac8285f560440c1218_img.jpg b/marked/Rel-16/23_series/23783/72bc1a2b64dd6bac8285f560440c1218_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30834288b8cae81abbd5c9a10bf51a5c09dc0531 --- /dev/null +++ b/marked/Rel-16/23_series/23783/72bc1a2b64dd6bac8285f560440c1218_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5edfdf0047da34e0c7d4b6d892cbbd9ff54019855222f7dba027cfcab8394f38 +size 62682 diff --git a/marked/Rel-16/23_series/23783/745261f385368efa3f2259c8681874e9_img.jpg b/marked/Rel-16/23_series/23783/745261f385368efa3f2259c8681874e9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..741e33ca4fb3e00fb5000992df475d990e66aabd --- /dev/null +++ b/marked/Rel-16/23_series/23783/745261f385368efa3f2259c8681874e9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b912648dad1def7180253436480029070f9c079edd3a421d3844a2d31a671b4 +size 49180 diff --git a/marked/Rel-16/23_series/23783/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-16/23_series/23783/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..291b9d5f7d8647addc5d5a9f8c7c2a618967a01f --- /dev/null +++ b/marked/Rel-16/23_series/23783/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33179bc08e77e74355c18fbb8a085207a1bb27a16987162909a9d1e9b6749470 +size 58068 diff --git a/marked/Rel-16/23_series/23783/768b8ab0d55761b205087c079df1e6e6_img.jpg b/marked/Rel-16/23_series/23783/768b8ab0d55761b205087c079df1e6e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..365d0c9f3e1c75ba7ce7175fd48c9d2a7e48a3a4 --- /dev/null +++ b/marked/Rel-16/23_series/23783/768b8ab0d55761b205087c079df1e6e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca7d28da681a040f121ee67ca1f722958caae39052274caeddd94b1900ae8f58 +size 43196 diff --git a/marked/Rel-16/23_series/23783/7722d62e33dcc894cc8555e9474c5606_img.jpg b/marked/Rel-16/23_series/23783/7722d62e33dcc894cc8555e9474c5606_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c37ce49393df07c9c238758cc751dd4c38582dc --- /dev/null +++ b/marked/Rel-16/23_series/23783/7722d62e33dcc894cc8555e9474c5606_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03a10109fb7952900487d67e1e94fa1783d7666407d40dab8e332c9f6863cb7e +size 42465 diff --git a/marked/Rel-16/23_series/23783/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/23_series/23783/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd2869df551a24086699d2ded5bb52df7b6062e7 --- /dev/null +++ b/marked/Rel-16/23_series/23783/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6f3f310d3e31d827e7d551ae2df0dbd88884cb6021dd8e9c261eada662c2e1f +size 64236 diff --git a/marked/Rel-16/23_series/23783/79aaab5889060cf8264226764a109cdb_img.jpg b/marked/Rel-16/23_series/23783/79aaab5889060cf8264226764a109cdb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9c922b8d6ece0576489570988ba0717b73d13ffa --- /dev/null +++ b/marked/Rel-16/23_series/23783/79aaab5889060cf8264226764a109cdb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0304d7a9147245e82b21c26ec23b071e0d4902cef829e3894a1ef7bec6f3a7d +size 61527 diff --git a/marked/Rel-16/23_series/23783/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/23_series/23783/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a14d6b5a6c526819818234540fcb6bb88baa49ca --- /dev/null +++ b/marked/Rel-16/23_series/23783/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45c0a7273703ec1a6131431439c438624c2c4d96d0f1cc73f2fdf271f19c1f0b +size 82441 diff --git a/marked/Rel-16/23_series/23783/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg b/marked/Rel-16/23_series/23783/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcd85eab7d7213154031d892e50af871299b0695 --- /dev/null +++ b/marked/Rel-16/23_series/23783/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67238b43b496888d792de0f44a428693d7804d771944d2a9e6133709cb3ecc76 +size 25407 diff --git a/marked/Rel-16/23_series/23783/7e74ac663f3e644b589ed28f5fd29398_img.jpg b/marked/Rel-16/23_series/23783/7e74ac663f3e644b589ed28f5fd29398_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bd6a334d859a5351505350c14a66698b6c5ae37 --- /dev/null +++ b/marked/Rel-16/23_series/23783/7e74ac663f3e644b589ed28f5fd29398_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db157191d0129f8724b30db9a3f82d2a8486a3831403bb6eb86e72e11e7d745c +size 77061 diff --git a/marked/Rel-16/23_series/23783/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-16/23_series/23783/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4a95c54a2385ebd47a0a8da70cad46dd09ba29a --- /dev/null +++ b/marked/Rel-16/23_series/23783/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ad29671ae7dcb35ae390ad12c2c27d58257b0cc60e99cb4b518c37ef645ed52 +size 67935 diff --git a/marked/Rel-16/23_series/23783/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23783/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2272443b734eb243f1c434a11f50b0922a9d4768 --- /dev/null +++ b/marked/Rel-16/23_series/23783/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46e0ce0cf67bd4ac01b5be31234fc6c3f798b84ce53375ba1542873a0697ac76 +size 47892 diff --git a/marked/Rel-16/23_series/23783/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/marked/Rel-16/23_series/23783/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e2e7d179a597a609320f10d2c6b1496b975c979 --- /dev/null +++ b/marked/Rel-16/23_series/23783/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:672b533350d146dc77570efff49a5b093ca32ee5626e7f6465557113650a3e5e +size 62551 diff --git a/marked/Rel-16/23_series/23783/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg b/marked/Rel-16/23_series/23783/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33640e4591d7433afa5317db214a40f68a933ac3 --- /dev/null +++ b/marked/Rel-16/23_series/23783/7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41a8a323180ed9a865b3915e1b81f0be22a1e7ee0beb154eaa2c12b20e17f076 +size 30038 diff --git a/marked/Rel-16/23_series/23783/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23783/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ac4c51fd4ef958a428ca00607bb80b0dc1d5627 --- /dev/null +++ b/marked/Rel-16/23_series/23783/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:183cca90bb127a55861c64a91aa75606eb7064736185f1523c132befd1694c7b +size 27827 diff --git a/marked/Rel-16/23_series/23783/820515db47ded68f5e0b625f4ec7d2c1_img.jpg b/marked/Rel-16/23_series/23783/820515db47ded68f5e0b625f4ec7d2c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb1b44a26af4d7de2fbd5c48f33fe29495075b3a --- /dev/null +++ b/marked/Rel-16/23_series/23783/820515db47ded68f5e0b625f4ec7d2c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aef8899ba8c076c5954a853cc975c5c6476dda4ccaf0b0d5e81fda89e793330a +size 89754 diff --git a/marked/Rel-16/23_series/23783/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/23_series/23783/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..611d417f51e39520f46586f4ebb6de242ebb2418 --- /dev/null +++ b/marked/Rel-16/23_series/23783/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d15ae1685ef76d5423b566ce9d3318229ce4b673d5e5e9a6233d98dd86e6031f +size 64903 diff --git a/marked/Rel-16/23_series/23783/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23783/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe5fd78fb935a4aeb98f8bf95cc86dcdd78e5e0a --- /dev/null +++ b/marked/Rel-16/23_series/23783/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e57e22fb95433acb3f74ec0fb50cc64aef20c731b4bfa064a19dc6a01cedba1 +size 57831 diff --git a/marked/Rel-16/23_series/23783/832a0ce332e784fe80289e9f00f56574_img.jpg b/marked/Rel-16/23_series/23783/832a0ce332e784fe80289e9f00f56574_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b816cf6541581d2dbfbc08038c7d0befc8bd07c --- /dev/null +++ b/marked/Rel-16/23_series/23783/832a0ce332e784fe80289e9f00f56574_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3effff74cffe9354961bbd865e4dbc2af9f11a6ec2f106c7324502184ef5dd4a +size 103121 diff --git a/marked/Rel-16/23_series/23783/836b0790cef5469a167fa8931df4e408_img.jpg b/marked/Rel-16/23_series/23783/836b0790cef5469a167fa8931df4e408_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bca883786ad223c17dea9d68ee28e371dd807513 --- /dev/null +++ b/marked/Rel-16/23_series/23783/836b0790cef5469a167fa8931df4e408_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e61fe6359a099c2b2745aedc3e847051b34ef9b2558a7ade02ef158bc9b8c49a +size 107873 diff --git a/marked/Rel-16/23_series/23783/8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg b/marked/Rel-16/23_series/23783/8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e479ed556e9c3ca03c55b02dba7f365b65f84ab5 --- /dev/null +++ b/marked/Rel-16/23_series/23783/8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68ab4de4d3efca71f5e29c012e5d2b84cee45122e1afc850f6786cc74b59b482 +size 34692 diff --git a/marked/Rel-16/23_series/23783/84e5b251aa38db522f76f5cc3afcb853_img.jpg b/marked/Rel-16/23_series/23783/84e5b251aa38db522f76f5cc3afcb853_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..973bcf11a6cc5c9501777acd1faa1f2e18226c61 --- /dev/null +++ b/marked/Rel-16/23_series/23783/84e5b251aa38db522f76f5cc3afcb853_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8dbb817e49b6a47018bbc6084ebebc59184082e8c638a5bb8a91611d04be215 +size 41039 diff --git a/marked/Rel-16/23_series/23783/854cb86f664ff62fd23e7607cfeb5727_img.jpg b/marked/Rel-16/23_series/23783/854cb86f664ff62fd23e7607cfeb5727_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da71e6aedf36c622ee7eff1d8b15ed5cf1a20c37 --- /dev/null +++ b/marked/Rel-16/23_series/23783/854cb86f664ff62fd23e7607cfeb5727_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b15d06fe070c6c0d593c74060d41e9a9bf6c92ec2e2c39e165d291213f72d295 +size 58297 diff --git a/marked/Rel-16/23_series/23783/869c547c11ac7e123c51aba22289f2cd_img.jpg b/marked/Rel-16/23_series/23783/869c547c11ac7e123c51aba22289f2cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50c53c31f6506bc27ca07720347f7e8de73266f9 --- /dev/null +++ b/marked/Rel-16/23_series/23783/869c547c11ac7e123c51aba22289f2cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4852ee4ab9777e94076030f517483e33d43c4de7e55f7f4c36fb43e8374445ba +size 66267 diff --git a/marked/Rel-16/23_series/23783/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg b/marked/Rel-16/23_series/23783/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87dd0b33c1568df2c07a54d91b8cbba2fd4d9f69 --- /dev/null +++ b/marked/Rel-16/23_series/23783/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d32edf4e50476329dc5e0ae493e7db59325619f3ab40116eeedfe8ad4b15bb7e +size 51320 diff --git a/marked/Rel-16/23_series/23783/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg b/marked/Rel-16/23_series/23783/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7685f89cba21550adbe1321356bc4673be5505bd --- /dev/null +++ b/marked/Rel-16/23_series/23783/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20f26edd41a37db85a0b5443baffa497c2aa03cc81be60dd67c5312b6bf39149 +size 54302 diff --git a/marked/Rel-16/23_series/23783/8b9e9fdabfd2a37e4475d78f8fdcf15c_img.jpg b/marked/Rel-16/23_series/23783/8b9e9fdabfd2a37e4475d78f8fdcf15c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24148a3d176b0c2e51c5bffae5da6fff2b8c901c --- /dev/null +++ b/marked/Rel-16/23_series/23783/8b9e9fdabfd2a37e4475d78f8fdcf15c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd4266838c221ba35be0c3a61b9f32f70d15442b083bdcb22e3f2b89da529611 +size 56517 diff --git a/marked/Rel-16/23_series/23783/8d1bb05debbaef0f72751449b2b55172_img.jpg b/marked/Rel-16/23_series/23783/8d1bb05debbaef0f72751449b2b55172_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..295c2358761070a703e7d6252403c44c6980694f --- /dev/null +++ b/marked/Rel-16/23_series/23783/8d1bb05debbaef0f72751449b2b55172_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9d2940d25fb4ceb194bc080c053eb4b26229579ce9e792cc581910d634a95a1 +size 32727 diff --git a/marked/Rel-16/23_series/23783/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-16/23_series/23783/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af9f46e9628b35fb5e88d6d720efd5a9b3aaf019 --- /dev/null +++ b/marked/Rel-16/23_series/23783/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81aff55e043dfa9ce407d28ee47e9e1ec5f0679ee46ece3fb3fe12c31879877c +size 42037 diff --git a/marked/Rel-16/23_series/23783/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-16/23_series/23783/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a055aded4c6cfeebff0e8b5aa1f218a0fd6eadb2 --- /dev/null +++ b/marked/Rel-16/23_series/23783/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7ea48a2ffaf17f26ed3ceac218672ddfa4f7dab37a41a0e216bd578e3e73635 +size 88162 diff --git a/marked/Rel-16/23_series/23783/8d8c758885b4f754ff071bf3b572ab3c_img.jpg b/marked/Rel-16/23_series/23783/8d8c758885b4f754ff071bf3b572ab3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bea474b6c635074c74b03c529df9e22d4ad9b85d --- /dev/null +++ b/marked/Rel-16/23_series/23783/8d8c758885b4f754ff071bf3b572ab3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0679d5ec585da0bce7f40426bb6a6d409b4bf78a27db4aa76b540b73ee83ecd7 +size 43627 diff --git a/marked/Rel-16/23_series/23783/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/23_series/23783/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..462933b1f8412008354b5186276456c8796ff20e --- /dev/null +++ b/marked/Rel-16/23_series/23783/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68127fdb3e580ad38ca4fe1425c6142f4cd53e7798c3c7585ca7ba0e4cf7c4fd +size 73951 diff --git a/marked/Rel-16/23_series/23783/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/23_series/23783/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eda8924af4275223cf79671a7f80a8ebc142d86c --- /dev/null +++ b/marked/Rel-16/23_series/23783/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1746870f4bdcc52ef1e4da1e4bed92436461432b90a3ae48b8339dbae1bb01f4 +size 31953 diff --git a/marked/Rel-16/23_series/23783/8fe84519a7da727cc2a27873b3389a52_img.jpg b/marked/Rel-16/23_series/23783/8fe84519a7da727cc2a27873b3389a52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..986b957ad92e901ee40ff9c422a47ddd22786baa --- /dev/null +++ b/marked/Rel-16/23_series/23783/8fe84519a7da727cc2a27873b3389a52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4755787bc3d144b33632c36ed133d969d5c5073444b7f7b9e172b7c7aaeaa127 +size 38101 diff --git a/marked/Rel-16/23_series/23783/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg b/marked/Rel-16/23_series/23783/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b02ca4b55bf9a4fa6286f8ece45c3a2fb18bb0a --- /dev/null +++ b/marked/Rel-16/23_series/23783/907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abdbe8c3229f29c37ba2084e9046fab96b24b423abe0ce141a129cdf4234558e +size 54373 diff --git a/marked/Rel-16/23_series/23783/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23783/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27e7c093bdaedcb570d6af35c03a49f0831b5888 --- /dev/null +++ b/marked/Rel-16/23_series/23783/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22899db2c75e0ddf58753ed14797b83921946de13f0ed2c528161633d7ba4af4 +size 38494 diff --git a/marked/Rel-16/23_series/23783/91134b9a38d7f73f03375473e7b706f9_img.jpg b/marked/Rel-16/23_series/23783/91134b9a38d7f73f03375473e7b706f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12b9a6e54a47ed2f7d0aca2fcb8fefa65730d17c --- /dev/null +++ b/marked/Rel-16/23_series/23783/91134b9a38d7f73f03375473e7b706f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c61cd7e630402c449b643285f2642a3da13ebb98d9be9afdfc24ee77f665d957 +size 45255 diff --git a/marked/Rel-16/23_series/23783/91b12db3c85bbf466ad27eb3665a1b06_img.jpg b/marked/Rel-16/23_series/23783/91b12db3c85bbf466ad27eb3665a1b06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88abeae6f0c24f1076de41fe90e4d76860a6a6f3 --- /dev/null +++ b/marked/Rel-16/23_series/23783/91b12db3c85bbf466ad27eb3665a1b06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3506e77f902e44334a672554b849750074521394a0f7bc3ff707b372aa22796e +size 47754 diff --git a/marked/Rel-16/23_series/23783/92271d74f67effbd92583eb3fba71514_img.jpg b/marked/Rel-16/23_series/23783/92271d74f67effbd92583eb3fba71514_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cab8265f92494738209faf63c88e44ffa379d3ec --- /dev/null +++ b/marked/Rel-16/23_series/23783/92271d74f67effbd92583eb3fba71514_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a45437116855ef2b8d4c01990c37a05c87b4c93df7c0999f7e8f4c403483651c +size 29437 diff --git a/marked/Rel-16/23_series/23783/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/23_series/23783/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4740021770e4ec08ed40eb77b3ae0295fbcc4ff8 --- /dev/null +++ b/marked/Rel-16/23_series/23783/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:930241ce4f464207b85f07c12756b10f1a42b8b787d7b105c60b1e0368731687 +size 86826 diff --git a/marked/Rel-16/23_series/23783/94acd33fcad85bb6f207a308f9b63191_img.jpg b/marked/Rel-16/23_series/23783/94acd33fcad85bb6f207a308f9b63191_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4de55c1022677e7113b2a63d96b3028d829c994e --- /dev/null +++ b/marked/Rel-16/23_series/23783/94acd33fcad85bb6f207a308f9b63191_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:919696210fd7d0ee8cd771dd7e5f9c28ff56083413ae1cdf4d9e9d90ad42d9e8 +size 62095 diff --git a/marked/Rel-16/23_series/23783/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg b/marked/Rel-16/23_series/23783/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fbb245246006c88b6f57d1647370b180f5f74aaf --- /dev/null +++ b/marked/Rel-16/23_series/23783/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8bc45f3e37388be92b00488f53168133c135ab371536035a6dab6253d2d5a18c +size 60961 diff --git a/marked/Rel-16/23_series/23783/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-16/23_series/23783/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..98aecd68cd889f0003ffe84d2ee8f64e5c9d7682 --- /dev/null +++ b/marked/Rel-16/23_series/23783/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c2d200e087542f8a0efbcda8f719cb55e57b6d08776de84deaef3e4c2f027a6 +size 33201 diff --git a/marked/Rel-16/23_series/23783/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/23_series/23783/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13a78b9f4dbcd699faa473286746f39830dfa188 --- /dev/null +++ b/marked/Rel-16/23_series/23783/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3ba38549b95c14970833a20b42897d6fc41833bdb4dff5e8eb33f54dd6aab43 +size 31609 diff --git a/marked/Rel-16/23_series/23783/9b686adccf125267a013fa25721231a3_img.jpg b/marked/Rel-16/23_series/23783/9b686adccf125267a013fa25721231a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4134523b797d8df020f83e21c0367f4c194ee60a --- /dev/null +++ b/marked/Rel-16/23_series/23783/9b686adccf125267a013fa25721231a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c20575f7f8f23a0f3125d654c4317c4311349b766e0f4f139f64cb274c7a6e0 +size 52176 diff --git a/marked/Rel-16/23_series/23783/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/23_series/23783/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..377089309798fab943ab88f437aa960376816be7 --- /dev/null +++ b/marked/Rel-16/23_series/23783/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06f37e41a49e8284c61b35ac05fd62763bc7cd381d14a4439de5cd5fe2a40516 +size 70630 diff --git a/marked/Rel-16/23_series/23783/9c45844d796e85ae05505870a54e4eb4_img.jpg b/marked/Rel-16/23_series/23783/9c45844d796e85ae05505870a54e4eb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46542e760ed23a55bb8b4ec62516781355a18f19 --- /dev/null +++ b/marked/Rel-16/23_series/23783/9c45844d796e85ae05505870a54e4eb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b767556e9628eea2bde05da4407ba422e7224cb8a015460a8f17d5ae93cd779d +size 76938 diff --git a/marked/Rel-16/23_series/23783/9cb54072e43a6b6717eb16036a7640a2_img.jpg b/marked/Rel-16/23_series/23783/9cb54072e43a6b6717eb16036a7640a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddccbc566b05dbcf665bdcc0f1e952bd53c6d92a --- /dev/null +++ b/marked/Rel-16/23_series/23783/9cb54072e43a6b6717eb16036a7640a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b12d4afca836dfd3b37f5d979984979a387216766ca2246e131f0e23c86e87f +size 31936 diff --git a/marked/Rel-16/23_series/23783/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg b/marked/Rel-16/23_series/23783/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b61d4c51d473ca8f24e5be415c6ef35738598368 --- /dev/null +++ b/marked/Rel-16/23_series/23783/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7226517fd5e5336f79f698dc3410ae3373bc37f576958db8a102124a7680bdd +size 44640 diff --git a/marked/Rel-16/23_series/23783/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/23_series/23783/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf36e7169581170257a86e16f032014a903c6752 --- /dev/null +++ b/marked/Rel-16/23_series/23783/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cf1545efce81f196728fb5b11e23ea73e215a12437628d1e1c4298384916192 +size 60375 diff --git a/marked/Rel-16/23_series/23783/9f50279046b74a4e66a1a0144c3b1d11_img.jpg b/marked/Rel-16/23_series/23783/9f50279046b74a4e66a1a0144c3b1d11_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59e6550d29219d6b92f6e3fe380571b4f7680296 --- /dev/null +++ b/marked/Rel-16/23_series/23783/9f50279046b74a4e66a1a0144c3b1d11_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae0556f69f42a8ce31e33b65d47cbc8a0d57aebc6c6fd37700464bc803f05366 +size 43031 diff --git a/marked/Rel-16/23_series/23783/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23783/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87a539b00a6c5ff51104e19b41b4862c13cfdfb6 --- /dev/null +++ b/marked/Rel-16/23_series/23783/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c5220b83f361c94c8a7bb235916dcaf65c24388ee1b0794786c3ead5374a82b +size 67620 diff --git a/marked/Rel-16/23_series/23783/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-16/23_series/23783/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ab8f472f2d2635703f44d8cb9c56ee8741c369c --- /dev/null +++ b/marked/Rel-16/23_series/23783/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bebb1c2f3a195b37220ac124f8bcfb7f2cc6e9355d37883a43987a96ef31756 +size 49150 diff --git a/marked/Rel-16/23_series/23783/a057800564be3506d2d87b6a4daee25b_img.jpg b/marked/Rel-16/23_series/23783/a057800564be3506d2d87b6a4daee25b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28c29200c69a50484a4c0d9d10d0feec13f01983 --- /dev/null +++ b/marked/Rel-16/23_series/23783/a057800564be3506d2d87b6a4daee25b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81f27c99852e05b6c9bb66c77ca149c1cde0df82068f42f690d84653492ed88b +size 32779 diff --git a/marked/Rel-16/23_series/23783/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/23_series/23783/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..05b809f8bc45da213282f1205264c9772274affe --- /dev/null +++ b/marked/Rel-16/23_series/23783/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c546ecd8f56b16f182f315823f3850a3098be65444272a23d6398c74882529ca +size 19179 diff --git a/marked/Rel-16/23_series/23783/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/Rel-16/23_series/23783/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..843c00c0182f55c70b8b21db4adfee14a62c099c --- /dev/null +++ b/marked/Rel-16/23_series/23783/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a6815fa1501cb843fc01f55fb8bb84ce642ff3d739ba1ef08ce8d24bbe21273 +size 71618 diff --git a/marked/Rel-16/23_series/23783/a2dc8d6396228142d4c2c1d3160b47dc_img.jpg b/marked/Rel-16/23_series/23783/a2dc8d6396228142d4c2c1d3160b47dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec7b41989e4a0284ef1f02ce45c96febfea2bfc4 --- /dev/null +++ b/marked/Rel-16/23_series/23783/a2dc8d6396228142d4c2c1d3160b47dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9dccd1da0c4a40e7951b88ef83d2561695191e91492a57443b6692d4fdb10b9b +size 30107 diff --git a/marked/Rel-16/23_series/23783/a47713c2491e6ce619259ed2f196fd24_img.jpg b/marked/Rel-16/23_series/23783/a47713c2491e6ce619259ed2f196fd24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9cb3a61b3bd2982310f7712eb98b1f6a4c4f7342 --- /dev/null +++ b/marked/Rel-16/23_series/23783/a47713c2491e6ce619259ed2f196fd24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0cfaab41c9c381c351219df97bc6b5c0c5eb35d57f341d3f7ee944257c3ad0c +size 24560 diff --git a/marked/Rel-16/23_series/23783/a5184899f915014fa38608754efcc9c7_img.jpg b/marked/Rel-16/23_series/23783/a5184899f915014fa38608754efcc9c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..011ab233d5de17371e428df3f1ebf16d8313bfb5 --- /dev/null +++ b/marked/Rel-16/23_series/23783/a5184899f915014fa38608754efcc9c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6931051c8fbfc2db4c40f0974b7ae107a4aedc536e0b53ee4e18be73c8b298a4 +size 100569 diff --git a/marked/Rel-16/23_series/23783/a5252b28ea220e69468dd1d0594e40fe_img.jpg b/marked/Rel-16/23_series/23783/a5252b28ea220e69468dd1d0594e40fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ac36f0abaf443c308f179be94dd12882338efb7 --- /dev/null +++ b/marked/Rel-16/23_series/23783/a5252b28ea220e69468dd1d0594e40fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ad150a19be8ea7262d8f8dcfb309d2fdb794000f543cfa7bc41d45384271a8d +size 53176 diff --git a/marked/Rel-16/23_series/23783/a7c51c18111139f9aca2805114108565_img.jpg b/marked/Rel-16/23_series/23783/a7c51c18111139f9aca2805114108565_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11b2f0d23158fcb5cdb1d5eff035697961622c18 --- /dev/null +++ b/marked/Rel-16/23_series/23783/a7c51c18111139f9aca2805114108565_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:906a90cafd2b8edce17ada7051f6498e5b58b76327ccdfc3fa0e7381a49ab1a7 +size 69713 diff --git a/marked/Rel-16/23_series/23783/a97518a839da75f8379c578562b01bc2_img.jpg b/marked/Rel-16/23_series/23783/a97518a839da75f8379c578562b01bc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2270fd8738c2367c9d1f88986c83ecdf66de8767 --- /dev/null +++ b/marked/Rel-16/23_series/23783/a97518a839da75f8379c578562b01bc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c47e5995141183e7ed0165d024319bf1ed31cfcdc6fb9ad8c999fc515fbcc812 +size 48151 diff --git a/marked/Rel-16/23_series/23783/a97f7c055c1fd8d79037d02b3fc38496_img.jpg b/marked/Rel-16/23_series/23783/a97f7c055c1fd8d79037d02b3fc38496_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0d2ffa8b84654741524718fa59344dfd4f523c8 --- /dev/null +++ b/marked/Rel-16/23_series/23783/a97f7c055c1fd8d79037d02b3fc38496_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b51f589f8456fd3da5c9dd37f8269e308cd6e74a47c2b8aa2bf59b6aec5c1c54 +size 39174 diff --git a/marked/Rel-16/23_series/23783/b06a4c871dfd0ce034cf801519d0039a_img.jpg b/marked/Rel-16/23_series/23783/b06a4c871dfd0ce034cf801519d0039a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e57582d41554824219da26c7d5ddcd7794615557 --- /dev/null +++ b/marked/Rel-16/23_series/23783/b06a4c871dfd0ce034cf801519d0039a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fd8e81ec598e344d4fbac70a84b4bd2b38cb5d6c55cdd6ba5ac153169fd8d77 +size 16984 diff --git a/marked/Rel-16/23_series/23783/b0988cfd9f60f2cd1916e3c2f9cae3da_img.jpg b/marked/Rel-16/23_series/23783/b0988cfd9f60f2cd1916e3c2f9cae3da_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e34afd84ef9e84ffbc2f0517491fd239bc535ba --- /dev/null +++ b/marked/Rel-16/23_series/23783/b0988cfd9f60f2cd1916e3c2f9cae3da_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5dd2393ec6d0bc953d793f1ec01bf49e08c17e0e528e4e464d70bd03d6d5308e +size 38854 diff --git a/marked/Rel-16/23_series/23783/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/marked/Rel-16/23_series/23783/b2ea162a0f53d5e0504b7d28346e0754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52bf1bf53631ae2ad2ff29feac1c37d8ff2623a2 --- /dev/null +++ b/marked/Rel-16/23_series/23783/b2ea162a0f53d5e0504b7d28346e0754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d73f363cd4ad4d6d66205829e4f903ce6ede14f96f10d40faff950771619fbe3 +size 88905 diff --git a/marked/Rel-16/23_series/23783/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/23_series/23783/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3277f5a653b305a46f2da7eeece1336201ef4982 --- /dev/null +++ b/marked/Rel-16/23_series/23783/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d183b4c2a39f6a390d5d3a2bb604d90372ce20e5e91fec59cf8c8c237780cdf3 +size 24765 diff --git a/marked/Rel-16/23_series/23783/b385e39c8b32616bd23ad744a3f71cfa_img.jpg b/marked/Rel-16/23_series/23783/b385e39c8b32616bd23ad744a3f71cfa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..062b989dad06a9d2095ea5aab911e9c6697dfaf0 --- /dev/null +++ b/marked/Rel-16/23_series/23783/b385e39c8b32616bd23ad744a3f71cfa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a465be58addcbef381ba7c80b38ec60cabdecfaad86af5ed9cc037a91715754 +size 11461 diff --git a/marked/Rel-16/23_series/23783/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23783/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66d6e4d1c0fbd97098c16785f52c39c69eb8c073 --- /dev/null +++ b/marked/Rel-16/23_series/23783/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de6d76e33ef1d211e6312115df8f83123c99a8e7226f287f68472a2408f88212 +size 80200 diff --git a/marked/Rel-16/23_series/23783/b4f6d3668f7e851eaff07ccf26001623_img.jpg b/marked/Rel-16/23_series/23783/b4f6d3668f7e851eaff07ccf26001623_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ce1d7ec80e7841bdacbf33b1abaa1decdca67106 --- /dev/null +++ b/marked/Rel-16/23_series/23783/b4f6d3668f7e851eaff07ccf26001623_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1badfa2931a6594d4dc2f722998df2b38ee5d740b3ef03655f4bf8803a44c82c +size 42304 diff --git a/marked/Rel-16/23_series/23783/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/23_series/23783/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8083d29b6efabf8154ae89b4e16a364aefc633fb --- /dev/null +++ b/marked/Rel-16/23_series/23783/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2059b1b5b53f7034c86a42c7df68178d28699c54dfe5326a43cfe420f36725c4 +size 52138 diff --git a/marked/Rel-16/23_series/23783/b612b838f94982799a69461ffb078a73_img.jpg b/marked/Rel-16/23_series/23783/b612b838f94982799a69461ffb078a73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c6070b70ad5ac6118b5754815a3dd32ee8acfa5 --- /dev/null +++ b/marked/Rel-16/23_series/23783/b612b838f94982799a69461ffb078a73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:164a76538dd5b4e46ed62ba7bee484a40afe2ae8505ce4fd5dc74e8f542a2bda +size 63581 diff --git a/marked/Rel-16/23_series/23783/b882c54d92390b4ca523f230e3e07617_img.jpg b/marked/Rel-16/23_series/23783/b882c54d92390b4ca523f230e3e07617_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b7e5b949446c881708307f1c937840d68487695 --- /dev/null +++ b/marked/Rel-16/23_series/23783/b882c54d92390b4ca523f230e3e07617_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6d2fe8559610080caf4c5852ffe121da41d55e0f20ca4c14a5ed1bb110a83fe +size 39721 diff --git a/marked/Rel-16/23_series/23783/b996d5a6408db9c4b3ac3aafd2ef44cf_img.jpg b/marked/Rel-16/23_series/23783/b996d5a6408db9c4b3ac3aafd2ef44cf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e41903c0f5fb9bacd1892dad0f8b5cacb0b7df8d --- /dev/null +++ b/marked/Rel-16/23_series/23783/b996d5a6408db9c4b3ac3aafd2ef44cf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75d63090429d62a342c86a87cb85b1a80cafbff43c4feb377475d234094ac94e +size 21534 diff --git a/marked/Rel-16/23_series/23783/bb3354f497635d15bef873577125c48d_img.jpg b/marked/Rel-16/23_series/23783/bb3354f497635d15bef873577125c48d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9d7a41753ef1530951731b7cf5bfb4367ec3f9a --- /dev/null +++ b/marked/Rel-16/23_series/23783/bb3354f497635d15bef873577125c48d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bd27cd28f9d16c9df0373cc8dbe916f59a23929cadf87ded74ac7974a00afe9 +size 31990 diff --git a/marked/Rel-16/23_series/23783/bccc028d0e75bc30c41528056f581545_img.jpg b/marked/Rel-16/23_series/23783/bccc028d0e75bc30c41528056f581545_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c4bbfba8a9f18be6cbca5acb1ba5a8c776245d73 --- /dev/null +++ b/marked/Rel-16/23_series/23783/bccc028d0e75bc30c41528056f581545_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae006ca3e5c3acad0ff9cc4318809e39a92f5e7ba05181527a6ef942b3300823 +size 166795 diff --git a/marked/Rel-16/23_series/23783/bd50d56ae2c12a92466ba2aea1a78040_img.jpg b/marked/Rel-16/23_series/23783/bd50d56ae2c12a92466ba2aea1a78040_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a5aaf98c17c2764658f8bb060fab88075873d16 --- /dev/null +++ b/marked/Rel-16/23_series/23783/bd50d56ae2c12a92466ba2aea1a78040_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3817f708b4157cc7d8c46c4c8c348ac7e3341b777262e7ca3381bc320c2e2fe5 +size 42493 diff --git a/marked/Rel-16/23_series/23783/bdd96f20e71f079cad85240efb3d3f24_img.jpg b/marked/Rel-16/23_series/23783/bdd96f20e71f079cad85240efb3d3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ce6000a404e4b3144afdafcde2c0178c5d71aae --- /dev/null +++ b/marked/Rel-16/23_series/23783/bdd96f20e71f079cad85240efb3d3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c5803c5266ba1eee43c674f0e5bc0120d84c984db7460f32ae52e231ce66bc0e +size 47601 diff --git a/marked/Rel-16/23_series/23783/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-16/23_series/23783/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d098c3e080324c44628c03bcb80652a7b725304f --- /dev/null +++ b/marked/Rel-16/23_series/23783/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:726bf3cfc90abfae0629fd6c12a0addb9b4b0951b87186b47f3f4de1346280bb +size 75589 diff --git a/marked/Rel-16/23_series/23783/c0c7f65c51c83fbe595b47326f6b089a_img.jpg b/marked/Rel-16/23_series/23783/c0c7f65c51c83fbe595b47326f6b089a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..608634a27b3739f71faaeb885a93ea614dbb839b --- /dev/null +++ b/marked/Rel-16/23_series/23783/c0c7f65c51c83fbe595b47326f6b089a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:851b2a183346afe75e9eba4c89d1e98e7eddd6a1bd312a2cdd41a360f806332b +size 40482 diff --git a/marked/Rel-16/23_series/23783/c1278da91cbcabe32628e589ebc47418_img.jpg b/marked/Rel-16/23_series/23783/c1278da91cbcabe32628e589ebc47418_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30061fe4471e0a4f0ffa8edc877350f8dd8bc05f --- /dev/null +++ b/marked/Rel-16/23_series/23783/c1278da91cbcabe32628e589ebc47418_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07c706565203655b79e882578cd103f7655c7c4fe5ea7025b322663d1dbcf31d +size 77274 diff --git a/marked/Rel-16/23_series/23783/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg b/marked/Rel-16/23_series/23783/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d71978b90324f5f87def75ce1a26c9aad56bbc0a --- /dev/null +++ b/marked/Rel-16/23_series/23783/c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9711531172486298ac88fb7a530c7393aa0e2c185b204e2c18965a0f3fceaf2e +size 72678 diff --git a/marked/Rel-16/23_series/23783/c6005b2627c6ca10f6b0e94cdb34858d_img.jpg b/marked/Rel-16/23_series/23783/c6005b2627c6ca10f6b0e94cdb34858d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a2a30e3004f47f1faae4ab0089a886091b543b7 --- /dev/null +++ b/marked/Rel-16/23_series/23783/c6005b2627c6ca10f6b0e94cdb34858d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a774f32c97eb42e31947415d43ec58a8652a6534d0a421ae88b16743f7567a65 +size 30422 diff --git a/marked/Rel-16/23_series/23783/c8a01394092e8f1fbaf91c81d752d401_img.jpg b/marked/Rel-16/23_series/23783/c8a01394092e8f1fbaf91c81d752d401_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5bfe8a87c919de6b1155136309b4dd93447e2b4 --- /dev/null +++ b/marked/Rel-16/23_series/23783/c8a01394092e8f1fbaf91c81d752d401_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6c3d13995b61ae66bd79466d1c41a4d04bbd4c7fc690d7978da26b2a00375e2 +size 56838 diff --git a/marked/Rel-16/23_series/23783/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/23_series/23783/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb117a5cb653815b897e7dcf6712442613a27856 --- /dev/null +++ b/marked/Rel-16/23_series/23783/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58c6b710b2e1b33451c17c80b15cd0772ddb5c5be3d56b8093aa015c2386962b +size 55504 diff --git a/marked/Rel-16/23_series/23783/cc542843836eecb036b99cb270b54a1e_img.jpg b/marked/Rel-16/23_series/23783/cc542843836eecb036b99cb270b54a1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b62824b48ab5d5b6ccec811998e2e97ac2a918a --- /dev/null +++ b/marked/Rel-16/23_series/23783/cc542843836eecb036b99cb270b54a1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01cdaa45b7e153609d392bb798bf4518ed191596edb7783beebceee33716dcc5 +size 38352 diff --git a/marked/Rel-16/23_series/23783/cd141897aa368dbbaa398ace230cdd85_img.jpg b/marked/Rel-16/23_series/23783/cd141897aa368dbbaa398ace230cdd85_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..030cd015c3d0e02fd67d534b599717541a0474d4 --- /dev/null +++ b/marked/Rel-16/23_series/23783/cd141897aa368dbbaa398ace230cdd85_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:077f53cfcfc4ecba995a0e7f34cc8239f35ce439c479dd11847fde01c19ec9a4 +size 25430 diff --git a/marked/Rel-16/23_series/23783/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg b/marked/Rel-16/23_series/23783/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a758edd25c7dc3eecb3965c67e82358ebaee74fa --- /dev/null +++ b/marked/Rel-16/23_series/23783/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e62a132a9814c6b5a757e2c4aed113fa86c4202e10aa01ea7f0e37942777fb61 +size 64685 diff --git a/marked/Rel-16/23_series/23783/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/23_series/23783/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd200db21234570343f1e1a30dd767d7e27df2da --- /dev/null +++ b/marked/Rel-16/23_series/23783/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e3c0c2b36075f85fdd430cd8d2605379274e50223ac28cbf1393805fe0d4418 +size 28458 diff --git a/marked/Rel-16/23_series/23783/d3b5eac55166fc428a223bba5c46961b_img.jpg b/marked/Rel-16/23_series/23783/d3b5eac55166fc428a223bba5c46961b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cd8fbf3eb64e824c027359c96db467d7367165bb --- /dev/null +++ b/marked/Rel-16/23_series/23783/d3b5eac55166fc428a223bba5c46961b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db2832cb86780acef4278d52220d9ad225848faef4e44f24a86181438f92f4e0 +size 50597 diff --git a/marked/Rel-16/23_series/23783/d3ca266c298aeb34b019960c6c36f187_img.jpg b/marked/Rel-16/23_series/23783/d3ca266c298aeb34b019960c6c36f187_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ec85bbda7f2d915c8d4bb9fac4de6a20d421856 --- /dev/null +++ b/marked/Rel-16/23_series/23783/d3ca266c298aeb34b019960c6c36f187_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1acd2147c4fde6c6ce7a5b65093f478c870f0aaf824b295159ec3101d6982db +size 72209 diff --git a/marked/Rel-16/23_series/23783/d5d5c87be8e612be9d06d406bc894fd5_img.jpg b/marked/Rel-16/23_series/23783/d5d5c87be8e612be9d06d406bc894fd5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35a06c2077d374f3bd651bedb60372efdddcf95c --- /dev/null +++ b/marked/Rel-16/23_series/23783/d5d5c87be8e612be9d06d406bc894fd5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43b35666487a4222e17ce2fc71f23960532cb957fd4aef9ae721d46d8e65eab1 +size 36184 diff --git a/marked/Rel-16/23_series/23783/d62e2e2281009c16f4ee61660e716cd9_img.jpg b/marked/Rel-16/23_series/23783/d62e2e2281009c16f4ee61660e716cd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f9c44f02efc2f72dba98e5cbb45710f203775cd --- /dev/null +++ b/marked/Rel-16/23_series/23783/d62e2e2281009c16f4ee61660e716cd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc5e0d346dc2a0918fbf331ea809ea51b6bad2d909befe98019eb6e90aad5670 +size 52739 diff --git a/marked/Rel-16/23_series/23783/d78e519e9186d30807342196675fd440_img.jpg b/marked/Rel-16/23_series/23783/d78e519e9186d30807342196675fd440_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cbeb249350efb6e006f9af2b4cdcc0b00186c16 --- /dev/null +++ b/marked/Rel-16/23_series/23783/d78e519e9186d30807342196675fd440_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55ff98d954e0266035615bb40e1fb4db5de0a9902bc9c4dae91272e78d426ee4 +size 37433 diff --git a/marked/Rel-16/23_series/23783/d7948c38a18636aefecdd95388196460_img.jpg b/marked/Rel-16/23_series/23783/d7948c38a18636aefecdd95388196460_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..513642f65f993317830e98488039bdf3e32e4aee --- /dev/null +++ b/marked/Rel-16/23_series/23783/d7948c38a18636aefecdd95388196460_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4500fd0a4baa7be833f55aaa01ad7e9dc9492acc0c1e6c2601c352363fcb8038 +size 57616 diff --git a/marked/Rel-16/23_series/23783/d7efe1d3c9fce95c7bacefb7e7d7faff_img.jpg b/marked/Rel-16/23_series/23783/d7efe1d3c9fce95c7bacefb7e7d7faff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe049ecb771773767ef2fe5fa11b3f3ac42effbb --- /dev/null +++ b/marked/Rel-16/23_series/23783/d7efe1d3c9fce95c7bacefb7e7d7faff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5007470c212cde59434e4af5753f0b8cc93695880ea889ed55ebacb88a14f4ef +size 27905 diff --git a/marked/Rel-16/23_series/23783/daf05db9f13b34fb12da52f007bbfe5b_img.jpg b/marked/Rel-16/23_series/23783/daf05db9f13b34fb12da52f007bbfe5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25000ceaa2a0a0a5e692b6d2cb99a8b2c0ec276a --- /dev/null +++ b/marked/Rel-16/23_series/23783/daf05db9f13b34fb12da52f007bbfe5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b63911b9de5254d07d4afd37b747c22d8719219d6a6d622c2a0c0d1c99a5a44 +size 63036 diff --git a/marked/Rel-16/23_series/23783/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/23_series/23783/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..018db67d569b0c6852d32c7764a5e1f4f49992f6 --- /dev/null +++ b/marked/Rel-16/23_series/23783/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40be978a521c9c8bdafe54dcf0b274cee3bc808cffa6a991f150cb64ead9e9bf +size 60568 diff --git a/marked/Rel-16/23_series/23783/dc23d430e878eb71b8cd589984113940_img.jpg b/marked/Rel-16/23_series/23783/dc23d430e878eb71b8cd589984113940_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa19f8263554c825b785251da3271f69da4f2ee7 --- /dev/null +++ b/marked/Rel-16/23_series/23783/dc23d430e878eb71b8cd589984113940_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e818d9e25ba6eeb2dc921d956ac6784d56246309a7e92bcf9f11f00abb3daaf1 +size 65231 diff --git a/marked/Rel-16/23_series/23783/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23783/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d94781cd969fac495253d60a4e82a67d83e9f4f9 --- /dev/null +++ b/marked/Rel-16/23_series/23783/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ed5fae364f784e96c678561104afcf8be41234d93f385535a4ef6fb52bdc3bc +size 88292 diff --git a/marked/Rel-16/23_series/23783/dd6c544ab685b25dd17f59456efcfbfc_img.jpg b/marked/Rel-16/23_series/23783/dd6c544ab685b25dd17f59456efcfbfc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58ac7629b7fac8a21bcf659655b2b18a34205c83 --- /dev/null +++ b/marked/Rel-16/23_series/23783/dd6c544ab685b25dd17f59456efcfbfc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0533041e8ab601b0b69a2c62e3f525cb9c6b042cb2a4fa98c9e35c152cda8b22 +size 93316 diff --git a/marked/Rel-16/23_series/23783/ddcf2f580e914bff1e7756ed288874e1_img.jpg b/marked/Rel-16/23_series/23783/ddcf2f580e914bff1e7756ed288874e1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34171d8235ad55572723ca0d4118bc2d5f92178e --- /dev/null +++ b/marked/Rel-16/23_series/23783/ddcf2f580e914bff1e7756ed288874e1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:41e72f0107c700c82764b03eaf2098b39ec08c41d1e5e37af9d34873955fc8f5 +size 42277 diff --git a/marked/Rel-16/23_series/23783/de98d4c97665a29427651680af184ff4_img.jpg b/marked/Rel-16/23_series/23783/de98d4c97665a29427651680af184ff4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f348a68933b42bede74ab9eab022f9801dcb2e24 --- /dev/null +++ b/marked/Rel-16/23_series/23783/de98d4c97665a29427651680af184ff4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7c6138861e8dc57eef0b76b1bf1b6ed5af7dd0b9bc86cede1fbb4e0d6519f21 +size 55427 diff --git a/marked/Rel-16/23_series/23783/e038bf4fcea08f51944b4a2dd6e197a5_img.jpg b/marked/Rel-16/23_series/23783/e038bf4fcea08f51944b4a2dd6e197a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..80a6b5ccd401920203f6ddbdfc495b7dd86c1990 --- /dev/null +++ b/marked/Rel-16/23_series/23783/e038bf4fcea08f51944b4a2dd6e197a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e20cb82e4e1f38d32c35060ec70a9fb2e144c51353c942371c702ff35d47ca3d +size 51421 diff --git a/marked/Rel-16/23_series/23783/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/23_series/23783/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab1d0a53ebfceea49610d6df13bece0a59b98d4c --- /dev/null +++ b/marked/Rel-16/23_series/23783/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5025363f6dd47866227bc18b2de25aff3a1356bede945720a4678fe97128eef +size 40697 diff --git a/marked/Rel-16/23_series/23783/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-16/23_series/23783/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9999dc3dd8196d48a0fbbd002c58af16c414fab8 --- /dev/null +++ b/marked/Rel-16/23_series/23783/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b70b40ab38a766a1c77d075727ec5b03de92807d81b6926851c6e96fa7f5b69 +size 22615 diff --git a/marked/Rel-16/23_series/23783/e42cc691d9c7c4d23e66b04472bb494e_img.jpg b/marked/Rel-16/23_series/23783/e42cc691d9c7c4d23e66b04472bb494e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72e49dea21182ad617c016d78df3eeb7bf97b6be --- /dev/null +++ b/marked/Rel-16/23_series/23783/e42cc691d9c7c4d23e66b04472bb494e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:437f37317e2710c1096655752a74cd4aa21b501703e5ac38266b6316fd6dd2ff +size 23461 diff --git a/marked/Rel-16/23_series/23783/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-16/23_series/23783/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6892c7a18048adf238994fda70377b8e77a56f61 --- /dev/null +++ b/marked/Rel-16/23_series/23783/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d2d9bf40e137128692acddaebb90c60d3b803675e642d66ef8bb29f1b2698e3 +size 57546 diff --git a/marked/Rel-16/23_series/23783/e90b25c8d90cadc3f76c376701cf27ed_img.jpg b/marked/Rel-16/23_series/23783/e90b25c8d90cadc3f76c376701cf27ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d528b9f1d921b1ecdb35f87281c0da594861320 --- /dev/null +++ b/marked/Rel-16/23_series/23783/e90b25c8d90cadc3f76c376701cf27ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:642012bdd22a689446d4f6fe70b95d265b39a2950c3ea9fb3b4602b574169342 +size 87808 diff --git a/marked/Rel-16/23_series/23783/e9f5aa7b76362051c591d6783211f820_img.jpg b/marked/Rel-16/23_series/23783/e9f5aa7b76362051c591d6783211f820_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..196a1d52e5f541e3c4756aa2c3b14235ef854224 --- /dev/null +++ b/marked/Rel-16/23_series/23783/e9f5aa7b76362051c591d6783211f820_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f63b7a3e30ad3827e1848e59218a6d7a89b985d6890c3eecc2f3cfe13db8939a +size 52672 diff --git a/marked/Rel-16/23_series/23783/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23783/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5a9f14062f080e76c197c8b33c4f5c5b0b6bde9 --- /dev/null +++ b/marked/Rel-16/23_series/23783/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:404faaebbb1e4e52b1f6a4f8af7ec264ce55b7d0d664599dc9f77988f2dcc97b +size 58259 diff --git a/marked/Rel-16/23_series/23783/ec31af936fa94a6917bf19f154df8ac3_img.jpg b/marked/Rel-16/23_series/23783/ec31af936fa94a6917bf19f154df8ac3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..614edd0e35390ee6ce00d77c55fade6c71cc1a11 --- /dev/null +++ b/marked/Rel-16/23_series/23783/ec31af936fa94a6917bf19f154df8ac3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2c289f6ac4ff9061afa78ee2a27ea8528c27dd5624f9a5881d95a1daf6fc66a +size 54403 diff --git a/marked/Rel-16/23_series/23783/ef5f5c6665b6ae13660ede412333ba45_img.jpg b/marked/Rel-16/23_series/23783/ef5f5c6665b6ae13660ede412333ba45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..617c9e91144ac0fd9511a6e1686629bad7b7826f --- /dev/null +++ b/marked/Rel-16/23_series/23783/ef5f5c6665b6ae13660ede412333ba45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ecdee3a931a2c8afc8f9b0a4ccf09c6751aa16f326f97cc24351ad6ecd8fb85 +size 27510 diff --git a/marked/Rel-16/23_series/23783/ef8f4838401ece0abd51d63b897fa388_img.jpg b/marked/Rel-16/23_series/23783/ef8f4838401ece0abd51d63b897fa388_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..453484223454e62eee4a4c96bf29721164f9ea05 --- /dev/null +++ b/marked/Rel-16/23_series/23783/ef8f4838401ece0abd51d63b897fa388_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd98d872448f435d4e6ab93fe0c5329fcd83597c21cda89c4d51fd33bfdd9618 +size 41037 diff --git a/marked/Rel-16/23_series/23783/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg b/marked/Rel-16/23_series/23783/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89f8e448ed98f458c1394fe1ef4333fd8a6b4230 --- /dev/null +++ b/marked/Rel-16/23_series/23783/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e0eda391eb3f7d01c0b044043c66e1646484d90bbfcd33fc07c8c04f6b13bd7 +size 42553 diff --git a/marked/Rel-16/23_series/23783/f10dc32e3673e1392029a49e958a9d6c_img.jpg b/marked/Rel-16/23_series/23783/f10dc32e3673e1392029a49e958a9d6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82f867c3944d535d476d6e5e69ddf80479ebb626 --- /dev/null +++ b/marked/Rel-16/23_series/23783/f10dc32e3673e1392029a49e958a9d6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:359e9fc344da045f140ddf83a9e3712558885606fec228f31252924915d66ebc +size 68948 diff --git a/marked/Rel-16/23_series/23783/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg b/marked/Rel-16/23_series/23783/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44ddac617d4988541a7356e377309995899d2864 --- /dev/null +++ b/marked/Rel-16/23_series/23783/f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7faa2277a1ebcef349c8c1fb8873b3a5851eb2a036d6d6e4279fc4421aa8ea8 +size 57222 diff --git a/marked/Rel-16/23_series/23783/f1fbb1287d999c7034742de35bdab836_img.jpg b/marked/Rel-16/23_series/23783/f1fbb1287d999c7034742de35bdab836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2a88d4352c1a844ec3a2c46b9af2f037d094c16 --- /dev/null +++ b/marked/Rel-16/23_series/23783/f1fbb1287d999c7034742de35bdab836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c130c816da26fb611914abb07daa91ed7fe8d51738a9b02c82911a37e780394 +size 42305 diff --git a/marked/Rel-16/23_series/23783/f52f816ab28ff4b4a9d12c6c94fbd41c_img.jpg b/marked/Rel-16/23_series/23783/f52f816ab28ff4b4a9d12c6c94fbd41c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d5eab5b83d72d7087838bb99d72eca52bfd7ee1 --- /dev/null +++ b/marked/Rel-16/23_series/23783/f52f816ab28ff4b4a9d12c6c94fbd41c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b4aa7978613dc9acf0efe5050d5d758e4a24572c2c4421559e7de2d1cec3df5 +size 23094 diff --git a/marked/Rel-16/23_series/23783/f6e8acf9f931452d01688d311b5c0364_img.jpg b/marked/Rel-16/23_series/23783/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e811839998d7fa208b335cbb74a18cd53b42a9c --- /dev/null +++ b/marked/Rel-16/23_series/23783/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0db7b35f1c06a742972124903d6912099c40b47551d17ff0797ae733729da377 +size 17583 diff --git a/marked/Rel-16/23_series/23783/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg b/marked/Rel-16/23_series/23783/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31a617fbde3aa17d897143b9393adf386c58deee --- /dev/null +++ b/marked/Rel-16/23_series/23783/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:374a05d4acbf8b32ae26dbb9f38987b80662bde12afb04f20f11403bc2a0862e +size 50623 diff --git a/marked/Rel-16/23_series/23783/f7d969388c4f7e30cd04a061314bfa0e_img.jpg b/marked/Rel-16/23_series/23783/f7d969388c4f7e30cd04a061314bfa0e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb79a8324b7b7ae1cd64f862ca4cb96558e6531d --- /dev/null +++ b/marked/Rel-16/23_series/23783/f7d969388c4f7e30cd04a061314bfa0e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77656afdb9d5e5322e9c09a446a4ae585524a45fe31f879d46da37f975c5961a +size 57868 diff --git a/marked/Rel-16/23_series/23783/f89631cc38aa971e8d15cbffe28f1183_img.jpg b/marked/Rel-16/23_series/23783/f89631cc38aa971e8d15cbffe28f1183_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e19a75c3d49687623d09a362011ebe80950b2629 --- /dev/null +++ b/marked/Rel-16/23_series/23783/f89631cc38aa971e8d15cbffe28f1183_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37ba41408d7a106d7f3a818d6f3eef1121a5796b08f2b7483efd31b320c2a9ff +size 34386 diff --git a/marked/Rel-16/23_series/23783/fc0735d325f0ebd9214171975c68a888_img.jpg b/marked/Rel-16/23_series/23783/fc0735d325f0ebd9214171975c68a888_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5b3cc5fab9be98fb418f433ab7da1f9efca2fce --- /dev/null +++ b/marked/Rel-16/23_series/23783/fc0735d325f0ebd9214171975c68a888_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1561a55bf7a4646498b31fc4f5d7ce1d75a4a0666ea7a0f300740db302d2bec8 +size 32554 diff --git a/marked/Rel-16/23_series/23783/fc3e2b49a9f850951570e502393b697f_img.jpg b/marked/Rel-16/23_series/23783/fc3e2b49a9f850951570e502393b697f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..304f8dcd19de09aaaba560a5710a43a26094f9e9 --- /dev/null +++ b/marked/Rel-16/23_series/23783/fc3e2b49a9f850951570e502393b697f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bd57774895ad2b10df7aea520eddb75b47789b5736b1eec4dd0863a88f2f4e8 +size 101914 diff --git a/marked/Rel-16/23_series/23783/fcbc3c31776721edc98ceb1944ec438f_img.jpg b/marked/Rel-16/23_series/23783/fcbc3c31776721edc98ceb1944ec438f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdb6bf5fe01b08a5b437f5930b19996d4305d521 --- /dev/null +++ b/marked/Rel-16/23_series/23783/fcbc3c31776721edc98ceb1944ec438f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a87a67e5041d815f39b85ebe23328a4870fbc238e4deab05095b2bcd1984b5cf +size 48814 diff --git a/marked/Rel-16/23_series/23783/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-16/23_series/23783/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86a8a5386a68e7d34cd582a5d27b34ca4be40998 --- /dev/null +++ b/marked/Rel-16/23_series/23783/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e014741f67967497cf4c06829e010fe392ec3b905fbfded085ee34658485da39 +size 54205 diff --git a/marked/Rel-16/23_series/23783/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-16/23_series/23783/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c15400d499b58d909ade2b195735194aca8526fb --- /dev/null +++ b/marked/Rel-16/23_series/23783/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8af4a80f083b3259df047eb9afdc9bab47caebad0ac7dd3c0f9c1b685fb8c607 +size 47499 diff --git a/marked/Rel-16/23_series/23783/fe7304192caf64cda93b580c5e7e5c06_img.jpg b/marked/Rel-16/23_series/23783/fe7304192caf64cda93b580c5e7e5c06_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec72effcf63f7ff1ed59e01472c0259e8eb6a6cc --- /dev/null +++ b/marked/Rel-16/23_series/23783/fe7304192caf64cda93b580c5e7e5c06_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26ccdc9ff123cc1d2a74fc889d7f90e93aab84ad367cf09193587f86f2240f61 +size 146781 diff --git a/marked/Rel-16/23_series/23783/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Rel-16/23_series/23783/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7af59bb8c8385818d58c4e3b755fc8f0b4e591ca --- /dev/null +++ b/marked/Rel-16/23_series/23783/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3b85cb2674c120d604309bd0e1e7d3d7faaa586b6d1e013af19fb44929bfa9d +size 41786 diff --git a/marked/Rel-16/23_series/23783/raw.md b/marked/Rel-16/23_series/23783/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..080cea7f23986510c67e92fad0d0efb8a5d718fb --- /dev/null +++ b/marked/Rel-16/23_series/23783/raw.md @@ -0,0 +1,28128 @@ +# Contents + +| | | +|-------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 Subclauses in Mission Critical Specifications containing 4G specific terminology ..... | 6 | +| 4.1 Introduction ..... | 6 | +| 4.2 TS 23.280 ..... | 6 | +| 4.2.1 Proposed change to 1 Scope ..... | 6 | +| 4.2.2 Proposed change to 2 References ..... | 7 | +| 4.2.3 Proposed change to 3.2 Abbreviations ..... | 7 | +| 4.2.4 Proposed change to 4 Introduction ..... | 7 | +| 4.2.X Proposed change to ..... | 7 | +| 4.3 TS 23.281 ..... | 7 | +| 4.3.X Proposed change to <Y> <Title> ..... | 7 | +| 4.4 TS 23.282 ..... | 8 | +| 4.4.X Proposed change to <Y> <Title> ..... | 8 | +| 4.5 TS 23.283 ..... | 8 | +| 4.5.X Proposed change to <Y> <Title> ..... | 8 | +| 4.6 TS 23.379 ..... | 8 | +| 4.6.X Proposed change to <Y> <Title> ..... | 8 | +| 4.7 TS 23.479 ..... | 8 | +| 4.7.X Proposed change to <Y> <Title> ..... | 8 | +| 5 5GS aspects to support Mission Critical architecture ..... | 8 | +| 5.X <Example> ..... | 8 | +| 5.X.1 General description..... | 8 | +| 5.X.2 Impact ..... | 8 | +| 6 Key issues to ensure support of Mission Critical services over 5GS..... | 9 | +| 6.1 Key issue 1: Service continuity between on-network MC services and UE-to-network relay MC service ..... | 9 | +| 6.1.1 Description ..... | 9 | +| 6.1.2 Architectural requirements ..... | 9 | +| 6.2 Key issue 2: 5GC level roaming ..... | 9 | +| 6.2.1 Description ..... | 9 | +| 6.2.2 Architectural requirements ..... | 9 | +| 6.3 Key issue 3: Use of multicast..... | 9 | +| 6.3.1 Description ..... | 9 | +| 6.3.2 Architectural requirements ..... | 10 | +| 6.4 Key issue 4: ProSe..... | 10 | +| 6.4.1 Description ..... | 10 | +| 6.4.2 Architectural requirements ..... | 10 | +| 6.5 Key issue 5: APN ..... | 10 | +| 6.5.1 Description ..... | 10 | +| 6.5.2 Architectural requirements ..... | 10 | +| 6.6 Key issue 6: resource control ..... | 11 | +| 6.6.1 Description ..... | 11 | +| 6.6.2 Architectural requirements ..... | 11 | +| 6.x Key issue x: <Key issue title>..... | 11 | +| 6.x.1 Description ..... | 11 | +| 6.x.2 Architectural requirements ..... | 11 | +| 7 Solutions to ensure support of Mission Critical services over 5GS..... | 11 | +| 7.x Solution x: <Solution title> ..... | 11 | +| 7.x.1 Description ..... | 11 | + +| | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------|-----------| +| 7.x.2 | Impacts on existing nodes and functionality ..... | 11 | +| 7.x.3 | Solution evaluation ..... | 11 | +| 8 | Overall evaluation ..... | 12 | +| 9 | Conclusions ..... | 12 | +| <b>Editor's Note: This clause is intended to list conclusions that have been agreed during the course of the study item activities. Annex A: Copy of TS 23.280 with highlighted E-UTRAN/EPS specific terminology and references.....</b> | | <b>12</b> | +| <b>Annex B: Copy of TS 23.379 with highlighted E-UTRAN/EPS specific terminology and references....</b> | | <b>13</b> | +| <b>Annex C: Copy of TS 23.281 with highlighted E-UTRAN/EPS specific terminology and references ...</b> | | <b>13</b> | +| <b>Annex D: Copy of TS 23.282 with highlighted E-UTRAN/EPS specific terminology and references ...</b> | | <b>14</b> | +| <b>Annex E: Copy of TS 23.283 with highlighted E-UTRAN/EPS specific terminology and references....</b> | | <b>14</b> | +| <b>Annex F: Change history.....</b> | | <b>14</b> | + +# --- Foreword + +This Technical Report has been produced by the 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. + +# --- Introduction + +*This clause is optional. If it exists, it is always the second unnumbered clause.* + +# --- 1 Scope + +The present document describes the impacts on and the necessary changes in the Stage 2 Mission Critical specifications to ensure that the set of Mission Critical services is supported over the 5GS. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +*Editor's note: Further numbered references to be inserted here* + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**example:** text used to clarify abstract rules by applying them literally. + +*Editor's note: Example line above to be deleted and replaced by definitions as needed.* + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +<ACRONYM> <Explanation> + +*Editor's note: Example line above to be deleted and replaced by definitions as needed.* + +# --- 4 Subclauses in Mission Critical Specifications containing 4G specific terminology + +## 4.1 Introduction + +*Editor's note: To be replaced by introductory text describing the approach.* + +## 4.2 TS 23.280 + +### 4.2.1 Proposed change to 1 Scope + +This document specifies the common functional architecture, procedures and information flows needed to support mission critical services including the common services core architecture. + +The corresponding service requirements are defined in 3GPP TS 22.179 [2], 3GPP TS 22.280 [3], 3GPP TS 22.281 [4] and 3GPP TS 22.282 [5]. + +The present document is applicable primarily to mission critical services **using E-UTRAN access based on the EPC architecture defined in 3GPP TS 23.401 [17] and using 5GS access based on the 5G System architecture defined in 3GPP TS 23.501[X]**. Certain MC service functions such as dispatch and administrative functions could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access. + +The common functional architecture to support mission critical services can be used for public safety applications and also for general commercial applications e.g. utility companies and railways. + +### 4.2.2 Proposed change to 2 References + +Add reference: + +[X] 3GPP TS 23.501: "System Architecture for the 5G System". + +### 4.2.3 Proposed change to 3.2 Abbreviations + +Insert abbreviation: + +5GC 5G Core Network + +### 4.2.4 Proposed change to 4 Introduction + +A common functional architecture to support MC services (i.e., MCPTT defined in 3GPP TS 23.379 [16], MCVideo defined in 3GPP TS 23.281 [12], MCData defined in 3GPP TS 23.282 [13]) including common application plane and signalling plane entities is specified in this document. + +Each MC service supports several types of communications amongst the users (e.g. group call, private call). There are several common functions and entities (e.g. group, configuration, identity) which are used by the MC services. + +The common functional architecture to support MC services utilises aspects of the IMS architecture defined in 3GPP TS 23.228 [9], the Proximity-based Services (ProSe) architecture defined in 3GPP TS 23.303 [14], the Group Communication System Enablers for LTE (GCSE\_LTE) architecture defined in 3GPP TS 23.468 [18] and the PS-PS access transfer procedures defined in 3GPP TS 23.237 [10]. + +The MC service UE primarily obtains access to a MC service via E-UTRAN, using the EPS architecture defined in 3GPP TS 23.401 [17] and using 5GS access based on the 5G System architecture defined in 3GPP TS 23.501[X]. + +Certain MC service functions such as dispatch and administrative functions can be supported using either MC service UEs in E-UTRAN, using MC service UEs in 5GS or using MC service UEs via non-3GPP access networks. External applications usage of MC services can be enabled via E-UTRAN, 5GS or non-3GPP access networks. + +NOTE: Dispatch consoles and devices used by MC service administrators are considered MC service UEs in the common functional architecture to support MC services. + +### 4.2.X Proposed change to <Y> <Title> + +Editor's note: Proposed modification to cover both 4G and 5GS, using highlighting, hard-strikeout of removed text and hard-underlining for new text. + +## 4.3 TS 23.281 + +### 4.3.X Proposed change to <Y> <Title> + +Editor's note: Proposed modification to cover both 4G and 5GS, using highlighting, hard-strikeout of removed text and hard-underlining for new text. + +## 4.4 TS 23.282 + +### 4.4.X Proposed change to <Y> <Title> + +Editor's note: Proposed modification to cover both 4G and 5GS, using highlighting, hard-strikeout of removed text and hard-underlining for new text. + +## 4.5 TS 23.283 + +### 4.5.X Proposed change to <Y> <Title> + +Editor's note: Proposed modification to cover both 4G and 5GS, using highlighting, hard-strikeout of removed text and hard-underlining for new text. + +## 4.6 TS 23.379 + +### 4.6.X Proposed change to <Y> <Title> + +Editor's note: Proposed modification to cover both 4G and 5GS, using highlighting, hard-strikeout of removed text and hard-underlining for new text. + +## 4.7 TS 23.479 + +### 4.7.X Proposed change to <Y> <Title> + +Editor's note: Proposed modification to cover both 4G and 5GS, using highlighting, hard-strikeout of removed text and hard-underlining for new text. + +# --- 5 5GS aspects to support Mission Critical architecture + +## 5.X <Example> + +### 5.X.1 General description + +### 5.X.2 Impact + +# --- 6 Key issues to ensure support of Mission Critical services over 5GS + +## 6.1 Key issue 1: Service continuity between on-network MC services and UE-to-network relay MC service + +### 6.1.1 Description + +Service continuity between on-network MC services and UE-to-network relay MC services is currently not supported by 5GS. + +This has impact to: + +- TS 23.280 subclause 5.1.1, 5.2.3, 8.3.1, 9.2.1.5, 9.2.1.6, 10.5.1, 10.5.2, 10.7.3.7.3, Annex B.1 + +The search terms to create the above list are: UE-R and UE-to-network relay. Occurrences of these terms have been highlighted in a copy of the TS in annex A of this report. + +### 6.1.2 Architectural requirements + +Editor's Note: Capture agreements on architectural requirements for solving the key issue. This clause may be omitted if deemed unnecessary. + +## 6.2 Key issue 2: 5GC level roaming + +### 6.2.1 Description + +5GC level roaming is FFS. + +This has impact to: + +- TS 23.280 subclause 5.2.2, 5.2.9.2, 9.4 + +Occurrences of the term EPC-level roaming have been highlighted in a copy of the TS in annex A of this report. + +### 6.2.2 Architectural requirements + +**Editor's Note:** Capture agreements on architectural requirements for solving the key issue. This clause may be omitted if deemed unnecessary. + +## 6.3 Key issue 3: Use of multicast + +### 6.3.1 Description + +The use of multicast in 5GS is FFS. + +This has impact to: + +- TS 23.280 subclause 5.2.1, 5.2.6, 5.2.7.1, 7.2, 7.3.1, 7.4.2.3.2, 7.5.3.2, 7.5.3.3, all of 10.7, 10.9.3.1, 10.11.4; +- TS 23.379 subclause 5.7.4, 7.3.1, 7.4.2.3.2, 7.5.2.2, 7.5.2.7, 7.5.2.9, 7.5.2.10, 10.6.2.5.2.4, 10.9.1.6, all of 10.10; +- TS 23.281 subclause 5.5.4, 6.1.1, 6.2.2.3.2, 6.3.4B, 6.3.6, 6.3.7, all of 7.10; and +- TS 23.282 subclause 5.4, 5.8.4, 6.4.3.1.2, 6.4.4.1.4, 6.5.4.1.3, 6.6.4.1.3, 6.6.4.1.5, 6.7.4.1.3, all of 7.3, 7.5.2.7.2, 7.7.2.2.2.1, 7.7.2.3.2.1 + +The search terms to create the above list are: GCSE\_LTE, MBMS, BM-SC, MB2-U, MB2-C, GC1, TMGI, MBSFN, ECGI, SAI, TS 23.246, TS 23.468 and TS 29.468. Occurrences of these terms have been highlighted in copies of the TSs in annex A, annex B, annex C and annex D of this report. + +### 6.3.2 Architectural requirements + +**Editor's Note:** Capture agreements on architectural requirements for solving the key issue. This clause may be omitted if deemed unnecessary. + +## 6.4 Key issue 4: ProSe + +### 6.4.1 Description + +A equivalent to ProSe in 5GS is FFS. + +This has impact to: + +- TS 23.280 subclause 5.1.1, 5.2.3, 8.1.3.2, 9.2.1.5, 9.2.1.6, 9.3.2, 10.5.1, 10.5.2, 10.7.2.1, 10.7.2.5, 10.7.3.7.3, 10.10.2.2.1, 10.10.2.2.2, A.4, B.1; +- TS 23.379 subclause 10.6.3.3, 10.6.3.9.1, 10.7.3.2, A.2, A.3, A.4, A.5; +- TS 23.281 subclause 7.1.3.3.2, 7.1.3.4.2, 7.1.3.5.2, 7.1.3.8.1, 7.1.3.8.2, 7.2.3.3, 7.2.3.4.2, 7.2.3.5.2, 7.2.3.5.3, 7.3.3.3.2, 7.4.3.3.2, 7.4.3.4.2, 7.5.3.3.2, 7.5.3.4.2, 7.5.3.4.3, 7.5.3.5.2, 7.5.3.5.3, 7.7.2.1, A.2, A.3, A.4, A.5; and +- TS 23.282 subclause 7.4.3.3.2, 7.4.3.4.2, 7.5.3.3.2, 7.5.3.4.2, 7.8.3.1.1, 7.8.3.2.1, 7.9.4.1.1, A.2, A.3, A.4, A.5; + +The search terms to create the above list are: PC5, ProSe, TS 23.303. Occurrences of these terms have been highlighted in copies of the TSs in annex A, annex B, annex C and annex D of this report. + +### 6.4.2 Architectural requirements + +*Editor's Note: Capture agreements on architectural requirements for solving the key issue. This clause may be omitted if deemed unnecessary.* + +## 6.5 Key issue 5: APN + +### 6.5.1 Description + +The impact of the APN alternative in 5GS is FFS. + +This has impact to: + +- TS 23.280 subclause 5.2.7.0, 5.2.7.2, 5.2.9.2, A.6; +- TS 23.379 subclause 5.7.1; +- TS 23.281 subclause 5.5.1; and +- TS 23.282 subclause 5.8.1; + +The search terms to create the above list are: APN, APNs, PAP, CHAP. Occurrences of these terms have been highlighted in copies of the TSs in annex A, annex B, annex C and annex D of this report. + +### 6.5.2 Architectural requirements + +*Editor's Note: Capture agreements on architectural requirements for solving the key issue. This clause may be omitted if deemed unnecessary.* + +## 6.6 Key issue 6: resource control + +### 6.6.1 Description + +The impact of different resource control (including 5QI) in 5GS is FFS. + +This has impact to: + +- TS 23.280 subclause 5.2.7.2, 7.2, 10.7.2.1, 10.7.2.4, 10.7.2.5, 10.7.2.6, 10.7.2.7, 10.11.2, 10.11.3, 10.11.5.2; +- TS 23.379 subclause 5.7.3, 7.5.2.6; +- TS 23.281 subclause 5.5.3, 6.3.4A; and +- TS 23.282 subclause 5.8.3, 6.4.4.1.3A; + +The search term to create the above list is: QCI, TS 23.203. Occurrences of these terms have been highlighted in copies of the TSs in annex A, annex B, annex C and annex D of this report. + +### 6.6.2 Architectural requirements + +*Editor's Note: Capture agreements on architectural requirements for solving the key issue. This clause may be omitted if deemed unnecessary.* + +## 6.x Key issue x: <Key issue title> + +### 6.x.1 Description + +*Editor's Note: Describe the key issue (i.e. problem statement), including technical constraints and interpretations.* + +### 6.x.2 Architectural requirements + +*Editor's Note: Capture agreements on architectural requirements for solving the key issue. This clause may be omitted if deemed unnecessary.* + +# --- 7 Solutions to ensure support of Mission Critical services over 5GS + +## 7.x Solution x: <Solution title> + +### 7.x.1 Description + +*Editor's Note: Describe the solutions. Sub-clause(s) may be added to capture details, procedural flow etc.* + +### 7.x.2 Impacts on existing nodes and functionality + +*Editor's Note: Capture impacts on existing 3GPP nodes and functional elements.* + +### 7.x.3 Solution evaluation + +*Editor's Note: Use this section for evaluation at solution level.* + +# --- 8 Overall evaluation + +*Editor's Note: This clause will provide evaluation of different solutions.* + +# --- 9 Conclusions + +**Editor's Note:** This clause is intended to list conclusions that have been agreed during the course of the study item activities. + +# Annex A: + +## Copy of TS 23.280 with highlighted E-UTRAN/EPS specific terminology and references + +### Editor's note: + +This copy of TS 23.280 has the following terminology highlighted, identified as E-UTRAN/EPS specific: +UE-R, UE-to-network relay, +EPC-level roaming, +GCSE\_LTE, MBMS, BM-SC, MB2-U, MB2-C, GC1, TMGI, MBSFN, ECGI, SAI, TS 23.246, TS 23.468, TS-29.468, +PC5, ProSe, TS 23.303, +APN, PAP, CHAP, +QCI, TS 23.203, +LTE, EPS, EPC, E-UTRAN, eNB, TS 23.401, TS 36.300, GSMA PRD IR.88, TS 36.331 + +--- + +# Annex B: + +## Copy of TS 23.379 with highlighted E-UTRAN/EPS specific terminology and references + +### Editor's note: + +This copy of TS 23.379 has the following terminology highlighted, identified as E-UTRAN/EPS specific: +UE-R, UE-to-network relay, +EPC-level roaming, +GCSE\_LTE, MBMS, BM-SC, MB2-U, MB2-C, GC1, TMGI, MBSFN, ECGI, SAI, TS 23.246, TS 23.468, TS-29.468, +PC5, ProSe, TS 23.303, +APN, PAP, CHAP, +QCI, TS 23.203, +LTE, EPS, EPC, E-UTRAN, eNB, TS 23.401, TS 36.300, GSMA PRD IR.88, TS 36.331 + +--- + +# Annex C: + +## Copy of TS 23.281 with highlighted E-UTRAN/EPS specific terminology and references + +### Editor's note: + +This copy of TS 23.281 has the following terminology highlighted, identified as E-UTRAN/EPS specific: +UE-R, UE-to-network relay, +EPC-level roaming, +GCSE\_LTE, MBMS, BM-SC, MB2-U, MB2-C, GC1, TMGI, MBSFN, ECGI, SAI, TS 23.246, TS 23.468, TS-29.468, +PC5, ProSe, TS 23.303, +APN, PAP, CHAP, +QCI, TS 23.203, +LTE, EPS, EPC, E-UTRAN, eNB, TS 23.401, TS 36.300, GSMA PRD IR.88, TS 36.331 + +# Annex D: + +## Copy of TS 23.282 with highlighted E-UTRAN/EPS specific terminology and references + +### Editor's note: + +This copy of TS 23.282 has the following terminology highlighted, identified as E-UTRAN/EPS specific: + UE-R, UE-to-network relay, + EPC-level roaming, + GCSE\_LTE, MBMS, BM-SC, MB2-U, MB2-C, GC1, TMGI, MBSFN, ECGI, SAI, TS 23.246, TS 23.468, TS-29.468, + PC5, ProSe, TS 23.303, + APN, PAP, CHAP, + QCI, TS 23.203, + LTE, EPS, EPC, E-UTRAN, eNB, TS 23.401, TS 36.300, GSMA PRD IR.88, TS 36.331 + +# Annex E: + +## Copy of TS 23.283 with highlighted E-UTRAN/EPS specific terminology and references + +### Editor's note: + +This copy of TS 23.283 has the following terminology highlighted, identified as E-UTRAN/EPS specific: + UE-R, UE-to-network relay, + EPC-level roaming, + GCSE\_LTE, MBMS, BM-SC, MB2-U, MB2-C, GC1, TMGI, MBSFN, ECGI, SAI, TS 23.246, TS 23.468, TS-29.468, + PC5, ProSe, TS 23.303, + APN, PAP, CHAP, + QCI, TS 23.203, + LTE, EPS, EPC, E-UTRAN, eNB, TS 23.401, TS 36.300, GSMA PRD IR.88, TS 36.331 + +# Annex F: + +# Change history + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-07 | SA6#25 | | | | | Implementation of the following p-CRs approved by SA6: S6-181194, S6-181196, S6-181197, S6-181199, S6-181200, S6 18201, S6-181251, S6-181267 | 0.0.0 | +| 2018-07 | SA6#25 | | | | | Correction of the change history to include references to the implemented pCRs | 0.1.0 | +| 2018-10 | SA6#26 | | | | | Implementation of the following p-CRs approved by SA6: S6-181516, S6-181517, S6-181518, S6-181519, S6-181566, S6-181567, S6-181568, S6-181569, S6-181570 | 0.2.0 | + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 Subclauses in Mission Critical Specifications containing 4G specific terminology ..... | 6 | +| 4.1 Introduction ..... | 6 | +| 4.2 TS 23.280 ..... | 6 | +| 4.2.1 Proposed change to 1 Scope ..... | 6 | +| 4.2.2 Proposed change to 2 References ..... | 7 | +| 4.2.3 Proposed change to 3.2 Abbreviations ..... | 7 | +| 4.2.4 Proposed change to 4 Introduction ..... | 7 | +| 4.2.X Proposed change to <Y> <Title> ..... | 7 | +| 4.3 TS 23.281 ..... | 7 | +| 4.3.X Proposed change to <Y> <Title> ..... | 7 | +| 4.4 TS 23.282 ..... | 8 | +| 4.4.X Proposed change to <Y> <Title> ..... | 8 | +| 4.5 TS 23.283 ..... | 8 | +| 4.5.X Proposed change to <Y> <Title> ..... | 8 | +| 4.6 TS 23.379 ..... | 8 | +| 4.6.X Proposed change to <Y> <Title> ..... | 8 | +| 4.7 TS 23.479 ..... | 8 | +| 4.7.X Proposed change to <Y> <Title> ..... | 8 | +| 5 5GS aspects to support Mission Critical architecture ..... | 8 | +| 5.X <Example> ..... | 8 | +| 5.X.1 General description..... | 8 | +| 5.X.2 Impact ..... | 8 | +| 6 Key issues to ensure support of Mission Critical services over 5GS..... | 9 | +| 6.1 Key issue 1: Service continuity between on-network MC services and UE-to-network relay MC service ..... | 9 | +| 6.1.1 Description ..... | 9 | +| 6.1.2 Architectural requirements ..... | 9 | +| 6.2 Key issue 2: 5GC level roaming ..... | 9 | +| 6.2.1 Description ..... | 9 | +| 6.2.2 Architectural requirements ..... | 9 | +| 6.3 Key issue 3: Use of multicast..... | 9 | +| 6.3.1 Description ..... | 9 | +| 6.3.2 Architectural requirements ..... | 10 | +| 6.4 Key issue 4: ProSe..... | 10 | +| 6.4.1 Description ..... | 10 | +| 6.4.2 Architectural requirements ..... | 10 | +| 6.5 Key issue 5: APN ..... | 10 | +| 6.5.1 Description ..... | 10 | +| 6.5.2 Architectural requirements ..... | 10 | +| 6.6 Key issue 6: resource control ..... | 11 | +| 6.6.1 Description ..... | 11 | +| 6.6.2 Architectural requirements ..... | 11 | +| 6.x Key issue x: <Key issue title>..... | 11 | +| 6.x.1 Description ..... | 11 | +| 6.x.2 Architectural requirements ..... | 11 | +| 7 Solutions to ensure support of Mission Critical services over 5GS..... | 11 | +| 7.x Solution x: <Solution title> ..... | 11 | +| 7.x.1 Description ..... | 11 | + +7.x.2 Impacts on existing nodes and functionality ..... 11 +7.x.3 Solution evaluation..... 11 +8 Overall evaluation..... 12 +9 Conclusions..... 12 +**Annex A: Copy of TS 23.280 with highlighted E-UTRAN/EPS specific terminology and references ... 12** +**Annex B: Copy of TS 23.379 with highlighted E-UTRAN/EPS specific terminology and references.... 12** +**Annex C: Copy of TS 23.281 with highlighted E-UTRAN/EPS specific terminology and references ... 12** +**Annex D: Copy of TS 23.282 with highlighted E-UTRAN/EPS specific terminology and references ... 13** +**Annex E: Copy of TS 23.283 with highlighted E-UTRAN/EPS specific terminology and references.... 13** +**Annex F: Change history..... 14** + +# --- Foreword + +This Technical Report has been produced by the 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. + +# --- Introduction + +*This clause is optional. If it exists, it is always the second unnumbered clause.* + +# --- 1 Scope + +The present document describes the impacts on and the necessary changes in the Stage 2 Mission Critical specifications to ensure that the set of Mission Critical services is supported over the 5GS. + +# --- 2 References + +The following documents contain provisions which, through reference in this text, constitute provisions of the present document. + +[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". + +*Editor's note: Further numbered references to be inserted here* + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**example:** text used to clarify abstract rules by applying them literally. + +*Editor's note: Example line above to be deleted and replaced by definitions as needed.* + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +<ACRONYM> <Explanation> + +*Editor's note: Example line above to be deleted and replaced by definitions as needed.* + +# --- 4 Subclauses in Mission Critical Specifications containing 4G specific terminology + +## 4.1 Introduction + +*Editor's note: To be replaced by introductory text describing the approach.* + +## 4.2 TS 23.280 + +### 4.2.1 Proposed change to 1 Scope + +This document specifies the common functional architecture, procedures and information flows needed to support mission critical services including the common services core architecture. + +The corresponding service requirements are defined in 3GPP TS 22.179 [2], 3GPP TS 22.280 [3], 3GPP TS 22.281 [4] and 3GPP TS 22.282 [5]. + +The present document is applicable primarily to mission critical services **using E-UTRAN access based on the EPC architecture defined in 3GPP TS 23.401 [17] and using 5GS access based on the 5G System architecture defined in 3GPP TS 23.501[X]**. Certain MC service functions such as dispatch and administrative functions could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access. + +The common functional architecture to support mission critical services can be used for public safety applications and also for general commercial applications e.g. utility companies and railways. + +### 4.2.2 Proposed change to 2 References + +Add reference: + +[X] 3GPP TS 23.501: "System Architecture for the 5G System". + +### 4.2.3 Proposed change to 3.2 Abbreviations + +Insert abbreviation: + +5GC 5G Core Network + +### 4.2.4 Proposed change to 4 Introduction + +A common functional architecture to support MC services (i.e., MCPTT defined in 3GPP TS 23.379 [16], MCVideo defined in 3GPP TS 23.281 [12], MCData defined in 3GPP TS 23.282 [13]) including common application plane and signalling plane entities is specified in this document. + +Each MC service supports several types of communications amongst the users (e.g. group call, private call). There are several common functions and entities (e.g. group, configuration, identity) which are used by the MC services. + +The common functional architecture to support MC services utilises aspects of the IMS architecture defined in 3GPP TS 23.228 [9], the Proximity-based Services (ProSe) architecture defined in 3GPP TS 23.303 [14], the Group Communication System Enablers for LTE (GCSE\_LTE) architecture defined in 3GPP TS 23.468 [18] and the PS-PS access transfer procedures defined in 3GPP TS 23.237 [10]. + +The MC service UE primarily obtains access to a MC service via E-UTRAN, using the EPS architecture defined in 3GPP TS 23.401 [17] and using 5GS access based on the 5G System architecture defined in 3GPP TS 23.501[X]. + +Certain MC service functions such as dispatch and administrative functions can be supported using either MC service UEs in E-UTRAN, using MC service UEs in 5GS or using MC service UEs via non-3GPP access networks. External applications usage of MC services can be enabled via E-UTRAN, 5GS or non-3GPP access networks. + +NOTE: Dispatch consoles and devices used by MC service administrators are considered MC service UEs in the common functional architecture to support MC services. + +### 4.2.X Proposed change to <Y> <Title> + +Editor's note: Proposed modification to cover both 4G and 5GS, using highlighting, hard-strikeout of removed text and hard-underlining for new text. + +## 4.3 TS 23.281 + +### 4.3.X Proposed change to <Y> <Title> + +Editor's note: Proposed modification to cover both 4G and 5GS, using highlighting, hard-strikeout of removed text and hard-underlining for new text. + +## 4.4 TS 23.282 + +### 4.4.X Proposed change to <Y> <Title> + +Editor's note: Proposed modification to cover both 4G and 5GS, using highlighting, hard-strikeout of removed text and hard-underlining for new text. + +## 4.5 TS 23.283 + +### 4.5.X Proposed change to <Y> <Title> + +Editor's note: Proposed modification to cover both 4G and 5GS, using highlighting, hard-strikeout of removed text and hard-underlining for new text. + +## 4.6 TS 23.379 + +### 4.6.X Proposed change to <Y> <Title> + +Editor's note: Proposed modification to cover both 4G and 5GS, using highlighting, hard-strikeout of removed text and hard-underlining for new text. + +## 4.7 TS 23.479 + +### 4.7.X Proposed change to <Y> <Title> + +Editor's note: Proposed modification to cover both 4G and 5GS, using highlighting, hard-strikeout of removed text and hard-underlining for new text. + +# --- 5 5GS aspects to support Mission Critical architecture + +## 5.X <Example> + +### 5.X.1 General description + +### 5.X.2 Impact + +# --- 6 Key issues to ensure support of Mission Critical services over 5GS + +## 6.1 Key issue 1: Service continuity between on-network MC services and UE-to-network relay MC service + +### 6.1.1 Description + +Service continuity between on-network MC services and UE-to-network relay MC services is currently not supported by 5GS. + +This has impact to: + +- TS 23.280 subclause 5.1.1, 5.2.3, 8.3.1, 9.2.1.5, 9.2.1.6, 10.5.1, 10.5.2, 10.7.3.7.3, Annex B.1 + +The search terms to create the above list are: UE-R and UE-to-network relay. Occurrences of these terms have been highlighted in a copy of the TS in annex A of this report. + +### 6.1.2 Architectural requirements + +Editor's Note: Capture agreements on architectural requirements for solving the key issue. This clause may be omitted if deemed unnecessary. + +## 6.2 Key issue 2: 5GC level roaming + +### 6.2.1 Description + +5GC level roaming is FFS. + +This has impact to: + +- TS 23.280 subclause 5.2.2, 5.2.9.2, 9.4 + +Occurrences of the term EPC-level roaming have been highlighted in a copy of the TS in annex A of this report. + +### 6.2.2 Architectural requirements + +**Editor's Note:** Capture agreements on architectural requirements for solving the key issue. This clause may be omitted if deemed unnecessary. + +## 6.3 Key issue 3: Use of multicast + +### 6.3.1 Description + +The use of multicast in 5GS is FFS. + +This has impact to: + +- TS 23.280 subclause 5.2.1, 5.2.6, 5.2.7.1, 7.2, 7.3.1, 7.4.2.3.2, 7.5.3.2, 7.5.3.3, all of 10.7, 10.9.3.1, 10.11.4; +- TS 23.379 subclause 5.7.4, 7.3.1, 7.4.2.3.2, 7.5.2.2, 7.5.2.7, 7.5.2.9, 7.5.2.10, 10.6.2.5.2.4, 10.9.1.6, all of 10.10; +- TS 23.281 subclause 5.5.4, 6.1.1, 6.2.2.3.2, 6.3.4B, 6.3.6, 6.3.7, all of 7.10; and +- TS 23.282 subclause 5.4, 5.8.4, 6.4.3.1.2, 6.4.4.1.4, 6.5.4.1.3, 6.6.4.1.3, 6.6.4.1.5, 6.7.4.1.3, all of 7.3, 7.5.2.7.2, 7.7.2.2.2.1, 7.7.2.3.2.1 + +The search terms to create the above list are: GCSE\_LTE, MBMS, BM-SC, MB2-U, MB2-C, GC1, TMGI, MBSFN, ECGI, SAI, TS 23.246, TS 23.468 and TS 29.468. Occurrences of these terms have been highlighted in copies of the TSs in annex A, annex B, annex C and annex D of this report. + +### 6.3.2 Architectural requirements + +**Editor's Note:** Capture agreements on architectural requirements for solving the key issue. This clause may be omitted if deemed unnecessary. + +## 6.4 Key issue 4: ProSe + +### 6.4.1 Description + +A equivalent to ProSe in 5GS is FFS. + +This has impact to: + +- TS 23.280 subclause 5.1.1, 5.2.3, 8.1.3.2, 9.2.1.5, 9.2.1.6, 9.3.2, 10.5.1, 10.5.2, 10.7.2.1, 10.7.2.5, 10.7.3.7.3, 10.10.2.2.1, 10.10.2.2.2, A.4, B.1; +- TS 23.379 subclause 10.6.3.3, 10.6.3.9.1, 10.7.3.2, A.2, A.3, A.4, A.5; +- TS 23.281 subclause 7.1.3.3.2, 7.1.3.4.2, 7.1.3.5.2, 7.1.3.8.1, 7.1.3.8.2, 7.2.3.3, 7.2.3.4.2, 7.2.3.5.2, 7.2.3.5.3, 7.3.3.3.2, 7.4.3.3.2, 7.4.3.4.2, 7.5.3.3.2, 7.5.3.4.2, 7.5.3.4.3, 7.5.3.5.2, 7.5.3.5.3, 7.7.2.1, A.2, A.3, A.4, A.5; and +- TS 23.282 subclause 7.4.3.3.2, 7.4.3.4.2, 7.5.3.3.2, 7.5.3.4.2, 7.8.3.1.1, 7.8.3.2.1, 7.9.4.1.1, A.2, A.3, A.4, A.5; + +The search terms to create the above list are: PC5, ProSe, TS 23.303. Occurrences of these terms have been highlighted in copies of the TSs in annex A, annex B, annex C and annex D of this report. + +### 6.4.2 Architectural requirements + +*Editor's Note: Capture agreements on architectural requirements for solving the key issue. This clause may be omitted if deemed unnecessary.* + +## 6.5 Key issue 5: APN + +### 6.5.1 Description + +The impact of the APN alternative in 5GS is FFS. + +This has impact to: + +- TS 23.280 subclause 5.2.7.0, 5.2.7.2, 5.2.9.2, A.6; +- TS 23.379 subclause 5.7.1; +- TS 23.281 subclause 5.5.1; and +- TS 23.282 subclause 5.8.1; + +The search terms to create the above list are: APN, APNs, PAP, CHAP. Occurrences of these terms have been highlighted in copies of the TSs in annex A, annex B, annex C and annex D of this report. + +### 6.5.2 Architectural requirements + +*Editor's Note: Capture agreements on architectural requirements for solving the key issue. This clause may be omitted if deemed unnecessary.* + +## 6.6 Key issue 6: resource control + +### 6.6.1 Description + +The impact of different resource control (including 5QI) in 5GS is FFS. + +This has impact to: + +- TS 23.280 subclause 5.2.7.2, 7.2, 10.7.2.1, 10.7.2.4, 10.7.2.5, 10.7.2.6, 10.7.2.7, 10.11.2, 10.11.3, 10.11.5.2; +- TS 23.379 subclause 5.7.3, 7.5.2.6; +- TS 23.281 subclause 5.5.3, 6.3.4A; and +- TS 23.282 subclause 5.8.3, 6.4.4.1.3A; + +The search term to create the above list is: QCI, TS 23.203. Occurrences of these terms have been highlighted in copies of the TSs in annex A, annex B, annex C and annex D of this report. + +### 6.6.2 Architectural requirements + +*Editor's Note: Capture agreements on architectural requirements for solving the key issue. This clause may be omitted if deemed unnecessary.* + +## 6.x Key issue x: <Key issue title> + +### 6.x.1 Description + +*Editor's Note: Describe the key issue (i.e. problem statement), including technical constraints and interpretations.* + +### 6.x.2 Architectural requirements + +*Editor's Note: Capture agreements on architectural requirements for solving the key issue. This clause may be omitted if deemed unnecessary.* + +# --- 7 Solutions to ensure support of Mission Critical services over 5GS + +## 7.x Solution x: <Solution title> + +### 7.x.1 Description + +Editor's Note: Describe the solutions. Sub-clause(s) may be added to capture details, procedural flow etc. + +### 7.x.2 Impacts on existing nodes and functionality + +Editor's Note: Capture impacts on existing 3GPP nodes and functional elements. + +### 7.x.3 Solution evaluation + +Editor's Note: Use this section for evaluation at solution level. + +# --- 8 Overall evaluation + +Editor's Note: This clause will provide evaluation of different solutions. + +# --- 9 Conclusions + +Editor's Note: This clause is intended to list conclusions that have been agreed during the course of the study item activities. + +# **Annex A:** + +Copy of TS 23.280 with highlighted E-UTRAN/EPS specific terminology and references + +## **Editor's note:** + +This copy of TS 23.280 has the following terminology highlighted, identified as E-UTRAN/EPS specific: +UE-R, UE-to-network relay, +EPC-level roaming, +GCSE\_LTE, MBMS, BM-SC, MB2-U, MB2-C, GC1, TMGI, MBSFN, ECGI, SAI, TS 23.246, TS 23.468, TS-29.468, +PC5, ProSe, TS 23.303, +APN, PAP, CHAP, +QCI, TS 23.203, +LTE, EPS, EPC, E-UTRAN, eNB, TS 23.401, TS 36.300, GSMA PRD IR.88, TS 36.331 + +--- + +# **Annex B:** + +**Copy of TS 23.379 with highlighted E-UTRAN/EPS specific terminology and references** + +## **Editor's note:** + +This copy of TS 23.379 has the following terminology highlighted, identified as E-UTRAN/EPS specific: +UE-R, UE-to-network relay, +EPC-level roaming, +GCSE\_LTE, MBMS, BM-SC, MB2-U, MB2-C, GC1, TMGI, MBSFN, ECGI, SAI, TS 23.246, TS 23.468, TS-29.468, +PC5, ProSe, TS 23.303, +APN, PAP, CHAP, +QCI, TS 23.203, +LTE, EPS, EPC, E-UTRAN, eNB, TS 23.401, TS 36.300, GSMA PRD IR.88, TS 36.331 + +--- + +# **Annex C:** + +**Copy of TS 23.281 with highlighted E-UTRAN/EPS specific terminology and references** + +## **Editor's note:** + +This copy of TS 23.281 has the following terminology highlighted, identified as E-UTRAN/EPS specific: +UE-R, UE-to-network relay, +EPC-level roaming, +GCSE\_LTE, MBMS, BM-SC, MB2-U, MB2-C, GC1, TMGI, MBSFN, ECGI, SAI, TS 23.246, TS 23.468, TS-29.468, +PC5, ProSe, TS 23.303, +APN, PAP, CHAP, +QCI, TS 23.203, +LTE, EPS, EPC, E-UTRAN, eNB, TS 23.401, TS 36.300, GSMA PRD IR.88, TS 36.331 + +--- + +# **Annex D:** + +**Copy of TS 23.282 with highlighted E-UTRAN/EPS specific terminology and references** + +## Editor's note: + +This copy of TS 23.282 has the following terminology highlighted, identified as E-UTRAN/EPS specific: + UE-R, UE-to-network relay, + EPC-level roaming, + GCSE\_LTE, MBMS, BM-SC, MB2-U, MB2-C, GC1, TMGI, MBSFN, ECGI, SAI, TS 23.246, TS 23.468, TS-29.468, + PC5, ProSe, TS 23.303, + APN, PAP, CHAP, + QCI, TS 23.203, + LTE, EPS, EPC, E-UTRAN, eNB, TS 23.401, TS 36.300, GSMA PRD IR.88, TS 36.331 + +# Annex E: + +## Copy of TS 23.283 with highlighted E-UTRAN/EPS specific terminology and references + +## Editor's note: + +This copy of TS 23.283 has the following terminology highlighted, identified as E-UTRAN/EPS specific: + UE-R, UE-to-network relay, + EPC-level roaming, + GCSE\_LTE, MBMS, BM-SC, MB2-U, MB2-C, GC1, TMGI, MBSFN, ECGI, SAI, TS 23.246, TS 23.468, TS-29.468, + PC5, ProSe, TS 23.303, + APN, PAP, CHAP, + QCI, TS 23.203, + LTE, EPS, EPC, E-UTRAN, eNB, TS 23.401, TS 36.300, GSMA PRD IR.88, TS 36.331 + +# Annex F: + +# Change history + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-07 | SA6#25 | | | | | Implementation of the following p-CRs approved by SA6:<br>S6-181194, S6-181196, S6-181197, S6-181199, S6-181200, S6 18201, S6-181251, S6-181267 | 0.0.0 | +| 2018-07 | SA6#25 | | | | | Correction of the change history to include references to the implemented pCRs | 0.1.0 | +| 2018-10 | SA6#26 | | | | | Implementation of the following p-CRs approved by SA6:<br>S6-181516, S6-181517, S6-181518, S6-181519, S6-181566, S6-181567, S6-181568, S6-181569, S6-181570 | 0.2.0 | + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|-----------------------------------------------------------------------------|----| +| Foreword ..... | 12 | +| 1 Scope..... | 13 | +| 2 References..... | 13 | +| 3 Definitions, symbols and abbreviations..... | 14 | +| 3.1 Definitions..... | 14 | +| 3.2 Symbols..... | 16 | +| 3.3 Abbreviations ..... | 16 | +| 4 Introduction..... | 17 | +| 5 Assumptions and architectural requirements ..... | 17 | +| 5.1 Assumptions..... | 17 | +| 5.1.1 Service continuity ..... | 17 | +| 5.1.2 Trust domain..... | 18 | +| 5.2 Architectural requirements ..... | 18 | +| 5.2.1 General architectural requirements..... | 18 | +| 5.2.2 Roaming requirements..... | 18 | +| 5.2.3 UE-to-network relay MC service requirements..... | 18 | +| 5.2.4 MC service user profile requirements ..... | 19 | +| 5.2.5 MC service group affiliation and MC service group de-affiliation..... | 19 | +| 5.2.6 GCS AS requirements for the MC services..... | 20 | +| 5.2.7 Bearer management..... | 20 | +| 5.2.7.0 General..... | 20 | +| 5.2.7.1 MBMS bearer management ..... | 21 | +| 5.2.7.2 EPS bearer considerations ..... | 21 | +| 5.2.8 External applications access to services in a MC system..... | 22 | +| 5.2.9 Migration ..... | 22 | +| 5.2.9.1 General..... | 22 | +| 5.2.9.2 PLMN utilisation ..... | 22 | +| 5.2.9.3 SIP core / IMS utilisation..... | 23 | +| 5.2.10 Interconnection ..... | 23 | +| 5.2.10.1 General..... | 23 | +| 5.2.10.2 Connectivity..... | 23 | +| 5.2.10.3 Migration ..... | 24 | +| 5.2.10.4 Private calls..... | 24 | +| 5.2.10.5 Group calls..... | 24 | +| 5.2.10.6 Group configuration..... | 24 | +| 5.2.10.7 MC system topology hiding..... | 24 | +| 6 Involved business relationships ..... | 24 | +| 7 Functional model..... | 27 | +| 7.1 General ..... | 27 | +| 7.2 Description of the planes..... | 27 | +| 7.3 Functional model description..... | 27 | +| 7.3.1 On-network functional model..... | 27 | +| 7.3.2 Off-network functional model..... | 31 | +| 7.4 Functional entities description ..... | 31 | +| 7.4.1 General ..... | 31 | +| 7.4.2 Application plane..... | 31 | +| 7.4.2.1 General..... | 31 | +| 7.4.2.2 Common services core..... | 32 | +| 7.4.2.2.1 Configuration management client..... | 32 | +| 7.4.2.2.2 Configuration management server ..... | 32 | +| 7.4.2.2.3 Group management client ..... | 32 | +| 7.4.2.2.4 Group management server ..... | 32 | +| 7.4.2.2.5 Identity management client..... | 32 | +| 7.4.2.2.6 Identity management server ..... | 32 | +| 7.4.2.2.7 Key management client..... | 33 | + +| | | | +|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 7.4.2.2.8 | Key management server ..... | 33 | +| 7.4.2.2.9 | Location management client ..... | 33 | +| 7.4.2.2.10 | Location management server ..... | 33 | +| 7.4.2.2.11 | Migration management server..... | 33 | +| 7.4.2.2.12 | Functional alias management client ..... | 34 | +| 7.4.2.2.13 | Functional alias management server ..... | 34 | +| 7.4.2.3 | MC service..... | 34 | +| 7.4.2.3.1 | MC service client ..... | 34 | +| 7.4.2.3.2 | MC service server..... | 34 | +| 7.4.2.3.3 | MC service user database..... | 34 | +| 7.4.2.3.4 | MC gateway server..... | 35 | +| 7.4.3 | Signalling control plane..... | 35 | +| 7.4.3.1 | SIP entities ..... | 35 | +| 7.4.3.1.1 | Signalling user agent ..... | 35 | +| 7.4.3.1.2 | SIP AS ..... | 35 | +| 7.4.3.1.3 | SIP core ..... | 35 | +| 7.4.3.1.3.1 | General ..... | 35 | +| 7.4.3.1.3.2 | Local inbound / outbound proxy ..... | 35 | +| 7.4.3.1.3.3 | Registrar finder ..... | 36 | +| 7.4.3.1.3.4 | Registrar / application service selection ..... | 36 | +| 7.4.3.1.4 | Diameter proxy..... | 36 | +| 7.4.3.2 | SIP database ..... | 37 | +| 7.4.3.2.1 | General ..... | 37 | +| 7.4.3.2.2 | SIP database logical functions..... | 37 | +| 7.4.3.3 | HTTP entities..... | 38 | +| 7.4.3.3.1 | HTTP client..... | 38 | +| 7.4.3.3.2 | HTTP proxy..... | 38 | +| 7.4.3.3.3 | HTTP server..... | 38 | +| 7.5 | Reference points..... | 38 | +| 7.5.1 | General reference point principle ..... | 38 | +| 7.5.2 | Application plane..... | 39 | +| 7.5.2.1 | General..... | 39 | +| 7.5.2.2 | Reference point CSC-1 (between the identity management client and the identity management server) ..... | 39 | +| 7.5.2.3 | Reference point CSC-2 (between the group management client and the group management server for configuration while UE is on-network)..... | 39 | +| 7.5.2.4 | Reference point CSC-3 (between the MC service server and the group management server)..... | 39 | +| 7.5.2.5 | Reference point CSC-4 (between the configuration management client and the configuration management server for configuration while UE is on-network) ..... | 39 | +| 7.5.2.6 | Reference point CSC-5 (between the MC service server and the configuration management server) ..... | 40 | +| 7.5.2.7 | Reference point CSC-7 (between the group management servers)..... | 40 | +| 7.5.2.8 | Reference point CSC-8 (between the key management server and the key management client)..... | 40 | +| 7.5.2.9 | Reference point CSC-9 (between the key management server and the MC service server) ..... | 40 | +| 7.5.2.10 | Reference point CSC-10 (between the key management server and the group management server) ..... | 40 | +| 7.5.2.11 | Reference point CSC-11 (between the configuration management client and the configuration management server for configuration while UE is off-network)..... | 40 | +| 7.5.2.12 | Reference point CSC-12 (between the group management client and the group management server for configuration while UE is off-network) ..... | 41 | +| 7.5.2.13 | Reference point CSC-13 (between the configuration management server and the MC service user database) ..... | 41 | +| 7.5.2.14 | Reference point CSC-14 (between the location management client and the location management server) ..... | 41 | +| 7.5.2.15 | Reference point CSC-15 (between the location management server and the MC service server) ..... | 41 | +| 7.5.2.16 | Reference point CSC-16 (between group management servers in different MC systems) ..... | 41 | +| 7.5.2.17 | Reference point CSC-17 (between configuration management servers in different MC systems) ..... | 41 | +| 7.5.2.18 | Reference point CSC-18 (between migration management servers in different MC systems) ..... | 42 | +| 7.5.2.19 | Reference point MCX-1 (between MC service servers)..... | 42 | +| 7.5.3 | Signalling control plane..... | 42 | +| 7.5.3.1 | General..... | 42 | +| 7.5.3.2 | Reference point SIP-1(between the signalling user agent and the SIP core)..... | 42 | + +| | | | +|-----------|--------------------------------------------------------------------------------------------------|----| +| 7.5.3.3 | Reference point SIP-2 (between the SIP core and the SIP AS)..... | 42 | +| 7.5.3.4 | Reference point SIP-3 (between the SIP core and SIP core)..... | 43 | +| 7.5.3.5 | Reference point HTTP-1 (between the HTTP client and the HTTP proxy)..... | 43 | +| 7.5.3.6 | Reference point HTTP-2 (between the HTTP proxy and the HTTP server)..... | 43 | +| 7.5.3.7 | Reference point HTTP-3 (between the HTTP proxy and HTTP proxy) ..... | 43 | +| 7.5.3.8 | Reference point AAA-1 (between the SIP database and the SIP core) ..... | 43 | +| 7.5.3.9 | Reference point AAA-2 (between the SIP core and Diameter proxy)..... | 43 | +| 8 | Identities..... | 44 | +| 8.1 | Application plane ..... | 44 | +| 8.1.1 | Mission Critical user identity (MC ID) ..... | 44 | +| 8.1.2 | MC service user identity (MC service ID) ..... | 44 | +| 8.1.3 | MC service group identity (MC service group ID) ..... | 44 | +| 8.1.3.1 | General..... | 44 | +| 8.1.3.2 | MC service group ID management (off-network operation) ..... | 45 | +| 8.1.4 | MC system identity (MC system ID) ..... | 45 | +| 8.2 | SIP signalling control plane ..... | 45 | +| 8.3 | Relationship between identities in different planes..... | 46 | +| 8.3.1 | Relationship between MC service ID and public user identity ..... | 46 | +| 8.3.2 | Relationship between MC service group ID and public service identity ..... | 46 | +| 9 | Application of functional model to deployments..... | 47 | +| 9.1 | General ..... | 47 | +| 9.2 | Architecture model and deployment scenarios for on-network operations..... | 47 | +| 9.2.1 | On-network architectural model..... | 47 | +| 9.2.1.1 | On-network architectural model diagram ..... | 47 | +| 9.2.1.2 | Application services layer..... | 48 | +| 9.2.1.2.1 | Overview ..... | 48 | +| 9.2.1.2.2 | Common services core ..... | 48 | +| 9.2.1.2.3 | MC services..... | 48 | +| 9.2.1.3 | SIP core ..... | 49 | +| 9.2.1.4 | EPS..... | 49 | +| 9.2.1.5 | UE 1 ..... | 49 | +| 9.2.1.6 | UE 2 ..... | 49 | +| 9.2.2 | Deployment scenarios ..... | 49 | +| 9.2.2.1 | Administration of MC service, SIP core and EPS ..... | 49 | +| 9.2.2.1.1 | General ..... | 49 | +| 9.2.2.1.2 | Common administration of all planes ..... | 49 | +| 9.2.2.1.3 | MC service provider separate from SIP core and EPS..... | 50 | +| 9.2.2.1.4 | MC service provider administers SIP core, separate from EPS..... | 51 | +| 9.2.2.1.5 | SIP core partially administered by both PLMN operator and MC service provider..... | 51 | +| 9.2.2.1.6 | PLMN operator administers SIP core with SIP identities administered by MC service provider ..... | 52 | +| 9.2.2.2 | MC service user database, SIP database and HSS..... | 53 | +| 9.2.2.3 | Control of bearers by SIP core and MC service server..... | 56 | +| 9.2.2.3.1 | General ..... | 56 | +| 9.2.2.3.2 | Control of bearers by SIP core ..... | 56 | +| 9.2.2.3.3 | Control of bearers by MC service server ..... | 56 | +| 9.3 | Architecture model for off-network operations ..... | 57 | +| 9.3.1 | Off-network architectural model diagram ..... | 57 | +| 9.3.2 | UE 3..... | 57 | +| 9.3.3 | UE 4..... | 58 | +| 9.3.4 | Offline common services server..... | 58 | +| 9.4 | Architecture model for roaming..... | 58 | +| 10 | Procedures and information flows ..... | 58 | +| 10.1 | MC service configuration..... | 58 | +| 10.1.1 | General ..... | 58 | +| 10.1.1.1 | MC service configuration on primary MC system ..... | 58 | +| 10.1.1.2 | MC service configuration for migration to partner MC system ..... | 59 | +| 10.1.2 | Information flows for MC service configuration ..... | 61 | +| 10.1.2.1 | Store group configuration request..... | 61 | +| 10.1.2.2 | Store group configuration response ..... | 61 | + +| | | | +|--------------|----------------------------------------------------------------------------------------------------------|----| +| 10.1.2.3 | Get group configuration request ..... | 61 | +| 10.1.2.4 | Get group configuration response ..... | 62 | +| 10.1.2.5 | Subscribe group configuration request ..... | 62 | +| 10.1.2.6 | Subscribe group configuration response ..... | 62 | +| 10.1.2.7 | Notify group configuration request ..... | 62 | +| 10.1.2.8 | Notify group configuration response ..... | 62 | +| 10.1.2.9 | Get functional alias configuration request ..... | 63 | +| 10.1.2.10 | Get functional alias configuration response ..... | 63 | +| 10.1.2.11 | Subscribe functional alias configuration request ..... | 63 | +| 10.1.2.12 | Subscribe functional alias configuration response ..... | 63 | +| 10.1.2.13 | Notify functional alias configuration request ..... | 64 | +| 10.1.2.14 | Notify functional alias configuration response ..... | 64 | +| 10.1.3 | MC service UE configuration data ..... | 64 | +| 10.1.3.1 | General ..... | 64 | +| 10.1.3.2 | Procedures ..... | 64 | +| 10.1.3.3 | Structure of UE configuration data ..... | 65 | +| 10.1.4 | MC service user profile ..... | 65 | +| 10.1.4.1 | General ..... | 65 | +| 10.1.4.2 | Information flows for MC service user profile ..... | 66 | +| 10.1.4.2.1 | Get MC service user profile request ..... | 66 | +| 10.1.4.2.2 | Get MC service user profile response ..... | 66 | +| 10.1.4.2.3 | Notification for MC service user profile data update ..... | 67 | +| 10.1.4.2.4 | Get updated MC service user profile data request ..... | 67 | +| 10.1.4.2.5 | Get updated MC service user profile data response ..... | 67 | +| 10.1.4.2.6 | Update MC service user profile data request ..... | 67 | +| 10.1.4.2.7 | Update MC service user profile data response ..... | 67 | +| 10.1.4.2.8 | Update pre-selected MC service user profile request ..... | 68 | +| 10.1.4.2.9 | Update pre-selected MC service user profile response ..... | 68 | +| 10.1.4.2.10 | Update selected MC service user profile request ..... | 68 | +| 10.1.4.2.11 | Update selected MC service user profile response ..... | 68 | +| 10.1.4.3 | MC service user obtains the MC service user profile(s) from the network ..... | 69 | +| 10.1.4.3.1 | MC service user receiving MC service in primary MC system ..... | 69 | +| 10.1.4.3.2 | MC service user receiving MC service from a partner MC system ..... | 69 | +| 10.1.4.4 | MC service user receives updated MC service user profile data from the network ..... | 71 | +| 10.1.4.5 | MC service user updates MC service user profile data to the network ..... | 71 | +| 10.1.4.6 | Updating the pre-selected MC service user profile ..... | 72 | +| 10.1.4.7 | Updating the selected MC service user profile for an MC service ..... | 73 | +| 10.1.5 | MC service group configuration management ..... | 75 | +| 10.1.5.1 | Store group configurations at the group management server ..... | 75 | +| 10.1.5.2 | Retrieve group configurations at the group management client ..... | 75 | +| 10.1.5.3 | Subscription and notification for group configuration data ..... | 76 | +| 10.1.5.4 | Structure of group configuration data ..... | 77 | +| 10.1.5.5 | Dynamic data associated with a group ..... | 77 | +| 10.1.5.6 | Subscription and notification for dynamic data associated with a group ..... | 77 | +| 10.1.5.6.1 | Information flows for subscription and notification for dynamic data associated with a group ..... | 78 | +| 10.1.5.6.1.1 | Subscribe group dynamic data request ..... | 78 | +| 10.1.5.6.1.2 | Subscribe group dynamic data response ..... | 78 | +| 10.1.5.6.1.3 | Notify group dynamic data request ..... | 78 | +| 10.1.5.6.1.4 | Notify group dynamic data response ..... | 78 | +| 10.1.5.6.2 | Procedure for subscription and notification for dynamic data associated with a group ..... | 78 | +| 10.1.6 | MC service UE migration ..... | 79 | +| 10.1.6.1 | MC service UE obtains migration connectivity information of partner MC system ..... | 79 | +| 10.1.6.2 | Signalling plane registration for the MC service UE between the primary and the partner MC systems ..... | 79 | +| 10.1.7 | Functional alias configuration management ..... | 81 | +| 10.1.7.1 | Retrieve functional alias configurations from the functional alias management server ..... | 81 | +| 10.1.7.2 | Subscription and notification for functional alias configuration data ..... | 82 | +| 10.2 | Group management (on-network) ..... | 83 | +| 10.2.1 | General ..... | 83 | +| 10.2.2 | Information flows for group management ..... | 83 | +| 10.2.2.1 | Group creation request ..... | 83 | +| 10.2.2.2 | Group creation response ..... | 84 | + +| | | | +|-----------|---------------------------------------------------------------------------------|-----| +| 10.2.2.3 | Group regroup request (group management client – group management server) ..... | 84 | +| 10.2.2.4 | Group regroup response (group management server – group management client)..... | 84 | +| 10.2.2.5 | Group regroup teardown request ..... | 85 | +| 10.2.2.6 | Group regroup teardown response..... | 85 | +| 10.2.2.7 | Group creation notify ..... | 85 | +| 10.2.2.8 | Group regroup notify ..... | 85 | +| 10.2.2.9 | Group regroup teardown notify ..... | 85 | +| 10.2.2.10 | Group regroup teardown notification ..... | 86 | +| 10.2.2.11 | Group regroup teardown notification response ..... | 86 | +| 10.2.2.12 | Group regroup request (group management server – group management server) ..... | 86 | +| 10.2.2.13 | Group regroup response (group management server – group management server)..... | 86 | +| 10.2.2.14 | Group regroup notification ..... | 86 | +| 10.2.2.15 | Group regroup notification response ..... | 87 | +| 10.2.2.16 | Group information query request..... | 87 | +| 10.2.2.17 | Group information query response ..... | 87 | +| 10.2.2.18 | Group membership update request ..... | 87 | +| 10.2.2.19 | Group membership update response..... | 88 | +| 10.2.2.20 | Group membership notification ..... | 88 | +| 10.2.2.21 | Group deletion request..... | 88 | +| 10.2.2.22 | Group deletion response ..... | 88 | +| 10.2.2.23 | Group deletion notification ..... | 89 | +| 10.2.2.24 | Group information provision request..... | 89 | +| 10.2.2.25 | Group information provision response ..... | 89 | +| 10.2.2.26 | Group information request..... | 89 | +| 10.2.2.27 | Group information response ..... | 90 | +| 10.2.2.28 | Group information subscribe request..... | 90 | +| 10.2.2.29 | Group information subscribe response ..... | 90 | +| 10.2.2.30 | Group information notify request ..... | 90 | +| 10.2.2.31 | Group information notify response..... | 91 | +| 10.2.3 | Group creation ..... | 91 | +| 10.2.4 | Group regrouping ..... | 92 | +| 10.2.4.1 | Temporary group formation - group regrouping within an MC system ..... | 92 | +| 10.2.4.2 | Temporary group formation involving multiple MC systems ..... | 93 | +| 10.2.4.3 | Temporary group tear down involving multiple group host servers ..... | 95 | +| 10.2.4.4 | Group regroup rules ..... | 97 | +| 10.2.5 | Membership and affiliation list query ..... | 97 | +| 10.2.5.1 | General ..... | 97 | +| 10.2.5.2 | Procedure ..... | 97 | +| 10.2.6 | Group membership ..... | 98 | +| 10.2.6.1 | Group membership notification ..... | 98 | +| 10.2.6.2 | Group membership update by authorized user ..... | 98 | +| 10.2.7 | Group configuration for interconnection..... | 99 | +| 10.2.7.1 | Overview..... | 99 | +| 10.2.7.2 | Primary MC system provides group configuration to the partner MC system..... | 100 | +| 10.2.7.3 | Partner MC system requests group configuration from the primary MC system ..... | 101 | +| 10.2.7.4 | Partner MC system subscribes to group configuration..... | 102 | +| 10.2.7.5 | Primary MC system notifies group configuration ..... | 103 | +| 10.2.8 | Group deletion ..... | 104 | +| 10.3 | Pre-established session (on-network)..... | 105 | +| 10.3.1 | General ..... | 105 | +| 10.3.2 | Procedures ..... | 105 | +| 10.3.2.1 | General ..... | 105 | +| 10.3.2.2 | Pre-established session establishment ..... | 105 | +| 10.3.2.3 | Pre-established session modification ..... | 106 | +| 10.3.2.4 | Pre-established session release ..... | 108 | +| 10.4 | Simultaneous session (on-network) ..... | 109 | +| 10.4.1 | General ..... | 109 | +| 10.5 | Use of UE-to-network relay ..... | 109 | +| 10.5.1 | UE-to-network relay service authorization..... | 109 | +| 10.5.2 | UE-to-network relay MC service ..... | 109 | +| 10.6 | General user authentication and authorization for MC services ..... | 109 | +| 10.6.1 | Primary MC system..... | 109 | + +| | | | +|--------------|------------------------------------------------------------------|-----| +| 10.6.2 | Interconnection partner MC system ..... | 110 | +| 10.6.3 | Migration to partner MC system ..... | 110 | +| 10.6.3.1 | General..... | 110 | +| 10.6.3.2 | Information flows for migrated service authorization ..... | 111 | +| 10.6.3.2.1 | Migration service authorization request..... | 111 | +| 10.6.3.2.2 | Migration service authorization response ..... | 111 | +| 10.6.3.3 | Procedure ..... | 111 | +| 10.7 | Use of MBMS transmission..... | 113 | +| 10.7.1 | General ..... | 113 | +| 10.7.2 | Information flows for MBMS transmission ..... | 113 | +| 10.7.2.1 | MBMS bearer announcement..... | 113 | +| 10.7.2.2 | MBMS listening status report..... | 114 | +| 10.7.2.3 | MBMS suspension reporting instruction ..... | 114 | +| 10.7.2.4 | Discover bearer request ..... | 115 | +| 10.7.2.5 | Discover bearer response..... | 115 | +| 10.7.2.6 | Media distribution request..... | 115 | +| 10.7.2.7 | Media distribution request response ..... | 116 | +| 10.7.2.8 | Identify multicast participants request..... | 116 | +| 10.7.2.9 | Remove call from bearer request..... | 116 | +| 10.7.2.10 | Media distribution release..... | 116 | +| 10.7.2.11 | Media broadcasting notification ..... | 116 | +| 10.7.3 | Procedures for MBMS usage..... | 116 | +| 10.7.3.1 | Use of pre-established MBMS bearers ..... | 116 | +| 10.7.3.1.1 | General ..... | 116 | +| 10.7.3.1.2 | Procedure..... | 117 | +| 10.7.3.2 | Use of dynamic MBMS bearer establishment ..... | 118 | +| 10.7.3.3 | Switching from MBMS bearer to unicast bearer..... | 119 | +| 10.7.3.4 | Use of MBMS bearer for application level control signalling..... | 120 | +| 10.7.3.4.1 | Description ..... | 120 | +| 10.7.3.4.2 | Procedure..... | 121 | +| 10.7.3.5 | MBMS bearer announcement over MBMS bearer ..... | 121 | +| 10.7.3.5.1 | Description ..... | 121 | +| 10.7.3.5.2 | Procedure..... | 122 | +| 10.7.3.6 | MBMS bearer quality detection..... | 123 | +| 10.7.3.6.1 | Description ..... | 123 | +| 10.7.3.6.2 | Procedure..... | 123 | +| 10.7.3.7 | Service continuity in MBMS scenarios ..... | 124 | +| 10.7.3.7.1 | General ..... | 124 | +| 10.7.3.7.2 | Service continuity when moving from one MBSFN to another..... | 124 | +| 10.7.3.7.3 | Service continuity with a UE-to-network relay..... | 126 | +| 10.7.3.8 | MBMS suspension notification ..... | 128 | +| 10.7.3.8.1 | Description ..... | 128 | +| 10.7.3.8.2 | Procedure..... | 128 | +| 10.7.3.9 | Multi-server bearer coordination ..... | 129 | +| 10.7.3.9.1 | General ..... | 129 | +| 10.7.3.9.2 | Procedures ..... | 129 | +| 10.7.3.9.2.1 | MBMS bearer coordination independent on broadcasted media..... | 129 | +| 10.7.3.9.2.2 | MBMS bearer coordination within one group call..... | 131 | +| 10.7.3.10 | MBMS bearer event notification ..... | 133 | +| 10.7.3.10.1 | General ..... | 133 | +| 10.7.3.10.2 | Procedure..... | 134 | +| 10.7.3.11 | Use of FEC to protect MBMS transmissions..... | 135 | +| 10.7.3.11.1 | General ..... | 135 | +| 10.7.3.11.2 | FEC encoding by the BM-SC..... | 135 | +| 10.7.3.11.3 | FEC encoding by the MC service server..... | 136 | +| 10.7.3.12 | Header compression over MBMS with ROHC ..... | 137 | +| 10.7.3.12.1 | General ..... | 137 | +| 10.7.3.12.2 | Header compression by the MC service server..... | 137 | +| 10.7.3.12.3 | Header compression by the BM-SC..... | 138 | +| 10.8 | Affiliation and de-affiliation to/from MC service group(s) ..... | 140 | +| 10.8.1 | General ..... | 140 | +| 10.8.2 | Information flows ..... | 140 | + +| | | | +|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-----| +| 10.8.2.1 | MC service group affiliation request ..... | 140 | +| 10.8.2.2 | MC service group affiliation request (MC service server – MC service server) ..... | 140 | +| 10.8.2.3 | MC service group affiliation response ..... | 140 | +| 10.8.2.4 | MC service group affiliation response (MC service server – MC service server) ..... | 141 | +| 10.8.2.5 | Group affiliation status update ..... | 141 | +| 10.8.2.6 | MC service group de-affiliation request ..... | 141 | +| 10.8.2.7 | MC service group de-affiliation request (MC service server – MC service server) ..... | 141 | +| 10.8.2.8 | MC service group de-affiliation response ..... | 142 | +| 10.8.2.9 | MC service group de-affiliation response (MC service server – MC service server) ..... | 142 | +| 10.8.2.10 | Group de-affiliation status update ..... | 142 | +| 10.8.2.11 | MC service group affiliation change request ..... | 142 | +| 10.8.2.12 | MC service group affiliation change response ..... | 143 | +| 10.8.2.13 | MC service group de-affiliation notification ..... | 143 | +| 10.8.3 | Affiliation ..... | 143 | +| 10.8.3.1 | MC service group affiliation procedure ..... | 143 | +| 10.8.3.2 | Affiliation to MC service group(s) defined in partner MC system without topology hiding ..... | 144 | +| 10.8.3.2.1 | Functional description ..... | 144 | +| 10.8.3.2.2 | Procedure ..... | 145 | +| 10.8.3.2a | Affiliation to MC service group(s) defined in partner MC system using topology hiding ..... | 146 | +| 10.8.3.2a.1 | Functional description ..... | 146 | +| 10.8.3.2a.2 | Procedure ..... | 146 | +| 10.8.4 | De-affiliation from MC service group(s) ..... | 148 | +| 10.8.4.1 | General ..... | 148 | +| 10.8.4.2 | MC service group de-affiliation procedure ..... | 148 | +| 10.8.4.3 | De-affiliation from MC service group(s) defined in partner MC service system ..... | 149 | +| 10.8.4.4 | MC server initiated group de-affiliation procedure ..... | 150 | +| 10.8.4.5 | MC server initiated group de-affiliation from group defined in partner MC service system ..... | 151 | +| 10.8.5 | Remote change of affiliation ..... | 153 | +| 10.8.5.1 | Remote change of affiliation for groups defined in primary MC system ..... | 153 | +| 10.8.5.1.1 | Authorized user remotely changes another MC service user's affiliated MC service group(s) –<br>mandatory mode ..... | 153 | +| 10.8.5.1.2 | Authorized user remotely changes another MC service user's affiliated MC service group(s) –<br>negotiated mode ..... | 154 | +| 10.8.5.2 | Remote change of affiliation for groups defined in partner MC system ..... | 156 | +| 10.8.5.2.1 | Authorized user remotely changes another MC service user's affiliated MC service group(s)<br>defined in partner MC system – mandatory mode ..... | 156 | +| 10.9 | Location management (on-network) ..... | 157 | +| 10.9.1 | General ..... | 157 | +| 10.9.2 | Information flows for location information ..... | 158 | +| 10.9.2.1 | Location reporting configuration ..... | 158 | +| 10.9.2.2 | Location information report ..... | 158 | +| 10.9.2.3 | Location information request ..... | 158 | +| 10.9.2.4 | Location reporting trigger ..... | 158 | +| 10.9.2.5 | Location information subscription request ..... | 159 | +| 10.9.2.6 | Location information subscription response ..... | 159 | +| 10.9.2.7 | Location information notification ..... | 159 | +| 10.9.3 | Procedure ..... | 160 | +| 10.9.3.1 | Event-triggered location reporting procedure ..... | 160 | +| 10.9.3.2 | On-demand location reporting procedure ..... | 161 | +| 10.9.3.3 | Client-triggered location reporting procedure ..... | 161 | +| 10.9.3.4 | Location reporting cancel procedure ..... | 162 | +| 10.9.3.5 | Location information subscription procedure ..... | 163 | +| 10.9.3.6 | Usage of location information procedure ..... | 163 | +| 10.9.3.6.1 | Event-trigger location information notification procedure ..... | 163 | +| 10.9.3.6.2 | On-demand usage of location information procedure ..... | 164 | +| 10.10 | Emergency Alert ..... | 164 | +| 10.10.1 | On-network emergency alert ..... | 164 | +| 10.10.1.1 | General ..... | 164 | +| 10.10.1.2 | MC service emergency alert ..... | 165 | +| 10.10.1.2.1 | MC service emergency alert initiation ..... | 165 | +| 10.10.1.2.2 | MC service emergency alert cancel ..... | 167 | +| 10.10.2 | Off-network emergency alert ..... | 169 | + +| | | | +|-------------|--------------------------------------------------------------------------------------------------------|-----| +| 10.10.2.1 | General..... | 169 | +| 10.10.2.2 | MC service emergency alert ..... | 169 | +| 10.10.2.2.1 | Emergency alert initiation ..... | 169 | +| 10.10.2.2.2 | Emergency alert cancel ..... | 170 | +| 10.11 | MC service resource management (on-network) ..... | 171 | +| 10.11.1 | General ..... | 171 | +| 10.11.2 | Request for unicast resources at session establishment..... | 172 | +| 10.11.3 | Request for modification of unicast resources ..... | 173 | +| 10.11.4 | Management of multicast media bearers ..... | 174 | +| 10.11.5 | Request for resources with shared priority ..... | 174 | +| 10.11.5.1 | General..... | 174 | +| 10.11.5.2 | Procedure ..... | 174 | +| 10.11.6 | Request for media resources from MC service server..... | 175 | +| 10.11.6.1 | General..... | 175 | +| 10.11.6.2 | Procedure ..... | 176 | +| 10.12 | Priority Management..... | 177 | +| 10.12.1 | General ..... | 177 | +| 10.12.2 | Information flows ..... | 177 | +| 10.12.2.1 | MC priority request..... | 177 | +| 10.12.3 | Procedure for priority coordination between multiple MC service servers ..... | 177 | +| 10.13 | Functional alias management (on-network)..... | 179 | +| 10.13.1 | General ..... | 179 | +| 10.13.2 | Information flows for functional alias management..... | 179 | +| 10.13.2.1 | Functional alias information query request ..... | 179 | +| 10.13.2.2 | Functional alias information query response ..... | 179 | +| 10.13.2.3 | Functional alias activation request..... | 179 | +| 10.13.2.4 | Functional alias activation response ..... | 180 | +| 10.13.2.5 | Functional alias de-activation request..... | 180 | +| 10.13.2.6 | Functional alias de-activation response ..... | 180 | +| 10.13.2.7 | Functional alias status notification ..... | 180 | +| 10.13.2.8 | Functional alias take over request..... | 181 | +| 10.13.2.9 | Functional alias take over response ..... | 181 | +| 10.13.2.10 | Functional alias revoke notification..... | 181 | +| 10.13.3 | Authorised MC service user retrieves active functional alias(es) for a certain MC service ..... | 181 | +| 10.13.4 | MC service user activates functional alias(es) within an MC system ..... | 182 | +| 10.13.5 | MC service user de-activates functional alias(es) within an MC system..... | 183 | +| 10.13.6 | Authorised MC service user takes over functional alias(es) within an MC system ..... | 184 | +| 10.14 | Generic procedures for interconnection ..... | 185 | +| 10.14.1 | General ..... | 185 | +| 10.14.2 | Generic call procedure with topology hiding ..... | 185 | +| 10.14.2.1 | General..... | 185 | +| 10.14.2.2 | Procedure for calls with topology hiding..... | 185 | +| 10.14.3 | Generic call procedure for enforcement of local MC service group configuration..... | 187 | +| 10.14.3.1 | General..... | 187 | +| 10.14.3.2 | MC service group call initiated in the partner MC system of the MC service group ..... | 187 | +| 10.14.3.3 | MC service group call request received from the primary MC system of the MC service group ..... | 188 | +| 10.14.4 | Generic call procedure for media replication in participating MC system in MC service group calls .... | 189 | +| 10.14.4.1 | General..... | 189 | +| 10.14.4.2 | Media replication in the partner MC system of the MC service group ..... | 189 | + +**Annex A (normative): Configuration data for MC services..... 191** + +A.1 General..... 191 + +A.2 MC service UE configuration data..... 192 + +A.3 MC service user profile configuration data..... 192 + +A.4 Group configuration data ..... 192 + +A.5 MC service configuration data..... 196 + +A.6 Initial MC service UE configuration data ..... 196 + +**Annex B (informative): Service continuity for MC service..... 197** + +B.1 Service continuity between on-network MC service and UE-to-network relay MC service..... 197 + +Annex C (informative): Change history..... 201 + +--- + +## Foreword + +This Technical Specification has been produced by the 3<sup>rd</sup> 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. + +# 1 Scope + +This document specifies the common functional architecture, procedures and information flows needed to support mission critical services including the common services core architecture. + +The corresponding service requirements are defined in 3GPP TS 22.179 [2], 3GPP TS 22.280 [3], 3GPP TS 22.281 [4] and 3GPP TS 22.282 [5]. + +The present document is applicable primarily to mission critical services using E-UTRAN access based on the EPC architecture defined in 3GPP TS 23.401 [17]. Certain MC service functions such as dispatch and administrative functions could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access. + +The common functional architecture to support mission critical services can be used for public safety applications and also for general commercial applications e.g. utility companies and railways. + +# 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1". +- [3] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1". +- [4] 3GPP TS 22.281: "Mission Critical Video services". +- [5] 3GPP TS 22.282: "Mission Critical Data services". +- [6] 3GPP TS 23.002: "Network Architecture". +- [7] 3GPP TS 23.179: "Functional architecture and information flows to support mission critical communication services; Stage 2" +- [8] 3GPP TS 23.203: "Policy and charging control architecture". +- [9] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [10] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2". +- [11] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description". +- [12] 3GPP TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2". +- [13] 3GPP TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2". +- [14] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2". +- [15] 3GPP TS 23.335: "User Data Convergence (UDC); Technical realization and information flows". + +- [16] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2". +- [17] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [18] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE\_LTE); Stage 2". +- [19] 3GPP TS 29.283: "Diameter Data Management Applications". +- [20] Void +- [21] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [22] IETF RFC 5245 (April 2010): "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols". +- [23] GSMA PRD IR.92 v10.0: "IMS Profile for Voice and SMS". +- [24] GSMA PRD IR.88 v15.0: "LTE and EPC Roaming Guidelines". +- [25] 3GPP TS 33.180: "Security of the mission critical service". +- [26] IETF RFC 6733 (October 2012): "Diameter Base Protocol". +- [27] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point". +- [28] 3GPP TS 22.011: "Service accessibility". + +--- + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Active MC service user profile:** The MC service user profile that is currently used by an MC service client of an MC service user while receiving MC service. + +**Interconnection:** A means of communication between MC systems whereby MC service users obtaining MC service from one MC system can communicate with MC service users who are obtaining MC service from one or more other MC systems. + +**Interconnection group:** An MC service group that is configured to allow inclusion of MC service group members who are MC service users from partner MC system(s). + +**Location:** The current physical location of the MC service UE. + +**MC gateway server:** A server providing topology hiding for MC service interconnection with a partner MC system, where that partner MC system is in a different trust domain. + +**MC service:** A generic name for any one of the three mission critical services: either MCPTT, or MCVideo, or MCData. + +**MC service affiliated group member:** An MC service user who has indicated an interest in a particular MC service group and has been accepted to participate in MC service group communication for that MC service group. + +**MC service client:** A generic name for the client application function of a specific MC service. MC service client could be replaced by MCPTT client, or MCVideo client, or MCData client depending on the context. + +**MC service group:** A defined set of MC service users with associated communication dispositions (e.g. media restrictions, default priority and commencement directions) configured for the use with one or more MC services. + +**MC service group affiliation:** A mechanism by which an MC service user's MC service(s) communication interest in one or more MC service groups is determined. + +**MC service group call:** A mechanism by which an MC service user can make a one-to-many MC service(s) transmission to other users that are members of MC service group(s). + +**MC service group de-affiliation:** A mechanism by which an MC service user's MC service(s) communication interest in one or more MC service groups is removed. + +**MC service group home system:** The MC system where the MC service group is defined. + +**MC service group host MC service server:** The MC service server within an MC system which provides centralised support for a particular MC service of an MC service group defined in a MC service group home system. + +**MC service group member:** An MC service user, whose MC service ID is listed in a particular MC service group. + +**MC service ID:** A generic name for the user ID of a mission critical user within a specific MC service. MC service ID could be replaced by MCPTT ID, or MCVideo ID, or MCData ID depending on the context. + +**MC service server:** A generic name for the server application function of a specific MC service. MC service server could be replaced by MCPTT server, MCVideo server, or MCData server depending on the context. + +**MC service user:** An authorized user, who can use an MC service UE to participate in one or more MC services. + +**MC service user profile:** The set of information associated to an MC service user that allows that user to employ one or more MC services in a given role and from a given MC service UE. + +**MC service UE:** A UE that can be used to participate in one or more MC services. + +**MC system:** The collection of applications, services, and enabling capabilities required to provide a single mission critical service or multiple mission critical services to one or more mission critical organizations. + +**MC user:** A user, identified by an MC ID, who, after authorization, obtains mission critical service(s). + +**Migration:** A means for an MC Service user to obtain MC service directly from a partner MC system. + +**Partner MC system:** Allied MC system that provides MC services to an MC service user based on the MC service user profiles that are defined in the primary MC system of that MC service user. + +**Pre-selected MC service user profile:** The MC service user profile that is to be selected as the active MC service user profile through configuration, and applicable for an authenticated MC service user upon MC service authorization. + +**Primary MC system:** MC system where the MC service user profiles of an MC service user are defined. + +**Selected MC service user profile:** The MC service user profile that is to be selected as the active MC service user profile for an MC service upon request by an MC service user. + +**Serving MC service server:** The MC service server which is providing MC service to an MC service client. + +NOTE 1: There is one serving MC service server for each MC service, which can be the primary MC service server of the MC service user of the MC service client, or can be a partner MC service server to which the MC service user has migrated. + +**Serving MC system:** The MC system which is providing MC service to an MC user. + +NOTE 2: The MC system can be the primary MC system of the MC service user, or can be a partner MC system to which the MC service user has migrated. + +For the purposes of the present document, the following terms given in 3GPP TS 22.280 [3] apply + +**Mission Critical** +**Mission Critical Applications** +**Mission Critical Organization** +**Mission Critical Service** +**Functional alias** + +For the purposes of the present document, the following terms given in 3GPP TS 22.179 [2] apply + +### Multi-talker control + +## 3.2 Symbols + +For the purposes of the present document, the symbols given in 3GPP TS 22.280 [3] apply + +Nc6 + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|----------|-----------------------------------------------------------------| +| APN | Access Point Name | +| BM-SC | Broadcast Multicast Service Centre | +| CSC | Common Services Core | +| CSCF | Call Server Control Function | +| DPF | Direct Provisioning Function | +| E-UTRAN | Evolved Universal Terrestrial Radio Access Network | +| EPC | Evolved Packet Core | +| EPS | Evolved Packet System | +| FEC | Forward Error Correction | +| GBR | Guaranteed Bit Rate | +| GCS AS | Group Communication Service Application Server | +| GCSE_LTE | Group Communication Service Enabler over LTE | +| GRUU | Globally Routable User agent URI | +| HSS | Home Subscriber Server | +| HTTP | Hyper Text Transfer Protocol | +| I-CSCF | Interrogating CSCF | +| IARI | IMS Application Reference Identifier | +| ICE | Interactive Connectivity Establishment | +| ICSI | IMS Communication Service Identifier | +| IM CN | IP Multimedia Core Network | +| IMPI | IP Multimedia Private Identity | +| IMPU | IP Multimedia PUblic identity | +| IMS | IP Multimedia Subsystem | +| MBMS | Multimedia Broadcast and Multicast Service | +| MBSFN | Multimedia Broadcast multicast service Single Frequency Network | +| MC | Mission Critical | +| MC ID | Mission Critical user identity | +| MCPTT AS | MCPTT Application Server | +| MCPTT ID | MCPTT user identity | +| NAT | Network Address Translation | +| P-CSCF | Proxy CSCF | +| PLMN | Public Land Mobile Network | +| ProSe | Proximity-based Services | +| PSI | Public Service Identity | +| QoS | Quality of Service | +| RAN | Radio Access Network | +| RF | Radio Frequency | +| ROHC | RObust Header Compression | +| S-CSCF | Serving CSCF | +| SIP | Session Initiated Protocol | +| SSL | Secure Sockets Layer | +| TLS | Transport Layer Security | +| TMGI | Temporary Mobile Group Identity | +| UDC | User Data Convergence | +| UDR | User Data Repository | +| USB | Universal Serial Bus | + +| | | +|------|-----------------------------| +| URI | Uniform Resource Identifier | +| WLAN | Wireless Local Area Network | + +For the purposes of the present document, the abbreviations given in 3GPP TS 22.280 [3] apply + +MCDData +MCPTT +MCVideo + +## 4 Introduction + +A common functional architecture to support MC services (i.e., MCPTT defined in 3GPP TS 23.379 [16], MCVideo defined in 3GPP TS 23.281 [12], MCData defined in 3GPP TS 23.282 [13]) including common application plane and signalling plane entities is specified in this document. + +Each MC service supports several types of communications amongst the users (e.g. group call, private call). There are several common functions and entities (e.g. group, configuration, identity) which are used by the MC services. + +The common functional architecture to support MC services utilises aspects of the IMS architecture defined in 3GPP TS 23.228 [9], the Proximity-based Services (ProSe) architecture defined in 3GPP TS 23.303 [14], the Group Communication System Enablers for LTE (GCSE LTE) architecture defined in 3GPP TS 23.468 [18] and the PS-PS access transfer procedures defined in 3GPP TS 23.237 [10]. + +The MC service UE primarily obtains access to a MC service via E-UTRAN, using the EPS architecture defined in 3GPP TS 23.401 [17]. Certain MC service functions such as dispatch and administrative functions can be supported using either MC service UEs in E-UTRAN or using MC service UEs via non-3GPP access networks. External applications usage of MC services can be enabled via E-UTRAN or non-3GPP access networks. + +NOTE: Dispatch consoles and devices used by MC service administrators are considered MC service UEs in the common functional architecture to support MC services. + +## 5 Assumptions and architectural requirements + +### 5.1 Assumptions + +#### 5.1.1 Service continuity + +Service continuity shall be supported between on-network MC services and UE-to-network relay MC services. The following 3GPP TS 23.237 [9] procedures are needed: + +- Originating sessions that use only PS media flow(s) as defined in subclause 6.2.1.3. +- Terminations sessions that use only PS media flow(s) as defined in subclause 6.2.2.3. +- Remote Leg Update as defined in subclause 6.3.1.5. +- PS-PS Access Transfer with full media transfer as defined in subclause 6.2.2.1. + +The MC service UE, prior to going out of E-UTRAN coverage, should attempt to make use of a ProSe UE-to-network relay to support service continuity. + +#### 5.1.2 Trust domain + +For an MC system, the trust domain consists of one or more MC service functions that are administered by the same or different service providers (e.g. MC service provider, PLMN operator) that have an agreement to share sensitive information. + +For the MC system architecture, the following rules are implied for functions in different trust domains: + +- A public user identity shall not identify an MC service user in a different trust domain (see subclause 8.3.1); + +- A public service identity shall not identify an MC service group ID in a different trust domain (see subclause 8.3.2); +- A SIP database shall not pass responses to a registrar or registrar finder in a different trust domain (see subclause 7.4.3.2.1); and +- An HTTP proxy shall not pass requests or responses to another HTTP proxy, an HTTP server or an HTTP client in a different trust domain (see subclause 7.4.3.3.2). + +## 5.2 Architectural requirements + +### 5.2.1 General architectural requirements + +General MC service architectural requirements include: + +- To develop economies of scale, it will be useful if PLMN operators can reuse the MC service architecture for non-public safety customers that require similar functionality. These PLMN operators may want to integrate many components of the MC service solution with their existing network architecture. + +Hence a functional decomposition of MC service architecture into distinct logical functions is required. + +- The MC service architecture should enable an application plane and signalling control plane split for the provisioning of the MC service. +- To enable parts of the MC service architecture to be shared for other applications, the architecture should enable the group management functions (e.g. admission control; linking of groups;) to be implemented on a separate node from the main application functions of the MC service (e.g. "call" setup/termination; allocation of **TMGI** to UE; floor control;). +- There is a need to promptly form (and release) groups of users that span multiple public safety network administrations. To enable this, the MC service architecture should provide the relevant interfaces between public safety networks. + +### 5.2.2 Roaming requirements + +The MC applications can provide MC services to users in various PLMNs. Roaming is supported using **EPC-level roaming** or IMS-level roaming. + +For **EPC-level roaming**, in order to prioritise for network selection PLMNs that allow migration to partner MC systems, the MC service UE's User Preferred PLMN Selector list (see 3GPP TS 22.011 [28]) may be configured with a list of PLMNs that can be used to migrate to one or more partner MC systems (see subclause 5.2.9.2). + +### 5.2.3 **UE-to-network relay** MC service requirements + +To support the requirement that a public safety **ProSe UE-to-network relay** shall be able to restrict the relayed group communication on a per group basis, the MC service should be able to provide a means for an MC service administrator to configure a **ProSe UE-to-network relay** with a list of allowed MC service groups. For each allowed MC service group, a unique associated relay service code should be allocated and it may be provided to the relay UE from MC service server or DPF. + +NOTE: According to the PLMN operator's configuration, one relay service code can map to one or multiple MC service group(s). + +### 5.2.4 MC service user profile requirements + +The MC service user profile shall: + +- be provisioned subject to the user authentication by the identity management server; +- be available at configuration management server; +- be available at MC service servers with the corresponding user profile information; +- be associated with an MC service user; and + +- contain an index to uniquely distinguish the MC service user profile from other MC service user profiles associated to the same MC service user. + +For the set of MC service user profiles associated to a single MC service user, one of the MC service user profiles shall be indicated as the pre-selected MC service user profile to the MC service client and the MC service server. + +The MC service user shall be able to: + +- change the pre-selected MC service user profile; and +- change the selected MC service user profile. + +The MC service user profile may be modified at the configuration management server. + +## 5.2.5 MC service group affiliation and MC service group de-affiliation + +The MC system shall support affiliation and de-affiliation to an MC service group for one or more MC services. For affiliation and de-affiliation, the MC service client shall indicate interest in one or more MC services for the MC service group. For a single MC service group configured for multiple MC services, the affiliation and de-affiliation shall be performed as per the MC service selected by the MC service user. For individual MC service group affiliation and MC service group de-affiliation, the requirements are specified in the corresponding MC service TS. + +**Editor's note: The requirement for a combined affiliation to multiple MC services for a single MC service group is FFS.** + +MC service group affiliation can be achieved through the following two methods: + +- a) **Explicit affiliation:** An MC service client indicates interest in one or many MC service groups to the MC service server. This interest may be initiated either by an MC service user using the MC service UE, or by an automatic procedure within the MC service client that indicates that the MC service user is interested in the MC service group at that MC service client. An authorized MC service user may remotely modify another MC service user's affiliation to an MC service group. +- b) **Implicit affiliation:** An MC service user's affiliations to MC service groups are determined through configurations and policies within the MC service and performed by the associated MC service server. + +**NOTE:** MC service group affiliation is not the same as MC service group membership; however, an MC service user is a member of an MC service group prior to becoming an affiliated member of that MC service group. + +The MC service server may refuse a request for affiliation from an MC service user to an MC service group, in which case the MC service user will be unable to take part in the requested MC service associated with that MC service group, and the MC service client should make the MC service user aware that the MC service user is not affiliated to the MC service group for the requested MC service. The MC service server may also de-affiliate an MC service client from an MC service group following a relevant trigger condition. + +MC service group de-affiliation indicates that the MC service user is no longer interested in that MC service group, either at the MC service client, or across all MC service clients depending on MC service group configuration, and therefore is unable to perform any actions that are associated with an affiliated member (e.g. receive media, notifications). MC service group de-affiliation can occur due to either an MC service client's explicit request, or implicitly i.e. changed by the MC service server as the result of another action e.g. the MC service user logging off. + +## 5.2.6 GCS AS requirements for the MC services + +Point to multipoint broadcast offered by the **LTE MBMS** technology is well suited to group communications, which form a major part of the public safety related communications. The MC service on-network architecture, is based in part on 3GPP **TS 23.468** [18] with the MC service server assuming the function of the GCS AS and can be represented (in a simplified diagram) as shown in figure 5.2.6-1: + +![Diagram of MC service on-network architecture showing UE, E-UTRAN, and MC service server (bundled with GCS AS) connected via various interfaces: GC1, Uu, Rx, SGi, MB2-C, and MB2-U. The UE contains an MC service client. The E-UTRAN shows a Unicast path and an MBMS path. The MC service server is connected to the E-UTRAN via the Rx, SGi, MB2-C, and MB2-U interfaces.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +The diagram illustrates the MC service on-network architecture. On the left, a UE (User Equipment) box contains an 'MC service client'. A 'Uu' interface connects the UE to an 'E-UTRAN' box. Inside the 'E-UTRAN' box, there are two paths: a 'Unicast path' (yellow) and an 'MBMS path' (green). The 'Unicast path' connects to an 'MC service server (shown bundled with GCS AS)' box on the right via an 'Rx' interface. The 'MBMS path' connects to the same 'MC service server' box via 'MB2-C' and 'MB2-U' interfaces. A 'GC1' interface is shown between the 'MC service client' and the 'MC service server'. A 'SGi' interface is also shown between the 'E-UTRAN' and the 'MC service server'. + +Diagram of MC service on-network architecture showing UE, E-UTRAN, and MC service server (bundled with GCS AS) connected via various interfaces: GC1, Uu, Rx, SGi, MB2-C, and MB2-U. The UE contains an MC service client. The E-UTRAN shows a Unicast path and an MBMS path. The MC service server is connected to the E-UTRAN via the Rx, SGi, MB2-C, and MB2-U interfaces. + +**Figure 5.2.6-1: MC service on-network architecture showing MBMS** + +The MC service server is shown being bundled with the GCS AS within the same network entity. It is illustrated this way for simplicity of the diagram. + +MC service media content is transmitted via **LTE** bearers, which are communication pipes with one end in the MC service server and the other end in the MC service UE. The uplink bearers are always allocated as unicast, but the downlink bearers can be allocated as unicast or as **MBMS** bearers, or both. + +An **MBMS** bearer (both network and radio part) is uniquely identified via a **TMGI** or via a combination of a **TMGI** and a flow identifier (see 3GPP **TS 23.246** [11]). The MC service server is capable, via the MB2 interface, to request the creation of **MBMS** bearers and associate a unique **TMGI** or a combination of a **TMGI** and a flow identifier (see 3GPP **TS 23.468** [18]). The MC service server may determine the **MBMS** broadcast area based on the cell identities of the affiliated group members received over **GC1**. The MC service server may determine for a user the switching from **MBMS** bearer to unicast bearer based on the information reported over **GC1**. + +## 5.2.7 Bearer management + +### 5.2.7.0 General + +The MC service UE shall use the following **APNs**: + +- an MC services **APN** for the SIP-1 reference point; +- an MC common core services **APN** for the HTTP-1 reference point; and +- an MC identity management service **APN** for the CSC-1 reference point. + +The value of each of these **APNs**: + +- may be the same or may differ; +- may be the same as other non-MC services that have compatible QoS and PDN (see NOTE); and +- shall be made available to the UE either via UE (pre)configuration or via initial UE configuration (see subclause 10.1.1) on a per HPLMN and optionally also a per VPLMN basis. + +NOTE: The **APN** value of "IMS" is a well-known **APN**, whose PDN connection characteristics are defined in GSMA PRD IR.92 [23] and **GSMA PRD IR.88** [24], and which is used in some deployments for operator IMS-based services e.g. Voice over **LTE**. This well-known **APN** can be used for the MC service **APN** if the SIP core belongs to the PLMN operator and both the PLMN operator and MC service provider have agreed which QoS aspects to utilise i.e. either the QoS aspects defined in subclause 5.2.7.2 or the QoS aspects defined in GSMA PRD IR.92 [23] and **GSMA PRD IR.88** [24]. + +The MC service UE may utilise PDN access credentials as specified in 3GPP **TS 23.401** [17] (e.g. **PAP**, **CHAP**) to access the PDNs identified by the MC service **APN**, the MC common core services **APN** and the MC identity management service **APN**. If PDN access credentials are required, then they shall be made available to the MC service UE via initial MC service UE configuration (see subclause 10.1.1) on a per **APN** basis. + +The PDN connection to the **APN**s defined within the present subclause can be of type "IPv4", "IPv6" or "IPv4v6" (see 3GPP **TS 23.401** [17]). If a PDN connection to an **APN** defined within the present subclause is of type "IPv4v6" then the MC service client shall use configuration data to determine whether to use IPv4 or IPv6. + +### 5.2.7.1 **MBMS** bearer management + +When operating in systems that support **MBMS** functionality, the MC service can provide downlink **MBMS** delivery of MC service media. + +When operating in systems that support **MBMS** functionality, the MC service can provide downlink **MBMS** delivery of application level control messages targeted towards multiple MC clients at the same time (e.g. floor idle and floor taken for MCPTT services). + +MC service UEs can receive the traffic delivered via **MBMS**, regardless of whether or not they have any unicast radio bearers available. + +When switching between different downlink bearers, the MC service UE shall preserve the reception context in order to eliminate or reduce to a minimum any interruption of service. + +The MC service shall enable an MC service UE in an ongoing MC service group session that has just entered an area of media delivery via **MBMS** bearers to immediately start receiving the media for that MC service group session via **MBMS**. + +The MC service server shall not map MC service group sessions to **MBMS** bearers that cannot provide the QoS required by the group. + +An MC service UE that uses **MBSFN** transmission should be able to support eight **MBSFN** areas simultaneously on the same RF carrier. + +### 5.2.7.2 **EPS** bearer considerations + +#### 5.2.7.2.1 Considerations for the **EPS** bearer to the MC services PDN + +If the PDN connection established during the initial attach by the MC service UE is to an **APN** other than the MC services **APN**, then prior to user authentication, the MC service UE shall establish another PDN connection to the MC services **APN**. PDN connection establishment can also be caused by a SIP registration request for one or more MC services. + +The **QCI** value of 69 (as specified in 3GPP **TS 23.203** [8]) shall be used for the **EPS** bearer that transports SIP-1 reference point messaging. + +#### 5.2.7.2.2 Considerations for the **EPS** bearer to the MC common core services PDN and MC identity management service PDN + +The **QCI** value 8 (as specified in 3GPP **TS 23.203** [8]) or better shall be used for the **EPS** bearer that transports HTTP-1 reference point messaging. + +## 5.2.8 External applications access to services in a MC system + +The MC system shall allow external applications to gain secure access to MC services by supporting authentication and authorization of external applications. + +*Editor's note: External applications reside outside a MC system and can access a MC system using IP connectivity.* + +*Editor's note: How to enable the external application access to services in an MC system is FFS.* + +*Editor's note: The definition for services and capabilities discovery is FFS.* + +## 5.2.9 Migration + +### 5.2.9.1 General + +MC service interconnection needs to be provided between MC systems that wish to provide migration of their MC service users. + +Migration of MC service users between any two MC systems can be on a bilateral or unilateral basis. + +NOTE: Whether migration is bilateral or unilateral between any two MC systems is left to business agreements between the two MC service providers, and is outside the scope of the present document. + +During migration of an MC service user to a partner MC system, media of the MC service user's calls may need to be routed to the MC service user's primary MC system e.g. for logging purposes. + +### 5.2.9.2 PLMN utilisation + +Migrated MC service users should utilise the HPLMN of the partner MC system to access MC services in the partner MC system, however, utilising the HPLMN of the primary MC system is not precluded. + +NOTE 1: The above recommendation ensures the security policy of the partner MC system is not compromised, the expected **QCI**s are used on the RAN, and ensures service-level delay requirements are consistently met (which are especially at risk when the HPLMN of the primary MC system and HPLMN of the partner MC system are far apart from a geographical point of view). + +NOTE 2: Whether the HPLMN of partner MC systems or the HPLMN of the primary MC system is used to access MC services in partner MC systems is left to business agreements between MC service providers, and is outside the scope of the present document. + +MC service users enabled for migration shall be provisioned with configuration that specifies which PLMNs may be used to migrate to different MC systems. + +If the HPLMN of a partner MC system is different from the HPLMN of the primary MC system (i.e. migrating MC service users roam onto the HPLMN of the partner MC system), then: + +- **EPC-level roaming** (see subclause 5.2.2) is needed between the HPLMN of the primary MC system and HPLMN of the partner MC system; +- the HPLMN of the partner MC system needs to enable local break-out for the **APN**s specified in subclause 5.2.7 that identify the PDNs of the partner MC system; and +- the **EPS** subscriptions of the HPLMN of the primary MC system utilised by the MC service users who are allowed to migrate to the partner MC system need to be provisioned with, and local break-out enabled for, the **APN**s specified in subclause 5.2.7 that identify the PDNs of the partner MC system. + +If the HPLMN of the partner MC system and the HPLMN of the primary MC system are the same (i.e. migrating MC service users continue to use the HPLMN of their primary MC system), then: + +- the **EPS** subscriptions of the HPLMN of the primary MC system utilised by the MC service users who are allowed to migrate to the partner MC system need to be provisioned with the **APN**s specified in subclause 5.2.7 that identify the PDNs of the partner MC system. + +NOTE 3: Provisioning of **APN**s in all of the above includes provisioning of any needed access credentials e.g. **PAP**, **CHAP**. + +### 5.2.9.3 SIP core / IMS utilisation + +Migrated MC service users should utilise the SIP core / IMS of the partner MC system. + +NOTE 1: The above recommendation ensures the security policy of the partner MC system is not compromised and ensures service-level delay requirements are consistently met (which are especially at risk when the SIP core / IMS of the primary MC system and the SIP core / IMS of the partner MC system are far apart from a geographical point of view). + +Where connectivity and security policies allow, the same SIP core / IMS can be utilised to connect to the primary MC system and one or more partner MC systems. + +NOTE 2: Whether the same SIP core / IMS can be utilised to connect to the primary MC system and a partner MC system is left to business agreements between MC service providers, and is outside the scope of the present document. + +For each partner MC system, MC service UEs of MC service users enabled for migration shall be provisioned with: + +- configuration that controls whether the MC service UE shall connect to the SIP core / IMS of the primary MC system or a different SIP core / IMS (i.e. SIP core / IMS of the partner MC system); and +- where a different SIP core / IMS to the primary MC system's SIP core / IMS is to be connected to then the MC service UE shall also be configured with: + - configuration required for the MC service UE to access the SIP core / IMS; and + - credentials required for the MC service UE to register with the SIP core / IMS. + +**Editor's note:** It is FFS how the MC service UE connects to the SIP core / IMS of the partner MC system to access MC services in the partner MC system. + +## 5.2.10 Interconnection + +### 5.2.10.1 General + +MC service interconnection allows a first set of MC service users who are receiving MC service from a first MC system to take part in communications with a second set of MC service users, where this second set of MC service users are receiving MC service from a second MC system, and where the second MC system is in a different trust domain to the first MC system. + +NOTE: Assumptions for trust domains are described in subclause 5.1.2 of the present document. + +### 5.2.10.2 Connectivity + +The MC service clients of the MC service users receiving MC service(s) from a first MC system and using MC service interconnection to take part in communication with MC service users in a second MC system require connectivity to only the identity management server in the second MC system. + +IP connectivity is required between MC systems wishing to interconnect. The IP connectivity is used to carry the signalling and application plane protocols needed to provide MC service. + +NOTE 1: The IP connectivity between interconnecting MC systems needs to provide appropriate performance (e.g. low packet latency) in order to meet MC service user performance requirements for the MC service. + +NOTE 2: If IP connectivity between interconnecting MC systems is carried outside the trust domain of both MC systems, then there will need to be appropriate security measures applied. Such security measures are outside the scope of the present document. + +### 5.2.10.3 Migration + +Interconnection may be used by a migrated MC service user who is receiving service from a partner MC system to take part in communication with MC service users in the primary MC system of that migrated MC service user. + +### 5.2.10.4 Private calls + +Where private calls take place using interconnection between MC service users who are receiving MC service in different MC systems, the MC system providing MC service to the calling MC service user will provide the controlling function for the private call. + +### 5.2.10.5 Group calls + +Where MC service users in a partner MC system of the group home MC system of an MC service group take part in group calls in that group, the group home MC system of the MC service group will provide the controlling function for the group call. + +### 5.2.10.6 Group configuration + +A partner MC system may apply local configuration to an MC service group configuration received from the primary MC system (i.e. the group home MC system). + +### 5.2.10.7 MC system topology hiding + +If an MC system requires internal network topology hiding, then this shall be achieved in the MC system by use of the following: + +- proxies for signalling plane functions; and +- gateway MC service servers for application plane functions. + +--- + +## 6 Involved business relationships + +Based on the information in subclause 5.2.1 and subclause 5.2.2, figure 6-1 shows the business relationships that exist and that are needed to support a single MC service user. + +![Diagram showing business relationships for MC services between MC service user, MC service provider, Mission critical organization, Home PLMN operator, and Visited PLMN operator.](26d664119ad25250780f554633444e54_img.jpg) + +The diagram illustrates the business relationships for MC services among five entities represented in ovals: + +- MC service user** (top right) is connected to **Mission critical organization** (middle right) via a vertical double-headed arrow labeled "MC service user agreement". +- Mission critical organization** (middle right) is connected to **MC service provider** (middle left) via a horizontal double-headed arrow labeled "MC service arrangement". +- MC service provider** (middle left) is connected to **MC service user** (top right) via a diagonal double-headed arrow labeled "MC service user agreement / MC service arrangement". +- MC service provider** (middle left) is connected to **Home PLMN operator** (bottom left) via a vertical double-headed arrow labeled "PLMN operator service arrangement (includes PLMN subscription arrangement)". +- Home PLMN operator** (bottom left) is connected to **Visited PLMN operator** (bottom right) via a horizontal double-headed arrow labeled "PLMN roaming agreement". + +Diagram showing business relationships for MC services between MC service user, MC service provider, Mission critical organization, Home PLMN operator, and Visited PLMN operator. + +**Figure 6-1: Business relationships for MC services** + +The MC service user belongs to a single mission critical organization based on a MC service user agreement between the MC service user and the mission critical organization. The MC service user can have MC service user agreement and MC service arrangement directly with a single MC service provider. + +The mission critical organization and the MC service provider can be part of the same organization, in which case the business relationship between the two is internal to a single organization. The mission critical organization can have MC service arrangements with several MC service providers. In this case, a MC service user of a mission critical organization is always served by only one MC service provider. The MC service provider can have MC service + +arrangements with several mission critical organizations. The MC service provider can have MC service user agreements and MC service arrangements with several MC service users. + +The MC service provider and the home PLMN operator can be part of the same organization, in which case the business relationship between the two is internal to a single organization. + +The home PLMN operator can have PLMN operator service arrangements with multiple MC service providers and the MC service provider can have PLMN operator service arrangements with multiple home PLMN operators. As part of the PLMN operator service arrangement between the MC service provider and the home PLMN operator, PLMN subscription arrangements can be provided which allows the MC service UEs to register with home PLMN operator network. + +The home PLMN operator can have PLMN roaming agreements with multiple visited PLMN operators and the visited PLMN operator can have PLMN roaming agreements with multiple home PLMN operators. + +Where mutual aid operates between MC service providers, figure 6-2 shows the required additional relationship. An MC service user can only affiliate to groups of the partner MC service provider: + +- if such a service provider agreement exists; or +- subject to authorisation for a specific group membership from the partner MC service provider. + +![Diagram showing the relationship between a Primary MC service provider and a Partner MC service provider. Two ovals, one on the left labeled 'Primary MC service provider' and one on the right labeled 'Partner MC service provider', are connected by a double-headed arrow. Above the arrow, the text 'Service provider agreement' is written.](bb3354f497635d15bef873577125c48d_img.jpg) + +``` +graph LR; A((Primary MC service provider)) <--> |Service provider agreement| B((Partner MC service provider)); +``` + +Diagram showing the relationship between a Primary MC service provider and a Partner MC service provider. Two ovals, one on the left labeled 'Primary MC service provider' and one on the right labeled 'Partner MC service provider', are connected by a double-headed arrow. Above the arrow, the text 'Service provider agreement' is written. + +**Figure 6-2: Additional business relationships for mutual aid** + +The primary and partner MC service providers do not need to be served by the same home SIP core operator in order to support mutual communication and mutual aid when interconnection between the SIP cores is available. + +An example of the usage of these business relationships is elaborated for two users, one resident on its primary MC service provider and one providing mutual aid within the same group: + +User A is a user on MC service provider X in group M. The relationships are as follows: + +- a) user A has user configuration established with MC service provider X and forms part of group M; +- b) user A uses a PLMN subscription arrangement with PLMN operator R provided by MC service provider X; and +- c) MC service provider X has a PLMN operator service arrangement with PLMN operator R. + +User B is a user on MC service provider Y and joins group M as part of a mutual aid: + +- a) user B has user configuration established with MC service provider Y and forms part of its own set of groups relating to MC service provider Y; +- b) user B uses a PLMN subscription arrangement with PLMN operator S provided by MC service provider Y; +- c) MC service provider Y has a PLMN operator service arrangement with PLMN operator S; +- d) MC service provider Y has a service provider agreement with MC service provider X that allows user B to participate within group M; and +- e) PLMN operator S has a PLMN roaming agreement with PLMN operator R allowing user B to roam to PLMN operator R. + +NOTE: There is no requirement that the PLMN operator that user B roams to is the same PLMN operator that MC service provider X has a service arrangement with. It does however need to support one or more MC services capabilities, and provides service in the same geographic area as used by MC service provider X. + +## 7 Functional model + +### 7.1 General + +The functional model for the MC services architecture is defined as a series of planes to allow for the breakdown of the architectural description. + +Further, each plane is expected to operate in an independent manner, providing services to the connected planes as and when requested by the connected plane, and requesting services from other planes as required. + +As a consequence of this each plane should manage on its own behalf: + +- use of identities. Each plane is therefore responsible for the privacy of that plane's own identities; and +- security for that plane. This does not preclude a plane requesting security services from another plane, but that is a decision made within the plane, as to whether to use offered security services or mechanisms within the plane itself. + +NOTE: Terminology such as client and server are not meant to imply specific physical implementation of a functional entity. + +### 7.2 Description of the planes + +The following planes are identified: + +- application plane: The application plane provides all of the services (e.g. call control, floor control, video control, data control) required by the user together with the necessary functions to support MC service. It uses the services of the signalling control plane to support those requirements. For example, within the MCPTT service, the application plane also provides for the conferencing of media, and provision of tones and announcements; and +- signalling control plane: The signalling control plane provides the necessary signalling support to establish the association of users involved in an MC service, such as an MCPTT call or other type of MC services. The signalling control plane also offers access to and control of services across MC services. The signalling control plane uses the services of the bearer plane. + +Bearers supporting these planes are defined for LTE within 3GPP TS 23.401 [17]. The resource control that is needed to support these planes is defined within 3GPP TS 23.203 [8]. The application plane also relies on the use of multicast bearers established via procedures defined in 3GPP TS 23.468 [18] and 3GPP TS 23.246 [11]. + +### 7.3 Functional model description + +#### 7.3.1 On-network functional model + +Each MC service can be represented by an application plane functional model. The functional model across MC services may be similar but is described by the individual functional entities and reference points that belong to that MC service. Within the application plane for an MC service there is a common set of functions and reference points. The common set is shared across services. This common set of functions and reference points is known as the common services core. + +Figure 7.3.1-1 shows the functional model for the application plane for an MC system. + +![Functional model for application plane for an MC system diagram showing various servers and clients connected via reference points like MCX-1, CSC-1, CSC-2, etc.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +The diagram illustrates the functional model for the application plane of an MC system. It is organized into three main vertical sections separated by dashed lines, with a vertical bar on the far right labeled 'EPS'. + +- Left Section (Other MC system):** Contains several functional blocks: + - Other MC service server** connected to the central MC service server(s) via reference point **MCX-1**. + - MC gateway server** (two instances) connected to the central MC service server(s) via reference point **MCX-1**. + - MC service user database(s)** connected to the central MC service server(s) via reference point **CSC-3**. + - Other group management server** connected to the central Group management server via reference point **CSC-7**. + - Group management server** connected to the central Group management server via reference point **CSC-16**. + - Configuration management server** connected to the central Configuration management server via reference point **CSC-17**. + - Migration management server** connected to the central Migration management server via reference point **CSC-18**. +- Center Section (Common services core):** Contains the core functional blocks: + - MC service server(s)**: The central hub for MC services. + - Group management server**: Connected to the MC service server(s) via **CSC-3** and to the central Configuration management server via **CSC-5**. + - Configuration management server**: Connected to the MC service server(s) via **CSC-13**. + - Migration management server**: Connected to the MC service server(s) via **CSC-9**. + - Identity management server**: Connected to the MC service server(s) via **CSC-15**. + - Key management server**: Connected to the MC service server(s) via **CSC-15**. + - Location management server**: Connected to the MC service server(s) via **CSC-15**. +- Right Section (MC service UE):** Contains client blocks that interact with the core servers: + - MC service client(s)**: Interacts with the MC service server(s). + - Group management client**: Connected to the central Group management server via **CSC-2**. + - Configuration management client**: Connected to the central Configuration management server via **CSC-4**. + - Identity management client**: Connected to the central Identity management server via **CSC-1**. + - Key management client**: Connected to the central Key management server via **CSC-8**. + - Location management client**: Connected to the central Location management server via **CSC-14**. + +Additional reference points shown include **CSC-10** (between central servers and clients), **CSC-16** (between left and center servers), and **CSC-17** (between left and center servers). + +Functional model for application plane for an MC system diagram showing various servers and clients connected via reference points like MCX-1, CSC-1, CSC-2, etc. + +Figure 7.3.1-1: Functional model for application plane for an MC system + +The common services core functions and reference points shown in figure 7.3.1-1 are shared across each MC service. The description of the functions and reference points specific to an MC service is contained in the corresponding MC service TS. + +In the model shown in figure 7.3.1-1, the following apply: + +- A specific MC service server is an instantiation of a GCS AS in accordance with 3GPP TS 23.468 [18]. +- The functional alias management client is an integrated functional entity of the configuration management client. The functional alias management client is described in subclause 7.4.2.2.12. +- The functional alias management server is an integrated functional entity of the configuration management server. The functional alias management server is described in subclause 7.4.2.2.13. + +Editor's note: Whether the functional alias management client and functional alias management server can be replaced by the configuration management client and configuration management server is FFS. + +Figure 7.3.1-2 shows the functional model for the signalling control plane. + +![Functional model for signalling control plane diagram showing various network components and their interactions.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +The diagram illustrates the functional model for the signalling control plane. It features several interconnected components and reference points: + +- Other MC system:** Contains a **SIP core** and an **HTTP proxy**. + - The **SIP core** connects to the **SIP database** via **SIP-3**. + - The **HTTP proxy** connects to the **HTTP Proxy** via **HTTP-3**. +- SIP database:** Connects to the **MC gateway server** via **AAA-1** and to the **Registrar finder/I-CSCF** via **SIP-2**. +- MC gateway server:** Contains a **SIP AS** and connects to the **MC service server**. +- MC service server:** Contains a **SIP AS**, an **HTTP server**, and an **HTTP client**. + - The **SIP AS** connects to the **Registrar finder/I-CSCF** via **SIP-2**. + - The **HTTP server** connects to the **HTTP Proxy** via **HTTP-2**. + - The **HTTP client** connects to the **HTTP Proxy** via **HTTP-1**. +- SIP core:** A central block containing: + - Registrar finder/I-CSCF** and **Registrar AS selection/S-CSCF** (dashed box). + - Local proxy/P-CSCF** (dashed box). + - Connects to the **SIP database** via **SIP-2**. + - Connects to the **MC service server** via **AAA-2**. + - Connects to the **HTTP Proxy** via **HTTP-2**. + - Connects to the **MC service UE** via **SIP-1** and **Rx**. + - Connects to the **Common services core** via **HTTP-1**. + - Connects to the **Other MC system** via **SIP-3**. +- Common services core:** Contains a **SIP AS**, **HTTP server**, **HTTP client**, and **Diameter proxy**. + - The **SIP AS** connects to the **HTTP Proxy** via **HTTP-2**. + - The **HTTP server** connects to the **HTTP Proxy** via **HTTP-2**. + - The **HTTP client** connects to the **HTTP Proxy** via **HTTP-1**. + - The **Diameter proxy** connects to the **HTTP Proxy** via **HTTP-1**. +- HTTP Proxy:** A central proxy component that receives connections from the **Other MC system** (**HTTP-3**), **MC service server** (**HTTP-1**, **HTTP-2**), **SIP core** (**HTTP-2**), and **Common services core** (**HTTP-1**, **HTTP-2**). It has outgoing connections to the **MC service UE** (**HTTP-1**) and to other external **HTTP Proxy** units (**HTTP-3**). +- MC service UE:** Contains a **Signalling user agent** and an **HTTP client**. + - The **Signalling user agent** connects to the **SIP core** via **SIP-1** and **Rx**. + - The **HTTP client** connects to the **HTTP Proxy** via **HTTP-1**. +- EPS:** A yellow box indicating the interface between the **SIP core** and the **MC service UE**. + +Functional model for signalling control plane diagram showing various network components and their interactions. + +Figure 7.3.1-2: Functional model for signalling control plane + +Figure 7.3.1-3 shows the relationships between the reference points of the application plane of an MC service server and the signalling plane. + +![Diagram showing relationships between reference points of MC service application plane and signalling control planes. It includes various servers (MC service server, Group management server, Migration management server, Configuration management server, Key management server, Location management server) and clients (MC service client, Group management client, Configuration management client, Key management client, Location management client) connected via SIP and HTTP reference points (SIP-1, SIP-2, SIP-3, HTTP-1, HTTP-2, HTTP-3). Red dashed lines indicate specific application plane reference points (CSC-2, CSC-3, CSC-4, CSC-5, CSC-7, CSC-8, CSC-9, CSC-10, CSC-14, CSC-15, CSC-18).](dd5771673aececa53d42ece89218299d_img.jpg) + +Diagram showing relationships between reference points of MC service application plane and signalling control planes. It includes various servers (MC service server, Group management server, Migration management server, Configuration management server, Key management server, Location management server) and clients (MC service client, Group management client, Configuration management client, Key management client, Location management client) connected via SIP and HTTP reference points (SIP-1, SIP-2, SIP-3, HTTP-1, HTTP-2, HTTP-3). Red dashed lines indicate specific application plane reference points (CSC-2, CSC-3, CSC-4, CSC-5, CSC-7, CSC-8, CSC-9, CSC-10, CSC-14, CSC-15, CSC-18). + +**Figure 7.3.1-3: Relationships between reference points of MC service application plane and signalling control planes** + +NOTE 1: Application plane reference point CSC-7 makes use of SIP-2 reference point when the group management servers are connected by a single SIP core. Where they are joined by more than one SIP core, CSC-7 also makes use of the SIP-3 reference point. + +NOTE 2: For simplicity, the HTTP proxy, which provides the interconnection between HTTP-1, HTTP-2 and HTTP-3 reference points, is not shown in figure 7.3.1-3. + +NOTE 3: CSC-5, CSC-9, and CSC-15 make use of SIP-1 and SIP-2 reference points. For simplicity, this mapping relationship is not shown in figure 7.3.1-3. + +## 7.3.2 Off-network functional model + +Figure 7.3.2-1 shows the functional model for off-network operation. + +![Figure 7.3.2-1: Functional model for MC service off-network operation. The diagram shows two User Equipment (UE) blocks, UE1 and UE2, connected by a green line (Media) and a red line (Signalling). Each UE contains a nested structure: an 'MC service client(s)' box at the top, an 'Application plane' box below it containing 'Configuration management client' and 'Group management client' boxes, and a 'Signalling control plane' box at the bottom containing a 'Signalling user agent client' box. A legend at the bottom indicates that the green line represents 'Media' and the red line represents 'Signalling'.](98e54d5540b2efe3e24af3cf936bc4ea_img.jpg) + +Figure 7.3.2-1: Functional model for MC service off-network operation. The diagram shows two User Equipment (UE) blocks, UE1 and UE2, connected by a green line (Media) and a red line (Signalling). Each UE contains a nested structure: an 'MC service client(s)' box at the top, an 'Application plane' box below it containing 'Configuration management client' and 'Group management client' boxes, and a 'Signalling control plane' box at the bottom containing a 'Signalling user agent client' box. A legend at the bottom indicates that the green line represents 'Media' and the red line represents 'Signalling'. + +**Figure 7.3.2-1: Functional model for MC service off-network operation** + +For a specific MC service, the description of off-network operation is contained in the corresponding MC service TS. + +## 7.4 Functional entities description + +### 7.4.1 General + +Each subclause is a description of a functional entity and does not imply a physical entity. + +### 7.4.2 Application plane + +#### 7.4.2.1 General + +Entities within the application plane of an MC system provide application control and media specific functions to support one or more MC services. + +For each MC service, the functional entities description is contained in the corresponding MC service TS. + +#### 7.4.2.2 Common services core + +##### 7.4.2.2.1 Configuration management client + +The configuration management client functional entity acts as the application user agent for configuration related transactions. The configuration management client interacts with the configuration management server and provides and receives configuration data. + +The configuration management client functional entity is supported by the signalling user agent and HTTP client functional entities of the signalling control plane. + +The configuration management client provides the functional alias management client functionality as described in subclause 7.4.2.2.12. + +#### 7.4.2.2.2 Configuration management server + +The configuration management server is a functional entity used to configure one or more MC service applications with non-group management MC service related information and configure data on the configuration management client. The configuration management server manages MC service configuration supported within the MC service provider. + +The configuration management server functional entity is supported by the SIP AS and HTTP server functional entities of the signalling control plane. + +The configuration management server provides the functional alias management server functionality as described in subclause 7.4.2.2.13. + +#### 7.4.2.2.3 Group management client + +The group management client functional entity acts as the application user agent for management of groups. A MC system maintains groups corresponding to one or more mission critical organizations. The group management client interacts with the group management server. + +The group management client functional entity is supported by the signalling user agent and HTTP client functional entities of the signalling control plane. + +#### 7.4.2.2.4 Group management server + +The group management server functional entity provides for management of groups supported within the MC service provider. + +The group management server functional entity is supported by the SIP AS and HTTP server functional entities of the signalling control plane. + +All the group management clients supporting users belonging to a single group are required to use the same group management server for that group. A group management client supporting a user involved in multiple groups can have relationships with multiple group management servers. + +The group management server manages media policy information for use by the UE for media processing. + +The group management server manages group call policy information for use by the UE for both on-network and off-network group call control. + +#### 7.4.2.2.5 Identity management client + +This functional entity acts as the application user agent for MC ID transactions. It interacts with the identity management server. + +#### 7.4.2.2.6 Identity management server + +The identity management server is a functional entity that is capable of authenticating the MC ID. It contains the knowledge and means to do authentication by verifying the credentials supplied by the user. + +The identity management server functional entity may reside in the same domain as the user's MC system. + +#### 7.4.2.2.7 Key management client + +This functional entity acts as the application user agent for key management functions. It interacts with the key management server. + +The functionality of the key management client is specified in 3GPP TS 33.180 [25]. + +#### 7.4.2.2.8 Key management server + +The key management server is a functional entity that stores and provides security related information (e.g. encryption keys) to the key management client, group management server and MC service server(s) to achieve the security goals of confidentiality and integrity of media and signalling. + +The functionality of the key management server is specified in 3GPP TS 33.180 [25]. + +#### 7.4.2.2.9 Location management client + +This functional entity acts as the application user agent for location management functions. It interacts with the location management server. + +#### 7.4.2.2.10 Location management server + +The location management server is a functional entity that receives and stores user location information, and provides user location information to the MC service server. The location management server may also acquire location information provided by PLMN operator. + +NOTE: The reference point and procedures to acquire location information from the PLMN operator are out of scope of the present document. + +#### 7.4.2.2.11 Migration management server + +The migration management server is used in migration from the SIP core of the primary MC system to the SIP core of the partner MC system. In the SIP core of the primary MC system, the migration management server provides configured SIP identities to be used by a particular MC service UE in order to migrate to one or more SIP cores belonging to partner MC systems. In the SIP core of a partner MC system, the migration management server provides a point of authority for binding SIP identities of the SIP core of partner MC system and SIP identities of the SIP core for primary MC system. + +The migration management server is used during configuration of an MC service UE for MC service user migration (see subclause 10.1.6.1), and during SIP registration of an MC service UE's SIP user agent when migrating to the SIP core of a partner MC system (see subclause 10.6.2). + +A single set or multiple sets of SIP identities of the SIP core of the primary MC system for an MC service UE that is enabled for migration shall be configured in the primary MC system's migration management server. + +NOTE 1: Different sets of SIP identities of the SIP core of the primary MC system provided to different partner MC system migration management servers enable migration of a single MC service UE on a per partner MC system basis. + +EXAMPLE: An MC service UE has SIP identities 1 of the SIP core of primary MC system for migrating to the SIP core of partner MC system 1, and has SIP identities 2 of the SIP core of the primary MC system for migrating to the SIP core of partner MC system 2. MC service UE's primary MC system decides to withdraw migration to partner MC system 1 by disabling primary SIP identities 1 of the SIP core of primary MC system, however, since primary MC system SIP identities 2 are still enabled, the MC service UE can still migrate to the SIP core of partner MC system 2. + +A unique set of partner MC system SIP identities for all possible inbound migrated MC service UEs shall be configured in the partner MC system's migration management server. + +NOTE 2: The migration management server could be part of the SIP database. + +NOTE 3: When the SIP core is located in the PLMN operator domain the migration management server will also be located in the PLMN operator domain. When the SIP core is in the MC service provider domain the migration management server will be located in the MC service provider domain. + +The migration management server functional entity is supported by the Diameter proxy functional entity of the signalling control plane. + +#### 7.4.2.2.12 Functional alias management client + +The functional alias management client functional entity acts as the application user agent for management of functional aliases. The functional alias management client interacts with the functional alias management server. + +The functional management client functional entity is supported by the signalling user agent and by the HTTP client functional entities of the signalling control plane. + +#### 7.4.2.2.13 Functional alias management server + +The functional alias management server functional entity provides the configuration management of functional alias(es). + +The functional alias management server functional entity is supported by the SIP AS and by the HTTP server functional entities of the signalling control plane. + +#### 7.4.2.3 MC service + +##### 7.4.2.3.1 MC service client + +The MC service client functional entity acts as the user agent for all MC service transactions. For a specific MC service, the detailed description of functions of the MC service client is contained in the corresponding MC service TS. + +##### 7.4.2.3.2 MC service server + +The MC service server functional entity provides centralised support for MC services. + +The MC service server functional entity represents a specific instantiation of the GCS AS described in 3GPP **TS 23.468** [18] to control multicast and unicast operations for group communications. For a specific MC service, the detailed description of the GCS AS role assumed by the MC service server is contained in the corresponding MC service TS. + +The MC service server performs the functional alias controlling role for functional alias management including functional alias activation, deactivation and take over. For a single functional alias, only one MC service server is specified as the functional alias controlling role. The detailed description of the functional alias controlling role assumed by the MCPTT server is contained in 3GPP TS 23.379 [16]. + +NOTE: Functional alias feature only applies to MCPTT in the present document. + +The MC service server functional entity is supported by the SIP AS, HTTP client and HTTP server functional entities of the signalling control plane. + +##### 7.4.2.3.3 MC service user database + +This functional entity contains information of the MC service user profile associated with an MC service ID that is held by the MC service provider at the application plane. The MC service user profile is determined by the mission critical organization, the MC service provider, and potentially the MC service user. + +Each MC service shall have a corresponding MC service user database i.e. MCPTT user database as defined in 3GPP TS 23.379 [16], MCVideo user database as defined in 3GPP TS 23.281 [12] and MCData user database as defined in 3GPP TS 23.282 [13]. These MC service user databases can be co-located. + +##### 7.4.2.3.4 MC gateway server + +The MC gateway server provides support for interconnection between a primary MC system and a partner MC system in a different trust domain whilst providing topology hiding. It acts as a proxy for one or more MC service servers in the partner MC system without needing to expose the MC service servers in the primary MC system outside the trusted domain of the primary MC system. It may be a role of an MC service server described in subclause 7.4.2.3.2 of the present document. + +The MC gateway server is responsible for relaying signalling control messages and media between MC service servers in the interconnected MC systems. + +### 7.4.3 Signalling control plane + +#### 7.4.3.1 SIP entities + +##### 7.4.3.1.1 Signalling user agent + +This functional entity acts as the SIP user agent (both client and server) for all SIP transactions. + +#### 7.4.3.1.2 SIP AS + +The SIP AS functional entity supports the following functions on behalf of the MC service: + +- influencing and impacting the SIP session; and +- supporting event subscription and event notification. + +NOTE: In the IM CN subsystem, this is provided by the Application Server as defined in 3GPP TS 23.002 [6]. + +#### 7.4.3.1.3 SIP core + +##### 7.4.3.1.3.1 General + +The SIP core contains a number of sub-entities responsible for registration, service selection and routing in the signalling control plane. + +The SIP core shall be either: + +1. compliant with 3GPP TS 23.228 [9], i.e. the SIP core is a 3GPP IP multimedia core network subsystem; or +2. a SIP core, which internally need not comply with the architecture of 3GPP TS 23.228 [9], but with the reference points that are defined in subclause 7.5.3 (if exposed), compliant to the reference points defined in 3GPP TS 23.002 [6]. + +The data related to the functions of the SIP core, e.g. for data for application service selection, the identity of the serving registrar or authentication related information may be provided by the PLMN operator responsible for the bearer plane. In this case, the SIP database that is the source of the data may be part of the HSS. Alternatively, this data may be provided by the MC service provider. In this case, the source of the data may be the MC service provider's SIP database. + +##### 7.4.3.1.3.2 Local inbound / outbound proxy + +The local inbound / outbound proxy functional entity acts as both an inbound proxy and an outbound proxy for all SIP transactions. This functional entity can provide the following functions: + +- NAT traversal; +- Resource control; +- Route/forward requests and responses to the user agents; +- SIP signalling security; and +- Depending on the PLMN operator policy, discovery and address resolution, including E.164 numbers. + +NOTE: In the IM CN subsystem, this functional entity is provided by the P-CSCF as defined in 3GPP TS 23.228 [9]. + +##### 7.4.3.1.3.3 Registrar finder + +The registrar finder functional entity is responsible for: + +- a) Identifying the serving registrar / application service selection functional entity. The serving registrar / application service selection functional entity is identified using information provided either by the PLMN operator's own SIP database or the MC service provider's SIP database, and optionally using the PLMN operator's internal information e.g. network topology, registrar availability. + - 1) Registrar finder and registrar in the MC service provider domain: registrar finder in the MC service provider's domain uses the information from the MC service provider's SIP database to identify the serving registrar in the MC service provider domain. + - 2) Registrar finder and registrar in the PLMN operator domain: registrar finder uses information from PLMN operator's SIP database to identify the serving registrar in the PLMN operator domain. + +- 3) Registrar finder in PLMN operator domain and registrar in MC service provider domain: registrar finder uses information from the MC service provider's SIP database to identify the serving registrar in the MC service provider domain. + +NOTE 1: The need for the registrar finder is deployment specific e.g. a deployment that has only one registrar does not need the registrar finder and the related SIP database information. + +- b) Providing discovery and address resolution, including E.164 numbers. + +NOTE 2: In the IM CN subsystem, this is provided by the I-CSCF as defined in 3GPP TS 23.228 [9]. + +#### 7.4.3.1.3.4 Registrar / application service selection + +The registrar / application service selection functional entity provides the following functions: + +- Registrar function (with integral provision of a location server) and also acts as an inbound proxy (with access to the integral location server), and outbound proxy for all SIP transactions where application service selection is required. It registers the user and maintains the association of the location and identity of the user in a location service. It provides notifications of the registration states. +- Supports authentication for identities provided within SIP signalling. Both the registrar (with integral location server) and authentication functions are supported by access either to the public network's own SIP database or the MC service provider's SIP database. +- Can provide the application service selection for all SIP transactions, possibly based on application service selection information stored by either the public network's own SIP database or the MC service provider's SIP database. +- Performs SIP signalling security. + +NOTE: In the IM CN subsystem, this is provided by the S-CSCF as defined in 3GPP TS 23.228 [9]. + +#### 7.4.3.1.4 Diameter proxy + +This functional entity acts as a proxy agent for Diameter messaging as specified in IETF RFC 6733 [26]. + +The Diameter proxy, when used on the AAA-2 interface, is collocated with the migration management server. + +Other instances of the Diameter proxy may also be present in the SIP core / IMS. + +NOTE: The number of instances of the Diameter proxy is deployment specific. + +### 7.4.3.2 SIP database + +#### 7.4.3.2.1 General + +The SIP database contains information concerning the SIP subscriptions and corresponding identity and authentication information required by the SIP core, and such information as application service selection. + +In deployment scenarios where the PLMN operator provides the SIP core, this database is provided by the HSS. + +In deployment scenarios where the MC service provider provides the SIP core, the SIP database may be provided by the MC service provider. + +Access to the data residing in the SIP database is restricted to the SIP core entities that are specifically serving the subscriber/user whose data are stored, i.e. registrars and registrar finders can access SIP databases only when they are part of the same trust domain for the data being provided. + +NOTE: The SIP database can be in a different network than the registrar finder since the trust domain for the criteria for registrar selection can be different than the trust domain for the signalling plane user identities. + +The SIP database is responsible for storing the following user related information: + +- signalling plane user identities: Numbering and addressing information; +- signalling plane security information: SIP core access control information for authentication and authorization; + +- MC service UE Location information at inter-system level: the SIP database supports the user registration, and stores inter-system location information, etc.; and +- signalling plane subscription profile (including initial filter criteria). + +The SIP database also generates signalling plane security information for mutual authentication, communication integrity check and ciphering. + +Based on this information, the SIP database is also responsible to support the call control and session management entities of the SIP core. + +The SIP database consists of the following functionalities: + +- support for control functions of the SIP core such as the Registrar and Registrar finder. This is needed to enable subscriber usage of the SIP core services. This functionality is independent of the access network used to access the SIP core; and +- authentication functionality required by the SIP core to authenticate the MC service UE. + +#### 7.4.3.2.2 SIP database logical functions + +The SIP database provides the following logical functions: + +- a) mobility management; + - provides the UE mobility through the SIP core. +- b) registrar assignment support; + - provides to the registrar finder the required capabilities for MC services based on MC service provider requirements on a per-user basis, (e.g. whether a particular registrar within the PLMN operator's network (e.g. a registrar reserved for MC service use or a registrar in a secure location) or a registrar within the MC service provider network is assigned. +- c) call and/or session establishment support; + - provides the call and/or session establishment procedures in the SIP core. For terminating traffic, it provides information on which registrar currently hosts the user. +- d) user security information generation; + - provides generation of user authentication, integrity and ciphering data for the SIP core. +- e) signalling plane security support; + - provides authentication procedures to access MC services by storing the generated data for authentication, integrity and ciphering at the signalling plane and by providing these data to the appropriate registrar. +- f) user identification handling; + - provides the appropriate relations among all the identifiers uniquely determining the signalling plane identities in the SIP core e.g. IMS public identities. +- g) access authorisation; and + - provides authorisation of the user for mobile access when requested by the registrar e.g. by checking that the user is allowed to roam to that visited network. +- h) service authorisation support. + - provides basic authorisation for terminating call/session establishment and service invocation. The SIP database may update the registrar with filter criteria to trigger the MC service server(s). + +### 7.4.3.3 HTTP entities + +#### 7.4.3.3.1 HTTP client + +This functional entity acts as the client for all hypertext transactions. + +#### 7.4.3.3.2 HTTP proxy + +This functional entity acts as a proxy for hypertext transactions between the HTTP client and one or more HTTP servers. The HTTP proxy terminates a TLS session on HTTP-1 with the HTTP client of the MC service UE allowing the HTTP client to establish a single TLS session for hypertext transactions with multiple HTTP servers that are reachable by the HTTP proxy. + +The HTTP proxy terminates the HTTP-3 reference point that lies between different HTTP proxies. It may provide a topology hiding function from HTTP entities outside the trust domain of the MC system. + +The HTTP proxy is not used as part of CSC-1 interface. CSC-1 is a direct HTTP interface between the IdM client in the UE and the IdM server as specified in 3GPP TS 33.180 [25]. + +According to 3GPP TS 33.180 [25], either an HTTP proxy or a direct HTTP interface is used between the key management server and the key management client in the UE for CSC-8. + +The HTTP proxy shall be in the same trust domain as the HTTP clients and HTTP servers that are located within a MC service provider's network. There can be multiple instances of an HTTP proxy e.g. one per trust domain. + +NOTE: The number of instances of the HTTP proxy is deployment specific. + +#### 7.4.3.3.3 HTTP server + +This functional entity acts as the HTTP server for all hypertext transactions. + +## 7.5 Reference points + +### 7.5.1 General reference point principle + +The protocols on any reference point that is exposed for MC service interoperability with other SIP core or other IMS entities in other systems shall be compatible with the protocols defined for the corresponding reference point defined in 3GPP TS 23.002 [6]. + +### 7.5.2 Application plane + +#### 7.5.2.1 General + +The reference points for the application plane of an MC service are described in the following subclauses. + +#### 7.5.2.2 Reference point CSC-1 (between the identity management client and the identity management server) + +The CSC-1 reference point, which exists between the identity management client and the identity management server, provides for the authentication of the common services core to the MC service client and subsequent authentication of the user to the common services core on behalf of applications within the application plane. + +CSC-1 is specified in 3GPP TS 33.180 [25]. + +#### 7.5.2.3 Reference point CSC-2 (between the group management client and the group management server for configuration while UE is on-network) + +The CSC-2 reference point, which exists between the group management client and the group management server, is used for MC service signalling for MC service data management of the MC service. + +The CSC-2 reference point supports: + +- Configuration of group related data at the group management client by the group management server; and + +- Configuration of group related data at the group management server by the group management client. + +The CSC-2 reference point shall use the HTTP-1 and HTTP-2 reference points for transport and routing of non-subscription/notification related signalling. The CSC-2 reference point shall use SIP-1 and SIP-2 reference points for transport and routing of subscription/notification related signalling. + +#### 7.5.2.4 Reference point CSC-3 (between the MC service server and the group management server) + +The CSC-3 reference point, which exists between the MC service server and the group management server, provides for the MC service server to obtain group information corresponding to the MC service. The CSC-3 reference point shall use HTTP-1 and HTTP-2 reference points for transport and routing of non-subscription/notification related signalling. The CSC-3 reference point shall use SIP-2 reference point for transport and routing of subscription/notification related signalling. + +#### 7.5.2.5 Reference point CSC-4 (between the configuration management client and the configuration management server for configuration while UE is on-network) + +The CSC-4 reference point, which exists between the configuration management client and the configuration management server, provides the configuration information required for MC services while the MC service client is on-network. + +The CSC-4 reference point supports: + +- configuration of the MC service UE by the MC service; and +- configuration of the MC service application with the MC service related information that is not part of group management (e.g. policy information) by the MC service UE. + +The CSC-4 reference point shall use the HTTP-1 and HTTP-2 reference points for transport and routing of non-subscription/notification related signalling. The CSC-4 reference point shall use SIP-1 and SIP-2 reference points for transport and routing of subscription/notification related signalling. + +#### 7.5.2.6 Reference point CSC-5 (between the MC service server and the configuration management server) + +The CSC-5 reference point, which exists between the MC service server and the configuration management server, provides for the MC service server to obtain non-group MC service related information (e.g. policy information). The CSC-5 reference point shall use HTTP-1 reference point and HTTP-2 reference point for transport and routing of non-subscription/notification related signalling. The CSC-5 reference point shall use SIP-2 reference point for transport and routing of subscription/notification related signalling. + +#### 7.5.2.7 Reference point CSC-7 (between the group management servers) + +The CSC-7 reference point, which exists between group management servers, allows group management servers to handle group management related signalling in multiple MC systems environment. The CSC-7 reference point shall use the HTTP-1, HTTP-2 and HTTP-3 reference points for transport and routing of non-subscription/notification related signalling. The CSC-7 reference point shall use SIP-2 and SIP-3 reference points for transport and routing of subscription/notification related signalling. + +#### 7.5.2.8 Reference point CSC-8 (between the key management server and the key management client) + +The CSC-8 reference point, which exists between the key management server and the key management client, provides a means for the key management server to provide security related information (e.g. encryption keys) to the key management client. + +The CSC-8 reference point shall use the HTTP-1 and HTTP-2 reference points for transport and routing of security related information to the key management client. + +CSC-8 is specified in 3GPP TS 33.180 [25]. + +#### **7.5.2.9 Reference point CSC-9 (between the key management server and the MC service server)** + +The CSC-9 reference point, which exists between the key management server and the MC service server, provides a means for the key management server to provide security related information (e.g. encryption keys) to the MC service server. + +The CSC-9 reference point shall use the HTTP-1 and HTTP-2 reference points for transport and routing of security related information to the MC service server. + +CSC-9 is specified in 3GPP TS 33.180 [25]. + +#### **7.5.2.10 Reference point CSC-10 (between the key management server and the group management server)** + +The CSC-10 reference point, which exists between the key management server and the group management server, provides a means for the key management server to provide security related information (e.g. encryption keys) to the group management server. + +The CSC-10 reference point shall use the HTTP-1 and HTTP-2 reference points and may use the HTTP-3 reference point for transport and routing of security related information to the group management server. + +CSC-10 is specified in 3GPP TS 33.180 [25]. + +#### **7.5.2.11 Reference point CSC-11 (between the configuration management client and the configuration management server for configuration while UE is off-network)** + +The CSC-11 reference point, which exists between the configuration management client and the configuration management server, provides the configuration information required for MC services while the MC service client is off-network. + +The CSC-11 reference point is the same as CSC-4 reference point except that CSC-11 does not support subscription/notification and therefore does not require the use of SIP-1 and SIP-2 reference points. + +#### **7.5.2.12 Reference point CSC-12 (between the group management client and the group management server for configuration while UE is off-network)** + +The CSC-12 reference point, which exists between the group management client and the group management server, is used for MC service application signalling for data management of the MC service. + +The CSC-12 reference point is the same as CSC-2 reference point except that CSC-12 does not support subscription/notification and therefore does not require the use of SIP-1 and SIP-2 reference points. + +#### **7.5.2.13 Reference point CSC-13 (between the configuration management server and the MC service user database)** + +The CSC-13 reference point, which exists between the MC service user database and the configuration management server, is used for: + +- the configuration management server to store the user profile data in the specific MC service user database; and +- the configuration management server to obtain the user profile from the specific MC service user database for further configuration in the MC service UE. + +#### **7.5.2.14 Reference point CSC-14 (between the location management client and the location management server)** + +The CSC-14 reference point, which exists between the location management client and the location management server, is used by the location management server to receive location information report from location management client. + +The CSC-14 reference point uses SIP-1 and SIP-2 reference points for transport and routing of subscription/notification related signalling. The CSC-14 reference point uses the HTTP-1 and HTTP-2 reference points for transport and routing of non-subscription/notification related signalling. + +#### 7.5.2.15 Reference point CSC-15 (between the location management server and the MC service server) + +The CSC-15 reference point, which exists between the location management server and the MC service server, is used by the MC service server to request and receive location information from location management server. + +The CSC-15 reference point uses SIP-1 and SIP-2 reference points for transport and routing of subscription/notification related signalling. The CSC-15 reference point uses the HTTP-1 and HTTP-2 reference points for transport and routing of non-subscription/notification related signalling. + +#### 7.5.2.16 Reference point CSC-16 (between group management servers in different MC systems) + +The CSC-16 reference point, which exists between two group management servers in different MC systems in different security domains, is used by the group management servers to share group configuration information for MC service groups that can take part in interconnected MC service group calls. + +Editor's note: It is FFS whether CSC-16 functionality can be subsumed into CSC-7. + +#### 7.5.2.17 Reference point CSC-17 (between configuration management servers in different MC systems) + +The CSC-17 reference point, which exists between configuration management servers in different MC systems in different security domains, is used by the configuration management servers to share user configuration information for MC service users who are permitted to migrate between the MC systems. + +#### 7.5.2.18 Reference point CSC-18 (between migration management servers in different MC systems) + +The CSC-18 reference point, which exists between migration management servers in different MC systems, is used by migration management servers to request and provide SIP authentication information for MC service UEs that are permitted to migrate between the different MC systems. + +#### 7.5.2.19 Reference point MCX-1 (between MC service servers) + +The MCX-1 reference point is defined between MC service servers, between MC service servers and MC gateway servers and between MC gateway servers. The MC service servers and MC gateway servers may be located within one MC system or in separate MC systems. Furthermore, the MC service servers may be of the same type or different types. + +This MCX-1 reference point is used by MC service servers' coordination procedures (e.g. priority coordination). This reference point is not part of the common service core functionality. + +Editor's note: The relation between MCX-1 and MCPTT-3 (see reference 3GPP TS 23.379 [16]), MCVideo-3 (see reference 3GPP TS 23.281 [4]) and MCData-3 (see reference 3GPP TS 23.282 [5]) is FFS. + +### 7.5.3 Signalling control plane + +#### 7.5.3.1 General + +The reference points for the SIP and HTTP signalling are described in the following subclauses. + +#### 7.5.3.2 Reference point SIP-1 (between the signalling user agent and the SIP core) + +The SIP-1 reference point, which exists between the signalling user agent and the SIP core for establishing a session in support of MC service, shall use the Gm reference point as defined in 3GPP TS 23.002 [6] (with necessary enhancements to support MC service requirements and profiled to meet the minimum requirements for support of MC service). The SIP-1 reference point fulfils the requirements of the GCI reference point specified in 3GPP TS 23.468 [18]. The SIP-1 reference point is used for: + +- SIP registration; +- authentication and security to the service layer; +- event subscription and event notification; +- communication of the **TMGI** for multicast operation; +- overload control; +- session management; and +- media negotiation. + +### 7.5.3.3 Reference point SIP-2 (between the SIP core and the SIP AS) + +The SIP-2 reference point, which exists between the SIP core and the SIP AS for establishing a session in support of MC service, shall use the ISC and Ma reference points as defined in 3GPP TS 23.002 [6]. The SIP-2 reference point is used for: + +- notification to the MC service server(s) of SIP registration by the MC service UE; +- authentication and security to the service layer; +- event subscription and event notification; +- communication of the **TMGI** for multicast operation; +- session management; and +- media negotiation. + +### 7.5.3.4 Reference point SIP-3 (between the SIP core and SIP core) + +The SIP-3 reference point, which exists between one SIP core and another SIP core for establishing a session in support of MC service, shall use the Mm and ICi reference points as defined in 3GPP TS 23.002 [6]. The SIP-3 reference point is used for: + +- event subscription and event notification; +- session management; and +- media negotiation. + +**Editor's note:** it is FFS whether changes are needed to SIP-3 when used between servers in different trust domains. + +### 7.5.3.5 Reference point HTTP-1 (between the HTTP client and the HTTP proxy) + +The HTTP-1 reference point exists between the HTTP client and the HTTP proxy. Between the MC service UE and the HTTP proxy, the HTTP-1 reference point shall use the Ut reference point as defined in 3GPP TS 23.002 [6] (with necessary enhancements to support specific MC service requirements). The HTTP-1 reference point is based on HTTP (which may be secured using e.g. SSL, TLS). + +### 7.5.3.6 Reference point HTTP-2 (between the HTTP proxy and the HTTP server) + +The HTTP-2 reference point, which exists between the HTTP proxy and the HTTP server, is based on HTTP (which may be secured using e.g. SSL, TLS). + +### 7.5.3.7 Reference point HTTP-3 (between the HTTP proxy and HTTP proxy) + +The HTTP-3 reference point, which exists between the HTTP proxy and another HTTP proxy in a different network, is based on HTTP (which may be secured using e.g. SSL, TLS). + +**Editor's note:** it is FFS whether changes are needed to HTTP-3 when used between servers in different trust domains. + +### 7.5.3.8 Reference point AAA-1 (between the SIP database and the SIP core) + +The AAA-1 reference point, which exists between the SIP database and the SIP core, is used by the SIP core to retrieve signalling plane data from the SIP database. The AAA-1 reference point utilises the Cx reference point as defined in 3GPP TS 23.002 [6]. + +In some deployment scenarios the registrar and SIP database are located in the MC service provider's network while the registrar finder is in the PLMN operator's network and the AAA-1 reference point is an inter-network interface. + +### 7.5.3.9 Reference point AAA-2 (between the SIP core and Diameter proxy) + +The AAA-2 reference point, which exists between the SIP core / IMS and Diameter proxy for SIP registration during migration, shall use the Cx reference point as defined in 3GPP TS 23.002 [6]. The AAA-2 reference point is used for: + +- authentication and security to the service layer for migration; + +--- + +## 8 Identities + +### 8.1 Application plane + +#### 8.1.1 Mission Critical user identity (MC ID) + +The mission critical user identity is also known as the MC ID. The MC ID is the identity that an MC service user presents to the identity management server during a user authentication transaction. In general, since identity management is a common service it uses an identity which is linked to a set of credentials (e.g. biometrics, secureID, username/password) that may not necessarily be tied to a single mission critical service. The MC ID and the MC service ID may be the same. The MC ID uniquely identifies the MC service user to the identity management server. The MC ID is used by the identity management server to provide the identity management client a means for mission critical service authentication. + +NOTE: The specific security and authentication mechanisms required in order to use the MC user identity is specified in 3GPP TS 33.180 [25]. + +#### 8.1.2 MC service user identity (MC service ID) + +The MC service user identity is also known as the MC service ID. The MC service ID is a globally unique identifier within the MC service that represents the MC service user. The MC service ID identifies an MC service user. The MC service ID may also identify one or more MC service user profiles for the user at the application layer. + +There are attributes associated with the MC service ID configured in the MC service that relate to the human user of the MC service. Typically this information identifies the MC service user, by name or role, may also identify a user's organization or agency, and may also identify MC service user's service subscription to one or more MC services. Such attributes associated with an MC service ID can be used by the MC service server to make authorization decisions about the MC service granted to the user. For example, if the MC service user is subscribed to MCPTT service, an attribute that identifies a user's role as an incident commander could automatically be used by the MCPTT service to grant the user additional administrative rights over the creation of groups, or access to privileged talk groups. + +The MC service ID shall be a URI. The MC service ID uniquely identifies an MC service user in an MC system. The MC service ID indicates the MC system where the MC service ID is defined. + +When required by the MC service provider, the MC service ID is hidden from the signalling control plane. + +A default or temporary MC service ID may be used where a user is not yet associated with a device. When a user would like to use one or more MC services but has not been authenticated by the identity management server, a default or temporary MC service ID and a corresponding MC service user profile may be used. + +#### 8.1.3 MC service group identity (MC service group ID) + +##### 8.1.3.1 General + +The MC service group identity is also known as the MC service group ID. The MC service group ID is a globally unique identifier within the MC service that represents a set of MC service users. The set of MC service users may + +belong to the same or different MC systems. The MC system for each user (within the group) is identified by each user's respective MC service ID. + +The MC service group ID identifies an MC service group in an MC system. It indicates the MC system where the MC service group is defined. It indicates the MC service server within the MC system where the group is defined as described in subclause 8.3.2. + +The MC service group ID is used as follows: + +- a) For identifying a set of identities of its group members; and +- b) By the MC service client to address the MC service group. + +The MC service group ID shall be a URI. + +When required by the MC service provider, the MC service group ID is hidden from the signalling control plane. + +In 3GPP TS 23.379 [16], the MCPTT group ID is an MC service group ID. + +In 3GPP TS 23.281 [12], the MCVideogroup ID is an MC service group ID. + +In 3GPP TS 23.282 [13], the MCData group ID is an MC service group ID. + +### 8.1.3.2 MC service group ID management (off-network operation) + +In off-network operation, an MC service group ID is used for identifying the MC service group while off-network. The MC service group ID should be resolved to the **ProSe** Group IP multicast address and **ProSe** Layer-2 Group ID for the group communication. The MC service UE is able to make one or more MC service communications (as per the group configuration) with other member UEs whose users are of the same MC service group ID over **ProSe** direct communications based on **ProSe** Layer-2 Group ID and **ProSe** Group IP multicast address, and utilising IPv4 or IPv6 as indicated by policy, as described in 3GPP TS 23.303 [14]. + +Figure 8.1.3.2-1 illustrates how the MC service group ID, **ProSe** Group IP multicast address and the **ProSe** Layer-2 Group ID are mapped to each other. **ProSe** Group IP multicast address and **ProSe** Layer-2 Group ID are pre-configured in accordance with the MC service group ID. Thus, they are pre-defined and associated. This mapping information should be provisioned through UICC in the UE or through **ProSe** function as specified in 3GPP TS 23.303 [14], or be delivered from an application server. Mapping information is provisioned from group management server for online configuration, and provisioned from configuration management server for offline configuration. + +NOTE: To define the retrieval mechanism of the off-network information (**ProSe** Group IP multicast address and **ProSe** Layer-2 Group ID) from **ProSe** function to group management server is out of scope of the present document. + +![Diagram showing the mapping of MC service group ID to Group IP multicast address and Layer-2 Group ID. A box contains three items: 'MC service group ID (e.g., 'police')', 'Group IP multicast address (e.g., 239.255.255.1)', and 'Layer-2 Group ID (e.g., L2_POLICE)'. Arrows from a 'Pre-defined and associated' label point to each of these three items.](92271d74f67effbd92583eb3fba71514_img.jpg) + +The diagram illustrates the relationship between three identifiers for an MC service group. A large rectangle is divided into three horizontal sections. The top section contains "MC service group ID (e.g., 'police')". The middle section contains "Group IP multicast address (e.g., 239.255.255.1)". The bottom section contains "Layer-2 Group ID (e.g., L2\_POLICE)". To the left of the rectangle, the text "Pre-defined and associated" has three arrows pointing from it to each of the three sections, indicating that all three identifiers are pre-defined and associated with each other. + +Diagram showing the mapping of MC service group ID to Group IP multicast address and Layer-2 Group ID. A box contains three items: 'MC service group ID (e.g., 'police')', 'Group IP multicast address (e.g., 239.255.255.1)', and 'Layer-2 Group ID (e.g., L2\_POLICE)'. Arrows from a 'Pre-defined and associated' label point to each of these three items. + +Figure 8.1.3.2-1: MC service group ID management in off-network operation + +### 8.1.4 MC system identity (MC system ID) + +The MC system ID is a globally unique identifier representing an MC system. The MC system ID shall be a URI. + +## 8.2 SIP signalling control plane + +The SIP signalling control plane depends upon the use of both a private user identity and one or more public user identities. + +When the signalling user agent sends registration requests to the registrar / application service selection, the private user identity is used to find corresponding credentials for authentication of the signalling user agent by the registrar / application service selection. This private user identity fulfils the same functions as the IMPI defined in 3GPP TS 23.228 [9]. + +All SIP signalling messages sent by a signalling user agent to an MC service server via a SIP core use a public user identity as the identifier to enable signalling messages to be routed through the SIP system. The public user identity fulfils the same functions as IMPU defined in 3GPP TS 23.228 [9]. + +NOTE 1: The relationship between the private user identity and public user identity is defined in 3GPP TS 23.228 [9]. + +The public user identities do not necessarily contain any application-level attributes of MC services (e.g., MCPTT ID). Any association of the public user identities with such attributes occurs at the application layer only. + +When the SIP core and the MC service are part of the same trust domain, public user identities may be provided by the MC service provider or the PLMN operator. When the SIP core and the MC service are part of the different trust domains, public user identities may be provided by the PLMN operator. + +NOTE 2: The MC service provider can have an agreement with the PLMN operator to manage a pool of public user identities. + +The SIP core may generate public GRUUs and temporary GRUUs in order to uniquely identify MC service UEs when a user logging on from multiple devices or multiple users sharing the same device is supported per 3GPP TS 23.228 [9]. + +Public service identity is used as the identifier to route SIP signalling for the MC system. The public service identity fulfils the same functions as PSI defined in 3GPP TS 23.228 [9]. + +## 8.3 Relationship between identities in different planes + +### 8.3.1 Relationship between MC service ID and public user identity + +The following relationships exist between the MC service ID(s) and the public user identity(ies): + +- An MC service ID may be mapped to one or more public user identities (e.g. multiple UEs, shared UE, multiple MC services); +- A public user identity may be mapped to one or more MC service IDs (e.g. **UE-to-network relay**); and +- An MC service ID may be mapped to one or more public GRUUs (e.g. a user logging on from multiple UEs, multiple users sharing the same UE). + +The MC service server manages the mapping between MC service IDs and public user identities. + +The MC service server manages the mapping between MC service IDs and public GRUUs. + +Temporary GRUUs are mapped to public GRUUs by the SIP core. + +The public user identity does not necessarily identify the MC service user at the SIP signalling control plane. When the MC service provider and the home PLMN operator are part of the same trust domain, the public user identity in the SIP signalling control plane may also identify the MC service user at the application plane. + +### 8.3.2 Relationship between MC service group ID and public service identity + +Each MC service group ID shall be mapped to a public service identity for the MC service server where the group is defined. The MC service server manages the mapping between MC service group IDs and public service identities. + +When the MC service provider and the home PLMN operator are part of the same trust domain, the public service identity in the SIP signalling control plane may also identify the MC service group ID at the application plane. + +![Diagram showing three examples of MC service group ID to Public service identity to MC service server mappings.](c1278da91cbcabe32628e589ebc47418_img.jpg) + +The diagram illustrates three distinct mapping scenarios between MC service group IDs, Public service identities (PSIs), and MC service servers: + +- Top scenario:** Two MC service group IDs (ID 1 and ID 2) are both mapped to a single Public service identity (PSI 1), which is then connected to MC service server 1. +- Middle scenario:** Two MC service group IDs (ID 1 and ID 2) are mapped to two different PSIs (PSI 1 and PSI 2), which are both connected to the same MC service server 1. +- Bottom scenario:** One MC service group ID (ID 1) is mapped to three different PSIs (PSI 1, PSI 2, and PSI 3), which are connected to three separate MC service servers (server 1, server 2, and server 3). + +Diagram showing three examples of MC service group ID to Public service identity to MC service server mappings. + +Figure 8.3.2-1: The relationship of MC service group IDs, PSIs and MC service servers + +## 9 Application of functional model to deployments + +### 9.1 General + +This clause describes the application of the functional model, described in clause 7, to on-network and off-network deployments. It also describes deployment scenarios that highlight some of the possible variations in the way that the functional model can be applied in different situations. + +### 9.2 Architecture model and deployment scenarios for on-network operations + +#### 9.2.1 On-network architectural model + +##### 9.2.1.1 On-network architectural model diagram + +Figure 9.2.1.1-1 below is the on-network architectural model for the MC system solution, where the MC system provides one or more MC services via a single PLMN. + +![Diagram of the on-network architectural model for a UE-to-network relay MC service. The diagram shows a vertical stack of layers: Application services layer, SIP core, EPS, UE 1, and UE 2. Media flows (green lines) are shown between the Application services layer and UE 2, passing through the EPS and UE 1. Signalling flows (red lines) are shown between the Application services layer and the SIP core, and between the SIP core and UE 2, passing through the EPS and UE 1. A dashed blue line separates UE 1 and UE 2. A legend indicates that green lines represent Media and red lines represent Signalling. The text 'UE-to-network relay MC service' is located to the right of the diagram.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +Diagram of the on-network architectural model for a UE-to-network relay MC service. The diagram shows a vertical stack of layers: Application services layer, SIP core, EPS, UE 1, and UE 2. Media flows (green lines) are shown between the Application services layer and UE 2, passing through the EPS and UE 1. Signalling flows (red lines) are shown between the Application services layer and the SIP core, and between the SIP core and UE 2, passing through the EPS and UE 1. A dashed blue line separates UE 1 and UE 2. A legend indicates that green lines represent Media and red lines represent Signalling. The text 'UE-to-network relay MC service' is located to the right of the diagram. + +**Figure 9.2.1.1-1: On-network architectural model** + +## 9.2.1.2 Application services layer + +### 9.2.1.2.1 Overview + +The application services layer includes application functions of one or more MC services and any required supporting functions grouped into common services core. + +### 9.2.1.2.2 Common services core + +Common services core is composed of the following functional entities: + +- for common services, a configuration management server as described in subclause 7.4.2.2.2, a group management server as described in subclause 7.4.2.2.4, an identity management server as described in subclause 7.4.2.2.6 and a key management server as described in subclause 7.4.2.2.8; and +- for signalling control, an HTTP proxy as described in subclause 7.4.3.3.2 and an HTTP server as described in subclause 7.4.3.3.3. + +### 9.2.1.2.3 MC services + +MC services are composed of the following functional entities: + +- an MC service server as described in subclause 7.4.2.3.2 with relevant application functions of the corresponding MC service defined in the corresponding MC service TS. + +## 9.2.1.3 SIP core + +The SIP core provides rendezvous (contact address binding and URI resolution) and service control (application service selection) functions. It is composed of the following functional entities: + +- for signalling control, a local inbound / outbound proxy as described in subclause 7.4.3.1.3.2, a registrar finder as described in subclause 7.4.3.1.3.3 and a registrar / application service selection entity as described in subclause 7.4.3.1.3.4. + +#### 9.2.1.4 EPS + +The EPS provides point-to-point and point-to-multipoint bearer services with QoS. + +#### 9.2.1.5 UE 1 + +UE 1 is: + +- an MC service UE in on-network mode supporting bearer services and application(s) related to one or more MC service; +- an MC service UE that acts as ProSe UE-to-network relay; or +- both of the above. + +When acting as an MC service UE in on-network mode supporting bearer services and application(s) related to one or more MC services, UE 1 is composed of the same functional entities as for UE 2, as described in subclause 9.2.1.6, without the support of ProSe capabilities. + +#### 9.2.1.6 UE 2 + +UE 2 is a device using ProSe UE-to-network relay, and supporting application(s) related to one or more MC services. It is composed of the following functional entities: + +- for common services, a group management client as described in subclause 7.4.2.2.3, a configuration management client as described in subclause 7.4.2.2.1, an identity management client as described in subclause 7.4.2.2.5 and a key management client as described in subclause 7.4.2.2.7; +- for MC services, MC service clients as described in subclause 7.4.2.3.1 with relevant application functions of the corresponding MC service defined in the corresponding MC service TS; and +- for signalling control, a signalling user agent as described in subclause 7.4.3.1.1 and an HTTP client as described in subclause 7.4.3.3.1. + +### 9.2.2 Deployment scenarios + +#### 9.2.2.1 Administration of MC service, SIP core and EPS + +##### 9.2.2.1.1 General + +This subclause describes five different deployment scenarios in which different administration of MC service, SIP core and EPS are described, together with the sensitivities of identities and other forms of signalling in those scenarios. + +In each of these scenarios, the owner of the devices at each plane may be different from the organisation that administers these devices. For example, the MC service provider may own some RAN components within the EPS even when the EPS is administered by the PLMN operator, and the MC service UE may be owned by an organisation that is independent from PLMN and MC service providers. + +##### 9.2.2.1.2 Common administration of all planes + +In this scenario, all planes (application services layer, SIP core and EPS) are administered by the same party. This is illustrated in figure 9.2.2.1.2-1 below. + +![Diagram of common administration of all services by one operator](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +This diagram illustrates a network architecture where all services are administered by a single operator. It features a vertical stack of components: an 'Application services layer' at the top, connected to a 'SIP core', which is connected to an 'EPS' (highlighted in yellow). Below the EPS is a box containing a 'SIP client' and an 'MC service client'. At the bottom is the 'MC service UE'. A dashed box encloses all these components, with the text 'All services administered by same operator' to its right. + +Diagram of common administration of all services by one operator + +**Figure 9.2.2.1.2-1: Common administration of all services by one operator** + +Although the identities in each plane are separate according to clause 8, there is no particular sensitivity of identities and other information at the application plane, and these may be exposed to the SIP core and the EPS. + +All authorisation and authentication mechanisms at each plane, i.e. the application services layer, SIP core and EPS, shall be separate, but there may be no need for any restrictions in how these are stored and managed; for example the same entity could provide services to each of the application services layer, SIP core and EPS. + +### 9.2.2.1.3 MC service provider separate from SIP core and EPS + +In this scenario, as illustrated in figure 9.2.2.1.3-1, the MC service provider is separate and independent from the PLMN operator, and the MC service is administered independently of the EPS and SIP core. The PLMN operator administers the EPS and the SIP core. + +![Diagram of MC service provider administering MC service separately from SIP core and EPS](b4f6d3668f7e851eaff07ccf26001623_img.jpg) + +This diagram shows a network architecture where the MC service provider is separate from the PLMN operator. The components are stacked vertically: 'Application services layer', 'SIP core', 'EPS' (highlighted in yellow), a box containing 'SIP client' and 'MC service client', and 'MC service UE'. The diagram is divided into three horizontal sections by dashed lines. The top section, containing the application services layer, is labeled 'MC service provider administered'. The middle section, containing the SIP core and EPS, is labeled 'PLMN operator administered'. The bottom section, containing the SIP client, MC service client, and MC service UE, is also labeled 'MC service provider administered'. + +Diagram of MC service provider administering MC service separately from SIP core and EPS + +**Figure 9.2.2.1.3-1: MC service provider administers MC service separately from SIP core and EPS** + +The MC service provider may require that all application services layer identities and other sensitive information are hidden both from the SIP core and the EPS. + +When required by the MC service provider, all authentication and authorisation mechanisms, including security roots, at the application services layer are hidden from and not available to the PLMN operator. + +#### 9.2.2.1.4 MC service provider administers SIP core, separate from EPS + +In this scenario, as illustrated in figure 9.2.2.1.4-1, the MC service provider administers the SIP core, and the MC services and SIP core are independent of the PLMN operator. + +![Diagram illustrating the MC service provider provision of SIP core, separate domain from EPS. The diagram shows three stacked domains separated by dashed lines. The top domain, labeled 'MC service provider administered', contains 'Application services layer' and 'SIP core'. The middle domain, labeled 'PLMN operator administered', contains 'EPS'. The bottom domain, labeled 'MC service provider administered', contains 'SIP client', 'MC service client', and 'MC service UE'. Vertical lines connect the layers: Application services layer to SIP core, SIP core to EPS, EPS to SIP client, SIP client to MC service client, and MC service client to MC service UE.](552328a9daaf3bc0069424b500025880_img.jpg) + +Diagram illustrating the MC service provider provision of SIP core, separate domain from EPS. The diagram shows three stacked domains separated by dashed lines. The top domain, labeled 'MC service provider administered', contains 'Application services layer' and 'SIP core'. The middle domain, labeled 'PLMN operator administered', contains 'EPS'. The bottom domain, labeled 'MC service provider administered', contains 'SIP client', 'MC service client', and 'MC service UE'. Vertical lines connect the layers: Application services layer to SIP core, SIP core to EPS, EPS to SIP client, SIP client to MC service client, and MC service client to MC service UE. + +**Figure 9.2.2.1.4-1: MC service provider provision of SIP core, separate domain from EPS** + +The MC service provider may require that all identities and other sensitive information at the application services layer are hidden from the EPS. The MC service provider need not hide the identities and signalling at the application services layer from the SIP core. However the MC service provider may require that identities and other sensitive information between SIP core and SIP client in the MC service UE are also hidden from the EPS. + +All authentication and authorisation mechanisms, including security roots, at both application services layer and at SIP signalling plane may need to be hidden from, and not available to, the PLMN operator. + +#### 9.2.2.1.5 SIP core partially administered by both PLMN operator and MC service provider + +In this scenario, as illustrated in figure 9.2.2.1.5-1, the SIP core is partially administered by both parties, for example when the SIP core registrar is administered by the MC service provider, but the SIP core registrar finder and proxy is administered by the PLMN operator. + +![Diagram of MC service provider partial provision of SIP core, separate domain from EPS](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +The diagram illustrates a layered architecture for MC services. It consists of four main layers, each enclosed in a dashed box. The top layer is labeled 'MC service provider administered' and contains the 'Application services layer'. Below it is the 'SIP core'. The third layer is labeled 'PLMN operator administered' and contains the 'EPS' (Evolved Packet System). The bottom layer is labeled 'MC service provider administered' and contains the 'SIP client', 'MC service client', and 'MC service UE'. Vertical lines connect the 'Application services layer' to the 'SIP core', the 'SIP core' to the 'EPS', and the 'EPS' to the 'SIP client'. + +Diagram of MC service provider partial provision of SIP core, separate domain from EPS + +**Figure 9.2.2.1.5-1: MC service provider partial provision of SIP core, separate domain from EPS** + +The MC service provider may require that all identities and signalling at the application services layer are hidden from the EPS, and may require identities and other sensitive information to be hidden from the PLMN operator administered part of the SIP core. + +All authentication and authorisation mechanisms, including security roots, at the application services layer may need to be hidden from, and not available to, the PLMN operator. + +#### 9.2.2.1.6 PLMN operator administers SIP core with SIP identities administered by MC service provider + +In this scenario, the PLMN operator administers the SIP core. However, the identities used by the SIP core (IMPI and IMPU) for MC service UEs served by the MC service provider are provided from the SIP database of the MC service provider. + +![Diagram of MC service provider providing identities to PLMN operator SIP core. The diagram is divided into three horizontal sections by dashed lines. The top section is 'MC service provider administered' and contains 'Application services layer', 'SIP database', and 'SIP core'. The middle section is 'PLMN operator administered' and contains a large box representing the EPS, with a yellow box labeled 'EPS' at its bottom right. The bottom section is 'Application service provider administered' and contains 'MC service client', 'SIP client', and 'MC service UE'. Connections: 'Application services layer' connects to 'SIP database' and 'SIP core'. 'SIP database' connects to 'SIP core'. 'SIP core' connects to the EPS box. The EPS box connects to the 'MC service client' and 'SIP client' in the bottom section. 'MC service client' connects to 'MC service UE' and 'SIP client'.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +Diagram of MC service provider providing identities to PLMN operator SIP core. The diagram is divided into three horizontal sections by dashed lines. The top section is 'MC service provider administered' and contains 'Application services layer', 'SIP database', and 'SIP core'. The middle section is 'PLMN operator administered' and contains a large box representing the EPS, with a yellow box labeled 'EPS' at its bottom right. The bottom section is 'Application service provider administered' and contains 'MC service client', 'SIP client', and 'MC service UE'. Connections: 'Application services layer' connects to 'SIP database' and 'SIP core'. 'SIP database' connects to 'SIP core'. 'SIP core' connects to the EPS box. The EPS box connects to the 'MC service client' and 'SIP client' in the bottom section. 'MC service client' connects to 'MC service UE' and 'SIP client'. + +**Figure 9.2.2.1.6-1: MC service provider provides identities to PLMN operator SIP core** + +The MC service provider may require that all identities and signalling at the application services layer are hidden from the SIP core and **EPS**. + +When required by the MC service provider, all authentication and authorisation mechanisms, including security roots, at the application services layer may need to be hidden from, and not available to, the PLMN operator. + +The security roots (authentication keys) required for access to the signalling control plane are not available to the PLMN operator as these are held in the MC service provider's SIP database. However, derived parameters e.g. authentication vectors are provided to the SIP core to allow signalling control plane authentication to take place. + +## 9.2.2.2 MC service user database, SIP database and HSS + +Figures 9.2.2.2-1 to 9.2.2.2-4 show the possible deployment scenarios of the MC service user database and SIP database, including collocation with the HSS. + +The MC service user database may be combined with an HSS in some deployment scenarios (e.g. when the MC service provider and the PLMN operator are part of the same trust domain). + +The MC service user database may be a user data repository (UDR) in deployment scenarios when the UDC architecture is applied (see 3GPP TS 23.335 [15]), in that case the MC service server and the configuration management server are assumed to be application front-ends and the Ud interface is used to access data from the repository. + +NOTE 1: As an implementation option, the SIP database can be located within the SIP core, in which case the AAA-1 interface is not exposed. + +NOTE 2: The MC service user database and the MC service server are always deployed in the same network i.e. both in the PLMN operator's network or both in the MC service provider's network. + +![Diagram of MC service user database and SIP database collocated with HSS.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +This diagram illustrates the collocation of the MC service user database and SIP database with the HSS. On the left, a large box labeled 'HSS' contains three stacked sub-components: 'MC service user database', 'SIP database', and 'HLR'. To the right of the HSS, three corresponding components are shown: 'MC service server', 'SIP core', and 'EPS' (highlighted in yellow). Horizontal lines connect each sub-component in the HSS to its respective component on the right. The connections are labeled as follows: 'MC service defined interface' between the MC service user database and MC service server; 'AAA-1' between the SIP database and SIP core; and 'S6a' between the HLR and EPS. + +Diagram of MC service user database and SIP database collocated with HSS. + +**Figure 9.2.2.2-1: Collocation of MC service user database and SIP database with HSS** + +The HSS depicted in figure 9.2.2.2-1 can be deployed either in the PLMN operator's network or the MC service provider's network. + +![Diagram of shared PLMN operator and MC service provider based deployment.](c0c7f65c51c83fbe595b47326f6b089a_img.jpg) + +This diagram shows a shared deployment scenario. On the left, there is a separate box for 'MCS user database' and a larger box for 'HSS'. The 'HSS' box contains 'SIP database' and 'HLR'. On the right, the components are 'MCX server', 'SIP core', and 'EPS' (highlighted in yellow). Connections are as follows: 'MCS user database defined interface' between the MCS user database and MCX server; 'AAA-1' between the SIP database (inside HSS) and SIP core; and 'S6a' between the HLR (inside HSS) and EPS. + +Diagram of shared PLMN operator and MC service provider based deployment. + +**Figure 9.2.2.2-2: Shared PLMN operator and MC service provider based deployment of MC service - SIP database collocated with HSS with separate MC service user database** + +The MC service user database depicted in figure 9.2.2.2-2 can be deployed in the PLMN operator's network or the MC service provider's network, and the HSS depicted in figure 9.2.2.2-2 can be deployed in the same or different network to the MC service user database i.e. PLMN operator's network or the MC service provider's network. + +![Diagram of shared PLMN operator and MC service provider based deployment of MC service - MC service user database and SIP database deployed together, with separate HSS. The diagram shows a stack of three components on the left: 'MC service user database' and 'SIP database' (grouped together), and 'HLR' (part of 'HSS'). These are connected to a stack of three components on the right: 'MC service server', 'SIP core', and 'EPS'. Connections are labeled: 'MC service defined interface' between MC service user database and MC service server; 'AAA-1' between SIP database and SIP core; and 'S6a' between HLR and EPS.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +Diagram of shared PLMN operator and MC service provider based deployment of MC service - MC service user database and SIP database deployed together, with separate HSS. The diagram shows a stack of three components on the left: 'MC service user database' and 'SIP database' (grouped together), and 'HLR' (part of 'HSS'). These are connected to a stack of three components on the right: 'MC service server', 'SIP core', and 'EPS'. Connections are labeled: 'MC service defined interface' between MC service user database and MC service server; 'AAA-1' between SIP database and SIP core; and 'S6a' between HLR and EPS. + +**Figure 9.2.2.2-3: Shared PLMN operator and MC service provider based deployment of MC service - MC service user database and SIP database deployed together, with separate HSS** + +The MC service user database and SIP database depicted in figure 9.2.2.2-3 can be deployed in the PLMN operator's network or the MC service provider's network, and the HSS depicted in figure 9.2.2.2-3 can be deployed in the same or different network to the MC service user database i.e. PLMN operator's network or the MC service provider's network. + +![Diagram of shared PLMN operator and MC service provider based deployment of MC service - separate HSS, MC service user database and SIP database. The diagram shows three separate components on the left: 'MC service user database', 'SIP database', and 'HLR' (part of 'HSS'). These are connected to a stack of three components on the right: 'MC service server', 'SIP core', and 'EPS'. Connections are labeled: 'MC service defined interface' between MC service user database and MC service server; 'AAA-1' between SIP database and SIP core; and 'S6a' between HLR and EPS.](7722d62e33dcc894cc8555e9474c5606_img.jpg) + +Diagram of shared PLMN operator and MC service provider based deployment of MC service - separate HSS, MC service user database and SIP database. The diagram shows three separate components on the left: 'MC service user database', 'SIP database', and 'HLR' (part of 'HSS'). These are connected to a stack of three components on the right: 'MC service server', 'SIP core', and 'EPS'. Connections are labeled: 'MC service defined interface' between MC service user database and MC service server; 'AAA-1' between SIP database and SIP core; and 'S6a' between HLR and EPS. + +**Figure 9.2.2.2-4: Shared PLMN operator and MC service provider based deployment of MC service - separate HSS, MC service user database and SIP database** + +Each of the MC service user database, SIP database and HSS depicted in figure 9.2.2.2-4 can be deployed in the same or different networks i.e. PLMN operator's network or the MC service provider's network. + +### 9.2.2.3 Control of bearers by SIP core and MC service server + +#### 9.2.2.3.1 General + +This subclause describes two different scenarios in which bearers are controlled by access to Rx by either the SIP core or the MC service server. + +These may provide suitable models for each of the scenarios listed in subclause 9.2.2.1. However, there is no direct correlation of any of the scenarios described in this subclause to each of the scenarios described in subclause 9.2.2.1. + +#### 9.2.2.3.2 Control of bearers by SIP core + +In this scenario, bearer control is performed by the SIP core alone, as shown in figure 9.2.2.3.2-1 below. + +![Diagram of bearer control by SIP core](b06a4c871dfd0ce034cf801519d0039a_img.jpg) + +The diagram shows a vertical stack of four components: MC service server, SIP core, EPS, and MC service UE. The MC service server is connected to the SIP core by a red line. The SIP core is connected to the EPS by a red line. The EPS is connected to the MC service UE by a red line. A label 'Rx' is placed next to the connection between the SIP core and the EPS. A legend indicates that red lines represent 'SIP signalling'. + +Diagram of bearer control by SIP core + +Figure 9.2.2.3.2-1: Bearer control by SIP core + +#### 9.2.2.3.3 Control of bearers by MC service server + +In this scenario, bearer control is performed by the MC service server alone, as shown in figure 9.2.2.3.3-1 below. + +![Diagram of bearer control by MC service server](1a1484a99fee36bd3ca4e40fe1538bf8_img.jpg) + +The diagram shows a vertical stack of four components: MC service server, SIP core, EPS, and MC service UE. The MC service server is connected to the SIP core by a red line. The SIP core is connected to the EPS by a red line. The EPS is connected to the MC service UE by a red line. A label 'Rx' is placed next to the connection between the SIP core and the EPS. A legend indicates that red lines represent 'SIP signalling'. + +Diagram of bearer control by MC service server + +Figure 9.2.2.3.3-1: Bearer control by MC service server + +## 9.3 Architecture model for off-network operations + +### 9.3.1 Off-network architectural model diagram + +Figure 9.3.1-1 shows the off-network architectural model for the MC system solution for inter-UE communication, where no relay function is used. + +![Figure 9.3.1-1: Off-network architectural model for inter-UE communication where no relay function is used. The diagram shows two User Equipment (UE) blocks, UE 3 and UE 4, connected by two lines. A green line represents 'Media' and a red line represents 'Signalling'. A legend box on the right contains a green line labeled 'Media' and a red line labeled 'Signalling'.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +Figure 9.3.1-1: Off-network architectural model for inter-UE communication where no relay function is used. The diagram shows two User Equipment (UE) blocks, UE 3 and UE 4, connected by two lines. A green line represents 'Media' and a red line represents 'Signalling'. A legend box on the right contains a green line labeled 'Media' and a red line labeled 'Signalling'. + +**Figure 9.3.1-1: Off-network architectural model for inter-UE communication where no relay function is used** + +Figure 9.3.1-2 shows the off-network architectural model for the MC system solution for configuration management and group management. + +![Figure 9.3.1-2: Off-network architectural model for configuration management and group management. The diagram shows an 'Offline common services server' (dashed box) containing a 'Group management server' and a 'Configuration management server'. These are connected via reference points CSC-12 and CSC-11 respectively to a 'Non-EPS access' block (yellow box). The 'Non-EPS access' block is connected to 'UE 3', which contains a 'Group management client' and a 'Configuration management client'.](408c4798ea60469e0728a7cbbd598668_img.jpg) + +Figure 9.3.1-2: Off-network architectural model for configuration management and group management. The diagram shows an 'Offline common services server' (dashed box) containing a 'Group management server' and a 'Configuration management server'. These are connected via reference points CSC-12 and CSC-11 respectively to a 'Non-EPS access' block (yellow box). The 'Non-EPS access' block is connected to 'UE 3', which contains a 'Group management client' and a 'Configuration management client'. + +**Figure 9.3.1-2: Off-network architectural model for configuration management and group management** + +NOTE 1: The offline common services server denoted in figure 9.3.1-2 could be provided by a portable device e.g. laptop. + +NOTE 2: Non-EPS access can be any IP-CAN that is mutually supported by the offline common services server and the UE 3, and which provides necessary connectivity for the CSC-11 and CSC-12 reference points. It is out of scope of this specification what type of IP-CANs are supported, but could be e.g. USB, Bluetooth or WLAN. + +The offline common services server could be the same entity (or set of entities) as the common services core. In this case the configuration management server shall not configure to the same user on the same UE, with parameters provisioned by offline and online configuration simultaneously. The configuration management server shall not configure to the same user on the same UE for the same parameters by using CSC-11 and CSC-4 reference points simultaneously. + +The entities within this model are described in the following subclauses and a full functional model is given in subclause 7.3.2. + +## 9.3.2 UE 3 + +The UE 3 is a UE using ProSe and supporting application(s) related to off-network MC service, and is composed of the following functional entities: + +- for MC services, MC service clients as described in subclause 7.4.2.3.1 with relevant application functions of the specific MC service defined in the corresponding MC service TS; +- for signalling control, a signalling user agent as described in subclause 7.4.3.1.1; +- for configuration management, a configuration management client as described in subclause 7.4.2.2.1; and +- for group management, a group management client as described in subclause 7.4.2.2.3. + +## 9.3.3 UE 4 + +The UE 4 represents one or more UEs with the same functionality as UE 3. + +### 9.3.4 Offline common services server + +The offline common services server supports configuration applications related to MC service, and is composed of the following functional entities: + +- for configuration management, a configuration management server as described in subclause 7.4.2.2.2; and +- for group management, a group management server as described in subclause 7.4.2.2.4. + +## 9.4 Architecture model for roaming + +Roaming is achieved using either: + +- **EPC-level roaming** as defined in 3GPP TS 23.401 [17]; or +- IMS-level roaming as defined in 3GPP TS 23.228 [9]. + +# 10 Procedures and information flows + +## 10.1 MC service configuration + +### 10.1.1 General + +#### 10.1.1.1 MC service configuration on primary MC system + +Depicted in figure 10.1.1.1-1 is a MC service configuration time sequence of the data related to specific MC service, representing the general lifecycle of MC service UE using an MC service. + +![Flowchart showing the MC service UE configuration time sequence. The sequence starts with 'Bootstrap', followed by 'MC service user authentication', 'MC service authorization', 'MC service operation(s) (e.g., Affiliation, Call establishment, Ongoing call, Call release)', and finally 'MC service log-off'. Configuration data boxes on the right point to specific steps: 'Initial UE configuration' points to the transition between Bootstrap and authentication; 'UE configuration', 'MC service user profile configuration', and 'Group configuration' point to the transition between authentication and authorization; 'Updates to: UE configuration, MC service user profile configuration, group configuration' points to the transition between operations and log-off. There are also feedback arrows from the operations box back to the authorization and log-off steps.](e9f5aa7b76362051c591d6783211f820_img.jpg) + +``` + +graph TD + Bootstrap[Bootstrap] --> Auth[MC service user authentication] + Auth --> AuthZ[MC service authorization] + AuthZ --> Ops["MC service operation(s) +(e.g., Affiliation, +Call establishment, +Ongoing call, +Call release)"] + Ops --> LogOff[MC service log-off] + + IUC[Initial UE configuration] -.-> Bootstrap + UC[UE configuration] -.-> AuthZ + MUPC[MC service user profile configuration] -.-> AuthZ + GC[Group configuration] -.-> AuthZ + U["Updates to: +UE configuration, +MC service user profile +configuration, group configuration"] -.-> Ops + + Ops --> AuthZ + Ops --> LogOff + +``` + +Flowchart showing the MC service UE configuration time sequence. The sequence starts with 'Bootstrap', followed by 'MC service user authentication', 'MC service authorization', 'MC service operation(s) (e.g., Affiliation, Call establishment, Ongoing call, Call release)', and finally 'MC service log-off'. Configuration data boxes on the right point to specific steps: 'Initial UE configuration' points to the transition between Bootstrap and authentication; 'UE configuration', 'MC service user profile configuration', and 'Group configuration' point to the transition between authentication and authorization; 'Updates to: UE configuration, MC service user profile configuration, group configuration' points to the transition between operations and log-off. There are also feedback arrows from the operations box back to the authorization and log-off steps. + +Figure 10.1.1.1-1 MC service UE configuration time sequence and associated configuration data + +The MC service UE is provided with initial UE configuration via a bootstrap procedure that provides the MC service UE's clients (e.g. MC service client, group management client, configuration management client, identity management client, key management client, functional alias management client) with critical information needed to connect to the MC system. This includes PDN connection information corresponding to the configured MC services on the MC service UE (see "EPS bearer considerations" in the 3GPP TS 23.379 [16]) and on-network server identity information for all application plane servers with which the MC service UE needs to interact. See annex A.6 for more information. + +The MC service UE is provided with UE configuration, MC service user profile configuration and group configuration via online configuration. While the MC service UE is using the MC service it may receive online configuration updates. If the MC service user profile configuration contains multiple MC service user profiles for an authenticated MC service user, then the MC service client and MC service server set the active MC service user profile to the configured pre-selected MC service user profile at MC service authorization (which can be updated by the MC service user using the procedure specified in subclause 10.1.4.6). The active MC service user profile can be changed by the MC service user to a different MC service user profile during MC service service (see MC service TSs). + +The MC service is configured with the service configuration (not shown in the figure 10.1.1.1-1) which the MC service enforces during the entire phase of MC service UE using the MC service. + +**Editor's note: Providing MC services to an MC service UE with an unauthenticated MC service user is FFS.** + +### 10.1.1.2 MC service configuration for migration to partner MC system + +Figure 10.1.1.2-1 depicts a general MC service configuration time sequence of the data related to MC service, representing the general lifecycle of MC service UE which obtains MC service when migrated to a partner MC system. The MC service user can only receive MC service from one MC system at a time. + +![Flowchart of MC service UE configuration sequence for migration. The sequence starts with 'MC service UE configuration and MC service authorization on primary MC system', followed by 'Select user profile that permits migration to selected partner MC system', 'Initiate migration to selected partner MC system', 'User authentication to partner MC system', 'Signalling plane migration', 'MC service authorization on partner MC system', 'MC service operations on partner MC system', and ends with 'MC service log-off'. Dashed boxes provide additional information: 'Security parameters to enable migration' (pointing to the transition between steps 2 and 3), 'MC service user profile configuration by partner MC system' and 'Group configuration for partner MC system' (pointing to the transition between steps 5 and 6), and 'Updates to: MC service user profile configuration by partner MC system, group configuration for partner MC system' (pointing to the transition between steps 6 and 7).](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +``` + +graph TD + A[MC service UE configuration and MC service authorization on primary MC system] --> B[Select user profile that permits migration to selected partner MC system] + B --> C[Initiate migration to selected partner MC system] + C --> D[User authentication to partner MC system] + D --> E[Signalling plane migration] + E --> F[MC service authorization on partner MC system] + F --> G[MC service operations on partner MC system] + G --> H[MC service log-off] + + I[Security parameters to enable migration] -.-> B + J[MC service user profile configuration by partner MC system] -.-> F + K[Group configuration for partner MC system] -.-> F + L[Updates to: MC service user profile configuration by partner MC system, group configuration for partner MC system] -.-> G + +``` + +Flowchart of MC service UE configuration sequence for migration. The sequence starts with 'MC service UE configuration and MC service authorization on primary MC system', followed by 'Select user profile that permits migration to selected partner MC system', 'Initiate migration to selected partner MC system', 'User authentication to partner MC system', 'Signalling plane migration', 'MC service authorization on partner MC system', 'MC service operations on partner MC system', and ends with 'MC service log-off'. Dashed boxes provide additional information: 'Security parameters to enable migration' (pointing to the transition between steps 2 and 3), 'MC service user profile configuration by partner MC system' and 'Group configuration for partner MC system' (pointing to the transition between steps 5 and 6), and 'Updates to: MC service user profile configuration by partner MC system, group configuration for partner MC system' (pointing to the transition between steps 6 and 7). + +**Figure 10.1.1.2-1 MC service UE configuration sequence for migration** + +The MC service user and MC service UE first follow the MC service UE configuration and MC service user authorization steps described in subclause 10.1.1.1 to obtain one or more MC service user profiles from the primary MC system. Each user profile received from the primary MC system contains a list of partner MC systems to which migration is permitted using that user profile, together with the access information needed to communicate with the application plane servers of the partner MC system. See Annex A.3 for more information. The MC service user also obtains the necessary security parameters needed to authenticate and become service authorized on the partner MC system; the process for this is specified in 3GPP TS 33.180 [25]. + +NOTE 1: The above steps which enable migration to take place may be carried out some time in advance of migration. The MC service user could repeatedly obtain migrated MC service, e.g. on successive days while located in the area of the partner MC system, without needing to obtain the initial configuration afresh in advance of each period of migrated MC service. The user profile from the primary MC system must be retained to provide the access information to permit this. + +To initiate migration, the desired partner system from those listed in the chosen user profile is selected, and the access information provided in the user profile is used to initiate communication with the partner MC system. + +NOTE 2: Selection of the relevant partner MC system could be performed as a result of a manual action by the user or automatically by an application in the MC service UE, e.g. according to the current location of the MC service UE or according to the serving PLMN of the MC service UE. + +The MC service user performs user authentication to the partner MC system as specified in 3GPP TS 33.180 [25]. The MC service UE performs signalling plane migration. + +NOTE 3: The security aspects of the signalling plane migration are outside the scope of the present document. + +The user profile or profiles for that MC service user which are to be used for service when migrated to the partner MC system are then downloaded to the configuration management client in the MC service UE by the partner MC system, and these downloaded profile or profiles are used by the MC service user during the ensuing period of MC service on the partner MC system. + +NOTE 4: The user profile obtained from the primary MC system is simply used to provide access information for the partner MC system, and is not otherwise used by the MC service client during migrated MC service. + +Group configuration for the MC service groups listed in the user profile are then obtained by the group management client in the MC service UE. After these configuration steps, the MC service user obtains service authorization on the partner MC system. + +Once service authorized, further configuration changes may be provided by the partner MC system during the period of operational MC service, in accordance with subclause 10.1.1.1. The partner MC system enforces the use of the user profiles and group configuration that have been provided by the configuration process described in this subclause. + +## 10.1.2 Information flows for MC service configuration + +### 10.1.2.1 Store group configuration request + +Table 10.1.2.1-1 describes the information flow store group configuration request from the group management client to the group management server. + +**Table 10.1.2.1-1: Store group configuration request** + +| Information element | Status | Description | +|-------------------------------------|--------|-------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| MC service group configuration data | M | MC service group configuration data | + +### 10.1.2.2 Store group configuration response + +Table 10.1.2.2-1 describes the information flow store group configuration response from the group management server to the group management client. + +**Table 10.1.2.2-1: Store group configuration response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| Result | M | Indicates the success or failure for the result | + +### 10.1.2.3 Get group configuration request + +Table 10.1.2.3-1 describes the information flow get group configuration request from the group management client to the group management server. + +**Table 10.1.2.3-1: Get group configuration request** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| MC service group information reference | M | Reference to configuration data for the MC service group | +| MC services requested (see NOTE) | O | Service(s) for which group configuration is requested; one or more of MCPTT, MCVideo, MCData | +| NOTE: If 'MC services requested' is not present, group configuration is requested for all services defined for the MC service group | | | + +### 10.1.2.4 Get group configuration response + +Table 10.1.2.4-1 describes the information flow get configuration response from the group management server to the group management client. + +**Table 10.1.2.4-1: Get group configuration response** + +| Information element | Status | Description | +|-------------------------------------|--------|-------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| MC service group configuration data | M | MC service group configuration data | + +### 10.1.2.5 Subscribe group configuration request + +Table 10.1.2.5-1 describes the information flow subscribe group configuration request from the group management client to the group management server. + +**Table 10.1.2.5-1: Subscribe group configuration request** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| MC services requested (see NOTE) | O | Service(s) for which group configuration is requested; one or more of MCPTT, MCVideo, MCData | +| NOTE: If 'MC services requested' is not present, group configuration is requested for all services defined for the MC service group | | | + +### 10.1.2.6 Subscribe group configuration response + +Table 10.1.2.6-1 describes the information flow subscribe group configuration response from the group management server to the group management client. + +**Table 10.1.2.6-1: Subscribe group configuration response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| Result | M | Indicates the success or failure for the result | + +### 10.1.2.7 Notify group configuration request + +Table 10.1.2.7-1 describes the information flow notify group configuration request from the group management server to the group management client. + +**Table 10.1.2.7-1: Notify group configuration request** + +| Information element | Status | Description | +|--------------------------------------------------------------------|--------|------------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| MC service group information reference (NOTE) | O | Reference to information stored relating to the MC service group | +| Group related key material (NOTE) | O | Key material for use with the MC service group | +| NOTE: At least one of these information elements shall be present. | | | + +### 10.1.2.8 Notify group configuration response + +Table 10.1.2.8-1 describes the information flow notify group configuration response from the group management client to the group management server. + +**Table 10.1.2.8-1: Notify group configuration response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| Result | M | Indicates the success or failure for the result | + +### 10.1.2.9 Get functional alias configuration request + +Table 10.1.2.9-1 describes the information flow get functional alias configuration request from the functional alias management client to the functional alias management server. + +**Table 10.1.2.9-1: Get functional alias configuration request** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------------------------------------------------| +| Functional alias | M | URI of the functional alias | +| Functional alias information reference | M | Reference to configuration data for the functional alias | +| MC services requested (see NOTE) | O | Service(s) for which functional alias configuration is requested; one or more of MCPTT, MCVideo, MCData | +| NOTE: If 'MC services requested' is not present, functional alias configuration is requested for all services defined for the functional alias. | | | + +### 10.1.2.10 Get functional alias configuration response + +Table 10.1.2.10-1 describes the information flow get configuration response from the functional alias management server to the functional alias management client. + +**Table 10.1.2.10-1: Get functional alias configuration response** + +| Information element | Status | Description | +|-------------------------------------|--------|-------------------------------------| +| Functional alias | M | URI of the functional alias | +| Functional alias configuration data | M | Functional alias configuration data | + +### 10.1.2.11 Subscribe functional alias configuration request + +Table 10.1.2.11-1 describes the information flow subscribe functional alias configuration request from the functional alias management client to the functional alias management server. + +**Table 10.1.2.11-1: Subscribe functional alias configuration request** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------------------------------------------------| +| Functional alias | M | URI of the functional alias | +| MC services requested (see NOTE) | O | Service(s) for which functional alias configuration is requested; one or more of MCPTT, MCVideo, MCData | +| NOTE: If 'MC services requested' is not present, functional alias configuration is requested for all services defined for the functional alias. | | | + +### 10.1.2.12 Subscribe functional alias configuration response + +Table 10.1.2.12-1 describes the information flow subscribe functional alias configuration response from the functional alias management server to the functional management client. + +**Table 10.1.2.12-1: Subscribe functional alias configuration response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------| +| Functional alias | M | URI of the functional alias | +| Result | M | Indicates the success or failure for the result | + +### 10.1.2.13 Notify functional alias configuration request + +Table 10.1.2.13-1 describes the information flow notify functional alias configuration request from the functional alias management server to the functional alias management client. + +**Table 10.1.2.13-1: Notify functional alias configuration request** + +| Information element | Status | Description | +|----------------------------------------|--------|------------------------------------------------------------------| +| Functional alias | M | URI of the functional alias | +| Functional alias information reference | M | Reference to information stored relating to the functional alias | + +### 10.1.2.14 Notify functional alias configuration response + +Table 10.1.2.14-1 describes the information flow notify functional alias configuration response from the functional alias management client to the functional alias management server. + +**Table 10.1.2.14-1: Notify functional alias configuration response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------| +| Functional alias | M | URI of the functional alias | +| Result | M | Indicates the success or failure for the result | + +## 10.1.3 MC service UE configuration data + +### 10.1.3.1 General + +The MC service UE configuration data has to be known by the MC service UE before it can use the MC service. + +### 10.1.3.2 Procedures + +The procedure for MC service UE obtaining the MC service UE related configuration data is illustrated in figure 10.1.3.2-1. + +Pre-conditions: + +- The MC service UE has the secure access to the configuration management server. + +![Sequence diagram showing the MC service UE obtaining configuration data. The client sends a 'Get MC service UE configuration request' to the server, and the server responds with a 'Get MC service UE configuration response'.](476fddf3a7afd9a5f77639c39a7aeeac_img.jpg) + +``` + +sequenceDiagram + participant Client as Configuration management client + participant Server as Configuration management server + Note left of Client: MC service UE + Client->>Server: 1. Get MC service UE configuration request + Server-->>Client: 2. Get MC service UE configuration response + +``` + +Sequence diagram showing the MC service UE obtaining configuration data. The client sends a 'Get MC service UE configuration request' to the server, and the server responds with a 'Get MC service UE configuration response'. + +**Figure 10.1.3.2-1: MC service UE obtains the configuration data** + +1. The configuration management client sends a get MC service UE configuration request to the configuration management server for obtaining MC service UE configuration data. +2. The configuration management server sends get MC service UE configuration response to the configuration management client. This message carries the MC service UE configuration data. + +### 10.1.3.3 Structure of UE configuration data + +For a MC service, the MC service UE configuration data is listed in the corresponding MC service TS. + +## 10.1.4 MC service user profile + +### 10.1.4.1 General + +An MC service user is identified by an MC service ID. An MC service ID is associated with at least one MC service user profile and can be associated with multiple MC service user profiles (identified by an index and optionally a profile name). This is depicted in figure 10.1.4.1-1. + +![Diagram illustrating the relationship between an MC service user, MC service IDs, and MC service user profiles.](cc542843836eecb036b99cb270b54a1e_img.jpg) + +``` + +graph LR + MCID[MC service user (MC ID)] --> MCIDX["MC service ID X +(corresponding to MC service A)"] + MCID --> MCIDY["MC service ID Y +(corresponding to MC service B)"] + MCIDX --> P1X["MC service user profile +(Index 1)"] + MCIDX --> P2X["MC service user profile +(Index 2)"] + MCIDX --> PnX["MC service user profile +(Index n)"] + MCIDY --> P1Y["MC service user profile +(Index 1)"] + MCIDY --> P2Y["MC service user profile +(Index 2)"] + MCIDY --> PnY["MC service user profile +(Index n)"] + +``` + +The diagram shows a hierarchical relationship. At the root is a box labeled 'MC service user (MC ID)'. Two lines branch out from this box to two separate boxes: 'MC service ID X (corresponding to MC service A)' and 'MC service ID Y (corresponding to MC service B)'. From the 'MC service ID X' box, three lines branch out to three boxes labeled 'MC service user profile (Index 1)', 'MC service user profile (Index 2)', and 'MC service user profile (Index n)'. Similarly, from the 'MC service ID Y' box, three lines branch out to three boxes labeled 'MC service user profile (Index 1)', 'MC service user profile (Index 2)', and 'MC service user profile (Index n)'. + +Diagram illustrating the relationship between an MC service user, MC service IDs, and MC service user profiles. + +**Figure 10.1.4.1-1: The relationship of MC service user, MC service IDs, MC service user profile and MC services** + +For an MC service user there can be multiple MC service IDs with the constraint that only one MC service ID exists for a given MC service for that MC service user (e.g. MC service ID X may correspond to MCPTT service and MC service ID Y may correspond to MCVideo service). When the MC service provider requires to support a single MC service ID for all MC services, the value of the multiple MC service IDs is the same (e.g. value of MC service ID X is same as MC service ID Y). + +In the case where a single MC service ID is configured for a MC service user for authorized access to multiple MC services, the MC service UE and MC service server shall include the indication of the specific MC service during the communication. + +For the same MC service user there can be different MC service user profiles active on different MC service UEs or different MC service user profiles active on the same MC service UE at different times. The MC service user may have one or more specific MC service user profiles defined for use in migration cases, whereby there may be more than one MC service user profiles defined for migration for that MC service user e.g. so that different MC service user profiles can be applied in different partner MC systems. The appropriate MC service user profile for migration for the relevant partner MC system will be provided to the partner MC system by the procedure. For both the cases of MC service on the primary MC system of the MC service user, and MC service when migrating to a partner MC system, only one MC service user profile per MC service client is active at a time. + +All MC service user profiles associated with an MC service user are stored in the MC service user database. Different parts of the MC service user profile are provisioned by the Mission Critical Organization, by the MC service provider and by the MC service user, respectively. + +MC service user profile information is downloaded to the MC service UE. The MC service user profile configuration may include more than one information exchange e.g. the configuration management server may provide the MC service UE with a list of some or all enabled MC service user profiles to allow the MC service user to select one (where the list may contain a subset of the MC service user profile information sufficient for the MC service user to distinguish which MC service user profile to select). + +When an MC service user is receiving MC service in its primary MC system, the MC service user profile provisioning in the UE is initiated by the configuration management client (e.g. upon MC service user authentication or on reconnect to the MC service), or initiated by the configuration management server (e.g. due to role change or organization + +change). For a migrating MC service user, the MC service user profile provisioning in the UE is initiated when the MC service user attempts to migrate to a partner MC system, and requests the MC service user profile from a nominated configuration management server in the partner MC system, prior to requesting service authorization from a partner MC service server. + +The partner MC system may require that the MC service user profiles for migrating MC service users have parameters imposed by that partner MC system according to its operating and security policies. For example, there may be limitations in the locations at which migrating MC users can receive service, specific priority levels for migrating MC service users or certain groups to which the migrating MC service users require access. The partner MC system applies any necessary modifications to the MC service user profile received from the primary MC system of the MC service user in accordance with its local requirements. This local profile will be stored, and will be provided to the configuration management server in the partner MC system in order to distribute it to the configuration management client of the migrating MC service user. This modified profile may be sent to the primary MC system of the migrating MC service user so that the primary MC system can validate the modified profile before it is provided to the migrating MC service UE. The modified MC service user profile will subsequently be provided to the MC service server in the partner MC system when the migrating MC user attempts service authorization. + +**Editor's note:** A reference should be added to configuration tables in Annex A to indicate where the local configuration policy can be configured. + +#### 10.1.4.2 Information flows for MC service user profile + +##### 10.1.4.2.1 Get MC service user profile request + +Table 10.1.4.2.1-1 describes the information flow get MC service user profile request from the configuration management client to the configuration management server. + +**Table 10.1.4.2.1-1: Get MC service user profile request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------| +| MC service ID | M | The MC service ID of the MC service user. | + +##### 10.1.4.2.2 Get MC service user profile response + +Table 10.1.4.2.2-1 describes the information flow get MC service user profile response from the configuration management server to the configuration management client. + +**Table 10.1.4.2.2-1: Get MC service user profile response** + +| Information element | Status | Description | +|------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MC service user profile data | M | One or more MC service user profiles (identified as specified in subclause 10.1.4.1) associated with the MC service ID provided in the associated get MC service user profile request. | + +##### 10.1.4.2.3 Notification for MC service user profile data update + +Table 10.1.4.2.3-1 describes the information flow notification for MC service user profile data update from the configuration management server to the configuration management client. + +**Table 10.1.4.2.3-1: Notification for MC service user profile data update** + +| Information element | Status | Description | +|---------------------------------------------------|--------|-------------------------------------------------------| +| Pointer to modified MC service user profile data. | M | Pointer to the modified MC service user profile data. | + +##### 10.1.4.2.4 Get updated MC service user profile data request + +Table 10.1.4.2.4-1 describes the information flow get updated MC service user profile data request from the configuration management client to the configuration management server. + +**Table 10.1.4.2.4-1: Get updated MC service user profile data request** + +| Information element | Status | Description | +|---------------------------------------------------|--------|-------------------------------------------------------| +| MC service ID | M | The MC service ID of the originating MC service user. | +| Pointer to modified MC service user profile data. | M | Pointer to the modified MC service user profile data. | + +#### 10.1.4.2.5 Get updated MC service user profile data response + +Table 10.1.4.2.5-1 describes the information flow get updated MC service user profile data response from the configuration management server to the configuration management client. + +**Table 10.1.4.2.5-1: Get updated MC service user profile data response** + +| Information element | Status | Description | +|--------------------------------------|--------|------------------------------------------------------| +| Updated MC service user profile data | M | MC service user profile data that has been modified. | + +#### 10.1.4.2.6 Update MC service user profile data request + +Table 10.1.4.2.6-1 describes the information flow update MC service user profile data request from the configuration management client to the configuration management server. + +**Table 10.1.4.2.6-1: Update MC service user profile data request** + +| Information element | Status | Description | +|--------------------------------------|--------|-------------------------------------------------------| +| MC service ID | M | The MC service ID of the originating MC service user. | +| Updated MC service user profile data | M | The contents of the user profile data to be updated. | + +#### 10.1.4.2.7 Update MC service user profile data response + +Table 10.1.4.2.7-1 describes the information flow update MC service user profile data response from the configuration management server to the configuration management client. + +**Table 10.1.4.2.7-1: Update MC service user profile data response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------| +| Result | M | Indicates the success or failure | + +#### 10.1.4.2.8 Update pre-selected MC service user profile request + +Table 10.1.4.2.8-1 describes the information flow update pre-selected MC service user profile request from the configuration management client to the configuration management server. + +**Table 10.1.4.2.8-1: Update pre-selected MC service user profile request** + +| Information element | Status | Description | +|-------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator. | +| MC service user profile index | M | The MC service user profile index of the MC service user profile that is to be pre-selected by the MC service server at MC service user authentication. | + +#### 10.1.4.2.9 Update pre-selected MC service user profile response + +Table 10.1.4.2.9-1 describes the information flow update pre-selected MC service user profile response from the configuration management server to the configuration management client. + +**Table 10.1.4.2.9-1: Update pre-selected MC service user profile response** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------| +| Result | M | Indicates the success or failure. | + +#### 10.1.4.2.10 Update selected MC service user profile request + +Table 10.1.4.2.10-1 describes the information flow update selected MC service user profile request from the MC service client to the MC service server and is used by the following MC services: + +- MCPTT (as specified in 3GPP TS 23.379 [16]); +- MCVideo (as specified in 3GPP TS 23.281 [12]); and +- MCData (as specified in 3GPP TS 23.282 [13]). + +**Table 10.1.4.2.10-1: Update selected MC service user profile request** + +| Information element | Status | Description | +|-------------------------------|--------|----------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator. | +| MC service user profile index | M | The MC service user profile index of the selected MC service user profile. | + +#### 10.1.4.2.11 Update selected MC service user profile response + +Table 10.1.4.2.11-1 describes the information flow update selected MC service user profile response from the MC service server to the MC service client and is used by the following MC services: + +- MCPTT (as specified in 3GPP TS 23.379 [16]); +- MCVideo (as specified in 3GPP TS 23.281 [12]); and +- MCData (as specified in 3GPP TS 23.282 [13]). + +**Table 10.1.4.2.11-1: Update selected MC service user profile response** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------| +| Result | M | Indicates the success or failure. | + +### 10.1.4.3 MC service user obtains the MC service user profile(s) from the network + +#### 10.1.4.3.1 MC service user receiving MC service in primary MC system + +The procedure for the MC service user obtaining MC service user profiles in the primary MC system of that MC service user is illustrated in figure 10.1.4.3.1-1. + +Pre-conditions: + +- The MC service user has performed user authentication in the identity management server. +- The MC service UE has secure access to the configuration management server. + +![Sequence diagram showing the interaction between a Configuration management client and a Configuration management server to obtain an MC service user profile.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +``` +sequenceDiagram + participant Client as Configuration management client + participant Server as Configuration management server + Note right of Server: 2. Obtain MC service user profile + Client->>Server: 1. Get MC service user profile request + Server-->>Client: 3. Get MC service user profile response +``` + +The diagram illustrates a sequence of three messages between a 'Configuration management client' and a 'Configuration management server'. The client sends a 'Get MC service user profile request' (step 1) to the server. The server then performs an internal action 'Obtain MC service user profile' (step 2) and sends a 'Get MC service user profile response' (step 3) back to the client. + +Sequence diagram showing the interaction between a Configuration management client and a Configuration management server to obtain an MC service user profile. + +**Figure 10.1.4.3.1-1: MC service user obtains the MC service user profile(s) from the network** + +1. The configuration management client sends a get MC service user profile request message to the configuration management server, which includes the MC service ID. +2. The configuration management server obtains the MC service user profile information. +3. The configuration management server sends get MC service user profile response message to the configuration management client. When a download is necessary, this message includes all MC service user profiles that are associated with the MC service ID. + +#### 10.1.4.3.2 MC service user receiving MC service from a partner MC system + +Figure 10.1.4.3.2-1 below illustrates mechanism for the configuration management client to retrieve the MC service user profile for the migrating MC service user from the partner MC system. + +**NOTE:** Any proxy servers at the edges of the primary and partner MC systems which are used to hide the topology of the MC systems from external entities are not shown in this procedure. + +##### Preconditions + +- The MC service user is permitted to migrate to the partner MC system, and the relevant authorizations are configured in both the primary and partner MC systems of that MC service user +- The MC service user has performed MC service user authentication in the partner MC system, and has received the necessary credentials to retrieve configuration information and to request service authorization. +- The MC service UE has been provided with addressing information to allow the configuration management client in the MC service UE to access the configuration management server in the partner MC system. + +![Sequence diagram showing the retrieval of user profile in partner MC system. The diagram involves three main lifelines: MC service UE, Partner MC system of user, and Primary MC system of user. The Partner MC system contains Configuration management server and MC service user database. The Primary MC system contains Configuration management server and MC service user database. The sequence of messages is: 1. Get MC service user profile for migration request from CM client to CM server in Partner MC system. 2. Get migrated MC service user profile request from CM server in Partner MC system to CM server in Primary MC system. 3. Retrieve user profile for migration from CM server in Primary MC system to CM server in Partner MC system. 4. Get migrated MC service user profile response from CM server in Primary MC system to CM server in Partner MC system. 5. Modify user profile according to partner MC system policy and store from CM server in Partner MC system to MC service user database in Partner MC system. 6. Validate modified MC service user profile request from CM server in Partner MC system to CM server in Primary MC system. 7. Validate modified user profile for migration from CM server in Primary MC system to CM server in Partner MC system. 8. Validate modified MC service user profile response from CM server in Primary MC system to CM server in Partner MC system. 9. Get MC service user profile for migration response from CM server in Partner MC system to CM client in MC service UE.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` + +sequenceDiagram + participant CM_client as Configuration management client + participant CM_server_partner as Configuration management server + participant DB_partner as MC service user database + participant CM_server_primary as Configuration management server + participant DB_primary as MC service user database + + Note left of CM_client: MC service UE + Note left of CM_server_partner: Partner MC system of user + Note left of CM_server_primary: Primary MC system of user + + CM_client->>CM_server_partner: 1. Get MC service user profile for migration request + CM_server_partner->>CM_server_primary: 2. Get migrated MC service user profile request + CM_server_primary->>CM_server_partner: 3. Retrieve user profile for migration + CM_server_primary->>CM_server_partner: 4. Get migrated MC service user profile response + CM_server_partner->>DB_partner: 5. Modify user profile according to partner MC system policy and store + CM_server_partner->>CM_server_primary: 6. Validate modified MC service user profile request + CM_server_primary->>CM_server_partner: 7. Validate modified user profile for migration + CM_server_primary->>CM_server_partner: 8. Validate modified MC service user profile response + CM_server_partner->>CM_client: 9. Get MC service user profile for migration response + +``` + +Sequence diagram showing the retrieval of user profile in partner MC system. The diagram involves three main lifelines: MC service UE, Partner MC system of user, and Primary MC system of user. The Partner MC system contains Configuration management server and MC service user database. The Primary MC system contains Configuration management server and MC service user database. The sequence of messages is: 1. Get MC service user profile for migration request from CM client to CM server in Partner MC system. 2. Get migrated MC service user profile request from CM server in Partner MC system to CM server in Primary MC system. 3. Retrieve user profile for migration from CM server in Primary MC system to CM server in Partner MC system. 4. Get migrated MC service user profile response from CM server in Primary MC system to CM server in Partner MC system. 5. Modify user profile according to partner MC system policy and store from CM server in Partner MC system to MC service user database in Partner MC system. 6. Validate modified MC service user profile request from CM server in Partner MC system to CM server in Primary MC system. 7. Validate modified user profile for migration from CM server in Primary MC system to CM server in Partner MC system. 8. Validate modified MC service user profile response from CM server in Primary MC system to CM server in Partner MC system. 9. Get MC service user profile for migration response from CM server in Partner MC system to CM client in MC service UE. + +**Figure 10.1.4.3.2-1: Retrieval of user profile in partner MC system** + +1. The configuration management client in the MC service UE of the migrating MC service user requests the MC service user profile for migration from the configuration management server in the partner MC system. +2. The configuration management server in the partner MC system requests the MC service user profile from the configuration management server in the primary MC system of the MC service user. +3. The configuration management server in the primary MC system of the MC service user retrieves the MC service user profile from the MC service user database in that primary MC system. The identification of the partner MC system to which the MC service user is attempting to migrate is used to determine which MC service user profile is retrieved for that MC service user for migration to that partner MC system. +4. The configuration management server in the primary MC system provides the MC service user profile to the configuration management server in the partner MC system of the MC service user, optionally requesting validation of the modified MC service user profile. +5. The partner MC system of the MC service user modifies the MC service user profile according to local configuration information and stores the modified MC service user profile in the MC service user database in the partner MC system. +6. If the primary MC system requested validation of the MC service user profile in step 4, the configuration management server in the partner MC system of the migrating MC service user may send the modified MC service user profile to the configuration management server of the primary MC system of the MC service user to allow the primary MC system of the MC service user to validate the modified MC service user profile. +7. The primary MC system of the migrated MC service user validates the modified MC service profile of the migrated MC service user. +8. The primary MC system of the migrated MC service user responds to the partner MC system with the results of the validation process. + +9. The configuration management server in the partner MC system provides the MC service user profile to the configuration management client of the migrating MC service user, + +NOTE: Step 9 is not followed if the validation process fails. + +#### 10.1.4.4 MC service user receives updated MC service user profile data from the network + +The procedure for MC service user obtaining updated MC service user profile data (see 3GPP TS 23.379 [16]) that is initiated by the network is illustrated in figure 10.1.4.4-1. + +Pre-conditions: + +- The MC service user has performed user authentication in identity management server. +- The MC service UE has secure access to the configuration management server. +- The MC service UE has already obtained one or more MC service user profiles. +- The configuration management server has access to the MC service user profile(s) associated with the MC service ID of the MC service user. + +![Sequence diagram illustrating the procedure for MC service user receiving updated MC service user profile data from the network. The diagram shows two lifelines: 'Configuration management client' and 'Configuration management server'. The sequence of messages is: 1. Obtain updated MC service user profile data (from server to server), 2. Notification for MC service user profile data update (from server to client), 3. Get updated MC service user profile data request (from client to server), 4. Get updated MC service user profile data response (from server to client).](8d1bb05debbaef0f72751449b2b55172_img.jpg) + +``` +sequenceDiagram + participant Client as Configuration management client + participant Server as Configuration management server + Note right of Server: 1. Obtain updated MC service user profile data + Server->>Client: 2. Notification for MC service user profile data update + Client->>Server: 3. Get updated MC service user profile data request + Server->>Client: 4. Get updated MC service user profile data response +``` + +Sequence diagram illustrating the procedure for MC service user receiving updated MC service user profile data from the network. The diagram shows two lifelines: 'Configuration management client' and 'Configuration management server'. The sequence of messages is: 1. Obtain updated MC service user profile data (from server to server), 2. Notification for MC service user profile data update (from server to client), 3. Get updated MC service user profile data request (from client to server), 4. Get updated MC service user profile data response (from server to client). + +**Figure 10.1.4.4-1: MC service user receives updated MC service user profile data from the network** + +1. The configuration management server obtains updated MC service user profile data. +2. The configuration management server sends a notification for MC service user profile data update to the configuration management client. +3. The configuration management client sends get updated MC service user profile data request to the configuration management server, which includes the MC service ID. +4. The configuration management server sends get updated MC service user profile data response to the configuration management client which includes the updated MC service user profile data requested in step 3. + +NOTE: The updated MC service user profile data could be for a specific MC service user profile, a specific parameter in an MC service user profile, a set of MC service user profiles, or all the MC service user profiles for the MC service ID. MC service user profile data is defined per MC service. E.g. the MC service user profile data related to MCPTT is defined in 3GPP TS 23.379 [16]. + +#### 10.1.4.5 MC service user updates MC service user profile data to the network + +The procedure for MC service user updating the MC service user profile data (see 3GPP TS 23.379 [16]) is illustrated in figure 10.1.4.5-1. + +Pre-conditions: + +- The MC service user has performed user authentication in identity management server. +- The MC service UE has secure access to the configuration management server. +- The MC service UE has already obtained one or more MC service user profiles. + +![Sequence diagram illustrating the MC service user updates MC service user profile data to the network. The diagram shows two lifelines: 'Configuration management client' and 'Configuration management server'. The sequence of steps is: 1. Triggered to update MC service user profile data (on the client); 2. Update MC service user profile data request (client to server); 3. Store MC service user profile data (on the server); 4. Update MC service user profile data response (server to client).](9cb54072e43a6b6717eb16036a7640a2_img.jpg) + +``` +sequenceDiagram + participant Client as Configuration management client + participant Server as Configuration management server + Note left of Client: 1. Triggered to update MC service user profile data + Client->>Server: 2. Update MC service user profile data request + Note right of Server: 3. Store MC service user profile data + Server-->>Client: 4. Update MC service user profile data response +``` + +Sequence diagram illustrating the MC service user updates MC service user profile data to the network. The diagram shows two lifelines: 'Configuration management client' and 'Configuration management server'. The sequence of steps is: 1. Triggered to update MC service user profile data (on the client); 2. Update MC service user profile data request (client to server); 3. Store MC service user profile data (on the server); 4. Update MC service user profile data response (server to client). + +**Figure 10.1.4.5-1: MC service user updates MC service user profile data to the network** + +1. The configuration management client is triggered (e.g. by user interaction operation) to update the MC service user profile data on the configuration management server. +2. The configuration management client sends update MC service user profile data request to the configuration management server, which includes the MC service user profile data to be updated. +3. The configuration management server stores the received MC service user profile data. +4. The configuration management server sends update MC service user profile data response to the configuration management client to confirm the MC service user profile data update is complete. + +**NOTE:** The updated MC service user profile data could be for a specific MC service user profile, a specific parameter in an MC service user profile, a set of MC service user profiles, or all the MC service user profiles for the MC service ID. MC service user profile data is defined per MC service. E.g. the MC service user profile data related to MCPTT is defined in 3GPP TS 23.379 [16]. + +#### 10.1.4.6 Updating the pre-selected MC service user profile + +The procedure for updating the pre-selected MC service user profile in the configuration for an MC service UE by the MC service user is illustrated in figure 10.1.4.6-1. + +Pre-conditions: + +- The MC service user has performed user authentication in identity management server. +- The MC service UE has secure access to the configuration management server. +- The MC service UE has already obtained one or more MC service user profiles. +- The configuration management client is triggered (e.g. by user interaction, by some automated means) to change the pre-selected MC service user profile. + +![Sequence diagram illustrating the MC service user updates the pre-selected MC service user profile. The diagram shows two lifelines: 'Configuration management client' and 'Configuration management server'. The sequence of messages is: 1. Update pre-selected MCPTT user profile request (client to server), 2. Authorization check (server internal), 3. Store MCPTT user profile selection (server internal), and 4. Update pre-selected MCPTT user profile response (server to client).](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` + +sequenceDiagram + participant Client as Configuration management client + participant Server as Configuration management server + Note right of Server: 2. Authorization check + Note right of Server: 3. Store MCPTT user profile selection + Client->>Server: 1. Update pre-selected MCPTT user profile request + Server-->>Client: 4. Update pre-selected MCPTT user profile response + +``` + +Sequence diagram illustrating the MC service user updates the pre-selected MC service user profile. The diagram shows two lifelines: 'Configuration management client' and 'Configuration management server'. The sequence of messages is: 1. Update pre-selected MCPTT user profile request (client to server), 2. Authorization check (server internal), 3. Store MCPTT user profile selection (server internal), and 4. Update pre-selected MCPTT user profile response (server to client). + +**Figure 10.1.4.6-1: MC service user updates the pre-selected MC service user profile** + +1. The configuration management client sends update pre-selected MC service user profile request to the configuration management server, which includes the MC service user's MC service ID and an MC service user profile index that indicates which MC service user profile is to be pre-selected by the MC service server at next MC service authorization. +2. The configuration management server checks the authorization of the update pre-selected MC service user profile request. +3. The configuration management server stores the received pre-selected MC service user profile selection. +4. The configuration management server sends update pre-selected MC service user profile response to the configuration management client to confirm the pre-selected MC service user profile has been set. + +NOTE: Steps 3 to 4 can occur in any order or in parallel. + +For each update pre-selected MC service user profile request to the MC service user profile, the configuration management server determines whether the requested update is allowed prior to storing the configuration parameters and updating the MC service user database (via the CSC-13 reference point as specified in 3GPP TS 29.283 [19]). + +After each update to the MC service user profile in the MC service user database, the MC service server receives the changes from the MC service user profile database via the corresponding MC service reference point defined between MC service server and the MC service user database, and all of the MC service UEs associated with the MC service user receive the updated MC service user profile as specified in subclause 10.1.4.4. + +A change to the pre-selected MC service user profile while the MC service user is receiving MC service does not have any effect on the active MC service user profile, however, the change will be applied at the next MC service authorization. + +**Editor's note: Specifying pre-selected MC service user profile specific to each UE associated with an MC service user is FFS.** + +#### 10.1.4.7 Updating the selected MC service user profile for an MC service + +The procedure for updating the selected MC service user profile within a single MC service for an MC service UE by the MC service user whilst the MC service user is receiving that MC service service is illustrated in figure 10.1.4.7-1. This procedure is used by the following MC services: + +- MCPTT (as specified in 3GPP TS 23.379 [16]); +- MCVideo (as specified in 3GPP TS 23.281 [12]); and +- MCData (as specified in 3GPP TS 23.282 [13]). + +Pre-conditions: + +- For the MC service (see list above) for which the selected MC service user profile is to be updated: + - The MC service user has performed user authentication in the identity management server. + - The MC service UE has secure access to the MC service server. + - The MC service UE has already obtained multiple MC service user profiles. + - The MC service UE has performed MC service authorization. + - The MC service client is triggered (e.g. by user interaction, by some automated means) to select a particular MC service user profile as active. + +![Sequence diagram showing the interaction between an MC service client and an MC service server for updating a selected MC service user profile. The client sends a request (1) to the server. The server performs internal steps: 2. Obtain MC service user profile data, 3. Store active MC service user profile index, and 4. Obtain group configuration data. The server then sends a response (5) to the client. Finally, the client performs an internal step: 6. Obtain group configuration data.](b0988cfd9f60f2cd1916e3c2f9cae3da_img.jpg) + +``` +sequenceDiagram + participant Client as MC service client + participant Server as MC service server + Note right of Server: 2. Obtain MC service user profile data + Note right of Server: 3. Store active MC service user profile index + Note right of Server: 4. Obtain group configuration data + Note left of Client: 6. Obtain group configuration data + Client->>Server: 1. Updated selected MC service user profile request + Server-->>Client: 5. Update selected MC service user profile response +``` + +Sequence diagram showing the interaction between an MC service client and an MC service server for updating a selected MC service user profile. The client sends a request (1) to the server. The server performs internal steps: 2. Obtain MC service user profile data, 3. Store active MC service user profile index, and 4. Obtain group configuration data. The server then sends a response (5) to the client. Finally, the client performs an internal step: 6. Obtain group configuration data. + +**Figure 10.1.4.7-1: MC service user updates the selected MC service user profile** + +1. MC service client sends update selected MC service user profile request to the MC service server, which includes the MC service user's MC service ID and an MC service user profile index that indicates which MC service user profile is selected to be currently active for MC service client. +2. If the MPCTT server does not have stored the MC service user profile data for the MC service user, then the MC service server obtains the MC service user profile data. +3. The MC service server stores the selected MC service user profile index for the MC service client. + +NOTE 1: Different MC service user profiles can be active for different MC service clients of the same MC service user. + +4. If the MC service server does not have stored the group configuration data for the selected MC service user profile then the MC service server obtains group configuration data according to the selected MC service user profile (see subclause 10.1.5.2) and subscribes to updates of the group configuration data (see subclause 10.1.5.3). + +5. The MC service server sends update selected MC service user profile response to the MC service client to confirm the active MC service user profile has been set. + +NOTE 2: Steps 4 to 5 can occur in any order or in parallel. + +6. If the MC service client does not have stored the group configuration data for the selected MC service user profile then the MC service client obtains group configuration data according to the successfully selected MC + +service user profile (see subclause 10.1.5.2) and subscribes to updates of the group configuration data (see subclause 10.1.5.3). + +After each of the MC service server and the MC service UE have successfully negotiated a selected MC service user profile, then both the MC service server and the MC service UE, based upon the selected MC service user profile, clear any currently active service state from any previously selected or pre-selected MC service user profile data (including deaffiliating from relevant groups, disconnecting any MC service calls) and process the successfully negotiated selected MC service user profile data e.g. perform any needed affiliations. + +## 10.1.5 MC service group configuration management + +### 10.1.5.1 Store group configurations at the group management server + +The procedure for store group configurations at the group management server is described in figure 10.1.5.1-1. + +Pre-conditions: + +- The group management server may have some pre-configuration data which can be used for online group configuration validation; + +![Sequence diagram for storing group configurations at the group management server.](8fe84519a7da727cc2a27873b3389a52_img.jpg) + +``` +sequenceDiagram + participant Client as Group management client (Authorized user) + participant Server as Group management server + Note left of Client: 1. Receive group configurations + Client->>Server: 2. Store group configuration request + Note right of Server: 3. Validate group configurations + Note right of Server: 4. Store group configurations + Server->>Client: 5. Store group configuration response +``` + +The diagram is a sequence diagram illustrating the interaction between a Group management client (Authorized user) and a Group management server. The process starts with the client receiving group configurations (step 1). It then sends a 'Store group configuration request' to the server (step 2). The server performs internal steps: 'Validate group configurations' (step 3, shown in a dashed box) and 'Store group configurations' (step 4). Finally, the server sends a 'Store group configuration response' back to the client (step 5). + +Sequence diagram for storing group configurations at the group management server. + +**Figure 10.1.5.1-1: Store group configurations at group management server** + +1. The group configurations are received by the group management client of an authorized user. +2. The received group configurations are sent to the group management server for storage using a store group configuration request. +3. The group management server may validate the group configurations before storage. +4. The group management server stores the group configurations. +5. The group management server provides a store group configuration response indicating success or failure. If any validation or storage fails, the group management server provides a failure indication in the store group configuration response. + +### 10.1.5.2 Retrieve group configurations at the group management client + +The procedure for retrieve group configurations at the group management client is described in figure 10.1.5.2-1. This procedure can be used following service authorisation when the configuration management client has received the list of groups and the group management client needs to obtain the group configurations, or following a notification from the group management server that new group configuration information is available. + +Pre-conditions: + +- The group management server has received configuration data for groups, and has stored this configuration data; +- The MC service UE has registered for service and the group management client needs to download group configuration data applicable to the current user. + +![Sequence diagram for Figure 10.1.5.2-1: Retrieve group configurations at group management client. The diagram shows three steps: 1. Get group configuration request from client to server, 2. Get group configuration response from server to client, and 3. Store group configuration data at the client.](60a40901e77feeb97ab6cf9c6d9418c3_img.jpg) + +``` +sequenceDiagram + participant Client as Group management client + participant Server as Group management server + Note left of Client: 3. Store group configuration data + Client->>Server: 1. Get group configuration request + Server-->>Client: 2. Get group configuration response +``` + +Sequence diagram for Figure 10.1.5.2-1: Retrieve group configurations at group management client. The diagram shows three steps: 1. Get group configuration request from client to server, 2. Get group configuration response from server to client, and 3. Store group configuration data at the client. + +**Figure 10.1.5.2-1: Retrieve group configurations at group management client** + +1. The group management client requests the group configuration data. +2. The group management server provides the group configuration data to the client. +3. The group management client stores the group configuration information. + +### 10.1.5.3 Subscription and notification for group configuration data + +The procedure for subscription for group configuration data as described in figure 10.1.5.3-1 is used by the group management client to indicate to the group management server that it wishes to receive updates of group configuration data for groups for which it is authorized. + +Pre-conditions: + +- The group management server has some group configurations stored. + +![Sequence diagram for Figure 10.1.5.3-1: Subscription for group configurations. The diagram shows two steps: 1. Subscribe group configuration request from client to server, and 2. Subscribe group configuration response from server to client.](2226ff0a3945d72d56b5150c5618e71c_img.jpg) + +``` +sequenceDiagram + participant Client as Group management client + participant Server as Group management server + Client->>Server: 1. Subscribe group configuration request + Server-->>Client: 2. Subscribe group configuration response +``` + +Sequence diagram for Figure 10.1.5.3-1: Subscription for group configurations. The diagram shows two steps: 1. Subscribe group configuration request from client to server, and 2. Subscribe group configuration response from server to client. + +**Figure 10.1.5.3-1: Subscription for group configurations** + +1. The group management client subscribes to the group configuration information stored at the group management server using the subscribe group configuration request. +2. The group management server provides a subscribe group configuration response to the group management client indicating success or failure of the request. + +The procedure for notification of group configuration data as described in figure 10.1.5.3-2 is used by the group management server to inform the group management client that new group configuration data is available. It can also be used by the group management server to provide new group related key material to the group management client. + +Pre-conditions: + +- The group management client has subscribed to the group configuration information +- The group management server has received and stored new group configuration information, or the group management server has generated and stored new key material, or both of these have occurred. + +![Sequence diagram showing the notification of group configurations between a Group management client and a Group management server. The sequence is: 1. Notify group configuration request (server to client), 2. Notify group configuration response (client to server), 3. Store group key material (client internal action).](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +``` + +sequenceDiagram + participant Client as Group management client + participant Server as Group management server + Note left of Client: 3. Store group key material + Server->>Client: 1. Notify group configuration request + Client-->>Server: 2. Notify group configuration response + +``` + +Sequence diagram showing the notification of group configurations between a Group management client and a Group management server. The sequence is: 1. Notify group configuration request (server to client), 2. Notify group configuration response (client to server), 3. Store group key material (client internal action). + +**Figure 10.1.5.3-2: Notification of group configurations** + +1. The group management server provides the notification to the group management client, who previously subscribed for the group configuration information. Optionally, the notify group configuration request may contain group related key material for the group management client. +2. The group management client provides a notify group configuration response to the group management server. +3. If the group management server had provided group related key material to the group management client, the group management client stores the key material. + +If the group management server has notified the group management client about new group configuration information through this procedure, the group management client may then follow the procedure described in subclause 10.1.5.2 in order to retrieve that group configuration information. + +#### 10.1.5.4 Structure of group configuration data + +The group configuration data contains group configuration data common to all MC services and group configuration data specific to each MC service. All group configuration data is specified in Annex A.4 of the present document. + +#### 10.1.5.5 Dynamic data associated with a group + +There may be dynamic data associated with a group. The following dynamic data is known to the MC service server and provided when requested: + +**Table 10.1.5.5-1: Dynamic data associated with a group** + +| Parameter description | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Status i.e. indication of potential emergency or in-peril status of the group, together with the identification of the user who has performed the last modification of this status. | +| Affiliation status of each MC service ID of the group corresponding to the MC service and the Contact URI(s) from which the user affiliated. | +| Contact URIs used for designation of the group e.g. aliases of group broadcast, group regroup group URIs. | +| Media description for group media, including transport and multiplexing information. | +| Group call ongoing. | + +#### 10.1.5.6 Subscription and notification for dynamic data associated with a group + +An authorized user can request the current dynamic data for an MC service group on request. The dynamic data is described in subclause 10.1.5.5. + +### 10.1.5.6.1 Information flows for subscription and notification for dynamic data associated with a group + +#### 10.1.5.6.1.1 Subscribe group dynamic data request + +Table 10.1.5.6.1.1-1 describes the information flow subscribe group dynamic data request from the MC service client to the MC service server. + +**Table 10.1.5.6.1-1: Subscribe group dynamic data request** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------| +| MC service group ID | M | The MC service group ID for which dynamic data is requested. | + +#### 10.1.5.6.1.2 Subscribe group dynamic data response + +Table 10.1.5.6.1.2-1 describes the information flow subscribe group dynamic data response from the MC service server to the MC service client. + +**Table 10.1.5.6.1.2-1: Subscribe group dynamic data response** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------| +| MC service group ID | M | The MC service group ID for which dynamic data is requested. | +| Status | M | Success or failure of the request | + +#### 10.1.5.6.1.3 Notify group dynamic data request + +Table 10.1.5.6.1.3-1 describes the information flow notify group dynamic data response from the MC service server to the MC service client. + +**Table 10.1.5.6.1.3-1: Notify group dynamic data request** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------| +| MC service group ID | M | The MC service group ID for which dynamic data is requested. | +| Group dynamic data | M | Dynamic data associated with the group | + +#### 10.1.5.6.1.4 Notify group dynamic data response + +Table 10.1.5.6.1.4-1 describes the information flow notify group dynamic data response from the MC service client to the MC service server. + +**Table 10.1.5.6.1.4-1: Notify group dynamic data response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------| +| MC service group ID | M | The MC service group ID for which dynamic data was received | + +### 10.1.5.6.2 Procedure for subscription and notification for dynamic data associated with a group + +The procedure for subscription for dynamic data associated with an MC service group is described in figure 10.1.5.6.2-1 and is used by the MC service client of the authorized user to obtain the dynamic data from the MC service server. + +Pre-conditions: + +- The MC service server holds dynamic data associated with the MC service group. +- The MC service client is authorized to request the dynamic data associated with the MC service group. + +![Sequence diagram for subscription for group dynamic data](719ef0f734259484038b2434e5dc3f24_img.jpg) + +``` +sequenceDiagram + participant MC service client + participant MC service server + Note right of MC service server: 2. Authorize subscription request + MC service client->>MC service server: 1. Subscribe group dynamic data request + MC service server-->>MC service client: 3. Subscribe group dynamic data response +``` + +The diagram shows a sequence of three messages between an MC service client and an MC service server. The client sends a '1. Subscribe group dynamic data request' to the server. The server responds with '2. Authorize subscription request' (shown in a box on the server side) and then '3. Subscribe group dynamic data response' back to the client. + +Sequence diagram for subscription for group dynamic data + +**Figure 10.1.5.6.2-1: Subscription for group dynamic data** + +1. The MC service client subscribes to the group dynamic data stored in the MC service server using the subscribe group dynamic data request. +2. The MC service server checks that the MC service client is authorized to receive dynamic data associated with the MC service group. +3. The MC service server provides a subscribe group dynamic data response to the MC service client indicating success or failure of the request. + +The procedure for notification of group dynamic data as shown in figure 10.1.5.6.2-2 is used by the MC service server to inform the MC service client about new group dynamic data. + +Pre-conditions: + +- The MC service client has subscribed to the group dynamic data +- The MC service server has new group dynamic data available. + +![Sequence diagram for notification of group dynamic data](42f0611a8a2766c986ff45551918ca5d_img.jpg) + +``` +sequenceDiagram + participant MC service client + participant MC service server + MC service server->>MC service client: 1. Notify group dynamic data request + MC service client-->>MC service server: 2. Notify group dynamic data response +``` + +The diagram shows a sequence of two messages between an MC service server and an MC service client. The server sends a '1. Notify group dynamic data request' to the client, and the client responds with '2. Notify group dynamic data response' back to the server. + +Sequence diagram for notification of group dynamic data + +**Figure 10.1.5.6.2-2: Notification of group dynamic data** + +1. The MC service server provides the notification to the MC service client, who previously subscribed for the group dynamic data. +2. The MC service client provides a notify group dynamic data response to the MC service server. + +## 10.1.6 MC service UE migration + +### 10.1.6.1 MC service UE obtains migration connectivity information of partner MC system + +**Editor's note:** It is for FFS how the MC service UE obtains migration connectivity information. + +### 10.1.6.2 Signalling plane registration for the MC service UE between the primary and the partner MC systems + +The MC service UE performs the following procedure when connecting to a partner MC system for one or more MC services. + +Pre-conditions: + +1. The MC service UE has successfully obtained migration connectivity information for the partner MC system (see subclause 10.1.6.1). + +2. The MC service UE has successfully set-up bearers to the partner MC system's PDN(s). +3. The configuration management client has secure access to the configuration management server in the primary MC system. +4. The migration management server in the partner MC system has been configured with the mapping between the SIP identities of the partner MC system and the SIP identities of the primary MC system. + +![Sequence diagram showing MC service UE signalling plane registration in a partner MC system. The diagram involves three main entities: MC service UE (with Signalling user agent), Partner MC system (with SIP core and Migration management server), and Primary MC system (with Migration management server and SIP core). The sequence of messages is: 1. SIP registration request from UE to Partner SIP core; 2. Get SIP authentication information request from Partner SIP core to Partner Migration server; 3. Map SIP identities (internal to Partner Migration server); 4. Get SIP authentication information request from Partner Migration server to Primary Migration server; 5. Get SIP authentication information request from Primary Migration server to Primary SIP core; 6. Get SIP authentication information response from Primary SIP core to Primary Migration server; 7. Get SIP authentication information response from Primary Migration server to Partner Migration server; 8. Map SIP identities (internal to Partner Migration server); 9. Get SIP authentication information response from Partner Migration server to Partner SIP core; 10. SIP Authentication procedure (internal to Partner SIP core); 11. SIP registration response from Partner SIP core to UE.](04f7b8f64493f6d83188232f10f86fe2_img.jpg) + +``` + +sequenceDiagram + participant UE as MC service UE (Signalling user agent) + subgraph Partner MC system + direction TB + SIP_core[ SIP core ] + Migration_server[ Migration management server ] + end + subgraph Primary MC system + direction TB + Migration_server[ Migration management server ] + SIP_core[ SIP core ] + end + UE->>SIP_core: 1. SIP registration request + SIP_core->>Migration_server: 2. Get SIP authentication information request + Note right of Migration_server: 3. Map SIP identities + Migration_server->>Migration_server: 4. Get SIP authentication information request + Migration_server->>SIP_core: 5. Get SIP authentication information request + SIP_core-->>Migration_server: 6. Get SIP authentication information response + Migration_server-->>Migration_server: 7. Get SIP authentication information response + Note right of Migration_server: 8. Map SIP identities + Migration_server-->>SIP_core: 9. Get SIP authentication information response + Note right of SIP_core: 10. SIP Authentication procedure + SIP_core-->>UE: 11. SIP registration response + +``` + +Sequence diagram showing MC service UE signalling plane registration in a partner MC system. The diagram involves three main entities: MC service UE (with Signalling user agent), Partner MC system (with SIP core and Migration management server), and Primary MC system (with Migration management server and SIP core). The sequence of messages is: 1. SIP registration request from UE to Partner SIP core; 2. Get SIP authentication information request from Partner SIP core to Partner Migration server; 3. Map SIP identities (internal to Partner Migration server); 4. Get SIP authentication information request from Partner Migration server to Primary Migration server; 5. Get SIP authentication information request from Primary Migration server to Primary SIP core; 6. Get SIP authentication information response from Primary SIP core to Primary Migration server; 7. Get SIP authentication information response from Primary Migration server to Partner Migration server; 8. Map SIP identities (internal to Partner Migration server); 9. Get SIP authentication information response from Partner Migration server to Partner SIP core; 10. SIP Authentication procedure (internal to Partner SIP core); 11. SIP registration response from Partner SIP core to UE. + +**Figure 10.1.6.2-1: MC service UE signalling plane registration in a partner MC system** + +1. The signalling user agent sends a SIP registration request to the SIP core of the partner MC system, which includes the partner MC system SIP identities. + +NOTE 1: The signalling user agent uses the partner MC system SIP identities instead of the default SIP private user identity and default SIP public user identity obtained from the MC service UE's ISIM (as typically occurs when registering to the primary MC system). + +2. The SIP core in the partner MC system sends get SIP authentication information request to the migration management server also in the partner MC system, which includes the partner MC system SIP identities received in step 2. +3. The migration management server in the partner MC system, due to the binding created in the migration management server (see pre-condition 4), recognises the partner MC system SIP identities and determines the identifier of the MC service user's migration management server in the primary MC system and the primary MC system SIP identities. +4. The migration management server in the partner MC system sends get SIP authentication information request to the migration management server in the primary MC system, which includes the primary MC system SIP identities as determined in step 3. + +NOTE 2: The messaging in the above step traverses the SIP core / IMS of the partner MC system and the SIP core / IMS of the primary MC system. However, for brevity this is not shown in figure 10.1.6.2-1. + +5. The migration management server in the primary MC system sends get SIP authentication information request to the SIP database, via the SIP core / IMS, in the primary MC system, which includes the primary MC system SIP identities received in step 4. +6. The SIP database in the primary MC system recognises the primary MC system SIP identities and sends get SIP authentication information response to the migration management server, via the SIP core / IMS, in the primary MC system, which includes the primary MC system SIP identities and authentication information (e.g. authentication vectors). +7. The migration management server in the primary MC system sends get SIP authentication information request to the migration management server in the partner MC system, which includes the primary MC system SIP identities and authentication information received in step 6. + +NOTE 3: The messaging in the above step traverses the SIP core / IMS of the primary MC system and the SIP core / IMS of the partner MC system. However, for brevity this is not shown in figure 10.1.6.2-1. + +8. The migration management server in the partner MC system, due to the binding created in the migration management server (see pre-condition 4), recognises the primary MC system SIP identities, and determines the partner MC system SIP identities. +9. The migration management server in the partner MC system sends get SIP authentication information response to the SIP core also in the partner MC system, which includes the partner MC system SIP identities and the authentication information as received in step 7. +10. The SIP core and MC service UE perform the SIP authentication procedure. +11. The SIP core in the partner MC system sends SIP registration response to the signalling user agent in the MC service UE, which includes an indication that the authentication is successful. + +## 10.1.7 Functional alias configuration management + +### 10.1.7.1 Retrieve functional alias configurations from the functional alias management server + +The procedure for retrieve functional alias configurations from the functional alias management server is described in figure 10.1.7.1-1. This procedure can be used following service authorisation when the configuration management client has received the list of functional aliases and the functional alias management client needs to obtain the functional alias configurations, or following a notification from the functional alias management server that new functional alias configuration information is available. + +Pre-conditions: + +- The functional alias management server has received configuration data for functional aliases, and has stored this configuration data; +- The MC service UE has registered for service and the functional alias management client needs to download functional alias configuration data applicable to the current user. + +![Sequence diagram for Figure 10.1.7.1-1: Retrieve functional alias configurations from the functional alias management server. The diagram shows three steps: 1. Get functional alias configuration request from client to server, 2. Get functional alias configuration response from server to client, 3. Store functional alias configuration data within the client.](2f587210e4f97c32758c5972e2e83d20_img.jpg) + +``` +sequenceDiagram + participant Client as Functional alias management client + participant Server as Functional alias management server + Note left of Client: 3. Store functional alias configuration data + Client->>Server: 1. Get functional alias configuration request + Server-->>Client: 2. Get functional alias configuration response +``` + +Sequence diagram for Figure 10.1.7.1-1: Retrieve functional alias configurations from the functional alias management server. The diagram shows three steps: 1. Get functional alias configuration request from client to server, 2. Get functional alias configuration response from server to client, 3. Store functional alias configuration data within the client. + +**Figure 10.1.7.1-1: Retrieve functional alias configurations from the functional alias management server** + +1. The functional alias management client requests the functional alias configuration data. +2. The functional alias management server provides the functional alias configuration data to the client. +3. The functional alias management client stores the functional alias configuration information. + +## 10.1.7.2 Subscription and notification for functional alias configuration data + +The procedure for subscription for functional alias configuration data as described in figure 10.1.7.2-1 is used by the functional alias management client to indicate to the functional alias management server that it wishes to receive updates of functional alias configuration data for functional aliases for which it is authorized. + +Pre-conditions: + +- The functional alias management server has some functional alias configurations stored. + +![Sequence diagram for Figure 10.1.7.2-1: Subscription for functional alias configurations. The diagram shows two steps: 1. Subscribe functional alias configuration request from client to server, 2. Subscribe functional alias configuration response from server to client.](b385e39c8b32616bd23ad744a3f71cfa_img.jpg) + +``` +sequenceDiagram + participant Client as Functional alias management client + participant Server as Functional alias management server + Client->>Server: 1. Subscribe functional alias configuration request + Server-->>Client: 2. Subscribe functional alias configuration response +``` + +Sequence diagram for Figure 10.1.7.2-1: Subscription for functional alias configurations. The diagram shows two steps: 1. Subscribe functional alias configuration request from client to server, 2. Subscribe functional alias configuration response from server to client. + +**Figure 10.1.7.2-1: Subscription for functional alias configurations** + +1. The functional alias management client subscribes to the functional alias configuration information stored at the functional alias management server using the subscribe functional alias configuration request. +2. The functional alias management server provides a subscribe functional alias configuration response to the functional alias management client indicating success or failure of the request. + +The procedure for notification of functional alias configuration data as described in figure 10.1.7.2-1 is used by the functional alias management server to inform the functional alias management client that new functional alias configuration data is available. + +Pre-conditions: + +- The functional alias management client has subscribed to the functional alias configuration information +- The functional alias management server has received and stored new functional alias configuration information. + +![Sequence diagram showing notification of functional alias configurations between a client and a server.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +``` + +sequenceDiagram + participant Client as Functional alias management client + participant Server as Functional alias management server + Note left of Client: (Implicit) Subscription + Server->>Client: 1. Notify functional alias configuration request + Client-->>Server: 2. Notify functional alias configuration response + +``` + +Sequence diagram showing notification of functional alias configurations between a client and a server. + +**Figure 10.1.7.2-2: Notification of functional alias configurations** + +1. The functional alias management server provides the notification to the functional alias management client, who previously subscribed for the functional alias configuration information. +2. The functional alias management client provides a notify functional alias configuration response to the functional alias management server. + +If the functional alias management server has notified the functional alias management client about new functional alias configuration information through this procedure, the functional alias management client may then follow the procedure described in subclause 10.1.7.1 in order to retrieve that functional alias configuration information. + +## 10.2 Group management (on-network) + +### 10.2.1 General + +Group management procedures apply to on-network MC service only. + +Group creation provides a dedicated MC service group to individual MC service users to enable the required communication for one or multiple MC services. This includes the normal group creation by administrators as well as user regrouping by authorized user/dispatcher. + +For an MC service, group regrouping enables dispatchers or authorized users to temporarily combine several MC service groups. + +NOTE 1: If an authorized MC service user wants to participate in a new group created by the authorized MC service user, then the authorized MC service user needs to have been included in the new group as a member and have affiliated to the new group. + +NOTE 2: If an authorized MC service user wants to participate in a temporary group created by a group regroup operation performed by this authorized MC service user, then the authorized MC service user needs to have been an existing member of and affiliated to at least one of the constituent groups that was part of the associated group regroup operation and have affiliated to the new temporary group. + +### 10.2.2 Information flows for group management + +#### 10.2.2.1 Group creation request + +Table 10.2.2.1-1 describes the information flow group creation request from the group management client to the group management server. + +**Table 10.2.2.1-1: Group creation request** + +| Information element | Status | Description | +|----------------------------|---------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| +| MC service ID list | M | List of MC service IDs that are part of the group to be created corresponding to the list of the configured services | +| MC service list (see NOTE) | O | List of MC services whose service communications are to be enabled on the group. | +| NOTE: | This information element shall be included in the message for creating a group configured for multiple MC services. | | + +### 10.2.2.2 Group creation response + +Table 10.2.2.2-1 describes the information flow group creation response from the group management server to the group management client. + +**Table 10.2.2.2-1: Group creation response** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------|----------|----------------------------------| +| MC service group ID | M (NOTE) | MC service group ID of the group | +| NOTE: If the Result information element indicates failure then the value of MC service group ID information element has no meaning. | | | + +### 10.2.2.3 Group regroup request (group management client – group management server) + +Table 10.2.2.3-1 describes the information flow for the group regroup request from the group management client to the group management server. + +**Table 10.2.2.3-1: Group regroup request** + +| Information element | Status | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------| +| MC service group ID list | M | List of MC service group IDs to be combined | +| Security level (see NOTE 1) | O | Required security level for the temporary group | +| Priority level | O | Required priority level for the temporary group | +| MC service list (see NOTE 2) | O | A subset of the common MC service(s) to be applied for the regrouped group | +| NOTE 1: Security level refers to the configuration of media and floor control protection parameters as listed in Annex A.4, table A.4-1 | | | +| NOTE 2: If this information element is not present, all the MC service(s) that are common to the groups being regrouped will be applicable for the regrouped group. | | | + +### 10.2.2.4 Group regroup response (group management server – group management client) + +Table 10.2.2.4-1 describes the information flow for the group regroup response from the group management server to the group management client. + +**Table 10.2.2.4-1: Group regroup response** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|--------------------------------------------------------------------------------------------| +| MC service group ID | O (NOTE) | MC service group ID of the temporary group | +| MC service list | O | List of MC services whose service communications are to be enabled on this temporary group | +| Result | M | Indicates the success or failure of group regroup | +| NOTE: Shall be present if the Result information element indicates that the group regroup operation is successful. Otherwise MC service group ID shall not be present. | | | + +### 10.2.2.5 Group regroup teardown request + +Table 10.2.2.5-1 describes the information flow group regroup teardown request from the group management client to the group management server. + +**Table 10.2.2.5-1: Group regroup teardown request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the temporary group which is requested to be torn down | + +### 10.2.2.6 Group regroup teardown response + +Table 10.2.2.6-1 describes the information flow group regroup teardown response from the group management server to the group management client. + +**Table 10.2.2.6-1: Group regroup teardown response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the temporary group | +| Result | M | Indicates the success or failure of group regroup teardown | + +### 10.2.2.7 Group creation notify + +Table 10.2.2.7-1 describes the information flow group creation notify from the group management server to the MC service server(s). + +NOTE: When group is configured for multiple MC services, the group creation notify message is sent from the group management server to the MC service servers configured for the group. + +**Table 10.2.2.7-1: Group creation notify** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------------------| +| MC service group ID | M | MC service group ID that was created based on the MC service ID list and the MC services enabled on them | +| MC service ID list | M | List of MC service IDs that are part of the created group | + +### 10.2.2.8 Group regroup notify + +Table 10.2.2.8-1 describes the information flow group regroup notify from the group management server to the MC service server. + +**Table 10.2.2.8-1: Group regroup notify** + +| Information element | Status | Description | +|--------------------------|--------|---------------------------------------------------------------------------------------------| +| MC service group ID list | M | List of constituent MC service group IDs | +| MC service group ID | M | MC service group ID of the temporary group | +| MC service list | O | List of MC services whose service communications are to be enabled on this temporary group. | + +### 10.2.2.9 Group regroup teardown notify + +Table 10.2.2.9-1 describes the information flow group regroup teardown notify from the group management server to the MC service server. + +**Table 10.2.2.9-1: Group regroup teardown notify** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the temporary group which is being torn down | + +### 10.2.2.10 Group regroup teardown notification + +Table 10.2.2.10-1 describes the information flow group regroup teardown notification between group management servers. + +**Table 10.2.2.10-1: Group regroup teardown notification** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the temporary group which is torn down | + +### 10.2.2.11 Group regroup teardown notification response + +Table 10.2.2.11-1 describes the information flow group regroup teardown notification response between group management servers. + +**Table 10.2.2.11-1: Group regroup teardown notification response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the temporary group which was torn down | +| Result | M | Indicates the success or failure | + +### 10.2.2.12 Group regroup request (group management server – group management server) + +Table 10.2.2.12-1 describes the information flow group regroup request between group management servers. + +**Table 10.2.2.12-1: Group regroup request** + +| Information element | Status | Description | +|--------------------------|--------|------------------------------------------------------------------------------------------| +| MC service group ID list | M | List of constituent MC service group IDs belonging to the target group management server | + +### 10.2.2.13 Group regroup response (group management server – group management server) + +Table 10.2.2.13-1 describes the information flow group regroup response between group management servers. + +**Table 10.2.2.13-1: Group regroup response** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------| +| Result | M | Indicates whether the group regroup was accepted or rejected by the group management server in the partner system | +| MC service group ID list | M | List of constituent MC service group IDs from group management server of the partner system | + +### 10.2.2.14 Group regroup notification + +Table 10.2.2.14-1 describes the information flow group regroup notification between group management servers. + +**Table 10.2.2.14-1: Group regroup notification** + +| Information element | Status | Description | +|---------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------| +| MC service group ID list | M | List of constituent MC service group IDs | +| MC service group ID | M | MC service group ID of the temporary group | +| Priority level | O | Required priority level for the temporary group | +| Security level (see NOTE) | O | Required security level for the temporary group | +| NOTE: | | Security level refers to the configuration of media and floor control protection parameters as listed in Annex A.4, table A.4-1 | + +### 10.2.2.15 Group regroup notification response + +Table 10.2.2.15-1 describes the information flow group regroup notification response between group management servers. + +**Table 10.2.2.15-1: Group regroup notification response** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------| +| MC service group ID list | M | List of constituent MC service group IDs | +| MC service group ID | M | MC service group ID of the temporary group | +| Priority level | M | Required priority level for the temporary group | +| Security level | M | Required security level for the temporary group | + +## 10.2.2.16 Group information query request + +Table 10.2.2.16-1 describes the information group information query request from group management client to group management server. + +**Table 10.2.2.16-1: Group information query request** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user who performs the query. | +| MC service group ID | M | The identity of the MC service group to be queried. | +| Query type | M | It indicates the query type, i.e., membership or affiliated group members. | + +## 10.2.2.17 Group information query response + +Table 10.2.2.17-1 describes the information group information query response from group management server to group management client. + +**Table 10.2.2.17-1: Group information query response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user who performs the query. | +| MC service group ID | M | The identity of the MC service group to be queried. | +| Query type | M | It indicates the query type, e.g., membership or affiliated group members. | +| Query result | M | The group information retrieved from the group management server based on the query type, i.e., a list of group members or a list of affiliated group member. | + +## 10.2.2.18 Group membership update request + +Table 10.2.2.18-1 describes the information flow group membership update request from the group management client to the group management server. + +**Table 10.2.2.18-1: Group membership update request** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------------------| +| MC service group ID | M | Identity of the MC service group | +| MC service ID list | M | List of identities of the MC service users that are affected by this operation | +| Operations | M | Add to or delete from the group | + +## 10.2.2.19 Group membership update response + +Table 10.2.2.19-1 describes the information flow group membership update response from the group management server to the group management client. + +**Table 10.2.2.19-1: Group membership update response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------| +| MC service group ID | M | Identity of the MC service group | +| Result | M | Indicates the success or failure for the operation | + +## 10.2.2.20 Group membership notification + +Table 10.2.2.20-1 describes the information flow group membership notification from the group management server to the MC service server. + +**Table 10.2.2.20-1: Group membership notification** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------------------| +| MC service group ID | M | Identity of the MC service group | +| MC service ID list | M | List of identities of the MC service users that are affected by this operation | +| Operations | M | Add to or delete from the group | + +Table 10.2.2.20-2 describes the information flow group membership notification from the group management server to the group management client. + +**Table 10.2.2.20-2: Group membership notification** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------| +| MC service group ID | M | Identity of the MC service group | +| Operations | M | Add to or delete from the group | + +## 10.2.2.21 Group deletion request + +Table 10.2.2.21-1 describes the information flow group deletion request from the group management client to the group management server. + +**Table 10.2.2.21-1: Group deletion request** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------| +| MC service group ID | M | MC service group ID of the group to delete | + +## 10.2.2.22 Group deletion response + +Table 10.2.2.22-1 describes the information flow group deletion response from the group management server to the group management client. + +**Table 10.2.2.22-1: Group deletion response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------| +| MC service group ID | M | Identity of the MC service group requested deleted | +| Result | M | Indicates success (group no longer exists), or failure (group deletion did not occur, eg. authorization failure). | + +## 10.2.2.23 Group deletion notification + +Table 10.2.2.23-1 describes the information flow group deletion notification from the group management server to the MC service server, and from the group management server to the group management clients for MC service users which are members of the group. + +**Table 10.2.2.23-1: Group deletion notification** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------| +| MC service group ID | M | MC service group ID has been deleted. | + +## 10.2.2.24 Group information provision request + +Table 10.2.2.24-1 describes the information flow group information provision request from the group management server in the primary MC system of the MC service group to the group management server in the partner MC system of the MC service group. + +**Table 10.2.2.24-1: Group information provision request** + +| Information element | Status | Description | +|--------------------------------------------|--------|----------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| MC service group configuration information | M | Configuration information for the MC service group | + +## 10.2.2.25 Group information provision response + +Table 10.2.2.25-1 describes the information flow group information provision response from the group management server in the partner MC system of the MC service group to the group management server in the primary MC system of the MC service group. + +**Table 10.2.2.25-1: Group information provision response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| Result | M | Indicates success or failure of reception, modification and storage of MC service group configuration information | + +## 10.2.2.26 Group information request + +Table 10.2.2.26-1 describes the information flow group information request from the group management server in the partner MC system of the MC service group to the group management server in the primary MC system of the MC service group. + +**Table 10.2.2.26-1: Group information request** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------| +| MC service group ID | M | MC service group ID of the group | + +## 10.2.2.27 Group information response + +Table 10.2.2.27-1 describes the information flow group information response from the group management server in the primary MC system of the MC service group to the group management server in the partner MC system of the MC service group. + +**Table 10.2.2.27-1: Group information response** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| MC service group configuration information | O (NOTE 1) | Configuration information for the MC service group | +| Failure reason | O (NOTE 2) | Indicates reason for failure to provide MC service group configuration information | +| NOTE 1: Shall be present if the request can be fulfilled by the group management server in the primary MC system of the MC service group. | | | +| NOTE 2: Shall be present if the request cannot be fulfilled by the group management server in the primary MC system of the MC service group. | | | + +### 10.2.2.28 Group information subscribe request + +Table 10.2.2.28-1 describes the information flow group information subscribe request from the group management server in the partner MC system of the MC service group to the group management server in the primary MC system of the MC service group. + +**Table 10.2.2.28-1: Group information subscribe request** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------| +| MC service group ID | M | MC service group ID of the group | + +### 10.2.2.29 Group information subscribe response + +Table 10.2.2.29-1 describes the information flow group information subscribe response from the group management server in the primary MC system of the MC service group to the group management server in the partner MC system of the MC service group. + +**Table 10.2.2.29-1: Group information subscribe response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| Result | M | Indicates success or failure of the subscribe request | + +### 10.2.2.30 Group information notify request + +Table 10.2.2.30-1 describes the information flow group information notify request from the group management server in the primary MC system of the MC service group to the group management server in the partner MC system of the MC service group. + +**Table 10.2.2.30-1: Group information notify request** + +| Information element | Status | Description | +|--------------------------------------------|--------|----------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| MC service group configuration information | M | Configuration information for the MC service group | + +### 10.2.2.31 Group information notify response + +Table 10.2.2.31-1 describes the information flow group information notify response from the group management server in the partner MC system of the MC service group to the group management server in the primary MC system of the MC service group. + +**Table 10.2.2.31-1: Group information notify response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| Result | M | Indicates success or failure of the notification request | + +## 10.2.3 Group creation + +Figure 10.2.3-1 below illustrates the group creation operations by authorized MC service user/ MC service administrator to create a group. It applies to the scenario of normal group creation by an MC service administrator and user regrouping operations by authorized user/dispatcher. + +Pre-conditions: + +1. The group management client, group management server, MC service server and the MC service group members belong to the same MC system. + +2. The administrator/authorized user/dispatcher is aware of the users' identities which will be combined to form the MC service group. + +![Sequence diagram for Group creation. Lifelines: Group management client (Administrator/authorized user/dispatcher), Group management server, Group management client (MC service group members), and MC service server. The sequence of messages is: 1. Group creation request from client to server; 2. Create and store the group related information (internal server action); 3. Group creation notify from server to MC service server; 4. Notify the users (internal server action); 5. Group creation response from server to client.](145fb9b19dc6513e7bf84c9ba7f083f2_img.jpg) + +``` + +sequenceDiagram + participant Client as Group management client (Administrator/authorized user/dispatcher) + participant Server as Group management server + participant Members as Group management client (MC service group members) + participant MCServer as MC service server + + Note right of Server: 2. Create and store the group related information + Note right of Members: 4. Notify the users + + Client->>Server: 1. Group creation request + Server-->>MCServer: 3. Group creation notify + Server-->>Client: 5. Group creation response + +``` + +Sequence diagram for Group creation. Lifelines: Group management client (Administrator/authorized user/dispatcher), Group management server, Group management client (MC service group members), and MC service server. The sequence of messages is: 1. Group creation request from client to server; 2. Create and store the group related information (internal server action); 3. Group creation notify from server to MC service server; 4. Notify the users (internal server action); 5. Group creation response from server to client. + +Figure 10.2.3-1: Group creation + +1. The group management client of the administrator/dispatcher/authorized MC service user requests group create operation to the group management server. The identities of the users being combined and the information of the MC services that are enabled on the group shall be included in this message. +2. During the group creation, the group management server creates and stores the information of the group as group configuration data as described in subclause 10.1.5.4. The group management server performs the check on the maximum limit of the total number (Nc6) of MC service group members for the MC service group(s). +3. The group management server may conditionally notify the MC service server regarding the group creation with the information of the group members. During user regroup, the group management server notifies the MC service server regarding the group creation with the information of the temporary group members. The MC service users of the temporary group may be automatically affiliated, if configured on the MC service server. +4. The MC service group members of the MC service group are notified about the newly created MC service group configuration data. +5. The group management server provides a group creation response to the group management client of the administrator/dispatcher/authorized MC service user. + +## 10.2.4 Group regrouping + +### 10.2.4.1 Temporary group formation - group regrouping within an MC system + +Figure 10.2.4.1-1 below illustrates the group regroup operations to create a temporary group within an MC system. For simplicity, only the case of two MC service groups being combined is represented, but the procedure is the same if more than two groups are combined. + +The temporary group formation is applicable only for groups configured with at least one common MC service. The temporary group formation shall be rejected if any of the requested MC services are not common to all MC service groups in the list. + +Pre-conditions: + +1. The group management client, group management server, MC service server and the MC service group members belong to the same MC system. + +- 2. The group management client has retrieved the group configurations of the groups to be regrouped. + +![Sequence diagram for group regrouping within the same MC system. Lifelines: Group management client, Group management server, Group management client (MC service group members), and MC service server. The sequence shows a request, authorization check, storage, notification to server, notification to members, and a response.](f7b2cf9e1b71dc4f900f3810646d3903_img.jpg) + +``` + +sequenceDiagram + participant GMC as Group management client + participant GMS as Group management server + participant GMC_M as Group management client (MC service group members) + participant MSS as MC service server + + Note right of GMS: 2. Authorization check based on group policy and check whether group1 or group2 is a temporary group + Note right of GMS: 3. Create and store the temporary group related information + + GMC->>GMS: 1. Group regroup Request + GMS->>GMS: 2. Authorization check based on group policy and check whether group1 or group2 is a temporary group + GMS->>GMS: 3. Create and store the temporary group related information + GMS->>MSS: 4. Group regroup notify + GMS->>GMC_M: 5. Notify the affiliated users + GMS->>GMC: 6. Group regroup response + +``` + +Sequence diagram for group regrouping within the same MC system. Lifelines: Group management client, Group management server, Group management client (MC service group members), and MC service server. The sequence shows a request, authorization check, storage, notification to server, notification to members, and a response. + +Figure 10.2.4.1-1: Group regroup for the groups within the same MC system + +- 1. The group management client of the MC service user requests group regroup operation to the group management server, which is the group management server of one of the groups to be regrouped. The identities of the groups being combined shall be included in this message. The group management client may indicate the security level required for the temporary group. The group management client may indicate the priority level required for the temporary group. +- 2. The group management server checks whether group regroup operation is performed by an authorized MC service user, based on group policy. The group management server checks whether group1 or group2 is a temporary group. If group 1 or group2 is a temporary group, then the group regrouping will be rejected, otherwise the group regrouping can proceed. +- 3. The group management server creates and stores the information of the temporary group, including the temporary MC service group ID, the MC service group ID of the groups being combined, the priority level of the temporary group and the security level of the temporary group. If the authorized MC service user does not specify the security level and the priority level, the group management server shall set the lowest security level and the highest priority of the constituent groups. If MC service types of the groups being combined are not identical, group management server determines the overlapping part and stores the MC service list for the temporary group. +- 4. The group management server notifies the MC service server regarding the temporary group creation with the information of the constituent groups, i.e. temporary MC service group ID, group1's MC service group ID and group2's MC service group ID. If MC service list is included, MC service server stores it and provides MC service types accordingly. +- 5. The group management server notifies the affiliated MC service group members of the constituent MC service groups, possibly with an indication of lower security level. +- 6. The group management server provides a group regroup response to the group management client of the authorized MC service user. If MC service list is included, group management client stores it and initiates MC service types accordingly. + +### 10.2.4.2 Temporary group formation involving multiple MC systems + +Figure 10.2.4.2-1 below illustrates the group regroup operations to create a temporary group involving multiple MC systems. For simplicity, only the case of two MC service groups being combined is represented, but the procedure is the same if more than two groups are combined. + +NOTE: The temporary group formation is applicable only for groups configured with the same MC service(s). + +Pre-conditions: + +1. The security aspects of sharing the user information between primary and partner MC systems shall be governed as per the service provider agreement between them. In this case, we consider the partner MC system does not share their users' information to the primary MC system. +2. The primary MC system consists of the group management server 1 and MC service server (primary). The partner MC system consists of the group management server 2 and MC service server (partner). +3. The group management client of the authorized MC service user belongs to the primary MC system. +4. The group management client has retrieved the group configurations of the groups to be regrouped. + +![Sequence diagram showing the interaction for temporary group formation involving multiple MC systems. Lifelines include: Group management client, Group management server 1, Group management client (Primary group members), MC service server (Primary), Group management server 2, Group management client (Partner group members), and MC service server (Partner). The process involves a regroup request, authorization checks, forwarding the request, notifications, and a final response.](333992a0b3b7a9d826f72f7bf199221b_img.jpg) + +``` + +sequenceDiagram + participant GGC as Group management client + participant GMS1 as Group management server 1 + participant GGC_P as Group management client (Primary group members) + participant MSS_P as MC service server (Primary) + participant GMS2 as Group management server 2 + participant GGC_R as Group management client (Partner group members) + participant MSS_R as MC service server (Partner) + + Note left of GGC: 1.Group regroup request + GGC->>GMS1: 1.Group regroup request + Note right of GMS1: 2.Authorization check based on group policy and check whether group1 is a temporary group + GMS1->>GMS2: 3.Group regroup request + Note right of GMS2: 4.Check whether group2 is a temporary group + GMS2->>GMS1: 5.Group regroup response + Note right of GMS1: 6.Create and store temporary group related information + GMS1->>GMS2: 7.Group regroup notification + GMS2->>GMS1: 8.Group regroup notification response + GMS1->>MSS_P: 12.Group regroup notify + GMS2->>MSS_R: 9.Group regroup notify + MSS_P->>GMS1: 13.Group regroup notify response + MSS_R->>GMS2: 10.Group regroup notify response + Note right of GMS1: 14.Notify the affiliated users + Note right of GMS2: 11.Notify the affiliated users + GMS1->>GGC: 15.Group regroup response + +``` + +Sequence diagram showing the interaction for temporary group formation involving multiple MC systems. Lifelines include: Group management client, Group management server 1, Group management client (Primary group members), MC service server (Primary), Group management server 2, Group management client (Partner group members), and MC service server (Partner). The process involves a regroup request, authorization checks, forwarding the request, notifications, and a final response. + +Figure 10.2.4.2-1: Temporary group formation - group regrouping involving multiple MC systems + +1. The group management client of the MC service user (e.g. dispatcher) requests group regroup operation to the group management server 1 (which is the group management server of one of the groups to be regrouped). The identities of the groups being combined shall be included in this message. The group management client may indicate the security level required for the temporary group. The group management client may indicate the priority level required for the temporary group. +2. The group management server checks whether group regroup operation is performed by an authorized MC service user, based on group policy. The group management server 1 checks whether group1 is a temporary group. If group1 is a temporary group, then the group regrouping will be rejected, otherwise the group regrouping can proceed. +3. The group management server 1 forwards the group regroup request to the target group management server 2 with the information of the group management server 2 MC service groups. +4. The group management server 2 checks whether group2 is a temporary group. If group2 is a temporary group, then the group regrouping will be rejected, otherwise the group regrouping can proceed. +5. The group management server 2 provides a group regroup response. Due to security aspects concerning sharing information among different MC systems, the group management server 2 does not share the users' information of the groups under its management to the group management server 1. Any regroup action that violates the rules specified in subclause 10.2.4.4 shall cause a negative response and the current procedure to proceed to step 15. + +- NOTE: If there is a trust relationship between the primary MC service provider and the partner MC service provider, the partner MC system can share their users' information to the primary MC system at this step. If there is a change in partner MC system's constituent group membership, the synchronization procedure with the primary MC system for temporary group is out of scope of this specification +6. The group management server 1 creates and stores the information of the temporary group, including the temporary MC service group ID, off-network information, and the MC service IDs of the groups being combined, the priority level of the temporary group, and the security level of the temporary group. If the authorized MC service user does not specify the security level and the priority level, the group management server shall set the lower security level and the higher priority of the constituent groups. + 7. The group management server 1 notifies the group management server 2 about its group regroup operation. + 8. The group management server 2 acknowledges the group management server 1 and the group management server 2 also stores the information about the temporary group including the temporary MC service group ID, the MC service group IDs of the groups being combined, the priority level of the temporary group and the security level of the temporary group. + 9. The group management server 2 notifies the partner MC service server regarding the temporary group creation with the information of the constituent groups i.e. temporary MC service group ID, group1's MC service group ID and group2's MC service group ID. + 10. Partner MC service server acknowledges the notification from the group management server 2. + 11. The group management server 2 notifies the affiliated MC service group members of the constituent MC service groups of the group management server 2, possibly with an indication of a lower security level. + 12. The group management server 1 notifies the MC service server of the primary system regarding the temporary group creation with the information of the constituent groups, i.e. temporary MC service group ID, group1's MC service group ID and group2's MC service group ID. If there are active calls to be merged then the group management server 1 includes an indication to merge active calls. + 13. Primary MC service server acknowledges the notification from the group management server 1. + 14. The group management server 1 notifies the affiliated MC service group members of the constituent MC service groups of the group management server 1, possibly with an indication of lower security level. + 15. The group management server 1 provides a group regroup response to the group management client of the authorized MC service user (e.g. dispatcher). + +#### 10.2.4.3 Temporary group tear down involving multiple group host servers + +Figure 10.2.4.3-1 below illustrates the tearing down procedure of temporary group created through the group regroup operation. The procedure can be used when, e.g., the specific task for which the temporary group was created has been completed or a busier period occurs. For simplicity, only the teardown case for a temporary group with two MC service groups is represented. The procedure is applicable for more than two groups combined in this temporary group. + +Pre-conditions: + +1. The security aspects of sharing the user information between primary and partner MC systems shall be governed as per the service provider agreement between them. In this case, it considers the partner MC system does not share their users' information to the primary MC system. + +2. The primary MC system consists of the group management server 1 and MC service server (primary). The partner MC system consists of the group management server 2 and MC service server (partner). +3. The group management client of the authorized MC service user belongs to the primary MC system. +4. The temporary group to be torn down is comprised of multiple MC service groups, and is created through the group regrouping procedure as described in subclause 10.2.4.2. + +![Sequence diagram for Temporary group tear down. Lifelines: Group management client, Group management server 1, Group management client (Primary group members), MC service server (Primary), Group management server 2, Group management client (Partner group members), MC service server (Partner). The sequence starts with a request from the client to server 1, followed by internal checks and completion of active calls. Server 1 then tears down the group and notifies the primary MC service server and affiliated users. Server 1 also sends notifications to server 2, which in turn notifies the partner MC service server and its affiliated users. Finally, server 1 sends a response back to the client.](820515db47ded68f5e0b625f4ec7d2c1_img.jpg) + +``` + +sequenceDiagram + participant Client as Group management client + participant Server1 as Group management server 1 + participant Members1 as Group management client (Primary group members) + participant PrimaryMC as MC service server (Primary) + participant Server2 as Group management server 2 + participant Members2 as Group management client (Partner group members) + participant PartnerMC as MC service server (Partner) + + Note right of Client: 1.Group regroup teardown request + Client->>Server1: 1.Group regroup teardown request + Note right of Server1: 2.Authorization check based on group policy and check whether group ID is a temporary group + Note right of Server1: 3.Any active group call for the temporary group is completed + Note right of Server1: 4.Tear down the temporary group and remove temporary group related information + Server1->>PrimaryMC: 5.Group regroup teardown notify + Note right of Server1: 6.Notify the affiliated users of the group + Server1->>Server2: 7a.Group regroup teardown notification + Server2->>Server1: 7b.Group regroup teardown notification + Server2->>PartnerMC: 8.Group regroup teardown notify + Note right of Server2: 9.Notify the affiliated users of the group + Server1->>Client: 10.Group regroup teardown response + +``` + +Sequence diagram for Temporary group tear down. Lifelines: Group management client, Group management server 1, Group management client (Primary group members), MC service server (Primary), Group management server 2, Group management client (Partner group members), MC service server (Partner). The sequence starts with a request from the client to server 1, followed by internal checks and completion of active calls. Server 1 then tears down the group and notifies the primary MC service server and affiliated users. Server 1 also sends notifications to server 2, which in turn notifies the partner MC service server and its affiliated users. Finally, server 1 sends a response back to the client. + +**Figure 10.2.4.3-1: Temporary group tear down** + +1. The group management client of the MC service user requests group regroup teardown operation to the group management server 1 (which is the group management server where the temporary group is created and stored). The identity of the temporary group (MC service group ID) being torn down shall be included in this message. This message may route through some other signalling nodes. +2. The group management server checks whether group regroup operation is performed by an authorized MC service user, based on group policy. The group management server 1 checks whether the MC service group ID is a temporary group. If MC service group ID is not a temporary group, then the group regroup teardown request will be rejected, otherwise the group regroup teardown can proceed. +3. Any active group call for the temporary group is completed. +4. The group management server 1 tears down the temporary group, i.e., remove the temporary group related information. +5. The group management server 1 notifies the primary MC service server regarding the temporary group teardown. +6. The group management server 1 notifies the affiliated MC service group members regarding the temporary group teardown. +7. The group management server 1 sends a group regroup teardown notification (7a) and receives a group regroup teardown notification response (7b) messages with the group management server 2 – group management server in another MC system regarding the temporary group teardown. +- 8-9. The group management server 2 notifies the partner MC service server and the affiliated MC service group members regarding the temporary group teardown. + +NOTE: Step 7, 8 and 9 are only performed when the teardown of the temporary group involves constituent groups from different MC systems. + +10. The group management server 1 provides a group regroup teardown confirmation response to the group management client of the authorized MC service user. + +#### 10.2.4.4 Group regroup rules + +To prevent routing issues and complexity related to group regrouping, the following rules shall be applied: + +- If security policy of the MC system allows a temporary group to include groups from other primary MC systems, group regrouping containing groups with multiple MC systems can only take place if: + - none of the groups to be regrouped are temporary groups; and + - the groups to be regrouped are not already regrouped into another temporary group; and + - the MC service server in which the regrouping is performed is the MC service server (controlling role) for all MC service groups involved in the regrouping; or + - the MC service server in which the regrouping is performed is an MC service server (participating role) for at least one of the MC service groups and the primary MC system of at least one MC service group allows floor control for the set of regrouped groups to be deferred to the MC service server (controlling role) of the temporary group. +- If security policy of the MC system does not allow a temporary group to include groups from other MC systems, regrouping of groups with members spanning multiple MC systems can only take place if: + - none of the groups to be regrouped are temporary groups; + - the groups to be regrouped are not already regrouped into another temporary group; and + - the MCPTT system in which the regrouping is performed is the MC service server (controlling role) for all MC service groups involved in the regrouping. + +### 10.2.5 Membership and affiliation list query + +#### 10.2.5.1 General + +An MC service user can request the membership or affiliation list on an MC service group regardless the user's group membership or affiliation. + +#### 10.2.5.2 Procedure + +Figure 10.2.5.2-1 below illustrates the membership or affiliation list query on an MC service group. + +![Sequence diagram illustrating the membership or affiliation list query procedure. The diagram shows three steps: 1. Group management client sends a 'Group information query request' to the Group management server. 2. The Group management server performs an 'Authorization check and retrieve according to the conditions'. 3. The Group management server sends a 'Group information query response' back to the Group management client.](a2dc8d6396228142d4c2c1d3160b47dc_img.jpg) + +``` +sequenceDiagram + participant Client as Group management client + participant Server as Group management server + Note right of Server: 2. Authorization check and retrieve according to the conditions + Client->>Server: 1. Group information query request + Server-->>Client: 3. Group information query response +``` + +Sequence diagram illustrating the membership or affiliation list query procedure. The diagram shows three steps: 1. Group management client sends a 'Group information query request' to the Group management server. 2. The Group management server performs an 'Authorization check and retrieve according to the conditions'. 3. The Group management server sends a 'Group information query response' back to the Group management client. + +Figure 10.2.5.2-1: membership or affiliation list query + +1. The group management client of the MC servicer user requests the membership or affiliation list on the MC service group from the group management server by sending a group information query request. The query type is included. +2. The group management server checks whether the MC servicer user is authorized to perform the query. If authorized, then the group management server retrieve the requested group information based on the query type. +3. The group management server sends a group information query response including the retrieved group information to the group management client. + +### 10.2.6 Group membership + +#### 10.2.6.1 Group membership notification + +Figure 10.2.6.1-1 illustrates the group membership notification operations to the MC service server(s) and group management clients upon the group membership change at group management server. + +Pre-conditions: + +1. The group management server and MC service server serve the same MC system. + +![Sequence diagram for group membership notification. Lifelines: Group management client, Group management server, MC service server. The sequence starts with a dashed box '4. Retrieve group configuration' between the client and server. Step 1: '1. Group membership changed' is a self-call on the server. Step 2: '2. Group membership notification' is sent from the server to the MC service server. Step 3: '3. Group membership notification' is sent from the server to the client.](f89631cc38aa971e8d15cbffe28f1183_img.jpg) + +``` + +sequenceDiagram + participant Client as Group management client + participant Server as Group management server + participant MCServer as MC service server + Note left of Client: 4. Retrieve group configuration + Note right of Server: 1. Group membership changed + Server->>MCServer: 2. Group membership notification + Server->>Client: 3. Group membership notification + +``` + +Sequence diagram for group membership notification. Lifelines: Group management client, Group management server, MC service server. The sequence starts with a dashed box '4. Retrieve group configuration' between the client and server. Step 1: '1. Group membership changed' is a self-call on the server. Step 2: '2. Group membership notification' is sent from the server to the MC service server. Step 3: '3. Group membership notification' is sent from the server to the client. + +Figure 10.2.6.1-1: group membership notification + +1. The membership of a specific MC service group is changed at group management server. +2. The group management server notifies the MC service server(s) regarding the group membership change with the information of the updated group members. +3. The group management server updates the group management clients of the MC service users who have been added to or removed from the group. +4. The group management client requests to retrieve the relevant group configurations from group management server by procedure defined in subclause 10.1.5.2, if the user is added to the group. If the user is deleted from the group, the locally stored group configurations in the MC service UE may be removed. + +#### 10.2.6.2 Group membership update by authorized user + +Figure 10.2.6.2-1 below illustrates the group membership update operations by an authorized user/administrator/dispatcher to change the membership a MC service group (e.g. to add or delete group members). + +Pre-conditions: + +1. The group management server and MC service server serve the same MC system; +2. The initiator of this operation is aware of the current group membership of the MC service group; + +3. The Administrator/dispatcher/authorized user is aware of the users' identities which will be added to or deleted from the MC service group. + +![Sequence diagram for Group membership update by authorized user. Lifelines: Group management client (Administrator/authorized user/dispatcher), Group management server, Group management client (MC service group members), and MC service server. The sequence is: 1. Request from client 1 to server; 2. Update from server to client 1; 3. Notification from server to server; 4. Notify the users (internal server action); 5. Response from server to client 1.](d62e2e2281009c16f4ee61660e716cd9_img.jpg) + +``` + +sequenceDiagram + participant Client1 as Group management client (Administrator/authorized user/dispatcher) + participant Server as Group management server + participant Client2 as Group management client (MC service group members) + participant MCServer as MC service server + + Client1->>Server: 1. Group membership update request + Server-->>Client1: 2. Group membership update + Server->>MCServer: 3. Group membership notification + Note right of Server: 4. Notify the users + Server-->>Client1: 5. Group membership update response + +``` + +Sequence diagram for Group membership update by authorized user. Lifelines: Group management client (Administrator/authorized user/dispatcher), Group management server, Group management client (MC service group members), and MC service server. The sequence is: 1. Request from client 1 to server; 2. Update from server to client 1; 3. Notification from server to server; 4. Notify the users (internal server action); 5. Response from server to client 1. + +**Figure 10.2.6.2-1: Group membership update by authorized user** + +1. The group management client of the administrator/dispatcher/authorized user requests group membership update operation to the group management server. +2. The group management server updates the group membership information. The group management server may perform the check on the maximum limit of the total number (Nc6) of MC service group members. +3. The group management server notifies the MC service server(s) regarding the group membership change with the information of the updated group members. +4. The group members that are added to or deleted from the group by this operation are notified about the group membership change. This step may be followed by retrieving group configurations defined in subclause 10.1.5.2 +5. The group management server provides a group membership response to the group management client of the administrator/dispatcher/authorized user. + +### 10.2.7 Group configuration for interconnection + +#### 10.2.7.1 Overview + +The procedures in the following subclauses describe the process for sharing group configuration from a primary MC system of the MC service group to an interconnected partner MC system of the MC service group where MC service clients receiving MC service in the partner MC system of the MC service group need to make use of the MC service group. + +The group management server in the primary MC system of the MC service group provides group configuration information to the group management server in the partner MC system of the MC service group. The group management server in the partner MC system of the MC service group may modify the configuration before storing it in accordance with policies and requirements within that MC system (for example the priority of the group within that partner MC system, or permitted locations for service within that partner MC system). The group management server in the partner MC system of the MC service group will be the source of group configuration information to the group management clients of any MC service user who is receiving MC service in the partner MC system of the MC service group and who is defined as a member of the MC service group. The list of groups in the user profile for those group members in the partner MC system of the MC service group will contain the address of this group management server in the partner MC system of the MC service group as the address of the server from which to obtain the MC service group configuration for this MC service group. + +The procedures in the following subclauses describe the cases where the provision of configuration information is initiated by the group management server in the primary MC system of the MC service group, and where the + +configuration is requested by the group management server in the partner MC system of the MC service group. There may be additional proxy servers in between the two group management servers on the edges of one or both MC systems so that each group management server is not aware of the network topology of the other MC system. These additional proxy servers are not shown in these procedures. + +#### 10.2.7.2 Primary MC system provides group configuration to the partner MC system + +Figure 10.2.7.2-1 below illustrates the case where the primary MC system of the MC service group provides the group configuration to the partner MC system of the MC service group, e.g. due to an action by an administrator or because the primary MC system of some of the MC service group members is the partner MC system of the MC service group. + +##### Preconditions + +- The MC service group is defined in its primary MC system. +- One or more MC service group members are defined in the partner MC system. +- The primary MC system of the MC service group has been configured with addressing information for the group management server in the partner MC system of the MC service group. +- The primary MC system of the MC service group is authorized to provide group configuration information to the partner MC system of the MC service group. + +NOTE 1: The primary MC system of the MC service group could be configured with an address of the group management server within the partner MC system of the MC service group which is a proxy address, and routing within the partner MC system of the MC service group determines which actual group management server is the correct server to receive the configuration information. + +NOTE 2: The group management server within the partner MC system of the MC service group is responsible for providing MC service group configuration information to MC service group members for whom the partner MC system of the MC service group is their serving MC system. + +![Sequence diagram showing the interaction between the Primary MC system of group and the Partner MC system of group. The Primary MC system contains a Group management server. The Partner MC system contains a Group management server and an MC service server. The sequence of messages is: 1. Group information provision request from Primary GMS to Partner GMS; 2. Modify group configuration according to partner MC system policy (internal to Partner GMS); 3. Store group configuration information (internal to Partner GMS); 4. Notify group information from Partner GMS to MC service server; 5. Group information provision response from Partner GMS to Primary GMS.](01141eb99b707de5aead56f84afe3b1f_img.jpg) + +``` + +sequenceDiagram + participant Primary MC system of group + participant Partner MC system of group + Note right of Partner MC system of group: Group management server + Note right of Partner MC system of group: MC service server + + Primary MC system of group->>Partner MC system of group: 1. Group information provision request + activate Partner MC system of group + Partner MC system of group->>Partner MC system of group: 2. Modify group configuration according to partner MC system policy + Partner MC system of group->>Partner MC system of group: 3. Store group configuration information + Partner MC system of group-->>MC service server: 4. Notify group information + Partner MC system of group-->>Primary MC system of group: 5. Group information provision response + deactivate Partner MC system of group + +``` + +Sequence diagram showing the interaction between the Primary MC system of group and the Partner MC system of group. The Primary MC system contains a Group management server. The Partner MC system contains a Group management server and an MC service server. The sequence of messages is: 1. Group information provision request from Primary GMS to Partner GMS; 2. Modify group configuration according to partner MC system policy (internal to Partner GMS); 3. Store group configuration information (internal to Partner GMS); 4. Notify group information from Partner GMS to MC service server; 5. Group information provision response from Partner GMS to Primary GMS. + +**Figure 10.2.7.2-1: Primary MC system provides group configuration to partner MC system** + +1. The group management server in the primary MC system of the MC service group provides the configuration information related to the MC service group to the group management server in the partner MC system of the MC service group. +2. The group management server in the partner MC system of the MC service group modifies the group configuration information received from the primary MC system of the MC service group according to the partner MC system's policies and local configuration information. + +3. The group management server in the partner MC system of the MC service group stores the modified group configuration. +4. The group management server in the partner MC system may notify the MC service server(s) in the partner MC system of the MC service group of the MC service group configuration. +5. The group management server of the partner MC system of the MC service group responds to the group management server of the primary MC system of the MC service group that the configuration has been received and stored correctly. + +#### 10.2.7.3 Partner MC system requests group configuration from the primary MC system + +Figure 10.2.7.3-1 below illustrates the case where the partner MC system of the MC service group requests the group configuration from the primary MC system of the MC service group, for example because an MC service user receiving service in the partner MC system of the MC service group has the group configured in the user profile. + +##### Preconditions + +- The MC service group is defined in its primary MC system. +- The MC service group is configured in the MC service user profiles of one or more MC service users in the partner MC system of the MC service group. +- At least one of the MC service users in the partner MC system of the MC service group that is listed as an MC service group member of the MC service group has become MC service authorized with the MC service server in the partner MC system of the MC service group. +- The group management server in the partner MC system of the MC service group does not have the configuration for the MC service group stored. +- The partner MC system of the MC service group has been configured with addressing information for the group management server in the primary MC system of the MC service group. +- The partner MC system of the MC service group is authorized to request group configuration information from the primary MC system of the group. + +NOTE 1: The partner MC system of the MC service group could be configured with an address of the group management server within the primary MC system of the MC service group which is a proxy address, and routing within the primary MC system of the MC service group determines which actual group management server is the correct server to provide the configuration information. + +NOTE 2: The group management server within the partner MC system of the MC service group is responsible for providing group configuration information to MC service group members for whom the partner MC system of the MC service group is their serving MC system. + +![Sequence diagram showing the interaction between a Partner MC system and a Primary MC system for group configuration. The Partner MC system contains an MC service server and a Group management server. The Primary MC system contains a Group management server. The sequence is: 1. MC service server to Partner GMS: Group information request; 2. Partner GMS to Primary GMS: Group information request; 3. Primary GMS to Partner GMS: Group information response; 4. Partner GMS internal: Modify group configuration according to partner MC system policy; 5. Partner GMS internal: Store group configuration information; 6. Partner GMS to MC service server: Group information response.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +``` +sequenceDiagram + participant MC service server + participant Partner GMS as Group management server + participant Primary GMS as Group management server + Note right of Partner GMS: Partner MC system of group + Note right of Primary GMS: Primary MC system of group + MC service server->>Partner GMS: 1. Group information request + Partner GMS->>Primary GMS: 2. Group information request + Primary GMS-->>Partner GMS: 3. Group information response + Partner GMS->>Partner GMS: 4. Modify group configuration according to partner MC system policy + Partner GMS->>Partner GMS: 5. Store group configuration information + Partner GMS-->>MC service server: 6. Group information response +``` + +Sequence diagram showing the interaction between a Partner MC system and a Primary MC system for group configuration. The Partner MC system contains an MC service server and a Group management server. The Primary MC system contains a Group management server. The sequence is: 1. MC service server to Partner GMS: Group information request; 2. Partner GMS to Primary GMS: Group information request; 3. Primary GMS to Partner GMS: Group information response; 4. Partner GMS internal: Modify group configuration according to partner MC system policy; 5. Partner GMS internal: Store group configuration information; 6. Partner GMS to MC service server: Group information response. + +**Figure 10.2.7.3-1: Partner MC system requests group configuration from primary MC system** + +1. The MC service server in the partner MC system of the MC service group requests the group configuration information from the group management server in the partner MC system of the MC service group. +2. The group management server in the partner MC system of the MC service group requests the group configuration from the group management server in the primary MC system of the MC service group. +3. The group management server in the primary MC system of the MC service group provides the requested group configuration information. +4. The group management server in the partner MC system of the MC service group modifies the group configuration information received from the primary MC system of the MC service group according to the partner MC system's policies and local configuration information. +5. The group management server in the partner MC system of the MC service group stores the modified group configuration. +6. The group management server in the partner MC system notifies the MC service server(s) in the partner MC system of the MC service group of the MC service group configuration. + +#### 10.2.7.4 Partner MC system subscribes to group configuration + +The procedure for subscription from the group management server in the partner system for group configuration information to the group management server in the primary MC system of the MC service group is shown in figure 10.2.7.4-1. + +Pre-conditions: + +- The MC service group is defined in its primary MC system. +- One or more MC service group members are defined in the partner MC system. +- The GMS in the partner MC system of the MC service group has received group configuration information from the GMS in the primary MC system of the MC service group. + +![Sequence diagram showing subscription from partner MC system to primary MC system for MC service group configuration.](d0abac95583b52a3b35f74a215567334_img.jpg) + +``` +sequenceDiagram + participant Partner MC system of MC service group + participant Primary MC system of MC service group + Note left of Partner MC system: Group management server + Note right of Primary MC system: Group management server + Partner MC system->>Primary MC system: 1. Group information subscribe request + Primary MC system-->>Partner MC system: 2. Group information subscribe response +``` + +The diagram illustrates a sequence of interactions between two entities: 'Partner MC system of MC service group' and 'Primary MC system of MC service group'. Each entity has a 'Group management server'. The sequence starts with the Partner MC system sending a '1. Group information subscribe request' to the Primary MC system. The Primary MC system responds with a '2. Group information subscribe response'. + +Sequence diagram showing subscription from partner MC system to primary MC system for MC service group configuration. + +**Figure 10.2.7.4-1: Subscription from partner MC system to primary MC system for MC service group configuration** + +1. The group management server in the partner MC system of the MC service group subscribes to the group configuration information stored in the group management server in the primary MC system of the MC service group. +2. The group management server in the primary MC system of the MC service group provides a group information subscribe response to the group management server in the partner MC system of the MC service group indicating success or failure of the request. + +#### 10.2.7.5 Primary MC system notifies group configuration + +The procedure for notification of group configuration information from the group management server in the primary MC system of the MC service group to the group management server in the partner MC system of the MC service group is shown in figure 10.2.7.5-1. + +Pre-conditions: + +- The group management server in the partner MC system of the MC service group has subscribed to the group configuration information for the MC service group in the group management server in the primary MC system of the MC service group. +- The group management server in the primary MC system of the MC service group has received and stored new group configuration information for the MC service group, or the group management server in the primary MC system of the MC service group has generated and stored new key material, or both of these have occurred. + +![Sequence diagram showing notification of group configuration information to partner MC system of MC service group.](7affafe7362a2d2d072e9d4bf515f0bb_img.jpg) + +``` +sequenceDiagram + participant Partner MC system of MC service group + participant Primary MC system of MC service group + Note left of Partner MC system: Group management server + Note right of Primary MC system: Group management server + Primary MC system->>Partner MC system: 1. Group information notify request + Partner MC system-->>Primary MC system: 2. Group information notify response +``` + +The diagram illustrates a sequence of interactions between two entities: 'Partner MC system of MC service group' and 'Primary MC system of MC service group'. Each entity has a 'Group management server'. The sequence starts with the Primary MC system sending a '1. Group information notify request' to the Partner MC system. The Partner MC system responds with a '2. Group information notify response'. + +Sequence diagram showing notification of group configuration information to partner MC system of MC service group. + +**Figure 10.2.7.5-1: Notification of group configuration information to partner MC system of MC service group** + +1. The group management server in the primary MC system of the MC service group provides the notification to the group management server in the partner MC system of the MC service group. Optionally, the notify group configuration request may contain group related key material for the group management client. +2. The group management server in the partner MC system of the MC service group provides a notify group information notify response to the group management server in the primary MC system of the MC service group indicating the success or failure of the notification. + +Following completion of the notification procedure, the group management server in the partner MC system of the MC service group stores the group configuration information and any key material provided. + +### 10.2.8 Group deletion + +Figure 10.2.8-1 below illustrates the group deletion procedure by an authorized MC service user/ MC service administrator to delete a group in the primary MC system. Any actions taken by the group management clients on the UE after receiving the group deletion notification are outside the scope of this procedure. + +Pre-conditions: + +1. The group management clients, the group management server, and the MC service server belong to the same MC system. +2. The group management client (originator) is for an authorized user with authorization to perform the group deletion. + +![Sequence diagram for group deletion showing interactions between Group management client (originator), Group management server, MC service server, and Group management clients (group members).](0b87abe67b21a93777287649c33e755d_img.jpg) + +``` + +sequenceDiagram + participant GMC as Group management client (originator) + participant GMS as Group management server + participant MSS as MC service server + participant GMC_members as Group management clients (group members) + + Note right of GMS: 2. Authorize group deletion request + GMS->>GMS: 2. Authorize group deletion request + GMS->>MSS: 3. Group deletion notification + GMS->>GMC_members: 4. Group deletion notification + GMS->>GMC: 5. Group deletion response + +``` + +Sequence diagram for group deletion showing interactions between Group management client (originator), Group management server, MC service server, and Group management clients (group members). + +Figure 10.2.8-1: Group deletion + +1. The group management client (originator) of an authorized MC service user sends a group deletion request to the group management server. 2. The group management server checks whether the MC service user is authorized to perform the group deletion operation. For an authorized MC service user, the group management server will proceed to delete the group and move to step 3. If the MC service user is not authorized, then the group management server will not delete the group and move to step 5 sending a group deletion response failure. +3. The group management server sends a group deletion notification to the MC service server of the group as well as any MC service servers subscribed to the group. When a group is configured for multiple MC services, the group deletion notification is sent from the group management server to all MC service servers subscribed to the group. Affiliations to the deleted group will be removed. + +NOTE 1: Any actions taken by the MC service server upon receiving the group deletion notification are not shown in this procedure. Whether ongoing calls associated with the group deletion are impacted is left to implementation. + +4. The group management server sends the group deletion notification to group management clients for all group members of the deleted group. MC service client affiliations to the deleted group are removed. + +NOTE 2: It is assumed in this flow that the group management client (originator) is not a member of the group, so it does not receive a group deletion notification. + +5. The group management server sends a group deletion response to the group management client (originator). + +## 10.3 Pre-established session (on-network) + +### 10.3.1 General + +A pre-established session is a session established between an MC service client and the MC service server, on a per MC service basis, to exchange necessary media parameters needed for the definition of media bearers, allowing a faster set-up of MC service calls/sessions. + +After a pre-established session is established, a media bearer carrying the media and media control messages is always active. The MC service client establishes one or more pre-established sessions to an MC service server after SIP registration, and prior to initiating any MC service related procedures (e.g. calls, sessions) to other MC service users. When establishing a pre-established session, the MC service client negotiates the media parameters, including establishing IP addresses and ports using interactive connectivity establishment (ICE) as specified in IETF RFC 5245 [22], which later can be used in MC service calls/sessions. This avoids the need to negotiate media parameters (including evaluating ICE candidates) and reserving bearer resources during the MC service call/session establishment that results in delayed MC service call/session establishment. + +The use of pre-established session on the origination side is completely compatible with the use of on demand session on the termination side. The use of pre-established session on the termination side is completely compatible with the use of on demand session on the origination side. + +The pre-established session may be modified by the MC service client and the MC service server using the SIP procedures for session modification. + +The pre-established session may be released by the MC service client and the MC service server using the SIP procedures for terminating a SIP session. + +### 10.3.2 Procedures + +#### 10.3.2.1 General + +The pre-established session can be established after MC service authorization for the user (see 3GPP TS 23.379 [16]). + +The pre-established session is a session establishment procedure between the MC service client and the MC service server to exchange necessary media parameters needed for the definition of the media bearers. After the pre-established session is established, the media bearer carrying the floor control messages is always active. Additionally, the MC service client is able to activate the media bearer carrying the voice whenever needed: + +- immediately after the pre-established session procedure; or +- using SIP signalling when an MC service call is initiated. + +#### 10.3.2.2 Pre-established session establishment + +The pre-established session is a session between the MC service client and the MC service server in the MC system, and which may utilise other functional entities (e.g. a media distribution function, as defined in subclause 7.4.2.3.5, for means of obtaining media parameters and gathering ICE candidates). Figure 10.3.2.2-1 represents the pre-established session establishment flow. + +![Sequence diagram for Pre-established session establishment between MC service client and MC service server.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` +sequenceDiagram + participant MC service client + participant MC service server + Note left of MC service client: 1. Gather ICE candidates + MC service client->>MC service server: 2. Create pre-established session request + Note right of MC service server: 3. Service control, obtain media parameters and gather ICE candidates + MC service server->>MC service client: 4. Create pre-established session response + Note over MC service client, MC service server: 5. ICE candidate pair checks + MC service client-->>MC service server: 6. Modify pre-established session request + MC service server-->>MC service client: 7. Modify pre-established session response +``` + +The diagram illustrates the sequence of interactions for pre-establishing a session. It begins with the MC service client gathering ICE candidates. It then sends a 'Create pre-established session request' to the MC service server. The server performs service control, obtains media parameters, and gathers its own ICE candidates. It responds with a 'Create pre-established session response'. Both client and server then perform 'ICE candidate pair checks'. If necessary, the client sends a 'Modify pre-established session request' to update the ICE candidate pair, and the server responds with a 'Modify pre-established session response'. + +Sequence diagram for Pre-established session establishment between MC service client and MC service server. + +**Figure 10.3.2.2-1: Pre-established session establishment** + +1. The MC service client within the MC service UE gathers ICE candidates. +2. The MC service client within the MC service UE sends a request to the MC service server to create a pre-established session. +3. MC service server performs necessary service control, obtains media parameters (e.g. by means of interacting with a media distribution function of the MC service server) and gathers ICE candidates. +4. MC service server sends a create pre-establish session response to the MC service client within the MC service UE. +5. ICE candidate pair checks take place e.g. between the MC service client within the MC service UE and a media distribution function of the MC service server. +6. If necessary the MC service client within the MC service UE sends a modify pre-established session request to the MC service server to update the ICE candidate pair for the pre-established session. +7. The MC service server sends a modify pre-established session response accepting the ICE candidate pair update. + +The media sessions consist of at least an active media session carrying the media and media control messages and an inactive media session for the media. + +#### 10.3.2.3 Pre-established session modification + +Figure 10.3.2.3-1 represents the pre-established session modification flow. + +![Sequence diagram for Pre-established session modification between MC service client and MC service server.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` +sequenceDiagram + participant MC service client + participant MC service server + Note left of MC service client: 1. Gather ICE candidates + MC service client->>MC service server: 2. Modify pre-established session request + Note right of MC service server: 3. Service control, obtain media parameters and gather ICE candidates + MC service server-->>MC service client: 4. Modify pre-established session response + Note left of MC service client: 5. ICE candidate pair checks + MC service client-->>MC service server: 6. Modify pre-established session request + MC service server-->>MC service client: 7. Modify pre-established session response +``` + +The diagram illustrates a sequence of interactions between an MC service client and an MC service server for pre-established session modification. The process begins with the client gathering ICE candidates (step 1). It then sends a 'Modify pre-established session request' (step 2) to the server. The server performs service control and gathers ICE candidates (step 3). A 'Modify pre-established session response' (step 4) is sent back to the client. The client then performs ICE candidate pair checks (step 5). If necessary, it sends another 'Modify pre-established session request' (step 6) to the server. Finally, the server sends a 'Modify pre-established session response' (step 7) accepting the update. Steps 1, 4, 5, 6, and 7 are enclosed in dashed boxes, indicating they occur within the MC service UE. + +Sequence diagram for Pre-established session modification between MC service client and MC service server. + +**Figure 10.3.2.3-1: Pre-established session modification** + +1. The MC service client within the MC service UE gathers ICE candidates, if necessary (e.g. depending on the information that needs to be updated). +2. The MC service client within the MC service UE sends a request to the MC service server to modify a pre-established session. +3. MC service server performs necessary service control, obtains any necessary media parameters (e.g. by means of interacting with a media distribution function of the MC service server) and gathers necessary ICE candidates. +4. MC service server sends a modify pre-establish session response to the MC service client within the MC service UE. +5. If necessary, ICE candidate pair checks take place e.g. between the MC service client within the MC service UE and a media distribution function of the MC service server. +6. If necessary the MC service client within the MC service UE sends a modify pre-established session request to the MC service server to update the ICE candidate pair for the pre-established session. +7. The MC service server sends a modify pre-established session response accepting the ICE candidate pair update. + +NOTE 1: The represented procedure corresponds to a session modification initiated by the MC service client. It can also be initiated by the MC service server. + +NOTE 2: The procedure can also be used to switch a media session from the inactive to the active state and the reverse. The modification of the session triggers a corresponding modification of the characteristics (e.g. activity, bandwidth) of the corresponding GBR bearers. + +#### 10.3.2.4 Pre-established session release + +Figure 10.3.2.4-1 represents the MC service client within the MC service UE initiated pre-established session release flow and figure 10.3.2.4-2 represents the MC service server initiated pre-established session release flow. + +![Sequence diagram for MC service client initiated pre-established session release. Lifelines: MC service client, MC service server. Steps: 1. Release pre-established session request (client to server), 2. Release pre-established session response (server to client), 3. Release resources (internal server step).](410562339ce067fdc6fa41940c118658_img.jpg) + +``` +sequenceDiagram + participant Client as MC service client + participant Server as MC service server + Note right of Server: 3. Release resources + Client->>Server: 1. Release pre-established session request + Server-->>Client: 2. Release pre-established session response +``` + +Sequence diagram for MC service client initiated pre-established session release. Lifelines: MC service client, MC service server. Steps: 1. Release pre-established session request (client to server), 2. Release pre-established session response (server to client), 3. Release resources (internal server step). + +**Figure 10.3.2.4-1: MC service client within the MC service UE initiated pre-established session release** + +1. The MC service client within the MC service UE sends a request to the MC service server to release a pre-established session. +2. The MC service server sends a release pre-establish session response to the MC service client within the MC service UE. +3. The MC service server releases all resources for the pre-established session. + +![Sequence diagram for MC service server initiated pre-established session release. Lifelines: MC service client, MC service server. Steps: 1. Release pre-established session request (server to client), 2. Release pre-established session response (client to server), 3. Release resources (internal server step).](4636adff5682a064f0ae5f13a1d464a6_img.jpg) + +``` +sequenceDiagram + participant Client as MC service client + participant Server as MC service server + Note right of Server: 3. Release resources + Server->>Client: 1. Release pre-established session request + Client-->>Server: 2. Release pre-established session response +``` + +Sequence diagram for MC service server initiated pre-established session release. Lifelines: MC service client, MC service server. Steps: 1. Release pre-established session request (server to client), 2. Release pre-established session response (client to server), 3. Release resources (internal server step). + +**Figure 10.3.2.4-2: MC service server initiated pre-established session release** + +1. The MC service server sends a request to the MC service client within the MC service UE to release a pre-established session. +2. The MC service client within the MC service UE sends a release pre-establish session response to the MC service server. +3. The MC service server releases all resources for the pre-established session. + +## 10.4 Simultaneous session (on-network) + +### 10.4.1 General + +A simultaneous session is functionality whereby the MC service client can receive the media from multiple MC service calls/sessions over the same SIP session and media bearer(s) between the MC service client and the MC service server. + +## 10.5 Use of UE-to-network relay + +### 10.5.1 UE-to-network relay service authorization + +The MC service shall support the capability for UE-to-network relay to restrict the relayed group communication on a per group basis. + +To meet the above requirement, ProSe (as specified in 3GPP TS 23.303 [14]) can be used with an appropriate relay service code as per the following: + +- To restrict connection from only the membership of allowed MC service groups, UE-to-network relay UE is provisioned with relay service code(s) associated with allowed MC service group(s). The UE-to-network relay performs the access control as follows: + - 1) The UE broadcasts which MC service group(s) is/are authorized to connect to the network over this UE-to-network relay by including the related relay service code(s) in the UE-to-network relay Discovery Announcement message (as specified in 3GPP TS 23.303 [14]); or + - 2) The UE determines whether to respond to a remote UE's broadcasting message by checking if the relay service code carried in the UE-to-network relay Discovery Solicitation message is within the list of allowed relay service codes. +- To find a permitted UE-to-network relay, a remote UE is provisioned with the relay service code(s) associated MC service group(s) which the MC service user belongs to. The remote UE performs the UE-to-network relay selection as follows: + - 1) The remote UE determines if it is allowed to connect to a particular UE-to-network relay by checking whether the relay service code(s) associated with its MC service group(s) is/are carried in UE-to-network relay Discovery Announcement message (as specified in 3GPP TS 23.303 [14]); or + - 2) The remote UE includes the relay service code(s) associated with its MC service group(s) in Network Relay Discovery Solicitation message (as specified in 3GPP TS 23.303 [14]). + +### 10.5.2 UE-to-network relay MC service + +The ProSe UE-to-network relay provides a purely layer 3 IP data routing service, when the remote UE loses the coverage of cellular network and the MC service user on the remote UE requires to access the MC service via a ProSe UE-to-network relay. + +The application layer signalling for the MC service user on a remote UE are identical to the application layer signalling for the MC service user on an on network UE. + +## 10.6 General user authentication and authorization for MC services + +### 10.6.1 Primary MC system + +NOTE: Figure 10.6.1-1 is a high level user authentication and authorization flow. 3GPP TS 33.180 [25] defines the specific user authentication and authorization architecture required by the MC services in order to realize the MC service user authentication and authorization requirements as defined in 3GPP TS 22.280 [3]. + +The user authentication process shown in figure 10.6.1-1 may take place in some scenarios as a separate step independently from a SIP registration phase, for example if the SIP core is outside the domain of the MC service server. + +A procedure for user authentication is illustrated in figure 10.6.1-1. Other alternatives may be possible, such as authenticating the user within the SIP registration phase. + +![Sequence diagram showing MC service user authentication and registration with Primary MC system, single domain. The diagram involves four lifelines: Identity management client, Signalling user agent, SIP core, and Identity management server. Step 1: Identity management client sends a request to Identity management server. Step 2: Signalling user agent sends a request to SIP core. Step 3: Signalling user agent sends a request to SIP core.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant Identity management client + participant Signalling user agent + participant SIP core + participant Identity management server + + Note left of Identity management client: 1. MC service user performs user authentication and acquires an access token. + Identity management client->>Identity management server: + Note left of Signalling user agent: 2. Signalling user agent establishes a secure connection to the SIP core. + Signalling user agent->>SIP core: + Note left of Signalling user agent: 3. Signalling user agent performs SIP registration to SIP core. + Signalling user agent->>SIP core: + +``` + +Sequence diagram showing MC service user authentication and registration with Primary MC system, single domain. The diagram involves four lifelines: Identity management client, Signalling user agent, SIP core, and Identity management server. Step 1: Identity management client sends a request to Identity management server. Step 2: Signalling user agent sends a request to SIP core. Step 3: Signalling user agent sends a request to SIP core. + +**Figure 10.6.1-1: MC service user authentication and registration with Primary MC system, single domain** + +1. In this step the identity management client begins the user authorization procedure. The MC service user supplies the user credentials (e.g. biometrics, secureID, username/password) for verification with the identity management server. This step may occur before or after step 3. In a MC system with multiple MC services, a single user authentication as in step 1 can be used for multiple MC service authorizations for the user. +2. The signalling user agent establishes a secure connection to the SIP core for the purpose of SIP level authentication and registration. +3. The signalling user agent completes the SIP level registration with the SIP core (and an optional third-party registration with the MC service server(s)). + +NOTE: The MC service client(s) perform the corresponding MC service authorization for the user by utilizing the result of this procedure. + +### 10.6.2 Interconnection partner MC system + +Where communications with a partner MC system using interconnection are required, user authorization takes place in the serving MC system of the MC service user, using the MCX user service authorization procedure specified in 3GPP TS 33.180 [25]. + +### 10.6.3 Migration to partner MC system + +#### 10.6.3.1 General + +The following subclauses describe the procedure used for user authentication and service authorization when migrating to a partner MC system. + +To enable migration, the inter-domain MCX user service authorization procedures specified in 3GPP TS 33.180 [25] are used. + +#### 10.6.3.2 Information flows for migrated service authorization + +##### 10.6.3.2.1 Migration service authorization request + +Table 10.6.3.2.1-1 describes the information flow migration service authorization request sent from the MC service client of the migrating MC service user to the partner MC service server, and from the partner MC service server to the primary MC service server of the migrating MC service user. + +**Table 10.6.3.2.1-1: Migration service authorization request** + +| <b>Information element</b> | <b>Status</b> | <b>Description</b> | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------------------------------------------------------------------------------------------------| +| MC service ID (see NOTE 1) | M | The MC service ID of the migrating MC service user provided by the partner MC system. | +| MC service ID | M | The MC service ID of the migrating MC service user in the primary MC system of the MC service user. | +| MC service user profile index (see NOTE 2) | M | The MC service user profile index of the selected MC service user profile. | +| NOTE 1: The MC service ID is provided by the identity management server in the partner MC system during authentication of the migrating MC service user. | | | +| NOTE 2: The MC service user profile index refers to the MC service user profile provided by the primary MC system of the MC service user that has been selected by the MC service user in order to request migrated MC service on the partner MC system. | | | + +##### 10.6.3.2.2 Migration service authorization response + +Table 10.6.3.2.2-1 describes the information flow migration service authorization response sent from the primary MC service server of the migrating MC service user to the partner MC service server of the migrating MC service user, and from the partner MC service server to the MC service client of the migrating MC service user. + +**Table 10.6.3.2.2-1: Migration service authorization response** + +| <b>Information element</b> | <b>Status</b> | <b>Description</b> | +|--------------------------------------------------------------------------------------------------------------------|---------------|-----------------------------------------------------------------------------------------------------| +| MC service ID (see NOTE) | M | The MC service ID of the migrating MC service user provided by the partner MC system. | +| MC service ID (see NOTE) | M | The MC service ID of the migrating MC service user in the primary MC system of the MC service user. | +| Result | M | Success or failure of the migration MC service authorization request | +| NOTE: The MC service IDs are the MC service IDs that were provided in the migration service authorization request. | | | + +#### 10.6.3.3 Procedure + +The procedure for service authorization for migration to a partner MC system is shown in figure 10.6.3.3-1. + +##### Pre-conditions + +- The MC service user wishes to migrate to the partner MC system. +- The MC service client has been configured with an MC service user profile that contains the necessary parameters needed for connectivity with the partner MC system. +- A user authentication process has taken place which has supplied the necessary credentials to the MC service client to permit service authorization to take place in the partner system. + +![Sequence diagram for Service authorization for migration to partner MC system. The diagram shows interactions between an MC service client, Partner MC service server, Partner MC system gateway server, Primary MC system gateway server, and Primary MC service server across two systems: Partner MC system of migrated MC service client and Primary MC system of migrated MC service client.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant MC client as MC service client + participant Partner MC server as Partner MC service server + participant Partner MC gateway as Partner MC system gateway server + participant Primary MC gateway as Primary MC system gateway server + participant Primary MC server as Primary MC service server + + Note left of Partner MC server: 2. Authorization check + Note right of Primary MC server: 6. Authorization check + Note right of Primary MC server: 7. Mark MC service user as migrated to partner system + + MC client->>Partner MC server: 1. Migration service authorization request + Partner MC server->>Partner MC gateway: 3. Migration service authorization request + Partner MC gateway->>Primary MC gateway: 4. Migration service authorization request + Primary MC gateway->>Primary MC server: 5. Migration service authorization request + Primary MC server->>Primary MC gateway: 8. Migration service authorization response + Primary MC gateway->>Partner MC gateway: 9. Migration service authorization response + Partner MC gateway->>Partner MC server: 10. Migration service authorization response + Partner MC server->>MC client: 11. Migration service authorization response + +``` + +Sequence diagram for Service authorization for migration to partner MC system. The diagram shows interactions between an MC service client, Partner MC service server, Partner MC system gateway server, Primary MC system gateway server, and Primary MC service server across two systems: Partner MC system of migrated MC service client and Primary MC system of migrated MC service client. + +**Figure 10.6.3.3-1 Service authorization for migration to partner MC system** + +1. The MC service client requests migration service authorization with the partner MC service server indicating the selected MC service user profile to be used during migrated MC service. The MC service client provides both the MC service ID provided during user authentication in the partner MC system, and the MC service ID of the MC service user in the primary MC system of the MC service user. + +NOTE 1: The migrating MC service client also provides authentication credentials which are specified in 3GPP TS 33.180 [25]. + +2. The partner MC service server performs an initial authorization check to verify that the MC service user is permitted to migrate to the partner MC system from the primary MC system of the MC service user. + +NOTE 2: The criteria for the initial authorization check is outside the scope of the present document, but for example could be based on a pre-configured list of users who are expected to request migrated service authorization. + +3. The partner MC service server identifies the primary MC system of the MC service user of the MC service client by use of the MC service ID of the MC service user in the primary MC system of the MC service user, which was presented by the MC service client in step 1, and sends a migration service authorization request to the gateway server in the partner MC system. +4. The partner MC system gateway server identifies the primary MC system of the MC service user from the MC service ID presented in step 3, and forwards the migration service authorization request to the gateway server of the primary MC system. +5. The gateway server in the primary MC system of the MC service user identifies the primary MC service server of the MC service user from the MC service ID presented in step 3, and forwards the migration service authorization request to that MC service server. +6. The primary MC service server of the MC service user performs an authorization check, to verify that migration is permitted to that partner MC system by this MC service user using the indicated MC service user profile. +7. The primary MC service server marks the MC service user as having migrated, and records the partner MC system as the migrated MC system. +8. The primary MC service server sends a migration service authorization response to the gateway server in the primary MC system. + +9. The gateway server in the primary MC system sends the migration service authorization response to the gateway server in the partner MC system. +10. The gateway server in the partner MC system sends the migration service authorization response to the partner MC service server. +11. The partner MC service server sends the migration service authorization response to the MC service client, confirming that successful migration and service authorization has taken place. + +NOTE 3: If topology hiding is not used, the migration service authorization request and migration service authorization response messages are sent between the MC service servers in the primary and partner MC system without the need to be sent via an MC gateway server. + +## 10.7 Use of MBMS transmission + +### 10.7.1 General + +This subclause defines information flows and procedures for MBMS usage that applies to MC services. MBMS bearers can be used by any MC service for any MC service group. A single MBMS bearer can be used for one or more MC services within a single group or by multiple group communications in parallel. + +The following subclauses specify the procedures and information flows for the usage of MBMS transmission that are utilised by the following MC services: + +- MCPTT (as specified in 3GPP TS 23.379 [16]); +- MCVideo (as specified in 3GPP TS 23.281 [12]); and +- MCData (as specified in 3GPP TS 23.282 [13]). + +MC service specific pre-requisites and resultant behaviour by functional entities in performing these procedures are specified in the respective MC service TSs as listed above. + +### 10.7.2 Information flows for MBMS transmission + +#### 10.7.2.1 MBMS bearer announcement + +Table 10.7.2.1-1 describes the information flow MBMS bearer announcement from the MC service server to the MC service client. + +**Table 10.7.2.1-1: MBMS bearer announcement** + +| Information element | Status | Description | +|---------------------------------|-----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TMGI | M | TMGI information | +| Alternative TMGI | O | A list of additional alternative TMGI may be included and used in roaming scenarios. | +| QCI | O | QCI information used by the ProSe UE-Network Relay to determine the ProSe Per-Packet Priority value to be applied for the multicast packets relayed to Remote UE over PC5 | +| List of service area identifier | M | A list of service area identifier for the applicable MBMS broadcast area. | +| Frequency | O | Identification of frequency if multi carrier support is provided | +| SDP information | M | SDP with media and floor control information applicable to groups that can use this bearer (e.g. codec, protocol id, FEC information) | +| Monitoring state | O | The monitoring state is used to control if the client is actively monitoring the MBMS bearer quality or not. | +| Announcement acknowledgment | O | Indicate if the MBMS server requires an acknowledgement of the MBMS bearer announcement. | +| Unicast status | O | An indication that the listening status of the unicast bearer is requested. | +| ROHC information | O | Indicate the usage of ROHC and provide the parameters of the ROHC channel to signal to the ROHC decoder. | +| NOTE: | When MBMS bearer announcement is done on a MBMS bearer all attributes above are optional except the TMGI. | | + +#### 10.7.2.2 MBMS listening status report + +Table 10.7.2.2-1 describes the information flow for the MBMS listening status report from MC service client to MC service server. The information is used for the decision on the switching from MBMS bearer to unicast bearer or vice versa. + +**Table 10.7.2.2-1: MBMS listening status report** + +| Information element | Status | Description | +|--------------------------|--------|------------------------------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user who wants to report the MBMS listening status. | +| TMGI(s) | M | TMGI(s) information. | +| MBMS listening status(s) | M | The MBMS listening status per TMGI. | +| Unicast listening status | O | The unicast listening status. | + +#### 10.7.2.3 MBMS suspension reporting instruction + +Table 10.7.2.3-1 describes the information flow for the MBMS suspension reporting instruction from MC service server to MC service client in a unicast bearer for MBMS suspension reporting. + +**Table 10.7.2.3-1: MBMS suspension reporting instruction (unicast)** + +| Information element | Status | Description | +|----------------------|--------|------------------------------------------------------------------------------| +| MC service ID | M | The MC service identity | +| Suspension reporting | M | Enables or disable the suspension reporting for a specific MC service client | + +Table 10.7.2.3-2 describes the information flow for the MBMS suspension reporting instruction from MC service server to MC service client in a multicast bearer for MBMS suspension reporting. + +**Table 10.7.2.3-2: MBMS suspension reporting instruction (multicast)** + +| Information element | Status | Description | +|------------------------------------|--------|---------------------------------------------------------------------------------------------------| +| Suspension reporting client subset | M | Contains a uniquely defined subset of MC service clients that shall report <b>MBMS</b> suspension | + +#### 10.7.2.4 Discover bearer request + +Table 10.7.2.4-1 describes the information flow discover bearer request from the MC service server to another MC service server (**MBMS** bearer control role). + +**Table 10.7.2.4-1: Discover bearer request** + +| Information element | Status | Description | +|----------------------------------|--------|----------------------------------------------------------------------------------| +| List of service area identifiers | M | A list of service area identifier for the applicable <b>MBMS</b> broadcast area. | +| Bandwidth | M | Maximum bandwidth required | +| <b>QCI</b> | O | Desired <b>QCI</b> | + +#### 10.7.2.5 Discover bearer response + +Table 10.7.2.5-1 describes the information flow discover bearer response from an MC service server (**MBMS** bearer control role) to the MC service server. + +**Table 10.7.2.5-1: Discover bearer response** + +| Information element | Status | Description | +|----------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| <b>TMGIs</b> | M | List of <b>TMGIs</b> and related information | +| List of service area identifiers | M | A list of service area identifiers for the applicable <b>MBMS</b> broadcast areas, corresponding to the listed <b>TMGIs</b> , over which the request was successful. | +| Frequency | O | Identification of the frequency if multi-carrier support is provided | +| <b>QCI</b> | O | <b>QCI</b> information used by the <b>ProSe</b> UE-Network relay to determine the <b>ProSe</b> per-packet priority value to be applied for the multicast packets relayed to a remote UE over <b>PC5</b> . | + +#### 10.7.2.6 Media distribution request + +Table 10.7.2.6-1 describes the information flow media distribution request from the MC service server to an MC service server (**MBMS** bearer control role) that has a desired bearer. + +**Table 10.7.2.6-1: Media distribution request** + +| Information element | Status | Description | +|------------------------|--------|----------------------------------------------------------------------------------------------------------------------| +| <b>TMGI</b> | M | <b>TMGI</b> information | +| Bandwidth | M | Maximum bandwidth required | +| Separate floor control | M | Whether or not a separate bearer is required for floor control | +| SDP information | M | SDP with media and floor control information applicable to groups that can use this bearer (e.g. codec, protocol id) | +| <b>QCI</b> | O | Desired <b>QCI</b> | +| MC Group ID | O | The MC group id for when the request is sent for a specific group call. | + +#### 10.7.2.7 Media distribution request response + +Table 10.7.2.7-1 describes the information flow media distribution response from an MC service server (**MBMS** bearer control role) that has a desired bearer to the MC service server. + +**Table 10.7.2.7-1: Media distribution response** + +| Information element | Status | Description | +|------------------------------|--------|----------------------------------------------------------------------------------------------------------------------| +| <b>TMGI</b> | M | <b>TMGI</b> information | +| Bandwidth | M | Maximum bandwidth required | +| SDP information | M | SDP with media and floor control information applicable to groups that can use this bearer (e.g. codec, protocol id) | +| <b>QCI</b> | O | Actual <b>QCI</b> | +| Media stream identifier | O | This element identifies the media stream of the SDP used for the group call (e.g. <b>MBMS</b> subchannel). | +| Media distribution indicator | O | Indicates to the MC service server whether the media in the ongoing group communication should be sent or not | + +#### 10.7.2.8 Identify multicast participants request + +Void + +#### 10.7.2.9 Remove call from bearer request + +Void + +#### 10.7.2.10 Media distribution release + +Table 10.7.2.10-1 describes the information flow media distribution release from the MC service server to an MC service server (**MBMS** bearer control role) that has the used bearer. + +**Table 10.7.2.10-1: Media distribution request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------| +| <b>TMGI</b> | M | <b>TMGI</b> information | +| Bandwidth | M | The bandwidth released by the MC service server that used the bearer | +| MC Group ID | O | The MC group id for when the request is sent for a specific group call. | + +#### 10.7.2.11 Media broadcasting notification + +Void. + +### 10.7.3 Procedures for **MBMS** usage + +#### 10.7.3.1 Use of pre-established **MBMS** bearers + +##### 10.7.3.1.1 General + +In this scenario, the MC service server pre-establishes **MBMS** bearer(s) in certain pre-configured areas before the initiation of the group communication session. When a user originates a request for a group communication session for one of these areas, the pre-established **MBMS** bearer(s) is used for the DL media transmission. + +The following steps needs to be performed prior the start of the MC group communication session over pre-established **MBMS** bearer: + +- **MBMS** bearer(s) is Pre-established +- Announce the pre-established **MBMS** bearer to the MC service clients + +When these preparation steps have been done the MC group communication session using **MBMS** bearer can start. + +Both the media packets as well as the application level control signalling (e.g. floor control messages) to the receiving MC service clients are sent on the **MBMS** bearer. Optionally a separate **MBMS** bearer could be used for the application level control messages, due to different bearer characteristic requirements. + +##### 10.7.3.1.2 Procedure + +The procedure figure 10.7.3.1.2-1 shows only one of the receiving MC service clients using an **MBMS** bearer. There might also be MC service clients in the same MC group communication session that receive the communication on unicast bearers. + +Pre-conditions: + +- The participating users are already affiliated. + +![Sequence diagram illustrating the use of pre-established MBMS bearers for MC communication. The diagram shows interactions between an MC service client and an MC service server, leading to media delivery over MBMS.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) + +``` + +sequenceDiagram + participant Client as MC service client + participant Server as MC service server + Note right of Server: 1a. Activate MBMS bearers + Note right of Server: 1b. Activate MBMS bearers for application level control signalling + Server-->>Client: 2a. MBMS bearer announcement + Server-->>Client: 2b. MBMS bearer announcement (For control signalling) + Note left of Client: 3. MC service client stores TMGI(s), service area and other info about the MBMS bearer(s), the MC service UE starts to monitor the TMGI(s). + Client-->>Server: 4. MBMS listening status report + Note right of Client: 5. Procedure of MC communication session setup and media delivery using MBMS + Note right of Client: 6. DL media over MBMS + +``` + +The diagram is a sequence diagram with two lifelines: 'MC service client' on the left and 'MC service server' on the right. + 1. The server performs two internal actions: '1a. Activate MBMS bearers' and '1b. Activate MBMS bearers for application level control signalling' (the latter is enclosed in a dashed box). + 2. The server sends two messages to the client: '2a. MBMS bearer announcement' and '2b. MBMS bearer announcement (For control signalling)'. + 3. The client performs an internal action: '3. MC service client stores TMGI(s), service area and other info about the MBMS bearer(s), the MC service UE starts to monitor the TMGI(s).'. + 4. The client sends a message to the server: '4. MBMS listening status report'. + 5. A large box on the server side indicates: '5. Procedure of MC communication session setup and media delivery using MBMS'. + 6. A large arrow pointing from the server to the client indicates: '6. DL media over MBMS'. + +Sequence diagram illustrating the use of pre-established MBMS bearers for MC communication. The diagram shows interactions between an MC service client and an MC service server, leading to media delivery over MBMS. + +**Figure 10.7.3.1.2-1: Use of pre-established MBMS bearers** + +1a. The MC service server determines to activate **MBMS** bearer. The activation of the **MBMS** bearer is done on the **MB2-C** reference point and according to 3GPP **TS 23.468** [18]. This bearer will be used for the MC communication media. + +1b. Optionally, the MC service server may also activate an **MBMS** bearer dedicated for application level control signalling. The activation of the **MBMS** bearer is done on **MB2-C** reference point and according to 3GPP **TS 23.468** [18]. + +NOTE 1: The procedure to determine the activation of **MBMS** bearers is implementation specific. + +2a. The MC service server passes the **MBMS** bearer info for the service description associated with the pre-established **MBMS** bearer to the MC service client. The MC service client obtains the **TMGI**, identifying the **MBMS** bearer, from the service description. + +- 2b. The MC service server may pass the **MBMS** bearer info for the service description associated with the pre-established floor control **MBMS** bearer to the MC service client. The MC service client obtains the **TMGI**, identifying the **MBMS** bearer, from the service description. + +NOTE 2: Step 2a and Step 2b can be done in one **MBMS** bearer announcement message. + +3. The MC service client stores the information associated with the **TMGI**(s). The MC service client uses the **TMGI** and other **MBMS** bearer related information to activate the monitoring of the **MBMS** bearer by the MC service UE. + 4. The MC service client that enters or is in the service area of at least one announced **TMGI** indicates to the MC service server that the MC service client is able to receive media over **MBMS**, whereby the MC service server may decide to use the **MBMS** bearer instead of unicast bearer for MC communication sessions. +- NOTE 3: Step 4 is optional for the MC service UE on subsequent **MBMS** bearer announcements. +5. An MC service group communication session is established. + 6. As the MC service server transmits the media over the **MBMS** bearer, the media packets are detected and delivered to the MC service client. + +#### 10.7.3.2 Use of dynamic **MBMS** bearer establishment + +In this scenario depicted in figure 10.7.3.2-1, the MC service server uses a unicast bearer for communication with the UE on the DL at the start of the group communication session. When the MC service server decides to use an **MBMS** bearer for the DL media transmission, the MC service server establishes an **MBMS** bearer using the procedures defined in 3GPP **TS 23.468** [18]. The MC service server provides **MBMS** service description information associated with **MBMS** bearer(s), obtained from the **BM-SC**, to the UE. The UE starts using the **MBMS** bearer(s) to receive DL media and stops using the unicast bearer for the DL media transmission. + +NOTE 1: The MC service server logic for determining when to establish the new **MBMS** delivery bearer is implementation specific. For example, the MC service server could decide to establish the **MBMS** delivery based on the location of the UE's that are a part of the group communication session. + +![Sequence diagram illustrating the use of dynamic MBMS bearer establishment between a UE and an MC service server.](19a59d6b53059ebd27b13c98793f88e0_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MC_service_server as MC service server + Note right of MC_service_server: 3. Establish MBMS bearers + Note left of UE: 5. UE starts monitoring data over MBMS bearer associated with TMGI(s) + Note left of UE: 6. UE detects that it is able to receive MBMS bearer + Note right of MC_service_server: 8. Group communication session via dynamic MBMS bearer(s) is established + + UE->>MC_service_server: 1. Procedure of MC communication session setup + MC_service_server-->>UE: 2. DL media over unicast + MC_service_server->>MC_service_server: 3. Establish MBMS bearers + MC_service_server-->>UE: 4. MBMS bearer announcement + UE->>MC_service_server: 7. MBMS bearer listening status report + MC_service_server-->>UE: 9. DL media over MBMS + +``` + +The diagram shows a sequence of interactions between a UE and an MC service server. + 1. The UE sends a 'Procedure of MC communication session setup' to the server. + 2. The server responds with 'DL media over unicast'. + 3. The server internally executes 'Establish MBMS bearers'. + 4. The server sends an 'MBMS bearer announcement' to the UE. + 5. The UE starts monitoring data over the MBMS bearer associated with TMGI(s). + 6. The UE detects that it is able to receive the MBMS bearer. + 7. The UE sends an 'MBMS bearer listening status report' to the server. + 8. The server establishes a 'Group communication session via dynamic MBMS bearer(s)'. + 9. The server then transmits 'DL media over MBMS' to the UE. + +Sequence diagram illustrating the use of dynamic MBMS bearer establishment between a UE and an MC service server. + +Figure 10.7.3.2-1: Use of dynamic **MBMS** bearer establishment + +1. An MC service group communication session is established. + +2. The downlink data is sent by unicast delivery. + 3. The MC service server establishes the **MBMS** bearer(s) for the group communication session according to the procedures defined in 3GPP **TS 23.468** [18]. Service description associated with the **MBMS** bearer(s) is returned from The **BM-SC**. + 4. The MC service server provides service description information associated with the **MBMS** bearer to the UE. The MC service UE obtains the **TMGI** from the announcement message. This message may be sent on an application level control signalling bearer. + 5. The MC service UE starts monitoring data over **MBMS** associated with the **TMGI**, while in the service area associated with the **TMGI**. + 6. The MC service UE detects that it is able to receive data over **MBMS** associated with the **TMGI**. + 7. The MC service client notifies the MC service server that it is successfully receiving the **TMGI**. MC service server stops sending media data over unicast way to the MC service client. + 8. An MC service group communication session via dynamic **MBMS** bearer(s) is established. +- NOTE 2: Step 8 can occur before step 7. +9. MC service server sends the downlink media for the group communication session over the **MBMS**. + +#### 10.7.3.3 Switching from **MBMS** bearer to unicast bearer + +Figure 10.7.3.3-1 shows the procedure for service continuity when a UE is about to move out of **MBMS** coverage by switching from **MBMS** bearer to unicast bearer. + +Pre-conditions: + +- It is assumed that the **MBMS** bearer has been activated by MC service server for downlink delivery. + +![Sequence diagram showing the switching from MBMS delivery to unicast delivery between a UE and an MC Service Server. The steps are: 1. UE detects bad MBMS condition; 2. UE sends MBMS listening status report; 3. Server provides DL data over unicast bearer; 4. UE receives both unicast and MBMS data (simultaneous); 5. UE stops MBMS and continues with unicast only.](19a5f0db57a21a0e82a7f326083e96fd_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MC Service Server + Note left of UE: 1. UE detects that it suffers from bad MBMS bearer condition + UE->>MC Service Server: 2. MBMS listening status report + Note right of MC Service Server: 3. DL data over unicast bearer + Note left of UE: 4. Simultaneously receives data over unicast & MBMS + Note left of UE: 5. Stops receiving MBMS and continues receiving traffic only over unicast + +``` + +Sequence diagram showing the switching from MBMS delivery to unicast delivery between a UE and an MC Service Server. The steps are: 1. UE detects bad MBMS condition; 2. UE sends MBMS listening status report; 3. Server provides DL data over unicast bearer; 4. UE receives both unicast and MBMS data (simultaneous); 5. UE stops MBMS and continues with unicast only. + +**Figure 10.7.3.3-1: Switching from **MBMS** delivery to unicast delivery** + +1. The MC service UE detects that it suffers from bad **MBMS** bearer condition for the corresponding **MBMS** service. The method to detect is implementation specific. +2. The MC service client notifies the MC service server that it suffers from bad **MBMS** bearer condition for the corresponding **MBMS** service by sending the **MBMS** listening status report. + +3. The MC service server sends the downlink data by unicast delivery to the MC service client. + +NOTE: The unicast bearer may be set up on demand after step 2 or before. + +4. During the switching, the MC service client simultaneously receives downlink data through both unicast bearer and **MBMS** bearer. If there is no downlink data to the MC service client, this step can be skipped. +5. The MC service client ceases to receive the downlink data through **MBMS** bearer but continues receiving data through unicast bearer. + +#### 10.7.3.4 Use of **MBMS** bearer for application level control signalling + +##### 10.7.3.4.1 Description + +The MC service server may use an **MBMS** bearer for application level control signalling, according to this subclause. An **MBMS** bearer for application level control signalling is typically used for the purposes beyond the benefit for using **MBMS** for resource efficiency, e.g. for improved MC service performance (KPIs), handling of high load scenarios. + +The **MBMS** bearer for application level control signalling may be used to transmit the following messages: + +- Transmission control (e.g. call setup and floor control) +- **MBMS** bearer announcement for media bearers +- Group application paging +- Group dynamic data (e.g. status of the group) +- Group state (e.g. emergency alerts) + +An **MBMS** bearer for application level control signalling is activated in a service area that is larger than the estimated service for media bearers. The service area for the media bearers mainly based on counting of group members in each defined service area. The **MBMS** bearer for application level control signalling is also activated with a QoS that is better than **MBMS** media bearers since the packet loss requirements are much stricter. + +##### 10.7.3.4.2 Procedure + +The procedure in figure 10.7.3.4.2-1 shows only one of the receiving MC service clients using an **MBMS** bearer. + +![Sequence diagram showing the procedure for using MBMS bearer for application level control signalling between an MC service client and an MC service server.](f7d969388c4f7e30cd04a061314bfa0e_img.jpg) + +``` + +sequenceDiagram + participant Client as MC service client + participant Server as MC service server + Note right of Server: 1. Activate MBMS bearer for +application control message + Server->>Client: 2. MBMS bearer announcement + Note left of Client: 3. MC service client stores TMGI, service area and +other info about the MBMS bearer, the MC +service UE starts to monitor the TMGI. + Client->>Server: 4. MBMS listening status report + Server->>Client: 5. Application control messages + +``` + +The diagram illustrates a five-step sequence: + 1. The MC service server activates the MBMS bearer for application control messages. + 2. The server sends an MBMS bearer announcement to the client. + 3. The client stores bearer information (TMGI, service area) and begins monitoring. + 4. The client sends a listening status report back to the server. + 5. The server transmits application control messages to the client via the established bearer. + +Sequence diagram showing the procedure for using MBMS bearer for application level control signalling between an MC service client and an MC service server. + +Figure 10.7.3.4.2-1: Use of **MBMS** bearer for application level control signalling + +1. The MC service server determines to activate **MBMS** bearer for application level control signalling. The activation of the **MBMS** bearer is done on the **MB2-C** reference point and according to 3GPP **TS 23.468** [18]. + +2. The MC service server passes the **MBMS** bearer info for the service description associated **MBMS** bearer to the MC service client. The MC service client obtains the **TMGI**, identifying the **MBMS** bearer, from the service description. +3. The MC service client stores the information associated with the **TMGI**. The MC service client uses the **TMGI** and other **MBMS** bearer related information to activate the monitoring of the **MBMS** bearer by the MC service UE. +4. The MC service client that enters or is in the service area of the announced **TMGI** indicates to the MC service server that the MC service client is able to receive application level control messages over the **MBMS** bearer, whereby the MC service server may decide to use the **MBMS** bearer for MC application control messages. +5. The MC service server transmit MC application control messages + +#### 10.7.3.5 **MBMS** bearer announcement over **MBMS** bearer + +##### 10.7.3.5.1 Description + +The **MBMS** announcement may be done on either a unicast bearer or a **MBMS** bearer. Using a unicast bearer for **MBMS** bearer announcement provides an interactive way of doing announcement. The MC service server will send the **MBMS** bearer announcement message to the MC service client regardless if there is an **MBMS** bearer active or the MC service client can receive the data on the **MBMS** bearer with sufficient quality. The benefit of the existing procedure is that it gives a secure way to inform the MC service client about the **MBMS** bearer and how to retrieve the data on the **MBMS** bearer. + +When there is more than one **MBMS** bearer active in the same service area for MC service, there are not the same reasons to use unicast bearer for additional **MBMS** bearer announcement. Instead a **MBMS** bearer for application level control signalling can be used to announce additional **MBMS** bearers. + +The **MBMS** bearer announcement messages are sent on an **MBMS** bearer used for application control messages. This bearer will have a different QoS setting compared to an **MBMS** bearer used for media, since application signalling messages are more sensitive to packet loss. + +##### 10.7.3.5.2 Procedure + +The procedure defined below enables the MC service to announcement a new **MBMS** bearer. + +Pre-conditions: + +- An **MBMS** bearer used for MC service application control messages must have been pre-established and announced to the MC service client. +- Additional **MBMS** bearer information may have already been announced to the client. + +![Sequence diagram illustrating MBMS bearer announcement over an MBMS bearer used for application control messages. The diagram shows interactions between an MC service client and an MC service server. The client monitors for control messages. The server activates a new bearer, decides to announce it, and sends an announcement. The client monitors the new bearer and sends an acknowledgement if requested. The server later decides to de-announce the bearer and sends a de-announcement. The client stops monitoring the de-announced bearer.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +``` + +sequenceDiagram + participant MC service client + participant MC service server + Note left of MC service client: 1. MC service client monitors a MBMS bearer for MC application control messages + Note right of MC service server: 2. MC service server activates a new MBMS bearer + Note right of MC service server: 3. MC service server decide to announce an MBMS bearer + MC service server->>MC service client: 4. MBMS bearer announcement + Note left of MC service client: 5. MC service client monitors the newly announced MBMS bearer + Note right of MC service server: 6. MBMS bearer acknowledgement + Note right of MC service server: 7. MC service server decide to de-announce an MBMS bearer + MC service server->>MC service client: 8. MBMS bearer de-announcement + Note left of MC service client: 9. MC service client stops monitor the newly de-announced MBMS bearer + +``` + +Sequence diagram illustrating MBMS bearer announcement over an MBMS bearer used for application control messages. The diagram shows interactions between an MC service client and an MC service server. The client monitors for control messages. The server activates a new bearer, decides to announce it, and sends an announcement. The client monitors the new bearer and sends an acknowledgement if requested. The server later decides to de-announce the bearer and sends a de-announcement. The client stops monitoring the de-announced bearer. + +**Figure 10.7.3.5.2-1: MBMS bearer announcement over an MBMS bearer used for application control messages** + +1. The MC service client monitors an **MBMS** bearer that is used for MC service application signalling messages, such as bearer announcement messages. +2. The MC service server activates a new **MBMS** bearer. +3. The MC service server announce the **MBMS** bearer to the MC service client. The bearer may have just been activated or may have already been running for some time. The step may be repeated as needed. +4. The MC service server sends a **MBMS** bearer announcement on the **MBMS** bearer used for MC application control messages. The **MBMS** bearer announcement contains the identity of the **MBMS** bearer (i.e. the **TMGI**) and may optionally include additional information about the newly announced bearer. Required and optional **MBMS** bearer announcement details may have already been provided. In this case the **MBMS** bearer identity could be used as a key for such **MBMS** bearer details. +5. The MC service clients start to monitor the newly announced **MBMS** bearer. +6. If requested by the MC service server, the MC service client sends an acknowledgement of the **MBMS** bearer to the MC service server. +7. The MC service server de-announce the **MBMS** bearer. +8. The MC service server sends a **MBMS** bearer de-announcement message that contains the identity of the **MBMS** bearer. +9. The MC service client stops monitoring the de-announced **MBMS** bearer. + +The same procedure can also be used to modify existing **MBMS** bearer announcement information. Example of such modification could be addition of UDP ports or modification of codec in the SDP. + +#### 10.7.3.6 MBMS bearer quality detection + +##### 10.7.3.6.1 Description + +The MC service client and MC service server use this procedure to report and take action on the MBMS bearer quality. An MC service client monitors an MBMS bearer to receive MC service media. Based on the received quality (e.g. radio level quality, transport level quality), the MC service client needs to inform the MC service server that the MC service client is able to receive the MC service media on the MBMS bearer with sufficient quality or not able to receive the MC service media on the MBMS bearer with sufficient quality. + +The issue can be more complex since the MC service client needs to estimate the quality of the bearer even in the scenario when there are no data currently transmitted on the MBMS bearer (e.g. between MCPTT group call). The reason for this is that an MC service client that has entered an area with significantly degraded MBMS quality, might not even notice that an MC service communication is ongoing, meanwhile the MC server still assumes that the MC service client can receive the media being broadcasted. + +To estimate the MBMS bearer quality, for example as an equivalent BLER (Block Error Rate) when no data is sent is implementation specific. This estimation is dependent on for example the modulation and coding scheme (MCS) and measurements from the reference signals from the eNB(s). Other metrics (e.g. RTP packet loss) may be used to estimate the MBMS bearer quality. + +##### 10.7.3.6.2 Procedure + +The MC service client shall indicate the ability of the MC service client to receive the MBMS bearer. + +Pre-conditions: + +- There is an MBMS bearer activated and the MBMS bearer information is announced to the MC service client +- The MC service client is located in the MBMS broadcasting area +- The MC service UE monitors SIB-13 (or SIB-20) and (SC-)MCCH to receive the modulation and coding scheme +- The MC service UE monitors the cell specific reference signal and when MBSFN transmission is used, the MBSFN specific reference signals + +![Sequence diagram for MBMS bearer quality detection. The diagram shows two lifelines: 'MC service client' and 'MC service server'. The sequence of messages is: 1. MBMS bearer quality determination (internal message on the client lifeline), 2. MBMS listening status report (message from client to server), and 3. MBMS bearer announcement (message from server to client).](49a49278cad196bdfe0db6b4dd1be7fd_img.jpg) + +``` + +sequenceDiagram + participant MC service client + participant MC service server + Note left of MC service client: 1. MBMS bearer quality determination + MC service client->>MC service server: 2. MBMS listening status report + MC service server-->>MC service client: 3. MBMS bearer announcement + +``` + +Sequence diagram for MBMS bearer quality detection. The diagram shows two lifelines: 'MC service client' and 'MC service server'. The sequence of messages is: 1. MBMS bearer quality determination (internal message on the client lifeline), 2. MBMS listening status report (message from client to server), and 3. MBMS bearer announcement (message from server to client). + +Figure 10.7.3.6.2-1: MBMS bearer quality detection + +1. The MC service client determines that the MBMS bearer quality shall be reported to the MC service server. The MC service client may determine the MBMS bearer quality by using the BLER of the received data. When no data is received, the quality estimation should consider the reference signals and the modulation and coding scheme (MCS). The UE may also use predictive methods to estimate the expected MBMS bearer quality (e.g. speed and direction) to proactively inform the MBMS service server of an expected loss of the MBMS bearer quality. + +NOTE 1: When MBSFN transmission is used, the MBSFN reference signal needs to be used and when SC-PTM is used the cell specific reference signal needs to be used. With the measured reference signal, the reference signal received quality (RSRQ) can be calculated. + +2. If the **MBMS** bearer quality reaches a certain threshold, the MC service client sends an **MBMS** listening status report. The threshold used indicates that the **MBMS** bearer is not acceptable for MC services. + +NOTE 2: Prior sending the **MBMS** listening status report, it could be beneficial to also include information for different alternatives e.g. another **MBMS** bearer might have better quality and could be a better option than a transfer of the communication to unicast. + +NOTE 3: The threshold used to indicate **MBMS** bearer quality depends on service type (i.e. MCPTT, MCVideo or MCData) and the metrics used. The metrics used and the associated thresholds are out of scope of this specification. + +3. The MC service server may send additional proposal for measurements e.g. information about neighbouring **MBMS** bearers. This message may be an **MBMS** bearer announcement message. + +#### 10.7.3.7 Service continuity in **MBMS** scenarios + +##### 10.7.3.7.1 General + +This subclause specify service continuity scenario when **MBMS** bearers are used. There are different solutions for different scenarios. + +##### 10.7.3.7.2 Service continuity when moving from one **MBSFN** to another + +The service continuity solution described in this subclause is suitable in the scenario when multiple **MBMS** bearers are used with the purpose to cover a larger area. In mission critical communication several media streams may be multiplexed in one **MBMS** bearer. Furthermore, one media stream (e.g. MCPTT group call) may be sent on more than one **MBMS** bearer if the receiving users are distributed over more than one **MBMS** service area. An MC service client that is interested in receiving a media stream that is broadcasted in both **MBMS** bearers is a candidate for this service continuity procedure. + +Figure 10.7.3.7.2-1 illustrates a deployment scenario that provides service continuity between two **MBSFN** areas. Two different **MBMS** bearers are activated (**TMGI 1** and **TMGI 2**), the activation of the bearers is done in the two **MBSFN** areas (**MBSFN 1** and **MBSFN 2**). The **MBSFN** areas 1 and 2 are partially overlapping, meaning that some transmitting cells belong to both **MBSFN** area 1 and **MBSFN** area 2. + +![Diagram illustrating two overlapping MBSFN areas, MBSFN 1 and MBSFN 2, each associated with a different TMGI (TMGI 1 and TMGI 2). The diagram shows a grid of hexagonal cells. MBSFN 1 is represented by a light blue shaded area on the left, and MBSFN 2 is represented by a light orange shaded area on the right. The two areas overlap in the center, where some cells are shaded with a grid pattern. Three mobile device icons are shown: one in a cell within MBSFN 1, one in the overlapping area, and one in a cell within MBSFN 2. Arrows indicate movement or signal flow between these areas.](745261f385368efa3f2259c8681874e9_img.jpg) + +Diagram illustrating two overlapping MBSFN areas, MBSFN 1 and MBSFN 2, each associated with a different TMGI (TMGI 1 and TMGI 2). The diagram shows a grid of hexagonal cells. MBSFN 1 is represented by a light blue shaded area on the left, and MBSFN 2 is represented by a light orange shaded area on the right. The two areas overlap in the center, where some cells are shaded with a grid pattern. Three mobile device icons are shown: one in a cell within MBSFN 1, one in the overlapping area, and one in a cell within MBSFN 2. Arrows indicate movement or signal flow between these areas. + +Figure 10.7.3.7.2-1: Two **MBMS** bearer using overlapping **MBSFN** areas + +The procedural steps will work as follows: + +1. The UE is located in **MBSFN 1** and can listen to **TMGI 1**. No additional **MBMS** bearers that the MC service client is interested in are active in the current cell. +2. The UE moves into a new cell in which both **TMGI 1** and **TMGI 2** are active. This cell is part of both **MBSFN** area 1 and **MBSFN** area 2, and broadcast the same service on both **TMGIs**. After some seconds the UE detects the new **MBMS** bearer and detects that **TMGI 2** broadcasts the same service. The UE may now listen to both **TMGI 1** and **TMGI 2** and receive duplicated packets. The MC service client must also verify that it is the same content sent on both bearers. The duplicated packets may also be used to perform error corrections. + +NOTE: It is assumed that both **MBMS** bearers are announcement to the MC service client, and the MC service UE listen to SIB-13 and (SC-)MCCH to detect these **MBMS** bearers. + +3. The UE moves into a new cell in which only **TMGI 2** is active. + +This service continuity procedure mitigates the risk of packet loss that may occur if the UE would request to transfer the media stream to a unicast bearer when moving into the new area and then back to a multicast bearer when the UE can listen to **TMGI 2**. However, it is still required that the MC service client sends a location report (and **MBMS** listening report), which means that a unicast bearer is needed. The location report from the MC service client is required, since the MC service server must know that the UE has entered a new area and can only listen to **MBMS** bearer active in that area. If this is not done the MC service server might send a media stream that the MC service client is required to listen to on the **MBMS** bearer 1, since the MC service server still assumes that the UE is located in the **MBSFN** area 1. + +The solution can be improved as illustrated in figure 10.7.3.7.2-2. In this case two different **MBMS** bearers are activated (**TMGI 1** and **TMGI 2**), these **MBMS** bearers are used only for media. An application level signalling bearer is activated (**TMGI 9**), in both **MBSFN** areas. This bearer is used for floor control messages and other application level signalling messages that are sent on the **MBMS** bearer **TMGI 9**. A similar concept was already introduced in 3GPP TS 23.179 [7] subclause 10.10.2, where the procedure allowed a separate **MBMS** bearer for floor control signalling. The application level signalling bearer will be used for all control messages needed for both media **MBMS** bearer (**TMGI 1** and **TMGI 2**). + +By using an application level signalling bearer (e.g. **TMGI 9**) the MC service clients can receive floor control messages for all calls going on in the areas of both **TMGI 1** and **TMGI 2**. A MC service client that is located in the area of **TMGI 2** and is interested in a MCPTT group call transmission only going on in **TMGI 1**, can with the information received in **TMGI 9** initiate a unicast bearer and request to receive that specific call over a unicast instead. Without the information received over **TMGI 9** the MC service client must immediately report that the MC service client has left the broadcast area that the MC service server assumes that the MC service client is located in. With the use of **TMGI 9** there is no immediate need for the MC service client to inform the MC service server of a location change. + +![Diagram illustrating two overlapping MBMS bearer areas (MBSFN 1 and MBSFN 2) with a separate MC application signalling bearer (TMGI 9). The diagram shows a network of hexagonal cells. MBSFN 1 (blue cells) and MBSFN 2 (orange cells) overlap in a central region. The central region is labeled 'TMGI 9 MBSFN 1+2'. Two mobile devices are shown: one in the blue area (MBSFN 1) and one in the orange area (MBSFN 2). Arrows indicate that both devices are receiving the TMGI 9 signalling bearer in the overlapping region.](5b6e139e89c6ce90107ea7d7d77620a0_img.jpg) + +Diagram illustrating two overlapping MBMS bearer areas (MBSFN 1 and MBSFN 2) with a separate MC application signalling bearer (TMGI 9). The diagram shows a network of hexagonal cells. MBSFN 1 (blue cells) and MBSFN 2 (orange cells) overlap in a central region. The central region is labeled 'TMGI 9 MBSFN 1+2'. Two mobile devices are shown: one in the blue area (MBSFN 1) and one in the orange area (MBSFN 2). Arrows indicate that both devices are receiving the TMGI 9 signalling bearer in the overlapping region. + +Figure 10.7.3.7.2-2: Two **MBMS** bearer using overlapping **MBSFN** areas with a separate MC application signalling bearer + +The procedural steps in this scenario will be the same as described above in this subclause. However, in this scenario the MC service client is not required to initiate a unicast bearer to send location report (or **MBMS** listening report). The UE may move between the two **MBMS** bearers (**TMGI 1** and **TMGI 2**) without the need to report an area change. A condition for this to work is that there is an application level signalling bearer (**TMGI 9**) activated in the full area (i.e. the area of both **TMGI 1** and **TMGI 2**). The **TMGI 9** will broadcast all floor control messages for all calls ongoing in both areas. If the UE is in coverage of one of the two **MBMS** bearers that does not transmit the media of interest the UE can report to the server that it is not able to listen to the media over the **MBMS** bearer, which triggers the server to use a unicast bearer instead. + +##### 10.7.3.7.3 Service continuity with a **UE-to-network relay** + +This procedure handles a scenario when UE is moving from a location when the UE is experiencing good reception of the **MBMS** bearer to a location outside the **MBMS** service coverage. The MC service client apply a service continuity + +procedure to ensure that the service can be maintained and that the packet loss can be minimized during transition to a **UE-to-network relay** connection. The solution also provides the benefit that it offloads the cell when UEs that normally would trigger a transfer from **MBMS** bearers to unicast bearers when moving outside the **MBMS** coverage area. + +Figure 10.7.3.7.3-1 below illustrates the concept of this procedure. In the figure UE A (with the MC service client) is first within the **MBMS** coverage (the far right most location). The **MBMS** coverage is represented by the dashed circle. The UE A is the moving outside the **MBMS** coverage and first enters a location in which the **MBMS** signal is not good enough, but in this location there is still coverage to use unicast bearers. Unicast bearers use link adaption and retransmission so the coverage area for unicast bearers is larger than the coverage of the **MBMS** bearers. The solid circle outer line represents the coverage of the unicast bearer. + +A UE that is leaving the area of **MBMS** coverage may in this scenario trigger a **ProSe** discovery procedure to initiate the establishment a relay communication path to UE-R. A UE that is receiving media over an **MBMS** bearer (and is in idle mode) and for the moment does not need a unicast bearer is costly (from a resource efficiency point of view) to transfer to a unicast bearer due to the need for retransmissions and robust coding in the outer part of cell. + +When the **ProSe** communication path is established the UE A may continue to receive the media over the relay UE-R. + +![Diagram illustrating UE A moving from MBMS coverage to outside network coverage via a relay UE-R.](fc0735d325f0ebd9214171975c68a888_img.jpg) + +The diagram shows a large solid circle representing 'Unicast coverage' and a smaller dashed circle inside it representing 'MBMS coverage'. Inside the dashed circle, there are two base station icons and three User Equipment (UE) icons labeled 'UE A'. Outside the dashed circle but inside the solid circle, there is one 'UE-R' (Relay UE) and two more 'UE A' icons. Red double-headed arrows indicate communication paths: one between a 'UE A' inside the dashed circle and the 'UE-R', and another between the 'UE-R' and a 'UE A' outside the dashed circle. A third red double-headed arrow shows a 'UE A' moving from inside the dashed circle towards the 'UE-R'. + +Diagram illustrating UE A moving from MBMS coverage to outside network coverage via a relay UE-R. + +**Figure 10.7.3.7.3-1: UE A is moving from a position in **MBMS** coverage to outside the network coverage passing an area where only unicast is possible** + +The procedure defined in this subclause allows for **MBMS** bearer service continuity when UE is moving from a **MBMS** coverage area to outside the **MBMS** coverage area. The procedure applies when the UE is not finding a target cell with good RSRP/RSRQ (receiving strong reference signals from other cells), which could trigger normal cell reselection procedure. In such scenario other aspects should be evaluated to trigger to a relay communication path. + +Pre-conditions: + +- The MC service client UE is not using a unicast bearer when this procedure applies. + +![Sequence diagram illustrating service continuity over MBMS bearer using UE-to-network relay. The diagram shows three participants: MC service client, UE-R, and MC service server. The sequence of steps is: 1. Estimation of the MBMS bearer quality (MC service client to itself); 2. Discovery and connection to UE-R (MC service client to UE-R); 3. Normal service continuity procedure (MC service client to MC service server); 4. Inform the UE-R about the reception of media over MBMS bearer (MC service client to UE-R); 5. UE-R relay the media received over MBMS bearer (UE-R to MC service server).](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +sequenceDiagram + participant MC service client + participant UE-R + participant MC service server + Note left of MC service client: 1. Estimation of the MBMS bearer quality + MC service client->>UE-R: 2. Discovery and connection to UE-R + Note over MC service client, MC service server: 3. Normal service continuity procedure + MC service client->>UE-R: 4. Inform the UE-R about the reception of media over MBMS bearer. + Note over UE-R, MC service server: 5. UE-R relay the media received over MBMS bearer. + +``` + +Sequence diagram illustrating service continuity over MBMS bearer using UE-to-network relay. The diagram shows three participants: MC service client, UE-R, and MC service server. The sequence of steps is: 1. Estimation of the MBMS bearer quality (MC service client to itself); 2. Discovery and connection to UE-R (MC service client to UE-R); 3. Normal service continuity procedure (MC service client to MC service server); 4. Inform the UE-R about the reception of media over MBMS bearer (MC service client to UE-R); 5. UE-R relay the media received over MBMS bearer (UE-R to MC service server). + +**Figure 10.7.3.7.3-2: Service continuity over MBMS bearer using UE-to-network relay** + +1. The MC service client estimate the **MBMS** bearer quality. The MC service clients also measure the reference signals from other cells to estimate the possibilities to transfer to unicast and perform a cell reselection procedure. +2. If the **MBMS** bearer quality has reach a certain threshold the MC service client performs **ProSe UE-to-network relay** discovery over **PC5** and establishes a secure point-to-point link with the relay (UE-R) over **PC5**. As part of this process the remote UE is mutually authenticated at **PC5** layer with either the relay or with the network as specified in 3GPP **TS 23.303** [14]. +3. Normal service continuity procedure for a **UE-to-network relay**. This may be done according to annex B. +4. The MC service client informs the UE-R about the reception of media over the **MBMS** bearer. This includes sending the **TMGIs**, **MBMS SAI**s and **ProSe** per packet priority to the UE-R. This procedure is specified in 3GPP **TS 23.303** [14]. +5. The UE-R will relay the **MBMS** media using one-to-many **ProSe** Direct Communication. The UE-R may also relay requests to transfer the media flow from multicast to unicast and vice versa. + +#### 10.7.3.8 **MBMS** suspension notification + +##### 10.7.3.8.1 Description + +In this procedure the MC service client is requested by the MC service server to send a **MBMS** suspension report. This request for **MBMS** suspension report can be included in the **MBMS** bearer announcement and the MC service server may choose to only send this request for **MBMS** suspension report to a subset of all MC service clients. + +##### 10.7.3.8.2 Procedure + +The information flow below defines a procedure in which the MC service client notifies the MC service server about an **MBMS** suspension decision in RAN. + +The MC service server can decide on a subset of all UE's in the **MBMS** broadcast area that shall report on **MBMS** bearer suspension. When the MC service server make the decision of the UE subset, consideration shall be taken to the location of the UEs, since UEs location is dynamically changed. This means that the **MBMS** suspension reporting instruction may need to be updated regularly based on the UEs mobility. + +Pre-conditions: + +- It is assumed that there is at least one active **MBMS** bearer + +![Sequence diagram illustrating MBMS suspension notification from MC service client. The diagram shows four steps: 1. MBMS suspension reporting instruction from MC service server to MC service client; 2. RAN suspend MBMS (internal RAN action); 3. MBMS suspension indication from Radio access network to MC service client; 4. MBMS suspension report from MC service client to MC service server.](3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg) + +``` + +sequenceDiagram + participant MC service client + participant Radio access network + participant MC service server + Note right of Radio access network: 2. RAN suspend MBMS + MC service server->>MC service client: 1. MBMS suspension reporting instruction + Radio access network->>MC service client: 3. MBMS suspension indication + MC service client->>MC service server: 4. MBMS suspension report + +``` + +Sequence diagram illustrating MBMS suspension notification from MC service client. The diagram shows four steps: 1. MBMS suspension reporting instruction from MC service server to MC service client; 2. RAN suspend MBMS (internal RAN action); 3. MBMS suspension indication from Radio access network to MC service client; 4. MBMS suspension report from MC service client to MC service server. + +**Figure 10.7.3.8.2-1: MBMS suspension notification from MC service client** + +1. The MC service server sends an **MBMS** suspension reporting instruction to the MC service client. + +NOTE: This message may be included in the **MBMS** bearer announcement message and may be sent both on a unicast bearer and a multicast bearer. + +2. RAN decides to suspend the **MBMS** bearer, according to existing procedures in 3GPP **TS 36.300** [21]. +3. An **MBMS** suspension indication is sent in the MSI (MCH Scheduling Information), according to existing procedures in 3GPP **TS 36.300** [21]. +4. The MC service client detect the **MBMS** suspension and sends an **MBMS** suspension report. + +MC service client that is not instructed to send an **MBMS** suspension report shall still detect the **MBMS** suspension indication from RAN (step 3). An MC service client shall in this case not send other types of report (e.g. **MBMS** listening reports). + +The same procedure can be applied at **MBMS** resumption or other **MBMS** events that may be detected by the MC service client. + +#### 10.7.3.9 Multi-server bearer coordination + +##### 10.7.3.9.1 General + +To avoid allocating duplicate bearers for an **MBMS** service area, a single MC service server may manage all the **MBMS** media transmission for all groups and users within a particular **MBMS** service area. An MC service server controlling the **MBMS** bearer has the **MBMS** bearer control role. Different MC service servers may allocate bearers as needed and make them available for other MC service servers to use. The use of the procedure in this sub clause is optional. MC system that support multi-server bearer coordination shall use this procedure. + +NOTE: Within one group communication session, multiple MC service servers (participating role) might be involved. Multiple **MBMS** service areas might have sufficient MC service group members to warrant multiple **MBMS** bearers to be used and therefore multiple MC service servers (**MBMS** bearer control role) might be involved. For brevity, this clause only illustrates the simplest case. + +##### 10.7.3.9.2 Procedures + +###### 10.7.3.9.2.1 MBMS bearer coordination independent on broadcasted media + +The procedure in this sub clause may be used when two or more MC service servers are serving users in the same area and are configured to share MBMS bearers for that specific area. The MC service servers may be of the same kind or different kind. The MC service servers are not participating in the same group call, which means that each MC service server broadcast media independently of each other. + +Pre-conditions: + +- All MC service servers are configured with the contact information of those MC service servers that are configured to take the MBMS bearer control role. + +![Sequence diagram illustrating the Multiple server MBMS procedure. The diagram shows interactions between MC service client 1, MC service server 1, MC service server 2 (MBMS bearer control role), and MC service client 2. The steps are: 1. Evaluate multicast applicability (internal to server 1); 2. Discover bearer request (server 1 to server 2); 3. Discover bearer response (server 2 to server 1); 4. MBMS bearer announcement and listening report handling (internal to server 1); 5. Media distribution request (server 1 to server 2); 6. Media distribution request response (server 2 to server 1); 7. Group communication session via the bearer is established (between server 1 and client 2); 8. Uplink media (client 2 to server 1); 9. Media (server 1 to client 2); 10. Downlink media via MBMS (server 1 to client 1); 11. Media distribution release (server 1 to server 2); 12. Media distribution release response (server 2 to server 1).](836b0790cef5469a167fa8931df4e408_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MC service client 1 + participant Server1 as MC service server 1 + participant Server2 as MC service server 2 (MBMS bearer control role) + participant Client2 as MC service client 2 + + Note right of Server1: 1. Evaluate multicast applicability + Server1->>Server2: 2. Discover bearer request + Server2-->>Server1: 3. Discover bearer response + Note right of Server1: 4. MBMS bearer announcement and listening report handling + Server1->>Server2: 5. Media distribution request + Server2-->>Server1: 6. Media distribution request response + Note over Server1, Client2: 7. Group communication session via the bearer is established + Client2->>Server1: 8. Uplink media + Server1->>Client2: 9. Media + Note right of Server1: 10. Downlink media via MBMS + Server1->>Server2: 11. Media distribution release + Server2-->>Server1: 12. Media distribution release response + +``` + +Sequence diagram illustrating the Multiple server MBMS procedure. The diagram shows interactions between MC service client 1, MC service server 1, MC service server 2 (MBMS bearer control role), and MC service client 2. The steps are: 1. Evaluate multicast applicability (internal to server 1); 2. Discover bearer request (server 1 to server 2); 3. Discover bearer response (server 2 to server 1); 4. MBMS bearer announcement and listening report handling (internal to server 1); 5. Media distribution request (server 1 to server 2); 6. Media distribution request response (server 2 to server 1); 7. Group communication session via the bearer is established (between server 1 and client 2); 8. Uplink media (client 2 to server 1); 9. Media (server 1 to client 2); 10. Downlink media via MBMS (server 1 to client 1); 11. Media distribution release (server 1 to server 2); 12. Media distribution release response (server 2 to server 1). + +Figure 10.7.3.9.2.1-1: Multiple server MBMS procedure + +1. The MC service server 1 evaluates whether multicast is desired for each service area in which MC service group members are located, based upon the locations, affiliation status and other factors. +2. The MC service server 1 determines whether another MC service server has already established a bearer with coverage for the MBMS service area where multicast is desired. To do this, the MC service server 1 consults a pre-configured list of MC service servers and sends them a discover bearer request. This request may be sent to several MC service servers. + +NOTE: MC service servers of the same type can be configured to discover bearers from a single server. The single server then becomes a centralized entity for MBMS bearer control for the MC service. Similarly, all MC service servers of all types can be configured to discover bearers from a single server. The single server then becomes a centralized MBMS bearer controller for all MC services. + +3. The MC service server 2 (MBMS bearer control role) responds with a discover bearer response indicating whether there is an MBMS bearer available in the specific MBMS service area with the requested bandwidth. The discover bearer response message includes the TMGI of the bearer that is shared between the MC service servers. If the bearer of interest has insufficient bandwidth, the polling MC service server 1 may resort to unicast, or may allocate another bearer for the congested area. If a duplicate bearer is allocated for the same area, the bearer should not be shared with other servers and may be torn down as soon as the congestion on the original bearer clears up, in order to conserve resources. + +For any MBMS service areas not covered by another MC service server, the MC service server 1 prepares to distribute media to those MBMS service areas via multicast by setting up a bearer. The bearer set up by the MC service server 1 may then become available for other MC service servers (controlling role) for other MC service groups. + +4. The MC service server 1 performs the MBMS bearer announcement and the MBMS listening reporting according relevant procedures specified in this specification. If the MC service server 2 is authorized to receive MBMS related location information from the users utilizing the services from MC service server 1, the MC service server 2 may optionally do the MBMS bearer announcement and handling the listening reports on behalf of MC service server 1. Listening reports shall in this case be sent to both MC service server 1 and MC service server 2. +5. The MC service server 1 sends a media distribution request to the MC service server 2 (MBMS bearer control role). The media distribution request is sent to reserve the specified capacity in the MBMS bearer. +6. MC service server 2 (MBMS bearer control role) sends a media distribution response to the MC service server 1 indicating whether the request can be supported and supplies details about the bearer. +7. The MC service server 1 establishes a group communication session via the bearer, informing MBMS connected MC service clients 1 and 2 that a group communication session is about to start on the MBMS bearer. This step is equivalent to MapGroupToBearer in MCPTT. +8. MC service client 2 sends media on the uplink to the MC service server 1 +9. The MC service server 1 forwards the media to MC service server 2 (MBMS bearer control role). +10. The MC service server 2 (MBMS bearer control role) distributes the media to MBMS served MC service client 1 via multicast. +11. The MC service server 1 sends a media distribution release request, informing the MC service server 2 (MBMS bearer control role) to request the MC service server 2 (MBMS bearer control role) to release the capacity that was reserved in step 5. +12. The MC service server 2 (MBMS bearer control role) respond to the request by sending a media distribution release request. + +###### 10.7.3.9.2.2 MBMS bearer coordination within one group call + +The procedure in this sub clause may be used when two MC service servers are serving users in the same area and are configured to share MBMS bearers for that specific area. The MC service servers are of the same kind, and the MC service servers may participate in the same group call, and by that have a need to broadcast the same content. + +Pre-conditions: + +- All MC service servers are configured with the contact information of those MC service servers that are configured to take the MBMS bearer control role. + +![Sequence diagram illustrating the Multiple server MBMS procedure. The diagram shows interactions between MC service client 1, MC service server 1, MC service server 2 (MBMS bearer control role), MC service client 2, and MC service server 3. The process involves evaluating multicast applicability, discovering bearers, announcing bearers, initiating a group communication session, distributing media, and releasing the distribution.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 + participant MC service server 1 + participant MC service server 2 as MC service server 2 (MBMS bearer control role) + participant MC service client 2 + participant MC service server 3 + + Note right of MC service server 1: 1. Evaluate multicast applicability + MC service server 1->>MC service server 2: 2. Discover bearer request + MC service server 2-->>MC service server 1: 3. Discover bearer response + Note right of MC service server 1: 4. MBMS bearer announcement and listening report handling + Note over MC service client 2: 5. Group communication session Initiation initiated by MC service client 2 + MC service server 1->>MC service server 2: 6a. Media distribution request + MC service server 2-->>MC service server 1: 7b. Media distribution request response + MC service client 2->>MC service server 3: 6b. Media distribution request + MC service server 3-->>MC service client 2: 7b. Media distribution request response + Note right of MC service server 1: 8a. Media + Note right of MC service server 1: 8b. Media + MC service server 1->>MC service server 2: 9. Media to be broadcasted + Note right of MC service client 1: 10. Downlink media via MBMS + MC service server 1->>MC service server 2: 11. Media distribution release + MC service server 2-->>MC service server 1: 12. Media distribution release response + +``` + +Sequence diagram illustrating the Multiple server MBMS procedure. The diagram shows interactions between MC service client 1, MC service server 1, MC service server 2 (MBMS bearer control role), MC service client 2, and MC service server 3. The process involves evaluating multicast applicability, discovering bearers, announcing bearers, initiating a group communication session, distributing media, and releasing the distribution. + +**Figure 10.7.3.9.2.2-1: Multiple server MBMS procedure** + +1. The MC service server 1 evaluates whether multicast is desired for each service area in which MC service group members are located, based upon the locations, affiliation status and other factors. +2. The MC service server 1 determines whether another MC service server has already established a bearer with coverage for the **MBMS** service area where multicast is desired. To do this, the MC service server 1 consults a pre-configured list of MC service servers and sends them a discover bearer request. This request may be sent to several MC service servers. + +NOTE 1: MC service servers of the same type can be configured to discover bearers from a single server. The single server then becomes a centralized entity for **MBMS** bearer control for the MC service. Similarly, all MC service servers of all types can be configured to discover bearers from a single server. The single server then becomes a centralized **MBMS** bearer controller for all MC services. + +3. The MC service server 2 (**MBMS** bearer control role) responds with a discover bearer response indicating whether there is an **MBMS** bearer available in the specific **MBMS** service area with the requested bandwidth. The discover bearer response message includes the **TMGI** of the bearer that is shared between the MC service servers. If the bearer of interest has insufficient bandwidth, the polling MC service server 1 may resort to unicast, or may allocate another bearer for the congested area. If a duplicate bearer is allocated for the same area, the bearer should not be shared with other servers and may be torn down as soon as the congestion on the original bearer clears up, in order to conserve resources. + +For any **MBMS** service areas not covered by another MC service server, the MC service server 1 prepares to distribute media to those **MBMS** service areas via multicast by setting up a bearer. The bearer set up by the MC service server 1 may then become available for other MC service servers (controlling role) for other MC service groups. + +4. The MC service server 1 performs the **MBMS** bearer announcement and the **MBMS** listening reporting according relevant procedures specified in this specification. If the MC service server 2 is authorized to receive **MBMS** related location information from the users utilizing the services from MC service server 1, the MC service server 2 may optionally do the **MBMS** bearer announcement and handling the listening reports on behalf of MC service server 1. Listening reports shall in this case be sent to both MC service server 1 and MC service server 2. + +NOTE 2: Step 1-4 is also performed by MC service server 3, but is not shown in the procedure to make it easier to read. + +5. The MC service client 2 initiate a group call that is subject for multicast transmission. In this scenario there are more than one MC service server (i.e. MC service server 1 and MC service server 3) that serves MC service clients that are affiliated to the group, and by that should receive the media in the group call. +- 6a. The MC service server 1 sends a media distribution request to the MC service server 2 (**MBMS** bearer control role). The media distribution request includes the MC group identifier. This indicates that the media distribution request is used for this specific group call. +- 6b. The MC service server 3 sends a media distribution request to the MC service server 2 (**MBMS** bearer control role). The media distribution request includes the MC group identifier. This indicates that the media distribution request is used for this specific group call. +- 7a. The MC service server 2 (**MBMS** bearer control role) sends a media distribution response to the MC service server 1 indicating whether the request can be supported and supplies details about the bearer. This also includes details on which media stream that should be used for broadcasting the media on the **MBMS** bearer. This information is used in the MapGroupToBearer message sent by the MC service server when setting up the group call. +- 7b. The MC service server 2 (**MBMS** bearer control role) sends a media distribution response to the MC service server 3 indicating that the group call is already transmitted on the **MBMS** bearer by another MC service server. Based on the information, the MC service server 3 could decide to not broadcast media if media is already being broadcasted. +- 8a. The media is sent from the MC service client 2 to MC service server 1, which is the participating server for the MC service group of the group call. +- 8b. The media is forwarded to all MC service servers that are serving users that takes part in the group call. + +NOTE 3: The figure above does not visualize the participating server for the MC service group and controlling server for the MC service group. The media is sent to all participating servers for the MC service group which are the servers that decide on unicast or multicast transmission. + +9. The MC service server 1 forwards the media to MC service server 2 (**MBMS** bearer control role). +10. The MC service server 2 (**MBMS** bearer control role) distributes the media to **MBMS** served MC service client 1 via multicast. +11. The MC service server 1 sends a media distribution release request, informing the MC service server 2 (**MBMS** bearer control role) to request the MC service server 2 (**MBMS** bearer control role) to release the capacity that was reserved in step 5. The media distribution release request shall only be sent when the group call is terminated. +12. The MC service server 2 (**MBMS** bearer control role) respond to the request by sending a media distribution release request. + +#### 10.7.3.10 **MBMS** bearer event notification + +##### 10.7.3.10.1 General + +The MC service server is an instantiation of a GCS AS. For the MC service server to know the status of the **MBMS** bearer, and thus know the networks ability to deliver the service, it is required that the network provides **MBMS** bearer event notifications to the MC service server. The different events notified to the MC service server include the **MBMS** bearer start result (e.g. when the first cell successfully allocated **MBMS** resources), including information if any cells fail to allocate **MBMS** resources to a specific **MBMS** bearer, the current status of the **MBMS** bearer, **MBMS** bearer suspension/resume or overload scenarios. + +Editor's note: The procedure defined in this sub clause requires an enhancement to GCSE and RAN and is therefore subject to implementation in EPC and RAN. + +##### 10.7.3.10.2 Procedure + +The procedure in figure 10.7.3.10.2-1 shows notification information flows from MC service server to BM-SC. + +![Sequence diagram illustrating the MBMS bearer event notification procedure. The diagram shows three main entities: MC service client, EPS (BM-SC), and MC service server. The sequence of messages is: 1. MC service server sends an 'Activate MBMS bearer request' to EPS (BM-SC). 2. EPS (BM-SC) responds with an 'Activate MBMS bearer response'. 3. EPS (BM-SC) initiates 'MBMS session setup procedures and MBMS resources allocation in RAN'. 4. EPS (BM-SC) sends an 'MBMS bearer event notification' to MC service server. 5. MC service server starts to use the MBMS bearer. 6. EPS (BM-SC) receives an 'Event received from RAN related to the MBMS session'. 7. EPS (BM-SC) sends another 'MBMS bearer event notification' to MC service server. 8. MC service server decides to switch to unicast for MC service clients in specific areas.](5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg) + +``` + +sequenceDiagram + participant MC service client + participant EPS (BM-SC) + participant MC service server + + Note right of MC service server: 1. Activate MBMS bearer request + MC service server->>EPS (BM-SC): 1. Activate MBMS bearer request + Note right of EPS (BM-SC): 2. Activate MBMS bearer response + EPS (BM-SC)-->>MC service server: 2. Activate MBMS bearer response + Note right of EPS (BM-SC): 3. MBMS session setup procedures and MBMS resources allocation in RAN + EPS (BM-SC)->>MC service server: 4. MBMS bearer event notification + Note right of MC service server: 5. MC service server starts to use the MBMS bearer + Note right of EPS (BM-SC): 6. Event received from RAN related to the MBMS session + EPS (BM-SC)->>MC service server: 7. MBMS bearer event notification + Note right of MC service server: 8. MC service server decide to switch to unicast for MC service clients in specific areas + +``` + +Sequence diagram illustrating the MBMS bearer event notification procedure. The diagram shows three main entities: MC service client, EPS (BM-SC), and MC service server. The sequence of messages is: 1. MC service server sends an 'Activate MBMS bearer request' to EPS (BM-SC). 2. EPS (BM-SC) responds with an 'Activate MBMS bearer response'. 3. EPS (BM-SC) initiates 'MBMS session setup procedures and MBMS resources allocation in RAN'. 4. EPS (BM-SC) sends an 'MBMS bearer event notification' to MC service server. 5. MC service server starts to use the MBMS bearer. 6. EPS (BM-SC) receives an 'Event received from RAN related to the MBMS session'. 7. EPS (BM-SC) sends another 'MBMS bearer event notification' to MC service server. 8. MC service server decides to switch to unicast for MC service clients in specific areas. + +Figure 10.7.3.10.2-1: MBMS bearer event notification + +1. The MC service server activates an MBMS bearer. The activation of the MBMS bearer is done on the MB2-C reference point and according to 3GPP TS 23.468 [18]. +2. The BMSC will respond to the activation with an Activate MBMS bearer response message, according to 3GPP TS 23.468 [18]. +3. The EPC and RAN will initiate the MBMS session start procedure according to 3GPP TS 23.246 [11]. This procedure is outside the scope of this specification. +4. At the first indication of a successful MBMS session start procedure, the BM-SC sends a MBMS bearer event notification, indicating that the MBMS bearer is ready to use. +5. The MC service server starts to use the MBMS bearer according to the MBMS procedures in this specification. +6. An event from RAN related to the MBMS session is received by the BM-SC. +7. The BM-SC notifies the MC service server of certain MBMS related events including references to affected MBMS services areas or list of cells. Example of such events may be radio resources not available, overload, MBMS suspension. +8. The MC service server may decide, based on the received events, to switch to unicast transmission for relevant MC service clients. + +NOTE: Steps 6-8 should be seen as example events from the network that may occur and possible actions taken by the MC service server. These steps may be done at any time and repeatedly during the life time of an MBMS bearer. + +#### 10.7.3.11 Use of FEC to protect MBMS transmissions + +##### 10.7.3.11.1 General + +Application layer FEC can be used to recover the packet losses when delivering a MC service over MBMS, to reach its required level of QoS. + +Support of FEC is optional for the MC service servers and MC service clients + +Adding FEC introduces an extra latency in the end to end media transport. This extra latency is bounded to fulfil the low latency requirements for mission critical services. + +FEC can be applied by the BM-SC if required by the MC service server (subclause 10.7.3.11.2), or directly by the MC service server (subclause 10.7.3.11.3). FEC is decoded by the MC service client. Either method is independent of the other. + +The MC service server may consider the listening status reports from previous MBMS bearer quality detection procedures (subclause 10.7.3.6) to adjust the FEC parameters when delivering over a new MBMS bearer. + +##### 10.7.3.11.2 FEC encoding by the BM-SC + +In this procedure, depicted in figure 10.7.3.11.2-1, the MC service server asks the BM-SC to apply FEC to a set of medias, transported by a MBMS bearer, using the Setup FEC request. + +This procedure can be applied when using pre-established MBMS bearers (10.7.3.1) or dynamic MBMS bearers (10.7.3.2). + +Pre-condition: + +1. The MC service server has already activated a MBMS Bearer, with the MBMS Bearer request specified in 3GPP TS 23.468 [18]. + +![Sequence diagram illustrating the application of FEC by the BM-SC. The diagram shows three main entities: MC service client, BM-SC, and MC service server. The sequence of interactions is: 1. Setup FEC request from MC service server to BM-SC; 2. Setup FEC response from BM-SC to MC service server; 3. MBMS Bearer announcement from BM-SC to MC service client; 4. Signaling group communication session over the MBMS bearer from BM-SC to MC service client; 5. DL payload media from MC service server to BM-SC; 6. DL payload media with FEC from BM-SC to MC service client; 7. FEC decoding of media by MC service client.](61d6d7aae4cc4d0310bdf9ec29e221c5_img.jpg) + +``` + +sequenceDiagram + participant MC service client + participant BM-SC + participant MC service server + Note right of BM-SC: 1. Setup FEC request + MC service server->>BM-SC: 1. Setup FEC request + Note right of BM-SC: 2. Setup FEC response + BM-SC->>MC service server: 2. Setup FEC response + Note right of BM-SC: 3. MBMS Bearer announcement + BM-SC->>MC service client: 3. MBMS Bearer announcement + Note right of BM-SC: 4. Signaling group communication session over the MBMS bearer + BM-SC->>MC service client: 4. Signaling group communication session over the MBMS bearer + Note right of MC service server: 5. DL payload media + MC service server->>BM-SC: 5. DL payload media + Note right of BM-SC: 6. DL payload media with FEC + BM-SC->>MC service client: 6. DL payload media with FEC + Note left of MC service client: 7. FEC decoding of media + MC service client->>MC service client: 7. FEC decoding of media + +``` + +Sequence diagram illustrating the application of FEC by the BM-SC. The diagram shows three main entities: MC service client, BM-SC, and MC service server. The sequence of interactions is: 1. Setup FEC request from MC service server to BM-SC; 2. Setup FEC response from BM-SC to MC service server; 3. MBMS Bearer announcement from BM-SC to MC service client; 4. Signaling group communication session over the MBMS bearer from BM-SC to MC service client; 5. DL payload media from MC service server to BM-SC; 6. DL payload media with FEC from BM-SC to MC service client; 7. FEC decoding of media by MC service client. + +Figure 10.7.3.11.2-1: Application of FEC by the BM-SC + +1. The MC service server decides to set up FEC for a set of MC service media flows. The request is done on the MB2-C reference point. It includes the following elements: the TMGI of the bearer transporting those media, the media descriptions (codecs, transport protocols, bitrates, destination ip addresses and ports), the identification of + +the FEC repair packet flow (IP destination and port), an upper bound to the additional latency resulting to FEC application. The MC Service server may perform this request several times to protect separately different sets of media transported within the same **MBMS** bearer. + +2. If the **BM-SC** can satisfy the request, the Setup FEC response includes a modified list of media information and FEC information. The response also includes an identifier to the FEC process instance, which can be used to release the application of FEC for these media flows. + +NOTE 1: Source media packets may be modified by the application of FEC (e.g. addition of a footer of header), leading to a modification of the delivery protocol to be announced within the media information. + +NOTE 2: The Release FEC request is not shown on the figure. + +3. The MC service server announces the **MBMS** bearer to the MC service client with the **MBMS** bearer announcement procedure, including the modified list of media information and FEC information within the SDP information. +4. When the MC service server decides to transmit the MC service media flow for a group communication, the MC service server sends to the group a message identifying the MC service media flow and the **TMGI** of the **MBMS** bearer, such as the MapGroupToBearer message for MCPTT, specified in 3GPP TS 23.379 [16], or the MapGroupToBearer message for MCVideo, specified in 3GPP TS 23.380 [12]. +5. The MC service server sends the downlink media to the **BM-SC** on the **MB2-U** reference points and according to 3GPP TS 23.468 [18]. +6. The **BM-SC** performs FEC encoding of the downlink media in accordance to the announced FEC algorithm and parameters and delivers it over **MBMS**. +7. The MC service client performs FEC decoding of the encoded media flows in accordance to the announced FEC information and delivers the decoded flows to the media player. + +NOTE 3: This procedure requires modifications to the 3GPP TS 23.468 [18], to include the new requests/responses mentioned in steps 1 and 2. It requires a **BM-SC** enhancement and can therefore only be used if supported by **BM-SC**. + +**Editor's note: the need for a MC service server ability to turn off/on the production of repair packets on the **BM-SC** during the media transmission must be discussed, and may impact the procedure.** + +##### 10.7.3.11.3 FEC encoding by the MC service server + +In this procedure, depicted in figure 10.7.3.11.3-1, FEC encoding is performed by the MC service server. The MC service server includes the FEC information within the **MBMS** bearer announcement. The FEC decoding is performed by the MC service client. + +![Sequence diagram illustrating the application of FEC by the MC service server. The diagram shows interactions between an MC service client and an MC service server. The server performs internal steps: 1. MBMS bearer announcement (sent to client), 2. Media distribution, 3. FEC encoding of media. The client performs 5. FEC decoding of media. The server sends 4. DL Media with FEC to the client via a large arrow.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` + +sequenceDiagram + participant Client as MC service client + participant Server as MC service server + Note right of Server: 1. MBMS bearer announcement + Server->>Client: 1. MBMS bearer announcement + Note right of Server: 2. Media distribution + Note right of Server: 3. FEC encoding of media + Note right of Server: 4. DL Media with FEC + Server->>Client: 4. DL Media with FEC + Note left of Client: 5. FEC decoding of media + +``` + +Sequence diagram illustrating the application of FEC by the MC service server. The diagram shows interactions between an MC service client and an MC service server. The server performs internal steps: 1. MBMS bearer announcement (sent to client), 2. Media distribution, 3. FEC encoding of media. The client performs 5. FEC decoding of media. The server sends 4. DL Media with FEC to the client via a large arrow. + +**Figure 10.7.3.11.3-1: Application of FEC by the MC service server** + +1. The MC service server sends **MBMS** bearer announcement message with FEC information to the MC service clients. +2. As media packets arrive from the originating MC service UE (not shown in diagram), the media is processed by the media distribution function on the MC service server. +3. The MC service server performs FEC encoding and processing in accordance with the selected FEC algorithm. +4. The MC service server sends the media with FEC to the MC service client (both payload source packets and the FEC repair packets are sent on the **MB2-U** to the **BM-SC**, which transparently forwards them unmodified to the MC service client). +5. MC service client performs FEC decoding and processing in accordance with the selected FEC algorithm + +#### 10.7.3.12 Header compression over **MBMS** with ROHC + +##### 10.7.3.12.1 General + +Support of ROHC over **MBMS** is optional for the MC service servers and MC service clients. If header compression and FEC are both applied to a communication over **MBMS**, the header compression shall be performed after the FEC encoding. + +These procedures can be applied when using pre-established **MBMS** bearers (see clause 10.7.3.1) or dynamic **MBMS** bearers (see clause 10.7.3.2). + +##### 10.7.3.12.2 Header compression by the MC service server + +In this procedure, depicted in figure 10.7.3.12.2-1, header compression is performed by the MC service server. The MC service server includes the ROHC information within the **MBMS** bearer announcement. The header decompression is performed by the MC service client. + +![Sequence diagram illustrating header compression by the MC service server. The diagram shows interactions between an MC service client and an MC service server. The sequence of steps is: 1. MBMS Bearer announcement (server to client), 2. Signaling group communication session over the MBMS bearer (server to client), 3. Media distribution (server to client), 4. Header compression (server to client), 5. DL Media (server to client), and 6. Header decompression (client to server).](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +``` + +sequenceDiagram + participant Client as MC service client + participant Server as MC service server + Note right of Server: 1. MBMS Bearer announcement + Note right of Server: 2. Signaling group communication session over the MBMS bearer + Note right of Server: 3. Media distribution + Note right of Server: 4. Header compression + Note right of Server: 5. DL Media + Note left of Client: 6. Header decompression + +``` + +Sequence diagram illustrating header compression by the MC service server. The diagram shows interactions between an MC service client and an MC service server. The sequence of steps is: 1. MBMS Bearer announcement (server to client), 2. Signaling group communication session over the MBMS bearer (server to client), 3. Media distribution (server to client), 4. Header compression (server to client), 5. DL Media (server to client), and 6. Header decompression (client to server). + +**Figure 10.7.3.12.2-1: Header compression by the MC service server** + +1. The MC service server sends **MBMS** bearer announcement message with ROHC information to the MC service clients. The ROHC information contains the list of ROHC profiles and the ROHC context identifier range). +2. When the MC service server decides to transmit the MC service media flow for a group communication, the MC service server sends to the group a message identifying the MC service media flow and the **TMGI** of the **MBMS** bearer, such as the MapGroupToBearer message for MCPTT, specified in 3GPP TS 23.379 [16], or the MapGroupToBearer message for MCVideo, specified in 3GPP TS 23.281 [12]. +3. As media packets arrive from the originating MC service UE (not shown in diagram), the media is processed by the media distribution function on the MC service server. +4. The MC service server performs header compression in accordance with the ROHC information. +5. The MC service server sends the header compressed media to the MC service client +6. The MC service client performs header decompression in accordance to the ROHC information + +##### 10.7.3.12.3 Header compression by the **BM-SC** + +In this procedure, depicted in figure 10.7.3.12.3-1, the MC service server asks the **BM-SC** to compress headers for a set of medias, transported by a **MBMS** bearer, using the Setup ROHC request. + +Pre-condition: + +1. The MC service server has already activated a **MBMS** Bearer, with the **MBMS** Bearer request specified in 3GPP **TS 23.468** [18]. + +![Sequence diagram illustrating header compression by the BM-SC. The diagram shows three main entities: MC service client, BM-SC, and MC service server. The sequence of interactions is: 1. Setup ROHC request from MC service server to BM-SC; 2. Setup ROHC response from BM-SC to MC service server; 3. MBMS Bearer announcement from MC service server to MC service client; 4. Signaling group communication session over the MBMS bearer from MC service server to MC service client; 5. DL media from MC service server to BM-SC; 6. DL header compressed media from BM-SC to MC service client; 7. Header decompression at the MC service client.](8269648391c59363ea61243864a2adf7_img.jpg) + +``` + +sequenceDiagram + participant MC service client + participant BM-SC + participant MC service server + Note right of MC service server: 1. Setup ROHC request + MC service server->>BM-SC: 1. Setup ROHC request + Note right of BM-SC: 2. Setup ROHC response + BM-SC->>MC service server: 2. Setup ROHC response + Note right of MC service server: 3. MBMS Bearer announcement + MC service server->>MC service client: 3. MBMS Bearer announcement + Note right of MC service server: 4. Signaling group communication session over the MBMS bearer + MC service server->>MC service client: 4. Signaling group communication session over the MBMS bearer + Note right of MC service server: 5. DL media + MC service server->>BM-SC: 5. DL media + Note right of BM-SC: 6. DL header compressed media + BM-SC->>MC service client: 6. DL header compressed media + Note left of MC service client: 7. Header decompression + MC service client->>MC service client: 7. Header decompression + +``` + +Sequence diagram illustrating header compression by the BM-SC. The diagram shows three main entities: MC service client, BM-SC, and MC service server. The sequence of interactions is: 1. Setup ROHC request from MC service server to BM-SC; 2. Setup ROHC response from BM-SC to MC service server; 3. MBMS Bearer announcement from MC service server to MC service client; 4. Signaling group communication session over the MBMS bearer from MC service server to MC service client; 5. DL media from MC service server to BM-SC; 6. DL header compressed media from BM-SC to MC service client; 7. Header decompression at the MC service client. + +**Figure 10.7.3.12.3-1: Header compression by the BM-SC** + +1. The MC service server decides to set up ROHC within a **MBMS** bearer. The request is done on the **MB2-C** reference point. It includes the following elements: the ROHC configuration, the list of RTP and UDP flows to be header compressed, characterized by their destination IPs and port numbers. For each of these flows, the request may indicate a target periodicity for the full header packets. + +NOTE 1: The MC service server can later modify the ROHC configuration by performing again the Setup ROHC request. + +NOTE 2: The Release ROHC request is also not shown on the figure. + +2. If the **BM-SC** can satisfy the request, the Setup ROHC response confirm the application of header compression. +3. The MC service server announces the **MBMS** bearer to the MC service client with the **MBMS** bearer announcement procedure, including the ROHC information. +4. When the MC service server decides to transmit the MC service media flow for a group communication, the MC service server sends to the group a message identifying the MC service media flow and the **TMGI** of the **MBMS** bearer, such as the MapGroupToBearer message for MCPTT, specified in 3GPP TS 23.379 [16], or the MapGroupToBearer message for MCVideo, specified in 3GPP TS 23.281 [12]. +5. The MC service server sends the downlink media to the **BM-SC** on the **MB2-U** reference points and according to 3GPP TS 23.468 [18]. +6. The **BM-SC** compresses headers of the downlink media in accordance to the announced ROHC parameters and delivers it over **MBMS**. +7. The MC service client performs header decompression in accordance to the ROHC information. + +Editor's note: This procedure requires modifications to the 3GPP TS 23.468 [18], to include the new requests/responses mentioned in steps 1 and 2. It requires a **BM-SC** enhancement and can therefore only be used if supported by **BM-SC**. + +## 10.8 Affiliation and de-affiliation to/from MC service group(s) + +### 10.8.1 General + +The following subclauses specify the procedures for affiliation and de-affiliation to a single MC service, and which are utilised by the following MC services: + +- MCPTT (as specified in 3GPP TS 23.379 [16]); +- MCVideo (as specified in 3GPP TS 23.281 [12]); and +- MCData (as specified in 3GPP TS 23.282 [13]). + +MC service specific pre-requisites and resultant behaviour by functional entities in performing these procedures are specified in the respective MC service TSs as listed above. + +### 10.8.2 Information flows + +#### 10.8.2.1 MC service group affiliation request + +Table 10.8.2.1-1 describes the information flow MC service group affiliation request from the MC service client to the MC service server. + +**Table 10.8.2.1-1: MC service group affiliation request** + +| Information element | Status | Description | +|--------------------------|--------|--------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the MC service group affiliation request. | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to affiliate. | + +#### 10.8.2.2 MC service group affiliation request (MC service server – MC service server) + +Table 10.8.2.2 -1 describes the information flow MC service group affiliation request between the MC service servers. + +**Table 10.8.2.2-1: MC service group affiliation request** + +| Information element | Status | Description | +|--------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the MC service group affiliation request. | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to affiliate and is defined in the destination MC system. | + +#### 10.8.2.3 MC service group affiliation response + +Table 10.8.2.3-1 describes the information flow MC service group affiliation response from the MC service server to the MC service client. + +**Table 10.8.2.3-1: MC service group affiliation response** + +| Information element | Status | Description | +|--------------------------------------------|--------|--------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the MC service group affiliation request. | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to affiliate. | +| Affiliation status per MC service group ID | M | Indicates the affiliation result for every MC service group ID in the list. | + +#### 10.8.2.4 MC service group affiliation response (MC service server – MC service server) + +Table 10.8.2.4-1 describes the information flow MC service group affiliation response between the MC service servers. + +**Table 10.8.2.4-1: MC service group affiliation response** + +| Information element | Status | Description | +|--------------------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the MC service group affiliation request. | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to affiliate and is defined in the destination MC system. | +| Affiliation status per MC service group ID | M | Indicates the affiliation result for every MC service group ID in the list. | + +#### 10.8.2.5 Group affiliation status update + +Table 10.8.2.5-1 describes the information flow group affiliation status update from the MC service server to the group management server. + +**Table 10.8.2.5-1: group affiliation status update** + +| Information element | Status | Description | +|--------------------------------------------|--------|--------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID for which the group affiliation status needs to be updated. | +| MC service group ID list | M | A list of one or more MC service group IDs for which the affiliation status needs to be updated. | +| Affiliation status per MC service group ID | M | Indicates the affiliation status for every MC service group ID in the list. | + +#### 10.8.2.6 MC service group de-affiliation request + +Table 10.8.2.6-1 describes the information flow MC service group de-affiliation request from the MC service client to the MC service server. + +**Table 10.8.2.6-1: MC service group de-affiliation request** + +| Information element | Status | Description | +|--------------------------|--------|-----------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the MC service group de-affiliation request. | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to de-affiliate. | + +#### 10.8.2.7 MC service group de-affiliation request (MC service server – MC service server) + +Table 10.8.2.7-1 describes the information flow MC service group de-affiliation request between the MC service servers. + +**Table 10.8.2.7-1: MC service group de-affiliation request** + +| Information element | Status | Description | +|--------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the MC service group de-affiliation request. | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to de-affiliate and is defined in the destination MC system. | + +#### 10.8.2.8 MC service group de-affiliation response + +Table 10.8.2.8-1 describes the information flow MC service group de-affiliation response from the MC service server to the MC service client. + +**Table 10.8.2.8-1: MC service group de-affiliation response** + +| Information element | Status | Description | +|-----------------------------------------------|--------|-----------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the MC service group de-affiliation request. | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to de-affiliate. | +| De-affiliation status per MC service group ID | M | Indicates the de-affiliation result for every MC service group ID in the list. | + +#### 10.8.2.9 MC service group de-affiliation response (MC service server – MC service server) + +Table 10.8.2.9-1 describes the information flow MC service group de-affiliation response between MC service servers. + +**Table 10.8.2.9-1: MC service group de-affiliation response** + +| Information element | Status | Description | +|-----------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the MC service group de-affiliation request. | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to de-affiliate and is defined in the destination MC system. | +| De-affiliation status per MC service group ID | M | Indicates the de-affiliation result for every MC service group ID in the list. | + +#### 10.8.2.10 Group de-affiliation status update + +Table 10.8.2.10-1 describes the information flow group de-affiliation status update from the MC service server to the group management server. + +**Table 10.8.2.10-1: group de-affiliation status update** + +| Information element | Status | Description | +|-----------------------------------------------|--------|-----------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID for which the group de-affiliation status needs to be updated. | +| MC service group ID list | M | A list of one or more MC service group IDs for which the de-affiliation status needs to be updated. | +| De-affiliation status per MC service group ID | M | Indicates the de-affiliation status for every MC service group ID in the list. | + +#### 10.8.2.11 MC service group affiliation change request + +Table 10.8.2.11-1 describes the information flow MC service group affiliation change request from the MC service client to the MC service server. + +**Table 10.8.2.11-1: MC service group affiliation change request** + +| Information element | Status | Description | +|-----------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the MC service group affiliation change request. | +| MC service ID list | M | A list of one or more MC service IDs to which the originator intends to change their MC service group affiliation relationship. | +| MC service group ID list (per listed MC service ID) | M | A list of one or more MC service group IDs to which the originator intends to change their affiliation relationship with the target user. | +| Requested affiliation status (per group ID) | M | Indicates if the request is to affiliate or deaffiliate | +| Change request type | M | Indicates the affiliation request type, i.e. mandatory or negotiated | + +#### 10.8.2.12 MC service group affiliation change response + +Table 10.8.2.12-1 describes the information flow MC service group affiliation change response from the MC service server to the MC service client. + +**Table 10.8.2.12-1: MC service group affiliation change response** + +| Information element | Status | Description | +|--------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the MC service group affiliation request. | +| MC service ID list | M | A list of one or more MC service IDs to which the originator intends to change their MC service group affiliation relationship. | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to change their affiliation relationship with the target user. | +| Affiliation status per MC service group ID | M | Indicates the affiliation relationship change result for every MC service group ID in the list. | + +#### 10.8.2.13 MC service group de-affiliation notification + +Table 10.8.2.13-1 describes the information flow MC service group de-affiliation notification from the MC service server to the MC service client. + +**Table 10.8.2.13-1: MC service group de-affiliation notification** + +| Information element | Status | Description | +|-----------------------------------------------|--------|---------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the MC service user that will be de-affiliated. | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to de-affiliate. | +| De-affiliation status per MC service group ID | M | Indicates the de-affiliation result for every MC service group ID in the list. | + +### 10.8.3 Affiliation + +#### 10.8.3.1 MC service group affiliation procedure + +Procedure for affiliation to MC service group(s) for a single MC service is described in figure 10.8.3.1-1. + +Pre-conditions: + +1. MC service client has already been provisioned (statically or dynamically) with the group information, or a pointer to the group information, that the MC service client is allowed to be affiliated. +2. MC service server may have retrieved the user subscription and group policy e.g. which user(s) are authorized to affiliate to what MC service group(s), priority, and other configuration data. + +3. MC service client may have indicated to the group management server that it wishes to receive updates of group configuration data for MC service groups(s) for which it is authorized (as described in subclause 10.1.5.3). +4. The MC service client triggers the affiliation procedure. This is an explicit affiliation caused either by the MC service user or determined by a trigger event such as the MC service UE coming within a permitted geographic operational area of an MC service group. + +![Sequence diagram showing the MC service group affiliation procedure between MC service client, MC service server, and Group management server.](7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg) + +``` + +sequenceDiagram + participant MC service client + participant MC service server + participant Group management server + + Note right of MC service server: 3.Authorization check based on group policy, user subscription and N2 limit check + Note right of MC service server: 4.Store group affiliation status + + MC service client->>MC service server: 1.MC service group affiliation request + MC service server-->>Group management server: 2a.Subscribe group policy + Group management server-->>MC service server: 2b.Notify group policy + MC service server-->>MC service client: 5a.MC service group affiliation response + MC service server->>Group management server: 5b.Group affiliation status update (MC service ID, MC service group ID(s)) + +``` + +Sequence diagram showing the MC service group affiliation procedure between MC service client, MC service server, and Group management server. + +**Figure 10.8.3.1-1: MC service group affiliation procedure** + +1. MC service client of the MC service user requests the MC service server to affiliate to an MC service group or a set of MC service groups. +- 2a. MC service server checks if the group policy is locally cached. If the group policy is not locally cached on the MC service server then MC service server requests the group policy from the group management server. +- 2b. MC service server receives the group policy from the group management server. +3. Based on the group policy and user subscription, the MC service server checks if the MC service group(s) is enabled and if the MC service client is authorised to affiliate to the requested MC service group(s). The MC service server also performs the check for the maximum limit of the total number (N2) of MC service groups that the user can be affiliated to simultaneously. +4. If the user of the MC service client is authorised to affiliate to the requested MC service group(s) then the MC service server stores the affiliation status of the user for the requested MC service group(s). +5. MC service server confirms to the MC service client the affiliation (5a) and updates the group management server with the affiliation status of the user for the requested MC service group(s) (5b). + +NOTE: Steps 5a and 5b can occur in any order or in parallel. + +#### 10.8.3.2 Affiliation to MC service group(s) defined in partner MC system without topology hiding + +##### 10.8.3.2.1 Functional description + +When an MC service client wants to affiliate to MC service group(s) which is defined in a partner MC system for a single MC service and where topology hiding is not required, it shall be subject to authorization from the partner MC system where the MC service group(s) is defined, and whether it subjects to authorization from the primary MC system is conditional. + +##### 10.8.3.2.2 Procedure + +The procedure for affiliation to MC service group(s) which is defined in a partner MC system where topology hiding is not required for a single MC service is described in figure 10.8.3.2.2-1. + +Pre-conditions: + +1. The MC service client has already been provisioned (statically or dynamically) with the group information, or a pointer to the group information, that the MC service client is allowed to be affiliated. +2. The MC service server of the primary MC system may have locally cached the MC service group affiliation status of the MC service user. +3. The MC service server of the partner MC system may have retrieved the group related information from the group management server. +4. The MC service client may have indicated to the group management server of the partner MC system that it wishes to receive updates of group configuration data for MC service group(s) for which it is authorized (as described in subclause 10.1.5.3). +5. The MC service user triggers the affiliation procedure. This is an explicit affiliation caused by the MC service user. + +![Sequence diagram illustrating the affiliation procedure for an MC service group defined in a partner MC system. The diagram shows interactions between the MC service Client, Primary MC service server, Partner MC service server, and Group management server.](1ce027dfd26183da52137cf990213724_img.jpg) + +``` + +sequenceDiagram + participant Client as MC service Client + participant PrimaryServer as Primary MC service server + participant PartnerServer as Partner MC service server + participant GroupServer as Group management server + + Note right of PrimaryServer: 2.Authorization check based on user subscription and N2 limit check + Note right of PartnerServer: 5.Authorization check based on group policy + Note right of PartnerServer: 6.Store group affiliation status + Note right of PrimaryServer: 8.Store group affiliation status + + Client->>PrimaryServer: 1.MC service group affiliation request + PrimaryServer->>PartnerServer: 3.MC service group affiliation request + PartnerServer->>GroupServer: 4a.Subscribe group policy + GroupServer-->>PartnerServer: 4b.Notify group policy + PartnerServer->>PrimaryServer: 7a.MC service group affiliation response + PartnerServer->>GroupServer: 7b.Group affiliation status update (MC service user ID, MC service group ID(s)) + PrimaryServer->>Client: 9.MC service group affiliation response + +``` + +Sequence diagram illustrating the affiliation procedure for an MC service group defined in a partner MC system. The diagram shows interactions between the MC service Client, Primary MC service server, Partner MC service server, and Group management server. + +**Figure 10.8.3.2.2-1: Affiliation for an MC service group defined in partner MC system where topology hiding is not required** + +1. The MC service client requests the MC service server of the primary MC system to affiliate to an MC service group or a set of MC service groups. +2. The MC service server of the primary MC system checks if the MC service client is authorized to affiliate to the requested MC service group(s) based on the user subscription. The MC service server also performs the check for the maximum limit of the total number (N2) of MC service groups that the user can be affiliated to simultaneously. +3. Based on the group information included in the request, the MC service server of the primary MC system, it determines to send group affiliation request to the corresponding MC service server of the partner MC system. The request may be routed through intermediate signalling nodes. +- 4a. The MC service server of the partner MC system checks if the group policy is locally cached. If the group policy is not locally cached on the MC service server then MC service server subscribes to the group policy from the group management server. +- 4b. The MC service server of the partner MC system receives the group policy from the group management server via notification and locally caches the group policy information. + +5. Based on the group policy, the MC service server of the partner MC system checks if the MC service group(s) is not disabled and if the user of the MC service client is authorised to affiliate to the requested MC service group(s). +6. If the user of the MC service client is authorised to affiliate to the requested MC service group(s) then the MC service server of the partner MC system stores the affiliation status of the user for the requested MC service group(s). +7. The MC service server of the partner MC system sends the affiliation status result of requested MC service group(s) to the MC service server of the primary MC system (7a) and updates the group management server with the affiliation status of the user for the requested MC service group(s) (7b). + +NOTE: Steps 7a and 7b can occur in any order or in parallel. + +8. The MC service server of the primary MC system stores the affiliation status of the user for the requested MC service group(s). +9. The MC service server of the primary MC system sends the group affiliation status result for the requested MC service group(s) to the MC service client. + +#### 10.8.3.2a Affiliation to MC service group(s) defined in partner MC system using topology hiding + +##### 10.8.3.2a.1 Functional description + +When an MC service client wants to affiliate to MC service group(s) which is defined in a partner MC system for a single MC service using topology hiding, it shall be subject to authorization from the partner MC system where the MC service group(s) is defined, and may also be subject to authorization from the serving MC system of the MC service client. + +###### 10.8.3.2a.2 Procedure + +Figure 10.8.3.2a.2-1 illustrates the group affiliation procedure to an MC service group defined in the partner MC system of the serving MC system of the MC service user, where topology hiding procedures are required. + +**Editor's note:** It is FFS whether the MC system gateway servers shown in this procedure are roles of an MC service server or separate entities. + +Pre-conditions: + +1. MC service client 1 is service authorized within its serving MC system. +2. The group host MC service server of the MC service group to which the MC service user of MC service client 1 wishes to affiliate is located in the partner MC system of the serving MC system of MC service client 1 +3. Topology hiding is required by both MC systems +4. The serving MC system of MC service client 1 and the group home MC system are configured to allow topology hiding to take place. + +![Sequence diagram showing group affiliation to an MC service group defined in partner MC system using topology hiding. The diagram is split into two lifelines: 'Serving MC system of MC service client 1' and 'Group home system of MC service group'. The sequence of messages is: 1. MC service client 1 sends an affiliation request to the Serving MC service server. 2. The server performs an authorization check. 3. It determines the group host MC service server. 4. It sends an affiliation request to the Serving MC system gateway server. 5. The gateway server determines the primary MC system. 6. It sends an affiliation request to the Group home MC system gateway server. 7. The gateway server determines the group host MC service server. 8. It sends an affiliation request to the Group host MC service server. 9. The server performs an authorization check. 10. It sends an affiliation response. 11. The response is passed back to the Serving MC system gateway server. 12. The gateway server passes the response to the Serving MC service server. 13. The server sends the final affiliation response to the MC service client 1.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 + participant Serving MC service server + participant Serving MC system gateway server + participant Group home MC system gateway server + participant Group host MC service server + + Note left of MC service client 1: Serving MC system of MC service client 1 + Note right of Group host MC service server: Group home system of MC service group + + MC service client 1->>Serving MC service server: 1. MC service group affiliation request + Serving MC service server-->>Serving MC system gateway server: 2. Authorization check based on user subscription and N2 check + Serving MC service server-->>Serving MC system gateway server: 3. Determine group host MC service server + Serving MC service server->>Serving MC system gateway server: 4. MC service group affiliation request + Serving MC system gateway server-->>Serving MC service server: 5. Determine primary MC system of MC service group + Serving MC system gateway server->>Group home MC system gateway server: 6. MC service group affiliation request + Group home MC system gateway server-->>Group host MC service server: 7. Determine group host MC service server + Group home MC system gateway server->>Group host MC service server: 8. MC service group affiliation request + Group host MC service server-->>Group home MC system gateway server: 9. Authorization check based on group policy + Group host MC service server-->>Group home MC system gateway server: 10. MC service group affiliation response + Group home MC system gateway server-->>Serving MC system gateway server: 11. MC service group affiliation response + Serving MC system gateway server-->>Serving MC service server: 12. MC service group affiliation response + Serving MC service server-->>MC service client 1: 13. MC service group affiliation response + +``` + +Sequence diagram showing group affiliation to an MC service group defined in partner MC system using topology hiding. The diagram is split into two lifelines: 'Serving MC system of MC service client 1' and 'Group home system of MC service group'. The sequence of messages is: 1. MC service client 1 sends an affiliation request to the Serving MC service server. 2. The server performs an authorization check. 3. It determines the group host MC service server. 4. It sends an affiliation request to the Serving MC system gateway server. 5. The gateway server determines the primary MC system. 6. It sends an affiliation request to the Group home MC system gateway server. 7. The gateway server determines the group host MC service server. 8. It sends an affiliation request to the Group host MC service server. 9. The server performs an authorization check. 10. It sends an affiliation response. 11. The response is passed back to the Serving MC system gateway server. 12. The gateway server passes the response to the Serving MC service server. 13. The server sends the final affiliation response to the MC service client 1. + +**Figure 10.8.3.2a.2-1: Group affiliation to an MC service group defined in partner MC system using topology hiding** + +1. MC service client 1 initiates an MC service group affiliation request to the serving MC service server of MC service client 1 on behalf of its MC service user. + 2. The MC service server of the serving MC system checks that the MC service client 1 is authorized to affiliate to the requested MC service group based on the user configuration, and that the maximum number of MC service groups that the user can be affiliated to (N2) has not been exceeded. + 3. The MC service server determines the group host MC service server of the MC service group. The MC service group is identified to have a different group home MC system, and if topology hiding is required by the serving MC system of MC service client 1, the serving MC system gateway server is determined to act as proxy group host MC service server for the MC service group. + 4. The MC service server of the serving MC system forwards the MC service group affiliation request to the gateway server of the serving MC system. +- NOTE 1: If the serving MC system of MC service client 1 does not require topology hiding, the serving MC service server of MC service client 1 is able to send the MC service group affiliation request directly to the gateway server of the group home MC system in step 4, omitting steps 5 and 6. +5. The gateway server determines which MC system is the group home system for the MC service group. + 6. The gateway server in the serving system of MC service client 1 forwards the MC service group affiliation request to the gateway server of the group home MC system of the MC service group. + +- NOTE 2: If the group home MC system does not require topology hiding, the request from the serving MC system of MC service client 1 is sent directly to the group host MC service server in either step 4 or step 6, omitting steps 7 and 8. +7. The gateway server of the group home MC system of the MC service group determines which MC service server is the group host MC service server for that MC service group. + 8. The gateway server of the group home system of the MC service group forwards the MC service group affiliation request to the group host MC service server of the MC service group. + 9. The group host MC service server in the partner MC system checks whether the user of MC service client 1 is authorized to affiliate to the MC service group based on the MC service group configuration. The group host MC service server may optionally subscribe to the GMS containing the group configuration information, and receive notification of group policy. + 10. The group host MC service server sends an MC service group affiliation response to the gateway server in the group home MC system of the MC service group. +- NOTE 3: If the group home MC system does not require topology hiding, the MC service group affiliation response is sent directly to the gateway server of the serving MC system of MC service client 1. +11. The gateway server in the group home MC system forwards the MC service group affiliation response to the gateway server in the serving MC system of MC service client 1. +- NOTE 4: If the serving MC system of MC service client 1 does not require topology hiding, the MC service group affiliation response is sent directly to the serving MC service server of MC service client 1. +12. The gateway server in the serving MC system of MC service client 1 forwards the MC service group affiliation response to the serving MC service server of MC service client 1. + 13. The serving MC service server of MC service client 1 forwards the MC service group affiliation response to MC service client 1. + +### 10.8.4 De-affiliation from MC service group(s) + +#### 10.8.4.1 General + +When an MC service user does not want to communicate with an MC service group anymore for a single MC service, then the MC service user can revoke its affiliation to the MC service group. + +#### 10.8.4.2 MC service group de-affiliation procedure + +The procedure for revoking the affiliation with an MC service group for a single MC service is described in figure 10.8.4.2-1. + +Pre-conditions: + +1. MC service server has already subscribed to the MC service group information from group management server and has stored the data of MC service group(s) to which the MC service user is affiliated to. +2. The MC service client triggers the de-affiliation procedure. This is an explicit de-affiliation requested either by the MC service user or determined by a trigger event such as the MC service UE moving outside a permitted geographic operational area of an MC service group. + +NOTE: The geographical operational area beyond which de-affiliation occurs may be larger than the geographical operational area within which affiliation is permitted, to avoid repeated affiliation and de-affiliation by a user on the edge of an operational area. + +![Sequence diagram of MC service group de-affiliation procedure](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +``` +sequenceDiagram + participant MC service client + participant MC service server + participant Group management server + Note right of MC service server: 2. Authorization check based on group policy and user subscription + Note right of MC service server: 3. Remove the MC service group affiliation status + MC service client->>MC service server: 1. MC service group de-affiliation request + MC service server-->>MC service client: 4a. MC service group de-affiliation response + MC service server->>Group management server: 4b. Group de-affiliation status update +``` + +The diagram illustrates the MC service group de-affiliation procedure. It involves three main participants: MC service client, MC service server, and Group management server. The sequence of messages is as follows: 1. MC service client sends an MC service group de-affiliation request to the MC service server. 2. The MC service server performs an authorization check based on group policy and user subscription. 3. The MC service server removes the MC service group affiliation status. 4a. The MC service server provides the MC service group de-affiliation response to the MC service client. 4b. The MC service server updates the group management server with the de-affiliation status update. + +Sequence diagram of MC service group de-affiliation procedure + +**Figure 10.8.4.2-1: MC service group de-affiliation procedure** + +1. MC service client requests the MC service server to de-affiliate from an MC service group or a set of MC service groups. +2. Based on the user subscription and stored group policy, the MC service server checks if the user of the MC service client is authorized to de-affiliate from the requested MC service group(s) and if the user of the MC service client has affiliated to the requested MC service group(s). +3. If the user of the MC service client has affiliated to the requested MC service group(s), is authorized to de-affiliate from the requested MC service group(s) then the MC service server removes the affiliation status of the user for the requested MC service group(s). +4. MC service server provides to the MC service client the group de-affiliation response (4a) and updates the group management server with the de-affiliation status of the user for the requested MC service group(s) (4b). + +NOTE: Steps 4a and 4b can occur in any order or in parallel. + +#### 10.8.4.3 De-affiliation from MC service group(s) defined in partner MC service system + +The procedure for de-affiliation from affiliated MC service group(s) which is defined in partner MC service system for a single MC service is described in figure 10.8.4.3-1. + +Pre-conditions: + +1. The primary/partner MC service servers have already subscribed to the group information from group management server and stored the data of MC service group(s) to which the MC service user intends to de-affiliate. + +![Sequence diagram for de-affiliation from an MC service group defined in partner MC service system. The diagram shows four lifelines: MC service client, Primary MC service server, Partner MC service server, and Group management server. The sequence of messages is: 1. MC service group de-affiliation request from client to primary server; 2. Authorization check based on user subscription (internal to primary server); 3. MC service group de-affiliation request from primary server to partner server; 4. Authorization check based on group(s) policy (internal to partner server); 5. Remove MC service group affiliation (internal to partner server); 6a. MC service group de-affiliation response from partner server to primary server; 6b. Group de-affiliation status update (user ID, group ID(s)) from partner server to group management server; 7. Remove MC service group affiliation (internal to primary server); 8. MC service group de-affiliation response from primary server to client.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +``` + +sequenceDiagram + participant MC service client + participant Primary MC service server + participant Partner MC service server + participant Group management server + + Note right of Primary MC service server: 2. Authorization check based on user subscription + Note right of Partner MC service server: 4. Authorization check based on group(s) policy + Note right of Partner MC service server: 5. Remove MC service group affiliation + Note right of Primary MC service server: 7. Remove MC service group affiliation + + MC service client->>Primary MC service server: 1. MC service group de-affiliation request + Primary MC service server->>Partner MC service server: 3. MC service group de-affiliation request + Partner MC service server->>Primary MC service server: 6a. MC service group de-affiliation response + Partner MC service server->>Group management server: 6b. Group de-affiliation status update (user ID, group ID(s)) + Primary MC service server->>MC service client: 8. MC service group de-affiliation response + +``` + +Sequence diagram for de-affiliation from an MC service group defined in partner MC service system. The diagram shows four lifelines: MC service client, Primary MC service server, Partner MC service server, and Group management server. The sequence of messages is: 1. MC service group de-affiliation request from client to primary server; 2. Authorization check based on user subscription (internal to primary server); 3. MC service group de-affiliation request from primary server to partner server; 4. Authorization check based on group(s) policy (internal to partner server); 5. Remove MC service group affiliation (internal to partner server); 6a. MC service group de-affiliation response from partner server to primary server; 6b. Group de-affiliation status update (user ID, group ID(s)) from partner server to group management server; 7. Remove MC service group affiliation (internal to primary server); 8. MC service group de-affiliation response from primary server to client. + +**Figure 10.8.4.3-1: De-affiliation from an MC service group defined in partner MC service system** + +1. The MC service client requests the primary MC service server to de-affiliate from an MC service group or a set of MC service groups. + 2. The primary MC service server checks if the MC service client is authorized to de-affiliate from the requested MC service group(s) based on the user subscription. The primary MC service server performs the check if the user has affiliated to the MC service groups. + 3. Based on the MC service group information included in the request, the primary MC service server determines to send MC service group de-affiliation request to the corresponding partner MC service server. The request may be routed through some intermediate signalling nodes. + 4. Based on the stored group policy, the partner MC service server checks if the MC service group is not disabled and if the user of the MC service client has affiliated to the requested MC service group(s) and is authorized to de-affiliate from the requested MC service group(s). + 5. If the user of the MC service client has affiliated to the requested MC service group(s) and is authorized to de-affiliate to the requested MC service group(s), then the partner MC service server removes the affiliation status of the user for the requested MC service group(s). + 6. The partner MC service server sends the MC service group de-affiliation response to primary MC service server (6a) and updates the group management server with the de-affiliation status of the user for the requested MC service group(s) (6b). +- NOTE: Steps 6a and 6b can occur in any order or in parallel. +7. The primary MC service server will remove any information stored about the user's affiliation with requested MC service group(s) of partner MC service system. + 8. The primary MC service server sends the MC service group de-affiliation response to the MC service client. + +#### 10.8.4.4 MC server initiated group de-affiliation procedure + +The procedure for the MC service server to trigger a de-affiliation with an MC service group is described in figure 10.8.4.4-1. + +Pre-conditions: + +1. The MC service user has previously affiliated to the group, and the MC service server has stored the status of MC service group affiliation. +2. Following a relevant trigger condition, e.g. the user moving outside the permitted geographical operational area of the MC service group, or the permitted geographical operational area is modified, causing user outside of the permitted geographical operational area, the MC service server de-affiliates the user from the MC service group. + +![Sequence diagram illustrating the MC service server initiated group de-affiliation procedure. The diagram shows three lifelines: MC service client, MC service server, and Group management server. The sequence of messages is: 1. MC service server determines that user is to be de-affiliated to group (internal message); 2. Store group affiliation status (internal message); 3. Group de-affiliation status update (message from MC service server to Group management server); 4. MC service group de-affiliation notification (message from MC service server to MC service client).](fe7304192caf64cda93b580c5e7e5c06_img.jpg) + +``` +sequenceDiagram + participant MC service client + participant MC service server + participant Group management server + Note right of MC service server: 1. MC service server determines that user is to be de-affiliated to group + Note right of MC service server: 2. Store group affiliation status + MC service server->>Group management server: 3. Group de-affiliation status update + MC service server->>MC service client: 4. MC service group de-affiliation notification +``` + +Sequence diagram illustrating the MC service server initiated group de-affiliation procedure. The diagram shows three lifelines: MC service client, MC service server, and Group management server. The sequence of messages is: 1. MC service server determines that user is to be de-affiliated to group (internal message); 2. Store group affiliation status (internal message); 3. Group de-affiliation status update (message from MC service server to Group management server); 4. MC service group de-affiliation notification (message from MC service server to MC service client). + +**Figure 10.8.4.4-1: MC service server initiated group de-affiliation procedure** + +1. The MC service server determines the MC service client could be de-affiliated to the group again due to the trigger event, e.g. the permitted geographical operational area is modified, causing the user outside of the permitted geographical operational area of the MC service group, the MC service server needs to de-affiliate the MC Service user from the group. +2. The MC service server changes the affiliation status of the user. +3. The MC service server updates the group management server with the de-affiliation status of the user for the requested MC service group(s). +4. The MC service server provides a de-affiliation notification with the group information to the MC service client. + +#### 10.8.4.5 MC server initiated group de-affiliation from group defined in partner MC service system + +The procedure for the MC service server to trigger a de-affiliation from an MC service group which is defined in partner MC service system is described in figure 10.8.4.5-1. + +Pre-conditions: + +1. The MC service user has previously affiliated to the group, and the MC service server has stored the status of MC service group affiliation. +2. Following a relevant trigger condition (e.g. the user moving outside the permitted geographical operational area of the MC service group, or the permitted geographical operational area is modified), the de-affiliation for the MC service user is initiated by the MC service server from the MC service group. +3. The primary/partner MC service servers have already subscribed to the group information from group management server and stored the data of MC service group(s) to which the MC service user intends to de-affiliate. + +![Sequence diagram for MC service server initiated group de-affiliation from group in partner system procedure. Lifelines: MC service client, Primary MC service server, Partner MC service server, Group management server. The process involves determining de-affiliation, sending a request to the partner server, authorization check, removing affiliation, storing status, and notifying the client.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +``` +sequenceDiagram + participant MC service client + participant Primary MC service server + participant Partner MC service server + participant Group management server + + Note right of Primary MC service server: 1. MC service server determines that user is to be de-affiliated from group + Primary MC service server->>Partner MC service server: 2. MC service group de-affiliation request + Note right of Partner MC service server: 3. Authorization check based on group(s) policy + Note right of Partner MC service server: 4. Remove MC service group affiliation + Partner MC service server-->>Primary MC service server: 5a. MC service group de-affiliation response + Partner MC service server-->>Group management server: 5b. Group de-affiliation status update + Note right of Primary MC service server: 6. Store group affiliation status + Primary MC service server-->>MC service client: 7. MC service group de-affiliation notification +``` + +Sequence diagram for MC service server initiated group de-affiliation from group in partner system procedure. Lifelines: MC service client, Primary MC service server, Partner MC service server, Group management server. The process involves determining de-affiliation, sending a request to the partner server, authorization check, removing affiliation, storing status, and notifying the client. + +**Figure 10.8.4.5-1: MC service server initiated group de-affiliation from group in partner system procedure** + +1. The MC service server determines the MC service client could be de-affiliated to the group due to the trigger event, e.g. the permitted geographical operational area is modified, causing the user outside of the permitted geographical operational area of the MC service group, the MC service server needs to de-affiliate the MC Service user from the group. + 2. Based on the stored MC service group information, the primary MC service server determines to send MC service group de-affiliation request to the corresponding partner MC service server. The request may be routed through some intermediate signalling nodes. + 3. Based on the stored group policy, the partner MC service server checks if the MC service group is not disabled and if the user of the MC service client has affiliated to the requested MC service group(s) and is authorized to de-affiliate from the requested MC service group(s). + 4. If the user of the MC service client has affiliated to the requested MC service group(s) and is authorized to de-affiliate to the requested MC service group(s), then the partner MC service server removes the affiliation status of the user for the requested MC service group(s). + 5. The partner MC service server sends the MC service group de-affiliation response to primary MC service server (5a) and updates the group management server with the de-affiliation status of the user for the requested MC service group(s) (5b). +- NOTE: Steps 5a and 5b can occur in any order or in parallel. +6. The primary MC service server changes the affiliation status of the user. + 7. The MC service server provides a de-affiliation notification with the group information to the MC service client. + +### 10.8.5 Remote change of affiliation + +#### 10.8.5.1 Remote change of affiliation for groups defined in primary MC system + +##### 10.8.5.1.1 Authorized user remotely changes another MC service user's affiliated MC service group(s) – mandatory mode + +The procedure for an authorized user to remotely change another MC service user's affiliated MC service group(s) for a single MC service without requiring the target user's approval is described in figure 10.8.5.1.1-1. + +Pre-conditions: + +- The MC service client 1 (authorized user 1) has already been provisioned (statically or dynamically) with the target MC service user's information and its group information, that target MC service user 2 is allowed to be affiliated or de-affiliated; +- The primary MC service server may have retrieved the user/group policy e.g. information regarding user(s) authorization to affiliate or to de-affiliate to MC service group(s), priority, and other related configuration data. + +![Sequence diagram showing the interaction between MC service client 1 (Authorized user 1), Primary MC service server, Group management server, and MC service client 2 (Target user 2) for a remote change of affiliation in mandatory mode. The steps are: 1. MC service group affiliation change request from client 1 to server; 2. Authorization check based on user subscription and limit check on server; 3a. Subscribe group policy from server to group management server; 3b. Notify group policy from group management server to server; 4. Authorization check based on the group policy on server; 5. Store group affiliation status on server; 6. Group affiliation status update (target user ID, group ID) from server to group management server; 7a. MC service group affiliation change request from server to client 2; 7b. MC service group affiliation change response from client 2 to server; 8. MC service group affiliation change response from server to client 1.](7e74ac663f3e644b589ed28f5fd29398_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MC service client 1 (Authorized user 1) + participant Server as Primary MC service server + participant GroupServer as Group management server + participant Client2 as MC service client 2 (Target user 2) + + Client1->>Server: 1. MC service group affiliation change request + Note right of Server: 2. Authorization check based on user subscription and limit check + Server-->>GroupServer: 3a. Subscribe group policy + GroupServer-->>Server: 3b. Notify group policy + Note right of Server: 4. Authorization check based on the group policy + Note right of Server: 5. Store group affiliation status + Server-->>GroupServer: 6. Group affiliation status update (target user ID, group ID) + Server-->>Client2: 7a. MC service group affiliation change request + Client2-->>Server: 7b. MC service group affiliation change response + Server-->>Client1: 8. MC service group affiliation change response + +``` + +Sequence diagram showing the interaction between MC service client 1 (Authorized user 1), Primary MC service server, Group management server, and MC service client 2 (Target user 2) for a remote change of affiliation in mandatory mode. The steps are: 1. MC service group affiliation change request from client 1 to server; 2. Authorization check based on user subscription and limit check on server; 3a. Subscribe group policy from server to group management server; 3b. Notify group policy from group management server to server; 4. Authorization check based on the group policy on server; 5. Store group affiliation status on server; 6. Group affiliation status update (target user ID, group ID) from server to group management server; 7a. MC service group affiliation change request from server to client 2; 7b. MC service group affiliation change response from client 2 to server; 8. MC service group affiliation change response from server to client 1. + +**Figure 10.8.5.1.1-1: Remotely change MC service group affiliation – mandatory mode** + +1. When an authorized user requires one or more MC service users to change the affiliation to an MC service group or set of MC service groups, the MC service client 1 of the authorized user 1 sends MC service group affiliation change request with the indication of mandatory mode to the primary MC service server. The information used to indicate the change of the affiliation relationship between the target MC service user 2 and the MC service group(s) shall be included. +2. The primary MC service server shall check if the MC service user 1 is authorized to initiate the change of the affiliation relationship between the target user 2 and the MC service group(s). The primary MC service server shall check if the target MC service user(s) are authorized for the requested affiliation relationship based on the user subscription. The primary MC service server also performs the check for the maximum limit on the total number (N2) of MC service groups that the user can be affiliated to simultaneously. + +- 3a. The primary MC service server checks if the group policy is locally cached. If the group policy is not locally cached on the MC service server, then, the MC service server subscribes to the group policy from the group management server. +- 3b. The primary MC service server receives the group policy from the group management server via notification and locally caches the group policy information. +4. Based on the group policy, the primary MC service server checks if the target MC service user 2 is authorized to affiliate or de-affiliate to the MC service group(s). +5. If the target MC service user 2 is authorized to affiliate or de-affiliate to the MC service group(s) then the primary MC service server stores the new requested affiliation status of the target MC service user 2 for the MC service group(s). +6. If the requested affiliation status is a change from the current affiliation status, then the primary MC service server updates the group management server with the affiliation status of the MC service user 2 for the MC service group(s). +- 7a. If the requested affiliation status is a change the primary MC service server sends the MC service group affiliation change request with the indication of mandatory mode to MC service client 2 of the target MC service user 2. The target MC service user 2 receives the latest information about the affiliated MC service groups. The MC service client 2 may subscribe to the affiliated MC service groups information with the group management server. +- 7b. The MC service user 2 provides a response to the primary MC service server by sending an MC service group affiliation change response. +8. The primary MC service server sends the MC service group affiliation change response to MC service client 1. If the requested affiliation status was not changed (see 7a), then the MC service server creates an appropriate (accept) MC service group affiliation change response to send to MC service client 1. + +NOTE: Steps 6, 7a, 7b and 8 can occur in any order or in parallel, with the restriction that step 7b can only occur after step 7a occurred. + +##### 10.8.5.1.2 Authorized user remotely changes another MC service user's affiliated MC service group(s) – negotiated mode + +The procedure for the authorized user to remotely change another MC service user's affiliated MC service group(s) for a single MC service with the target MC service user's approval is described in figure 10.8.5.1.2-1. + +Pre-conditions: + +- The MC service client 1 (authorized user 1) has already been provisioned (statically or dynamically) with target MC service user's information and its group information, that target MC service user 2 is allowed to be affiliated or de-affiliated; +- The primary MC service server may have retrieved the user/group policy e.g. information regarding user(s) authorization to affiliate or to de-affiliate to MC service group(s), priority, and other related configuration data. + +![Sequence diagram for Remotely change MC service group affiliation – negotiated mode. The diagram shows four lifelines: MC service client 1 (Authorized user 1), Primary MC service server, Group management server, and MC service client 2 (Target user 2). The sequence of messages is: 1. MC service group affiliation change request from client 1 to server; 2. Authorization check based on user subscription and limit check (internal to server); 3. MC service group affiliation change request from server to client 2; 4. Notify group affiliation change to MC service user and get agreement from the user (internal to client 2, shown in a dashed box); 5. MC service group affiliation change response from client 2 to server; 6. MC service group affiliation change response from server to client 1.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MC service client 1 (Authorized user 1) + participant Server as Primary MC service server + participant GroupServer as Group management server + participant Client2 as MC service client 2 (Target user 2) + + Note right of Server: 2. Authorization check based on user subscription and limit check + Note right of Client2: 4. Notify group affiliation change to MC service user and get agreement from the user + + Client1->>Server: 1. MC service group affiliation change request + Server-->>Server: 2. Authorization check based on user subscription and limit check + Server-->>Client2: 3. MC service group affiliation change request + Note right of Client2: 4. Notify group affiliation change to MC service user and get agreement from the user + Client2-->>Server: 5. MC service group affiliation change response + Server-->>Client1: 6. MC service group affiliation change response + +``` + +Sequence diagram for Remotely change MC service group affiliation – negotiated mode. The diagram shows four lifelines: MC service client 1 (Authorized user 1), Primary MC service server, Group management server, and MC service client 2 (Target user 2). The sequence of messages is: 1. MC service group affiliation change request from client 1 to server; 2. Authorization check based on user subscription and limit check (internal to server); 3. MC service group affiliation change request from server to client 2; 4. Notify group affiliation change to MC service user and get agreement from the user (internal to client 2, shown in a dashed box); 5. MC service group affiliation change response from client 2 to server; 6. MC service group affiliation change response from server to client 1. + +**Figure 10.8.5.1.2-1: Remotely change MC service group affiliation – negotiated mode** + +1. When an authorized user requires one or more MC service users to change the affiliation to an MC service group or set of MC service groups, the MC service client 1 of the authorized user 1 sends MC service group affiliation change request to the primary MC service server. The information (i.e. target MC service user(s) ID, MC service group(s) ID, requested affiliation status) used to indicate the change of the affiliation relationship between the target MC service user 2 and the MC service group(s) shall be included. +2. The primary MC service server checks if the MC service user 1 is authorized to initiate the change of the affiliation relationship between the target user 2 and the MC service group(s). The primary MC service server checks if the target MC service user(s) are authorized for the requested affiliation relationship based on the user subscription and the group policy (i.e. if not available, the primary MC service server obtains the group policy from the group management server). The primary MC service server also performs the check for the maximum limit on the total number (N2) of MC service groups that the user can be affiliated to simultaneously. +3. If the target MC service user 2 is authorized to accept the changes to its affiliated MC service group(s), then the primary MC service server sends the MC service group affiliation change request to the MC service client 2 of the target MC service user 2. +4. If the requested affiliation status is different from the current affiliation status, then the MC service client 2 notifies the MC service group affiliation change request to the target MC service user 2 to receive the approval from the user on the proposed changes to the affiliated MC service group(s). + +NOTE 1: The procedure is aborted if the target MC service user 2 does not respond to the notification within an implementation dependent time. + +5. If the target MC service user 2 provides a response (accept or reject) to the notification, then the MC service client 2 sends an MC service group affiliation change response to the primary MC service server. A response indicating target user 2's acceptance to the requested affiliation change by authorized user 1, triggers the affiliation or de-affiliation procedures at the primary MC service server (see subclause 10.8.3.1 or subclause 10.8.4.2) as per the MC service user 1's requested changes to the target user 2's affiliated group(s). + +NOTE 2: In the case where the affiliation changes for target user 2 includes MC service groups defined in partner MC systems, the primary MC service server performs the affiliation or de-affiliation procedures by interacting with the partner MC systems (see subclause 10.8.3.2 or subclause 10.8.4.3). + +6. The primary MC service server sends the MC service group affiliation change response to the MC service client 1. If the requested affiliation status was not changed (see 4), then the MC service server creates an appropriate (accept) MC service group affiliation change response to send to MC service client 1. + +NOTE 3: If multiple MC service groups are included in step 1, and these MC service groups belong to different partner MC systems, the primary MC service server can wait until all the partner MC systems provides the MC service group affiliation change response messages. + +#### 10.8.5.2 Remote change of affiliation for groups defined in partner MC system + +##### 10.8.5.2.1 Authorized user remotely changes another MC service user's affiliated MC service group(s) defined in partner MC system – mandatory mode + +The procedure for the authorized user to remotely change another MC service user's affiliated MC service group(s) defined in partner MC systems for a single MC service without requiring the target user's approval is described in figure 10.8.5.2.1-1. + +Pre-conditions: + +- The MC service client 1 (authorized user) has already been provisioned (statically or dynamically) with the target MC service user 2's information and group information, that the target MC service user 2 is allowed to be affiliated or de-affiliated; +- The MC service client 1 (authorized user 1), MC service client 2 (target MC service user 2), and the primary MC service server belong to the same MC system; +- The partner MC service server may have retrieved the group related information from the group management server; and +- The primary MC service server may have retrieved the user policy e.g. user related information regarding user(s) authorization to affiliate or to de-affiliate to MC service group(s), priority, and other related configuration data. + +![Sequence diagram illustrating the remote change of MC service group affiliation defined in partner MC system – mandatory mode. The diagram shows interactions between MC service client 1 (Authorized user 1), Primary MC service server, Partner MC service server 2 (Group host server), Partner Group management server, and MC service client 2 (Target MCPTT user 2).](e90b25c8d90cadc3f76c376701cf27ed_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 (Authorized user 1) + participant Primary MC service server + participant Partner MC service server 2 (Group host server) + participant Partner Group management server + participant MC service client 2 (Target MCPTT user 2) + + Note right of Primary MC service server: 2. Authorization check based on subscription and limit check + + Note right of Partner MC service server 2: 5. Authorization check based on group policy + Note right of Partner MC service server 2: 6. Update group affiliation status + + Note right of Primary MC service server: 9. Update group affiliation status + + MC service client 1 (Authorized user 1)->>Primary MC service server: 1. MC service group affiliation change request + Primary MC service server->>Partner MC service server 2 (Group host server): 3. MC service group affiliation change request + Partner MC service server 2 (Group host server)-->>Partner Group management server: 4a. Subscribe group policy + Partner Group management server-->>Partner MC service server 2 (Group host server): 4b. Notify group policy + Partner MC service server 2 (Group host server)-->>Primary MC service server: 7. MC service group affiliation change response + Primary MC service server->>MC service client 1 (Authorized user 1): 11. MC service group affiliation change response + Partner MC service server 2 (Group host server)->>MC service client 2 (Target MCPTT user 2): 8. Group affiliation status update (target user ID, group ID(s)) + Partner MC service server 2 (Group host server)-->>MC service client 2 (Target MCPTT user 2): 10a. MC service group affiliation change request + MC service client 2 (Target MCPTT user 2)-->>Partner MC service server 2 (Group host server): 10b. MC service group affiliation change response + +``` + +Sequence diagram illustrating the remote change of MC service group affiliation defined in partner MC system – mandatory mode. The diagram shows interactions between MC service client 1 (Authorized user 1), Primary MC service server, Partner MC service server 2 (Group host server), Partner Group management server, and MC service client 2 (Target MCPTT user 2). + +**Figure 10.8.5.2.1-1: Remote change MC service group affiliation defined in partner MC system – mandatory mode** + +1. When an authorized user requires one or more MC service users to change the affiliation to an MC service group or set of MC service groups, the MC service client 1 of the authorized user 1 sends MC service group affiliation change request with the indication of mandatory mode to the primary MC service server. The information (i.e. + +target MC service user(s) ID, MC service group(s) ID, requested affiliation status) used to indicate the change of the affiliation relationship between the target MC service user 2 and the MC service group(s) shall be included. + +2. The primary MC service server shall check if the MC service user 1 is authorized to initiate the change of the affiliation relationship between the target user 2 and the MC service group(s). The primary MC service server shall check if the target MC service user(s) are authorized for the requested affiliation relationship based on the user subscription. The primary MC service server also performs the check for the maximum limit on the total number (N2) of MC service groups that the user can be affiliated to simultaneously. +3. Based on the MC service group information included in the request, the primary MC service server determines to send MC service group affiliation change request to the corresponding partner MC service server (group host server). +- 4a. The partner MC service server checks if the group policy is locally cached. If the group policy is not locally cached on the partner MC service server then the partner MC service server subscribes to the group policy from the group management server. +- 4b. The partner MC service server receives the group policy from the group management server via notification and locally caches the group policy information. +5. Based on the group policy, the partner MC service server checks if the target MC service user 2 is authorized to affiliate to the MC service group(s). It is possible that the target MC service user 2 affiliates to one or more MC service groups and also de-affiliates from one or more MC service groups. +6. If the target MC service user 2 is authorized to affiliate or de-affiliate to the MC service group(s) and if the requested affiliation status is different to the current affiliation status, then the partner MC service server stores the new affiliation status of the target MC service user 2 for the MC service group(s). +7. The partner MC service server updates the group management server with the affiliation status of the target MC service user 2 for the MC service group(s). +8. The partner MC service server sends the MC service group affiliation change response to the primary MC service server. + +NOTE: Steps 7 and 8 can occur in any order or in parallel. + +9. If the requested affiliation status is different to the current affiliation status, then the primary MC service server stores the new affiliation status of the target MC service user 2 for the MC service group(s). +- 10a. If the requested affiliation status is different to the current affiliation status, then the primary MC service server sends the MC service group affiliation change request with the indication of mandatory mode to MC service client 2 of the target MC service user 2. The target MC service user 2 receives the latest information about the affiliated MC service groups. Further the MC service client 2 may subscribe for the affiliated MC service groups information with the group management server. +- 10b. The target MC service client 2 provides an MC service group affiliation change response to the MC service server. +11. The primary MC service server sends the MC service group affiliation change response to MC service client 1 (authorized user). If the requested affiliation status was not changed (see 10a), then the MC service server creates an appropriate (accept) MC service group affiliation change response to send to MC service client 1. + +## 10.9 Location management (on-network) + +### 10.9.1 General + +Location information of MC service user shall be provided by the location management client to the location management server. The location information reporting triggers are based on the location reporting configuration. Different type of location information can be provided. + +### 10.9.2 Information flows for location information + +#### 10.9.2.1 Location reporting configuration + +Table 10.9.2.1-1 describes the information flow from the location management server to the location management client for the location reporting configuration. + +**Table 10.9.2.1-1: Location reporting configuration** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------|----------|---------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | Identity of the MC service user to which the location reporting configuration is targeted. | +| Requested non-emergency location information | O (NOTE) | Identifies what location information is requested, except for emergency or imminent peril calls or emergency alerts | +| Requested emergency location information | O (NOTE) | Identifies what location information is requested, for emergency or imminent peril calls or emergency alerts | +| Triggering criteria in non-emergency cases | O (NOTE) | Identifies when the location management client will send the location report in non-emergency cases | +| Minimum time between consecutive reports | O (NOTE) | Defaults to 0 if absent and 0 for emergency calls, imminent peril calls and emergency alerts | +| NOTE: If none of the information element is present, this represents a cancellation for location reporting. | | | + +#### 10.9.2.2 Location information report + +Table 10.9.2.2-1 describes the information flow from the location management client to the location management server for the location information reporting. + +**Table 10.9.2.2-1: Location information report** + +| Information element | Status | Description | +|-----------------------|--------|----------------------------------------------------------------------------------------------------------------| +| Set of MC service IDs | M | Set of identities of the reporting MC service user on the MC service UE (e.g. MCPTT ID, MCVideo ID, MCData ID) | +| Triggering event | M | Identity of the event that triggered the sending of the report | +| Location Information | M | Location information | + +#### 10.9.2.3 Location information request + +Table 10.9.2.3-1 describes the information flow from the MC service server to the location management server and from the location management server to the location management client for requesting an immediate location information report. + +**Table 10.9.2.3-1: Location information request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------| +| MC service ID list | M | List of MC service users whose location information is requested | + +#### 10.9.2.4 Location reporting trigger + +Table 10.9.2.4-1 describes the information flow from the location management client to the location management server for triggering a location reporting procedure. + +**Table 10.9.2.4-1: Location reporting trigger** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------| +| MC service ID | M (NOTE 1) | Identity of the requesting authorized MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID) | +| MC service ID | M (NOTE 1) | Identity of the requested MC service user (e.g. MCPTT ID, MCVideo ID, MCData ID) | +| Immediate Report Indicator | O (NOTE 2) | Indicates whether an immediate location report is required | +| Requested non-emergency location information | O (NOTE 2) | Identifies what location information is requested, except for emergency or imminent peril calls or emergency alerts | +| Requested emergency location information | O (NOTE 2) | Identifies what location information is requested, for emergency or imminent peril calls or emergency alerts | +| Triggering criteria in non-emergency cases | O (NOTE 2) | Identifies when the client will send the location report in non-emergency cases | +| Minimum time between consecutive reports | O (NOTE 2) | Defaults to 0 if absent and 0 for emergency calls, imminent peril calls and emergency alerts | +| NOTE 1: The identity of the requesting MC service user and the requested MC service user should belong to the same MC service. E.g. if requesting MC service user is using a MCPTT ID, then the requested MC service user identity should be an MCPTT ID. | | | +| NOTE 2: At least one of these rows shall be present. | | | + +#### 10.9.2.5 Location information subscription request + +Table 10.9.2.5-1 describes the information flow from the MC service server to the location management server for location information subscription request. + +**Table 10.9.2.5-1: Location information subscription request** + +| Information element | Status | Description | +|----------------------------------|--------|-------------------------------------------------------------------| +| MC service ID | M | Identity of the requesting MC service user | +| MC service ID list | M | List of MC service users whose location information is requested. | +| Time between consecutive reports | M | It indicates the interval time between consecutive reports | + +#### 10.9.2.6 Location information subscription response + +Table 10.9.2.6-1 describes the information flow from the location management server to the MC service server for location information subscription response. + +**Table 10.9.2.6-1: Location information subscription response** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------| +| MC service ID | M | Identity of the requesting MC service user | +| Subscription status | M | It indicates the subscription result | + +#### 10.9.2.7 Location information notification + +Table 10.9.2.7-1 describes the information flow from the location management server to the MC service server. + +**Table 10.9.2.7-1: Location information notification** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------------------| +| MC service ID list | M | List of the MC service users whose location information needs to be notified | +| MC service ID | M | Identity of the MC service user subscribed to location of another MC service user (NOTE) | +| Triggering event | M | Identity of the event that triggered the sending of the notification | +| Location Information | M | Location information | +| NOTE: This is only used for location management server sends location information notification to the MC service user who has subscribed the location. | | | + +### 10.9.3 Procedure + +#### 10.9.3.1 Event-triggered location reporting procedure + +The location management server provides location reporting configuration to the location management clients, indicating what information the location management server expects and what events will trigger the sending of this information to the location management server. The decision to report location information can be triggered at the location management client by different conditions, e.g., the reception of the location reporting configuration, initial registration, distance travelled, elapsed time, cell change, **MBMS SAI** change, **MBMS** session change, leaving a specific **MBMS** bearer service area, tracking area change, PLMN change, call initiation, or other types of events such as emergency alert, emergency call or imminent peril calls. The location report can include information described as **ECGI**, **MBMS SAI**s, geographic coordinates and other location information. + +![Sequence diagram of the event-triggered location reporting procedure. It shows four steps: 1. Location management Server sends 'Location Reporting Configuration' to Location management client. 2. Location management client sends 'Configured location reporting event triggers' to Location management Server. 3. Location management client sends 'Location Information Report' to Location management Server. 4. Location management Server performs 'Update the location information'.](a057800564be3506d2d87b6a4daee25b_img.jpg) + +``` + +sequenceDiagram + participant Server as Location management Server + participant Client as Location management client + Note right of Client: 2. Configured location reporting event triggers + Note left of Server: 4. Update the location information + Server->>Client: 1. Location Reporting Configuration + Client->>Server: 2. Configured location reporting event triggers + Client->>Server: 3. Location Information Report + Server->>Server: 4. Update the location information + +``` + +Sequence diagram of the event-triggered location reporting procedure. It shows four steps: 1. Location management Server sends 'Location Reporting Configuration' to Location management client. 2. Location management client sends 'Configured location reporting event triggers' to Location management Server. 3. Location management client sends 'Location Information Report' to Location management Server. 4. Location management Server performs 'Update the location information'. + +**Figure 10.9.3.1-1: Event-triggered location reporting procedure** + +1. The location management server sends location reporting configuration message to the location management client(s) containing the initial configuration (or a subsequent update) for reporting the location of the MC service UE. This message can be sent over a unicast bearer to a specific location management client or as a group message over an **MBMS** bearer to update the location reporting configuration for multiple location management clients at the same time. + +NOTE 1: The location reporting configuration information can be made part of the user profile, in which case the sending of the message is not necessary. + +NOTE 2: Different location management clients may be given different location reporting criteria. + +2. A location reporting event occurs, triggering step 3. +3. The location management client sends a location information report to the location management server, containing location information identified by the location management server and available to the location management client. + +4. Upon receiving the report, the location management server updates location of the reporting location management client. If the location management server does not have location information of the reporting location management client before, then just stores the reporting location information for that location management client. + +#### 10.9.3.2 On-demand location reporting procedure + +The location management server can request UE location information at any time by sending a location information request to the location management client, which may trigger location management client to immediately send the location report. + +![Sequence diagram showing the on-demand location information reporting procedure between a Location management Server and a Location management client.](91134b9a38d7f73f03375473e7b706f9_img.jpg) + +``` + +sequenceDiagram + participant Server as Location management Server + participant Client as Location management client + Note left of Server: 1. Based on configurations or location request from other entities, decide to immediately initiate request location from user + Server->>Client: 2. Location Information Request + Note right of Client: 3. notify user and ask for permission to share location + Client->>Server: 4. Location Information Report + Note left of Server: 5. Update location information + +``` + +Sequence diagram showing the on-demand location information reporting procedure between a Location management Server and a Location management client. + +**Figure 10.9.3.2-1: On-demand location information reporting procedure** + +1. Based on configurations such as periodical location information timer, or location information request from other entities (e.g., another location management client, MC service server), location management server initiates the immediately request location information from the location management client. +2. The location management server sends a location information request to the location management client. +3. MC service user is notified and asked about the permission to share its location. MC service user can accept or deny the request +4. The location management client immediately responds to the location management server with a report containing location information identified by the location management server and available to the location management client. +5. Upon receiving the report, the location management server updates location of the reporting location management client. If the location management server does not have location information of the reporting location management client before, then just stores the reporting location information for that location management client. + +#### 10.9.3.3 Client-triggered location reporting procedure + +Figure 10.9.3.3-1 illustrates the high level procedure of client-triggered location reporting. + +![Sequence diagram for Client-triggered location reporting procedure](fcc757566216206ceddbd6c775e8db02_img.jpg) + +``` + +sequenceDiagram + participant C2 as Location management client 2 + participant S as Location management server + participant C1 as Location management client 1 + C2->>S: 1. Location reporting trigger + Note over S, C1: 2. Event-triggered location reporting procedure or +On-demand location reporting procedure + +``` + +The diagram illustrates the client-triggered location reporting procedure. It features three lifelines: 'Location management client 2', 'Location management server', and 'Location management client 1'. A message labeled '1. Location reporting trigger' is sent from Client 2 to the Server. The Server then initiates a procedure, represented by a box spanning the Server and Client 1 lifelines containing '2. Event-triggered location reporting procedure or On-demand location reporting procedure'. + +Sequence diagram for Client-triggered location reporting procedure + +**Figure 10.9.3.3-1: Client-triggered location reporting procedure** + +1. Location management client 2 (authorized MC service user) sends a location reporting trigger to the location management server to activate a location reporting procedure for obtaining the location information of location management client 1. +2. Location management server checks whether location management client 2 is authorized to send a location reporting trigger. Depending on the information specified by the location reporting trigger, location management server initiates an on-demand location reporting procedure or an event-triggered location reporting procedure for the location of location management client 1. + +#### 10.9.3.4 Location reporting cancel procedure + +The location reporting cancel procedure reuses the information flow of location reporting configuration. + +Pre-conditions: + +- The location management client has been provided the location reporting configuration information. + +![Sequence diagram for Location reporting cancel procedure](b996d5a6408db9c4b3ac3aafd2ef44cf_img.jpg) + +``` + +sequenceDiagram + participant S as Location management server + participant C as Location management client + S->>C: 1. Location Reporting Configuration + Note right of C: 2. stop location report + +``` + +The diagram illustrates the location reporting cancel procedure. It features two lifelines: 'Location management server' and 'Location management client'. A message labeled '1. Location Reporting Configuration' is sent from the Server to the Client. The Client then initiates a procedure, represented by a box on its lifeline containing '2. stop location report'. + +Sequence diagram for Location reporting cancel procedure + +**Figure 10.9.3.4-1: Location reporting cancel procedure** + +1. The location management server sends location reporting configuration without any information element to the location management client to stop location reporting from the MC service UE. +2. The location management client stops sending location information reports to the location management server. + +#### 10.9.3.5 Location information subscription procedure + +Figure 10.9.3.5-1 illustrates the high level procedure of location information subscription request. The same procedure can be applied for location management client and other entities that would like to subscribe to MC service user location information. + +![Sequence diagram for Figure 10.9.3.5-1 showing the location information subscription request procedure between a Location management server and an MC service server.](a47713c2491e6ce619259ed2f196fd24_img.jpg) + +``` + +sequenceDiagram + participant MC service server + participant Location management server + Note right of MC service server: 1. Location information subscription request + MC service server->>Location management server: 1. Location information subscription request + Note left of Location management server: 2. Authorization check + Note right of Location management server: 3. Location information subscription response + Location management server->>MC service server: 3. Location information subscription response + +``` + +Sequence diagram for Figure 10.9.3.5-1 showing the location information subscription request procedure between a Location management server and an MC service server. + +**Figure 10.9.3.5-1: Location information subscription request procedure** + +1. MC service server sends a location information subscription request to the location management server to subscribe location information of one or more MC service users. +2. The location management server shall check if the MC service server is authorized to initiate the location information subscription request. +3. The location management server replies with a location information subscription response indicating the subscription status. + +#### 10.9.3.6 Usage of location information procedure + +##### 10.9.3.6.1 Event-trigger location information notification procedure + +Figure 10.9.3.6.1-1 illustrates the high level procedure of event-trigger usage of location information. The same procedure can be applied for location management client and other entities that would like to subscribe to location information of MC service user. + +![Sequence diagram for Figure 10.9.3.6.1-1 showing the event-trigger usage of location information procedure between a Location management server and an MC service server.](d7efe1d3c9fce95c7bacefb7e7d7faff_img.jpg) + +``` + +sequenceDiagram + participant MC service server + participant Location management server + Note left of Location management server: 1. Based on configurations and subscription to report location information + Note right of Location management server: 2. Location information notification + Location management server->>MC service server: 2. Location information notification + Note right of MC service server: 3. share to other MC service user + Note left of MC service server: 3. share to other MC service user + +``` + +Sequence diagram for Figure 10.9.3.6.1-1 showing the event-trigger usage of location information procedure between a Location management server and an MC service server. + +**Figure 10.9.3.6.1-1: Event-trigger usage of location information procedure** + +1. Based on the configurations, e.g., subscription, periodical location information timer, location management server is triggered to report the latest user location information to MC service server. + +2. The location management server send the location information report including the latest location information of one or more MC service users to the MC service server. The latest location information is from the location report procedure as described in subclause 10.9.3.1, or from PLMN operator. +3. MC service server may further share this location information to a group or to another MC service user. + +NOTE: For other entities, the step 3 can be skipped if not needed. + +##### 10.9.3.6.2 On-demand usage of location information procedure + +The MC service server can request UE location information at any time by sending a location information request to the location management server, which may trigger location management server to immediately send the location report. + +Figure 10.9.3.6.2-1 illustrates the high level procedure of on demand usage of location information. The same procedure can be applied for location management client and other entities that would like to subscribe to location information of MC service user. + +![Sequence diagram illustrating the on-demand usage of location information procedure. The diagram shows two main entities: 'Location management server' and 'MC service server'. The sequence of messages is: 1. MC service server sends a 'Location Information request' to the Location management server. 2. The Location management server performs an internal action 'Get the latest location information'. 3. The Location management server sends a 'Location Information notification' to the MC service server. 4. A dashed box labeled 'share to other MC service user' is shown as an optional step from the MC service server.](10bf8762a8e8d9385609cc6fb11061fe_img.jpg) + +``` +sequenceDiagram + participant MC service server + participant Location management server + Note right of Location management server: 2. Get the latest location information + MC service server->>Location management server: 1. Location Information request + Location management server-->>MC service server: 3. Location Information notification + Note right of MC service server: 4. share to other MC service user +``` + +Sequence diagram illustrating the on-demand usage of location information procedure. The diagram shows two main entities: 'Location management server' and 'MC service server'. The sequence of messages is: 1. MC service server sends a 'Location Information request' to the Location management server. 2. The Location management server performs an internal action 'Get the latest location information'. 3. The Location management server sends a 'Location Information notification' to the MC service server. 4. A dashed box labeled 'share to other MC service user' is shown as an optional step from the MC service server. + +**Figure 10.9.3.6.2-1: On-demand usage of location information procedure** + +1. MC service server sends a location information request to the location management server. +2. The location management server acquires the latest location of the UEs being requested, by triggering an on-demand location report procedure as described in subclause 10.9.3.2, or from PLMN operator. +3. Then, location management server immediately sends the location information report including the latest location information acquired of one or more MC service users. +4. MC service server may further share this location information to a group or to another MC service user. + +NOTE: For other entities, the step 3 can be skipped if not needed. + +## 10.10 Emergency Alert + +### 10.10.1 On-network emergency alert + +#### 10.10.1.1 General + +The following subclauses specify the procedures for emergency alert initiation and emergency alert cancel that are utilised by the following MC services: + +- MCVideo service +- MCData service + +**Editor's note: Whether the following procedures for emergency alert initiation and emergency alert cancel apply to MCPTT service also is FFS.** + +#### 10.10.1.2 MC service emergency alert + +##### 10.10.1.2.1 MC service emergency alert initiation + +The procedure focuses on the case where an MC service client is initiating an MC service emergency alert unicast signalling for communicating the alert with the affiliated MC service group members of that MC service group. An MC service client in the MC service emergency state gains elevated access privilege for all of the MC service user's mission critical applications. This procedure will place the MC service client in the MC service emergency state if the MC service client is not already in that state. + +Procedures in figure 10.10.1.2.1-1 are the signalling control plane procedures for the MC service client initiating an MC service emergency alert with an MC service group i.e., MC service users on MC service client 1, MC service client 2 and MC service client 3 belong to the same MC service group which is defined on group management server. + +NOTE 1: For simplicity, a single MC service server is shown in place of a user home MC service server and a group hosting MC service server. + +Pre-conditions: + +1. The MC service group is previously defined on the group management server with MC service client 2 and MC service client 3 affiliated to that MC service group. +2. All members of the MC service group belong to the same MC system. +3. The initiating MC service client 1 is affiliated with one or more MC service groups. +4. The initiating MC service client 1 has been provisioned with an MC service group designated as the MC service emergency group. + +NOTE 2: Alternatively, the client could have been provisioned for emergency behaviour on the currently selected group. + +5. The initiating MC service client 1 may not have carried out an explicit affiliation procedure with the MC service group designated as the MC service emergency group. + +![Sequence diagram for MC service emergency alert. Lifelines: MC service client 1, MC service server, Group management server, MC service client 2, MC service client 3. The sequence starts with client 1 initiating an alert, followed by a request to the server, authorization check, group ID resolution, response to client 1, request to clients 2 and 3, notification to clients 2 and 3, response from clients 2 and 3 to the server, and finally an affiliate to group message from the server to the group management server.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 + participant MC service server + participant Group management server + participant MC service client 2 + participant MC service client 3 + + Note left of MC service client 1: 1. initiate emergency alert + MC service client 1->>MC service server: 2. MC service emergency alert request + Note right of MC service server: 3. Check alert authorization + Note right of MC service server: 4. Resolve group ID + MC service server->>MC service client 1: 5. MC service emergency alert response + MC service server->>MC service client 2: 6. MC service emergency alert request + MC service server->>MC service client 3: 6. MC service emergency alert request + Note right of MC service client 2: 7. Notify emergency + Note right of MC service client 3: 7. Notify emergency + MC service client 2->>MC service server: 8. MC service emergency alert response + MC service client 3->>MC service server: 8. MC service emergency alert response + Note right of MC service server: 9. Affiliate to group + MC service server-->>Group management server: 9. Affiliate to group + +``` + +Sequence diagram for MC service emergency alert. Lifelines: MC service client 1, MC service server, Group management server, MC service client 2, MC service client 3. The sequence starts with client 1 initiating an alert, followed by a request to the server, authorization check, group ID resolution, response to client 1, request to clients 2 and 3, notification to clients 2 and 3, response from clients 2 and 3 to the server, and finally an affiliate to group message from the server to the group management server. + +**Figure 10.10.1.2.1-1 MC service emergency alert** + +1. The user at the MC service client 1 initiates an MC service emergency alert. MC service client 1 sets its MC service emergency state. The MC service emergency state is retained by the MC service client until explicitly cancelled. +2. MC service client 1 requests the MC service server to send an MC service emergency alert request to the MC service group designated as the MC service emergency group. +3. MC service server checks whether the MC service user of MC service client 1 is authorized for initiation of MC service emergency alerts for the indicated MC service group. +4. MC service server resolves the MC service group ID to determine the members of that MC service group and their affiliation status, based on the information from group management server. +5. The MC service server sends the MC service emergency alert response to the MC service user 1 to confirm the MC service emergency alert request. MC service group calls made to this MC service group by the MC service client 1 will be sent as emergency calls until the emergency state on the MC service client 1 is cancelled. +6. The MC service server sends an MC service emergency alert request towards the MC service clients of each of those affiliated MC service group members. The MC service emergency alert request message shall contain the following information: Location, MC service ID and MC service group ID (i.e., MC service user's selected MC service group or dedicated MC service emergency group, as per MC service group configuration) and the MC service user's mission critical organization name. +7. MC service users are notified of the MC service emergency. +8. The receiving MC service clients send the MC service emergency alert response to the MC service server to acknowledge the MC service emergency alert. + +9. The MC service server implicitly affiliates the client to the emergency group if the client is not already affiliated. + +NOTE 3: Sending the emergency alert without making a request to also start an emergency call does not put the group into the in-progress emergency state. + +NOTE 4: Sending the emergency alert does not put the other UEs in the group into an emergency state. + +NOTE 5: The MC service client 1 need not initiate a group call. For example, the MC service client can be configured to only allow alerts or the MC service user can choose not to make an MC service emergency group call. + +**Editor's note: How emergency alert is synchronized between MC services is FFS.** + +##### 10.10.1.2.2 MC service emergency alert cancel + +The procedure focuses on the case where an MC service client has initiated an MC service emergency alert and entered the emergency state, and wishes to cancel the alert, informing the MC service server and other group members of this cancellation. By doing so, the MC service client may also request the cancellation of the in-progress emergency state of the group. + +Procedures in figure 10.10.1.2.2-1 are the signalling control plane procedures for the MC service client cancelling an MC service emergency alert with an MC service group i.e., MC service users on MC service client 1, MC service client 2 and MC service client 3 belong to the same MC service group which is defined on MC service group management server. + +NOTE 1: For simplicity, a single MC service server is shown in place of a user home MC service server and a group hosting MC service server. + +Pre-conditions: + +1. The MC service client 1 had previously successfully initiated an MC service emergency alert. +2. The MC service client 1 is still in the emergency state. +3. The initiating MC service client 1 has affiliated with the MC service group designated as the MC service emergency group. + +![Sequence diagram for MC service emergency alert cancel. Lifelines: MC service client 1, MC service server, Group management server, MC service client 2, MC service client 3. The sequence starts with client 1 initiating an emergency alert cancel. Client 1 sends a request to the server. The server resolves the group ID with the group management server. The server sends a response to client 1. The server then sends a request to clients 2 and 3. Clients 2 and 3 notify their users. Finally, clients 2 and 3 send responses to the server.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MC service client 1 + participant Server as MC service server + participant GroupServer as Group management server + participant Client2 as MC service client 2 + participant Client3 as MC service client 3 + + Note left of Client1: 1. initiate emergency alert cancel + Client1->>Server: 2. MC service emergency alert cancel request + Server->>GroupServer: 3. Resolve group ID + Server-->>Client1: 4. MC service emergency alert cancel response + Server->>Client2: 5. MC service emergency alert cancel request + Server->>Client3: 5. MC service emergency alert cancel request + Note right of Client2: 6. Notify emergency cancel + Note right of Client3: 6. Notify emergency cancel + Client2-->>Server: 7. MC service emergency alert cancel response + Client3-->>Server: 7. MC service emergency alert cancel response + +``` + +Sequence diagram for MC service emergency alert cancel. Lifelines: MC service client 1, MC service server, Group management server, MC service client 2, MC service client 3. The sequence starts with client 1 initiating an emergency alert cancel. Client 1 sends a request to the server. The server resolves the group ID with the group management server. The server sends a response to client 1. The server then sends a request to clients 2 and 3. Clients 2 and 3 notify their users. Finally, clients 2 and 3 send responses to the server. + +**Figure 10.10.1.2.2-1 MC service emergency alert cancel** + +1. The user at the MC service client 1 initiates an MC service emergency alert cancel. + +NOTE 2: The MC service emergency alert cancel request carries an indication to also request that the in-progress emergency is to be cancelled. The MC service server can accept or deny the request to cancel the in-progress emergency state of the group as a whole, separately from accepting or denying the request to cancel the emergency alert at MC service client 1. Additionally, an authorized user can cancel either or both the in-progress emergency state of the group and the initiator's MC service emergency alert. + +2. MC service client 1 requests the MC service server to send an MC service emergency alert cancel to the MC service group to which MC service client 1 had previously sent the emergency alert. +3. MC service server resolves the MC service group ID to determine the members of that MC service group and their affiliation status, based on the information from group management server. +4. The MC service server sends the MC service emergency alert cancel response to the MC service client 1 to confirm the MC service emergency alert cancel request. MC service client 1 resets its emergency state. +5. The MC service server sends an MC service emergency alert cancel request towards the MC service clients of each of those affiliated MC service group members. +6. MC service users are notified of the MC service emergency alert cancellation of MC service client 1. +7. The receiving MC service clients send the MC service emergency alert cancel response to the MC service server to acknowledge the MC service emergency alert cancel. For a multicast call scenario, these acknowledgements are not sent. + +### 10.10.2 Off-network emergency alert + +#### 10.10.2.1 General + +The following subclauses specify the procedures for emergency alert initiation and emergency alert cancel that are utilised by the following MC services: + +- MCVideo service +- MCData service + +**Editor's note:** Whether the following procedures for emergency alert initiation and emergency alert cancel apply to MCPTT service also is FFS. + +#### 10.10.2.2 MC service emergency alert + +##### 10.10.2.2.1 Emergency alert initiation + +Figure 10.10.2.2.1-1 describes procedures for the MC service client initiating an MC service emergency alert with an MC service group. + +This procedure will place the MC service client in the MC service emergency state if the MC service client is not already in that state. + +Pre-conditions: + +1. The initiating MC service client 1 has been provisioned with an MC service group designated as the MC service emergency group. + +NOTE 1: Alternatively, MC service client 1 could have been provisioned for emergency behaviour on the currently selected group. + +2. Information for **ProSe** direct communications corresponding to the MC service group and its mapping to **ProSe** Layer-2 Group ID are pre-configured in MC service client 1. +3. MC service client 1 to MC service client N are members of the same MC service group. +4. MC service user 1 has initiated MC service emergency alert. + +![Sequence diagram for Emergency alert initiation. Lifelines: MC service client 1 (Originator), MC service client 2, and MC service client 3. The sequence starts with client 1 sending a '1. MC service emergency alert announcement' to clients 2 and 3. Clients 2 and 3 then execute '2. Notify MC service emergency alert'. Both clients then send '3. Response' back to client 1. Finally, client 1 executes '4. Check participants'.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 (Originator) + participant MC service client 2 + participant MC service client 3 + Note left of MC service client 1: + MC service client 1->>MC service client 2: 1. MC service emergency alert announcement + MC service client 1->>MC service client 3: 1. MC service emergency alert announcement + Note right of MC service client 2: 2. Notify MC service emergency alert + Note right of MC service client 3: 2. Notify MC service emergency alert + MC service client 2->>MC service client 1: 3. Response + MC service client 3->>MC service client 1: 3. Response + Note left of MC service client 1: 4. Check participants + +``` + +Sequence diagram for Emergency alert initiation. Lifelines: MC service client 1 (Originator), MC service client 2, and MC service client 3. The sequence starts with client 1 sending a '1. MC service emergency alert announcement' to clients 2 and 3. Clients 2 and 3 then execute '2. Notify MC service emergency alert'. Both clients then send '3. Response' back to client 1. Finally, client 1 executes '4. Check participants'. + +**Figure 10.10.2.2.1-1: Emergency alert initiation** + +1. MC service client 1 sends an MC service emergency alert announcement message to the other clients. MC service client 1 sets its MC service emergency state. This MC service emergency state is retained by the MC service client until explicitly cancelled. Once MC service client1 is in the MC service emergency state, any communications initiated by MC service client 1, group or private, shall be initiated as emergency communications and shall receive priority treatment. The MC service emergency alert announcement is sent periodically so that late joining MC service group members are notified. + +NOTE 2: Sending the emergency alert without making a request to also start an MC service emergency communication does not put the group into the in-progress emergency state. + +2. MC service users are notified of the MC service emergency state of the originating MC service user. + +3. The MC service clients upon receiving the emergency alert announcement message acknowledge the MC service emergency alert to the originating MC service client. + +NOTE 3: The MC service client 1 need not initiate a group communication. For example, the MC service client can be configured to only allow alerts or the MC service user can choose not to make an MC service emergency group communication. + +NOTE 4: MC service clients need to respond only to the first emergency alert announcement message that is received. + +4. The originating MC service client 1 checks the responses and may inform the MC service user of the MC service group members whose MC service clients responded. + +##### 10.10.2.2.2 Emergency alert cancel + +An MC service client has initiated an MC service emergency alert, has entered the MC service emergency state and wishes to cancel the alert, informing the other MC service group members of the cancellation. As part of this process, the MC service client may also request the cancellation of the in-progress emergency state in the group if authorized to do so. + +Procedures in figure 10.10.2.2.2-1 describe procedures for the MC service client cancelling an MC service emergency alert. + +Pre-conditions: + +1. The MC service client 1 has successfully initiated an MC service emergency alert and is in the MC service emergency state. +2. Information for ProSe direct communications corresponding to the MC service group and its mapping to ProSe Layer-2 Group ID are pre-configured in MC service client 1. +3. MC service client 1 to MC service client N are members of the same MC service group. +4. MC service user 1 has initiated MC service emergency alert cancel. + +![Sequence diagram for Emergency alert cancel. MC service client 1 (Originator) sends a '1. MC service emergency alert cancel announcement' to MC service client 2 and MC service client 3. MC service client 2 and MC service client 3 each send a '2. Notify MC service emergency alert cancel' message. MC service client 2 and MC service client 3 each send a '3. Response' message back to MC service client 1.](9f50279046b74a4e66a1a0144c3b1d11_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 (Originator) + participant MC service client 2 + participant MC service client 3 + Note left of MC service client 1: MC service emergency alert cancel + MC service client 1->>MC service client 2: 1. MC service emergency alert cancel announcement + MC service client 1->>MC service client 3: 1. MC service emergency alert cancel announcement + MC service client 2->>MC service client 1: 2. Notify MC service emergency alert cancel + MC service client 3->>MC service client 1: 2. Notify MC service emergency alert cancel + MC service client 2->>MC service client 1: 3. Response + MC service client 3->>MC service client 1: 3. Response + +``` + +Sequence diagram for Emergency alert cancel. MC service client 1 (Originator) sends a '1. MC service emergency alert cancel announcement' to MC service client 2 and MC service client 3. MC service client 2 and MC service client 3 each send a '2. Notify MC service emergency alert cancel' message. MC service client 2 and MC service client 3 each send a '3. Response' message back to MC service client 1. + +**Figure 10.10.2.2.2-1 Emergency alert cancel** + +1. MC service client 1 sends an MC service emergency alert cancel announcement to the MC service group to which MC service client 1 had previously sent the emergency alert announcement message. +2. MC service users are notified of the MC service emergency alert cancellation by MC service client 1. +3. The receiving MC service clients acknowledge the MC service emergency alert cancel to the originating MC service client. + +NOTE: MC service clients that track the MC service emergency alerts of other MC service users, e.g. clients that fail to receive subsequent periodic MC service emergency alert announcements after a configured timeout can consider the alert to be cancelled. + +## 10.11 MC service resource management (on-network) + +### 10.11.1 General + +The following subclauses specify the procedures for resource management for mission critical services. The procedures are utilised by the following MC services: + +- MCPTT (as specified in 3GPP TS 23.379 [16]); +- MCVideO (as specified in 3GPP TS 23.281 [12]); and +- MCData (as specified in 3GPP TS 23.282 [13]). + +The MC service server sets up media bearers and may need to modify the bearers for an already established MC communication. + +Media characteristics that may need to be modified include: + +- activation and deactivation of the bearer; +- modification of the QoS characteristics of the bearer (e.g. bearer priority adjustment); and +- modification of GBR due to media codec change + +NOTE: A group call can consist of both unicast and multicast bearers which can all need modification due to the same event. + +### 10.11.2 Request for unicast resources at session establishment + +The procedure defined in this subclause specifies how network resources are requested at session establishment. If concurrent sessions are used the MC service server may utilize the capability of resource sharing specified in 3GPP TS 23.203 [8]. The request for resources is sent to the PCRF on the Rx reference point and includes media type, bandwidth, priority, application identifier and resource sharing information. + +The procedure is generic to any type of session establishment that requires requests for network resources. + +Procedures in figure 10.11.2-1 are the signalling procedures for the requesting resource at session establishment. + +![Sequence diagram showing the resource request at session establishment between MC service client, EPS (PCRF), SIP core, and MC service server. The steps are: 1. Session establishment from client to server; 2. MC service server evaluates need for network resources and media sharing; 3. Session progress - request for resources from server to SIP core; 4. PCC procedures (as defined in 3GPP TS 23.203 [4]) within SIP core; 5. Session progress from SIP core to client; 6. ok from client to SIP core; 7. ok from SIP core to server; 8. MC service call/session using unicast bearer established.](10cc1e74f2b71404f021bb8b3cec0ff0_img.jpg) + +``` + +sequenceDiagram + participant MC service client + participant EPS (PCRF) + participant SIP core + participant MC service server + + Note right of MC service server: 2. MC service server evaluates need for network resources and media sharing + Note right of SIP core: 4. PCC procedures (as defined in 3GPP TS 23.203 [4]) + + MC service client->>MC service server: 1. Session establishment + MC service server-->>SIP core: 3. Session progress - request for resources + SIP core-->>MC service client: 5. Session progress + MC service client-->>SIP core: 6. ok + SIP core-->>MC service server: 7. ok + Note bottom: 8. MC service call/session using unicast bearer established + +``` + +Sequence diagram showing the resource request at session establishment between MC service client, EPS (PCRF), SIP core, and MC service server. The steps are: 1. Session establishment from client to server; 2. MC service server evaluates need for network resources and media sharing; 3. Session progress - request for resources from server to SIP core; 4. PCC procedures (as defined in 3GPP TS 23.203 [4]) within SIP core; 5. Session progress from SIP core to client; 6. ok from client to SIP core; 7. ok from SIP core to server; 8. MC service call/session using unicast bearer established. + +Figure 10.11.2-1: Resource request at session establishment + +1. MC service client sends a call/session establishment request. +2. MC service server receives evaluates the need network resources and use of media resource sharing. +3. MC service server send a session progress request containing request for resources. +4. PCC procedures (as defined in 3GPP TS 23.203 [8]) initiated from SIP core local inbound/outbound proxy over Rx. +5. The SIP core local inbound / outbound proxy forwards the call control protocol request to the MC service client. +6. The MC service client acknowledges the session progress request with an OK message. + +7. The SIP core local inbound / outbound proxy forwards the OK message to the MC service server. +8. The MC service call/session is established and resources have been allocated. + +### 10.11.3 Request for modification of unicast resources + +To modify unicast media bearers, the MC service server shall send a resource modification request containing the parameters to be modified, using the call control protocol via the SIP core to the UE. + +Possible scenarios when this procedure may be used are: + +- Modify the allocation and retention priority for unicast resources; +- Release and resume resources in-between MC service calls when using the chat model; or +- Release and resume resources when a UE is able to receive the MC service call over multicast transmission + +Releasing resources for the media plane should give the option to allow the SIP session to either be torn down or continue. + +Procedures in figure 10.11.3-1 are the signalling procedures for the modification of a unicast: + +Pre-conditions: + +- An MC service call or session is already in progress; + +![Sequence diagram for Bearer modification request. The diagram shows four lifelines: MC service client, EPS (PCRF), SIP core, and MC service server. The process starts with an 'MC service call/session using unicast bearer already established'. The MC service server makes a '1. Media bearer modification decision', then sends a '2. Session update - Resource modification request' to the SIP core. The SIP core triggers '3. PCC procedures (as defined in 3GPP TS 23.203 [4])' with the EPS (PCRF). The SIP core then sends a '4. Session update' to the MC service client. The client responds with '5. ok' to the SIP core, which in turn sends '6. ok' to the MC service server. Finally, the MC service call/session continues with modified unicast resources.](1018d0db7bb02c169f646cb9cc244dc6_img.jpg) + +``` + +sequenceDiagram + participant MC service client + participant EPS (PCRF) + participant SIP core + participant MC service server + + Note over MC service client, MC service server: MC service call/session using unicast bearer already established + + MC service server->>MC service server: 1. Media bearer modification decision + MC service server->>SIP core: 2. Session update - Resource modification request + SIP core->>EPS (PCRF): 3. PCC procedures (as defined in 3GPP TS 23.203 [4]) + SIP core->>MC service client: 4. Session update + MC service client->>SIP core: 5. ok + SIP core->>MC service server: 6. ok + Note over MC service client, MC service server: 7. MC service call/session continues with modified unicast resources + +``` + +Sequence diagram for Bearer modification request. The diagram shows four lifelines: MC service client, EPS (PCRF), SIP core, and MC service server. The process starts with an 'MC service call/session using unicast bearer already established'. The MC service server makes a '1. Media bearer modification decision', then sends a '2. Session update - Resource modification request' to the SIP core. The SIP core triggers '3. PCC procedures (as defined in 3GPP TS 23.203 [4])' with the EPS (PCRF). The SIP core then sends a '4. Session update' to the MC service client. The client responds with '5. ok' to the SIP core, which in turn sends '6. ok' to the MC service server. Finally, the MC service call/session continues with modified unicast resources. + +**Figure 10.11.3-1: Bearer modification request** + +1. MC service server decides to modify the parameters of a unicast bearer (e.g. a request to upgrade the existing MC service call to an MC service emergency or imminent threat call). +2. MC service server sends a session update which includes a resource modification request containing the modified parameters of the unicast bearer. + +3. PCC procedures (as defined in 3GPP **TS 23.203** [8]) initiated from SIP core local inbound/outbound proxy over Rx. +4. The SIP core local inbound / outbound proxy forwards the session update request to the MC service client. +5. The MC service client acknowledges the call control protocol request with an OK message. +6. The SIP core local inbound / outbound proxy forwards the OK message to the MC service server. +7. The MC service call continues with the modified unicast resources. + +NOTE 1: If the MC service call is transferred to multicast transmission, the unicast resources could be temporarily be released. + +NOTE 2: If multiple audio streams are sent to the UE, additional bearer resources could be required during an established session. Pre-allocation of additional bearer resources already at session establishment could be useful. + +### 10.11.4 Management of multicast media bearers + +To activate the multicast media bearers the MC service server shall use the Activate **MBMS** Bearer procedure specified in 3GPP **TS 23.468** [18] with the MC service server performing the GCS AS function. + +To deactivate the multicast media bearers the MC service server shall use the Deactivate **MBMS** Bearer procedure specified in 3GPP **TS 23.468** [18] with the MC service server performing the GCS AS function. + +To modify multicast media bearers the MC service server shall use the Modify **MBMS** Bearer procedure specified in 3GPP **TS 23.468** [18] with the MC service server performing the GCS AS function. + +### 10.11.5 Request for resources with shared priority + +#### 10.11.5.1 General + +An MC service server that supports simultaneous sessions may need to share a common priority on the **EPS** bearer for several MC service group calls that may use different priorities on the application level. This is achieved by including information for priority sharing on the request of resources over Rx reference point to PCRF. All sessions associated with the same priority sharing information will be handled by one **EPS** bearer, which will have a priority based on the highest requested priority among the sessions. + +The use of the procedure defined in subclause 10.11.5.2 is dependent on operator policy. + +#### 10.11.5.2 Procedure + +Pre-conditions: + +- All previous resource requests from the MC service have included a priority sharing information. + +![Sequence diagram illustrating the resource request including priority sharing information. The diagram shows four lifelines: MC service client, EPS (PCRF), SIP core, and MC service server. The sequence of messages is: 1. Decision for bearer priority adjustment (from MC service server to SIP core), 2. Call control Bearer modification request (from SIP core to EPS (PCRF)), 3. PCC Bearer modification (from EPS (PCRF) to SIP core), 4. OK (from SIP core to EPS (PCRF)), 5. PCC updates the priority for the bearer (internal message in EPS (PCRF)), 6. Call control Bearer modification request (from SIP core to MC service client).](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +``` + +sequenceDiagram + participant MC service client + participant EPS (PCRF) + participant SIP core + participant MC service server + + Note right of MC service server: 1. Decision for bearer priority adjustment + MC service server->>SIP core: 2. Call control Bearer modification request + SIP core->>EPS (PCRF): 3. PCC Bearer modification + EPS (PCRF)-->>SIP core: 4. OK + Note right of EPS (PCRF): 5. PCC updates the priority for the bearer + SIP core->>MC service client: 6. Call control Bearer modification request + +``` + +Sequence diagram illustrating the resource request including priority sharing information. The diagram shows four lifelines: MC service client, EPS (PCRF), SIP core, and MC service server. The sequence of messages is: 1. Decision for bearer priority adjustment (from MC service server to SIP core), 2. Call control Bearer modification request (from SIP core to EPS (PCRF)), 3. PCC Bearer modification (from EPS (PCRF) to SIP core), 4. OK (from SIP core to EPS (PCRF)), 5. PCC updates the priority for the bearer (internal message in EPS (PCRF)), 6. Call control Bearer modification request (from SIP core to MC service client). + +**Figure 10.11.5.2-1: Resource request including priority sharing information** + +1. The MC service server decides based on a request from the MC service client that the priority of an ongoing call must be adjusted. +2. The MC service server requests a session update to the SIP core. This request will contain information of priority sharing. +3. The proxy function in the SIP core sends a request to the PCRF over Rx to request for modified priority. The request will include the priority sharing information over Rx. +4. The PCRF acknowledges the request. +5. PCC updates the bearer priority for the bearer that contains the SDFs associated with the same priority sharing information. The priority is set to highest priority (lowest ARP) among those SDFs. No additional bearer is created. Also the default bearer priority is updated accordingly. +6. The session update is forwarded to the MC service client. + +NOTE 1: The procedure defined above requires a PCC enhancement and is subject to implementation in **EPC** and IMS and can therefore only be used if supported by **EPC** and IMS. + +NOTE 2: If the **EPC** and IMS does not support the priority sharing from MC system, no shared priority treatment applies, and a new **EPS** bearer will be setup based on **QCI/ARP** combination. + +### 10.11.6 Request for media resources from MC service server + +#### 10.11.6.1 General + +The procedure in this sub clause specify how request for resource for floor control (or transmission control in MCVideo and MCData) and for the media plane can be handled independently. This procedure utilizes the Rx reference point both between from the MC service server to the PCRF and from the SIP core to the PCRF. + +Resource for the transmission control are requested at session establishment, in this case the IMS standard procedures as specified in 3GPP TS 23.228 [9] are used. The session description shall in this procedure include bandwidth + +information applicable for the transmission control traffic requirement. At group call setup the request for resources for the media plane is triggered. This request is sent directly from the MC service server to the PCRF. + +The procedure is optional and is suitable when the procedures for pre-established sessions are used, it may also be used to setup and tear down the media plane used by between consecutive group calls in one communication session using the chat call model. + +#### 10.11.6.2 Procedure + +The figure below illustrates the procedure for resource reservation + +![Sequence diagram showing the procedure for resource reservation between MC service client, EPS (PCRF), SIP core, and MC service server. The steps include: 1. Group affiliation request, 2. Session Establishment, 3. Session establishment, 4. Request for resource for transmission control, 5. Session establishment, 6. Call setup, 7. Request for resources for media bearers, 8. Group call ongoing, 9. Release of resources for media bearers.](bd50d56ae2c12a92466ba2aea1a78040_img.jpg) + +``` + +sequenceDiagram + participant MC service client + participant EPS (PCRF) + participant SIP core + participant MC service server + + Note left of MC service client: + MC service client->>MC service server: 1. Group affiliation request + MC service client->>SIP core: 2. Session Establishment + SIP core->>MC service server: 3. Session establishment + SIP core->>EPS (PCRF): 4. Request for resource for transmission control + SIP core->>MC service client: 5. Session establishment + MC service client->>MC service server: 6. Call setup + MC service server->>EPS (PCRF): 7. Request for resources for media bearers + Note right of MC service server: 8. Group call ongoing + MC service server->>EPS (PCRF): 9. Release of resources for media bearers + +``` + +Sequence diagram showing the procedure for resource reservation between MC service client, EPS (PCRF), SIP core, and MC service server. The steps include: 1. Group affiliation request, 2. Session Establishment, 3. Session establishment, 4. Request for resource for transmission control, 5. Session establishment, 6. Call setup, 7. Request for resources for media bearers, 8. Group call ongoing, 9. Release of resources for media bearers. + +**Figure 10.11.6.2-1: Request for resources for transmission control and media plane** + +1. The MC service client sends a request for group affiliation. +2. The MC service client sends a request to the MC service server for establishment of a communication session. +3. The MC service server answer the session establishment request and adjust the bandwidth information in the session description. The requested bandwidth shall be minimized to cover the bandwidth requirements for floor control signaling (or transmission control for MCVideo or MCData). +4. The SIP core request resources towards the PCRF according to the session establishment request.5. The session establishment request is completed and a response is sent towards the MC service client. +6. The MC service client sends a cell setup message according to existing procedures. +7. The MC service server sends a request for resources for the media plane to PCRF, and the media plane is by that established. This request includes media description relevant for the media plane. +8. Group call is ongoing on the group communication session. +9. The MC service serve sends a release of media resources to PCRF, and the media plane is by that terminated. + +NOTE 1: The resources for transmission control are retained. + +NOTE 2: Step 6-9 can be repeated several times within the life cycle of one communication session. + +## 10.12 Priority Management + +### 10.12.1 General + +Mission critical priority and QoS management is situational. The MC Services provides a real-time priority and QoS experience for the MC users, who have significant dynamic operational requirements that determine their priority. For example, the type of incident a responder is serving or the responder's overall shift role needs to strongly influence a user's ability to obtain resources from the **LTE** system. + +Priority treatment applies on both application layer as well as on transport layer. The details on how the priority level is evaluated and used is outside the scope of this specification. What is specified is the necessary mechanisms to apply the priority and QoS and map different priority parameters between different entities, for example to map application layer priority to transport layer priority. + +One of the requirements for MC communication services is to coordinate the use of priority levels between the different MC service servers. This priority coordination is used to mitigate and manage the risk for network congestion situations. + +### 10.12.2 Information flows + +#### 10.12.2.1 MC priority request + +Table 10.12.1.1-1 describes the information flow MC priority request from one MC service server to an MC service server taking the priority arbitration role. + +**Table 10.12.1.1-1: MC priority request** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------| +| Priority | M | Requested priority | +| Priority area | M | The geographical area for which the requested priority is required. | +| Type of service | O | The MC service type e.g. MCVideo, MCPTT or MCData | + +### 10.12.3 Procedure for priority coordination between multiple MC service servers + +In deployment scenarios with multiple MC service servers of different or the same type it is required to coordinate the priorities used by the different servers. The procedure defined below provides the necessary coordination between MC service servers to manage high priority levels. One of the involved MC service servers is assigned the role of being a priority arbitrator among a group of MC service servers serving the same geographical area. The priority arbitrator may also compete for the same limited network resources. Prior to using this procedure all MC service servers need to be configured with information about which MC service server will act as the priority arbitrator and under what conditions (e.g. priority level) the priority arbitrator should be used. The use of this procedure is not mandated. MC systems that supports priority coordination between multiple MC service servers should support this procedure. + +Pre-condition: + +1. One of the MC service servers is assigned the role of the priority arbitrator. +2. It is assumed that all MC service servers are part of the same trusted domain. +3. A MC communication session is ongoing or is about to commence. The operational situation together with static and dynamic attributes requires the use of elevated priority for network resources. + +Editor's note: It is FFS if enforcement of the granted priority can be applied to MC service servers outside of the same trusted domain + +Editor's note: It is FFS how the MC service server 2 (priority arbitrator) knows about ongoing traffic. + +![Sequence diagram illustrating priority arbitration between multiple MC service servers. The diagram shows four lifelines: MC service server 1, MC service server 2 (priority arbitrator), MC service server 3, and MC service clients. The process starts with server 1 identifying a need for elevated priority, sending a request to server 2, which makes a decision and grants it. Server 2 then notifies server 3 and the clients. Server 1 then communicates with elevated priority. When the need ceases, server 1 sends a release to server 2, which in turn releases it to server 3.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +``` + +sequenceDiagram + participant S1 as MC service server 1 + participant S2 as MC service server 2 +(priority arbitrator) + participant S3 as MC service server 3 + participant CL as MC service clients + + Note over S1: 1. Need for elevated MC +priority level identified + S1->>S2: 2. MC priority request + Note over S2: 3. Priority decision based +on requested priority + S2-->>S1: 4. MC priority granted + S2->>S3: 5. MC Priority taken + Note over S1: 6. MC service communication +with elevated priority + S2-->>S3: 7a. Elevated priority notification + S3-->>CL: 7b. Elevated priority notification + S2-->>S1: 7c. Elevated priority notification + Note over S1: 8. The need for elevated MC +priority is ceased + S1->>S2: 9. MC Priority Release + S2->>S3: 10. MC Priority Release + +``` + +Sequence diagram illustrating priority arbitration between multiple MC service servers. The diagram shows four lifelines: MC service server 1, MC service server 2 (priority arbitrator), MC service server 3, and MC service clients. The process starts with server 1 identifying a need for elevated priority, sending a request to server 2, which makes a decision and grants it. Server 2 then notifies server 3 and the clients. Server 1 then communicates with elevated priority. When the need ceases, server 1 sends a release to server 2, which in turn releases it to server 3. + +**Figure 10.12.3-1: Priority arbitration between multiple MC service servers** + +1. A need for high priority level is identified by the MC service server 1. The priority level identified is above the level of priority that the MC service server 1 can utilise without centralized priority arbitration. +2. The MC service server 1 sends a MC priority request to the MC service server being assigned the priority arbitrator role. The request includes the geographical area, duration, the priority level, service type and needed capacity. +3. The priority arbitrator determines whether to grant, reject or queue the request for elevated priority. + +NOTE 1: How the priority arbitrator makes this determination is out of scope of the present document. + +NOTE 2: One source of information for the priority arbitrator to evaluate the priority request, could be information received at the resource reservations over the Rx reference point. Example of such information is resource request failure and Retry-Interval AVP which could be an indication of RAN user plane congestion, see reference 3GPP TS 29.214 [27]. + +4. The priority arbitrator grants MC service server 1 the elevated priority. +5. The priority arbitrator notifies other MC service servers about the elevated priority granted to other services. + +NOTE 3: The behaviour of the MC service servers that receive this information is implementation specific. The MC service server may take this information into account when performing priority evaluations for the MC service clients managed by this MC service server. + +6. The MC service server utilizes the elevated priority when requesting resources for new or existing MC service communication. + +NOTE 4: The priority level granted to the MC service server 1 can be mapped to an applicable SIP priority header or a reservation priority AVP (when the MC service server use the Rx reference point directly). + +- 7a-c. A priority notification may be sent to the MC service clients in the geographical area in which the priority was granted. Messages to MC service clients need to be sent from the MC service server serving each MC user. This message is preferably sent over a multicast bearer. + +**Editor's note: How the clients could utilize such notifications is FFS.** + +8. The MC service server 1 identifies that the elevated priority is not needed. +9. The requested MC Priority is released from the MC service server 1. +10. The MC service server 2 (priority arbitrator) informs other MC servers that the elevated priority is released. + +Editor's note: It is FFS to include procedure for MC priority revoking. + +Editor's note: It is FFS to include procedure for MC priority queueing. + +## 10.13 Functional alias management (on-network) + +### 10.13.1 General + +Functional alias management procedures apply to on-network MC service only. + +### 10.13.2 Information flows for functional alias management + +#### 10.13.2.1 Functional alias information query request + +Table 10.13.2.1-1 describes the information functional alias information query request from the MC service client to the MC service server. + +**Table 10.13.2.1-1: Functional alias information query request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user who performs the query. | +| MC service ID | M | The identity of the MC service user to be queried. | + +#### 10.13.2.2 Functional alias information query response + +Table 10.13.2.2-1 describes the information functional alias information query response from the MC service server to the MC service client. + +**Table 10.2.2.17-1: Functional alias information query response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user who performs the query. | +| MC service ID | M | The identity of the MC service user to be queried. | +| Query result | M | The functional alias information retrieved from the functional alias management server, i.e. the list of activated functional alias identities of the MC service user. | + +#### 10.13.2.3 Functional alias activation request + +Table 10.13.2.3-1 describes the information flow functional alias activation request from the MC service client to the MC service server. + +**Table 10.13.2.3-1: Functional alias activation request** + +| Information element | Status | Description | +|-----------------------|--------|-------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the functional alias activation request. | +| Functional alias list | M | A list of one or more functional aliases which the originator intends to activate. | + +#### 10.13.2.4 Functional alias activation response + +Table 10.13.2.4-1 describes the information flow functional alias activation response from the MC service server to the MC service client. + +**Table 10.13.2.4-1: Functional alias activation response** + +| Information element | Status | Description | +|----------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the functional alias activation request. | +| Functional alias list | M | A list of one or more functional aliases which the originator intends to activate. | +| Activation status per functional alias | M | Indicates the activation result for each functional alias in the list (activated, rejected, can be taken over). | + +#### 10.13.2.5 Functional alias de-activation request + +Table 10.13.2.5-1 describes the information flow functional alias de-activation request from the MC service client to the MC service server. + +**Table 10.13.2.5-1: Functional alias de-activation request** + +| Information element | Status | Description | +|-----------------------|--------|----------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the functional alias de-activation request. | +| Functional alias list | M | A list of one or more functional aliases which the originator intends to de-activate. | + +#### 10.13.2.6 Functional alias de-activation response + +Table 10.13.2.6-1 describes the information flow functional alias de-activation response from the MC service server to the MC service client. + +**Table 10.13.2.6-1: Functional alias de-activation response** + +| Information element | Status | Description | +|-------------------------------------------|--------|----------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the functional alias de-activation request. | +| Functional alias list | M | A list of one or more functional aliases which the originator intends to de-activate. | +| De-activation status per functional alias | M | Indicates the de-activation result for every functional alias in the list. | + +#### 10.13.2.7 Functional alias status notification + +Table 10.13.2.7-1 describes the information flow functional alias notification from the MC service server to the MC service client. + +**Table 10.13.2.7-1: Functional alias status notification** + +| Information element | Status | Description | +|-----------------------|--------|-----------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the functional alias activation, de-activation or take over request. | +| Functional alias list | M | A list of one or more functional aliases. | +| Operations | M | Activation, de-activation or take over status per functional alias. | + +#### 10.13.2.8 Functional alias take over request + +Table 10.13.2.8-1 describes the information flow functional alias take over request from the MC service client to the MC service server. + +**Table 10.13.2.8-1: Functional alias take over request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the functional alias take over request. | +| Functional alias | M | A functional alias which the originator intends to take over. | + +#### 10.13.2.9 Functional alias take over response + +Table 10.13.2.9-1 describes the information flow functional alias take over response from the MC service server to the MC service client. + +**Table 10.13.2.9-1: Functional alias take over response** + +| Information element | Status | Description | +|----------------------------------------|--------|-------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the functional alias activation request. | +| Functional alias | M | A functional alias which the originator intends to take over. | +| Activation status per functional alias | M | Indicates the take over request result (accepted, rejected). | + +#### 10.13.2.10 Functional alias revoke notification + +Table 10.13.2.10-1 describes the information flow functional revoke notification from the MC service server to the MC service client. + +**Table 10.13.2.10-1: Functional alias revoke notification** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator who triggers the functional alias take over request. | +| Functional alias | M | The functional alias which is revoked. | + +### 10.13.3 Authorised MC service user retrieves active functional alias(es) for a certain MC service + +An authorised MC service user can request the active functional alias(es) for a certain MC service user. + +Figure 10.13.3-1 below illustrates the active functional alias list query for a certain MC service user. + +![Sequence diagram for Active functional alias list query](9c45844d796e85ae05505870a54e4eb4_img.jpg) + +``` +sequenceDiagram + participant MC service client + participant MC service server + Note right of MC service server: 2. Authorization check and retrieve according to the conditions + MC service client->>MC service server: 1. Function alias information query request + MC service server-->>MC service client: 3. Function alias information query response +``` + +The diagram illustrates a sequence of interactions between an MC service client and an MC service server. The client sends a 'Function alias information query request' (step 1) to the server. The server performs an 'Authorization check and retrieve according to the conditions' (step 2) and then sends a 'Function alias information query response' (step 3) back to the client. + +Sequence diagram for Active functional alias list query + +**Figure 10.13.3-1: Active functional alias list query** + +1. The MC service client of the MC service user requests a list of active functional aliases for a certain MC service user from the MC service server by sending a functional alias information query request. The MC service ID is included. +2. The MC service server checks whether the MC service user is authorized to perform the query. If authorized, then the MC service server retrieves the requested active functional alias information based on the MC service ID. +3. The MC service server sends a functional alias information query response including the active functional alias information to the MC service client. + +### 10.13.4 MC service user activates functional alias(es) within an MC system + +The procedure for MC service user activates functional alias(es) within an MC system is illustrated in figure 10.13.4-1. + +Pre-conditions: + +1. MC service client has already been provisioned (statically or dynamically) with the functional alias(es) information that the MC service client is allowed to activate. +2. MC service server may have retrieved the user subscription and functional alias policy e.g. which user(s) are authorized to activate to what functional alias, priority, and other configuration data. +3. MC service client may have indicated to the functional alias management server that it wishes to receive updates of functional alias data for the functional aliases for which it is authorized. +4. The MC service client triggers the functional alias activation procedure. This is an explicit activation caused either by the MC service user or determined by a trigger event such as the MC service UE coming within a permitted geographic operational area of a functional alias. + +![Sequence diagram illustrating the functional alias activation procedure within an MC system. The diagram shows three lifelines: MC service client, MC service server, and Other MC service client(s). The sequence of messages is: 1. Functional alias(es) activation request from MC service client to MC service server; 2. Authorization check based on functional alias(es) policy, user subscription etc. (internal message on MC service server); 3. Store functional alias(es) status (internal message on MC service server); 4. Functional alias(es) activation response from MC service server to MC service client; 5. Functional alias(es) status notification from MC service server to Other MC service client(s).](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +``` + +sequenceDiagram + participant MC service client + participant MC service server + participant Other MC service client(s) + Note right of MC service server: 2. Authorization check based on functional alias(es) policy, user subscription etc. + Note right of MC service server: 3. Store functional alias(es) status + MC service client->>MC service server: 1. Functional alias(es) activation request + MC service server-->>MC service client: 4. Functional alias(es) activation response + MC service server->>Other MC service client(s): 5. Functional alias(es) status notification + +``` + +Sequence diagram illustrating the functional alias activation procedure within an MC system. The diagram shows three lifelines: MC service client, MC service server, and Other MC service client(s). The sequence of messages is: 1. Functional alias(es) activation request from MC service client to MC service server; 2. Authorization check based on functional alias(es) policy, user subscription etc. (internal message on MC service server); 3. Store functional alias(es) status (internal message on MC service server); 4. Functional alias(es) activation response from MC service server to MC service client; 5. Functional alias(es) status notification from MC service server to Other MC service client(s). + +**Figure 10.13.4-1: Functional alias activation procedure within an MC system** + +1. MC service client of the MC service user requests the MC service server to activate a functional alias or a set of functional aliases. +2. The MC service server checks if there are any conflicts with active functional alias(es). +3. If the user of the MC service client is authorised to activate the requested functional alias(es) then the MC service server stores the functional alias(es) status of the requested functional alias(es). + +If a certain functional alias(es) can be simultaneously active for multiple MC service users and the upper limit of number of simultaneous MC service users is not reached, the MC service shall activate the functional alias(es) for the MC service user and inform all other MC service user(s) with sharing the same functional alias(es) (step 5). If the limit of number of simultaneous MC service users is reached or the functional alias is not allowed to be shared, the request is rejected and the MC service user is notified (step 4). + +If the functional alias(es) is (are) already used by another MC service user(s), an authorized MC service user gets an offer to take over the functional alias from the MC service user currently using the functional alias(es). + +4. MC service server sends a functional alias(es) activation response to the MC service client. +5. The MC service server informs all other MC service user(s) sharing the same functional alias(es). + +### 10.13.5 MC service user de-activates functional alias(es) within an MC system + +The procedure for MC service user de-activates functional alias(es) within an MC system is illustrated in figure 10.13.5-1. + +When an MC service user does not want to use a functional alias(es) anymore, then the MC service user can de-activate functional alias(es). + +Pre-conditions: + +1. MC service server has already subscribed to the functional alias(es) information from the functional alias management server and has stored the data of the functional alias(es) a MC service user has activated. +2. The MC service client triggers the functional alias(es) de-activation procedure. This is an explicit de-activation request either by the MC service user or determined by a trigger event such as the MC service UE moving outside a permitted geographic operational area of a functional alias. + +![Sequence diagram illustrating the functional alias de-activation procedure within an MC system. The diagram shows three lifelines: MC service client, MC service server, and Other MC service client(s). The sequence of messages is: 1. Functional alias(es) de-activation request from MC service client to MC service server; 2. Authorization check based on functional alias(es) policy, user subscription etc. within MC service server; 3. Store functional alias(es) status within MC service server; 4. Functional alias(es) de-activation response from MC service server to MC service client; 5. Functional alias(es) status notification from MC service server to Other MC service client(s).](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +``` +sequenceDiagram + participant MC service client + participant MC service server + participant Other MC service client(s) + Note right of MC service server: 2. Authorization check based on functional alias(es) policy, user subscription etc. + Note right of MC service server: 3. Store functional alias(es) status + MC service client->>MC service server: 1. Functional alias(es) de-activation request + MC service server-->>MC service client: 4. Functional alias(es) de-activation response + MC service server->>Other MC service client(s): 5. Functional alias(es) status notification +``` + +Sequence diagram illustrating the functional alias de-activation procedure within an MC system. The diagram shows three lifelines: MC service client, MC service server, and Other MC service client(s). The sequence of messages is: 1. Functional alias(es) de-activation request from MC service client to MC service server; 2. Authorization check based on functional alias(es) policy, user subscription etc. within MC service server; 3. Store functional alias(es) status within MC service server; 4. Functional alias(es) de-activation response from MC service server to MC service client; 5. Functional alias(es) status notification from MC service server to Other MC service client(s). + +**Figure 10.13.5-1: Functional alias de-activation procedure within an MC system** + +1. MC service client requests the MC service server to de-activate a functional alias or a set of functional aliases. +2. Based on the MC service user subscription and stored functional alias policy, the MC service server checks if the MC service user of the MC service client is authorized to de-activate from the requested functional alias(es) and if the MC service user of the MC service client has activated to the requested functional alias(es). +3. If the MC service user is authorized to de-activate from the requested functional alias(es) then the MC service server updates the functional alias activation status of the MC service user. +4. MC service server provides to the MC service client the functional alias de-activation response. +5. The MC service server informs all other MC service user(s) sharing the same functional alias(es). + +### 10.13.6 Authorised MC service user takes over functional alias(es) within an MC system + +The procedure for MC service user takes over functional alias(es) within an MC system is illustrated in figure 10.13.6-1. + +During functional alias(es) activation, if the functional alias(es) is (are) already used by another MC service user(s), an authorized MC service user may get an offer to take over the functional alias(es) from the MC service user currently using the functional alias(es). + +Pre-conditions: + +1. MC service client 1 has performed the functional alias(es) activation procedure as described in subclause 10.13.4. +2. As result of the functional alias(es) activation procedure, the MC service user of MC service client 1 is aware which functional alias(es) are already used but can be taken over. +3. The MC service user of MC service client 1 decides to take over a functional alias. + +![Sequence diagram illustrating the functional alias taking over procedure within an MC system. The diagram shows interactions between MC service client 1, MC service server, MC service client 2, and Other MC service client(s).](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 + participant MC service server + participant MC service client 2 + participant Other MC service client(s) + + Note right of MC service server: 2. Authorization check based on functional alias(es) policy, user subscription etc. + Note right of MC service server: 4. Store functional alias(es) status + + MC service client 1->>MC service server: 1. Functional alias take over request + MC service server-->>MC service client 2: 3. Functional alias revoke notification + MC service server-->>MC service client 1: 5. Functional alias take over response + MC service server-->>Other MC service client(s): 6. Functional alias(es) status notification + +``` + +Sequence diagram illustrating the functional alias taking over procedure within an MC system. The diagram shows interactions between MC service client 1, MC service server, MC service client 2, and Other MC service client(s). + +**Figure 10.13.6-1: Functional alias taking over procedure within an MC system** + +1. MC service client 1 of the MC service user 1 requests the MC service server to take over a functional alias by sending a functional alias take over request. +2. The MC service server checks if there are any conflicts taking over the functional alias. +3. If the user of the MC service client 1 is authorised to take over the requested functional alias then the MC service server sends a functional alias revoke notification to inform MC service client 2 that the functional alias has been revoked and is not any longer active for the user of MC service client 2. +4. The MC service server stores the functional alias status of the requested functional alias. +5. MC service server sends a functional alias take over response to the MC service client. +6. The MC service server informs all other MC service user(s) sharing the same functional alias. + +## 10.14 Generic procedures for interconnection + +### 10.14.1 General + +Interconnection provides a means for communication between different MC systems with differing levels of trust between those MC systems. This subclause describes generic procedures for interconnection which are variations of specific procedures detailed in 3GPP TS 23.379 [16] and 3GPP TS 23.281 [12]. These procedures should be read in conjunction with specific procedures in those specifications. + +### 10.14.2 Generic call procedure with topology hiding + +#### 10.14.2.1 General + +The procedure in this subclause applies to MC service group calls and private calls made between multiple MC systems where topology hiding is required. An MC gateway server in an MC system is used to route calls to and from partner MC systems, and by doing so hides the topology of the MC system. + +#### 10.14.2.2 Procedure for calls with topology hiding + +Figure 10.14.2.2-1 shows the procedure where an MC service client initiates an MC service group call to an MC service group where the primary MC system of that MC service group is an interconnected MC system, or where an MC service client initiates an MC service private call to an MC service user where the primary MC system of that MC service user is an interconnected partner MC system. In this procedure, both MC systems make use of topology hiding. + +NOTE 1: This procedure does not illustrate the case where the target MC service client has migrated, and where further forwarding of the call request is required. + +Pre-conditions: + +1. MC service client 1 is receiving MC service in a different MC system to the primary MC system of the target MC service group or MC service user, and the MC systems are interconnected. + +NOTE 2: MC service client 1 may be receiving service in the primary MC system of MC service client 1, or may have successfully migrated to a partner MC system. + +2. If the call to be originated by MC service client 1 is an MC service group call, MC service client 1 has affiliated to the MC service group. +3. If the call to be originated by MC service client 1 is an MC service private call, the target MC service client, MC service client 2, is receiving service from the primary MC system of that MC service client. + +![Sequence diagram titled 'Call to target in interconnected MC system'. It shows the interaction between MC service client 1, its serving MC service server, its MC gateway server, a partner MC system gateway server, a partner MC service server, and MC service client 2. The sequence includes call requests, determination steps, authorization checks, and call responses.](832a0ce332e784fe80289e9f00f56574_img.jpg) + +``` + +sequenceDiagram + participant MCSC1 as MC service client 1 + participant SMSS as Serving MC service server + participant SMGWS as Serving MC system MC gateway server + participant PMGWS as Partner MC system MC gateway server + participant PMSS as Partner MC service server + participant MCSC2 as MC service client 2 + + Note left of SMSS: Serving MC system of MC service client 1 + Note right of PMGWS: Partner MC system + + MCSC1->>SMSS: 1. Call request + SMSS->>SMGWS: 2. Determine target MC service server + SMSS->>SMGWS: 3. Call request + SMGWS->>PMGWS: 4. Determine partner MC system for target for call + SMGWS->>PMGWS: 5. Call request + PMGWS->>PMSS: 6. Determine partner MC service server + PMGWS->>PMSS: 7. Call request + PMSS->>MCSC2: 8. Authorization check + PMSS->>MCSC2: 9. Call request + MCSC2->>PMSS: 10. Call response + PMSS->>PMGWS: 11. Call response + PMGWS->>SMGWS: 12. Call response + SMGWS->>SMSS: 13. Call response + SMSS->>MCSC1: 14. Call response + Note bottom: 15. Establish floor/transmission control and media paths + +``` + +Sequence diagram titled 'Call to target in interconnected MC system'. It shows the interaction between MC service client 1, its serving MC service server, its MC gateway server, a partner MC system gateway server, a partner MC service server, and MC service client 2. The sequence includes call requests, determination steps, authorization checks, and call responses. + +Figure 10.14.2.2-1: Call to target in interconnected MC system + +1. MC service client 1 initiates a call request to a target MC service user or MC service group, where the primary MC system of that MC service user or MC service group is an interconnected partner MC system. +2. The serving MC service server of MC service client 1 determines that the call has a target in a different MC system, and that the MC gateway server is the correct next hop for the call. +3. The serving MC service server of MC service client 1 forwards the call request to the MC gateway server of the serving MC system. +4. The MC gateway server identifies the correct partner MC system which is the primary MC system for the target of the call. + +NOTE 3: The MC gateway server of the serving MC system of MC service client 1 will contain configuration to allow it to route the call request over the signalling plane to the MC gateway server in the partner MC system. + +5. The MC gateway server of the primary MC system of MC service client 1 forwards the call request to the MC gateway server of the partner MC system. +6. The MC gateway server of the partner MC system determines the MC service server which is the primary MC service server for the target MC service user or MC service group. + +NOTE 4: The MC gateway server of the partner MC system will contain configuration allowing it to make use of the target MC service ID or MC service group ID to identify the primary MC service server of the target MC service user or MC service group. + +7. The call request is forwarded to the partner MC service server which is the primary MC service server of the target MC service user or MC service group. +8. The partner MC service server which is the primary MC service server of the target MC service user or MC service group checks that the call is authorized to be made. The authorization process checks that the call origin is permissible (i.e. from the serving MC system of calling MC service user, and from that calling MC service user) for a call to the target MC service user or MC service group. +9. Providing that the authorization in step 8 is successful, the call request is sent to MC service client 2. +10. MC service client 2 sends a call response to the call request. +11. The partner MC service server, which is the primary MC service server of the target MC service user or MC service group, sends a call response to the MC gateway server in the partner MC system. +12. The MC gateway server in the partner MC system sends the call response to the MC gateway server in the primary MC system of MC service client 1. +13. The MC gateway server in the primary MC system sends the call response to the serving MC service server of MC service client 1. +14. The serving MC service server sends the call response to MC service client 1. + +NOTE 5. Steps 9 and 10 may occur at any time after step 8 and prior to step 15, provided that step 9 always take place before step 10. If the authorization in step 8 has failed, then steps 9 and 10 do not occur. + +- 15.If the call response was successful, floor control and media paths are established for the call. + +### 10.14.3 Generic call procedure for enforcement of local MC service group configuration + +#### 10.14.3.1 General + +The procedure in the following subclauses apply to MC service group calls made between multiple MC systems where the partner MC system applies local configuration to the MC service group configuration which has been provided by the primary MC system of the MC service group. The serving MC server of the MC service group members, that is a participating server for the MC service group, applies enforcement of local MC service group configuration. + +#### 10.14.3.2 MC service group call initiated in the partner MC system of the MC service group + +Figure 10.14.3.2-1 shows the procedure where an MC service group call is initiated by an MC service client receiving MC service in the partner MC system of the MC service group. + +NOTE 1: Any topology hiding by the primary or partner MC system of the MC service group is not shown within this procedure. + +Pre-conditions: + +1. MC service client 1 is receiving MC service in a partner MC system of the MC service group, and the MC systems are interconnected. + +NOTE 2: MC service client 1 can be receiving service in the primary MC system of MC service client 1, or can have successfully migrated to a partner MC system. + +- MC service client 1 has affiliated to the MC service group. + +![Sequence diagram illustrating the enforcement of local configuration with a call originated in a partner MC system of the MC service group. The diagram shows interactions between MC service client 1, Serving MC service server, and Group host MC service server.](f1de68a4cbb9b92a1c0ffd919bbd199c_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 + participant Serving MC service server + participant Group host MC service server + + Note left of MC service client 1: Serving MC system of MC service client 1 + Note right of Group host MC service server: Primary MC system of MC service group + + MC service client 1->>Serving MC service server: 1. Group call request + activate Serving MC service server + Serving MC service server->>Serving MC service server: 2. Authorize group call request using local configuration + activate Serving MC service server + Serving MC service server->>Group host MC service server: 3. Group call request + deactivate Serving MC service server + activate Group host MC service server + Group host MC service server->>Group host MC service server: 4. Authorize group call request using group configuration + activate Group host MC service server + Group host MC service server->>Serving MC service server: 5. Group call response + deactivate Group host MC service server + activate Serving MC service server + Serving MC service server->>MC service client 1: 6. Group call response + deactivate Serving MC service server + Note bottom: 7. Establish floor/transmission control and media paths + +``` + +Sequence diagram illustrating the enforcement of local configuration with a call originated in a partner MC system of the MC service group. The diagram shows interactions between MC service client 1, Serving MC service server, and Group host MC service server. + +**Figure 10.14.3.2-1: Enforcement of local configuration with call originated in partner MC system of MC service group** + +- MC service client 1 initiates a group call request to the MC service group, where the primary MC system of that MC service group is an interconnected partner MC system. +- The serving MC service server of MC service client 1 authorizes the group call request using local group configuration information. +- If the group call request authorization by the serving MC service server of MC service client 1 is successful, the serving MC service server forwards the group call request to the group host MC service server in the primary MC system of the MC service group. +- The primary MC service server of the MC service group checks that the call is authorized to be made. The authorization process checks that the call origin is permissible (i.e. from the serving MC system of calling MC service user, and from that calling MC service user) for a call to that MC service group. +- Providing that authorization in step 4 is successful, the group call response is sent to the serving MC service server of MC service client 1. +- The serving MC service server sends the MC service group call response to MC service client 1. +- Floor control or transmission control and media paths are established for the MC service group call. + +#### 10.14.3.3 MC service group call request received from the primary MC system of the MC service group + +Figure 10.14.3.3-1 shows the procedure where an MC service group call request is received from the primary MC system of the MC service group, which includes an MC service group member MC service client 1 that is receiving service within the partner MC system of the MC service group. Any topology hiding by the primary or partner MC system of the MC service group is not shown within this procedure. + +Pre-conditions: + +- MC service client 1 is receiving MC service in a partner MC system of the MC service group, and the MC systems are interconnected. + +NOTE: MC service client 1 can be receiving service in the primary MC system of MC service client 1, or can have successfully migrated to a partner MC system. + +- 2. MC service client 1 has affiliated to the MC service group. + +![Sequence diagram showing the enforcement of local configuration for a group call request. The diagram involves two main systems: 'Primary MC system of MC service group' and 'Serving MC system of MC service client 1'. The 'Primary MC system' contains a 'Group host MC service server'. The 'Serving MC system' contains a 'Serving MC service server' and 'MC service client 1'. The sequence of messages is: 1. Group call request from Group host MC service server to Serving MC service server; 2. Authorize group call request using local configuration (internal to Serving MC service server); 3. Group call request from Serving MC service server to MC service client 1; 4. Group call response from MC service client 1 to Serving MC service server; 5. Group call response from Serving MC service server to Group host MC service server; 6. Establish floor/transmission control and media paths (internal to Primary MC system).](114902bbeea56bda01b64b43fad41920_img.jpg) + +Sequence diagram showing the enforcement of local configuration for a group call request. The diagram involves two main systems: 'Primary MC system of MC service group' and 'Serving MC system of MC service client 1'. The 'Primary MC system' contains a 'Group host MC service server'. The 'Serving MC system' contains a 'Serving MC service server' and 'MC service client 1'. The sequence of messages is: 1. Group call request from Group host MC service server to Serving MC service server; 2. Authorize group call request using local configuration (internal to Serving MC service server); 3. Group call request from Serving MC service server to MC service client 1; 4. Group call response from MC service client 1 to Serving MC service server; 5. Group call response from Serving MC service server to Group host MC service server; 6. Establish floor/transmission control and media paths (internal to Primary MC system). + +**Figure 10.14.3.3-1: Enforcement of local configuration where group call request is received from primary MC system of MC service group** + +- 1. A group call request is received from the group host MC service server in the primary MC system of the MC service group. +- 2. The serving MC service server of MC service client 1 authorizes the group call request using local group configuration information. +- 3. If the group call request authorization by the serving MC service server of MC service client 1 is successful, the serving MC service server sends the group call request to MC service client 1. +- 4. MC service client 1 responds to the group call request with a group call response. +- 5. The group call response is sent to the group host MC service server of the MC service group. +- 6. Floor control or transmission control and media paths are established for the MC service group call. + +### 10.14.4 Generic call procedure for media replication in participating MC system in MC service group calls + +#### 10.14.4.1 General + +The procedure in the following subclause applies to MC service group calls made between multiple MC systems where the partner MC system carries out media replication to served MC service group members. + +#### 10.14.4.2 Media replication in the partner MC system of the MC service group + +Figure 10.14.4.2-1 shows the procedure where an MC service group call is initiated by an MC service client receiving MC service in the primary MC system of the MC service group, and media replication takes place in the partner MC system. + +NOTE1: Any topology hiding by the primary or partner MC system of the MC service group is not shown within this procedure. + +Pre-conditions: + +- 1. MC service client 1 is receiving MC service in the primary MC system of the MC service group, and the MC systems are interconnected. +- 2. MC service clients 2, 3 and n are receiving MC service in the partner MC system of the MC service group. + +NOTE 2: MC service clients 2,3 and n can be receiving MC service in the primary MC system of MC clients 2, 3 and n, or one or more of MC service clients 2, 3 and n can have successfully migrated to a partner MC system. + +3. MC service clients 1, 2, 3 and n have affiliated to the MC service group. + +![Sequence diagram showing media replication in a partner MC system. It includes Primary MC system (MC service client 1, Group host MC service server) and Partner MC system (Serving MC service server, MC service client 2, 3, n). Steps: 1. Group call setup; 2. Floor grant; 3a. Media flow from client 1 to host; 3b. Media flow from host to serving server; 3c. Media flow from serving server to clients 2, 3, n.](79aaab5889060cf8264226764a109cdb_img.jpg) + +The diagram illustrates the interaction between a Primary MC system and a Partner MC system for media replication. + +Primary MC system components: MC service client 1, Group host MC service server. + +Partner MC system components: Serving MC service server, MC service client 2, MC service client 3, MC service client n. + +Sequence of events: + +1. A horizontal bar across all components labeled '1. Group call setup and floor/transmission control and media paths established'. + +2. An arrow labeled '2. Floor grant' points from the Group host MC service server back to MC service client 1. + +3a. An arrow labeled '3a. Media flow' points from MC service client 1 to the Group host MC service server. + +3b. An arrow labeled '3b. Media flow' points from the Group host MC service server to the Serving MC service server. + +3c. A horizontal bar labeled '3c. Media flow' is shown at the Serving MC service server, with lines extending to MC service client 2, 3, and n. + +Sequence diagram showing media replication in a partner MC system. It includes Primary MC system (MC service client 1, Group host MC service server) and Partner MC system (Serving MC service server, MC service client 2, 3, n). Steps: 1. Group call setup; 2. Floor grant; 3a. Media flow from client 1 to host; 3b. Media flow from host to serving server; 3c. Media flow from serving server to clients 2, 3, n. + +Figure 10.14.4.2-1: Media replication in partner MC system of MC service group + +- 1. An MC service group call is set up and floor or transmission control and media paths are established, and MC service client 1 requests permission to transmit media to the MC service group. +- 2. The group host MC service server grants the requested floor or transmission permission to MC service client 1. +- 3a. MC service client 1 transmits a media stream to the group host MC service server. +- 3b. The group host MC service server sends a single media stream to the serving MC service server of MC service clients 2, 3 and n in the partner MC system of the MC service group. +- 3c. The serving MC service server of MC service clients 2, 3 and n replicates and distributes the media to MC service clients 2, 3 and n. + +NOTE 3: Media distribution to MC service clients 2, 3 and n may be using unicast or multicast bearers. + +# Annex A (normative): Configuration data for MC services + +## A.1 General + +This Annex provides information about the static data needed for configuration for MC services, which belong to one of the following categories: + +- MC service UE configuration data (see subclause A.2); +- MC service user profile data (see subclause A.3); +- MC service group configuration data (see subclause A.4); +- MC service configuration data (see subclause A.5); and +- Initial MC service UE configuration data (see subclause A.6). + +For each configuration category, data is split between configuration data that is applicable to both on-network and off-network, configuration data that is applicable to on-network only, and configuration data that is applicable to off-network only. The configuration data in each configuration category corresponds to a single instance of the category type i.e. the MC service UE, MC service group, MC service user and MC service configuration data refers to the information that will be stored against each MC service UE, MC service group, MC service user and MC service. This means that the three separate tables (on-network and off-network, on-network only, off-network only) for each configuration category represent the complete set of data for each configuration data category element. + +The columns in the tables have the following meanings: + +- Reference: the reference of the corresponding requirement in 3GPP TS 22.280 [3] or 3GPP TS 22.281 [4] or 3GPP TS 22.282 [5] or 3GPP TS 22.179 [2] or the corresponding subclause from the present document. +- Parameter description: A short definition of the semantics of the corresponding item of data, including denotation of the level of the parameter in the configuration hierarchy. +- When it is not clear to which functional entities the parameter is configured, then one or more columns indicating this are provided where the following nomenclature is used: + - "Y" to denote "Yes" i.e. the parameter denoted for the row needs to be configured to the functional entity denoted for the column. + - "N" to denote "No" i.e. the parameter denoted for the row does not need to be configured to the functional entity denoted for the column. + +Parameters within a set of configuration data have a level within a hierarchy that pertains only to that configuration data. The hierarchy of the configuration data is common across all the three tables of on-network and off-network, on-network only and off-network only. The level of a parameter within the hierarchy of the configuration data is denoted by use of the character ">" in the parameter description field within each table, one per level. Parameters that are at the top-most level within the hierarchy have no ">" character. Parameters that have one or more ">" characters are child parameters of the first parameter above them that has one less ">" character. Parent parameters are parameters that have one or more child parameters. Parent parameters act solely as a "grouping" of their child parameters and therefore do not contain an actual value themselves i.e. they are just containers for their child parameters. + +Each parameter that can be configured online shall only be configured through one online reference point. Each parameter that can be configured offline shall only be configured through one offline reference point. The most recent configuration data made available to the MC service UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism. + +## --- A.2 MC service UE configuration data + +MC service UE configuration data has to be known by an MC service UE after MC service authorization. The CSC-4 reference point is used for configuration between the configuration management server and the configuration management client on the MC service UE when the MC service UE is on-network. + +MC service UE configuration data can be configured offline using the CSC-11 reference point. + +MC service UE configuration data is specific to each MC service and is specified as follows: + +- MCPTT UE configuration data is specified in 3GPP TS 23.379 [16]; +- MCVideo UE configuration data is specified in 3GPP TS 23.281 [12]; and +- MCData UE configuration data is specified in 3GPP TS 23.282 [13]. + +Within each MC service, the MC service UE configuration data can be the same or different across MC service UEs. + +## --- A.3 MC service user profile configuration data + +The MC service user profile configuration data is stored in the MC service user database. The configuration management server is used to configure the MC service user profile configuration data to the MC service user database (CSC-13) and MC service UE (CSC-4). + +MC service user profile configuration data can be configured offline using the CSC-11 reference point. + +MC service user profile configuration data is specific to each MC service and is specified as follows: + +- MCPTT user profile configuration data is specified in 3GPP TS 23.379 [16]; +- MCVideo user profile configuration data is specified in 3GPP TS 23.281 [12]; and +- MCData user profile configuration data is specified in 3GPP TS 23.282 [13]; + +## --- A.4 Group configuration data + +The group configuration data is stored in the group management server. The group management server is used to configure the group configuration data to the MC service UE (CSC-2) and the MC service server (CSC-3). + +A single group can support one or multiple MC service configurations. Hence, the MC service group configuration data is divided into common group configuration data and MC service specific group configuration data. + +The group configuration data can be configured offline using the CSC-12 reference point. + +The common group configuration data are specified in table A.4-1. Tables A.4-1 and A.4-2 contain the group configuration required to support the use of on-network MC service. Tables A.4-1 and A.4-3 contain the group configuration required to support the use of off-network MC service. + +The MC service related group configuration data specific to each MC service is specified as follows: + +- MCPTT related group configuration data is specified in 3GPP TS 23.379 [16]; +- MCVideo related group configuration data is specified in 3GPP TS 23.281 [12]; and +- MCData related group configuration data is specified in 3GPP TS 23.282 [13]; + +**Table A.4-1: Common group configuration data (on and off network)** + +| Reference | Parameter description | MC service UE | MC service Server | Group management server | +|----------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------------|-------------------------| +| [R-5.17-004],<br>[R-6.4.3-001],<br>[R-6.4.3-002],<br>[R-6.9-004] and<br>[R-5.1.3-002] of<br>3GPP TS 22.280 [3] | MC service group ID | Y | Y | Y | +| [R-5.17-004],<br>[R-6.4.3-001],<br>[R-6.4.3-002] and<br>[R-6.9-004] of<br>3GPP TS 22.280 [3] | Group Alias (Contact URIs) | Y | Y | Y | +| | List of group members (see NOTE 1)<br>(see NOTE 8) | | | | +| [R-5.1.3-001],<br>[R-5.1.5-001],<br>[R-6.4.5-005] and<br>[R-6.4.5-006] of<br>3GPP TS 22.280 [3] | > MCPTT | | | | +| | >> MCPTT ID (see NOTE 2) | N | Y | Y | +| 3GPP TS 33.180 [25] | >> KMSUri for security domain of the MCPTT ID (see NOTE 3) | N | Y | Y | +| [R-6.2.2-001] and<br>[R-7.6-007] of<br>3GPP TS 22.280 [3] | >> User priority for the group | N | Y | Y | +| [R-5.1.3-001] of<br>3GPP TS 22.280 [3] | >> Participant type for the group (group membership information). The participant type values are defined and configured by the Mission Critical Organisation (e.g. first responder, second responder, dispatcher, dispatch supervisor, MC service administrator). | N | Y | Y | +| [R-5.1.3-001],<br>[R-5.1.5-001],<br>[R-6.4.5-005] and<br>[R-6.4.5-006] of<br>3GPP TS 22.280 [3] | > MCVideo | | | | +| | >> MCVideo ID (see NOTE 2) | N | Y | Y | +| 3GPP TS 33.180 [25] | >> KMSUri for security domain of the MCVideo ID (see NOTE 3) | N | Y | Y | +| [R-6.2.2-001] and<br>[R-7.6-007] of<br>3GPP TS 22.280 [3] | >> User priority for the group | N | Y | Y | +| [R-5.1.3-001] of<br>3GPP TS 22.280 [3] | >> Participant type for the group (group membership information). The participant type values are defined and configured by the Mission Critical Organisation (e.g. first responder, second responder, dispatcher, dispatch supervisor, MC service administrator). | N | Y | Y | +| [R-5.1.3-001],<br>[R-5.1.5-001],<br>[R-6.4.5-005] and<br>[R-6.4.5-006] of<br>3GPP TS 22.280 [3] | > MCData | | | | +| | >> MCData ID (see NOTE 2) | N | Y | Y | +| 3GPP TS 33.180 [25] | >> KMSUri for security domain of the MCData ID (see NOTE 3) | N | Y | Y | +| [R-6.2.2-001] and<br>[R-7.6-007] of<br>3GPP TS 22.280 [3] | >> User priority for the group | N | Y | Y | + +| | | | | | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---| +| [R-5.1.3-001] of 3GPP TS 22.280 [3] | >> Participant type for the group (group membership information). The participant type values are defined and configured by the Mission Critical Organisation (e.g. first responder, second responder, dispatcher, dispatch supervisor, MC service administrator). | N | Y | Y | +| | > Affiliation status | | | | +| | >> MCPTT | N | Y | Y | +| | >> MCVideo | N | Y | Y | +| | >> MCData | N | Y | Y | +| [R-5.16.2-001] and [R-5.16.2-002] of 3GPP TS 22.280 [3] | Group's owner (Mission Critical Organisation) | Y | Y | Y | +| Subclause 8.3.2, 10.2.3 | MC service specific configuration (see NOTE 4) | | | | +| | > MCPTT configuration (see NOTE 5) | | | | +| | > MCVideo configuration (see NOTE 6) | | | | +| | > MCData configuration (see NOTE 7) | | | | +| | List of subordinate groups | | | | +| [R-5.2.2-002] of 3GPP TS 22.280 [3] | > MC service group ID | N | Y | Y | +| | Group broadcast information | | | | +| [R-5.2.2-001] of 3GPP TS 22.280 [3] | Level within group hierarchy | N | Y | Y | +| [R-5.2.3-001] of 3GPP TS 22.280 [3] | Level within user hierarchy | N | Y | Y | +| NOTE 1: The list of group members is provided to an authorized user only upon request and not by default. | | | | | +| NOTE 2: MC service IDs for all configured MC services shall be provided for the configured group member. | | | | | +| NOTE 3: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1. | | | | | +| NOTE 4: An MC service specific configuration shall be provided for all of the MC services for which the group is enabled. At least one MC service shall be enabled for a group. | | | | | +| NOTE 5: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.379 [16]. | | | | | +| NOTE 6: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.281 [12]. | | | | | +| NOTE 7: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.282 [13]. | | | | | +| NOTE 8: The list of group members comprises all group members in primary and in partner MC systems of the MC service group. | | | | | + +**Table A.4-2: Common group configuration data (on-network)** + +| Reference | Parameter description | MC service UE | MC service Server | Group management server | +|----------------------------------------|---------------------------------------------------------------------------------------|---------------|-------------------|-------------------------| +| [R-6.1-001] of 3GPP TS 22.280 [3] | Maximum number of group members (Nc6) | N | Y | Y | +| [R-6.1-003] of 3GPP TS 22.280 [3] | Enabled/disabled group (basic status) | Y | Y | Y | +| [R-6.6.1-006] of 3GPP TS 22.280 [3] | Temporary group indication | Y | Y | Y | +| [R-6.4.5-005] of 3GPP TS 22.280 [3] | List of authorised users who can request the list of members of an MC service group | Y | Y | Y | +| | > MCPTT IDs | | | Y | +| | > MCVideo IDs | | | Y | +| | > MCData IDs | | | Y | +| | MC service specific configuration | | | | +| | > MCPTT configuration (see NOTE 1) | | | | +| | > MCVideo configuration (see NOTE 2) | | | | +| | > MCData configuration (see NOTE 3) | | | | +| [R-6.4.9-006] of 3GPP TS 22.280 [3] | Geographic area within which affiliation to the group is permitted (see NOTE 4) | Y | Y | Y | +| [R-6.4.9-006] of 3GPP TS 22.280 [3] | Geographic area outside which de-affiliation from the group is mandatory (see NOTE 4) | Y | Y | Y | +| Subclause 10.2.5 | List of authorised users who can retrieve the group information | | | | +| | > MCPTT IDs | | | Y | +| | > MCVideo IDs | | | Y | +| | > MCData IDs | | | Y | +| Subclause 5.2.3 | Associated relay service code (as specified in 3GPP TS 23.303 [14]) | Y | N | Y | +| Subclause 5.2.9 of 3GPP TS 23.280 [16] | List of partner MC systems from which interconnection is permitted for the group | | | | +| Subclause 5.2.9 of 3GPP TS 23.280 [16] | > Identity of partner MCPTT system | | Y | Y | +| Subclause 5.2.9 of 3GPP TS 23.280 [16] | > Identity of partner MCVideo system | | Y | Y | +| Subclause 5.2.9 of 3GPP TS 23.280 [16] | > Identity of partner MCData system | | Y | Y | + +NOTE 1: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.379 [16]. + +NOTE 2: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.281 [12]. + +NOTE 3: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.282 [13]. + +NOTE 4: The geographic area may consist of a union of regions that are non-contiguous or contain holes. + +Editor's note: the identity of the partner MC system is FFS + +**Table A.4-3: Common group configuration data (off-network)** + +| Reference | Parameter description | MC service UE | MC service server | Group management server | +|-------------------|--------------------------------------------------------------------------------------------------------------------|---------------|-------------------|-------------------------| +| Subclause 8.1.3.2 | ProSe layer-2 group ID (as specified in 3GPP TS 23.303 [14]) | Y | N | Y | +| Subclause 8.1.3.2 | ProSe group IP multicast address (as specified in 3GPP TS 23.303 [14]) | Y | N | Y | +| Subclause 8.1.3.2 | Indication of whether the UE shall use IPv4 or IPv6 for the MC service group (as specified in 3GPP TS 23.303 [14]) | Y | N | Y | +| | MC service specific configuration | | | | +| | > MCPTT configuration (see NOTE 1) | | | | +| | > MCVideo configuration (see NOTE 2) | | | | +| | > MCData configuration (see NOTE 3) | | | | + +NOTE 1: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.379 [16]. +NOTE 2: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.281 [12]. +NOTE 3: This parameter is a parent parameter whose child parameters are defined in 3GPP TS 23.282 [13]. + +## A.5 MC service configuration data + +The MC service configuration data is stored in the MC service server. The configuration management server is used to configure the MC service configuration data to the MC service server (CSC-5) and the MC service UE (CSC-4). + +The MC service configuration data can be configured offline using the CSC-11 reference point. + +The MC service configuration data is specific to each MC service and hence the detailed list of MC service configuration data is listed as follows: + +- MCPTT service configuration data is specified in 3GPP TS 23.379 [16]; +- MCVideo service configuration data is specified in 3GPP TS 23.281 [12]; and +- MCData service configuration data is specified in 3GPP TS 23.282 [13]; + +## A.6 Initial MC service UE configuration data + +The initial MC service UE configuration data is essential to the MC service UE to successfully connect to the MC system. The initial MC service UE configuration data can be the same or different across MC service UEs. + +Data in table A.6-1 is provided to the MC service UE's clients (e.g. MC service client, group management client, configuration management client, identity management client, key management client) during the bootstrap process (see subclause 10.1.1), and can be configured on the MC service UE offline using the CSC-11 reference point or via other means e.g. as part of the MCPTT client's provisioning on the UE, using a device management procedure. + +**Table A.6-1: Initial MC service UE configuration data (on-network)** + +| Reference | Parameter description | +|------------------|---------------------------------------------------------------| +| Subclause 10.1.1 | PDN connectivity information | +| | > HPLMN ID and optionally VPLMN ID to which the data pertains | +| | > MC services PDN | +| | >> APN | +| | >> PDN access credentials | +| | > MC common core services PDN | +| | >> APN | +| | >> PDN access credentials | +| | > MC identity management service PDN | +| | >> APN | +| | >> PDN access credentials | +| Subclause 10.1.1 | Application plane server identity information | +| | > Identity management server | +| | >> Server URI | +| | > Configuration management server | +| | >> Server URI | +| | > Key management server | +| | >> Server URI | +| | >> KMSUri for security domain managed by KMS | + +# Annex B (informative): Service continuity for MC service + +## B.1 Service continuity between on-network MC service and UE-to-network relay MC service + +This annex describes how 3GPP TS 23.237 [10] mechanisms for IMS service continuity can be used to provide service continuity between on-network MC service and UE-to-network relay MC service. For illustration, MCPTT AS is considered as the MC service. + +Only the procedure for service continuity from on-network MCPTT service to UE-to-network relay MCPTT service is described in figure B.1-1. The procedure for service continuity in the opposite direction is identical. + +![A complex network architecture diagram showing service continuity from on-network to UE-to-network relay. It includes components like UE-1, eNB, MME, PCRF, SGW/PGW, MBMS GW, BM-SC, SIP core, MCPTT AS, and SCC AS. The diagram illustrates two states: an initial on-network state with solid lines and a relay state with dashed lines after a handover indicated by a downward arrow.](fc3e2b49a9f850951570e502393b697f_img.jpg) + +The diagram illustrates the network architecture for service continuity. A central yellow box contains the eNB, MME, PCRF, SGW/PGW, MBMS GW, and BM-SC. UE-1 (with an MCPTT client) is initially connected to the eNB via a Uu interface. The eNB is connected to the MME via S1-MME, and the MME is connected to the SGW/PGW via S1-U. The SGW/PGW is connected to the SIP core via SGi. The SIP core is connected to the MCPTT AS and the SCC AS. The MBMS GW is connected to the BM-SC via SG-imb and SG-mb interfaces. The BM-SC is connected to the SIP core via MB2. The MME is also connected to the PCRF via Sm and S11 interfaces. The PCRF is connected to the SIP core via Rx and Gx interfaces. A downward arrow indicates a transition from the initial on-network state (solid lines) to a relay state (dashed lines). In the relay state, UE-1 establishes a PC5 connection with a UE-R, which is connected to the eNB. The SIP session is anchored at the SCC AS. The diagram also shows SIP-1 and MCPTT-1 signaling paths between the UE and the SIP core. + +A complex network architecture diagram showing service continuity from on-network to UE-to-network relay. It includes components like UE-1, eNB, MME, PCRF, SGW/PGW, MBMS GW, BM-SC, SIP core, MCPTT AS, and SCC AS. The diagram illustrates two states: an initial on-network state with solid lines and a relay state with dashed lines after a handover indicated by a downward arrow. + +**Figure B.1-1: Service continuity from on-network to UE-to-network relay** + +As illustrated in figure B.1-1: + +- Initially UE-1 has a direct connection to the network (on-network MCPTT service). It is registered with the SIP core and is engaged in a SIP session with the MCPTT Application Server (solid lines SIP-1 and MCPTT-1 in figure B.1-1). +- When UE-1 realises that it is losing connection to the network, or after the connection to the network has been lost, UE-1 discovers a **UE-to-network relay** (UE-R) and establishes a **PC5** connection with UE-R. UE-1 registers with the SIP core over the target access leg and enters **UE-to-network relay** MCPTT service by transferring the media streams over the target leg (dashed lines SIP-1 and MCPTT-1 in figure B.1-1). +- The SIP session is anchored at a Service Centralisation and Continuity Application Server (SCC AS) before and after the handover, as described in 3GPP TS 23.237 [10]. + +Depicted in figure B.1-2 is the call flow for service continuity when the UE switches from on-network MCPTT service to UE-to-network MCPTT relay service. + +![Sequence diagram illustrating service continuity when a UE switches from on-network MCPTT service to UE-to-network relay MCPTT service. The diagram shows five steps: 0. UE-1 engaged in On-Network service; 1. UE-1 losing connection; 2. UE-1 connects to the relay (discovery, PC5 auth, IP address); 3. UE-1 registers with the SIP core on the access leg relayed via UE-R; 4. UE-1 transfers media streams on the access leg relayed via UE-R (including 4a. INVITE (STI), 4b. INVITE (STI), 4c. UPDATE or reINVITE, 4d. UPDATE or reINVITE); 5. UE-1 engaged in UE-to-Network Relay service. Lifelines: UE-1 (Remote UE), SIP core, SCC AS, MCPTT AS, and UE-R (Relay).](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +``` + +sequenceDiagram + participant UE1 as UE-1 (Remote UE) + participant SIP as SIP core + participant SCC as SCC AS + participant MCPTT as MCPTT AS + participant UR as UE-R (Relay) + + Note over UE1, MCPTT: 0. UE-1 engaged in On-Network service with the MCPTT server via the SCC AS + Note over UE1: 1. UE-1 losing connection + Note over UE1, UR: 2. UE-1 connects to the relay (discovery, PC5 auth, IP address) + Note over UE1, SIP: 3. UE-1 registers with the SIP core on the access leg relayed via UE-R + Note over UE1, SIP: 4. UE-1 transfers the media streams on the access leg relayed via UE-R + UE1->>SIP: 4a. INVITE (STI) + SIP->>SCC: 4b. INVITE (STI) + SCC->>SIP: 4c. UPDATE or reINVITE + SIP->>MCPTT: 4d. UPDATE or reINVITE + Note over UE1, MCPTT: 5. UE-1 engaged in UE-to-Network Relay service + +``` + +Sequence diagram illustrating service continuity when a UE switches from on-network MCPTT service to UE-to-network relay MCPTT service. The diagram shows five steps: 0. UE-1 engaged in On-Network service; 1. UE-1 losing connection; 2. UE-1 connects to the relay (discovery, PC5 auth, IP address); 3. UE-1 registers with the SIP core on the access leg relayed via UE-R; 4. UE-1 transfers media streams on the access leg relayed via UE-R (including 4a. INVITE (STI), 4b. INVITE (STI), 4c. UPDATE or reINVITE, 4d. UPDATE or reINVITE); 5. UE-1 engaged in UE-to-Network Relay service. Lifelines: UE-1 (Remote UE), SIP core, SCC AS, MCPTT AS, and UE-R (Relay). + +**Figure B.1-2 Service continuity when UE switches from on-network MCPTT service to UE-to-network relay MCPTT service** + +0. UE-1 has a direct connection to the network and is engaged in a SIP session with the MCPTT AS (on-network MCPTT service). The SIP session is anchored at a Service Centralisation and Continuity Application Server (SCC AS) and a Session transfer Identifier (STI) is assigned for the anchored SIP session, as described in 3GPP TS 23.237 [10]. + +1. UE-1 realises that it is losing connection to the network or has completely lost it. + +2. UE-1 (in the role of remote UE) performs **ProSe UE-to-network relay** discovery over **PC5** and establishes a secure point-to-point link with the relay (UE-R) over **PC5**. As part of this process the remote UE is mutually authenticated at **PC5** layer with either the relay or with the network as specified in 3GPP **TS 23.303** [14]. In the process UE-1 is also assigned an IP address/prefix by the relay. + +NOTE 1: If step 2 is started after losing connection, the service interruption can be noticeable to the user. + +NOTE 2: Step 2 will be entirely described under in 3GPP **TS 23.303** [14]. + +3: UE-1 registers with the SIP core over the **UE-to-network relay** leg. + +4. In order to transfer the media streams of the SIP session UE-1 sends an INVITE message on the new access leg towards the SCC AS. The INVITE message includes the STI identifying the session to be transferred. The SCC AS identifies the session based on STI and updates the session over the remote access leg i.e. towards the MCPTT AS. + +5. The procedure is completed when all media streams have been transferred on the access leg relayed via UE-R. At this point UE-1 may deregister the on-network leg if it still has direct network connection (not shown in the figure). + +NOTE 3: The procedure for service continuity is always completed with unicast delivery on the target side. If MCPTT content is being distributed on the target side in multicast mode, then switching from unicast to multicast delivery is performed after completion of the service continuity procedure. + +# --- Annex C (informative): Change history + +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +|---------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016-04 | | | | | | Initial version. | 0.0.0 | +| 2016-04 | | | | | | Alignment with the following Rel-13 CRs agreed at SA6#10:<br>CR0057(S6-160312), CR0063(S6-160189),<br>CR0065(S6-160362),CR0068(S6-160348),<br>CR0069(S6-160313), CR0070(S6-160280),<br>CR0071(S6-160199), CR0079(S6-160360),<br>CR0080(S6-160297), CR0085(S6-160361),<br>CR0092(S6-160345), CR0095(S6-160339),<br>CR0099(S6-160342) | 0.1.0 | +| 2016-06 | | | | | | Implemented the following pCRs approved in SA6#11:<br>S6-160378, S6-160489, S6-160492, S6-160504,<br>S6-160524, S6-160528, S6-160560, S6-160561,<br>S6-160570, S6-160578, S6-160579, S6-160583,<br>S6-160600, S6-160601<br>Also implemented the Rapporteur actions from SA6#11:<br>1. Removed all colour coding from the TS<br>2. Fixed the subclauses numbering in the entire TS.<br>3. Generalized the text as per agreed terminology.<br>4. Added references for TS 23.303 and TS 23.237 | 0.2.0 | +| 2016-08 | | | | | | Implemented the following pCRs approved in SA6#12:<br>S6-160794, S6-160795, S6-160796, S6-160797,<br>S6-160798, S6-160799, S6-160880, S6-160888,<br>S6-160919, S6-160920 | 0.3.0 | +| 2016-09 | | | | | | Implemented the pCR S6-160822 which was approved in SA6#12<br>Modified the references order | 0.4.0 | +| 2016-10 | | | | | | Implemented the following pCRs approved in SA6#13: S6-160960, S6-161119, S6-161120, S6-161122, S6-161128, S6-161207, S6-161208, S6-161214, S6-161215, S6-161220, S6-161252, S6-161255 | 0.5.0 | +| 2016-11 | | | | | | Implemented the following pCRs approved in SA6#14: S6-161417, S6-161490, S6-161521, S6-161527, S6-161530, S6-161531, S6-161539, S6-161571, S6-161582, S6-161583, S6-161592, S6-161593, S6-161606, S6-161617, S6-161618, S6-161619, S6-161620, S6-161625, S6-161627, S6-161632, S6-161638 | 0.6.0 | +| 2016-11 | SA#74 | SP-160875 | | | | Submitted for Approval at SA#74 | 1.0.0 | +| 2016-12 | SA#74 | SP-160875 | | | | MCC Editorial update for publication after TSG SA approval (SA#74) | 14.0.0 | +| 2017-03 | SA#75 | SP-170069 | 0001 | 1 | F | Alignment of definitions | 14.1.0 | +| 2017-03 | SA#75 | SP-170069 | 0002 | 2 | F | Alignment of group affiliation and de-affiliation requirements | 14.1.0 | +| 2017-03 | SA#75 | SP-170069 | 0003 | 1 | F | Alignment of bearer management | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0004 | 1 | F | Removal of CSC-6 from figure 7.3.1-1 | 14.1.0 | +| 2017-03 | SA#75 | SP-170069 | 0005 | 1 | F | CFA Correction of information flow for MBMS | 14.1.0 | +| 2017-03 | SA#75 | SP-170069 | 0009 | 1 | F | Corrections on group configuration tables | 14.1.0 | +| 2017-03 | SA#75 | SP-170069 | 0012 | 1 | F | MBMS quality report clarifications | 14.1.0 | +| 2017-03 | SA#75 | SP-170069 | 0014 | 2 | D | Resolving editor's note on service continuity | 14.1.0 | +| 2017-03 | SA#75 | SP-170069 | 0015 | 2 | F | Clarification on Editor's notes in CFA | 14.1.0 | +| 2017-03 | SA#75 | SP-170069 | 0020 | 3 | F | Add location management entities and reference points in figure 7.3.1-3 | 14.1.0 | +| 2017-03 | SA#75 | SP-170069 | 0022 | 1 | F | Clarification that initial UE config and UE config are specific to one or more UEs | 14.1.0 | +| 2017-03 | SA#75 | SP-170069 | 0023 | 1 | F | Identities used in location information procedures | 14.1.0 | +| 2017-06 | SA#76 | SP-170390 | 0024 | 1 | F | Correction on Annex A Configuration data for MC services | 14.2.0 | +| 2017-06 | SA#76 | SP-170390 | 0033 | 1 | F | Addition of MC service to group configuration request | 14.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|----------------------------------------------------------------------------------------|--------| +| 2017-06 | SA#76 | SP-170390 | 0034 | | F | Miscellaneous corrections to configuration | 14.2.0 | +| 2017-06 | SA#76 | SP-170390 | 0035 | 2 | F | Corrections on determination of MBMS bearer quality | 14.2.0 | +| 2017-06 | SA#76 | SP-170390 | 0044 | 1 | F | Add note to bearer coordination procedure | 14.2.0 | +| 2017-06 | SA#76 | SP-170390 | 0050 | | F | Correction of information flow MBMS listening report | 14.2.0 | +| 2017-06 | SA#76 | SP-170390 | 0054 | 1 | F | Alignment of server address with stage 3 | 14.2.0 | +| 2017-06 | SA#76 | SP-170390 | 0055 | 2 | F | Inclusion of KMSUri to allow multiple security domains | 14.2.0 | +| 2017-06 | SA#76 | SP-170390 | 0063 | 1 | F | Corrections to Group configuration data for all MC services | 14.2.0 | +| 2017-06 | SA#76 | SP-170396 | 0026 | 4 | B | Introduction of MC server initiated group de-affiliation procedure | 15.0.0 | +| 2017-06 | SA#76 | SP-170396 | 0052 | 1 | B | Enhancement on group regrouping with an MC system | 15.0.0 | +| 2017-06 | SA#76 | SP-170396 | 0053 | 3 | B | MC server initiated group de-affiliation from group(s) in partner system | 15.0.0 | +| 2017-06 | SA#76 | SP-170396 | 0059 | 2 | B | Resource Management in CFA | 15.0.0 | +| 2017-06 | SA#76 | SP-170397 | 0025 | 2 | B | MBMS bearer event notification | 15.0.0 | +| 2017-06 | SA#76 | SP-170397 | 0043 | 4 | B | FEC for mission critical services | 15.0.0 | +| 2017-06 | SA#76 | SP-170397 | 0058 | 1 | B | Header compression for MC services over MBMS | 15.0.0 | +| 2017-09 | SA#77 | SP-170679 | 0070 | 1 | A | MC group configuration data correction | 15.1.0 | +| 2017-09 | SA#77 | SP-170684 | 0073 | 2 | B | Application plane functional model for interconnection | 15.1.0 | +| 2017-09 | SA#77 | SP-170684 | 0074 | 1 | B | Group configuration for interconnection | 15.1.0 | +| 2017-09 | SA#77 | SP-170684 | 0075 | 2 | B | User profile retrieval for migration | 15.1.0 | +| 2017-09 | SA#77 | SP-170683 | 0076 | 2 | B | Service type for group regroup | 15.1.0 | +| 2017-09 | SA#77 | SP-170684 | 0077 | 2 | C | Rules for temporary groups | 15.1.0 | +| 2018-01 | SA#78 | SP-170895 | 0066 | 9 | B | Retrieval of migration credentials for access to SIP core / IMS of a partner MC system | 15.2.0 | +| 2018-01 | SA#78 | SP-170897 | 0070 | 2 | A | MC group configuration data correction | 15.2.0 | +| 2018-01 | SA#78 | SP-170893 | 0071 | 4 | B | Priority between MC service servers | 15.2.0 | +| 2018-01 | SA#78 | SP-170894 | 0072 | 3 | C | Multi-server MBMS bearer coordination | 15.2.0 | +| 2018-01 | SA#78 | SP-170895 | 0079 | 1 | B | Architecture requirements for migration | 15.2.0 | +| 2018-01 | SA#78 | SP-170895 | 0080 | 4 | B | Signalling plane functional model for interconnection | 15.2.0 | +| 2018-01 | SA#78 | SP-170895 | 0081 | 1 | B | Architectural requirements for interconnection | 15.2.0 | +| 2018-01 | SA#78 | SP-170895 | 0082 | 4 | B | Addition of interconnection affiliation | 15.2.0 | +| 2018-01 | SA#78 | SP-170897 | 0086 | 3 | F | CR on clarification for MC service group ID | 15.2.0 | +| 2018-01 | SA#78 | SP-170894 | 0088 | 1 | F | CR on MBMS usage for group configuration | 15.2.0 | +| 2018-01 | SA#78 | SP-170893 | 0091 | 1 | B | Request for resources from MC service server | 15.2.0 | +| 2018-01 | SA#78 | SP-170893 | 0092 | 2 | B | Functional model update | 15.2.0 | +| 2018-01 | SA#78 | SP-170893 | 0093 | 1 | F | Location Server integration to PLMN | 15.2.0 | +| 2018-01 | SA#78 | SP-170896 | 0094 | 1 | B | Introduction of multi-talker control | 15.2.0 | +| 2018-01 | SA#78 | SP-170896 | 0095 | 4 | B | Introduction of Functional alias(es) | 15.2.0 | +| 2018-01 | SA#78 | SP-170887 | 0096 | | D | CR to replace uneditable figures | 15.2.0 | +| 2018-01 | SA#78 | SP-170897 | 0097 | 1 | F | Renaming of "emergency condition" | 15.2.0 | +| 2018-01 | SA#78 | SP-170895 | 0099 | 1 | B | Network selection for EPC-level roaming to support migration | 15.2.0 | +| 2018-01 | SA#78 | SP-170896 | 0105 | 2 | C | Take over procedure for Functional alias(es) | 15.2.0 | +| 2018-01 | SA#78 | SP-170896 | 0106 | 2 | B | Functional alias controlling role of MC service server | 15.2.0 | +| 2018-01 | SA#78 | SP-170893 | 0107 | 1 | F | GMS selection during group regroup | 15.2.0 | +| 2018-01 | SA#78 | SP-170893 | 0108 | 1 | F | Correction of "Group creation confirmation response" | 15.2.0 | +| 2018-01 | SA#78 | SP-170895 | 0110 | 1 | B | Information flows for interconnection group configuration | 15.2.0 | +| 2018-01 | SA#78 | SP-170895 | 0111 | 1 | B | Interconnection call procedures | 15.2.0 | +| 2018-01 | SA#78 | SP-170895 | 0112 | 2 | B | Interconnection configuration enforcement | 15.2.0 | +| 2018-01 | SA#78 | SP-170895 | 0113 | 1 | B | Interconnection media replication | 15.2.0 | +| 2018-01 | SA#78 | SP-170895 | 0114 | 1 | B | Serving server and system definition | 15.2.0 | +| 2018-01 | SA#78 | SP-170897 | 0115 | 2 | F | Renaming of "MCService emergency state cancel" | 15.2.0 | +| 2018-01 | SA#78 | SP-170893 | 0117 | 2 | F | Addition to group configuration data | 15.2.0 | +| 2018-01 | SA#78 | SP-170894 | 0118 | | F | Removal of Editor's note in the procedures for MBMS usage | 15.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-----------------------------------------------------------------|--------| +| 2018-01 | SA#78 | SP-170887 | 0120 | 1 | A | Add group deletion functionality | 15.2.0 | +| 2018-01 | SA#78 | SP-170893 | 0122 | 2 | B | Provision of group dynamic data | 15.2.0 | +| 2018-01 | SA#78 | SP-170895 | 0123 | | B | Definitions of interconnection, migration and MC gateway server | 15.2.0 | +| 2018-04 | SA#79 | SP-180154 | 0125 | 4 | B | Signalling plane registration for MC UE migration | 15.3.0 | +| 2018-04 | SA#79 | SP-180153 | 0127 | 2 | C | Multi-server MBMS bearer coordination | 15.3.0 | +| 2018-04 | SA#79 | SP-180145 | 0129 | 1 | A | Correction of security specification references | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0130 | | F | Correction of interconnection configuration enforcement figure | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0131 | 1 | B | Interconnection subscription to group configuration | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0131 | 6 | B | User authorization for interconnection and migration | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0133 | 2 | B | Group configuration for interconnection | 15.3.0 | +| 2018-04 | SA#79 | SP-180145 | 0135 | 1 | A | Aligning 10.9.3.1 procedure with diagram | 15.3.0 | +| 2018-04 | SA#79 | SP-180149 | 0137 | 1 | A | Update of references to stage 1 specifications | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0138 | 2 | B | Description of MC system identity | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0139 | 2 | B | Functional model update for interconnection | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0140 | 1 | B | Removal of editor's notes related to interconnection | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0141 | 1 | B | Service configuration for migration | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0142 | 1 | B | Update to connectivity for interconnection | 15.3.0 | +| 2018-06 | SA#80 | SP-180371 | 0143 | 4 | F | Correction of MC service system | 15.4.0 | +| 2018-06 | SA#80 | SP-180364 | 0145 | 2 | A | Clarification on MBMS bearer announcement | 15.4.0 | +| 2018-06 | SA#80 | SP-180368 | 0146 | | F | Functional model corrections | 15.4.0 | +| 2018-06 | SA#80 | SP-180368 | 0149 | 1 | F | Handling of group configuration and group state over MBMS | 15.4.0 | + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|---------------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 10 | +| 1 Scope..... | 11 | +| 2 References..... | 11 | +| 3 Definitions, symbols and abbreviations..... | 12 | +| 3.1 Definitions..... | 12 | +| 3.2 Symbols..... | 13 | +| 3.3 Abbreviations ..... | 13 | +| 4 Introduction..... | 15 | +| 5 Architectural requirements..... | 15 | +| 5.1 Media routing requirements ..... | 15 | +| 5.2 Requirements for user identity management..... | 15 | +| 5.3 MCPTT group affiliation and MCPTT group de-affiliation ..... | 15 | +| 5.4 MCPTT call requirements..... | 16 | +| 5.4.1 General ..... | 16 | +| 5.4.2 Group call requirements ..... | 16 | +| 5.5 GCS AS requirements for the MCPTT service..... | 16 | +| 5.6 Group selection ..... | 16 | +| 5.7 Bearer management..... | 16 | +| 5.7.1 General ..... | 16 | +| 5.7.2 EPS bearer considerations ..... | 16 | +| 5.7.2.1 Void ..... | 16 | +| 5.7.2.2 Void ..... | 16 | +| 5.7.3 EPS unicast bearer considerations for MCPTT ..... | 16 | +| 5.7.4 MBMS bearer management..... | 17 | +| 5.8 MCPTT system interconnect requirements..... | 17 | +| 6 Involved business relationships ..... | 17 | +| 7 Functional model..... | 17 | +| 7.1 General ..... | 17 | +| 7.2 Description of the planes..... | 17 | +| 7.3 Functional model description..... | 18 | +| 7.3.1 On-network functional model..... | 18 | +| 7.3.2 Off-network functional model..... | 19 | +| 7.4 Functional entities description ..... | 20 | +| 7.4.1 General ..... | 20 | +| 7.4.2 Application plane of MCPTT service..... | 20 | +| 7.4.2.1 General..... | 20 | +| 7.4.2.2 Common services core..... | 20 | +| 7.4.2.3 MCPTT application service ..... | 20 | +| 7.4.2.3.1 MCPTT client..... | 20 | +| 7.4.2.3.2 MCPTT server..... | 20 | +| 7.4.2.3.3 Floor participant ..... | 22 | +| 7.4.2.3.4 Floor control server ..... | 22 | +| 7.4.2.3.5 Media distribution function..... | 22 | +| 7.4.2.3.6 Media mixer ..... | 22 | +| 7.4.2.3.7 MCPTT user database..... | 23 | +| 7.4.2.3.8 MC gateway server..... | 23 | +| 7.4.3 Signalling control plane..... | 23 | +| 7.5 Reference points..... | 23 | +| 7.5.1 General reference point principle ..... | 23 | +| 7.5.2 Application plane of MCPTT service..... | 23 | +| 7.5.2.1 General..... | 23 | +| 7.5.2.2 Reference point MCPTT-1 (between the MCPTT client and the MCPTT server)..... | 23 | +| 7.5.2.3 Reference point MCPTT-2 (between the MCPTT server and the MCPTT user database) ..... | 24 | +| 7.5.2.4 Reference point MCPTT-3 (between the MCPTT server and the MCPTT server and between the MCPTT server and the MC gateway server)..... | 24 | + +| | | | +|-------------|---------------------------------------------------------------------------------------------------------------------|----| +| 7.5.2.5 | Reference point MCPTT-4 (unicast between the floor control server and the floor participant)..... | 24 | +| 7.5.2.6 | Reference point MCPTT-5 (between the media distribution function and the EPS) ..... | 24 | +| 7.5.2.7 | Reference point MCPTT-6 (between the MCPTT server and the EPS)..... | 24 | +| 7.5.2.8 | Reference point MCPTT-7 (unicast between the media distribution function and the media mixer)..... | 25 | +| 7.5.2.9 | Reference point MCPTT-8 (multicast between the media distribution function and the media mixer)..... | 25 | +| 7.5.2.10 | Reference point MCPTT-9 (multicast between the floor control server and the floor participant) ..... | 25 | +| 7.5.2.11 | Reference point IWF-1 (between the MCPTT server and the interworking function to legacy systems) ..... | 25 | +| 7.5.2.12 | Reference points of common services core used in the MCPTT service ..... | 25 | +| 7.5.2.13 | Reference point MCPTT-10 (between the MC gateway server and the MC gateway server in a different MCPTT system)..... | 25 | +| 8 | Identities..... | 25 | +| 9 | Application of functional model to deployments..... | 25 | +| 10 | Procedures and information flows ..... | 26 | +| 10.1 | MCPTT service configuration..... | 26 | +| 10.2 | User authentication and authorization for MCPTT service ..... | 26 | +| 10.3 | Affiliation and de-affiliation to/from MCPTT group(s) ..... | 27 | +| 10.3a | Activation and de-activation of/from functional alias(es)..... | 27 | +| 10.4 | MCPTT group selection..... | 27 | +| 10.4.1 | General ..... | 27 | +| 10.4.2 | Information flows for group selection..... | 27 | +| 10.4.2.1 | Group selection change request..... | 27 | +| 10.4.2.2 | Group selection change response..... | 27 | +| 10.4.2.3 | Group selection change notification ..... | 28 | +| 10.4.3 | Authorized user remotely changes another MCPTT user's selected MCPTT group – mandatory mode.... | 28 | +| 10.5 | Pre-established session (on-network)..... | 29 | +| 10.5.1 | General ..... | 29 | +| 10.5.2 | Information flows for pre-established session..... | 29 | +| 10.5.2.1 | Pre-established session establishment ..... | 29 | +| 10.5.2.2 | Pre-established session modification..... | 30 | +| 10.5.2.3 | Pre-established session release - client initiated..... | 30 | +| 10.5.2.4 | Pre-established session release - server initiated..... | 31 | +| 10.5.2.5 | Pre-established session call connect request..... | 31 | +| 10.5.2.6 | Pre-established session call disconnect request ..... | 31 | +| 10.5.3 | Procedures ..... | 32 | +| 10.5.3.1 | General..... | 32 | +| 10.5.3.2 | Call connect and disconnect procedures using pre-established session ..... | 32 | +| 10.5.3.2.1 | Call connect over unicast ..... | 32 | +| 10.5.3.2.2 | Call disconnect over unicast..... | 33 | +| 10.6 | Group call..... | 33 | +| 10.6.1 | General ..... | 33 | +| 10.6.2 | On-network group call..... | 33 | +| 10.6.2.1 | General..... | 33 | +| 10.6.2.2 | Information flows for group call in on-network ..... | 33 | +| 10.6.2.2.1 | MCPTT emergency group call request ..... | 33 | +| 10.6.2.2.1a | MCPTT emergency group call response..... | 34 | +| 10.6.2.2.2 | MCPTT in-progress emergency group state cancel request..... | 34 | +| 10.6.2.2.2a | MCPTT in-progress emergency group state cancel response ..... | 34 | +| 10.6.2.2.3 | MCPTT emergency alert request ..... | 35 | +| 10.6.2.2.3a | MCPTT emergency alert response..... | 35 | +| 10.6.2.2.3b | MCPTT emergency alert area trigger..... | 36 | +| 10.6.2.2.4 | MCPTT emergency alert cancel request..... | 36 | +| 10.6.2.2.4a | MCPTT emergency alert cancel response..... | 36 | +| 10.6.2.2.5 | MCPTT imminent peril group call request ..... | 36 | +| 10.6.2.2.5a | MCPTT imminent peril group call response..... | 37 | +| 10.6.2.2.6 | MCPTT in-progress imminent peril group state cancel request ..... | 37 | +| 10.6.2.2.6a | MCPTT in-progress imminent peril group state cancel response..... | 37 | +| 10.6.2.2.7 | Group call request (MCPTT client – MCPTT server) ..... | 38 | + +| | | | +|--------------|--------------------------------------------------------------------------------------------------------------------------|----| +| 10.6.2.2.8 | Group call request (MCPTT server – MCPTT server) ..... | 38 | +| 10.6.2.2.9 | Group call request (MCPTT server – MCPTT client) ..... | 39 | +| 10.6.2.2.10 | Group call response (MCPTT server – MCPTT client)..... | 39 | +| 10.6.2.2.11 | Group call response (MCPTT server – MCPTT server)..... | 40 | +| 10.6.2.2.12 | Group call response (MCPTT client – MCPTT server)..... | 40 | +| 10.6.2.2.13 | Group call notify (MCPTT server – MCPTT client) ..... | 40 | +| 10.6.2.2.14 | Group call release request (MCPTT server – MCPTT client) ..... | 40 | +| 10.6.2.2.14a | Group call release request (MCPTT client – MCPTT server) ..... | 41 | +| 10.6.2.2.15 | Group call release request (MCPTT server – MCPTT server) ..... | 41 | +| 10.6.2.2.16 | Group call release response (MCPTT client – MCPTT server)..... | 41 | +| 10.6.2.2.17 | Group call release response (MCPTT server – MCPTT server)..... | 42 | +| 10.6.2.2.18 | Group call rejoin request (MCPTT client – MCPTT server)..... | 42 | +| 10.6.2.2.19 | Group call rejoin response (MCPTT server – MCPTT client)..... | 42 | +| 10.6.2.2.20 | Group join request..... | 43 | +| 10.6.2.2.21 | Group join response ..... | 43 | +| 10.6.2.2.22 | Group call leave request (MCPTT server – MCPTT client)..... | 44 | +| 10.6.2.2.23 | Group call leave response (MCPTT client – MCPTT server) ..... | 44 | +| 10.6.2.2.24 | Group interrogate request (MCPTT server – MCPTT server)..... | 44 | +| 10.6.2.2.25 | Group interrogate response (MCPTT server – MCPTT server) ..... | 45 | +| 10.6.2.2.26 | Group-broadcast group call request (MCPTT client – MCPTT server) ..... | 45 | +| 10.6.2.2.27 | Group-broadcast group call request (MCPTT server – MCPTT client) ..... | 45 | +| 10.6.2.2.28 | Group-broadcast group call response (MCPTT client – MCPTT server)..... | 46 | +| 10.6.2.2.29 | Group-broadcast group call response (MCPTT server – MCPTT client)..... | 46 | +| 10.6.2.2.30 | Group-broadcast group call release request (MCPTT client – MCPTT server) ..... | 46 | +| 10.6.2.2.31 | Group-broadcast group call release request (MCPTT server – MCPTT client) ..... | 47 | +| 10.6.2.2.32 | Group-broadcast group call release response (MCPTT server – MCPTT client)..... | 47 | +| 10.6.2.2.33 | Group-broadcast group call release response (MCPTT client – MCPTT server)..... | 47 | +| 10.6.2.3 | Group call within one MCPTT system..... | 48 | +| 10.6.2.3.1 | Group call models ..... | 48 | +| 10.6.2.3.1.1 | Pre-arranged group call ..... | 48 | +| 10.6.2.3.1.2 | Chat group call ..... | 52 | +| 10.6.2.3.2 | Exiting group call due to de-affiliation ..... | 57 | +| 10.6.2.4 | Group call involving groups from multiple MCPTT systems ..... | 58 | +| 10.6.2.4.1 | Group call for temporary groups across multiple MCPTT systems..... | 58 | +| 10.6.2.4.1.1 | Group call setup..... | 58 | +| 10.6.2.4.1.2 | Group call release ..... | 60 | +| 10.6.2.4.2 | Group call for temporary group formed by group regroup procedure involving multiple MCPTT systems via trusted mode ..... | 62 | +| 10.6.2.4.3 | Group call for an MCPTT group defined in the partner MCPTT system..... | 63 | +| 10.6.2.4.3.1 | Pre-arranged group call setup procedure – initiating side ..... | 63 | +| 10.6.2.4.3.2 | Pre-arranged group call setup – terminating side ..... | 64 | +| 10.6.2.4.3.3 | Chat group call setup..... | 65 | +| 10.6.2.4.4 | Merging of groups involving multiple MCPTT systems ..... | 66 | +| 10.6.2.5 | Broadcast group call ..... | 67 | +| 10.6.2.5.1 | General ..... | 67 | +| 10.6.2.5.2 | Common broadcast group call procedure..... | 68 | +| 10.6.2.5.2.1 | Group-broadcast group call procedure ..... | 68 | +| 10.6.2.5.2.2 | Group-broadcast group call procedure when a subordinate group has an on-going MCPTT emergency group call ..... | 70 | +| 10.6.2.5.2.3 | Group-broadcast group call release procedure ..... | 71 | +| 10.6.2.5.2.4 | Server-initiated broadcast group call release procedure..... | 72 | +| 10.6.2.5.3 | Temporary group – broadcast group call procedure ..... | 73 | +| 10.6.2.6 | Emergency and imminent peril procedures ..... | 75 | +| 10.6.2.6.1 | MCPTT emergency group call..... | 75 | +| 10.6.2.6.1.1 | MCPTT emergency group call commencement..... | 75 | +| 10.6.2.6.1.2 | MCPTT group call upgraded to an MCPTT emergency group call..... | 77 | +| 10.6.2.6.1.3 | MCPTT in-progress emergency group state cancel ..... | 79 | +| 10.6.2.6.2 | MCPTT imminent peril group call..... | 81 | +| 10.6.2.6.2.1 | MCPTT imminent peril group call commencement..... | 81 | +| 10.6.2.6.2.2 | Imminent peril group call upgrade ..... | 83 | +| 10.6.2.6.2.3 | MCPTT in-progress imminent peril group state cancel ..... | 84 | +| 10.6.2.6.3 | MCPTT emergency alert..... | 86 | + +| | | | +|--------------|------------------------------------------------------------------------------------------------------|-----| +| 10.6.2.6.3.1 | MCPTT emergency alert initiation..... | 86 | +| 10.6.2.6.3.2 | MCPTT emergency alert cancel..... | 88 | +| 10.6.2.6.3.3 | Entering MCPTT emergency alert area..... | 89 | +| 10.6.2.7 | Location of current talker ..... | 90 | +| 10.6.2.8 | Temporary group call – user regroup ..... | 91 | +| 10.6.2.8.1 | General ..... | 91 | +| 10.6.2.8.2 | Group call setup ..... | 91 | +| 10.6.2.8.3 | Group call end (by authorized user)..... | 93 | +| 10.6.3 | Off-network group call ..... | 94 | +| 10.6.3.1 | General..... | 94 | +| 10.6.3.2 | Information flows for group call in off-network ..... | 94 | +| 10.6.3.2.1 | Group call announcement..... | 94 | +| 10.6.3.2.2 | MCPTT upgrade to emergency call ..... | 94 | +| 10.6.3.2.3 | MCPTT emergency group state cancel ..... | 95 | +| 10.6.3.2.4 | Response..... | 95 | +| 10.6.3.2.5 | MCPTT emergency alert announcement..... | 95 | +| 10.6.3.2.6 | MCPTT emergency alert cancel announcement ..... | 95 | +| 10.6.3.2.7 | MCPTT upgrade to imminent peril call ..... | 96 | +| 10.6.3.2.8 | MCPTT imminent peril group call cancel..... | 96 | +| 10.6.3.3 | Group call setup ..... | 96 | +| 10.6.3.4 | Passive join to group call..... | 97 | +| 10.6.3.5 | Join to ongoing group call when new entry member initiates the call with on-going group call id..... | 98 | +| 10.6.3.6 | Immediate group call announcement to join an ongoing group call..... | 99 | +| 10.6.3.7 | Group call release due to inactivity ..... | 100 | +| 10.6.3.8 | Broadcast group call ..... | 101 | +| 10.6.3.9 | Emergency and imminent peril procedures ..... | 101 | +| 10.6.3.9.1 | Emergency group call..... | 101 | +| 10.6.3.9.2 | MCPTT imminent peril..... | 102 | +| 10.6.3.9.3 | MCPTT emergency alert..... | 102 | +| 10.6.3.9.3.1 | MCPTT emergency alert initiation..... | 102 | +| 10.6.3.9.3.2 | MCPTT emergency alert cancel ..... | 104 | +| 10.7 | Private call..... | 105 | +| 10.7.1 | General ..... | 105 | +| 10.7.2 | Private call in on-network ..... | 105 | +| 10.7.2.1 | Information flows for private call in on-network ..... | 105 | +| 10.7.2.1.1 | MCPTT private call request (MCPTT client to MCPTT server)..... | 105 | +| 10.7.2.1.2 | MCPTT private call request (MCPTT server to MCPTT server)..... | 105 | +| 10.7.2.1.2a | MCPTT private call request (MCPTT server to MCPTT client)..... | 106 | +| 10.7.2.1.3 | MCPTT private call response (MCPTT client to MCPTT server)..... | 106 | +| 10.7.2.1.4 | MCPTT private call response..... | 107 | +| 10.7.2.1.4a | MCPTT private call end request ..... | 107 | +| 10.7.2.1.4b | MCPTT private call end response..... | 107 | +| 10.7.2.1.5 | MCPTT emergency private call request (MCPTT client to MCPTT server) ..... | 107 | +| 10.7.2.1.5a | MCPTT emergency private call request (MCPTT server to MCPTT client) ..... | 108 | +| 10.7.2.1.6 | MCPTT progress indication..... | 108 | +| 10.7.2.1.7 | MCPTT ringing..... | 109 | +| 10.7.2.2 | Private call within one MCPTT system..... | 109 | +| 10.7.2.2.1 | Private call setup in automatic commencement mode ..... | 109 | +| 10.7.2.2.2 | Private call setup in manual commencement mode ..... | 110 | +| 10.7.2.2.2.1 | Description ..... | 110 | +| 10.7.2.2.2.2 | Procedure..... | 110 | +| 10.7.2.2.3 | Private call release..... | 112 | +| 10.7.2.2.3.1 | Client initiated ..... | 112 | +| 10.7.2.2.3.2 | Server initiated..... | 113 | +| 10.7.2.3 | Private call within several MCPTT systems..... | 114 | +| 10.7.2.3.1 | Private call setup in automatic commencement mode – MCPTT users in multiple MCPTT systems ..... | 114 | +| 10.7.2.3.2 | Private call setup in manual commencement mode – MCPTT users in multiple MCPTT systems ..... | 116 | +| 10.7.2.3.3 | Private call release – MCPTT users in multiple MCPTT systems..... | 118 | +| 10.7.2.4 | MCPTT emergency private call..... | 118 | +| 10.7.2.4.1 | MCPTT emergency private call commencement..... | 118 | + +| | | | +|--------------|---------------------------------------------------------------------------------------------------------------------------|-----| +| 10.7.2.4.2 | MCPTT private call emergency upgrade ..... | 120 | +| 10.7.3 | Private call in off-network..... | 121 | +| 10.7.3.1 | Information flows for private call in off-network..... | 121 | +| 10.7.3.1.1 | Call setup request ..... | 121 | +| 10.7.3.1.2 | Call setup response..... | 121 | +| 10.7.3.1.3 | Call release request..... | 121 | +| 10.7.3.1.4 | Call release response ..... | 121 | +| 10.7.3.2 | Use of ProSe capability for private call ..... | 122 | +| 10.7.3.3 | Private call setup in automatic commencement mode..... | 122 | +| 10.7.3.4 | Private call setup in manual commencement mode..... | 123 | +| 10.7.3.5 | Private call release ..... | 124 | +| 10.7.3.6 | MCPTT emergency private call..... | 125 | +| 10.7.4 | MCPTT private call call-back request..... | 125 | +| 10.7.4.1 | Information flows for MCPTT private call call-back request ..... | 125 | +| 10.7.4.1.1 | MCPTT private call call-back request ..... | 125 | +| 10.7.4.1.2 | MCPTT private call call-back response ..... | 125 | +| 10.7.4.1.3 | MCPTT private call call-back cancel request ..... | 126 | +| 10.7.4.1.4 | MCPTT private call call-back cancel response..... | 126 | +| 10.7.4.2 | MCPTT private call call-back request within one MCPTT system..... | 126 | +| 10.7.4.3 | MCPTT private call call-back cancel request within one MCPTT system ..... | 127 | +| 10.7.4.4 | MCPTT private call call-back request fulfillment within one MCPTT system ..... | 128 | +| 10.8 | Simultaneous session for MCPTT calls (on-network)..... | 129 | +| 10.8.1 | General ..... | 129 | +| 10.9 | Floor control..... | 129 | +| 10.9.1 | Floor control for on-network MCPTT service ..... | 129 | +| 10.9.1.1 | General..... | 129 | +| 10.9.1.2 | Information flows for floor control for on-network..... | 130 | +| 10.9.1.2.1 | General ..... | 130 | +| 10.9.1.2.2 | Floor request..... | 130 | +| 10.9.1.2.3 | Floor granted ..... | 130 | +| 10.9.1.2.4 | Floor rejected..... | 130 | +| 10.9.1.2.5 | Floor request cancel ..... | 131 | +| 10.9.1.2.6 | Floor request cancel response ..... | 131 | +| 10.9.1.2.7 | Floor request cancel notify ..... | 131 | +| 10.9.1.2.8 | Floor idle ..... | 132 | +| 10.9.1.2.9 | Floor release ..... | 132 | +| 10.9.1.2.9a | Multi-talker floor release..... | 132 | +| 10.9.1.2.10 | Floor taken..... | 132 | +| 10.9.1.2.10a | Multi-talker floor taken ..... | 133 | +| 10.9.1.2.11 | Floor revoked ..... | 133 | +| 10.9.1.2.12 | Floor acknowledgement ..... | 133 | +| 10.9.1.2.13 | Queue position request..... | 134 | +| 10.9.1.2.14 | Queue position info ..... | 134 | +| 10.9.1.2.15 | Unicast media stop request ..... | 134 | +| 10.9.1.2.16 | Unicast media resume request ..... | 134 | +| 10.9.1.3 | Floor control within one MCPTT system..... | 135 | +| 10.9.1.3.1 | Floor request, floor granted and floor taken during an MCPTT session..... | 135 | +| 10.9.1.3.1a | Floor request, floor granted and multi-talker floor taken during an MCPTT session enhanced with multi-talker control..... | 137 | +| 10.9.1.3.2 | Floor override..... | 138 | +| 10.9.1.3.2.1 | Floor override using floor revoked (also floor rejected) during an MCPTT session ..... | 138 | +| 10.9.1.3.2.2 | Floor override without using floor revoked during an MCPTT session ..... | 140 | +| 10.9.1.3.2.3 | Floor override using floor revoked (also floor rejected) during an MCPTT session enhanced with multi-talker control..... | 141 | +| 10.9.1.3.2.4 | Floor release during an MCPTT session enhanced with multi-talker control..... | 143 | +| 10.9.1.3.3 | Queue position during an MCPTT session ..... | 144 | +| 10.9.1.3.4 | Floor request cancellation from the floor request queue..... | 145 | +| 10.9.1.3.4.1 | Floor request cancellation from the queue – MCPTT user initiated ..... | 145 | +| 10.9.1.3.4.2 | Floor request cancellation from the queue - floor control server initiated ..... | 146 | +| 10.9.1.4 | Floor control involving groups from multiple MCPTT systems ..... | 147 | +| 10.9.1.4.1 | Partner MCPTT system routes all floor control messages to primary MCPTT system's floor control server..... | 147 | + +| | | | +|-------------|----------------------------------------------------------------------------------------------------------------------|-----| +| 10.9.1.4.2 | Partner MCPTT system performs filtering of floor control messages entering and leaving the partner MCPTT system..... | 149 | +| 10.9.1.5 | Floor control for audio cut-in enabled group..... | 152 | +| 10.9.1.6 | Unicast media stop and resume requests ..... | 154 | +| 10.9.2 | Floor control for off-network MCPTT service..... | 156 | +| 10.9.2.1 | General ..... | 156 | +| 10.9.2.2 | Information flows for floor control for off-network..... | 157 | +| 10.9.2.2.1 | General ..... | 157 | +| 10.9.2.2.2 | Floor granted ..... | 157 | +| 10.9.2.3 | Floor control during silence ..... | 157 | +| 10.9.2.3.1 | Successful floor taken (No floor contention) ..... | 157 | +| 10.9.2.4 | Simultaneous floor requests..... | 158 | +| 10.9.2.5 | Floor request during speaking with queue..... | 159 | +| 10.9.2.6 | Floor request during speaking without queue..... | 160 | +| 10.9.2.7 | Override ..... | 161 | +| 10.9.2.8 | Floor queue status ..... | 162 | +| 10.10 | Use of MBMS transmission (on-network)..... | 163 | +| 10.10.1 | Information flows for MBMS Transmission..... | 163 | +| 10.10.1.1 | MapGroupToBearer..... | 163 | +| 10.10.1.2 | UnmapGroupFromBearer ..... | 164 | +| 10.10.1.3 | Application group paging ..... | 164 | +| 10.10.2 | Use of pre-established MBMS bearers..... | 164 | +| 10.10.3 | Use of dynamic MBMS bearer establishment..... | 164 | +| 10.10.4 | Call connect and disconnect over MBMS..... | 165 | +| 10.10.4.1 | General..... | 165 | +| 10.10.4.2 | Procedure ..... | 165 | +| 10.10.4.2.1 | Call connect over MBMS..... | 165 | +| 10.10.4.2.2 | Call disconnect over MBMS..... | 166 | +| 10.10.5 | Switching from MBMS bearer to unicast bearer..... | 167 | +| 10.10.6 | Enhanced MCPTT group call setup procedure with MBMS bearer ..... | 167 | +| 10.10.6.1 | Description..... | 167 | +| 10.10.6.2 | Procedure ..... | 168 | +| 10.11 | MCPTT resource management (on-network) ..... | 168 | +| 10.11.1 | General ..... | 168 | +| 10.11.2 | Request for unicast resources at session establishment..... | 169 | +| 10.11.3 | Request for modification of unicast resources ..... | 169 | +| 10.11.4 | Management of multicast media bearers..... | 169 | +| 10.11.5 | Request for resources with shared priority ..... | 169 | +| 10.11.5.1 | General..... | 169 | +| 10.11.5.2 | Procedure ..... | 169 | +| 10.12 | MCPTT media plane transmissions with partner MCPTT systems (on-network)..... | 169 | +| 10.13 | Location information (on-network)..... | 171 | +| 10.14 | Ambient listening call ..... | 171 | +| 10.14.1 | General ..... | 171 | +| 10.14.2 | Information flows for ambient listening call..... | 171 | +| 10.14.2.1 | Ambient listening call request ..... | 171 | +| 10.14.2.2 | Ambient listening call response..... | 172 | +| 10.14.2.3 | Ambient listening call release request ..... | 172 | +| 10.14.2.4 | Ambient listening call release response..... | 172 | +| 10.14.2.5 | Ambient listening call release notification ..... | 173 | +| 10.14.3 | Ambient listening call procedures..... | 173 | +| 10.14.3.1 | Remotely initiated ambient listening call setup..... | 173 | +| 10.14.3.2 | Locally initiated ambient listening call setup ..... | 174 | +| 10.14.3.3 | Ambient listening call release – server initiated..... | 175 | +| 10.14.3.4 | Remotely initiated ambient listening call release – "listening" user initiated ..... | 176 | +| 10.14.3.5 | Ambient listening call release – "listened to" user initiated ..... | 177 | +| 10.15 | First-to-answer call setup ..... | 178 | +| 10.15.1 | Description ..... | 178 | +| 10.15.2 | Information flows for first-to-answer call..... | 178 | +| 10.15.3 | Procedure ..... | 178 | +| 10.16 | Remotely initiated MCPTT call ..... | 180 | +| 10.16.1 | General ..... | 180 | + +10.16.2 Information flows for remotely initiated MCPTT call ..... 181 + +10.16.2.1 Remotely initiated MCPTT call request..... 181 + +10.16.2.2 Remotely initiated MCPTT call response ..... 181 + +10.16.3 Procedure ..... 181 + +10.16.3.1 Remotely initiated MCPTT call request ..... 181 + +10.17 Support for multiple devices ..... 183 + +10.17.1 General ..... 183 + +**Annex A (normative): MCPTT related configuration data ..... 184** + +A.1 General..... 184 + +A.2 MCPTT UE configuration data..... 185 + +A.3 MCPTT user profile configuration data..... 185 + +A.4 MCPTT related group configuration data..... 190 + +A.5 MCPTT service configuration data..... 193 + +**Annex B (informative): Local UE settings for MCPTT..... 197** + +B.1 Local UE settings for MCPTT ..... 197 + +Annex C (informative): Change history..... 198 + +--- + +## Foreword + +This Technical Specification has been produced by the 3<sup>rd</sup> 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. + +# 1 Scope + +This document specifies the functional architecture, procedures and information flows needed to support the mission critical push to talk (MCPTT) service. The MCPTT service utilizes the common functional architecture to support MC services over **LTE** including the common services core defined in 3GPP TS 23.280 [16]. Support for both MCPTT group calls and MCPTT private calls operating in on-network and off-network modes of operation is specified. + +The corresponding service requirements are defined in 3GPP TS 22.179 [2] and 3GPP TS 22.280 [17]. + +The present document is applicable primarily to MCPTT voice service using **E-UTRAN** access based on the **EPC** architecture defined in 3GPP **TS 23.401** [8]. Certain application functions of the MCPTT service such as dispatch and administrative functions could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access. + +The MCPTT service requires preferential handling compared to normal telecommunication services e.g. in support of police or fire brigade including the handling of prioritised MCPTT calls for emergency and imminent threats. + +The MCPTT service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways. + +In the present document, MCPTT calls between MCPTT users on different MCPTT systems are considered. + +# 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT)"; Stage 1. +- [3] 3GPP TS 23.002: "Network Architecture". +- [4] 3GPP TS 23.203: "Policy and charging control architecture". +- [5] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [6] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2". +- [7] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2". +- [8] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [9] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE\_LTE); Stage 2". +- [10] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE\_LTE); MB2 Reference Point; Stage 3". +- [11] Void +- [12] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". + +- [13] IETF RFC 5245 (April 2010): "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols". +- [14] void +- [15] void +- [16] 3GPP TS 23.280: "Common functional architecture to support mission critical services". +- [17] 3GPP TS 22.280: "Mission Critical Common Requirements (MCCoRe); Stage 1". +- [18] 3GPP TS 29.283: "Diameter data management applications". +- [19] 3GPP TS 33.180: "Security of the mission critical service". +- [20] 3GPP TS 23.283: "Mission Critical Communication Interworking with Land Mobile Radio Systems; Stage 2". + +--- + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Automatic commencement mode:** A mode in which the initiation of the private call does not require any action on the part of the receiving MCPTT user. + +**First-to-answer call:** A call that is started when the first MCPTT user among multiple potential target recipients' answers. This call requires the answering MCPTT user to answer manually; automatic answer is not allowed + +**Group call:** A mechanism by which an MCPTT user can make a one-to-many MCPTT transmission to other users that are members of MCPTT group(s). + +**Group home MCPTT system:** The MCPTT system where the MCPTT group is defined. + +**Group host MCPTT server:** The MCPTT server within an MCPTT system that provides centralised support for MCPTT services of an MCPTT group defined in a group home MCPTT system. + +**Manual commencement mode:** A mode in which the initiation of the private call requires the receiving MCPTT user to perform some action to accept or reject the call setup. + +**MCPTT client:** An instance of an MC service client that provides the client application function for the MCPTT service. + +**MCPTT group:** An MC service group configured for MCPTT service. + +**MCPTT group affiliation:** An MC service group affiliation for MCPTT. + +**MCPTT group de-affiliation:** An MC service group de-affiliation for MCPTT. + +**MCPTT ID:** An instance of an MC service ID within the MCPTT service. + +**MCPTT server:** An instance of an MC service server that provides the server application function for the MCPTT service. + +**On-network MCPTT service:** The collection of functions and capabilities required to provide MCPTT via EPS bearers using E-UTRAN to provide the last hop radio bearers. + +**Pre-selected MCPTT user profile:** An instance of the pre-selected MC service user profile for MCPTT. + +**UE-to-network relay MCPTT service:** The collection of functions and capabilities required to provide MCPTT via a ProSe UE-to-network relay using ProSe direct communication paths to provide the last hop radio bearer(s). + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.179 [2] apply: + +**Dispatcher** +**Floor control** +**MCPTT administrator** +**MCPTT service** +**MCPTT system** +**MCPTT UE** +**MCPTT user** +**MCPTT User Profile** +**Mission Critical Organization** +**Mission Critical Push To Talk** +**Off-network MCPTT service** +**Partner MCPTT system** +**Primary MCPTT system** +**Private call** +**Multi-talker control** + +For the purposes of the present document, the following terms and definitions given in IETF RFC 5245 [13] apply: + +**Candidate** +**Candidate pair** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.280 [16] apply: + +**Active MC service user profile** +**MC service client** +**MC service group** +**MC service group affiliation** +**MC service group de-affiliation** +**MC service ID** +**MC service server** +**Pre-selected MC service user profile** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.280 [17] apply: + +**Functional alias** + +## 3.2 Symbols + +For the purposes of the present document, the following symbols given in 3GPP TS 22.179 [2] apply: + +**B1** +**B2** +**N2** +**N3** +**N4** +**N5** +**N6** +**N7** +**N10** +**N11** + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|--------------|---------------------------------------------| +| <b>APN</b> | Access Point Name | +| <b>ARP</b> | Allocation and Retention Priority | +| <b>BM-SC</b> | Broadcast Multicast Service Centre | +| <b>CHAP</b> | Challenge-Handshake Authentication Protocol | + +| | | +|----------------|-----------------------------------------------------------------| +| CSCF | Call Server Control Function | +| DL | Downlink | +| DPF | Direct Provisioning Function | +| E-UTRAN | Evolved Universal Terrestrial Radio Access Network | +| E2EE | End to End Encryption | +| ECGI | E-UTRAN Cell Global Identifier | +| EPC | Evolved Packet Core | +| EPS | Evolved Packet System | +| GBR | Guaranteed Bit Rate | +| GCS AS | Group Communication Service Application Server | +| GCSE_LTE | Group Communication Service Enabler over LTE | +| GRUU | Globally Routable User agent URI | +| HLR | Home Location Register | +| HSS | Home Subscriber Server | +| HTTP | Hyper Text Transfer Protocol | +| I-CSCF | Interrogating CSCF | +| ICE | Interactive Connectivity Establishment | +| IM CN | IP Multimedia Core Network | +| IMPI | IP Multimedia Private Identity | +| IMPU | IP Multimedia PUblic identity | +| IMS | IP Multimedia Subsystem | +| ITSI | Individual TETRA Subscriber Identity | +| LMR | Land Mobile Radio | +| MBMS | Multimedia Broadcast and Multicast Service | +| MBFSN | Multimedia Broadcast multicast service Single Frequency Network | +| MC | Mission Critical | +| MC ID | Mission Critical user identity | +| MCPTT | Mission Critical Push To Talk | +| MCPTT AS | MCPTT Application Server | +| MCPTT group ID | MCPTT group identity | +| MCPTT ID | MCPTT user identity | +| NAT | Network Address Translation | +| PAP | Password Authentication Protocol | +| P-CSCF | Proxy CSCF | +| PCC | Policy and Charging Control | +| PCRF | Policy and Charging Rules Function | +| PLMN | Public Land Mobile Network | +| ProSe | Proximity-based Services | +| PSI | Public Service Identity | +| PTT | Push To Talk | +| QCI | QoS Class Identifier | +| QoS | Quality of Service | +| RAN | Radio Access Network | +| RF | Radio Frequency | +| RSI | Radio Set Identity | +| S-CSCF | Serving CSCF | +| SAI | Service Area Identifier | +| SDF | Service Data Flow | +| SIP | Session Initiated Protocol | +| SSL | Secure Sockets Layer | +| TLS | Transport Layer Security | +| TMGI | Temporary Mobile Group Identity | +| UM | Unacknowledged Mode | +| URI | Uniform Resource Identifier | +| USB | Universal Serial Bus | +| WLAN | Wireless Local Area Network | + +## 4 Introduction + +The MCPTT service supports communication between several users (i.e. group call), where each user has the ability to gain access to the permission to talk in an arbitrated manner. The MCPTT service also supports private calls between two users. + +The MCPTT architecture utilises the common functional architecture to support mission critical services over **LTE** defined in 3GPP TS 23.280 [16] and aspects of the IMS architecture defined in 3GPP TS 23.228 [5], the Proximity-based Services (**ProSe**) architecture defined in 3GPP TS 23.303 [7], the Group Communication System Enablers for **LTE (GCSE\_LTE)** architecture defined in 3GPP TS 23.468 [9] and the PS-PS access transfer procedures defined in 3GPP TS 23.237 [6] to enable support of the MCPTT service. + +The MCPTT UE primarily obtains access to the MCPTT service via **E-UTRAN**, using the **EPS** architecture defined in 3GPP TS 23.401 [8]. Certain application functions of MCPTT service such as dispatch and administrative functions can be supported using either MCPTT UEs in **E-UTRAN** or using MCPTT UEs via non-3GPP access networks. + +NOTE: Dispatch consoles and devices used by MCPTT service administrators are considered MCPTT UEs in the MCPTT architecture. + +MCPTT UEs that use non-3GPP access can only support a subset of the functionality specified in this specification that is supported by the non-3GPP access network. + +The MCPTT system provides the function to support interworking with LMR systems defined in 3GPP TS 23.283 [20]. + +## 5 Architectural requirements + +### 5.1 Media routing requirements + +The voice media flow for a private call shall be routed according to one of the following two options: + +- a) Option 1: + - 1) Through the primary MCPTT system if both users in the call belong to the same organisation; or + - 2) Through the primary MCPTT system of both users, if the users in the call do not belong to the same organisation. +- b) Option 2: The voice media flow may be routed locally, under the control of the primary MCPTT system, through an entity allowing the duplication of the media flow to the primary MCPTT system of each user. + +The voice media flow for a group call shall be routed to the group home MCPTT system. + +The routing of media flow shall be end-to-end from transmitter to receiver(s), except for the MCPTT control function. + +### 5.2 Requirements for user identity management + +To allow for confidentiality of user identities in various cases of business relationship as defined in clause 6, the MCPTT application may provide public user identities to the MCPTT UE, to be used by MCPTT UE for MCPTT services. + +### 5.3 MCPTT group affiliation and MCPTT group de-affiliation + +MCPTT group affiliation shall be as specified in clause 5.2.5 of 3GPP TS 23.280 [16]. In addition, the following requirements shall be fulfilled by the MCPTT service for MCPTT users affiliated to MCPTT groups: + +- MCPTT users receive notifications for MCPTT group call setup and invitations for their affiliated MCPTT group(s). +- MCPTT users receive media and events from their affiliated MCPTT group(s). + +## 5.4 MCPTT call requirements + +### 5.4.1 General + +The on-network MCPTT service shall support the use of pre-established sessions. + +### 5.4.2 Group call requirements + +The MCPTT service shall support the chat group (restricted) call model for MCPTT group call. + +The MCPTT service shall support the pre-arranged group call model for MCPTT group call. + +## 5.5 GCS AS requirements for the MCPTT service + +The GCS AS architecture requirements for MC services are specified in 3GPP TS 23.280 [16]. + +## 5.6 Group selection + +The following functionalities shall be supported by the MCPTT service. + +- a. The MCPTT user shall select an affiliated group to initiate a new group call or transmit media in an existing group call. +- b. An authorized MCPTT user (e.g., dispatcher) may remotely force or request to change other on-network MCPTT users' selected MCPTT group to a particular affiliated group. + +## 5.7 Bearer management + +### 5.7.1 General + +The MCPTT UE shall use the **APN**s as defined in subclause 5.2.7.0 of 3GPP TS 23.280 [16]. + +### 5.7.2 **EPS** bearer considerations + +The **EPS** bearer considerations specified in subclause 5.2.7.2 of 3GPP TS 23.280 [16] shall apply. + +5.7.2.1 Void + +5.7.2.2 Void + +### 5.7.3 **EPS** unicast bearer considerations for MCPTT + +For an MCPTT call session request, resources shall be requested utilising interaction with dynamic PCC. The MCPTT system shall request resources over Rx to a PCRF. The dedicated bearer for voice and MCPTT-4 reference point messaging shall utilise the **QCI** value of 65 (as specified in 3GPP **TS 23.203** [4]). The request of resources over Rx shall include an application identifier for MCPTT in order for the PCRF to evaluate the correct **QCI**. + +The UE is required to support at minimum one UM bearer which is used for MCPTT voice (see annex A in 3GPP **TS 36.331** [12]). + +Depending on operator policy: + +- the MCPTT system may be able to request modification of the priority (ARP) of an existing bearer without the need to initiate a new dedicated GBR bearer; or +- the **EPS** bearers for MCPTT call may enable pre-emption of lower priority **EPS** bearers if the maximum number of UM bearers has been reached in favour of MCPTT initiated **EPS** bearer, if the **EPS** bearer used for MCPTT call has higher priority level (ARP) than the UM bearer(s) used for other application(s) and if the bearers for non MCPTT application are pre-emptable. In this case, the **EPS** bearer for MCPTT call pre-empts one of the existing **EPS** bearers when the maximum number of bearers is established for other applications. + +NOTE 1: Operator policy takes into account regional/national requirements. + +The **EPS** bearer for MCPTT emergency call shall have highest priority level among MCPTT call types. The **EPS** bearer for MCPTT imminent peril call shall have higher priority level than one for MCPTT call. + +To ensure that the MCPTT service always has access to a dedicated bearer for MCPTT media, a pre-established session may be setup that includes a request for resources at the first MCPTT group affiliation. + +This means that the PCC may multiplex MCPTT media streams from multiple concurrent MCPTT calls into one **EPS** bearer on one shared network priority regardless of MCPTT call priority. + +NOTE 2: A single UM bearer is used to multiplex the media streams from multiple concurrent MCPTT calls. + +NOTE 3: The sharing of a single GBR bearer for voice means that different **QCI** and/or ARP values are not possible for different voice media streams. + +NOTE 4: Multi-talker control may require additional bearer resources if multiple audio streams are sent to the UE when the floor is granted to additional participants during an established MCPTT group session. + +#### 5.7.4 **MBMS** bearer management + +The **MBMS** bearer management for MC services is specified in subclause 5.2.7.1 of 3GPP TS 23.280 [16]. + +### 5.8 MCPTT system interconnect requirements + +The architecture for interconnect between MCPTT systems is specified, allowing the affiliation of MCPTT users from an MCPTT system with MCPTT groups defined in another MCPTT system. When both MCPTT systems are served by different networks, interconnect of signalling and media is achieved using the interfaces defined for interconnect between PLMNs. + +--- + +## 6 Involved business relationships + +The description of the involved business relationships for the MCPTT service is contained in clause 6 of 3GPP TS 23.280 [16]. + +--- + +## 7 Functional model + +### 7.1 General + +The functional model for the support of MCPTT is defined as a series of planes to allow for the breakdown of the architectural description. + +### 7.2 Description of the planes + +The description of the planes and the relationship between the planes are contained in the common functional architecture to support MC services in 3GPP TS 23.280 [16]. + +### 7.3 Functional model description + +#### 7.3.1 On-network functional model + +Figure 7.3.1-1 shows the functional model for the application plane of the MCPTT service. + +![Functional model for application plane of the MCPTT service diagram](4356776ca004ecba5d599667a155d7d4_img.jpg) + +The diagram illustrates the functional model for the application plane of the MCPTT service. It features a central MCPTT server connected to various external systems and a User Equipment (UE). + +- External Systems:** + - Other MCPTT server:** Connected to the MCPTT server via reference point MCPTT-3. + - MCPTT user database:** Connected to the MCPTT server via reference point MCPTT-2. + - Interworking function to legacy system:** Connected to the MCPTT server via reference point IWF-1. + - MC gateway server:** Connected to the MCPTT server via reference point MCPTT-3. This server is part of an **Other MCPTT system** (indicated by a dashed box) and is also connected via reference point MCPTT-10. +- MCPTT Server:** Contains two internal functional blocks: + - Media distribution function:** Connected to the EPS via reference points MCPTT-5, MCPTT-6 (labeled MB2C), MCPTT-7, and MCPTT-8. + - Floor control server:** Connected to the EPS via reference points MCPTT-1, MCPTT-4, and MCPTT-9. +- MCPTT UE:** Contains an **MCPTT client** block with: + - Media mixer:** Receives media from the EPS via reference point Rx and interacts with the media distribution function via MCPTT-7 and MCPTT-8. + - Floor participant:** Interacts with the floor control server via the EPS through reference points MCPTT-1, MCPTT-4, and MCPTT-9. +- EPS (Evolved Packet System):** Acts as a central communication hub, connecting the MCPTT server and the MCPTT UE. It is highlighted with a yellow label. + +Functional model for application plane of the MCPTT service diagram + +**Figure 7.3.1-1: Functional model for application plane of the MCPTT service** + +In the model shown in figure 7.3.1-1, the following apply: + +- The MCPTT server is an instantiation of a MC service server in accordance with 3GPP TS 23.280 [16]. +- The MCPTT server is an instantiation of a GCS AS in accordance with 3GPP TS 23.468 [9]. +- MCPTT-9 carries multicast floor control signalling between the floor control server of the MCPTT server and the floor participant of the MCPTT UE. +- MCPTT-4 carries unicast floor control signalling between the floor control server of the MCPTT server and the floor participant of the MCPTT UE. +- MCPTT-7 carries unicast media between the media distribution function of the MCPTT server and the media mixer of the MCPTT UE. +- MCPTT-8 carries multicast media from the media distribution function of the MCPTT server to the media mixer of the MCPTT UE. + +Figure 7.3.1-2 shows the relationships between the reference points of the application plane and the signalling plane. + +![Diagram showing relationships between reference points of MCPTT application and signalling control planes. It includes MCPTT servers, SIP cores, an MCPTT client, and an 'Other MCPTT system' connected via various SIP and HTTP interfaces.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +The diagram illustrates the network architecture for MCPTT. At the top, two MCPTT servers are connected to a SIP core. The first server uses SIP-2 and MCPTT-3 interfaces. The second server uses SIP-2 and SIP-2 interfaces. This SIP core is connected to another SIP core below it via MCPTT-3 and SIP-3 interfaces, with HTTP-1 and HTTP-2 also indicated. The second SIP core connects to an MCPTT Client via MCPTT-1 and SIP-1. To the left of the second SIP core, another MCPTT server connects via SIP-2, SIP-2, and MCPTT-3. Below that, an MC gateway server connects via SIP-2 and SIP-2. At the bottom, a third SIP core is part of an 'Other MCPTT system' and connects to the second SIP core via MCPTT-10 and SIP-3. This third SIP core is connected to an MC gateway server via SIP-2. + +Diagram showing relationships between reference points of MCPTT application and signalling control planes. It includes MCPTT servers, SIP cores, an MCPTT client, and an 'Other MCPTT system' connected via various SIP and HTTP interfaces. + +Figure 7.3.1-2: Relationships between reference points of MCPTT application and signalling control planes + +### 7.3.2 Off-network functional model + +Figure 7.3.2-1 shows the functional model for off-network operation of MCPTT service. + +![Functional model for off-network operation of MCPTT service diagram showing two User Equipment (UE) blocks, UE1 and UE2, connected by Media (green line) and Signalling (red line) paths. Each UE contains an Application plane and a Signalling control plane. The Application plane includes Media mixer, Floor control server, Floor participant, MCPTT client, Configuration management client, and Group management client. The Signalling control plane includes a Signalling user agent client.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +The diagram illustrates the functional model for off-network operation of MCPTT service across two User Equipment (UE) blocks, UE1 and UE2. Each UE is composed of two main planes: the Application plane and the Signalling control plane. The Application plane within each UE contains six functional entities: Media mixer, Floor control server, Floor participant, MCPTT client, Configuration management client, and Group management client. The Signalling control plane contains a Signalling user agent client. A green horizontal line represents the Media path, and a red horizontal line represents the Signalling path, connecting the corresponding entities between UE1 and UE2. A legend at the bottom indicates that the green line represents Media and the red line represents Signalling. + +Functional model for off-network operation of MCPTT service diagram showing two User Equipment (UE) blocks, UE1 and UE2, connected by Media (green line) and Signalling (red line) paths. Each UE contains an Application plane and a Signalling control plane. The Application plane includes Media mixer, Floor control server, Floor participant, MCPTT client, Configuration management client, and Group management client. The Signalling control plane includes a Signalling user agent client. + +Figure 7.3.2-1: Functional model for off-network operation of MCPTT service + +## 7.4 Functional entities description + +### 7.4.1 General + +Each subclause is a description of a functional entity and does not imply a physical entity. + +### 7.4.2 Application plane of MCPTT service + +#### 7.4.2.1 General + +Entities within the application plane of MCPTT service provide application control, media control and distribution functions. + +#### 7.4.2.2 Common services core + +The description of the common services core entities are contained in common functional architecture to support MC services in 3GPP TS 23.280 [16]. + +#### 7.4.2.3 MCPTT application service + +##### 7.4.2.3.1 MCPTT client + +The MCPTT client functional entity acts as the user agent for all MCPTT application transactions. The client reports the information of where the client is currently located. + +##### 7.4.2.3.2 MCPTT server + +The MCPTT server functional entity provides centralised support for MCPTT services. + +All the MCPTT clients supporting users belonging to a single group are required to use the same MCPTT server for that group. An MCPTT client supporting a user involved in multiple groups can have relationships with multiple MCPTT servers. + +NOTE 1: Possible requirements for handling multiple distinct media on different MCPTT servers are not covered in this version of the document. + +The MCPTT server functional entity represents a specific instantiation of the GCS AS described in 3GPP **TS 23.468** [9] to control multicast and unicast operations for group communications. + +The MCPTT server functional entity is supported by the SIP AS, HTTP client and HTTP server functional entities of the signalling control plane. + +By assuming the role of a GCS AS, the MCPTT server functional entity is responsible for: + +- requesting the allocation of multicast resources utilizing the media distribution function; +- announcing the association of multicast resources to calls to MCPTT UEs; +- determining for each MCPTT UE involved in a given call whether to use unicast or multicast transport; +- announcing the assignment of multicast transport for specific calls to MCPTT UEs; and +- informing the media distribution function of the media streams requiring support for a given call. + +The MCPTT server shall support the controlling role and the participating role. The MCPTT server may perform the controlling role for private calls and group calls. The MCPTT server performing the controlling role for a private call or group call may also perform a participating role for the same private call or group call. For each private call and group call, there shall be only one MCPTT server assuming the controlling role, while one or more MCPTT servers in participating role may be involved. + +The MCPTT server performing the controlling roles is responsible for: + +- call control (e.g. policy enforcement for participation in the MCPTT group calls) towards all the MCPTT users of the group call and private call; +- interfacing with the group management server for group policy and affiliation status information of this MCPTT server's served affiliated users; +- interfacing with the functional alias management server for functional alias policy;- functional alias activation and deactivation support for MCPTT user; +- managing floor control entity in a group call and private call; and +- managing media handling entity in call i.e. conferencing, transcoding. + +The controlling roles for group call, private call and functional alias are independent with each other. + +The MCPTT server performing the participating roles is responsible for: + +- call control (e.g. authorization for participation in the MCPTT group calls) to its MCPTT users for group call and private call; +- group affiliation support for MCPTT user, including enforcement of maximum N2 number of simultaneous group affiliations by a user; +- functional alias activation and deactivation support for MCPTT user; +- relaying the call control and floor control messages between the MCPTT client and the MCPTT server performing the controlling role; and +- media handling in call for its MCPTT users, i.e. transcoding, recording, lawful interception for both unicast and multicast media. + +NOTE 2: The MCPTT server in the controlling role and the MCPTT server in the participating role can belong to the same MCPTT system or to different MCPTT systems. + +For group regrouping involving multiple groups from primary and partner MCPTT systems, + +- the group host MCPTT server of the temporary group performs the controlling role and is responsible for the centralized floor control, and for arbitration according to the temporary group or user policies (e.g., priority); + +- the group host MCPTT server of the constituent MCPTT group is responsible for providing call invitations to their group members, and for filtering between constituent group members' floor control requests according to the constituent group or user policies (e.g., priority); and +- the MCPTT server responsible for the constituent MCPTT group members performs the participating role. + +#### 7.4.2.3.3 Floor participant + +The floor participant functional entity is responsible for floor requests. This functional entity is located in the UE for both on-network and off-network operations. + +#### 7.4.2.3.4 Floor control server + +This functional entity provides support for centralised floor control for on-network and distributed floor control for off-network operation. It may provide arbitration between floor control requests between different users, grant the floor in response to successful requests, and provide queuing in cases of contention. For on-network operation, this functional entity is located with the MCPTT server. For off-network operation, this functional entity is located in the UE. + +#### 7.4.2.3.5 Media distribution function + +The media distribution function is responsible for the distribution of media to call participants. By means of information provided by the MCPTT server (e.g. IP addresses, transport layer ports), it will provide the following functionality: + +- provide for the reception of uplink MCPTT UE media transmission by means of the MCPTT-7 reference point; +- replicate the media as needed for distribution to those participants using unicast transport; +- distribute downlink media to MCPTT UEs by IP unicast transmission to those participants utilizing unicast transport by means of the MCPTT-7 reference point; +- distribute downlink media to MCPTT UEs using multicast downlink transport of media for the call by means of the MCPTT-8 reference point; and +- provide a media mixing function where multiple media streams are combined (e.g. multi-talker control) into a single media stream for transmission to the MCPTT UE. + +NOTE 1: If media mixing function occurs within the media distribution function, it operates independently of the media mixer in the UE. + +NOTE 2: A media mixing function within the media distribution function is not possible where the media is end to end encrypted. + +Group configuration data determines whether audio mixing for multi-talker control is applied by the media mixing function in the MCPTT server. + +NOTE 3: If media mixing in the network is utilized, care should be taken to minimize the feedback of the user's own voice from the mixed audio in order to avoid echoes. + +#### 7.4.2.3.6 Media mixer + +This functional entity exists on the UE and provides support for combining multiple media streams (e.g. multi-talker control) into one media stream through the enforcement of media policy information. Group configuration data determines whether audio mixing for multi-talker control is applied by the media mixing function in the UE. + +#### 7.4.2.3.7 MCPTT user database + +This functional entity contains information of the MCPTT user profile associated with an MCPTT ID that is held by the MCPTT service provider at the application plane. The MCPTT user profile is determined by the mission critical organization, the MCPTT service provider, and potentially the MCPTT user. + +#### 7.4.2.3.8 MC gateway server + +The MC gateway server provides support for MCPTT interconnection services with a partner MCPTT system in a different trust domain whilst providing topology hiding. It acts as a proxy for one or more MCPTT servers in the partner MCPTT system without needing to expose the MCPTT servers in the primary MCPTT system outside the trusted + +domain of the primary MCPTT system. It may be a role of the MCPTT server described in subclause 7.4.2.3.2 of the present document. + +The MC gateway server is responsible for relaying call control and floor control signalling messages, and media between MCPTT servers within the MCPTT system and the interconnected MCPTT system. + +**Editor's note:** It is FFS whether the gateway MC server can act as a signalling proxy as defined in 3GPP TS 33.180 [25]. + +## 7.4.3 Signalling control plane + +The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [16]. + +# 7.5 Reference points + +## 7.5.1 General reference point principle + +The protocols on any reference point that is exposed for MCPTT service interoperability with other SIP core or other IMS entities in other systems shall be compatible with the protocols defined for the corresponding reference point defined in 3GPP TS 23.002 [3]. + +## 7.5.2 Application plane of MCPTT service + +### 7.5.2.1 General + +The reference points for the application plane of MCPTT service are described in the following subclauses. + +### 7.5.2.2 Reference point MCPTT-1 (between the MCPTT client and the MCPTT server) + +The MCPTT-1 reference point, which exists between the MCPTT client and the MCPTT server, is used for MCPTT application signalling for establishing a session in support of MCPTT. The MCPTT-1 reference point shall use the SIP-1 and SIP-2 reference points for transport and routing of SIP signalling. The MCPTT-1 reference point may use the HTTP-1 and HTTP-2 reference points. + +The **TMGI** is communicated between the MCPTT server and the MCPTT client using the MCPTT-1 reference point. + +Information that is reported to the MCPTT server from the MCPTT client shall be configurable at the application layer. This interface may include the area where a UE is currently located, described as **ECGI** of the serving and neighbouring cell(s), **MBMS SAI**s, MBFSN Area ID. This information comes from the broadcast by the local cell, e.g. from SIB1 and SIB15 (see 3GPP TS 36.331 [12]) as decoded by the UE. + +**NOTE:** This reference point includes the **GC1** reference point as described in 3GPP TS 23.468 [9]. It is assumed that the MCPTT server is performing the function of GCS AS. While 3GPP TS 23.468 [9] does not specify **GC1** it does include high level descriptions of certain interactions on **GC1**, including those relating to the availability of multicast delivery for the application client. The MCPTT-1 reference point fulfils the requirements of the **GC1** reference point for MCPTT. + +Messages supported on this interface may also include the MCPTT server providing the MCPTT client with information describing the mapping of transport resources to specific group calls. + +### 7.5.2.3 Reference point MCPTT-2 (between the MCPTT server and the MCPTT user database) + +The MCPTT-2 reference point, which exists between the MCPTT server and the MCPTT user database, is used by the MCPTT server to obtain information about a specific user. The MCPTT-2 reference point utilises a diameter management application protocol as defined in 3GPP TS 29.283 [18] and shall be intra-network. + +#### 7.5.2.4 Reference point MCPTT-3 (between the MCPTT server and the MCPTT server and between the MCPTT server and the MC gateway server) + +The MCPTT-3 reference point exists between the MCPTT server and the MCPTT server and between the MCPTT server and the MC gateway server for MCPTT application signalling for establishing MCPTT sessions. The MCPTT-3 reference point shall use the SIP-2 reference point for transport and routing of signalling. If a pair of MCPTT servers, or an MCPTT server and an MC gateway server, are served by different SIP cores then the MCPTT-3 reference point shall also use the SIP-3 reference point for transport and routing of signalling. Floor control signalling and media are also transferred using the MCPTT-3 reference point. + +#### 7.5.2.5 Reference point MCPTT-4 (unicast between the floor control server and the floor participant) + +The MCPTT-4 reference point, which exists between the floor control server in the MCPTT server and the floor participant in the MCPTT client, provides floor control signalling between the floor control server in the MCPTT server and the floor participant over a unicast bearer. The MCPTT-4 reference point uses the SGi reference point defined in 3GPP TS 23.002 [3]. + +#### 7.5.2.6 Reference point MCPTT-5 (between the media distribution function and the EPS) + +The MCPTT-5 reference point, which exists between the media distribution function and the EPS, is used, subject to the conditions below, by the media distribution function of the MCPTT server to obtain unicast bearers with appropriate QoS from the EPS. It utilises the Rx interface of the EPS according to 3GPP TS 23.203 [4]. + +MCPTT-5 is not used when the MCPTT service provider and the PLMN operator do not have an operational agreement for QoS control to be provided directly from the MCPTT service provider domain. + +MCPTT-5 may be used when the MCPTT service provider and the PLMN operator have an operational agreement where QoS control is provided directly from the MCPTT service provider domain. + +NOTE: Any coordination between the P-CSCF use of Rx and the MCPTT server use of Rx (via MCPTT-5) from the MCPTT service provider domain is not specified in this release of this specification. + +#### 7.5.2.7 Reference point MCPTT-6 (between the MCPTT server and the EPS) + +The MCPTT-6 reference point, which exists between the MCPTT server and the EPS, is used to request the allocation and activation of multicast transport resources for MCPTT application usage. The MCPTT-6 reference point uses the MB2-C interface as defined in 3GPP TS 29.468 [10]. + +#### 7.5.2.8 Reference point MCPTT-7 (unicast between the media distribution function and the media mixer) + +The MCPTT-7 reference point, which exists between the media distribution function and the media mixer, is used to exchange unicast media between the media distribution function of the MCPTT server and the media mixer of the MCPTT client. The MCPTT-7 reference point uses the SGi reference point defined in 3GPP TS 23.002 [3]. + +#### 7.5.2.9 Reference point MCPTT-8 (multicast between the media distribution function and the media mixer) + +The MCPTT-8 reference point, which exists between the media distribution function and the media mixer, is used by the media distribution function of the MCPTT server to send multicast media to the media mixer of the MCPTT client. The MCPTT-8 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [9]. + +#### 7.5.2.10 Reference point MCPTT-9 (multicast between the floor control server and the floor participant) + +The MCPTT-9 reference point, which exists between the floor control server and the floor participant, provides floor control signalling between the floor control server and the floor participant over a multicast bearer. The MCPTT-9 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [9]. + +#### 7.5.2.11 Reference point IWF-1 (between the MCPTT server and the interworking function to legacy systems) + +The IWF-1 reference point is specified in 3GPP TS 23.283 [20]. + +#### 7.5.2.12 Reference points of common services core used in the MCPTT service + +The descriptions for reference points of the common services core are contained in the common functional architecture to support MC services specified in 3GPP TS 23.280 [16]. + +#### 7.5.2.13 Reference point MCPTT-10 (between the MC gateway server and the MC gateway server in a different MCPTT system) + +The MCPTT-10 reference point, which exists between the MC gateway server and the MC gateway server in an interconnected MCPTT system for MCPTT application signalling for establishing MCPTT sessions, shall use the SIP-3 reference point for transport and routing of signalling. Floor control signalling and media are also transferred using the MCPTT-10 reference point between interconnected MCPTT systems. + +--- + +## 8 Identities + +The MCPTT service specific identities (e.g. MCPTT ID, MCPTT group ID) are described in clause 8 of 3GPP TS 23.280 [16]. + +--- + +## 9 Application of functional model to deployments + +The application of the functional model to deployments, and description of various deployment scenarios for the MCPTT service, can be found in clause 9 of 3GPP TS 23.280 [16]. + +--- + +## 10 Procedures and information flows + +### 10.1 MCPTT service configuration + +The MCPTT service shall support the procedures and related information flows as specified in subclause 10.1 of 3GPP TS 23.280 [16] with the following clarifications: + +- The MC service client is the MCPTT client; +- The MC service server is the MCPTT server; +- The MC service ID is the MCPTT ID; and +- The MC service user profile index is the MCPTT user profile index. + +### 10.2 User authentication and authorization for MCPTT service + +NOTE: Flow 10.2-1 is a high level user authentication and authorization flow. 3GPP TS 33.180 [19] defines the specific user authentication and authorization architecture required by the MCPTT service in order to realize the MCPTT user authentication and authorization requirements as defined in 3GPP TS 22.179 [2]. + +A procedure for user authentication is illustrated in figure 10.2-1. The user authentication is performed based on the procedure specified in 3GPP TS 23.280[16]. + +![Sequence diagram for MCPTT user authentication and registration in a single domain. The diagram shows six lifelines: MCPTT client, Identity management client, Signalling user agent, SIP core, Identity management server, and MCPTT server. Step 1, 'User Authentication is based on the procedure – “General user authentication and authorization for MC services” specified in 3GPP TS 23.280[18].', is shown as a horizontal bar spanning the Identity management client, Signalling user agent, SIP core, and Identity management server lifelines. Step 2, 'The MCPTT client performs the service authorization with the MCPTT server.', is shown as a horizontal bar spanning the MCPTT client and MCPTT server lifelines.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +Sequence diagram for MCPTT user authentication and registration in a single domain. The diagram shows six lifelines: MCPTT client, Identity management client, Signalling user agent, SIP core, Identity management server, and MCPTT server. Step 1, 'User Authentication is based on the procedure – “General user authentication and authorization for MC services” specified in 3GPP TS 23.280[18].', is shown as a horizontal bar spanning the Identity management client, Signalling user agent, SIP core, and Identity management server lifelines. Step 2, 'The MCPTT client performs the service authorization with the MCPTT server.', is shown as a horizontal bar spanning the MCPTT client and MCPTT server lifelines. + +**Figure 10.2-1: MCPTT user authentication and registration, single domain** + +1. The user authentication is performed as per the general user authentication procedure specified in 3GPP TS 23.280[16]. +2. MCPTT client performs the MCPTT service authorization for the user. Step 2 utilizes the results of step 1. + +## 10.3 Affiliation and de-affiliation to/from MCPTT group(s) + +The MCPTT service shall support the procedures and related information flows as specified in subclause 10.8 of 3GPP TS 23.280 [16] with the following clarifications: + +- The MC service client is the MCPTT client; +- The MC service server is the MCPTT server; +- The MC service group is the MCPTT group; +- The MC service ID is the MCPTT ID; and +- The MC service group ID is the MCPTT group ID. + +When an MCPTT user has affiliated to an MCPTT group then the MCPTT user can send and receive MCPTT related media for that MCPTT group. When an MCPTT user has de-affiliated from an MCPTT group then the MCPTT user cannot send and receive MCPTT related media to and from that MCPTT group. + +### 10.3a Activation and de-activation of/from functional alias(es) + +The MCPTT service shall support the procedures and related information flows as specified in subclause 10.13.4 and subclause 10.13.5 of 3GPP TS 23.280 [16]. + +- The MC service client is the MCPTT client; +- The MC service server is the MCPTT server; +- The MC service ID is the MCPTT ID. + +## 10.4 MCPTT group selection + +### 10.4.1 General + +When an MCPTT user wants to transmit on a MCPTT group, an affiliated MCPTT group shall be set as the selected MCPTT group to the MCPTT user. Only one MCPTT group can be set as the selected MCPTT group to an MCPTT user from one particular MCPTT UE at any given time. This sub-clause describes the detailed procedures for the MCPTT group selection. + +### 10.4.2 Information flows for group selection + +#### 10.4.2.1 Group selection change request + +Table 10.4.2.1-1 describes the information flow group selection change request from the MCPTT client to the MCPTT server. + +**Table 10.4.2.1-1: Group selection change request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| MCPTT ID | M | MCPTT user identity whose group selection information is to be changed | +| MCPTT group ID | M | MCPTT group identity for which the selection is made for the MCPTT ID | + +#### 10.4.2.2 Group selection change response + +Table 10.4.2.2-1 describes the information flow group selection change response from the MCPTT server to the MCPTT client. + +**Table 10.4.2.2-1: Group selection change response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| Result | M | Result indicates success or failure of group selection change | + +#### 10.4.2.3 Group selection change notification + +Table 10.4.2.3-1 describes the information flow group selection change notification from the MCPTT server to the MCPTT client. + +**Table 10.4.2.3-1: Group selection change notification** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| MCPTT ID | M | MCPTT user identity whose group selection information is to be changed | +| MCPTT group ID | M | MCPTT group identity for which the selection is made for the MCPTT ID | + +## 10.4.3 Authorized user remotely changes another MCPTT user's selected MCPTT group – mandatory mode + +Procedure for an authorized user to change other MCPTT users' selected MCPTT group without requiring target user's approval is described in figure 10.4.3-1. + +Pre-conditions: + +- The MCPTT client 1 has already been provisioned (statically or dynamically) with the target MCPTT user's information and its group information, that the selected MCPTT group of target MCPTT user 2 is allowed to be changed; + +![Sequence diagram for Remotely change MCPTT group selection – mandatory mode. The diagram shows three lifelines: MCPTT client 1 (authorized user 1), MCPTT server, and MCPTT client 2 (target user 2). The sequence of messages is: 1. Group selection change request from client 1 to server; 2. Authorization check based on subscription and affiliation relationship check based on the stored affiliation status (internal server process); 3. Remotely affiliate to the requested MCPTT group using procedure from subclause 10.3.5 (internal server process); 4. Group selection change notification from server to client 2; 5. Group selection change response from server to client 1; 6. Notify target user the change of the selected MCPTT group (internal client 2 process).](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 (authorized user 1) + participant MCPTT server + participant MCPTT client 2 (target user 2) + Note right of MCPTT server: 2. Authorization check based on subscription and affiliation relationship check based on the stored affiliation status + Note right of MCPTT server: 3. Remotely affiliate to the requested MCPTT group using procedure from subclause 10.3.5 + Note right of MCPTT client 2: 6. Notify target user the change of the selected MCPTT group + MCPTT client 1->>MCPTT server: 1. Group selection change request + MCPTT server->>MCPTT client 2: 4. Group selection change notification + MCPTT server->>MCPTT client 1: 5. Group selection change response + +``` + +Sequence diagram for Remotely change MCPTT group selection – mandatory mode. The diagram shows three lifelines: MCPTT client 1 (authorized user 1), MCPTT server, and MCPTT client 2 (target user 2). The sequence of messages is: 1. Group selection change request from client 1 to server; 2. Authorization check based on subscription and affiliation relationship check based on the stored affiliation status (internal server process); 3. Remotely affiliate to the requested MCPTT group using procedure from subclause 10.3.5 (internal server process); 4. Group selection change notification from server to client 2; 5. Group selection change response from server to client 1; 6. Notify target user the change of the selected MCPTT group (internal client 2 process). + +**Figure 10.4.3-1: Remotely change MCPTT group selection – mandatory mode** + +1. When an authorized user changes other MCPTT users' selected MCPTT group, the MCPTT client 1 sends MCPTT group selection change request to the MCPTT server. The information (i.e. target MCPTT ID(s), MCPTT group ID(s)) used to set the requested MCPTT group as the selected MCPTT group of the target MCPTT user shall be included. +2. The MCPTT server shall check if the MCPTT user 1 is authorized to change the target MCPTT user's selected MCPTT group. The MCPTT server shall perform the affiliation relationship check based on the stored affiliation status. +3. If the MCPTT user 1 is authorized to change the target MCPTT user's selected MCPTT group, and if the target MCPTT user is not already affiliated to the requested MCPTT group, the remotely change of affiliation procedures in shall be performed (see subclause 10.8 in 3GPP TS 23.280 [16]). +4. The MCPTT server then shall send the MCPTT group selection change notification including the target user ID and the selected MCPTT group ID to the MCPTT client 2. +5. The group selection change response then returns to the MCPTT client 1. +6. Target MCPTT client 2 are notified about the change of its selected MCPTT group. + +## 10.5 Pre-established session (on-network) + +### 10.5.1 General + +The MCPTT server may use one or more pre-established sessions as defined in 3GPP TS 23.280 [16] for the following procedures for on-network: + +- Group calls (as specified in subclause 10.6.2.3 and subclause 10.6.2.4); +- Private calls (as specified in subclause 10.7.2.2 and subclause 10.7.2.3); +- MCPTT emergency group calls (as specified in subclause 10.6.2.6.1); +- MCPTT imminent peril group calls (as specified in subclause 10.6.2.6.2); +- MCPTT emergency private calls (as specified in subclause 10.7.2.4); and + +- MCPTT emergency alerts (as specified in subclause 10.6.2.6.3). + +For outgoing MCPTT call setup for a private call or a pre-arranged group call using a pre-established session, an MCPTT UE uses SIP procedures to establish the call. + +For incoming MCPTT call setup for a pre-arranged group call using a pre-established session, an MCPTT UE is notified of the start of the MCPTT call using floor control messages. + +For incoming MCPTT call setup for a private call using a pre-established session, an MCPTT UE is notified of the start of the MCPTT call control using SIP procedures in manual commencement mode and using floor control procedures in automatic commencement mode. + +An MCPTT UE can join an MCPTT chat group using a pre-established session by sending a group join request using SIP procedures. + +NOTE: A chat group call is started and notified using floor control messages regardless of whether pre-established session is used. + +## 10.5.2 Information flows for pre-established session + +### 10.5.2.1 Pre-established session establishment + +Table 10.5.2.1-1 describes the information flow create pre-established session request from the MCPTT client to the MCPTT server, for the procedure defined in 3GPP TS 23.280 [16]. + +**Table 10.5.2.1-1: Create pre-established session request** + +| Information element | Status | Description | +|------------------------------------|--------|-----------------------------------------------------------------------------------------| +| MCPTT ID of requester (originator) | M | This element identifies the MCPTT user that wishes to create a pre-established session. | +| SDP offer | M | SDP with media information offered by client (e.g. ports, codec, protocol id). | + +Table 10.5.2.1-2 describes the information flow create pre-established session response from the MCPTT server to the MCPTT client, for the procedure defined in 3GPP TS 23.280 [16]. + +**Table 10.5.2.1-2: Create pre-established session response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------| +| SDP Answer | M | SDP with media information offered by server (e.g. ports, codec, protocol id) | +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | + +### 10.5.2.2 Pre-established session modification + +Table 10.5.2.2-1 describes the information flow modify pre-established session request from the MCPTT client to the MCPTT server, for the procedure defined in 3GPP TS 23.280 [16]. + +**Table 10.5.2.2-1: Modify pre-established session request** + +| Information element | Status | Description | +|------------------------------------|--------|-----------------------------------------------------------------------------------------| +| MCPTT ID of requester (originator) | M | This element identifies the MCPTT user that wishes to create a pre-established session. | +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | +| SDP offer | M | SDP with media information offered by client (e.g. ports, codec, protocol id). | + +Table 10.5.2.2-2 describes the information flow modify pre-established session response from the MCPTT server to the MCPTT client, for the procedure defined in 3GPP TS 23.280 [16]. + +**Table 10.5.2.2-2: Modify pre-established session response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------| +| SDP Answer | M | SDP with media information offered by server (e.g. ports, codec, protocol id). | +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | + +### 10.5.2.3 Pre-established session release - client initiated + +Table 10.5.2.3-1 describes the information flow release pre-established session request from the MCPTT client to the MCPTT server, for the procedure defined in 3GPP TS 23.280 [16]. + +**Table 10.5.2.3-1: Release pre-established session request - client initiated** + +| Information element | Status | Description | +|------------------------------------|--------|------------------------------------------------------------------------------------------| +| MCPTT ID of requester (originator) | M | This element identifies the MCPTT user that wishes to release a pre-established session. | +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | +| Release reason | M | This element indicates that reason for the session release. | + +Table 10.5.2.3-2 describes the information flow release pre-established session response from the MCPTT server to the MCPTT client, for the procedure defined in 3GPP TS 23.280 [16]. + +**Table 10.5.2.3-2: Release pre-established session response - client initiated** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------| +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | + +### 10.5.2.4 Pre-established session release - server initiated + +Table 10.5.2.4-1 describes the information flow release pre-established session request from the MCPTT server to the MCPTT client, for the procedure defined in 3GPP TS 23.280 [16]. + +**Table 10.5.2.4-1: Release pre-established session release request - server initiated** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------| +| MCPTT ID of target | M | This element identifies the MCPTT user that is the target of the for pre-established session release. | +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | +| Release reason | M | This element indicates the reason for the session release. | + +Table 10.5.2.4-2 describes the information flow release pre-established session response from the MCPTT client to the MCPTT server, for the procedure defined in 3GPP TS 23.280 [16]. + +**Table 10.5.2.4-2: Release pre-established session response - server initiated** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------| +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | + +### 10.5.2.5 Pre-established session call connect request + +Table 10.5.2.5-1 describes the information flow pre-established session call connect request from the MCPTT server to the MCPTT client, for the procedure defined in subclause 10.5.3.2.1 of the present document. + +**Table 10.5.2.5-1: Pre-established session call connect request** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------------| +| MCPTT group ID | O | Identity of the MCPTT group (NOTE) | +| MCPTT ID | O | MCPTT ID of the private call MCPTT user (NOTE) | +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | +| NOTE: Depending on type of connection either MCPTT group ID or MCPTT ID shall be present | | | + +## 10.5.2.6 Pre-established session call disconnect request + +Table 10.5.2.1.6-1 describes the information flow pre-established session call disconnect request from the MCPTT server to the MCPTT client, for the procedure defined in subclause 10.5.3.2.2 of the present document. + +**Table 10.5.2.6-1: Pre-established session call disconnect request** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------------| +| MCPTT group ID | O | Identity of the MCPTT group (NOTE) | +| MCPTT ID | O | MCPTT ID of the private call MCPTT user (NOTE) | +| Session ID | M | This element identifies the specific session ID used for pre-established sessions. | +| NOTE: Depending on type of connection either MCPTT group ID or MCPTT ID shall be present | | | + +## 10.5.3 Procedures + +### 10.5.3.1 General + +The MCPTT server and MCPTT client make use of the procedures defined in the following subclauses of the present document and the following procedures in 3GPP TS 23.280 [16]: + +- pre-established session establishment; +- pre-established session modification; and +- pre-established session release. + +### 10.5.3.2 Call connect and disconnect procedures using pre-established session + +#### 10.5.3.2.1 Call connect over unicast + +Call connect and disconnect information flows are sent over non-SIP media plane signalling using MCPTT-4 for including or releasing an MCPTT client in the call using a pre-established session. + +Figure 10.5.3.2.1-1 shows the high level procedure where a call connect information flow is sent by the MCPTT server to inform MCPTT client(s) using a pre-established session that the MCPTT client(s) has/have been connected to an MCPTT private call or group call. + +![Sequence diagram for the connect procedure. The diagram is titled 'Home MCPTT service provider' and shows four lifelines: MCPTT client A, Floor participant A, MCPTT server, and Floor control server. Step 1: A horizontal bar labeled '1. Pre-established session' spans between MCPTT client A and MCPTT server. Step 2: A box labeled '2. Include MCPTT client 1 in call' is shown on the MCPTT server lifeline. Step 3: An arrow labeled '3. Pre-established session call connect request' points from the MCPTT server to the Floor participant A lifeline.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +Sequence diagram for the connect procedure. The diagram is titled 'Home MCPTT service provider' and shows four lifelines: MCPTT client A, Floor participant A, MCPTT server, and Floor control server. Step 1: A horizontal bar labeled '1. Pre-established session' spans between MCPTT client A and MCPTT server. Step 2: A box labeled '2. Include MCPTT client 1 in call' is shown on the MCPTT server lifeline. Step 3: An arrow labeled '3. Pre-established session call connect request' points from the MCPTT server to the Floor participant A lifeline. + +**Figure 10.5.3.2.1-1: Connect procedure** + +1. Pre-established session exists between MCPTT client A and MCPTT server. +2. MCPTT server has determined to include MCPTT client A in the call e.g., upon receiving the request from another MCPTT client to include MCPTT client A in the call. +3. Pre-established session call connect request information flow is sent by the MCPTT server to inform MCPTT client A using a pre-established session that it has been connected to MCPTT private or group call. The floor control is established between floor participant A and floor control server. + +#### 10.5.3.2.2 Call disconnect over unicast + +Figure 10.5.3.2.2-1 shows the high level procedure where a disconnect information flow is sent by the MCPTT server to the MCPTT client A to indicate that the MCPTT private call or group call using a pre-established session has been released. + +![Sequence diagram for the disconnect procedure. The diagram is titled 'Home MCPTT service provider' and shows the same four lifelines as the previous diagram. Step 1: A horizontal bar labeled '1. Ongoing call in pre-established session with floor control' spans between MCPTT client A and MCPTT server. Step 2: A box labeled '2. Call release' is shown on the MCPTT server lifeline. Step 3: An arrow labeled '3. Pre-established session call disconnect request' points from the MCPTT server to the Floor participant A lifeline.](f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg) + +Sequence diagram for the disconnect procedure. The diagram is titled 'Home MCPTT service provider' and shows the same four lifelines as the previous diagram. Step 1: A horizontal bar labeled '1. Ongoing call in pre-established session with floor control' spans between MCPTT client A and MCPTT server. Step 2: A box labeled '2. Call release' is shown on the MCPTT server lifeline. Step 3: An arrow labeled '3. Pre-established session call disconnect request' points from the MCPTT server to the Floor participant A lifeline. + +**Figure 10.5.3.2.2-1: Disconnect procedure** + +1. Floor control is ongoing within a private or group call established using pre-established session. +2. MCPTT server has determined to release MCPTT client A from the call e.g., due to call release. +3. Pre-established session call disconnect request message is sent by the MCPTT server to indicate to MCPTT client A that the MCPTT private call or group call using a pre-established session has been released. Pre-established session between MCPTT client A and MCPTT server remains for further use. + +## 10.6 Group call + +### 10.6.1 General + +Group calls are enabled in both on-network and off-network. + +### 10.6.2 On-network group call + +#### 10.6.2.1 General + +This subclause contains procedures for group call across a single and multiple MCPTT servers, and associated functions such as emergency call, broadcast call and others. + +Two variations of group call model are described in subclause 10.6.2.3, the pre-arranged group call and the chat group call. Each of the subsequent group call types in subclause 10.6.2.4 onwards are applicable to either call model. + +#### 10.6.2.2 Information flows for group call in on-network + +##### 10.6.2.2.1 MCPTT emergency group call request + +Table 10.6.2.2.1-1 describes the information flow MCPTT emergency group call request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.1-1 MCPTT emergency group call request information elements** + +| Information Element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Emergency indicator | M | Indicates that the group call request is an MCPTT emergency call | +| Alert indicator | M | Indicates whether an emergency alert is to be sent | +| Implicit floor request (NOTE) | O | Indicates that the originating client requests the floor. | +| NOTE: This element shall be included only when this information flow is from the client to the server and the originating client requests the floor. | | | + +##### 10.6.2.2.1a MCPTT emergency group call response + +Table 10.6.2.2.1a-1 describes the information flow MCPTT emergency group call response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.1a-1 MCPTT emergency group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Result | M | Result of the MCPTT emergency group call request (success or failure) | + +##### 10.6.2.2.2 MCPTT in-progress emergency group state cancel request + +Table 10.6.2.2.2-1 describes the information flow MCPTT in-progress emergency group state cancel request from the MCPTT client to the MCPTT server. + +NOTE: In Rel-14 and Rel-13 versions of this specification the name of this information flow is "MCPTT emergency group call cancel request". + +**Table 10.6.2.2.2-1: MCPTT in-progress emergency group state cancel request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the MCPTT in-progress emergency state is to be cancelled. | +| Alert indicator | O | Indicates whether the emergency alert of the cancelling party is to be cancelled | + +#### 10.6.2.2.2a MCPTT in-progress emergency group state cancel response + +Table 10.6.2.2.2a-1 describes the information flow MCPTT in-progress emergency group state cancel response from the MCPTT server to the MCPTT client. + +NOTE: In Rel-14 and Rel-13 versions of this specification the name of this information flow is "MCPTT emergency group call cancel response". + +**Table 10.6.2.2.2a-1: MCPTT in-progress emergency group state cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the MCPTT in-progress emergency in-progress is to be cancelled. | + +#### 10.6.2.2.3 MCPTT emergency alert request + +Table 10.6.2.2.3-1 describes the information flow MCPTT emergency alert request from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.3-1 MCPTT emergency alert request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| MCPTT ID | M | The identity of the alerting party | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | +| Location | O | The alerting MCPTT client's location | + +Table 10.6.2.2.3-2 describes the information flow MCPTT emergency alert request from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.3-2 MCPTT emergency alert request information elements** + +| Information Element | Status | Description | +|---------------------|--------|--------------------------------------------------------------| +| MCPTT ID | M | The identity of the alerting party | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | +| Organization name | M | The alerting MCPTT user's mission critical organization name | +| Location | O | The alerting MCPTT client's location | + +#### 10.6.2.2.3a MCPTT emergency alert response + +Table 10.6.2.2.3a-1 describes the information flow MCPTT emergency alert response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.3a-1 MCPTT emergency alert response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| MCPTT ID | M | The identity of the alerting party | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | + +#### 10.6.2.2.3b MCPTT emergency alert area trigger + +Table 10.6.2.2.3b-1 describes the information flow MCPTT emergency alert area trigger from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.3b-1 MCPTT emergency alert area trigger information elements** + +| Information Element | Status | Description | +|--------------------------------|--------|-----------------------------------------------------------------| +| MCPTT ID | M | MCPTT user identity of the party to be notified | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | +| Emergency Alert Area Indicator | M | An indicator that the MCPTT user is in an Emergency Alert Area. | + +**Editor's Note: The information flow for MCPTT emergency alert area trigger cancel is FFS.** + +#### 10.6.2.2.4 MCPTT emergency alert cancel request + +Table 10.6.2.2.4-1 describes the information flow MCPTT emergency alert cancel request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.4-1 MCPTT emergency alert cancel request information elements** + +| Information Element | Status | Description | +|----------------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | MCPTT user identity of the cancelling party | +| MCPTT ID (NOTE) | O | MCPTT user identity whose emergency alert is to be cancelled | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | +| Group's in-progress emergency state cancel request | O | Requests cancellation of the in-progress emergency state of the group | +| NOTE: | | This information shall be present if the message is requesting cancellation of another MCPTT user's alert. If not present, then the alert of the MCPTT ID of the cancelling party is being cancelled | + +#### 10.6.2.2.4a MCPTT emergency alert cancel response + +Table 10.6.2.2.4a-1 describes the information flow MCPTT emergency alert cancel response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.4a-1 MCPTT emergency alert cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | + +#### 10.6.2.2.5 MCPTT imminent peril group call request + +Table 10.6.2.2.5-1 describes the information flow MCPTT imminent peril group call request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.5-1 MCPTT imminent peril group call request information elements** + +| Information Element | Status | Description | +|-------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Imminent peril indicator | M | Indicates that the group call request is an imminent peril call | +| Implicit floor request (NOTE) | O | Indicates that the originating client requests the floor | +| NOTE: | | This element shall be included only when this information flow is from the client to the server and the originating client requests the floor. | + +#### 10.6.2.2.5a MCPTT imminent peril group call response + +Table 10.6.2.2.5a-1 describes the information flow MCPTT imminent peril group call response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.5a-1 MCPTT imminent peril group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Result | M | Result of the MCPTT imminent peril group call request (success or failure) | + +#### 10.6.2.2.6 MCPTT in-progress imminent peril group state cancel request + +Table 10.6.2.2.6-1 describes the information flow MCPTT in-progress imminent peril group state cancel request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +NOTE: In Rel-14 and Rel-13 versions of this specification the name of this information flow is "MCPTT imminent peril group call cancel request". + +**Table 10.6.2.2.6-1 MCPTT in-progress imminent peril group state cancel request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the imminent peril group state is to be cancelled | + +#### 10.6.2.2.6a MCPTT in-progress imminent peril group state cancel response + +Table 10.6.2.2.6a-1 describes the information flow MCPTT in-progress imminent peril group state cancel response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +NOTE: In Rel-14 and Rel-13 versions of this specification the name of this information flow is "MCPTT imminent peril group call cancel response". + +**Table 10.6.2.2.6a-1 MCPTT in-progress imminent peril group state cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the imminent peril group state is to be cancelled | + +#### 10.6.2.2.7 Group call request (MCPTT client – MCPTT server) + +Table 10.6.2.2.7-1 describes the information flow group call request from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.7-1 Group call request information elements** + +| Information Element | Status | Description | +|--------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID (NOTE) | O | The MCPTT group ID of the group on which the call is requested | +| SDP offer | M | Media parameters of MCPTT clients | +| Implicit floor request | O | When originating client requests the floor, this element shall be included | +| Broadcast indicator | O | Indicates that the group call request is for a broadcast group call | +| MCPTT ID list | O | The MCPTT ID of users being invited to the temporary group call - user regroup | +| Temporary group indicator | O | Indicates that the group call request is for a temporary group call - user regroup | +| NOTE: the MCPTT group ID shall not be present for the temporary group call - user regroup. | | | + +#### 10.6.2.2.8 Group call request (MCPTT server – MCPTT server) + +Table 10.6.2.2.8-1 describes the information flow group call request between the MCPTT servers. + +**Table 10.6.2.2.8-1 Group call request information elements** + +| Information Element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is initiated | +| SDP offer | M | Media parameters of MCPTT server | +| Broadcast indicator | O | Indicates that the group call request is for a broadcast group call | +| Implicit floor request (NOTE) | O | Indicates that the originating client requests the floor. | +| NOTE: This element shall be included only when the originating client requests the floor. | | | + +#### 10.6.2.2.9 Group call request (MCPTT server – MCPTT client) + +Table 10.6.2.2.9-1 describes the information flow group call request from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.9-1 Group call request information elements** + +| Information Element | Status | Description | +|---------------------------|--------|-----------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is initiated | +| SDP offer | M | Media parameters of MCPTT server | +| Broadcast indicator | O | Indicates that the group call request is for a broadcast group call | +| Temporary group indicator | O | Indicates that the group call request is for a temporary group call performed by user regroup | + +#### 10.6.2.2.10 Group call response (MCPTT server – MCPTT client) + +Table 10.6.2.2.10-1 describes the information flow group call response from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.10-1 Group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the group call request (success or failure) | + +#### 10.6.2.2.11 Group call response (MCPTT server – MCPTT server) + +Table 10.6.2.2.11-1 describes the information flow group call response between the MCPTT servers. + +**Table 10.6.2.2.11-1 Group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the target MCPTT group member | +| Functional alias | O | The functional alias of the target MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the group call request (success or failure) | + +#### 10.6.2.2.12 Group call response (MCPTT client – MCPTT server) + +Table 10.6.2.2.12-1 describes the information flow group call response from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.12-1 Group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the target MCPTT group member | +| Functional alias | O | The functional alias of the target MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is initiated | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the group call request (success or failure) | + +#### 10.6.2.2.13 Group call notify (MCPTT server – MCPTT client) + +Table 10.6.2.2.13-1 describes the information flow group call notify from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.13-1 Group call notify information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| MCPTT ID list | O | The list of MCPTT IDs of the MCPTT group members whose acknowledgement is not required | + +#### 10.6.2.2.14 Group call release request (MCPTT server – MCPTT client) + +Table 10.6.2.2.14-1 describes the information flow group call release request from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.14-1 Group call release request information elements** + +| Information Element | Status | Description | +|---------------------------|--------|--------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | +| Temporary group indicator | O | Indicates that the group call release request is for a temporary group call - user regroup | + +#### 10.6.2.2.14a Group call release request (MCPTT client – MCPTT server) + +Table 10.6.2.2.14a-1 describes the information flow group call release request from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.14a-1 Group call release request information elements** + +| Information Element | Status | Description | +|---------------------------|--------|--------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | +| Temporary group indicator | O | Indicates that the group call release request is for a temporary group call - user regroup | + +#### 10.6.2.2.15 Group call release request (MCPTT server – MCPTT server) + +Table 10.6.2.2.15-1 describes the information flow group call release request between the MCPTT servers. + +**Table 10.6.2.2.15-1 Group call release request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +#### 10.6.2.2.16 Group call release response (MCPTT client – MCPTT server) + +Table 10.6.2.2.16-1 describes the information flow group call release response from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.16-1 Group call release response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +#### 10.6.2.2.17 Group call release response (MCPTT server – MCPTT server) + +Table 10.6.2.2.17-1 describes the information flow group call release response between the MCPTT servers. + +**Table 10.6.2.2.17-1 Group call release response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +#### 10.6.2.2.18 Group call rejoin request (MCPTT client – MCPTT server) + +Table 10.6.2.2.18-1 describes the information flow group call rejoin request from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.18-1 Group call rejoin request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the re-joining MCPTT group member | +| Functional alias | O | The functional alias of the re-joining MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is on-going | +| SDP offer | M | Media parameters of MCPTT client | + +#### 10.6.2.2.19 Group call rejoin response (MCPTT server – MCPTT client) + +Table 10.6.2.2.19-1 describes the information flow group call rejoin response from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.19-1 Group call rejoin response information elements** + +| Information Element | Status | Description | +|--------------------------|--------|-----------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member rejoining the group call | +| Functional alias | O | The functional alias of the MCPTT group member re-joining the group call | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is on-going | +| SDP answer | M | Media parameters selected | +| Emergency indicator | O | Indicates that the ongoing group call is an MCPTT emergency group call | +| Imminent peril indicator | O | Indicates that the ongoing group call is an MCPTT imminent peril group call | + +#### 10.6.2.2.20 Group join request + +Table 10.6.2.2.20-1 describes the information flow group join request from the MCPTT client to the MCPTT server and from the (MCPTT user's primary) MCPTT server to the group host MCPTT server. + +**Table 10.6.2.2.20-1 Group join request information elements** + +| Information Element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member joining the group communications for the group | +| Functional alias | O | The functional alias of the MCPTT group member joining the group communication for the group | +| MCPTT group ID | M | The MCPTT group ID of the group to which the group communication is requested | +| SDP offer | M | Media parameters of MCPTT client | +| Implicit floor request (NOTE) | O | Indicates that the originating client requests the floor. | +| NOTE: This element shall be included only when the originating client requests the floor. | | | + +#### 10.6.2.2.21 Group join response + +Table 10.6.2.2.21-1 describes the information flow group join response from the MCPTT server to the MCPTT client and from the group host MCPTT server to the (MCPTT user's primary) MCPTT server. + +**Table 10.6.2.2.21-1 Group join response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member joining the group communications for the group | +| Functional alias | O | The functional alias of the MCPTT group member joining the group communication for the group | +| MCPTT group ID | M | The MCPTT group ID of the group to which the group communication is requested | +| SDP answer | M | Media parameters selected | + +#### 10.6.2.2.22 Group call leave request (MCPTT server – MCPTT client) + +Table 10.6.2.2.22-1 describes the information flow group call leave request from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.22-1 Group call leave request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member which has been de-affiliated | +| Functional alias | O | The functional alias of the MCPTT group member which has been de-affiliated | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is on-going | + +#### 10.6.2.2.23 Group call leave response (MCPTT client – MCPTT server) + +Table 10.6.2.2.23-1 describes the information flow group call leave response from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.23-1 Group call leave response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member which has been de-affiliated | +| Functional alias | O | The functional alias of the MCPTT group member which has been de-affiliated | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is on-going | + +#### 10.6.2.2.24 Group interrogate request (MCPTT server – MCPTT server) + +Table 10.6.2.2.24-1 describes the information flow group interrogate request between two MCPTT servers. + +**Table 10.6.2.2.24-1 Group interrogate request information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester | +| MCPTT group ID | M | The MCPTT group ID of the group being interrogated | + +#### 10.6.2.2.25 Group interrogate response (MCPTT server – MCPTT server) + +Table 10.6.2.2.25-1 describes the information flow group interrogate response between two MCPTT servers. + +**Table 10.6.2.2.25-1 Group interrogate response information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester | +| MCPTT group ID | M | The MCPTT group ID of the group being interrogated | +| MCPTT ID list | M | List of the MCPTT IDs for the MCPTT group members that are members of the MCPTT group ID | + +#### 10.6.2.2.26 Group-broadcast group call request (MCPTT client – MCPTT server) + +Table 10.6.2.2.26-1 describes the information flow group-broadcast group call request from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.26-1 Group-broadcast group call request information elements** + +| Information Element | Status | Description | +|------------------------|--------|----------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| SDP offer | M | Media parameters of MCPTT clients | +| Implicit floor request | M | When originating client requests the floor, this element shall be included | +| Broadcast indicator | M | Indicates that the group call request is for a broadcast group call | + +#### 10.6.2.2.27 Group-broadcast group call request (MCPTT server – MCPTT client) + +Table 10.6.2.2.27-1 describes the information flow group-broadcast group call request from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.27-1 Group-broadcast group call request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| SDP offer | M | Media parameters of MCPTT clients | +| Broadcast indicator | M | Indicates that the group call request is for a broadcast group call | + +#### 10.6.2.2.28 Group-broadcast group call response (MCPTT client – MCPTT server) + +Table 10.6.2.2.28-1 describes the information flow group-broadcast group call response from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.28-1 Group-broadcast group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the target MCPTT group member | +| Functional alias | O | The functional alias of the target MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is initiated | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the group-broadcast group call request (success or failure) | + +#### 10.6.2.2.29 Group-broadcast group call response (MCPTT server – MCPTT client) + +Table 10.6.2.2.29-1 describes the information flow group-broadcast group call response from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.29-1 Group-broadcast group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| Functional alias | O | The functional alias of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the group-broadcast group call request (success or failure) | + +#### 10.6.2.2.30 Group-broadcast group call release request (MCPTT client – MCPTT server) + +Table 10.6.2.2.30-1 describes the information flow group-broadcast group call release request from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.30-1 Group-broadcast group call release request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +#### 10.6.2.2.31 Group-broadcast group call release request (MCPTT server – MCPTT client) + +Table 10.6.2.2.31-1 describes the information flow group-broadcast group call release request from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.31-1 Group-broadcast group call release request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +#### 10.6.2.2.32 Group-broadcast group call release response (MCPTT server – MCPTT client) + +Table 10.6.2.2.32-1 describes the information flow group-broadcast group call release response from the MCPTT server to the MCPTT client. + +**Table 10.6.2.2.32-1 Group-broadcast group call release response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +### 10.6.2.2.33 Group-broadcast group call release response (MCPTT client – MCPTT server) + +Table 10.6.2.2.33-1 describes the information flow group-broadcast group call release response from the MCPTT client to the MCPTT server. + +**Table 10.6.2.2.33-1 Group-broadcast group call release response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| Functional alias | O | The functional alias of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +### 10.6.2.3 Group call within one MCPTT system + +#### 10.6.2.3.1 Group call models + +##### 10.6.2.3.1.1 Pre-arranged group call + +###### 10.6.2.3.1.1.1 General + +A pre-arranged group call is initiated by one of the group members. The initiation of a pre-arranged group call results in all other affiliated group members being invited. + +###### 10.6.2.3.1.1.2 Pre-arranged group call setup + +The procedure focuses on the case where an MCPTT client is initiating an MCPTT group call with unicast signalling for communicating with the affiliated MCPTT members of that group. + +Procedures in figure 10.6.2.3.1.1.2-1 are the signalling control plane procedures for the MCPTT client initiating establishment of an MCPTT group call with a pre-arranged group i.e., MCPTT users on client 1, client 2 and client 3 belong to the same group which is defined in the MCPTT group management server. + +Pre-conditions: + +1. A pre-arranged group is an MCPTT group that is pre-defined with MCPTT group ID and member list in the group management server. All members of the group belong to the same MCPTT system. +2. It is assumed that MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 are already registered for receiving MCPTT service and affiliated. Optionally, they may have an activated functional alias to be used during the group communication. + +![Sequence diagram for Pre-arranged group call setup. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The process involves initiating a group call, resolving the group ID, sending requests to other clients, receiving responses, notifying the initiator, and establishing the media plane.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note left of MCPTT client 1: 1. Initiate group call + MCPTT client 1->>MCPTT server: 2. Group call request + Note over MCPTT server, Group management server: 3. Resolve group id + MCPTT server->>MCPTT client 2: 4a. Group call request + Note right of MCPTT client 2: 4a. Notify group call + MCPTT server->>MCPTT client 3: 4b. Group call request + Note right of MCPTT client 3: 4b. Notify group call + MCPTT client 2->>MCPTT server: 5. Group call response + MCPTT client 3->>MCPTT server: 5. Group call response + MCPTT server->>MCPTT client 1: 6. Group call response + MCPTT server->>MCPTT client 1: 7. Group call notify + Note over MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3: 8. Media plane and floor control establishment + +``` + +Sequence diagram for Pre-arranged group call setup. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The process involves initiating a group call, resolving the group ID, sending requests to other clients, receiving responses, notifying the initiator, and establishing the media plane. + +**Figure 10.6.2.3.1.1.2-1: Pre-arranged group call setup** + +1. User at MCPTT client 1 would like to initiate an MCPTT group call with a selected group (identified by MCPTT group ID). The MC service user may select a functional alias, which is displayed to other MC service users. + +NOTE 1: MCPTT client 1 need not be aware of the affiliation status of other MCPTT clients to the group while initiating the group call. + +NOTE 2: The selected functional alias is not changed during the group call, i.e. a MCPTT client uses the same functional alias until the group call is released or the MCPTT client has left the group call. + +2. MCPTT client 1 sends a group call request towards the MCPTT server via the SIP core, which hosts the group selected by the user and identified by MCPTT group ID. The group call request also contains the MCPTT group ID and an SDP offer containing the MCPTT client media parameters. If there is a floor request to transmit, then the group call request contains an indication of an implicit floor request. If the MC service user of MCPTT client 1 has selected a functional alias, then the group call request contains that functional alias. + +3. MCPTT server checks whether the user of MCPTT client 1 is authorized to initiate a group call for the selected group. If authorized and the group call is ongoing for that MCPTT group ID, the MCPTT server adds the requesting MCPTT client 1 to the existing MCPTT group call and notifies the MCPTT client 1 that the MCPTT group call is already in progress. Otherwise, MCPTT server resolves the MCPTT group ID to determine the members of that group and their affiliation status, based on the information from the group management server. + +If present, the MCPTT server checks whether the provided functional alias is allowed to be used and has been activated for the user. + +NOTE 3: MCPTT server can have already retrieved the user/group configuration data and locally cached. If the user/group configuration data is not locally cached on the MCPTT server then MCPTT server requests the user/group configuration data from the MCPTT user database/group management server. + +4. MCPTT server includes information that it communicates using MCPTT service, offers the same media parameters or a subset of the media parameters contained in the initial received request and sends the + +corresponding group call request via the SIP core towards the MCPTT clients of each of those affiliated group members. MCPTT users are notified about the incoming group call and the functional alias of the group call initiating user is displayed if present. The MCPTT server indicates whether acknowledgement is required for the call and the functional alias of the group call initiating MC service user may be displayed. + +5. The receiving MCPTT clients accept the group call request, and a group call response is sent to the group host MCPTT server. This response may contain an acknowledgement. The conditions for sending acknowledgement may be based on configuration. The response may also contain a functional alias of the responding MC service user, which is verified (valid and activated for the user) by the MCPTT server. +6. MCPTT server sends the group call response including the selected media parameters to the MCPTT client 1 through the signalling path to inform about successful call establishment. The response may contain the functional alias, which may be displayed + +NOTE 4: Step 6 can occur at any time following step 4b, and prior to step 7 depending on the conditions to proceed with the call. + +7. If the initiating MCPTT user requires the acknowledgement from affiliated MCPTT group members, and the required MCPTT group members do not acknowledge the call setup within a configured time (the "acknowledged call setup timeout"), then the MCPTT server may proceed with or abandon the call and then notify the initiating MCPTT user that the acknowledgements did not include all required members according to group policy. This notification may be sent to the initiating MCPTT user by the MCPTT server more than once during the call when MCPTT users join or leave the MCPTT group call. +8. MCPTT client 1, client 2 and client 3 have successfully established media plane for communication. MCPTT floor participant 1, floor participant 2 and floor participant 3 exchange floor control information e.g., MCPTT client 1 receives the floor granted information over the established media plane assuming implicit floor control request from MCPTT client 1 while at the same time floor participants at other MCPTT client's receive floor taken information. MCPTT client 1 indicates to the MCPTT user that the floor is available to send media, while the other MCPTT clients in the group call will be receiving that media. If audio cut-in policy is enabled for the MCPTT group, floor arbitration follows the logic defined in subclause 10.9.1.5. + +NOTE 5: The clients use the same functional alias within floor control procedures as used during group call setup. + +#### 10.6.2.3.1.1.3 Release pre-arranged group call + +The procedure focuses on the case where an MCPTT server initiates the termination of an ongoing MCPTT group call for all the participants of that group call, since at least one of the termination conditions are met e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCPTT group members are not present. + +NOTE: The procedure for MCPTT user leaving the group call is a different scenario and is not considered in this solution. + +Procedures in figure 10.6.2.3.1.1.3-1 are the signalling control plane procedures for the MCPTT server initiating termination of an ongoing MCPTT group call. + +![Sequence diagram showing the release of a pre-arranged group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3. The process starts with an ongoing group call, followed by a release request from the server, notification of users, release responses, and finally resource release.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +Home MCPTT service provider + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + + Note over MCPTT client 1, MCPTT client 3: 1.Group call ongoing between MCPTT client 1, client 2 and client 3 + Note over MCPTT server: 2.Release group call + Note over MCPTT server: 3. Determine group call participants and generate group call release + MCPTT server->>MCPTT client 1: 4a.Group call release request + MCPTT server->>MCPTT client 2: 4b.Group call release request + MCPTT server->>MCPTT client 3: 4c.Group call release request + MCPTT client 1->>MCPTT server: 5a.Notify user + MCPTT client 2->>MCPTT server: 5b.Notify user + MCPTT client 3->>MCPTT server: 5c.Notify user + MCPTT client 1->>MCPTT server: 6.Group call release response + MCPTT client 2->>MCPTT server: 6.Group call release response + MCPTT client 3->>MCPTT server: 6.Group call release response + Note over MCPTT client 1, MCPTT client 3: 7. Releasing floor control and media plane resources associated with the group call + +``` + +Sequence diagram showing the release of a pre-arranged group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3. The process starts with an ongoing group call, followed by a release request from the server, notification of users, release responses, and finally resource release. + +**Figure 10.6.2.3.1.1.3-1: Release pre-arranged group call** + +1. It is assumed that MCPTT users on MCPTT client 1, client 2 and client 3 are already part of the ongoing group call (e.g., as a result of pre-arranged group call setup). +2. MCPTT server would like to release the MCPTT group call which is ongoing e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCPTT group members are not present. +3. MCPTT server identifies the participants of the ongoing group call and generates group call release request to release ongoing session. +4. MCPTT server sends a group call release request via SIP core towards each participant of the ongoing group call. +5. MCPTT users are notified about the release of the group call. +6. MCPTT client(s) receiving group call release request, acknowledge towards the MCPTT server by sending a group call release response. +7. MCPTT client 1, client 2 and client 3 have successfully released the floor control and media plane resources associated with the group call that is terminated. + +#### 10.6.2.3.1.1.4 Late entry pre-arranged group call + +Procedures in figure 10.6.2.3.1.1.4-1 are the signalling control plane procedures for the MCPTT server requesting a newly affiliated member or a member coming back from out of coverage to join an ongoing MCPTT group call. + +Pre-condition: + +1. MCPTT group is previously defined on the group management server with MCPTT users affiliated to that group. All members of the group belong to the same MCPTT system. +2. It is assumed that MCPTT users on MCPTT client 2 to MCPTT client n are on an ongoing call. Optionally, the MCPTT users may use activated functional aliases. + +![Sequence diagram titled 'Home MCPTT service provider' showing the interaction for a late entry pre-arranged group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client n. The sequence of messages is: 1. MCPTT client 1 is newly affiliated or coming back from out of network coverage (internal event); 2. Group call request from MCPTT server to MCPTT client 1; 3. Notify user (internal event on MCPTT client 1); 4. Group call response from MCPTT client 1 to MCPTT server; 5. MCPTT client 1 is added to ongoing group call (internal event on MCPTT server); 6. Floor taken from MCPTT server to MCPTT client 1.](08f6ace0c83e7394657fa372b47aec04_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client n + Note right of MCPTT server: 1. MCPTT client 1 is newly affiliated or coming back from out of network coverage + MCPTT server->>MCPTT client 1: 2. Group call request + Note left of MCPTT client 1: 3. Notify user + MCPTT client 1->>MCPTT server: 4. Group call response + Note right of MCPTT server: 5. MCPTT client 1 is added to ongoing group call + MCPTT server->>MCPTT client 1: 6. Floor taken + +``` + +Sequence diagram titled 'Home MCPTT service provider' showing the interaction for a late entry pre-arranged group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client n. The sequence of messages is: 1. MCPTT client 1 is newly affiliated or coming back from out of network coverage (internal event); 2. Group call request from MCPTT server to MCPTT client 1; 3. Notify user (internal event on MCPTT client 1); 4. Group call response from MCPTT client 1 to MCPTT server; 5. MCPTT client 1 is added to ongoing group call (internal event on MCPTT server); 6. Floor taken from MCPTT server to MCPTT client 1. + +**Figure 10.6.2.3.1.1.4-1: Late entry pre-arranged group call** + +1. MCPTT server determines that MCPTT client 1 which is newly affiliated or coming back from out of coverage has to be invited to join an ongoing group call (late entry). +2. MCPTT server generates group call request including the information such as MCPTT service identifier (possible for the SIP core to route the request to the MCPTT server), MCPTT group ID of the group invited to join, offer one or more media types and sends towards the MCPTT client 1 via SIP core. +3. MCPTT user at MCPTT client 1 is notified about the incoming group call. +4. Upon MCPTT user at MCPTT client 1 accepting the incoming group call request, MCPTT client 1 sends the group call response including the selected media types to the MCPTT server through the signalling path. If the incoming group call request is rejected by the MCPTT client 1, the MCPTT server should not resend the group call request. The group call response may also contain a functional alias of MCPTT client 1. +5. MCPTT client 1 is successfully added to the ongoing group call and MCPTT users at MCPTT client 1 to MCPTT client n may be notified about the MCPTT client 1 joining the group call and the functional alias of MCPTT client 1 may be displayed. +6. The floor taken with the information of the current talker is sent to MCPTT client 1. + +#### 10.6.2.3.1.1.5 Rejoining call + +Procedures in figure 10.6.2.3.1.1.5-1 are the signalling control plane procedures for the MCPTT client to rejoin an ongoing MCPTT group call (e.g. coming back from out of coverage). + +Pre-conditions: + +- It is assumed that MCPTT users on MCPTT client 2 to MCPTT client n are on an ongoing call. Optionally, the MCPTT users may use activated functional aliases. + +![Sequence diagram for 'Rejoin call' within a 'Home MCPTT service provider' box. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client n. The sequence is: 1. MCPTT client 1 sends a 'Group call rejoin request' to the MCPTT server. 2. The MCPTT server sends an 'Authorize' message to MCPTT client 1. 3. The MCPTT server sends a 'Group call rejoin response' to MCPTT client 1. 4. A horizontal bar indicates that MCPTT client 1 is added to the ongoing group call. 5. The MCPTT server sends a 'Floor taken' message to MCPTT client 1.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client n + Note right of MCPTT client n: Home MCPTT service provider + MCPTT client 1->>MCPTT server: 1. Group call rejoin request + MCPTT server-->>MCPTT client 1: 2. Authorize + MCPTT server-->>MCPTT client 1: 3. Group call rejoin response + Note right of MCPTT client n: 4. MCPTT client 1 is added to ongoing group call + MCPTT server-->>MCPTT client 1: 5. Floor taken + +``` + +Sequence diagram for 'Rejoin call' within a 'Home MCPTT service provider' box. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client n. The sequence is: 1. MCPTT client 1 sends a 'Group call rejoin request' to the MCPTT server. 2. The MCPTT server sends an 'Authorize' message to MCPTT client 1. 3. The MCPTT server sends a 'Group call rejoin response' to MCPTT client 1. 4. A horizontal bar indicates that MCPTT client 1 is added to the ongoing group call. 5. The MCPTT server sends a 'Floor taken' message to MCPTT client 1. + +**Figure 10.6.2.3.1.1.5-1: Rejoin call** + +1. MCPTT client 1 has necessary information for rejoining an ongoing group call, then the MCPTT client 1 initiates group call rejoin request including the ongoing group call information. The group call rejoin request may contain a functional alias of MCPTT client 1 as selected by the MC service user. +2. MCPTT server checks whether the MCPTT client 1 can rejoin the ongoing call (e.g. based upon affiliation status) and checks the functional alias, if present. +3. MCPTT client 1 is informed that the group call rejoin is successful by sending a group call rejoin response. If the ongoing group call is emergency or imminent peril group call, the response shall contain emergency or imminent peril indicator. +4. MCPTT client 1 is successfully added to the ongoing group call and MCPTT users at MCPTT client 1 to MCPTT client n may be notified about the MCPTT client 1 joining the group call and the functional alias of MCPTT client 1 may be displayed. +5. The floor taken with the information of the current talker is sent to MCPTT client 1. + +#### 10.6.2.3.1.2 Chat group call + +##### 10.6.2.3.1.2.1 General + +In a chat group (restricted) call model, the MCPTT user individually joins a group call without being invited. The establishment of a chat group (restricted) call does not result in other group members being invited. + +Figure 10.6.2.3.1.2.2-1 describes the basic procedure for the MCPTT client initiating an MCPTT group call which uses the chat group (restricted) call model. Restricted means that only users that have been configured as members of the given group are allowed to join the group communications for the given group. + +Chat group join mechanism: + +- Each MCPTT client sends a group join request when the MCPTT user wants to participate in the group communication for the group. (This message does not impact the MCPTT user's membership in the group; the MCPTT server will verify that the MCPTT user is an authorized member of the group.) +- The group join request may include a request to transmit. It is assumed that the group join request will be delivered from MCPTT client to MCPTT server using SIP. +- The group join request is used to indicate to the MCPTT server that the MCPTT user associated with the given MCPTT client wishes to participate (begin to receive media) from the group. + +- The group join request shall cause the MCPTT server to generate an implicit affiliation for the MCPTT user to the group, if the user is not already affiliated to the group. +- The group join request normally contains the information needed to negotiate media parameters between MCPTT server and MCPTT client for the group call. The group join request can take the form of a SIP invite. +- A selected functional alias is not changed by a MCPTT client during the whole participation within a chat group call, i.e. a MCPTT client uses the same functional alias selected when joining the chat group call until the chat group call is released or the MCPTT client leaves the chat group call. + +Subsequent participation in a group call when the group is using the chat model: + +- Once an MCPTT client successfully joins a group call which is using the chat model, the MCPTT client connects to the media plane for the call if the call is currently ongoing. +- If the MCPTT group call is not currently ongoing (i.e.: when MCPTT clients on the group call are not sending or receiving media, and the time out between floor control exchanges has expired) then the newly joined MCPTT client will only have pre-established its media parameters for the call. +- If the newly joined MCPTT user wishes to transmit media (start or re-start the call) to the affiliated users of the group using the chat model, then the MCPTT client using its associated floor control participant would follow a normal floor control procedure for requesting the floor. +- Since subsequent group call media transmissions are controlled using floor control signalling, additional SIP signalling messages may not be required for subsequent call stop and start. +- Each request to transmit from an MCPTT user could be viewed as a new instance of a group call for the given group when the floor idle timer expires and no media is present for an extended time. +- The MCPTT server may tear down the media plane between successive group calls using the chat model, or the MCPTT server may allow the media plane to remain up between successive group calls using the chat model depending on resources. + +#### 10.6.2.3.1.2.2 Chat group call setup + +MCPTT client 1, client 2, and client 3 are served by the home MCPTT service provider in figure 10.6.2.3.1.2.2-1. + +Pre-condition: + +1. MCPTT user 2 and MCPTT user 3 have previously joined (affiliated) to the group. MCPTT client 1, client 2, and client 3 are registered and all users (MCPTT user 1, user 2, and user 3) have been authenticated and authorized to use the MCPTT service. +2. MCPTT client 1, MCPTT client 2 and MCPTT client 3 may have activated functional alias(es) configured to be used during the group call communication. No call is currently in progress for the group. + +![Sequence diagram for MCPTT chat group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3. The sequence starts with 1a. Group join request from client 1 to server. 1b. MCPTT server receives the group join request. 1c. Group join response from server to client 1. 2. MCPTT user 1 requests to transmit causing the media plane to be established (if not pre-established). 3. Media plane signaling using floor control, shown as a wide double-headed arrow spanning all lifelines.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + Note right of MCPTT server: 1b. MCPTT server receives the group join request. + MCPTT client 1->>MCPTT server: 1a. Group join request + MCPTT server-->>MCPTT client 1: 1c. Group join response + Note over MCPTT client 1, MCPTT client 3: 2. MCPTT user 1 requests to transmit causing the media plane to be established (if not pre-established). + Note over MCPTT client 1, MCPTT client 3: 3. Media plane signaling using floor control + +``` + +Sequence diagram for MCPTT chat group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3. The sequence starts with 1a. Group join request from client 1 to server. 1b. MCPTT server receives the group join request. 1c. Group join response from server to client 1. 2. MCPTT user 1 requests to transmit causing the media plane to be established (if not pre-established). 3. Media plane signaling using floor control, shown as a wide double-headed arrow spanning all lifelines. + +**Figure 10.6.2.3.1.2.2-1: MCPTT chat group call** + +1. MCPTT user 1 indicates to join the group communication for the group. This may include a request to transmit. + +1a. MCPTT client 1 sends a group join request with the MCPTT group ID of the desired group. It contains the MCPTT user's MCPTT ID, the MCPTT client media parameters and optionally a functional alias. If there is a request to transmit, then the group join request contains an indication of an implicit floor request. + +1b. The MCPTT server receives the group join request. MCPTT server generates an implicit affiliation (if the MCPTT user is not already affiliated to the group) and verifies that MCPTT user 1 is authorized to affiliate to the group by following the affiliation procedure (subclause 10.8.3 in 3GPP TS 23.280 [16]). + +If present, the MCPTT server checks whether the provided functional alias is allowed to be used and has been activated for the user. + +1c. The MCPTT server replies with a group join response indicating the acceptance of the group join request and also returns the MCPTT server selected media parameters for the group call in the group join response. + +2. If MCPTT user 1 requests to transmit, the MCPTT server establishes the media plane (if not already established) for the call. The associated floor participants for MCPTT client 1, client 2, and client 3 use the floor control procedure to initiate the call. E.g., the floor participant for MCPTT client 1 receives the MCPTT floor grant. The corresponding floor participants for MCPTT client 2 and MCPTT client 3 receive the MCPTT floor taken. If present, the functional alias of MCPTT client 1, MCPTT client 2 and MCPTT client 3 are displayed where appropriate. + +3. Floor control will continue to be used by the floor participants associated with MCPTT client 1, MCPTT client 2 and MCPTT client 3 for the duration of the call. Media plane signalling using floor control will be used for subsequent calls for the group as long as one or more users are affiliated. If audio cut-in policy is enabled for the MCPTT group, floor arbitration follows the logic defined in subclause 10.9.1.5. + +#### 10.6.2.3.1.2.3 Release chat group call + +The procedure describes the case where the MCPTT server releases an ongoing MCPTT group call for all the participants of that group call, since at least one of the conditions for release are met e.g. due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or the number of affiliated MCPTT group members is below the minimum number permitted. + +NOTE 1: The procedure for an MCPTT user leaving the group call is a different procedure. + +Procedures in figure 10.6.2.3.1.2.3-1 are the procedures for the MCPTT server initiating the release of an ongoing MCPTT group call. + +The following precondition applies: + +- A group call is ongoing between MCPTT clients 1, 2 and 3 + +![Sequence diagram titled 'Release chat group call' showing the interaction between an MCPTT server and three MCPTT clients (1, 2, and 3) within a 'Home MCPTT service provider'.](3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + Note right of MCPTT server: Home MCPTT service provider + + MCPTT server->>MCPTT server: 1. Release group call + MCPTT server->>MCPTT server: 2. Determine group call participants and generate group call release request + MCPTT server->>MCPTT client 1: 3a. Group call release request + MCPTT client 1->>MCPTT client 1: 4a. Notify user + MCPTT server->>MCPTT client 2: 3b. Group call release request + MCPTT client 2->>MCPTT client 2: 4b. Notify user + MCPTT server->>MCPTT client 3: 3c. Group call release request + MCPTT client 3->>MCPTT client 3: 4c. Notify user + MCPTT client 1->>MCPTT server: 5. Group call release response + MCPTT client 2->>MCPTT server: 5. Group call release response + MCPTT client 3->>MCPTT server: 5. Group call release response + Note right of MCPTT server: 6. Release floor control and media plane resources associated with the group call + +``` + +Sequence diagram titled 'Release chat group call' showing the interaction between an MCPTT server and three MCPTT clients (1, 2, and 3) within a 'Home MCPTT service provider'. + +**Figure 10.6.2.3.1.2.3-1: Release chat group call** + +1. MCPTT server would like to release the MCPTT group call which is ongoing e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCPTT group members are not present. +2. MCPTT server identifies the participants of the ongoing group call and generates group call release request to release the ongoing session. +3. MCPTT server sends a group call release request towards each participant of the ongoing group call. + +NOTE 2: The group call release request can also be sent over SIP signalling on the signalling plane. + +4. MCPTT users are notified about the release of the group call. +5. Optionally the MCPTT client(s) receiving group call release request, may send a group call release response to the MCPTT server. + +NOTE 3: The MCPTT client can send group call release response when the group call release request is sent using a unicast bearer. + +- MCPTT client 1, client 2 and client n release the floor control and media plane resources associated with the group call that is released. Successful release of the group call does not affect the status of affiliation of any of the clients. + +#### 10.6.2.3.1.2.4 Late entry chat group call + +Procedures in figure 10.6.2.3.1.2.4-1 are those for the MCPTT server requesting a group member that is newly affiliated or coming back from out of coverage to join an ongoing MCPTT group call. + +Pre-conditions: + +- MCPTT group is previously defined on the group management server with MCPTT users affiliated to that group. All members of the group belong to the same MCPTT system. +- MCPTT users using MCPTT client 2 to MCPTT client n are in an ongoing call. Optionally, the MCPTT users may use activated functional aliases. + +![Sequence diagram for Late entry chat group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client n. The diagram shows the process of adding a newly affiliated client (client 1) to an ongoing group call.](65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client n + + Note right of MCPTT server: 1. MCPTT client 1 is newly affiliated or coming back from out of network coverage + MCPTT server->>MCPTT client 1: 2. Group call request + Note left of MCPTT client 1: 3. Notify user + MCPTT client 1->>MCPTT server: 4. Group call response + Note over MCPTT client 1, MCPTT client n: 5. MCPTT client 1 is added to ongoing group call + MCPTT server->>MCPTT client 1: 6. Floor taken + +``` + +Sequence diagram for Late entry chat group call. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client n. The diagram shows the process of adding a newly affiliated client (client 1) to an ongoing group call. + +**Figure 10.6.2.3.1.2.4-1: Late entry chat group call** + +- MCPTT server determines that MCPTT client 1 which is newly affiliated or has returned from being out of coverage has to be requested to join an ongoing group call (late entry). +- MCPTT server sends group call request to MCPTT client 1. +- MCPTT user at MCPTT client 1 is notified about the incoming group call. +- Upon MCPTT user at MCPTT client 1 accepting the incoming request, MCPTT client 1 sends a group call response to the MCPTT server. If the incoming request is rejected by MCPTT client 1, the MCPTT server should not resend the group call request. If the group call response includes a functional alias, it is the same functional alias as used before and checked by the MCPTT server. +- MCPTT client 1 is successfully added to the ongoing group call and MCPTT users at MCPTT client 1 to MCPTT client n may be notified about the MCPTT client 1 joining the group call. The functional aliases of MCPTT client 1 displayed, if present. +- Floor taken with the information of the current talker is sent to MCPTT client 1. + +### 10.6.2.3.2 Exiting group call due to de-affiliation + +Procedures in figure 10.6.2.3.2-1 are the signalling control plane procedures for the MCPTT server requesting a newly de-affiliated member to leave an ongoing MCPTT group call. + +Pre-conditions: + +1. MCPTT group is previously defined on the group management server with MCPTT users affiliated to that group. All members of the group belong to the same MCPTT system. +2. MCPTT users on MCPTT client 1 to MCPTT client n are on an ongoing call. +3. MCPTT client 1 has been de-affiliated from the MCPTT group. + +![Sequence diagram showing the procedure for exiting an MCPTT group call due to de-affiliation.](d7948c38a18636aefecdd95388196460_img.jpg) + +The diagram illustrates the interaction between MCPTT clients and a server within a 'Home MCPTT service provider'. It starts with an ongoing group call (Step 0) between MCPTT client 1 and clients 2 through n. A box indicates that MCPTT client 1 has been de-affiliated from the group. The server then sends a 'Group call leave request' (Step 2) to client 1. Client 1 notifies its user (Step 3) and sends a 'Group call leave response' (Step 4) to the server. Finally, the server confirms that MCPTT client 1 has been removed from the ongoing group call (Step 5). + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client n + Note right of MCPTT server: Home MCPTT service provider + Note over MCPTT client 1, MCPTT client n: 0. Group call ongoing between MCPTT client 1 to client n + Note right of MCPTT client 1: 1. MCPTT client 1 has been de-affiliated from the MCPTT group + MCPTT server->>MCPTT client 1: 2. Group call leave request + Note left of MCPTT client 1: 3. Notify user + MCPTT client 1->>MCPTT server: 4. Group call leave response + Note over MCPTT server, MCPTT client n: 5. MCPTT client 1 is removed from the ongoing group call +``` + +Sequence diagram showing the procedure for exiting an MCPTT group call due to de-affiliation. + +**Figure 10.6.2.3.2-1: Exiting MCPTT group call due to de-affiliation** + +1. MCPTT client 1 which has been de-affiliated is instructed to leave the ongoing group call. +2. MCPTT server sends a group call leave request to MCPTT client 1. +3. MCPTT user at MCPTT client 1 is notified about leaving the group call. +4. MCPTT client 1 sends the group call leave response and leaves the group call. +5. MCPTT client 1 is now removed from the ongoing group call and MCPTT users at MCPTT client 2 to MCPTT client n may be notified that MCPTT client 1 has left the group call. + +### 10.6.2.4 Group call involving groups from multiple MCPTT systems + +#### 10.6.2.4.1 Group call for temporary groups across multiple MCPTT systems + +##### 10.6.2.4.1.1 Group call setup + +###### 10.6.2.4.1.1.1 Group call setup procedure – originating side + +Figure 10.6.2.4.1.1.1-1 illustrates the originating side group call involving groups from multiple MCPTT systems. It considers the scenario for group hierarchies and temporary groups formed by group regroup. The protocol followed may be SIP. + +Pre-conditions: + +1. The security aspects of sharing the user information between primary and partner MCPTT systems shall be governed as per the service provider agreement between them. In this case, we consider the partner MCPTT system does not share their users' information to the primary MCPTT system. +2. The MCPTT user belongs to an MCPTT group hosted by the primary MCPTT system. +3. A temporary group is formed by authorized MCPTT user/dispatcher by the group regroup procedure (subclause 10.2.4.2 in 3GPP TS 23.280 [16]) and identified via a temporary MCPTT group ID. +4. The MCPTT group members of the constituent MCPTT groups belonging to the temporary group are affiliated to participate in a group call for the temporary group. +5. The authorized MCPTT user/dispatcher created the temporary group on the MCPTT server of the primary MCPTT system. +6. The constituent groups of the temporary group may belong to MCPTT servers of the partner MCPTT systems. + +![Sequence diagram showing the group call setup procedure. Lifelines: MCPTT client, MCPTT server (primary), Group management server (primary), and MCPTT server (partner). The sequence starts with a '1. Group call request' from the client to the primary server. The primary server then performs internal steps '2. Get the group information and resolve the constituent groups information' and '3. Call the accessible group members'. It then sends a '4. Group call request' to the partner server. The partner server performs '5. Call the group members'. A '6. Group call response' is sent from the partner server back to the primary server, which then sends a '7. Group call response' to the client. Finally, '8. Group call communication' is established between the client and the primary server.](17439b945bd5156395c7ba15bf04f8fb_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server (primary) + participant Group management server (primary) + participant MCPTT server (partner) + + Note right of MCPTT server (primary): 2. Get the group information and resolve the constituent groups information + Note right of MCPTT server (primary): 3. Call the accessible group members + + MCPTT client->>MCPTT server (primary): 1. Group call request + MCPTT server (primary)->>MCPTT server (partner): 4. Group call request + MCPTT server (partner)->>MCPTT server (primary): 6. Group call response + MCPTT server (primary)->>MCPTT client: 7. Group call response + Note over MCPTT client, MCPTT server (primary): 8. Group call communication + +``` + +Sequence diagram showing the group call setup procedure. Lifelines: MCPTT client, MCPTT server (primary), Group management server (primary), and MCPTT server (partner). The sequence starts with a '1. Group call request' from the client to the primary server. The primary server then performs internal steps '2. Get the group information and resolve the constituent groups information' and '3. Call the accessible group members'. It then sends a '4. Group call request' to the partner server. The partner server performs '5. Call the group members'. A '6. Group call response' is sent from the partner server back to the primary server, which then sends a '7. Group call response' to the client. Finally, '8. Group call communication' is established between the client and the primary server. + +**Figure 10.6.2.4.1.1.1-1: Group call setup involving temporary groups from multiple MCPTT systems (originating)** + +1. The affiliated MCPTT user via MCPTT client initiates a group call with an MCPTT group ID. A group call request message with the MCPTT group ID is routed to the MCPTT server of the primary MCPTT system, which owns the group and is where the authorized MCPTT user/dispatcher created the temporary group. If the group call is for a temporary group formed by the group regroup procedure, the MCPTT group ID will be a temporary MCPTT group ID. + +2. The MCPTT server of the primary MCPTT system gets the group information (either from group management server or itself) including the constituent MCPTT groups' identities, accessible group members list of the constituent groups, and other related data. +3. The MCPTT server of the primary MCPTT system initiates directly a call request to the accessible group members using the detailed user information and/or location information. The group members upon receipt of the call request may accept or reject the call. +4. The MCPTT server of the primary MCPTT system may not have access to group members' information of the constituent group belonging to the partner MCPTT system. For such group members, the MCPTT server of the primary MCPTT system initiates a group call request message to the MCPTT server of the partner MCPTT system with the target group's MCPTT group ID information. +5. The MCPTT server of the partner MCPTT system further initiates a call request to the constituent group's members as described in step 3. +6. The MCPTT server of the partner MCPTT system provides a group call response to the MCPTT server of the primary MCPTT system with success or failure result and/or detailed reason information if there is a failure. +7. The MCPTT server of the primary MCPTT system provides a group call response message to the MCPTT client of the affiliated MCPTT user upon receiving responses to the call requests sent to members of primary and partner MCPTT systems. The group call response message will consist of the success or failure result and/or detailed reason information if there is a failure. + +NOTE: The group call response message is triggered depending on the conditions to proceed with the call. + +8. Upon successful call setup completion a group call is established for the group members from constituent groups of multiple MCPTT servers. + +#### 10.6.2.4.1.1.2 Group call setup procedure – terminating side + +The procedure in figure 10.6.2.4.1.1.2-1 illustrates the terminating side group call involving groups from multiple MCPTT systems. It considers the scenario for group hierarchies and temporary groups formed by group regroup. The protocol followed may be SIP. + +![Sequence diagram showing the terminating side group call setup. 1. Primary MCPTT server sends 'Group call request' to Partner MCPTT server. 2. Partner MCPTT server performs 'Determine to forward the request'. 3. Partner MCPTT server sends 'Group call request' to Affiliated MCPTT user client. 4. Client performs 'Notify group call'. 5. Client sends 'Group call response' back to Partner server. 6. Partner server sends 'Group call response' back to Primary server.](91b12db3c85bbf466ad27eb3665a1b06_img.jpg) + +``` + +sequenceDiagram + participant Primary as MCPTT server (Primary) + participant Partner as MCPTT server (Partner) + participant Client as MCPTT client (Affiliated MCPTT user) + + Primary->>Partner: 1.Group call request + Note over Partner: 2.Determine to forward the request + Partner->>Client: 3.Group call request + Note over Client: 4.Notify group call + Client->>Partner: 5.Group call response + Partner->>Primary: 6.Group call response + +``` + +Sequence diagram showing the terminating side group call setup. 1. Primary MCPTT server sends 'Group call request' to Partner MCPTT server. 2. Partner MCPTT server performs 'Determine to forward the request'. 3. Partner MCPTT server sends 'Group call request' to Affiliated MCPTT user client. 4. Client performs 'Notify group call'. 5. Client sends 'Group call response' back to Partner server. 6. Partner server sends 'Group call response' back to Primary server. + +**Figure 10.6.2.4.1.1.2-1: Group call involving groups from multiple MCPTT systems (terminating)** + +1. The MCPTT server of the primary MCPTT system sends the group call request message to the MCPTT server(s) of the partner MCPTT system. + +2. The MCPTT server of the partner MCPTT system determines whether to forward the group call request message to the MCPTT client(s) based on the user affiliation. +3. The MCPTT server of the partner MCPTT system forwards the group call request message to MCPTT client(s). The MCPTT server indicates whether acknowledgement is required for the call. +4. The MCPTT user is notified about the incoming MCPTT group call. +5. The receiving MCPTT client(s) accept the group call request and a group call response message is sent to the MCPTT server of the partner MCPTT system. This response may contain an acknowledgement. The conditions for sending acknowledgement may be based on configuration. +6. The MCPTT server of the partner MCPTT system forwards the group call response message to the MCPTT server of the primary MCPTT system (i.e. group hosting MCPTT server for the group call involving groups from multiple MCPTT systems). + +#### 10.6.2.4.1.2 Group call release + +The procedure focuses on the case where the group host MCPTT server releases an ongoing MCPTT group call for all the participants of that group call involving groups from multiple MCPTT systems, since at least one of the release conditions are met e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCPTT group members are not present. + +NOTE: The scenario of MCPTT user leaving the group call is not considered in this procedure. + +Figure 10.6.2.4.1.2-1 illustrates the procedure for the MCPTT server releasing an ongoing MCPTT group call involving groups from multiple MCPTT systems. + +Pre-conditions: + +1. The MCPTT server of the primary MCPTT system is controlling the group call involving groups from multiple MCPTT systems. +2. The MCPTT client 1 belongs to group of the MCPTT server of the primary MCPTT system and the MCPTT client 2 and client 3 belong to the groups of the MCPTT server of the partner MCPTT system. +3. The MCPTT users on MCPTT client 1, client 2 and client 3 are already part of the ongoing group call (e.g., as a result of group call setup involving groups from multiple MCPTT systems). + +![Sequence diagram illustrating the group call release procedure involving multiple MCPTT systems. Lifelines: MCPTT client 1, MCPTT server (Primary), MCPTT server (Partner), MCPTT client 2, MCPTT client 3. The sequence starts with the Primary server sending a '1.Release group call' message to itself, followed by '2.Determine group call participants and generate group call release'. It then sends '3a.Group call release request' to client 1, '3b.Group call release request' to the Partner server, which in turn sends '3c-1.Group call release request' to client 2 and '3c-2.Group call release request' to client 3. Clients 1, 2, and 3 notify their users ('4a.Notify user', '4b-1.Notify user', '4b-2.Notify user') and send responses ('5a.Group call release response', '5b-1.Group call release response', '5b-2.Group call release response') back to the Primary server. Finally, a message '6.Releasing floor control and media plane resources associated with the group call' is shown at the bottom.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server (Primary) + participant MCPTT server (Partner) + participant MCPTT client 2 + participant MCPTT client 3 + + Note right of MCPTT server (Primary): 1.Release group call + Note right of MCPTT server (Primary): 2.Determine group call participants and generate group call release + MCPTT server (Primary)->>MCPTT client 1: 3a.Group call release request + MCPTT server (Primary)->>MCPTT server (Partner): 3b.Group call release request + MCPTT server (Partner)->>MCPTT client 2: 3c-1.Group call release request + MCPTT server (Partner)->>MCPTT client 3: 3c-2.Group call release request + MCPTT client 1->>MCPTT server (Primary): 4a.Notify user + MCPTT client 2->>MCPTT server (Partner): 4b-1.Notify user + MCPTT client 3->>MCPTT server (Partner): 4b-2.Notify user + MCPTT client 1->>MCPTT server (Primary): 5a.Group call release response + MCPTT client 2->>MCPTT server (Partner): 5b-1.Group call release response + MCPTT client 3->>MCPTT server (Partner): 5b-2.Group call release response + MCPTT server (Partner)->>MCPTT server (Primary): 5c.Group call release response + Note right of MCPTT client 3: 6.Releasing floor control and media plane resources associated with the group call + +``` + +Sequence diagram illustrating the group call release procedure involving multiple MCPTT systems. Lifelines: MCPTT client 1, MCPTT server (Primary), MCPTT server (Partner), MCPTT client 2, MCPTT client 3. The sequence starts with the Primary server sending a '1.Release group call' message to itself, followed by '2.Determine group call participants and generate group call release'. It then sends '3a.Group call release request' to client 1, '3b.Group call release request' to the Partner server, which in turn sends '3c-1.Group call release request' to client 2 and '3c-2.Group call release request' to client 3. Clients 1, 2, and 3 notify their users ('4a.Notify user', '4b-1.Notify user', '4b-2.Notify user') and send responses ('5a.Group call release response', '5b-1.Group call release response', '5b-2.Group call release response') back to the Primary server. Finally, a message '6.Releasing floor control and media plane resources associated with the group call' is shown at the bottom. + +**Figure 10.6.2.4.1.2-1: Group call release involving groups from multiple MCPTT systems** + +1. The MCPTT server of primary MCPTT system would like to release the MCPTT group call which is ongoing e.g., due to hang timer expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCPTT group members are not present. +2. The MCPTT server of the primary MCPTT system identifies the participants of the ongoing group call and generates group call release message to release ongoing session. +3. The MCPTT server of the primary MCPTT system initiates a group call release request message via SIP core towards each accessible participant of the ongoing group call (3a). The MCPTT server of the primary MCPTT system may not have access to group members' information of the constituent group belonging to a partner MCPTT system. For such group members, the MCPTT server of the primary MCPTT system initiates a group call release request message (3b) to the MCPTT server(s) of the partner MCPTT system(s) with the target group's MCPTT group ID information. The MCPTT server(s) of the partner MCPTT system(s) further initiate group call release request messages (3c-1, 3c-2) to its group's users. +4. The MCPTT users are notified about the release of the group call. +5. The MCPTT client(s) receiving the group call release request messages provide group call release response to the MCPTT server of the primary MCPTT system. The MCPTT client(s) of the MCPTT users belonging to partner MCPTT system(s) route their responses via the MCPTT server(s) of the partner MCPTT system(s). +6. The MCPTT client 1, client 2 and client 3 have successfully released the floor control and media plane resources associated with the group call that is released. + +#### 10.6.2.4.2 Group call for temporary group formed by group regroup procedure involving multiple MCPTT systems via trusted mode + +Figure 10.6.2.4.2-1 illustrates a group call involving a temporary group formed by group regroup from multiple MCPTT systems. The protocol followed may be SIP. + +Pre-conditions: + +1. The security aspects of sharing the user information between primary and partner MCPTT systems shall be governed as per the service provider agreement between them. In this case, we consider the partner MCPTT system shares their users' information to the primary MCPTT system. + +2. The MCPTT user belongs to an MCPTT group hosted by the primary MCPTT system. +3. A temporary group is formed by authorized MCPTT user/dispatcher by the group regroup procedure (subclause 10.2.4.2 in 3GPP TS 23.280 [16]) and identified via a temporary MCPTT group ID. +4. The MCPTT group members of the constituent MCPTT groups belonging to the temporary group are affiliated to participate in a group call for the temporary group. +5. The authorized MCPTT user/dispatcher created the temporary group on the MCPTT server of the primary MCPTT system. +6. The constituent groups of the temporary group may belong to MCPTT servers of the partner MCPTT systems. + +![Sequence diagram illustrating a group call involving a temporary group formed by group regroup from multiple MCPTT systems. The diagram shows interactions between an MCPTT client, a primary MCPTT server, a primary group management server, and a partner MCPTT server.](212c50c4e3d043c989037a01e13c1a98_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server (primary) + participant Group management server (primary) + participant MCPTT server (partner) + + Note right of MCPTT server (primary): 2.Get the temporary group information and resolve to constituent groups #1 and #2 + + MCPTT client->>MCPTT server (primary): 1. Group call request + MCPTT server (primary)-->>MCPTT server (partner): 3. Group interrogate request + MCPTT server (partner)-->>MCPTT server (primary): 4. Group interrogate response + MCPTT server (primary)->>MCPTT client: 6. Group call response + Note left of MCPTT server (primary): 5.Call invite/notify members of groups #1 and #2 that satisfy hierarchical group policy + Note bottom: 7.Group call communication + +``` + +Sequence diagram illustrating a group call involving a temporary group formed by group regroup from multiple MCPTT systems. The diagram shows interactions between an MCPTT client, a primary MCPTT server, a primary group management server, and a partner MCPTT server. + +**Figure 10.6.2.4.2-1: Group call involving temporary group formed by group regroup from multiple MCPTT systems** + +1. The affiliated MCPTT user via MCPTT client initiates a group call with an MCPTT group ID. A group call request message with the MCPTT group ID is routed to the MCPTT server of the primary MCPTT system, which owns the temporary group formed by group regroup procedure, and is also where the authorized MCPTT user/dispatcher has created the temporary group. The MCPTT group ID will be a temporary MCPTT group ID. +2. The MCPTT server of the primary MCPTT system gets the group information (either from group management server or itself) including the constituent MCPTT groups' identities, and other related data. +3. The MCPTT server of the primary MCPTT system may interrogate the MCPTT server of the partner MCPTT system for the affiliated group 2 members. +4. The MCPTT server of the partner MCPTT system responds with a list of the affiliated group members of group 2. + +NOTE 1: Steps 3 and 4 do not occur if the constituent groups' information is available and up to date at primary MCPTT system due to the procedure for temporary group formation as defined in subclause 10.2.4.2 in 3GPP TS 23.280 [16]. + +5. The MCPTT server of the primary MCPTT system verifies the commencement policies of the temporary group, and initiates a call invitation or call notification to the affiliated members of groups 1 and 2. +6. The MCPTT server of the primary MCPTT system provides group call response message to the MCPTT UE of authorized MCPTT user/dispatcher upon receiving responses to the call invitations sent to members of primary and partner MCPTT systems. The group call response will consist of the success or failure result and/or detailed reason information if there is a failure. +7. Upon successful call setup completion a group call is established for the group members belonging to constituent groups of multiple MCPTT systems. + +NOTE 2: MCPTT clients are generally aware that their (constituent) groups have been regrouped (e.g., see subclause 10.1.5.3 in 3GPP TS 23.280 [16]); however, if not, the partner MCPTT server of the constituent group can also respond to a group call request with a redirection response, such as "moved temporarily" that includes the group URI of the temporary group formed by group regroup procedure. + +### 10.6.2.4.3 Group call for an MCPTT group defined in the partner MCPTT system + +#### 10.6.2.4.3.1 Pre-arranged group call setup procedure – initiating side + +Figure 10.6.2.4.3.1-1 illustrates the pre-arranged group call setup procedure for an MCPTT group defined in the partner MCPTT system. + +Pre-conditions: + +1. MCPTT group is defined on the group management server which is located in the partner MCPTT system with MCPTT users affiliated to that group. +2. The members of the MCPTT group defined in partner MCPTT system belong to different MCPTT systems. + +![Sequence diagram showing the pre-arranged group call setup procedure. Lifelines: MCPTT client (Affiliated MCPTT user), MCPTT server (primary), MCPTT server (Group host MCPTT server) (partner), and Group management server. The sequence starts with a Group call request from the client to the primary server, followed by a determination of the group home server, forwarding the request to the partner server, resolving the group ID, calling members, and finally establishing communication.](a97f7c055c1fd8d79037d02b3fc38496_img.jpg) + +``` + +sequenceDiagram + participant Client as MCPTT client (Affiliated MCPTT user) + participant PrimaryServer as MCPTT server (primary) + participant PartnerServer as MCPTT server (Group host MCPTT server) (partner) + participant GroupManagementServer as Group management server + + Note right of PrimaryServer: 2.Determine the group home MCPTT server based on the group id + Note right of PartnerServer: 4.Resolve group id + Note right of PartnerServer: 5.Call the affiliated group members + + Client->>PrimaryServer: 1.Group call request + PrimaryServer->>PartnerServer: 3.Group call request + PartnerServer->>GroupManagementServer: 4.Resolve group id + PartnerServer->>GroupManagementServer: 5.Call the affiliated group members + PartnerServer->>PrimaryServer: 6.Group call response + PrimaryServer->>Client: 7.Group call response + Note left of Client: 8.Group call communication establishment + +``` + +Sequence diagram showing the pre-arranged group call setup procedure. Lifelines: MCPTT client (Affiliated MCPTT user), MCPTT server (primary), MCPTT server (Group host MCPTT server) (partner), and Group management server. The sequence starts with a Group call request from the client to the primary server, followed by a determination of the group home server, forwarding the request to the partner server, resolving the group ID, calling members, and finally establishing communication. + +**Figure 10.6.2.4.3.1-1: Pre-arranged group call setup for an MCPTT group defined in partner MCPTT system (initiating)** + +1. The affiliated MCPTT user via MCPTT client initiates a group call with an MCPTT group ID. A group call request message with the MCPTT group ID is routed to the MCPTT server of the primary MCPTT system. +2. The MCPTT server of the primary MCPTT system determines the group home MCPTT server where the MCPTT group is defined. +3. The MCPTT server of the primary MCPTT system forwards the group call request to the MCPTT server of the partner MCPTT system which owns the group and is where the authorized MCPTT user/dispatcher created the temporary group. + +4. The MCPTT server of the partner MCPTT system checks whether the user of MCPTT client is authorized for initiating the group call for the selected group. If authorized, it resolves the MCPTT group ID to determine the members of that group and their affiliation status, based on the information from group management server. +5. The MCPTT server of the partner MCPTT system initiates a call request to the group's affiliated members. +6. The MCPTT server of the partner MCPTT system provides a group call response message to the MCPTT server of the primary MCPTT system of the MCPTT client. The group call response message will consist of the success or failure result and/or detailed reason information if there is a failure. +7. The MCPTT server of the primary MCPTT system forwards the group call response message to the MCPTT client. +- 8 Upon successful call setup completion a group call is established for the group members. + +#### 10.6.2.4.3.2 Pre-arranged group call setup – terminating side + +The procedure described in figure 10.6.2.4.3.2-1 is used for pre-arranged group call setup when acknowledgement is required from at least some of the call recipients. + +![Sequence diagram for Pre-arranged group call setup – terminating side. The diagram shows three lifelines: Partner MCPTT server (Group host MCPTT server), Primary MCPTT server, and MCPTT client (Affiliated MCPTT user). The sequence of messages is: 1. Group call request from Partner to Primary; 2. Determine forward the request (internal to Primary); 3. Group call request from Primary to MCPTT client; 4. Notify group call (internal to MCPTT client); 5. Group call response from MCPTT client to Primary; 6. Group call response from Primary to Partner.](cc542843836eecb036b99cb270b54a1e_img.jpg) + +``` + +sequenceDiagram + participant Partner MCPTT server (Group host MCPTT server) + participant Primary MCPTT server + participant MCPTT client (Affiliated MCPTT user) + Note right of Primary: 2. Determine forward the request + Note right of MCPTT client: 4. Notify group call + Partner->>Primary: 1. Group call request + Primary->>MCPTT client: 3. Group call request + MCPTT client->>Primary: 5. Group call response + Primary->>Partner: 6. Group call response + +``` + +Sequence diagram for Pre-arranged group call setup – terminating side. The diagram shows three lifelines: Partner MCPTT server (Group host MCPTT server), Primary MCPTT server, and MCPTT client (Affiliated MCPTT user). The sequence of messages is: 1. Group call request from Partner to Primary; 2. Determine forward the request (internal to Primary); 3. Group call request from Primary to MCPTT client; 4. Notify group call (internal to MCPTT client); 5. Group call response from MCPTT client to Primary; 6. Group call response from Primary to Partner. + +**Figure 10.6.2.4.3.2-1: Pre-arranged group call setup for an MCPTT group defined in partner MCPTT system (terminating)** + +1. MCPTT server of the partner MCPTT system sends the group call request message towards the MCPTT server of the primary MCPTT system of the MCPTT client. +2. The MCPTT server of the primary MCPTT system determines whether to forward the group call request message to the MCPTT client based on the user subscription. +3. The MCPTT server of the primary MCPTT system forwards the group call request message to MCPTT client. The MCPTT server indicates whether acknowledgement is required for the call. +4. MCPTT user is notified about the incoming group call. +5. The receiving MCPTT client accepts the group call and a response message is sent to the MCPTT server of the primary MCPTT system. This response may contain an acknowledgement. The conditions for sending acknowledgement may be based on configuration. +6. The MCPTT server of the primary MCPTT system forwards the response message to the MCPTT server of the partner MCPTT system (i.e. group hosting MCPTT server). + +### 10.6.2.4.3.3 Chat group call setup + +Figure 10.6.2.4.3.3-1 illustrates the group call setup procedure for an MCPTT chat group defined in the partner MCPTT system. + +Pre-conditions: + +1. The MCPTT users of MCPTT clients 1, 2 and 3 are members of a chat group that is defined in the partner MCPTT system. +2. MCPTT user 2 and MCPTT user 3 have previously joined (affiliated) to the group. MCPTT client 1, client 2, and client 3 are registered and all users (MCPTT user 1, user 2, and user 3) have been authenticated and authorized to use the MCPTT service. +3. MCPTT client 1, MCPTT client 2 and MCPTT client 3 may have activated functional alias(es) configured to be used during the group call communication. +4. No call is currently in progress for the group. + +![Sequence diagram illustrating the chat group call setup for an MCPTT group defined in a partner MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT server (primary), MCPTT server (Group host MCPTT server) (partner), MCPTT client 2, and MCPTT client 3. The steps are: 1. Group join request from client 1 to primary server; 2. Check user authorization and determine group home server; 3. Forwarded group join request from primary server to partner server; 4. Check authorization and affiliate user; 5. Group join response from partner server to primary server; 6. Store group affiliation status; 7. Group join response from primary server to client 1; 8. MCPTT user 1 requests to transmit; 9. Media plane signaling using floor control.](dd6c544ab685b25dd17f59456efcfbfc_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server (primary) + participant MCPTT server (Group host MCPTT server) (partner) + participant MCPTT client 2 + participant MCPTT client 3 + + Note right of MCPTT server (primary): 2. Check user authorization. Determine the group home MCPTT server based on the group id + Note right of MCPTT server (partner): 4. Check authorization. Affiliate the MCPTT user. + Note right of MCPTT server (primary): 6. Store group affiliation status + + MCPTT client 1->>MCPTT server (primary): 1. Group join request + MCPTT server (primary)->>MCPTT server (partner): 3. Group join request + MCPTT server (partner)->>MCPTT server (primary): 5. Group join response + MCPTT server (primary)->>MCPTT client 1: 7. Group join response + Note over MCPTT client 1, MCPTT client 3: 8. MCPTT user 1 requests to transmit causing the media plane to be established (if not pre-established). + Note over MCPTT client 1, MCPTT client 3: 9. Media plane signaling using floor control + +``` + +Sequence diagram illustrating the chat group call setup for an MCPTT group defined in a partner MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT server (primary), MCPTT server (Group host MCPTT server) (partner), MCPTT client 2, and MCPTT client 3. The steps are: 1. Group join request from client 1 to primary server; 2. Check user authorization and determine group home server; 3. Forwarded group join request from primary server to partner server; 4. Check authorization and affiliate user; 5. Group join response from partner server to primary server; 6. Store group affiliation status; 7. Group join response from primary server to client 1; 8. MCPTT user 1 requests to transmit; 9. Media plane signaling using floor control. + +**Figure 10.6.2.4.3.3-1: Chat group call setup for an MCPTT group defined in partner MCPTT system** + +1. MCPTT client 1 sends a group join request with the MCPTT group ID of the desired group. If there is a request to transmit, then the group join request contains an indication of an implicit floor request. +2. The MCPTT server of the primary MCPTT system verifies that MCPTT user 1 is authorized to affiliate to the group by following the affiliation procedure (subclause 10.8.3.2 / 10.8.3.2a in 3GPP TS 23.280 [16]). The MCPTT server of the primary MCPTT system determines the group home MCPTT server where the MCPTT group is defined. +3. The MCPTT server of the primary MCPTT system forwards the group join request to the partner MCPTT server i.e. to the the group home MCPTT server. +4. The partner MCPTT server receives the group join request. The partner MCPTT server generates an implicit affiliation (if the MCPTT user 1 is not already affiliated to the group) and verifies that MCPTT user 1 is authorized to affiliate to the group by following the affiliation procedure (subclause 10.8.3 in 3GPP TS 23.280 [16]). + +If present, the MCPTT server checks whether the provided functional alias is allowed to be used and has been activated for the user. + +5. The MCPTT server of the partner MCPTT system replies with a group join response indicating the acceptance of the group join request and also including the MCPTT server selected media parameters for the group call. +6. The primary MCPTT server stores the affiliation status of the user for the requested MCPTT group. +7. The primary MCPTT server forwards the group join response to the MCPTT client. +8. The MCPTT user 1 requests to transmit, causing the media plane to be established (if not already established) for the call. +9. Floor control will continue to be used by the floor participants associated with MCPTT client 1, MCPTT client 2 and MCPTT client 3 for the duration of the call. Media plane signalling using floor control will be used for subsequent calls for the group as long as one or more users are affiliated. + +### 10.6.2.4.4 Merging of groups involving multiple MCPTT systems + +Figure 10.6.2.4.4-1 below illustrates the merging of MCPTT clients in a newly formed temporary group with active group calls. + +Pre-conditions: + +1. The temporary group consists of group 1, which is hosted by the primary MCPTT system, and group 2, which is hosted by the partner MCPTT system. +2. Both group 1 and group 2 have active calls. +3. The group management client of the authorized MCPTT user belongs to the primary MCPTT system. + +![Sequence diagram showing the merging of groups involving multiple MCPTT systems. Lifelines: MCPTT client (Authorized MCPTT user), MCPTT server (Primary), MCPTT server (Partner), MCPTT client n (Partner). The process involves temporary group formation, merge request/response, combine request/response, transfer of clients and metadata, floor control activation, and a final merge notify.](e42cc691d9c7c4d23e66b04472bb494e_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client (Authorized MCPTT user) + participant MCPTT server (Primary) + participant MCPTT server (Partner) + participant MCPTT client n (Partner) + + Note over MCPTT client, MCPTT server (Partner): 1. Temporary group formation (see figure 10.4.4.2-1) + MCPTT client (Authorized MCPTT user)->>MCPTT server (Primary): 2. Group call merge request + MCPTT server (Primary)-->>MCPTT client (Authorized MCPTT user): 3. Group call merge response + MCPTT server (Primary)->>MCPTT server (Partner): 4. Group combine request + MCPTT server (Partner)-->>MCPTT server (Primary): 5. Group combine response (member details) + Note over MCPTT server (Primary), MCPTT client n (Partner): 6. Transfer group 2 MPCTT clients to temporary group call + Note over MCPTT server (Primary), MCPTT server (Partner): 7. Transfer group 2 meta data (e.g. queues, etc) to MCPTT server (group 1) + Note over MCPTT server (Primary), MCPTT client n (Partner): 8. Floor control temporary group + MCPTT server (Primary)-->>MCPTT client (Authorized MCPTT user): 9. Group call merge notify + +``` + +Sequence diagram showing the merging of groups involving multiple MCPTT systems. Lifelines: MCPTT client (Authorized MCPTT user), MCPTT server (Primary), MCPTT server (Partner), MCPTT client n (Partner). The process involves temporary group formation, merge request/response, combine request/response, transfer of clients and metadata, floor control activation, and a final merge notify. + +**Figure 10.6.2.4.4-1: Merging of groups involving multiple MCPTT systems** + +1. The temporary group formation - group regrouping involving multiple MCPTT systems, according to subclause 10.2.4.2 in 3GPP TS 23.280 [16], takes place. +2. The MCPTT client of the authorized MCPTT user requests group call merge operation to MCPTT server hosting group 1. The identities of the groups being combined are included in this message. +3. The MCPTT server (primary) responds with an OK response. + +4. The MCPTT server (primary) sends a group combine request to the MCPTT server (partner) that is hosting group 2. +5. The MCPTT server (partner) responds with a list members of group 2 and an indication of which members are affiliated and which are active in the call. +6. The MCPTT server (primary) contacts the active members of group 2 inviting them to join the temporary group call. +7. The MCPTT server (partner) transfers group 2's floor status data (including pending requests and queue positions) to the primary MCPTT server and combines this with the group 1's floor status data in order to create the temporary group's floor status data. +8. The MCPTT server (primary) performs floor control for the temporary group. +9. The MCPTT server (primary) notifies the MCPTT client of the authorised MCPTT user that the active calls have been merged. + +NOTE: The MCPTT server in primary system revokes and queues floor given to one of the two talkers based on the arbitration result for the temporary group. + +### 10.6.2.5 Broadcast group call + +#### 10.6.2.5.1 General + +A broadcast group call is a special group call where the initiating MCPTT user expects no response from the other MCPTT users, so that when his transmission is complete, so is the call. + +#### 10.6.2.5.2 Common broadcast group call procedure + +The group-broadcast group and the regrouped group are similar in structure (a collection of groups). Similarly the user-broadcast group and the pre-arranged group (a collection of users) are similar in structure. Only the call originator can transmit media during the broadcast group call and the broadcast group call is released when the transmission is complete, unless the call originator is overridden. + +Figure 10.6.2.5.2-1 illustrates the common procedure both for group-broadcast group call and user-broadcast group call. + +Pre-conditions: + +1. MCPTT client 1 and MCPTT client 2 are members of a group-broadcast group/user-broadcast group. + +![Sequence diagram for Broadcast group call procedure. The diagram shows three participants: MCPTT client 1, MCPTT server, and MCPTT client 2. The sequence of messages is: 1. Broadcast group call setup (from client 1 to server), 2. Media transmission (from client 1 to server and then to client 2), and 3. Broadcast group call release (from server to client 2).](ef8f4838401ece0abd51d63b897fa388_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note over MCPTT client 1, MCPTT server: 1. Broadcast group call setup + MCPTT client 1->>MCPTT server: + Note over MCPTT server, MCPTT client 2: 2. Media transmission + MCPTT server->>MCPTT client 2: + Note over MCPTT server, MCPTT client 2: 3. Broadcast group call release + MCPTT server->>MCPTT client 2: + +``` + +Sequence diagram for Broadcast group call procedure. The diagram shows three participants: MCPTT client 1, MCPTT server, and MCPTT client 2. The sequence of messages is: 1. Broadcast group call setup (from client 1 to server), 2. Media transmission (from client 1 to server and then to client 2), and 3. Broadcast group call release (from server to client 2). + +Figure 10.6.2.5.2-1: Broadcast group call + +1. MCPTT user at MCPTT client 1 initiates the broadcast group call setup procedure with the indication of broadcast group call. The signalling procedure is identical to the group call setup as described in subclause 10.6.2 with the inclusion of the parameter for broadcast group call indicator. + +- NOTE 1: Broadcast group call applies to both pre-arranged and chat group call model. In the chat group call model case, the broadcast group call setup procedure is done by floor control signalling. +2. MCPTT client 1 starts to transmit media. +- NOTE 2: Only the call originating MCPTT user is allowed to transmit media on broadcast group call, unless overridden. +- NOTE 3: A broadcast group call transmitted on a user-broadcast group has priority over group calls involving users within the user hierarchy. A broadcast group call transmitted on a group-broadcast group has priority over group calls on its subordinate groups. +3. If the media transmission from call originating MCPTT user is complete, the broadcast group call is released. + +#### 10.6.2.5.2.1 Group-broadcast group call procedure + +The group-broadcast group is defined as a set of groups, not a set of MCPTT users. The group-broadcast group is also defined with a hierarchy. It is expected that the MCPTT user that originates the group-broadcast group call is the only one transmitting media during the group-broadcast group call and that the group-broadcast group call is terminated when the transmission is complete. However, if the override feature is enabled, then the call originator may be overridden. + +Figure 10.6.2.5.2.1-1 illustrates the procedure for group-broadcast group call establishment. + +Pre-conditions: + +1. The group (e.g. A) to which MCPTT client 1 and MCPTT client 2 are members is a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group A as a subordinate group). +2. The group (e.g. A) currently has an on-going MCPTT group call that is not an MCPTT emergency group call. +3. The call initiator of the group-broadcast group is a member of another group (e.g., X, not group A) which is also a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group X as a subordinate group). +4. The group-broadcast group and its subordinated groups are defined in the same group management server and served by the same MCPTT server. + +![Sequence diagram for Group-broadcast group call setup. Lifelines: MCPTT client 3, MCPTT server, Group management server, MCPTT client 1, MCPTT client 2. The process involves initiating a call, resolving the group ID, checking for ongoing calls, releasing them if necessary, and then setting up the new group call with media flow.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 3 + participant MCPTT server + participant Group management server + participant MCPTT client 1 + participant MCPTT client 2 + + Note left of MCPTT client 3: 1. Initiate group-broadcast group call + MCPTT client 3->>MCPTT server: 2. Group-broadcast group call request + MCPTT server->>Group management server: 3. Resolve (group-broadcast) group ID + Note right of MCPTT server: 4. Consider on-going calls on subordinate groups + MCPTT server-->>MCPTT client 1: 5a. Group call release request + MCPTT server-->>MCPTT client 2: 5b. Group call release request + Note right of MCPTT client 1: 6a. Notify user + Note right of MCPTT client 2: 6b. Notify user + MCPTT client 1-->>MCPTT server: 7a. Group call release response + MCPTT client 2-->>MCPTT server: 7b. Group call release response + MCPTT server->>MCPTT client 1: 8a. Group-broadcast group call request + MCPTT server->>MCPTT client 2: 8b. Group-broadcast group call request + Note right of MCPTT client 1: 9a. Notify group-broadcast group call + Note right of MCPTT client 2: 9b. Notify group-broadcast group call + MCPTT client 1-->>MCPTT server: 10a. Group-broadcast group call response + MCPTT client 2-->>MCPTT server: 10b. Group-broadcast group call response + MCPTT server-->>MCPTT client 3: 11. Group-broadcast group call response + Note left of MCPTT client 3: 12. Notify user + Note right of MCPTT client 3: Media Flow + Note right of MCPTT server: Media Flow + Note right of MCPTT client 2: Media Flow + +``` + +Sequence diagram for Group-broadcast group call setup. Lifelines: MCPTT client 3, MCPTT server, Group management server, MCPTT client 1, MCPTT client 2. The process involves initiating a call, resolving the group ID, checking for ongoing calls, releasing them if necessary, and then setting up the new group call with media flow. + +**Figure 10.6.2.5.2.1-1: Group-broadcast group call** + +1. MCPTT user at MCPTT client 3 initiates the group-broadcast group call setup procedure. +2. The MCPTT client 3 sends a group-broadcast group call request to the MCPTT server. +3. The MCPTT server needs to resolve the group-broadcast group ID into its subordinate groups in order to contact the affiliated MCPTT users of those subordinate groups. +4. The MCPTT server then needs to consider any on-going group calls on those subordinate groups because this may effect the behaviour for what happens next. In this case a group call exists on a subordinate group. Thus the MCPTT users involved in the group call on this subordinate group. +5. Optionally the on-going group call on a subordinate group may be terminated in which case the MCPTT client 1 and MCPTT client 2 need to be sent a Group call release request. +6. The MCPTT client 1 and MCPTT client 2 then notify their users of the group call release request. +7. The MCPTT client 1 and MCPTT client 2 respond to the group call release request by sending a group call release response. +8. A group-broadcast group call request is sent to both the MCPTT client 1 and the MCPTT client 2. +9. MCPTT client 1 and MCPTT client 2 notify their users of the incoming group-broadcast group call. + +10. MCPTT client 1 and MCPTT client 2 respond to the group-broadcast group call request by sending a group-broadcast group call response. +11. The MCPTT server responds to MCPTT client 3 (the call initiator) that the group-broadcast group call has been established by sending a group-broadcast group call response. +12. The MCPTT client 3 notifies its user that the user can begin transmitting using the group-broadcast group call resources. + +Resources are now available for the transmission from MCPTT client 3 to MCPTT client 1 and MCPTT client 2. Once the user of MCPTT client 3 completes transmitting, the group-broadcast group call is released as are the resources. + +#### 10.6.2.5.2.2 Group-broadcast group call procedure when a subordinate group has an on-going MCPTT emergency group call + +The group-broadcast group is defined as a set of groups, not MCPTT users. The affiliated MCPTT group members of a subordinate group with an on-going MCPTT emergency group call are not interrupted by a group-broadcast group call. + +Figure 10.6.2.5.2.2-1 illustrates the procedure for group-broadcast group call when a subordinate group has an on-going MCPTT emergency group call. + +Pre-conditions: + +1. MCPTT The group (e.g. A) to which MCPTT client 1 and MCPTT client 2 are members is a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group A as a subordinate group). +2. The group (e.g. A) currently has an on-going MCPTT emergency group call. +3. The call initiator (user of MCPTT client 3) of the group-broadcast group is a member of another group (e.g., X, not group A) which is also a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group X as a subordinate group). + +![Sequence diagram illustrating the group-broadcast group call procedure when an emergency group call is on-going in one of the subordinate groups. The diagram shows interactions between MCPTT client 3, MCPTT server, Group management server, MCPTT client 1, and MCPTT client 2.](de98d4c97665a29427651680af184ff4_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 3 + participant MCPTT server + participant Group management server + participant MCPTT client 1 + participant MCPTT client 2 + + Note left of MCPTT client 3: 1. Initiate group-broadcast group call + MCPTT client 3->>MCPTT server: 2. Group-broadcast group call request + Note right of MCPTT server: 3. Resolve (group-broadcast) group ID + Note right of MCPTT server: 4. Consider on-going calls on subordinate groups + MCPTT server->>MCPTT client 3: 5. Group-broadcast group call response + Note left of MCPTT client 3: 6. Notify user + Note right of MCPTT client 3: Media Flow + +``` + +Sequence diagram illustrating the group-broadcast group call procedure when an emergency group call is on-going in one of the subordinate groups. The diagram shows interactions between MCPTT client 3, MCPTT server, Group management server, MCPTT client 1, and MCPTT client 2. + +**Figure 10.6.2.5.2.2-1: Group-broadcast group call when an emergency group call is on-going in one of the subordinate groups** + +1. The MCPTT user at MCPTT client 3 initiates the group-broadcast group call setup procedure. +2. The MCPTT client 3 sends a group-broadcast group call request to the MCPTT server. + +3. The MCPTT server needs to resolve the group-broadcast group ID into its subordinate groups in order to contact the affiliated MCPTT group members of those subordinate groups. +4. The MCPTT server then considers any on-going group calls on those subordinate groups (e.g. A) because this may affect the behaviour for what happens next. In this case an emergency group call exists on a subordinate group. + +NOTE: Not shown - The group-broadcast group call request is sent to the MCPTT clients of the MCPTT users who are affiliated members of any other subordinate groups of the group-broadcast group being set up + +5. The MCPTT server responds to the call initiator that the group-broadcast group call has been established. +6. The MCPTT client 3 notifies its user that the user can begin transmitting using the group-broadcast group call resources. + +Resources are now available for the transmission from MCPTT client 3 to the MCPTT clients (not shown) of other subordinate groups (i.e., not A). Once the user of MCPTT client 3 completes transmitting, the group-broadcast group call is released as are the resources. + +**10.6.2.5.2.3 Group-broadcast group call release procedure** + +When the call originator has completed transmitting, the group-broadcast group call is terminated and resources released. + +Figure 10.6.2.5.2.3-1 illustrates the procedure for group-broadcast group call release. + +Pre-conditions: + +1. An on-going group-broadcast group call involving MCPTT client 1, MCPTT client 2, and MCPTT client 3 exists. + +![Sequence diagram showing the group-broadcast group call release procedure. Lifelines: MCPTT client 3, MCPTT server, Group management server, MCPTT client 1, MCPTT client 2. The process starts with MCPTT client 3 finishing transmission and sending a release request to the server, which then forwards it to clients 1 and 2, notifying their users and receiving responses back to the server and client 3.](02e16c8e8e61c2706b5c0129674884a8_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 3 + participant MCPTT server + participant Group management server + participant MCPTT client 1 + participant MCPTT client 2 + + Note left of MCPTT client 3: 1. Finished transmitting + MCPTT client 3->>MCPTT server: 2. Group-broadcast group call release request + MCPTT server->>MCPTT client 1: 3a. Group-broadcast group call release request + MCPTT server->>MCPTT client 2: 3b. Group-broadcast group call release request + Note right of MCPTT client 1: 4a. Notify user + Note right of MCPTT client 2: 4b. Notify user + MCPTT client 1->>MCPTT server: 5a. Group-broadcast group call release response + MCPTT client 2->>MCPTT server: 5b. Group-broadcast group call release response + MCPTT server->>MCPTT client 3: 6. Group-broadcast group call release response + +``` + +Sequence diagram showing the group-broadcast group call release procedure. Lifelines: MCPTT client 3, MCPTT server, Group management server, MCPTT client 1, MCPTT client 2. The process starts with MCPTT client 3 finishing transmission and sending a release request to the server, which then forwards it to clients 1 and 2, notifying their users and receiving responses back to the server and client 3. + +**Figure 10.6.2.5.2.3-1: Group-broadcast group call transmission ended** + +1. MCPTT user on MCPTT client 3 finished transmitting. +2. A group-broadcast group call release request is sent to the MCPTT server of the group-broadcast group. +3. The MCPTT users of MCPTT client 1 and MCPTT client 2 of the group-broadcast group's subordinate groups are sent a group-broadcast group call release request +4. MCPTT client 1 and MCPTT client 2 notify their users that the group-broadcast group call has ended. + +5. MCPTT client 1 and MCPTT client 2 respond to confirm the release of the group-broadcast group call by sending a group-broadcast group call release response. +6. The MCPTT server sends a group-broadcast group call release response indicating to the initiator that the call is now terminated. + +10.6.2.5.2.4 Server-initiated broadcast group call release procedure + +In a broadcast group call, when the call originator has completed transmitting, the MCPTT client releases the floor. Upon receiving the floor release message the MCPTT server then determines if the broadcast call should be released. + +Figure 10.6.2.5.2.4-1 illustrates the procedure for server-initiated broadcast group call release. + +Pre-conditions: + +1. An on-going broadcast group call involving MCPTT client 1, MCPTT client 2, and MCPTT client 3 exists. +2. MCPTT client 3 is transmitting. + +![Sequence diagram showing the server-initiated broadcast group call release procedure between MCPTT client 3, MCPTT server, MCPTT client 1, and MCPTT client 2.](854cb86f664ff62fd23e7607cfeb5727_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 3 + participant MCPTT server + participant MCPTT client 1 + participant MCPTT client 2 + + Note left of MCPTT client 3: 1. Finished transmitting + MCPTT client 3->>MCPTT server: 2. Floor release + Note right of MCPTT server: 3. Evaluate group type and hang time + MCPTT server->>MCPTT client 1: 4. Group call release request + MCPTT server->>MCPTT client 3: 4. Group call release request + MCPTT server->>MCPTT client 2: 4. Group call release request + Note right of MCPTT client 1: 5. Notify user + Note right of MCPTT client 2: 5. Notify user + MCPTT client 1->>MCPTT server: 6. Group call release response + MCPTT client 3->>MCPTT server: 6. Group call release response + MCPTT client 2->>MCPTT server: 6. Group call release response + +``` + +Sequence diagram showing the server-initiated broadcast group call release procedure between MCPTT client 3, MCPTT server, MCPTT client 1, and MCPTT client 2. + +Figure 10.6.2.5.2.4-1: Server-initiated broadcast group call release + +1. MCPTT user on MCPTT client 3 finished transmitting. +2. MCPTT client 3 sends a Floor release message to the MCPTT server of the group. +3. The MCPTT Server determines that the group is a broadcast group and decides that the call should be released. + +NOTE 1: Whether the MCPTT server uses the Broadcast indicator in the originating group call request message or uses the configured Group call hang timer to determine whether the call should be released is left to implementation. + +4. The MCPTT server sends a Group call release request to MCPTT clients 1, 2, and 3. +5. MCPTT client 1 and MCPTT client 2 notify their users that the group call has ended. + +6. MCPTT clients 1, 2, and 3 respond to confirm the release of the group call by sending a group call release response. + +NOTE 2: If the group call release request is sent from the MCPTT server via **MBMS**, no response is expected from the MCPTT clients. + +### 10.6.2.5.3 Temporary group – broadcast group call procedure + +NOTE: This procedure has no security solution in 3GPP TS 33.180 [19]. + +Figure 10.6.2.5.3-1 illustrates the procedure for temporary group-broadcast group call procedure. The protocol used may be SIP. + +Pre-conditions: + +1. The security aspects of sharing the user information between primary and partner MCPTT systems shall be governed as per the service provider agreement between them. In this case, we consider the partner MCPTT system does not share their users' information to the primary MCPTT system. +2. The authorized MCPTT user/dispatcher belongs to the primary MCPTT system. +3. The MCPTT server of the primary MCPTT system is where the authorized MCPTT user/dispatcher created the temporary group. +4. Other groups in the temporary group – broadcast group may belong to partner MCPTT systems. + +![Sequence diagram illustrating the Temporary group – broadcast group call procedure. The diagram shows interactions between an MCPTT client (Authorized MCPTT user), an MCPTT server (primary), and an MCPTT server (partner).](443ee770f0d3d98d7411497a3191e2e0_img.jpg) + +``` + +sequenceDiagram + participant Client as MCPTT client (Authorized MCPTT user) + participant PrimaryServer as MCPTT server (primary) + participant PartnerServer as MCPTT server (partner) + + Note right of PrimaryServer: 2. Temporary group initiation and call invite/notify group members + + Client->>PrimaryServer: 1. Group call request + PrimaryServer->>PartnerServer: 3. Group call request + PartnerServer->>Client: 6. Group call response + Note right of PartnerServer: 4. Call invite/notify group members + PartnerServer->>PrimaryServer: 5. Group call response + Note right of PrimaryServer: 8. Temporary group is torn down + Client->>PartnerServer: 7. Media transmission + +``` + +Sequence diagram illustrating the Temporary group – broadcast group call procedure. The diagram shows interactions between an MCPTT client (Authorized MCPTT user), an MCPTT server (primary), and an MCPTT server (partner). + +**Figure 10.6.2.5.3-1: Temporary group – broadcast group call** + +1. The MCPTT client of authorized user initiates a group call with multiple groups from primary and partner MCPTT systems. A group call request message with the MCPTT group IDs (group1's MCPTT group ID, group2's MCPTT group ID) is routed to the MCPTT server of the primary MCPTT system, which is where the authorized MCPTT user/dispatcher created the temporary group. +2. The MCPTT server of the primary MCPTT system forms the temporary group with the groups' information received. It resolves the MCPTT group IDs and identifies the appropriate MCPTT server responsible for the groups. It further triggers a temporary group – broadcast group call via a group call request message to the affiliated group members of group1's MCPTT group ID of the MCPTT server of the primary MCPTT system. + +NOTE 1: The temporary group information is not notified to the group members of the constituent groups. + +3. A group call request message is further initiated with the MCPTT server of the partner MCPTT system for group2's MCPTT group ID. +4. Upon receiving the group call request message from the MCPTT server of the primary MCPTT system, the MCPTT server of the partner MCPTT system initiates a call invitation to their affiliated group members. The group members upon receipt of the invitation may accept or reject the call. Alternatively, the MCPTT server of the partner MCPTT system notifies the group members via a notification message containing the group call session identity information. Upon receipt of the notification message, the group members may perform a late call entry. +5. The MCPTT server of the partner MCPTT system provides a group call response message to the MCPTT server of the primary MCPTT system with success or failure result and/or detailed reason information in case of failure. +6. The MCPTT server of the primary MCPTT system provides a group call response message to the MCPTT client of the authorized MCPTT user upon receiving response to the corresponding group call request with the MCPTT server of the partner MCPTT system. The group call response will consist of the success or failure result and/or detailed reason information in case of failure. + +NOTE 2: The group call response message is triggered depending on the conditions to proceed with the call. + +7. Upon successful group call setup, a group call is established amongst the multiple group members from primary and partner MCPTT systems. The call originating MCPTT user starts transmitting media to other group call participants. + +NOTE 3: Only the call originating MCPTT user is allowed to transmit media on broadcast group call. + +NOTE 4: A broadcast group call transmitted on a temporary group-broadcast group has priority over group calls on its subordinate groups. + +8. At the completion of the media transmission, the broadcast group call is released, and the temporary group – broadcast group is torn down. + +## 10.6.2.6 Emergency and imminent peril procedures + +### 10.6.2.6.1 MCPTT emergency group call + +#### 10.6.2.6.1.1 MCPTT emergency group call commencement + +The procedure focuses on the case where an MCPTT client is initiating an MCPTT emergency group call with the affiliated MCPTT members of that MCPTT group. An MCPTT client in the MCPTT emergency state gains elevated access privilege for all of the MCPTT user's mission critical applications. + +Procedures in figure 10.6.2.6.1.1-1 are the signalling control plane procedures for the MCPTT client initiating establishment of an MCPTT emergency group call with an MCPTT group i.e., MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 belong to the same MCPTT group which is defined on MCPTT group management server. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group. +2. All members of the MCPTT group belong to the same MCPTT system. +3. The initiating MCPTT client 1 has been provisioned with an MCPTT group that has been designated via provisioning as the MCPTT emergency group. + +NOTE 2: Alternatively, the client could have been provisioned for emergency behaviour on the selected group. + +![Sequence diagram for MCPTT emergency group call. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The sequence shows the initiation of an emergency call, server-side processing (affiliation, authorization, bearer configuration), and subsequent notification to other group members.](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +Home MCPTT service provider + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note left of MCPTT client 1: 1. initiate MCPTT emergency group call + MCPTT client 1->>MCPTT server: 2. MCPTT emergency group call request + Note right of MCPTT server: 3. Affiliate user to group + Note right of MCPTT server: 4. Resolve group id + Note right of MCPTT server: 5. Bearer priority configuration + MCPTT server->>MCPTT client 2: 6. MCPTT emergency group call request + MCPTT server->>MCPTT client 3: 6. MCPTT emergency group call request + Note right of MCPTT client 2: 7. Notify MCPTT emergency group call + Note right of MCPTT client 3: 7. Notify MCPTT emergency group call + MCPTT client 2-->>MCPTT server: 8. MCPTT emergency group call response + MCPTT client 3-->>MCPTT server: 8. MCPTT emergency group call response + MCPTT server->>MCPTT client 1: 9. MCPTT emergency group call response + +``` + +Sequence diagram for MCPTT emergency group call. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The sequence shows the initiation of an emergency call, server-side processing (affiliation, authorization, bearer configuration), and subsequent notification to other group members. + +**Figure 10.6.2.6.1.1-1: MCPTT emergency group call** + +1. The user at the MCPTT client 1 initiates an MCPTT emergency group call. MCPTT client 1 sets its MCPTT emergency state. The MCPTT emergency state is retained until explicitly cancelled. + 2. MCPTT client 1 sends an MCPTT group call request towards the MCPTT server. The request contains an indication of the MCPTT emergency. The MCPTT server records the identity of the MCPTT user that initiated the MCPTT emergency group call until the MCPTT emergency is cancelled. Once an MCPTT emergency call has been initiated, the MCPTT group is considered to be in an in-progress emergency state until cancelled. If configured to send an MCPTT emergency alert when initiating an MCPTT emergency group call, the request also contains an indication that an MCPTT emergency alert is to be initiated. The request may contain an indication of an implicit floor request. + 3. The MCPTT server implicitly affiliates MCPTT client 1 to the emergency group if the client is not already affiliated. + 4. MCPTT server checks whether the MCPTT user of MCPTT client 1 is authorized for initiation of MCPTT emergency calls on the indicated MCPTT group, and if authorized, it resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status, based on the information from group management server. + 5. The MCPTT server configures the priority of the underlying bearers for all participants in the MCPTT group. +- NOTE 3: Successive calls during the MCPTT group's in-progress emergency state will all receive the adjusted bearer priority. +6. MCPTT server sends the MCPTT emergency group call request towards the MCPTT clients of each of those affiliated MCPTT group members. The request contains an indication of the in-progress emergency. The request + +contains an indication of an MCPTT emergency alert if the request from the originator indicated MCPTT emergency alert. + +7. MCPTT users are notified of the incoming MCPTT group call. +8. The receiving MCPTT clients send the MCPTT emergency group call response to the MCPTT server to acknowledge the MCPTT emergency group call request. For a multicast call, these acknowledgements are not sent. +9. The MCPTT server sends the MCPTT emergency group call response to the MCPTT user 1 to inform the successful MCPTT emergency call establishment. + +NOTE 4: Step 9 can occur at any time following step 5, and prior to step 10 depending on the conditions to proceed with the call. + +MCPTT client 1, MCPTT client 2 and MCPTT client 3 have successfully established media plane for communication. MCPTT floor participant 1, floor participant 2 and floor participant 3 exchange floor control information e.g., MCPTT client 1 receives the floor granted information over the established media plane, while the other MCPTT client's receive floor taken information. MCPTT client 1 indicates to the MCPTT user that the floor is available to send media, while the other MCPTT clients in the MCPTT emergency group call will be receiving that media. MCPTT client 1 can override other clients in the call except those that are also in the MCPTT emergency state. + +#### 10.6.2.6.1.2 MCPTT group call upgraded to an MCPTT emergency group call + +The procedure focuses on the case where an authorized MCPTT user is upgrading an MCPTT group call to an MCPTT emergency group call while the MCPTT group call is already in progress. + +Procedures in figure 10.6.2.6.1.2-1 are the signalling control plane procedures for the MCPTT client upgrading an MCPTT group call on an MCPTT group to an MCPTT emergency group call. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group. +2. All members of the MCPTT group belong to the same MCPTT system. +3. An MCPTT group call is already in progress. +4. The initiating MCPTT client 1 has been configured to send an MCPTT emergency alert when upgrading an MCPTT emergency group call. + +![Sequence diagram showing the upgrade of an MCPTT group call to an emergency group call. The diagram is titled 'Home MCPTT service provider' and shows a 'Group call already in progress' involving MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, and MCPTT client 3. The sequence of messages is: 1. Initiate group emergency (from client 1), 2. MCPTT emergency group call request (from client 1 to server), 3. Bearer priority adjustment (internal to server), 4. MCPTT emergency group call request (from server to clients 2 and 3), 5. Notify group emergency status (from clients 2 and 3), 6. MCPTT emergency group call response (from clients 2 and 3 to server), and 7. MCPTT emergency group call response (from server to client 1).](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note over MCPTT client 1, MCPTT client 3: Group call already in progress + + MCPTT client 1->>MCPTT server: 1. Initiate group emergency + MCPTT client 1->>MCPTT server: 2. MCPTT emergency group call request + Note over MCPTT server: 3. Bearer priority adjustment + MCPTT server->>MCPTT client 2: 4. MCPTT emergency group call request + MCPTT server->>MCPTT client 3: 4. MCPTT emergency group call request + MCPTT client 2->>MCPTT server: 5. Notify group emergency status + MCPTT client 3->>MCPTT server: 5. Notify group emergency status + MCPTT client 2->>MCPTT server: 6. MCPTT emergency group call response + MCPTT client 3->>MCPTT server: 6. MCPTT emergency group call response + MCPTT server->>MCPTT client 1: 7. MCPTT emergency group call response + +``` + +Sequence diagram showing the upgrade of an MCPTT group call to an emergency group call. The diagram is titled 'Home MCPTT service provider' and shows a 'Group call already in progress' involving MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, and MCPTT client 3. The sequence of messages is: 1. Initiate group emergency (from client 1), 2. MCPTT emergency group call request (from client 1 to server), 3. Bearer priority adjustment (internal to server), 4. MCPTT emergency group call request (from server to clients 2 and 3), 5. Notify group emergency status (from clients 2 and 3), 6. MCPTT emergency group call response (from clients 2 and 3 to server), and 7. MCPTT emergency group call response (from server to client 1). + +**Figure 10.6.2.6.1.2-1: MCPTT group call upgraded to an MCPTT emergency group call** + +1. The MCPTT user at MCPTT client 1 initiates a group emergency. MCPTT client 1 sets its MCPTT emergency state. The MCPTT emergency state is retained until explicitly cancelled. +2. MCPTT client 1 requests the MCPTT server to upgrade the MCPTT group to an in-progress emergency state by sending an MCPTT emergency group call request. If configured to send an MCPTT alert when initiating an MCPTT emergency upgrade, the request also contains an indication that an MCPTT alert is to be initiated. The request may contain an indication of an implicit floor request. + +3. The MCPTT server adjusts the priority of the underlying bearer for all or selected participants in the MCPTT group call that receive the communication over unicast. + +NOTE 2: The determination of the selected participants whose bearers have to be upgraded is left to implementation. + +4. MCPTT server sends the MCPTT emergency group call request towards the MCPTT clients of each of those affiliated MCPTT group members. The request contains an indication of an MCPTT emergency alert if the request from the originator indicated MCPTT emergency alert. +5. MCPTT users are notified of the in-progress emergency state of the MCPTT group. +6. The receiving MCPTT clients send the MCPTT emergency group call response to the MCPTT server to acknowledge the MCPTT group emergency request. For a multicast call, these acknowledgements are not sent. +7. The MCPTT server sends the MCPTT emergency group call response to the MCPTT user 1 to confirm the upgrade request. + +NOTE 3: Step 7 can occur at any time following step 3, and prior to step 8 depending on the conditions to proceed with the call. + +MCPTT client 1, MCPTT client 2 and MCPTT client 3 continue with the MCPTT group call, which has been transformed into an MCPTT emergency group call. MCPTT client 1 can override other clients in the call except those that are also in the MCPTT emergency state. + +#### 10.6.2.6.1.3 MCPTT in-progress emergency group state cancel + +NOTE 1: In Rel-14 and Rel-13 versions of this specification the title of this subclause is "MCPTT emergency group call cancel". + +The procedure focuses on the case where an MCPTT client cancels an MCPTT group's in-progress emergency. + +Procedures in figure 10.6.2.6.1.3-1 are the signalling control plane procedures for the MCPTT client cancelling an in-progress emergency of a group. + +NOTE 2: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +NOTE 3: The end of the MCPTT emergency group call does not cancel the MCPTT group's in-progress emergency state. It is explicitly cancelled by an authorized user using this procedure. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group. +2. All members of the MCPTT group belong to the same MCPTT system. +3. MCPTT group members have been notified about the in-progress emergency. +4. The MCPTT group is in the in-progress emergency state and has prioritized bearer support. +5. MCPTT client 1 previously initiated the in-progress emergency for the group. + +![Sequence diagram for MCPTT in-progress emergency group state cancel. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The process involves initiating a cancel, resolving group ID, adjusting bearer priority, notifying members, and receiving responses.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +Home MCPTT service provider + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note left of MCPTT client 1: 1. Initiate in-progress emergency group state cancel + MCPTT client 1->>MCPTT server: 2. MCPTT in-progress emergency group state cancel request + Note right of MCPTT server: 3. Resolve group id + Note right of MCPTT server: 4. Bearer priority adjustment + MCPTT server->>MCPTT client 2: 5. MCPTT in-progress emergency group state cancel request + MCPTT server->>MCPTT client 3: 5. MCPTT in-progress emergency group state cancel request + Note right of MCPTT client 2: 6. Notify emergency cancel + Note right of MCPTT client 3: 6. Notify emergency cancel + MCPTT client 2-->>MCPTT server: 7. MCPTT in-progress emergency group state cancel response + MCPTT client 3-->>MCPTT server: 7. MCPTT in-progress emergency group state cancel response + MCPTT server-->>MCPTT client 1: 8. MCPTT in-progress emergency group state cancel response + +``` + +Sequence diagram for MCPTT in-progress emergency group state cancel. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The process involves initiating a cancel, resolving group ID, adjusting bearer priority, notifying members, and receiving responses. + +**Figure 10.6.2.6.1.3-1: MCPTT in-progress emergency group state cancel** + +1. The user at the MCPTT client 1 initiates an MCPTT in-progress emergency group state cancel. + +NOTE 3: An MCPTT user authorized to cancel in-progress emergencies on the MCPTT group can also be authorised to cancel the MCPTT emergency alert in addition to the initiator. However, only the initiator can cancel the initiator's local MCPTT emergency state. + +2. MCPTT client 1 sends an MCPTT in-progress emergency group state cancel request to the MCPTT server. + +NOTE 4: When MCPTT emergency alerts are in effect together with an MCPTT in-progress emergency group state on the same MCPTT group, the MCPTT emergency alert can, under some circumstances be cancelled at the same time. In that case, the MCPTT in-progress emergency group state cancel request carries an indication that the alert is also being cancelled. + +3. MCPTT server resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status, based upon the information from group management server. +4. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required. The MCPTT server cancels/resets the emergency in-progress state of the MCPTT group. +5. The MCPTT server sends an MCPTT in-progress emergency group state cancel request to the MCPTT group members. +6. MCPTT group members are notified of the MCPTT in-progress emergency group state cancel. +7. The receiving MCPTT clients send the MCPTT in-progress emergency group state cancel response to the MCPTT server to acknowledge the MCPTT in-progress emergency group state cancel. For a multicast call scenario, these acknowledgements are not sent. + +8. The MCPTT server sends the MCPTT in-progress emergency group state cancel response to the MCPTT user 1 to confirm the MCPTT in-progress emergency group state cancel. If the MCPTT in-progress emergency group state cancel request (in step 2) contained the "Alert indicator" IE, the MCPTT client 1 resets its local emergency status. + +NOTE 5: Step 8 can occur at any time following step 4, depending on the conditions to proceed with the call. + +#### 10.6.2.6.2 MCPTT imminent peril group call + +##### 10.6.2.6.2.1 MCPTT imminent peril group call commencement + +The procedure focuses on the case where an authorized MCPTT user is initiating an imminent peril group call for communicating with the affiliated MCPTT members of that MCPTT group. This procedure will gain elevated access privilege for the MCPTT client if it is not already in that state. The access privilege for other applications will not necessarily be affected. + +Procedures in figure 10.6.2.6.2.1-1 are the signalling control plane procedures for the MCPTT client initiating establishment of an imminent peril group call with an MCPTT group i.e., MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 belong to the same MCPTT group which is defined on MCPTT group management server. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group. +2. All members of the MCPTT group belong to the same MCPTT system. +3. The initiating MCPTT client 1 has been provisioned with an MCPTT group that has been designated in the provisioning to be used for imminent peril communications. + +NOTE 1: Alternatively, the client could have been provisioned for imminent peril behaviour on the selected group. + +![Sequence diagram for MCPTT imminent peril group call. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The sequence starts with client 1 initiating a call, followed by a request to the server, internal server steps (affiliate, resolve ID, configure bearers), then the server sends requests to clients 2 and 3, who notify the user. Responses return from clients 2 and 3 through the server back to client 1.](2f587210e4f97c32758c5972e2e83d20_img.jpg) + +Home MCPTT service provider + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note left of MCPTT client 1: 1. initiate imminent peril group call + MCPTT client 1->>MCPTT server: 2. Imminent peril group call request + Note right of MCPTT server: 3. Affiliate user to group + Note right of MCPTT server: 4. Resolve group id + Note right of MCPTT server: 5. Bearer priority configuration + MCPTT server->>MCPTT client 2: 6. Imminent peril group call request + MCPTT server->>MCPTT client 3: 6. Imminent peril group call request + Note right of MCPTT client 2: 7. Notify immediate peril call + Note right of MCPTT client 3: 7. Notify immediate peril call + MCPTT client 2-->>MCPTT server: 8. Imminent peril group call response + MCPTT client 3-->>MCPTT server: 8. Imminent peril group call response + MCPTT server-->>MCPTT client 1: 9. Imminent peril group call response + +``` + +Sequence diagram for MCPTT imminent peril group call. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The sequence starts with client 1 initiating a call, followed by a request to the server, internal server steps (affiliate, resolve ID, configure bearers), then the server sends requests to clients 2 and 3, who notify the user. Responses return from clients 2 and 3 through the server back to client 1. + +**Figure 10.6.2.6.2.1-1: MCPTT imminent peril group call** + +1. The user at the MCPTT client 1 initiates an imminent peril group call. + 2. MCPTT client 1 sends an MCPTT imminent peril group call request towards the MCPTT server. The request contains an indication of the in-progress imminent peril. The MCPTT server records the identity of the MCPTT user that initiated the imminent peril group call until the in-progress imminent peril state is cancelled. Once an imminent peril group call has been initiated, the MCPTT group is considered to be in an in-progress imminent peril state until cancelled. The request may contain an indication of an implicit floor request. + 3. The MCPTT server implicitly affiliates MCPTT client 1 to the imminent peril group if the client is not already affiliated. + 4. MCPTT server checks whether the MCPTT user of MCPTT client 1 is authorized for initiation of imminent peril group calls on the indicated MCPTT group, and if authorized, it resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status, based on the information from group management server. + 5. The MCPTT server configures the priority of the underlying bearers for all participants in the MCPTT group. +- NOTE 2: Successive calls during the in-progress imminent peril state will all receive the adjusted bearer priority. +6. MCPTT server sends the imminent peril group call request towards the MCPTT clients of each of those affiliated MCPTT group members. The request contains an indication of the in-progress imminent peril. + 7. MCPTT users are notified of the incoming imminent peril call. + +8. The receiving MCPTT clients send the MCPTT imminent peril group call response to the MCPTT server to acknowledge the imminent peril call request. For a multicast call, these acknowledgements are not set. +9. The MCPTT server sends the MCPTT imminent peril group call response to the MCPTT user 1 to inform the successful imminent peril call establishment. + +NOTE 3: Step 9 can occur at any time following step 5, and prior to step 10 depending on the conditions to proceed with the imminent peril call. + +MCPTT client 1, MCPTT client 2 and MCPTT client 3 have successfully established media plane for communication. MCPTT floor participant 1, floor participant 2 and floor participant 3 exchange floor control information e.g., MCPTT client 1 receives the floor granted information over the established media plane, while the other MCPTT clients receive floor taken information. MCPTT client 1 indicates to the MCPTT user that the floor is available to send media, while the other MCPTT clients in the imminent peril call will be receiving that media. + +#### 10.6.2.6.2.2 Imminent peril group call upgrade + +The procedure focuses on the case where an authorized MCPTT user is upgrading an MCPTT group call to an imminent peril group call while the MCPTT group call is already in progress. + +Procedures in figure 10.6.2.6.2.2-1 are the signalling control plane procedures for the MCPTT client upgrading an MCPTT group call on an MCPTT group to an imminent peril group call. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 1, MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group. +2. All members of the MCPTT group belong to the same MCPTT system. +3. An MCPTT group call is already in progress. + +![Sequence diagram titled 'MCPTT group call upgrade to an imminent peril group call'. The diagram shows the interaction between MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, and MCPTT client 3. The process starts with a 'Group call already in progress' phase. Then, MCPTT client 1 initiates an imminent peril call (1. User initiates imminent peril call). The MCPTT server performs a 'Bearer priority adjustment' (3. Bearer priority adjustment). The MCPTT server sends an 'MCPTT imminent peril group call request' (4. MCPTT imminent peril group call request) to MCPTT client 2 and MCPTT client 3. MCPTT client 2 and MCPTT client 3 notify the imminent peril status (5. Notify imminent peril status). The MCPTT server sends an 'MCPTT imminent peril group call response' (6. MCPTT imminent peril group call response) to MCPTT client 1. MCPTT client 1 receives the response (7. MCPTT imminent peril group call response).](5152ddc7d77f41ae1eaf931aaac810eb_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note over MCPTT client 1, MCPTT client 3: Group call already in progress + + MCPTT client 1->>MCPTT server: 1. User initiates imminent peril call + Note over MCPTT server: 3. Bearer priority adjustment + MCPTT server->>MCPTT client 2: 4. MCPTT imminent peril group call request + MCPTT server->>MCPTT client 3: 4. MCPTT imminent peril group call request + MCPTT client 2->>MCPTT client 2: 5. Notify imminent peril status + MCPTT client 3->>MCPTT client 3: 5. Notify imminent peril status + MCPTT server->>MCPTT client 1: 6. MCPTT imminent peril group call response + MCPTT client 1->>MCPTT server: 7. MCPTT imminent peril group call response + +``` + +Sequence diagram titled 'MCPTT group call upgrade to an imminent peril group call'. The diagram shows the interaction between MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, and MCPTT client 3. The process starts with a 'Group call already in progress' phase. Then, MCPTT client 1 initiates an imminent peril call (1. User initiates imminent peril call). The MCPTT server performs a 'Bearer priority adjustment' (3. Bearer priority adjustment). The MCPTT server sends an 'MCPTT imminent peril group call request' (4. MCPTT imminent peril group call request) to MCPTT client 2 and MCPTT client 3. MCPTT client 2 and MCPTT client 3 notify the imminent peril status (5. Notify imminent peril status). The MCPTT server sends an 'MCPTT imminent peril group call response' (6. MCPTT imminent peril group call response) to MCPTT client 1. MCPTT client 1 receives the response (7. MCPTT imminent peril group call response). + +Figure 10.6.2.6.2.2-1: MCPTT group call upgrade to an imminent peril group call + +1. The MCPTT user at MCPTT client 1 initiates an imminent peril call. +2. MCPTT client 1 requests the MCPTT server to upgrade the MCPTT group to an in-progress imminent peril state by sending an MCPTT imminent peril group call request. The request may contain an indication of an implicit floor request. +3. The MCPTT server adjusts the priority of the underlying bearer for all participants in the MCPTT group. +4. MCPTT server sends the MCPTT imminent peril group call request towards the MCPTT clients of each of those affiliated MCPTT group members. +5. MCPTT users are notified of the in-progress imminent peril state of the MCPTT group. +6. The receiving MCPTT clients send the MCPTT imminent peril group call response to the MCPTT server to acknowledge the MCPTT imminent peril group call request. For a multicast call, these acknowledgements are not set. +7. The MCPTT server sends the MCPTT imminent peril group call response to the MCPTT user 1 to confirm the upgrade request. + +NOTE: Step 7 can occur at any time following step 4, and prior to step 8 depending on the conditions to proceed with the call. + +MCPTT client 1, MCPTT client 2 and MCPTT client 3 continue with the MCPTT group call, which has been transformed into an imminent peril group call. + +#### 10.6.2.6.2.3 MCPTT in-progress imminent peril group state cancel + +NOTE 1: In Rel-14 and Rel-13 versions of this specification the title of this subclause is "MCPTT imminent peril group call cancel". + +The procedure focuses on the case where an authorized MCPTT user cancels an MCPTT group's in-progress imminent peril state. + +Procedures in figure 10.6.2.6.2.3-1 are the signalling control plane procedures for the MCPTT client cancelling an MCPTT group's in-progress imminent peril state. + +NOTE 2: The end of the imminent peril call does not cancel the MCPTT group's in-progress imminent peril state. It is explicitly cancelled by an authorized user using this procedure. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 1, MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group. +2. All members of the MCPTT group belong to the same MCPTT system. +3. The MCPTT group is in an in-progress imminent peril state and has prioritized bearer support. +4. MCPTT group members have been notified about the MCPTT group's in-progress imminent peril state. +5. MCPTT client 1 previously initiated the in-progress imminent peril. + +![Sequence diagram for MCPTT in-progress imminent peril group state cancel. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The process involves initiating a cancel, adjusting bearer priority, resolving group ID, notifying members, and receiving responses.](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) + +MCPTT service provider + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note left of MCPTT client 1: 1. initiate in-progress imminent peril group state cancel + MCPTT client 1->>MCPTT server: 2. MCPTT in-progress imminent peril group state cancel request + Note right of MCPTT server: 3. Bearer priority adjustment + Note right of MCPTT server: 4. Resolve group id + MCPTT server->>MCPTT client 2: 5. MCPTT in-progress imminent peril group state cancel request + MCPTT server->>MCPTT client 3: 5. MCPTT in-progress imminent peril group state cancel request + Note right of MCPTT client 2: 6. Notify Imminent peril cancel + Note right of MCPTT client 3: 6. Notify Imminent peril cancel + MCPTT client 2->>MCPTT server: 7. MCPTT in-progress imminent peril group state cancel response + MCPTT client 3->>MCPTT server: 7. MCPTT in-progress imminent peril group state cancel response + MCPTT server->>MCPTT client 1: 8. MCPTT in-progress imminent peril group state cancel response + +``` + +Sequence diagram for MCPTT in-progress imminent peril group state cancel. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The process involves initiating a cancel, adjusting bearer priority, resolving group ID, notifying members, and receiving responses. + +**Figure 10.6.2.6.2.3-1: MCPTT in-progress imminent peril group state cancel** + +1. The user at the MCPTT client 1 initiates an in-progress imminent peril group state cancel. +2. MCPTT client 1 sends an MCPTT in-progress imminent peril group state cancel request to the MCPTT server. +3. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required. The MCPTT server cancels/resets the in-progress imminent peril group state. +4. MCPTT server resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status, based upon the information from group management server. +5. The MCPTT server sends an MCPTT imminent peril group state cancel request to the MCPTT group members. +6. MCPTT group members are notified of the in-progress imminent peril group state cancel. +7. The receiving MCPTT group members send the MCPTT in-progress imminent peril group state cancel response to the MCPTT server to acknowledge the MCPTT in-progress imminent peril group state cancel request. For a multicast scenario, these acknowledgements are not set. +8. The MCPTT server sends the MCPTT in-progress imminent peril group state cancel response to the MCPTT user 1 to confirm the MCPTT in-progress imminent peril group state cancel request. + +NOTE 3: Step 8 can occur at any time following step 4, depending on the conditions to proceed with the call. + +### 10.6.2.6.3 MCPTT emergency alert + +**Editor's note: whether the following procedures for emergency alert initiation and emergency alert cancel remain in this specification is FFS.** + +#### 10.6.2.6.3.1 MCPTT emergency alert initiation + +The procedure focuses on the case where an MCPTT client is initiating an MCPTT emergency alert unicast signalling for communicating the alert with the affiliated MCPTT members of that MCPTT group. An MCPTT client in the MCPTT emergency state gains elevated access privilege for all of the MCPTT user's mission critical applications. This procedure will place the MCPTT client in the MCPTT emergency state if the MCPTT client is not already in that state. + +Procedures in figure 10.6.2.6.3.1-1 are the signalling control plane procedures for the MCPTT client initiating an MCPTT emergency alert with an MCPTT group i.e., MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 belong to the same MCPTT group which is defined on MCPTT group management server. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group. +2. All members of the MCPTT group belong to the same MCPTT system. +3. The initiating MCPTT client 1 is affiliated with one or more MCPTT groups. +4. The initiating MCPTT client 1 has been provisioned with an MCPTT group designated as the MCPTT emergency group. + +NOTE 2: Alternatively, the client could have been provisioned for emergency behaviour on the currently selected group. + +5. The initiating MCPTT client 1 may not have carried out an explicit affiliation procedure with the MCPTT group designated as the MCPTT emergency group. + +![Sequence diagram for MCPTT emergency alert. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The process involves initiating an alert, checking authorization, resolving group ID, and notifying members.](9c45844d796e85ae05505870a54e4eb4_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note left of MCPTT client 1: 1. initiate emergency alert + MCPTT client 1->>MCPTT server: 2. MCPTT emergency alert request + Note right of MCPTT server: 3. Check alert authorization + Note right of MCPTT server: 4. Resolve group ID + MCPTT server-->>MCPTT client 1: 5. MCPTT emergency alert response + MCPTT server->>MCPTT client 2: 6. MCPTT emergency alert request + MCPTT server->>MCPTT client 3: 6. MCPTT emergency alert request + Note right of MCPTT client 2: 7. Notify emergency + Note right of MCPTT client 3: 7. Notify emergency + MCPTT server-->>MCPTT client 1: 8. MCPTT emergency alert response + Note right of MCPTT server: 9. Affiliate to group + +``` + +Sequence diagram for MCPTT emergency alert. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The process involves initiating an alert, checking authorization, resolving group ID, and notifying members. + +**Figure 10.6.2.6.3.1-1 MCPTT emergency alert** + +1. The user at the MCPTT client 1 initiates an MCPTT emergency alert. MCPTT client 1 sets its MCPTT emergency state. The MCPTT emergency state is retained by the MCPTT client until explicitly cancelled. +2. MCPTT client 1 requests the MCPTT server to send an MCPTT emergency alert request to the MCPTT group designated as the MCPTT emergency group. +3. MCPTT server checks whether the MCPTT user of MCPTT client 1 is authorized for initiation of MCPTT emergency alerts for the indicated MCPTT group. +4. MCPTT server resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status, based on the information from group management server. +5. The MCPTT server sends the MCPTT emergency alert response to the MCPTT user 1 to confirm the MCPTT emergency alert request. MCPTT group calls made to this MCPTT group by the MCPTT client 1 will be sent as emergency calls until the emergency state on the MCPTT client 1 is cancelled. +6. The MCPTT server sends an MCPTT emergency alert request towards the MCPTT clients of each of those affiliated MCPTT group members. The MCPTT emergency alert request message shall contain the following information: Location, MCPTT ID and MCPTT group ID (i.e., MCPTT user's selected MCPTT group or dedicated MCPTT emergency group, as per MCPTT group configuration) and the MCPTT user's mission critical organization name. If in step 2, the MCPTT client 1 does not include the location information in the MCPTT emergency alert request to the MCPTT server, the MCPTT server acquires the location of user at the MCPTT client 1 from the location management server. If the location is included in step 2, then the MCPTT server acquires the location from MCPTT client 1. +7. MCPTT users are notified of the MCPTT emergency. + +8. For a unicast MCPTT emergency alert, the receiving MCPTT clients send the MCPTT emergency alert response to the MCPTT server to acknowledge the MCPTT emergency alert. For a multicast MCPTT emergency alert, these acknowledgements are not sent unless the MCPTT clients have been configured to do so. +9. The MCPTT server implicitly affiliates MCPTT client 1 to the emergency group if the client is not already affiliated. + +NOTE 3: Sending the emergency alert without making a request to also start an emergency call does not put the group into the in-progress emergency state. + +NOTE 4: Sending the emergency alert does not put the other UEs in the group into an emergency state. + +NOTE 5: The MCPTT client 1 need not initiate a group call. For example, the MCPTT client can be configured to only allow alerts or the MCPTT user can choose not to make an MCPTT emergency group call. + +#### 10.6.2.6.3.2 MCPTT emergency alert cancel + +The procedure focuses on the case where an MCPTT client has initiated an MCPTT emergency alert and entered the emergency state, and wishes to cancel the alert, informing the MCPTT server and other group members of this cancellation. By doing so, the MCPTT client may also request the cancellation of the in-progress emergency state of the group. + +Procedures in figure 10.6.2.6.3.2-1 are the signalling control plane procedures for the MCPTT client cancelling an MCPTT emergency alert with an MCPTT group i.e., MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 belong to the same MCPTT group which is defined on MCPTT group management server. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +Pre-conditions: + +1. The MCPTT client 1 had previously successfully initiated an MCPTT emergency alert. +2. The MCPTT client 1 is still in the emergency state. +3. The initiating MCPTT client 1 has affiliated with the MCPTT group designated as the MCPTT emergency group. + +![Sequence diagram for MCPTT emergency alert cancel. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The process involves client 1 sending a cancel request to the server, the server resolving the group ID, responding to client 1, and then notifying other clients (2 and 3) via the server. Clients 2 and 3 send responses back to the server.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note left of MCPTT client 1: 1. initiate emergency alert cancel + MCPTT client 1->>MCPTT server: 2. MCPTT emergency alert cancel request + MCPTT server->>Group management server: 3. Resolve group ID + MCPTT server-->>MCPTT client 1: 4. MCPTT emergency alert cancel response + MCPTT server->>MCPTT client 2: 5. MCPTT emergency alert cancel request + MCPTT server->>MCPTT client 3: 5. MCPTT emergency alert cancel request + MCPTT client 2->>MCPTT server: 6. Notify emergency alert cancel + MCPTT client 3->>MCPTT server: 6. Notify emergency alert cancel + MCPTT client 2-->>MCPTT server: 7. MCPTT emergency alert cancel response + MCPTT client 3-->>MCPTT server: 7. MCPTT emergency alert cancel response + +``` + +Sequence diagram for MCPTT emergency alert cancel. Lifelines: MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3. The process involves client 1 sending a cancel request to the server, the server resolving the group ID, responding to client 1, and then notifying other clients (2 and 3) via the server. Clients 2 and 3 send responses back to the server. + +**Figure 10.6.2.6.3.2-1 MCPTT emergency alert cancel** + +1. The user at the MCPTT client 1 initiates an MCPTT emergency alert cancel. + +NOTE 2: The MCPTT emergency alert cancel request carries an indication to also request that the in-progress emergency is to be cancelled. The MCPTT server can accept or deny the request to cancel the in-progress emergency state of the group as a whole, separately from accepting or denying the request to cancel the emergency alert at MCPTT client 1. Additionally, an authorized user can cancel either or both the in-progress emergency state of the group and the initiator's local MCPTT emergency state. + +2. MCPTT client 1 requests the MCPTT server to send an MCPTT emergency alert cancel to the MCPTT group to which MCPTT client 1 had previously sent the emergency alert. +3. MCPTT server resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status, based on the information from group management server. +4. The MCPTT server sends the MCPTT emergency alert cancel response to the MCPTT client 1 to confirm the MCPTT emergency alert cancel request. MCPTT client 1 resets its emergency state. +5. The MCPTT server sends an MCPTT emergency alert cancel request towards the MCPTT clients of each of those affiliated MCPTT group members. +6. MCPTT users are notified of the MCPTT emergency alert cancellation of MCPTT client 1. +7. For a unicast MCPTT emergency alert cancel, the receiving MCPTT clients send the MCPTT emergency alert cancel response to the MCPTT server to acknowledge the MCPTT emergency alert cancel. For a multicast MCPTT emergency alert cancel, these acknowledgements are not sent unless the MCPTT clients have been configured to do so. + +### 10.6.2.6.3.3 Entering MCPTT emergency alert area + +**Editor's Note:** MCPTT emergency alert triggered by MCPTT client locally which stores the predefined area is another possible solution. How to define this procedure and how to combine the two solutions is FFS. + +The procedure focuses on the case where an MCPTT service emergency alert to be triggered when an MCPTT UE moves into a predefined area. This procedure will place the MCPTT client in the MCPTT emergency state if the MCPTT client is not already in that state. + +Procedures in figure 10.6.2.6.3.3-1 are the signalling control plane procedures for the MCPTT server triggers an MCPTT emergency alert with an MCPTT group i.e., MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 belong to the same MCPTT group which is defined on MCPTT group management server. + +NOTE: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 2 and MCPTT client 3 affiliated to that MCPTT group. +2. All members of the MCPTT group belong to the same MCPTT system. +3. An area in which the MCPTT client should send emergency alert is pre-defined in MCPTT server. + +![Sequence diagram illustrating the procedure for entering an MCPTT emergency alert area. The diagram shows interactions between MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, and MCPTT client 3. The steps are: 1. MCPTT server acquires location info from client 1; 2. MCPTT server checks if client 1 is in a predefined area; 3. MCPTT server sends an emergency alert area trigger to client 1; 4. MCPTT client 1 notifies the user; 5. MCPTT client 1 initiates the emergency alert procedure.](8a0a9aa5fac5d73eefb772afd44649f6_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant Group management server + participant MCPTT client 2 + participant MCPTT client 3 + + Note right of MCPTT server: 1. Acquire latest location information of user at MCPTT client 1 + Note right of MCPTT server: 2. Check whether MCPTT client 1 has moved into a predefined area + MCPTT server->>MCPTT client 1: 3. MCPTT emergency alert area trigger + Note left of MCPTT client 1: 4. Notify user + Note over MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, MCPTT client 3: 5. MCPTT emergency alert initiation procedure +``` + +Sequence diagram illustrating the procedure for entering an MCPTT emergency alert area. The diagram shows interactions between MCPTT client 1, MCPTT server, Group management server, MCPTT client 2, and MCPTT client 3. The steps are: 1. MCPTT server acquires location info from client 1; 2. MCPTT server checks if client 1 is in a predefined area; 3. MCPTT server sends an emergency alert area trigger to client 1; 4. MCPTT client 1 notifies the user; 5. MCPTT client 1 initiates the emergency alert procedure. + +**Figure 10.6.2.6.3.3-1 Entering MCPTT emergency alert area** + +1. MCPTT server acquires the latest location information of user at MCPTT client 1 from location management server as described in subclause 10.9.3.6 in 3GPP TS 23.280[16]. +2. MCPTT server checks whether MCPTT client 1 has moved into a predefined area. +3. If so, MCPTT server sends an MCPTT emergency alert area trigger to MCPTT client 1 to notify that it has moved in to the area in potential danger. +4. MCPTT client 1 notifies the MCPTT user about the MCPTT emergency alert area. +5. MCPTT client 1 initiates MCPTT emergency alert procedure as described in 10.6.2.6.3.1. + +## 10.6.2.7 Location of current talker + +Figure 10.6.2.7-1 shows the high level procedure to for MCPTT service to provide the location information about the current talking user to all the receiving MCPTT users. + +Precondition: + +1. There is on-going group call involving MCPTT client 1 and MCPTT client 2. +2. MCPTT client 1 is the current talking user. +3. MCPTT server has obtained the location information of MCPTT client 1 according to subclause 10.9 in 3GPP TS 23.280 [16]. + +![Sequence diagram showing the interaction between MCPTT server, MCPTT client 2, and MCPTT client 1 for providing location information. Step 1: MCPTT client 1 acquires the floor for transmission. Step 2: MCPTT server checks users' privacy policy for sharing location information. Step 3: MCPTT server provides the location information of the current talker to MCPTT client 2.](070352b751dd0711b8ac6ddfa6df1d98_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT server + Note right of MCPTT client 1: 1.MCPTT client 1 acquires the floor for transmission + Note left of MCPTT server: 2.Check users' privacy policy for sharing location information + Note right of MCPTT server: 3.Provides the location information of the current talker + +``` + +Sequence diagram showing the interaction between MCPTT server, MCPTT client 2, and MCPTT client 1 for providing location information. Step 1: MCPTT client 1 acquires the floor for transmission. Step 2: MCPTT server checks users' privacy policy for sharing location information. Step 3: MCPTT server provides the location information of the current talker to MCPTT client 2. + +**Figure 10.6.2.7-1: Providing location information of the current talker** + +1. MCPTT client 1 gets the floor to transmit voice media. +2. MCPTT server checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in Annex A.3) of the current talking MCPTT user to decide if the location information of MCPTT client 1 can be provided to other MCPTT users on the call. MCPTT server acquires the location of the current talker from the location management server as described in subclause 10.9.3.6 in 3GPP TS 23.280[16]. Optionally, the MCPTT server acquires the location of the current talker directly from the floor request received from MCPTT client 1 in step 1. +3. MCPTT server provides the location information of MCPTT client 1 to MCPTT client 2. Optionally, the location information may be provided in the floor taken message sent to MCPTT client 2 according to subclause 10.9.1.3.1. + +## 10.6.2.8 Temporary group call – user regroup + +### 10.6.2.8.1 General + +NOTE: This procedure has no security solution in 3GPP TS 33.180 [19]. + +The temporary group call performed by user regroup can be initiated by an authorized user inviting a list of MCPTT users. The group ID for this temporary group may be obtained during call setup, or prior to call setup. The users being invited are implicitly affiliated to this temporary group during call setup, and can be implicitly de-affiliated with the release of the group call. The group call is terminated by either the MCPTT server releasing the call or the authorized user ending the call. The release of the call may be followed by release of the temporary group ID. + +### 10.6.2.8.2 Group call setup + +Figure 10.6.2.8.2-1 below illustrates the group call setup procedure initiated by an authorized user. + +Pre-conditions: + +1. The authorized user is aware of the MCPTT users who will be invited to the temporary group call. + +2. The MCPTT server is allowed to perform implicit affiliation/de-affiliation operation for this type of group call based on relevant configurations. +3. The MCPTT users being invited have relevant configurations that allow them to be implicitly affiliated for this type of group call. +4. A group ID may be available prior to group call setup. + +![Sequence diagram illustrating the group call setup for a temporary group call with user regrouping. The diagram shows interactions between MCPTT Client 1 (Authorized User), MCPTT Server, MCPTT Client 2, and MCPTT Client 3. The steps are: 1. Group call request from Client 1 to Server; 2. Authorize from Server; 3. Implicit affiliation user to group from Server; 4a. Group call request from Server to Client 2; 5a. Notify temporary group call from Client 2; 4b. Group call request from Server to Client 3; 5b. Notify temporary group call from Client 3; 6a. Group call response from Client 2 to Server; 6b. Group call response from Client 3 to Server; 7. Group call response from Server to Client 1; 8. Media plane and floor control establishment (a horizontal bar spanning all participants).](f7b2cf9e1b71dc4f900f3810646d3903_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCPTT Client 1 (Authorized User) + participant S as MCPTT Server + participant C2 as MCPTT Client 2 + participant C3 as MCPTT Client 3 + + Note right of S: 2. Authorize + Note right of S: 3. Implicit affiliation user to group + + C1->>S: 1. Group call request + S-->>C2: 4a. Group call request + C2-->>S: 5a. Notify temporary group call + S-->>C3: 4b. Group call request + C3-->>S: 5b. Notify temporary group call + C2-->>S: 6a. Group call response + C3-->>S: 6b. Group call response + S-->>C1: 7. Group call response + Note over C1,S,C2,C3: 8. Media plane and floor control establishment + +``` + +Sequence diagram illustrating the group call setup for a temporary group call with user regrouping. The diagram shows interactions between MCPTT Client 1 (Authorized User), MCPTT Server, MCPTT Client 2, and MCPTT Client 3. The steps are: 1. Group call request from Client 1 to Server; 2. Authorize from Server; 3. Implicit affiliation user to group from Server; 4a. Group call request from Server to Client 2; 5a. Notify temporary group call from Client 2; 4b. Group call request from Server to Client 3; 5b. Notify temporary group call from Client 3; 6a. Group call response from Client 2 to Server; 6b. Group call response from Client 3 to Server; 7. Group call response from Server to Client 1; 8. Media plane and floor control establishment (a horizontal bar spanning all participants). + +**Figure 10.6.2.8.2-1: Group call setup for temporary group call – user regroup** + +1. MCPTT client 1 (of an authorized user) initiates the group call by sending the group call request to the MCPTT server. +2. The MCPTT server checks whether the MCPTT client 1 can initiate the group call. + +**Editor's note:** It is FFS how the MCPTT server obtains the group ID for the temporary group call. + +3. The MCPTT server implicitly affiliates the clients to the group. +4. The MCPTT server sends the group call requests towards the MCPTT clients. The message contains the temporary group indicator. +5. The receiving MCPTT clients are notified about the incoming group call. The users verify they are authorized to participate in the temporary group call. +6. The receiving MCPTT clients accept the group call requests and send group call responses to the MCPTT server. This response may contain an acknowledgement. The conditions for sending acknowledgement may be based on configuration. +7. The MCPTT server sends the group call response to MCPTT client 1 through the signalling path to inform about successful call establishment. + +**NOTE:** Step 7 can occur at any time following step 6a, and prior to step 8 depending on the conditions to proceed with the call. + +8. MCPTT client 1, client 2 and client 3 establish media plane and floor control resources. + +### 10.6.2.8.3 Group call end (by authorized user) + +Figure 10.6.2.8.3-1 below illustrates the group call end requested by the authorized user. + +Pre-conditions: + +1. The MCPTT server is allowed to perform implicit affiliation/de-affiliation operation for this type of group call. +2. MCPTT users on MCPTT client 1, client 2 and client 3 are already part of the ongoing temporary group call. + +![Sequence diagram for Figure 10.6.2.8.3-1: Group call end (by authorized user) for temporary group call – user regroup. The diagram shows the interaction between MCPTT Client 1 (Authorized User), Group Management Server, MCPTT Server, MCPTT Client 2, and MCPTT Client 3. The process involves a release request, authorization, group ID resolution, notification of members, responses, resource release, and optional de-affiliation.](869c547c11ac7e123c51aba22289f2cd_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MCPTT Client 1 (Authorized User) + participant GMS as Group Management Server + participant Server as MCPTT Server + participant Client2 as MCPTT Client 2 + participant Client3 as MCPTT Client 3 + + Note left of Client1: Pre-conditions: 1. MCPTT server allowed for implicit affiliation/de-affiliation. 2. Clients 1, 2, 3 are part of ongoing temporary group call. + + Client1->>Server: 1. Group call release request + Server-->>GMS: 2. Authorize + Note right of GMS: 3. Resolve group ID (optional) + Server->>Client2: 4a. Group call release request + Server->>Client3: 4b. Group call release request + Note right of Client2: 5a. Notify group call release + Note right of Client3: 5b. Notify group call release + Client2->>Server: 6a. Group call release response + Client3->>Server: 6b. Group call release response + Server->>Client1: 7. Group call release response + Note right of Server: 8. Releasing floor control and media plane resources + Note right of Server: 9. Implicit de-affiliation user to group and release of group ID (optional) + +``` + +Sequence diagram for Figure 10.6.2.8.3-1: Group call end (by authorized user) for temporary group call – user regroup. The diagram shows the interaction between MCPTT Client 1 (Authorized User), Group Management Server, MCPTT Server, MCPTT Client 2, and MCPTT Client 3. The process involves a release request, authorization, group ID resolution, notification of members, responses, resource release, and optional de-affiliation. + +**Figure 10.6.2.8.3-1: Group call end (by authorized user) for temporary group call – user regroup** + +1. The MCPTT client 1 (of an authorized user) requests to end the group call by sending group call release request to MCPTT server. +2. The MCPTT server checks whether the MCPTT client 1 can end the group call. +3. In this optional step the MCPTT server resolves the MCPTT group ID to determine the members of the group based upon the information from group management server. +4. The MCPTT server sends group call release requests to MCPTT clients of the group members. +5. The MCPTT clients are notified about the group call release. +6. The MCPTT clients send the group call release responses to MCPTT server to acknowledge the group call release. For a multicast call scenario, these acknowledgements are not sent. +7. The MCPTT server sends the group call release response to MCPTT client 1 to confirm the call is released. + +NOTE: Step 7 can occur at any time following step 6a, and prior to step 8 depending on the conditions to release the call. + +8. MCPTT client 1, client 2 and client 3 released the floor control and media plane resources associated with the group call. +9. MCPTT server implicitly de-affiliates MCPTT clients to the group. The group management server releases the temporary group ID. This step is optional. + +## 10.6.3 Off-network group call + +### 10.6.3.1 General + +Off-network group calls can use pre-defined configuration information provided to MCPTT clients prior to the off-network group call or configuration information that is transmitted to MCPTT clients during group call setup or late entry procedures. + +If off-network group configuration information is pre-defined (e.g. codec to be used) and provided to the MCPTT clients prior to the off-network group call (e.g. as part of group metadata), the MCPTT client will be able to participate in the off-network group call without needing to follow the group call setup or late joining procedures as they will be able to receive the media and signalling without the need for the announcement or invitation. + +If off-network group configuration information is not pre-defined or provided, call parameters need to be transmitted to MCPTT clients via group call announcement or invitation. + +NOTE: When the MCPTT client receives a message that is not addressed to either its MCPTT ID or to any MCPTT group of which the MCPTT client is an affiliated group member, the MCPTT client ignores the message. + +### 10.6.3.2 Information flows for group call in off-network + +#### 10.6.3.2.1 Group call announcement + +Table 10.6.3.2.1-1 describes the information flow for the group call announcement from the MCPTT client to other MCPTT clients. + +**Table 10.6.3.2.1-1: Group call announcement** + +| Information Element | Status | Description | +|---------------------------|--------|-------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Media type | M | Type of the media to be used for the call | +| Media codec | M | The media codec to be used for the call | +| Multi-cast port | M | Multicast port number for media | +| Floor control port number | M | Port number for floor control protocol | +| Announcement period | M | Period of the group call announcement | +| Encryption parameters | O | Encryption parameters to be used for the call, if the call is to be encrypted | +| Confirm mode indicator | O | Indicates whether the MCPTT group call is to be confirmed | +| Emergency indicator | O | Indicates that the MCPTT group call is an MCPTT emergency call | +| Imminent peril indicator | O | Indicates that the MCPTT group call is an MCPTT imminent peril call | + +##### 10.6.3.2.2 MCPTT upgrade to emergency call + +Table 10.6.3.2.2-1 describes the information flow for the MCPTT upgrade to emergency call from the MCPTT client to other MCPTT clients. + +**Table 10.6.3.2.2-1: MCPTT upgrade to emergency call** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------| +| MCPTT ID | M | The identity of the upgrading party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | + +##### 10.6.3.2.3 MCPTT emergency group state cancel + +Table 10.6.3.2.3-1 describes the information flow for the MCPTT emergency group state cancel from the MCPTT client to other MCPTT clients. + +NOTE: In Rel-14 and Rel-13 versions of this specification the name of this information flow is "MCPTT emergency group cancel". + +**Table 10.6.3.2.3-1: MCPTT emergency group state cancel** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID which emergency state is to be cancelled | + +##### 10.6.3.2.4 Response + +Table 10.6.3.2.4-1 describes the information flow for the response. + +**Table 10.6.3.2.4-1: Response** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------| +| MCPTT ID | M | The identity of the called party | + +##### 10.6.3.2.5 MCPTT emergency alert announcement + +Table 10.6.3.2.5-1 describes the information flow for the MCPTT emergency alert announcement from the MCPTT client to the other MCPTT clients. + +**Table 10.6.3.2.5-1: MCPTT emergency alert announcement** + +| Information Element | Status | Description | +|---------------------|--------|--------------------------------------------------------| +| MCPTT ID | M | The identity of the alerting MCPTT user | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | +| Location | O | The alerting client's location, if known | +| Organization name | M | The alerting user's mission critical organization name | + +##### 10.6.3.2.6 MCPTT emergency alert cancel announcement + +Table 10.6.3.2.6-1 describes the information flow for the MCPTT emergency alert cancel announcement from the MCPTT client to other MCPTT clients. + +**Table 10.6.3.2.6-1: MCPTT emergency alert cancel announcement** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling MCPTT user | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | + +##### 10.6.3.2.7 MCPTT upgrade to imminent peril call + +Table 10.6.3.2.7-1 describes the information flow for the MCPTT upgrade to imminent peril call from the MCPTT client to other MCPTT clients. + +**Table 10.6.3.2.7-1: MCPTT upgrade to imminent peril call** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------| +| MCPTT ID | M | The identity of the upgrading party | +| MCPTT group ID | M | The MCPTT group ID of the group to be upgraded | + +##### 10.6.3.2.8 MCPTT imminent peril group call cancel + +Table 10.6.3.2.8-1 describes the information flow MCPTT imminent peril group call cancel from the MCPTT client to other MCPTT clients. + +**Table 10.6.3.2.8-1: MCPTT imminent peril group call cancel** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the imminent peril is to be cancelled | + +#### 10.6.3.3 Group call setup + +The flow in figure 10.6.3.3-1 illustrates the control plane procedures for MCPTT group call establishment for off-network. The procedure describes how an MCPTT client initiates an MCPTT group call with other MCPTT client within the off-network radio coverage and how the group call is established. + +Pre-conditions: + +- It is assumed that information for **ProSe** direct communications corresponding to the mappings of MCPTT group ID and **ProSe** Layer-2 Group ID (see subclause 8.1.3.2 in 3GPP TS 23.280 [16]) are pre-configured; +- It is assumed that a multicast IP address and port for the call setup signalling are pre-configured; +- All messages exchanged between the MCPTT clients for the MCPTT group follows **ProSe** direct communications as defined in 3GPP **TS 23.303** [7]; and +- The MCPTT users of MCPTT client 1, 2 and 3 belong to the same MCPTT group. + +![Sequence diagram for Off-network group call setup. Lifelines: MCPTT client 1 (Call Originator), MCPTT client 2, and MCPTT client 3. The sequence starts with a 'Group call announcement' from client 1 to clients 2 and 3. Clients 2 and 3 then send 'Setting parameters for media plane' messages. Clients 2 and 3 then send 'Response' messages back to client 1. Finally, a 'checking participants' block is shown at the bottom.](69edc2887e907309499ac95b47ab6905_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 (Call Originator) + participant MCPTT client 2 + participant MCPTT client 3 + Note right of MCPTT client 1: 1. Group call announcement + MCPTT client 1->>MCPTT client 2: 1. Group call announcement + MCPTT client 1->>MCPTT client 3: 1. Group call announcement + Note right of MCPTT client 2: 2. Setting parameters for media plane + MCPTT client 2->>MCPTT client 1: 2. Setting parameters for media plane + Note right of MCPTT client 3: 2. Setting parameters for media plane + MCPTT client 3->>MCPTT client 1: 2. Setting parameters for media plane + Note right of MCPTT client 2: 3. Response + MCPTT client 2->>MCPTT client 1: 3. Response + Note right of MCPTT client 3: 3. Response + MCPTT client 3->>MCPTT client 1: 3. Response + Note right of MCPTT client 1: 4. checking participants + Note left of MCPTT client 1: 4. checking participants + +``` + +Sequence diagram for Off-network group call setup. Lifelines: MCPTT client 1 (Call Originator), MCPTT client 2, and MCPTT client 3. The sequence starts with a 'Group call announcement' from client 1 to clients 2 and 3. Clients 2 and 3 then send 'Setting parameters for media plane' messages. Clients 2 and 3 then send 'Response' messages back to client 1. Finally, a 'checking participants' block is shown at the bottom. + +**Figure 10.6.3.3-1: Off-network group call setup** + +- MCPTT client 1 as the group call originator sends group call announcement message to the group. This message contains the following parameters such as MCPTT group ID, group call originator identity, media type, media codec, multicast port number for media, port number for floor control protocol, period of group call announcement, and any encryption key for the media encryption if needed, and optionally confirm mode indication. + +NOTE 1: The group call announcement includes at least one common set of parameters and values for media transfer. Additional values per parameter will not be prohibited for the better user experience. + +NOTE 2: By using the **ProSe** Layer-2 Group ID mapping with the MCPTT group ID, **ProSe** layer ensures that the messages sent for the corresponding MCPTT group are only received by its group's members. + +- MCPTT client 2, 3 join the group call. The MCPTT clients configure the parameters for media delivery by making use of the received parameters in group call announcement. +- MCPTT client 2, 3 may send the response message to the group when the group call announcement from originator includes confirm mode indication. This message contains MCPTT ID. +- MCPTT client 2, 3 recognize the group call originator through the group call announcement and MCPTT client 1 checks the participants of the group call through the received response message. + +NOTE 3: Due to the movement of the participants (in and out of the radio coverage) during the off-network group call, the group call announcement message including parameters for media delivery is periodically sent. + +NOTE 4: The participating MCPTT clients do not need to respond to the periodic group call announcement. + +#### 10.6.3.4 Passive join to group call + +Figure 10.6.3.4-1 illustrates the control plane procedures for the passive MCPTT client to join the on-going MCPTT group call. The passive MCPTT client does not initiate to establish an MCPTT group call, but receives the group call announcement to be transferred periodically. When receiving the announcement message with parameters for media transfer, the passive MCPTT client configures the parameter to receive the voice and joins the announced MCPTT group call. + +This procedure happens after the MCPTT group call is established. The group call announcement including the parameters for the media transfer has been performed periodically, in order for the MCPTT client later to join the MCPTT group call. + +The MCPTT client 4 enters the coverage of the MCPTT group call lately. + +![Sequence diagram illustrating the passive join to a group call. Four lifelines are shown: MCPTT client 1, MCPTT client 2, MCPTT client 3, and MCPTT client 4. The process starts with 'Group call establishment' followed by 'Periodic group call announcement' from client 2. Client 4 sends an 'Entry' message. Client 2 sends a '1. Periodic group call announcement' to client 4. Client 4 responds with '2. Setting parameters' and '3. Response'. Client 2 then sends '4. Floor taken' to client 4. Finally, a 'Periodic group call announcement' is shown from client 2.](d3ca266c298aeb34b019960c6c36f187_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT client 3 + participant MCPTT client 4 + + Note over MCPTT client 1, MCPTT client 3: Group call establishment + Note over MCPTT client 1, MCPTT client 3: Periodic group call announcement + + MCPTT client 4->>MCPTT client 2: Entry + Note right of MCPTT client 4: 2. Setting parameters + + MCPTT client 2->>MCPTT client 4: 1. Periodic group call announcement + MCPTT client 4-->>MCPTT client 2: 3. Response + MCPTT client 2-->>MCPTT client 4: 4. Floor taken + + Note over MCPTT client 1, MCPTT client 3: Periodic group call announcement + +``` + +Sequence diagram illustrating the passive join to a group call. Four lifelines are shown: MCPTT client 1, MCPTT client 2, MCPTT client 3, and MCPTT client 4. The process starts with 'Group call establishment' followed by 'Periodic group call announcement' from client 2. Client 4 sends an 'Entry' message. Client 2 sends a '1. Periodic group call announcement' to client 4. Client 4 responds with '2. Setting parameters' and '3. Response'. Client 2 then sends '4. Floor taken' to client 4. Finally, a 'Periodic group call announcement' is shown from client 2. + +**Figure 10.6.3.4-1: Passive join to group call** + +1. MCPTT client 2 sends the group call announcement message. This message contains parameters such as MCPTT group ID, group call originator identity, media type, media codec, multicast port number for media, port number for floor control protocol, any encryption key for the media encryption if needed, and optionally confirm mode indication. + +NOTE 1: The group call announcement includes at least one common set of parameters and values for media transfer. Additional values per parameter will not be prohibited for the better user experience. + +2. MCPTT client 4 configures the parameters for media transfer by making use of the received parameters in group call announcement. +3. MCPTT client 4 may send the response message to the group when the periodic group call announcement includes confirm mode indication. This message contains the MCPTT ID. +4. MCPTT client 1, 2, 3 check through the received response message that the MCPTT client 4 joins the group call. The MCPTT client 2, as the floor control arbitrator, may send a floor taken message. + +NOTE 2: Due to the movement of the participants (in and out of the radio coverage) during the off-network group call, the group call announcement message including parameters for media delivery is periodically sent. + +NOTE 3: The participating MCPTT clients do not need to respond to the periodic group call announcement. + +#### 10.6.3.5 Join to ongoing group call when new entry member initiates the call with on-going group call id + +Figure 10.6.3.5-1 illustrates the control plane procedures for an MCPTT client to join an on-going MCPTT group call. When entering the coverage of on-going group call, new MCPTT client may send group call setup announcement message with on-going group call id. Upon receiving the group call setup announcement, the MCPTT client as a + +participant of on-going MCPTT group call sends parameters for media transfer to the newly entered MCPTT client (entrant) to join the on-going MCPTT group call. When receiving the parameters for media transfer of on-going MCPTT group call, the MCPTT client configures the parameters to receive the voice and becomes the participant of the on-going MCPTT group call. + +![Sequence diagram showing the late entry join process for MCPTT clients 1, 2, 3, and 4. The diagram illustrates the interaction between the new client (MCPTT client 4) and the existing participants (MCPTT client 1, 2, 3) to join an ongoing group call.](53f1f7d17b3e7aae62169c41d2a88a77_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT client 3 + participant MCPTT client 4 + Note over MCPTT client 1, MCPTT client 3: On-going group call + Note right of MCPTT client 4: 1. Entry + MCPTT client 4->>MCPTT client 1: 2. Group call setup announcement + MCPTT client 1->>MCPTT client 4: 3. Announcement of On-going call media parameters + MCPTT client 4-->>MCPTT client 1: 4. OK + Note right of MCPTT client 4: 5. Setting parameters + Note over MCPTT client 1, MCPTT client 3: On-going group call + +``` + +Sequence diagram showing the late entry join process for MCPTT clients 1, 2, 3, and 4. The diagram illustrates the interaction between the new client (MCPTT client 4) and the existing participants (MCPTT client 1, 2, 3) to join an ongoing group call. + +**Figure 10.6.3.5-1: Late entry join when receiving MCPTT group call announcement with on-going MCPTT group ID** + +1. MCPTT client 4 enters the coverage of the on-going MCPTT group call. +2. The new entry of MCPTT client 4 sends group call setup announcement with MCPTT group call id. +3. MCPTT client 1 as a participant of on-going MCPTT group call acknowledges that on-going MCPTT group call exists with MCPTT group call id sent by MCPTT client 4 and sends parameters for media transfer to MCPTT client 4. +4. MCPTT client 4 may send a response message. +5. MCPTT client 4 sets the parameters for media delivery in the on-going MCPTT group call. + +MCPTT client 4 joins and becomes participants of the on-going MCPTT group call. + +#### 10.6.3.6 Immediate group call announcement to join an ongoing group call + +Figure 10.6.3.6-1 illustrates the control plane procedures for an MCPTT client to immediately join an on-going MCPTT group call. Upon the detection of a new entrant, the MCPTT client that is the current talker (floor arbitrator) immediately sends the group call announcement. When receiving the group call announcement message with parameters for media transfer, that MCPTT client configures the parameters to receive the voice and joins the on-going MCPTT group call. + +Pre-conditions: + +- 1. There is on-going group call. MCPTT client 1 is the current talker and therefore the floor arbitrator. + +![Sequence diagram showing the interaction between four MCPTT clients (1, 2, 3, 4) for joining an ongoing group call. The sequence starts with MCPTT client 4 sending an 'Entry' message. MCPTT client 1 detects the new entrant and sends a 'Group call announcement' to clients 2, 3, and 4. Client 4 responds with 'OK'. Client 4 then proceeds with 'Setting parameters'. Finally, the diagram shows the state as 'On-going group call (MCPTT client 1 is current talker – floor arbitrator)'.](573c8f9e728e343b6864e1070c14b8cf_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT client 3 + participant MCPTT client 4 + Note right of MCPTT client 4: 1. Entry + Note over MCPTT client 1, MCPTT client 3: 2. New entrant is detected + MCPTT client 1->>MCPTT client 2: 3. Group call announcement + MCPTT client 1->>MCPTT client 3: 3. Group call announcement + MCPTT client 1->>MCPTT client 4: 3. Group call announcement + Note right of MCPTT client 4: 4. OK + Note right of MCPTT client 4: 5. Setting parameters + Note over MCPTT client 1, MCPTT client 3: 6. On-going group call (MCPTT client 1 is current talker – floor arbitrator) + +``` + +Sequence diagram showing the interaction between four MCPTT clients (1, 2, 3, 4) for joining an ongoing group call. The sequence starts with MCPTT client 4 sending an 'Entry' message. MCPTT client 1 detects the new entrant and sends a 'Group call announcement' to clients 2, 3, and 4. Client 4 responds with 'OK'. Client 4 then proceeds with 'Setting parameters'. Finally, the diagram shows the state as 'On-going group call (MCPTT client 1 is current talker – floor arbitrator)'. + +**Figure 10.6.3.6-1: Immediate group call announcement to join an ongoing group call** + +- 1. MCPTT client 4 enters the coverage of the on-going MCPTT group call. +- 2. The entry of MCPTT client 4 is detected by the current participants. +- 3. Since MCPTT client 1 is the current talker (floor arbitrator), MCPTT client 1 immediately sends the group call announcement with the call parameters to the group. +- 4. MCPTT client 4 may send a response message. +- 5. MCPTT client 4 sets the parameters for the group call. +- 6. All participants are now considered part of the on-going group call. + +#### 10.6.3.7 Group call release due to inactivity + +If the on-going MCPTT group call is inactive for a specific duration, the participating MCPTT clients release the MCPTT group call by themselves. + +NOTE: Inactivity time can be set according to the policy of MCPTT service provider. + +#### 10.6.3.8 Broadcast group call + +Group call on group-broadcast group and user-broadcast group are handled without distinction in off-network. + +Figure 10.6.3.8.1-1 illustrates the control plane procedures for broadcast group call in off-network. + +![Sequence diagram illustrating a broadcast group call in off-network. Three MCPTT clients (1, 2, and 3) are shown. Client 1 (Call Originator) initiates the process. The sequence consists of three main steps: 1. Group call setup, 2. Media transmission (indicated by a large blue arrow from Client 1 to Client 3), and 3. Group call release.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 (Call Originator) + participant MCPTT client 2 + participant MCPTT client 3 + Note over MCPTT client 1, MCPTT client 3: 1. Group call setup + Note over MCPTT client 1, MCPTT client 3: 2. Media transmission + Note over MCPTT client 1, MCPTT client 3: 3. Group call release + +``` + +Sequence diagram illustrating a broadcast group call in off-network. Three MCPTT clients (1, 2, and 3) are shown. Client 1 (Call Originator) initiates the process. The sequence consists of three main steps: 1. Group call setup, 2. Media transmission (indicated by a large blue arrow from Client 1 to Client 3), and 3. Group call release. + +**Figure 10.6.3.8.1-1: Broadcast group call in off-network** + +1. An authorized MCPTT client 1 initiates broadcast group call setup as described in subclause 10.6.3.3. The group call announcement message includes the indication of broadcast group call. + 2. The MCPTT client 1 initiating broadcast group call starts to transmit media. +- NOTE: Other clients of group member are not allowed to transmit media in broadcast group call. +3. The broadcast group call is released as described in subclause 10.6.3.7. + +#### 10.6.3.9 Emergency and imminent peril procedures + +##### 10.6.3.9.1 Emergency group call + +The off-network emergency group call is a special case of off-network (non-emergency) group call as defined in subclauses 10.6.3.2, 10.6.3.3, 10.6.3.4, 10.6.3.5, 10.6.3.6 and 10.6.3.7. The following are modifications to the aforementioned subclauses to support MCPTT emergency group calls: + +- As a pre-condition, the client initiating the emergency call has previously been provisioned with an MCPTT group designated as the MCPTT emergency group. The MCPTT client initiates MCPTT emergency group calls on this group. Alternatively, the MCPTT client could have been provisioned for emergency behaviour on the selected MCPTT group. +- The group call announcement contains an indication that the MCPTT group call is to be an MCPTT emergency call regardless of whether or not the MCPTT client is in call. Group call participants learn of the MCPTT group's in-progress emergency state from the indication. +- Every call initiated by the MCPTT client will be an emergency call while the MCPTT client is in MCPTT emergency state. +- The MCPTT client enters the MCPTT emergency state when initiating an MCPTT emergency call or MCPTT emergency alert. Only the MCPTT user of the MCPTT client can clear the client's local MCPTT emergency state. +- The MCPTT group in-progress emergency state is cancelled when the call ends. +- The MCPTT user who initiated an emergency call, or upgraded a group call to an emergency call, or an authorized user, may cancel the in-progress emergency state with an MCPTT emergency group state cancel message. The message is sent to the call participants. +- When the MCPTT group is no longer in the in-progress emergency state, every client returns its default value of **ProSe** Per Packet Priority. + +- An MCPTT group call in-progress is upgraded to an emergency group call when the periodic group call announcement contains the emergency indicator. +- The value of **ProSe** Per Packet Priority is upgraded according to emergency state of MCPTT group call. +- An MCPTT group call becoming an emergency group call does not affect the state of other MCPTT call(s) in the client. +- The MCPTT group remains in the in-progress emergency state until the emergency group call ends or the in-progress emergency state is cancelled. + +##### 10.6.3.9.2 MCPTT imminent peril + +The off-network imminent peril group call is a special case of off-network (non-imminent peril) group call as defined in subclauses 10.6.3.2, 10.6.3.3, 10.6.3.4, 10.6.3.5, 10.6.3.6 and 10.6.3.7. The following are modifications to the aforementioned subclauses to support MCPTT imminent peril calls: + +- As a pre-condition, the user initiating the imminent peril call has previously an MCPTT group to be used as the MCPTT imminent peril group. The MCPTT client initiates MCPTT imminent peril group calls on this group. +- The group call announcement contains an indication that the MCPTT group call is to be an MCPTT imminent peril call. Group call participants learn of the MCPTT group in-progress imminent peril condition from the indication. +- The MCPTT group in-progress imminent peril state is considered cancelled when the call ends. +- The originating MCPTT user of the in-progress imminent peril or an authorized user may cancel the in-progress imminent peril state with an MCPTT imminent peril group cancel. The message is sent to the call participants. +- When the MCPTT in-progress imminent peril is no longer in the in-progress imminent peril state, every MCPTT client returns its bearer to the priority it had prior to the in-progress imminent peril state. +- An MCPTT upgrade to imminent peril call is used to upgrade an MCPTT group call already in progress. The message is sent to all call participants so that they are aware of the in-progress imminent peril. +- The bearer is upgraded by all participants for the MCPTT group call already in progress when the MCPTT group call is upgraded to in-progress imminent peril state. +- An MCPTT imminent peril call puts the MCPTT group into the in-progress imminent peril state. + +##### 10.6.3.9.3 MCPTT emergency alert + +**Editor's note: whether the following procedures for emergency alert initiation and emergency alert cancel remain in this specification is FFS.** + +###### 10.6.3.9.3.1 MCPTT emergency alert initiation + +An MCPTT client initiates an MCPTT emergency alert to the members of an MCPTT group. This procedure will place the MCPTT client in the MCPTT emergency state if the MCPTT client is not already in that state. + +Procedures in figure 10.6.3.9.3.1-1 are the signalling control plane procedures for the MCPTT client initiating an MCPTT emergency alert with an MCPTT group i.e., MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 belong to the same MCPTT group. + +Pre-conditions: + +1. The pre-conditions for off-network group calls as described in subclause 10.6.3.3 apply. +2. The initiating MCPTT client 1 has been provisioned with an MCPTT group designated as the MCPTT emergency group. + +NOTE 1: Alternatively, MCPTT client 1 could have been provisioned for emergency behaviour on the currently selected group. + +3. MCPTT clients 2 and 3 belong to and are ready for off-network communications on the MCPTT group. + +![Sequence diagram for MCPTT emergency alert. Lifelines: MCPTT client 1 (Call Originator), MCPTT client 2, and MCPTT client 3. The sequence starts with '1. User initiates MCPTT emergency alert' at client 1. Client 1 sends '2. MCPTT Emergency alert announcement' to clients 2 and 3. Clients 2 and 3 each perform '3. Notify MCPTT emergency alert'. Both clients 2 and 3 then send '4. Response' back to client 1. Finally, client 1 performs '5. checking participants'.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCPTT client 1 (Call Originator) + participant C2 as MCPTT client 2 + participant C3 as MCPTT client 3 + Note left of C1: 1. User initiates MCPTT emergency alert + C1->>C2: 2. MCPTT Emergency alert announcement + C1->>C3: 2. MCPTT Emergency alert announcement + Note right of C2: 3. Notify MCPTT emergency alert + Note right of C3: 3. Notify MCPTT emergency alert + C2->>C1: 4. Response + C3->>C1: 4. Response + Note left of C1: 5. checking participants + +``` + +Sequence diagram for MCPTT emergency alert. Lifelines: MCPTT client 1 (Call Originator), MCPTT client 2, and MCPTT client 3. The sequence starts with '1. User initiates MCPTT emergency alert' at client 1. Client 1 sends '2. MCPTT Emergency alert announcement' to clients 2 and 3. Clients 2 and 3 each perform '3. Notify MCPTT emergency alert'. Both clients 2 and 3 then send '4. Response' back to client 1. Finally, client 1 performs '5. checking participants'. + +**Figure 10.6.3.9.3.1-1: MCPTT emergency alert** + +1. The user at the MCPTT client 1 initiates an MCPTT emergency alert by sending an MCPTT emergency alert announcement to the other clients. MCPTT client 1 sets its MCPTT emergency state. The MCPTT emergency state is retained by the MCPTT client until explicitly cancelled. Once MCPTT client1 is in the MCPTT emergency state, any calls initiated by MCPTT client 1, group or private, shall be initiated as emergency calls and receive priority treatment. The MCPTT emergency alert announcement is sent periodically so that late joining MCPTT group members are notified. + +2. MCPTT client 1 sends an MCPTT emergency alert announcement to the other participants on the MCPTT emergency group. + +NOTE 2: Sending the emergency alert without making a request to also start an MCPTT emergency call does not put the group into the in-progress emergency state. + +3. MCPTT users are notified of the MCPTT emergency state of the originating MCPTT user. + +4. The receiving MCPTT clients acknowledge the MCPTT emergency alert to the originating MCPTT client. + +NOTE 3: Sending the emergency alert without making a request to also start an emergency call does not put the group into the in-progress emergency state. + +NOTE 4: The MCPTT client 1 need not initiate a group call. For example, the MCPTT client can be configured to only allow alerts or the MCPTT user can choose not to make an MCPTT emergency group call. + +NOTE 5: MCPTT clients receiving subsequent MCPTT emergency alert announcements that are sent periodically need only respond to the first one that they receive. + +5. The originating MCPTT client 1 checks the responses and may inform the MCPTT user of the MCPTT group members whose MCPTTT clients responded. + +###### 10.6.3.9.3.2 MCPTT emergency alert cancel + +An MCPTT client has initiated an MCPTT emergency alert, has entered the MCPTT emergency state and wishes to cancel the alert, informing the other MCPTT group members of the cancellation. As part of this process, the MCPTT client may also request the cancellation of the in-progress emergency state of the group if authorized to do so. + +Procedures in figure 10.6.3.9.3.2-1 are the signalling control plane procedures for the MCPTT client cancelling an MCPTT emergency alert with an MCPTT group i.e., MCPTT users on MCPTT client 1, MCPTT client 2 and MCPTT client 3 belong to the same MCPTT group. + +Pre-conditions: + +1. The MCPTT client 1 had previously successfully initiated an MCPTT emergency alert. +2. The MCPTT client 1 is still in the MCPTT emergency state. +3. The initiating MCPTT client 1 and MCPTT clients 2 and 3 are still in off-network contact via the MCPTT group designated provisioned to MCPTT client 1 as the MCPTT emergency group. + +![Sequence diagram for MCPTT emergency alert cancel. Lifelines: MCPTT client 1 (Call Originator), MCPTT client 2, MCPTT client 3. Steps: 1. User initiates MCPTT emergency alert cancel (at client 1); 2. MCPTT Emergency alert cancel announcement (from client 1 to client 3); 3. Notify MCPTT emergency alert cancel (from client 3 to client 2, and from client 2 to client 1); 4. Response (from client 2 to client 1, and from client 3 to client 1).](54fabc351eda5228d2fa28cd9ba07971_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCPTT client 1 (Call Originator) + participant C2 as MCPTT client 2 + participant C3 as MCPTT client 3 + Note left of C1: 1. User initiates MCPTT emergency alert cancel + C1->>C3: 2. MCPTT Emergency alert cancel announcement + Note right of C3: 3. Notify MCPTT emergency alert cancel + C3->>C2: 3. Notify MCPTT emergency alert cancel + Note right of C2: 4. Response + C2->>C1: 4. Response + Note right of C3: 4. Response + C3->>C1: 4. Response + +``` + +Sequence diagram for MCPTT emergency alert cancel. Lifelines: MCPTT client 1 (Call Originator), MCPTT client 2, MCPTT client 3. Steps: 1. User initiates MCPTT emergency alert cancel (at client 1); 2. MCPTT Emergency alert cancel announcement (from client 1 to client 3); 3. Notify MCPTT emergency alert cancel (from client 3 to client 2, and from client 2 to client 1); 4. Response (from client 2 to client 1, and from client 3 to client 1). + +Figure 10.6.3.9.3.2-1 MCPTT emergency alert cancel + +1. The user at the MCPTT client 1 initiates an MCPTT emergency alert cancel. +2. MCPTT client 1 sends an MCPTT emergency alert cancel announcement to the MCPTT group to which MCPTT client 1 had previously sent the emergency alert. +3. MCPTT users are notified of the MCPTT emergency alert cancellation by MCPTT client 1. +4. The receiving MCPTT clients acknowledge the MCPTT emergency alert cancel to the originating MCPTT client. + +NOTE: MCPTT clients that track the MCPTT emergency alerts of other MCPTT users, e.g. consoles that fail to receive subsequent periodic MCPTT emergency alert announcements after a configured timeout can consider the alert to be cancelled. + +## 10.7 Private call + +### 10.7.1 General + +Private calls are enabled in both on-network and off-network. + +Private calls can be setup in two different commencement modes, automatic commencement mode and manual commencement mode. + +Private calls in on-network can be with or without floor control. Private calls in off-network are with floor control. + +### 10.7.2 Private call in on-network + +#### 10.7.2.1 Information flows for private call in on-network + +##### 10.7.2.1.1 MCPTT private call request (MCPTT client to MCPTT server) + +Table 10.7.2.1.1-1 describes the information flow MCPTT private call request from the MCPTT client to the MCPTT server. + +**Table 10.7.2.1.1-1: MCPTT private call request (MCPTT client to MCPTT server) information elements** + +| Information Element | Status | Description | +|------------------------------|--------|-----------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Use floor control indication | M | This element indicates whether floor control will be used for the private call. | +| SDP offer | O | Media parameters of MCPTT client. | +| Requested commencement mode | O | An indication that is included if the user is requesting a particular commencement mode | +| Implicit floor request | O | An indication that the user is also requesting the floor. | + +##### 10.7.2.1.2 MCPTT private call request (MCPTT server to MCPTT server) + +Table 10.7.2.1.2-1 describes the information flow MCPTT private call request from the MCPTT server to the MCPTT server. + +**Table 10.7.2.1.2-1: MCPTT private call request (MCPTT server to MCPTT server) information elements** + +| Information Element | Status | Description | +|------------------------------|--------|---------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Use floor control indication | M | This element indicates whether floor control will be used for the private call. | +| SDP offer | M | Media parameters of MCPTT client. | +| Requested commencement mode | O | An indication of the commencement mode to be used. | +| Implicit floor request | O | An indication that the user is also requesting the floor. | + +##### 10.7.2.1.2a MCPTT private call request (MCPTT server to MCPTT client) + +Table 10.7.2.1.2a describes the information flow MCPTT private call request from the MCPTT server to the MCPTT client. + +**Table 10.7.2.1.2a: MCPTT private call request (MCPTT server to MCPTT client) information elements** + +| Information Element | Status | Description | +|------------------------------|--------|---------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Use floor control indication | M | This element indicates whether floor control will be used for the private call. | +| SDP offer | M | Media parameters of MCPTT client. | +| Requested commencement mode | O | An indication of the commencement mode to be used. | +| Implicit floor request | O | An indication that the user is also requesting the floor. | + +##### 10.7.2.1.3 MCPTT private call response (MCPTT client to MCPTT server) + +Table 10.7.2.1.3-1 describes the information flow MCPTT private call response from the MCPTT client to the MCPTT server. + +**Table 10.7.2.1.3-1: MCPTT private call response (MCPTT client to MCPTT server) information elements** + +| Information Element | Status | Description | +|-----------------------------|--------|----------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | O | The MCPTT ID of the called party | +| SDP answer | M | Media parameters selected | +| Requested commencement mode | O | An indication of the commencement mode to be used. | + +##### 10.7.2.1.4 MCPTT private call response + +Table 10.7.2.1.4-1 describes the information flow MCPTT private call response from the MCPTT server to the MCPTT server and the MCPTT server to the MCPTT client. + +**Table 10.7.2.1.4-1: MCPTT private call response information elements** + +| Information Element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | O | The MCPTT ID of the called party | +| Acceptance confirmation | O | An indication whether the user has positively accepted the call. | +| SDP answer | M | Media parameters selected | + +##### 10.7.2.1.4a MCPTT private call end request + +Table 10.7.2.1.4a-1 describes the information flow MCPTT private call end request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.7.2.1.4a-1: MCPTT private call end request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | + +###### 10.7.2.1.4b MCPTT private call end response + +Table 10.7.2.1.4b-1 describes the information flow MCPTT private call end response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.7.2.1.4b-1: MCPTT private call end response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | In the direction MCPTT client to MCPTT server this shall be the MCPTT ID of the responding MCPTT client.<br>In the direction MCPTT server to MCPTT client this shall be the MCPTT ID of the destination MCPTT client | + +##### 10.7.2.1.5 MCPTT emergency private call request (MCPTT client to MCPTT server) + +Table 10.7.2.1.5-1 describes the information flow MCPTT emergency private call request from the MCPTT client to the MCPTT server. + +**Table 10.7.2.1.5-1: MCPTT emergency private call request (MCPTT client to MCPTT server) information elements** + +| Information Element | Status | Description | +|-----------------------------|--------|--------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Emergency indicator | M | Indicates that the private call request is an MCPTT emergency call | +| Alert indicator | M | Indicates whether an emergency alert is to be sent | +| Requested commencement mode | O | An indication of the commencement mode to be used. | +| Implicit floor request | O | An indication that the user is also requesting the floor. | +| SDP offer | M | Media parameters of MCPTT client. | + +###### 10.7.2.1.5a MCPTT emergency private call request (MCPTT server to MCPTT client) + +Table 10.7.2.1.5a-1 describes the information flow MCPTT emergency private call request from the MCPTT server to the MCPTT client. + +**Table 10.7.2.1.5a-1: MCPTT emergency private call request (MCPTT server to MCPTT client) information elements** + +| Information Element | Status | Description | +|-----------------------------|--------|--------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Emergency indicator | M | Indicates that the private call request is an MCPTT emergency call | +| Alert indicator | M | Indicates whether an emergency alert is to be sent | +| Requested commencement mode | O | An indication of the commencement mode to be used. | +| Implicit floor request | O | An indication that the user is also requesting the floor. | +| SDP offer | M | Media parameters of MCPTT client. | + +##### 10.7.2.1.6 MCPTT progress indication + +Table 10.7.2.1.6-1 describes the information flow MCPTT progress indication from the MCPTT server to the MCPTT client. + +**Table 10.7.2.1.6-1: MCPTT progress indication information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Progress indication | O | Indication to the caller. | + +##### 10.7.2.1.7 MCPTT ringing + +Table 10.7.2.1.7-1 describes the information flow MCPTT ringing from the MCPTT client to the MCPTT server, from the MCPTT server to the MCPTT server, and from the MCPTT server to the MCPTT client. + +**Table 10.7.2.1.7-1: MCPTT ringing information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Ringing indication | O | Indication to the caller. | + +#### 10.7.2.2 Private call within one MCPTT system + +##### 10.7.2.2.1 Private call setup in automatic commencement mode + +The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call for communicating with another MCPTT user, with or without floor control enabled, in an automatic commencement mode. + +Procedures in figure 10.7.2.2.1-1 are the basic signalling control plane procedures for the MCPTT client initiating establishment of MCPTT private call with the chosen MCPTT user. + +Pre-conditions: + +1. The calling MCPTT user has selected automatic commencement mode for the call; or +2. The called MCPTT client is set to automatic commencement mode. + +![Sequence diagram illustrating the private call setup in automatic commencement mode for MCPTT users in the same MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT server, and MCPTT client 2 under the 'Home MCPTT service provider'.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note over MCPTT client 1, MCPTT client 2: Home MCPTT service provider + Note left of MCPTT client 1: 2. initiate private call + MCPTT client 1->>MCPTT server: 3. MCPTT private call request + MCPTT server->>MCPTT server: 4. Authorize request + MCPTT server-->>MCPTT client 1: 5. MCPTT progress indication + MCPTT server->>MCPTT client 2: 6. MCPTT private call request + MCPTT client 2->>MCPTT client 2: 7. Notify call + MCPTT client 2->>MCPTT server: 8. MCPTT private call response + MCPTT server->>MCPTT client 1: 9. MCPTT private call response + Note over MCPTT client 1, MCPTT client 2: 10. Media plane established + +``` + +Sequence diagram illustrating the private call setup in automatic commencement mode for MCPTT users in the same MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT server, and MCPTT client 2 under the 'Home MCPTT service provider'. + +**Figure 10.7.2.2.1-1: Private call setup in automatic commencement mode– MCPTT users in the same MCPTT system** + +1. MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service, as per procedure in subclause 10.2. +2. User at MCPTT client 1 would like to initiate an MCPTT private call for the chosen MCPTT user. For a private call with floor control, floor control is to be established. +3. MCPTT client 1 sends an MCPTT private call request towards the MCPTT server (via SIP core) using a service identifier as defined in 3GPP TS 23.228 [5] for MCPTT, for establishing a private call with the chosen MCPTT user. The MCPTT private call request contains the MCPTT id of invited user, an SDP offer containing one or more media types. For a private call with floor control, the MCPTT private call request also contains an element that indicates that MCPTT client 1 is requesting the floor. The MCPTT client 1 may include a Requested commencement mode that indicates that the call is to be established in automatic commencement mode if automatic commencement mode is requested by the initiating user. +4. MCPTT server checks whether the MCPTT user at MCPTT client 1 is authorized to initiate the private call, and that MCPTT user at MCPTT client 2 is authorized to receive the private call. If the MCPTT private call request requested automatic commencement mode then the MCPTT server also checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a private call in automatic commencement mode. +5. MCPTT server may provide a progress indication to MCPTT client 1 to indicate progress in the call setup process. + +NOTE: Step 5 can occur at any time following step 4, and prior to step 9. + +6. If authorized, MCPTT server includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request, includes the requested automatic commencement mode indication based on a requested automatic commencement mode by the calling user or based upon the setting of the called MCPTT client and sends the corresponding MCPTT private call request towards the MCPTT client 2, including the MCPTT ID of the calling MCPTT user 1. If the called MCPTT user has registered to the MCPTT service with multiple MCPTT UEs and has designated the MCPTT UE for receiving the private calls, then the incoming MCPTT private call request is delivered only to the designated MCPTT UE. +7. The receiving MCPTT client 2 notifies the user about the incoming private call. +8. The receiving MCPTT client 2 accepts the private call automatically, and an MCPTT private call response is sent to the MCPTT server (via SIP core). + +9. Upon receiving the MCPTT private call response from MCPTT client 2 accepting the private call request, the MCPTT server informs the MCPTT client 1 about successful call establishment. +10. MCPTT client 1 and MCPTT client 2 have successfully established media plane for communication and either user can transmit media. For successful call establishment for private call with floor control request from MCPTT client 1, floor participant at MCPTT client 1 is granted floor by the floor control server, giving it permission to transmit. At the same time floor participant at MCPTT client 2 is informed by the floor control server that floor is taken. + +##### 10.7.2.2.2 Private call setup in manual commencement mode + +###### 10.7.2.2.2.1 Description + +Figure 10.7.2.2.2.2-1 describes the basic procedure for the MCPTT client initiating an MCPTT private call that uses manual commencement mode. The flow may use a floor request in the MCPTT private call request indicating that the originator will be given the floor when the call starts and eliminates the need for a separate initial floor request message during media plane establishment. Alternatively the call initiation may be sent without the floor request, which allows the called party to request the floor first. + +###### 10.7.2.2.2.2 Procedure + +Both clients are served by the primary MCPTT service provider in figure 10.7.2.2.2.2-1. + +Pre-conditions: + +1. The calling MCPTT user has selected manual commencement mode or has not specified a commencement mode for the call; and +2. The called MCPTT client is set to manual commencement mode. + +![Sequence diagram of MCPTT private call in manual commencement mode. Lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2. The process starts with registration and authentication, followed by a private call request from client 1 to the server, which then verifies authorization and forwards the request to client 2. Client 2 rings, and the server rings client 1. Both clients send responses, and the media plane is established.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + + Note over MCPTT client 1, MCPTT client 2: 1. MCPTT client 1 and MCPTT client 2 are both registered, their respective users are authenticated and authorized for the MCPTT Service + + Note left of MCPTT client 1: 2. Initiate private call + MCPTT client 1->>MCPTT server: 3. MCPTT private call request + Note right of MCPTT server: 4. MCPTT server verifies that MCPTT client 1 and MCPTT client 2 are authorized to participate in the call + MCPTT server->>MCPTT client 2: 5. MCPTT private call request + MCPTT server-->>MCPTT client 1: 6. MCPTT progress indication + MCPTT server->>MCPTT client 2: 7a. MCPTT ringing + MCPTT client 2-->>MCPTT server: 8. MCPTT private call response + MCPTT server->>MCPTT client 1: 7b. MCPTT ringing + MCPTT client 1-->>MCPTT server: 9. MCPTT private call response + Note over MCPTT client 1, MCPTT client 2: 10. Media plane established + +``` + +Sequence diagram of MCPTT private call in manual commencement mode. Lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2. The process starts with registration and authentication, followed by a private call request from client 1 to the server, which then verifies authorization and forwards the request to client 2. Client 2 rings, and the server rings client 1. Both clients send responses, and the media plane is established. + +**Figure 10.7.2.2.2.2-1: MCPTT private call in manual commencement mode– MCPTT users in the same MCPTT system** + +1. MCPTT client 1 and MCPTT client 2 are both registered and their respective users, MCPTT user 1 and MCPTT user 2, are authenticated and authorized to use the MCPTT service, as per procedure in subclause 10.2. +2. MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call for the selected MCPTT user. For a private call with floor control, floor control is to be established. For private call without floor control, both users will have the ability to transmit without floor arbitration. +3. MCPTT client 1 sends an MCPTT private call request addressed to the MCPTT ID of MCPTT user 2 using an MCPTT service identifier as defined in 3GPP TS 23.228 [5] (possible for the SIP core to route the request to the MCPTT server). The MCPTT private call request contains the MCPTT ID of invited user and an SDP offer containing one or more media types. The MCPTT private call request may also contain a data element that indicates that MCPTT client 1 is requesting the floor, for a private call with floor control. The MCPTT client 1 may include a requested commencement mode that indicates that the call is to be established in manual commencement mode if manual commencement mode is requested by the initiating user. +4. The MCPTT server confirms that both MCPTT users are authorized for the private call. The MCPTT server checks the commencement mode setting of the called MCPTT client and also checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a call in manual commencement mode. +5. The MCPTT server includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request and sends an MCPTT private call request for the call to MCPTT client 2, including the MCPTT ID of the calling MCPTT user 1. If the called MCPTT user has registered to the MCPTT service with multiple MCPTT UEs and has designated the MCPTT UE for receiving the private calls, then the incoming MCPTT private call request is delivered only to the designated MCPTT UE. + +- 6. MCPTT server may provide a progress indication to MCPTT client 1 to indicate progress in the call setup process. + +NOTE: Step 6 can occur at any time following step 4, and prior to step 7b. + +- 7a. The MCPTT user is alerted. MCPTT client 2 sends an MCPTT ringing to the MCPTT server. + +- 7b. The MCPTT server sends an MCPTT ringing to MCPTT client 1, indicating that MCPTT client 2 is being alerted. + +- 8. MCPTT user 2 has accepted the call using manual commencement mode (i.e., has taken some action to accept via the user interface) which causes MCPTT client 2 to send an MCPTT private call response to the MCPTT server. If MCPTT user 2 has not accepted the incoming call, the MCPTT client 2 sends a call failure response to the MCPTT server without adding reason for call failure. + +- 9. The MCPTT server sends an MCPTT private call response to MCPTT client 1 indicating that MCPTT user 2 has accepted the call, including the accepted media parameters. + +- 10. The media plane for communication is established. Either user can transmit media individually when using floor control. For successful call establishment for private call with floor request from MCPTT client 1, the floor participant associated with MCPTT client 1 is granted the floor initially. At the same time the floor participant associated with MCPTT client 2 is informed that the floor is taken. The meaning of the floor request (give floor initially to originator [client 1], or give floor initially to target [client 2]) may be configurable. For a private call without floor control both users are allowed to transmit simultaneously. + +##### 10.7.2.2.3 Private call release + +###### 10.7.2.2.3.1 Client initiated + +The procedure focuses on the case where an MCPTT client is requesting to release an ongoing MCPTT private call (with or without floor control) and the call established in either of the two commencement modes (manual or automatic). + +Procedures in figure 10.7.2.2.3.1-1 are the basic signalling control plane procedures for the MCPTT client initiating the release of an ongoing MCPTT private call. + +![Sequence diagram titled 'Home MCPTT service provider' showing the interaction between MCPTT client 1, MCPTT server, and MCPTT client 2 for a private call release. The sequence starts with a note that both clients are registered and an ongoing call exists. Client 1 sends a 'Release private call' action, followed by a 'MCPTT private call end request' to the server. The server then sends a 'MCPTT private call end request' to Client 2. Client 2 performs 'Notify call termination' and sends a 'MCPTT private call end response' back to the server. The server then sends a 'MCPTT private call end response' to Client 1. Finally, a note indicates that 'Media plane resources released'.](dc23d430e878eb71b8cd589984113940_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MCPTT client 1 + participant Server as MCPTT server + participant Client2 as MCPTT client 2 + Note over Client1, Server, Client2: 1. MCPTT client 1 and MCPTT client 2 are registered for MCPTT service and private call is ongoing between them + Note left of Client1: 2. Release private call + Client1->>Server: 3. MCPTT private call end request + Server->>Client2: 4. MCPTT private call end request + Note right of Client2: 5. Notify call termination + Client2->>Server: 6. MCPTT private call end response + Server->>Client1: 7. MCPTT private call end response + Note over Client1, Server, Client2: 8. Media plane resources released + +``` + +Sequence diagram titled 'Home MCPTT service provider' showing the interaction between MCPTT client 1, MCPTT server, and MCPTT client 2 for a private call release. The sequence starts with a note that both clients are registered and an ongoing call exists. Client 1 sends a 'Release private call' action, followed by a 'MCPTT private call end request' to the server. The server then sends a 'MCPTT private call end request' to Client 2. Client 2 performs 'Notify call termination' and sends a 'MCPTT private call end response' back to the server. The server then sends a 'MCPTT private call end response' to Client 1. Finally, a note indicates that 'Media plane resources released'. + +Figure 10.7.2.2.3.1-1: Private call release – client initiated + +1. It is assumed that MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service and are involved in private call with or without floor control established either in manual or automatic commencement mode, as described in subclause 10.7.2.2.1 and subclause 10.7.2.2.2. +2. User at MCPTT client 1 would like to release an ongoing MCPTT private call with MCPTT client 2. +3. MCPTT client 1 sends an MCPTT private call end request towards the MCPTT server (via SIP core), for tearing down the private call with the other client. +4. MCPTT server sends the corresponding MCPTT private call end request towards the MCPTT client specified in the original MCPTT private call end request. +5. MCPTT user is notified about the release of the private call. +6. The receiving MCPTT client 2 acknowledges the MCPTT private call end request with an MCPTT private call end response. +7. After receiving the MCPTT private call end response from MCPTT client 2, the MCPTT server generates an acknowledgement for the MCPTT client 1's MCPTT private call end request. +8. MCPTT clients release all the media plane resources used for the private call. Further, if the private call was established with floor control, floor control resources are released and MCPTT clients cannot make further requests for floor control or send media. + +###### 10.7.2.2.3.2 Server initiated + +The procedure focuses on the case where an MCPTT server is terminating an ongoing MCPTT private call (with or without floor control) and the call established in either of the two commencement modes (manual or automatic), upon conditions to terminate call e.g., MCPTT administrator configured maximum duration for MCPTT private calls has expired or timed out due to MCPTT private call without transmission/reception. + +Procedures in figure 10.7.2.2.3.2-1 are the basic signalling control plane procedures for the MCPTT server initiating termination of an ongoing MCPTT private call. + +![Sequence diagram titled 'Home MCPTT service provider' showing the server-initiated termination of an MCPTT private call between Client 1 and Client 2 via an MCPTT server.](12de9b926df0384ec07702671827c9cd_img.jpg) + +``` +sequenceDiagram + participant C1 as MCPTT client 1 + participant S as MCPTT server + participant C2 as MCPTT client 2 + Note over C1, C2: 1. Client 1 and client 2 are registered for MCPTT service and private call is ongoing between them + Note over S: 2. Conditions to trigger terminate private call + S->>C1: 3. MCPTT private call end request + S->>C2: 3. MCPTT private call end request + Note left of C1: 4. Notify call termination + Note right of C2: 4. Notify call termination + C1->>S: 5. MCPTT private call end response + C2->>S: 5. MCPTT private call end response + Note over C1, C2: 6. Media plane resources released +``` + +Sequence diagram titled 'Home MCPTT service provider' showing the server-initiated termination of an MCPTT private call between Client 1 and Client 2 via an MCPTT server. + +**Figure 10.7.2.2.3.2-1: End private call – server initiated** + +1. It is assumed that MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service and are involved in private call with or without floor control established either in manual or automatic commencement mode. + +2. Upon conditions to terminate call e.g., MCPTT administrator configured maximum duration for MCPTT private calls has expired or timed out due to MCPTT private call without transmission/reception, the MCPTT server decides to initiate termination of an ongoing MCPTT private call between MCPTT client 1 and MCPTT client 2. +3. MCPTT server sends an MCPTT private call end request towards the MCPTT clients 1 and 2 (via SIP core), for tearing down the private call between them. +4. MCPTT users at client 1 and client 2 are notified about the termination of the private call. +5. The MCPTT private call end request receiving MCPTT clients 1 and 2 acknowledge the request with an MCPTT private call end response. +6. MCPTT clients release all the media plane resources used for the private call. Further, if the private call was established with floor control, floor control resources are released and MCPTT clients cannot make further requests for floor control or send media. + +#### 10.7.2.3 Private call within several MCPTT systems + +##### 10.7.2.3.1 Private call setup in automatic commencement mode – MCPTT users in multiple MCPTT systems + +The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call (automatic commencement mode) for communicating with MCPTT user in another MCPTT system with or without floor control enabled. + +Procedures in figure 10.7.2.3.1-1 are the procedures for the MCPTT client initiating establishment of MCPTT private call with the chosen MCPTT user. + +Pre-conditions: + +1. The calling MCPTT user has selected automatic commencement mode for the call; or +2. The called MCPTT client is set to automatic commencement mode. + +![Sequence diagram illustrating the private call setup in automatic commencement mode between two MCPTT service providers. The diagram shows the interaction between MCPTT client 1, MCPTT server 1, MCPTT server 2, and MCPTT client 2. The process involves registration, call initiation, authorization, progress indication, and media plane establishment.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server 1 + participant MCPTT server 2 + participant MCPTT client 2 + + Note left of MCPTT client 1: 1. MCPTT client 1 registered for MCPTT service + Note right of MCPTT client 2: 1. MCPTT client 2 registered for MCPTT service + + Note left of MCPTT client 1: 2. initiate private call + MCPTT client 1->>MCPTT server 1: 3. MCPTT private call request + MCPTT server 1->>MCPTT server 2: 4. Authorize request + MCPTT server 1-->>MCPTT client 1: 5. MCPTT progress indication + MCPTT server 1->>MCPTT server 2: 6. MCPTT private call request + MCPTT server 2->>MCPTT client 2: 7. Authorize request + MCPTT server 2->>MCPTT client 2: 8. MCPTT private call request + Note right of MCPTT client 2: 9. Notify call + MCPTT client 2->>MCPTT server 2: 10. MCPTT private call response + MCPTT server 2->>MCPTT server 1: 11. MCPTT private call response + Note bottom: 12. Media plane established + +``` + +Sequence diagram illustrating the private call setup in automatic commencement mode between two MCPTT service providers. The diagram shows the interaction between MCPTT client 1, MCPTT server 1, MCPTT server 2, and MCPTT client 2. The process involves registration, call initiation, authorization, progress indication, and media plane establishment. + +**Figure 10.7.2.3.1-1: Private call setup in automatic commencement mode – users in multiple MCPTT systems** + +1. It is assumed that MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service to their respective MCPTT service provider, as per procedure in subclause 10.2. +2. MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call for the chosen MCPTT user. For a private call with floor control, floor control is to be established. +3. MCPTT client 1 sends an MCPTT private call request towards the home MCPTT server 1 (via SIP core) using a service identifier as defined in 3GPP TS 23.228 [5] for MCPTT, for establishing private call with the MCPTT client 2 registered at MCPTT service provider 2. The MCPTT private call request contains the MCPTT id of invited user and an SDP offer containing one or more media types. For a private call with floor control, the MCPTT private call request also contains an element that indicates that MCPTT client 1 is requesting the floor. The MCPTT client 1 may include a requested commencement mode that indicates that the call is to be established in automatic commencement mode if automatic commencement mode is requested by the initiating user. +4. MCPTT server 1 checks whether the MCPTT user at MCPTT client 1 is authorized to initiate the private call. If the MCPTT private call request requested automatic commencement mode then the MCPTT server 1 also checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a call in automatic commencement mode. +5. MCPTT server 1 may provide a progress indication to MCPTT client 1 to indicate progress in the call setup process. + +NOTE: Step 5 can occur at any time following step 4, and prior to step 11. + +6. If authorized, MCPTT server 1 includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request, includes an automatic commencement mode indication if automatic commencement mode was requested by and authorised for the + +calling user and sends the corresponding MCPTT private call request towards the MCPTT system (via SIP core) of the MCPTT client specified in the original MCPTT private call request (MCPTT client 2) i.e., MCPTT server 2. + +7. MCPTT server 2 checks whether the MCPTT user at MCPTT client 2 is authorized to receive a private call. +8. MCPTT server 2 includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request, includes a requested automatic commencement mode indication based on a requested automatic commencement mode by the calling user or based upon the setting of the called MCPTT client and sends the received MCPTT private call request towards the MCPTT client specified in the received MCPTT private call request (i.e., MCPTT client 2). If the called MCPTT user has registered to the MCPTT service with multiple MCPTT UEs and has designated the MCPTT UE for receiving the private calls, then the incoming MCPTT private call request is delivered only to the designated MCPTT UE. +9. The receiving MCPTT client 2 notifies the user about the incoming private call. +10. The receiving MCPTT client 2 accepts the private call automatically, and an acknowledgement is sent to the MCPTT server 1 (via SIP core and MCPTT server 2). +11. Upon receiving the MCPTT private call response from MCPTT client 2 accepting the private call request, MCPTT client 1 is informed about successful call establishment. +12. MCPTT client 1 and MCPTT client 2 have successfully established media plane for communication and either user can transmit media. For successful call establishment of a private call with implicit floor control request from MCPTT client 1, floor participant at MCPTT client 1 is granted floor by the floor control server at MCPTT service provider 1, giving it permission to transmit. At the same time floor participant at MCPTT client 2 is informed by the floor control server at MCPTT service provider 1 that the floor is taken. + +##### 10.7.2.3.2 Private call setup in manual commencement mode – MCPTT users in multiple MCPTT systems + +The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call (manual commencement mode) for communicating with MCPTT user in another MCPTT system with or without floor control enabled. + +Procedures in figure 10.7.2.3.2-1 are the procedures for the MCPTT client initiating establishment of MCPTT private call with the selected MCPTT user. + +Pre-conditions: + +1. The calling MCPTT user has selected manual commencement mode or has not specified a commencement mode for the call; and +2. The called MCPTT client is set to manual commencement mode. + +![Sequence diagram illustrating the private call setup in manual commencement mode between two MCPTT service providers. The diagram shows the interaction between MCPTT client 1, MCPTT server 1, MCPTT server 2, and MCPTT client 2. The process involves registration, call initiation, authorization, and media plane establishment.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server 1 + participant MCPTT server 2 + participant MCPTT client 2 + + Note left of MCPTT client 1: 1. MCPTT client 1 registered for MCPTT service + Note right of MCPTT client 2: 1. MCPTT client 2 registered for MCPTT service + + Note left of MCPTT client 1: 2. initiate private call + MCPTT client 1->>MCPTT server 1: 3. MCPTT private call request + MCPTT server 1->>MCPTT server 1: 4. Authorize request + MCPTT server 1->>MCPTT server 2: 5. MCPTT private call request + MCPTT server 2->>MCPTT server 2: 7. Authorize request + MCPTT server 2->>MCPTT client 2: 8. MCPTT private call request + MCPTT client 2->>MCPTT server 2: 9. MCPTT ringing + MCPTT server 2->>MCPTT server 1: 9. MCPTT ringing + MCPTT server 1->>MCPTT client 1: 10. MCPTT ringing + MCPTT client 2->>MCPTT server 2: 11. MCPTT private call response + MCPTT server 2->>MCPTT server 1: 11. MCPTT private call response + MCPTT server 1->>MCPTT client 1: 12. MCPTT private call response + Note bottom: 13. Media plane established + +``` + +Sequence diagram illustrating the private call setup in manual commencement mode between two MCPTT service providers. The diagram shows the interaction between MCPTT client 1, MCPTT server 1, MCPTT server 2, and MCPTT client 2. The process involves registration, call initiation, authorization, and media plane establishment. + +**Figure 10.7.2.3.2-1: Private call setup in manual commencement mode – users in multiple MCPTT systems** + +1. It is assumed that MCPTT users on MCPTT client 1 and MCPTT client 2 are already registered for receiving MCPTT service to their respective MCPTT service provider, as per procedure in subclause 10.2. +2. MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call for the selected MCPTT user. For a private call with floor control, floor control is to be established. +3. MCPTT client 1 sends an MCPTT private call request towards the home MCPTT server 1 (via SIP core), for establishing private call with the MCPTT client 2 registered at MCPTT service provider 2. For a private call with floor control, the MCPTT private call request contains an element that indicates that MCPTT client 1 is requesting the floor. The MCPTT client 1 may include a requested commencement mode that indicates that the call is to be established in manual commencement mode if manual commencement mode is requested by the initiating user. +4. MCPTT server 1 checks whether the MCPTT user at MCPTT client 1 is authorized to initiate the private call. The MCPTT server 1 also checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a call in manual commencement mode. +5. If authorized, MCPTT server 1 sends the corresponding MCPTT private call request towards the MCPTT system (via SIP core) of the MCPTT client specified in the original MCPTT private call request (MCPTT client 2) i.e., MCPTT server 2. +6. MCPTT server may provide a progress indication to MCPTT client 1 to indicate progress in the call setup process. + +NOTE: Step 6 can occur at any time following step 4, and prior to step 10. + +7. The MCPTT server 2 checks whether the MCPTT user at MCPTT client 2 is authorized to receive a private call and also checks the commencement mode setting of MCPTT client 2. +8. The MCPTT server 2 offers the same media types or a subset of the media types contained in the initial received request and sends an MCPTT private call request towards the MCPTT client specified in the received MCPTT private call request (i.e., MCPTT client 2). If the called MCPTT user has registered to the MCPTT service with multiple MCPTT UEs and has designated the MCPTT UE for receiving the private calls, then the incoming MCPTT private call request is delivered only to the designated MCPTT UE. +9. The MCPTT user is alerted. MCPTT client 2 sends an MCPTT ringing to the MCPTT server 1 (via server 2). +10. The MCPTT server 1 sends an MCPTT ringing to MCPTT client 1, indicating that MCPTT client 2 is being alerted. +11. MCPTT user 2 has accepted the call using manual commencement mode (i.e. has taken some action to accept via the user interface) which causes MCPTT client 2 to send an MCPTT private call response to the MCPTT server 1 (via SIP core and MCPTT server 2) +12. Upon receiving the MCPTT private call response from MCPTT client 2 accepting the private call request, MCPTT client 1 is informed about successful call establishment. +13. MCPTT client 1 and client 2 have successfully established media plane for communication and either user can transmit media. For successful call establishment of a private call with implicit floor control request from MCPTT client 1, floor participant at MCPTT client 1 is granted the floor by the floor control server at MCPTT service provider 1, giving it permission to transmit. At the same time floor participant at MCPTT client 2 is informed by the floor control server at MCPTT service provider 1 that the floor is taken. + +##### 10.7.2.3.3 Private call release – MCPTT users in multiple MCPTT systems + +The procedure in this subclause is for the case where an MCPTT client is requesting to release an ongoing MCPTT private call (with or without floor control) established in either of the two commencement modes (manual or automatic), and the MCPTT users are in multiple MCPTT systems. + +Procedures are similar to those described for private call release when MCPTT users are in single MCPTT system as in subclause 10.7.2.2.3.1, with the addition that the MCPTT call end request and the corresponding acknowledgement are routed through the MCPTT server in partner MCPTT system. + +#### 10.7.2.4 MCPTT emergency private call + +##### 10.7.2.4.1 MCPTT emergency private call commencement + +This procedure focuses on the case where an authorized MCPTT user is initiating an MCPTT emergency private call with unicast signalling for communicating with another MCPTT user. An MCPTT client in the MCPTT emergency state gains elevated access privilege for all of the MCPTT user's mission critical applications. + +Procedures in figure 10.7.2.4.1-1 are the signalling control plane procedures for the MCPTT client initiating establishment of an MCPTT emergency private call. + +Pre-conditions: + +1. Both members of the MCPTT private call belong to the same MCPTT system. +2. The initiating MCPTT client 1 has been configured to send an MCPTT emergency alert prior to initiating an MCPTT emergency private call. + +![Sequence diagram for MCPTT emergency private call. The diagram shows interactions between MCPTT client 1, MCPTT server, and MCPTT client 2 under the 'Home MCPTT service provider'. The steps are: 1. initiate emergency call (client 1), 2. MCPTT emergency private call request (client 1 to server), 3. MCPTT emergency private call request (server to client 2), 4. Notify emergency call (client 2), 5. OK (client 2 to server), 6. Bearer priority adjustment (server), 7. OK (server to client 1), 8. Media plane and floor control establishment (client 1 and 2).](26d664119ad25250780f554633444e54_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MCPTT client 1 + participant Server as MCPTT server + participant Client2 as MCPTT client 2 + Note over Client1, Server, Client2: Home MCPTT service provider + + Client1->>Server: 1. initiate emergency call + Client1->>Server: 2. MCPTT emergency private call request + Server->>Client2: 3. MCPTT emergency private call request + Client2->>Server: 4. Notify emergency call + Client2->>Server: 5. OK + Server->>Server: 6. Bearer priority adjustment + Server->>Client1: 7. OK + Client1->>Client2: 8. Media plane and floor control establishment + +``` + +Sequence diagram for MCPTT emergency private call. The diagram shows interactions between MCPTT client 1, MCPTT server, and MCPTT client 2 under the 'Home MCPTT service provider'. The steps are: 1. initiate emergency call (client 1), 2. MCPTT emergency private call request (client 1 to server), 3. MCPTT emergency private call request (server to client 2), 4. Notify emergency call (client 2), 5. OK (client 2 to server), 6. Bearer priority adjustment (server), 7. OK (server to client 1), 8. Media plane and floor control establishment (client 1 and 2). + +**Figure 10.7.2.4.1-1 MCPTT emergency private call** + +1. The user at the MCPTT client 1 initiates an MCPTT emergency private call. MCPTT client 1 sets its MCPTT emergency state. The MCPTT emergency state is retained until explicitly cancelled. +2. MCPTT client 1 sends an MCPTT emergency private call request towards the MCPTT server. The request contains an indication of the MCPTT emergency. The MCPTT server records the identity of the MCPTT user that initiated the MCPTT emergency private call until the MCPTT emergency is cancelled. If the MCPTT client is configured to send an MCPTT emergency alert when initiating an MCPTT emergency private call, the request also contains an indication that an MCPTT emergency alert is to be initiated. +3. MCPTT server sends the MCPTT emergency private call request towards the target MCPTT client. The request contains an indication of the in-progress emergency. The request contains an indication of an MCPTT emergency alert if the request from the originator indicated MCPTT emergency alert. +4. The MCPTT user on MCPTT client 2 is notified of the incoming MCPTT emergency private call. +5. The receiving MCPTT client acknowledges the MCPTT emergency private call request to the MCPTT server. +6. The MCPTT server adjusts the priority of the underlying bearer. +7. The MCPTT server informs MCPTT client 1 about the successful MCPTT emergency private call establishment. +8. MCPTT client 1 and MCPTT client 2 establish the media plane for communication. The MCPTT client 1 can override MCPTT client 2 unless MCPTT client 2 is also in the MCPTT emergency state. + +NOTE 1: The priority for the MCPTT emergency private call is retained until cancelled according to system policy (e.g. timeout or call end) or cancelled by an authorized MCPTT user. + +NOTE 2: The initiating MCPTT user's MCPTT emergency state is retained by the system until cancelled as in subclause 10.6.2.6.1.3. The initiating MCPTT user's MCPTT emergency state is also retained locally by the MCPTT client until explicitly cancelled by the MCPTT user. + +##### 10.7.2.4.2 MCPTT private call emergency upgrade + +This procedure focuses on the case where an authorized MCPTT user is upgrading a private call to an MCPTT emergency private call while the private call is already in progress. + +Procedures in figure 10.7.2.4.2-1 are the signalling procedures for the MCPTT client upgrading a private call to an MCPTT emergency private call. + +Pre-conditions: + +- 1. Both members of the private call belong to the same MCPTT system. +- 2. A private call is already in progress. + +![Sequence diagram titled 'Home MCPTT service provider' showing the interaction between MCPTT client 1, MCPTT server, and MCPTT client 2 for an emergency upgrade. The process starts with 'Private call already in progress'. Step 1: 'User initiates emergency' at client 1. Step 2: 'MCPTT emergency private call request' from client 1 to server. Step 3: 'MCPTT emergency private call request' from server to client 2. Step 4: 'Notify emergency status' at client 2. Step 5: 'OK' from client 2 to server. Step 6: 'Bearer priority adjustment' at server. Step 7: 'OK' from server to client 1. Step 8: 'Private call continues as a private emergency call'.](9b686adccf125267a013fa25721231a3_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note over MCPTT client 1, MCPTT client 2: Private call already in progress + Note left of MCPTT client 1: 1. User initiates emergency + MCPTT client 1->>MCPTT server: 2. MCPTT emergency private call request + MCPTT server->>MCPTT client 2: 3. MCPTT emergency private call request + Note right of MCPTT client 2: 4. Notify emergency status + MCPTT client 2->>MCPTT server: 5. OK + Note over MCPTT server: 6. Bearer priority adjustment + MCPTT server->>MCPTT client 1: 7. OK + Note over MCPTT client 1, MCPTT client 2: 8. Private call continues as a private emergency call + +``` + +Sequence diagram titled 'Home MCPTT service provider' showing the interaction between MCPTT client 1, MCPTT server, and MCPTT client 2 for an emergency upgrade. The process starts with 'Private call already in progress'. Step 1: 'User initiates emergency' at client 1. Step 2: 'MCPTT emergency private call request' from client 1 to server. Step 3: 'MCPTT emergency private call request' from server to client 2. Step 4: 'Notify emergency status' at client 2. Step 5: 'OK' from client 2 to server. Step 6: 'Bearer priority adjustment' at server. Step 7: 'OK' from server to client 1. Step 8: 'Private call continues as a private emergency call'. + +Figure 10.7.2.4.2-1: MCPTT private call upgrade + +- 1. The MCPTT user at MCPTT client 1 initiates an emergency. MCPTT client 1 sets its MCPTT emergency state. The MCPTT emergency state is retained until explicitly cancelled. +- 2. MCPTT client 1 requests the MCPTT server to upgrade the private call to in-progress emergency by sending an MCPTT emergency request. If configured to send an MCPTT alert when initiating an MCPTT emergency upgrade, the request also contains an indication that an MCPTT alert is to be initiated. The request may contain an indication of an implicit floor request. +- 3. MCPTT server sends the MCPTT emergency request towards the MCPTT client of the other participant. +- 4. The MCPTT user is notified of the in-progress emergency of the MCPTT emergency private call. +- 5. The receiving MCPTT client acknowledges the MCPTT emergency request to the MCPTT server. +- 6. The MCPTT server adjusts the priority of the underlying bearer for both participants in the private call. The priority is retained until the call ends. +- 7. The MCPTT server confirms the upgrade request to MCPTT client 1. + +- MCPTT client 1 and MCPTT client 2 continue with the private call, which has been transformed into an MCPTT emergency private call. The MCPTT client 1 can override MCPTT client 2 unless MCPTT client 2 is also in the MCPTT emergency state. + +### 10.7.3 Private call in off-network + +#### 10.7.3.1 Information flows for private call in off-network + +##### 10.7.3.1.1 Call setup request + +Table 10.7.3.1.1-1 describes the information flow call setup request from one MCPTT client to another MCPTT client. + +**Table 10.7.3.1.1-1: call setup request** + +| Information element | Status | Description | +|----------------------------|--------|---------------------------------------------------| +| MCPTT ID of the caller | M | The identity of the calling party | +| MCPTT ID of the callee | M | The identity of the called party | +| SDP offer for private call | M | SDP with media information offered by (to) client | + +##### 10.7.3.1.2 Call setup response + +Table 10.7.3.1.2-1 describes the information flow call setup response from one MCPTT client to another MCPTT client. + +**Table 10.7.3.1.2-1: call setup response** + +| Information element | Status | Description | +|-----------------------------|--------|---------------------------------------------------| +| MCPTT ID of the caller | M | The identity of the calling party | +| MCPTT ID of the callee | M | The identity of the called party | +| SDP answer for private call | M | SDP with media information offered by (to) client | + +##### 10.7.3.1.3 Call release request + +Table 10.7.3.1.3-1 describes the information flow call release request from one MCPTT client to another MCPTT client. + +**Table 10.7.3.1.3-1: call release request** + +| Information element | Status | Description | +|-----------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID of the caller | M | The identity of the calling party | +| MCPTT ID of the callee | M | The identity of the called party | +| MCPTT private call release reason | O | This element indicates that reason for the private call release. e.g., Originating client requested, target client requested. | + +##### 10.7.3.1.4 Call release response + +Table 10.7.3.1.4-1 describes the information flow call release response from one MCPTT client to another MCPTT client. + +**Table 10.7.3.1.4-1: call release response** + +| Information element | Status | Description | +|-----------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID of the caller | M | The identity of the calling party | +| MCPTT ID of the callee | M | The identity of the called party | +| MCPTT private call release reason | O | This element indicates that reason for the private call release. e.g., Originating client requested, target client requested, server requested. | + +#### 10.7.3.2 Use of ProSe capability for private call + +When an MCPTT user using a ProSe-enabled UE wants to communicate with a specific MCPTT user using a ProSe-enabled UE by a ProSe mechanism, the MCPTT client retrieves the ProSe discovery group ID and user info ID of the + +target MCPTT user from the "List of user(s) who can be called in private call" in the MCPTT user profile and requests the IP address of the MCPTT UE associated with the target MCPTT user from the **ProSe** layer. + +The MCPTT client enables the **ProSe** layer to determine IP address for the target MCPTT UE by providing the **ProSe** discovery group ID and user info ID (as defined in specification 3GPP **TS 23.303** [7]) of the target MCPTT user. This may trigger the **ProSe** layer procedure (e.g. discovery). The user info ID of the target MCPTT user is used by the **ProSe** layer as the target info (as defined in specification 3GPP **TS 23.303** [7]). + +The **ProSe** layer can then provide the IP address related to the target MCPTT user's MCPTT ID to the MCPTT client. + +NOTE: The **ProSe** procedures for one-to-one direct communications specified in 3GPP **TS 23.303** [7] retrieves a layer-2 ID associated with the user info ID of the target MCPTT user by the discovery procedure to establish direct communications between **ProSe** users. + +#### 10.7.3.3 Private call setup in automatic commencement mode + +The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call for communicating with another MCPTT user when off-network using an automatic commencement mode. + +Procedures in figure 10.7.3.3-1 are the basic signalling procedures for the MCPTT client initiating establishment of an off-network MCPTT private call with the chosen MCPTT user. + +Pre-conditions: + +- 1. MCPTT user profile used for off-network operation mode is pre-provisioned in the MCPTT UEs. + +![Sequence diagram showing private call setup between MCPTT client 1 and MCPTT client 2. Steps: 1. Initiate private call (internal to client 1), 2. Call setup request (client 1 to client 2), 3. Notify user (internal to client 2), 4. Call setup response (client 2 to client 1), 5. Media plane is established with floor control (between clients).](49a49278cad196bdfe0db6b4dd1be7fd_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + Note left of MCPTT client 1: 1. Initiate private call + MCPTT client 1->>MCPTT client 2: 2. Call setup request + Note right of MCPTT client 2: 3. Notify user + MCPTT client 2->>MCPTT client 1: 4. Call setup response + Note left of MCPTT client 1: 5. Media plane is established with floor control + +``` + +Sequence diagram showing private call setup between MCPTT client 1 and MCPTT client 2. Steps: 1. Initiate private call (internal to client 1), 2. Call setup request (client 1 to client 2), 3. Notify user (internal to client 2), 4. Call setup response (client 2 to client 1), 5. Media plane is established with floor control (between clients). + +**Figure 10.7.3.3-1: Private call setup in automatic commencement mode** + +- 1. The MCPTT user at MCPTT client 1 would like to initiate a private call to the MCPTT user at MCPTT client 2. +- 2. The MCPTT client 1 sends a call setup request towards the MCPTT client 2. The call setup request contains an SDP offer, an automatic commencement mode indication, and an element that indicates that MCPTT client 1 is requesting the floor. +- 3. The MCPTT client 2 notifies the MCPTT user about the incoming private call. +- 4. The receiving MCPTT client 2 accepts the private call automatically, and a call setup response indicating the successful call establishment is sent to MCPTT client 1. If MCPTT client 2 rejected the incoming call, the MCPTT client 2 sends a call setup response indicating the failure reason to the MCPTT client 1. + +NOTE: Step 4 can also occur prior to step 3. + +- 5. The MCPTT client 1 and the MCPTT client 2 have successfully established the media plane for communication with floor control and the MCPTT client 1 is automatically granted the floor. + +#### 10.7.3.4 Private call setup in manual commencement mode + +The procedure focuses on the case where an MCPTT user is initiating an MCPTT private call for communicating with another MCPTT user when off-network using a manual commencement mode. + +Procedures in figure 10.7.3.4-1 are the basic signalling procedures for the MCPTT client initiating establishment of an off-network MCPTT private call with the chosen MCPTT user. + +Pre-conditions: + +- 1. MCPTT user profile used for off-network operation mode is pre-provisioned in the MCPTT UEs. + +![Sequence diagram showing the private call setup in manual commencement mode between MCPTT client 1 and MCPTT client 2. The steps are: 1. Initiate private call (local to client 1), 2. Call setup request (client 1 to client 2), 3. Notify user (local to client 2), 4. MCPTT ringing (client 2 to client 1), 5. User answers (local to client 2), 6. Call setup response (client 2 to client 1), 7. Media plane is established with floor control (common for both).](84e5b251aa38db522f76f5cc3afcb853_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + Note left of MCPTT client 1: 1. Initiate private call + MCPTT client 1->>MCPTT client 2: 2. Call setup request + Note right of MCPTT client 2: 3. Notify user + MCPTT client 2->>MCPTT client 1: 4. MCPTT ringing + Note right of MCPTT client 2: 5. User answers + MCPTT client 2->>MCPTT client 1: 6. Call setup response + Note over MCPTT client 1, MCPTT client 2: 7. Media plane is established with floor control + +``` + +Sequence diagram showing the private call setup in manual commencement mode between MCPTT client 1 and MCPTT client 2. The steps are: 1. Initiate private call (local to client 1), 2. Call setup request (client 1 to client 2), 3. Notify user (local to client 2), 4. MCPTT ringing (client 2 to client 1), 5. User answers (local to client 2), 6. Call setup response (client 2 to client 1), 7. Media plane is established with floor control (common for both). + +**Figure 10.7.3.4-1: Private call setup in manual commencement mode** + +- 1. The MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call to the MCPTT user at MCPTT client 2. +- 2. The MCPTT client 1 sends a call setup request towards the MCPTT client 2. The MCPTT private call setup request contains an SDP offer, a manual commencement mode indication, and an element that indicates that MCPTT client 1 is requesting the floor. +- 3. The receiving MCPTT client 2 notifies the MCPTT user about the incoming private call. +- 4. The MCPTT client 2 sends MCPTT ringing message to the MCPTT client 1. + +NOTE: Step 4 can also occur prior to step 3. + +5. The MCPTT user at the MCPTT client 2 has accepted the call using manual commencement mode (i.e., has taken some action to accept via the user interface). The MCPTT user may also reject or fail to answer the incoming call. +6. The MCPTT client 2 sends a call setup response indicating the successful call establishment to MCPTT client 1. If the MCPTT client 2 rejected the call or the MCPTT user 2 rejected or failed to answer the incoming call, the MCPTT client 2 sends a call setup response indicating the failure reason to the MCPTT client 1. +7. The MCPTT client 1 and the MCPTT client 2 have successfully established the media plane for communication with floor control and the MCPTT client 1 is automatically granted the floor. + +#### 10.7.3.5 Private call release + +The procedure focuses on the case where an MCPTT client is requesting to release an ongoing MCPTT private call whether the call was established using either of the two commencement modes (manual or automatic), as described in subclause 10.7.3.3 and subclause 10.7.3.4. Either MCPTT client can initiate the call release procedure. + +Procedures in figure 10.7.3.5-1 are the basic signalling control plane procedures for an MCPTT client initiating the release of an ongoing off-network MCPTT private call. + +Pre-conditions: + +1. Two MCPTT users are currently engaged in an off-network MCPTT private call. + +![Sequence diagram for Private call release procedure between MCPTT client 1 and MCPTT client 2.](7fe7bcb3d40736e0b29d9f48ff3cc026_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + Note left of MCPTT client 1: 1. Initiate private call release + MCPTT client 1->>MCPTT client 2: 2. Call release request + Note right of MCPTT client 2: 3. Notify user + MCPTT client 2->>MCPTT client 1: 4. Call release response + Note bottom of MCPTT client 1: 5. Media plane resources are released +``` + +The diagram is a sequence diagram illustrating the 'Private call release' procedure. It features two lifelines: 'MCPTT client 1' on the left and 'MCPTT client 2' on the right. The sequence of events is as follows: 1. A local action on the MCPTT client 1 lifeline labeled '1. Initiate private call release'. 2. A message arrow labeled '2. Call release request' from MCPTT client 1 to MCPTT client 2. 3. A local action on the MCPTT client 2 lifeline labeled '3. Notify user'. 4. A message arrow labeled '4. Call release response' from MCPTT client 2 back to MCPTT client 1. 5. A final note spanning both lifelines at the bottom labeled '5. Media plane resources are released'. + +Sequence diagram for Private call release procedure between MCPTT client 1 and MCPTT client 2. + +**Figure 10.7.3.5-1: Private call release** + +1. The MCPTT user at MCPTT client 1 would like to initiate an MCPTT private call release to the MCPTT user at MCPTT client 2. +2. The MCPTT client 1 sends a call release request towards the MCPTT client 2. +3. The MCPTT client 2 notifies the MCPTT user about the private call release. +4. The MCPTT client 2 sends a call release response indicating the successful call release to MCPTT client 1. + +NOTE: Step 4 can also occur prior to step 3. + +5. The MCPTT client 1 and the MCPTT client 2 release all associated media plane resources. + +#### 10.7.3.6 MCPTT emergency private call + +The off-network emergency private call is a special case of off-network private call as defined in subclause 10.7.3. The following are modifications to the aforementioned subclause to support MCPTT private calls: + +- The call setup contains an indication that the MCPTT private call is to be an MCPTT emergency private call, +- the bearers of both MCPTT private call participants are given MCPTT emergency priority prior to media transfer, +- either participant in an MCPTT private call may upgrade the call to the MCPTT emergency state during the call by sending an MCPTT upgrade private emergency request, +- placing an MCPTT emergency private call places the MCPTT client in the MCPTT emergency state, +- the bearer priority of each participant is restored to the priority as it was prior to the MCPTT emergency private call initiation, when the call ends or when the MCPTT emergency priority is cancelled +- an authorized user or the originator of the call may cancel the MCPTT emergency priority of the call by sending an MCPTT cancel private emergency request and +- the MCPTT emergency priority of the MCPTT private call may be cancelled when criteria established by the MCPTT Administrator are met (e.g., timeout). + +### 10.7.4 MCPTT private call call-back request + +#### 10.7.4.1 Information flows for MCPTT private call call-back request + +##### 10.7.4.1.1 MCPTT private call call-back request + +Table 10.7.4.1.1-1 describes the information flow MCPTT private call call-back request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.7.4.1.1-1: MCPTT private call call-back request information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Urgency indication | M | This element indicates the urgency (i.e., low, normal, high) of the call-back request. | + +##### 10.7.4.1.2 MCPTT private call call-back response + +Table 10.7.4.1.2-1 describes the information flow MCPTT private call call-back response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.7.4.1.2-1: MCPTT private call call-back response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Result | M | Result of the MCPTT call-back request – success or fail. | + +##### 10.7.4.1.3 MCPTT private call call-back cancel request + +Table 10.7.4.1.3-1 describes the information flow MCPTT private call call-back cancel request from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.7.4.1.3-1: MCPTT private call call-back cancel request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | + +##### 10.7.4.1.4 MCPTT private call call-back cancel response + +Table 10.7.4.1.4-1 describes the information flow MCPTT private call call-back cancel response from the MCPTT client to the MCPTT server and from the MCPTT server to the MCPTT client. + +**Table 10.7.4.1.4-1: MCPTT private call call-back cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Result | M | Result of the MCPTT private call call-back cancel request – success or fail. | + +#### 10.7.4.2 MCPTT private call call-back request within one MCPTT system + +The MCPTT private call call-back request procedure includes the initial MCPTT private call call-back request from the MCPTT user and the indication to the receiving MCPTT user of the who called, the time when the call request was made, and the urgency indication. + +Procedures in figure 10.7.4.2-1 show the signalling control plane procedures for the MCPTT client initiating an MCPTT private call call-back request with the chosen MCPTT user. + +Pre-conditions: + +- MCPTT user 1 is the current user at MCPTT client 1 and MCPTT user 2 is the current user at MCPTT client 2; +- MCPTT client 1 and MCPTT client 2 are registered for MCPTT service. + +![Sequence diagram for MCPTT private call call-back request. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2. The sequence starts with MCPTT client 1 initiating a call-back (1. initiate MCPTT private call call-back). MCPTT client 1 sends a request to the server (2. MCPTT private call call-back request). The server checks authorization (3. Authorize request). If authorized, the server sends a request to MCPTT client 2 (4. MCPTT private call call-back request). MCPTT client 2 stores the information (5. Store call-back request information) and notifies the user (6. Notify user). MCPTT client 2 sends a response to the server (7. MCPTT private call call-back response). Finally, the server informs MCPTT client 1 (8. MCPTT private call call-back response).](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note left of MCPTT client 1: 1. initiate MCPTT private call call-back + MCPTT client 1->>MCPTT server: 2. MCPTT private call call-back request + Note right of MCPTT server: 3. Authorize request + MCPTT server->>MCPTT client 2: 4. MCPTT private call call-back request + Note right of MCPTT client 2: 5. Store call-back request information + Note right of MCPTT client 2: 6. Notify user + MCPTT client 2->>MCPTT server: 7. MCPTT private call call-back response + MCPTT server->>MCPTT client 1: 8. MCPTT private call call-back response +``` + +Sequence diagram for MCPTT private call call-back request. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2. The sequence starts with MCPTT client 1 initiating a call-back (1. initiate MCPTT private call call-back). MCPTT client 1 sends a request to the server (2. MCPTT private call call-back request). The server checks authorization (3. Authorize request). If authorized, the server sends a request to MCPTT client 2 (4. MCPTT private call call-back request). MCPTT client 2 stores the information (5. Store call-back request information) and notifies the user (6. Notify user). MCPTT client 2 sends a response to the server (7. MCPTT private call call-back response). Finally, the server informs MCPTT client 1 (8. MCPTT private call call-back response). + +**Figure 10.7.4.2-1: MCPTT private call call-back request – MCPTT users in the same MCPTT system** + +1. MCPTT user on MCPTT client 1 initiates an MCPTT private call call-back request to the MCPTT user of MCPTT client 2. +2. MCPTT client 1 sends an MCPTT private call call-back request towards the MCPTT server. +3. MCPTT server checks whether the MCPTT user 1 at MCPTT client 1 is authorized to initiate the MCPTT private call call-back request. +4. If authorized, MCPTT server sends the corresponding MCPTT private call call-back request towards the MCPTT client 2. +5. The receiving MCPTT client 2 stores the MCPTT user who initiated the MCPTT private call call-back request, the time the MCPTT private call call-back request was received, and the urgency indication for the MCPTT private call call-back request. +6. The MCPTT client 2 notifies the MCPTT user 2 that there is an MCPTT private call call-back request awaiting his attention. +7. The receiving MCPTT client 2 sends an MCPTT private call call-back response to the MCPTT server. +8. Upon receiving the MCPTT private call call-back response from MCPTT client 2, the MCPTT server informs the MCPTT client 1 about successful call-back request. + +#### 10.7.4.3 MCPTT private call call-back cancel request within one MCPTT system + +Once an MCPTT private call call-back request has been successfully made and before the receiving MCPTT user has made an MCPTT private call to the calling MCPTT user, the calling MCPTT user may cancel the outstanding MCPTT private call request. + +Procedures in figure 10.7.4.3-1 show the signalling control plane procedures for the MCPTT client initiating an MCPTT private call call-back cancel request with the chosen MCPTT user. + +Pre-conditions: + +1. A previously successfully made MCPTT private call call-back request from MCPTT client 1 to MCPTT client 2. + +![Sequence diagram showing the MCPTT private call call-back cancel request process between MCPTT client 1, MCPTT server, and MCPTT client 2. The steps are: 1. Client 1 wants to cancel a request; 2. Client 1 sends a cancel request to the server; 3. Server authorizes the request; 4. Server sends the cancel request to Client 2; 5. Client 2 removes stored information; 6. Client 2 sends a response to the server; 7. Server informs Client 1 of the cancellation.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note left of MCPTT client 1: 1. Wants to cancel a previous call-back request + MCPTT client 1->>MCPTT server: 2. MCPTT private call call-back cancel request + Note right of MCPTT server: 3. Authorize cancel request + MCPTT server->>MCPTT client 2: 4. MCPTT private call call-back cancel request + Note right of MCPTT client 2: 5. Remove the stored call-back request information + MCPTT client 2->>MCPTT server: 6. MCPTT private call call-back cancel response + MCPTT server->>MCPTT client 1: 7. MCPTT private call call-back cancel response + +``` + +Sequence diagram showing the MCPTT private call call-back cancel request process between MCPTT client 1, MCPTT server, and MCPTT client 2. The steps are: 1. Client 1 wants to cancel a request; 2. Client 1 sends a cancel request to the server; 3. Server authorizes the request; 4. Server sends the cancel request to Client 2; 5. Client 2 removes stored information; 6. Client 2 sends a response to the server; 7. Server informs Client 1 of the cancellation. + +**Figure 10.7.4.3-1: MCPTT private call call-back cancel request – MCPTT users in the same MCPTT system** + +1. MCPTT user on MCPTT client 1 wants to cancel a previously created MCPTT private call call-back request to the MCPTT user 2 of MCPTT client 2. +2. MCPTT client 1 sends an MCPTT private call call-back cancel request towards the MCPTT server. +3. MCPTT server checks whether the MCPTT user 1 at MCPTT client 1 is authorized to cancel the previous MCPTT private call call-back request, if one exists. +4. If authorized, MCPTT server sends the corresponding MCPTT private call call-back cancel request towards the MCPTT client 2. +5. The receiving MCPTT client 2 removes all stored information about the previous MCPTT private call call-back request from the MCPTT user 1 on MCPTT client 1. +6. The receiving MCPTT client 2 sends an MCPTT private call call-back cancel response to the MCPTT server. +7. Upon receiving the MCPTT private call call-back cancel response from MCPTT client 2, the MCPTT server informs the MCPTT client 1 about successful call-back request cancelation. + +#### 10.7.4.4 MCPTT private call call-back request fulfillment within one MCPTT system + +Once an MCPTT private call call-back request has been successfully made, it is expected that the receiving MCPTT user will make an MCPTT private call to the MCPTT user who sent the MCPTT private call call-back request. The procedures for establishing the MCPTT private call between the two users is the same as an MCPTT private call (10.7.2.2.2). + +Procedures in figure 10.7.4.4-1 show the signalling control plane procedures for the MCPTT client returning an MCPTT private call to the MCPTT user who initiated the MCPTT private call call-back request. + +Pre-conditions: + +1. A previously successfully made MCPTT private call call-back request from MCPTT client 1 to MCPTT client 2. + +![Sequence diagram showing MCPTT private call-back request fulfillment. The diagram involves three participants: MCPTT client 1, MCPTT server, and MCPTT client 2. The process starts with a call from client 2 to client 1 via the server. After the call, client 2 sends a message to the server to remove stored call-back request information.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note right of MCPTT client 2: 1. MCPTT private call in manual commencement mode procedures + MCPTT client 2->>MCPTT client 1: + Note right of MCPTT client 2: 2. Remove stored call-back request information + MCPTT client 2->>MCPTT server: + +``` + +Sequence diagram showing MCPTT private call-back request fulfillment. The diagram involves three participants: MCPTT client 1, MCPTT server, and MCPTT client 2. The process starts with a call from client 2 to client 1 via the server. After the call, client 2 sends a message to the server to remove stored call-back request information. + +**Figure 10.7.4.4-1: MCPTT private call-back request fulfillment – MCPTT users in the same MCPTT system** + +1. MCPTT user 2 on MCPTT client 2 decides to initiate an MCPTT private call based on the stored MCPTT private call call-back request to the MCPTT user 1 on MCPTT client 1 using the MCPTT private call procedures of 10.7.2.2.2. +2. Once a successful MCPTT private call has been made between the MCPTT user 1 on MCPTT client 1 and MCPTT user 2, then the MCPTT client 2 removes the stored call-back request information. + +## 10.8 Simultaneous session for MCPTT calls (on-network) + +### 10.8.1 General + +An MCPTT client and MCPTT server may use a simultaneous session as defined in 3GPP TS 23.280 [16] for MCPTT calls. The MCPTT client becomes involved in a simultaneous session for MCPTT calls by inviting, joining or accepting more than one MCPTT call, or affiliating to a group. + +NOTE: An MCPTT client affiliating to multiple MCPTT groups with active calls will result in the MCPTT client being invited simultaneously to multiple MCPTT calls. + +The MCPTT client can also still handle multiple MCPTT calls in parallel at the same time i.e. using multiple dialogs. + +The simultaneous session is established during either an originating on-demand call establishment or during pre-established session establishment or a modification of an already established pre-established session or on-demand call. + +It is possible to change the prioritisation while the MCPTT client is engaged in multiple MCPTT calls. The setting of the priority can be made at MCPTT call setup or by performing a modification after the MCPTT call is established. This may result in more than one media bearer. + +## 10.9 Floor control + +### 10.9.1 Floor control for on-network MCPTT service + +#### 10.9.1.1 General + +The procedure is for providing a floor control to MCPTT UE in an on-network case and applies for both private call and group call. Floor control is performed by using floor control information flows between the floor participant and the floor control server. + +#### 10.9.1.2 Information flows for floor control for on-network + +##### 10.9.1.2.1 General + +When the floor control server receives a floor request from the floor participant, it decides whether to give a grant or not based on, e.g., the session status (i.e., whether the grant is given to another user or not), user profile, priority. The result + +is informed to the requesting floor participant. When the floor participant receives a floor granted message, it can send voice media over the uplink bearer established beforehand. The floor revoked message can be used as part of override. The floor queue status request can be used to know current position in the queue for floor. + +Some floor control information flows can also piggyback call control information flows to provide efficient call setup and clearing: + +- Call setup request is optionally carried in floor request (uplink) or floor taken (downlink, can be broadcast); and +- Call release request is optionally carried in floor release (uplink) or floor idle (downlink, can be broadcast). + +##### 10.9.1.2.2 Floor request + +Table 10.9.1.2.2-1 describes the information flow floor request, from the floor participant to the floor control server and from the floor control server to the floor control server, which is used to request the floor for media transfer. This information flow is sent in unicast to the floor control server. + +**Table 10.9.1.2.2-1: Floor request** + +| Information element | Status | Description | +|----------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCP TT ID | M | Requester identity | +| Functional alias | O | Functional alias of the requester | +| Floor priority | M | Priority of the request | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Location Information | O | Location information | + +##### 10.9.1.2.3 Floor granted + +Table 10.9.1.2.3-1 describes the information flow floor granted, from the floor control server to the floor participant and from the floor control server to the floor control server, which is used to indicate that a request for floor is granted and media transfer is possible. This information flow is sent in unicast (to the granted floor participant). + +**Table 10.9.1.2.3-1: Floor granted** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Duration | M | The time for which the granted party is allowed to transmit | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +##### 10.9.1.2.4 Floor rejected + +Table 10.9.1.2.4-1 describes the information flow floor rejected, from the floor control server to the floor participant, which is used to indicate that a request for the floor is rejected. This information flow is sent in unicast (to the refused floor participant). + +**Table 10.9.1.2.4-1: Floor rejected** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Rejection cause | O | Indicates the cause for floor rejection | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +##### 10.9.1.2.5 Floor request cancel + +Table 10.9.1.2.5-1 describes the information flow floor request cancel, from the floor participant to the floor control server, which is used to request cancelling the floor request from the floor request queue. This information flow is sent in unicast to the floor control server. + +**Table 10.9.1.2.5-1: Floor request cancel** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCP TT ID | M | Identity for the requester | +| Functional alias | O | Functional alias for the requester | +| List of MCP TT IDs | M | Target identity (Identities) whose floor request is to be cancelled | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 10.9.1.2.6 Floor request cancel response + +Table 10.9.1.2.6-1 describes the information flow floor request cancel response, from the floor control server to the floor control participant, which is used to indicate the response for the floor request cancellation. This information flow is sent in unicast. + +**Table 10.9.1.2.6-1: Floor request cancel response** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +##### 10.9.1.2.7 Floor request cancel notify + +Table 10.9.1.2.7-1 describes the information flow floor request cancel notify, from the floor control server to the floor control participant, which is used to indicate the floor request is cancelled by the administrator/floor control server. This information flow is sent in unicast or broadcast. + +**Table 10.9.1.2.7-1: Floor request cancel notify** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCP TT ID | M | Identity of the administrator | +| Functional alias | O | Functional alias of the administrator | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +##### 10.9.1.2.8 Floor idle + +Table 10.9.1.2.8-1 describes the information flow floor idle, from the floor control server to the floor participant, which is used to indicate that a session is in idle status, i.e. the floor is not granted to any party. This information flow is sent in unicast or broadcast. + +**Table 10.9.1.2.8-1: Floor idle** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +##### 10.9.1.2.9 Floor release + +Table 10.9.1.2.9-1 describes the information flow floor release, from the floor participant to the floor control server, which is used to indicate the media transfer is completed and floor is released. This information flow is sent in unicast to the floor control server. + +**Table 10.9.1.2.9-1: Floor release** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +###### 10.9.1.2.9a Multi-talker floor release + +Table 10.9.1.2.9a-1 describes the information elements of floor release for multi-talker control, from the floor control server to the floor participants, which is used to indicate the media transfer is completed and floor is released. This information flow is sent in unicast from the floor control server. + +**Table 10.9.1.2.9a-1: Multi-talker floor release** + +| | | | +|---------------------------------------------------------------------------|---|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID (NOTE) | M | Identity of participant releasing the floor | +| List of functional aliases (NOTE) | O | Functional alias(es) of participant releasing the floor | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| NOTE: One or more functional aliases may be associated with the MCPTT ID. | | | + +##### 10.9.1.2.10 Floor taken + +Table 10.9.1.2.10-1 describes the information flow floor taken, from the floor control server to the floor participant, which is used to indicate the floor is granted to another MCPTT user. This information flows is sent in unicast or broadcast. + +**Table 10.9.1.2.10-1: Floor taken** + +| Information element | Status | Description | +|---------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity for the granted party | +| Functional alias | O | Functional alias for the granted party | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Permission to request the floor | O | Indicates whether receiving parties are allowed to request the floor or not (e.g. broadcast call). | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | +| Location Information | O | Location information | + +##### 10.9.1.2.10a Multi-talker floor taken + +Table 10.9.1.2.10a-1 describes the information elements of floor taken for multi-talker control, from the floor control server to the floor participant, which is used to indicate when the floor is simultaneously granted to multiple MCPTT users. The multi-talker floor taken is sent in unicast or broadcast. + +**Table 10.9.1.2.10a-1: Multi-talker floor taken** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| List of MCPTT IDs (NOTE) | M | Identity (identities) of the granted participant(s) | +| List of functional aliases (NOTE) | O | Functional alias(es) of the granted participant(s) | +| List of source identifiers (NOTE) | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | +| NOTE: One or more functional aliases and one source identifier may be associated with an MCPTT ID. | | | + +##### 10.9.1.2.11 Floor revoked + +Table 10.9.1.2.11-1 describes the information flow floor revoked, from the floor control server to the floor participant, which is used to indicate the floor is revoked from its current holder (the floor participant who was granted the floor). This information flows is sent in unicast (to the revoked floor participant). + +**Table 10.9.1.2.11-1: Floor revoked** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +##### 10.9.1.2.12 Floor acknowledgement + +Table 10.9.1.2.12-1 describes the information flow floor acknowledgement, from the floor participant to the floor control server, which is used to provide an acknowledgement if the acknowledgement is required in the received floor control message. + +NOTE: The floor acknowledgement flow can be sent by the floor participant after each floor control information flow that includes an indication that an acknowledgement is required. The procedures defined in subclauses 10.9.1.3 to 10.9.1.5 do not explicitly illustrates all scenarios when floor acknowledgement can be used. + +**Table 10.9.1.2.12-1: Floor acknowledgement** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------| +| MCPTT ID | M | Identity of the sender. | +| Functional alias | O | Functional alias of the sender. | + +##### 10.9.1.2.13 Queue position request + +Table 10.9.1.2.13-1 describes the information flow queue position request, from the floor participant to the floor control server, which is used to request the position in the floor request queue. The MCPTT server and the MCPTT client support queuing of the floor control requests shall support this information flow. This information flow is sent in unicast to the floor control server. + +**Table 10.9.1.2.13-1: Queue position request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 10.9.1.2.14 Queue position info + +Table 10.9.1.2.14-1 describes the information flow queue position info, from the floor control server to the floor participant, which is used to indicate the floor request is queued and the queue position to the floor requesting UE. The MCPTT server and the MCPTT client support queuing of the floor control requests shall support this information flow. This information flows is sent in unicast (to the queued floor participant). + +**Table 10.9.1.2.14-1: Queue position info** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Queue position info | M | Position of the queued floor request in the queue | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +##### 10.9.1.2.15 Unicast media stop request + +Table 10.9.1.2.15-1 describes the information flow unicast media stop request from the floor participant to the floor control server, which is used by the floor participant to indicate that the unicast media flow of the designated communication does not need to be sent to the MCPTT client. + +**Table 10.9.1.2.15-1: Unicast media stop request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of the requester | +| Functional alias | O | Functional alias for the requester | +| Source identifier | O | Identifies the communication whose media flow is to be stopped, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 10.9.1.2.16 Unicast media resume request + +Table 10.9.1.2.16-1 describes the information flow unicast media resume request from the floor participant to the floor control server, which is used by the floor participant to request that the unicast media flow of the designated communication is to be sent to the MCPTT client. + +**Table 10.9.1.2.16-1: Unicast media resume request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of the requester | +| Functional alias | O | Functional alias of the requester | +| Source identifier | O | Identifies the communication whose media flow is to be resumed, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +#### 10.9.1.3 Floor control within one MCPTT system + +##### 10.9.1.3.1 Floor request, floor granted and floor taken during an MCPTT session + +Figure 10.9.1.3.1-1 shows the high level procedure that the floor control is conducted for the MCPTT session already established between the floor participant and the floor control server. Only two UEs involved in the session are shown for the simplicity. + +Pre-condition: + +- 1. MCPTT session is established between MCPTT clients (client A and client B) and MCPTT server. + +![Sequence diagram titled 'MCPTT Service Provider' showing floor control interactions between Floor participant A, Floor control server, and Floor participant B. The sequence includes steps: 1. Floor control establishment; 2. User wants to talk (A); 3. Floor request (A to server); 4. Arbitration (server); 5a. Floor granted (server to A); 5b. Floor taken (server to B); 5c. Floor acknowledgement (A to server); 5d. Floor acknowledgement (B to server); 6a. Grant notification (A); 6b. Talker notification (B); 7. Voice media (A to B); 8. User wants to talk (B); 9. Floor request (B to server); 10. Floor request queued (server); 11a. Queue position info (server to B); 11b. Floor acknowledgement (B to server).](4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg) + +Sequence diagram titled 'MCPTT Service Provider' showing floor control interactions between Floor participant A, Floor control server, and Floor participant B. The sequence includes steps: 1. Floor control establishment; 2. User wants to talk (A); 3. Floor request (A to server); 4. Arbitration (server); 5a. Floor granted (server to A); 5b. Floor taken (server to B); 5c. Floor acknowledgement (A to server); 5d. Floor acknowledgement (B to server); 6a. Grant notification (A); 6b. Talker notification (B); 7. Voice media (A to B); 8. User wants to talk (B); 9. Floor request (B to server); 10. Floor request queued (server); 11a. Queue position info (server to B); 11b. Floor acknowledgement (B to server). + +**Figure 10.9.1.3.1-1: Floor request, floor granted, floor taken during an MCPTT session** + +- 1. The floor control is established between the floor participants and floor control server. It is assumed that the floor is now in idle status. +- 2. Floor participant A wants to send voice media over the session. +- 3. Floor participant A sends a floor request message to floor control server which includes floor priority and other information as necessary. +- 4. Floor control server makes the determination on what action (grant, deny, or queue) to take on the request based on criteria (e.g., floor priority, participant type) and determines to accept the floor request from floor + +participant A. The floor control server may limit the time a user talks (hold the floor) as allowed by the configuration. + +- 5a. Floor control server responds with a floor granted message to floor participant A including the maximum floor granted duration e.g., if no other floor participant has the permission for transmission. +- 5b. Floor control server sends a floor taken message to the other floor participant (floor participant B) including information about who is granted the floor. +- 5c. Floor participant A sends a floor acknowledgement if indicated to do so by the floor granted message. +- 5d. Floor participant B sends a floor acknowledgement if indicated to do so by the floor taken message. +- 6a. The floor granted shall cause the user of UE A where the floor participant A is located to be notified. +- 6b. The receipt of the floor taken may be used to inform the user of UE B where the floor participant B is located. +7. Floor participant A starts sending voice media over the session established beforehand. + +NOTE: Voice media can continue to be sent while steps 8 through 11 occur. + +8. Suppose there are one or more users requesting to talk at this time, the floor request(s) are queued as decided by floor control server e.g., based on floor priority. +9. Floor participant B sends a floor request message. +10. Floor control server queues the request of floor participant B. +- 11a. Floor control server sends queue position info to floor participant B. +- 11b. Floor participant B sends a floor acknowledgement if indicated to do so by the queue position info message. + +##### 10.9.1.3.1a Floor request, floor granted and multi-talker floor taken during an MCPTT session enhanced with multi-talker control + +Figure 10.9.1.3.1a-1 shows the high level procedure that allows several participants to talk simultaneously in a MCPTT session already established between the floor participant and the floor control server. Three UEs involved in the session are shown for simplicity. + +Pre-conditions: + +1. The MCPTT group is configured to support multi-talker control and audio mixing by the network is applied. +2. MCPTT session is established between MCPTT clients (client A, client B and client C) and MCPTT server. +3. Participants A and B have the permission to talk to all other participants and the floor is granted to floor participant B. + +![Sequence diagram illustrating floor request, floor granted, and multi-talker floor taken during an MCPTT session. The diagram shows interactions between MCPTT client A (New Talker), MCPTT server, MCPTT client B (Talker), and MCPTT client C (Listener).](8269648391c59363ea61243864a2adf7_img.jpg) + +``` + +sequenceDiagram + participant Client A as MCPTT client A (New Talker) + participant Server as MCPTT server + participant Client B as MCPTT client B (Talker) + participant Client C as MCPTT client C (Listener) + + Note left of Client A: 2. User A wants to talk + Client B->>Server: 1. Voice media (B) + Server-->>Client A: 1. Voice media (B) + Server-->>Client C: 1. Voice media (B) + Client A->>Server: 3. Floor request + Note right of Server: 4. Based on arbitration result e.g., considering floor priority, maximum number of simultaneous talkers + Server-->>Client A: 5a. Floor granted + Server-->>Client B: 5b. Multi-talker floor taken + Server-->>Client C: 5c. Multi-talker floor taken + Note left of Client A: 6a. Grant notification + Note right of Client B: 6b. Multi-talker floor taken notification without floor revoked + Note right of Client C: 6c. Multi-talker floor taken notification + Client A-->>Server: 7. Voice media (A) + Server-->>Client B: 7. Voice media (A) + Server-->>Client C: 7. Voice media (A and B) + Client A-->>Server: 7. Voice media (B) + Server-->>Client B: 7. Voice media (B) + +``` + +Sequence diagram illustrating floor request, floor granted, and multi-talker floor taken during an MCPTT session. The diagram shows interactions between MCPTT client A (New Talker), MCPTT server, MCPTT client B (Talker), and MCPTT client C (Listener). + +**Figure 10.9.1.3.1a-1: Floor request, floor granted and multi-talker floor taken during an MCPTT session** + +1. Floor participant B is talking and is sending the voice media. + 2. Floor participant A wants to send voice media over the session. + 3. Floor participant A sends a floor request message to the floor control server which includes the necessary information, e.g. floor priority. + 4. Based on applicable criteria (e.g. floor priority, participant type, allowance to transmit, maximum number of simultaneous talkers) floor control server determines what action (grant, deny, or queue) shall be applied to the request. In this case, the floor request from floor participant A will be accepted. Simultaneous floor requests to transmit are handled in a sequential order. Based on the group configuration repository data, the floor control server may limit the time a floor participant is allowed to talk. + - 5a. Floor control server responds with a floor granted message to floor participant A. + - 5b. Floor control server sends a multi-talker floor taken message to floor participant B. + - 5c. Floor control server sends a multi-talker floor taken message to floor participant C. + - 5d. Floor control server may send a multi-talker floor taken message to floor participant A. + - 6a. The floor granted shall cause the user of UE A, where the floor participant A is located, to be notified. + - 6b. The multi-talker floor taken shall inform the user of UE B, that the floors are granted to other floor participants, but the floor is not revoked. + - 6c. The multi-talker floor taken shall inform the user of UE C floor participants list the floor are currently granted to. + 7. Floor participant A starts sending voice media over the session established beforehand, i.e. participants A and B receive and transmit voice media; participant C only receives voice media. +- NOTE: Floor control is independent from whether audio mixing is performed by the MCPTT server or by the UE. + +##### 10.9.1.3.2 Floor override + +###### 10.9.1.3.2.1 Floor override using floor revoked (also floor rejected) during an MCPTT session + +Figure 10.9.1.3.2.1-1 shows the high level procedure that the floor control is conducted for the MCPTT session already established between the floor participant (with floor granted to floor participant B) and the floor control server (with an override based on priority). Only two UEs involved in the session are shown for the simplicity. + +![Sequence diagram illustrating floor override using floor revoked (also floor rejected) during an MCPTT session. The diagram shows interactions between Floor participant A, Floor control server, and Floor participant B within a Home MCPTT Service Provider. The process starts with an established session where floor is granted to participant B. Participant A then requests the floor. The server arbitrates and revokes the floor from B, granting it to A. B receives a revoke notification. A receives a grant notification and starts voice media. B then requests the floor again, but the server rejects it based on arbitration, sending a reject notification to B.](a5184899f915014fa38608754efcc9c7_img.jpg) + +``` + +sequenceDiagram + participant A as Floor participant A + participant S as Floor control server + participant B as Floor participant B + Note over A, S, B: 1. Session is established, Floor control is established between floor participant and floor control server. Floor granted to floor participant B + Note left of A: 2. User wants to talk + A->>S: 3. Floor request + Note right of S: 4. Based on arbitration result e.g., considering priority + S->>B: 4. Floor revoked + Note right of B: 5. Revoke notification + S->>A: 6. Floor granted + S->>B: 6. Floor Taken + Note left of A: 7. Grant notification + Note right of B: 7. Talker notification + A->>S: 8. Voice media + S->>B: 8. Voice media + Note right of B: 9. User wants to talk + B->>S: 10. Floor request + Note right of S: 11. Based on arbitration result e.g., considering priority + S->>B: 12. Floor rejected + Note right of B: 13. Reject notification + +``` + +Sequence diagram illustrating floor override using floor revoked (also floor rejected) during an MCPTT session. The diagram shows interactions between Floor participant A, Floor control server, and Floor participant B within a Home MCPTT Service Provider. The process starts with an established session where floor is granted to participant B. Participant A then requests the floor. The server arbitrates and revokes the floor from B, granting it to A. B receives a revoke notification. A receives a grant notification and starts voice media. B then requests the floor again, but the server rejects it based on arbitration, sending a reject notification to B. + +**Figure 10.9.1.3.2.1-1: Floor override using floor revoked (also floor rejected) during an MCPTT session** + +1. It is assumed that floor participant B has been given floor and is transmitting voice media. +2. Floor participant A having a priority which is relatively higher than that of floor participant B wants to send voice media over the session. +3. Floor participant A sends a floor request message to the floor control server. +4. The floor control server determines to accept the floor request from floor participant A based on arbitration result e.g., according to the priority information that is received in the floor request message. The floor control server sends a floor revoked message to floor participant B stopping the voice media transmission from floor participant B. +5. The user of floor participant B may be notified that the floor is revoked. +6. The Floor control server sends a floor granted message to floor participant A, while sending a floor taken message to floor participant B with information of who is granted the floor. + +7. The user of floor participant A may be notified that he is granted the floor. Similarly, the user of floor participant B may be notified who is granted the floor. +8. Floor participant A starts sending voice media over the session established beforehand. +9. Now floor participant B may want the floor to start sending voice media. +10. Floor participant B sends a floor request message to floor control server which may include priority information. +11. Floor control server determines whether to accept the floor request from floor participant B based on arbitration result e.g., according to the priority information that is received in the floor request message. +12. The floor control server responds with a floor rejected message to floor participant B. +13. Floor participant B may be notified that he is rejected. + +###### 10.9.1.3.2.2 Floor override without using floor revoked during an MCPTT session + +Figure 10.9.1.3.2.2-1 shows the high level procedure that the floor control is conducted for the MCPTT session already established between the floor participants (with floor granted to floor participant B) and the floor control server (with an override based on priority and configured to permit the transmission of the overridden floor participant B to continue). Only two UEs involved in the session are shown for the simplicity. + +###### Pre-conditions + +- The floor control server has been configured to support override. +- The override supported in this case permits both the overridden floor participant and the overriding floor participant to be transmitting. + +![Sequence diagram illustrating floor override during an MCPTT session. The diagram shows interactions between Floor participant A, Floor control server, and Floor participant B under the MCPTT Service Provider. The process starts with an established session where Floor participant B has the floor. Floor participant A wants to talk and sends a floor request. The server arbitrates based on priority and grants the floor to A while taking it from B. Notifications are sent to both participants, and voice media from both continues.](a97518a839da75f8379c578562b01bc2_img.jpg) + +``` + +sequenceDiagram + participant A as Floor participant A + participant S as Floor control server + participant B as Floor participant B + Note right of B: 1. Session is established. Floor control is established between floor participants and floor control server. Floor granted to floor participant B. + Note left of A: 2. User wants to talk + A->>S: 3. Floor request + Note right of S: 4. Based on arbitration result e.g., considering floor priority + S->>A: 5a. Floor granted + S->>B: 5b. Floor taken + Note left of A: 6a. Grant notification + Note right of B: 6b. Override notification + Note right of B: 7. Voice media + +``` + +Sequence diagram illustrating floor override during an MCPTT session. The diagram shows interactions between Floor participant A, Floor control server, and Floor participant B under the MCPTT Service Provider. The process starts with an established session where Floor participant B has the floor. Floor participant A wants to talk and sends a floor request. The server arbitrates based on priority and grants the floor to A while taking it from B. Notifications are sent to both participants, and voice media from both continues. + +**Figure 10.9.1.3.2.2-1: Floor override (overridden continues to transmit) during an MCPTT session** + +1. It is assumed that floor participant B has been given the floor and is transmitting voice media. +2. Floor participant A having a floor priority which is relatively higher than that of floor participant B wants to send voice media over the session. + +3. Floor participant A sends a floor request message to the floor control server. + 4. The floor control server determines to accept the floor request from floor participant A based on arbitration result e.g., according to the floor priority information that is received in the floor request message. + - 5a. Floor control server responds with a floor granted message to floor participant A. + - 5b. Floor control server sends a floor taken message to the other floor participants (including floor participant B). Floor participant B continues transmitting the (overridden) voice media transmission. +- NOTE 1: All other floor participants (not shown) that are part of this group call receive a floor taken message, so that the other floor participants learn who the newly granted talker (overriding) is. +- 6a. The floor granted causes the user of floor participant A to be notified. + - 6b. The user of floor participant B is notified of the status that the floor is now taken by floor participant A. + 7. Floor participant A (overriding) starts sending voice media over the session established beforehand. +- NOTE 2: Floor participant B is still sending voice (overridden). The list of floor participants that receive the overriding, overridden, or both transmissions is based on configuration. + +###### 10.9.1.3.2.3 Floor override using floor revoked (also floor rejected) during an MCPTT session enhanced with multi-talker control + +Figure 10.9.1.3.2.3-1 shows the high-level procedure that the floor control allows several participants to talk simultaneously in a MCPTT session already established between the floor participant (with floor granted to floor participant B) and the floor control server. Only two UEs involved in the session are shown for the simplicity. + +Pre-conditions: + +1. The MCPTT group is configured to support multi-talker control. +2. MCPTT session is established between MCPTT clients (client A, client B and client C) and MCPTT server. +3. The maximum number of simultaneous talkers is set to 2. +4. The floor priority of floor participant A is higher than of floor participant B. +5. The floor is granted to floor participant B and floor participant C. + +![Sequence diagram illustrating floor override using floor revoked (also floor rejected) during an MCPTT session. The diagram shows interactions between MCPTT client A (New Talker), MCPTT server, MCPTT client B (Talker), and MCPTT client C (Talker).](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +``` + +sequenceDiagram + participant Client A as MCPTT client A (New Talker) + participant Server as MCPTT server + participant Client B as MCPTT client B (Talker) + participant Client C as MCPTT client C (Talker) + + Note right of Client B: 1. Voice media (B) + Note right of Client C: 1. Voice media (C) + Server-->Client A: 1. Voice media (B and C) + Note right of Client B: 1. Voice media (B) + Note right of Client C: 1. Voice media (C) + + Note left of Client A: 2. User A wants to talk + Client A->>Server: 3. Floor request + Note right of Server: 4. Based on arbitration result e.g., considering floor priority, maximum number of simultaneous talkers + Server-->>Client B: 5. Floor revoked + Note right of Client B: 6. Revoke notification + + Server-->>Client A: 7. Floor granted + Note left of Client A: 8. Grant notification + Server-->>Client B: 7. Multi-talker floor taken + Note right of Client B: 8. Multi-talker notification + Server-->>Client C: 7. Multi-talker floor taken + Note right of Client C: 8. Multi-talker notification + + Note right of Client A: 9. Voice media (A) + Note right of Client B: 9. Voice media (C) + Note right of Client C: 9. Voice media (A and C) + Note right of Client A: 9. Voice media (C) + Note right of Client B: 9. Voice media (A) + Note right of Client C: 9. Voice media (A) + + Note right of Client B: 10. User B wants to talk + Client B->>Server: 11. Floor request + Note right of Server: 12. Based on arbitration result e.g., considering floor priority, maximum number of simultaneous talkers + Server-->>Client B: 13. Floor rejected + Note right of Client B: 14. Reject notification + +``` + +Sequence diagram illustrating floor override using floor revoked (also floor rejected) during an MCPTT session. The diagram shows interactions between MCPTT client A (New Talker), MCPTT server, MCPTT client B (Talker), and MCPTT client C (Talker). + +**Figure 10.9.1.3.2.3-1: Floor override using floor revoked (also floor rejected) during an MCPTT session** + +1. Floor participant B and floor participant C are sending voice media over the session established. +2. Floor participant A wants to send voice media over the session. +3. Floor participant A wants to talk (i.e. send voice media) over the session. Floor participant A sends a floor request message to the floor control server. +4. Based on an arbitration result (e.g. per the priority information that is received in the floor request message), the floor control server determines to accept the floor request from floor participant A. The maximum number of simultaneous talkers in the MCPTT group has been reached, the floor control server decides to apply the override mechanism. +5. The floor control server sends a floor revoked message to floor participant B stopping the voice media transmission of floor participant B. +6. The user of floor participant B may be notified that the floor is revoked. +7. The Floor control server sends a floor granted message to floor participant A, while sending a multi-talker floor taken message to floor participant B and floor participant C including the information to whom the floor has been granted. +8. The user of floor participant A may be notified that the floor has been granted to him. Similarly, the user of floor participant B and floor participant C may be notified to whom the floor has been granted. + +9. Floor participant A starts sending voice media over the session established beforehand. +10. Now floor participant B may want the floor to start sending voice media. +11. Floor participant B sends a floor request message to floor control server that may include participant priority information. +12. Based on arbitration result, e.g. per the priority information that is received in the floor request message, and if the number of MCPTT Users has already reached the maximum number of simultaneous talkers in the group, the floor control server determines whether to accept or reject the floor request from floor participant B. Due to lower priority of participant B and the applicable limitation of simultaneous talkers, the floor control server rejects the floor request. +13. The floor control server responds with a floor rejected message to floor participant B. +14. Floor participant B may be notified about the floor rejection. + +NOTE: Floor control procedure is independent from whether audio mixing is performed by the MCPTT server or by the UE. + +###### 10.9.1.3.2.4 Floor release during an MCPTT session enhanced with multi-talker control + +Figure 10.9.1.3.2.4-1 shows the high-level procedure where the floor controller allows a participant to release the floor while other participants continue to talk simultaneously in a MCPTT session already established between the floor participants and the floor control server. Only three UEs involved in the session are shown for simplicity. + +Pre-conditions: + +1. The MCPTT group is configured to support multi-talker control and audio mixing by the network is applied. +2. MCPTT session is established between MCPTT clients (client A, client B, and client C) and the MCPTT server. +3. Participants A, B, and C have the permission to talk to all other participants, and the floor is granted to floor participants A, B, and C. + +![Sequence diagram illustrating floor release during an MCPTT session. Lifelines: MCPTT client A (Talker), MCPTT server, MCPTT client B (Talker), MCPTT client C (Talker). The sequence shows voice media exchange, a floor release request from A, server notifications to B and C, and subsequent voice media exchange between B and C.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +``` + +sequenceDiagram + participant A as MCPTT client A (Talker) + participant S as MCPTT server + participant B as MCPTT client B (Talker) + participant C as MCPTT client C (Talker) + + Note left of A: 2. User A stops talking + A->>S: 1. Voice media (A) + S->>B: 1. Voice media (B) + S->>C: 1. Voice media (C) + S->>A: 1. Voice media (B and C) + S->>C: 1. Voice media (A and B) + Note left of A: 3. Floor release + A->>S: 3. Floor release + S->>B: 4. Multi-talker floor release + S->>C: 4. Multi-talker floor release + Note right of B: 4a. Multi-talker floor release notification + Note right of C: 4a. Multi-talker floor release notification + S->>B: 5. Voice media (B) + S->>C: 5. Voice media (C) + S->>A: 5. Voice media (B and C) + S->>C: 5. Voice media (B) + S->>B: 5. Voice media (C) + +``` + +Sequence diagram illustrating floor release during an MCPTT session. Lifelines: MCPTT client A (Talker), MCPTT server, MCPTT client B (Talker), MCPTT client C (Talker). The sequence shows voice media exchange, a floor release request from A, server notifications to B and C, and subsequent voice media exchange between B and C. + +**Figure 10.9.1.3.2.4-1: Floor release during an MCPTT session** + +1. Floor participants A, B and C are sending voice media over the established session. +2. User A stops talking and wants to stop sending voice media over the session. +3. Floor participant A sends a floor release message to the floor control server. +4. The floor control server accepts the floor release from floor participant A and sends a multi-talker floor release message to floor participant B and floor participant C. +- 4a. The users of floor participant B and floor participant C may be notified that floor participant A has released the floor. +5. Floor participants B and C continue sending voice media over the established session. + +NOTE: Floor control procedures are independent from whether audio mixing is performed by the MCPTT server or by the UE. + +##### 10.9.1.3.3 Queue position during an MCPTT session + +Figure 10.9.1.3.3-1 shows the high level procedure that the floor control is conducted for the MCPTT session already established between MCPTT clients (with floor granted to floor participant B) and server (with an override based on priority at floor control server). Only two UEs involved in the session are shown for the simplicity. + +![Sequence diagram illustrating queue status during an MCPTT session. The diagram shows interactions between Floor participant A, Floor control server, and Floor participant B. The process starts with session establishment and floor granting to participant B, while participant A and others are queued. Participant A then requests their queue position, and the server responds with the current position, informing the user.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +MCPTT Service Provider + +``` + +sequenceDiagram + participant A as Floor participant A + participant S as Floor control server + participant B as Floor participant B + Note right of B: 1. Session is established. Floor control is established between floor participants and floor control server. Floor granted to floor participant B. Many floor participants requested floor (including floor participant A) which got queued. + Note left of A: 2. User wants to know queue position + A->>S: 3. Queue position request + Note right of S: 4. Current queue position for floor participant A + S->>A: 5. Queue position info + Note left of A: 6. User informed about queue position + +``` + +Sequence diagram illustrating queue status during an MCPTT session. The diagram shows interactions between Floor participant A, Floor control server, and Floor participant B. The process starts with session establishment and floor granting to participant B, while participant A and others are queued. Participant A then requests their queue position, and the server responds with the current position, informing the user. + +**Figure 10.9.1.3.3-1: Queue status during an MCPTT session** + +1. It is assumed that floor participant B has been given a floor granted and is transmitting voice media. There are several other floor participants (including floor participating A) requesting floor which get queued at the floor control server. +2. Floor participant A would like to know its current position in the floor request queue. +3. Floor participant A sends a queue position request message to the floor control server. +4. Floor control server determines the current queue position of floor participant A from the floor request queue. +5. Floor control server responds with the current position in queue position info message. +6. User at floor participant A is informed about the current queue position. + +##### 10.9.1.3.4 Floor request cancellation from the floor request queue + +###### 10.9.1.3.4.1 Floor request cancellation from the queue – MCPTT user initiated + +Figure 10.9.1.3.4.1-1 illustrates the procedure for floor request cancellation from the floor queue initiated by the MCPTT user. The MCPTT user may be an authorized user who has rights to cancel the floor requests of other MCPTT users, whose floor requests are in floor control queue. + +Pre-conditions: + +- It is assumed that floor participant B has been granted the floor and is transmitting voice media. There are several other floor participants (including floor participant A and floor participant C) requesting the floor which have been queued at the floor control server. + +![Sequence diagram for floor request cancellation from queue initiated by MCPTT user. The diagram shows four lifelines: Floor participant A (or MCPTT Dispatcher), Floor control server, Floor participant B, and Floor participant C. A box at the top indicates that floor control is established, floor is granted to participant B, and requests from A and C are in the queue. The sequence of messages is: 1. User wants to cancel a floor request (internal to participant A), 2. Floor request cancel (A to server), 3. Authorization check and removal from queue (internal to server), 4. Floor request cancel notify (server to participant C), and 5. Floor request cancel response (server to participant A).](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +Home MCPTT service provider + +``` + +sequenceDiagram + participant A as Floor participant A (or MCPTT Dispatcher) + participant S as Floor control server + participant B as Floor participant B + participant C as Floor participant C + + Note right of A: Floor control established between floor participants and floor control server. Floor is granted to participant B, and floor requests of floor participant A and floor participant C are in the floor queue. + + Note left of A: 1. User wants to cancel a floor request from the floor request queue + A->>S: 2. Floor request cancel + Note right of S: 3. Authorization check, and remove floor request from the floor queue + S-->>C: 4. Floor request cancel notify + S->>A: 5. Floor request cancel response + +``` + +Sequence diagram for floor request cancellation from queue initiated by MCPTT user. The diagram shows four lifelines: Floor participant A (or MCPTT Dispatcher), Floor control server, Floor participant B, and Floor participant C. A box at the top indicates that floor control is established, floor is granted to participant B, and requests from A and C are in the queue. The sequence of messages is: 1. User wants to cancel a floor request (internal to participant A), 2. Floor request cancel (A to server), 3. Authorization check and removal from queue (internal to server), 4. Floor request cancel notify (server to participant C), and 5. Floor request cancel response (server to participant A). + +**Figure 10.9.1.3.4.1-1: Floor request cancellation from queue initiated by MCPTT user** + +1. The floor participant A wants to remove the floor request from the floor request queue. If floor participant A is an authorized MCPTT user with the rights to cancel another MCPTT user's floor request, the authorized MCPTT user may request floor request cancellation for one or more floor participants, whose floor request needs to be removed from the floor queue. +2. The floor participant A sends a floor request cancel (initiating MCPTT ID) message to the floor control server. If the floor participant A wants to remove the floor request(s) of other participant(s), the target participant(s)' MCPTT ID should be included in this message. +3. The floor control server shall check whether the requesting floor participant has authorization to cancel the floor request(s). If authorized, the floor request(s) will be removed from the floor request queue. When current transmission is completed, floor control server will process the floor request from the updated floor request queue. +4. If the floor request cancel in step 3 is sent by an authorized user (e.g., dispatcher) to cancel the floor request(s) of other participant(s) from the floor request queue, the floor request cancel notify message is sent to the floor participant whose floor request was cancelled from the floor queue. +5. The floor control server provides a floor request cancel response to the floor participant A when the floor cancellation is completed. Optionally, the new queue position information may be notified to the floor participants whose floor requests are in the floor request queue (not shown in the figure). + +###### 10.9.1.3.4.2 Floor request cancellation from the queue - floor control server initiated + +Figure 10.9.1.3.4.2-1 illustrates the procedure for floor request cancellation from the queue initiated by the floor control server. Only two UEs involved in the session are shown for the simplicity. + +Pre-conditions: + +- It is assumed that floor participant B has been granted the floor and is transmitting voice media. There are several other floor participants (including floor participant A and participant C) requesting the floor which have been queued at the floor control server. + +![Sequence diagram titled 'Home MCPTT service provider' showing floor request cancellation. It features three lifelines: Floor participant A, Floor control server, and Floor participant C. A message box at the top states: 'Floor control established between floor participants and floor control server. Now floor is granted to participant B, and floor participant A and participant C have sent floor requests being put into queue.' Below this, the sequence of messages is: 1. Remove the floor request from the floor request queue based on policy (internal to server), 2. Floor request cancel notify (server to participant A), and 3. Queue position info (server to participant C).](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +Sequence diagram titled 'Home MCPTT service provider' showing floor request cancellation. It features three lifelines: Floor participant A, Floor control server, and Floor participant C. A message box at the top states: 'Floor control established between floor participants and floor control server. Now floor is granted to participant B, and floor participant A and participant C have sent floor requests being put into queue.' Below this, the sequence of messages is: 1. Remove the floor request from the floor request queue based on policy (internal to server), 2. Floor request cancel notify (server to participant A), and 3. Queue position info (server to participant C). + +**Figure 10.9.1.3.4.2-1: Floor request cancellation from queue initiated by floor control server** + +1. The floor control server removes the floor request from the floor request queue based on policy. e.g., expiration of a timer. In the case when floor control server receives repeated floor requests from a floor participant while the floor is occupied, the new floor request is accepted and added into the floor queue and the existing/former floor request is removed from the floor queue or the new floor request is rejected and the existing/former floor request of this floor participant is retained in the floor request queue. +2. The floor control server sends a floor request cancel notify to the floor participant(s) whose floor request is removed from the floor request queue. +3. Optionally, the newly queue position information is notified to the other floor participants whose floor requests are queued. + +#### **10.9.1.4 Floor control involving groups from multiple MCPTT systems** + +##### **10.9.1.4.1 Partner MCPTT system routes all floor control messages to primary MCPTT system's floor control server** + +The MCPTT users belonging to different groups in multiple MCPTT systems will participate in MCPTT media services (group communication, private calls, etc.) in scenarios like group hierarchies and temporary groups formed by group regroup. In this service delivery model involving multiple groups from different MCPTT systems, the floor control arbitration resides with the primary MCPTT system. This is determined in the group call setup stage. The MCPTT users of groups involved in the call session will transmit their floor control messages through the partner MCPTT systems to which they belong. In this scenario, the partner MCPTT systems request the floor control for its MCPTT user(s) from the floor control server of the primary MCPTT system. The protocol used for media plane signalling is non-SIP like RTCP. + +Figure 10.9.1.4.1-1 describes the procedure for floor control involving groups from multiple MCPTT systems. + +Pre-conditions: + +1. The security aspects of sharing the user information between primary and partner MCPTT systems shall be governed as per the service provider agreement between them. In this case, we consider the partner MCPTT system does not share all information of their users' to the primary MCPTT system (public information would still need to be shared). +2. The group 1 is hosted by primary MCPTT system and group 2 and 3 are hosted by the partner MCPTT system. +3. The floor participant 1 corresponds to the MCPTT user of group 1. The floor participant 2 corresponds to the MCPTT user of group 2. The floor participant 3 corresponds to the MCPTT user of group 3. The floor control server 1 belongs to primary MCPTT system. The floor control server 2 belongs to partner MCPTT system. + +4. The floor control server 1 is the floor arbitrator of the MCPTT group call. The floor control server 2 routes all floor control messages to and from the floor participants 2 and 3 and then floor control server 1. + +![Sequence diagram illustrating floor control (partner MCPTT system forwarding) involving groups from multiple MCPTT systems. The diagram shows interactions between five entities: Floor participant 1 (primary), Floor control server 1 (primary), Floor control server 2 (partner), Floor participant 2 (partner), and Floor participant 3 (partner). The process starts with session establishment, followed by floor requests from participants, arbitration by server 1, and subsequent floor granted/rejected/queue position notifications. Finally, voice media is established between participants 1 and 3.](bccc028d0e75bc30c41528056f581545_img.jpg) + +MCPTT Service Provider + +``` + +sequenceDiagram + participant FP1 as Floor participant 1 (primary) + participant FCS1 as Floor control server 1 (primary) + participant FCS2 as Floor control server 2 (partner) + participant FP2 as Floor participant 2 (partner) + participant FP3 as Floor participant 3 (partner) + + Note over FP1, FCS1, FCS2, FP2, FP3: 1. Session is established. Floor control is established among floor participants and floor control servers. + + Note left of FP1: 2. User wants to talk + FP1->>FCS1: 3. Floor request + FCS1->>FCS2: 4. Floor request + Note over FCS1, FCS2: 5. Group call arbitration according to policy (floor priority or order) + FCS1->>FCS2: 6. Floor granted + FCS2->>FP2: 7. Floor granted + Note right of FP2: 8. Grant notification + + Note left of FP2: 2. User wants to talk + FP2->>FCS2: 3. Floor request + FCS2->>FCS1: 4. Floor request + + Note right of FP3: 2. User wants to talk + FP3->>FCS2: 3. Floor request + FCS2->>FCS1: 4. Floor request + + Note over FCS1, FCS2: 9a.1. Floor rejected + FCS1->>FCS2: 9a.2. Floor rejected + Note right of FP3: 9a.3. Reject notification + Note right of FP3: 9b.3. User informed about queue position + + Note over FCS1, FCS2: 9b.1. Queue position info + FCS1->>FCS2: 9b.2. Queue position info + + Note left of FP1: 10a.1. Floor rejected + Note left of FP1: 10a.2. Reject notification + Note left of FP1: 10b.1. Queue position info + Note left of FP1: 10b.2. User informed about queue position + + FCS1->>FCS2: 11a. Floor taken + FCS1->>FCS2: 11b.1. Floor taken + FCS2->>FP2: 11b.2. Floor taken + FCS2->>FP3: 11b.2. Floor taken + + Note left of FP1: 12. Talker notification + Note right of FP3: 12. Talker notification + + Note over FP1, FP3: 13. Voice media + +``` + +Sequence diagram illustrating floor control (partner MCPTT system forwarding) involving groups from multiple MCPTT systems. The diagram shows interactions between five entities: Floor participant 1 (primary), Floor control server 1 (primary), Floor control server 2 (partner), Floor participant 2 (partner), and Floor participant 3 (partner). The process starts with session establishment, followed by floor requests from participants, arbitration by server 1, and subsequent floor granted/rejected/queue position notifications. Finally, voice media is established between participants 1 and 3. + +**Figure 10.9.1.4.1-1: Floor control (partner MCPTT system forwarding) involving groups from multiple MCPTT systems** + +1. An MCPTT group call involving group1, group 2 and group 3 is setup and active. +2. The MCPTT users want to talk. +3. The floor participants initiate a floor request to the floor control server of their corresponding MCPTT systems. (The requests may or may not occur at the same time). + +4. If only one floor request is received, or floor control server 2 handles the floor request sequentially, there is no arbitration performed and the corresponding floor request is forwarded to the floor control server 1. If the floor control server 2 receives multiple floor requests at the same time or during an interval, then it forwards the floor requests to the floor control server 1 (floor arbitrator for the MCPTT group call). As the floor participant information shall not be exposed, the floor priority related information or/and group information to be used by floor control server 1 should be included in the forwarded request. + 5. The floor control server 1 performs floor arbitration for the MCPTT group call and determines the floor request to be accepted. + 6. If the floor request from floor participant 2 of the partner MCPTT system is accepted, a floor granted is sent with permission to talk. The floor control messages from floor control server 1 are routed to floor participant 2 via the floor control server 2. + 7. When the floor control server 2 (partner) receives the floor granted, the floor control server 2 sends a floor granted message on to floor participant 2. + 8. The floor granted shall cause the user of the UE where the floor participant 2 is located to be notified. + 9. The primary floor control server 1 may (9a.1) send a floor rejected message, or (9b.1) send a queue position info message for each non-granted received floor requests forwarded from the floor control server 2 (partner). When the floor control server 2 (partner) receives the floor rejected message, then the floor control server 2 (partner) (9a.2) sends a floor rejected message to the appropriate floor participant. When the floor control server 2 (partner) receives the queue position info, then the floor control server 2 (partner) (9b.2) sends a queue position info message to the appropriate floor participant. + - 10a.1 If floor control server 1 rejects the floor request from floor participant 1, then a floor reject message is sent. + - 10a.2 Upon this being received the user of the UE where floor participant 1 is located may be notified. + - 10b.1 If floor control server 1 supports floor queue, queue position info message is sent to the floor participant 1. + - 10b.2 Upon this being received the user of the UE where floor participant 1 is located may be notified. +- NOTE 1: Steps 10a.1 through 10b.2 are optional as indicated by the dashed box enclosing them. However if this box is implemented then either information flow 10a or 10b would occur. +11. Since the floor is granted to floor participant 2 of the partner MCPTT system, then a floor taken is sent to all other floor participants ((11a) floor participant 1 and (11b.1) to floor control server 2 (partner) for forwarding to (11b.2) floor participant 3. + 12. The receipt of the floor taken may be used to inform the users of the UEs where the floor participant entity 1 and floor participant 3 are located to be notified. + 13. Upon successful floor granted, the group call media transmission occurs. + +NOTE 2: The media flow between the media gateways of primary and partner MCPTT systems have not been depicted in the figure for clarity. + +##### 10.9.1.4.2 Partner MCPTT system performs filtering of floor control messages entering and leaving the partner MCPTT system + +The MCPTT users belonging to different groups in multiple MCPTT systems will participate in MCPTT media services (group communication, private calls, etc.) in scenarios like group hierarchies and temporary groups formed by group regroup. In this service delivery model involving multiple groups from different MCPTT systems, the floor control arbitration resides with the primary MCPTT system. This is determined in the group call setup stage. The MCPTT users of groups involved in the call session will transmit their floor control messages through the partner MCPTT systems to which they belong. In this scenario, the partner MCPTT system filters its MCPTT users' floor requests before communicating with the floor control server of the primary MCPTT system. The protocol used for media plane signalling is non-SIP like RTCP. + +Figure 10.9.1.4.2-1 describes the procedure for floor control involving groups from multiple MCPTT systems. + +Pre-conditions: + +1. The security aspects of sharing the user information between primary and partner MCPTT systems shall be governed as per the service provider agreement between them. In this case, we consider the partner MCPTT system does not share all information of their users to the primary MCPTT system (public information would still need to be shared). +2. The group 1 is hosted by primary MCPTT system and group 2 and 3 are hosted by the partner MCPTT system. +3. The floor participant 1 corresponds to the MCPTT user of group 1. The floor participant 2 corresponds to the MCPTT user of group 2. The floor participant 3 corresponds to the MCPTT user of group 3. The floor control server 1 belongs to primary MCPTT system. The floor control server 2 belongs to partner MCPTT system. +4. The floor control server 1 is the floor arbitrator of the MCPTT group call. The floor control server 2 does floor control filtering with its floor participants 2 and 3 before communicating with the floor control server 1. + +![Sequence diagram titled 'MCPTT Service Provider' showing floor control interactions between Floor participant 1 (primary), Floor control server 1 (primary), Floor control server 2 (partner), Floor participant 2 (partner), and Floor participant 3 (partner). The diagram illustrates the process of establishing a session, requesting the floor, filtering requests, granting the floor, and handling voice media.](fe7304192caf64cda93b580c5e7e5c06_img.jpg) + +``` + +sequenceDiagram + participant FP1 as Floor participant 1 (primary) + participant FCS1 as Floor control server 1 (primary) + participant FCS2 as Floor control server 2 (partner) + participant FP2 as Floor participant 2 (partner) + participant FP3 as Floor participant 3 (partner) + + Note over all: 1. Session is established. Floor control is established among floor participants and floor control servers. + + Note left of FP1: 2. User wants to talk + FP1->>FCS1: 3. Floor request + Note right of FP2: 2. User wants to talk + FP2->>FCS2: 3. Floor request + Note right of FP3: 2. User wants to talk + FP3->>FCS2: 3. Floor request + + Note over FCS1, FCS2: 4. Floor control filtering according to policy (floor priority or order) + FCS2->>FP3: 5. Floor rejected + Note right of FP3: 6. Reject notification + + FCS2->>FCS1: 7. Floor request + Note over FCS1, FCS2: 8. Group call arbitration according to policy (floor priority or order) + FCS1->>FCS2: 9. Floor granted + + Note left of FP1: 10a.1. Floor rejected + Note left of FP1: 10a.2. Reject notification + Note left of FP1: 10b.1. Queue position info + Note left of FP1: 10b.2. User informed about queue position + + FCS2->>FP2: 14. Floor granted + Note right of FP2: 15. Grant notification + FCS2->>FP3: 16. Floor taken + Note right of FP3: 17. Talker notification + + FCS1->>FP1: 11. Floor taken + Note left of FP1: 12. Talker notification + + Note over FP1, FP2: 18. Voice media + +``` + +Sequence diagram titled 'MCPTT Service Provider' showing floor control interactions between Floor participant 1 (primary), Floor control server 1 (primary), Floor control server 2 (partner), Floor participant 2 (partner), and Floor participant 3 (partner). The diagram illustrates the process of establishing a session, requesting the floor, filtering requests, granting the floor, and handling voice media. + +Figure 10.9.1.4.2-1: Floor control (filtering by partner MCPTT system) involving groups from multiple MCPTT systems + +1. An MCPTT group call involving group 1, group 2 and group 3 is setup and active. + +2. The MCPTT users want to talk +3. The floor participants initiate a floor request to the floor control server of their corresponding MCPTT systems. (The requests may or may not occur at the same time). +4. Floor control server 2 receives a floor request from floor participant 2 and from participant 3 at the same time or during an interval, then the floor control server 2 (partner) performs filtering of the floor requests received according to its local policy such as priority or order based on its own users, and forwards the selected floor request (floor participant 2) to the floor control server 1 (floor arbitrator for the MCPTT group call). As the floor participant information shall not be exposed, the priority related information or/and group information to be used by floor control server 1 should be included in the forwarded request. +5. The floor control server 2 (partner) may send a floor rejected towards the floor participant 3, since its floor request was not chosen to be forwarded on to the floor control server 1. + +6. The user on the UE where the floor participant 3 is located may be notified of the rejection. + +NOTE 1: Steps 5 and 6 can occur any time between step 4 and step 16. + +7. The floor control server 2 (partner) forwards the floor request of floor participant 2 to the floor server 1. +8. The floor control server 1 performs floor arbitration for the MCPTT group call and determines the floor request to be accepted. The floor request message from floor participant 2 of the partner system is accepted by the floor control server 1 (arbitrator) and is determined that a floor granted is sent with permission to talk. +9. The floor granted message from floor control server 1 is routed to floor participant 2 via the floor control server 2 (partner). + +10. Since floor participant 1 sent a floor request but was not granted, + +- 10a.1 the primary floor control server may send a floor rejected message to floor participant 1. + +- 10a.2 The user of the UE where the floor participant 1 is located may be notified of the rejection. + +- 10b.1 if floor control server supports floor queuing, send a queue position info message to floor participant 1. + +- 10b.2 The user of the UE where the floor participant 1 is located may be notified of the queue position. + +NOTE 2: Steps 10a.1 through 10b.2 are optional as indicated by the dashed box enclosing them. However if this box is implemented then either information flow 10a or 10b would occur. + +11. A floor taken message is sent to floor participant 1. + +12. The user of the UE where the floor participant 1 is located may be notified. + +NOTE 3: Step 10 through Step 12 can occur any time between step 8 and step 18. + +13. Since the floor control server 2 (partner) filters floor requests, when the floor control server 2 (partner) receives the floor granted for floor participant 2 from floor control server 1, the floor control server 2 (partner) needs to use the information received to generate the floor taken which will be sent to all other floor participants (floor control participant 3). +14. The floor control server 2 (partner) sends a floor granted message to floor participant 2. +15. The user of the UE where the floor participant 2 is located is notified. +16. The floor control server 2 (partner) sends a floor taken message to all other floor participants (floor participant 3). +17. The user of the UE where the floor participant 1 is located may be notified. +18. Upon successful floor grant, the group call media transmission occurs. + +NOTE 4: The media flow between the media gateways of primary and partner MCPTT systems have not been depicted in the figure for clarity. + +#### 10.9.1.5 Floor control for audio cut-in enabled group + +Figure 10.9.1.5-1 shows the procedure for audio cut-in for the session already established between the floor participants from same MCPTT service provider. Floor participants may request the floor while Floor Participant B is transmitting voice media. Floor control server grants floor immediately to the floor request received. + +**Editor's note: Configuration parameter for queue depth is FFS.** + +Pre-conditions: + +- The floor control server has been configured to support audio cut-in. +- It is assumed that the floor has been granted to floor participant B and floor participant B is transmitting voice media. There are several other floor participants (including floor participant A). + +![Sequence diagram illustrating floor control for audio cut-in enabled group in a single MCPTT system. The diagram shows interactions between Floor participant A, Floor control server, and Floor participant B within a Home MCPTT Service Provider. The process starts with an established session where Floor participant B has the floor. When Floor participant A wants to talk, it sends a Floor Request. The server applies the audio cut-in policy, revokes the floor from B, and grants it to A. B receives a revoke notification and sends a talker notification. A receives a grant notification and starts transmitting voice media. Later, when Floor participant B wants to talk, it sends a Floor Request. The server applies the policy, revokes the floor from A, and grants it to B. A receives a revoke notification and sends a talker notification. B receives a grant notification and starts transmitting voice media.](367378559e35017a5e1a6f5c30798c5a_img.jpg) + +``` + +sequenceDiagram + participant A as Floor participant A + participant S as Floor control server + participant B as Floor participant B + Note right of B: 1. Session is established, Floor control is established between floor participant and floor control server. +Floor granted to floor participant B + Note left of A: 2. User wants to talk + A->>S: 3. Floor Request + Note right of S: 4. Audio cut-in policy is applied. + S->>B: 5. Floor Revoked + Note right of B: 6. Revoke notification + S->>A: 7. Floor Granted + Note right of B: 7. Floor Taken + Note left of A: 8. Grant notification + Note right of B: 8. Talker notification + Note left of A: 9. Voice media + Note right of B: 9. Voice media + Note right of B: 10. User wants to talk + B->>S: 11. Floor Request + Note right of S: 12. Audio cut-in policy is applied. + S->>A: 13. Floor Revoked + Note left of A: 14. Revoke notification + S->>A: 15. Floor Taken + S->>B: 15. Floor Granted + Note left of A: 16. Talker notification + Note right of B: 16. Grant notification + Note left of A: 17. Voice media + Note right of B: 17. Voice media + +``` + +Sequence diagram illustrating floor control for audio cut-in enabled group in a single MCPTT system. The diagram shows interactions between Floor participant A, Floor control server, and Floor participant B within a Home MCPTT Service Provider. The process starts with an established session where Floor participant B has the floor. When Floor participant A wants to talk, it sends a Floor Request. The server applies the audio cut-in policy, revokes the floor from B, and grants it to A. B receives a revoke notification and sends a talker notification. A receives a grant notification and starts transmitting voice media. Later, when Floor participant B wants to talk, it sends a Floor Request. The server applies the policy, revokes the floor from A, and grants it to B. A receives a revoke notification and sends a talker notification. B receives a grant notification and starts transmitting voice media. + +**Figure 10.9.1.5-1: Floor control for audio cut-in enabled group in single MCPTT system** + +1. Floor participant B has been given floor and is transmitting voice media. + +2. Floor participant A wants to send voice media over the session. +3. Floor participant A sends a floor request message to the floor control server. +4. The floor control server applies the audio cut-in policy with floor queue disabled i.e., floor is immediately granted to the floor participant A, and revoked from floor participant B. +5. The floor control server sends a floor revoked message to floor participant B stopping the voice media transmission from floor participant B. +6. The user of floor participant B may be notified that the floor is revoked. +7. The Floor control server sends a floor granted message to floor participant A, and sends a floor taken message to floor participant B with information of who is granted the floor. The floor control server may limit the time a user talks (holds the floor). +8. The user of floor participant A may be notified that he is granted the floor. Similarly, the user of floor participant B may be notified who is granted the floor. +9. Floor participant A starts sending voice media over the session established. +10. Now floor participant B may want the floor to start sending voice media. +11. Floor participant B sends a floor request message to floor control server. +12. The floor control server applies the audio cut-in policy with floor queue disabled. +13. The floor control server sends a floor revoked message to floor participant A stopping the voice media transmission from floor participant A. +14. The user of floor participant A may be notified that the floor is revoked. +15. The Floor control server sends a floor granted message to floor participant B, and sends a floor taken message to floor participant A with information of who is granted the floor. The floor control server may limit the time a user talks (holds the floor). +16. The user of floor participant B may be notified that he is granted the floor. Similarly, the user of floor participant A may be notified who is granted the floor. +17. Floor participant B starts sending voice media over the session established. + +#### 10.9.1.6 Unicast media stop and resume requests + +Figure 10.9.1.6-1 shows the procedure for a floor participant to indicate to the floor control server that the unicast media flow of an active MCPTT group call can be stopped. + +Pre-condition: + +1. An MCPTT session is established between MCPTT client A and MCPTT server for an MCPTT group call. Other participants to the call are not shown in the figure for simplicity. +2. The floor control is established between the floor participant and the floor control server. + +![Sequence diagram illustrating the unicast media stop request during an MCPTT session. The diagram shows interactions between Floor participant A and Floor control server. The sequence is: 1. Floor taken (server to participant), 2. Unicast media flow (server to participant), 3. User indicates that media for the call is not needed (participant internal), 4. Unicast media stop request (participant to server), 5. Server stops the unicast media flow (server internal).](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +``` +sequenceDiagram + participant FCS as Floor control server + participant FPA as Floor participant A + Note right of FPA: 3. User indicates that media for the call is not needed + FCS->>FPA: 1. Floor taken + FCS->>FPA: 2. Unicast media flow + FPA->>FCS: 4. Unicast media stop request + Note right of FCS: 5. Server stops the unicast media flow +``` + +Sequence diagram illustrating the unicast media stop request during an MCPTT session. The diagram shows interactions between Floor participant A and Floor control server. The sequence is: 1. Floor taken (server to participant), 2. Unicast media flow (server to participant), 3. User indicates that media for the call is not needed (participant internal), 4. Unicast media stop request (participant to server), 5. Server stops the unicast media flow (server internal). + +**Figure 10.9.1.6-1: Unicast media stop request during an MCPTT session** + +1. Another floor participant has requested and has been granted the floor. The floor control server sends a floor taken message to floor participant A. The floor taken message may include an identifier of the associated media flow. +2. Floor control server sends the voice media flow to floor participant A over unicast. +3. Floor participant A gets the information, e.g. from the user, that media for the call is not needed. +4. Floor participant A sends a unicast media stop request to floor control server, identifying the media flow to be stopped. +5. Floor control server stops sending that unicast media flow to floor participant A. Associated bearer resources may be de-allocated by the MCPTT server. + +Figure 10.9.1.6-2 shows the procedure for a floor participant to request from the floor control server that the unicast media flow of an active MCPTT group call be restarted. + +Pre-condition: + +1. An MCPTT session is established between MCPTT client A and MCPTT server for an MCPTT group call. Other participants to the call are not shown in the figure for simplicity +2. The floor control is established between the floor participant and the floor control server. +3. Floor participant A has previously indicated to the floor control server that unicast media flow for that call should be stopped, using the procedure described in Figure 10.9.1.6-1. + +![Sequence diagram showing the interaction between Floor participant A and Floor control server for a unicast media resume request. The sequence is: 1. Floor taken (server to participant), 2. User indicates that media for the call is needed (internal participant action), 3. Unicast media resume request (participant to server), 4. Unicast media flow (server to participant).](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +``` + +sequenceDiagram + participant FCS as Floor control server + participant FPA as Floor participant A + Note right of FPA: 2. User indicates that media for the call is needed + FCS->>FPA: 1. Floor taken + FPA->>FCS: 3. Unicast media resume request + FCS->>FPA: 4. Unicast media flow + +``` + +Sequence diagram showing the interaction between Floor participant A and Floor control server for a unicast media resume request. The sequence is: 1. Floor taken (server to participant), 2. User indicates that media for the call is needed (internal participant action), 3. Unicast media resume request (participant to server), 4. Unicast media flow (server to participant). + +**Figure 10.9.1.6-2: Unicast media resume request during an MCPTT session** + +1. Another floor participant has requested and has been granted the floor. The floor control server sends a floor taken message to floor participant A. The floor taken message may include an identifier of the associated media flow. +2. Floor participant A gets the information, e.g. from the user, that media for the call is needed again. +3. Floor participant A sends a unicast media resume request to floor control server, identifying the media flow to be re-started. +4. Floor control server starts sending that unicast media flow to floor participant A. This may need new bearer resources to be allocated. + +NOTE 1: The identifier of the flow to be stopped or resumed is known by the floor participant from the floor control information flows associated with that MCPTT session. + +NOTE 2: Stopping a media flow is not leaving the session and subsequent floor control messages will still be sent by the floor control server to the floor participant which has requested a unicast media stop. + +NOTE 3: Both requests have no effect on a possible ongoing transmission of the media flow over **MBMS**. In particular, they are not interpreted by the MCPTT server as **MBMS** listening status reports. + +### 10.9.2 Floor control for off-network MCPTT service + +#### 10.9.2.1 General + +The procedures defined in this subclause provide floor control to MCPTT UEs in off-network operation. The procedures apply to both private calls and group calls. + +In off-network, floor control is performed by using floor control messages among the MCPTT clients without centralized MCPTT server. The MCPTT client can transmit voice packets once it is granted the right to speak, either locally in the UE or by reception of a floor granted message from another MCPTT client. + +In off-network, the MCPTT client currently speaking performs the temporary floor arbitrator during speaking since there is no centralized MCPTT floor control server. The floor arbitrator controls the floor whether or not queue is supported, and when floor is requested with override. If queue is supported, the MCPTT client performing floor arbitrator grants the right to speak to the next speaker and transfers the floor arbitrator role after completing the voice transfer and releasing the floor. For group calls, the floor arbitrator also transfers the floor control queue when granting + +the floor. The next MCPTT client receiving the right to speak becomes the new floor arbitrator and, for group calls, has the floor control queue. + +For group calls, the floor control message is delivered in multicast based communication and can be monitored by all the members within the MCPTT group. + +The following information flows apply among MCPTT clients. + +- Floor request (from the floor participants to the floor arbitrator): used to request a floor for voice transfer. +- Floor release (from the floor arbitrator to the floor participants): used to inform that the voice transfer is completed and the floor is released. +- Floor granted (from the floor arbitrator to a floor participant): used to indicate that the request for floor is granted, that voice transfer is possible and the current queue list. +- Queue position request (from the floor participant to the floor arbitrator): used to request the position in the floor request queue. +- Queue position info (from the floor arbitrator to the floor participant): used to indicate the floor request is queued and the current queue status. +- Floor rejected (from the floor arbitrator to the floor participant): used to indicate that a request for the floor is rejected. +- Floor taken (from the floor arbitrator to the floor participant): used to indicate the floor is granted to another MCPTT user. + +#### 10.9.2.2 Information flows for floor control for off-network + +##### 10.9.2.2.1 General + +For floor control for off-network, the information flows defined under subclause 10.9.1.2 apply unless it is explicitly defined under this subclause. + +##### 10.9.2.2.2 Floor granted + +Table 10.9.2.2.2-1 describes the information flow floor granted, from the floor participant to the floor participant, which is used to indicate that a request for floor is granted and media transfer is possible. + +**Table 10.9.2.2.2-1: Floor granted** + +| Information element | Status | Description | +|--------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Requester identity | +| Duration | M | The time for which the granted party is allowed to transmit | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only in case of media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +#### 10.9.2.3 Floor control during silence + +##### 10.9.2.3.1 Successful floor taken (No floor contention) + +If a floor arbitrator still exists, the expected behaviour for floor requests during periods of silence is described in subclauses 10.9.2.5 and 10.9.2.6 (with the exception that no media was being generated prior to the floor request). + +If a floor arbitrator does not exist, figure 10.9.2.3.1-1 shows the successful high level floor control procedure during periods when there is no detectable talker. + +NOTE 1: The description also applies to private calls. + +Pre-conditions: + +1. An off-network group call had been established and all MCPTT clients have the call parameters. No participant is currently talking and no floor arbitrator is identified. + +![Sequence diagram illustrating the successful floor taken flow with no floor contention. Four MCPTT clients (1, 2, 3, 4) are shown. Client 1 sends a 'Floor request' to the group. A 'No contention detected' box is shown on Client 1's timeline. Client 1 then sends a 'Floor taken' message to the group. A 'User notification' box is shown on Client 1's timeline. Finally, a 'Media flow' is shown as a thick blue arrow from Client 1 to the other clients. A 'No speech' bar is at the top of the diagram.](212c50c4e3d043c989037a01e13c1a98_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT client 3 + participant MCPTT client 4 + Note over all: No speech + MCPTT client 1->>MCPTT client 2: 1. Floor request + Note left of MCPTT client 1: 2. No contention detected + MCPTT client 1->>MCPTT client 2: 3. Floor taken + Note left of MCPTT client 1: 4. User notification + MCPTT client 1->>MCPTT client 2: 5. Media flow +``` + +Sequence diagram illustrating the successful floor taken flow with no floor contention. Four MCPTT clients (1, 2, 3, 4) are shown. Client 1 sends a 'Floor request' to the group. A 'No contention detected' box is shown on Client 1's timeline. Client 1 then sends a 'Floor taken' message to the group. A 'User notification' box is shown on Client 1's timeline. Finally, a 'Media flow' is shown as a thick blue arrow from Client 1 to the other clients. A 'No speech' bar is at the top of the diagram. + +**Figure 10.9.2.3.1-1: Successful floor taken flow (No floor contention)** + +1. The MCPTT client 1 sends the floor request message to the MCPTT group. +2. The MCPTT client 1 does not detect any floor contention. Floor contention occurs when multiple floor requests may exist simultaneously. + +NOTE 2: The mechanism for detecting floor contention is out of scope of the present document. + +3. The MCPTT client 1 sends the floor taken message to the MCPTT group. +4. The user gets a notification that the floor request was successful (the floor has been granted). +5. The MCPTT client 1 begins voice transmission. + +#### 10.9.2.4 Simultaneous floor requests + +If a floor arbitrator does not exist, figure 10.9.2.4.1-1 shows the expected behaviour in case of simultaneous floor requests are generated when there is no detectable talker. + +Pre-conditions: + +1. An off-network group call is established and all MCPTT clients have the call parameters. No participant is currently talking and no floor arbitrator is identified. +2. MCPTT client 1 has higher priority than MCPTT client 2. + +![Sequence diagram illustrating simultaneous floor requests among four MCPTT clients. The diagram shows a 'No speech' state, followed by parallel floor requests from client 1 and client 2. Client 1 then compares priority, determines it has higher priority, sends a 'Floor taken' message, and receives a user notification.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT client 3 + participant MCPTT client 4 + Note over all: No speech + Note left of MCPTT client 1: 1a. Floor request + MCPTT client 1->>MCPTT client 2: + Note left of MCPTT client 2: 1b. Floor request + MCPTT client 2->>MCPTT client 3: + Note left of MCPTT client 1: 2. Compare priority + Note left of MCPTT client 2: 2. Compare priority + Note left of MCPTT client 1: 3. Floor taken + MCPTT client 1->>MCPTT client 2: + Note left of MCPTT client 1: 4. User notification + +``` + +Sequence diagram illustrating simultaneous floor requests among four MCPTT clients. The diagram shows a 'No speech' state, followed by parallel floor requests from client 1 and client 2. Client 1 then compares priority, determines it has higher priority, sends a 'Floor taken' message, and receives a user notification. + +**Figure 10.9.2.4.1-1: Simultaneous floor requests** + +1a. The MCPTT client 1 sends the floor request message to the MCPTT group. + +1b. The MCPTT client 2 sends the floor request message to the MCPTT group. + +NOTE 1: Step 1a and 1b happen in parallel + +2. On receiving a floor request message, while waiting for a response to the sent floor request message, the MCPTT client compares its floor priority with the floor priority indicated in the received floor request message. +3. On determining that it has higher floor priority than the received floor request message(s), and no response to the sent floor request message is received, the MCPTT client 1 sends the floor taken message to the MCPTT group. +4. The user at MCPTT client 1 gets notification that the floor request was successful (the floor has been granted). + +NOTE 2: If the floor priority in the received floor request message is same as its own floor priority, the MCPTT client can use another scheme to decide who gets the floor. + +#### 10.9.2.5 Floor request during speaking with queue + +Figure 10.9.2.5-1 shows the high level procedure that the floor control is conducted when the MCPTT off-network session is already established among MCPTT floor participants and while voice media is transmitting. In the case, MCPTT clients should support queue function. The current speaking MCPTT client acting as the floor arbitrator put the floor request into the queue list when receiving the floor request from other MCPTT clients. This procedure happens while voice media is transmitting. In the flow, MCPTT client 1 transmits the voice media to the MCPTT group and acts as the floor arbitrator. + +NOTE: The description only applies to group calls. + +![Sequence diagram illustrating floor request during speaking with queue. Four MCPTT clients (1, 2, 3, 4) are shown. Client 1 is transmitting media flow. Client 2 sends a floor request. Client 1 performs queuing and sends queue position info. Client 1 sends floor granted when ending transmission. Client 2 then transmits media flow.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT client 3 + participant MCPTT client 4 + + Note left of MCPTT client 1: During speech + MCPTT client 1->>MCPTT client 2: 1. Media flow + MCPTT client 2->>MCPTT client 3: 2. Floor request + Note left of MCPTT client 1: 3. Queuing + MCPTT client 1->>MCPTT client 4: 4. Queue position info + Note left of MCPTT client 1: Ending Transmission + MCPTT client 1->>MCPTT client 2: 5. Floor granted + MCPTT client 2->>MCPTT client 3: 6. Media flow + MCPTT client 3->>MCPTT client 4: 6. Media flow + +``` + +Sequence diagram illustrating floor request during speaking with queue. Four MCPTT clients (1, 2, 3, 4) are shown. Client 1 is transmitting media flow. Client 2 sends a floor request. Client 1 performs queuing and sends queue position info. Client 1 sends floor granted when ending transmission. Client 2 then transmits media flow. + +**Figure 10.9.2.5-1: Floor request during speaking with queue** + +1. MCPTT client 1 is transmitting voice media to the MCPTT group. +2. MCPTT client 2 sends the floor request message to the MCPTT group. +3. MCPTT client 1 acting as the floor arbitrator put the floor request of MCPTT client 2 into the queue list. +4. MCPTT client 1 sends the queue position info message with the queuing status regarding the floor request of MCPTT client 2 in order to inform the floor request is queued. +5. MCPTT client 1 sends the floor granted message to the MCPTT group when releasing the floor. The message contains the MCPTT ID to be granted to send the voice media, and queue list, if any. MCPTT client 1 may include the maximum duration that MCPTT client 2 transmits in the floor granted message. +6. MCPTT client 2 sends the voice media when receiving the floor granted message and being granted as next speaker in the floor granted message. In addition, MCPTT client 2 becomes the floor arbitrator. + +#### 10.9.2.6 Floor request during speaking without queue + +Figure 10.9.2.6-1 shows the high level procedure that the floor control is conducted when the MCPTT off-network session is already established among MCPTT floor participants. In the case, MCPTT clients do not support queue function. The current speaking MCPTT client acting as the floor arbitrator controls the floor request when receiving the floor request from other MCPTT clients. This procedure happens while voice media is transmitting. In the flow, MCPTT client 1 transmits the voice media to the MCPTT group and acts as the floor arbitrator. + +NOTE: The description also applies to private calls. + +![Sequence diagram illustrating floor request during speaking without queue. Four MCPTT clients (1-4) are shown. Client 1 is the floor arbitrator. Client 2 sends a floor request. Client 1 rejects it. Client 1 then sends a floor release. The diagram shows media flows and message exchanges between clients.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +The diagram is a sequence diagram with four lifelines: MCPTT client 1, MCPTT client 2, MCPTT client 3, and MCPTT client 4. At the top, three large arrows labeled 'Media flow' point from client 1 to clients 2, 3, and 4 respectively. A vertical dashed line separates the 'During speech' phase (left) from the 'No speech' phase (right). In the 'During speech' phase, client 2 sends a '1. Floor request' message to client 1. Client 1 responds with '2. Floor rejected' to clients 2, 3, and 4. A box labeled 'Floor release' is on the left. In the 'No speech' phase, client 1 sends a '3. Floor release' message to clients 2, 3, and 4. + +Sequence diagram illustrating floor request during speaking without queue. Four MCPTT clients (1-4) are shown. Client 1 is the floor arbitrator. Client 2 sends a floor request. Client 1 rejects it. Client 1 then sends a floor release. The diagram shows media flows and message exchanges between clients. + +**Figure 10.9.2.6-1: Floor request during speaking without queue** + +1. MCPTT client 2 sends the floor request message to the MCPTT group. +2. MCPTT client 1 acting as the floor arbitrator rejects the floor request from MCPTT client 2 if no queue function is supported and sends the floor rejected message to the MCPTT group. +3. MCPTT client 1 sends the floor release message to the MCPTT group when releasing the floor, in order to indicate that MCPTT client 1 finishes to send the voice media and releases the floor. + +When the floor release message is transmitted, there are no voice media in the MCPTT group until an MCPTT client requests the floor as described in subclause 10.9.2.3. + +#### 10.9.2.7 Override + +Figure 10.9.2.7-1 shows the high level procedure that the floor control is conducted when the MCPTT off-network session is already established among MCPTT floor participants and while voice media is transmitting. When the currently speaking MCPTT floor participant receives the floor request message from another floor participant who is authorized to revoke the active transmission (e.g. higher hierarchy), the current speaking MCPTT floor participant immediately stops sending the audio media and then grants the permission to that authorized floor participant. + +NOTE: The description also applies to private calls. + +Pre-condition: + +- MCPTT client 1, who acts as the floor arbitrator, transmits the audio media to the MCPTT group. + +![Sequence diagram illustrating floor request with override authorization among four MCPTT clients. MCPTT client 1 is the floor arbitrator. The diagram shows media flows, a floor request from client 2, processing by client 1, and a floor granted message from client 1.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT client 3 + participant MCPTT client 4 + + Note left of MCPTT client 1: During speech + MCPTT client 1->>MCPTT client 2: Media flow + MCPTT client 2->>MCPTT client 3: Media flow + MCPTT client 3->>MCPTT client 4: Media flow + MCPTT client 2->>MCPTT client 1: 1. Floor request + Note left of MCPTT client 1: 2. Processing Floor request + MCPTT client 1->>MCPTT client 2: 3. Floor granted + MCPTT client 2->>MCPTT client 1: Media flow + MCPTT client 1->>MCPTT client 3: Media flow + MCPTT client 3->>MCPTT client 4: Media flow + +``` + +Sequence diagram illustrating floor request with override authorization among four MCPTT clients. MCPTT client 1 is the floor arbitrator. The diagram shows media flows, a floor request from client 2, processing by client 1, and a floor granted message from client 1. + +**Figure 10.9.2.7-1: Floor request with override authorization** + +1. MCPTT client 2 sends the floor request message with override criteria (e.g., priority level) to the MCPTT group. +2. MCPTT client 1 acting as the floor arbitrator determines if the floor is to be revoked based on override criteria. If this is the case, MCPTT client 1 revokes its right of the floor and stops sending the voice media immediately. +3. MCPTT client 1 sends the floor granted message to the MCPTT group. The floor granted message contains the MCPTT ID to be granted, the floor and the floor control queue (if supported). MCPTT client 1 may also include the maximum duration that MCPTT client 2 can transmit voice in the floor granted message. + +MCPTT client 2 who has revoked the floor is the new floor arbitrator and transmits the audio media to the MCPTT group. + +#### 10.9.2.8 Floor queue status + +Figure 10.9.2.8-1 shows the high level procedure that the floor control is conducted when the MCPTT off-network session is already established among MCPTT floor participants and while voice media is transmitting. If the floor control queueing is supported by the floor control mechanism, the current speaking MCPTT group member who is acting as the floor arbitrator collects the information about the queue status based on the received request(s) from the MCPTT group participant(s). The current speaker can then share information about the queue status of the MCPTT floor participant upon request. + +NOTE: The description only applies to group calls. + +Pre-condition: + +- MCPTT client 1, who acts as the floor arbitrator, transmits the audio media to the MCPTT group. + +![Sequence diagram showing MCPTT client 1, 2, 3, and 4. Client 2 sends a 'Queue position request' to client 1. Client 1 responds with 'Queue position info'. Media flows are shown between clients 1 and 2, 2 and 3, and 3 and 4.](5801c19431e76330430e92a598cc7a16_img.jpg) + +The diagram illustrates a sequence of interactions between four MCPTT clients (1, 2, 3, and 4) during a speech call. + +1. **Media flow:** Continuous horizontal arrows at the top and bottom indicate ongoing media streams between client 1 and 2, 2 and 3, and 3 and 4. + +2. **Queue status request:** + +    - Client 2 sends a '1. Queue position request' message to Client 1. + +    - Client 1 performs a '2. Processing request' (shown in a box). + +    - Client 1 then sends a '3. Queue position info' message back to Client 2. + +3. **During speech:** A vertical label indicates the entire sequence occurs while the group call is active. + +Sequence diagram showing MCPTT client 1, 2, 3, and 4. Client 2 sends a 'Queue position request' to client 1. Client 1 responds with 'Queue position info'. Media flows are shown between clients 1 and 2, 2 and 3, and 3 and 4. + +Figure 10.9.2.8-1: Queue status request + +1. MCPTT client 2 sends the queue position request message targeted to MCPTT client 1 i.e. the floor arbitrator by broadcasting the message to the MCPTT group to get its queue status. +2. Since the queue function is assumed to be supported in this call flow, MCPTT client 1 i.e. the floor arbitrator processes the queue position request to find out the status of MCPTT client 1 in the queue. +3. MCPTT client 1 constructs the queue position info message containing the MCPTT client 2's queue status and sends it toward MCPTT client 2 by broadcasting the message to the MCPTT group. + +MCPTT client1 continues being the floor arbitrator and transmits the audio media to the MCPTT group. + +## 10.10 Use of MBMS transmission (on-network) + +### 10.10.1 Information flows for MBMS Transmission + +#### 10.10.1.1 MapGroupToBearer + +Table 10.10.1.1-1 describes the information flow to associate a MCPTT group call to a MBMS bearer. It is sent from the MCPTT server to the MCPTT client. + +Table 10.10.1.1-1: MapGroupToBearer + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT group ID | M | This element identifies the MCPTT group, in which the call is started. | +| Media stream identifier | M | This element identifies the media stream of the SDP used for the group call (e.g. MBMS subchannel). | +| TMGI (NOTE) | O | The MBMS bearer identifier if the media of the MCPTT group call is not sent on the same MBMS bearer as this MapGroupToBearer message. | +| Call acknowledgement indicator | O | Indication that the MCPTT group call requires acknowledgement from receiving MCPTT clients. | +| NOTE: TMGI shall be present if this message is sent over a different MBMS bearer than the media of the group call; TMGI may be present if this message is sent over the same MBMS bearer as the media of the group call. | | | + +#### 10.10.1.2 UnmapGroupFromBearer + +Table 10.10.1.2-1 describes the information flow to disconnect a MCPTT group call from a **MBMS** bearer. It is sent from the MCPTT server to the MCPTT client. + +**Table 10.10.1.2-1: UnmapGroupFromBearer** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------| +| MCPTT group ID | M | This element identifies the MCPTT group which will no longer use the <b>MBMS</b> bearer. | + +#### 10.10.1.3 Application group paging + +Table 10.10.1.3-1 describes the information flow application group paging from the MCPTT server to the MCPTT client. + +**Table 10.10.1.3-1: Application group paging** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------| +| MCPTT Group ID | M | This element identifies the MCPTT group which is paged by the application. | + +### 10.10.2 Use of pre-established **MBMS** bearers + +The MCPTT service shall support the procedure for using pre-established **MBMS** bearers as specified 3GPP TS 23.280 [16]. The MCPTT service shall use the MCPTT-1, MCPTT-6, MCPTT-8 and MCPTT-9 reference points for this procedure. + +MCPTT may use pre-established **MBMS** bearer for the different types of MCPTT group calls. Both pre-arranged group calls and chat group calls can use the pre-established **MBMS** bearer for distributing the media. The **MBMS** bearer can be used by any group. Depending on the capacity of the **MBMS** bearer, the bearer can be used to broadcast one or more group calls in parallel. + +Both the media packets as well as the floor control messages to the receiving users are sent on the **MBMS** bearer. Optionally a separate **MBMS** bearer could be used for the floor control messages, due to different bearer characteristic requirements. + +When using the pre-established procedure for MCPTT, the MCPTT server perform the procedure of call connect and disconnect over **MBMS** as defined in subclause 10.10.4 at the group communication session establishment step. + +### 10.10.3 Use of dynamic **MBMS** bearer establishment + +The MCPTT service shall support the procedure for using dynamic **MBMS** bearers as specified 3GPP TS 23.280 [16]. The MCPTT service shall use the MCPTT-1, MCPTT-4, MCPTT-6, MCPTT-7, MCPTT-8 and MCPTT-9 reference points for this procedure. + +MCPTT may use dynamic **MBMS** bearer establishment for the different types of MCPTT group calls. Both pre-arranged group calls and chat group calls can use the dynamic **MBMS** bearer for distributing the media. + +Both the media packets as well as the floor control messages to the receiving users are sent on the **MBMS** bearer. + +When using the procedures for dynamic **MBMS** bearer establishment for MCPTT, the MCPTT server perform the procedure of call connect and disconnect over **MBMS** as defined in subclause 10.10.4 at the group communication session establishment step. + +### 10.10.4 Call connect and disconnect over **MBMS** + +#### 10.10.4.1 General + +**MBMS** bearer can be used for MCPTT group calls. One **MBMS** bearer is not permanently associated to one specific group or group call. Before sending media packets of a group call over **MBMS** bearer, the MCPTT server shall send the + +association information between group call and the **MBMS** bearer. The group call setup procedure indicates the media stream within one **MBMS** bearer that is used for the specific group call. When the group call over the **MBMS** bearer is finished, this temporary association information of an MCPTT group call to specific resources on a **MBMS** bearer is undone. The procedure in figure 10.10.4.2.1-1 requires that the group session is setup before the call start. This eliminates the need for the receiving clients to continuously use a unicast bearer. Prior to this the **MBMS** bearer is activated and announced to the MCPTT clients. + +#### 10.10.4.2 Procedure + +##### 10.10.4.2.1 Call connect over **MBMS** + +In figure 10.10.4.2.1-1 the MCPTT client 1 is the client that initiate an MCPTT chat group call and also the transmitting client. MCPTT client 1 may, but does not have to be in an **MBMS** service area. The MCPTT client 2 and MCPTT client 3 represents MCPTT clients receiving the MCPTT call over an **MBMS** bearer. There may be other receiving clients both over unicast bearers and over this or other **MBMS** bearer(s), however they are not illustrated in this figure. + +The same procedure as for chat group call can also be applied for pre-arranged calls. However that requires that the pre-arranged sessions are already active. If a pre-arranged group session is initiated the use of pre-established sessions are required. + +Pre-conditions: + +- All users participating in the MCPTT group call are already affiliated to the group. +- All participating users have joined the group session. + +![Sequence diagram illustrating the chat group call connect over MBMS bearer. The diagram shows four lifelines: MCPTT client 1, MCPTT server, MCPTT Client 2, and MCPTT Client 3. The sequence of messages is: 1. Activation and announcement of MBMS bearer (from server to clients); 2. Initial floor request (from client 1 to server); 3. MapGroupToBearer (from server to clients); 4. Floor granted (from server to client 1); 5. Floor taken (from server to clients); 6. Media flow (uplink unicast from client 1 to server, and downlink MBMS from server to clients).](0ff19975027a3c5177519975f9af055f_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT Client 2 + participant MCPTT Client 3 + + Note right of MCPTT server: 1. Activation and announcement of MBMS bearer + MCPTT client 1->>MCPTT server: 2. Initial floor request + MCPTT server->>MCPTT Client 2: 3. MapGroupToBearer + MCPTT server->>MCPTT Client 3: 3. MapGroupToBearer + MCPTT server->>MCPTT client 1: 4. Floor granted + MCPTT server->>MCPTT Client 2: 5. Floor taken + MCPTT server->>MCPTT Client 3: 5. Floor taken + Note left of MCPTT server: 6. Media flow (uplink unicast) + Note right of MCPTT server: 6. Media flow (downlink MBMS) + MCPTT client 1->>MCPTT server: 6. Media flow (uplink unicast) + MCPTT server->>MCPTT Client 2: 6. Media flow (downlink MBMS) + MCPTT server->>MCPTT Client 3: 6. Media flow (downlink MBMS) + +``` + +Sequence diagram illustrating the chat group call connect over MBMS bearer. The diagram shows four lifelines: MCPTT client 1, MCPTT server, MCPTT Client 2, and MCPTT Client 3. The sequence of messages is: 1. Activation and announcement of MBMS bearer (from server to clients); 2. Initial floor request (from client 1 to server); 3. MapGroupToBearer (from server to clients); 4. Floor granted (from server to client 1); 5. Floor taken (from server to clients); 6. Media flow (uplink unicast from client 1 to server, and downlink MBMS from server to clients). + +**Figure 10.10.4.2.1-1: Chat group call connect on **MBMS** bearer** + +1. Activation and announcement of **MBMS** bearer availability. + +NOTE 1: The procedure does not include the steps for MCPTT client location reporting, or for **MBMS** capability information exchange. + +2. MCPTT client 1 initiate the MCPTT group call by sending an initial floor request over a unicast bearer to the MCPTT server (reference point MCPTT-4). +3. The MCPTT server will send a MapGroupToBearer message over a previously activated **MBMS** bearer to all users that will receive the call over an **MBMS** bearer. The MapGroupToBearer message includes association information between the group call and **MBMS** bearer. The MapGroupToBearer message includes MCPTT group ID and information about the media stream identifier of the activated **MBMS** bearer and may include the + +identifier (i.e. the **TMGI**) of the **MBMS** bearer broadcasting the call. The message is sent over reference point MCPTT-9. + +NOTE 2: Step 3 can be deferred until step 5 and the MapGroupToBearer message can then be included in the floor taken message. + +4. The MCPTT server grants the right to transmit for MCPTT client 1 and by that sends a floor granted message to the MCPTT client 1. This message is sent over a unicast bearer (reference point MCPTT-4). +5. A floor taken message is sent from the MCPTT server to all receiving users. This message includes the MCPTT ID of the transmitting MCPTT client as well as the MCPTT group ID. The message is sent over a **MBMS** bearer to all users that have previously been setup to receive calls over the **MBMS** bearer. The message is sent over reference point MCPTT-9. +6. The media is sent from MCPTT client 1 to the MCPTT server over unicast bearer and from the MCPTT server to the MCPTT client 2 and MCPTT client 3 over **MBMS** bearer. + +NOTE 3: Additional floor request messages in the same call will not trigger the MapGroupToBearer message to be sent. + +##### 10.10.4.2.2 Call disconnect over **MBMS** + +Figure 10.10.4.2.2-1 shows the high level procedure where an UnmapGroupFromBearer message is sent by the MCPTT server to the MCPTT clients to indicate that the MCPTT group call is being dissociated from the **MBMS** bearer. + +![Sequence diagram showing interactions between MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3. The sequence starts with activation of MBMS bearer and service announcement, followed by call activation, floor request, floor granted, floor taken, and finally media flow.](5e9af8986a5845504f251d3079da8078_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + + Note over all participants: 1. Activation of MBMS bearer and service announcement + MCPTT client 1->>MCPTT server: 2. Call activate + activate MCPTT server + MCPTT server->>MCPTT client 2: 3. Connect + deactivate MCPTT server + MCPTT client 1->>MCPTT server: 4. Floor request + activate MCPTT server + MCPTT server->>MCPTT client 1: 5. Floor granted + deactivate MCPTT server + activate MCPTT server + MCPTT server->>MCPTT client 2: 6. Floor taken + deactivate MCPTT server + Note over all participants: 7. Media flow +``` + +The diagram illustrates a sequence of interactions between four entities: MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3. The sequence begins with a common activation step (1. Activation of MBMS bearer and service announcement). MCPTT client 1 sends a 'Call activate' message (2) to the MCPTT server. The MCPTT server responds with a 'Connect' message (3) to MCPTT client 2. MCPTT client 1 then sends a 'Floor request' (4) to the MCPTT server, which replies with 'Floor granted' (5). The MCPTT server then sends a 'Floor taken' message (6) to MCPTT client 2. Finally, a 'Media flow' (7) is established between MCPTT client 2 and MCPTT client 3. + +Sequence diagram showing interactions between MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3. The sequence starts with activation of MBMS bearer and service announcement, followed by call activation, floor request, floor granted, floor taken, and finally media flow. + +###### **Figure 10.10.4.2.2-1: Chat group call disconnect on MBMS bearer** + +1. An MCPTT group call is ongoing; the media is broadcasted over **MBMS** bearer to MCPTT client 2 and MCPTT client 3. +2. MCPTT server has determined to disconnect the call over the **MBMS** bearer for the MCPTT clients +3. An UnmapGroupFromBearer message is sent by the MCPTT server to MCPTT client 2, MCPTT client 3 and possibly to MCPTT client 1 (if in **MBMS** coverage area) on **MBMS** bearer(s). + +NOTE 4: The UnmapGroupFromBearer message can be sent as part of other messages. + +NOTE 5: The UnmapGroupFromBearer message and the MapGroupToBearer message can be combined, to facilitate switching bearers in one signalling step, as necessary. + +### 10.10.5 Switching from **MBMS** bearer to unicast bearer + +The MCPTT service shall support the procedure for switching from **MBMS** bearer to unicast bearer as specified 3GPP TS 23.280 [16]. The MCPTT service shall use the MCPTT-1, MCPTT-4, MCPTT-7, MCPTT-8 and MCPTT-9 reference points for this procedure. + +### 10.10.6 Enhanced MCPTT group call setup procedure with **MBMS** bearer + +#### 10.10.6.1 Description + +When the MCPTT server initiates a new MCPTT call, the MCPTT server shall decide to use unicast bearers or broadcast bearers for the downlink media. A similar decision may also be made for other types of media communication e.g. MCVideo. To decide to use broadcast or unicast involves a number of aspects. The figure 10.10.6.1-1 specifies a procedural flow to perform such decision. + +The flow described evaluates which bearer type to use for a new MCPTT group call. It is assumed that if an **MBMS** bearer is active it is also announced to the MCPTT client. + +When using an **MBMS** bearer for application level control signalling, the announcement of an already active **MBMS** bearer could be part of the MCPTT group call setup, however that will have an impact on the call setup time. + +![Flowchart for MBMS bearer decision flow](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +``` +graph TD; A[New MCPTT group call setup applicable for multicast transmission] --> B{Is there an active MBMS bearer to use?}; B -- No --> C[Use Unicast bearers for the MCPTT group call]; B -- Yes --> D{Does the bearer have capacity for a new call?}; D -- No --> E{Any ongoing call that can be moved to unicast?}; E -- Yes --> F[Initiate transfer of ongoing call to unicast bearer]; E -- No --> G[Use the MBMS bearer for call setup message]; G --> H[Use unicast bearer for the media. Optionally queue the call until resources become available.]; D -- Yes --> I{Does the call require ack from receiving users?}; I -- No --> J[Use the MBMS bearer for the new call]; I -- Yes --> K[Use the MBMS bearer for the call and indicate on the MBMS bearer that an acknowledgment is needed]; +``` + +The flowchart illustrates the decision process for selecting a bearer for a new MCPTT group call. It begins with the condition 'New MCPTT group call setup applicable for multicast transmission'. The first decision point is 'Is there an active MBMS bearer to use?'. If 'No', the outcome is 'Use Unicast bearers for the MCPTT group call'. If 'Yes', the next decision is 'Does the bearer have capacity for a new call?'. If 'No', it checks 'Any ongoing call that can be moved to unicast?'. If 'Yes', it 'Initiate transfer of ongoing call to unicast bearer'. If 'No', it 'Use the MBMS bearer for call setup message', leading to 'Use unicast bearer for the media. Optionally queue the call until resources become available.'. If 'Yes' to the capacity question, it checks 'Does the call require ack from receiving users?'. If 'No', it 'Use the MBMS bearer for the new call'. If 'Yes', it 'Use the MBMS bearer for the call and indicate on the MBMS bearer that an acknowledgment is needed'. + +Flowchart for MBMS bearer decision flow + +Figure 10.10.6.1-1: **MBMS** bearer decision flow + +On a high level the procedure outcome is to use unicast or broadcast bearers for the new MCPTT group call. For an enhanced group call setup procedure, the **MBMS** bearer may be used to trigger the use of a unicast bearer. + +#### 10.10.6.2 Procedure + +The procedure in figure 10.10.6.2-1 can be used in the following scenarios: + +- Initiate a new call on unicast bearer +- Transfer an ongoing call from broadcast bearer to unicast bearers + +Pre-conditions: + +- There must be an active and announced **MBMS** bearer + +![Sequence diagram illustrating Application Group paging over an MBMS bearer. The diagram shows interactions between an MCPTT Client and an MCPTT server. The server makes a decision to start a new call or transfer an ongoing call to unicast. It then sends an application group paging message to the client via the MBMS bearer. The client triggers the UE to enter connected mode. The server stops sending media over the MBMS bearer and initiates DL media transmission over the unicast bearer.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +``` + +sequenceDiagram + participant MCPTT server + participant MCPTT Client + Note right of MCPTT server: 1. Decision to start new call on unicast or transfer a ongoing call to unicast + MCPTT server->>MCPTT Client: 2. Application group paging + Note left of MCPTT Client: 3. Trigger UE to enter connected mode + Note right of MCPTT server: 4. Stop sending media over MBMS bearer + MCPTT server->>MCPTT Client: 5. DL media over unicast + +``` + +Sequence diagram illustrating Application Group paging over an MBMS bearer. The diagram shows interactions between an MCPTT Client and an MCPTT server. The server makes a decision to start a new call or transfer an ongoing call to unicast. It then sends an application group paging message to the client via the MBMS bearer. The client triggers the UE to enter connected mode. The server stops sending media over the MBMS bearer and initiates DL media transmission over the unicast bearer. + +**Figure 10.10.6.2-1: Application Group paging over an MBMS bearer** + +1. The MCPTT server initiates a new MCPTT group call on unicast or decides to transfer an ongoing call to unicast. +2. The MCPTT sends an application group paging message on the **MBMS** bearer to inform the MCPTT client that the MCPTT server will initiate media transmission over a unicast bearer. + +NOTE: The group paging message is sent with the assumption that there are UEs in idle mode. Furthermore, this message is an application level paging message and does not replace the normal paging procedure executed by **EPC** and RAN. + +3. In the case that the UE is in idle mode the UE will initiate a service request to transfer the UE to connected mode. +4. The MCPTT server stops sending the media over an **MBMS** bearer. This step is only performed if transferring an ongoing call. +5. The MCPTT server initiates the media transmission over the unicast bearer. + +Step 4-5 may be performed in parallel with step 2-3. Step 5 will trigger a normal paging in **EPC** and RAN if the client is still in idle mode. + +## 10.11 MCPTT resource management (on-network) + +### 10.11.1 General + +Procedures for resource management are defined in subclause 10.11 of 3GPP TS 23.280 [16]. + +### 10.11.2 Request for unicast resources at session establishment + +Void + +### 10.11.3 Request for modification of unicast resources + +Void + +### 10.11.4 Management of multicast media bearers + +Void + +### 10.11.5 Request for resources with shared priority + +#### 10.11.5.1 General + +Void + +#### 10.11.5.2 Procedure + +Void + +## 10.12 MCPTT media plane transmissions with partner MCPTT systems (on-network) + +The MCPTT user is able to receive MCPTT media services (e.g. group communication, private calls) from partner MCPTT systems in normal and roaming conditions. In this service delivery model, the media plane transmissions between the MCPTT UE of the user and the partner MCPTT system can be achieved directly or via the primary MCPTT system, selected by the PLMN operator's policy. The protocol used for media plane signalling is non-SIP like RTCP. + +Figure 10.12-1 provides the procedure for media related signalling. + +Figure 10.12-2 provide the procedure for the media transmission (directly) between MCPTT UE of the user and the partner MCPTT system. + +Figure 10.12-3 provides the procedure for the media transmission (via the primary MCPTT system) between MCPTT UE of the user and the partner MCPTT system. + +Pre-conditions: + +1. The MCPTT group is defined in the partner MCPTT system, where the MCPTT client of user receives the MCPTT service. +2. An MCPTT group call is set up and active. +3. The partner MCPTT system is the group host MCPTT server that is hosting the MCPTT group. The corresponding floor control server manages the media corresponding to the group call. +4. Protocol used for signalling of media plane is non-SIP, it can be protocol like RTCP. +5. Media related signalling is sent via the primary MCPTT system. +6. The path for media between the MCPTT UE and partner MCPTT system has been selected to be sent directly to the partner MCPTT system or via the primary MCPTT system based on PLMN operator's policy. + +![Sequence diagram illustrating media related signalling communication between a Floor participant (MCPTT user), a Floor control server (Primary MCPTT system), and a Floor control server (Partner MCPTT system).](8395ccdee8a80af834aca2bdfd7f9a9b_img.jpg) + +``` + +sequenceDiagram + participant User as Floor participant (MCPTT user) + participant PrimaryServer as Floor control server (Primary MCPTT system) + participant PartnerServer as Floor control server (Partner MCPTT system) + + Note left of User: 1. Want to talk + User->>PrimaryServer: 2. Floor request + PrimaryServer->>PartnerServer: 2. Floor request + Note right of PartnerServer: 3. Authorization and arbitration + PartnerServer->>PrimaryServer: 4. Floor granted + PrimaryServer->>User: 4. Floor granted + +``` + +Sequence diagram illustrating media related signalling communication between a Floor participant (MCPTT user), a Floor control server (Primary MCPTT system), and a Floor control server (Partner MCPTT system). + +Figure 10.12-1: Media related signalling communication + +![Figure 10.12-2: Media communication direct. A sequence diagram showing three lifelines: MCPTT client (MCPTT user), Media distribution function (Primary MCPTT system), and Media distribution function (Partner MCPTT system). The flow is: 1. MCPTT client sends '5.Uplink media' to Partner MCPTT system. 2. Partner MCPTT system sends '6.Downlink media to send' to itself (internal logic). 3. Partner MCPTT system sends '7.Downlink media' back to the MCPTT client.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +``` + +sequenceDiagram + participant C as MCPTT client (MCPTT user) + participant P as Media distribution function (Primary MCPTT system) + participant S as Media distribution function (Partner MCPTT system) + C->>S: 5.Uplink media + Note right of S: 6.Downlink +media to send + S->>C: 7.Downlink media + +``` + +Figure 10.12-2: Media communication direct. A sequence diagram showing three lifelines: MCPTT client (MCPTT user), Media distribution function (Primary MCPTT system), and Media distribution function (Partner MCPTT system). The flow is: 1. MCPTT client sends '5.Uplink media' to Partner MCPTT system. 2. Partner MCPTT system sends '6.Downlink media to send' to itself (internal logic). 3. Partner MCPTT system sends '7.Downlink media' back to the MCPTT client. + +**Figure 10.12-2: Media communication direct** + +![Figure 10.12-3: Media communication via primary MCPTT system. A sequence diagram showing three lifelines: MCPTT client (MCPTT user), Media distribution function (Primary MCPTT system), and Media distribution function (Partner MCPTT system). The flow is: 1. MCPTT client sends '5.Uplink media' to Primary MCPTT system. 2. Primary MCPTT system sends '5.Uplink media' to Partner MCPTT system. 3. Partner MCPTT system sends '6.Downlink media to send' to itself. 4. Partner MCPTT system sends '7.Downlink media' to Primary MCPTT system. 5. Primary MCPTT system sends '7.Downlink media' to MCPTT client.](57939c16065211317c5442cf2a4009e0_img.jpg) + +``` + +sequenceDiagram + participant C as MCPTT client (MCPTT user) + participant P as Media distribution function (Primary MCPTT system) + participant S as Media distribution function (Partner MCPTT system) + C->>P: 5.Uplink media + P->>S: 5.Uplink media + Note right of S: 6.Downlink +media to send + S->>P: 7.Downlink media + P->>C: 7.Downlink media + +``` + +Figure 10.12-3: Media communication via primary MCPTT system. A sequence diagram showing three lifelines: MCPTT client (MCPTT user), Media distribution function (Primary MCPTT system), and Media distribution function (Partner MCPTT system). The flow is: 1. MCPTT client sends '5.Uplink media' to Primary MCPTT system. 2. Primary MCPTT system sends '5.Uplink media' to Partner MCPTT system. 3. Partner MCPTT system sends '6.Downlink media to send' to itself. 4. Partner MCPTT system sends '7.Downlink media' to Primary MCPTT system. 5. Primary MCPTT system sends '7.Downlink media' to MCPTT client. + +**Figure 10.12-3: Media communication via primary MCPTT system** + +For media related signalling communication: + +1. An MCPTT user wants to talk. +2. The floor participant corresponding to the MCPTT user sends a floor request message to floor control server (partner MCPTT system) to get the authorization and/or permission to talk. +3. The floor control server (partner MCPTT system) performs the authorization and arbitrates between requests that are in contention (i.e., floor control). +4. If the floor control server (partner MCPTT system) allows the floor participant to talk, a floor granted is provided with permission granted to talk. + +For media communication: + +5. The MCPTT client can now send uplink media data to the media distribution function of the MCPTT server (partner MCPTT system). +6. The media distribution function of the MCPTT server (partner MCPTT system) has downlink media data to transfer. +7. The media distribution function of the MCPTT server (partner MCPTT system) transfers the downlink media to the MCPTT client of the MCPTT user. + +## 10.13 Location information (on-network) + +The MCPTT system makes use of all of the procedures for location management as specified in 3GPP TS 23.280 [16], utilising the CSC-14 reference point between the location management client and location management server and the CSC-15 reference point between the MCPTT server and location management server. + +- The MC service client is the MCPTT client; + +- The MC service server is the MCPTT server; +- The MC service group is the MCPTT group; +- The MC service ID is the MCPTT ID; and +- The MC service group ID is the MCPTT group ID. + +## 10.14 Ambient listening call + +### 10.14.1 General + +The ambient listening call is a type of a private MCPTT call that only allows a "listened to" user to transmit media to a "listening" user such that there is no indication on the MCPTT UE of the "listened to" user about the call and the media transmission. + +NOTE 1: "listened to" user refers to the user who is transmitting media in an ambient listening call. + +NOTE 2: "listening" user refers to the user who is receiving media in an ambient listening call. + +There are two types of ambient listening call as below: + +- Remotely initiated ambient listening is initiated by the authorized user (e.g., dispatcher) who wants to listen to another user. In this case, the "listened to" user is the called party, and shall automatically accept the call without causing any indication about the call and transmit the media to the "listening" user. +- Locally initiated ambient listening is initiated by an authorized user who wants another user to listen to the MCPTT UE communication. In this case, the "listened to" user is the calling party and shall automatically transmit the media to the "listening" user without causing any indication about the call processing and media transmission. + +### 10.14.2 Information flows for ambient listening call + +#### 10.14.2.1 Ambient listening call request + +Table 10.14.2.1-1 describes the information flow ambient listening call request from the MCPTT client to the MCPTT server and MCPTT server to the MCPTT client. + +**Table 10.14.2.1-1: Ambient listening call request** + +| Information Element | Status | Description | +|------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the "listening" user | +| MCPTT ID | M | The MCPTT ID of the "listened to" user | +| SDP offer | M | Media parameters of MCPTT client. | +| Ambient listening type | M | The ambient listening type indicates remotely initiated ambient listening call or locally initiated ambient listening call. | + +#### 10.14.2.2 Ambient listening call response + +Table 10.14.2.2-1 describes the information flow ambient listening call response from the MCPTT client to the MCPTT server and MCPTT server to the MCPTT client. + +**Table 10.14.2.2-1: Ambient listening call response** + +| <b>Information Element</b> | <b>Status</b> | <b>Description</b> | +|----------------------------|---------------|----------------------------------------| +| MCPTT ID | M | The MCPTT ID of the "listening" user | +| MCPTT ID | M | The MCPTT ID of the "listened to" user | +| SDP answer | M | Media parameters selected | + +#### 10.14.2.3 Ambient listening call release request + +Table 10.14.2.3-1 describes the information flow ambient listening call release request from the MCPTT client to the MCPTT server and MCPTT server to the MCPTT client. + +**Table 10.14.2.3-1: Ambient listening call release request** + +| <b>Information Element</b> | <b>Status</b> | <b>Description</b> | +|----------------------------|---------------|---------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the "listening" user | +| MCPTT ID | M | The MCPTT ID of the "listened to" user | +| Ambient listening type | M | The ambient listening type indicates a remotely initiated ambient listening call or a locally initiated ambient listening call. | + +#### 10.14.2.4 Ambient listening call release response + +Table 10.14.2.4-1 describes the information flow ambient listening call release response from the MCPTT client to the MCPTT server and MCPTT server to the MCPTT client. + +**Table 10.14.2.4-1: Ambient listening call release response** + +| <b>Information Element</b> | <b>Status</b> | <b>Description</b> | +|----------------------------|---------------|---------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the "listening" user | +| MCPTT ID | M | The MCPTT ID of the "listened to" user | +| Ambient listening type | M | The ambient listening type indicates a remotely initiated ambient listening call or a locally initiated ambient listening call. | + +#### 10.14.2.5 Ambient listening call release notification + +Table 10.14.2.5-1 describes the information flow ambient listening call release notification from the MCPTT server to the MCPTT client. + +**Table 10.14.2.5-1: Ambient listening call release notification** + +| Information Element | Status | Description | +|------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the "listening" user | +| MCPTT ID | M | The MCPTT ID of the "listened to" user | +| Call release reason | M | The reason for call release by the MCPTT server | +| Ambient listening type | M | The ambient listening type indicates a remotely initiated ambient listening call or a locally initiated ambient listening call. | + +### 10.14.3 Ambient listening call procedures + +#### 10.14.3.1 Remotely initiated ambient listening call setup + +The MCPTT service provides the capability for an authorised user to initiate a remotely initiated ambient listening call at an MCPTT client. + +Figure 10.14.3.1-1 illustrates the information flow for remotely initiated ambient listening call setup. + +Pre-conditions: + +- MCPTT client 1 is the client of the authorized user who is authorized to invoke a remotely initiated ambient listening call to be set up at the requested MCPTT client 2. +- MCPTT user 1 is the "listening" user at MCPTT client 1, and MCPTT user 2 is the "listened to" user at MCPTT client 2. + +![Sequence diagram illustrating the remotely initiated ambient listening call setup. The diagram shows three participants: MCPTT client 1, MCPTT server, and MCPTT client 2. The sequence of messages is: 1. MCPTT client 1 sends an 'Ambient listening call request' to the MCPTT server. 2. The MCPTT server performs an 'Authorize ambient listening call request' (shown in a box). 3. The MCPTT server sends an 'Ambient listening call request' to MCPTT client 2. 4. MCPTT client 2 sends an 'Ambient listening call response' back to the MCPTT server. 5. The MCPTT server sends an 'Ambient listening call response' back to MCPTT client 1. 6. The MCPTT server sends a 'Floor granted' message to MCPTT client 2. 7. The MCPTT server sends a 'Floor taken' message to MCPTT client 1. 8. A 'Media flow' is established between MCPTT client 1 and MCPTT client 2, indicated by double-lined arrows at the bottom.](5492fadb32a8df1ee9f2528a053c9862_img.jpg) + +Sequence diagram illustrating the remotely initiated ambient listening call setup. The diagram shows three participants: MCPTT client 1, MCPTT server, and MCPTT client 2. The sequence of messages is: 1. MCPTT client 1 sends an 'Ambient listening call request' to the MCPTT server. 2. The MCPTT server performs an 'Authorize ambient listening call request' (shown in a box). 3. The MCPTT server sends an 'Ambient listening call request' to MCPTT client 2. 4. MCPTT client 2 sends an 'Ambient listening call response' back to the MCPTT server. 5. The MCPTT server sends an 'Ambient listening call response' back to MCPTT client 1. 6. The MCPTT server sends a 'Floor granted' message to MCPTT client 2. 7. The MCPTT server sends a 'Floor taken' message to MCPTT client 1. 8. A 'Media flow' is established between MCPTT client 1 and MCPTT client 2, indicated by double-lined arrows at the bottom. + +**Figure 10.14.3.1-1: Remotely initiated ambient listening call** + +1. MCPTT client 1 initiates a remotely initiated ambient listening call by sending the ambient listening call request to the MCPTT server. The remotely initiated ambient listening call type is included. +2. The MCPTT server performs an authorization check for the authorized user 1 for the remotely initiated ambient listening call. If authorization fails, the MCPTT server provides a failure response to MCPTT client 1. + +3. The MCPTT server sends the ambient listening call request to MCPTT client 2. +4. MCPTT client 2 returns the ambient listening call response to the MCPTT server. +5. MCPTT server provides an ambient listening call response to MCPTT client 1, indicating whether the call is set up successfully or not. +6. The floor control server of the MCPTT server then sends a floor granted to MCPTT client 2 according to the ambient listening type received in step 1. +7. Accordingly, the floor control server of the MCPTT server sends a floor taken to MCPTT client 1. +8. After receiving the floor granted message at the MCPTT client 2, the media is transmitted from MCPTT client 2 to MCPTT client 1. + +NOTE: MCPTT client 2 does not provide any indication of the ambient listening call release to its user. + +#### 10.14.3.2 Locally initiated ambient listening call setup + +The MCPTT service provides the capability for an authorised user to initiate a locally initiated ambient listening call at an MCPTT client. + +Figure 10.14.3.2-1 illustrates the information flow for locally initiated ambient listening call setup. + +Pre-conditions: + +- MCPTT client 2 is the client of the authorized user who is authorized to invoke a locally initiated ambient listening call to be set up at the requested MCPTT client 1. +- MCPTT user 1 is the "listening" user at MCPTT client 1, and MCPTT user 2 is the "listened to" user at MCPTT client 2. + +![Sequence diagram for locally initiated ambient listening call setup. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2. The sequence starts with MCPTT client 2 sending an 'Ambient listening call request' to the MCPTT server. The server responds with 'Authorize ambient listening call request' to client 2. The server then sends an 'Ambient listening call request' to MCPTT client 1. Client 1 responds with 'Ambient listening call response' to the server. The server sends an 'Ambient listening call response' to client 2. The server then sends a 'Floor granted' message to client 2 and a 'Floor taken' message to client 1. Finally, a 'Media flow' is established between client 2 and client 1.](ec31af936fa94a6917bf19f154df8ac3_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note right of MCPTT server: 2.Authorize ambient listening call request + MCPTT client 2->>MCPTT server: 1.Ambient listening call request + MCPTT server-->>MCPTT client 2: 2.Authorize ambient listening call request + MCPTT server->>MCPTT client 1: 3.Ambient listening call request + MCPTT client 1->>MCPTT server: 4.Ambient listening call response + MCPTT server->>MCPTT client 2: 5.Ambient listening call response + MCPTT server->>MCPTT client 2: 6. Floor granted + MCPTT server->>MCPTT client 1: 7. Floor taken + Note left of MCPTT server: 8.Media flow + Note right of MCPTT server: 8.Media flow + +``` + +Sequence diagram for locally initiated ambient listening call setup. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2. The sequence starts with MCPTT client 2 sending an 'Ambient listening call request' to the MCPTT server. The server responds with 'Authorize ambient listening call request' to client 2. The server then sends an 'Ambient listening call request' to MCPTT client 1. Client 1 responds with 'Ambient listening call response' to the server. The server sends an 'Ambient listening call response' to client 2. The server then sends a 'Floor granted' message to client 2 and a 'Floor taken' message to client 1. Finally, a 'Media flow' is established between client 2 and client 1. + +**Figure 10.14.3.1-1: Locally initiated ambient listening call** + +1. MCPTT client 2 initiates a locally initiated ambient listening call by sending the ambient listening call request to the MCPTT server. The locally initiated ambient listening call type is included. +2. The MCPTT server performs an authorization check for the authorized user 2 for the locally initiated ambient listening call. If authorization fails, the MCPTT server provides a failure response to MCPTT client 2. +3. The MCPTT server sends the ambient listening call request to MCPTT client 1. + +4. MCPTT client 1 returns the ambient listening call response to the MCPTT server. +5. MCPTT server provides an ambient listening call response to MCPTT client 2, indicating whether the call is set up successfully or not. +6. The floor control server of the MCPTT server then sends a floor granted to MCPTT client 2 according to the ambient listening type received in step 1. +7. Accordingly, the floor control server of the MCPTT server sends a floor taken to MCPTT client 1. +8. After receiving the floor granted message at the MCPTT client 2, the media is transmitted from MCPTT client 2 to MCPTT client 1. + +NOTE: MCPTT client 2 does not provide any indication of the ambient listening call release to its user. + +#### 10.14.3.3 Ambient listening call release – server initiated + +Figure 10.14.3.3-1 illustrates the information flow for ambient listening call release – server initiated when trigger by the MCPTT administrator. This procedure is applied for both remotely initiated ambient listening call and the locally initiated ambient listening call. + +Pre-conditions: + +- MCPTT client 1 is the MCPTT client of the authorized user, who initiated the ambient listening call at MCPTT client 2. +- There is an ongoing ambient listening call between MCPTT client 2 and MCPTT client 1. +- MCPTT user 1 is the current user at MCPTT client 1 who is listening, and MCPTT user 2 is the current user at MCPTT client 2 who is being listened to. + +![Sequence diagram for ambient listening call release – server initiated. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2. The process starts with the server triggering the release, followed by a request to client 2, stopping media transmission, a response from client 2, a notification from the server to client 1, and finally notifying the user at client 1.](ddcf2f580e914bff1e7756ed288874e1_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note right of MCPTT server: 1.Ambient listening call release Is triggered + MCPTT server->>MCPTT client 2: 2.Ambient listening call release request + Note right of MCPTT client 2: 3. Stop transmitting media + MCPTT client 2->>MCPTT server: 4.Ambient listening call release response + MCPTT server->>MCPTT client 1: 5. Ambient listening call release notification + Note left of MCPTT client 1: 6.Notify user + +``` + +Sequence diagram for ambient listening call release – server initiated. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2. The process starts with the server triggering the release, followed by a request to client 2, stopping media transmission, a response from client 2, a notification from the server to client 1, and finally notifying the user at client 1. + +**Figure 10.14.3.3-1: Ambient listening call release – server initiated** + +1. The ambient listening call release is triggered by the MCPTT administrator or by one of the following events: + - the MCPTT server receives MCPTT call requests towards MCPTT client 2; or + - the MCPTT client 2 initiates MCPTT call requests; +2. The MCPTT server sends an ambient listening call release request to MCPTT client 2. +3. MCPTT client 2 stops transmitting media to MCPTT client 1. + +NOTE: MCPTT client 2 does not provide any indication of the ambient listening call release to its user. + +4. MCPTT client 2 provides an ambient listening call release response to the MCPTT server. + +- 5. The MCPTT server sends an ambient listening call release notification to MCPTT client 1 together with a reason code identifying that the call was released. +- 6. MCPTT client 1 notifies the authorized user 1. + +#### 10.14.3.4 Remotely initiated ambient listening call release – "listening" user initiated + +Figure 10.14.3.4-1 illustrates the information flow for ambient listening call release – "listening" user initiated. This procedure is applied for both remotely initiated ambient listening call and the locally initiated ambient listening call. + +Pre-conditions: + +- MCPTT client 1 is the MCPTT client of the authorized user, who is authorized to release the ambient listening call at MCPTT client 2. +- There is an ongoing ambient listening call between MCPTT client 2 and MCPTT client 1. +- MCPTT user 1 is the "listening" user at MCPTT client 1, and MCPTT user 2 is the "listened to" user at MCPTT client 2. + +![Sequence diagram showing the information flow for ambient listening call release initiated by the 'listening' user at MCPTT client 1. The diagram involves three participants: MCPTT client 1, MCPTT server, and MCPTT client 2. The sequence of messages is: 1. MCPTT client 1 sends an 'Ambient listening call release request' to the MCPTT server. 2. The MCPTT server sends an 'Ambient listening call release request' to MCPTT client 2. 3. MCPTT client 2 performs an internal action 'Stop transmitting media'. 4. MCPTT client 2 sends an 'Ambient listening call release response' to the MCPTT server. 5. The MCPTT server sends an 'Ambient listening call release response' back to MCPTT client 1.](6334c962f5e106e3331e59946e4d166e_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note right of MCPTT client 2: 3.Stop transmitting media + MCPTT client 1->>MCPTT server: 1.Ambient listening call release request + MCPTT server->>MCPTT client 2: 2.Ambient listening call release request + MCPTT client 2->>MCPTT server: 4.Ambient listening call release response + MCPTT server->>MCPTT client 1: 5.Ambient listening call release response + +``` + +Sequence diagram showing the information flow for ambient listening call release initiated by the 'listening' user at MCPTT client 1. The diagram involves three participants: MCPTT client 1, MCPTT server, and MCPTT client 2. The sequence of messages is: 1. MCPTT client 1 sends an 'Ambient listening call release request' to the MCPTT server. 2. The MCPTT server sends an 'Ambient listening call release request' to MCPTT client 2. 3. MCPTT client 2 performs an internal action 'Stop transmitting media'. 4. MCPTT client 2 sends an 'Ambient listening call release response' to the MCPTT server. 5. The MCPTT server sends an 'Ambient listening call release response' back to MCPTT client 1. + +**Figure 10.14.3.4-1: Ambient listening call release – "listening" user initiated** + +- 1. The authorized user 1 at MCPTT client 1 initiates the ambient listening call release by sending an ambient listening call release request to the MCPTT server. +- 2. The MCPTT server provides an ambient listening call release request to MCPTT client 2. +- 3. MCPTT client 2 stops transmitting media to MCPTT client 1. + +NOTE: MCPTT client 2 does not provide any indication of the ambient listening call release to its user. + +- 4. MCPTT client 2 provides an ambient listening call release response to the MCPTT server. +- 5. The MCPTT server provides the ambient listening call release response to MCPTT client 1. + +#### 10.14.3.5 Ambient listening call release – "listened to" user initiated + +Figure 10.14.3.5-1 illustrates the information flow for ambient listening call release – "listened to" user initiated. This procedure is only applied for the locally initiated ambient listening call. + +Pre-conditions: + +- There is an ongoing ambient listening call between MCPTT client 1 and MCPTT client 2. +- MCPTT user 1 is the "listening" user at MCPTT client 1, and MCPTT user 2 is the "listened to" user at MCPTT client 2. + +- MCPTT client 2 is the MCPTT client of the authorized user, who is authorized to release the locally initiated ambient listening call at MCPTT client 2. + +![Sequence diagram for Ambient listening call release – 'listened to' user initiated. The diagram shows interactions between MCPTT client 1, MCPTT server, and MCPTT client 2. The sequence is: 1. MCPTT client 2 sends a release request to the server. 2. The server sends a release request to MCPTT client 1. 3. MCPTT client 1 notifies its user. 4. MCPTT client 1 sends a release response to the server. 5. The server sends a release response to MCPTT client 2. 6. MCPTT client 1 stops transmitting media to MCPTT client 2.](0a3ab80d35c138cc4038b5758f6ff34d_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 2 + participant MCPTT server + participant MCPTT client 1 + Note left of MCPTT client 1: 3.Notify user + Note right of MCPTT client 2: 6.Stop transmitting media + + MCPTT client 2->>MCPTT server: 1.Ambient listening call release request + MCPTT server->>MCPTT client 1: 2.Ambient listening call release request + MCPTT client 1->>MCPTT server: 4.Ambient listening call release response + MCPTT server->>MCPTT client 2: 5.Ambient listening call release response + +``` + +Sequence diagram for Ambient listening call release – 'listened to' user initiated. The diagram shows interactions between MCPTT client 1, MCPTT server, and MCPTT client 2. The sequence is: 1. MCPTT client 2 sends a release request to the server. 2. The server sends a release request to MCPTT client 1. 3. MCPTT client 1 notifies its user. 4. MCPTT client 1 sends a release response to the server. 5. The server sends a release response to MCPTT client 2. 6. MCPTT client 1 stops transmitting media to MCPTT client 2. + +**Figure 10.14.3.5-1: Ambient listening call release – "listened to" user initiated** + +1. The authorized user 2 at MCPTT client 2 initiates the ambient listening call release by sending an ambient listening call release request to the MCPTT server. +2. The MCPTT server provides an ambient listening call release request to MCPTT client 1. +3. MCPTT client 1 is notified about the ambient listening call release. +4. MCPTT client 1 provides an ambient listening call release response to the MCPTT server. +5. The MCPTT server provides the ambient listening call release response to MCPTT client 2. +6. MCPTT client 1 stops transmitting media to MCPTT client 2. + +NOTE: MCPTT client 1 does not provide any indication of the ambient listening call release to its user. + +## 10.15 First-to-answer call setup + +### 10.15.1 Description + +Figure 10.15.3-1 describes the basic procedure for the MCPTT client initiating MCPTT first-to-answer call. The flow may use a floor request in the MCPTT call request indicating that the originator will be given the floor when the call starts and eliminates the need for a separate initial floor request message during media plane establishment. Alternatively the call initiation may be sent without the floor request, which allows the called party to request the floor first. For a MCPTT first-to-answer call without floor control, floor control is not established. + +### 10.15.2 Information flows for first-to-answer call + +**Editor's note: Information flows for first-to-answer call to be included.** + +### 10.15.3 Procedure + +All clients are served by the primary MCPTT service provider in figure 10.15.3-1. + +Pre-conditions: + +1. The calling MCPTT user has selected first-to-answer call +2. MCPTT clients 1 to n are registered and their respective users, MCPTT user 1 to MCPTT user n, are authenticated and authorized to use the MCPTT service, as per procedure in subclause 10.2. + +![Sequence diagram for MCPTT first-to-answer call within the same MCPTT system. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3, MCPTT client n. The process involves a request from client 1, server authorization and user list determination, notification calls to clients 2, 3, and n, responses from clients 2 and 3, media plane establishment, and subsequent cancel requests and responses from the server to clients 3 and n.](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) + +Home MCPTT service provider + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + participant MCPTT client n + + Note left of MCPTT client 1: 1. initiate first-to-answer call + MCPTT client 1->>MCPTT server: 2. MCPTT first-to-answer call request + MCPTT server->>MCPTT server: 3. Authorize request + MCPTT server->>MCPTT server: 4. Determine the list of users to send request based on request in step 2 + MCPTT server->>MCPTT client 2: 5a. MCPTT first-to-answer call request + MCPTT client 2->>MCPTT client 2: 6a. Notify call + MCPTT server->>MCPTT client 3: 5b. MCPTT first-to-answer call request + MCPTT client 3->>MCPTT client 3: 6b. Notify call + MCPTT server->>MCPTT client n: 5c. MCPTT first-to-answer call request + MCPTT client n->>MCPTT client n: 6c. Notify call + MCPTT client 2->>MCPTT server: 7. MCPTT first-to-answer call response + MCPTT server->>MCPTT client 1: 8. MCPTT first-to-answer call response + Note over MCPTT client 1, MCPTT server: 9. Media plane established + MCPTT server->>MCPTT client 3: 10. MCPTT first-to-answer call response + MCPTT server->>MCPTT client 3: 11. MCPTT first-to-answer call cancel request + MCPTT client 3->>MCPTT client 3: 12. Notify call cancel + MCPTT client 3->>MCPTT server: 13. MCPTT first-to-answer call cancel response + MCPTT server->>MCPTT client n: 14. MCPTT first-to-answer call cancel request + MCPTT client n->>MCPTT client n: 15. Notify call cancel + MCPTT client n->>MCPTT server: 16. MCPTT first-to-answer call cancel response + +``` + +Sequence diagram for MCPTT first-to-answer call within the same MCPTT system. Lifelines: MCPTT client 1, MCPTT server, MCPTT client 2, MCPTT client 3, MCPTT client n. The process involves a request from client 1, server authorization and user list determination, notification calls to clients 2, 3, and n, responses from clients 2 and 3, media plane establishment, and subsequent cancel requests and responses from the server to clients 3 and n. + +**Figure 10.15.3-1: MCPTT first-to-answer call – MCPTT users in the same MCPTT system** + +1. MCPTT user at MCPTT client 1 would like to establish a MCPTT first-to-answer call indicating a set of potential target recipients. For a MCPTT first-to-answer call with floor control, floor control is to be established. For first-to-answer call without floor control, both users will have the ability to transmit without floor arbitration. +2. MCPTT client 1 sends an MCPTT first-to-answer call request including a set of potential target recipients, using an MCPTT service identifier as defined in 3GPP TS 23.228 [5] (possible for the SIP core to route the request to the MCPTT server). The MCPTT first-to-answer call request contains the MCPTT ID of originating user and an SDP offer containing one or more media types. The MCPTT first-to-answer call request may also contain a data element that indicates that MCPTT client 1 is requesting the floor, for a first-to-answer call with floor control. + +The MCPTT client 1 includes a first-to-answer call indication that the call is to be established only to the first answering user. + +**Editor's note:** It is FFS whether the target recipients are pre-configured and included by the MCPTT server. + +3. The MCPTT server confirms that MCPTT users are authorized for the call and whether the MCPTT user at MCPTT client 1 is authorized to initiate a first-to-answer call. + 4. The MCPTT server determines the list of MCPTT users to send MCPTT first-to-answer call request, based on a set of potential target recipients obtained from the request from MCPTT client 1 + - 5a, 5b, 5c. The MCPTT server includes information that it communicates using MCPTT service, offers the same media types or a subset of the media types contained in the initial received request and sends similar MCPTT first-to-answer call request to each potential target recipient, including the MCPTT ID of the calling MCPTT user at MCPTT client 1. If one or more called MCPTT users have registered to the MCPTT service with multiple MCPTT UEs and has designated the MCPTT UE for receiving the calls, then the incoming MCPTT first-to-answer call request is delivered only to the designated MCPTT UE. Otherwise MCPTT first-to-answer call request may be delivered to all the registered MCPTT UEs. + - 6a, 6b, 6c. The MCPTT users are alerted, regardless of the commencement mode. + 7. MCPTT user at MCPTT client 2 accepted the call which causes MCPTT client 2 to send an MCPTT first-to-answer call response to the MCPTT server. +- NOTE: MCPTT server does not divert MCPTT first-to-answer call to voicemail if MCPTT user at MCPTT client 2 has not accepted the incoming call. +8. The MCPTT server sends an MCPTT first-to-answer call response to MCPTT client 1 indicating that MCPTT user at MCPTT client 2 has accepted the call, including the accepted media parameters. + 9. The media plane for communication is established. Either user can transmit media individually when using floor control. For successful call establishment for first-to-answer call with floor request from MCPTT client 1, the floor participant associated with MCPTT client 1 is granted the floor initially. At the same time the floor participant associated with MCPTT client 2 is informed that the floor is taken. For a first-to-answer call without floor control both users are allowed to transmit simultaneously. + 10. MCPTT user at MCPTT client 3 has also accepted the call which causes MCPTT client 3 to send an MCPTT first-to-answer call response to the MCPTT server. + 11. Since the MCPTT first-to-answer call response from MCPTT client 2 is already accepted, the MCPTT server sends a MCPTT first-to-answer call cancel request to MCPTT client 3. + - 12-13. MCPTT user at MCPTT client 3 may be notified that the MCPTT first-to-answer call is released with a reason for call release and MCPTT client 3 sends a MCPTT first-to-answer call cancel response. + 14. MCPTT server sends a MCPTT first-to-answer call cancel request to all other MCPTT first-to-answer call request receiving users from that call. This step may happen immediately after Step 9. + - 15-16. MCPTT user at MCPTT client n may be notified that the MCPTT first-to-answer call is cancelled with a reason for call cancel and MCPTT client n sends a MCPTT first-to-answer call cancel response. + +## 10.16 Remotely initiated MCPTT call + +### 10.16.1 General + +A remotely initiated MCPTT call allows an authorized user to cause a remote MCPTT UE to initiate a call by itself, without its user explicitly initiating the call. + +### 10.16.2 Information flows for remotely initiated MCPTT call + +#### 10.16.2.1 Remotely initiated MCPTT call request + +Table 10.16.2.1-1 describes the information flow remotely initiated MCPTT call request from the MCPTT client to the MCPTT server and from the MCPTT server to MCPTT client. + +**Table 10.16.2.1-1: remotely initiated MCPTT call request information elements** + +| Information Element | Status | Description | +|--------------------------------------------------------|----------|------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the called party (remote) | +| Notification to remote user of remotely initiated call | M | Use to determine whether the called party (remote) receives any indication of the remotely initiated MCPTT call. | +| MCPTT ID | O (NOTE) | For a remotely initiated MCPTT private call the MCPTT User ID to be called | +| MCPTT Group | O (NOTE) | For a remotely initiated MCPTT group call to use. | +| NOTE: One and only one of these shall be present. | | | + +#### 10.16.2.2 Remotely initiated MCPTT call response + +Table 10.16.2.2-1 describes the information flow remotely initiated MCPTT call response from the MCPTT client to the MCPTT server and from the MCPTT server to MCPTT client. + +**Table 10.16.2.2-1: Remotely initiated MCPTT call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Result | M | Result of the remotely initiated MCPTT call request – success or fail. | + +### 10.16.3 Procedure + +#### 10.16.3.1 Remotely initiated MCPTT call request + +The remotely initiated MCPTT call request procedure includes the initial remotely initiated MCPTT call request from the MCPTT user to the remote UE and either the MCPTT private call procedures or the MCPTT group call procedures originating at the remote UE. + +Procedures in figure 10.16.3.1-1 show the signalling control plane procedures for the MCPTT client initiating a remotely initiated MCPTT call request with the chosen MCPTT user. + +Pre-conditions: + +- If the MCPTT user on MCPTT client 1 wants the resulting remotely initiated MCPTT call to be: + - an MCPTT group call, then MCPTT user 2 on MCPTT client 2 is an affiliated MCPTT group member of the MCPTT group that is the target of the remotely initiated MCPTT call. Otherwise prior to these procedures the MCPTT user 1 on MCPTT client 1 can use existing procedures (e.g., remotely change MCPTT group affiliation (10.3.5.1.1), if authorized, to satisfy the necessary preconditions for the MCPTT user 2 on MCPTT client 2 to initiate a MCPTT group call from that MCPTT group. + - an MCPTT private call, then the MCPTT user 2 on MCPTT client 2 is permitted to initiate an MCPTT private call to the identified MCPTT user. + +![Sequence diagram illustrating the 'Remotely initiated MCPTT call request' procedure. Lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2. The sequence starts with a self-call on client 1 (step 1), followed by a request to the server (step 2). The server sends an authorize request (step 3) and then a request to client 2 (step 4). Client 2 may notify the user (step 5, dashed box), send a response to the server (step 6), and the server then informs client 1 (step 7). Finally, client 2 initiates the MCPTT call (step 8).](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + Note left of MCPTT client 1: 1. Remotely initiated MCPTT call + MCPTT client 1->>MCPTT server: 2. Remotely initiated MCPTT call request + MCPTT server->>MCPTT server: 3. Authorize request + MCPTT server->>MCPTT client 2: 4. Remotely initiated MCPTT call request + Note right of MCPTT client 2: 5. Notify user + MCPTT client 2-->>MCPTT server: 6. Remotely initiated MCPTT call response + MCPTT server-->>MCPTT client 1: 7. Remotely initiated MCPTT call response + Note right of MCPTT client 2: 8. Initiate MCPTT call + +``` + +Sequence diagram illustrating the 'Remotely initiated MCPTT call request' procedure. Lifelines: MCPTT client 1, MCPTT server, and MCPTT client 2. The sequence starts with a self-call on client 1 (step 1), followed by a request to the server (step 2). The server sends an authorize request (step 3) and then a request to client 2 (step 4). Client 2 may notify the user (step 5, dashed box), send a response to the server (step 6), and the server then informs client 1 (step 7). Finally, client 2 initiates the MCPTT call (step 8). + +**Figure 10.16.3.1-1: Remotely initiated MCPTT call request** + +1. MCPTT user on MCPTT client 1 initiates a remotely initiated MCPTT call request to the MCPTT user of MCPTT client 2. +2. MCPTT client 1 sends a remotely initiated MCPTT call request towards the MCPTT server. +3. MCPTT server checks whether the MCPTT user at MCPTT client 1 is authorized to initiate a remotely initiated MCPTT call request. +4. If authorized, MCPTT server sends the corresponding remotely initiated MCPTT call request towards the MCPTT client 2. +5. Based on the received information the receiving MCPTT client 2 may notify the user of the remotely initiated MCPTT call request. +6. Optionally the receiving MCPTT client 2 sends a remotely initiated MCPTT call response to the MCPTT server. +7. After receiving the remotely initiated MCPTT call response from MCPTT client 2, the MCPTT server informs the MCPTT client 1 about successful remotely initiated MCPTT call request. + +NOTE 1: Step 6 and step 7 might not be sent, since it could be determined that the remotely initiated MCPTT call was successful by receiving the MCPTT call initiated by MCPTT client 2. + +8. Based on the received information the MCPTT client 2 initiates an MCPTT call (either an MCPTT group call or an MCPTT private call) using the normal MCPTT call establishment procedures (10.6.2.3.1.1.2 or 10.7.2.2) with implicit floor request. + +NOTE 2: Step 6 and step 7 are received in this order. However, step 6 or step 7 or both might occur before or after step 8. + +The result of these procedures is an on-going MCPTT (group or private) call which includes MCPTT client 1. + +## 10.17 Support for multiple devices + +### 10.17.1 General + +An MCPTT user may be authorized to use the MCPTT service from multiple MCPTT UEs as per the procedure in subclause 10.2. + +If an MCPTT server receives a service authorization request for an MCPTT user who is previously MCPTT service authorized on another MCPTT UE, then the MCPTT server shall process this service authorization request as described in subclause 10.2. In the MCPTT service authorization response to the MCPTT user, the MCPTT server shall also indicate that the MCPTT user is already MCPTT service authorized from another MCPTT UE. + +**Editor's Note:** How to log off remotely from MCPTT clients on one or more other MCPTT UEs that the MCPTT user is already MCPTT service authorized from is FFS. + +# --- Annex A (normative): MCPTT related configuration data + +## A.1 General + +This Annex provides information about the static data needed for configuration for the MCPTT service, which belongs to one of the following categories: + +- MCPTT UE configuration data (see subclause A.2); +- MCPTT user profile configuration data (see subclause A.3); +- MCPTT related group configuration data (see subclause A.4); and +- MCPTT service configuration data (see subclause A.5). + +For each configuration category, data is split between configuration data that is applicable to both on-network and off-network, configuration data that is applicable to on-network only, and configuration data that is applicable to off-network only. The configuration data in each configuration category corresponds to a single instance of the category type i.e. the MCPTT UE, MCPTT group, MCPTT user and MCPTT service configuration data refers to the information that will be stored against each MCPTT UE, MCPTT group, MCPTT user and MCPTT service. This means that the three separate tables (on-network and off-network, on-network only, off-network only) for each configuration category represent the complete set of data for each configuration data category element. + +The columns in the tables have the following meanings: + +- Reference: the reference of the corresponding requirement in 3GPP TS 22.179 [2] or 3GPP TS 22.280 [17] or 3GPP TS 23.280 [16] or the corresponding subclause from the present document. +- Parameter description: A short definition of the semantics of the corresponding item of data, including denotation of the level of the parameter in the configuration hierarchy. +- When it is not clear to which functional entities the parameter is configured, then one or more columns indicating this are provided where the following nomenclature is used: + - "Y" to denote "Yes" i.e. the parameter denoted for the row needs to be configured to the functional entity denoted for the column. + - "N" to denote "No" i.e. the parameter denoted for the row does not need to be configured to the functional entity denoted for the column. + +Parameters within a set of configuration data have a level within a hierarchy that pertains only to that configuration data. The hierarchy of the configuration data is common across all three tables of on-network and off-network, on network only and off network only. The level of a parameter within the hierarchy of the configuration data is denoted by use of the character ">" in the parameter description field within each table, one per level. Parameters that are at the top most level within the hierarchy have no ">" character. Parameters that have one or more ">" characters are child parameters of the first parameter above them that has one less ">" character. Parent parameters are parameters that have one or more child parameters. Parent parameters act solely as a "grouping" of their child parameters and therefore do not contain an actual value themselves i.e. they are just containers for their child parameters. + +Each parameter that can be configured online shall only be configured through one online reference point. Each parameter that can be configured offline shall only be configured through one offline reference point. The most recent configuration data made available to the MCPTT UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism. + +## --- A.2 MCPTT UE configuration data + +The general aspects of UE configuration are specified in 3GPP TS 23.280 [16]. Data in tables A.2-1 and A.2-2 have to be known by the MCPTT UE after MCPTT authorization. + +Data in table A.2-1 can be configured offline using the CSC-11 reference point. Table A.2-2 contains the UE configuration required to support the use of off-network MCPTT service. + +**Table A.2-1: UE configuration data (on and off network)** + +| Reference | Parameter description | +|---------------------------------------|--------------------------------------------------| +| [R-5. 4.2-002] of 3GPP TS 22.280 [17] | Maximum number of simultaneous group calls (Nc4) | +| [R-5.4.2-003] of 3GPP TS 22.280 [17] | Maximum number of transmissions (Nc5) in a group | +| [R-5.5.2-007] of 3GPP TS 22.280 [17] | Maximum number of private calls (N10) | + +**Table A.2-2: UE configuration data (on network)** + +| Reference | Parameter description | +|----------------------------------------|------------------------------------------------------------------------------------------------------------------------------| +| Subclause 5.2.3 of 3GPP TS 23.280 [16] | Relay service (Y/N) | +| Subclause 5.2.3 of 3GPP TS 23.280 [16] | List of allowed relayed MCPTT groups and their relay service code (as specified in 3GPP TS 23.303 [7]) (optional) (see NOTE) | +| | > MCPTT group ID | +| | > Relay service code (as specified in 3GPP TS 23.303 [7]) | +| Subclause 5.2.7 of 3GPP TS 23.280 [16] | Indication of whether the UE shall use IPv4 or IPv6 for on-network MCPTT | +| | MCPTT server | +| | > Server URI | +| NOTE: | When the value of the parameter Relay service is N, this parameter and its child parameters are not needed. | + +## A.3 MCPTT user profile configuration data + +The general aspects of MC service user profile configuration data are specified in 3GPP TS 23.280 [16]. The MCPTT user profile configuration data is stored in the MCPTT user database. The MCPTT server obtains the MCPTT user profile configuration data from the MCPTT user database (MCPTT-2). + +Tables A.3-1 and A.3-2 contain the MCPTT user profile configuration required to support the use of on-network MCPTT service. Tables A.3-1 and A.3-3 contain the MCPTT user profile configuration required to support the use of off-network MCPTT service. Data in table A.3-1 and A.3-3 can be configured offline using the CSC-11 reference point. + +**Table A.3-1: MCPTT user profile data (on and off network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Configuration management server | MCPTT user database | +|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|----------|--------------|---------------------------------|---------------------| +| Subclause 8.1.2 of 3GPP TS 23.280 [16] | MCPTT user identity (MCPTT ID) | Y | Y | Y | Y | +| 3GPP TS 33.180 [19] | KMSUri for security domain of MCPTT ID (see NOTE 4) | Y | Y | Y | Y | +| Subclause 5.2.4 of 3GPP TS 23.280 [16] | Pre-selected MCPTT user profile indication (see NOTE 3) | Y | Y | Y | Y | +| Subclause 5.2.4 of 3GPP TS 23.280 [16] | MCPTT user profile index | Y | Y | Y | Y | +| Subclause 5.2.4 of 3GPP TS 23.280 [16] | MCPTT user profile name | Y | Y | Y | Y | +| [R-5.19-007], [R-6.13.4-002] of 3GPP TS 22.280 [17] | User profile status (enabled/disabled) | | Y | Y | Y | +| [R-5.8-001], [R-6.9-003] of 3GPP TS 22.280 [17] | Authorised to create and delete aliases of an MCPTT User and its associated user profiles. | | | Y | Y | +| [R-5.8-002], [R-6.9-003] of 3GPP TS 22.280 [17] | Alphanumeric aliases of user | Y | Y | Y | Y | +| [R-5.10-001] of 3GPP TS 22.280 [17] | Participant type of the user | Y | Y | Y | Y | +| [R-5.3-002], [R-5.10-001] of 3GPP TS 22.280 [17] | User's Mission Critical Organization (i.e. which organization a user belongs to) | Y | Y | Y | Y | +| [R-5.5.2-008] of 3GPP TS 22.280 [17] | Maximum number of simultaneously received group calls (Nc5) | | Y | Y | Y | +| [R-5.6.5-004] of 3GPP TS 22.179 [2] | Authorised to make a private call | Y | Y | Y | Y | +| [R-5.6.5-001] of 3GPP TS 22.179 [2] | Authorised to make a private call with manual commencement | Y | Y | Y | Y | +| [R-5.6.5-003] of 3GPP TS 22.179 [2]<br>[R-6.7.4-004] of 3GPP TS 22.280 [17] | List of user(s) who can be called in private call | | | | | +| | > MCPTT ID | Y | Y | Y | Y | +| | > User info ID | Y | Y | Y | Y | +| | > ProSe discovery group ID | Y | Y | Y | Y | +| 3GPP TS 33.180 [19] | > KMSUri for security domain of MCPTT ID (see NOTE 4) | Y | Y | Y | Y | +| | > Presentation priority relative to other users and groups (see NOTE 2) | Y | Y | Y | Y | +| [R-5.6.5-003] of 3GPP TS 22.179 [2] | Authorised to make a private call to users not included in "list of user(s) who can be called in private call" | Y | Y | Y | Y | +| [R-5.6.5-002] of 3GPP TS 22.179 [2] | Authorised to make a private call with automatic commencement | Y | Y | Y | Y | +| [R-5.6.3-011], [R-6.7.4-010] of 3GPP TS 22.179 [2] | Authorisation of user to force automatic answer for a private call | Y | Y | Y | Y | +| [R-5.6.5-006], [R-6.7.5-002] of 3GPP TS 22.179 [2] | Authorised to restrict the provision of a notification of call failure reason for private call | Y | Y | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | Authorisation to protect confidentiality and integrity of media in a private call (see NOTE 1) | Y | Y | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | Authorisation to protect confidentiality and integrity of floor control signalling in a private call (see NOTE 1) | Y | Y | Y | Y | +| [R-5.7.2.1.1-001] of 3GPP TS 22.280 [17] | Authorisation to make an MCPTT emergency group call functionality enabled for user | Y | Y | Y | Y | + +| | | | | | | +|--------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---| +| [R-5.7.2.1.1-001] of 3GPP TS 22.280 [17] | Group used on initiation of an MCPTT emergency group call (currently selected/ dedicated) | Y | Y | Y | Y | +| [R-5.7.2.1.2-005] of 3GPP TS 22.280 [17] | Authorisation to cancel an in progress emergency associated with a group | Y | Y | Y | Y | +| [R-5.7.2.2.1-001] of 3GPP TS 22.280 [17] | Authorised to make an Imminent Peril group call | Y | Y | Y | Y | +| [R-5.7.2.2.1-009] of 3GPP TS 22.280 [17] | Group used on initiation of an MCPTT imminent peril group call (currently selected/ dedicated/ default if no group selected) | Y | Y | Y | Y | +| [R-5.7.2.2.2-002] of 3GPP TS 22.280 [17] | Authorised for imminent in- peril cancellation | Y | Y | Y | Y | +| [R-5.7.2.3.1-001] of 3GPP TS 22.179 [2] | Recipient for an emergency private call (Pre-configured/ user locally determined) | Y | Y | Y | Y | +| [R-5.7.2.3.1-001] of 3GPP TS 22.179 [2] | Authorised to make an emergency private call | Y | Y | Y | Y | +| [R-5.7.2.3.2-001] of 3GPP TS 22.179 [2] | Authorised to cancel emergency priority in a private emergency call by an authorized user | Y | Y | Y | Y | +| [R-5.7.2.4.1-002] of 3GPP TS 22.280 [17] | Authorised to activate emergency alert | Y | Y | Y | Y | +| [R-5.7.2.4.1-004], [R-5.7.2.4.1-008], [R-5.7.2.4.1-012] of 3GPP TS 22.280 [17] | Group / user recipient of an emergency alert (Pre-defined group, currently selected group, pre-defined recipient/ user locally defined recipient/ default if no recipient selected) | Y | Y | Y | Y | +| [R-5.7.2.4.2-002] of 3GPP TS 22.280 [17] | Authorisation to cancel an MCPTT emergency alert | Y | Y | Y | Y | +| [R-5.1.7-002] of 3GPP TS 22.280 [17] | Priority of the user for initiating/receiving calls | | Y | Y | Y | +| [R-5.2.2-003] of 3GPP TS 22.280 [17] | Authorisation to create a group-broadcast group | | | Y | Y | +| [R-5.2.2-003] of 3GPP TS 22.280 [17] | Authorisation to create a user-broadcast group | | | Y | Y | +| [R-5.3-003], [R-6.12-001], [R-7.2-005] of 3GPP TS 22.280 [17] | Authorisation to provide location information to other MCPTT users on a call when talking | | Y | Y | Y | +| 3GPP TS 23.283 [20] | Authorised to use LMR E2EE for interworking | Y | Y | Y | Y | +| 3GPP TS 23.283 [20] | > List of supported LMR technology types | | | | | +| 3GPP TS 23.283 [20] | >> LMR technology type (P25, TETRA etc.) | Y | N | Y | Y | +| 3GPP TS 23.283 [20] | >> URI of LMR key management functional entity (see NOTE 6) | Y | N | Y | Y | +| 3GPP TS 23.283 [20] | >> LMR specific identity (RSI for P25 or ITS1 for TETRA) (see NOTE 5) | Y | N | Y | Y | +| 3GPP TS 23.283 [20] | >> LMR specific security information (see NOTE 5) | Y | N | Y | Y | + +NOTE 1: Security mechanisms are specified in 3GPP TS 33.180 [11]. + +NOTE 2: The use of this parameter by the MCPTT UE is outside the scope of the present document. + +NOTE 3: As specified in 3GPP TS 23.280 [16], for each MCPTT user's set of MCPTT user profiles, only one MCPTT user profile shall be indicated as being the pre-selected MCPTT user profile. + +NOTE 4: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [16]. + +NOTE 5: This is an LMR specific parameter with no meaning within MC services. + +NOTE 6: The LMR key management functional entity is part of the LMR system and is outside the scope of the present document. + +**Table A.3-2: MCPTT user profile data (on network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Configuration management server | MCPTT user database | +|----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|----------|--------------|---------------------------------|---------------------| +| [R-5.1.5-001],<br>[R-5.1.5-002],<br>[R-5.10-001],<br>[R-6.4.7-002],<br>[R-6.8.1-008] of<br>3GPP TS 22.280 [17] | List of on-network MCPTT groups for use by an MCPTT user | | | | | +| | > MCPTT Group ID | Y | Y | Y | Y | +| | > Application plane server identity information of group management server where group is defined | | | | | +| | >> Server URI | Y | N | Y | Y | +| | > Application plane server identity information of identity management server which provides authorization for group (see NOTE 1) | | | | | +| | >> Server URI | Y | N | Y | Y | +| 3GPP TS 33.180 [19] | > KMSUri for security domain of group (see NOTE 3) | Y | Y | Y | Y | +| | > Presentation priority of the group relative to other groups and users (see NOTE 2) | Y | Y | Y | Y | +| [R-6.2.3.7.2-006] of<br>3GPP TS 22.179 [2] | > Authorisation of an MCPTT user to change the maximum number of simultaneous talkers | Y | Y | Y | Y | +| Subclause 5.2.5 of<br>3GPP TS 23.280 [16] | List of groups user implicitly affiliates to after MCPTT service authorization for the user | | | | | +| | > MCPTT Group IDs | Y | Y | Y | Y | +| [R-6.4.2-006] of<br>3GPP TS 22.280 [17] | Authorisation of an MCPTT user to request a list of which groups an MCPTT user has affiliated to | | Y | Y | Y | +| [R-6.4.6.1-002],<br>[R-6.4.6.1-003] of<br>3GPP TS 22.280 [17] | Authorisation to change affiliated groups of other specified user(s) | | Y | Y | Y | +| [R-6.4.6.2-001],<br>[R-6.4.6.2-002] of<br>3GPP TS 22.280 [17] | Authorisation to recommend to specified user(s) to affiliate to specific group(s) | | Y | Y | Y | +| [R-6.6.1-004] of<br>3GPP TS 22.280 [17] | Authorisation to perform regrouping | Y | Y | Y | Y | +| [R-6.7.2-001] of<br>3GPP TS 22.280 [17] | Presence status is available/not available to other users | Y | Y | Y | Y | +| [R-6.7.1-002],<br>[R-6.7.2-002] of<br>3GPP TS 22.280 [17] | List of MCPTT users that an MCPTT user is authorised to obtain presence of | | | | | +| | > MCPTT IDs | Y | Y | Y | Y | +| [R-6.7.2-003] of<br>3GPP TS 22.280 [17] | User is able/ unable to participate in private calls | Y | Y | Y | Y | +| [R-6.7.1-004],<br>[R-6.7.2-003],<br>[R-6.7.2-004] of<br>3GPP TS 22.280 [17] | Authorisation to query whether MCPTT User is available for private calls | | Y | Y | Y | +| [R-6.7.1-010] of<br>3GPP TS 22.179 [2] | Authorisation to override transmission in a private call | Y | Y | Y | Y | +| [R-6.7.1-013] of<br>3GPP TS 22.179 [2] | Authorisation to restrict provision of private call set-up failure cause to the caller | | Y | Y | Y | +| [R-6.7.6-001] of<br>3GPP TS 22.179 [2] | Authorized to make a private call-back request | Y | Y | Y | Y | +| [R-6.7.6-004] of<br>3GPP TS 22.179 [2] | Authorized to cancel a private call-back request | Y | Y | Y | Y | + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|---|---|---|---| +| [R-6.8.7.4.2-001], [R-6.8.7.4.2-002] of 3GPP TS 22.280 [17] | Authorisation of an MCPTT user to cancel an emergency alert on any MCPTT UE of any MCPTT user | | Y | Y | Y | +| [R-6.13.4-001] of 3GPP TS 22.280 [17] | Authorisation for a MCPTT user to enable/disable an MCPTT user | | Y | Y | Y | +| [R-6.13.4-003], [R-6.13.4-005], [R-6.13.4-006], [R-6.13.4-007] of 3GPP TS 22.280 [17] | Authorisation for an MCPTT user to (permanently /temporarily) enable/disable a UE | | Y | Y | Y | +| [R-6.2.3.4-001] of 3GPP TS 22.179 [2] | Authorisation to revoke permission to transmit | | Y | Y | Y | +| [R-7.14-002], [R-7.14-003] of 3GPP TS 22.280 [17] | Authorization for manual switch to off-network while in on-network | Y | Y | Y | Y | +| [R-5.1.5-004] of 3GPP TS 22.280 [17] | Limitation of number of affiliations per user (N2) | N | Y | Y | Y | +| [R-5.5.2-009] of 3GPP TS 22.179 [2] | Maximum number of simultaneous transmissions received in one group call for override (N7) | | Y | Y | Y | +| [R-6.4.6.1-001], [R-6.4.6.1-004] of 3GPP TS 22.280 [17] | List of MCPTT users whose selected groups are authorized to be remotely changed | | | | | +| | > MCPTT IDs | Y | Y | Y | Y | +| Subclause 10.15.3 | Authorization to make a first-to-answer call | Y | Y | Y | Y | +| [R-6.15.2.2.2-001] of 3GPP TS 22.280 [17] | Authorization to make a remotely initiated ambient listening private call | Y | Y | Y | Y | +| [R-6.15.2.2.3-001] of 3GPP TS 22.280 [17] | Authorization to make a locally initiated ambient listening private call | Y | Y | Y | Y | +| [R-6.15.3.2-001] of 3GPP TS 22.280 [17] | Authorization to make a remotely initiated private call | Y | Y | Y | Y | +| [R-6.15.3.2-003] of 3GPP TS 22.280 [17] | Authorization to make a remotely initiated group call | Y | Y | Y | Y | +| [R-5.9a-013] of 3GPP TS 22.280 [17] | Authorised to interrogate the functional alias(es) active for another MCPTT user | | Y | Y | Y | +| [R-5.9a-012] of 3GPP TS 22.280 [17] | Authorised to take over a functional alias from another MCPTT user | | Y | Y | Y | +| | List of functional alias(es) of the MCPTT user | | | | | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | > Functional alias | Y | Y | Y | Y | +| Subclause 5.2.9 of 3GPP TS 23.280 [16] | List of partner MCPTT systems in which this profile is valid for use during migration | | | | | +| Subclause 5.2.9 of 3GPP TS 23.280 [16] | > Identity of partner MCPTT system | Y | Y | Y | Y | +| Subclause 10.1.1 of 3GPP TS 23.280 [16] | > Access information for partner MCPTT system (see NOTE 4) | Y | | Y | Y | +| NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [16]. | | | | | | +| NOTE 2: The use of this parameter by the MCPTT UE is outside the scope of the present document. | | | | | | +| NOTE 3: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [16]. | | | | | | +| NOTE 4: Access information for each partner MCPTT system comprises the list of information required for initial UE configuration to access an MCPTT system, as defined in table A.6-1 of 3GPP TS 23.280 [16] | | | | | | + +**Table A.3-3: MCPTT user profile data (off network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Configuration management server | MCPTT user database | +|---------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|----------|--------------|---------------------------------|---------------------| +| [R-7.2-003], [R-7.6-004] of 3GPP TS 22.280 [17] | List of off-network MCPTT groups for use by an MCPTT user | Y | N | Y | Y | +| | > MCPTT Group ID | Y | N | Y | Y | +| | > Application plane server identity information of group management server where group is defined | | | | | +| | >> Server URI | Y | N | Y | Y | +| | > Application plane server identity information of identity management server which provides authorization for group (see NOTE 1) | | | | | +| | >> Server URI | Y | N | Y | Y | +| 3GPP TS 33.180 [19] | > KMSUri for security domain of group (see NOTE 3) | Y | N | Y | Y | +| | > Presentation priority of the group relative to other groups and users (see NOTE 2) | Y | N | Y | Y | +| [R-7.3.3-008] of 3GPP TS 22.179 [2] | Allowed listening of both overriding and overridden | Y | N | Y | Y | +| [R-7.3.3-006] of 3GPP TS 22.179 [2] | Allowed transmission for override (overriding and/or overridden) | Y | N | Y | Y | +| [R-7.8.1-001] of 3GPP TS 22.280 [17] | Authorization for participant to change an off-network group call in-progress to off-network emergency group call | Y | N | Y | Y | +| [R-7.8.3.1-003] of 3GPP TS 22.280 [17] | Authorization for participant to change an off-network group call in-progress to off-network imminent peril group call | Y | N | Y | Y | +| [R-7.12-002], [R-7.12-003] of 3GPP TS 22.280 [17] | Authorization for off-network services | Y | N | Y | Y | +| Subclause 10.7.2 | User info id (as specified in 3GPP TS 23.303 [7]) | Y | N | Y | Y | + +NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [16]. + +NOTE 2: The use of this parameter by the MCPTT UE is outside the scope of the present document. + +NOTE 3: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [16]. + +## A.4 MCPTT related group configuration data + +The general aspects of group configuration are specified in 3GPP TS 23.280 [16]. + +Parameters specified in table A.4-1 are child parameters of the "MCPTT configuration" parameter specified in table A.4-1 in 3GPP TS 23.280 [16]. Parameters specified in table A.4-2 are child parameters of the "MCPTT configuration" parameter specified in table A.4-2 in 3GPP TS 23.280 [16]. Parameters specified in table A.4-3 are child parameters of the "MCPTT configuration" parameter specified in table A.4-3 in 3GPP TS 23.280 [16]. + +**Table A.4-1: Group configuration data (on and off network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Group management server | +|-----------------------------------------------------------------|---------------------------------------------------------------------------------|----------|--------------|-------------------------| +| [R-6.4.9-006] of 3GPP TS 22.280 [17] | >> Preferred voice codecs for MCPTT group | Y | Y | Y | +| [R-5.7.2.1.1-013], [R-5.7.2.4.1-008] of 3GPP TS 22.280 [17] | >> Indication whether emergency group call is permitted on the MCPTT group | Y | Y | Y | +| [R-5.7.2.2.1-009] of 3GPP TS 22.280 [17] | >> Indication whether imminent peril group call is permitted on the MCPTT group | Y | Y | Y | +| [R-5.7.2.4.1-012] of 3GPP TS 22.280 [17] | >> Indication whether emergency alert is possible on the MCPTT group | Y | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | >> Media confidentiality and integrity protection (see NOTE) | Y | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | >> Floor control confidentiality and integrity protection (see NOTE) | Y | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | >> Group media protection security material (see NOTE) | Y | N | Y | +| NOTE: Security mechanisms are specified in 3GPP TS 33.180 [19]. | | | | | + +**Table A.4-2: Group configuration data (on-network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Group management server | +|---------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|----------|--------------|-------------------------| +| [R-5.7.2.1.2-002] of 3GPP TS 22.280 [17] | >> Timeout value for the cancellation of an in-progress emergency for an on-network group call | N | Y | Y | +| [R-5.7.2.2.2-004] of 3GPP TS 22.280 [17] | >> Timeout value for the cancellation of an in progress imminent-peril group call for an on-network group call | N | Y | Y | +| [R-6.2.4-003], [R-6.4.9-002] of 3GPP TS 22.179 [2] | >> Group call hang timer | N | Y | Y | +| [R-6.4.9-003] of 3GPP TS 22.280 [17] | >> Maximum duration of group calls | N | Y | Y | +| Subclause 10.6.2 | >> Group call model used for group (chat/ pre-arranged) | Y | Y | Y | +| [R-6.2.1-004], [R-6.2.1-007] of 3GPP TS 22.179 [2] | >> Minimum number of affiliated group members acknowledging before start of audio transmission | N | Y | Y | +| [R-6.2.1-007] of 3GPP TS 22.179 [2] | >> List of affiliated group members which have to acknowledge before start of audio transmission | | | | +| | >>>MCPTT IDs | N | Y | Y | +| [R-6.2.1-006], [R-6.2.1-007] of 3GPP TS 22.179 [2] | >> Geographical area where acknowledgement of all affiliated group members is required before start of audio transmission | N | Y | Y | +| [R-6.2.1-008], [R-6.2.1-009] of 3GPP TS 22.179 [2] | >> Timeout for acknowledgement of required group members | N | Y | Y | +| [R-6.2.1-008], [R-6.2.1-009], [R-6.2.1-012] of 3GPP TS 22.179 [2] | >> Action upon failure to receive acknowledgement from required group members before call timeout (proceed or abandon) | N | Y | Y | +| [R-6.4.9-004] of 3GPP TS 22.280 [17] | >> List of group members with receive-only capability (see NOTE 1) | | | | +| | >>>MCPTT IDs | N | Y | Y | +| [R-6.4.5-001], [R-6.4.5-003] of 3GPP TS 22.280 [17] | >> Authorisation of a user to request a list of affiliated members of a group | Y | Y | Y | +| [R-5.1.7-002], [R-6.2.2-001], [R-6.6.2.2-006], [R-6.8.6.2-003] of 3GPP TS 22.280 [17] | >> Priority of the group | N | Y | Y | +| [R-6.8.6.2-003] of 3GPP TS 22.280 [17] | >> Pre-emption capability | Y | Y | Y | +| [R-6.8.6.2-003] of 3GPP TS 22.280 [17] | >> Pre-empted capability | Y | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | >> Group floor control protection security material for multicast use (see NOTE 2) | Y | Y | Y | +| [R-6.2.3.6.2-001] of 3GPP TS 22.179 [2] | >> Audio cut-in policy (enabled/disabled) | N | Y | Y | +| [R-6.2.3.7.2-001] of 3GPP TS 22.179 [2] | >> Support of multi-talker control | Y | Y | Y | +| [R-6.2.3.7.2-005] of 3GPP TS 22.179 [2] | >> Maximum number of simultaneous talkers applicable for multi-talker control | N | Y | Y | +| Subclause 7.4.2.3.5 and subclause 7.4.2.3.6 | >> Audio mixing is performed in the UE or in the network to support multi-talker control | Y | Y | Y | +| [R-6.2.3.7.2-003] of 3GPP TS 22.179 [2] | >> List of group members which are allowed to talk (see NOTE 1) | | | | +| | >>> MCPTT IDs | N | Y | Y | + +| | | | | | +|------------------------------------------|--------------------------------------------------------------------------------------------------|---|---|---| +| Subclause 10.2.7 of 3GPP TS 23.280 [16] | >> List of partner MCPTT systems where system specific configuration applies for interconnection | | | | +| | >>> MC system identity of partner MCPTT system | N | Y | Y | +| [R-6.4.9-004] of 3GPP TS 22.280 [17] | >>> List of group members with receive-only capability (see NOTE 1) | | | | +| | >>>>MCPTT IDs | N | Y | Y | +| [R-6.2.3.7.2-003] of 3GPP TS 22.179 [2], | >>> List of group members which are allowed to talk (see NOTE 1) | | | | +| | >>>> MCPTT IDs | N | Y | Y | +| 3GPP TS 23.283 [20] | >> Indication whether use of LMR E2EE is permitted on the MCPTT group | Y | N | Y | +| 3GPP TS 23.283 [20] | >> LMR specific identity for MCPTT group (see NOTE 3) | Y | N | Y | +| 3GPP TS 23.283 [20] | >> Group to key binding (see NOTE 3) | Y | N | Y | + +NOTE 1: A group member shall not be listed in both the list of group members with receive only capability and the list of group members which are allowed to talk. +NOTE 2: The details of security related elements are specified in 3GPP TS 33.180 [19]. +NOTE 3: This is an LMR specific parameter with no meaning within MC services. + +**Table A.4-3: Group configuration data (off-network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Group management server | +|------------------------------------------|-----------------------------------------------------------------------------------------------------------------|----------|--------------|-------------------------| +| [R-5.7.2.1.2-002] of 3GPP TS 22.280 [17] | >> Timeout value for the cancellation of an in-progress emergency for an off-network group call | Y | N | Y | +| [R-5.7.2.2.2-004] of 3GPP TS 22.280 [17] | >> Timeout value for the cancellation of an in progress imminent-peril group call for an off-network group call | Y | N | Y | +| [R-7.4-002] of 3GPP TS 22.179 [2] | >> Group call hang timer | Y | N | Y | +| [R-7.4-003] of 3GPP TS 22.280 [17] | >> Max duration of group calls | Y | N | Y | +| Subclause 10.6.3.9.1 | >> Default <b>ProSe</b> Per-Packet priority (as specified in 3GPP <b>TS 23.303</b> [7]) values | | | | +| | >>> MCPTT group call signalling | Y | N | Y | +| | >>> MCPTT group call media | Y | N | Y | +| | >>> MCPTT emergency group call signalling | Y | N | Y | +| | >>> MCPTT emergency group call media | Y | N | Y | +| | >>> MCPTT imminent peril group call signalling | Y | N | Y | +| | >>> MCPTT imminent peril group call media | Y | N | Y | + +## A.5 MCPTT service configuration data + +The general aspects of MC service configuration are specified in 3GPP TS 23.280 [16]. The MCPTT service configuration data is stored in the MCPTT server. + +Tables A.5-1 and A.5-2 describe the configuration data required to support the use of on-network MCPTT service. Tables A.5-1 and A.5-3 describe the configuration data required to support the use of off-network MCPTT service. Data in tables A.5-1 and A.5-3 can be configured offline using the CSC-11 reference point. + +**Table A.5-1: MCPTT service configuration data (on and off network)** + +| <b>Reference</b> | <b>Parameter description</b> | <b>MCPTT UE</b> | <b>MCPTT Server</b> | <b>Configuration management server</b> | +|--------------------------------------|-----------------------------------------------------------------------------------------------------|-----------------|---------------------|----------------------------------------| +| [R-5.2.2-001] of 3GPP TS 22.280 [17] | Levels of group hierarchy for group-broadcast groups (Bc1) | Y | Y | Y | +| [R-5.2.3-001] of 3GPP TS 22.280 [17] | Levels of user hierarchy for user-broadcast groups (Bc2) | Y | Y | Y | +| [R-5.8-002] of 3GPP TS 22.280 [17] | Minimum length (Nc3) of an alphanumeric identifier (i.e. alias) assigned by an MCPTT administrator. | Y | N | Y | + +**Table A.5-2: MCPTT service configuration data (on-network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Configuration management server | +|--------------------------------------------------------|-----------------------------------------------------------------------------------------------|----------|--------------|---------------------------------| +| [R-5.7.2.3.2-002] of 3GPP TS 22.179 [2] | Timeout value for the cancellation of an in-progress emergency for an on-network private call | N | Y | Y | +| [R-5.7.2.1.2-002] of 3GPP TS 22.280 [17] | Time limit for an in-progress emergency related to an on-network MCPTT group | N | Y | Y | +| [R-5.6.5-004] of 3GPP TS 22.179 [2] | Max on-network private call (with floor control) duration | N | Y | Y | +| [R-6.2.4-003] of 3GPP TS 22.179 [2] | Hang timer for private calls | N | Y | Y | +| [R-6.7.2-008] of 3GPP TS 22.280 [17] | Max duration of private call (without floor control) | N | Y | Y | +| [R-6.2.3.3.1-001] of 3GPP TS 22.179 [2] | Hierarchy of participant rights to override | N | Y | Y | +| [R-6.2.3.5-002] of 3GPP TS 22.179 [2] | Transmit time limit from a single request to transmit in a group or private call transmission | N | Y | Y | +| [R-6.2.3.5-003], [R-6.2.3.5-004] of 3GPP TS 22.179 [2] | Configuration of warning time before time limit of transmission is reached (on-network) | N | Y | Y | +| [R-6.2.4-005] of 3GPP TS 22.179 [2] | Configuration of warning time before call hang time (on-network) | N | Y | Y | +| [R-6.2.3.2-006] of 3GPP TS 22.179 [2] | Depth of floor control queue | N | Y | Y | +| [R-6.2.3.2-012] of 3GPP TS 22.179 [2] | Max time for a user's floor control request to be queued | N | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | Protect confidentiality of signalling (see NOTE) | Y | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | Protect integrity of signalling (see NOTE) | Y | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | Use signalling protection between MCPTT servers (see NOTE) | N | Y | Y | +| [R-5.13-001] of 3GPP TS 22.280 [17] | Use floor control protection between MCPTT servers (see NOTE) | N | Y | Y | +| | List of functional alias identities | | | | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | > Functional alias | Y | Y | Y | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | > Limit number of simultaneous activations | | Y | Y | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | > This functional alias can be taken over | Y | Y | Y | +| | > List of users | | | | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | >> MCPTT ID | | Y | Y | + +NOTE: Security mechanisms are specified in 3GPP TS 33.180 [19]. + +**Table A.5-3: MCPTT service configuration data (off-network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Configuration management server | +|--------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|----------|--------------|---------------------------------| +| [R-5.7.2.3.2-002] of 3GPP TS 22.179 [2] | Timeout value for the cancellation of an in-progress emergency for an off-network private call | Y | N | Y | +| [R-5.7.2.1.2-002] of 3GPP TS 22.280 [17] | Time limit for an in-progress emergency related to an off-network MCPTT group | Y | N | Y | +| [R-5.6.5-004] of 3GPP TS 22.179 [2] | Max off-network private call (with floor control) duration | Y | N | Y | +| [R-7.4-002] of 3GPP TS 22.179 [2]<br>[R-7.4-003] of 3GPP TS 22.280 [17] | Hang timer for private calls in off-network | Y | N | Y | +| [R-7.3.3-001], [R-7.3.3-002], [R-7.3.3-003] of 3GPP TS 22.179 [2] | Priority hierarchy for floor control override in off-network | Y | N | Y | +| [R-7.3.5-001], [R-7.3.5-002], [R-7.3.5-003] of 3GPP TS 22.179 [2] | Transmit time limit from a single request to transmit in a group or private call. | Y | N | Y | +| [R-7.3.5-001], [R-7.3.5-004] of 3GPP TS 22.179 [2] | Configuration of warning time before time limit of transmission is reached (off-network) | Y | N | Y | +| [R-7.4-004] of 3GPP TS 22.280 [17] | Configuration of warning time before hang time is reached (off-network) | Y | N | Y | +| [R-7.7-001], [R-7.7-003] of 3GPP TS 22.280 [17]<br>[R-7.7-002] of 3GPP TS 22.179 [2] | Default <b>ProSe</b> Per-Packet priority (as specified in 3GPP <b>TS 23.303</b> [7]) values | | | | +| | > MCPTT private call signalling | Y | N | Y | +| | > MCPTT private call media | Y | N | Y | +| | > MCPTT Emergency private call signalling | Y | N | Y | +| | > MCPTT Emergency private call media | Y | N | Y | +| [R-7.15-001], [R-7.7-003] of 3GPP TS 22.280 [17] | Configuration of metadata to log | Y | N | Y | + +# Annex B (informative): Local UE settings for MCPTT + +## B.1 Local UE settings for MCPTT + +Table B.1-1 details local UE settings for MCPTT that represent important functionalities that may be required by MCPTT UEs, however these functionalities do not require central configuration like the parameters in annex A, so these are detailed in this annex for information to UE vendors interested in producing MCPTT UEs. The various columns in the tables have the following meanings: + +- Reference: Is the reference of the corresponding requirement in 3GPP TS 22.179 [2]. +- Definition: A short definition of the local UE setting. + +**Table B.1-1: Local UE settings for MCPTT** + +| Reference | Definition | +|------------------------------------------|---------------------------------------------------------------------------| +| [R-5.1.1-003] of 3GPP TS 22.280 [17] | Call reception signalling method | +| [R-5.1.1-004] of 3GPP TS 22.280 [17] | Disabling of call reception signalling | +| [R-5.8-003] of 3GPP TS 22.280 [17] | Configuration of display of MCPTT ID (on/off) | +| [R-5.8-003] of 3GPP TS 22.280 [17] | Configuration of display of aliases associated with the MCPTT ID (on/off) | +| [R-5.8-003] of 3GPP TS 22.280 [17] | Configuration of display of Selected MCPTT Group (on/off) | +| [R-5.8-003] of 3GPP TS 22.280 [17] | Configuration of display of Mission Critical Organization name (on/off) | +| [R-6.8.7.4.1-003] of 3GPP TS 22.280 [17] | Configuration of the notification of an emergency alert | + +# --- Annex C (informative): Change history + +| Date | Meeting | TDoc | CR | R ev | Cat | Subject/Comment | New | +|---------|---------|-----------|------|------|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2016-04 | | | | | | Initial version. | 0.0.0 | +| 2016-04 | | | | | | Alignment with the following Rel-13 CRs agreed at SA6#10:<br>CR0053(S6-160271), CR0055(S6-160307),<br>CR0057(S6-160312), CR0058(S6-160289),<br>CR0059(S6-160346), CR0060(S6-160335),<br>CR0061(S6-160268), CR0062(S6-160333),<br>CR0067(S6-160274), CR0069(S6-160313),<br>CR0071(S6-160199), CR0072(S6-160334),<br>CR0075(S6-160331), CR0076(S6-160269),<br>CR0078(S6-160284), CR0079(S6-160360),<br>CR0080(S6-160297), CR0081(S6-160332),<br>CR0085(S6-160361), CR0088(S6-160291),<br>CR0089(S6-160347), CR0090(S6-160310),<br>CR0093(S6-160293), CR0094(S6-160294),<br>CR0099(S6-160342) | 0.1.0 | +| 2016-06 | | | | | | Implemented the following pCRs approved during SA6#11:<br>S6-160414, S6-160475, S6-160497, S6-160499,<br>S6-160501, S6-160508, S6-160514, S6-160518,<br>S6-160530, S6-160532, S6-160568, S6-160571,<br>S6-160581, S6-160584, S6-160588, and merged<br>relevant content from S6-160489.<br>Editorial changes: renumbering subclauses as<br>needed; added top level subclauses where needed<br>with editor's notes; added a few missing subclauses<br>at level 2 with editor's notes; use actual TS numbers<br>made available at SA plenary: 23.379 and 23.280. | 0.2.0 | +| 2016-09 | | | | | | Implemented the following pCRs approved during SA6#12:<br>S6-160681, S6-160698, S6-160707, S6-160790,<br>S6-160802, S6-160828, S6-160873, S6-160908,<br>S6-160909, S6-160921, S6-160925.<br>Editorial changes: renumbering subclauses as<br>needed; added a few missing headings at level 2<br>and level 3 with editor's notes for consistency. | 0.3.0 | +| 2016-10 | | | | | | Implemented the following pCRs approved during SA6#13:<br>S6-160961, S6-161016, S6-161112, S6-161113,<br>S6-161116, S6-161124, S6-161210, S6-161211,<br>S6-161212, S6-161219, S6-161231, S6-161249,<br>S6-161251, S6-161258, S6-161268<br>Editorial changes: renumbering subclauses as<br>needed. | 0.4.0 | +| 2016-11 | | | | | | Implemented the following pCRs approved during SA6#14:<br>S6-161330, S6-161522, S6-161538, S6-161564,<br>S6-161572, S6-161584, S6-161591, S6-161595,<br>S6-161596, S6-161597, S6-161598, S6-161607.<br>Editorial changes: renumbering subclauses as<br>needed. | 0.5.0 | +| 2016-12 | SA#74 | SP-160876 | | | | Submitted for Approval at SA#74 | 1.0.0 | +| 2016-12 | SA#74 | SP-160876 | | | | MCC Editorial update for publication after TSG SA approval (SA#74) | 14.0.0 | +| 2017-03 | SA#75 | SP-170068 | 0003 | 1 | F | Alignment of definitions | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0004 | 2 | F | Alignment of group affiliation and de-affiliation requirements | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0005 | 1 | F | Alignment of bearer management | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0006 | 1 | F | Resolve editor's note in clause 10.6.2.8.1 | 14.1.0 | +| 2017-03 | SA#75 | SP-170069 | 0008 | 1 | F | Store and update affiliation status in the GMS | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0009 | 2 | F | Duplicated reference remove | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0011 | 1 | F | Corrections to MCPTT UE configuration data | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0013 | 1 | D | Correction of references | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0016 | 1 | D | Message title alignment | 14.1.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-----------------------------------------------------------------------------------------------------------|--------| +| 2017-03 | SA#75 | SP-170068 | 0017 | 3 | F | Resolve group ID issue for temporary group call – user regroup | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0018 | 1 | F | Addition of definition for MCPTT ID | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0019 | | F | Correction of requirement reference for list of implicitly affiliated groups in MCPTT user profile config | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0020 | 2 | F | Simultaneous floor requests | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0021 | 2 | F | Correction on floor control | 14.1.0 | +| 2017-03 | SA#75 | SP-170068 | 0022 | 2 | F | Miscellaneous corrections on term | 14.1.0 | +| 2017-06 | SA#76 | SP-170389 | 0042 | 1 | F | Miscellaneous corrections to configuration | 14.2.0 | +| 2017-06 | SA#76 | SP-170389 | 0043 | 6 | F | Addition of identity management server address per group | 14.2.0 | +| 2017-06 | SA#76 | SP-170389 | 0049 | 1 | F | Correction in Ambient Listening | 14.2.0 | +| 2017-06 | SA#76 | SP-170389 | 0050 | 1 | F | Clarifications on response in off-network | 14.2.0 | +| 2017-06 | SA#76 | SP-170389 | 0062 | 2 | F | Inclusion of KMSUri to allow multiple security domains | 14.2.0 | +| 2017-06 | SA#76 | SP-170389 | 0068 | 1 | F | Corrections to configuration for ambient listening | 14.2.0 | +| 2017-06 | SA#76 | SP-170389 | 0069 | 1 | F | Correction to configuration for first-to-answer call | 14.2.0 | +| 2017-06 | SA#76 | SP-170389 | 0070 | | F | Corrections to Group configuration data for all MC services | 14.2.0 | +| 2017-06 | SA#76 | SP-170340 | 0044 | 1 | B | MCPTT unicast media flow stop and resume | 15.0.0 | +| 2017-06 | SA#76 | SP-170398 | 0063 | 1 | D | Editorial corrections in call back cancel request | 15.0.0 | +| 2017-06 | SA#76 | SP-170340 | 0066 | 1 | C | Resource Management enhancements for MCPTT | 15.0.0 | +| 2017-06 | SA#76 | SP-170340 | 0067 | 2 | C | Addition of Floor acknowledgement | 15.0.0 | +| 2017-09 | SA#77 | SP-170685 | 0074 | 2 | B | Updating IWF-1 description | 15.1.0 | +| 2017-09 | SA#77 | SP-170678 | 0075 | 2 | A | CR on MapGroupToBearer message | 15.1.0 | +| 2017-09 | SA#77 | SP-170678 | 0077 | 1 | A | Corrections for configuration references | 15.1.0 | +| 2018-01 | SA#78 | SP-170895 | 0079 | 3 | B | Functional model for MCPTT interconnection | 15.2.0 | +| 2018-01 | SA#78 | SP-170896 | 0086 | 2 | B | Introduction of the multi-talker control | 15.2.0 | +| 2018-01 | SA#78 | SP-170896 | 0087 | 3 | B | Introduction of Functional alias(es) | 15.2.0 | +| 2018-01 | SA#78 | SP-170896 | 0089 | 1 | C | Multi-talker floor release message and procedure | 15.2.0 | +| 2018-01 | SA#78 | SP-170886 | 0101 | 2 | A | Rejection of group call | 15.2.0 | +| 2018-01 | SA#78 | SP-170886 | 0103 | 2 | A | MCPTT server PSI configuration | 15.2.0 | +| 2018-01 | SA#78 | SP-170886 | 0110 | 1 | A | authorization for remotely initiated MCPTT call | 15.2.0 | +| 2018-01 | SA#78 | SP-170890 | 0090 | 2 | F | Renaming of MCPTT emergency group call cancel | 15.2.0 | +| 2018-01 | SA#78 | SP-170890 | 0091 | 1 | F | Renaming of MCPTT "emergency condition" | 15.2.0 | +| 2018-01 | SA#78 | SP-170890 | 0093 | 2 | F | Renaming of MCPTT imminent peril group call cancel | 15.2.0 | +| 2018-01 | SA#78 | SP-170890 | 0094 | 2 | F | Renaming Off-network MCPTT emergency group cancel | 15.2.0 | +| 2018-01 | SA#78 | SP-170890 | 0095 | 2 | F | Adding implicit floor request IE to MCPTT emergency group call request | 15.2.0 | +| 2018-01 | SA#78 | SP-170890 | 0096 | 3 | B | Server-initiated Broadcast group call release procedure | 15.2.0 | +| 2018-01 | SA#78 | SP-170890 | 0107 | 2 | F | Renaming of "MCPTT emergency state cancel" and corrections to information flow | 15.2.0 | +| 2018-04 | SA#79 | SP-180146 | 0112 | 1 | A | Correction of security specification references | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0113 | 1 | A | User profile for MCPTT migration | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0114 | 4 | B | MCPTT specific group configuration for interconnection | 15.3.0 | +| 2018-04 | SA#79 | SP-180155 | 0115 | 3 | B | LMR E2EE user profile and group parameters | 15.3.0 | +| 2018-04 | SA#79 | SP-180158 | 0116 | 2 | F | Introduction of MCPTT call end response message | 15.3.0 | +| 2018-04 | SA#79 | SP-180150 | 0117 | 1 | F | Update of references to stage 1 specifications | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0119 | | B | Definition of MCPTT-3 | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0120 | | D | Editorial correction to gateway server entity | 15.3.0 | +| 2018-06 | SA#80 | SP-180365 | 0123 | 3 | A | Addition of implicit floor request IEs | 15.4.0 | +| 2018-06 | SA#80 | SP-180365 | 0125 | 1 | A | Corrections to implicit floor request handling | 15.4.0 | +| 2018-06 | SA#80 | SP-180373 | 0129 | 1 | F | Correction of referenced subclauses | 15.4.0 | +| 2018-06 | SA#80 | SP-180365 | 0133 | | A | Clarification for presentation priority in MCPTT UE configuration | 15.4.0 | +| 2018-06 | SA#80 | SP-180369 | 0134 | 2 | F | Update of MCPTT emergency alert for multicast | 15.4.0 | +| 2018-06 | SA#80 | SP-180369 | 0135 | 1 | F | Correction of Group call rejoin response | 15.4.0 | +| 2018-09 | SA#81 | SP-180672 | 0137 | 1 | F | Emergency Alert Area Trigger | 15.5.0 | +| 2018-09 | SA#81 | SP-180672 | 0138 | 1 | C | Location of Current Talker via Floor Request | 15.5.0 | +| 2018-09 | SA#81 | SP-180671 | 0140 | 2 | A | Removal of temporary regroup procedures | 15.5.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|-----------------------------------------------------------|--------| +| 2018-09 | SA#81 | SP-180672 | 0141 | | F | 23.379 Table A.3-1 duplicate note 4 | 15.5.0 | +| 2018-09 | SA#81 | SP-180672 | 0142 | 1 | F | Correction to Chat group call pre-condition | 15.5.0 | +| 2018-09 | SA#81 | SP-180672 | 0145 | 1 | F | Removal of group call notify from normal group call setup | 15.5.0 | +| 2018-09 | SA#81 | SP-180672 | 0147 | | F | Correction to chat group join mechanism | 15.5.0 | +| 2018-09 | SA#81 | SP-180678 | 0143 | 1 | B | Interconnection chat group call | 16.0.0 | +| 2018-09 | SA#81 | SP-180676 | 0146 | 1 | F | Issues with temporary regroup procedures | 16.0.0 | + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|----------------------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 10 | +| 1 Scope..... | 11 | +| 2 References..... | 11 | +| 3 Definitions, symbols and abbreviations..... | 12 | +| 3.1 Definitions..... | 12 | +| 3.2 Symbols..... | 13 | +| 3.3 Abbreviations ..... | 13 | +| 4 Introduction..... | 13 | +| 5 Architectural requirements..... | 13 | +| 5.1 Media routing requirements ..... | 13 | +| 5.2 MCVideo group affiliation and MCVideo group de-affiliation..... | 14 | +| 5.3 Device inventory requirements ..... | 14 | +| 5.4 Device discovery requirements (off-network) ..... | 14 | +| 5.5 Bearer management..... | 14 | +| 5.5.1 General ..... | 14 | +| 5.5.2 EPS bearer considerations ..... | 14 | +| 5.5.3 EPS unicast bearer considerations for MCVideo ..... | 14 | +| 5.5.4 MBMS bearer management..... | 15 | +| 5A Involved business relationships ..... | 15 | +| 6 MCVideo Functional model..... | 15 | +| 6.1 Functional model description..... | 15 | +| 6.1.1 On-network functional model..... | 15 | +| 6.1.2 Off-network functional model..... | 16 | +| 6.2 Functional entities description ..... | 16 | +| 6.2.1 General ..... | 16 | +| 6.2.2 MCVideo service application plane ..... | 16 | +| 6.2.2.1 General..... | 16 | +| 6.2.2.2 Common services core..... | 16 | +| 6.2.2.3 MCVideo application service ..... | 16 | +| 6.2.2.3.1 MCVideo client..... | 16 | +| 6.2.2.3.2 MCVideo server ..... | 16 | +| 6.2.2.3.3 Media distribution function..... | 17 | +| 6.2.2.3.4 Media mixer ..... | 17 | +| 6.2.2.3.5 MCVideo user database ..... | 17 | +| 6.2.2.3.6 Transmission control server ..... | 18 | +| 6.2.2.3.7 Transmission control participant..... | 18 | +| 6.2.2.3.8 MC gateway server..... | 18 | +| 6.3 Reference points..... | 18 | +| 6.3.1 Reference point MCVideo-1 (between the MCVideo client and the MCVideo server) ..... | 18 | +| 6.3.2 Reference point MCVideo-2 (between the MCVideo server and the MCVideo user database)..... | 18 | +| 6.3.3 Reference point MCVideo-3 (between the MCVideo server and the MCVideo server and between the MCVideo server and the MC gateway server) ..... | 18 | +| 6.3.4 Reference point MCVideo-4 (between the transmission control participant and the transmission control server)..... | 19 | +| 6.3.4A Reference point MCVideo-5 (unicast between the media distribution function and the EPS) ..... | 19 | +| 6.3.4B Reference point MCVideo-6 (between the MCVideo server and the EPS) ..... | 19 | +| 6.3.5 Reference point MCVideo-7 (between the media distribution function and the media mixer) ..... | 19 | +| 6.3.6 Reference point MCVideo-8 (between the media distribution function and the media mixer) ..... | 19 | +| 6.3.7 Reference point MCVideo-9 (between the transmission control participant and the transmission control server)..... | 19 | +| 6.3.8 Reference point MCVideo-10 (between the MC gateway server and the MC gateway server in a different MCVideo system)..... | 19 | + +| | | | +|-------------|---------------------------------------------------------------------|----| +| 6A | Identities..... | 20 | +| 6B | Application of functional model to deployments..... | 20 | +| 7 | Procedures and information flows ..... | 20 | +| 7.1 | Group call..... | 20 | +| 7.1.1 | General ..... | 20 | +| 7.1.2 | On-network group call..... | 20 | +| 7.1.2.1 | General..... | 20 | +| 7.1.2.2 | Information flows for group call in on-network ..... | 20 | +| 7.1.2.2.1 | Group call request (MCVideo client – MCVideo server)..... | 20 | +| 7.1.2.2.2 | Group call request (MCVideo server – MCVideo client)..... | 21 | +| 7.1.2.2.3 | Group call response (MCVideo server – MCVideo client)..... | 21 | +| 7.1.2.2.4 | Group call response (MCVideo client – MCVideo server)..... | 21 | +| 7.1.2.2.5 | Group call release request (MCVideo server – MCVideo client)..... | 22 | +| 7.1.2.2.6 | Group call release request (MCVideo client – MCVideo server)..... | 22 | +| 7.1.2.2.7 | Group call release response (MCVideo client – MCVideo server) ..... | 22 | +| 7.1.2.2.8 | Group call rejoin request (MCVideo client – MCVideo server)..... | 22 | +| 7.1.2.2.9 | Group call rejoin response (MCVideo server – MCVideo client) ..... | 23 | +| 7.1.2.2.10 | Group call join request (MCVideo client – MCVideo server)..... | 23 | +| 7.1.2.2.11 | Group call join response (MCVideo server – MCVideo client) ..... | 23 | +| 7.1.2.2.12 | Group call leave request (MCVideo server – MCVideo client)..... | 24 | +| 7.1.2.2.13 | Group call leave response (MCVideo client – MCVideo server)..... | 24 | +| 7.1.2.2.14 | MCVideo emergency alert request..... | 24 | +| 7.1.2.2.15 | MCVideo emergency alert response ..... | 25 | +| 7.1.2.2.16 | MCVideo emergency alert cancel request ..... | 25 | +| 7.1.2.2.17 | MCVideo emergency alert cancel response ..... | 25 | +| 7.1.2.2.18 | MCVideo emergency group call request..... | 26 | +| 7.1.2.2.19 | MCVideo emergency group call response ..... | 26 | +| 7.1.2.2.20 | MCVideo in-progress emergency group state cancel request..... | 26 | +| 7.1.2.2.21 | MCVideo in-progress emergency group state cancel response ..... | 27 | +| 7.1.2.2.22 | MCVideo imminent peril group call request..... | 27 | +| 7.1.2.2.23 | MCVideo imminent peril group call response..... | 27 | +| 7.1.2.2.24 | MCVideo imminent peril group call cancel request ..... | 28 | +| 7.1.2.2.25 | MCVideo imminent peril group call cancel response..... | 28 | +| 7.1.2.3 | Group call within one MC system ..... | 28 | +| 7.1.2.3.1 | Group call models ..... | 28 | +| 7.1.2.3.1.1 | Pre-arranged group call ..... | 28 | +| 7.1.2.3.1.2 | Chat group call ..... | 33 | +| 7.1.2.3.2 | Exiting group call due to de-affiliation ..... | 37 | +| 7.1.2.4 | Broadcast group call ..... | 38 | +| 7.1.2.4.1 | General ..... | 38 | +| 7.1.2.4.2 | Common broadcast group call procedure..... | 38 | +| 7.1.2.5 | Emergency and imminent peril procedures ..... | 39 | +| 7.1.2.5.1 | MCVideo emergency group call ..... | 39 | +| 7.1.2.5.1.1 | MCVideo emergency group call commencement ..... | 39 | +| 7.1.2.5.1.2 | MCVideo group call upgraded to an MCVideo emergency group call..... | 41 | +| 7.1.2.5.1.3 | MCVideo in-progress emergency group state cancel..... | 43 | +| 7.1.2.5.2 | MCVideo imminent peril group call ..... | 45 | +| 7.1.2.5.2.1 | MCVideo imminent peril group call commencement ..... | 45 | +| 7.1.2.5.2.2 | Imminent peril group call upgrade ..... | 47 | +| 7.1.2.5.2.3 | MCVideo imminent peril group call cancel ..... | 49 | +| 7.1.2.6 | MCVideo emergency alert..... | 50 | +| 7.1.2.6.1 | General ..... | 50 | +| 7.1.3 | Off-network group communications ..... | 50 | +| 7.1.3.1 | General..... | 50 | +| 7.1.3.2 | Information flows for off-network group communications ..... | 50 | +| 7.1.3.2.1 | Group communication announcement ..... | 50 | +| 7.1.3.2.2 | Group communication answer response ..... | 51 | +| 7.1.3.2.3 | MCVideo upgrade to emergency group communication ..... | 51 | +| 7.1.3.2.4 | MCVideo emergency group communication cancel..... | 52 | +| 7.1.3.2.5 | MCVideo upgrade to imminent peril group communication ..... | 52 | + +| | | | +|-------------|---------------------------------------------------------------------------------|----| +| 7.1.3.2.6 | MCVideo imminent peril group communication cancel..... | 52 | +| 7.1.3.2.7 | MCVideo emergency alert announcement..... | 52 | +| 7.1.3.2.8 | MCVideo emergency alert cancel announcement..... | 53 | +| 7.1.3.3 | Group communication setup..... | 53 | +| 7.1.3.3.1 | General ..... | 53 | +| 7.1.3.3.2 | Procedure..... | 53 | +| 7.1.3.4 | Passive join to group communication..... | 55 | +| 7.1.3.4.1 | General ..... | 55 | +| 7.1.3.4.2 | Procedure..... | 55 | +| 7.1.3.5 | Active join to group communication ..... | 56 | +| 7.1.3.5.1 | General ..... | 56 | +| 7.1.3.5.2 | Procedure..... | 56 | +| 7.1.3.6 | Broadcast group communication ..... | 57 | +| 7.1.3.7 | Group communication release due to inactivity ..... | 58 | +| 7.1.3.8 | Emergency and imminent peril procedures ..... | 58 | +| 7.1.3.8.1 | Emergency group communication ..... | 58 | +| 7.1.3.8.2 | MCVideo imminent peril ..... | 59 | +| 7.1.3.9 | MCVideo emergency alert..... | 60 | +| 7.1.3.9.1 | General ..... | 60 | +| 7.2 | Private call..... | 60 | +| 7.2.1 | General ..... | 60 | +| 7.2.2 | Private call on-network..... | 60 | +| 7.2.2.1 | General..... | 60 | +| 7.2.2.2 | Information flows for private call in on-network ..... | 60 | +| 7.2.2.2.1 | MCVideo private call request (MCVideo client – MCVideo server) ..... | 60 | +| 7.2.2.2.2 | MCVideo private call request (MCVideo server – MCVideo client)..... | 61 | +| 7.2.2.2.3 | MCVideo private call response (MCVideo client – MCVideo server)..... | 61 | +| 7.2.2.2.4 | MCVideo private call response (MCVideo server – MCVideo client)..... | 62 | +| 7.2.2.2.5 | MCVideo call end request..... | 62 | +| 7.2.2.2.6 | MCVideo emergency private call request (MCVideo client to MCVideo server) ..... | 62 | +| 7.2.2.2.7 | MCVideo emergency private call request (MCVideo server to MCVideo client) ..... | 63 | +| 7.2.2.2.8 | Emergency MCVideo private call response (MCVideo client – MCVideo server) ..... | 63 | +| 7.2.2.2.9 | Emergency MCVideo private call response (MCVideo server – MCVideo client) ..... | 64 | +| 7.2.2.3 | Private call within one MC system..... | 64 | +| 7.2.2.3.1 | Private call setup in automatic commencement mode ..... | 64 | +| 7.2.2.3.2 | Private call setup in manual commencement mode ..... | 66 | +| 7.2.2.3.2.1 | Description ..... | 66 | +| 7.2.2.3.2.2 | Procedure..... | 66 | +| 7.2.2.3.3 | Private call release..... | 67 | +| 7.2.2.3.3.1 | Client initiated ..... | 67 | +| 7.2.2.3.3.2 | Server initiated..... | 68 | +| 7.2.2.4 | MCVideo emergency private call..... | 69 | +| 7.2.2.4.1 | MCVideo emergency private call commencement ..... | 69 | +| 7.2.2.4.2 | MCVideo private call emergency upgrade..... | 71 | +| 7.2.3 | Off-network private communications..... | 72 | +| 7.2.3.1 | General..... | 72 | +| 7.2.3.2 | Information flows for off-network private communications ..... | 72 | +| 7.2.3.2.1 | Private communication request..... | 72 | +| 7.2.3.2.2 | Private communication answer response ..... | 72 | +| 7.2.3.2.3 | Private communication release request..... | 73 | +| 7.2.3.2.4 | Private communication release response..... | 73 | +| 7.2.3.3 | Use of ProSe for off-network private communications ..... | 73 | +| 7.2.3.4 | Automatic commencement private communication ..... | 74 | +| 7.2.3.4.1 | General ..... | 74 | +| 7.2.3.4.2 | Procedure..... | 74 | +| 7.2.3.5 | Manual commencement private communication..... | 76 | +| 7.2.3.5.1 | General ..... | 76 | +| 7.2.3.5.2 | Procedure – Communication accepted..... | 76 | +| 7.2.3.5.3 | Procedure – Communication rejected/ignored..... | 78 | +| 7.2.3.6 | Private communication release ..... | 79 | +| 7.2.3.6.1 | General ..... | 79 | +| 7.2.3.6.2 | Procedure..... | 79 | + +| | | | +|-----------|-------------------------------------------------------------------------------|-----| +| 7.3 | Video pull..... | 80 | +| 7.3.1 | General ..... | 80 | +| 7.3.2 | On-network video pull..... | 80 | +| 7.3.2.1 | General..... | 80 | +| 7.3.2.2 | Information flows for on-network video pull ..... | 80 | +| 7.3.2.2.1 | MCVideo pull from server request..... | 81 | +| 7.3.2.2.2 | MCVideo pull from server response ..... | 81 | +| 7.3.2.2.3 | MCVideo pull from server complete request..... | 81 | +| 7.3.2.2.4 | MCVideo pull from server complete response ..... | 81 | +| 7.3.2.3 | One-to-one video pull ..... | 82 | +| 7.3.2.3.1 | General ..... | 82 | +| 7.3.2.3.2 | One-to-one video pull – call setup ..... | 82 | +| 7.3.2.3.3 | One-to-one video pull – call release..... | 83 | +| 7.3.2.4 | One-from-server video pull ..... | 83 | +| 7.3.2.4.1 | General ..... | 83 | +| 7.3.2.4.2 | Procedure..... | 83 | +| 7.3.3 | Off-network video pull ..... | 84 | +| 7.3.3.1 | General..... | 84 | +| 7.3.3.2 | Information flows for off-network video pull..... | 85 | +| 7.3.3.3 | Video pull to self..... | 85 | +| 7.3.3.3.1 | General ..... | 85 | +| 7.3.3.3.2 | Procedure..... | 85 | +| 7.4 | Video push..... | 87 | +| 7.4.1 | General ..... | 87 | +| 7.4.2 | On-network video push ..... | 87 | +| 7.4.2.1 | General..... | 87 | +| 7.4.2.2 | Information flows for on-network video push..... | 87 | +| 7.4.2.2.1 | Remote video push request ..... | 87 | +| 7.4.2.2.2 | Remote video push response..... | 88 | +| 7.4.2.2.3 | Remote video push release request ..... | 88 | +| 7.4.2.2.4 | MCVideo push to server request..... | 89 | +| 7.4.2.2.5 | MCVideo push to server response ..... | 89 | +| 7.4.2.2.6 | MCVideo push to server complete request ..... | 89 | +| 7.4.2.2.7 | MCVideo push to server complete response..... | 90 | +| 7.4.2.3 | One-to-one video push..... | 90 | +| 7.4.2.3.1 | General ..... | 90 | +| 7.4.2.3.2 | One-to-one video push – call setup..... | 90 | +| 7.4.2.3.3 | One-to-one video push – call release ..... | 91 | +| 7.4.2.4 | One-to-server video push..... | 91 | +| 7.4.2.4.1 | General ..... | 91 | +| 7.4.2.4.2 | Procedure..... | 91 | +| 7.4.2.5 | Remotely initiated video push ..... | 93 | +| 7.4.2.5.1 | General ..... | 93 | +| 7.4.2.5.2 | Remotely initiated video push – call setup..... | 93 | +| 7.4.2.5.3 | Remotely initiated video push – call release by authorized user ..... | 94 | +| 7.4.2.6 | Remotely initiated video push to group..... | 95 | +| 7.4.2.6.1 | General ..... | 95 | +| 7.4.2.6.2 | Remotely initiated video push to group – call setup..... | 95 | +| 7.4.2.6.3 | Remotely initiated video push to group – call release by authorized user..... | 96 | +| 7.4.3 | Off-network video push..... | 97 | +| 7.4.3.1 | General..... | 97 | +| 7.4.3.2 | Information flows for off-network video push ..... | 97 | +| 7.4.3.2.1 | Remote video push request ..... | 97 | +| 7.4.3.2.2 | Video push trying response..... | 97 | +| 7.4.3.2.3 | Notification of video push..... | 97 | +| 7.4.3.3 | Video push to another MCVideo user ..... | 98 | +| 7.4.3.3.1 | General ..... | 98 | +| 7.4.3.3.2 | Procedure..... | 98 | +| 7.4.3.4 | Remotely initiated video push ..... | 99 | +| 7.4.3.4.1 | General ..... | 99 | +| 7.4.3.4.2 | Procedure..... | 99 | +| 7.4.3.5 | Remotely initiated video push to a group ..... | 101 | + +| | | | +|-----------|--------------------------------------------------------------------------|-----| +| 7.4.3.5.1 | General ..... | 101 | +| 7.4.3.5.2 | Procedure..... | 101 | +| 7.5 | Capability information sharing..... | 102 | +| 7.5.1 | General ..... | 102 | +| 7.5.2 | On-network capability information sharing ..... | 102 | +| 7.5.2.1 | General..... | 102 | +| 7.5.2.2 | Information flows for on-network capability information sharing..... | 102 | +| 7.5.2.2.1 | Update MCVideo capabilities info request..... | 102 | +| 7.5.2.2.2 | Update MCVideo capabilities info response..... | 103 | +| 7.5.2.2.3 | Get MCVideo capabilities info request..... | 103 | +| 7.5.2.2.4 | Get MCVideo capabilities info response ..... | 103 | +| 7.5.2.2.5 | Subscribe MCVideo capabilities info request..... | 103 | +| 7.5.2.2.6 | Subscribe MCVideo capabilities info response ..... | 104 | +| 7.5.2.2.7 | Notify MCVideo capabilities info request ..... | 104 | +| 7.5.2.2.8 | Notify MCVideo capabilities info response..... | 104 | +| 7.5.2.3 | Update MCVideo capabilities information at the MCVideo server ..... | 104 | +| 7.5.2.4 | Retrieve MCVideo capabilities information by the MCVideo client..... | 105 | +| 7.5.2.5 | Subscription and notification for MCVideo capabilities information ..... | 105 | +| 7.5.3 | Off-network capability information sharing..... | 106 | +| 7.5.3.1 | General..... | 106 | +| 7.5.3.2 | Information flows for Off-network capability information sharing ..... | 107 | +| 7.5.3.2.1 | Capability request..... | 107 | +| 7.5.3.2.2 | Capability announcement..... | 107 | +| 7.5.3.2.3 | Activity status request..... | 107 | +| 7.5.3.2.4 | Activity status announcement ..... | 108 | +| 7.5.3.3 | Periodic capability announcements ..... | 108 | +| 7.5.3.3.1 | General ..... | 108 | +| 7.5.3.3.2 | Procedure..... | 108 | +| 7.5.3.4 | Request capabilities from client(s) ..... | 109 | +| 7.5.3.4.1 | General ..... | 109 | +| 7.5.3.4.2 | Request clients with particular capabilities..... | 109 | +| 7.5.3.4.3 | Request capabilities from a particular client ..... | 110 | +| 7.5.3.5 | Request activity status from client(s)..... | 111 | +| 7.5.3.5.1 | General ..... | 111 | +| 7.5.3.5.2 | Request activity status of group members..... | 111 | +| 7.5.3.5.3 | Request activity status from a particular client ..... | 112 | +| 7.6 | Ambient viewing call ..... | 113 | +| 7.6.1 | General ..... | 113 | +| 7.6.2 | Information flows for ambient viewing call ..... | 113 | +| 7.6.2.1 | Ambient viewing call request ..... | 113 | +| 7.6.2.2 | Ambient viewing call response..... | 114 | +| 7.6.2.3 | Ambient viewing call release request ..... | 114 | +| 7.6.2.4 | Ambient viewing call release response..... | 114 | +| 7.6.2.5 | Ambient viewing call release notification ..... | 115 | +| 7.6.3 | Procedures ..... | 115 | +| 7.6.3.1 | Remotely initiated ambient viewing call setup procedure..... | 115 | +| 7.6.3.2 | Locally initiated ambient viewing call setup procedure ..... | 116 | +| 7.6.3.3 | Ambient viewing call release – server initiated..... | 117 | +| 7.6.3.4 | Ambient viewing call release – "viewing" user initiated..... | 118 | +| 7.6.3.5 | Ambient viewing call release – "viewed to" user initiated..... | 119 | +| 7.7 | Transmission control..... | 120 | +| 7.7.1 | Transmission control for on-network MCVideo service..... | 120 | +| 7.7.1.1 | General..... | 120 | +| 7.7.1.2 | Information flows for transmission control for on-network ..... | 120 | +| 7.7.1.2.1 | General ..... | 120 | +| 7.7.1.2.2 | Transmit media request..... | 120 | +| 7.7.1.2.3 | Transmit media granted..... | 121 | +| 7.7.1.2.4 | Transmit media rejected..... | 121 | +| 7.7.1.2.5 | Media transmission notification ..... | 121 | +| 7.7.1.2.6 | Receive media request..... | 121 | +| 7.7.1.2.7 | Receive media response ..... | 122 | +| 7.7.1.2.8 | Media reception notification ..... | 122 | + +| | | | +|-------------|-----------------------------------------------------------------------------------------------|-----| +| 7.7.1.2.9 | Queue position info ..... | 122 | +| 7.7.1.2.10 | Transmission revoked ..... | 122 | +| 7.7.1.2.11 | Queue position request..... | 123 | +| 7.7.1.2.12 | Transmit media cancel request..... | 123 | +| 7.7.1.2.13 | Transmit media cancel response ..... | 123 | +| 7.7.1.2.14 | Transmit media cancel request notify ..... | 123 | +| 7.7.1.2.15 | Transmit media end request ..... | 124 | +| 7.7.1.2.16 | Transmit media end response..... | 124 | +| 7.7.1.2.17 | Remote transmit media request..... | 124 | +| 7.7.1.2.18 | Remote transmit media response..... | 124 | +| 7.7.1.2.19 | Remote transmit media end request ..... | 125 | +| 7.7.1.2.20 | Remote transmit media cancel response ..... | 125 | +| 7.7.1.2.21 | Media reception end request ..... | 125 | +| 7.7.1.2.22 | Media reception end response..... | 125 | +| 7.7.1.2.23 | Media reception override notification ..... | 126 | +| 7.7.1.2.24 | Transmit media end notify ..... | 126 | +| 7.7.1.3 | Transmission control within one MC system for MCVideo service ..... | 126 | +| 7.7.1.3.1 | Transmission control during an MCVideo session ..... | 126 | +| 7.7.1.3.2 | Reception control during an MCVideo session..... | 127 | +| 7.7.1.3.2A | End media reception – receiving user initiated ..... | 129 | +| 7.7.1.3.2B | End media reception – transmission control server initiated ..... | 129 | +| 7.7.1.3.2C | Reception control on overridden – mandatory mode ..... | 130 | +| 7.7.1.3.2D | Reception control on overridden – negotiated mode ..... | 131 | +| 7.7.1.3.3 | Transmission revoke during an MCVideo session..... | 132 | +| 7.7.1.3.4 | Queue position during an MCVideo session..... | 133 | +| 7.7.1.3.5 | Transmit media request cancellation from the video transmission queue ..... | 134 | +| 7.7.1.3.5.1 | Transmit media request cancellation from the queue – MCVideo user initiated ..... | 134 | +| 7.7.1.3.5.2 | Transmit media request cancellation from the queue - transmission control server initiated .. | 135 | +| 7.7.1.3.6 | End a media transmission during an MCVideo session..... | 136 | +| 7.7.1.3.6.1 | End a media transmission – MCVideo user initiated ..... | 136 | +| 7.7.1.3.6.2 | End a media transmission – transmission control server initiated..... | 137 | +| 7.7.1.3.6.3 | End a media transmission – remote MCVideo user initiated ..... | 138 | +| 7.7.1.3.7 | Remotely initiated media transmission during an MCVideo session ..... | 139 | +| 7.7.2 | Off-network transmission control..... | 140 | +| 7.7.2.1 | General..... | 140 | +| 7.7.2.2 | Information flows for off-network transmission control ..... | 140 | +| 7.7.2.2.1 | Transmission request..... | 140 | +| 7.7.2.2.2 | Transmission granted ..... | 141 | +| 7.7.2.2.3 | Transmission release ..... | 141 | +| 7.7.2.2.4 | Transmission rejected..... | 141 | +| 7.7.2.2.5 | Transmission revoked ..... | 141 | +| 7.7.2.2.6 | Transmission arbitration taken..... | 142 | +| 7.7.2.2.7 | Transmission arbitration release..... | 142 | +| 7.7.2.3 | Initializing transmission control – single arbitrator approach ..... | 142 | +| 7.7.2.3A | Initializing transmission control – self arbitration approach ..... | 143 | +| 7.7.2.4 | Transmission permission granted ..... | 144 | +| 7.7.2.5 | Transmission permission rejected..... | 145 | +| 7.7.2.6 | Releasing transmission permission..... | 146 | +| 7.7.2.7 | Transmission override..... | 147 | +| 7.7.2.8 | Transmission override (revoke self) ..... | 148 | +| 7.7.2.9 | Transmission arbitration release ..... | 150 | +| 7.7.2.9.1 | Transmission arbitration release..... | 150 | +| 7.7.2.9.2 | Transmission arbitration release with delegation..... | 150 | +| 7.7.2.10 | Simultaneous transmission requests ..... | 151 | +| 7.8 | MCVideo service configuration ..... | 152 | +| 7.9 | Affiliation and de-affiliation to/from MCVideo group(s)..... | 152 | +| 7.10 | Use of MBMS transmission (on-network)..... | 153 | +| 7.10.1 | Information flows for MBMS Transmission..... | 153 | +| 7.10.1.1 | General..... | 153 | +| 7.10.1.2 | MapGroupToBearer..... | 153 | +| 7.10.1.3 | UnmapGroupFromBearer ..... | 153 | +| 7.10.2 | Use of pre-established MBMS bearers..... | 154 | + +| | | | +|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------|------------| +| 7.10.3 | Use of dynamic MBMS bearer establishment..... | 154 | +| 7.10.4 | Video call connect and disconnect over MBMS ..... | 154 | +| 7.10.4.1 | General..... | 154 | +| 7.10.4.2 | Procedure ..... | 155 | +| 7.10.4.2.1 | Call connect over MBMS..... | 155 | +| 7.10.4.2.2 | Call disconnect over MBMS..... | 156 | +| 7.10.5 | Switching from MBMS bearer to unicast bearer..... | 157 | +| 7.11 | Simultaneous session for MCVideo calls (on-network) ..... | 157 | +| 7.12 | User authentication and authorization for MCVideo service..... | 157 | +| 7.13 | Support for multiple devices ..... | 158 | +| 7.14 | Location information (on-network)..... | 158 | +| 7.15 | MCVideo resource management (on-network)..... | 158 | +| 7.16 | MCVideo client query..... | 159 | +| 7.16.1 | General ..... | 159 | +| 7.16.2 | Information flows for MCVideo client query ..... | 159 | +| 7.16.2.1 | MCVideo client query request..... | 159 | +| 7.16.2.2 | MCVideo client query response ..... | 159 | +| 7.16.3 | MCVideo client query procedure ..... | 159 | +| 7.17 | MCVideo adaptation during MCVideo communication..... | 160 | +| 7.17.1 | General ..... | 160 | +| 7.17.2 | Information flows for MCVideo adaptation..... | 160 | +| 7.17.2.1 | MCVideo communication parameter update request ..... | 160 | +| 7.17.2.2 | MCVideo communication parameter update response..... | 161 | +| 7.17.3 | MCVideo adaptation procedure ..... | 161 | +| 7.17.3.1 | MCVideo adaptation during group communication procedure – transmitting client triggered ..... | 161 | +| 7.17.3.2 | MCVideo adaptation during group communication procedure – receiving user triggered ..... | 162 | +| 7.17.3.3 | MCVideo adaptation during private communication procedure – transmitting client triggered..... | 163 | +| 7.17.3.4 | MCVideo adaptation during group communication procedure – receiving user triggered ..... | 164 | +| <b>Annex A (normative): MCVideo related configuration data .....</b> | | <b>166</b> | +| A.1 | General..... | 166 | +| A.2 | MCVideo UE configuration data ..... | 167 | +| A.3 | MCVideo user profile configuration data ..... | 167 | +| A.4 | MCVideo related Group configuration data ..... | 172 | +| A.5 | MCVideo service configuration data ..... | 174 | +| <b>Annex B (informative): Change history .....</b> | | <b>176</b> | + +--- + +## Foreword + +This Technical Specification has been produced by the 3<sup>rd</sup> 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. + +--- + +# 1 Scope + +This document specifies the functional model, procedures and information flows needed for the mission critical video (MCVideo) service. Support for both MCVideo group streaming and MCVideo private streaming operating in on-network and off-network modes of operation is specified. + +The corresponding service requirements are defined in 3GPP TS 22.280 [2], and 3GPP TS 22.281 [3]. + +The present document is applicable primarily to mission critical video service using **E-UTRAN** access based on the common functional architecture for mission critical services defined in 3GPP TS 23.280 [6] and the **EPC** architecture defined in 3GPP **TS 23.401** [8]. + +The MCVideo service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways. + +--- + +# 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.280: "Mission Critical Common Requirements (MCCoRe); Stage 1". +- [3] 3GPP TS 22.281: "Mission Critical Video services". +- [4] 3GPP TS 23.002: "Network Architecture". +- [5] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [6] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2". +- [7] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2". +- [8] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [9] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE\_LTE); Stage 2". +- [10] Void +- [11] 3GPP TS 23.203: "Policy and charging control architecture". +- [12] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [13] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE\_LTE); MB2 reference point; Stage 3". +- [14] 3GPP TS 33.180: "Security of the mission critical service". + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**MCVideo client:** An instance of an MC service client that provides the client application function for the MCVideo service. + +**MCVideo group:** An MC service group configured for MCVideo service. + +**MCVideo group affiliation:** An MC service group affiliation for MCVideo. + +**MCVideo group de-affiliation:** An MC service group de-affiliation for MCVideo. + +**MCVideo group home system:** The mission critical system where the MCVideo group is defined. + +**MCVideo group host server:** The MCVideo server within a mission critical system which provides centralised support for MCVideo services of an MCVideo group defined in a MCVideo group home system. + +**MCVideo ID:** An instance of an MC service ID within the MCVideo service. + +**MCVideo server:** An instance of an MC service server that provides the server application function for the MCVideo service. + +**MCVideo service:** A video communication service supporting applications for mission critical organizations and mission critical applications for other businesses and organizations (e.g., utilities, railways) with strong security, high availability, reliability and priority handling. + +**MCVideo system:** The collection of applications, services, and enabling capabilities required to provide Mission Critical video for a Mission Critical Organization. + +**MCVideo UE:** An MC service UE that can be used to participate in MCVideo services. + +**MCVideo user:** An MC service user who is authorized for MCVideo services via an MCVideo UE. + +**Transmission control:** Video transmitting control mechanism in an MCVideo service that determines which participants have the authority to transmit video, and determines the onward downlink video transmission during a video call. + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.280 [2] apply: + +**Mission Critical** +**Mission Critical Applications** +**Mission Critical Service** +**Mission Critical Organization** +**Mission Critical System** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.281 [3] apply: + +**Real Time** +**Real Time Video** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.280 [6] apply: + +**MC service client** +**MC service group** +**MC service group affiliation** +**MC service group de-affiliation** +**MC service group home system** + +**MC service group host** +**MC service ID** +**MC service server** + +## 3.2 Symbols + +For the purposes of the present document, the following symbols given in 3GPP TS 22.280 [2] apply: + +**Nc2** + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|------------------|----------------------------------------------------| +| E-UTRAN | Evolved Universal Terrestrial Radio Access Network | +| EPC | Evolved Packet Core | +| GCS AS | Group Communication Service Application Server | +| GCSE_LTE | Group Communication Service Enabler over LTE | +| HTTP | Hyper Text Transfer Protocol | +| IMS | IP Multimedia Subsystem | +| MC | Mission Critical | +| MCVideo | Mission Critical Video | +| MCVideo group ID | MCVideo group identity | +| MCVideo ID | MCVideo user identity | +| ProSe | Proximity-based Services | +| SIP | Session Initiated Protocol | + +--- + +## 4 Introduction + +The MCVideo service supports video media communication between several users (i.e. group call), where each user has the ability to gain access to the permission to stream video in an arbitrated manner. The MCVideo service also supports private calls between two users. + +The MCVideo architecture is based on the functional architecture for mission critical communication services defined in 3GPP TS 23.280 [6]. + +--- + +## 5 Architectural requirements + +### 5.1 Media routing requirements + +The video media flow for a private call shall be routed according to one of the following two options: + +- a) Option 1: + - 1) Through the primary MCVideo system if both users in the call belong to the same organisation; or + - 2) Through the primary MCVideo system of each users, if the users in the call do not belong to the same organisation. +- b) Option 2: The video media flow may be routed locally, under the control of the primary MCVideo system, through an entity allowing the duplication of the media flow to the primary MCVideo system of each user. + +The video media flow for a group call shall be routed to the group home MCVideo system. + +### 5.2 MCVideo group affiliation and MCVideo group de-affiliation + +MCVideo group affiliation shall be as specified in clause 5.2.5 of 3GPP TS 23.280 [6]. In addition, the following requirements shall be fulfilled by the MCVideo service for MCVideo users affiliated to MCVideo groups: + +- MCVideo users receive notifications for MCVideo group call setup and invitations for their affiliated MCVideo group(s). +- MCVideo users select an affiliated MCVideo group to initiate a new group MCVideo call or transmit media in an existing MCVideo group call. +- MCVideo users receive media and events from their affiliated MCVideo group(s). + +## 5.3 Device inventory requirements + +The MCVideo service shall provide device inventory capabilities for MCVideo UEs. The device inventory capabilities shall include: + +- device information registration; +- device information storage; and +- device information query. + +## 5.4 Device discovery requirements (off-network) + +The MCVideo service shall provide device discovery for devices as requested by the MCVideo user according to the MC service provider policy for off-network operations. + +## 5.5 Bearer management + +### 5.5.1 General + +The MCVideo UE shall use the **APNs** as defined in subclause 5.2.7.0 of 3GPP TS 23.280 [6]. The MCVideo UE shall use the MC services **APN** as defined in subclause 5.2.7.0 of 3GPP TS 23.280 [6] for the SIP-1 reference point. + +### 5.5.2 **EPS** bearer considerations + +The **EPS** bearer considerations specified in subclause 5.2.7.2 of 3GPP TS 23.280 [6] shall apply. + +### 5.5.3 **EPS** unicast bearer considerations for MCVideo + +For an MCVideo call session request, resources shall be requested utilising interaction with dynamic PCC. The MCVideo system shall request resources over Rx to a PCRF. The dedicated bearer(s) for video media and control of the video media (i.e. MCVideo-4 and MCVideo-7) shall utilise the **QCI** values depending on the MCVideo mode of the MCVideo call/session, as per table 5.5.3-1. The request of resources over Rx shall include an application identifier for MCVideo in order for the PCRF to evaluate the correct **QCI**. + +**Table 5.5.3-1: QCI values to use for EPS unicast bearers for each MCVideo mode** + +| MCVideo mode | QCI value utilised<br>(as specified in 3GPP<br>TS 23.203 [11]) | +|---------------------------|----------------------------------------------------------------| +| Urgent real-time mode | 2 | +| Non-urgent real-time mode | 2 | +| Non real-time mode | 4 | + +The UE is required to support at minimum one UM bearer, which is used for MCVideo (see annex A in 3GPP **TS 36.331** [12]). + +### 5.5.4 **MBMS** bearer management + +The **MBMS** bearer management for MC services is specified in subclause 5.2.7.1 of 3GPP TS 23.280 [6]. + +## 5A Involved business relationships + +The description of the involved business relationships for the MCVideo service is contained in clause 6 of 3GPP TS 23.280 [6]. + +## 6 MCVideo Functional model + +### 6.1 Functional model description + +#### 6.1.1 On-network functional model + +Figure 6.1.1-1 shows the functional model for the application plane of MCVideo service for on-network operations. + +![Functional model for application plane of MCVideo service. The diagram shows the MCVideo server (containing Media distribution function and Transmission control server) connected to various external entities and the MCVideo UE. External entities include Other MCVideo server, MCVideo user database, MC gateway server, and Other MCVideo system. The MCVideo UE contains MCVideo client, Media mixer, and Transmission control participant. Interfaces are labeled MCVideo-1 through MCVideo-10. MCVideo-3 connects Other MCVideo server and MC gateway server to the MCVideo server. MCVideo-2 connects MCVideo user database to the MCVideo server. MCVideo-10 connects MC gateway server to the Other MCVideo system. MCVideo-5, 6, 7, 8, 1, 4, and 9 connect the MCVideo server to the MCVideo UE. MCVideo-9 is specifically labeled as carrying signalling over multicast bearer, while MCVideo-4 carries signalling over unicast bearer. The EPS (Evolved Packet System) is shown as a vertical bar between the MCVideo server and the MCVideo UE.](a7c51c18111139f9aca2805114108565_img.jpg) + +Functional model for application plane of MCVideo service. The diagram shows the MCVideo server (containing Media distribution function and Transmission control server) connected to various external entities and the MCVideo UE. External entities include Other MCVideo server, MCVideo user database, MC gateway server, and Other MCVideo system. The MCVideo UE contains MCVideo client, Media mixer, and Transmission control participant. Interfaces are labeled MCVideo-1 through MCVideo-10. MCVideo-3 connects Other MCVideo server and MC gateway server to the MCVideo server. MCVideo-2 connects MCVideo user database to the MCVideo server. MCVideo-10 connects MC gateway server to the Other MCVideo system. MCVideo-5, 6, 7, 8, 1, 4, and 9 connect the MCVideo server to the MCVideo UE. MCVideo-9 is specifically labeled as carrying signalling over multicast bearer, while MCVideo-4 carries signalling over unicast bearer. The EPS (Evolved Packet System) is shown as a vertical bar between the MCVideo server and the MCVideo UE. + +**Figure 6.1.1-1: Functional model for application plane of MCVideo service** + +In the model shown in figure 6.1.1-1, the following apply: + +- The MCVideo server is an instantiation of a MC service server in accordance with 3GPP TS 23.280 [6]. +- The MCVideo server is an instantiation of a GCS AS in accordance with 3GPP **TS 23.468** [9]. +- MCVideo-9 carries signalling over multicast bearer between the transmission control server of the MCVideo server and the transmission control participant of the MCVideo UE. +- MCVideo-4 carries signalling over unicast bearer between the transmission control server of the MCVideo server and the transmission control participant of the MCVideo UE. + +#### 6.1.2 Off-network functional model + +Figure 6.1.2-1 shows the functional model for the application plane of MCVideo service for off-network operations. + +![Figure 6.1.2-1: Functional model for application plane of off-network MCVideo service. The diagram shows two User Equipment (UE) blocks, UE 1 and UE 2, connected by Media (green line) and Signalling (red line) paths. Each UE contains a Signalling control plane with a Signalling user agent, an Application plane with a Common services core (Configuration management client and Group management client), and an MCVideo client (Media mixer, Transmission control participant, and Transmission control server).](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +The diagram illustrates the functional model for the application plane of an off-network MCVideo service across two User Equipment (UE) units, UE 1 and UE 2. Each UE is structured into three main planes: + +- Signalling control plane:** Contains a **Signalling user agent**. +- Application plane:** Contains a **Common services core** (dashed box) which includes a **Configuration management client** and a **Group management client**. Above this is the **MCVideo client**, which consists of a **Media mixer**, a **Transmission control participant**, and a **Transmission control server**. +- Media plane:** Represented by a green line connecting the **Media mixer** entities of UE 1 and UE 2. +- Signalling plane:** Represented by a red line connecting the **Signalling user agent** entities of UE 1 and UE 2. + +Figure 6.1.2-1: Functional model for application plane of off-network MCVideo service. The diagram shows two User Equipment (UE) blocks, UE 1 and UE 2, connected by Media (green line) and Signalling (red line) paths. Each UE contains a Signalling control plane with a Signalling user agent, an Application plane with a Common services core (Configuration management client and Group management client), and an MCVideo client (Media mixer, Transmission control participant, and Transmission control server). + +**Figure 6.1.2-1: Functional model for application plane of off-network MCVideo service** + +## 6.2 Functional entities description + +### 6.2.1 General + +Each subclause is a description of a functional entity and does not imply a physical entity. + +### 6.2.2 MCVideo service application plane + +#### 6.2.2.1 General + +Entities within the application plane of MCVideo service provide application control, media transmission control and distribution functions. + +#### 6.2.2.2 Common services core + +The description of the common services core entities are contained in common functional architecture for MC services over **LTE** in 3GPP TS 23.280 [6]. + +#### 6.2.2.3 MCVideo application service + +##### 6.2.2.3.1 MCVideo client + +The MCVideo client functional entity acts as the user agent for all MCVideo application transactions. + +The MCVideo client is responsible for remote device control. This functional entity is located in the UE for both on-network and off-network operations. + +##### 6.2.2.3.2 MCVideo server + +The MCVideo server functional entity provides centralised support for MCVideo services. + +All the MCVideo clients supporting users belonging to a single group are required to use the same MCVideo server for that group. An MCVideo client supporting a user involved in multiple groups can have relationships with multiple MCVideo servers. + +The MCVideo server is an instantiation of a MC service server in accordance with 3GPP TS 23.280 [6]. + +The MCVideo server functional entity represents a specific instantiation of the GCS AS described in 3GPP **TS 23.468** [9] to control multicast and unicast operations for group communications. + +The MCVideo server functional entity is supported by the SIP AS, HTTP client and HTTP server functional entities of the signalling control plane. + +This MCVideo server provides support for centralised media transmission control for on-network and distributed media transmission control for off-network operation. + +The MCVideo server is responsible for managing and providing the device information that can participate in MCVideo communications. The device information is further associated to MCVideo users to manage remote device control authorization. The device information is provisioned to the MCVideo server by the MCVideo service provider, mission critical organization and the MCVideo user. + +#### 6.2.2.3.3 Media distribution function + +The media distribution function is responsible for the distribution of media to MCVideo clients. By means of information provided by the MCVideo server (e.g. IP addresses, transport layer ports), it will provide the following functionality: + +- provide for the reception of uplink MCVideo UE media transmission by means of the MCVideo-7 reference point; +- storing the received media stream as MCVideo content files; +- replicate the media as needed for distribution to those participants using unicast transport; +- distribute downlink media to MCVideo UEs by IP unicast transmission to those participants utilizing unicast transport by means of the MCVideo-7 reference point; +- distribute downlink media to MCVideo UEs using multicast downlink transport of media for the call by means of the MCVideo-8 reference point; and +- provide a media mixing function where multiple media streams are combined into a single media stream for transmission to the MCVideo UE. + +NOTE 1: If media mixing function occurs within the media distribution function, it operates independently of the media mixer in the UE. + +NOTE 2: A media mixing function within the media distribution function is not possible where the media is end to end encrypted. + +#### 6.2.2.3.4 Media mixer + +This functional entity exists on the UE and provides support for sending and receiving one or multiple media streams. It also provides support for combining multiple media streams into one media stream through the enforcement of media policy information. It supports the storing of a media stream as MCVideo content files. + +#### 6.2.2.3.5 MCVideo user database + +This functional entity contains information of the MCVideo user profile associated with an MCVideo ID that is held by the MCVideo service provider at the application plane. The MCVideo user profile is determined by the mission critical organization, the MCVideo service provider, and potentially the MCVideo user. + +The MCVideo ID is a MC service ID as described in clause 8 of 3GPP TS 23.280 [6]. The MCVideo user profile is a MC service user profile as described in clause 10.1.4 of 3GPP TS 23.280 [6]. + +The MCVideo user profile can be co-located with other MC service user profiles and stored in a common MC service user database. + +#### 6.2.2.3.6 Transmission control server + +This functional entity provides support for centralised transmission control for on-network and distributed transmission control for off-network operation. It may schedule transmission requests according to uplink criteria from different transmission control participants, send an notification to all transmission control participants to allow them to receive the video according to downlink criteria if the transmission request is granted, and provide queuing in cases of contention. Transmission control applies to all MCVideo communications including group call and private call. For on-network operation, this functional entity is located with the MCVideo server. For off-network operation, this functional entity is located in the UE. + +### 6.2.2.3.7 Transmission control participant + +The transmission control participant functional entity is responsible for handling outgoing transmission requests and the incoming video stream invitations and notifications. This functional entity is located in the UE for both on-network and off-network operations. + +### 6.2.2.3.8 MC gateway server + +The MC gateway server provides support for MCVideo interconnection services with a partner MCVideo system in a different trust domain whilst providing topology hiding. It acts as a proxy for one or more MCVideo servers in the partner MCVideo system without needing to expose the MCVideo servers in the primary MCVideo system outside the trusted domain of the primary MCVideo system. It may be a role of the MCVideo server described in subclause 6.2.2.3.2 of the present document. + +The MC gateway server is responsible for relaying call control and floor control signalling messages, and media between MCVideo servers within the MCVideo system and the interconnected MCVideo system. + +**Editor's note:** It is FFS whether the gateway MC server can act as a signalling proxy as defined in 3GPP TS 33.180 [14] + +## 6.3 Reference points + +### 6.3.1 Reference point MCVideo-1 (between the MCVideo client and the MCVideo server) + +The MCVideo-1 reference point, which exists between the MCVideo client and the MCVideo server, is used for MCVideo application signalling for establishing a session in support of MCVideo service. + +### 6.3.2 Reference point MCVideo-2 (between the MCVideo server and the MCVideo user database) + +The MCVideo-2 reference point, which exists between the MCVideo server and the MCVideo user database, is used by the MCVideo server to obtain information about a specific user. + +### 6.3.3 Reference point MCVideo-3 (between the MCVideo server and the MCVideo server and between the MCVideo server and the MC gateway server) + +The MCVideo-3 reference point exists between the MCVideo server and another MCVideo server and between the MCVideo server and the MC gateway server, and is used for MCVideo application signalling. + +### 6.3.4 Reference point MCVideo-4 (between the transmission control participant and the transmission control server) + +The MCVideo-4 reference point, which exists between the transmission control participant and the transmission control server, is used for MCVideo transmission control signalling over unicast. The MCVideo-4 reference point uses the SGi reference point defined in 3GPP TS 23.002 [4]. + +### 6.3.4A Reference point MCVideo-5 (unicast between the media distribution function and the EPS) + +The MCVideo-5 reference point, which exists between the media distribution function and the EPS, is used, subject to the conditions below, by the media distribution function of the MCVideo server to obtain unicast bearers with appropriate QoS from the EPS. It utilises the Rx interface of the EPS according to 3GPP TS 23.203 [11]. + +MCVideo-5 is not used when the MCVideo service provider and the PLMN operator do not have an operational agreement for QoS control to be provided directly from the MCVideo service provider domain. + +MCVideo-5 may be used when the MCVideo service provider and the PLMN operator have an operational agreement where QoS control is provided directly from the MCVideo service provider domain. + +NOTE: Any coordination between the P-CSCF use of Rx and the MCVideo server use of Rx (via MCVideo-5) from the MCVideo service provider domain is not specified in this release of this specification. + +#### 6.3.4B Reference point MCVideo-6 (between the MCVideo server and the EPS) + +The MCVideo-6 reference point, which exists between the MCVideo server and the EPS, is used to request the allocation and activation of multicast transport resources for MCVideo application usage. The MCVideo-6 reference point uses the MB2-C interface as defined in 3GPP TS 29.468 [13]. + +#### 6.3.5 Reference point MCVideo-7 (between the media distribution function and the media mixer) + +The MCVideo-7 reference point, which exists between the media distribution function and the media mixer, is used to exchange unicast media between the media distribution function of the MCVideo server and the media mixer of the MCVideo client. The MCVideo-7 reference point uses the SGi reference point defined in 3GPP TS 23.002 [4]. + +#### 6.3.6 Reference point MCVideo-8 (between the media distribution function and the media mixer) + +The MCVideo-8 reference point, which exists between the media distribution function and the media mixer, is used by the media distribution function of the MCVideo server to send multicast media to the media mixer of the MCVideo client. The MCVideo-8 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [9]. + +#### 6.3.7 Reference point MCVideo-9 (between the transmission control participant and the transmission control server) + +The MCVideo-9 reference point, which exists between the transmission control participant and the transmission control server, is used MCVideo transmission control signalling over multicast. The MCVideo-9 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [9]. + +#### 6.3.8 Reference point MCVideo-10 (between the MC gateway server and the MC gateway server in a different MCVideo system) + +The MCVideo-10 reference point, which exists between the MC gateway server and the MC gateway server in an interconnected MCVideo system for MCVideo application signalling for establishing MCVideo sessions, shall use the SIP-3 reference point for transport and routing of signalling. Floor control signalling and media are also transferred using the MCVideo-10 reference point between interconnected MCVideo systems. + +--- + +## 6A Identities + +The MCVideo service specific identities (e.g. MCVideo ID, MCVideo group ID) are described in clause 8 of 3GPP TS 23.280 [6]. + +--- + +## 6B Application of functional model to deployments + +The application of the functional model to deployments, and description of various deployment scenarios for the MCVideo service, can be found in clause 9 of 3GPP TS 23.280 [6]. + +--- + +# 7 Procedures and information flows + +## 7.1 Group call + +### 7.1.1 General + +Group calls are enabled in both on-network and off-network. + +## 7.1.2 On-network group call + +### 7.1.2.1 General + +This subclause contains procedures for group call across a single and multiple MCVideo servers, and associated functions such as emergency call, broadcast call and others. + +Two variations of group call model are described in subclause 7.1.2.3, the pre-arranged group call and the chat group call. Each of the subsequent group call types in subclause 7.1.2.4 onwards are applicable to either call model. + +### 7.1.2.2 Information flows for group call in on-network + +#### 7.1.2.2.1 Group call request (MCVideo client – MCVideo server) + +Table 7.1.2.2.1-1 describes the information flow group call request from the MCVideo client to the MCVideo server. + +**Table 7.1.2.2.1-1: Group call request (MCVideo client – MCVideo server)** + +| Information Element | Status | Description | +|---------------------------------|--------|---------------------------------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| MCVideo group ID | M | The MCVideo group ID of the group on which the call is requested | +| SDP offer | M | Media parameters of MCVideo clients | +| Implicit transmit media request | O | When originating client requests the permission to transmit media, this element shall be included | +| Broadcast indicator | O | Indicates that the group call request is for a broadcast group call | + +#### 7.1.2.2.2 Group call request (MCVideo server – MCVideo client) + +Table 7.1.2.2.2-1 describes the information flow group call request from the MCVideo server to the MCVideo client. + +**Table 7.1.2.2.2-1: Group call request (MCVideo server – MCVideo client)** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| MCVideo group ID | M | The MCVideo group ID of the group on which the call is initiated | +| SDP offer | M | Media parameters of MCVideo server | +| Broadcast indicator | O | Indicates that the group call request is for a broadcast group call | + +#### 7.1.2.2.3 Group call response (MCVideo server – MCVideo client) + +Table 7.1.2.2.3-1 describes the information flow group call response from the MCVideo server to the MCVideo client. + +**Table 7.1.2.2.3-1: Group call response (MCVideo server – MCVideo client)** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| MCVideo group ID | M | The MCVideo group ID of the group on which the call is requested | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the group call request (success or failure) | + +#### 7.1.2.2.4 Group call response (MCVideo client – MCVideo server) + +Table 7.1.2.2.4-1 describes the information flow group call response from the MCVideo client to the MCVideo server. + +**Table 7.1.2.2.4-1: Group call response (MCVideo client – MCVideo server)** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the target MCVideo group member | +| MCVideo group ID | M | The MCVideo group ID of the group on which the call is initiated | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the group call request (success or failure) | + +#### 7.1.2.2.5 Group call release request (MCVideo server – MCVideo client) + +Table 7.1.2.2.5-1 describes the information flow group call release request from the MCVideo server to the MCVideo client. + +**Table 7.1.2.2.5-1: Group call release request (MCVideo server – MCVideo client)** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the MCVideo group member | +| MCVideo group ID | M | The MCVideo group ID of the group on which the call is released | + +#### 7.1.2.2.6 Group call release request (MCVideo client – MCVideo server) + +Table 7.1.2.2.6-1 describes the information flow group call release request from the MCVideo client to the MCVideo server. + +**Table 7.1.2.2.6-1: Group call release request (MCVideo client – MCVideo server)** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the MCVideo group member | +| MCVideo group ID | M | The MCVideo group ID of the group on which the call is released | + +#### 7.1.2.2.7 Group call release response (MCVideo client – MCVideo server) + +Table 7.1.2.2.7-1 describes the information flow group call release response from the MCVideo client to the MCVideo server. + +**Table 7.1.2.2.7-1: Group call release response (MCVideo client – MCVideo server)** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the MCVideo group member | +| MCVideo group ID | M | The MCVideo group ID of the group on which the call is released | + +#### 7.1.2.2.8 Group call rejoin request (MCVideo client – MCVideo server) + +Table 7.1.2.2.8-1 describes the information flow group call rejoin request from the MCVideo client to the MCVideo server. + +**Table 7.1.2.2.8-1: Group call rejoin request (MCVideo client – MCVideo server))** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the re-joining MCVideo group member | +| MCVideo group ID | M | The MCVideo group ID of the group on which the call is on-going | +| SDP offer | M | Media parameters of MCVideo client | + +#### 7.1.2.2.9 Group call rejoin response (MCVideo server – MCVideo client) + +Table 7.1.2.2.9-1 describes the information flow group call rejoin response from the MCVideo server to the MCVideo client. + +**Table 7.1.2.2.9-1: Group call rejoin response (MCVideo server – MCVideo client)** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the MCVideo group member rejoining the group call | +| MCVideo group ID | M | The MCVideo group ID of the group on which the call is on-going | +| SDP answer | M | Media parameters selected | + +#### 7.1.2.2.10 Group call join request (MCVideo client – MCVideo server) + +Table 7.1.2.2.10-1 describes the information flow group call join request from the MCVideo client to the MCVideo server. + +**Table 7.1.2.2.10-1: Group call join request (MCVideo client – MCVideo server)** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the MCVideo group member joining the group communications for the group | +| MCVideo group ID | M | The MCVideo group ID of the group to which the group communication is requested | +| SDP offer | M | Media parameters of MCVideo client | + +#### 7.1.2.2.11 Group call join response (MCVideo server – MCVideo client) + +Table 7.1.2.2.11-1 describes the information flow group call join response from the MCVideo server to the MCVideo client. + +**Table 7.1.2.2.11-1: Group call join response (MCVideo server – MCVideo client)** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the MCVideo group member joining the group communications for the group | +| MCVideo group ID | M | The MCVideo group ID of the group to which the group communication is requested | +| SDP answer | M | Media parameters selected | + +#### 7.1.2.2.12 Group call leave request (MCVideo server – MCVideo client) + +Table 7.1.2.2.12-1 describes the information flow group call leave request from the MCVideo server to the MCVideo client. + +**Table 7.1.2.2.12-1: Group call leave request (MCVideo server – MCVideo client)** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the MCVideo group member which has been de-affiliated | +| MCVideo group ID | M | The MCVideo group ID of the group on which the call is on-going | + +#### 7.1.2.2.13 Group call leave response (MCVideo client – MCVideo server) + +Table 7.1.2.2.13-1 describes the information flow group call leave response from the MCVideo client to the MCVideo server. + +**Table 7.1.2.2.13-1: Group call leave response (MCVideo client – MCVideo server)** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the MCVideo group member which has been de-affiliated | +| MCVideo group ID | M | The MCVideo group ID of the group on which the call is on-going | + +#### 7.1.2.2.14 MCVideo emergency alert request + +Table 7.1.2.2.14-1 describes the information flow MCVideo emergency alert request from the MCVideo client to the MCVideo server, for the procedures defined in 3GPP TS 23.280 [6]. + +**Table 7.1.2.2.14-1: MCVideo emergency alert request (MCVideo client – MCVideo server)** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------| +| MCVideo ID | M | The identity of the alerting party | +| MCVideo group ID | M | The MCVideo group ID with which the alert is associated | +| Location | O | The alerting MCVideo client's location | + +Table 7.1.2.2.14-2 describes the information flow MCVideo emergency alert request from the MCVideo server to the MCVideo client, for the procedures defined in 3GPP TS 23.280 [6]. + +**Table 7.1.2.2.14-2: MCVideo emergency alert request (MCVideo server – MCVideo client)** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCVideo ID | M | The identity of the alerting party | +| MCVideo group ID | M | The MCVideo group ID with which the alert is associated | +| Organization name | M | The alerting MCVideo user's mission critical organization name | +| Location | O | The alerting MCVideo client's location | + +#### 7.1.2.2.15 MCVideo emergency alert response + +Table 7.1.2.2.15-1 describes the information flow MCVideo emergency alert response from the MCVideo client to the MCVideo server and from the MCVideo server to the MCVideo client, for the procedures defined in 3GPP TS 23.280 [6]. + +**Table 7.1.2.2.15-1: MCVideo emergency alert response** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------| +| MCVideo ID | M | The identity of the alerting party | +| MCVideo group ID | M | The MCVideo group ID with which the alert is associated | + +#### 7.1.2.2.16 MCVideo emergency alert cancel request + +Table 7.1.2.2.16-1 describes the information flow MCVideo emergency alert cancel request from the MCVideo client to the MCVideo server and from the MCVideo server to the MCVideo client, for the procedures defined in 3GPP TS 23.280 [6]. + +**Table 7.1.2.2.16-1: MCVideo emergency alert cancel request** + +| Information Element | Status | Description | +|-------------------------------------------------------------------|--------|-----------------------------------------------------------------------| +| MCVideo ID | M | The identity of the cancelling party | +| MCVideo group ID | M | The MCVideo group ID with which the alert is associated | +| Client emergency alert cancel inform (NOTE) | O | Requests cancellation of the emergency alert of the cancelling party | +| Group in-progress emergency state cancel request (NOTE) | O | Requests cancellation of the in-progress emergency state of the group | +| NOTE: At least one of these information elements shall be present | | | + +#### 7.1.2.2.17 MCVideo emergency alert cancel response + +Table 7.1.2.2.17-1 describes the information flow MCVideo emergency alert cancel response from the MCVideo client to the MCVideo server and from the MCVideo server to the MCVideo client, for the procedures defined in 3GPP TS 23.280 [6]. + +**Table 7.1.2.2.17-1: MCVideo emergency alert cancel response** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------| +| MCVideo ID | M | The identity of the cancelling party | +| MCVideo group ID | M | The MCVideo group ID with which the alert is associated | + +#### 7.1.2.2.18 MCVideo emergency group call request + +Table 7.1.2.2.18-1 describes the information flow emergency group call request from the MCVideo client to the MCVideo server and from the MCVideo server to the MCVideo client. + +**Table 7.1.2.2.18-1: MCVideo emergency group call request** + +| Information Element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the calling party | +| MCVideo group ID | M | The MCVideo group ID on which the call is to be conducted | +| Emergency indicator | M | Indicates that the group call request is an MCVideo emergency call | +| Alert indicator | M | Indicates whether an emergency alert is to be sent | +| Implicit transmit media request (NOTE) | O | Indicates that the originating client requests the permission to transmit media. | +| NOTE: This element shall be included only when the originating client requests the the permission to transmit media. | | | + +#### 7.1.2.2.19 MCVideo emergency group call response + +Table 7.1.2.2.19-1 describes the information flow emergency group call response from the MCVideo client to the MCVideo server and from the MCVideo server to the MCVideo client. + +**Table 7.1.2.2.19-1: MCVideo emergency group call response** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the calling party | +| MCVideo group ID | M | The MCVideo group ID on which the call is to be conducted | +| Result | M | Result of the MCVideo emergency group call request (success or failure) | + +#### 7.1.2.2.20 MCVideo in-progress emergency group state cancel request + +Table 7.1.2.2.20-1 describes the information flow MCVideo in-progress emergency group state cancel request from the MCVideo client to the MCVideo server. + +NOTE: In Rel-14 and Rel-13 versions of this specification the name of this information flow is "MCVideo emergency group call cancel request". + +**Table 7.1.2.2.20-1: MCVideo in-progress emergency group state cancel request** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the cancelling party | +| MCVideo group ID | M | The MCVideo group ID on which the MCVideo in-progress emergency state is to be cancelled. | +| Alert indicator | O | Indicates whether the emergency alert of the cancelling party is to be cancelled | + +#### 7.1.2.2.21 MCVideo in-progress emergency group state cancel response + +Table 7.1.2.2.21-1 describes the information flow MCVideo in-progress emergency group state cancel response from the MCVideo server to the MCVideo client. + +NOTE: In Rel-14 and Rel-13 versions of this specification the name of this information flow is "MCVideo emergency group call cancel response". + +**Table 7.1.2.2.21-1: MCVideo in-progress emergency group state cancel response** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the cancelling party | +| MCVideo group ID | M | The MCVideo group ID on which the MCVideo in-progress emergency state is to be cancelled. | + +#### 7.1.2.2.22 MCVideo imminent peril group call request + +Table 7.1.2.2.22-1 describes the information flow MCVideo imminent peril group call request from the MCVideo client to the MCVideo server and from the MCVideo server to the MCVideo client. + +**Table 7.1.2.2.22-1: MCVideo imminent peril group call request** + +| Information Element | Status | Description | +|--------------------------|--------|-----------------------------------------------------------------| +| MCVideo ID | M | The identity of the calling party | +| MCVideo group ID | M | The MCVideo group ID on which the call is to be conducted | +| Imminent peril indicator | M | Indicates that the group call request is an imminent peril call | + +#### 7.1.2.2.23 MCVideo imminent peril group call response + +Table 7.1.2.2.23-1 describes the information flow MCVideo imminent peril group call response from the MCVideo client to the MCVideo server and from the MCVideo server to the MCVideo client. + +**Table 7.1.2.2.23-1: MCVideo imminent peril group call response** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the calling party | +| MCVideo group ID | M | The MCVideo group ID on which the call is to be conducted | +| Result | M | Result of the MCVideo imminent peril group call request (success or failure) | + +#### 7.1.2.2.24 MCVideo imminent peril group call cancel request + +Table 7.1.2.2.24-1 describes the information flow MCVideo imminent peril group call cancel request from the MCVideo client to the MCVideo server and from the MCVideo server to the MCVideo client. + +**Table 7.1.2.2.24-1: MCVideo imminent peril group call cancel request** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------| +| MCVideo ID | M | The identity of the cancelling party | +| MCVideo group ID | M | The MCVideo group ID on which the imminent peril is to be cancelled | + +#### 7.1.2.2.25 MCVideo imminent peril group call cancel response + +Table 7.1.2.2.25-1 describes the information flow MCVideo imminent peril group call cancel response from the MCVideo client to the MCVideo server and from the MCVideo server to the MCVideo client. + +**Table 7.1.2.2.25-1: MCVideo imminent peril group call cancel response** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------| +| MCVideo ID | M | The identity of the cancelling party | +| MCVideo group ID | M | The MCVideo group ID on which the imminent peril is to be cancelled | + +### 7.1.2.3 Group call within one MC system + +#### 7.1.2.3.1 Group call models + +##### 7.1.2.3.1.1 Pre-arranged group call + +###### 7.1.2.3.1.1.1 General + +A pre-arranged group call is initiated by one of the group members. The initiation of a pre-arranged group call results in all other affiliated group members being invited. + +###### 7.1.2.3.1.1.2 Pre-arranged group call setup + +The procedure enables the scenario where an MCVideo client is initiating an MCVideo group call with unicast signalling for communicating with the affiliated members of that group. + +Procedures in figure 7.1.2.3.1.1.2-1 are the signalling control plane procedures for the MCVideo client initiating establishment of an MCVideo group call with a pre-arranged group i.e., MCVideo users on client 1, client 2 and client 3 belong to the same group which is defined in the group management server. + +Pre-conditions: + +1. A pre-arranged group is an MCVideo group that is pre-defined with MCVideo group ID and member list in the group management server. All members of the group belong to the same MC system. +2. It is assumed that MCVideo users on MCVideo client 1, MCVideo client 2 and MCVideo client 3 are already registered for receiving MCVideo service and affiliated. + +![Sequence diagram for Pre-arranged group call setup. Lifelines: MCVideo client 1, MCVideo server, Group management server, MCVideo client 2, MCVideo client 3. The process involves initiating a group call, resolving the group ID, sending requests to members, receiving responses, notifying the initiator, and establishing the media plane.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant Group management server + participant MCVideo client 2 + participant MCVideo client 3 + + Note left of MCVideo client 1: 1. Initiate group call + MCVideo client 1->>MCVideo server: 2. Group call request + Note over MCVideo server: 3. Resolve group id + MCVideo server->>MCVideo client 2: 4a. Group call request + Note over MCVideo client 2: 4a. Notify group call + MCVideo server->>MCVideo client 3: 4b. Group call request + Note over MCVideo client 3: 4b. Notify group call + MCVideo client 2->>MCVideo server: 5a. Group call response + MCVideo client 3->>MCVideo server: 5b. Group call response + MCVideo server->>MCVideo client 1: 6. Group call response + MCVideo server-->>MCVideo client 1: 7. Group call notify + Note over all participants: 8. Media plane and transmission control establishment + +``` + +Sequence diagram for Pre-arranged group call setup. Lifelines: MCVideo client 1, MCVideo server, Group management server, MCVideo client 2, MCVideo client 3. The process involves initiating a group call, resolving the group ID, sending requests to members, receiving responses, notifying the initiator, and establishing the media plane. + +**Figure 7.1.2.3.1.1.2-1: Pre-arranged group call setup** + +1. User at MCVideo client 1 would like to initiate an MCVideo group call with a selected group (identified by MCVideo group ID). +2. MCVideo client 1 sends a group call request towards the MCVideo server via the SIP core, which hosts the group selected by the user and identified by MCVideo group ID. The group call request also contains the MCVideo group ID and an SDP offer containing the MCVideo client media parameters. If there is a transmit media request, then the group call request contains an indication for the implicit transmit media request. +3. MCVideo server checks whether the user of MCVideo client 1 is authorized to initiate a group call for the selected group. If authorized and the group call is ongoing for that MCVideo group ID, the MCVideo server adds the requesting MCVideo client 1 to the existing MCVideo group call and notifies the MCVideo client 1 that the MCVideo group call is already in progress. Otherwise, MCVideo server resolves the MCVideo group ID to determine the members of that group and their affiliation status, based on the information from the group management server. + +NOTE 1: MCVideo server can have already retrieved the user/group configuration data and locally cached. If the user/group configuration data is not locally cached on the MCVideo server then MCVideo server requests the user/group configuration data from the MCVideo user database/group management server. + +4. MCVideo server includes information that it communicates using MCVideo service, offers the same media parameters or a subset of the media parameters contained in the initial received request and sends the corresponding group call request via the SIP core towards the MCVideo clients of each of those affiliated group members. MCVideo users are notified about the incoming group call. The MCVideo server indicates whether acknowledgement is required for the call. +5. The receiving MCVideo clients accept the group call request, and a group call response is sent to the group host MCVideo server. This response may contain an acknowledgement. The conditions for sending acknowledgement may be based on configuration. + +6. MCVideo server sends the group call response including the selected media parameters to the MCVideo client 1 through the signalling path to inform about successful call establishment. + +NOTE 2: Step 6 can occur at any time following step 4b, and prior to step 7 depending on the conditions to proceed with the call. + +7. If the initiating MCVideo user requires the acknowledgement from affiliated MCVideo group members, and the required MCVideo group members do not acknowledge the call setup within a configured time (the "acknowledged call setup timeout"), then the MCVideo server may proceed with or abandon the call and then notify the initiating MCVideo user that the acknowledgements did not include all required members according to group policy. This notification may be sent to the initiating MCVideo user by the MCVideo server more than once during the call when MCVideo users join or leave the MCVideo group call. +8. MCVideo client 1, client 2 and client 3 have successfully established media plane and transmission control for communication. + +#### 7.1.2.3.1.1.3 Release pre-arranged group call + +The procedure enables the scenario where an MCVideo server initiates the termination of an ongoing MCVideo group call for all the participants of that group call, since at least one of the termination conditions are met e.g., last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCVideo group members are not present. + +NOTE: The procedure for MCVideo user leaving the group call is a different scenario and is not considered in this solution. + +Procedures in figure 7.1.2.3.1.1.3-1 are the signalling control plane procedures for the MCVideo server initiating termination of an ongoing MCVideo group call. + +![Sequence diagram for releasing a pre-arranged group call. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2, MCVideo client 3. The sequence starts with an ongoing group call, followed by a release request from the server, participant notification, release responses, and final resource release.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + participant MCVideo client 3 + + Note over all: 1.Group call ongoing between MCVideo client 1, client 2 and client 3 + Note over MCVideo server: 2.Release group call + Note over MCVideo server: 3. Determine group call participants and generate group call release + MCVideo server->>MCVideo client 1: 4a.Group call release request + MCVideo server->>MCVideo client 2: 4b.Group call release request + MCVideo server->>MCVideo client 3: 4c.Group call release request + MCVideo client 1->>MCVideo server: 6a.Group call release response + MCVideo client 2->>MCVideo server: 6b.Group call release response + MCVideo client 3->>MCVideo server: 6c.Group call release response + Note over MCVideo client 1: 5a.Notify user + Note over MCVideo client 2: 5b.Notify user + Note over MCVideo client 3: 5c.Notify user + Note over all: 7. Releasing transmission control and media plane resources associated with the group call + +``` + +Sequence diagram for releasing a pre-arranged group call. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2, MCVideo client 3. The sequence starts with an ongoing group call, followed by a release request from the server, participant notification, release responses, and final resource release. + +**Figure 7.1.2.3.1.1.3-1: Release pre-arranged group call** + +1. It is assumed that MCVideo users on MCVideo client 1, client 2 and client 3 are already part of the ongoing group call (e.g., as a result of pre-arranged group call setup). +2. MCVideo server would like to release the MCVideo group call which is ongoing e.g., last participant leaving, initiator leaving, or minimum number of affiliated group members are not present. +3. MCVideo server identifies the participants of the ongoing group call and generates group call release request to release ongoing session. +4. MCVideo server sends a group call release request via SIP core towards each participant of the ongoing group call. +5. MCVideo users are notified about the release of the group call. +6. MCVideo client(s) receiving group call release request, acknowledge towards the MCVideo server by sending a group call release response. +7. MCVideo client 1, client 2 and client 3 have successfully released the media transmission control and media plane resources associated with the group call that is terminated. + +#### 7.1.2.3.1.1.4 Late entry pre-arranged group call + +Procedures in figure 7.1.2.3.1.1.4-1 are the signalling control plane procedures for the MCVideo server requesting a newly affiliated member or a member coming back from out of coverage to join an ongoing MCVideo group call. + +Pre-conditions: + +1. MCVideo group is previously defined on the group management server with MCVideo users affiliated to that group. All members of the group belong to the same MC system. +2. It is assumed that MCVideo users on MCVideo client 2 to MCVideo client n are on an ongoing call. + +![Sequence diagram for Late entry pre-arranged group call. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2, MCVideo client n. The sequence shows: 1. MCVideo client 1 is newly affiliated or coming back from out of network coverage; 2. Group call request from server to client 1; 3. Notify user; 4. Group call response from client 1 to server; 5. MCVideo client 1 is added to ongoing group call; 6. Notification of video transmissions in the group call from server to client 1.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + participant MCVideo client n + + Note right of MCVideo server: 1. MCVideo client 1 is newly affiliated or coming back from out of network coverage + MCVideo server->>MCVideo client 1: 2. Group call request + MCVideo client 1->>MCVideo server: 3. Notify user + MCVideo client 1->>MCVideo server: 4. Group call response + Note over MCVideo client 1, MCVideo client n: 5. MCVideo client 1 is added to ongoing group call + MCVideo server->>MCVideo client 1: 6. Notification of video transmissions in the group call + +``` + +Sequence diagram for Late entry pre-arranged group call. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2, MCVideo client n. The sequence shows: 1. MCVideo client 1 is newly affiliated or coming back from out of network coverage; 2. Group call request from server to client 1; 3. Notify user; 4. Group call response from client 1 to server; 5. MCVideo client 1 is added to ongoing group call; 6. Notification of video transmissions in the group call from server to client 1. + +**Figure 7.1.2.3.1.1.4-1: Late entry pre-arranged group call** + +1. MCVideo server determines that MCVideo client 1 which is newly affiliated or coming back from out of coverage has to be invited to join an ongoing group call (late entry). +2. MCVideo server generates group call request including the information such as MCVideo service identifier (possible for the SIP core to route the request to the MCVideo server), MC service group ID of the group invited to join, offer one or more media types and sends towards the MCVideo client 1 via SIP core. +3. MCVideo user at MCVideo client 1 is notified about the incoming group call. +4. Upon MCVideo user at MCVideo client 1 accepting the incoming group call request, MCVideo client 1 sends the group call response including the selected media types to the MCVideo server through the signalling path. If the incoming group call request is rejected by the MCVideo client 1, the MCVideo server should not resend the group call request +5. MCVideo client 1 is successfully added to the ongoing group call and MCVideo users at MCVideo client 1 to MCVideo client n may be notified about the MCVIDEO client 1 joining the group call. +6. A notification with the information of media transmissions in the group call is sent to MCVideo client 1. + +#### 7.1.2.3.1.1.5 Rejoining call + +Procedures in figure 7.1.2.3.1.1.5-1 are the signalling control plane procedures for the MCVideo client to rejoin an ongoing MCVideo group call (e.g. coming back from out of coverage). + +Pre-condition: + +- It is assumed that MCVideo users on MCVideo client 2 to MCVideo client n are on an ongoing call. + +![Sequence diagram for 'Rejoin call' showing interactions between MCVideo client 1, MCVideo server, MCVideo client 2, and MCVideo client n. The steps are: 1. MCVideo client 1 sends a 'Group call rejoin request' to the server. 2. The server sends an 'Authorize' response. 3. The server sends a 'Group call rejoin response' to client 1. 4. A horizontal bar indicates that MCVideo client 1 is added to the ongoing group call. 5. The server sends a 'Notification of video transmissions in the group call' to client 1.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + participant MCVideo client n + Note left of MCVideo client 1: 1. Group call rejoin request + MCVideo client 1->>MCVideo server: 1. Group call rejoin request + Note right of MCVideo server: 2. Authorize + MCVideo server-->>MCVideo client 1: 3. Group call rejoin response + Note over MCVideo client 1, MCVideo client n: 4. MCVideo client 1 is added to ongoing group call + Note left of MCVideo client 1: 5. Notification of video transmissions in the group call + MCVideo server-->>MCVideo client 1: 5. Notification of video transmissions in the group call + +``` + +Sequence diagram for 'Rejoin call' showing interactions between MCVideo client 1, MCVideo server, MCVideo client 2, and MCVideo client n. The steps are: 1. MCVideo client 1 sends a 'Group call rejoin request' to the server. 2. The server sends an 'Authorize' response. 3. The server sends a 'Group call rejoin response' to client 1. 4. A horizontal bar indicates that MCVideo client 1 is added to the ongoing group call. 5. The server sends a 'Notification of video transmissions in the group call' to client 1. + +**Figure 7.1.2.3.1.1.5-1: Rejoin call** + +1. MCVideo client 1 has necessary information for rejoining an ongoing group call, then the MCVideo client 1 initiates group call rejoin request including the ongoing group call information. +2. MCVideo server checks whether the MCVideo client 1 can rejoin the ongoing call (e.g. based upon affiliation status). +3. MCVideo client 1 is informed that the group call rejoin is successful by sending a group call rejoin response. +4. MCVideo client 1 is successfully added to the ongoing group call and MCVideo users at MCVideo client 1 to MCVideo client n may be notified about the MCVideo client 1 joining the group call. +5. A notification with the information of media transmissions in the group call is sent to MCVideo client 1. + +#### 7.1.2.3.1.2 Chat group call + +##### 7.1.2.3.1.2.1 General + +In a chat group call model, the MCVideo user individually joins a group call without being explicitly invited by the MCVideo server. The establishment of a chat group call does not result in other group members being invited. + +Figure 7.1.2.3.1.2.2-1 describes the basic procedure for the MCVideo client initiating an MCVideo group call which uses the chat group call model. The chat group call model can be used to realize the video conferencing service where only users that have been configured as participants for the video conferencing are allowed to join the group communications for the given group. + +Chat group call join mechanism: + +- Each MCVideo client sends a group call join request when the MCVideo user wants to participate in the group communication for the group. (This message does not impact the MCVideo user's membership in the group; the MCVideo server will verify that the MCVideo user is an authorized member of the group.) +- The group call join request may include a transmit media request. It is assumed that the group call join request will be delivered from MCVideo client to MCVideo server using SIP. +- The group call join request is used to indicate to the MCVideo server that the MCVideo user associated with the given MCVideo client wishes to participate (begin to receive notifications for media transmissions) from the group. +- The group call join request may cause the MCVideo server to generate an implicit affiliation for the MCVideo user to the group, if the user is not already affiliated to the group. + +- The group call join request normally contains the information needed to negotiate media parameters between MCVideo server and MCVideo client for the group call. The group call join request can take the form of a SIP invite. + +Subsequent participation in a group call when the group is using the chat model: + +- Once an MCVideo client successfully joins a group call which is using the chat model, the MCVideo client connects to the media plane for the media transmission if the media transmission is currently ongoing. +- If the MCVideo group call is not currently ongoing (i.e.: when MCVideo clients on the group call are not sending or receiving media) then the newly joined MCVideo client will only have pre-established its media parameters for the call. +- If the newly joined MCVideo user wishes to transmit media to the affiliated users of the group using the chat model, then the MCVideo client using its associated transmission control participant would follow a normal transmission control procedure for transmitting the media. +- Subsequent group call media transmissions are controlled using transmission control signalling. +- The MCVideo server may tear down the media plane between successive group calls using the chat model, or the MCVideo server may allow the media plane to remain up between successive group calls using the chat model depending on resources. + +### 7.1.2.3.1.2.2 Chat group call setup + +MCVideo client 1, client 2, and client 3 are served by the home MCVideo service provider in figure 7.1.2.3.1.2.2-1. + +Pre-conditions: + +1. The MCVideo server may use the group call join request to generate an implicit affiliation (using the affiliation procedure for MCVideo) on behalf of the client that sends the MCVideo group call join request. +2. MCVideo user 2 and MCVideo user 3 have previously joined (affiliated) to the group call. MCVideo client 1, client 2, and client 3 are registered and all users (MCVideo user 1, user 2, and user 3) have been authenticated and authorized to use the MCVideo service. No call is currently in progress for the group. + +![Sequence diagram for MCVideo chat group call setup showing interactions between MCVideo client 1, MCVideo server, MCVideo client 2, and MCVideo client 3.](94acd33fcad85bb6f207a308f9b63191_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant S as MCVideo server + participant C2 as MCVideo client 2 + participant C3 as MCVideo client 3 + + C1->>S: 1a. Group call join request + Note over S: 1b. MCVideo server receives the group call join request. + S->>C1: 1c. Group call join response + Note over C1, C3: 2. MCVideo user 1 requests to transmit video causing the media plane to be established (if not pre-established). + C1<->C3: 3. Media plane signaling using transmission control + +``` + +Sequence diagram for MCVideo chat group call setup showing interactions between MCVideo client 1, MCVideo server, MCVideo client 2, and MCVideo client 3. + +**Figure 7.1.2.3.1.2.2-1: MCVideo chat group call** + +1. MCVideo user 1 indicates to join the group communication for the group. This may include a transmit media request. + +- 1a. MCVideo client 1 sends a group call join request with the MCVideo group ID of the desired group. It contains the MCVideo user's MCVideo ID and the MCVideo client media parameters. If there is a request for media transmission, then the group call join request contains an indication of the transmit media request. +- 1b. The MCVideo server receives the group call join request. MCVideo server generates an implicit affiliation (if the MCVideo user is not already affiliated to the group) and verifies that MCVideo user 1 is authorized to affiliate to the group by following the affiliation procedure for MCVideo. +- 1c. The MCVideo server replies with a group call join response indicating the acceptance of the group call join request and also returns the MCVideo server selected media parameters for the group call in the group call join response. +2. If MCVideo user 1 requests to transmit media by sending transmit media request to MCVideo server, the MCVideo server establishes the media plane (if not already established) for the call. +3. Transmission control will continue to be used by the transmission control participants associated with MCVideo client 1, MCVideo client 2 and MCVideo client 3 for the duration of the call. + +#### 7.1.2.3.1.2.3 Release chat group call + +The procedure describes the case where the MCVideo server releases an ongoing MCVideo group call for all the participants of that group call, since at least one of the conditions for release are met e.g. due to chat duration expiry, last participant leaving or initiator leaving. + +NOTE 1: The procedure for an MCVideo user leaving the group call is a different procedure. + +Procedures in figure 7.1.2.3.1.2.3-1 are the procedures for the MCVideo server initiating the release of an ongoing MCVideo group call. + +The following precondition applies: + +- A group call is ongoing between MCVideo clients 1, 2 and 3 + +![Sequence diagram for releasing a chat group call. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2, MCVideo client 3. The sequence starts with the server sending a '1.Release group call' message to client 1. The server then performs an internal step '2. Determine group call participants and generate group call release request'. Next, the server sends '3a.Group call release request' to client 1, '3b.Group call release request' to client 2, and '3c.Group call release request' to client 3. Clients 1, 2, and 3 each perform an internal 'Notify user' step (4a, 4b, 4c). Clients 2 and 3 then send '5b.Group call release response' and '5c.Group call release response' back to the server. Client 1 sends a '5a.Group call release response' to the server. Finally, all participants perform a common step '6. Release transmission control and media plane resources associated with the group call'.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + participant MCVideo client 3 + + Note right of MCVideo server: 1.Release group call + Note right of MCVideo server: 2. Determine group call participants and generate group call release request + MCVideo server->>MCVideo client 1: 3a.Group call release request + MCVideo server->>MCVideo client 2: 3b.Group call release request + MCVideo server->>MCVideo client 3: 3c.Group call release request + Note left of MCVideo client 1: 4a.Notify user + Note right of MCVideo client 2: 4b.Notify user + Note right of MCVideo client 3: 4c.Notify user + MCVideo client 2-->>MCVideo server: 5b.Group call release response + MCVideo client 3-->>MCVideo server: 5c.Group call release response + MCVideo client 1-->>MCVideo server: 5a.Group call release response + Note over MCVideo client 1, MCVideo client 3: 6. Release transmission control and media plane resources associated with the group call + +``` + +Sequence diagram for releasing a chat group call. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2, MCVideo client 3. The sequence starts with the server sending a '1.Release group call' message to client 1. The server then performs an internal step '2. Determine group call participants and generate group call release request'. Next, the server sends '3a.Group call release request' to client 1, '3b.Group call release request' to client 2, and '3c.Group call release request' to client 3. Clients 1, 2, and 3 each perform an internal 'Notify user' step (4a, 4b, 4c). Clients 2 and 3 then send '5b.Group call release response' and '5c.Group call release response' back to the server. Client 1 sends a '5a.Group call release response' to the server. Finally, all participants perform a common step '6. Release transmission control and media plane resources associated with the group call'. + +**Figure 7.1.2.3.1.2.3-1: Release chat group call** + +1. MCVideo server would like to release the MCVideo group call which is ongoing e.g., due to chat duration expiry, last participant leaving, or initiator leaving. +2. MCVideo server identifies the participants of the ongoing group call and generates group call release request to release the ongoing session. +3. MCVideo server sends a group call release request towards each participant of the ongoing group call. + +NOTE 2: The group call release request can also be sent over SIP signalling on the signalling plane. + +4. MCVideo users are notified about the release of the group call. +5. Optionally the MCVideo client(s) receiving group call release request, may send a group call release response to the MCVideo server. + +NOTE 3: The MCVideo client can send group call release response when the group call release request is sent using a unicast bearer. + +6. MCVideo client 1, client 2 and client 3 release the transmission control and media plane resources associated with the group call that is released. Successful release of the group call does not affect the status of affiliation of any of the clients. + +#### 7.1.2.3.1.2.4 Rejoin a chat group call + +Procedures in figure 7.1.2.3.1.2.4-1 are for the MCVideo server rejoining a MCVideo client coming back from out of coverage to rejoin an ongoing MCVideo group call using chat group call model. + +Pre-conditions: + +1. MCVideo group is previously defined on the group management server with MCVideo users affiliated to that group. All members of the group belong to the same MC system. +2. MCVideo users using MCVideo client 2 to MCVideo client n are in an ongoing MCVideo chat group call. + +![Sequence diagram illustrating the rejoin process for an ongoing group call. The diagram shows interactions between MCVideo client 1, MCVideo server, MCVideo client 2, and MCVideo client n. The process starts with a note that MCVideo client 1 is returning from out-of-coverage. The server sends a rejoin request to client 1, which notifies the user. Client 1 then sends a rejoin response. A horizontal bar indicates the successful rejoin. Finally, the server sends a notification of video transmissions to client 1.](fcbc3c31776721edc98ceb1944ec438f_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + participant MCVideo client n + + Note right of MCVideo server: 1. MCVideo client 1 is coming back from out of network coverage + MCVideo server->>MCVideo client 1: 2. Group call rejoin request + MCVideo client 1->>MCVideo server: 3. Notify user + MCVideo client 1->>MCVideo server: 4. Group call rejoin response + Note over MCVideo client 1, MCVideo client n: 5. MCVideo client 1 is rejoined to ongoing group call + MCVideo server->>MCVideo client 1: 6. Notification of video transmissions in the group call + +``` + +Sequence diagram illustrating the rejoin process for an ongoing group call. The diagram shows interactions between MCVideo client 1, MCVideo server, MCVideo client 2, and MCVideo client n. The process starts with a note that MCVideo client 1 is returning from out-of-coverage. The server sends a rejoin request to client 1, which notifies the user. Client 1 then sends a rejoin response. A horizontal bar indicates the successful rejoin. Finally, the server sends a notification of video transmissions to client 1. + +**Figure 7.1.2.3.1.2.4-1: Rejoin an on-going chat group call** + +1. MCVideo server determines that MCVideo client 1 requires to rejoin an on-going chat group call which has returned from being out of coverage. +2. MCVideo server sends group call rejoin request to MCVideo client 1. +3. MCVideo user at MCVideo client 1 is notified to rejoin an on-going chat group call. +4. Upon MCVideo client 1 accepting the group call rejoin request, MCVideo client 1 sends a group call rejoin response to the MCVideo server. +5. MCVideo client 1 is successfully rejoined the ongoing group call and MCVideo users at MCVideo client 1 to MCVideo client n may be notified about the MCVideo client 1 joining the group call. +6. Notification with the information of the media transmissions in the group call is sent to MCVideo client 1. + +### 7.1.2.3.2 Exiting group call due to de-affiliation + +Procedures in figure 7.1.2.3.2-1 are the signalling control plane procedures for the MCVideo server requesting a newly de-affiliated member to leave an ongoing MCVideo group call. + +Pre-conditions: + +1. MCVideo group is previously defined on the group management server with MCVideo users affiliated to that group. All members of the group belong to the same MC system. +2. MCVideo users on MCVideo client 1 to MCVideo client n are on an ongoing call. +3. MCVideo client 1 has been de-affiliated from the MCVideo group. + +![Sequence diagram illustrating the procedure for exiting an MCVideo group call due to de-affiliation. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2, MCVideo client n. The sequence starts with a note on MCVideo client 1 stating '1. MCVideo client 1 has been de-affiliated from the MCVideo group'. Then, the MCVideo server sends a '2. Group call leave request' to MCVideo client 1. MCVideo client 1 performs '3. Notify user', then sends a '4. Group call leave response' to the server. Finally, a note spanning all lifelines states '5. MCVideo client 1 is removed from the ongoing group call'.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + participant MCVideo client n + + Note right of MCVideo client 1: 1. MCVideo client 1 has been de-affiliated from the MCVideo group + MCVideo server->>MCVideo client 1: 2. Group call leave request + Note left of MCVideo client 1: 3. Notify user + MCVideo client 1->>MCVideo server: 4. Group call leave response + Note over MCVideo client 1, MCVideo server, MCVideo client 2, MCVideo client n: 5. MCVideo client 1 is removed from the ongoing group call + +``` + +Sequence diagram illustrating the procedure for exiting an MCVideo group call due to de-affiliation. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2, MCVideo client n. The sequence starts with a note on MCVideo client 1 stating '1. MCVideo client 1 has been de-affiliated from the MCVideo group'. Then, the MCVideo server sends a '2. Group call leave request' to MCVideo client 1. MCVideo client 1 performs '3. Notify user', then sends a '4. Group call leave response' to the server. Finally, a note spanning all lifelines states '5. MCVideo client 1 is removed from the ongoing group call'. + +**Figure 7.1.2.3.2-1: Exiting MCVideo group call due to de-affiliation** + +1. MCVideo client 1 which has been de-affiliated is instructed to leave the ongoing group call. +2. MCVideo server sends a group call leave request to MCVideo client 1. +3. MCVideo user at MCVideo client 1 is notified about leaving the group call. +4. MCVideo client 1 sends the group call leave response and leaves the group call. +5. MCVideo client 1 is now removed from the ongoing group call and MCVideo users at MCVideo client 2 to MCVideo client n may be notified that MCVideo client 1 has left the group call. + +## 7.1.2.4 Broadcast group call + +### 7.1.2.4.1 General + +A broadcast group call is a special group call where the initiating MCVideo user expects no response from the other MCVideo users, i.e. no response from the recipients is required to start media transmission and the call ends when the media transmission is complete. + +### 7.1.2.4.2 Common broadcast group call procedure + +Only the call originator can transmit media during the broadcast group call and the broadcast group call is released when the transmission is complete. + +Figure 7.1.2.4.2-1 illustrates the common procedure both for group-broadcast group call and user-broadcast group call. + +Pre-condition: + +1. MCVideo client 1 and MCVideo client 2 are members of a group-broadcast group/user-broadcast group. + +![Sequence diagram for Broadcast group call. Lifelines: MCVideo client 1, MCVideo server, and MCVideo client 2. The sequence is: 1. Broadcast group call setup (from client 1 to server and client 2), 2. Video transmission (from client 1 to server and client 2), 3. Broadcast group call release (from client 1 to server and client 2).](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + Note over MCVideo client 1, MCVideo server, MCVideo client 2: 1. Broadcast group call setup + Note over MCVideo client 1, MCVideo server, MCVideo client 2: 2. Video transmission + Note over MCVideo client 1, MCVideo server, MCVideo client 2: 3. Broadcast group call release + +``` + +Sequence diagram for Broadcast group call. Lifelines: MCVideo client 1, MCVideo server, and MCVideo client 2. The sequence is: 1. Broadcast group call setup (from client 1 to server and client 2), 2. Video transmission (from client 1 to server and client 2), 3. Broadcast group call release (from client 1 to server and client 2). + +**Figure 7.1.2.4.2-1: Broadcast group call** + +1. MCVideo user at MCVideo client 1 initiates the broadcast group call setup procedure with the indication of broadcast group call. The signalling procedure is identical to the group call setup as described in subclause 7.1.2.3.1.1 with the inclusion of the parameter for broadcast group call indicator. + +2. MCVideo client 1 starts to transmit media. + +NOTE 1: Only the call originating MCVideo user is allowed to transmit media on broadcast group call. + +NOTE 2: A broadcast group call transmitted on a user-broadcast group has priority over group calls involving users within the user hierarchy. A broadcast group call transmitted on a group-broadcast group has priority over group calls on its subordinate groups. + +3. If the media transmission from call originating MCVideo user is complete, the broadcast group call is released. + +## 7.1.2.5 Emergency and imminent peril procedures + +### 7.1.2.5.1 MCVideo emergency group call + +#### 7.1.2.5.1.1 MCVideo emergency group call commencement + +The procedure describes the case where an MCVideo client is initiating an MCVideo emergency group call with the affiliated MCVideo group members of that MCVideo group. An MCVideo client in the MCVideo emergency state gains elevated access privilege for all of the MCVideo user's mission critical applications. + +Procedures in figure 7.1.2.5.1.1-1 are the signalling control plane procedures for the MCVideo client initiating establishment of an MCVideo emergency group call with an MCVideo group i.e., MCVideo users on MCVideo client 1, MCVideo client 2 and MCVideo client 3 belong to the same MCVideo group which is defined on group management server. + +NOTE 1: For simplicity, a single MCVideo server is shown in place of a user home MCVideo server and a group hosting MCVideo server. + +Pre-conditions: + +1. The MCVideo group is previously defined on the group management server with MCVideo client 2 and MCVideo client 3 affiliated to that MCVideo group. +2. All members of the MCVideo group belong to the same MC system. +3. The initiating MCVideo client 1 has been provisioned with an MCVideo group that has been designated via provisioning as the MCVideo emergency group. + +NOTE 2: Alternatively, the client could have been provisioned for emergency behaviour on the selected group. + +![Sequence diagram for MCVideo emergency group call. Lifelines: MCVideo client 1, MCVideo server, Group management server, MCVideo client 2, MCVideo client 3. The sequence starts with client 1 initiating a call, followed by a request to the server, affiliation, group ID resolution, bearer configuration, and then the server notifying clients 2 and 3. A response is sent from client 2 back to client 1 via the server.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant Group management server + participant MCVideo client 2 + participant MCVideo client 3 + + Note left of MCVideo client 1: 1. initiate MCVideo emergency group call + MCVideo client 1->>MCVideo server: 2. MCVideo emergency group call request + Note right of MCVideo server: 3. Affiliate user to group + Note right of MCVideo server: 4. Resolve group id + Note right of MCVideo server: 5. Bearer priority configuration + MCVideo server->>MCVideo client 2: 6. MCVideo emergency group call request + MCVideo server->>MCVideo client 3: 6. MCVideo emergency group call request + Note right of MCVideo client 2: 7. Notify MCVideo emergency group call + Note right of MCVideo client 3: 7. Notify MCVideo emergency group call + MCVideo client 2-->>MCVideo server: 8. MCVideo emergency group call response + MCVideo server->>MCVideo client 1: 9. MCVideo emergency group call response + +``` + +Sequence diagram for MCVideo emergency group call. Lifelines: MCVideo client 1, MCVideo server, Group management server, MCVideo client 2, MCVideo client 3. The sequence starts with client 1 initiating a call, followed by a request to the server, affiliation, group ID resolution, bearer configuration, and then the server notifying clients 2 and 3. A response is sent from client 2 back to client 1 via the server. + +**Figure 7.1.2.5.1.1-1: MCVideo emergency group call** + +1. The user at the MCVideo client 1 initiates an MCVideo emergency group call. MCVideo client 1 sets its MCVideo emergency state. The MCVideo emergency state is retained until explicitly cancelled. + 2. MCVideo client 1 sends an MCVideo group call request towards the MCVideo server. The request contains an indication of the MCVideo emergency. The MCVideo server records the identity of the MCVideo user that initiated the MCVideo emergency group call until the MCVideo emergency is cancelled. Once an MCVideo emergency call has been initiated, the MCVideo group is considered to be in an in-progress emergency state until cancelled. If configured to send an MCVideo emergency alert when initiating an MCVideo emergency group call, the request also contains an indication that an MCVideo emergency alert is to be initiated. The request may contain an indication of an implicit transmit media request. + 3. The MCVideo server implicitly affiliates MCVideo client 1 to the emergency group if the client is not already affiliated. + 4. MCVideo server checks whether the MCVideo user of MCVideo client 1 is authorized for initiation of MCVideo emergency calls on the indicated MCVideo group, and if authorized, it resolves the MCVideo group ID to determine the members of that MCVideo group and their affiliation status, based on the information from group management server. + 5. The MCVideo server configures the priority of the underlying bearers for all participants in the MCVideo group. +- NOTE 3: Successive calls during the MCVideo group's in-progress emergency state will all receive the adjusted bearer priority. +6. MCVideo server sends the MCVideo emergency group call request towards the MCVideo clients of each of those affiliated MCVideo group members. The request contains an indication of the in-progress emergency. The + +request contains an indication of an MCVideo emergency alert if the request from the originator indicated MCVideo emergency alert. + +7. MCVideo users are notified of the incoming MCVideo group call. +8. The receiving MCVideo clients send the MCVideo emergency group call response to the MCVideo server to acknowledge the MCVideo emergency group call request. For a multicast call, these acknowledgements are not sent. +9. The MCVideo server sends the MCVideo emergency group call response to the MCVideo user 1 to inform the successful MCVideo emergency call establishment. + +NOTE 4: Step 9 can occur at any time following step 5, and prior to step 10 depending on the conditions to proceed with the call. + +MCVideo client 1, MCVideo client 2 and MCVideo client 3 have successfully established media plane for communication. MCVideo transmission control participant 1, transmission control participant 2 and transmission control participant 3 exchange transmission control information e.g., MCVideo client 1 receives the transmit media granted information over the established media plane, while the other MCVideo client's receive media available notification with forced reception information. MCVideo client 1 indicates to the MCVideo user that the permission is granted to transmit media, while the other MCVideo clients in the MCVideo emergency group call will be receiving that media. MCVideo client 1 can override other clients in the call except those that are also in the MCVideo emergency state. + +#### 7.1.2.5.1.2 MCVideo group call upgraded to an MCVideo emergency group call + +The procedure describes the case where an authorized MCVideo user is upgrading an MCVideo group call to an MCVideo emergency group call while the MCVideo group call is already in progress. + +Procedures in figure 7.1.2.5.1.2-1 are the signalling control plane procedures for the MCVideo client upgrading an MCVideo group call on an MCVideo group to an MCVideo emergency group call. + +NOTE 1: For simplicity, a single MCVideo server is shown in place of a user home MCVideo server and a group hosting MCVideo server. + +Pre-conditions: + +1. The MCVideo group is previously defined on the group management server with MCVideo client 2 and MCVideo client 3 affiliated to that MCVideo group. +2. All members of the MCVideo group belong to the same MC system. +3. An MCVideo group call is already in progress. +4. The initiating MCVideo client 1 has been configured to send an MCVideo emergency alert when upgrading an MCVideo emergency group call. + +![Sequence diagram showing the upgrade of an MCVideo group call to an emergency group call. Lifelines: MCVideo client 1, MCVideo server, Group management server, MCVideo client 2, MCVideo client 3. The process starts with a group call already in progress. Client 1 initiates an emergency, sends a request to the server, which adjusts bearer priority and then requests the emergency group call from clients 2 and 3. Clients 2 and 3 notify their users and send responses to the server, which finally responds to client 1.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant Group management server + participant MCVideo client 2 + participant MCVideo client 3 + + Note over MCVideo client 1, MCVideo client 3: Group call already in progress + + MCVideo client 1->>MCVideo client 1: 1. Initiate group emergency + MCVideo client 1->>MCVideo server: 2. MCVideo emergency group call request + MCVideo server->>MCVideo server: 3. Bearer priority adjustment + MCVideo server->>MCVideo client 2: 4. MCVideo emergency group call request + MCVideo server->>MCVideo client 3: 4. MCVideo emergency group call request + MCVideo client 2->>MCVideo client 2: 5. Notify group emergency status + MCVideo client 3->>MCVideo client 3: 5. Notify group emergency status + MCVideo client 2->>MCVideo server: 6. MCVideo emergency group call response + MCVideo client 3->>MCVideo server: 6. MCVideo emergency group call response + MCVideo server->>MCVideo client 1: 7. MCVideo emergency group call response + +``` + +Sequence diagram showing the upgrade of an MCVideo group call to an emergency group call. Lifelines: MCVideo client 1, MCVideo server, Group management server, MCVideo client 2, MCVideo client 3. The process starts with a group call already in progress. Client 1 initiates an emergency, sends a request to the server, which adjusts bearer priority and then requests the emergency group call from clients 2 and 3. Clients 2 and 3 notify their users and send responses to the server, which finally responds to client 1. + +**Figure 7.1.2.5.1.2-1: MCVideo group call upgraded to an MCVideo emergency group call** + +1. The MCVideo user at MCVideo client 1 initiates a group emergency. MCVideo client 1 sets its MCVideo emergency state. The MCVideo emergency state is retained until explicitly cancelled. +2. MCVideo client 1 requests the MCVideo server to upgrade the MCVideo group to an in-progress emergency state by sending an MCVideo emergency group call request. If configured to send an MCVideo alert when initiating an MCVideo emergency upgrade, the request also contains an indication that an MCVideo alert is to be initiated. The request may contain an indication of an implicit transmit media request. +3. The MCVideo server adjusts the priority of the underlying bearer for all participants in the MCVideo group. +4. MCVideo server sends the MCVideo emergency group call request towards the MCVideo clients of each of those affiliated MCVideo group members. The request contains an indication of an MCVideo emergency alert if the request from the originator indicated MCVideo emergency alert. +5. MCVideo users are notified of the in-progress emergency state of the MCVideo group. +6. The receiving MCVideo clients send the MCVideo emergency group call response to the MCVideo server to acknowledge the MCVideo group emergency request. For a multicast call, these acknowledgements are not sent. +7. The MCVideo server sends the MCVideo emergency group call response to the MCVideo user 1 to confirm the upgrade request. If the MCVideo emergency request contained an implicit transmit media request, the OK message contains the result of the implicit transmit media request. + +NOTE 2: Step 7 can occur at any time following step 3, and prior to step 8 depending on the conditions to proceed with the call. + +MCVideo client 1, MCVideo client 2 and MCVideo client 3 continue with the MCVideo group call, which has been transformed into an MCVideo emergency group call. MCVideo client 1 can override other clients in the call except those that are also in the MCVideo emergency state. + +#### 7.1.2.5.1.3 MCVideo in-progress emergency group state cancel + +NOTE 1: In Rel-14 and Rel-13 versions of this specification the title of this subclause is "MCVideo emergency group call cancel". + +The procedure describes the case where an MCVideo client cancels an MCVideo group's in-progress emergency. + +Procedures in figure 7.1.2.5.1.3-1 are the signalling control plane procedures for the MCVideo client cancelling an in-progress emergency of a group. + +NOTE 2: For simplicity, a single MCVideo server is shown in place of a user home MCVideo server and a group hosting MCVideo server. + +NOTE 3: The end of the MCVideo emergency group call does not cancel the MCVideo group's in-progress emergency state. It is explicitly cancelled by an authorized user using this procedure. + +#### Pre-conditions: + +1. The MCVideo group is previously defined on the group management server with MCVideo client 2 and MCVideo client 3 affiliated to that MCVideo group. +2. All members of the MCVideo group belong to the same MC system. +3. MCVideo group members have been notified about the in-progress emergency. +4. The MCVideo group is in the in-progress emergency state and has prioritized bearer support. +5. MCVideo client 1 previously initiated the in-progress emergency for the group. + +![Sequence diagram for MCVideo in-progress emergency group state cancel. Lifelines: MCVideo client 1, MCVideo server, Group management server, MCVideo client 2, MCVideo client 3. The sequence starts with client 1 initiating a cancel, followed by a request to the server, group ID resolution, bearer priority adjustment, a request to other clients, notifications to clients 2 and 3, responses from clients 2 and 3 to the server, and finally a response from the server to client 1.](8269648391c59363ea61243864a2adf7_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant Group management server + participant MCVideo client 2 + participant MCVideo client 3 + + Note left of MCVideo client 1: 1. Initiate MCVideo in-progress emergency group State cancel + MCVideo client 1->>MCVideo server: 2. MCVideo in-progress emergency group state cancel request + MCVideo server->>Group management server: 3. Resolve group id + Note right of MCVideo server: 4. Bearer priority adjustment + MCVideo server->>MCVideo client 2: 5. MCVideo in-progress emergency group state cancel request + MCVideo server->>MCVideo client 3: 5. MCVideo in-progress emergency group state cancel request + Note right of MCVideo client 2: 6. Notify emergency cancel + Note right of MCVideo client 3: 6. Notify emergency cancel + MCVideo client 2-->>MCVideo server: 7. MCVideo in-progress emergency group state cancel response + MCVideo client 3-->>MCVideo server: 7. MCVideo in-progress emergency group state cancel response + MCVideo server-->>MCVideo client 1: 8. MCVideo in-progress emergency group state cancel response + +``` + +Sequence diagram for MCVideo in-progress emergency group state cancel. Lifelines: MCVideo client 1, MCVideo server, Group management server, MCVideo client 2, MCVideo client 3. The sequence starts with client 1 initiating a cancel, followed by a request to the server, group ID resolution, bearer priority adjustment, a request to other clients, notifications to clients 2 and 3, responses from clients 2 and 3 to the server, and finally a response from the server to client 1. + +**Figure 7.1.2.5.1.3-1: MCVideo in-progress emergency group state cancel** + +1. The user at the MCVideo client 1 initiates an MCVideo in-progress emergency group state cancel. + +NOTE 4: An MCVideo user authorized to cancel in-progress emergencies on the MCVideo group can also be authorised to cancel the MCVideo emergency alert in addition to the initiator. However, only the initiator can cancel the initiator's local MCVideo emergency state. + +2. MCVideo client 1 sends an MCVideo in-progress emergency group state cancel request to the MCVideo server. + +NOTE 5: When MCVideo emergency alerts are in effect together with an MCVideo in-progress emergency group state on the same MCVideo group, the MCVideo emergency alert can, under some circumstances be cancelled at the same time. In that case, the MCVideo in-progress emergency group state request carries an indication that the alert is also being cancelled. + +3. MCVideo server resolves the MCVideo group ID to determine the members of that MCVideo group and their affiliation status, based upon the information from group management server. +4. The MCVideo server adjusts the priority of the underlying bearer; priority treatment is no longer required. The MCVideo server cancels/resets the emergency in-progress state of the MCVideo group. +5. The MCVideo server sends an MCVideo in-progress emergency group state cancel request to the MCVideo group members. +6. MCVideo group members are notified of the MCVideo in-progress emergency group state cancel. +7. The receiving MCVideo clients send the MCVideo in-progress emergency group state cancel response to the MCVideo server to acknowledge the MCVideo in-progress emergency group state cancel. For a multicast call scenario, these acknowledgements are not sent. + +8. The MCVideo server sends the MCVideo in-progress emergency group state cancel response to the MCVideo user 1 to confirm the MCVideo in-progress emergency group state cancel. If the MCVideo in-progress emergency group state cancel request (in step 2) contained the "Alert indicator" IE, the MCVideo client 1 resets its local emergency status. + +NOTE 6: Step 8 can occur at any time following step 4, depending on the conditions to proceed with the call. + +#### 7.1.2.5.2 MCVideo imminent peril group call + +##### 7.1.2.5.2.1 MCVideo imminent peril group call commencement + +The procedure focuses on the case where an authorized MCVideo user is initiating an imminent peril group call for communicating with the affiliated MCVideo members of that MCVideo group. This procedure will gain elevated access privilege for the MCVideo client if it is not already in that state. The access privilege for other applications will not necessarily be affected. + +Procedures in figure 7.1.2.5.2.1-1 are the signalling control plane procedures for the MCVideo client initiating establishment of an imminent peril group call with an MCVideo group i.e., MCVideo users on MCVideo client 1, MCVideo client 2 and MCVideo client 3 belong to the same MCVideo group which is defined on MCVideo group management server. + +Pre-conditions: + +1. The MCVideo group is previously defined on the group management server with MCVideo client 2 and MCVideo client 3 affiliated to that MCVideo group. +2. All members of the MCVideo group belong to the same MC system. +3. The initiating MCVideo client 1 has been provisioned with an MCVideo group that has been designated in the provisioning to be used for imminent peril communications. + +NOTE 1: Alternatively, the client could have been provisioned for imminent peril behaviour on the selected group. + +![Sequence diagram for MCVideo imminent peril group call. Lifelines: MCVideo client 1, MCVideo server, Group management server, MCVideo client 2, MCVideo client 3. The sequence starts with client 1 initiating a call, followed by a request to the server, which then interacts with the group management server to affiliate the user and resolve the group ID. The server then configures bearer priority and sends requests to other clients (2 and 3), who notify their users. Finally, clients 2 and 3 send responses back to the server, which then responds to client 1.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant Group management server + participant MCVideo client 2 + participant MCVideo client 3 + + Note left of MCVideo client 1: 1. initiate imminent peril group call + MCVideo client 1->>MCVideo server: 2. Imminent peril group call request + Note right of MCVideo server: 3. Affiliate user to group + MCVideo server->>Group management server: 4. Resolve group id + Note right of MCVideo server: 5. Bearer priority configuration + MCVideo server->>MCVideo client 2: 6. Imminent peril group call request + MCVideo server->>MCVideo client 3: 6. Imminent peril group call request + Note right of MCVideo client 2: 7. Notify immediate peril call + Note right of MCVideo client 3: 7. Notify immediate peril call + MCVideo client 2-->>MCVideo server: 8. Imminent peril group call response + MCVideo client 3-->>MCVideo server: 8. Imminent peril group call response + MCVideo server->>MCVideo client 1: 9. Imminent peril group call response + +``` + +Sequence diagram for MCVideo imminent peril group call. Lifelines: MCVideo client 1, MCVideo server, Group management server, MCVideo client 2, MCVideo client 3. The sequence starts with client 1 initiating a call, followed by a request to the server, which then interacts with the group management server to affiliate the user and resolve the group ID. The server then configures bearer priority and sends requests to other clients (2 and 3), who notify their users. Finally, clients 2 and 3 send responses back to the server, which then responds to client 1. + +**Figure 7.1.2.5.2.1-1: MCVideo imminent peril group call** + +1. The user at the MCVideo client 1 initiates an imminent peril group call. + 2. MCVideo client 1 sends an MCVideo imminent peril group call request towards the MCVideo server. The request contains an indication of the in-progress imminent peril. The MCVideo server records the identity of the MCVideo user that initiated the imminent peril group call until the in-progress imminent peril state is cancelled. Once an imminent peril group call has been initiated, the MCVideo group is considered to be in an in-progress imminent peril state until cancelled. The request may contain an indication of an implicit transmit media request. + 3. The MCVideo server implicitly affiliates MCVideo client 1 to the imminent peril group if the client is not already affiliated. + 4. MCVideo server checks whether the MCVideo user of MCVideo client 1 is authorized for initiation of imminent peril group calls on the indicated MCVideo group, and if authorized, it resolves the MCVideo group ID to determine the members of that MCVideo group and their affiliation status, based on the information from group management server. + 5. The MCVideo server configures the priority of the underlying bearers for all participants in the MCVideo group. +- NOTE 2: Successive calls during the in-progress imminent peril state will all receive the adjusted bearer priority. +6. MCVideo server sends the imminent peril group call request towards the MCVideo clients of each of those affiliated MCVideo group members. The request contains an indication of the in-progress imminent peril. + 7. MCVideo users are notified of the incoming imminent peril call. + +8. The receiving MCVideo clients send the MCVideo imminent peril group call response to the MCVideo server to acknowledge the imminent peril call request. For a multicast call, these acknowledgements are not set. +9. The MCVideo server sends the MCVideo imminent peril group call response to the MCVideo user 1 to inform the successful imminent peril call establishment. If the MCVideo imminent peril request contained an implicit transmit media request, the OK message contains the result of the implicit transmit media request. + +NOTE 3: Step 9 can occur at any time following step 5, and prior to step 10 depending on the conditions to proceed with the imminent peril call. + +MCVideo client 1, MCVideo client 2 and MCVideo client 3 have successfully established media plane for communication. MCVideo transmission control participant 1, transmission control participant 2 and transmission control participant 3 exchange transmission control information e.g., MCVideo client 1 receives the transmit media granted information over the established media plane, while the other MCVideo clients receive media available notification with forced reception mode information. MCVideo client 1 indicates to the MCVideo user that the permission is granted to transmit media, while the other MCVideo clients in the imminent peril call will be receiving that media. + +#### 7.1.2.5.2.2 Imminent peril group call upgrade + +The procedure focuses on the case where an authorized MCVideo user is upgrading an MCVideo group call to an imminent peril group call while the MCVideo group call is already in progress. + +Procedures in figure 7.1.2.5.2.2-1 are the signalling control plane procedures for the MCVideo client upgrading an MCVideo group call on an MCVideo group to an imminent peril group call. + +Pre-conditions: + +1. The MCVideo group is previously defined on the group management server with MCVideo client 1, MCVideo client 2 and MCVideo client 3 affiliated to that MCVideo group. +2. All members of the MCVideo group belong to the same MC system. +3. An MCVideo group call is already in progress. + +![Sequence diagram for MCVideo group call upgrade to an imminent peril group call. Lifelines: MCVideo client 1, MCVideo server, Group management server, MCVideo client 2, MCVideo client 3. The process starts with a user initiating an imminent peril call at client 1, followed by a request to the server, a bearer priority adjustment, requests to other clients, notifications to users, responses from clients to the server, and a final response to the user at client 1.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant Group management server + participant MCVideo client 2 + participant MCVideo client 3 + + Note over MCVideo client 1, MCVideo client 3: Group call already in progress + + Note left of MCVideo client 1: 1. User initiates imminent peril call + MCVideo client 1->>MCVideo server: 2. MCVideo imminent peril group call request + Note over MCVideo server: 3. Bearer priority adjustment + MCVideo server->>MCVideo client 2: 4. MCVideo imminent peril group call request + MCVideo server->>MCVideo client 3: 4. MCVideo imminent peril group call request + Note over MCVideo client 2: 5. Notify imminent peril status + Note over MCVideo client 3: 5. Notify imminent peril status + MCVideo client 2-->>MCVideo server: 6. MCVideo imminent peril group call response + MCVideo client 3-->>MCVideo server: 6. MCVideo imminent peril group call response + MCVideo server->>MCVideo client 1: 7. MCVideo imminent peril group call response + +``` + +Sequence diagram for MCVideo group call upgrade to an imminent peril group call. Lifelines: MCVideo client 1, MCVideo server, Group management server, MCVideo client 2, MCVideo client 3. The process starts with a user initiating an imminent peril call at client 1, followed by a request to the server, a bearer priority adjustment, requests to other clients, notifications to users, responses from clients to the server, and a final response to the user at client 1. + +**Figure 7.1.2.5.2.2-1: MCVideo group call upgrade to an imminent peril group call** + +1. The MCVideo user at MCVideo client 1 initiates an imminent peril call. +2. MCVideo client 1 requests the MCVideo server to upgrade the MCVideo group to an in-progress imminent peril state by sending an MCVideo imminent peril group call request. The request may contain an indication of an implicit transmit media request. +3. The MCVideo server adjusts the priority of the underlying bearer for all participants in the MCVideo group. +4. MCVideo server sends the MCVideo imminent peril group call request towards the MCVideo clients of each of those affiliated MCVideo group members. +5. MCVideo users are notified of the in-progress imminent peril state of the MCVideo group. +6. The receiving MCVideo clients send the MCVideo imminent peril group call response to the MCVideo server to acknowledge the MCVideo imminent peril group call request. For a multicast call, these acknowledgements are not set. +7. The MCVideo server sends the MCVideo imminent peril group call response to the MCVideo user 1 to confirm the upgrade request. If the MCVideo imminent peril group call request contained an implicit transmit media request, the OK message contains the result of the implicit transmit media request. + +NOTE: Step 7 can occur at any time following step 4, and prior to step 8 depending on the conditions to proceed with the call. + +MCVideo client 1, MCVideo client 2 and MCVideo client 3 continue with the MCVideo group call, which has been transformed into an imminent peril group call. + +#### 7.1.2.5.2.3 MCVideo imminent peril group call cancel + +The procedure focuses on the case where an authorized MCVideo user cancels an MCVideo group's in-progress imminent peril state. + +Procedures in figure 7.1.2.5.2.3-1 are the signalling control plane procedures for the MCVideo client cancelling an MCVideo group's in-progress imminent peril state. + +NOTE 1: The end of the imminent peril call does not cancel the MCVideo group's in-progress imminent peril state. It is explicitly cancelled by an authorized user. + +Pre-conditions: + +1. The MCVideo group is previously defined on the group management server with MCVideo client 1, MCVideo client 2 and MCVideo client 3 affiliated to that MCVideo group. +2. All members of the MCVideo group belong to the same MC system. +3. The MCVideo group is an in-progress imminent peril state and has prioritized bearer support. +4. MCVideo group members have been notified about the MCVideo group's in-progress imminent peril state. +5. MCVideo client 1 previously initiated the in-progress imminent peril. + +![Sequence diagram for MCVideo imminent peril group call cancel. Lifelines: MCVideo client 1, MCVideo server, Group management server, MCVideo client 2, MCVideo client 3. The sequence starts with client 1 sending an 'initiate imminent peril cancel' message to the server. The server performs 'Bearer priority adjustment' and 'Resolve group id' internally. It then sends an 'MCVideo imminent peril group call cancel request' to clients 2 and 3. Clients 2 and 3 send 'Notify Imminent peril cancel' responses. Finally, the server sends an 'MCVideo imminent peril group call cancel response' back to client 1.](1316d63eca7b84e13c27f55f0027b7b5_img.jpg) + +``` +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant Group management server + participant MCVideo client 2 + participant MCVideo client 3 + + Note left of MCVideo client 1: 1. initiate imminent peril cancel + MCVideo client 1->>MCVideo server: 2. MCVideo imminent peril group call cancel request + Note right of MCVideo server: 3. Bearer priority adjustment + Note right of MCVideo server: 4. Resolve group id + MCVideo server->>MCVideo client 2: 5. MCVideo imminent peril group call cancel request + MCVideo server->>MCVideo client 3: 5. MCVideo imminent peril group call cancel request + Note right of MCVideo client 2: 6. Notify Imminent peril cancel + Note right of MCVideo client 3: 6. Notify Imminent peril cancel + MCVideo client 2-->>MCVideo server: 7. MCVideo imminent peril group call cancel response + MCVideo client 3-->>MCVideo server: 7. MCVideo imminent peril group call cancel response + MCVideo server->>MCVideo client 1: 8. MCVideo imminent peril group call cancel response +``` + +Sequence diagram for MCVideo imminent peril group call cancel. Lifelines: MCVideo client 1, MCVideo server, Group management server, MCVideo client 2, MCVideo client 3. The sequence starts with client 1 sending an 'initiate imminent peril cancel' message to the server. The server performs 'Bearer priority adjustment' and 'Resolve group id' internally. It then sends an 'MCVideo imminent peril group call cancel request' to clients 2 and 3. Clients 2 and 3 send 'Notify Imminent peril cancel' responses. Finally, the server sends an 'MCVideo imminent peril group call cancel response' back to client 1. + +**Figure 7.1.2.5.2.3-1: MCVideo imminent peril group call cancel** + +1. The user at the MCVideo client 1 initiates an imminent peril cancel. +2. MCVideo client 1 sends an MCVideo imminent peril group call cancel request to the MCVideo server. +3. The MCVideo server adjusts the priority of the underlying bearer; priority treatment is no longer required. The MCVideo server cancels/resets the in-progress imminent peril state. +4. MCVideo server resolves the MCVideo group ID to determine the members of that MCVideo group and their affiliation status, based upon the information from group management server. + +5. The MCVideo server sends an MCVideo imminent peril group call cancel request to the MCVideo group members. +6. MCVideo group members are notified of the in-progress imminent peril cancel. +7. The receiving MCVideo group members send the MCVideo imminent peril group call cancel response to the MCVideo server to acknowledge the in-progress MCVideo imminent peril group call cancel request. For a multicast scenario, these acknowledgements are not set. +8. The MCVideo server sends the MCVideo imminent peril group call cancel response to the MCVideo user 1 to confirm the MCVideo imminent peril group call cancel request. + +NOTE 2: Step 8 can occur at any time following step 4, depending on the conditions to proceed with the call. + +## 7.1.2.6 MCVideo emergency alert + +### 7.1.2.6.1 General + +The MCVideo server and MCVideo client use emergency alert initiation and emergency alert cancel procedures defined in 3GPP TS 23.280 [6] using MCVideo-1 reference point, with the following clarifications: + +- The MC service ID is the MCVideo ID; and +- The MC service group ID is the MCVideo group ID. + +## 7.1.3 Off-network group communications + +### 7.1.3.1 General + +This subclause contains procedures for group communications directly between multiple MCVideo clients without involving the network to provide associated functions. + +The group communication setup is described in subclause 7.1.3.3 and two variations of joining an existing communication group communication are described, the passive variant in subclause 7.1.3.4 and the active variant in subclause 7.1.3.5. + +NOTE: When the MCVideo client receives a message that is not addressed to either its MCVideo ID or to any MCVideo group of which the MCVideo client is an affiliated group member, the MCVideo client ignores the message. + +### 7.1.3.2 Information flows for off-network group communications + +#### 7.1.3.2.1 Group communication announcement + +Table 7.1.3.2.1-1 describes the information flow for the group communication announcement sent from the MCVideo client to other MCVideo clients. + +**Table 7.1.3.2.1-1: Group communication announcement** + +| <b>Information Element</b> | <b>Status</b> | <b>Description</b> | +|------------------------------------|---------------|--------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user sending the announcement | +| MCVideo group ID | M | The MCVideo group ID towards which the announcement was sent | +| Media codec | M | The media characteristics like codec, resolution, frame rate and video mode to be used for the communication | +| Multi-cast port | M | Multicast port number for media | +| Transmission control port number | M | Port number for transmission control protocol | +| Announcement period | M | Period of the group communication announcement | +| Encryption parameters | O | Encryption parameters to be used for the communication, if the communication is to be encrypted | +| Confirm mode indication | O | Indicates whether the receiving MCVideo user needs to confirm participation | +| Emergency indication | O | Indicates that the MCVideo group communication is an MCVideo emergency communication | +| Imminent peril indication | O | Indicates that the MCVideo group communication is an MCVideo imminent peril communication | +| Broadcast communication indication | O | Indicates that the MCVideo communication is a broadcast communication | +| Video push indication | O | Indicates that the MCVideo communication is for video push | +| Video pull indication | O | Indicates that the MCVideo communication is for video pull | + +### 7.1.3.2.2 Group communication answer response + +Table 7.1.3.2.2-1 describes the information flow for the group communication answer response sent from the MCVideo client to other MCVideo clients. + +**Table 7.1.3.2.2-1: Group communication answer response** + +| <b>Information Element</b> | <b>Status</b> | <b>Description</b> | +|----------------------------|---------------|------------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user sending the response | +| MCVideo group ID | M | The identity of the MCVideo group on which the call is requested | + +### 7.1.3.2.3 MCVideo upgrade to emergency group communication + +Table 7.1.3.2.3-1 describes the information flow for the MCVideo upgrade to emergency sent from the MCVideo client to other MCVideo clients. + +**Table 7.1.3.2.3-1: MCVideo upgrade to emergency group communication** + +| <b>Information Element</b> | <b>Status</b> | <b>Description</b> | +|----------------------------|---------------|--------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user upgrading the communication | +| MCVideo group ID | M | The MCVideo group ID towards which the upgrade was sent | + +#### 7.1.3.2.4 MCVideo emergency group communication cancel + +Table 7.1.3.2.4-1 describes the information flow for the MCVideo emergency group communication cancel sent from the MCVideo client to other MCVideo clients. + +**Table 7.1.3.2.4-1: MCVideo emergency group communication cancel** + +| <b>Information Element</b> | <b>Status</b> | <b>Description</b> | +|----------------------------|---------------|---------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user cancelling the upgrade | +| MCVideo group ID | M | The MCVideo group ID towards which the cancel was sent | + +#### 7.1.3.2.5 MCVideo upgrade to imminent peril group communication + +Table 7.1.3.2.5-1 describes the information flow for the MCVideo upgrade to imminent peril sent from the MCVideo client to other MCVideo clients. + +**Table 7.1.3.2.5-1: MCVideo upgrade to imminent peril group communication** + +| <b>Information Element</b> | <b>Status</b> | <b>Description</b> | +|----------------------------|---------------|--------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user upgrading the communication | +| MCVideo group ID | M | The MCVideo group ID towards which the upgrade was sent | + +#### 7.1.3.2.6 MCVideo imminent peril group communication cancel + +Table 7.1.3.2.6-1 describes the information flow for MCVideo imminent peril group communication cancel sent from the MCVideo client to other MCVideo clients. + +**Table 7.1.3.2.6-1: MCVideo imminent peril group communication cancel** + +| <b>Information Element</b> | <b>Status</b> | <b>Description</b> | +|----------------------------|---------------|---------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user cancelling the upgrade | +| MCVideo group ID | M | The MCVideo group ID towards which the cancel was sent | + +#### 7.1.3.2.7 MCVideo emergency alert announcement + +Table 7.1.3.2.7-1 describes the information flow for the MCVideo emergency alert announcement sent from the MCVideo client to the other MCVideo clients, for the procedures defined in 3GPP TS 23.280 [6]. + +**Table 7.1.3.2.7-1: MCVideo emergency alert announcement** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user sending emergency alert | +| MCVideo group ID | M | The MCVideo group ID towards which the alert was sent | +| Organization name | M | The alerting user's mission critical organization name | +| Location | O | The alerting client's location, if known | + +#### 7.1.3.2.8 MCVideo emergency alert cancel announcement + +Table 7.1.3.2.8-1 describes the information flow for the MCVideo emergency alert cancel sent from the MCVideo client to other MCVideo clients, for the procedures defined in 3GPP TS 23.280 [6]. + +**Table 7.1.3.2.8-1: MCVideo emergency alert cancel announcement** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user cancelling emergency alert | +| MCVideo group ID | M | The MCVideo group ID towards which the cancel was sent | + +### 7.1.3.3 Group communication setup + +#### 7.1.3.3.1 General + +A group communication setup is initiated by one member of a pre-configured MCVideo group and ends up with an established MCVideo group between multiple MCVideo clients ready for video sharing. + +#### 7.1.3.3.2 Procedure + +Figure 7.1.3.3.2-1 describes procedures to establish a MCVideo group communication with other MCVideo clients. + +Once the MCVideo group communication is established the MCVideo clients send Group communication announcement periodically. + +Pre-conditions: + +1. Information for **ProSe** direct communications corresponding to the MCVideo group and its mapping to **ProSe** Layer-2 Group ID are pre-configured in MCVideo client 1 to client N. +2. MCVideo client 1 to MCVideo client N are members of the same MCVideo group. +3. MCVideo user 1 has initiated MCVideo group communication. + +![Sequence diagram illustrating the MCVideo group communication setup. The diagram shows three MCVideo clients (client 1, client 2, and client N) interacting. Step 1: MCVideo client 1 sends a 'Group communication announcement' to clients 2 and N. Step 2: Clients 2 and N each send a 'Set parameters for media plane' message. Step 3: Clients 2 and N each send a 'Group communication answer response' back to client 1. Step 4: A dashed box labeled 'Check participants' spans across the lifelines. Step 5: A solid box labeled 'Media plane and transmission control establishment with periodic group communication announcements' spans across the lifelines.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant C2 as MCVideo client 2 + participant CN as MCVideo client N + Note right of C2: 2. Set parameters for media plane + Note right of CN: 2. Set parameters for media plane + Note over C1, C2, CN: 4. Check participants + Note over C1, C2, CN: 5. Media plane and transmission control establishment with periodic group communication announcements + + C1->>C2: 1. Group communication announcement + C1->>CN: 1. Group communication announcement + C2->>C1: 3. Group communication answer response + CN->>C1: 3. Group communication answer response + +``` + +Sequence diagram illustrating the MCVideo group communication setup. The diagram shows three MCVideo clients (client 1, client 2, and client N) interacting. Step 1: MCVideo client 1 sends a 'Group communication announcement' to clients 2 and N. Step 2: Clients 2 and N each send a 'Set parameters for media plane' message. Step 3: Clients 2 and N each send a 'Group communication answer response' back to client 1. Step 4: A dashed box labeled 'Check participants' spans across the lifelines. Step 5: A solid box labeled 'Media plane and transmission control establishment with periodic group communication announcements' spans across the lifelines. + +**Figure 7.1.3.3.2-1: MCVideo group communication setup** + +1. MCVideo client 1 sends a Group communication announcement message to the MCVideo group. +2. Upon receiving the Group communication announcement message, all MCVideo clients that are not part of an ongoing group communication for the MCVideo group indicated in the Group communication announcement message set parameters for the media plane as described in the Group communication announcement message. +3. The MCVideo clients send a group communication answer response to the MCVideo group confirming the participation in the MCVideo group communication. On receiving a group communication answer response message from at least one MCVideo client, other MCVideo clients need not send a group communication answer response message. If the Group communication announcement message included a confirm mode indication, then the MCVideo clients should send a group communication answer response message. + +NOTE 1: MCVideo client 1 should wait for at least one group communication answer response message before transmitting video to the MCVideo group. + +4. MCVideo client 1 checks the participants of the MCVideo group communication through the received group communication answer response messages. + +NOTE 2: Due to the movement of the participants (in and out of the radio coverage) during the off-network group communication, the Group communication announcement message, including parameters for media delivery, is periodically sent. + +NOTE 3: Group communication announcement may include user ID, group ID, media type codec, control port for transmission video, video resolution and video frame rate, video mode, last change time of video mode etc. + +5. MCVideo client 1, MCVideo client 2 and MCVideo client 3 have successfully established the media plane and transmission control for communication. + +### 7.1.3.4 Passive join to group communication + +#### 7.1.3.4.1 General + +There is ongoing group communication between multiple MCVideo clients. Another MCVideo client, after becoming aware of that group communication and after it has received periodically sent communication parameters, joins the group with or without sending an indication to other group members. + +### 7.1.3.4.2 Procedure + +Figure 7.1.3.4.2-1 describes procedures to join a MCVideo group communication passively. + +The MCVideo client X passively waits for a Group communication announcement message. Upon receiving a periodic Group communication announcement message, MCVideo client X establishes media plane and joins the MCVideo group communication. + +Pre-conditions: + +1. Information for **ProSe** direct communications corresponding to the MCVideo group and its mapping to **ProSe** Layer-2 Group ID are pre-configured in MCVideo client 1 to client N and client X. +2. MCVideo client 1 to MCVideo client N and MCVideo client X are members of the same MCVideo group. +3. MCVideo client 1 to MCVideo client N are part of an ongoing MCVideo group communication. + +![Sequence diagram showing the passive join process for MCVideo group communication. Lifelines: MCVideo client 1, MCVideo client N, and MCVideo client X. Steps: 1. MCVideo client X enters in communication range; 2. Periodic group communication announcement from client N to client 1 and X; 3. Set parameters for media plane at client X; 4. Group communication answer response from client X to client 1 and N; 5. MCVideo group communication with periodic group communication announcements involving all clients.](605ad256780bc1b6022dfb65a6e24a3b_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MCVideo client 1 + participant ClientN as MCVideo client N + participant ClientX as MCVideo client X + Note right of ClientX: 1. MCVideo client enters in communication range + ClientN->>Client1: 2. Periodic group communication announcement + Note right of ClientX: 3. Set parameters for media plane + ClientX-->>Client1: 4. Group communication answer response + Note right of ClientX: 5. MCVideo group communication with periodic group communication announcements + +``` + +Sequence diagram showing the passive join process for MCVideo group communication. Lifelines: MCVideo client 1, MCVideo client N, and MCVideo client X. Steps: 1. MCVideo client X enters in communication range; 2. Periodic group communication announcement from client N to client 1 and X; 3. Set parameters for media plane at client X; 4. Group communication answer response from client X to client 1 and N; 5. MCVideo group communication with periodic group communication announcements involving all clients. + +**Figure 7.1.3.4.2-1: Passive join to MCVideo group communication** + +1. Another MCVideo client X enters in the communication range after the MCVideo group communication establishment. The MCVideo client X does not do anything and passively waits for a periodic Group communication announcement message. +2. An MCVideo client which is part of the ongoing MCVideo group communication eventually sends a periodic Group communication announcement message. +3. Upon receiving the periodic Group communication announcement message MCVideo client X sets the parameters for media plane as described in the Group communication announcement message. +4. If the Group communication announcement message included a confirm mode indication, MCVideo client X may sends a group communication answer response towards MCVideo group to inform all MCVideo group members of its participation the MCVideo group communication. +5. MCVideo group communication continues with the MCVideo client X. + +### 7.1.3.5 Active join to group communication + +#### 7.1.3.5.1 General + +There is ongoing group communication between multiple MCVideo clients. Another MCVideo client, after becoming aware of that group communication, sends a request to get the required communication parameters and after feedback joins the group with or without sending an indication to other group members. + +#### 7.1.3.5.2 Procedure + +Figure 7.1.3.5.2-1 describes procedures to join a MCVideo group communication actively. + +The MCVideo client X sends a Group communication announcement message towards the MCVideo group. + +Upon receiving a Group communication announcement message with new communication parameters, such as communication identifier, a MCVideo client participating in the on-going group communication for the MCVideo group sends a Group communication announcement message. + +The Group communication announcement message contains parameters for the on-going MCVideo group communication. MCVideo client X upon receiving such a Group communication announcement message establishes the media plane as described in the message and joins the MCVideo group communication. + +Pre-conditions: + +1. Information for **ProSe** direct communications corresponding to the MCVideo group and its mapping to **ProSe** Layer-2 Group ID are pre-configured in MCVideo client 1 to client N and client X. +2. MCVideo client 1 to MCVideo client N and MCVideo client X are members of the same MCVideo group. +3. MCVideo client 1 to MCVideo client N are part of an ongoing MCVideo group communication. + +![Sequence diagram showing the active join process for MCVideo group communication. Lifelines: MCVideo client 1, MCVideo client N, and MCVideo client X. The sequence includes: 1. Client X sends announcement to N; 2. Client N sends announcement to X; 3. Client X sets parameters; 4. Client X sends response to N; 5. Ongoing group communication with periodic announcements.](1a1484a99fee36bd3ca4e40fe1538bf8_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant CN as MCVideo client N + participant CX as MCVideo client X + Note right of CX: 3. Set parameters for media plane + CX->>CN: 1. Group communication announcement + CN->>CX: 2. Group communication announcement + Note right of CX: 3. Set parameters for media plane + CX-->>CN: 3. Group communication answer response + Note over C1, CN, CX: 5. MCVideo group communication with periodic group communication announcements + +``` + +Sequence diagram showing the active join process for MCVideo group communication. Lifelines: MCVideo client 1, MCVideo client N, and MCVideo client X. The sequence includes: 1. Client X sends announcement to N; 2. Client N sends announcement to X; 3. Client X sets parameters; 4. Client X sends response to N; 5. Ongoing group communication with periodic announcements. + +Figure 7.1.3.5.2-1: Active join to MCVideo group communication + +1. Another MCVideo client X enters in the communication range after the MCVideo group communication establishment. The MCVideo client X sends a Group communication announcement message to start a newMCVideo group communication. +2. Upon receiving a Group communication announcement message with new communication parameters, such as communication identifier, another MCVideo client, which is part of the ongoing MCVideo group communication sends a Group communication announcement message. +3. Upon receiving the Group communication announcement message MCVideo client X sets parameters for the media plane as described in the Group communication announcement message. +4. If the Group communication announcement message included a confirm mode indication, MCVideo client X may send a group communication answer response towards MCVideo group to inform all MCVideo group members of its participation the MCVideo group communication. +5. MCVideo group communication continues with the MCVideo client X. + +### 7.1.3.6 Broadcast group communication + +Figure 7.1.3.6-1 describes procedures for broadcast group communication. + +Broadcast group communication over group-broadcast group and over user-broadcast group are handled without distinction in off-network. + +![Sequence diagram showing broadcast group communication between MCVideo client 1 (Originator), MCVideo client 2, and MCVideo client 3. The process consists of three steps: 1. Group communication setup, 2. Video transmission, and 3. Group communication release.](0997dbaa9dfecedd60029d70b53327b8_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 (Originator) + participant MCVideo client 2 + participant MCVideo client 3 + Note over MCVideo client 1, MCVideo client 3: 1. Group communication setup + Note over MCVideo client 1, MCVideo client 3: 2. Video transmission + Note over MCVideo client 1, MCVideo client 3: 3. Group communication release + +``` + +Sequence diagram showing broadcast group communication between MCVideo client 1 (Originator), MCVideo client 2, and MCVideo client 3. The process consists of three steps: 1. Group communication setup, 2. Video transmission, and 3. Group communication release. + +Figure 7.1.3.6-1: Broadcast group communication + +1. MCVideo client 1 initiates group communication setup as described in subclause 7.1.3.3. The group communication announcement message includes the indication of broadcast group communication. +2. MCVideo client 1 initiating broadcast group communication starts to transmit video. + +NOTE: Other clients of the group member are not allowed to transmit media in broadcast group communication. + +3. The broadcast group communication is released as described in subclause 7.1.3.7. + +### 7.1.3.7 Group communication release due to inactivity + +If the on-going MCVideo group communication is inactive for a specific duration, the participating MCVideo clients release the MCVideo group communication. Inactivity is defined as absence of any transmission to or from other communication participants. + +NOTE: Inactivity time can be set according to the policy of MC service provider. + +### 7.1.3.8 Emergency and imminent peril procedures + +#### 7.1.3.8.1 Emergency group communication + +The off-network emergency group communication is a special case of off-network (non-emergency) group communication as defined in subclause 7.1.3.2, subclause 7.1.3.3, subclause 7.1.3.4, subclause 7.1.3.5, subclause 7.1.3.6 and subclause 7.1.3.7. The following are modifications to the aforementioned subclauses to support MCVideo emergency group communications: + +- As a pre-condition, the client initiating the emergency communication has previously been provisioned with an MCVideo group designated as the MCVideo emergency group. The MCVideo client initiates MCVideo emergency group communications on this group. Alternatively, the MCVideo client could have been provisioned for emergency behaviour on the selected MCVideo group. +- The group communication announcement contains an indication that the MCVideo group communication is to be an MCVideo emergency communication regardless of whether or not the MCVideo client is in communication. Group communication participants learn of the MCVideo group's in-progress emergency state from the indication. +- Every communication initiated by the MCVideo client will be an emergency communication while the MCVideo client is in MCVideo emergency state. +- The MCVideo client enters the MCVideo emergency state when initiating an MCVideo emergency communication or emergency alert. Only the MCVideo user of the MCVideo client can clear the client's local MCVideo emergency state. +- The MCVideo group in-progress emergency state is cancelled when the communication ends. +- The MCVideo user who initiated the emergency communication, or upgraded the group communication to emergency group communication, or an authorized user, may cancel the in-progress emergency state with an MCVideo emergency group communication cancel message. The message is sent to the MCVideo group. +- When the MCVideo group is no longer in the in-progress emergency state, every client returns the value of **ProSe** Per Packet Priority to its default value. +- An in-progress MCVideo group communication is upgraded to an emergency group communication when the periodic group communication announcement contains the emergency indicator. +- The value of **ProSe** Per Packet Priority is upgraded according to emergency state of MCVideo group communication. +- An MCVideo group communication upgraded to emergency group communication does not affect the state of other MCVideo communication(s) in the client. +- The MCVideo group remains in the in-progress emergency state until the emergency group communication ends or the in-progress emergency state is cancelled. + +#### 7.1.3.8.2 MCVideo imminent peril + +The off-network imminent peril group communication is a special case of off-network (non-imminent peril) group communication as defined in subclause 7.1.3.2, subclause 7.1.3.3, subclause 7.1.3.4, subclause 7.1.3.5, subclause 7.1.3.6 and subclause 7.1.3.7. The following are modifications to the aforementioned subclauses to support MCVideo imminent peril communications: + +- As a pre-condition, the user initiating the imminent peril communication has previously been provisioned with an MCVideo group to be used as the MCVideo imminent peril group. The MCVideo client initiates MCVideo imminent peril group communications on this group. Alternatively, the MCVideo client could have been provisioned for imminent peril behaviour on the selected MCVideo group. +- The group communication announcement contains an indication that the MCVideo group communication is to be an MCVideo imminent peril communication. Group communication participants learn of the MCVideo group's in-progress imminent peril condition from the indication. + +- The MCVideo group in-progress imminent peril state is considered cancelled when the communication ends. +- The MCVideo user who initiated the in-progress imminent peril communication or upgraded the group communication to imminent peril group communication, or an authorized user may cancel the in-progress imminent peril state with an MCVideo imminent peril group communication cancel message. The message is sent to the communication participants. +- When the MCVideo group is no longer in the in-progress imminent peril state, every MCVideo client returns the value of **ProSe** Per Packet Priority to its default value. +- An in-progress MCVideo group communication is upgraded to an imminent peril group communication when the periodic group communication announcement contains the imminent peril indicator. +- The value of **ProSe** Per Packet Priority is upgraded according to imminent peril state of MCVideo group communication. +- The MCVideo group remains in the in-progress imminent peril state until the imminent peril group communication ends or the in-progress imminent peril state is cancelled. + +### 7.1.3.9 MCVideo emergency alert + +#### 7.1.3.9.1 General + +The MCVideo client use emergency alert initiation and emergency alert cancel procedures defined in 3GPP TS 23.280 [6], with the following clarifications: + +- The MC service ID is the MCVideo ID; and +- The MC service group ID is the MCVideo group ID. + +## 7.2 Private call + +### 7.2.1 General + +Private calls are enabled in both on-network and off-network. + +Private calls can be setup in two different commencement modes, automatic commencement mode and manual commencement mode. + +### 7.2.2 Private call on-network + +#### 7.2.2.1 General + +The private call setup in automatic commencement mode is described in subclause 7.2.2.3.1, manual commencement mode in subclause 7.2.2.3.2 and private call release (client or server initiated) in subclause 7.2.2.3.3. + +#### 7.2.2.2 Information flows for private call in on-network + +##### 7.2.2.2.1 MCVideo private call request (MCVideo client – MCVideo server) + +Table 7.2.2.2.1-1 describes the information flow MCVideo private call request from the MCVideo client to the MCVideo server. + +**Table 7.2.2.2.1-1: MCVideo private call request (MCVideo client – MCVideo server)** + +| <b>Information Element</b> | <b>Status</b> | <b>Description</b> | +|-----------------------------------|---------------|-----------------------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| MCVideo ID | M | The MCVideo ID of the called party | +| Transmit media request indication | M | This element indicates whether transmission control will be used for the private call. | +| SDP offer | M | Media parameters of MCVideo client. | +| Requested commencement mode | O | An indication that is included if the user is requesting a particular commencement mode | +| Implicit transmit media request | O | An indication that the user is also requesting the permission to transmit video | +| Push indication | O | Indicates that the private call request is for a one-to-one push call | +| Pull indication | O | Indicates that the private call request is for a one-to-one pull call | + +#### 7.2.2.2.2 MCVideo private call request (MCVideo server – MCVideo client) + +Table 7.2.2.2.2-1 describes the information flow MCVideo private call request from the MCVideo server to the MCVideo client. + +**Table 7.2.2.2.2-1: MCVideo private call request (MCVideo server – MCVideo client)** + +| <b>Information Element</b> | <b>Status</b> | <b>Description</b> | +|-----------------------------------|---------------|-----------------------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| MCVideo ID | M | The MCVideo ID of the called party | +| Transmit media request indication | M | This element indicates whether transmission control will be used for the private call. | +| SDP offer | M | Media parameters of MCVideo client. | +| Requested commencement mode | O | An indication that is included if the user is requesting a particular commencement mode | +| Implicit transmit media request | O | An indication that the user is also requesting the permission to transmit video | + +#### 7.2.2.2.3 MCVideo private call response (MCVideo client – MCVideo server) + +Table 7.2.2.2.3-1 describes the information flow MCVideo private call response from the MCVideo client to the MCVideo server. + +**Table 7.2.2.2.3-1: MCVideo private call response (MCVideo client – MCVideo server)** + +| Information Element | Status | Description | +|-----------------------------|--------|----------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| MCVideo ID | O | The MCVideo ID of the called party | +| SDP answer | M | Media parameters selected | +| Requested commencement mode | O | An indication of the commencement mode to be used. | + +#### 7.2.2.2.4 MCVideo private call response (MCVideo server – MCVideo client) + +Table 7.2.2.2.4-1 describes the information flow MCVideo private call response from the MCVideo server to the MCVideo client. + +**Table 7.2.2.2.4-1: MCVideo private call response (MCVideo server – MCVideo client)** + +| Information Element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| MCVideo ID | O | The MCVideo ID of the called party | +| Acceptance confirmation | O | An indication whether the user has positively accepted the call. | +| SDP answer | M | Media parameters selected | + +#### 7.2.2.2.5 MCVideo call end request + +Table 7.2.2.2.5-1 describes the information flow MCVideo call end request from the MCVideo client to the MCVideo server and from the MCVideo server to the MCVideo client. + +**Table 7.2.2.2.5-1: MCVideo call end request** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| MCVideo ID | M | The MCVideo ID of the called party | + +#### 7.2.2.2.6 MCVideo emergency private call request (MCVideo client to MCVideo server) + +Table 7.2.2.2.6-1 describes the information flow MCVideo emergency private call request from the MCVideo client to the MCVideo server. + +**Table 7.2.2.2.6-1: MCVideo emergency private call request (MCVideo client to MCVideo server)** + +| Information Element | Status | Description | +|---------------------------------|--------|----------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| MCVideo ID | M | The MCVideo ID of the called party | +| Emergency indicator | M | Indicates that the private call request is an MCVideo emergency call | +| Alert indicator | M | Indicates whether an emergency alert is to be sent | +| Requested commencement mode | O | An indication of the commencement mode to be used. | +| Implicit transmit media request | O | An indication that the user is also requesting to transmit media | +| SDP offer | M | Media parameters of MCVideo client. | + +#### 7.2.2.2.7 MCVideo emergency private call request (MCVideo server to MCVideo client) + +Table 7.2.2.2.7-1 describes the information flow MCVideo emergency private call request from the MCVideo server to the MCVideo client. + +**Table 7.2.2.2.7-1: MCVideo emergency private call request (MCVideo server to MCVideo client)** + +| Information Element | Status | Description | +|---------------------------------|--------|----------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| MCVideo ID | M | The MCVideo ID of the called party | +| Emergency indicator | M | Indicates that the private call request is an MCVideo emergency call | +| Alert indicator | M | Indicates whether an emergency alert is to be sent | +| Requested commencement mode | O | An indication of the commencement mode to be used. | +| Implicit transmit media request | O | An indication that the user is also requesting to transmit media. | +| SDP offer | M | Media parameters of MCVideo client. | + +#### 7.2.2.2.8 Emergency MCVideo private call response (MCVideo client – MCVideo server) + +Table 7.2.2.2.8-1 describes the information flow emergency MCVideo private call response from the MCVideo client to the MCVideo server. + +**Table 7.2.2.2.8-1: Emergency MCVideo private call response (MCVideo client – MCVideo server)** + +| Information Element | Status | Description | +|-----------------------------|--------|----------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| MCVideo ID | O | The MCVideo ID of the called party | +| SDP answer | M | Media parameters selected | +| Requested commencement mode | O | An indication of the commencement mode to be used. | + +### 7.2.2.2.9 Emergency MCVideo private call response (MCVideo server – MCVideo client) + +Table 7.2.2.2.9-1 describes the information flow Emergency MCVideo private call response from the MCVideo server to the MCVideo client. + +**Table 7.2.2.2.9-1: Emergency MCVideo private call response (MCVideo server – MCVideo client)** + +| Information Element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| MCVideo ID | O | The MCVideo ID of the called party | +| Acceptance confirmation | O | An indication whether the user has positively accepted the call. | +| SDP answer | M | Media parameters selected | + +### 7.2.2.3 Private call within one MC system + +#### 7.2.2.3.1 Private call setup in automatic commencement mode + +The procedure describes the scenario where an MCVideo user is initiating an MCVideo private call for communicating with another MCVideo user, with or without transmission control enabled, in an automatic commencement mode. + +Procedures in figure 7.2.2.3.1-1 are the basic signalling control plane procedures for the MCVideo client initiating establishment of MCVideo private call with the chosen MCVideo user. + +Pre-conditions: + +1. MCVideo users on MCVideo client 1 and MCVideo client 2 are already registered for receiving MCVideo service. +2. The calling MCVideo user has selected automatic commencement mode for the call; or +3. The called MCVideo client is set to automatic commencement mode. + +![Sequence diagram showing the private call setup in automatic commencement mode between MCVideo client 1, MCVideo server, and MCVideo client 2. The steps are: 1. initiate private call (client 1 to server), 2. MCVideo private call request (client 1 to server), 3. Authorize request (server to client 2), 4. MCVideo progress indication (server to client 1), 5. MCVideo private call request (server to client 2), 6. Notify call (client 2 to server), 7. MCVideo private call response (client 2 to server), 8. MCVideo private call response (server to client 1), 9. Media plane and transmission control is established (server to both clients).](a5252b28ea220e69468dd1d0594e40fe_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MCVideo client 1 + participant Server as MCVideo server + participant Client2 as MCVideo client 2 + Note left of Client1: 1. initiate private call + Client1->>Server: 2. MCVideo private call request + Note right of Server: 3. Authorize request + Server-->>Client1: 4. MCVideo progress indication + Server->>Client2: 5. MCVideo private call request + Note right of Client2: 6. Notify call + Client2->>Server: 7. MCVideo private call response + Server-->>Client1: 8. MCVideo private call response + Note bottom: 9. Media plane and transmission control is established + Server->>Client1: + Server->>Client2: + +``` + +Sequence diagram showing the private call setup in automatic commencement mode between MCVideo client 1, MCVideo server, and MCVideo client 2. The steps are: 1. initiate private call (client 1 to server), 2. MCVideo private call request (client 1 to server), 3. Authorize request (server to client 2), 4. MCVideo progress indication (server to client 1), 5. MCVideo private call request (server to client 2), 6. Notify call (client 2 to server), 7. MCVideo private call response (client 2 to server), 8. MCVideo private call response (server to client 1), 9. Media plane and transmission control is established (server to both clients). + +**Figure 7.2.2.3.1-1: Private call setup in automatic commencement mode– MCVideo users in the same MC system** + +1. User at MCVideo client 1 would like to initiate an MCVideo private call for the chosen MCVideo user. + 2. MCVideo client 1 sends an MCVideo private call request towards the MCVideo server (via SIP core) using a service identifier as defined in 3GPP TS 23.228 [5] for MCVideo, for establishing a private call with the chosen MCVideo user. The MCVideo private call request contains the MCVideo ID of invited user, an SDP offer containing one or more media types. The MCVideo client 1 may include a Requested commencement mode that indicates that the call is to be established in automatic commencement mode if automatic commencement mode is requested by the initiating user. + 3. MCVideo server checks whether the MCVideo user at MCVideo client 1 is authorized to initiate the private call, and that MCVideo user at MCVideo client 2 is authorized to receive the private call. If the MCVideo private call request requested automatic commencement mode then the MCVideo server also checks whether the MCVideo user at MCVideo client 1 is authorized to initiate a private call in automatic commencement mode. + 4. MCVideo server may provide a progress indication to MCVideo client 1 to indicate progress in the call setup process. +- NOTE: Step 4 can occur at any time following step 3, and prior to step 8. +5. If authorized, MCVideo server includes information that it communicates using MCVideo service, offers the same media types or a subset of the media types contained in the initial received request, includes the requested automatic commencement mode indication based on a requested automatic commencement mode by the calling user or based upon the setting of the called MCVideo client and sends the corresponding MCVideo private call request towards the MCVideo client 2, including the MC service ID of the calling MCVideo user 1. If the called MCVideo user has registered to the MCVideo service with multiple MCVideo UEs and has designated the MCVideo UE for receiving the private calls, then the incoming MCVideo private call request is delivered only to the designated MCVideo UE. + 6. The receiving MCVideo client 2 notifies the user about the incoming private call. + 7. The receiving MCVideo client 2 accepts the private call automatically, and an MCVideo private call response is sent to the MCVideo server (via SIP core). + 8. Upon receiving the MCVideo private call response from MCVideo client 2 accepting the private call request, the MCVideo server informs the MCVideo client 1 about successful call establishment. + 9. MCVideo client 1 and MCVideo client 2 have successfully established media plane and transmission control for communication and both users can transmit media. + +### 7.2.2.3.2 Private call setup in manual commencement mode + +#### 7.2.2.3.2.1 Description + +Figure 7.2.2.3.2.2-1 describes the basic procedure for the MCVideo client initiating an MCVideo private call that uses manual commencement mode. The flow may use a transmit media request in the MCVideo private call request indicating that the originator will be granted permission to transmit when the call starts and eliminates the need for a separate initial transmit media request message during media plane establishment. Alternatively the call initiation may be sent without the transmit media request, which allows the called party to transmit media request first. + +#### 7.2.2.3.2.2 Procedure + +Both clients are served by the primary MC service provider in figure 7.2.2.3.2.2-1. + +Pre-conditions: + +1. MCVideo client 1 and MCVideo client 2 are both registered and their respective users, MCVideo user 1 and MCVideo user 2, are authenticated and authorized to use the MCVideo service. +2. The calling MCVideo user has selected manual commencement mode or has not specified a commencement mode for the call; and +3. The called MCVideo client is set to manual commencement mode. + +![Sequence diagram for MCVideo private call in manual commencement mode. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2. The sequence shows the initiation, request, authorization, forwarding, progress indication, ringing, user notification, response, and media plane establishment.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + + Note left of MCVideo client 1: 1. Initiate private call + MCVideo client 1->>MCVideo server: 2. MCVideo private call request + Note right of MCVideo server: 3. MCVideo server verifies that MCVideo client 1 and MCVideo client 2 are authorized to participate in the call + MCVideo server->>MCVideo client 2: 4. MCVideo private call request + MCVideo server-->>MCVideo client 1: 5. MCVideo progress indication + MCVideo client 2->>MCVideo server: 6a. MCVideo ringing + MCVideo server->>MCVideo client 1: 6b. MCVideo ringing + Note right of MCVideo client 2: 7. User is notified and accepts the call + MCVideo client 2->>MCVideo server: 8. MCVideo private call response + MCVideo server->>MCVideo client 1: 9. MCVideo private call response + Note over all: 10. Media plane and transmission control is established + +``` + +Sequence diagram for MCVideo private call in manual commencement mode. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2. The sequence shows the initiation, request, authorization, forwarding, progress indication, ringing, user notification, response, and media plane establishment. + +**Figure 7.2.2.3.2.2-1: MCVideo private call in manual commencement mode– MCVideo users in the same MC system** + +1. MCVideo user at MCVideo client 1 would like to initiate an MCVideo private call for the selected MCVideo user. +2. MCVideo client 1 sends an MCVideo private call request addressed to the MC service ID of MCVideo user 2 using an MCVideo service identifier as defined in 3GPP TS 23.228 [5] (possible for the SIP core to route the request to the MCVideo server). The MCVideo private call request contains the MC service ID of invited user and an SDP offer containing one or more media types. The MCVideo client 1 may include a requested commencement mode that indicates that the call is to be established in manual commencement mode if manual commencement mode is requested by the initiating user. +3. The MCVideo server confirms that both MCVideo users are authorized for the private call. The MCVideo server checks the commencement mode setting of the called MCVideo client and also checks whether the MCVideo user at MCVideo client 1 is authorized to initiate a call in manual commencement mode. +4. The MCVideo server includes information that it communicates using MCVideo service, offers the same media types or a subset of the media types contained in the initial received request and sends an MCVideo private call request for the call to MCVideo client 2, including the MC service ID of the calling MCVideo user 1. If the called MCVideo user has registered to the MCVideo service with multiple MCVideo UEs and has designated the MCVideo UE for receiving the private calls, then the incoming MCVideo private call request is delivered only to the designated MCVideo UE. +5. MCVideo server may provide a progress indication to MCVideo client 1 to indicate progress in the call setup process. + +NOTE: Step 5 can occur at any time following step 3, and prior to step 6b. + +- 6a. The MCVideo user is alerted. MCVideo client 2 sends an MCVideo ringing to the MCVideo server. + +- 6b. The MCVideo server sends an MCVideo ringing to MCVideo client 1, indicating that MCVideo client 2 is being alerted. +7. MCVideo user 2 is notified and has accepted the call using manual commencement mode (i.e., has taken some action to accept via the user interface). +8. The MCVideo client 2 sends an MCVideo private call response to the MCVideo server. If MCVideo user 2 has not accepted the incoming call, the MCVideo client 2 sends a call failure response to the MCVideo server without adding reason for call failure. +9. The MCVideo server sends an MCVideo private call response to MCVideo client 1 indicating that MCVideo user 2 has accepted the call, including the accepted media parameters. +10. The media plane and transmission control for communication is established. + +**7.2.2.3.3 Private call release** + +**7.2.2.3.3.1 Client initiated** + +The procedure describes the scenario where an MCVideo client is requesting to release an ongoing MCVideo private call (with or without transmission control) and the call established in either of the two commencement modes (manual or automatic). + +Procedures in figure 7.2.2.3.3.1-1 are the basic signalling control plane procedures for the MCVideo client initiating the release of an ongoing MCVideo private call. + +Pre-condition: + +1. It is assumed that MCVideo users on MCVideo client 1 and MCVideo client 2 are already registered for receiving MCVideo service and are involved in private call as described in subclause 7.2.2.3.1 and subclause 7.2.2.3.2. + +![Sequence diagram for private call release initiated by client 1. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2. Steps: 1. Release private call (internal), 2. MCVideo call end request (client 1 to server), 3. MCVideo call end request (server to client 2), 4. Notify call termination (internal to client 2), 5. MCVideo call end response (client 2 to server), 6. MCVideo call end response (server to client 1), 7. Media plane and transmission control resources are released (common).](bdd96f20e71f079cad85240efb3d3f24_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MCVideo client 1 + participant Server as MCVideo server + participant Client2 as MCVideo client 2 + Note left of Client1: 1. Release private call + Client1->>Server: 2. MCVideo call end request + Server->>Client2: 3. MCVideo call end request + Note right of Client2: 4. Notify call termination + Client2->>Server: 5. MCVideo call end response + Server->>Client1: 6. MCVideo call end response + Note bottom: 7. Media plane and transmission control resources are released + +``` + +Sequence diagram for private call release initiated by client 1. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2. Steps: 1. Release private call (internal), 2. MCVideo call end request (client 1 to server), 3. MCVideo call end request (server to client 2), 4. Notify call termination (internal to client 2), 5. MCVideo call end response (client 2 to server), 6. MCVideo call end response (server to client 1), 7. Media plane and transmission control resources are released (common). + +**Figure 7.2.2.3.3.1-1: Private call release – client initiated** + +1. User at MCVideo client 1 would like to release an ongoing MCVideo private call with MCVideo client 2. +2. MCVideo client 1 sends an MCVideo call end request towards the MCVideo server (via SIP core), for tearing down the private call with the other client. +3. MCVideo server sends the corresponding MCVideo call end request towards the MCVideo client specified in the original MCVideo call end request. + +4. MCVideo user is notified about the release of the private call. +5. The receiving MCVideo client 2 acknowledges the MCVideo call end request with a MCVideo call end response. +6. After receiving the MCVideo call end response from MCVideo client 2, the MCVideo server generates an MCVideo call end response for the MCVideo client 1's MCVideo call end request. +7. MCVideo clients release all the media plane resources used for the private call. Further, if the private call was established with transmission control, transmission control resources are released. + +**7.2.2.3.3.2 Server initiated** + +The procedure describes the scenario where an MCVideo server is terminating an ongoing MCVideo private call and the call established in either of the two commencement modes (manual or automatic), upon conditions to terminate call e.g., MCVideo administrator configured maximum duration for MCVideo private calls has expired or timed out due to MCVideo private call without transmission/reception. + +Procedures in figure 7.2.2.3.3.2-1 are the basic signalling control plane procedures for the MCVideo server initiating termination of an ongoing MCVideo private call. + +Pre-condition: + +1. It is assumed that MCVideo users on MCVideo client 1 and MCVideo client 2 are already registered for receiving MCVideo service and are involved in private call established either in manual or automatic commencement mode. + +![Sequence diagram showing the server-initiated termination of an MCVideo private call between MCVideo client 1, MCVideo server, and MCVideo client 2.](2438c4dd81a8b76ec881d47d87b11fc3_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant S as MCVideo server + participant C2 as MCVideo client 2 + Note over S: 1. Conditions to trigger +terminate private call + S->>C1: 2. MCVideo call end request + S->>C2: 2. MCVideo call end request + Note over C1: 3. Notify call +termination + Note over C2: 3. Notify call +termination + C1->>S: 4. MCVideo call end response + C2->>S: 4. MCVideo call end response + Note over C1, C2: 5. Media plane and transmission control resources are released + +``` + +Sequence diagram showing the server-initiated termination of an MCVideo private call between MCVideo client 1, MCVideo server, and MCVideo client 2. + +**Figure 7.2.2.3.3.2-1: End private call – server initiated** + +1. Upon conditions to terminate call e.g., MCVideo administrator configured maximum duration for MCVideo private calls has expired or timed out due to MCVideo private call without transmission/reception, the MCVideo server decides to initiate termination of an ongoing MCVideo private call between MCVideo client 1 and MCVideo client 2. +2. MCVideo server sends an MCVideo call end request towards the MCVideo clients 1 and 2 (via SIP core), for tearing down the private call between them. +3. MCVideo users at client 1 and client 2 are notified about the termination of the private call. +4. The MCVideo call end request receiving MCVideo clients 1 and 2 acknowledge the request with MCVideo call end response. +5. MCVideo clients release all the media plane resources used for the private call. Further, if the private call was established with transmission control, transmission control resources are released. + +### 7.2.2.4 MCVideo emergency private call + +#### 7.2.2.4.1 MCVideo emergency private call commencement + +This procedure describes the case where an authorized MCVideo user is initiating an MCVideo emergency private call with unicast signalling for communicating with another MCVideo user. An MCVideo client in the MCVideo emergency state gains elevated access privilege for all of the MCVideo user's mission critical applications. + +Procedures in figure 7.2.2.4.1-1 are the signalling control plane procedures for the MCVideo client initiating establishment of an MCVideo emergency private call. + +Pre-conditions: + +1. Both members of the MCVideo private call belong to the same MCVideo system. +2. The initiating MCVideo client 1 has been configured to send an MCVideo emergency alert prior to initiating an MCVideo emergency private call. + +![Sequence diagram showing the signalling control plane procedures for MCVideo emergency private call commencement between MCVideo client 1, MCVideo server, and MCVideo client 2.](0ea87c5f55e5857d0969bc5ca36dccba_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + Note left of MCVideo client 1: 1. initiate emergency call + MCVideo client 1->>MCVideo server: 2. MCVideo emergency private call request + MCVideo server->>MCVideo client 2: 3. MCVideo emergency private call request + Note right of MCVideo client 2: 4. Notify emergency call + MCVideo client 2->>MCVideo server: 5. MCVideo emergency private call response + Note left of MCVideo server: 6. Bearer priority adjustment + MCVideo server->>MCVideo client 1: 7. MCVideo emergency private call response + Note bottom: 8. Media plane and transmission control establishment + +``` + +Sequence diagram showing the signalling control plane procedures for MCVideo emergency private call commencement between MCVideo client 1, MCVideo server, and MCVideo client 2. + +Figure 7.2.2.4.1-1 MCVideo emergency private call + +1. The user at the MCVideo client 1 initiates an MCVideo emergency private call. MCVideo client 1 sets its MCVideo emergency state. The MCVideo emergency state is retained until explicitly cancelled. +2. MCVideo client 1 sends an MCVideo emergency private call request towards the MCVideo server. The request contains an indication of the MCVideo emergency. The MCVideo server records the identity of the MCVideo user that initiated the MCVideo emergency private call until the MCVideo emergency is cancelled. If the MCVideo client is configured to send an MCVideo emergency alert when initiating an MCVideo emergency private call, the request also contains an indication that an MCVideo emergency alert is to be initiated. +3. MCVideo server sends the MCVideo emergency private call request towards the target MCVideo client. The request contains an indication of the in-progress emergency. The request contains an indication of an MCVideo emergency alert if the request from the originator indicated MCVideo emergency alert. +4. The MCVideo user on MCVideo client 2 is notified of the incoming MCVideo emergency private call. + +5. The receiving MCVideo client acknowledges the MCVideo emergency private call request to the MCVideo server via a MCVideo emergency private call response. +6. The MCVideo server adjusts the priority of the underlying bearer. +7. The MCVideo server informs MCVideo client 1 about the successful MCVideo emergency private call establishment via a MCVideo emergency private call response. +8. MCVideo client 1 and MCVideo client 2 establish the media plane and transmission control for video communication. + +NOTE 1: The priority for the MCVideo emergency private call is retained until cancelled according to system policy (e.g. call end) or cancelled by an authorized MCVideo user. + +NOTE 2: The initiating MCVideo user's MCVideo emergency state is retained by the system until cancelled as in subclause 7.1.2.6. The initiating MCVideo user's MCVideo emergency state is also retained locally by the MCVideo client until explicitly cancelled by the MCVideo user. + +### 7.2.2.4.2 MCVideo private call emergency upgrade + +This procedure describes the case where an authorized MCVideo user is upgrading a private call to an MCVideo emergency private call while the private call is already in progress. + +Procedures in figure 7.2.2.4.2-1 are the signalling procedures for the MCVideo client upgrading a private call to an MCVideo emergency private call. + +Pre-conditions: + +1. Both members of the private call belong to the same MCVideo system. +2. A private call is already in progress. + +![Sequence diagram for MCVideo private call upgrade. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2. The process starts with 'Private call already in progress'. Step 1: 'User initiates emergency' (internal to client 1). Step 2: 'MCVideo emergency private call request' from client 1 to server. Step 3: 'MCVideo emergency private call request' from server to client 2. Step 4: 'Notify emergency status' (internal to client 2). Step 5: 'MCVideo emergency private call response' from client 2 to server. Step 6: 'Bearer priority adjustment' (internal to server). Step 7: 'MCVideo emergency private call response' from server to client 1. Step 8: 'Private call continues as a private emergency call' (internal to client 1).](c8a01394092e8f1fbaf91c81d752d401_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + + Note over MCVideo client 1, MCVideo client 2: Private call already in progress + + Note left of MCVideo client 1: 1. User initiates emergency + MCVideo client 1->>MCVideo server: 2. MCVideo emergency private call request + MCVideo server->>MCVideo client 2: 3. MCVideo emergency private call request + Note right of MCVideo client 2: 4. Notify emergency status + MCVideo client 2->>MCVideo server: 5. MCVideo emergency private call response + Note over MCVideo server: 6. Bearer priority adjustment + MCVideo server->>MCVideo client 1: 7. MCVideo emergency private call response + Note left of MCVideo client 1: 8. Private call continues as a private emergency call + +``` + +Sequence diagram for MCVideo private call upgrade. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2. The process starts with 'Private call already in progress'. Step 1: 'User initiates emergency' (internal to client 1). Step 2: 'MCVideo emergency private call request' from client 1 to server. Step 3: 'MCVideo emergency private call request' from server to client 2. Step 4: 'Notify emergency status' (internal to client 2). Step 5: 'MCVideo emergency private call response' from client 2 to server. Step 6: 'Bearer priority adjustment' (internal to server). Step 7: 'MCVideo emergency private call response' from server to client 1. Step 8: 'Private call continues as a private emergency call' (internal to client 1). + +Figure 7.2.2.4.2-1: MCVideo private call upgrade + +1. The MCVideo user at MCVideo client 1 initiates an emergency. MCVideo client 1 sets its MCVideo emergency state. The MCVideo emergency state is retained until explicitly cancelled. + +2. MCVideo client 1 requests the MCVideo server to upgrade the private call to in-progress emergency by sending an MCVideo emergency private call request. If configured to send an MCVideo alert when initiating an MCVideo emergency upgrade, the request also contains an indication that an MCVideo alert is to be initiated. The request may contain an indication of an implicit transmit media request. +3. MCVideo server sends the MCVideo emergency request towards the MCVideo client of the other participant. +4. The MCVideo user is notified of the in-progress emergency of the MCVideo emergency private call. +5. The receiving MCVideo client acknowledges the MCVideo emergency request to the MCVideo server. +6. The MCVideo server adjusts the priority of the underlying bearer for both participants in the private call. The priority is retained until the call ends. +7. The MCVideo server confirms the upgrade request to MCVideo client 1. If the MCVideo emergency request contained an implicit transmit media request, the MCVideo emergency private call response message contains the result of the implicit transmit media request. +8. MCVideo client 1 and MCVideo client 2 continue with the private call, which has been transformed into an MCVideo emergency private call. + +## 7.2.3 Off-network private communications + +### 7.2.3.1 General + +The private call setup in automatic commencement mode is described in subclause 7.2.3.4, manual commencement mode in subclause 7.2.3.5 and private call release in subclause 7.2.3.6. + +### 7.2.3.2 Information flows for off-network private communications + +#### 7.2.3.2.1 Private communication request + +Table 7.2.3.2.1-1 describes the information flow for the private communication request sent from one MCVideo client to another MCVideo client. + +**Table 7.2.3.2.1-1: Private communication request** + +| Information element | Status | Description | +|-----------------------|--------|------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user requesting the communication | +| MCVideo ID | M | The identity of the MCVideo user with whom communication was requested | +| SDP offer | M | SDP with media information offered by the caller | +| Video push indication | O | Indicates that the MCVideo private communication is for video push | +| Video pull indication | O | Indicates that the MCVideo private communication is for video pull | + +NOTE 1: For video push, 'the identity of the MCVideo user requesting the communication' refers to the user who will be the source of the video, and 'the identity of the MCVideo user with whom the communication was requested' refers to the user who will receive the video. + +NOTE 2: For video pull, 'the identity of the MCVideo user requesting the communication' refers to the user who wants to receive the video, and 'the identity of the MCVideo user with whom the communication was requested' refers to the user who will be the source of the video. + +#### 7.2.3.2.2 Private communication answer response + +Table 7.2.3.2.2-1 describes the information flow for the response of private communication request sent from one MCVideo client to another MCVideo client. + +**Table 7.2.3.2.2-1: Private communication answer response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user requesting the communication | +| MCVideo ID | M | The identity of the MCVideo user with whom communication was requested | +| SDP answer | M | SDP with media information accepted by the callee | + +NOTE 1: For video push, 'the identity of the MCVideo user requesting the communication' refers to the user who will be the source of the video, and 'the identity of the MCVideo user with whom the communication was requested' refers to the user who will receive the video. + +NOTE 2: For video pull, 'the identity of the MCVideo user requesting the communication' refers to the user who wants to receive the video, and 'the identity of the MCVideo user with whom the communication was requested' refers to the user who will be the source of the video. + +### 7.2.3.2.3 Private communication release request + +Table 7.2.3.2.3-1 describes the information flow for the private communication release request sent from one MCVideo client to another MCVideo client. + +**Table 7.2.3.2.3-1: Private communication release request** + +| Information element | Status | Description | +|----------------------------------------------|--------|------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user requesting the communication | +| MCVideo ID | M | The identity of the MCVideo user with whom communication was requested | +| MCVideo private communication release reason | O | Reason for the private communication release. | + +NOTE 1: For video push, 'the identity of the MCVideo user requesting the communication' refers to the user who will be the source of the video, and 'the identity of the MCVideo user with whom the communication was requested' refers to the user who will receive the video. + +NOTE 2: For video pull, 'the identity of the MCVideo user requesting the communication' refers to the user who wants to receive the video, and 'the identity of the MCVideo user with whom the communication was requested' refers to the user who will be the source of the video. + +### 7.2.3.2.4 Private communication release response + +Table 7.2.3.2.4-1 describes the information flow for the private communication release response sent from one MCVideo client to another MCVideo client. + +**Table 7.2.3.2.4-1: Private communication release response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user requesting the communication | +| MCVideo ID | M | The identity of the MCVideo user with whom communication was requested | + +NOTE 1: For video push, 'the identity of the MCVideo user requesting the communication' refers to the user who will be the source of the video, and 'the identity of the MCVideo user with whom the communication was requested' refers to the user who will receive the video. + +NOTE 2: For video pull, 'the identity of the MCVideo user requesting the communication' refers to the user who wants to receive the video, and 'the identity of the MCVideo user with whom the communication was requested' refers to the user who will be the source of the video. + +### 7.2.3.3 Use of **ProSe** for off-network private communications + +To enable an MCVideo user, using a **ProSe**-enabled UE, to communicate with another MCVideo user, using **ProSe**-enabled UE, the MCVideo client retrieves the **ProSe** discovery group ID and user info ID of the target MCVideo user from the "List of user(s) who can be communicated privately" in the MCVideo user profile and requests the IP address of the MCVideo UE associated with the target MCVideo user, from the **ProSe** layer. + +The MCVideo client enables the **ProSe** layer to determine the IP address for the target MCVideo UE by providing the **ProSe** discovery group ID and user info ID (as defined in specification 3GPP **TS 23.303** [7]) of the target MCVideo user. This may trigger the **ProSe** layer procedure (e.g. discovery). The user info ID of the target MCVideo user is used by the **ProSe** layer as the target info (as defined in specification 3GPP **TS 23.303** [7]). The **ProSe** layer can then provide the IP address related to the target MCVideo user's MCVideo ID to the MCVideo client. + +### 7.2.3.4 Automatic commencement private communication + +#### 7.2.3.4.1 General + +A private call request is sent by a MCVideo client directly to another MCVideo client, which checks the request, establishes the MCVideo session without further user interaction and notifies its user that the MCVideo session has been established. + +#### 7.2.3.4.2 Procedure + +Figure 7.2.3.4.2-1 describes procedures to establish an off-network automatic commencement private communication between MCVideo user A MCVideo user B. + +Pre-conditions: + +1. MCVideo user A has initiated automatic commencement private communication with MCVideo user B. +2. MCVideo user B has indicated MCVideo client B as the designated MCVideo client for MCVideo private communications. +3. MCVideo client A and MCVideo client B are members of the same **ProSe** Discovery group and are **ProSe** 1:1 direct communication capable. +4. MCVideo client A has discovered MCVideo client B in proximity, associated with MCVideo user B, using **ProSe** Discovery procedures. + +**Editor's Note: How MCVideo client A determines that MCVideo client B is the designated MCVideo client of MCVideo user B for private communications is FFS.** + +![Sequence diagram illustrating the off-network automatic commencement private communication between MCVideo client A and MCVideo client B.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client A + participant MCVideo client B + Note right of MCVideo client B: 2. Check if the MCVideo client is the designated client + Note right of MCVideo client B: 3b. Notify MCVideo user + Note over MCVideo client A, MCVideo client B: 4. Establish media plane + + MCVideo client A->>MCVideo client B: 1. Private communication request + MCVideo client B->>MCVideo client A: 3a. Private communication answer response + Note right of MCVideo client B: 3b. Notify MCVideo user + Note over MCVideo client A, MCVideo client B: 4. Establish media plane + Note over MCVideo client A, MCVideo client B: 5. Video Transmission from MCVideo client A to MCVideo client B + +``` + +The diagram shows a sequence of interactions between MCVideo client A and MCVideo client B. + 1. MCVideo client A sends a 'Private communication request' to MCVideo client B. + 2. MCVideo client B receives the request and checks if it is the designated client (shown in a box). + 3a. MCVideo client B sends a 'Private communication answer response' back to MCVideo client A. + 3b. MCVideo client B also notifies its associated MCVideo user (shown in a box). + 4. Both clients then proceed to 'Establish media plane' (shown in a box spanning both lifelines). + 5. Finally, 'Video Transmission from MCVideo client A to MCVideo client B' occurs, indicated by a large arrow. + +Sequence diagram illustrating the off-network automatic commencement private communication between MCVideo client A and MCVideo client B. + +**Figure 7.2.3.4.2-1: Off-network automatic commencement private communication** + +1. The MCVideo client A sends the Private communication request towards MCVideo client associated with MCVideo user B. The Private communication request contains an indication for automatic commencement and the SDP offer. + 2. On receiving a Private communication request with an indication for automatic commencement, the MCVideo client checks if it is the designated MCVideo client for off-network MCVideo private communications. + - 3a. The designated MCVideo client B automatically accepts the Private communication request, and sends a Private communication answer response, indicating the successful receipt of communication request to the MCVideo client A. The Private communication answer response contains the SDP answer. + - 3b. The designated MCVideo client B notifies the MCVideo user B about the incoming Private communication request. +- NOTE 1: Step 3a and step 3b can occur in any order. +4. The MCVideo client A and the MCVideo client B establish the media plane for Private Communication. +- NOTE 2: If a MCVideo client fails to establish the communication, the MCVideo client should send a Private communication failed response indicating the failure reason to the appropriate MCVideo client. +5. MCVideo media is transmitted from the MCVideo client A to the MCVideo client B and is presented to the MCVideo user B. + +NOTE 3: If a Private communication failed response is received by a MCVideo client, before or after establishing the media session, if already established, the session is terminated and the MCVideo user is notified about the failure and its reason, if any. + +### 7.2.3.5 Manual commencement private communication + +#### 7.2.3.5.1 General + +A private call request is sent by a MCVideo client directly to another MCVideo client, which checks the request, establishes the MCVideo session without further user interaction and notifies its user about the incoming MCVideo session request. The MCVideo user may accept, reject or ignore the MCVideo session request. + +#### 7.2.3.5.2 Procedure – Communication accepted + +Figure 7.2.3.5.2-1 describes procedures to establish an off-network manual commencement private communication between MCVideo user A MCVideo user B, which is accepted by the MCVideo user B. + +Pre-conditions: + +1. MCVideo user A has initiated manual commencement private communication with MCVideo user B. +2. MCVideo user B has indicated MCVideo client B as the designated MCVideo client for MCVideo private communications, if the MCVideo user B has signed on to the MCVideo service with multiple MCVideo clients. +3. MCVideo client A and MCVideo client B are members of the same **ProSe** Discovery group and are **ProSe** 1:1 direct communication capable. +4. MCVideo client A has discovered MCVideo clients B in proximity, associated with MCVideo user B, using **ProSe** Discovery procedures. + +**Editor's Note:** How MCVideo client A determines that MCVideo client B is the designated MCVideo client of MCVideo user B for private communications is FFS. + +![Sequence diagram illustrating the off-network manual commencement private communication process between MCVideo client A and MCVideo client B.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +``` + +sequenceDiagram + participant A as MCVideo client A + participant B as MCVideo client B + A->>B: 1. Private communication request + Note right of B: 2. Check if the MCVideo client is +the designated client + Note right of B: 3a. Present incoming +communication +request + B-->>A: 3b. Private communication ringing response + Note left of A: 4. Notify MCVideo +user that the +request is +presented + Note right of B: 5. User answers + B->>A: 6. Private communication answer response + rect rgb(255, 255, 255) + Note over A,B: 7. Establish media plane + end + A->>B: 8. Video Transmission from MCVideo client A to MCVideo client B + +``` + +Sequence diagram illustrating the off-network manual commencement private communication process between MCVideo client A and MCVideo client B. + +**Figure 7.2.3.5.2-1: Off-network manual commencement private communication – Accepted** + +1. The MCVideo client A sends the Private communication request towards MCVideo client associated with MCVideo user B. The Private communication request contains an indication for manual commencement and the SDP offer. + 2. On receiving a Private communication request, the MCVideo client checks if it is the designated MCVideo client for off-network MCVideo private communications. + - 3a. The designated MCVideo client B presents the incoming Private communication request to the MCVideo user B. + - 3b. The MCVideo client B sends back a Private communication ringing response to the MCVideo client A. +- NOTE 1: Step 3a and step 3b can occur in any order. +4. The MCVideo client A notifies the ringing status to the MCVideo user A. + 5. The MCVideo user B accepts the Private communication request. + 6. The MCVideo client B sends the Private communication answer response to the MCVideo client A. The Private communication response contains the SDP answer. + 7. The MCVideo client A and the MCVideo client B establish the media plane for Private communication. + +NOTE 2: If a MCVideo client fails to establish the communication, the MCVideo client should send a Private communication failed response indicating the failure reason to the appropriate MCVideo client. + +- 8. MCVideo media is transmitted from the MCVideo client A to the MCVideo client B and is presented to the MCVideo user B. + +NOTE 3: If a Private communication failed response is received by a MCVideo client, before or after establishing the media session, if already established, the session is terminated and the MCVideo user is notified about the failure and its reason, if any. + +**7.2.3.5.3 Procedure – Communication rejected/ignored** + +Figure 7.2.3.5.3-1 describes procedures to initiate an off-network manual commencement private communication between MCVideo user A MCVideo user B, which is rejected or ignored by the MCVideo user B. + +Pre-conditions: + +- 1. MCVideo user A has initiated manual commencement private communication with MCVideo user B. +- 2. MCVideo user B has indicated MCVideo client B as the designated MCVideo client for MCVideo Private Communications, if the MCVideo user B has signed on to the MCVideo service with multiple MCVideo clients. +- 3. MCVideo client A and MCVideo client B are members of the same **ProSe** Discovery group and are **ProSe** 1:1 direct communication capable. +- 4. MCVideo client A has discovered MCVideo clients B in proximity, associated with MCVideo user B, using **ProSe** Discovery procedures. + +**Editor's Note: How MCVideo client A determines that MCVideo client B is the designated MCVideo client of MCVideo user B for private communications is FFS.** + +![Sequence diagram showing the procedure for off-network manual commencement private communication between MCVideo client A and MCVideo client B. The steps are: 1. Private communication request from A to B; 2. Check if the MCVideo client is the designated client (internal to B); 3a. Present incoming communication request (internal to B); 3b. Private communication ringing response from B to A; 4. Notify MCVideo user that the request is presented (internal to A); 5. User rejects or ignores (internal to B); 6. Private communication reject response from B to A; 7. Notify MCVideo user that the request is rejected or ignored (internal to A).](453a1dc18dd2dd3334d19f453b04d11b_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client A + participant MCVideo client B + Note right of MCVideo client B: 2. Check if the MCVideo client is the designated client + Note right of MCVideo client B: 3a. Present incoming communication request + Note left of MCVideo client A: 4. Notify MCVideo user that the request is presented + Note right of MCVideo client B: 5. User rejects or ignores + Note left of MCVideo client A: 7. Notify MCVideo user that the request is rejected or ignored + MCVideo client A->>MCVideo client B: 1. Private communication request + MCVideo client B-->>MCVideo client A: 3b. Private communication ringing response + MCVideo client B-->>MCVideo client A: 6. Private communication reject response + +``` + +Sequence diagram showing the procedure for off-network manual commencement private communication between MCVideo client A and MCVideo client B. The steps are: 1. Private communication request from A to B; 2. Check if the MCVideo client is the designated client (internal to B); 3a. Present incoming communication request (internal to B); 3b. Private communication ringing response from B to A; 4. Notify MCVideo user that the request is presented (internal to A); 5. User rejects or ignores (internal to B); 6. Private communication reject response from B to A; 7. Notify MCVideo user that the request is rejected or ignored (internal to A). + +**Figure 7.2.3.5.3-1: Off-network manual commencement private communication – Rejected or Ignored** + +1. The MCVideo client A sends the private communication request towards MCVideo client associated with MCVideo user B. The private communication request contains an indication for manual commencement and the SDP offer. + 2. On receiving a Private communication request, the MCVideo client checks if it is the designated MCVideo client for off-network MCVideo private communications. + - 3a. The designated MCVideo client B presents the incoming Private communication request to the MCVideo user B. + - 3b. The MCVideo client B sends back a Private communication ringing response to the MCVideo client A. +- NOTE 1: Step 3a and step 3b can occur in any order. +4. The MCVideo client A notifies the ringing status to the MCVideo user A. + 5. The MCVideo user B rejects (or ignores) the Private communication request. +- NOTE 2: The MCVideo client B determines that the MCVideo user B has ignored the Private communication request, if the MCVideo user B does not respond within a configured time limit. +6. The MCVideo client B sends a Private communication reject response to the MCVideo client A. The Private communication reject response may indicate that the MCVideo user B has ignored the Private communication request. + 7. The MCVideo client A notifies the MCVideo user A that the Private communication request was rejected (or ignored). + +### 7.2.3.6 Private communication release + +#### 7.2.3.6.1 General + +Either of the MCVideo users involved in a private communication may release the unidirectional media plane or the whole private communication at any time. + +#### 7.2.3.6.2 Procedure + +Figure 7.2.3.6.2-1 describes procedures to release an ongoing MCVideo Private communication (either automatic commencement private communication or manual commencement private communication). + +Either of the MCVideo users, the initiator or the receiver of the Private communication can request to release the Private communication. + +The Private communication release request can be to release an individual (unidirectional) media plane or to terminate the Private communication. Based on the request the requested media plane or both the media planes are terminated in step 3. + +Pre-conditions: + +1. MCVideo client A and MCVideo client B are engaged in a Private communication. +2. MCVideo user A at MCVideo client A initiates release of the Private communication. + +![Sequence diagram for Off-network Private communication release. The diagram shows three main steps: 1. MCVideo client A sends a 'Private communication release request' to MCVideo client B. 2a. MCVideo client B sends a 'Private communication release response' back to MCVideo client A. 2b. MCVideo client B sends a 'Notify MCVideo user' message to the MCVideo user. 3. Both MCVideo client A and MCVideo client B perform a 'Release media plane' action.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client A + participant MCVideo client B + participant MCVideo user + Note right of MCVideo client B: 2b. Notify MCVideo user + MCVideo client A->>MCVideo client B: 1. Private communication release request + MCVideo client B-->>MCVideo client A: 2a. Private communication release response + MCVideo client B->>MCVideo user: 2b. Notify MCVideo user + Note left of MCVideo client A: 3. Release media plane + Note right of MCVideo client B: 3. Release media plane + +``` + +Sequence diagram for Off-network Private communication release. The diagram shows three main steps: 1. MCVideo client A sends a 'Private communication release request' to MCVideo client B. 2a. MCVideo client B sends a 'Private communication release response' back to MCVideo client A. 2b. MCVideo client B sends a 'Notify MCVideo user' message to the MCVideo user. 3. Both MCVideo client A and MCVideo client B perform a 'Release media plane' action. + +**Figure 7.2.3.6.2-1: Off-network Private communication release** + +- 1, The MCVideo client A sends the Private communication release request to the MCVideo client B. + - 2a. The MCVideo client B sends a Private communication release response indicating successful receipt of the request to the MCVideo client A. + - 2b. The MCVideo client B notifies the MCVideo user B about the Private communication release request. +- NOTE: Step 2a and step 2b can occur in any order. +3. MCVideo client A and MCVideo client B release the requested media plane. If both the media planes are released, the Private communication is terminated. + +## 7.3 Video pull + +### 7.3.1 General + +MCVideo pull is enabled in both on-network and off-network mode. + +For on-network MCVideo pull is supported between MCVideo clients, or between a MCVideo client and a MCVideo server. + +For off-network MCVideo pull is supported between MCVideo clients only. + +### 7.3.2 On-network video pull + +#### 7.3.2.1 General + +A MCVideo user triggers its MCVideo client to pull a video either from another MCVideo client or from a MCVideo server. + +#### 7.3.2.2 Information flows for on-network video pull + +The following information flows for private call specified in subclause 7.2.2.2 is used for on-network video pull: + +- MCVideo private call request (MCVideo client – MCVideo server) +- MCVideo private call request (MCVideo server – MCVideo client) +- MCVideo private call response (MCVideo client – MCVideo server) + +- MCVideo private call response (MCVideo server – MCVideo client) +- MCVideo call end request + +#### 7.3.2.2.1 MCVideo pull from server request + +Table 7.3.2.2.1-1 describes the information flow MCVideo pull from server request from the MCVideo client to the MCVideo server. + +**Table 7.3.2.2.1-1: MCVideo pull from server request** + +| Information Element | Status | Description | +|---------------------|--------|--------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| File URL | M | URL of the video file to be streamed | +| SDP offer | M | Media parameters of MCVideo client | + +#### 7.3.2.2.2 MCVideo pull from server response + +Table 7.3.2.2.2-1 describes the information flow MCVideo pull from server response from the MCVideo server to the MCVideo client. + +**Table 7.3.2.2.2-1: MCVideo pull from server response** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| SDP answer | M | Media parameters selected | + +#### 7.3.2.2.3 MCVideo pull from server complete request + +Table 7.3.2.2.3-1 describes the information flow MCVideo pull from server complete request from the MCVideo client to the MCVideo server or from the MCVideo server to the MCVideo client.. + +**Table 7.3.2.2.3-1: MCVideo pull from server complete request** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| Cause | M | End of communication cause | + +#### 7.3.2.2.4 MCVideo pull from server complete response + +Table 7.3.2.2.4-1 describes the information flow MCVideo pull from server complete response from the MCVideo client to the MCVideo server or from the MCVideo server to the MCVideo client.. + +**Table 7.3.2.2.4-1: MCVideo pull from server complete response** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | + +### 7.3.2.3 One-to-one video pull + +#### 7.3.2.3.1 General + +One-to-one video pull is a private call that only allows the called party to transmit video to the calling party, and the private call ends when the video transmission is completed. + +### 7.3.2.3.2 One-to-one video pull – call setup + +The procedure describes the case where an MCVideo user is initiating an MCVideo private call to pull video from called MCVideo user in an automatic or manual commencement mode. Only the called party is allowed to transmit video. + +Procedures in figure 7.3.2.3.2-1 are the basic signalling control plane procedures for the MCVideo client initiating establishment of MCVideo private call with the chosen MCVideo user for video pull. + +![Sequence diagram for One-to-one video pull call setup. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2. Steps: 1. Private call request (client 1 to server), 2. Authorization check (server internal), 3. Private call progress indication (server to client 1), 4. Private call request (server to client 2), 5. Notify user (client 2 internal), 6. Private call response (client 2 to server), 7. Private call response (server to client 1), 8. Media plane and transmission control established (between client 1 and 2).](907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + Note right of MCVideo server: 2. Authorization check + Note right of MCVideo client 2: 5. Notify user + MCVideo client 1->>MCVideo server: 1. Private call request + MCVideo server-->>MCVideo client 1: 3. Private call progress indication + MCVideo server->>MCVideo client 2: 4. Private call request + MCVideo client 2-->>MCVideo server: 6. Private call response + MCVideo server-->>MCVideo client 1: 7. Private call response + Note over MCVideo client 1, MCVideo client 2: 8. Media plane and transmission control established + +``` + +Sequence diagram for One-to-one video pull call setup. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2. Steps: 1. Private call request (client 1 to server), 2. Authorization check (server internal), 3. Private call progress indication (server to client 1), 4. Private call request (server to client 2), 5. Notify user (client 2 internal), 6. Private call response (client 2 to server), 7. Private call response (server to client 1), 8. Media plane and transmission control established (between client 1 and 2). + +**Figure 7.3.2.3.2-1: One-to-one video pull** + +1. MCVideo user on MCVideo client 1 initiates video pull from MCVideo client 2, by sending a private call request to the MCVideo server using a service identifier as defined in 3GPP TS 23.228 [5] for MCVideo, for establishing a private call with the chosen MCVideo user for video pull. The MCVideo private call request contains MCVideo ID of invited user, an SDP offer containing one or more media types and the video pull indication to indicate that invited user is requested to transmit video to the requester. +2. MCVideo server checks whether the MCVideo user at MCVideo client 1 is authorized to initiate the private call for video pull, and that MCVideo user at MCVideo client 2 is authorized to receive the private call for video pull. +3. MCVideo server may provide a progress indication to MCVideo client 1 to indicate progress in the call setup process. +4. If authorized, MCVideo server includes information that it communicates using MCVideo service, offers the same media types or a subset of the media types contained in the initial received request, includes the requested automatic commencement mode indication based on a requested commencement mode by the calling user or based upon the setting of the called MCVideo client and sends the corresponding MCVideo private call request towards the MCVideo client 2, including the MCVideo ID of the calling MCVideo user 1. If the called MCVideo user has registered to the MCVideo service with multiple MCVideo UEs and has designated the MCVideo UE for receiving the private calls, then the incoming MCVideo private call request is delivered only to the designated MCVideo UE. +5. The MCVideo client 2 notifies the user about the incoming private call for video pull. +6. The receiving MCVideo client 2 accepts the private call for video pull, and sends an MCVideo private call response to the MCVideo server with an implicit transmit media request. +7. Upon receiving the MCVideo private call response from MCVideo client 2 accepting the private call request for video pull, the MCVideo server informs the MCVideo client 1 about successful call establishment via a private call response message. +8. MCVideo client 1 and MCVideo client 2 have successfully established media plane and transmission control for media communication. + +NOTE 1: Step 3 can occur at any time following step 4, and prior to step 6. + +NOTE 2: When the video transmission is completed, the private call is released. + +### 7.3.2.3.3 One-to-one video pull – call release + +The private call release procedure specified in subclause 7.2.2.3.3 is used for one-to-one video pull call release. + +### 7.3.2.4 One-from-server video pull + +#### 7.3.2.4.1 General + +One-from-server video pull is a private call between the calling party and the MCVideo server that allows the calling party to request streaming of a video from the server where it is stored in a file. The one-from-server video pull ends typically when the end of the video file has been reached or when the transmission is stopped by the calling user or by the MCVideo server. + +NOTE: This procedure fulfills the requirements for the stage 1 replay of stored video feature. + +#### 7.3.2.4.2 Procedure + +Procedure in figure 7.3.2.4.2-1 is the basic signalling control plane procedures for the MCVideo client initiating establishment of MCVideo video pull from the MCVideo server. + +Pre-conditions: + +- 1. MCVideo user 1 on MCVideo client 1 has been authenticated and authorized to use MCVideo service. +- 2. MCVideo client 1 is registered. +- 3. MCVideo client 1 has been received the URL of a video file available on the MCVideo server, e.g. within an MCData SDS. + +![Sequence diagram showing the interaction between MCVideo client 1 and MCVideo server for a one-from-server video pull. The steps are: 1. MCVideo push to server request, 2. Authorization check, 3. MCVideo push to server response, 4. Media plane and transmission control established, 5. Video stream from MCVideo client 1, 6. MCVideo push to server complete request, 7. MCVideo push to server complete response.](387a5f91aee45a659456a67b070bc047_img.jpg) + +``` + +sequenceDiagram + participant Client as MCVideo client 1 + participant Server as MCVideo server + Note right of Server: 2. Authorization check + Note left of Client: 4. Media plane and transmission control established + Note right of Client: 5. Video stream from MCVideo client 1 + + Client->>Server: 1. MCVideo push to server request + Server-->>Server: 2. Authorization check + Server-->>Client: 3. MCVideo push to server response + Note left of Client: 4. Media plane and transmission control established + Note right of Client: 5. Video stream from MCVideo client 1 + Note right of Client: 6. MCVideo push to server complete request + Note right of Client: 7. MCVideo push to server complete response + +``` + +Sequence diagram showing the interaction between MCVideo client 1 and MCVideo server for a one-from-server video pull. The steps are: 1. MCVideo push to server request, 2. Authorization check, 3. MCVideo push to server response, 4. Media plane and transmission control established, 5. Video stream from MCVideo client 1, 6. MCVideo push to server complete request, 7. MCVideo push to server complete response. + +Figure 7.3.2.4.2-1: One-from-server video pull + +- 1. MCVideo user on MCVideo client 1 initiates the pull of a video from the server and sends an MCVideo pull from server request to the MCVideo server. The request contains the URL of the video file and an SDP offer with media description.. +- 2. MCVideo server checks whether MCVideo client 1 is authorized to pull the requested video from the server. + +3. MCVideo server accepts the pull from server request and sends an MCVideo pull from server response. The response contains the SDP answer. + +NOTE 1: The SDP may contain a media description that allows the receiving party to remote control the stream (e.g. rewind, fast forward). + +4. MCVideo client 1 and MCVideo server have successfully established the media plane and transmission control for the video stream. +5. Video stream is transmitted from MCVideo server to MCVideo client 1. The MCVideo client 1 may be able to remote control the video stream, subject to SDP negotiation. +6. MCVideo user on MCVideo client 1 stops the video pull from the server and sends an MCVideo pull from server complete request. +7. MCVideo server acknowledges the end of the communication. + +NOTE 2: Alternatively, based on internal criteria (e.g. maximum duration of the video playback, end of the video file), the MCVideo server can end the transmission. + +### 7.3.3 Off-network video pull + +#### 7.3.3.1 General + +A MCVideo client pulls a video from another MCVideo client directly, i.e. without involving the network. + +#### 7.3.3.2 Information flows for off-network video pull + +The following information flows for private call specified in subclause 7.2.3.2 are used for off-network video pull: + +- Private communication request; and +- Private communication answer response. + +#### 7.3.3.3 Video pull to self + +##### 7.3.3.3.1 General + +A MCVideo user requests another MCVideo user to deliver a video from its MCVideo client. + +##### 7.3.3.3.2 Procedure + +Figure 7.3.3.3.2-1 describes procedures for an off-network MCVideo video pull, initiated by MCVideo user A at MCVideo client A with another MCVideo client B, to pull a video to MCVideo client A. + +MCVideo client B can be an autonomous MCVideo client or can be a human controlled MCVideo client. In either case, following procedure should be followed. + +Pre-conditions: + +1. MCVideo user A has initiated MCVideo video pull with MCVideo user B. +2. MCVideo client A and MCVideo client B are members of the same **ProSe** Discovery group and are **ProSe** 1:1 direct communication capable. +3. MCVideo client A has discovered MCVideo client B in proximity, associated with MCVideo user B, using **ProSe** Discovery procedures. + +![Sequence diagram for Off-network video pull to self. The diagram shows interactions between MCVideo client A, MCVideo client B, and MCVideo users. Step 1: MCVideo client A sends a 'Private communication request (Video Pull)' to MCVideo client B. Step 2a: MCVideo client B sends a 'MCVideo Pull notification to the MCVideo user'. Step 2b: MCVideo client B sends a 'Private communication answer response (Video Pull)' to MCVideo client A. Step 3: MCVideo client A sends a 'Notify response to MCVideo user'. Step 4: A box labeled 'Establish media plane' spans between the clients. Step 5: A large arrow points from MCVideo client B to MCVideo client A, labeled 'Video from MCVideo client B to MCVideo client A'.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client A + participant MCVideo client B + participant MCVideo user A + participant MCVideo user B + + Note left of MCVideo client A: MCVideo user A + Note right of MCVideo client B: MCVideo user B + + MCVideo client A->>MCVideo client B: 1. Private communication request (Video Pull) + MCVideo client B->>MCVideo user B: 2a. MCVideo Pull notification to the MCVideo user + MCVideo client B->>MCVideo client A: 2b. Private communication answer response (Video Pull) + MCVideo client A->>MCVideo user A: 3. Notify response to MCVideo user + Note over MCVideo client A, MCVideo client B: 4. Establish media plane + MCVideo client B->>MCVideo client A: 5. Video from MCVideo client B to MCVideo client A + +``` + +Sequence diagram for Off-network video pull to self. The diagram shows interactions between MCVideo client A, MCVideo client B, and MCVideo users. Step 1: MCVideo client A sends a 'Private communication request (Video Pull)' to MCVideo client B. Step 2a: MCVideo client B sends a 'MCVideo Pull notification to the MCVideo user'. Step 2b: MCVideo client B sends a 'Private communication answer response (Video Pull)' to MCVideo client A. Step 3: MCVideo client A sends a 'Notify response to MCVideo user'. Step 4: A box labeled 'Establish media plane' spans between the clients. Step 5: A large arrow points from MCVideo client B to MCVideo client A, labeled 'Video from MCVideo client B to MCVideo client A'. + +**Figure 7.3.3.3.2-1: Off-network video pull to self** + +1. The MCVideo client A sends a Private communication request towards the MCVideo client B. The Private communication request includes a video pull request and indicates MCVideo client A as the intended recipient of the video pull. Private communication request contains the SDP offer. +- 2a. The MCVideo client B notifies the MCVideo user B about the incoming video pull request. +- 2b. The MCVideo client B automatically accepts the video pull request, and sends a Private communication answer response indicating the acceptance of the video pull request. The Private communication answer response contains SDP answer. + +NOTE 1: Step 2a and step 2b can occur in any order. + +3. The MCVideo client A notifies MCVideo user A about the incoming Private communication answer response as an indication of acceptance of MCVideo video pull request. +4. The MCVideo client A and the MCVideo client B establish the media plane for communication. + +NOTE 2: If a MCVideo client fails to establish the communication, the MCVideo client should send a Private communication failed response indicating the failure reason to the appropriate MCVideo client. + +5. Media is transmitted from MCVideo client B to MCVideo client A and presented to the MCVideo user A. + +NOTE 3: If a Private communication failed response is received by a MCVideo client, before or after establishing the media session, if already established, the session is terminated and the MCVideo user is notified about the failure and its reason, if any. + +## 7.4 Video push + +### 7.4.1 General + +MCVideo push is enabled in both on-network and off-network mode. + +For on-network MCVideo push is supported between MCVideo clients, or between a MCVideo client and a MCVideo server. + +For off-network MCVideo push is supported between MCVideo clients only. + +### 7.4.2 On-network video push + +#### 7.4.2.1 General + +A MCVideo user triggers its MCVideo client to push a video to another MCVideo client or a MCVideo server. + +A MCVideo user triggers its MCVideo client to trigger a remote video push, i.e. a second MCVideo client pushes a video to a third MCVideo client or to a MCVideo group. + +#### 7.4.2.2 Information flows for on-network video push + +The following information flows for private call specified in subclause 7.2.2.2 is used for on-network video push: + +- MCVideo private call request (MCVideo client – MCVideo server) +- MCVideo private call request (MCVideo server – MCVideo client) +- MCVideo private call response (MCVideo client – MCVideo server) +- MCVideo private call response (MCVideo server – MCVideo client) +- MCVideo call end request + +##### 7.4.2.2.1 Remote video push request + +Table 7.4.2.2.1-1 describes the information flow remote video push request from the MCVideo client to the MCVideo server and from the MCVideo server to the MCVideo client. + +**Table 7.4.2.2.1-1: Remote video push request** + +| Information Element | Status | Description | +|-----------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the call originating party | +| MCVideo ID | M | The MCVideo ID of the source party who should transmit media | +| MCVideo ID | O (see NOTE) | The MCVideo ID of the destination party who should receive media | +| MCVideo group ID | O (see NOTE) | The MCVideo group ID of the destination group whose affiliated group members should receive media | +| SDP offer | O | Media parameters of MCVideo client. | +| Requested commencement mode | O | An indication that is included if the user is requesting a particular commencement mode | +| NOTE: | | MCVideo ID information element is present if remote video push to destination user is requested. MCVideo group ID information element is present if remote video push to group is requested. | + +#### 7.4.2.2.2 Remote video push response + +Table 7.4.2.2.2-1 describes the information flow remote video push request from the MCVideo server to the MCVideo client and from the MCVideo client to the MCVideo server. + +**Table 7.4.2.2.2-1: Remote video push response** + +| Information Element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the call originating party | +| MCVideo ID | M | The MCVideo ID of the source party who should transmit media | +| MCVideo ID | O (see NOTE) | The MCVideo ID of the destination party who should receive media | +| MCVideo group ID | O (see NOTE) | The MCVideo group ID of the destination group whose affiliated group members should receive media | +| Acceptance confirmation | O | An indication whether the user or group members have positively accepted the call. | +| SDP answer | M | Media parameters selected | +| NOTE: MCVideo ID information element is present if remote video push to destination user is requested. MCVideo group ID information element is present if remote video push to group is requested. | | | + +#### 7.4.2.2.3 Remote video push release request + +Table 7.4.2.2.3-1 describes the information flow Remote video push release request from the MCVideo client to the MCVideo server and from the MCVideo server to the MCVideo client. + +**Table 7.4.2.2.3-1: Remote video push release request** + +| Information Element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the call originating party | +| MCVideo ID | M | The MCVideo ID of the source party who should transmit media | +| MCVideo ID | O (see NOTE) | The MCVideo ID of the destination party who should receive media | +| MCVideo group ID | O (see NOTE) | The MCVideo group ID of the destination group whose affiliated group members should receive media | +| NOTE: MCVideo ID information element is present if remote video push to destination user is requested. MCVideo group ID information element is present if remote video push to group is requested. | | | + +#### 7.4.2.2.4 MCVideo push to server request + +Table 7.4.2.2.4-1 describes the information flow MCVideo push to server request from the MCVideo client to the MCVideo server. + +**Table 7.4.2.2.4-1: MCVideo push to server request** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| Time limit | O | Requested duration of the stream to be recorded | +| SDP offer | M | Media parameters of MCVideo client | + +#### 7.4.2.2.5 MCVideo push to server response + +Table 7.4.2.2.5-1 describes the information flow MCVideo push to server response from the MCVideo server to the MCVideo client. + +**Table 7.4.2.2.5-1: MCVideo push to server response** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| Time limit | O | Accepted or imposed duration limit of the stream to be recorded | +| File URL | M | URL of the file the stream will be recorded to | +| SDP answer | M | Media parameters selected | + +#### 7.4.2.2.6 MCVideo push to server complete request + +Table 7.4.2.2.6-1 describes the information flow MCVideo push to server complete request from the MCVideo client to the MCVideo server or from the MCVideo server to the MCVideo client. + +**Table 7.4.2.2.6-1: MCVideo push to server complete request** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | +| Cause | M | End of communication cause | + +#### 7.4.2.2.7 MCVideo push to server complete response + +Table 7.4.2.2.7-1 describes the information flow MCVideo push to server complete response from the MCVideo client to the MCVideo server or from the MCVideo server to the MCVideo client. + +**Table 7.4.2.2.7-1: MCVideo push to server complete response** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------| +| MCVideo ID | M | The MCVideo ID of the calling party | + +### 7.4.2.3 One-to-one video push + +#### 7.4.2.3.1 General + +One-to-one video push is a private call that only allows the calling party to transmit video to the called party, and the private call ends when the video transmission is completed. + +#### 7.4.2.3.2 One-to-one video push – call setup + +Procedures in figure 7.4.2.3.2-1 are the basic signalling control plane procedures for the MCVideo client initiating establishment of MCVideo private call with the chosen MCVideo user for video push. + +Pre-conditions: + +This procedure is initiated either manually by the authorized MCVideo users at MCVideo client 1, or automatically due to triggers set by authorized MCVideo users at MCVideo client 1. + +![Sequence diagram for One-to-one video push. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2. Steps: 1. Private call request (client 1 to server); 2. Authorization check (server internal); 3. Private call progress indication (server to client 1, dashed line); 4. Private call request (server to client 2); 5. Notify user (client 2 internal); 6. Private call response (client 2 to server); 7. Private call response (server to client 1); 8. Media plane and transmission control established (client 1 and client 2).](1c79f31a718d63814feb28ab46f64f19_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + Note right of MCVideo server: 2. Authorization check + MCVideo client 1->>MCVideo server: 1. Private call request + MCVideo server-->>MCVideo client 1: 3. Private call progress indication + MCVideo server->>MCVideo client 2: 4. Private call request + Note right of MCVideo client 2: 5. Notify user + MCVideo client 2->>MCVideo server: 6. Private call response + MCVideo server->>MCVideo client 1: 7. Private call response + Note over MCVideo client 1, MCVideo client 2: 8. Media plane and transmission control established + +``` + +Sequence diagram for One-to-one video push. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2. Steps: 1. Private call request (client 1 to server); 2. Authorization check (server internal); 3. Private call progress indication (server to client 1, dashed line); 4. Private call request (server to client 2); 5. Notify user (client 2 internal); 6. Private call response (client 2 to server); 7. Private call response (server to client 1); 8. Media plane and transmission control established (client 1 and client 2). + +**Figure 7.4.2.3.2-1: One-to-one video push** + +1. MCVideo client 1 initiates push video to MCVideo client 2, and sends a private call request to the MCVideo server using a service identifier as defined in 3GPP TS 23.228 [5] for MCVideo, for establishing a private call with the chosen MCVideo user for video push. The MCVideo private call request contains MCVideo ID of invited user, an SDP offer containing one or more media types and the video push indication to indicate that requestor is requesting to transmit video to the called party. +2. MCVideo server checks whether the MCVideo user at MCVideo client 1 is authorized to initiate the private call for video push, and that MCVideo user at MCVideo client 2 is authorized to receive the private call for video push. +3. MCVideo server may provide a progress indication to MCVideo client 1 to indicate progress in the call setup process. +4. If authorized, MCVideo server includes information that it communicates using MCVideo service, offers the same media types or a subset of the media types contained in the initial received request, includes the requested automatic commencement mode indication based on a requested commencement mode by the calling user or based upon the setting of the called MCVideo client and sends the corresponding MCVideo private call request towards the MCVideo client 2, including the MCVideo ID of the calling MCVideo user 1. If the called MCVideo user has registered to the MCVideo service with multiple MCVideo UEs and has designated the MCVideo UE for receiving the private calls, then the incoming MCVideo private call request is delivered only to the designated MCVideo UE. +5. The MCVideo client 2 notifies the user about the incoming private call for video push. +6. The MCVideo client 2 accepts the private call for video push, and sends an MCVideo private call response to the MCVideo server. +7. Upon receiving the MCVideo private call response from MCVideo client 2 accepting the private call request for video push, the MCVideo server informs the MCVideo client 1 about successful call establishment via a private call response message. +8. MCVideo client 1 and MCVideo client 2 have successfully established media plane and transmission control for media communication. + +NOTE 2: When the video transmission is completed, the private call is released. + +#### 7.4.2.3.3 One-to-one video push – call release + +The private call release procedure specified in subclause 7.2.2.3.3 is used for one-to-one video push call release. + +## 7.4.2.4 One-to-server video push + +### 7.4.2.4.1 General + +One-to-server video push is a private call between the calling party and the MCVideo server that allows the calling party to transmit video to the server for it to be recorded to a file. The one-to-server video push ends when the video transmission is stopped by the calling party or by the MCVideo server. + +NOTE: This procedure fulfils part of the requirements for the stage 1 video processing capabilities feature. + +##### 7.4.2.4.2 Procedure + +Procedure in figure 7.4.2.4.2-1 is the basic signalling control plane procedures for the MCVideo client initiating establishment of MCVideo video push to the MCVideo server. + +Pre-conditions: + +1. MCVideo user 1 on MCVideo client 1 has been authenticated and authorized to use MCVideo service. +2. MCVideo client 1 is registered. + +![Sequence diagram for One-to-server video push showing interactions between MCVideo client 1 and MCVideo server. Steps include request, authorization check, response, media plane establishment, video stream transmission, and completion request/response.](768b8ab0d55761b205087c079df1e6e6_img.jpg) + +``` + +sequenceDiagram + participant Client as MCVideo client 1 + participant Server as MCVideo server + Client->>Server: 1. MCVideo push to server request + Note right of Server: 2. Authorization check + Server-->>Client: 3. MCVideo push to server response + Note over Client, Server: 4. Media plane and transmission control established + Client->>Server: 5. Video stream from MCVideo client 1 + Client->>Server: 6. MCVideo push to server complete request + Server-->>Client: 7. MCVideo push to server complete response + +``` + +Sequence diagram for One-to-server video push showing interactions between MCVideo client 1 and MCVideo server. Steps include request, authorization check, response, media plane establishment, video stream transmission, and completion request/response. + +**Figure 7.4.2.4.2-1: One-to-server video push** + +1. MCVideo user on MCVideo client 1 initiates the push of a video to the server and sends an MCVideo push to server request to the MCVideo server. The request contains an SDP offer with media. +2. MCVideo server checks whether MCVideo client 1 is authorized to push a video to the server. +3. MCVideo server accepts the push to server request and sends an MCVideo push to server response. The response contains the SDP answer and the URL of the file where the video stream will be recorded. + +NOTE 1: Push request and response can include a negotiated maximum duration for the transmission. + +4. MCVideo client 1 and MCVideo server have successfully established the media plane and transmission control for the video stream. +5. Video stream is transmitted from MCVideo client 1 to MCVideo server. The MCVideo server records the stream to the file whose URL has been given in the MCVideo push to server response. + +NOTE 2: Notifications of new media availability can be sent by the initiating MCVideo user or by the MCVideo server using the URL received in the MCVideo push to server response. + +NOTE 3: MCVideo clients which receive the notification can initiate a pull of the video stream from the server using the URL provided in the notification, at their convenience, using the procedure defined in subclause 7.3.2.4.2. + +6. MCVideo user on MCVideo client 1, or MCVideo client 1 based on pre-defined criteria (e.g. duration), stops the video push to the server and sends an MCVideo push to server complete request. + +7. MCVideo server acknowledges the end of the communication. + +NOTE 4: Alternatively, based on internal criteria (e.g. maximum duration of the recorded video), the MCVideo server can end the transmission. + +#### 7.4.2.5 Remotely initiated video push + +##### 7.4.2.5.1 General + +Remotely initiated video push is a private call remotely initiated by a user that only allows a source user to transmit video to a destination, and the private call ends when the video transmission is completed or released by the authorized user who remotely initiated video push call. + +##### 7.4.2.5.2 Remotely initiated video push – call setup + +The procedure describes the case where an authorized MCVideo user is initiating an remotely initiated video push call from source MCVideo user to a destination MCVideo user. Only the source user is allowed to transmit video to the destination user. + +Procedures in figure 7.4.2.5.2-1 are the basic signalling control plane procedures for the MCVideo client remotely initiating establishment of MCVideo private call between the source and destination MCVideo users. + +![Sequence diagram for Remotely initiated video push – call setup. The diagram shows four lifelines: MCVideo client 1, MCVideo server, MCVideo client 2, and MCVideo client 3. The sequence of messages is: 1. MCVideo client 3 sends a 'Remote video push request' to the MCVideo server. 2. The MCVideo server performs an internal check for authorization and ongoing calls. 3. The MCVideo server sends a 'Remote video push request' to MCVideo client 1. 4. A box indicates the establishment of a one-to-one video push call between MCVideo client 1 and MCVideo client 2. 5. MCVideo client 1 sends a 'Remote video push response' to the MCVideo server. 6. The MCVideo server sends a 'Remote video push response' to MCVideo client 3.](72bc1a2b64dd6bac8285f560440c1218_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 3 + participant MCVideo server + participant MCVideo client 1 + participant MCVideo client 2 + Note right of MCVideo server: 2. Check for authorization and whether any on-going private call between source user and destination user + MCVideo client 3->>MCVideo server: 1. Remote video push request + MCVideo server-->>MCVideo client 1: 3. Remote video push request + Note over MCVideo client 1, MCVideo client 2: 4. Establish one-to-one video push call between MCVideo client 1 and MCVideo client 2 + MCVideo client 1->>MCVideo server: 5. Remote video push response + MCVideo server-->>MCVideo client 3: 6. Remote video push response + +``` + +Sequence diagram for Remotely initiated video push – call setup. The diagram shows four lifelines: MCVideo client 1, MCVideo server, MCVideo client 2, and MCVideo client 3. The sequence of messages is: 1. MCVideo client 3 sends a 'Remote video push request' to the MCVideo server. 2. The MCVideo server performs an internal check for authorization and ongoing calls. 3. The MCVideo server sends a 'Remote video push request' to MCVideo client 1. 4. A box indicates the establishment of a one-to-one video push call between MCVideo client 1 and MCVideo client 2. 5. MCVideo client 1 sends a 'Remote video push response' to the MCVideo server. 6. The MCVideo server sends a 'Remote video push response' to MCVideo client 3. + +**Figure 7.4.2.5.2-1: Remotely initiated video push – call setup** + +1. MCVideo user on MCVideo client 3 initiates remote video push from MCVideo client 1 to MCVideo client 2, by sending a remote video push request to the MCVideo server for establishing a one-to-one video push call between MCVideo client 1 and MCVideo client 2. The remote video push call request contains MCVideo ID of source (MCVideo client 1) and destination (MCVideo client 2) users +2. MCVideo server checks whether the MCVideo user at MCVideo client 3 is authorized to remotely initiate video push call between the source user and the destination user. MCVideo server also checks if there is any on-going call between the source user and the destination user. +3. If MCVideo client 3 is authorized and there is no on-going private call between source user and destination user, the MCVideo server sends the remote video push request message to MCVideo client 1 including the information of MCVideo ID of source and destination users. +4. The MCVideo client 1 accepts the remote video push request and establishes a one-to-one video push call between MCVideo client 1 and MCVideo client 2 as described in the subclause 7.4.2.3.2. The video is transmitted from MCVideo client 1 to MCVideo Client 2. +5. The MCVideo client 1 sends a remote video push response message to MCVideo server indicating success or failure of call establishment between MCVideo client 1 and MCVideo client 2. + +6. Upon receiving the remote video push response from MCVideo client 1, the MCVideo server informs the MCVideo client 3 about success or failure of the call establishment by sending a remote video push response message. + +NOTE: Steps 5 and 6 can occur before step 4. + +##### 7.4.2.5.3 Remotely initiated video push – call release by authorized user + +The procedure describes the case where an authorized MCVideo user is releasing an remotely initiated video push call. + +Procedures in figure 7.4.2.5.3-1 are the basic signalling control plane procedures for the MCVideo client releasing the remotely initiated video push call between the source and destination users. + +![Sequence diagram showing the call release process between MCVideo client 1, MCVideo server, MCVideo client 2, and MCVideo client 3. The steps are: 1. Remote video push release request from client 3 to server; 2. Check for authorization and ongoing private call; 3. Remote video push release request from server to client 1; 4. Release the one-to-one video push call between client 1 and client 2; 5. Remote video push release response from client 1 to server; 6. Remote video push release response from server to client 3.](b612b838f94982799a69461ffb078a73_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 3 + participant MCVideo server + participant MCVideo client 1 + participant MCVideo client 2 + Note right of MCVideo server: 2. Check for authorization and whether any on-going private call between source user and destination user + MCVideo client 3->>MCVideo server: 1. Remote video push release request + MCVideo server->>MCVideo client 1: 3. Remote video push release request + Note over MCVideo client 1, MCVideo client 2: 4. Release the one-to-one video push call between MCVideo client 1 and MCVideo client 2 + MCVideo client 1->>MCVideo server: 5. Remote video push release response + MCVideo server->>MCVideo client 3: 6. Remote video push release response + +``` + +Sequence diagram showing the call release process between MCVideo client 1, MCVideo server, MCVideo client 2, and MCVideo client 3. The steps are: 1. Remote video push release request from client 3 to server; 2. Check for authorization and ongoing private call; 3. Remote video push release request from server to client 1; 4. Release the one-to-one video push call between client 1 and client 2; 5. Remote video push release response from client 1 to server; 6. Remote video push release response from server to client 3. + +**Figure 7.4.2.5.3-1: Remotely initiated video push – call release by authorized user** + +1. MCVideo user on MCVideo client 3 initiates release of remotely initiated video push call between MCVideo client 1 and MCVideo client 2, by sending a remote video push release request to the MCVideo server for releasing a one-to-one video push call between MCVideo client 1 and MCVideo client 2. The remote video push release request contains MCVideo ID of source user (MCVideo client 1) and destination user (MCVideo client 2). +2. MCVideo server checks whether the MCVideo user at MCVideo client 3 is authorized to release the remotely initiated video push call between MCVideo client 1 and MCVideo client 2, and whether there is any on-going one-to-one video push call between MCVideo client 1 and MCVideo client 2. +3. MCVideo server sends the remote video push release request to MCVideo client 1 for releasing the on-going one-to-one video push call between MCVideo client 1 and MCVideo client 2. +4. The MCVideo client 1 accepts the remote video push release request and performs the release procedure for the one-to-one video push call between MCVideo client 1 and MCVideo client 2 as described in the subclause 7.4.2.3.3. +5. The MCVideo client 1 sends a remote video push release response to the MCVideo server indicating the release of the one-to-one video push call between MCVideo client 1 and MCVideo client 2. +6. Upon receiving the remote video push release response from MCVideo client 1, the MCVideo server informs the MCVideo client 3 about the one-to-one video push call release by sending a remote video push release response message. + +NOTE: Steps 5 and 6 can occur before step 4. + +#### 7.4.2.6 Remotely initiated video push to group + +##### 7.4.2.6.1 General + +Remotely initiated video push to group is a type of broadcast group call that only allows the originating user to remotely request a source user to transmit video to the group, and the group call ends when the video transmission is completed or the authorized user releases the remotely initiated video push to group call. + +##### 7.4.2.6.2 Remotely initiated video push to group – call setup + +The procedure describes the case where an authorized MCVideo user is initiating video push to group call for transmitting video from a source MCVideo user to the group. Only the source MCVideo user is allowed to transmit video. + +Procedures in figure 7.4.2.6.2-1 are the basic signalling control plane procedures for the MCVideo client remotely initiating a video push to group call. + +Pre-conditions: + +1. MCVideo client 1 and MCVideo client 2 are affiliated members of the group X. +2. The user on MCVideo client 1 is authorized to remotely initiate a video push to group call to enable transmitting the video from the user on MCVideo client 2. + +![Sequence diagram illustrating the remotely initiated video push to group – call setup procedure. The diagram shows interactions between MCVideo client 1, MCVideo server, and MCVideo client 2. Step 1: MCVideo client 1 sends a 'Remote video push request' to the MCVideo server. Step 2: The MCVideo server performs an internal check for user authorization and ongoing group calls. Step 3: The MCVideo server sends a 'Remote video push request' to MCVideo client 2. Step 4: MCVideo client 2 initiates a 'Broadcast group call initiated by MCVideo client 2'. Step 5: MCVideo client 2 sends a 'Remote video push response' to the MCVideo server. Step 6: The MCVideo server sends a 'Remote video push response' to MCVideo client 1.](37a6ab1d23efb9dc00cfae09d353b1da_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + Note right of MCVideo server: 2. Check for user authorization and whether there is a on-going group call + MCVideo client 1->>MCVideo server: 1. Remote video push request + MCVideo server-->>MCVideo client 2: 3. Remote video push request + MCVideo client 2->>MCVideo server: 4. Broadcast group call initiated by MCVideo client 2 + MCVideo client 2-->>MCVideo server: 5. Remote video push response + MCVideo server-->>MCVideo client 1: 6. Remote video push response + +``` + +Sequence diagram illustrating the remotely initiated video push to group – call setup procedure. The diagram shows interactions between MCVideo client 1, MCVideo server, and MCVideo client 2. Step 1: MCVideo client 1 sends a 'Remote video push request' to the MCVideo server. Step 2: The MCVideo server performs an internal check for user authorization and ongoing group calls. Step 3: The MCVideo server sends a 'Remote video push request' to MCVideo client 2. Step 4: MCVideo client 2 initiates a 'Broadcast group call initiated by MCVideo client 2'. Step 5: MCVideo client 2 sends a 'Remote video push response' to the MCVideo server. Step 6: The MCVideo server sends a 'Remote video push response' to MCVideo client 1. + +**Figure 7.4.2.6.2-1: Remotely initiated video push to group – call setup procedure** + +1. MCVideo user on MCVideo client 1 remotely initiates a video push to group from MCVideo client 2, by sending a remote video push request to the MCVideo server. The remote video push request contains MCVideo ID of the source user (user of MCVideo client 2) and the MCVideo group ID of the group X to which the video transmission is requested. +2. MCVideo server checks whether the MCVideo user at MCVideo client 1 is authorized to remotely initiate a video push to group, and also checks whether MCVideo client 2 is transmitting video in any on-going MCVideo group call on group X. If MCVideo client 2 is already transmitting video to group X then a suitable response is provided in step 6 to MCVideo client 1. +3. The MCVideo server sends a remote video push request initiated by MCVideo client 1 to MCVideo client 2. The remote video push request contains MCVideo ID of the source user, the MCVideo group ID of the group X to which the video transmission is to be initiated by the source user and an SDP offer containing one or more media types. +4. MCVideo client 2 initiates a MCVideo broadcast group call on group X. The MCVideo client 2 begins to transmit video to the group X. + +5. The MCVideo client 2 sends a remote video push response message to MCVideo server indicating success or failure in remotely initiating the video push to group X. +6. The MCVideo server sends a remote video push response message to MCVideo client 1 indicating success or failure in remotely initiating the video push to group X by the MCVideo client 2. + +NOTE: Steps 5 and 6 can occur before step 4. + +##### 7.4.2.6.3 Remotely initiated video push to group – call release by authorized user + +The procedure describes the case where an MCVideo user is remotely releasing a video push to group call for ending the video transmission from the source MCVideo user. + +Procedures in figure 7.4.2.6.3-1 are the basic signalling control plane procedures for the MCVideo client remotely releasing a video push to group call. + +Pre-condition: + +- MCVideo client 1 and MCVideo client 2 are affiliated members of the group X and there is an on-going broadcast group call on group X from MCVideo client 2 remotely initiated by MCVideo client 1 as described in subclause 7.4.2.6.2. + +![Sequence diagram for Remotely initiated video push to group – call release by authorized user. The diagram shows three participants: MCVideo client 1, MCVideo server, and MCVideo client 2. The sequence of messages is: 1. Remote video push release request from client 1 to server; 2. Internal check on the server; 3. Remote video push release request from server to client 2; 4. Remote video push release response from client 2 to server; 5. Remote video push release response from server to client 1; 6. Broadcast group call release by remote user (shown as a horizontal bar at the bottom).](01141eb99b707de5aead56f84afe3b1f_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + Note right of MCVideo server: 2. Check for user authorization and whether there is a on-going video pull to group call + MCVideo client 1->>MCVideo server: 1. Remote video push release request + MCVideo server->>MCVideo client 2: 3. Remote video push release request + MCVideo client 2->>MCVideo server: 4. Remote video push release response + MCVideo server->>MCVideo client 1: 5. Remote video push release response + Note bottom: 6. Broadcast group call release by remote user + +``` + +Sequence diagram for Remotely initiated video push to group – call release by authorized user. The diagram shows three participants: MCVideo client 1, MCVideo server, and MCVideo client 2. The sequence of messages is: 1. Remote video push release request from client 1 to server; 2. Internal check on the server; 3. Remote video push release request from server to client 2; 4. Remote video push release response from client 2 to server; 5. Remote video push release response from server to client 1; 6. Broadcast group call release by remote user (shown as a horizontal bar at the bottom). + +**Figure 7.4.2.6.3-1: Remotely initiated video push to group – call release by authorized user** + +1. MCVideo user on MCVideo client 1 remotely initiates a release of the video push to group call from MCVideo client 2, by sending a remote video push release request to the MCVideo server. The remote video push release request contains MCVideo ID of the source user (user of MCVideo client 2) and the MCVideo group ID of the group X to which the video transmission is to be released. +2. MCVideo server checks whether the MCVideo user at MCVideo client 1 is authorized to remotely release a video push to group call, and also checks whether MCVideo client 2 is transmitting video in an on-going MCVideo group call on group X remotely initiated by MCVideo client 1. If MCVideo client 2 is not transmitting video on group X then a suitable response is provided in step 5 to MCVideo client 1. +3. The MCVideo server sends a remote video push release request initiated by MCVideo client 1 to MCVideo client 2. The remote video push release request contains MCVideo ID of the source user, the MCVideo group ID of the group X to which the video transmission is to be released. +4. The MCVideo client 2 sends a remote video push release response message to MCVideo server indicating the release of video push to group call. +5. The MCVideo server sends a remote video push release response message to MCVideo client 1 indicating the release of video push to group call. + +6. MCVideo client 2 stops the video transmission to the group X and releases the MCVideo broadcast group call on group X remotely initiated by MCVideo client 1. + +NOTE: Step 6 can occur before steps 4 and 5. + +### 7.4.3 Off-network video push + +#### 7.4.3.1 General + +A MCVideo user triggers its MCVideo client to push a video to another MCVideo client. + +A MCVideo user triggers its MCVideo client to trigger a remote video push, which requests a second MCVideo client to push a video to a third MCVideo client or to a MCVideo group. + +Off-network remote video push works without involving the network. + +#### 7.4.3.2 Information flows for off-network video push + +##### 7.4.3.2.1 Remote video push request + +Table 7.4.3.2.1-1 describes the information flow for the remote video push request sent from one MCVideo client to other MCVideo client(s). + +**Table 7.4.3.2.1-1: Remote video push request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user remotely requesting the video push | +| MCVideo ID | M | The identity of the MCVideo user from whom the video push is requested | +| Video information | O | Information identifying the video | +| MCVideo group ID | O | The MCVideo group ID to which the video is to be transmitted. | + +##### 7.4.3.2.2 Video push trying response + +Table 7.4.3.2.2-1 describes the information flow for the video push trying response sent from one MCVideo client to another MCVideo client. + +**Table 7.4.3.2.2-1: Video push trying response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user sending the trying response | +| MCVideo ID | M | The identity of the MCVideo user to whom the trying response is sent | +| MCVideo ID | M | The identity of the MCVideo user to whom the video is attempted | + +##### 7.4.3.2.3 Notification of video push + +Table 7.4.3.2.3-1 describes the information flow for the notification of video push sent from one MCVideo client to another MCVideo client. + +**Table 7.4.3.2.3-1: Notification of video push** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user sending the notification | +| MCVideo ID | M | The identity of the MCVideo user to whom the notification is sent | +| MCVideo ID | M | The identity of the MCVideo user to whom the video is pushed | + +#### 7.4.3.3 Video push to another MCVideo user + +##### 7.4.3.3.1 General + +The MCVideo Push is the capability of a MCVideo user to push a video to another MCVideo user. A MCVideo user can push a video which is: + +- being received by the MCVideo user from another a MCVideo client; or +- being recorded live on the MCVideo client. + +##### 7.4.3.3.2 Procedure + +Figure 7.4.3.3.2-1 describes procedures for an off-network MCVideo video push, initiated by MCVideo client B with another MCVideo client C, to push a video received from MCVideo client A to MCVideo client C. + +MCVideo client A or MCVideo client C or both can be autonomous MCVideo clients or can be human controlled MCVideo clients. In any such combination, following the procedure is followed. + +MCVideo client A and MCVideo client B may belong to the same MCVideo user. + +Pre-conditions: + +1. MCVideo client A and MCVideo client B are engaged in MCVideo communication, where MCVideo client B is receiving media from MCVideo client A. +2. MCVideo user B has initiated MCVideo video push with MCVideo user C. +3. MCVideo client B and MCVideo client C are members of the same **ProSe** Discovery group and are **ProSe** 1:1 direct communication capable. +4. MCVideo client B has discovered MCVideo client C in proximity, associated with MCVideo user C, using **ProSe** Discovery procedures. + +![Sequence diagram illustrating the off-network video push procedure between three MCVideo clients: A, B, and C. The sequence starts with client B sending a 'Private communication request (Video push)' to client C. Client C responds with '2a. Notify MCVideo Push request' to client B. Client B then sends '2b. Private communication answer response (Video push)' to client C. Client B also sends '3a. Notification of video push to MCVideo client C' to client A. Client A responds with '3b. Notify MCVideo user' to client B. Client B and client C then proceed to '4. Establish media plane'. Finally, client B sends '5. Video from MCVideo client B to MCVideo client C' to client C.](06da11ab76cacc38bbcd714e437797ea_img.jpg) + +``` + +sequenceDiagram + participant A as MCVideo client A + participant B as MCVideo client B + participant C as MCVideo client C + Note left of A: 3b. Notify MCVideo user + B->>C: 1. Private communication request (Video push) + C-->>B: 2a. Notify MCVideo Push request + B-->>C: 2b. Private communication answer response (Video push) + B->>A: 3a. Notification of video push to MCVideo client C + A-->>B: 3b. Notify MCVideo user + Note right of B: 4. Establish media plane + B->>C: 5. Video from MCVideo client B to MCVideo client C + +``` + +Sequence diagram illustrating the off-network video push procedure between three MCVideo clients: A, B, and C. The sequence starts with client B sending a 'Private communication request (Video push)' to client C. Client C responds with '2a. Notify MCVideo Push request' to client B. Client B then sends '2b. Private communication answer response (Video push)' to client C. Client B also sends '3a. Notification of video push to MCVideo client C' to client A. Client A responds with '3b. Notify MCVideo user' to client B. Client B and client C then proceed to '4. Establish media plane'. Finally, client B sends '5. Video from MCVideo client B to MCVideo client C' to client C. + +**Figure 7.4.3.3.2-1: Off-network Video push to another MCVideo user** + +1. The MCVideo client B sends a Private communication request towards MCVideo client C. The Private communication request indicates that the request is for video push and contains the SDP offer. +- 2a. The MCVideo client C may notify the MCVideo user C about the MCVideo Push request (if the MCVideo client C is human controlled) +- 2b. The MCVideo client C automatically accepts the Private communication request for video push and sends a Private communication answer response to MCVideo client B. The Private communication answer response contains SDP answer. + +NOTE 1: Step 2a and step 2b can occur in any order. + +- 3a. If configured, the MCVideo client B notifies MCVideo client A about the video being pushed to MCVideo client C by sending a notification message to MCVideo client A. +- 3b. If configured, the MCVideo client A may notify the MCVideo user A about the video being pushed to MCVideo client C. +4. The MCVideo client B and MCVideo client C establish the media plane for communication. +5. Video being received by MCVideo client B from MCVideo client A is transmitted from MCVideo client B to MCVideo client C and presented to the MCVideo user C. + +NOTE 2: If a MCVideo client fails to establish the communication, the MCVideo client should send a Private communication failed response indicating the failure reason to the appropriate MCVideo client(s). + +NOTE 3: If a Private communication failed response is received by a MCVideo client, before or after establishing the media session, if already established, the session is terminated and the MCVideo user is notified about the failure and its reason, if any. + +#### 7.4.3.4 Remotely initiated video push + +##### 7.4.3.4.1 General + +The MCVideo push is the capability of a MCVideo user to push a video from a second MCVideo user to a third MCVideo user. + +##### 7.4.3.4.2 Procedure + +Figure 7.4.3.4.2-1 describes procedures for a remotely initiated off-network MCVideo video push, initiated by MCVideo user A at MCVideo client A with another MCVideo client B, to push a video to MCVideo client C. + +MCVideo client B can be an autonomous MCVideo client or can be a human controlled MCVideo client. In either case, following procedure is followed. + +Pre-conditions: + +1. MCVideo user A has remotely initiated MCVideo video push with MCVideo user B. +2. MCVideo client A and MCVideo client B are members of the same **ProSe** Discovery group and are **ProSe** 1:1 direct communication capable. +3. MCVideo client A has discovered MCVideo client B in proximity, associated with MCVideo user B, using **ProSe** Discovery procedures. + +![Sequence diagram for Remotely initiated off-network video push. Lifelines: MCVideo client A, MCVideo client B, MCVideo client C, and MCVideo user. The sequence starts with a Remote video push request from A to B. B then discovers C (2a), notifies its user (2b), and sends a trying response to A (2c). B then sends a private communication request to C (3). C responds (4a) and notifies its user (4b). B then notifies A (5) and its user (6). Finally, a media plane is established (7) and video is pushed from B to C (8).](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +``` + +sequenceDiagram + participant A as MCVideo client A + participant B as MCVideo client B + participant C as MCVideo client C + participant BU as MCVideo user + Note left of A: MCVideo user + Note right of C: MCVideo user + + A->>B: 1. Remote video push request + B->>C: 2a. MCVideo client B discovers MCVideo client C + B->>BU: 2b. Notification to the MCVideo user + B->>A: 2c. Video push trying response + B->>C: 3. Private communication request (Video push) + C->>B: 4a. Private communication answer response (Video push) + C->>CU: 4b. Notify connection request to MCVideo user + B->>A: 5. Notification of video push to MCVideo client C + B->>BU: 6. Notify MCVideo user + B->>C: 7. Establish media plane + B->>C: 8. Video from MCVideo client B to MCVideo client C + +``` + +Sequence diagram for Remotely initiated off-network video push. Lifelines: MCVideo client A, MCVideo client B, MCVideo client C, and MCVideo user. The sequence starts with a Remote video push request from A to B. B then discovers C (2a), notifies its user (2b), and sends a trying response to A (2c). B then sends a private communication request to C (3). C responds (4a) and notifies its user (4b). B then notifies A (5) and its user (6). Finally, a media plane is established (7) and video is pushed from B to C (8). + +**Figure 7.4.3.4.2-1: Remotely initiated off-network video push** + +1. The MCVideo client A sends a Video push request towards the MCVideo client B. The Video push request indicates MCVideo client C as the intended recipient. + - 2a. The MCVideo client B checks whether there is on-going private communication with MCVideo client C. If there is on-going private communication with MCVideo client C, then step 3, step 4 and step 5 are skipped, else MCVideo client B enables **ProSe** layer to discover MCVideo client C as specified in subclause 7.2.3. +- NOTE 1: MCVideo client A may provide the IP address of the MCVideo client C as part of the Video push request to the MCVideo B client. If such is the case, MCVideo client B does not require discovering MCVideo client C. +- 2b. The MCVideo client B notifies the MCVideo user B about the incoming Video push request (if MCVideo client B is human controlled). + - 2c. The MCVideo client B sends a video push trying response to MCVideo client A indicating that it is attempting to establish a connection with MCVideo client C, +- NOTE 2: Step 2a, 2b and 2c can occur in any order. +3. Once the required details of MCVideo client C are obtained (either by discovery or from MCVideo client A) the MCVideo client B accepts the Video push request, and sends a Private communication request to MCVideo client C. The Private communication request indicates that the request was in response to the video push request from the MCVideo client A. The Private communication request contains the SDP offer. + - 4a. MCVideo client C sends a Private communication answer response to MCVideo client B in response to the Private communication request. The Private communication answer response contains the SDP answer. + - 4b: The MCVideo client C notifies MCVideo user C about the incoming Private communication request as an indication of incoming video. +- NOTE 3: Step 4a and step 4b can occur in any order. +5. Upon receiving a Private communication answer response from the MCVideo client C, the MCVideo client B sends a notification message to the MCVideo client A indicating that MCVideo client C has accepted the request. + +6. MCVideo client A notifies the MCVideo user A about the acceptance of the request by MCVideo client C (if the MCVideo client A is human controlled) + +7. The MCVideo client B and the MCVideo client C establish the media plane for communication. + +NOTE 4: If a MCVideo client fails to establish the communication, the MCVideo client should send a Private communication failed response indicating the failure reason to the appropriate MCVideo client. + +8: Media is transmitted from MCVideo client B to MCVideo client C and presented to the MCVideo user C. + +NOTE 5: If a Private communication failed response is received by a MCVideo client, before or after establishing the media session, if already established, the session is terminated and the MCVideo user is notified about the failure and its reason, if any. + +NOTE 6: If the MCVideo client B fails to transmit the video to MCVideo client C, it should send a notification to MCVideo client A, indicating the reason. + +#### 7.4.3.5 Remotely initiated video push to a group + +##### 7.4.3.5.1 General + +The MCVideo push is the capability of a MCVideo user to push a video from a second MCVideo user to a MCVideo group. + +##### 7.4.3.5.2 Procedure + +Figure 7.4.3.5.2-1 describes procedures for an off-network remote video push request, initiated by MCVideo user A at MCVideo client A towards a MCVideo client B, to initiate a video push to MCVideo group G. + +MCVideo client B can be an autonomous MCVideo client or can be a human controlled MCVideo client. In either case, following procedure should be followed. + +Pre-conditions: + +1. MCVideo client A and MCVideo client B are members of MCVideo group G. +2. MCVideo user A has initiated remote video push request with MCVideo user B to initiate a video push to MCVideo group G. + +![Sequence diagram for Remotely initiated video push to a group. Lifelines: MCVideo Client B, MCVideo Client A, MCVideo group G. Step 1: MCVideo Client A sends '1. Remote video push request' to both MCVideo Client B and MCVideo group G. Step 2: MCVideo Client B sends '2. Notify remote push request' to MCVideo group G. Step 3: MCVideo group G sends '3. Group communication' to MCVideo Client B.](c6005b2627c6ca10f6b0e94cdb34858d_img.jpg) + +``` + +sequenceDiagram + participant MCVideo Client B + participant MCVideo Client A + participant MCVideo group G + Note left of MCVideo Client B: 2. Notify remote push request + MCVideo Client A->>MCVideo Client B: 1. Remote video push request + MCVideo Client A->>MCVideo group G: 1. Remote video push request + MCVideo Client B->>MCVideo group G: 2. Notify remote push request + MCVideo group G->>MCVideo Client B: 3. Group communication + +``` + +Sequence diagram for Remotely initiated video push to a group. Lifelines: MCVideo Client B, MCVideo Client A, MCVideo group G. Step 1: MCVideo Client A sends '1. Remote video push request' to both MCVideo Client B and MCVideo group G. Step 2: MCVideo Client B sends '2. Notify remote push request' to MCVideo group G. Step 3: MCVideo group G sends '3. Group communication' to MCVideo Client B. + +**Figure 7.4.3.5.2-1: Remotely initiated video push to a group** + +1. MCVideo client A sends a remote video push request towards the MCVideo group. The remote video push request indicates MCVideo client B as the intended target of the request and MCVideo group G as the intended recipient. +2. Upon receiving the remote video push request as the intended target of the request, the MCVideo client B notifies the MCVideo user B of the remote video push request, if the MCVideo client B is human controlled. Other MCVideo group members notify their respective MCVideo users of the remote video push request. + +3. The MCVideo client B automatically accepts the remote video push request and sends a group communication announcement message with video push indication towards the MCVideo group, as described in subclause 7.1.3.3. The group communication announcement message contains an SDP body and an indication that the group communication announcement is for video push. + +## 7.5 Capability information sharing + +### 7.5.1 General + +The MCVideo UE can store its capabilities information at the MCVideo server which can be retrieved by authorized users or MCVideo group members during on-network operations. The MCVideo UE can share their capabilities periodically or on-demand to another MCVideo UE or to MCVideo group members during off-network operations. + +### 7.5.2 On-network capability information sharing + +#### 7.5.2.1 General + +The MCVideo UE can store and update its capabilities information at the MCVideo server. Authorized MCVideo users or MCVideo group members can retrieve the capabilities information from the MCVideo server directly or via subscription and notification. + +#### 7.5.2.2 Information flows for on-network capability information sharing + +##### 7.5.2.2.1 Update MCVideo capabilities info request + +Table 7.5.2.2.1-1 describes the information flow update MCVideo capabilities info request from the MCVideo client to the MCVideo server. + +**Table 7.5.2.2.1-1: Update MCVideo capabilities info request** + +| Information element | Status | Description | +|----------------------|--------|----------------------------------------------------------------| +| MCVideo ID | M | Identity of the MCVideo user who is logged into the MCVideo UE | +| MCVideo capabilities | M | List of capabilities available at the MCVideo UE | + +NOTE: The device identification associated with MCVideo UE used for providing the MCVideo capabilities when the user logs on to multiple MCVideo UEs is specified by stage 3. + +##### 7.5.2.2.2 Update MCVideo capabilities info response + +Table 7.5.2.2.2-1 describes the information flow update MCVideo capabilities info response from the MCVideo server to the MCVideo client. + +**Table 7.5.2.2.2-1: Update MCVideo capabilities info response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------| +| Result | M | Indicates success or failure | + +##### 7.5.2.2.3 Get MCVideo capabilities info request + +Table 7.5.2.2.3-1 describes the information flow get MCVideo capabilities info request from the MCVideo client to the MCVideo server. + +**Table 7.5.2.2.3-1: Get MCVideo capabilities info request** + +| Information element | Status | Description | +|------------------------------------------------------------------|--------|-------------------------------------------------| +| MCVideo ID | M | Identity of the requesting MCVideo user | +| MCVideo ID list (NOTE) | O | List of Identities of the target MCVideo users | +| MCVideo group ID list (NOTE) | O | List of Identities of the target MCVideo groups | +| NOTE: At least one of the information elements shall be present. | | | + +##### 7.5.2.2.4 Get MCVideo capabilities info response + +Table 7.5.2.2.4-1 describes the information flow get MCVideo capabilities info response from the MCVideo server to the MCVideo client. + +**Table 7.5.2.2.4-1: Get MCVideo capabilities info response** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------| +| Result | M | Indicates success or failure | +| MCVideo ID (NOTE) | M | Identity of the MCVideo user whose MCVideo capabilities are requested | +| MCVideo capabilities (NOTE) | M | List of capabilities available at the requested MCVideo user's UE | +| NOTE: The MCVideo capabilities correspond to the MCVideo ID. MCVideo ID and MCVideo capabilities information elements shall not be present if the Result is failure. Multiple pairs of MCVideoID and MCVideo capabilities information elements may be appended. Only the affiliated group members in the requested MCVideo group ID list are returned. | | | + +##### 7.5.2.2.5 Subscribe MCVideo capabilities info request + +Table 7.5.2.2.5-1 describes the information flow subscribe MCVideo capabilities info request from the MCVideo client to the MCVideo server. + +**Table 7.5.2.2.5-1: Subscribe MCVideo capabilities info request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------| +| MCVideo ID | M | Identity of the requesting MCVideo user | +| MCVideo ID | O | Identity of the target MCVideo user | + +##### 7.5.2.2.6 Subscribe MCVideo capabilities info response + +Table 7.5.2.2.6-1 describes the information flow subscribe MCVideo capabilities info response from the MCVideo server to the MCVideo client. + +**Table 7.5.2.2.6-1: Subscribe MCVideo capabilities info response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------| +| Result | M | Indicates success or failure | + +##### 7.5.2.2.7 Notify MCVideo capabilities info request + +Table 7.5.2.2.7-1 describes the information flow notify MCVideo capabilities info request from the MCVideo server to the MCVideo client. + +**Table 7.5.2.2.7-1: Notify MCVideo capabilities info request** + +| Information element | Status | Description | +|----------------------|--------|-----------------------------------------------------------------| +| MCVideo ID | M | Identity of the MCVideo user logged in at the target MCVideo UE | +| MCVideo capabilities | M | List of capabilities available at the target MCVideo user's UE | + +##### 7.5.2.2.8 Notify MCVideo capabilities info response + +Table 7.5.2.2.8-1 describes the information flow notify MCVideo capabilities info response from the MCVideo client to the MCVideo server. + +**Table 7.5.2.2.8-1: Notify MCVideo capabilities info response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------| +| Result | M | Indicates success or failure | + +#### 7.5.2.3 Update MCVideo capabilities information at the MCVideo server + +The procedure for updating the MCVideo capabilities information at the MCVideo server is described in figure 7.5.2.3-1. + +![Sequence diagram for updating MCVideo capabilities information at the MCVideo server.](410562339ce067fdc6fa41940c118658_img.jpg) + +``` +sequenceDiagram + participant MCVideo client + participant MCVideo server + Note right of MCVideo server: 2. Update MCVideo capabilities information + MCVideo client->>MCVideo server: 1. Update MCVideo capabilities info request + MCVideo server-->>MCVideo client: 3. Update MCVideo capabilities info response +``` + +The diagram shows a sequence of three messages between an MCVideo client and an MCVideo server. The client sends a request (1. Update MCVideo capabilities info request) to the server. The server performs an internal action (2. Update MCVideo capabilities information) and then sends a response (3. Update MCVideo capabilities info response) back to the client. + +Sequence diagram for updating MCVideo capabilities information at the MCVideo server. + +**Figure 7.5.2.3-1: Update MCVideo capabilities information at the MCVideo server** + +1. The MCVideo client sends a update MCVideo capabilities info request message to MCVideo server to update the capabilities information available at the MCVideo client +2. The MCVideo server stores the updated MCVideo capabilities information received from the MCVideo client. +3. The MCVideo server provides a Update MCVideo capabilities info response indicating success or failure. + +#### 7.5.2.4 Retrieve MCVideo capabilities information by the MCVideo client + +The procedure for retrieval of MCVideo capabilities information by the MCVideo client is described in figure 7.5.2.4-1. + +Pre-conditions: + +- The MCVideo server has received MCVideo capabilities information from MCVideo clients and has stored this information; +- The MCVideo user is authorized to access the MCVideo capabilities information from the MCVideo server. +- The requesting MCVideo user is within the same MCVideo system as the requested MCVideo users and the requested MCVideo groups. + +![Sequence diagram for retrieving MCVideo capabilities information by the MCVideo client.](5dfc130b129ace4df375839020a5700d_img.jpg) + +``` +sequenceDiagram + participant MCVideo client + participant MCVideo server + Note right of MCVideo server: 2. Authorization check + MCVideo client->>MCVideo server: 1. Get MCVideo capabilities info request + MCVideo server-->>MCVideo client: 3. Get MCVideo capabilities info response +``` + +The diagram shows a sequence of three messages between an MCVideo client and an MCVideo server. The client sends a request (1. Get MCVideo capabilities info request) to the server. The server performs an internal action (2. Authorization check) and then sends a response (3. Get MCVideo capabilities info response) back to the client. + +Sequence diagram for retrieving MCVideo capabilities information by the MCVideo client. + +**Figure 7.5.2.4-1: Retrieve MCVideo capabilities information by the MCVideo client** + +1. The MCVideo client requests the MCVideo capabilities information by specifying some criteria (e.g. parameters, MCVideo ID). +2. The MCVideo server checks whether the user of the MCVideo client is authorized to retrieve the requested MCVideo capabilities information. +3. If authorized, the MCVideo server provides the requested MCVideo capabilities information to the MCVideo client. + +Editor's note: It is FFS for the case when the requesting MCVideo user is not within the same MCVideo system and the requested MCVideo users and the requested groups. + +#### 7.5.2.5 Subscription and notification for MCVideo capabilities information + +The procedure for subscription for MCVideo capabilities information as described in figure 7.5.2.5-1 is used by the MCVideo client to indicate to the MCVideo server that it wishes to receive updates of MCVideo capabilities information for which it is authorized. + +Pre-conditions: + +- The MCVideo server has some MCVideo capabilities information stored. + +![Sequence diagram for subscription to MCVideo capabilities information](f6e8acf9f931452d01688d311b5c0364_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client + participant MCVideo server + MCVideo client->>MCVideo server: 1. Subscribe MCVideo capabilities info request + MCVideo server-->>MCVideo client: 2. Subscribe MCVideo capabilities info response + +``` + +The diagram shows a sequence of two messages between an MCVideo client and an MCVideo server. The client sends a 'Subscribe MCVideo capabilities info request' to the server, and the server responds with a 'Subscribe MCVideo capabilities info response'. + +Sequence diagram for subscription to MCVideo capabilities information + +**Figure 7.5.2.5-1: Subscription for MCVideo capabilities information** + +1. The MCVideo client subscribes to the MCVideo capabilities information stored at the MCVideo server using the subscribe MCVideo capabilities info request. +2. The MCVideo server provides a subscribe MCVideo capabilities info response to the MCVideo client indicating success or failure of the request. + +The procedure for notification of MCVideo capabilities information as described in figure 7.5.2.5-2 is used by the MCVideo server to inform the MCVideo client that new or updated MCVideo capabilities information is available. + +Pre-conditions: + +- The MCVideo client has subscribed to the MCVideo capabilities information +- The MCVideo server has received and stored new or updated MCVideo capabilities information. + +![Sequence diagram for notification of MCVideo capabilities information](2bc39576969969ffe6d3f3d5264bba75_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client + participant MCVideo server + MCVideo server->>MCVideo client: 1. Notify MCVideo capabilities info request + MCVideo client-->>MCVideo server: 2. Notify MCVideo capabilities info response + +``` + +The diagram shows a sequence of two messages between an MCVideo server and an MCVideo client. The server sends a 'Notify MCVideo capabilities info request' to the client, and the client responds with a 'Notify MCVideo capabilities info response'. + +Sequence diagram for notification of MCVideo capabilities information + +**Figure 7.5.2.5-2: Notification of MCVideo capabilities information** + +1. The MCVideo server provides the notification to the MCVideo client, who previously subscribed for the MCVideo capabilities information. +2. The MCVideo client provides a notify MCVideo capabilities info response to the MCVideo server. + +If the MCVideo server has notified the MCVideo client about new or updated MCVideo capabilities information through this procedure, the MCVideo client may then follow the procedure described in subclause 7.5.2.4 in order to retrieve that MCVideo capabilities information. + +### 7.5.3 Off-network capability information sharing + +#### 7.5.3.1 General + +Each MCVideo client within a MCVideo group needs to share its video capabilities with other members of the MCVideo group. + +Video capability sharing can be done by sending information periodically as described in subclause 7.5.3.3 or on request as described in subclause 7.5.3.4. + +The receiving MCVideo clients need to store and update the video capability information from the sharing MCVideo client. + +#### 7.5.3.2 Information flows for Off-network capability information sharing + +##### 7.5.3.2.1 Capability request + +Table 7.5.3.2.1-1 describes the information flow for the capability request sent from the MCVideo client to other MCVideo client(s). + +**Table 7.5.3.2.1-1: Capability request** + +| Information Element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user requesting the capabilities | +| MCVideo ID | O | The identity of the MCVideo user towards whom the capability request was sent. | +| MCVideo group ID | O | The MCVideo group ID towards which the request was sent | +| Search criteria | O | A criteria filter for the capability request (e.g. category tags, video capabilities etc.) | + +##### 7.5.3.2.2 Capability announcement + +Table 7.5.3.2.2-1 describes the information flow for the capability announcement sent from the MCVideo client to other MCVideo client(s). + +**Table 7.5.3.2.2-1: Capability announcement** + +| Information Element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user announcing the capabilities | +| MCVideo ID | O | The identity of the MCVideo user towards whom the capability announcement was sent. | +| MCVideo group ID | O | The MCVideo group ID towards which the announcement was sent | +| Category tags | O | Category tags associated with a specific MCVideo UE or a video | +| Video capabilities | O | Set of video capabilities (e.g. codecs), camera capabilities (e.g. self-activated camera, wide field of view etc.) | +| Location | O | The location of the MCVideo user announcing the capabilities, if known | + +##### 7.5.3.2.3 Activity status request + +Table 7.5.3.2.3-1 describes the information flow for the activity status request sent from the MCVideo client to other MCVideo client(s). + +**Table 7.5.3.2.3-1: Activity status request** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user requesting the activity status | +| MCVideo ID | O | The identity of the MCVideo user towards whom the activity status request was sent. | +| MCVideo group ID | O | The MCVideo group ID towards which the activity status request was sent | + +##### 7.5.3.2.4 Activity status announcement + +Table 7.5.3.2.4-1 describes the information flow for the activity status announcement sent from the MCVideo client to other MCVideo client(s). + +**Table 7.5.3.2.4-1: Activity status announcement** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user announcing the activity status | +| Activity status | M | Current status of MCVideo UE's activities (e.g. receiving video, transmitting video, or recording video) | +| Video details | O | Details of the video like category tags or bit rate. | +| MCVideo ID | O | The identity of the MCVideo user towards whom the activity status announcement was sent. | +| MCVideo group ID | O | The MCVideo group ID towards which the activity status announcement was sent | + +#### 7.5.3.3 Periodic capability announcements + +##### 7.5.3.3.1 General + +The MCVideo client periodically provides its video capability information to other members of the MCVideo group. + +##### 7.5.3.3.2 Procedure + +Figure 7.5.3.3.2-1 describes procedures for periodic capability announcements. + +Each MCVideo client periodically sends a Capability announcement messages to the MCVideo group. This Capability announcement message is received by all other members of MCVideo group members. + +Upon receiving such a Capability announcement message, the MCVideo client stores/updates the information about the transmitting MCVideo client. + +Pre-conditions: + +- Information for **ProSe** direct communications corresponding to the MCVideo group and its mapping to **ProSe** Layer-2 Group ID are pre-configured in MCVideo client 1. +- MCVideo client 1 to MCVideo client N are members of the same MCVideo group. + +![Sequence diagram illustrating periodic capability announcements. Three lifelines are shown: MCVideo client 1, MCVideo client 2, and MCVideo client N. Step 1: MCVideo client 1 sends a 'Capability announcement' message to MCVideo client N. Step 2: MCVideo client 2 sends a message to MCVideo client N labeled 'Cache MCVideo client 1's presence and capabilities'.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo client 2 + participant MCVideo client N + Note left of MCVideo client 1: 1. Capability announcement + MCVideo client 1->>MCVideo client N: Capability announcement + Note right of MCVideo client 2: 2. Cache MCVideo client 1's presence and capabilities + MCVideo client 2->>MCVideo client N: Cache MCVideo client 1's presence and capabilities + +``` + +Sequence diagram illustrating periodic capability announcements. Three lifelines are shown: MCVideo client 1, MCVideo client 2, and MCVideo client N. Step 1: MCVideo client 1 sends a 'Capability announcement' message to MCVideo client N. Step 2: MCVideo client 2 sends a message to MCVideo client N labeled 'Cache MCVideo client 1's presence and capabilities'. + +**Figure 7.5.3.3.2-1: Periodic capability announcements** + +1. MCVideo client 1 periodically sends a Capability announcement message, which contains its capability information with other relevant information. +2. Other MCVideo clients, upon receiving a Capability announcement message from MCVideo client 1, cache its presence and capability information along with other relevant information. + +NOTE: Capability announcement may include specific category tags (e.g. certain video camera), video capabilities of the client, location, camera angles, camera orientation, etc. + +#### 7.5.3.4 Request capabilities from client(s) + +##### 7.5.3.4.1 General + +The MCVideo client requests video capability information from other members of the MCVideo group. + +##### 7.5.3.4.2 Request clients with particular capabilities + +Figure 7.5.3.4.2-1 describes procedures for a mechanism to request other MCVideo clients having particular characteristics to share their capabilities. + +MCVideo client sends a Capability request message to other MCVideo clients with search criteria. The search criteria may include MCVideo user ID or MCVideo client ID or a set of capabilities or a particular category of capabilities, or a mix of such criterions, etc. + +Upon receiving the Capability request message, the MCVideo client that fulfils the search criteria responds to the received Capability request message with a Capability announcement message. + +Pre-conditions: + +1. Information for ProSe direct communications corresponding to the MCVideo group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCVideo client 1. +2. MCVideo client 1 to MCVideo client N are members of the same MCVideo group. + +![Sequence diagram illustrating the request for clients with particular capabilities. Three lifelines are shown: MCVideo client 1, MCVideo client 2, and MCVideo client N. Step 1: MCVideo client 1 sends a 'Capability request' message to MCVideo client N. Step 2: MCVideo client N sends a 'Capability announcement' message back to MCVideo client 1. Step 3: A box labeled 'Cache presence and capabilities of other MCVideo clients' is shown below the lifelines, indicating the result of the process.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` +sequenceDiagram + participant MCVideo client 1 + participant MCVideo client 2 + participant MCVideo client N + Note left of MCVideo client 1: 1. Capability request + MCVideo client 1->>MCVideo client N: Capability request + Note right of MCVideo client N: 2. Capability announcement + MCVideo client N-->>MCVideo client 1: Capability announcement + Note below MCVideo client 1: 3. Cache presence and capabilities of other MCVideo clients +``` + +Sequence diagram illustrating the request for clients with particular capabilities. Three lifelines are shown: MCVideo client 1, MCVideo client 2, and MCVideo client N. Step 1: MCVideo client 1 sends a 'Capability request' message to MCVideo client N. Step 2: MCVideo client N sends a 'Capability announcement' message back to MCVideo client 1. Step 3: A box labeled 'Cache presence and capabilities of other MCVideo clients' is shown below the lifelines, indicating the result of the process. + +**Figure 7.5.3.4.2-1: Request clients with particular capabilities** + +1. MCVideo client 1 sends a Capability request message with search criteria to request MCVideo clients of the MCVideo group, with particular characteristics, to share their capabilities. +2. Upon receiving a Capability request message with search criteria, all MCVideo clients which fulfil the search criteria respond with a Capability announcement message, which contains its capability information with other relevant information. + +NOTE 1: If the Capability request message does not contain a search criteria, all the MCVideo clients that receive the Capability request message respond with a Capability announcement message. + +3. MCVideo clients, upon receiving a Capability announcement message from another MCVideo client, cache its presence and capability information along with other relevant information. + +NOTE 2: Capability announcement may include specific category tags (e.g. certain video camera), video capabilities of the client, location, camera angles, camera orientation, etc. + +##### 7.5.3.4.3 Request capabilities from a particular client + +Figure 7.5.3.4.3-1 describes procedures for a mechanism to request a particular MCVideo client in proximity, for its capabilities. + +MCVideo client sends a Capability request message to the other MCVideo client. + +Upon receiving the Capability request message, the MCVideo client responds to the received Capability request message by sending a Capability announcement message to the sender of the Capability request message. + +Pre-conditions: + +1. Information for **ProSe** direct communications corresponding to the MCVideo client 2 is pre-configured in MCVideo client 1. +2. MCVideo client 1 has discovered MCVideo client 2 in proximity using **ProSe** Discovery procedures. + +![Sequence diagram showing the interaction between MCVideo client 1 and MCVideo client 2. Step 1: MCVideo client 1 sends a 'Capability request' to MCVideo client 2. Step 2: MCVideo client 2 responds with a 'Capability announcement'. Step 3: MCVideo client 1 receives the announcement and caches the presence and capabilities of MCVideo client 2.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo client 2 + Note left of MCVideo client 1: 3. Cache presence and capabilities of the MCVideo client 2 + MCVideo client 1->>MCVideo client 2: 1. Capability request + MCVideo client 2-->>MCVideo client 1: 2. Capability announcement + +``` + +Sequence diagram showing the interaction between MCVideo client 1 and MCVideo client 2. Step 1: MCVideo client 1 sends a 'Capability request' to MCVideo client 2. Step 2: MCVideo client 2 responds with a 'Capability announcement'. Step 3: MCVideo client 1 receives the announcement and caches the presence and capabilities of MCVideo client 2. + +**Figure 7.5.3.4.3-1: Request capabilities from a particular client** + +1. MCVideo client 1 sends a Capability request message towards MCVideo client 2. +2. Upon receiving the Capability request message the MCVideo client 2 responds with a Capability announcement message, which contains its capability information with other relevant information. +3. MCVideo client 1, upon receiving a Capability announcement message, caches MCVideo client 2's presence and capability information along with other relevant information. + +NOTE: Capability announcement may include specific category tags (e.g. certain video camera), video capabilities of the client, location, camera angles, camera orientation, etc. + +#### 7.5.3.5 Request activity status from client(s) + +##### 7.5.3.5.1 General + +The MCVideo client requests activity status information from other members of the MCVideo group. + +##### 7.5.3.5.2 Request activity status of group members + +Figure 7.5.3.5.2-1 describes procedures to request activity status of other MCVideo clients having particular characteristics. + +MCVideo client sends an activity status request message to other MCVideo clients with search criteria. The search criteria may include MCVideo user ID or MCVideo client ID or a set of capabilities or a particular category of capabilities, or a mix of such criterion, etc. + +Upon receiving the activity status request message, the MCVideo client that fulfils the search criteria responds to the received activity status request message with an activity status announcement message. + +Pre-conditions: + +1. Information for **ProSe** direct communications corresponding to the MCVideo group and its mapping to **ProSe** Layer-2 Group ID are pre-configured in MCVideo client 1. +2. MCVideo client 1 to MCVideo client N are members of the same MCVideo group. + +![Sequence diagram showing activity status request and announcement among multiple MCVideo clients (client 1, client 2, client N).](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant C2 as MCVideo client 2 + participant CN as MCVideo client N + C1->>C2: 1. Activity status request + C1->>CN: 1. Activity status request + C2->>C1: 2. Activity status announcement + CN->>C1: 2. Activity status announcement + Note over C1,CN: 3. Cache presence and activity status of other MCVideo clients + +``` + +Sequence diagram showing activity status request and announcement among multiple MCVideo clients (client 1, client 2, client N). + +Figure 7.5.3.5.2-1: Request activity status of group members + +1. MCVideo client 1 sends an activity status request message with search criteria to request MCVideo clients of the MCVideo group, with particular characteristics, to share their activity status. + 2. Upon receiving a activity status request message with search criteria, all MCVideo clients which fulfil the search criteria respond with an activity status announcement message, which contains its activity status information. +- NOTE 1: If the activity status request message does not contain a search criteria, all the MCVideo clients that receive the activity status request message respond with an activity status announcement message. +3. MCVideo clients, upon receiving an activity status announcement message from another MCVideo client, cache its presence and activity status information. + +##### 7.5.3.5.3 Request activity status from a particular client + +Figure 7.5.3.5.3-1 describes procedures to request a particular MCVideo client in proximity, for its activity status. + +MCVideo client sends an activity status request message to the other MCVideo client. + +Upon receiving the activity status request message, the MCVideo client responds to the received activity status request message by sending an activity status announcement message to the sender of the activity status request message. + +Pre-conditions: + +1. Information for **ProSe** direct communications corresponding to the MCVideo client 2 is pre-configured in MCVideo client 1. +2. MCVideo client 1 has discovered MCVideo client 2 in proximity using **ProSe** Discovery procedures. + +![Sequence diagram showing activity status request and announcement between two specific MCVideo clients (client 1 and client 2).](cd141897aa368dbbaa398ace230cdd85_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant C2 as MCVideo client 2 + C1->>C2: 1. Activity status request + C2->>C1: 2. Activity status announcement + Note over C1: 3. Cache presence and activity status of the MCVideo client 2 + +``` + +Sequence diagram showing activity status request and announcement between two specific MCVideo clients (client 1 and client 2). + +Figure 7.5.3.5.3-1: Request activity status from a particular client + +1. MCVideo client 1 sends an activity status request message towards MCVideo client 2. +2. Upon receiving the activity status request message the MCVideo client 2 responds with an activity status announcement message, which contains its activity status information. +3. MCVideo client 1, upon receiving an activity status announcement message, caches MCVideo client 2's presence and activity status information. + +## 7.6 Ambient viewing call + +### 7.6.1 General + +The ambient viewing call is a type of a private MCVideo call that only allows a "viewed to" user to transmit media to a "viewing" user such that there is no indication on the MCVideo UE of the "viewed to" user about the call and the media transmission. + +NOTE 1: "viewed to" user refers to the user who is transmitting media in an ambient viewing call. + +NOTE 2: "viewing" user refers to the user who is receiving media in an ambient viewing call. + +There are two types of ambient viewing call as below: + +- Remotely initiated ambient viewing is initiated by the authorized user (e.g., dispatcher) who wants to view to another user. In this case, the "viewed to" user is the called party, and shall automatically accept the call without causing any indication about the call and transmit the media to the "viewing" user. +- Locally initiated ambient viewing is initiated by an authorized user who wants another user to view to the MCVideo UE communication. In this case, the "viewed to" user is the calling party and shall automatically transmit the media to the "viewing" user without causing any indication about the call processing and media transmission. + +### 7.6.2 Information flows for ambient viewing call + +#### 7.6.2.1 Ambient viewing call request + +Table 7.6.2.1-1 describes the information flow for the ambient viewing call request from MCVideo client and MCVideo server and MCVideo server to the MCVideo client. + +**Table 7.6.2.1-1: Ambient viewing call request** + +| Information Element | Status | Description | +|----------------------|--------|-----------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the "viewing" user to view | +| MCVideo ID | M | The MCVideo ID of the "viewed to" user | +| SDP offer | M | Media parameters of MCVideo client. | +| Ambient viewing type | M | The ambient viewing type indicates remotely initiated ambient viewing call or locally initiated ambient viewing call. | + +#### 7.6.2.2 Ambient viewing call response + +Table 7.6.2.2-1 describes the information flow ambient viewing call response from the MCVideo client to the MCVideo server and MCVideo server to the MCVideo client. + +**Table 7.6.2.2-1: Ambient viewing call response** + +| <b>Information Element</b> | <b>Status</b> | <b>Description</b> | +|----------------------------|---------------|-----------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the "viewing" user | +| MCVideo ID | M | The MCVideo ID of the "viewed to" user | +| SDP answer | M | Media parameters | +| Ambient viewing type | M | The ambient viewing type indicates remotely initiated ambient viewing call or locally initiated ambient viewing call. | + +#### 7.6.2.3 Ambient viewing call release request + +Table 7.6.2.3-1 describes the information flow ambient viewing call release request from the MCVideo client to the MCVideo server and MCVideo server to the MCVideo client. + +**Table 7.6.2.3-1: Ambient viewing call release request** + +| <b>Information Element</b> | <b>Status</b> | <b>Description</b> | +|----------------------------|---------------|-----------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the "viewing" user | +| MCVideo ID | M | The MCVideo ID of the "viewed to" user | +| Ambient viewing type | M | The ambient viewing type indicates remotely initiated ambient viewing call or locally initiated ambient viewing call. | + +#### 7.6.2.4 Ambient viewing call release response + +Table 7.6.2.4-1 describes the information flow ambient viewing call release response from the MCVideo client to the MCVideo server and MCVideo server to the MCVideo client. + +**Table 7.6.2.4-1: Ambient viewing call release response** + +| <b>Information Element</b> | <b>Status</b> | <b>Description</b> | +|----------------------------|---------------|-----------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the "viewing" user | +| MCVideo ID | M | The MCVideo ID of the "viewed to" user | +| Ambient viewing type | M | The ambient viewing type indicates remotely initiated ambient viewing call or locally initiated ambient viewing call. | + +#### 7.6.2.5 Ambient viewing call release notification + +Table 7.6.2.5-1 describes the information flow ambient viewing call release notification from the MCVideo server to the MCVideo client. + +**Table 7.6.2.5-1: Ambient viewing call release notification** + +| Information Element | Status | Description | +|----------------------|--------|-----------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | The MCVideo ID of the user to view | +| MCVideo ID | M | The MCVideo ID of the user to be viewed to | +| Call release reason | M | The reason for call release by the MCVideo server | +| Ambient viewing type | M | The ambient viewing type indicates remotely initiated ambient viewing call or locally initiated ambient viewing call. | + +### 7.6.3 Procedures + +#### 7.6.3.1 Remotely initiated ambient viewing call setup procedure + +The MCVideo service provides the capability for an authorised user to initiate a remotely initiated ambient viewing call. + +Figure 7.6.3.1-1 illustrates the high level procedure of remotely initiated ambient viewing call setup procedure. + +Pre-conditions: + +- MCVideo client 1 is the client of the authorized user who is authorized to invoke a remotely initiated ambience viewing call with MCVideo client 2. +- MCVideo user 1 is the "viewing" user at MCVideo client 1, and MCVideo user 2 is the "viewed to" user at MCVideo client 2. + +![Sequence diagram illustrating the remotely initiated ambient viewing call setup procedure. The diagram shows three participants: MCVideo client 1, MCVideo server, and MCVideo client 2. The sequence of messages is: 1. MCVideo client 1 sends an 'Ambient viewing call request' to the MCVideo server. 2. The MCVideo server sends an 'Authorize ambient viewing call request' to MCVideo client 2. 3. MCVideo client 2 sends an 'Ambient viewing call request' to the MCVideo server. 4. The MCVideo server sends an 'Ambient viewing call response' to MCVideo client 2. 5. The MCVideo server sends an 'Ambient viewing call response' to MCVideo client 1. 6. The MCVideo server sends a 'Transmit media granted' message to MCVideo client 2. 7. Both MCVideo client 1 and MCVideo client 2 send 'Media transmission' messages to the MCVideo server, indicated by large blue arrows.](86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + Note right of MCVideo server: 2.Authorize ambient viewing call request + MCVideo client 1->>MCVideo server: 1.Ambient viewing call request + MCVideo server->>MCVideo client 2: 3.Ambient viewing call request + MCVideo client 2->>MCVideo server: 4.Ambient viewing call response + MCVideo server->>MCVideo client 2: 6. Transmit media granted + MCVideo server->>MCVideo client 1: 5.Ambient viewing call response + Note left of MCVideo client 1: 7. Media transmission + Note right of MCVideo client 2: 7. Media transmission + +``` + +Sequence diagram illustrating the remotely initiated ambient viewing call setup procedure. The diagram shows three participants: MCVideo client 1, MCVideo server, and MCVideo client 2. The sequence of messages is: 1. MCVideo client 1 sends an 'Ambient viewing call request' to the MCVideo server. 2. The MCVideo server sends an 'Authorize ambient viewing call request' to MCVideo client 2. 3. MCVideo client 2 sends an 'Ambient viewing call request' to the MCVideo server. 4. The MCVideo server sends an 'Ambient viewing call response' to MCVideo client 2. 5. The MCVideo server sends an 'Ambient viewing call response' to MCVideo client 1. 6. The MCVideo server sends a 'Transmit media granted' message to MCVideo client 2. 7. Both MCVideo client 1 and MCVideo client 2 send 'Media transmission' messages to the MCVideo server, indicated by large blue arrows. + +**Figure 7.6.3.1-1: Remotely initiated ambient viewing call setup** + +1. MCVideo client 1 initiates a remotely initiated ambient viewing call to MCVideo client 2 by sending an ambient viewing request to MCVideo server. The remotely initiated ambient viewing call type is included. +2. The MCVideo server performs an authorization check for the authorized user 1 for the remotely initiated ambient viewing call. If authorization fails, the MCVideo server provides a failure response to MCVideo client 1. +3. The MCVideo server sends the ambient viewing call request to MCVideo client 2. +4. MCVideo client 2 returns the ambient viewing call response to the MCVideo server. +5. MCVideo server provides an ambient viewing call response to MCVideo client 1, indicating that whether the remotely initiated ambient viewing call is set up successfully or not. + +6. The transmission control server of the MCVideo server then sends a media transmit granted message to MCVideo client 2 according to the ambient viewing type received in step 1. +7. After receiving the media transmit granted message, the MCVideo client to be viewed to transmit video to the MCVideo client 1 for viewing. + +NOTE: MCVideo client 2 does not provide any indication of the ambient viewing call release to its user. + +#### 7.6.3.2 Locally initiated ambient viewing call setup procedure + +The MCVideo service provides the capability for an authorised user to initiate a locally initiated ambient viewing call. + +Figure 7.6.3.2-1 illustrates the high level procedure of locally initiated ambient viewing call setup procedure. + +Pre-conditions: + +- MCVideo client 2 is the client of the authorized user who is authorized to invoke a locally initiated ambient viewing call from MCVideo client 2. +- MCVideo user 1 is the "viewing" user at MCVideo client 1, and MCVideo user 2 is the "viewed to" user at MCVideo client 2. + +![Sequence diagram showing the locally initiated ambient viewing call setup procedure between MCVideo client 1, MCVideo server, and MCVideo client 2.](d3b5eac55166fc428a223bba5c46961b_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 2 + participant MCVideo server + participant MCVideo client 1 + Note right of MCVideo server: 2.Authorize ambient viewing call request + MCVideo client 2->>MCVideo server: 1.Ambient viewing call request + MCVideo server->>MCVideo client 2: 2.Authorize ambient viewing call request + MCVideo server->>MCVideo client 1: 3.Ambient viewing call request + MCVideo client 1->>MCVideo server: 4.Ambient viewing call response + MCVideo server->>MCVideo client 2: 5.Ambient viewing call response + MCVideo server->>MCVideo client 2: 6. Transmit media granted + Note left of MCVideo server: 7. Video transmission + Note right of MCVideo server: 7. Video transmission + MCVideo client 2->>MCVideo client 1: 7. Video transmission + +``` + +Sequence diagram showing the locally initiated ambient viewing call setup procedure between MCVideo client 1, MCVideo server, and MCVideo client 2. + +**Figure 7.6.3.2-1: Locally initiated ambient viewing call setup** + +1. MCVideo client 2 initiates a locally initiated ambient viewing call to MCVideo client 1 by sending an ambient viewing request to MCVideo server. The locally initiated ambient viewing call type is included. +2. The MCVideo server performs an authorization check for the authorized user 2 for the locally initiated ambient viewing call. If authorization fails, the MCVideo server provides a failure response to MCVideo client 2. +3. The MCVideo server sends the ambient viewing call request to MCVideo client 1. +4. MCVideo client 1 returns the ambient viewing call response to the MCVideo server. +5. MCVideo server provides an ambient viewing call response to MCVideo client 2, indicating that whether the locally initiated ambient viewing call is set up successfully or not. +6. The transmission control server of the MCVideo server then sends a media transmit granted message to MCVideo client 2 according to the ambient viewing type received in step 1. +7. After receiving the media transmit granted message, the MCVideo client to be viewed to, transmits video to the MCVideo client 1 for viewing. + +NOTE: MCVideo client 2 does not provide any indication of the ambient viewing call release to its user. + +#### 7.6.3.3 Ambient viewing call release – server initiated + +Figure 7.6.3.3-1 illustrates the information flow for ambient viewing call release – server initiated when trigger by the MCVideo administrator. This procedure is applied for both remotely initiated ambient viewing call and the locally initiated ambient viewing call. + +Pre-conditions: + +- MCVideo client 1 is the MCVideo client of the authorized user, who initiated the ambient viewing call at MCVideo client 2. +- There is an ongoing ambient viewing call between MCVideo client 2 and MCVideo client 1. +- MCVideo user 1 is the "viewing" user at MCVideo client 1, and MCVideo user 2 is the "viewed to" user at MCVideo client 2. + +![Sequence diagram for ambient viewing call release – server initiated. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2. Steps: 1. Ambient viewing call release is triggered (at server); 2. Ambient viewing call release request (server to client 2); 3. Stop transmitting media (internal at client 2); 4. Ambient viewing call release response (client 2 to server); 5. Ambient viewing call release notification (server to client 1); 6. Notify user (internal at client 1).](8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + Note right of MCVideo server: 1.Ambient viewing call release is triggered + MCVideo server->>MCVideo client 2: 2.Ambient viewing call release request + Note right of MCVideo client 2: 3. Stop transmitting media + MCVideo client 2->>MCVideo server: 4.Ambient viewing call release response + MCVideo server->>MCVideo client 1: 5. Ambient viewing call release notification + Note left of MCVideo client 1: 6.Notify user + +``` + +Sequence diagram for ambient viewing call release – server initiated. Lifelines: MCVideo client 1, MCVideo server, MCVideo client 2. Steps: 1. Ambient viewing call release is triggered (at server); 2. Ambient viewing call release request (server to client 2); 3. Stop transmitting media (internal at client 2); 4. Ambient viewing call release response (client 2 to server); 5. Ambient viewing call release notification (server to client 1); 6. Notify user (internal at client 1). + +**Figure 7.6.3.3-1: Ambient viewing call release – server initiated** + +1. The ambient viewing call release criteria by the MCVideo administrator. + 2. The MCVideo server sends an ambient viewing call release request to MCVideo client 2. + 3. MCVideo client 2 stops transmitting media to MCVideo client 1. +- NOTE: MCVideo client 2 does not provide any indication of the ambient viewing call release to its user. +4. MCVideo client 2 provides an ambient viewing call release response to the MCVideo server. + 5. The MCVideo server sends an ambient viewing call release notification to MCVideo client 1 together with a reason code identifying that the call was released. + 6. MCVideo client 1 notifies the authorized MCVideo user 1. + +#### 7.6.3.4 Ambient viewing call release – "viewing" user initiated + +Figure 7.6.3.4-1 illustrates the information flow for ambient viewing call release – "viewing" user initiated. This procedure is applied for both remotely initiated ambient viewing call and the locally initiated ambient viewing call. + +Pre-conditions: + +- MCVideo client 1 is the client of the authorized user, who is authorized to release the ambient viewing call at MCVideo client 2. +- There is an ongoing ambient viewing call between MCVideo client 2 and MCVideo client 1. +- MCVideo user 1 is the "viewing" user at MCVideo client 1, and MCVideo user 2 is the "viewed to" user at MCVideo client 2. + +![Sequence diagram for ambient viewing call release initiated by the 'viewing' user (MCVideo client 1).](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant S as MCVideo server + participant C2 as MCVideo client 2 + C1->>S: 1.Ambient viewing call release request + S->>C2: 2.Ambient viewing call release request + Note over C2: 3.Stop transmitting media + C2->>S: 4.Ambient viewing call release response + S->>C1: 5.Ambient viewing call release response + +``` + +Sequence diagram for ambient viewing call release initiated by the 'viewing' user (MCVideo client 1). + +**Figure 7.6.3.4-1: Ambient viewing call release – "viewing" user initiated** + +1. The authorized user 1 at MCVideo client 1 initiates the ambient viewing call release to MCVideo client 2 by sending an ambient viewing call release request to the MCVideo server. + 2. The MCVideo server sends an ambient viewing call release request to MCVideo client 2. + 3. MCVideo client 2 stops transmitting media to MCVideo client 1. +- NOTE: MCVideo client 2 does not provide any indication of the ambient viewing call release to its user. +4. MCVideo client 2 provides an ambient viewing call release response to the MCVideo server. + 5. The MCVideo server provides the ambient viewing call release response to MCVideo client 1. + +#### 7.6.3.5 Ambient viewing call release – "viewed to" user initiated + +Figure 7.6.3.5-1 illustrates the information flow for ambient viewing call release – "viewed to" user initiated. This procedure is only applied for the locally initiated ambient viewing call. + +Pre-conditions: + +- MCVideo client 2 is the client of the authorized user, who is authorized to release the locally initiated ambient viewing call at MCVideo client 2. +- There is an ongoing ambient viewing call between MCVideo client 1 and MCVideo client 2. +- MCVideo user 1 is the current user at MCVideo client 1 who is viewing, and MCVideo user 2 is the current user at MCVideo client 2 who is being viewed to. + +![Sequence diagram for ambient viewing call release initiated by the 'viewed to' user (MCVideo client 2).](f1fbb1287d999c7034742de35bdab836_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant S as MCVideo server + participant C2 as MCVideo client 2 + C2->>S: 1.Ambient viewing call release request + S->>C1: 2.Ambient viewing call release request + Note over C1: 3.Notify user + C1->>S: 4.Ambient viewing call release response + S->>C2: 5.Ambient viewing call release response + Note over C2: 6.Stop transmitting media + +``` + +Sequence diagram for ambient viewing call release initiated by the 'viewed to' user (MCVideo client 2). + +**Figure 7.6.3.5-1: Ambient viewing call release – "viewed to" user initiated** + +1. The authorized user 2 at MCVideo client 2 initiates the ambient viewing call release by sending an ambient viewing call release request to the MCVideo server. +2. The MCVideo server provides an ambient viewing call release request to MCVideo client 1. +3. MCVideo client 1 is notified about the ambient viewing call release. +4. MCVideo client 1 provides an ambient viewing call release response to the MCVideo server. +5. The MCVideo server provides the ambient viewing call release response to MCVideo client 2. +6. MCVideo client 1 stops transmitting media to MCVideo client 2. + +NOTE: MCVideo client 1 does not provide any indication of the ambient viewing call release to its user. + +## 7.7 Transmission control + +### 7.7.1 Transmission control for on-network MCVideo service + +#### 7.7.1.1 General + +The procedure is for providing a transmission control to MCVideo UE in an on-network case and applies for both private call and group call. Transmission control is performed by using transmission control information flows between the transmission control participant and the transmission control server. + +#### 7.7.1.2 Information flows for transmission control for on-network + +##### 7.7.1.2.1 General + +When the transmission control server receives a transmit media request from the transmission control participant, it decides whether to give a grant or not. The result is informed to the requesting transmission control participant. When the transmission control participant receives a transmit media granted message, it can send video media over the uplink bearer established beforehand. The transmit media revoked message can be used as part of revoke. The transmit media queue status request can be used to know current position in the queue for media transmission. + +Some transmission control information flows can also piggyback call control information flows to provide efficient call setup and clearing: + +- Call setup request is optionally carried in transmit media request (uplink); and +- Call release request is optionally carried in media transmission release (uplink). + +##### 7.7.1.2.2 Transmit media request + +Table 7.7.1.2.2-1 describes the information flow transmit media request, from the transmission control participant to the transmission control server, which is used to request the transmit media request. This information flow is sent in unicast to the transmission control server. + +**Table 7.7.1.2.2-1: Transmit media request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of the user whose media transmission is requested | +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.3 Transmit media granted + +Table 7.7.1.2.3-1 describes the information flow transmit media granted, from the transmission control server to the transmission control participant, which is used to indicate that a transmit media request is granted and media transmission is possible. This information flow is sent in unicast (to the granted transmission control participant). + +**Table 7.7.1.2.3-1: Transmit media granted** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the transmission control participant is required | + +##### 7.7.1.2.4 Transmit media rejected + +Table 7.7.1.2.4-1 describes the information flow transmit media rejected, from the transmission control server to the transmission control participant, which is used to indicate that a transmit media request is rejected. This information flow is sent in unicast (to the refused transmission control participant). + +**Table 7.7.1.2.4-1: Transmit media rejected** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Rejection cause | O | Indicates the cause for transmit media rejection | +| Acknowledgement required | O | Indicates if acknowledgement from the transmission control participant is required | + +##### 7.7.1.2.5 Media transmission notification + +Table 7.7.1.2.5-1 describes the information flow media transmission notification, from the transmission control server to the transmission control participant, which is used to indicate that a media transmission is available from another user. This information flow is sent in unicast (to the receiving transmission control participant). + +**Table 7.7.1.2.5-1: Media transmission notification** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of the user who is transmitting the media | +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.6 Receive media request + +Table 7.7.1.2.6-1 describes the information flow receive media request, from the transmission control participant to the transmission control server, which is used to request the reception of the media from another user. This information flow is sent in unicast (to the transmission control server). + +**Table 7.7.1.2.6-1: Receive media request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of the user who is requesting the reception of the media | +| Source MCVideo ID | M | Identity of the user who is transmitting the media | +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.7 Receive media response + +Table 7.7.1.2.7-1 describes the information flow receive media response, from the transmission control server to the transmission control participant, which is used to indicate whether the media reception is possible or not. This information flow is sent in unicast (to the receiving transmission control participant). + +**Table 7.7.1.2.7-1: Receive media response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Result | M | Indicates whether media reception is possible as per the request | +| Rejection cause | O | Indicates the cause for rejecting the media receive request | +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.8 Media reception notification + +Table 7.7.1.2.8-1 describes the information flow media reception notification, from the transmission control server to the transmission control participant, which is used to indicate that a media reception has been initiated to a user. This information flow is sent in unicast (to the transmitting transmission control participant). + +**Table 7.7.1.2.8-1: Media reception notification** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of the user who is receiving the media | +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.9 Queue position info + +Table 7.7.1.2.9-1 describes the information flow queue position info, from the transmission control server to the transmission control participant, which is used to indicate that the transmit media request is queued and the queue position to the transmit media requesting UE. The MCVideo server and the MCVideo client support queuing of the transmit media requests shall support this information flow. This information flow is sent in unicast (to the queued transmission control participant). + +**Table 7.7.1.2.9-1: Queue position info** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Queue position info | M | Position of the queued transmit media request in the queue | +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the transmission control participant is required | + +##### 7.7.1.2.10 Transmission revoked + +Table 7.7.1.2.10-1 describes the information flow transmission revoked, from the transmission control server to the transmission control participant, which is used to indicate that the on-going video transmission is queued and the queue position is provided or the on-going video transmission is terminated. This information flow is sent in unicast (to the queued transmission control participant). + +**Table 7.7.1.2.10-1: Transmission revoked** + +| Information element | Status | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-------------------------------------------------------------------------------------------------------------------------------| +| Revoke reason | M | The reason for revoke like queue or termination of on-going video transmission | +| Queue position info | O (see NOTE1) | Position of the queued transmit media request in the queue | +| Media identifier | O (see NOTE2) | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the transmission control participant is required | +| NOTE1: If revoke reason is queuing, then queue position info is included.<br>NOTE2: If revoke reason is termination, then media identifier is included. | | | + +##### 7.7.1.2.11 Queue position request + +Table 7.7.1.2.11-1 describes the information flow queue position request, from the transmission control participant to the transmission control server, which is used to request the position in the video transmission queue. The MCVideo server and the MCVideo client support queuing of the transmission control requests shall support this information flow. This information flow is sent in unicast to the transmission control server. + +**Table 7.7.1.2.11-1: Queue position request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.12 Transmit media cancel request + +Table 7.7.1.2.12-1 describes the information flow transmit media cancel request, from the transmission control participant to the transmission control server. This information flow is sent in unicast to the transmission control server. + +**Table 7.7.1.2.12-1: Transmit media cancel request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of the user whose media transmission is requested for cancellation | +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.13 Transmit media cancel response + +Table 7.7.1.2.13-1 describes the information flow transmit media cancel response, from the transmission control server to the transmission control participant. This information flow is sent in unicast to the transmission control server. + +**Table 7.7.1.2.13-1: Transmit media cancel response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.14 Transmit media cancel request notify + +Table 7.7.1.2.14-1 describes the information flow transmit media cancel request notify, from the transmission control server to the transmission control participant. This information flow is sent in unicast to the transmission control server. + +**Table 7.7.1.2.14-1: Transmit media cancel request notify** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.15 Transmit media end request + +Table 7.7.1.2.15-1 describes the information flow transmit media end request, from the transmission control participant to the transmission control server and from the transmission control server to the transmission control participant. This information flow is sent in unicast to the transmission control server/transmission control participant. + +**Table 7.7.1.2.15-1: Transmit media end request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of the user whose media transmission is requested to be terminated. | +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.16 Transmit media end response + +Table 7.7.1.2.16-1 describes the information flow transmit media end response, from the transmission control participant and the transmission control server and from the transmission control server to the transmission control participant. This information flow is sent in unicast to the transmission control server/transmission control participant. + +**Table 7.7.1.2.16-1: Transmit media end response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.17 Remote transmit media request + +Table 7.7.1.2.17-1 describes the information flow remote transmit media request, from the transmission control participant to the transmission control server. This information flow is sent in unicast to the transmission control server. + +**Table 7.7.1.2.17-1: Remote transmit media request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of the user who remotely initiated the media transmission of another user. | +| MCVideo ID | M | Identity of the user whose media transmission is requested | +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.18 Remote transmit media response + +Table 7.7.1.2.18-1 describes the information flow remote transmit media response, from the transmission control server to the transmission control participant. This information flow is sent in unicast to the transmission control participant. + +**Table 7.7.1.2.18-1: Remote transmit media response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.19 Remote transmit media end request + +Table 7.7.1.2.19-1 describes the information flow remote transmit media end request, from the transmission control participant to the transmission control server. This information flow is sent in unicast to the transmission control server. + +**Table 7.7.1.2.19-1: Remote transmit media end request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of the user whose media transmission is requested for cancellation | +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.20 Remote transmit media cancel response + +Table 7.7.1.2.20-1 describes the information flow transmit media end response, from the transmission control server to the transmission control participant. This information flow is sent in unicast to the transmission control server. + +**Table 7.7.1.2.20-1: Remote transmit media end response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.21 Media reception end request + +Table 7.7.1.2.21-1 describes the information flow media reception end request, from the transmission control server to the transmission control participant and from the transmission control participant to the transmission control server. + +**Table 7.7.1.2.21-1: Media reception end request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of the user whose media receipt is requested for cancellation | +| Media identifier | M | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.22 Media reception end response + +Table 7.7.1.2.22-1 describes the information flow media reception end response, from the transmission control server to the transmission control participant and from the transmission control participant to the transmission control server. + +**Table 7.7.1.2.22-1: Media reception end response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| /Media identifier | M | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.23 Media reception override notification + +Table 7.7.1.2.23-1 describes the information flow media reception override notification, from the transmission control server to the transmission control participant. + +**Table 7.7.1.2.23-1: Media reception override notification** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of the user who is requesting the reception of the media | +| MCVideo ID | O | Identity of the user of the overriding media | +| Media identifier | M | Identifies the communication of overriding media, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| MCVideo ID | O | Identity of the user of the overridden media | +| Media identifier | M | Identifies the communication of overridden media, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.1.2.24 Transmit media end notify + +Table 7.7.1.2.24-1 describes the information flow transmit media end notify, from the transmission control server to the transmission control participant. This information flow is sent in unicast to the transmission control server. + +**Table 7.7.1.2.24-1: Transmit media end notify** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of the user whose media transmission has been released | +| Media identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +#### 7.7.1.3 Transmission control within one MC system for MCVideo service + +##### 7.7.1.3.1 Transmission control during an MCVideo session + +Figure 7.7.1.3.1-1 describes the procedure for transmission control between the transmission control participant and the transmission control server during an MCVideo session. Only two UEs involved in the session are shown for the simplicity. + +Pre-condition: + +1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server +2. Transmission control is established between transmission control participants and transmission control server and there is no ongoing media transmission. + +![Sequence diagram illustrating transmission control during an MCVideo session. Lifelines: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence shows: 1. User wants to transmit media; 2. Transmit media request; 3. Based on group policy, user authorization, maximum simultaneous transmission check, permit the media transmission; 4a. Transmit media granted or 4b. Transmit media rejected or 4c. Queue position info; 5. Transmit media granted notification; 6. Video transmission.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +sequenceDiagram + participant A as Transmission control participant A + participant S as Transmission control server + participant B as Transmission control participant B + Note left of A: 1. User wants to transmit media + A->>S: 2. Transmit media request + Note right of S: 3. Based on group policy, user authorization, maximum simultaneous transmission check, permit the media transmission + S-->>A: 4a. Transmit media granted or 4b. Transmit media rejected or 4c. Queue position info + Note left of A: 5. Transmit media granted notification + A->>S: 6. Video transmission + +``` + +Sequence diagram illustrating transmission control during an MCVideo session. Lifelines: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence shows: 1. User wants to transmit media; 2. Transmit media request; 3. Based on group policy, user authorization, maximum simultaneous transmission check, permit the media transmission; 4a. Transmit media granted or 4b. Transmit media rejected or 4c. Queue position info; 5. Transmit media granted notification; 6. Video transmission. + +**Figure 7.7.1.3.1-1: Transmission control during an MCVideo session** + +1. Transmission control participant A wants to send video media over the session. +2. Transmission control participant A sends a transmit media request message to transmission control server which includes transmission priority and other information as necessary. +3. Transmission control server makes the determination on what action (grant, deny, or queue) to take on the request based on transmission control criteria (e.g., group policy) and determines to accept the transmit media request from transmission control participant A. +4. Transmission control server responds with a transmit media granted message (4a) to transmission control participant A. Transmission control server may send transmit media rejected message (4b) indicating the cause of rejection or queue position info message (4c) indicating that the transmit media request has been queued. +5. The transmit media granted shall cause the user of UE A where the transmission control participant A is located to be notified. +6. Transmission control participant A starts sending video media over the session established to the transmission control server. + +##### 7.7.1.3.2 Reception control during an MCVideo session + +Figure 7.7.1.3.2-1 describes the procedure for the reception control between the transmission control participant and the transmission control server during an MCVideo session. Only two UEs involved in the session are shown for the simplicity. + +Pre-condition: + +1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server +2. Transmission control is established between transmission control participants and transmission control server. +3. Transmission control participant A has been granted the permission to transmit media. + +![Sequence diagram illustrating reception control during an MCVideo session. The diagram shows interactions between Transmission control participant A, Transmission control server, and Transmission control participant B. The process involves the server deciding a reception mode, notifying participant B, who then informs the user. The user may request to receive media, which the server checks against criteria and responds to. Finally, the server transmits the video and optionally notifies participant A.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +``` + +sequenceDiagram + participant A as Transmission control participant A + participant S as Transmission control server + participant B as Transmission control participant B + Note right of S: 1. Based on configurations, network conditions, decide the reception mode + S->>B: 2. Media transmission notification + Note right of B: 3. Media transmission notification + Note right of B: 4. User wants to receive media + B->>S: 5. Receive media request + Note right of S: 6. Determine the availability of the media and reception criteria check like maximum simultaneous receptions + S->>B: 7. Receive media response + Note right of S: 8. Video transmission + S-->>A: 9. Media reception notification + +``` + +Sequence diagram illustrating reception control during an MCVideo session. The diagram shows interactions between Transmission control participant A, Transmission control server, and Transmission control participant B. The process involves the server deciding a reception mode, notifying participant B, who then informs the user. The user may request to receive media, which the server checks against criteria and responds to. Finally, the server transmits the video and optionally notifies participant A. + +**Figure 7.7.1.3.2-1: Reception control during an MCVideo session** + +1. The transmission control server determines the reception mode for downlink transmission control participants for the media transmission permitted to transmission control participant A. The manual and forced reception modes are determined based on configurations (e.g. auto-receive video transmissions, auto-receive emergency video transmissions) as described in Annex A. +2. Transmission control server sends a media transmission notification message to the transmission control participant B including information about the video transmitter and the reception mode. +3. The receipt of the media transmission notification is used to inform the user of UE B the details of video transmission and the video transmitter. +4. Based on the notification received, the user of UE B may want take actions (receive, reject or cancel) regarding the media available for reception. +5. If user of UE B wants to receive the media or it required to receive the media via forced reception, it causes the transmission control participant B to send a media receive request message to the transmission control server. +6. Transmission control server makes the determination on what action (e.g., real-time stream downlink, make stream downloadable, reject) to take on the request based on reception control criteria (e.g., allowed simultaneous reception) and determines to accept the media receive request from transmission control participant B. Transmission control server will also determine the availability of the media at the server to initiate the downlink reception. +7. Transmission control server sends a receive media response message to transmission control participant B. +8. Transmission control server sends video media to transmission control participant B. +9. Optionally, the transmission control server sends media reception notification message to transmission control participant A which includes the information about the video recipient (transmission control participant B). + +##### 7.7.1.3.2A End media reception – receiving user initiated + +Figure 7.7.1.3.2A-1 describes the procedure for the receiving user initiated media reception end. Only two UEs involved in the session are shown for the simplicity. + +Pre-condition: + +1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server +2. Transmission control is established between transmission control participants and transmission control server. +3. Transmission control participant A has been granted the permission to transmit media. + +![Sequence diagram for Figure 7.7.1.3.2A-1: End media reception – receiving user initiated. The diagram shows three lifelines: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence of messages is: 1. User determines to end receiving the video stream (from participant B to server); 2. Media reception end request (from participant B to server); 3. Media reception end response (from server to participant B); 4. stop sending downlink video stream selected to be ended by user (from server to participant B); 5. Optionally, transmission control server initiated end media transmission procedure as described in subclause 7.7.1.3.6.2 (from server to participant A, enclosed in a dashed box).](315bdbeafb39026e19b77c26b19d9d1f_img.jpg) + +``` + +sequenceDiagram + participant B as Transmission control participant B + participant S as Transmission control server + participant A as Transmission control participant A + Note right of B: 1. User determines to end receiving the video stream. + B->>S: 2. Media reception end request + S-->>B: 3. Media reception end response + Note right of S: 4. stop sending downlink video stream selected to be ended by user + S-->>A: 5. Optionally, transmission control server initiated end media transmission procedure as described in subclause 7.7.1.3.6.2. + +``` + +Sequence diagram for Figure 7.7.1.3.2A-1: End media reception – receiving user initiated. The diagram shows three lifelines: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence of messages is: 1. User determines to end receiving the video stream (from participant B to server); 2. Media reception end request (from participant B to server); 3. Media reception end response (from server to participant B); 4. stop sending downlink video stream selected to be ended by user (from server to participant B); 5. Optionally, transmission control server initiated end media transmission procedure as described in subclause 7.7.1.3.6.2 (from server to participant A, enclosed in a dashed box). + +**Figure 7.7.1.3.2A-1: End media reception – receiving user initiated** + +1. The MCVideo user determines to end a receiving video stream. +2. The user sends an media reception end request including the video stream to be ended to the transmission control server. +3. The transmission control server returns a media reception end response. +4. Upon receiving the media reception end request, the transmission control server stops sending the video stream selected to the transmission control participant B. +5. If the end media reception at transmission control participant B causes the video transmission continuation condition to fail, then the transmission control server initiates the media transmission end procedure as described in subclause 7.7.1.3.6.2. + +##### 7.7.1.3.2B End media reception – transmission control server initiated + +Figure 7.7.1.3.2B-1 describes the procedure for the transmission control server initiated media reception end. Only two UEs involved in the session are shown for the simplicity. + +Pre-condition: + +1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server +2. Transmission control is established between transmission control participants and transmission control server. +3. Transmission control participant A has been granted the permission to transmit media. + +![Sequence diagram for 'End media reception – transmission control server initiated'. Lifelines: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence starts with the server determining to end the stream (1), sending a request to participant B (2), notifying the user (3), receiving a response (4), and stopping the stream (5). A dashed box indicates an optional step (6) where the server initiates a media transmission end procedure.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +``` + +sequenceDiagram + participant A as Transmission control participant A + participant S as Transmission control server + participant B as Transmission control participant B + Note right of S: 1. Determine to end the video stream transmitting to transmission control participant B + S->>B: 2. Media reception end request + Note right of B: 3. notify user + B->>S: 4. Media reception end response + Note right of S: 5. stop sending the downlink video stream + Note left of A: 6. Optionally, transmission control server initiated end media transmission procedure as described in subclause 7.7.1.3.6.2. + +``` + +Sequence diagram for 'End media reception – transmission control server initiated'. Lifelines: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence starts with the server determining to end the stream (1), sending a request to participant B (2), notifying the user (3), receiving a response (4), and stopping the stream (5). A dashed box indicates an optional step (6) where the server initiates a media transmission end procedure. + +**Figure 7.7.1.3.2B-1: End media reception – transmission control server initiated** + +1. The transmission control server determines to end a video stream transmitting to transmission control participant B according to events or configurations. +2. The transmission control server sends an media reception end request including the video stream to be ended to the transmission control participant B. +3. The MCVideo user is notified about the media reception end. +4. The transmission control participant B returns a media reception end response. +5. The transmission control server stops sending the video stream selected to the transmission control participant B. +6. If the end media reception at transmission control participant B causes the continuation conditions to fail, then the transmission control server initiates media transmission end procedure as described in subclause 7.7.1.3.6.2. + +##### 7.7.1.3.2C Reception control on overridden – mandatory mode + +Figure 7.7.1.3.2C-1 describes the procedure for the reception control on overridden with mandatory mode that the transmission control server determines the video stream to be overridden. Only two UEs involved in the session are shown for the simplicity. + +Pre-condition: + +1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server. +2. Transmission control is established between transmission control participants and transmission control server. +3. Transmission control participant A has been granted the permission to transmit media. + +![Sequence diagram showing reception control on overriding/overridden in mandatory mode. Lifelines: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence starts with the server detecting the maximum number of simultaneous receiving streams. It then sends a media reception override notification to participant B, who notifies the user. The server then initiates a media reception end procedure, followed by a normal reception control procedure.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +``` + +sequenceDiagram + participant A as Transmission control participant A + participant S as Transmission control server + participant B as Transmission control participant B + Note right of S: 1. Maximum number of simultaneous receiving streams detect + S->>B: 2. Media reception override notification + Note right of B: 3. Notify user the override + Note right of S: 4. Transmission control server initiated media reception end procedure as described in subclause 7.7.1.3.2.B + Note right of S: 5. Normal reception control procedure as described in subclause 7.7.1.3.2. + +``` + +Sequence diagram showing reception control on overriding/overridden in mandatory mode. Lifelines: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence starts with the server detecting the maximum number of simultaneous receiving streams. It then sends a media reception override notification to participant B, who notifies the user. The server then initiates a media reception end procedure, followed by a normal reception control procedure. + +**Figure 7.7.1.3.2C-1: Reception control on overriding/overridden – mandatory mode** + +1. A new media stream is to be delivered to the transmission control participant B while the maximum number of simultaneous streams is reached. The transmission control server determines to override another media stream being received by the transmission control participant B accord to the media stream characteristics. +2. Transmission control server sends a media reception override notification message to the transmission control participant B including information about the video stream being overridden and stop the downlink delivery of the overridden video stream to the transmission control participant B. The overriding video stream information maybe also included. +3. The user of UE B is notified about the details of overriding/overridden. +4. The transmission control server initiates the media reception end procedure as described in subclause 7.7.1.3.2B. + 5. The transmission control server performs the normal reception control procedure as described in subclause 7.7.1.3.2. + +##### **7.7.1.3.2D Reception control on overridden – negotiated mode** + +Figure 7.7.1.3.2D-1 describes the procedure for the reception control on overridden with negotiated mode that the transmission control participant determines the video stream to be overridden. Only two UEs involved in the session are shown for the simplicity. + +Pre-condition: + +1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server +2. Transmission control is established between transmission control participants and transmission control server. +3. Transmission control participant A has been granted the permission to transmit media. + +![Sequence diagram illustrating Reception control on overriding/overridden – negotiated mode. The diagram shows three lifelines: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence of events is: 1. Maximum number of simultaneous receiving streams detect (within a self-call on the server); 2. Media transmission notification (server to participant B); 3. Notify user and the user determines to reject or override (within a self-call on participant B); 4. User initiated media reception end procedure as described in subclause 7.7.1.3.2A. (a horizontal bar spanning all three lifelines); 5. Request to receive newly video stream as described in subclause 7.7.1.3.2. (a horizontal bar between participant B and the server).](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +Sequence diagram illustrating Reception control on overriding/overridden – negotiated mode. The diagram shows three lifelines: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence of events is: 1. Maximum number of simultaneous receiving streams detect (within a self-call on the server); 2. Media transmission notification (server to participant B); 3. Notify user and the user determines to reject or override (within a self-call on participant B); 4. User initiated media reception end procedure as described in subclause 7.7.1.3.2A. (a horizontal bar spanning all three lifelines); 5. Request to receive newly video stream as described in subclause 7.7.1.3.2. (a horizontal bar between participant B and the server). + +**Figure 7.7.1.3.2D-1: Reception control on overriding/overridden – negotiated mode** + +1. A new media stream is to be delivered to the transmission control participant B while the maximum number of simultaneous streams is received. The transmission control server determines to override another media stream being received by the transmission control participant B according to the media stream characteristics. +2. Transmission control server sends a media transmission notification message to the transmission control participant B including information about the new video stream. +3. The user of transmission control participant B is notified about the maximum number of simultaneous streams received. The MCVideo user determines to reject the video stream or accept the video streaming by overriding a receiving video stream. +4. The transmission control participant initiates the media reception end procedure as described in subclause 7.7.1.3.2A. +5. Then the transmission control participant B requests to receive the new video stream as the normal reception control procedure described in subclause 7.7.1.3.2. + +##### 7.7.1.3.3 Transmission revoke during an MCVideo session + +Figure 7.7.1.3.3-1 describes the procedure for transmission revoke during an MCVideo session. Only two UEs involved in the session are shown for the simplicity. + +Pre-condition: + +1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server +2. Transmission control is established between transmission control participants and transmission control server. +3. Transmission control participant B has been granted the permission to transmit media and there may be ongoing media transmission from transmission control participant B. +4. The maximum media transmission limit for the MCVideo session is reached. + +![Sequence diagram illustrating the transmission revoke during an MCVideo session. The diagram shows three lifelines: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence of messages is: 1. User wants to transmit media (internal to A), 2. Transmit media request (A to Server), 3. Pre-empting by queuing or terminating the on-going transmission (internal to Server), 4a. Transmission revoked (Server to B), 4b. Transmit media granted (Server to A), 5b. Transmit media granted notification (internal to A), 5a. Transmission revoke notification (internal to B), 6. Video transmission (A to Server).](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` + +sequenceDiagram + participant A as Transmission control participant A + participant S as Transmission control server + participant B as Transmission control participant B + Note left of A: 1. User wants to transmit media + A->>S: 2. Transmit media request + Note right of S: 3. Pre-empting by queuing or terminating the on-going transmission. + S->>B: 4a. Transmission revoked + S->>A: 4b. Transmit media granted + Note left of A: 5b. Transmit media granted notification + Note right of B: 5a. Transmission revoke notification + Note right of A: 6. Video transmission + A->>S: 6. Video transmission + +``` + +Sequence diagram illustrating the transmission revoke during an MCVideo session. The diagram shows three lifelines: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence of messages is: 1. User wants to transmit media (internal to A), 2. Transmit media request (A to Server), 3. Pre-empting by queuing or terminating the on-going transmission (internal to Server), 4a. Transmission revoked (Server to B), 4b. Transmit media granted (Server to A), 5b. Transmit media granted notification (internal to A), 5a. Transmission revoke notification (internal to B), 6. Video transmission (A to Server). + +**Figure 7.7.1.3.3-1: Transmission revoke during an MCVideo session** + +1. Transmission control participant A wants to send video media over the session. +2. Transmission control participant A sends a transmit media request message to transmission control server which includes transmission priority and other information as necessary. +3. Transmission control server determines to accept the transmit media request from transmission control participant A and decides to pre-empt the on-going video transmission from transmission control participant B by queuing or ending the on-going video transmission. +4. Transmission control server responds with a transmission revoked message (4a) to transmission control participant B with the action of pre-emption whether queued or terminated. Transmission control server responds with a transmit media granted message (4b) to transmission control participant A. +5. The transmission revoked shall cause the transmission control participant B to be notified of the revoke (5a) of the on-going video transmission by queuing or termination. The transmit media granted shall cause the user of UE A where the transmission control participant A is located to be notified. +6. Transmission control participant A starts sending video media over the session established to the transmission control server. + +##### 7.7.1.3.4 Queue position during an MCVideo session + +Figure 7.7.1.3.4-1 describes the procedure where the transmission control is conducted for the MCVideo session already established between MCVideo clients (with transmit media granted to transmission control participant B) and server (with an revoke determination at transmission control server). Only two UEs involved in the session are shown for the simplicity. + +![Sequence diagram illustrating the queue status during an MCVideo session. The diagram shows interactions between Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence starts with a message from participant B to the server, followed by a message from participant A to the server, and then a response from the server to participant A.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` + +sequenceDiagram + participant A as Transmission control participant A + participant S as Transmission control server + participant B as Transmission control participant B + Note right of B: 1. MCVideo session is established. Transmission control is established between transmission control participants and transmission control server. Transmit media is granted to transmission control participant B. Many transmission control participants have requested permission to transmit media which have got queued. + Note left of A: 2. User wants to know queue position + A->>S: 3. Queue position request + S-->>A: 4. Current queue position for transmission control participant A + S-->>A: 5. Queue position info + Note left of A: 6. User is informed about queue position + +``` + +Sequence diagram illustrating the queue status during an MCVideo session. The diagram shows interactions between Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence starts with a message from participant B to the server, followed by a message from participant A to the server, and then a response from the server to participant A. + +**Figure 7.7.1.3.4-1: Queue status during an MCVideo session** + +1. It is assumed that transmission control participant B has been granted permission to transmit media and is transmitting video media. There are several other transmission control participants (including transmission control participant A) requesting video transmission which get queued at the transmission control server. +2. Transmission control participant A would like to know its current position in the video transmission queue. +3. Transmission control participant A sends a queue position request message to the transmission control server. +4. Transmission control server determines the current queue position of transmission control participant A from the video transmission queue. +5. Transmission control server responds with the current position in queue position info message. +6. User at transmission control participant A is informed about the current queue position. + +##### 7.7.1.3.5 Transmit media request cancellation from the video transmission queue + +###### 7.7.1.3.5.1 Transmit media request cancellation from the queue – MCVideo user initiated + +Figure 7.7.1.3.5.1-1 illustrates the procedure for transmit media request cancellation from the video transmission queue initiated by the MCVideo user. The MCVideo user may be an authorized user who has rights to cancel the transmit media requests of other MCVideo users, whose transmit media requests are in video transmission queue. + +Pre-conditions: + +- It is assumed that transmission control participant B has been granted the permission for video transmission and is transmitting video. There are several other transmission control participants (including transmission control participant A and transmission control participant C) requesting the permission to transmit media which have been queued at the transmission control server. + +![Sequence diagram for Transmit media request cancellation from queue initiated by MCVideo user.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +``` + +sequenceDiagram + participant A as Transmission control participant A + participant S as Transmission control server + participant B as Transmission control participant B + participant C as Transmission control participant C + + Note over A, C: Transmission control is established between transmission control participants and transmission control server. +Permission to transmit media is granted to transmission control participant B, and transmit media requests of +Transmission control participant A and transmission control participant C are in the video transmission queue. + + Note left of A: 1. User wants to cancel a +transmit media request from +the video transmission queue + A->>S: 2. Transmit media cancel request + Note right of S: 3. Authorization check, and +remove transmit media request +from the video transmission +queue + S-->>C: 4. Transmit media cancel request notify + S-->>A: 5. Transmit media cancel +response + +``` + +Sequence diagram for Transmit media request cancellation from queue initiated by MCVideo user. + +**Figure 7.7.1.3.5.1-1: Transmit media request cancellation from queue initiated by MCVideo user** + +1. The transmission control participant A wants to remove the transmit media request from the video transmission queue. If transmission control participant A is an authorized MCVideo user with the rights to cancel another MCVideo user's transmit media request, the authorized MCVideo user may request for transmit media request cancellation for one or more transmission control participants, whose transmit media request needs to be removed from the video transmission queue. +2. The transmission control participant A sends a transmit media cancel request (initiating MCVideo ID) message to the transmission control server. If the transmission control participant A wants to remove the transmit media request(s) of other participant(s), the target participant(s)' MCVideo ID should be included in this message. +3. The transmission control server shall check whether the requesting transmission control participant has authorization to cancel the transmit media request(s). If authorized, the transmit media request(s) will be removed from the video transmission queue. When the on-going transmissions are completed and are within the limit of the maximum simultaneous transmissions, the transmission control server will process the transmit media request from the updated video transmission queue. +4. If the transmit media cancel request in step 3 is sent by an authorized user (e.g., dispatcher) to cancel the transmit media request(s) of other participant(s) from the video transmission queue, the transmit media cancel request notify message is sent to the transmission control participant whose transmit media request was cancelled from the video transmission queue. +5. The transmission control server provides a transmit media cancel response to the transmission control participant A when the transmit media request cancellation is completed. Optionally, the new queue position information may be notified to the transmission control participants whose transmit media requests are in the video transmission queue (not shown in the figure). + +###### 7.7.1.3.5.2 Transmit media request cancellation from the queue - transmission control server initiated + +Figure 7.7.1.3.5.2-1 illustrates the procedure for transmit media request cancellation from the queue initiated by the transmission control server. Only two UEs involved in the session are shown for the simplicity. + +Pre-conditions: + +- It is assumed that transmission control participant B has been granted the permission to transmit media and is transmitting video. There are several other transmission control participants (including transmission control participant A and participant C) requesting the permission to transmit media which have been queued at the transmission control server. + +![Sequence diagram for transmit media request cancellation from queue initiated by transmission control server. The diagram shows three lifelines: Transmission control participant A, Transmission control server, and Transmission control participant C. A pre-condition box states that transmission control is established, participant B has permission, and participants A and C have requests in the queue. The server performs three steps: 1. Remove the transmit request from the video transmission queue based on policy; 2. Transmit media cancel request notify to participant A; 3. Queue position info to participant C.](8269648391c59363ea61243864a2adf7_img.jpg) + +``` + +sequenceDiagram + participant A as Transmission control participant A + participant S as Transmission control server + participant C as Transmission control participant C + Note right of S: Transmission control is established between transmission control participants and transmission control server. Now permission to transmit media is granted to participant B, and transmission control participant A and participant C have transmit media requests being put into the queue. + S->>A: 2. Transmit media cancel request notify + S-->>C: 3. Queue position info + Note left of S: 1. Remove the transmit request from the video transmission queue based on policy + +``` + +Sequence diagram for transmit media request cancellation from queue initiated by transmission control server. The diagram shows three lifelines: Transmission control participant A, Transmission control server, and Transmission control participant C. A pre-condition box states that transmission control is established, participant B has permission, and participants A and C have requests in the queue. The server performs three steps: 1. Remove the transmit request from the video transmission queue based on policy; 2. Transmit media cancel request notify to participant A; 3. Queue position info to participant C. + +**Figure 7.7.1.3.5.2-1: Transmit media request cancellation from queue initiated by transmission control server** + +1. The transmission control server removes the transmit media request from the video transmission queue based on policy. e.g., expiration of a timer. In the case when transmission control server receives repeated transmit media requests from a transmission control participant while the limit for maximum simultaneous media transmissions has reached, the new transmit media request is accepted and added into the video transmission queue and the existing/former transmit media request is removed from the video transmission queue or the new transmit media request is rejected and the existing/former transmit media request of this transmission control participant is retained in the video transmission queue. +2. The transmission control server sends a transmit media cancel request notify to the transmission control participant(s) whose transmit media request is removed from the video transmission queue. +3. Optionally, the new queue position information is notified to the other transmission control participants whose transmit media requests are queued. + +##### 7.7.1.3.6 End a media transmission during an MCVideo session + +###### 7.7.1.3.6.1 End a media transmission – MCVideo user initiated + +Figure 7.7.1.3.6.1-1 describes the procedure for ending a media transmission during an MCVideo session by a MCVideo user. Only two UEs involved in the session are shown for the simplicity. + +Pre-condition: + +1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server +2. Transmission control is established between transmission control participants and transmission control server. +3. Transmission control participant A and participant B have been granted the permission to transmit media and there are ongoing media transmission from transmission control participant A and participant B. + +![Sequence diagram for ending a media transmission by an MCVideo user. Lifelines: Transmission control participant A, Transmission control server, Transmission control participant B. Steps: 1. Transmit media end request (A to Server), 2. Terminate the on-going media transmission (Server internal), 3. Transmit media end response (Server to A), 4. Transmit media end notify (Server to B), 5. Media transmission end notification (B internal).](32ff77da4286b58c4778033acaa10836_img.jpg) + +``` +sequenceDiagram + participant A as Transmission control participant A + participant S as Transmission control server + participant B as Transmission control participant B + Note right of S: 2. Terminate the on-going media transmission + A->>S: 1. Transmit media end request + S-->>A: 3. Transmit media end response + S->>B: 4. Transmit media end notify + Note right of B: 5. Media transmission end notification +``` + +Sequence diagram for ending a media transmission by an MCVideo user. Lifelines: Transmission control participant A, Transmission control server, Transmission control participant B. Steps: 1. Transmit media end request (A to Server), 2. Terminate the on-going media transmission (Server internal), 3. Transmit media end response (Server to A), 4. Transmit media end notify (Server to B), 5. Media transmission end notification (B internal). + +**Figure 7.7.1.3.6.1-1: End a media transmission by an MCVideo user** + +1. Transmission control participant A wants to end its media transmission in a session and sends a transmit media end request message to transmission control server. +2. Transmission control server terminates the on-going media transmission from transmission control participant A. +3. Transmission control server responds with a transmit media end response message to transmission control participant A indicating that the transmission control server has terminated the media transmission. +4. Transmission control server sends a transmit media end notify message to transmission control participant B indicating that the media transmission from transmission control participant A is terminated by the user. +5. The transmit media end notification shall cause the user of the transmission control participant B to be notified of the media transmission termination by the sending user. + +###### **7.7.1.3.6.2 End a media transmission – transmission control server initiated** + +Figure 7.7.1.3.6.2-1 describes the procedure for ending a media transmission during an MCVideo session by the transmission control server. Only two UEs involved in the session are shown for the simplicity. + +Pre-condition: + +1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server +2. Transmission control is established between transmission control participants and transmission control server. +3. Transmission control participant A and participant B have been granted the permission to transmit media and there are ongoing media transmission from transmission control participant A and participant B. + +![Sequence diagram for ending a media transmission by the transmission control server. Lifelines: Transmission control participant A, Transmission control server, Transmission control participant B. Steps: 1. Terminate the on-going media transmission from transmission control participant A (Server internal), 2. Transmit media end request (Server to A), 3. Transmit media end response (A to Server), 4. Transmit media end notify (Server to B), 5. Media transmission end notification (B internal).](8d8c758885b4f754ff071bf3b572ab3c_img.jpg) + +``` +sequenceDiagram + participant A as Transmission control participant A + participant S as Transmission control server + participant B as Transmission control participant B + Note right of S: 1. Terminate the on-going media transmission from transmission control participant A + S->>A: 2. Transmit media end request + A-->>S: 3. Transmit media end response + S->>B: 4. Transmit media end notify + Note right of B: 5. Media transmission end notification +``` + +Sequence diagram for ending a media transmission by the transmission control server. Lifelines: Transmission control participant A, Transmission control server, Transmission control participant B. Steps: 1. Terminate the on-going media transmission from transmission control participant A (Server internal), 2. Transmit media end request (Server to A), 3. Transmit media end response (A to Server), 4. Transmit media end notify (Server to B), 5. Media transmission end notification (B internal). + +**Figure 7.7.1.3.6.2-1: End a media transmission by the transmission control server** + +1. Transmission control server terminates the on-going media transmission from transmission control participant A due to a termination event (e.g. revoke for another priority media transmission or there are no receiving participants). +2. Transmission control server sends a transmit media end request message to transmission control participant A indicating the reason for ending the media transmission. +3. Transmission control participant A responds with a transmit media end response message to transmission control server as acknowledgement +4. Transmission control server sends a transmit media end notify message to transmission control participant B indicating that the media transmission from transmission control participant A is terminated by the transmission control server. +5. The transmit media end notification shall cause the user of the transmission control participant B to be notified of the media transmission termination by the transmission control server. + +###### 7.7.1.3.6.3 End a media transmission – remote MCVideo user initiated + +Figure 7.7.1.3.6.3-1 describes the procedure for ending a media transmission during an MCVideo session by a remote MCVideo user. Only two UEs involved in the session are shown for the simplicity. + +Pre-condition: + +1. MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server +2. Transmission control is established between transmission control participants and transmission control server. +3. Transmission control participant B has been granted the permission to transmit media and there is ongoing media transmission from transmission control participant B. +4. Transmission control participant A is authorized to end the on-going media transmission from transmission control participant B. + +![Sequence diagram illustrating the procedure for ending a media transmission by a remote MCVideo user. The diagram shows three participants: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence of messages is: 1. Remote transmit media end request from A to Server; 2. Authorization check for remote termination of the on-going media transmission from participant B (internal to Server); 3. Terminate the on-going media transmission from transmission control participant B (internal to Server); 4. Remote transmit media end response from Server to A.](a97518a839da75f8379c578562b01bc2_img.jpg) + +``` + +sequenceDiagram + participant A as Transmission control participant A + participant S as Transmission control server + participant B as Transmission control participant B + Note right of S: 2. Authorization check for remote termination of the on-going media transmission from transmission control participant B + Note right of S: 3. Terminate the on-going media transmission from transmission control participant B + A->>S: 1. Remote transmit media end request + S-->>A: 4. Remote transmit media end response + +``` + +Sequence diagram illustrating the procedure for ending a media transmission by a remote MCVideo user. The diagram shows three participants: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence of messages is: 1. Remote transmit media end request from A to Server; 2. Authorization check for remote termination of the on-going media transmission from participant B (internal to Server); 3. Terminate the on-going media transmission from transmission control participant B (internal to Server); 4. Remote transmit media end response from Server to A. + +**Figure 7.7.1.3.6.3-1: End a media transmission by a remote MCVideo user** + +1. Transmission control participant A sends a remote transmit media end request message to transmission control server including the MCVideo ID of the user at the UE of the transmission control participant B and the MCVideo ID of the user at the UE of the transmission control participant A. +2. Transmission control server checks whether the user at the UE of transmission control participant A is authorized to end the on-going media transmission from transmission control participant B. If authorized, the transmission control server ends the media transmission from transmission control participant B. +3. Transmission control server ends the on-going media transmission from transmission control participant B. The transmission control server shall send transmit media end notify messages to the transmission control participants receiving the media transmission from transmission control participant B, indicating that the transmission has ended. + +- Transmission control server responds with a remote transmit media end response message to transmission control participant A indicating that the transmission control server has ended the requested media transmission. + +##### 7.7.1.3.7 Remotely initiated media transmission during an MCVideo session + +Figure 7.7.1.3.7-1 describes the procedure for remotely initiated media transmission during an MCVideo session by an authorized user. Only two UEs involved in the session are shown for the simplicity. + +Pre-condition: + +- MCVideo session is established between MCVideo clients (client A and client B) and MCVideo server +- Transmission control is established between transmission control participants and transmission control server and there is no ongoing media transmission. +- The user of the UE at the transmission control participant A is authorized to remotely initiate a media transmission from transmission control participant B + +![Sequence diagram showing the procedure for remotely initiated media transmission. It involves three main entities: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence of messages is: 1. Remote transmit media request from A to Server; 2. Authorization check (internal to Server); 3. Transmit media granted from Server to B; 4. Remote transmit media response from Server to A; 5. Video transmission from B to Server.](48f209b7c0c1f91af40cfc3466dbd534_img.jpg) + +``` + +sequenceDiagram + participant A as Transmission control participant A + participant S as Transmission control server + participant B as Transmission control participant B + Note right of S: 2. Authorization check for remotely initiating media transmission from transmission control participant B. Check for maximum simultaneous media transmissions limit + A->>S: 1. Remote transmit media request + S->>B: 3. Transmit media granted + S->>A: 4. Remote transmit media response + B->>S: 5. Video transmission + +``` + +Sequence diagram showing the procedure for remotely initiated media transmission. It involves three main entities: Transmission control participant A, Transmission control server, and Transmission control participant B. The sequence of messages is: 1. Remote transmit media request from A to Server; 2. Authorization check (internal to Server); 3. Transmit media granted from Server to B; 4. Remote transmit media response from Server to A; 5. Video transmission from B to Server. + +**Figure 7.7.1.3.7-1: Remotely initiated media transmission during an MCVideo session** + +- Transmission control participant A sends a remote transmit media request message to transmission control server including the MCVideo ID of the user at the UE of the transmission control participant B and the MCVideo ID of the user at the UE of the transmission control participant A. +- Transmission control server checks whether the user at the UE of transmission control participant A is authorized to remotely initiate a media transmission from transmission control participant B. If authorized, the transmission control server makes the determination on what action (grant, deny, or queue) to take on the request based on transmission control criteria (e.g., group policy) and determines to accept the remotely initiated transmit media request from transmission control participant A. +- Transmission control server sends a transmit media granted message to transmission control participant B. +- Transmission control server provides a remote transmit media response message to transmission control participant A indicating success (media transmission occurs from transmission control participant B) or a failure reason. +- Transmission control participant B starts sending video media over the session established to the transmission control server. + +### 7.7.2 Off-network transmission control + +#### 7.7.2.1 General + +The procedure is for providing transmission control to MCVideo UE in an off-network case. Transmission control is performed by using transmission control information flows between the transmission control participant and the + +transmission control arbitrator. The transmission control arbitrator is a member MCVideo UE of the MCVideo group where the transmission rules are applied. + +Transmission control in off-network can be performed in two ways: + +- Single arbitrator: transmission participants rely on a single participant designated as transmission arbitrator for the arbitration of transmission requests. +- Self arbitration: each transmission participant arbitrates its own transmission based on its view of the topology. + +Both of the approaches, as appropriate for the deployment model, can be adopted for MCVideo group using a configurable parameter (as defined in Annex A.4). + +In the single arbitrator approach, one MCVideo client assumes the responsibility for arbitration of transmission requests for all group members within range. All requests for transmission are directed to the arbitrator, and the arbitrator checks the configured limits on the simultaneous transmissions, and grants or denies the request. If an MCVideo client is out of range of the current arbitrator, the MCVideo client is allowed to transmit and also become a transmission arbitrator. If there is insufficient capacity to carry an extra transmission i.e. the configured limit for simultaneous transmissions is reached, the MCVideo client may request that an existing transmitting MCVideo client is pre-empted; the pre-emption request is sent to the transmission arbitrator. + +In the self arbitration approach, each MCVideo client decides for itself whether there is sufficient capacity to carry the transmission. If it determines that there is insufficient capacity i.e. the configured limit for simultaneous transmissions is reached, and from its perspective another transmitting MCVideo client has a lower priority, the requesting MCVideo client may send an override request directly to this other transmitting MCVideo client, which will either accept the override request and give way, or deny the override request. + +In both the single arbitrator approach and the self arbitration approach, if there is insufficient capacity to carry the communication i.e. the configured limit on the simultaneous transmissions is reached, the MCVideo client may report this to the MCVideo user. The MCVideo user may decide to transmit anyway, and instruct the MCVideo client to proceed with the transmission. + +NOTE: The **ProSe** function within the MCVideo client could determine that there is insufficient capacity to carry an MCVideo call requested by the MCVideo client, however interactions between the MCVideo client and the **ProSe** function are outside the scope of the present document. + +Further subclauses apply to one or both of the single arbitrator approach and the self arbitration approach. Applicability is explicitly indicated in each of the relevant subclauses. + +#### 7.7.2.2 Information flows for off-network transmission control + +##### 7.7.2.2.1 Transmission request + +Table 7.7.2.2.1-1 describes the information flow for the transmission request sent by a transmission participant to request for the transmission permission. This information flow is sent in unicast or broadcast. + +**Table 7.7.2.2.1-1: Transmission request** + +| Information element | Status | Description | +|-----------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user requesting the transmission permission | +| Transmission priority | M | Priority of the request | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.2.2.2 Transmission granted + +Table 7.7.2.2.2-1 describes the information flow for the transmission granted sent by the transmission arbitrator, to indicate that a request for transmission is granted and media may be transmitted. This information flow is sent in unicast or broadcast. + +**Table 7.7.2.2.2-1: Transmission granted** + +| Information element | Status | Description | +|-------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of the user whose client is acting as transmission arbitrator | +| MCVideo ID | M | Identity of the user that has been granted transmission permission | +| Duration | M | The time for which the granted party is allowed to transmit | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| MCVideo ID of subsequent arbitrator | O | Subsequent transmission arbitrator's identity | +| Acknowledgement required | O | Indicates if acknowledgement from the transmission participant is required | + +##### 7.7.2.2.3 Transmission release + +Table 7.7.2.2.3-1 describes the information flow for transmission release sent by the transmission participant, to indicate that the media transmission is complete and transmission permission is released. This information flows is sent in unicast or broadcast. + +**Table 7.7.2.2.3-1: Transmission release** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of user releasing transmission | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +##### 7.7.2.2.4 Transmission rejected + +Table 7.7.2.2.4-1 describes the information flow for transmission rejected sent by the transmission arbitrator, to indicate that a request for the transmission is rejected. This information flows is sent in unicast or broadcast. + +**Table 7.7.2.2.4-1: Transmission rejected** + +| Information element | Status | Description | +|------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of the user whose client is acting as transmission arbitrator | +| MCVideo ID of rejected party | M | Identity of user whose transmission request has been rejected | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Rejection cause | O | Indicates the cause for transmission rejection | +| Acknowledgement required | O | Indicates if acknowledgement from the transmission participant is required | + +##### 7.7.2.2.5 Transmission revoked + +Table 7.7.2.2.5-1 describes the information flow for transmission revoked sent by the transmission arbitrator, to indicate that the transmission permission, that was earlier granted, is revoked. This information flows is sent in unicast or broadcast. + +**Table 7.7.2.2.5-1: Transmission revoked** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of the user whose client is acting as transmission arbitrator | +| MCVideo ID | M | Identity of user whose transmission permission has been revoked | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the transmission participant is required | + +##### 7.7.2.2.6 Transmission arbitration taken + +Table 7.7.2.2.6-1 describes the information flow for transmission taken sent by the transmission participant, to indicate that the transmission participant has taken the responsibility of transmission arbitration. This information flows is sent in unicast or broadcast. + +**Table 7.7.2.2.6-1: Transmission arbitration taken** + +| Information element | Status | Description | +|----------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of the MCVideo user taking responsibility of transmission arbitration | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Permission to request the transmission | O | Indicates whether receiving parties are allowed to request the transmission or not (e.g. broadcast call). | +| Acknowledgement required | O | Indicates if acknowledgement from the transmission participant is required | + +##### 7.7.2.2.7 Transmission arbitration release + +Table 7.7.2.2.7-1 describes the information flow for transmission arbitration release sent by the transmission arbitrator, to indicate that the responsibility of transmission arbitration is released. This information flows is sent in unicast or broadcast. + +**Table 7.7.2.2.7-1: Transmission arbitration release** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | Identity of the user whose client is acting as transmission arbitrator | +| MCVideo ID | O | Identity of the user whose client is being delegated transmission arbitrator function | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +#### 7.7.2.3 Initializing transmission control – single arbitrator approach + +This subclause is applicable only in single arbitrator approach. + +Figure 7.7.2.3-1 describes procedures for transmission participants when an MCVideo client initializes transmission control. The MCVideo client sends a transmission request to detect presence of a transmission arbitrator. If the MCVideo client does not receive a response to the transmission request, it sends a transmission arbitration taken message and becomes the transmission arbitrator. The MCVideo client may now transmit a video. This procedure applies when either there have been no recent MCVideo transmissions within the MCVideo group and therefore no arbitrator has been selected, or where there have been recent MCVideo transmissions which may still be ongoing, but the arbitrator cannot be reached, e.g. where MCVideo client that wants to transmit video has gone out of range of the arbitrator. + +Pre-conditions: + +- 1. An off-network group communication has been established. +- 2. MCVideo client 1 wishes to transmit video, and has determined that the pre-configured limit on the number of transmissions within the MCVideo group has not been reached. + +![Sequence diagram showing the initialization of transmission control for a single arbitrator case. It involves four lifelines: MCVideo client 1, MCVideo client 2, MCVideo client 3, and MCVideo client N. The sequence of messages is: 1. Transmission request from client 1 to the group; 2. No response detected by client 1; 3a. Transmission arbitration taken by client 1; 3b. Notify user (internal action); 4. Media Flow from client 1 to the group.](9cbc1ebd80813fc36e499f7d70ed6881_img.jpg) + +``` +sequenceDiagram + participant C1 as MCVideo client 1 + participant C2 as MCVideo client 2 + participant C3 as MCVideo client 3 + participant CN as MCVideo client N + Note left of C1: 2. No response detected + Note left of C1: 3b. Notify user + C1->>C2: 1. Transmission request + C1->>C3: 1. Transmission request + C1->>CN: 1. Transmission request + Note left of C1: 2. No response detected + Note left of C1: 3b. Notify user + C1->>C2: 3a. Transmission arbitration taken + C1->>C3: 3a. Transmission arbitration taken + C1->>CN: 3a. Transmission arbitration taken + Note left of C1: 3b. Notify user + Note left of C1: 4. Media Flow + C1->>C2: 4. Media Flow + C1->>C3: 4. Media Flow + C1->>CN: 4. Media Flow +``` + +Sequence diagram showing the initialization of transmission control for a single arbitrator case. It involves four lifelines: MCVideo client 1, MCVideo client 2, MCVideo client 3, and MCVideo client N. The sequence of messages is: 1. Transmission request from client 1 to the group; 2. No response detected by client 1; 3a. Transmission arbitration taken by client 1; 3b. Notify user (internal action); 4. Media Flow from client 1 to the group. + +**Figure 7.7.2.3-1: Initializing transmission control, single arbitrator case** + +- 1. MCVideo client 1 sends a transmission request message to the MCVideo group. +- 2. MCVideo client 1 does not detect any response to the transmission request. +- 3a. MCVideo client 1 sends a transmission arbitration taken message to the MCVideo group. +- 3b. MCVideo user may be notified that the video can now be transmitted. +- 4. MCVideo client 1 transmits video to the MCVideo group. + +#### 7.7.2.3A Initializing transmission control – self arbitration approach + +This subclause is applicable only in self arbitration approach. + +Figure 7.7.2.3a-1 describes procedures for transmission participants when an MCVideo client initializes transmission control. + +Pre-conditions: + +- 1. An off-network group communication has been established. +- 2. MCVideo client 1 wishes to transmit video. + +![Sequence diagram illustrating the self arbitration case for initializing transmission control. Four MCVideo clients (client 1, client 2, client 3, client N) are shown. Client 1 performs an internal check (1. Check transmission limit and inform user). Then, Client 1 sends a 'Transmission arbitration taken' message to clients 2, 3, and N. Finally, Client 1 begins the 'Media Flow' to clients 2, 3, and N.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +``` +sequenceDiagram + participant Client1 as MCVideo client 1 + participant Client2 as MCVideo client 2 + participant Client3 as MCVideo client 3 + participant ClientN as MCVideo client N + Note left of Client1: 1. Check transmission limit and inform user + Client1->>Client2: 2. Transmission arbitration taken + Client1->>Client3: 2. Transmission arbitration taken + Client1->>ClientN: 2. Transmission arbitration taken + Note left of Client1: 3. Media Flow + Client1->>Client2: 3. Media Flow + Client1->>Client3: 3. Media Flow + Client1->>ClientN: 3. Media Flow +``` + +Sequence diagram illustrating the self arbitration case for initializing transmission control. Four MCVideo clients (client 1, client 2, client 3, client N) are shown. Client 1 performs an internal check (1. Check transmission limit and inform user). Then, Client 1 sends a 'Transmission arbitration taken' message to clients 2, 3, and N. Finally, Client 1 begins the 'Media Flow' to clients 2, 3, and N. + +**Figure 7.7.2.3a-1: Initializing transmission control, self arbitration case** + +1. The MCVideo client checks whether the pre-configured limit on the number of transmissions within the MCVideo group has been reached and informs the user. If the pre-configured limit on the number of transmissions within the MCVideo group has been reached, the MCVideo user may defer the transmission, or request an override as specified in subclause 7.7.2.8, or decide to continue with the transmission anyway. + +NOTE: If the MCVideo user decides to transmit even if the pre-configured limit on the number of transmissions within the MCVideo group has been reached, the MCVideo user decides to accept any consequences of interference. + +2. MCVideo client 1 sends a transmission arbitration taken message to the MCVideo group. +3. MCVideo client 1 transmits video to the MCVideo group. + +#### 7.7.2.4 Transmission permission granted + +This subclause is applicable only in single arbitrator approach. + +Figure 7.7.2.4-1 describes procedures for transmission participants when an MCVideo client requests for transmission permission. + +The MCVideo client has detected presence of a transmission arbitrator e.g., by receiving responses to transmission arbitration control message. The MCVideo client sends a transmission request and waits for a response. The MCVideo client upon receiving a transmission granted message may transmit a video. + +Pre-conditions: + +1. An off-network group communication has been established. +2. At least one participant is currently transmitting video. + +![Sequence diagram illustrating the 'Requesting transmission permission' process. Lifelines: MCVideo client 1 (TA), MCVideo client 2, MCVideo client 3, MCVideo client N. Steps: 1. Transmission request from client 2 to clients 1, 3, and N. 2. Check if limit is reached (internal to client 1). 3. Transmission granted from client 1 to clients 2, 3, and N. 4. Notify user (internal to client 2). 5. Media Flow from client 2 to clients 1, 3, and N.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +``` +sequenceDiagram + participant TA as MCVideo client 1 (TA) + participant C2 as MCVideo client 2 + participant C3 as MCVideo client 3 + participant CN as MCVideo client N + + Note left of TA: 2. Check if limit is reached + C2->>TA: 1. Transmission request + TA->>C2: 3. Transmission granted + Note right of C2: 4. Notify user + C2->>TA: 5. Media Flow + C2->>C3: 5. Media Flow + C2->>CN: 5. Media Flow +``` + +Sequence diagram illustrating the 'Requesting transmission permission' process. Lifelines: MCVideo client 1 (TA), MCVideo client 2, MCVideo client 3, MCVideo client N. Steps: 1. Transmission request from client 2 to clients 1, 3, and N. 2. Check if limit is reached (internal to client 1). 3. Transmission granted from client 1 to clients 2, 3, and N. 4. Notify user (internal to client 2). 5. Media Flow from client 2 to clients 1, 3, and N. + +**Figure 7.7.2.4-1: Requesting transmission permission** + +1. MCVideo client 2 sends a transmission request message to the MCVideo group. +2. MCVideo client 1, being the transmission arbitrator, checks if the configured limit of maximum simultaneous transmissions is already reached. +3. If the maximum simultaneous transmissions limit is not reached, MCVideo client 1 sends a transmission granted message to the MCVideo group. Transmission granted message indicates MCVideo client 2 as the intended recipient. +4. MCVideo user at MCVideo client 2 may be notified that the video can now be transmitted. +5. MCVideo client 2 transmits video to the MCVideo group. + +#### 7.7.2.5 Transmission permission rejected + +This subclause is applicable only in single arbitrator approach. + +Figure 7.7.2.5-1 describes procedures for transmission participants when an MCVideo client requests for transmission permission. + +The MCVideo client has detected presence of a transmission arbitrator e.g., by receiving responses to transmission arbitration control message. The MCVideo client sends a transmission request and waits for a response. + +Pre-conditions: + +1. An off-network group communication has been established. +2. At least one participant is currently transmitting video. + +![Sequence diagram illustrating the process of requesting transmission permission. Lifelines: MCVideo client 1 (TA), MCVideo client 2, MCVideo client 3, and MCVideo client N. The sequence is: 1. MCVideo client 2 sends a 'Transmission request' to the group. 2. MCVideo client 1 (TA) checks if the limit is reached. 3. MCVideo client 1 sends a 'Transmission rejected' message to the group. 4. MCVideo client 2 notifies the user.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +``` +sequenceDiagram + participant TA as MCVideo client 1 (TA) + participant C2 as MCVideo client 2 + participant C3 as MCVideo client 3 + participant CN as MCVideo client N + Note left of TA: 2. Check if limit is reached + Note right of C2: 4. Notify user + C2->>TA: 1. Transmission request + TA->>C2: 3. Transmission rejected + TA->>C3: 3. Transmission rejected + TA->>CN: 3. Transmission rejected +``` + +Sequence diagram illustrating the process of requesting transmission permission. Lifelines: MCVideo client 1 (TA), MCVideo client 2, MCVideo client 3, and MCVideo client N. The sequence is: 1. MCVideo client 2 sends a 'Transmission request' to the group. 2. MCVideo client 1 (TA) checks if the limit is reached. 3. MCVideo client 1 sends a 'Transmission rejected' message to the group. 4. MCVideo client 2 notifies the user. + +**Figure 7.7.2.5-1: Requesting transmission permission** + +1. MCVideo client 2 sends a transmission request message to the MCVideo group. +2. MCVideo client 1, being the transmission arbitrator, checks if the configured limit of maximum simultaneous transmissions is already reached. +3. If the maximum simultaneous transmissions limit has reached, MCVideo client 1 sends a transmission rejected message to the MCVideo group. Transmission denied message indicates MCVideo client 2 as the intended recipient. The transmission rejected message may include a rejection cause which indicates that the configured maximum transmissions limit has been reached. +4. MCVideo user at MCVideo client 2 may be notified that the video cannot be transmitted right now. + +Following step 4, the MCVideo user at MCVideo client 2 may decide to transmit anyway, for example if the user knows the topology of the off-network MCVideo group and locations of the MCVideo group members and needs to transmit video to other local MCVideo group members despite causing a potential conflict with one or more other existing MCVideo transmissions within the MCVideo group. In this case, the MCVideo client follows the procedure in subclause 7.7.2.3. + +#### 7.7.2.6 Releasing transmission permission + +This subclause is applicable in both the single arbitrator and self arbitration approaches. + +Figure 7.7.2.6-1 describes procedures for transmission participants when an MCVideo client releases transmission permission. + +The MCVideo client has detected presence of a transmission arbitrator e.g., by receiving responses to transmission arbitration control message. The MCVideo client stops the video transmission and sends a transmission release request. + +Pre-conditions: + +1. An off-network group communication has been established. +2. MCVideo client has requested transmission permission and may have received transmission permission. + +![Sequence diagram illustrating the request for transmission permission. Four lifelines are shown: MCVideo client 1 (TA), MCVideo client 2, MCVideo client 3, and MCVideo client N. MCVideo client 2 performs an internal action '1. Stop video transmission' and then sends a '2. Transmission release' message to the group, indicated by an arrow pointing from client 2 to client 3 and client N.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +``` +sequenceDiagram + participant TA as MCVideo client 1 (TA) + participant C2 as MCVideo client 2 + participant C3 as MCVideo client 3 + participant CN as MCVideo client N + Note right of C2: 1. Stop video transmission + C2->>C3: 2. Transmission release + Note right of C3: (Message also received by CN) +``` + +Sequence diagram illustrating the request for transmission permission. Four lifelines are shown: MCVideo client 1 (TA), MCVideo client 2, MCVideo client 3, and MCVideo client N. MCVideo client 2 performs an internal action '1. Stop video transmission' and then sends a '2. Transmission release' message to the group, indicated by an arrow pointing from client 2 to client 3 and client N. + +**Figure 7.7.2.6-1: Requesting transmission permission** + +1. If transmitting, the MCVideo client 2 stops the transmission of the video. +2. MCVideo client 2 sends a transmission release message to the MCVideo group. + +NOTE: The transmission arbitrator does not respond to a pending (not granted or denied) transmission request if a transmission release notification is received from the MCVideo client. + +#### 7.7.2.7 Transmission override + +This subclause is applicable in the single arbitrator in the approach. + +Figure 7.7.2.7-1 describes procedures for transmission participants when an MCVideo client authorized to override, requests for transmission permission. + +The MCVideo client has detected presence of a transmission arbitrator e.g., by receiving responses to transmission arbitration control message. The MCVideo client sends a transmission request and waits for a response. + +Pre-conditions: + +1. An off-network group communication has been established. +2. Maximum simultaneous transmissions limit has been reached. + +![Sequence diagram illustrating the Transmission override process. The diagram shows four lifelines: MCVideo client 1 (TA), MCVideo client 2, MCVideo client 3, and MCVideo client N. The sequence of messages is: 1. Transmission request from client 2 to the group; 2. Check override policy by client 1; 3. Transmission revoked from client 1 to the group; 4. Revoke transmission by client 3; 5. Transmission granted from client 1 to the group; 6. Notify user (dashed box) for client 2; 7. Media Flow from client 2 to the group.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +``` + +sequenceDiagram + participant TA as MCVideo client 1 (TA) + participant C2 as MCVideo client 2 + participant C3 as MCVideo client 3 + participant CN as MCVideo client N + + Note left of TA: 2. Check override policy + Note right of C3: 4. Revoke transmission + Note right of C2: 6. Notify user + + C2->>TA: 1. Transmission request + TA->>C2: 3. Transmission revoked + TA->>C3: 3. Transmission revoked + TA->>CN: 3. Transmission revoked + C3->>TA: 4. Revoke transmission + TA->>C2: 5. Transmission granted + TA->>C3: 5. Transmission granted + TA->>CN: 5. Transmission granted + C2->>TA: 7. Media Flow + C2->>C3: 7. Media Flow + C2->>CN: 7. Media Flow + +``` + +Sequence diagram illustrating the Transmission override process. The diagram shows four lifelines: MCVideo client 1 (TA), MCVideo client 2, MCVideo client 3, and MCVideo client N. The sequence of messages is: 1. Transmission request from client 2 to the group; 2. Check override policy by client 1; 3. Transmission revoked from client 1 to the group; 4. Revoke transmission by client 3; 5. Transmission granted from client 1 to the group; 6. Notify user (dashed box) for client 2; 7. Media Flow from client 2 to the group. + +**Figure 7.7.2.7-1: Transmission override** + +1. MCVideo client 2 sends a transmission request message to the MCVideo group. +2. As the configured limit of maximum simultaneous transmissions is already reached, MCVideo client 1, being the transmission arbitrator, checks the override policy. +3. If MCVideo client 2 is authorized to override (based on e.g., transmission priority), MCVideo client 1 sends a transmission revoked message to the MCVideo group. Transmission revoked message indicates the MCVideo client from which the permission is revoked, as the intended recipient. +4. MCVideo client 3 stops transmission of video and MCVideo user at MCVideo client 3 may be notified that the transmission permission has been revoked. +5. MCVideo client 1 sends a transmission granted message to the MCVideo group. Transmission granted message indicates MCVideo client 2 as the intended recipient. +6. MCVideo user at MCVideo client 2 may be notified that the video can now be transmitted. +7. MCVideo client 2 transmits video to the MCVideo group. + +#### 7.7.2.8 Transmission override (revoke self) + +This subclause is applicable in the single arbitrator approach. + +**Editor's note: transmission override in the self arbitration approach is FFS.** + +Figure 7.7.2.8-1 describes procedures for transmission participants when an MCVideo client authorized to override, requests for transmission permission. + +The MCVideo client has detected presence of a transmission arbitrator e.g., by receiving responses to transmission arbitration control message. The MCVideo client sends a transmission request and waits for a response. + +Pre-conditions: + +1. An off-network group communication has been established. + +- Maximum simultaneous transmissions limit has been reached. + +![Sequence diagram illustrating the Transmission override process. The diagram shows four lifelines: MCVideo client 1 (TA), MCVideo client 2, MCVideo client 3, and MCVideo client N. The sequence of messages is: 1. Transmission request from client 2 to client 1; 2. Check override policy (internal to client 1); 3. Transmission revoked from client 1 to clients 2, 3, and N; 4. Revoke transmission (internal to client 1); 5. Transmission granted (including new arbitrator) from client 1 to clients 2, 3, and N; 6a. Transmission arbitration taken from client 2 to client 1; 6b. Notify user (internal to client 2); 7. Release transmission arbitration from client 1 to client 2; 8. Media Flow from client 2 to clients 3 and N.](c3fcdb9e14cb1f7e5e0232c5fe0c5198_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 (TA) + participant C2 as MCVideo client 2 + participant C3 as MCVideo client 3 + participant CN as MCVideo client N + + Note left of C1: 2. Check override policy + C2->>C1: 1. Transmission request + Note left of C1: 3. Transmission revoked + C1->>C2: 3. Transmission revoked + C1->>C3: 3. Transmission revoked + C1->>CN: 3. Transmission revoked + Note left of C1: 4. Revoke transmission + Note left of C1: 5. Transmission granted (including new arbitrator) + C1->>C2: 5. Transmission granted (including new arbitrator) + C1->>C3: 5. Transmission granted (including new arbitrator) + C1->>CN: 5. Transmission granted (including new arbitrator) + Note left of C2: 6a. Transmission arbitration taken + C2->>C1: 6a. Transmission arbitration taken + Note left of C2: 6b. Notify user + Note left of C1: 7. Release transmission arbitration + C1->>C2: 7. Release transmission arbitration + Note left of C2: 8. Media Flow + C2->>C3: 8. Media Flow + C2->>CN: 8. Media Flow + +``` + +Sequence diagram illustrating the Transmission override process. The diagram shows four lifelines: MCVideo client 1 (TA), MCVideo client 2, MCVideo client 3, and MCVideo client N. The sequence of messages is: 1. Transmission request from client 2 to client 1; 2. Check override policy (internal to client 1); 3. Transmission revoked from client 1 to clients 2, 3, and N; 4. Revoke transmission (internal to client 1); 5. Transmission granted (including new arbitrator) from client 1 to clients 2, 3, and N; 6a. Transmission arbitration taken from client 2 to client 1; 6b. Notify user (internal to client 2); 7. Release transmission arbitration from client 1 to client 2; 8. Media Flow from client 2 to clients 3 and N. + +**Figure 7.7.2.8-1: Transmission override** + +- MCVideo client 2 sends a transmission request message to the MCVideo group. + - As the configured limit of maximum simultaneous transmissions is already reached, MCVideo client 1, being a transmission arbitrator, checks the override policy. + - If MCVideo client 2 is authorized to override (based on e.g., transmission priority), MCVideo client 1 may send a transmission revoked message to the MCVideo group. Transmission revoked message indicates the MCVideo client 1, the current arbitrator, whose permission is revoked. + - MCVideo client 1 stops transmission of video and MCVideo user at MCVideo client 1 may be notified that the transmission permission has been revoked. + - MCVideo client 1 sends a transmission granted message to the MCVideo group. The transmission granted message indicates MCVideo client 2 as the intended recipient and MCVideo client 2 as the subsequent transmission arbitrator. + - MCVideo client 2 sends a transmission arbitration taken message to the MCVideo group. + - MCVideo user at MCVideo client 2 may be notified that the video can now be transmitted. +- NOTE: Step 6a and step 6b can occur in any order. +- MCVideo client 1, upon receiving the transmission arbitration taken message releases transmission arbitration. + - MCVideo client 2 transmits video to the MCVideo group. + +#### 7.7.2.9 Transmission arbitration release + +##### 7.7.2.9.1 Transmission arbitration release + +This subclause is applicable only in single arbitrator approach. + +Figure 7.7.2.9.1-1 describes procedures for an MCVideo client to release transmission arbitration. There is no other MCVideo client to which transmission arbitration can be delegated. + +Pre-conditions: + +- 1. An off-network group communication has been established. +- 2. Only MCVideo client 1 is transmitting a video. + +![Sequence diagram showing transmission arbitration release without delegation. MCVideo client 1 (TA) sends a 'Transmission arbitration release' message to clients 2, 3, and N. Client 1 then performs a 'Release' action.](ef5f5c6665b6ae13660ede412333ba45_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 (TA) + participant C2 as MCVideo client 2 + participant C3 as MCVideo client 3 + participant CN as MCVideo client N + C1->>C2: 1. Transmission arbitration release + C1->>C3: 1. Transmission arbitration release + C1->>CN: 1. Transmission arbitration release + Note over C1: 2. Release + +``` + +Sequence diagram showing transmission arbitration release without delegation. MCVideo client 1 (TA) sends a 'Transmission arbitration release' message to clients 2, 3, and N. Client 1 then performs a 'Release' action. + +**Figure 7.7.2.9.1-1: Transmission arbitration release without delegation** + +- 1. MCVideo client 1 sends a transmission release message to the MCVideo group. +- 2. MCVideo client 1 stops transmission of the video. + +##### **7.7.2.9.2 Transmission arbitration release with delegation** + +This subclause is applicable only in single arbitrator approach. + +Figure 7.7.2.9.2-1 describes procedures for an MCVideo client to release transmission arbitration. There are other MCVideo clients currently transmitting to which transmission arbitration can be delegated. + +Pre-conditions: + +- 1. An off-network group communication has been established. +- 2. At least one more MCVideo client is transmitting video other than the current transmission arbitrator. + +![Sequence diagram illustrating Transmission arbitration release with delegation. The diagram shows four lifelines: MCVideo client 1 (TA), MCVideo client 2, MCVideo client 3, and MCVideo client N. The sequence of messages is: 1. Stop media transmission (internal to client 1); 2. Transmission arbitration release (delegated to MCVideo client 2) from client 1 to clients 2, 3, and N; 3. No response detected (internal to client 1); 4. Transmission arbitration release (delegated to MCVideo client 3) from client 1 to clients 2, 3, and N; 5. Transmission arbitration taken from client 3 to client 1; 6. Release transmission arbitration (internal to client 1).](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 (TA) + participant MCVideo client 2 + participant MCVideo client 3 + participant MCVideo client N + + Note left of MCVideo client 1 (TA): 1. Stop media transmission + MCVideo client 1 (TA)->>MCVideo client 2: 2. Transmission arbitration release (delegated to MCVideo client 2) + MCVideo client 1 (TA)->>MCVideo client 3: 2. Transmission arbitration release (delegated to MCVideo client 2) + MCVideo client 1 (TA)->>MCVideo client N: 2. Transmission arbitration release (delegated to MCVideo client 2) + Note left of MCVideo client 1 (TA): 3. No response detected + MCVideo client 1 (TA)->>MCVideo client 2: 4. Transmission arbitration release (delegated to MCVideo client 3) + MCVideo client 1 (TA)->>MCVideo client 3: 4. Transmission arbitration release (delegated to MCVideo client 3) + MCVideo client 1 (TA)->>MCVideo client N: 4. Transmission arbitration release (delegated to MCVideo client 3) + Note left of MCVideo client 1 (TA): 6. Release transmission arbitration + MCVideo client 3->>MCVideo client 1 (TA): 5. Transmission arbitration taken + +``` + +Sequence diagram illustrating Transmission arbitration release with delegation. The diagram shows four lifelines: MCVideo client 1 (TA), MCVideo client 2, MCVideo client 3, and MCVideo client N. The sequence of messages is: 1. Stop media transmission (internal to client 1); 2. Transmission arbitration release (delegated to MCVideo client 2) from client 1 to clients 2, 3, and N; 3. No response detected (internal to client 1); 4. Transmission arbitration release (delegated to MCVideo client 3) from client 1 to clients 2, 3, and N; 5. Transmission arbitration taken from client 3 to client 1; 6. Release transmission arbitration (internal to client 1). + +**Figure 7.7.2.9.2-1: Transmission arbitration release with delegation** + +1. MCVideo client 1 stops video transmission but does not release transmission arbitration. +2. MCVideo client 1 sends a transmission arbitration release message. The transmission arbitration release message indicates a MCVideo client which is currently transmitting video, MCVideo client 2, as the subsequent transmission arbitrator. The MCVideo client 1 waits for a confirmation before releasing transmission arbitration. +3. MCVideo client 1 detects no response from MCVideo client 2. +4. MCVideo client 1 sends another transmission arbitration release message. The transmission arbitration release message indicates another MCVideo client which is currently transmitting video, MCVideo client 3, as the subsequent transmission arbitrator. The MCVideo client 1 waits for a confirmation before releasing transmission arbitration. +5. MCVideo client 3 sends a transmission arbitration taken message to the MCVideo group. +6. MCVideo client 1, upon receiving the transmission arbitration taken message releases transmission arbitration. + +#### 7.7.2.10 Simultaneous transmission requests + +This subclause is applicable in both the single arbitrator and self arbitration approaches. + +Figure 7.7.2.10-1 describes procedures for transmission participants when simultaneous transmission requests are generated when more than one MCVideo client initializes transmission control. + +Figure 7.7.2.10-1 shows the expected behaviour if simultaneous transmission requests are generated in the following scenarios: + +- a single arbitrator approach is used but there is currently no arbitrator; or +- self arbitration is used. + +Pre-conditions: + +1. An off-network group communication has been established. + +2. MCVideo client 1 has higher transmission priority than MCVideo client 2. + +![Sequence diagram illustrating simultaneous transmission requests among multiple MCVideo clients (1, 2, 3, N).](03d9aaba6c1af8bfd8e42c1d2422ae5c_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo client 2 + participant MCVideo client 3 + participant MCVideo client N + + Note left of MCVideo client 1: 2. MCVideo client 1 has higher transmission priority than MCVideo client 2. + + MCVideo client 1->>MCVideo client 2: 1a. Transmission request + MCVideo client 2->>MCVideo client 3: 1b. Transmission request + Note left of MCVideo client 1: 2. Compare priority + Note left of MCVideo client 2: 2. Compare priority + MCVideo client 1->>MCVideo client 3: 3. Transmission arbitration taken + Note left of MCVideo client 1: 4. Notify user + +``` + +The diagram shows a sequence of interactions between four MCVideo clients (1, 2, 3, and N). + 1. MCVideo client 1 sends a 'Transmission request' (1a) to MCVideo client 2. + 2. MCVideo client 2 receives the request and sends its own 'Transmission request' (1b) to MCVideo client 3. + 3. Simultaneously, MCVideo client 1 and MCVideo client 2 both enter a 'Compare priority' state. + 4. MCVideo client 1, having higher priority, sends a 'Transmission arbitration taken' message to MCVideo client 3. + 5. Finally, MCVideo client 1 sends a 'Notify user' message, indicating the video can now be transmitted. + +Sequence diagram illustrating simultaneous transmission requests among multiple MCVideo clients (1, 2, 3, N). + +**Figure 7.7.2.10-1: Simultaneous transmission requests** + +- 1a. The MCVideo client 1 sends the transmission request message to the MCVideo group. +- 1b. The MCVideo client 2 sends the transmission request message to the MCVideo group. + +NOTE: Step 1a and 1b happen in parallel + +2. On receiving a transmission request message, while waiting for a response to the sent transmission request message, the MCVideo client compares its transmission priority with the transmission priority indicated in the received transmission request message. +3. On determining that it has higher transmission priority than the received transmission request message(s), and no response to the sent transmission request message is received, the MCVideo client 1 sends the transmission arbitration taken message to the MCVideo group. +4. MCVideo user may be notified that the video can now be transmitted. + +## 7.8 MCVideo service configuration + +The MCVideo service shall support the procedures and related information flows as specified in subclause 10.1 of 3GPP TS 23.280 [6] with the following clarifications: + +- The MC service client is the MCVideo client; +- The MC service server is the MCVideo server; +- The MC service ID is the MCVideo ID; and +- The MC service user profile index is the MCVideo user profile index. + +## 7.9 Affiliation and de-affiliation to/from MCVideo group(s) + +The MCVideo service shall support the procedures and related information flows as specified in subclause 10.8 of 3GPP TS 23.280 [6] with the following clarifications: + +- The MC service client is the MCVideo client; +- The MC service server is the MCVideo server; + +- The MC service group is the MCVideo group; +- The MC service ID is the MCVideo ID; and +- The MC service group ID is the MCVideo group ID. + +When an MCVideo user has affiliated to an MCVideo group then the MCVideo user can send and receive MCVideo related media for that MCVideo group. When an MCVideo user has de-affiliated from an MCVideo group then the MCVideo user cannot send and receive MCVideo related media to and from that MCVideo group. + +## 7.10 Use of MBMS transmission (on-network) + +### 7.10.1 Information flows for MBMS Transmission + +#### 7.10.1.1 General + +Information flows for generic MBMS procedures are defined in 3GPP TS 23.280 [6]. + +#### 7.10.1.2 MapGroupToBearer + +Table 7.10.1.2-1 describes the information flow to associate a MCVideo group call to a MBMS bearer. It is sent from the MCVideo server to the MCVideo client. + +**Table 7.10.1.2-1: MapGroupToBearer** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCVideo group ID | M | This element identifies the MCVideo group, in which the call is started. | +| Media stream identifier (video) | M | This element identifies the media stream of the SDP used for the Video group call (e.g. MBMS subchannel). | +| Media stream identifier (audio) | O | This element identifies the audio media stream of the SDP used for the Video group call (e.g. MBMS subchannel). This is used if separate codecs are used for video and audio. | +| TMGI (NOTE) | O | The MBMS bearer identifier if the media of the MCVideo group call is not sent on the same MBMS bearer as this MapGroupToBearer message. | +| Call acknowledgement indicator | O | Indication that the MCVideo group call requires acknowledgement from receiving MCVideo clients. | +| NOTE: TMGI shall be present if this message is sent over a different MBMS bearer than the media of the group call; TMGI may be present if this message is sent over the same MBMS bearer as the media of the group call. | | | + +#### 7.10.1.3 UnmapGroupFromBearer + +Table 7.10.1.3-1 describes the information flow to disconnect a MCVideo group call from a MBMS bearer. It is sent from the MCVideo server to the MCVideo client. + +**Table 7.10.1.3-1: UnmapGroupFromBearer** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------| +| MCVideo group ID | M | This element identifies the MCVideo group which will no longer use the MBMS bearer. | + +### 7.10.2 Use of pre-established MBMS bearers + +The MCVideo service shall support the procedure for using pre-established MBMS bearers as specified 3GPP TS 23.280 [6] with the following clarifications: + +- The MC service client is the MCVideo client; + +- The MC service server is the MCVideo server; and +- The MC service ID is the MCVideo ID. + +The MCVideo service shall use the MCVideo-1, MCVideo-8 and MCVideo-9 reference points for this procedure. + +MCVideo may use pre-established **MBMS** bearer for the different types of MCVideo group calls. Both pre-arranged group calls and chat group calls can use the pre-established **MBMS** bearer for distributing the media. The **MBMS** bearer can be used by any group. Depending on the capacity of the **MBMS** bearer, the bearer can be used to broadcast one or more group calls in parallel. + +Both the media packets as well as the transmission control messages to the receiving MCVideo clients are sent on the **MBMS** bearer. Optionally a separate **MBMS** bearer could be used for the transmission control messages, due to different bearer characteristic requirements. + +When using the pre-established **MBMS** bearer for MCVideo, the MCVideo server perform the procedure of call connect and disconnect over **MBMS** as defined in subclause 7.10.4 at the group communication session establishment step. + +### 7.10.3 Use of dynamic **MBMS** bearer establishment + +The MCVideo service shall support the procedure for using dynamic **MBMS** bearers as specified 3GPP TS 23.280 [6] with the following clarifications: + +- The MC service client is the MCVideo client; +- The MC service server is the MCVideo server; and +- The MC service ID is the MCVideo ID. + +The MCVideo service shall use the MCVideo-1, MCVideo-4, MCVideo-7, MCVideo-8 and MCVideo-9 reference points for this procedure. + +MCVideo may use dynamic **MBMS** bearer establishment for the different types of MCVideo group calls. Both pre-arranged group calls and chat group calls can use the dynamic **MBMS** bearer for distributing the media. + +Both the media packets as well as the transmission control messages to the receiving MCVideo clients are sent on the **MBMS** bearer. + +When using the procedures for dynamic **MBMS** bearer establishment for MCVideo, the MCVideo server perform the procedure of mapping group communication to **MBMS** bearer as defined in subclause 7.10.4 at the group communication session establishment step. + +### 7.10.4 Video call connect and disconnect over **MBMS** + +#### 7.10.4.1 General + +**MBMS** bearer can be used for MCVideo group calls. One **MBMS** bearer is not permanently associated to one specific group or group call. Before sending media packets of a group call over **MBMS** bearer, the MCVideo server shall send the association information between group call and the **MBMS** bearer. The group call setup procedure indicates the media stream or media streams within one **MBMS** bearer that is used for the specific MCVideo group call. When the group call over the **MBMS** bearer is finished, this temporary association information of an MCVideo group call to specific resources on a **MBMS** bearer is undone. The procedure in figure 7.10.4.2.1-1 requires that the group session is setup before the call start. This eliminates the need for the receiving clients to continuously use a unicast bearer. Prior to this the **MBMS** bearer is activated and announced to the MCVideo clients. + +#### 7.10.4.2 Procedure + +##### 7.10.4.2.1 Call connect over **MBMS** + +In figure 7.10.4.2.1-1 the MCVideo client 1 is the client that initiate an MCVideo chat group call and also the transmitting client. MCVideo client 1 may, but does not have to be in an **MBMS** service area. The MCVideo client 2 and MCVideo client 3 represents MCVideo clients receiving the MCVideo call over an **MBMS** bearer. There may be other receiving clients both over unicast bearers and over this or other **MBMS** bearer(s), however they are not illustrated in this figure. + +The same procedure as for chat group call can also be applied for pre-arranged calls. + +Pre-conditions: + +- All users participating in the MCVideo group call are already affiliated to the group. +- All participating users have joined the group session. + +![Sequence diagram illustrating the chat group call connect on MBMS bearer. The diagram shows interactions between MCVideo client 1, MCVideo server, MCVideo Client 2, and MCVideo Client 3. The process starts with activation and announcement of the MBMS bearer, followed by an initial transmit media request from client 1 to the server. The server responds with MapGroupToBearer, Transmitted media granted, and Media transmission notification. Clients 2 and 3 receive notifications and send receive media requests. The server responds with receive media response. Finally, client 1 sends a media flow (uplink unicast) to the server, which then broadcasts it as a media flow (downlink MBMS) to clients 2 and 3.](cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg) + +``` + +sequenceDiagram + participant Client1 as MCVideo client 1 + participant Server as MCVideo server + participant Client2 as MCVideo Client 2 + participant Client3 as MCVideo Client 3 + + Note right of Server: 1. Activation and announcement of MBMS bearer + Client1->>Server: 2. Initial transmit media request + Server->>Client2: 3. MapGroupToBearer + Server->>Client1: 4. Transmitted media granted + Server->>Client3: 5. Media transmission notification + Note right of Client2: 6. Notify + Note right of Client3: 6. Notify + Client2-->>Server: 7. Receive media request + Client3-->>Server: 8. Receive media response + Note right of Server: 9. Media flow (downlink MBMS) + Client1->>Server: 9. Media flow (uplink unicast) + Server->>Client2: 9. Media flow (downlink MBMS) + Server->>Client3: 9. Media flow (downlink MBMS) + +``` + +Sequence diagram illustrating the chat group call connect on MBMS bearer. The diagram shows interactions between MCVideo client 1, MCVideo server, MCVideo Client 2, and MCVideo Client 3. The process starts with activation and announcement of the MBMS bearer, followed by an initial transmit media request from client 1 to the server. The server responds with MapGroupToBearer, Transmitted media granted, and Media transmission notification. Clients 2 and 3 receive notifications and send receive media requests. The server responds with receive media response. Finally, client 1 sends a media flow (uplink unicast) to the server, which then broadcasts it as a media flow (downlink MBMS) to clients 2 and 3. + +Figure 7.10.4.2.1-1: Chat group call connect on MBMS bearer + +1. Activation and announcement of MBMS bearer availability. + +NOTE 1: The procedure does not include the steps for MCVideo client location reporting, or for MBMS capability information exchange. + +2. MCVideo client 1 initiate the MCVideo group call by sending an initial transmit media request over a unicast bearer to the MCVideo server (reference point MCVideo-4). +3. The MCVideo server will send a MapGroupToBearer message over a previously activated MBMS bearer to all users that will receive the call over an MBMS bearer. The MapGroupToBearer message includes association information between the group call and MBMS bearer. The MapGroupToBearer message includes MCVideo group ID and information about the media stream identifier or media stream identifiers of the activated MBMS bearer and may include the identifier (i.e. the TMGI) of the MBMS bearer broadcasting the call. The message is sent over reference point MCVideo-9. + +NOTE 2: Step 3 can be deferred until step 5 and the MapGroupToBearer message can then be included in the transmission arbitration taken message. + +4. The MCVideo server grants the right to transmit for MCVideo client 1 and by that sends a transmit media granted message to the MCVideo client 1. This message is sent over a unicast bearer (reference point MCVideo-4). +5. A media transmission notification message is sent from the MCVideo server to all receiving users. This message includes the MCVideo ID of the transmitting MCVideo client as well as the MCVideo group ID. The message is sent over a MBMS bearer to all users that have previously been setup to receive calls over the MBMS bearer. The message is sent over reference point MCVideo-9. +6. The users of MCVideo clients are informed about the details of video transmission and the video transmitter. +7. The MCVideo clients may send a receive media request to the MCVideo server, to indicate the reception of media over the MBMS bearer. + +8. MCVideo server accepts the media receive request and sends a receive media response message to MCVideo clients over a **MBMS** bearer by using reference point MCVideo-9. + +NOTE 3: The receive media response can also be sent by unicast to the MCVideo clients that request to receive media over the **MBMS** bearer. + +NOTE 4: Step 7 and 8 may be omitted when auto-receive transmission mode is used, e.g. for emergency group calls. + +9. The media is sent from MCVideo client 1 to the MCVideo server over unicast bearer and from the MCVideo server to the MCVideo client 2 and MCVideo client 3 over **MBMS** bearer. + +NOTE 5: Additional transmission request messages in the same call will not trigger the MapGroupToBearer message to be sent. + +##### 7.10.4.2.2 Call disconnect over **MBMS** + +Figure 7.10.4.2.2-1 shows the high level procedure where an UnmapGroupFromBearer message is sent by the MCVideo server to the MCVideo clients to indicate that the MCVideo group call is being dissociated from the **MBMS** bearer. + +![Sequence diagram illustrating the call disconnect over MBMS bearer. The diagram shows four lifelines: MCVideo client 1, MCVideo server, MCVideo client 2, and MCVideo client 3. Step 1: MCVideo client 1 sends a 'Media flow (uplink, unicast)' to the MCVideo server. The MCVideo server then forwards this as '1. Media flow' to both MCVideo client 2 and MCVideo client 3. Step 2: A decision box labeled '2. Decision to disconnect the call or dissociate from the MBMS bearer' is shown within the MCVideo server's lifeline. Step 3: The MCVideo server sends a '3. Disconnect / UnmapGroupFromBearer' message to MCVideo client 2 and MCVideo client 3.](a97f7c055c1fd8d79037d02b3fc38496_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + participant MCVideo client 3 + Note right of MCVideo server: 2. Decision to disconnect the call or dissociate from the MBMS bearer + MCVideo client 1->>MCVideo server: 1. Media flow (uplink, unicast) + MCVideo server->>MCVideo client 2: 1. Media flow + MCVideo server->>MCVideo client 3: 1. Media flow + MCVideo server->>MCVideo client 2: 3. Disconnect / UnmapGroupFromBearer + MCVideo server->>MCVideo client 3: 3. Disconnect / UnmapGroupFromBearer + +``` + +Sequence diagram illustrating the call disconnect over MBMS bearer. The diagram shows four lifelines: MCVideo client 1, MCVideo server, MCVideo client 2, and MCVideo client 3. Step 1: MCVideo client 1 sends a 'Media flow (uplink, unicast)' to the MCVideo server. The MCVideo server then forwards this as '1. Media flow' to both MCVideo client 2 and MCVideo client 3. Step 2: A decision box labeled '2. Decision to disconnect the call or dissociate from the MBMS bearer' is shown within the MCVideo server's lifeline. Step 3: The MCVideo server sends a '3. Disconnect / UnmapGroupFromBearer' message to MCVideo client 2 and MCVideo client 3. + +Figure 7.10.4.2.2-1: Chat group call disconnect on **MBMS** bearer + +1. An MCVideo group call is ongoing; the media is broadcasted over **MBMS** bearer to MCVideo client 2 and MCVideo client 3. +2. MCVideo server has determined to disconnect the call over the **MBMS** bearer for the MCVideo clients +3. An UnmapGroupFromBearer message is sent by the MCVideo server to MCVideo client 2, MCVideo client 3 and possibly to MCVideo client 1 (if in **MBMS** coverage area) on **MBMS** bearer(s). + +NOTE 4: The UnmapGroupFromBearer message can be sent as part of other messages. + +NOTE 5: The UnmapGroupFromBearer message and the MapGroupToBearer message can be combined, to facilitate switching bearers in one signalling step, as necessary. + +### 7.10.5 Switching from **MBMS** bearer to unicast bearer + +The MCVideo service shall support the procedure for switching from **MBMS** bearer to unicast bearer as specified 3GPP TS 23.280 [6] with the following clarifications: + +- The MC service client is the MCVideo client; +- The MC service server is the MCVideo server; and +- The MC service ID is the MCVideo ID. + +The MCVideo service shall use the MCVideo-1, MCVideo-4, MCVideo-7, MCVideo-8 and MCVideo-9 reference points for this procedure. + +## 7.11 Simultaneous session for MCVideo calls (on-network) + +An MCVideo client and MCVideo server may use a simultaneous session as defined in 3GPP TS 23.280 [6] for MCVideo calls. The MCVideo client becomes involved in a simultaneous session for MCVideo calls by inviting, joining or accepting more than one MCVideo call, or affiliating to a group. + +NOTE: An MCVideo client affiliating to multiple MCVideo groups with active calls will result in the MCVideo client being invited simultaneously to multiple MCVideo calls. + +The MCVideo client can also still handle multiple MCVideo calls in parallel at the same time i.e. using multiple dialogs. + +The simultaneous session is established during either an originating on-demand call establishment or during pre-established session establishment or a modification of an already established pre-established session or on-demand call. + +It is possible to change the prioritisation while the MCVideo client is engaged in multiple MCVideo calls. The setting of the priority can be made at MCVideo call setup or by performing a modification after the MCVideo call is established. This may result in more than one media bearer. + +## 7.12 User authentication and authorization for MCVideo service + +NOTE: Flow 7.12-1 is a high level user authentication and authorization flow. 3GPP TS 33.180 [14] defines the specific user authentication and authorization architecture required by the MCVideo service in order to realize the MCVideo user authentication and authorization requirements as defined in 3GPP TS 22.280 [2]. + +A procedure for user authentication is illustrated in figure 7.12-1. The user authentication is performed based on the procedure specified in 3GPP TS 23.280 [6]. + +![Sequence diagram showing MCVideo user authentication and registration. Lifelines: MCVideo client, Identity management client, Signalling user agent, SIP core, Identity management server, MCVideo server. Step 1: User Authentication based on 'General user authentication and authorization for MC services' (3GPP TS 23.280[18]). Step 2: MCVideo client performs service authorization with the MCVideo server.](8b9e9fdabfd2a37e4475d78f8fdcf15c_img.jpg) + +The diagram is a sequence diagram with six lifelines: MCVideo client, Identity management client, Signalling user agent, SIP core, Identity management server, and MCVideo server. + Step 1: A message is sent from the MCVideo client to the Identity management client, which then interacts with the Signalling user agent, SIP core, and Identity management server. A note box indicates: "1. User Authentication is based on the procedure – “General user authentication and authorization for MC services” specified in 3GPP TS 23.280[18].". + Step 2: A message is sent from the MCVideo client to the MCVideo server. A note box indicates: "2. The MCVideo client performs the service authorization with the MCVideo server.". + +Sequence diagram showing MCVideo user authentication and registration. Lifelines: MCVideo client, Identity management client, Signalling user agent, SIP core, Identity management server, MCVideo server. Step 1: User Authentication based on 'General user authentication and authorization for MC services' (3GPP TS 23.280[18]). Step 2: MCVideo client performs service authorization with the MCVideo server. + +Figure 7.12-1: MCVideo user authentication and registration, single domain + +1. The user authentication is performed as per the general user authentication procedure specified in 3GPP TS 23.280 [6]. +2. MCVideo client performs the MCVideo service authorization for the user. Step 2 utilizes the results of step 1. + +## 7.13 Support for multiple devices + +An MCVideo user may be authorized to use the MCVideo service from multiple MCVideo UEs as per the procedure in subclause 7.12. + +If an MCVideo server receives a service authorization request for an MCVideo user who is previously MCVideo service authorized on another MCVideo UE, then the MCVideo server shall process this service authorization request as described in subclause 7.12. In the MCVideo service authorization response to the MCVideo user, the MCVideo server shall also indicate that the MCVideo user is already MCVideo service authorized from another MCVideo UE. + +## 7.14 Location information (on-network) + +The MCVideo system makes use of all of the procedures for location management as specified in 3GPP TS 23.280 [6], utilising the CSC-14 reference point between the location management client and location management server and the CSC-15 reference point between the MCVideo server and location management server. + +- The MC service client is the MCVideo client; +- The MC service server is the MCVideo server; +- The MC service group is the MCVideo group; +- The MC service ID is the MCVideo ID; and +- The MC service group ID is the MCVideo group ID. + +## 7.15 MCVideo resource management (on-network) + +Procedures for resource management are defined in subclause 10.11 of 3GPP TS 23.280 [6]. + +## 7.16 MCVideo client query + +### 7.16.1 General + +The MCVideo client query is used by an authorized MCVideo client to retrieve the characteristics of the MCVideo clients in an area with certain criteria. The query criteria may be a set of capabilities, or category tags, or a mix of such criterions, etc. + +### 7.16.2 Information flows for MCVideo client query + +#### 7.16.2.1 MCVideo client query request + +Table 7.16.2.1-1 describes the information flow for the MCVideo client query request from MCVideo client to MCVideo server. + +**Table 7.16.2.1-1: MCVideo client query request** + +| Information Element | Status | Description | +|----------------------|--------|--------------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user requesting MCVideo client query | +| Location information | M | The location information where the query to be applied | +| Query criteria | O | A criteria filter for the query (e.g. category tags, video capabilities, etc.) | + +#### 7.16.2.2 MCVideo client query response + +Table 7.16.2.2-1 describes the information flow for the MCVideo client query response from the MCVideo server to the MCVideo client. + +**Table 7.16.2.2-1: MCVideo client query response** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------| +| MCVideo ID list | O | The MCVideo clients that fulfil the query criteria | + +### 7.16.3 MCVideo client query procedure + +Figure 7.16.3-1 describes the procedure for MCVideo client query in on-network. This procedure is applicable to query the MCVideo clients belonging to the same MCVideo system as the requesting MCVideo user. + +Pre-conditions: + +1. The video capabilities have been collected at MCVideo server during the update MCVideo capabilities information at the MCVideo server procedure in subclause 7.5.2.3. + +![Sequence diagram of MCVideo client query procedure. It shows three steps: 1. MCVideo client A sends a query request to the MCVideo server. 2. The server performs an authorization check and retrieves clients. 3. The server sends a response back to the client.](e42cc691d9c7c4d23e66b04472bb494e_img.jpg) + +``` + +sequenceDiagram + participant Client as MCVideo client A + participant Server as MCVideo server + Note right of Server: 2. Authorization check and retrieve MCVideo clients + Client->>Server: 1. MCVideo client query request + Server-->>Client: 3. MCVideo client query response + +``` + +Sequence diagram of MCVideo client query procedure. It shows three steps: 1. MCVideo client A sends a query request to the MCVideo server. 2. The server performs an authorization check and retrieves clients. 3. The server sends a response back to the client. + +**Figure 7.16.3-1: MCVideo client query procedure** + +1. MCVideo client A sends a MCVideo client query request to the MCVideo server with certain search criteria. +2. MCVideo server checks whether the MCVideo user of MCVideo client A has the authorization to perform MCVideo client query. If success, MCVideo server retrieves the MCVideo clients that fulfil the search criteria. If MCVideo group ID list is included in the MCVideo client query request, MCVideo server retrieves the affiliated group members that fulfil the query criteria in each affiliated MCVideo group in the received MCVideo group ID list. +3. MCVideo server returns the MCVideo client query response to the MCVideo client A with the retrieved MCVideo clients. + +**Editor's note:** It is FFS when the requesting MCVideo user and the MCVideo users or the affiliated groups to be requested are not within the same MCVideo system. + +## 7.17 MCVideo adaptation during MCVideo communication + +### 7.17.1 General + +The MCVideo adaption is used by an authorized MCVideo client to automatically change the video communication parameters including codec, resolution etc. according to the network conditions changes detected through such as packet loss or packet delay. + +### 7.17.2 Information flows for MCVideo adaptation + +#### 7.17.2.1 MCVideo communication parameter update request + +Table 7.17.2.1-1 describes the information flow for the MCVideo communication parameter update request from MCVideo client to MCVideo sever and from MCVideo server to MCVideo client. + +**Table 7.17.2.1-1: MCVideo communication parameter update request** + +| Information Element | Status | Description | +|-------------------------------------------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | The identity of the MCVideo user requesting to update MCVideo communication parameter | +| MCVideo group ID | O (NOTE) | The identity of the MCVideo group which the MCVideo communication parameter to be updated (Only used in group communication) | +| MCVideo ID | O (NOTE) | The identity of the MCVideo user ID which the MCVideo communication parameter to be updated (Only used in private communication) | +| SDP | M | The new SDP including codec, resolution, frame rate and etc. for MCVideo communication | +| NOTE: At least one of these information elements shall be present | | | + +#### 7.17.2.2 MCVideo communication parameter update response + +Table 7.17.2.2-1 describes the information flow for the MCVideo communication parameter update response from the MCVideo server to the MCVideo client and from MCVideo client to MCVideo server. + +**Table 7.17.2.2-1: MCVideo communication parameter update response** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------| +| Result | M | Indicates success or failure | + +### 7.17.3 MCVideo adaptation procedure + +#### 7.17.3.1 MCVideo adaptation during group communication procedure – transmitting client triggered + +Figure 7.17.3.1-1 describes the procedure for transmitting MCVideo client triggered MCVideo communication parameters update in on-network. For simplicity, only one receiving user is shown in the figure. This procedure is applicable to only one MCVideo transmitting user during the MCVideo group call, e.g., broadcast group call. + +NOTE: The MCVideo adaptation for MCVideo group communication allows multiple transmitting users are not specified in this release. + +Pre-conditions: + +1. MCVideo client 1 and MCVideo client 2 are the group communication participants, and the MCVideo client 1 is transmitting video in the MCVideo group communication. + +![Sequence diagram showing the interaction between MCVideo client 1, MCVideo server, and MCVideo client 2 for user-triggered adaptation. The process starts with client 1 transmitting video to the group. It then sends a parameter update request to the server. The server performs an authorization check and, if authorized, sends the request to client 2. Client 2 notifies its user and sends a response to the server. The server then sends its response to client 1. Finally, the group communication applies the new parameters.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant S as MCVideo server + participant C2 as MCVideo client 2 + Note right of C1: MCVideo client 1 is transmitting video to the group + C1->>S: 1. MCVideo communication parameter update request + S->>S: 2. Authorization check + S->>C2: 3. MCVideo communication parameter update request + C2->>C2: 4. Notify user + C2->>S: 5. MCVideo communication parameter update response + S->>C1: 6. MCVideo communication parameter update response + Note over C1, S, C2: 7. The MCVideo group communication applies new parameters + +``` + +Sequence diagram showing the interaction between MCVideo client 1, MCVideo server, and MCVideo client 2 for user-triggered adaptation. The process starts with client 1 transmitting video to the group. It then sends a parameter update request to the server. The server performs an authorization check and, if authorized, sends the request to client 2. Client 2 notifies its user and sends a response to the server. The server then sends its response to client 1. Finally, the group communication applies the new parameters. + +**Figure 7.17.3.1-1: Transmitting user triggered MCVideo adaptation in group communication** + +1. MCVideo client 1 sends MCVideo communication parameter update request to the MCVideo server to adjust the video communication parameters due to network conditions changes detected, e.g., through packet loss or packet delay. The new parameters including codec, resolution, frame rate and etc. are included. +2. MCVideo server checks whether the MCVideo user of MCVideo client 1 has the authorization to update the MCVideo communication parameters. +3. When authorized, MCVideo server sends the MCVideo communication parameter update request to the MCVideo client 2. +4. The MCVideo user of MCVideo client 2 is notified about the changes of MCVideo communication parameters. +5. The MCVideo client 2 accepts the request, and sends the MCVideo communication parameter update response to the MCVideo server. +6. The MCVideo server sends the MCVideo communication parameter update response to the MCVideo client 1 with the result. +7. Then, the MCVideo group communication applies the new MCVideo communication parameters. + +#### **7.17.3.2 MCVideo adaptation during group communication procedure – receiving user triggered** + +Figure 7.17.3.2-1 describes the procedure for MCVideo server initiated MCVideo communication parameters update in on-network. For simplicity, only one receiving user is shown in the figure. This procedure is applicable to only one MCVideo transmitting user during the MCVideo group call e.g., broadcast group call. + +Pre-conditions: + +1. MCVideo client 1 and MCVideo client 2 are the group communication participants. MCVideo client 2 is transmitting video, and MCVideo client 1 is receiving video. + +![Sequence diagram illustrating the receiving user triggered MCVide adaptation in group communication. The diagram shows interactions between MCVideo client 1, MCVideo server, and MCVideo client 2. The process starts with Client 1 sending a parameter update request to the server. The server determines to update parameters and then sends requests to both clients. Clients notify their users and send responses. Finally, the group communication applies the new parameters.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant S as MCVideo server + participant C2 as MCVideo client 2 + Note right of C1: Client 1 is receiving video from Client 2 within the group communication + C1->>S: 1. MCVideo communication parameter update request + S->>S: 2. Determine to update the MCVideo communication parameters + S->>C1: 3b. MCVideo communication parameter update request + S->>C2: 3a. MCVideo communication parameter update request + C1->>C1: 4b. Notify user + C2->>C2: 4a. Notify user + C1->>S: 5b. MCVideo communication parameter update response + C2->>S: 5a. MCVideo communication parameter update response + Note over C1, S, C2: 6. The MCVideo group communication applies new parameters + +``` + +Sequence diagram illustrating the receiving user triggered MCVide adaptation in group communication. The diagram shows interactions between MCVideo client 1, MCVideo server, and MCVideo client 2. The process starts with Client 1 sending a parameter update request to the server. The server determines to update parameters and then sends requests to both clients. Clients notify their users and send responses. Finally, the group communication applies the new parameters. + +**Figure 7.17.3.2-1: Receiving user triggered MCVide adaptation in group communication** + +1. MCVideo client 1 sends MCVideo communication parameter update request to the MCVideo server to request the video communication parameters due to network conditions changes detected, e.g., through packet loss. The expected parameters including codec, resolution, frame rate and etc. are included. +2. MCVideo server may receive a multitude of notifications from the receiving users. The MCVideo server performs authorization check and determines to update the MCVideo communication parameters according to the received notifications. + +NOTE 1: The determination of update the MCVideo communication parameters is implementation. + +3. When authorized, MCVideo server sends the MCVideo communication parameter update request to the MCVideo client 2. +4. The MCVideo users of MCVideo client 1 and MCVideo client 2 are notified about the changes of MCVideo communication parameters. +5. The MCVideo client 1 and MCVideo client 2 accepts the request, and sends the MCVideo communication parameter update response to the MCVideo server. +6. Then, the MCVideo group communication applies the new MCVideo communication parameters. + +#### 7.17.3.3 MCVide adaptation during private communication procedure – transmitting client triggered + +Figure 7.17.3.3-1 describes the procedure for transmitting MCVideo client initiated MCVideo communication parameters update in on-network. This procedure is applicable to the video push and video pull. + +Pre-conditions: + +1. The private communication is ongoing between MCVideo client 1 and MCVideo client 2, and MCVideo client 1 is transmitting video to MCVideo client 2. + +![Sequence diagram illustrating the procedure for transmitting user-initiated MCVideo adaptation in private communication. The diagram shows three lifelines: MCVideo client 1, MCVideo server, and MCVideo client 2. The sequence starts with MCVideo client 1 transmitting video to MCVideo client 2. Then, MCVideo client 1 sends a parameter update request to the server. The server performs an authorization check and, if authorized, sends a parameter update request to MCVideo client 2. MCVideo client 2 notifies its user, accepts the request, and sends a response to the server. The server then sends a response to MCVideo client 1. Finally, all participants apply the new parameters.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 + Note right of MCVideo client 1: MCVideo client 1 is transmitting video to MCVideo client 2 + MCVideo client 1->>MCVideo server: 1. MCVideo communication parameter update request + MCVideo server->>MCVideo server: 2. Authorization check + MCVideo server->>MCVideo client 2: 3. MCVideo communication parameter update request + MCVideo client 2->>MCVideo client 2: 4. Notify user + MCVideo client 2->>MCVideo server: 5. MCVideo communication parameter update response + MCVideo server->>MCVideo client 1: 6. MCVideo communication parameter update response + Note over all: 7. The MCVideo communication applies new parameters + +``` + +Sequence diagram illustrating the procedure for transmitting user-initiated MCVideo adaptation in private communication. The diagram shows three lifelines: MCVideo client 1, MCVideo server, and MCVideo client 2. The sequence starts with MCVideo client 1 transmitting video to MCVideo client 2. Then, MCVideo client 1 sends a parameter update request to the server. The server performs an authorization check and, if authorized, sends a parameter update request to MCVideo client 2. MCVideo client 2 notifies its user, accepts the request, and sends a response to the server. The server then sends a response to MCVideo client 1. Finally, all participants apply the new parameters. + +**Figure 7.17.3.3-1: Transmitting user initiated MCVideo adaptation in private communication** + +1. MCVideo client 1 sends MCVideo communication parameter update request to the MCVideo server to adjust the video communication parameters due to network conditions changes detected, e.g., through packet loss. The new parameters including codec, resolution, frame rate and etc. are included. +2. MCVideo server checks whether the MCVideo user of MCVideo client 1 has the authorization to update the MCVideo communication parameters. +3. When authorized, MCVideo server sends the MCVideo communication parameter update request to the MCVideo client 2. +4. The MCVideo user of MCVideo client 2 is notified about the changes of MCVideo communication parameters. +5. The MCVideo client 2 accepts the request, and sends the MCVideo communication parameter update response to the MCVideo server. +6. The MCVideo server sends the MCVideo communication parameter update response to the MCVideo client 1 with the result. +7. Then, the MCVideo communication applies the new MCVideo communication parameters. + +#### 7.17.3.4 MCVideo adaptation during group communication procedure – receiving user triggered + +Figure 7.17.3.4-1 describes the procedure for receiving user initiated MCVideo communication parameters update in on-network. This procedure is applicable in video push and video pull. + +Pre-conditions: + +1. The private communication is ongoing between MCVideo client 1 and MCVideo client 2, and the MCVideo client 1 is receiving video from MCVideo client 2. + +![Sequence diagram illustrating the process of receiving user-triggered MCVideo adaptation in private communication. The diagram shows interactions between MCVideo client 1, MCVideo server, and MCVideo client 2. A green bar at the top indicates that MCVideo client 1 is receiving video from MCVideo client 2. The sequence of steps is: 1. MCVideo client 1 sends a parameter update notification to the server; 2. The server determines to update parameters; 3. The server sends a request to client 2; 4. Client 2 notifies its user; 5. Client 2 sends a response to the server; 6. The server sends a response to client 1; 7. A final bar indicates that the new parameters are applied.](5e9af8986a5845504f251d3079da8078_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCVideo client 1 + participant S as MCVideo server + participant C2 as MCVideo client 2 + Note right of C1: MCVideo client 1 is receiving video from MCVideo client 2 + C1->>S: 1. MCVideo communication parameter update notification + S->>S: 2. Determine to update the MCVideo communication parameters + S->>C2: 3. MCVideo communication parameter update request + C2->>C2: 4. Notify user + C2->>S: 5. MCVideo communication parameter update response + S->>C1: 6. MCVideo communication parameter update response + Note over C1, S, C2: 7. The MCVideo communication applies new parameters + +``` + +Sequence diagram illustrating the process of receiving user-triggered MCVideo adaptation in private communication. The diagram shows interactions between MCVideo client 1, MCVideo server, and MCVideo client 2. A green bar at the top indicates that MCVideo client 1 is receiving video from MCVideo client 2. The sequence of steps is: 1. MCVideo client 1 sends a parameter update notification to the server; 2. The server determines to update parameters; 3. The server sends a request to client 2; 4. Client 2 notifies its user; 5. Client 2 sends a response to the server; 6. The server sends a response to client 1; 7. A final bar indicates that the new parameters are applied. + +**Figure 7.17.3.4-1: Receiving user triggered MCVideo adaptation in private communication** + +1. MCVideo client 1 sends MCVideo communication parameter update request to the MCVideo server to request the video communication parameters due to network conditions changes detected, e.g., through packet loss. The expected parameters including codec, resolution, frame rate and etc. are included. +2. MCVideo server checks whether the MCVideo user of MCVideo client 1 has the authorization to update the MCVideo communication parameters. +3. When authorized, MCVideo server sends the MCVideo communication parameter update request to the MCVideo client 2. +4. The MCVideo user of MCVideo client 2 is notified about the request of MCVideo communication parameters update. +5. The MCVideo client 2 accepts the request, and sends the MCVideo communication parameter update response to the MCVideo server. +6. The MCVideo server sends the MCVideo communication parameter update response to the MCVideo client 1 with the result. +7. Then, the MCVideo communication applies the new MCVideo communication parameters. + +# --- Annex A (normative): MCVideo related configuration data + +## A.1 General + +This Annex provides information about the static data needed for configuration for the MCVideo service, which belongs to one of the following categories: + +- MCVideo UE configuration data (see subclause A.2); +- MCVideo user profile configuration data (see subclause A.3); +- MCVideo related group configuration data (see subclause A.4); and +- MCVideo service configuration data (see subclause A.5). + +For each configuration category, data is split between configuration data that is applicable to both on network and off network, configuration data that is applicable to on-network only, and configuration data that is applicable to off-network only. The configuration data in each configuration category corresponds to a single instance of the category type i.e. the MCVideo UE, MCVideo group, MCVideo user and MCVideo service configuration data refers to the information that will be stored against each MCVideo UE, MCVideo group, MCVideo user and MCVideo service. This means that the three separate tables (on-network and off-network, on-network only, off-network only) for each configuration category represent the complete set of data for each configuration data category element. + +The columns in the tables have the following meanings: + +- Reference: the reference of the corresponding requirement in 3GPP TS 22.281 [3] or 3GPP TS 22.280 [2] or the corresponding subclause from either the present document or the referenced document. +- Parameter description: A short definition of the semantics of the corresponding item of data, including denotation of the level of the parameter in the configuration hierarchy. +- When it is not clear to which functional entities the parameter is configured, then one or more columns indicating this are provided where the following nomenclature is used: + - "Y" to denote "Yes" i.e. the parameter denoted for the row needs to be configured to the functional entity denoted for the column. + - "N" to denote "No" i.e. the parameter denoted for the row does not need to be configured to the functional entity denoted for the column. + +Parameters within a set of configuration data have a level within a hierarchy that pertains only to that configuration data. The hierarchy of the configuration data is common across all three tables of on-network and off-network, on network only and off network only. The level of a parameter within the hierarchy of the configuration data is denoted by use of the character ">" in the parameter description field within each table, one per level. Parameters that are at the top most level within the hierarchy have no ">" character. Parameters that have one or more ">" characters are child parameters of the first parameter above them that has one less ">" character. Parent parameters are parameters that have one or more child parameters. Parent parameters act solely as a "grouping" of their child parameters and therefore do not contain an actual value themselves i.e. they are just containers for their child parameters. + +Each parameter that can be configured online shall only be configured through one online reference point. Each parameter that can be configured offline shall only be configured through one offline reference point. The most recent configuration data made available to the MCVideo UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism. + +## --- A.2 MCVideo UE configuration data + +The general aspects of UE configuration are specified in 3GPP TS 23.280 [6]. Data in tables A.2-1 and A.2-2 have to be known by the MCVideo UE after MCVideo authorization. + +Data in table A.2-1 can be configured offline using the CSC-11 reference point. Table A.2-1 contains the UE configuration required to support the use of off-network MCVideo service. + +**Table A.2-1: UE configuration data (on and off network)** + +| Reference | Parameter description | +|-------------------------------------|----------------------------------------------------------| +| [R-5.4.2-002] of 3GPP TS 22.280 [2] | Maximum number of simultaneous MCVideo group calls (Nc4) | +| [R-5.4.2-003] of 3GPP TS 22.280 [2] | Maximum number of video transmissions (Nc5) in a group | + +**Table A.2-2: UE configuration data (on network)** + +| Reference | Parameter description | +|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| +| Subclause 5.2.3 of 3GPP TS 23.280 [6] | Relay service (Y/N) | +| Subclause 5.2.3 of 3GPP TS 23.280 [6] | List of allowed relayed MCVideo groups and their relay service code (as specified in 3GPP TS 23.303 [7]) (optional) (see NOTE) | +| | > MCVideo group ID | +| | > Relay service code (as specified in 3GPP TS 23.303 [7]) | +| Subclause 5.7 of 3GPP TS 23.280 [6] | Indication of whether the UE shall use IPv4 or IPv6 for on-network MCVideo | +| | MCVideo server | +| | > Server URI | +| NOTE: | When the value of the parameter Relay service is N, this parameter and its child parameters are not needed. | + +## A.3 MCVideo user profile configuration data + +The general aspects of MC service user profile configuration data are specified in 3GPP TS 23.280 [6]. The MCVideo user profile configuration data is stored in the MCVideo user database. The MCVideo server obtains the MCVideo user profile configuration data from the MCVideo user database (MCVideo-2). + +Tables A.3-1 and A.3-2 contain the MCVideo user profile configuration required to support the use of on-network MCVideo service. Tables A.3-1 and A.3-3 contain the MCVideo user profile configuration required to support the use of off-network MCVideo service. Data in table A.3-1 and table A.3-3 can be configured offline using the CSC-11 reference point. + +**Table A.3-1: MCVideo user profile configuration data (on and off network)** + +| Reference | Parameter description | MCVideo UE | MCVideo Server | Configuration management server | MCVideo user database | +|-----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------|---------------------------------|-----------------------| +| Subclause 5.2.11 of 3GPP TS 23.280 [6] | MCVideo identity (MCVideo ID) | Y | Y | Y | Y | +| 3GPP TS 33.180 [14] | KMSUri for security domain of MCVideo ID (see NOTE 1) | Y | Y | Y | Y | +| Subclause 5.2.11 of 3GPP TS 23.280 [6] | Pre-selected MCVideo user profile indication (see NOTE 2) | Y | Y | Y | Y | +| Subclause 5.2.11 of 3GPP TS 23.280 [6] | MCVideo user profile index | Y | Y | Y | Y | +| Subclause 5.2.11 of 3GPP TS 23.280 [6] | MCVideo user profile name | Y | Y | Y | Y | +| [R-5.17-007], [R-6.13.4-002] of 3GPP TS 22.280 [2] | User profile status (enabled/disabled) | | Y | Y | Y | +| [R-5.7-001] [R-6.9-003] of 3GPP TS 22.280 [2] | Authorised to create and delete aliases of an MCVideo user and its associated user profiles. | | | Y | Y | +| [R-5.7-002], [R-6.9-003] of 3GPP TS 22.280 [2] | Alphanumeric aliases of user | Y | Y | Y | Y | +| [R-5.1.1-005], [R-5.9-001] of 3GPP TS 22.280 [2] | Participant type of the user | Y | Y | Y | Y | +| [R-5.1.8-006], [R-5.3-002], [R-5.9-001], [R-5.16.2-001], [R-5.16.2-002] of 3GPP TS 22.280 [2] | User's Mission Critical Organization (i.e. which organization a user belongs to) | Y | Y | Y | Y | +| [R-5.2.2-003] of 3GPP TS 22.280 [2] | Authorisation to create a group-broadcast group | | | Y | Y | +| [R-5.2.2-003] of 3GPP TS 22.280 [2] | Authorisation to create a user-broadcast group | | | Y | Y | +| [R-5.6.2.4.1-002] of 3GPP TS 22.280 [2] | Authorised to activate MCVideo emergency alert | Y | Y | Y | Y | +| [R-5.6.2.4.1-004] [R-5.6.2.4.1-008] [R-5.6.2.4.1-012] of 3GPP TS 22.280 [2] | Group / user recipient of an MCVideo emergency alert (Pre-defined group, currently selected group, pre-defined recipient/ user locally defined recipient/ default if no recipient selected) | Y | Y | Y | Y | +| [R-5.6.2.4.2-002] of 3GPP TS 22.280 [2] | Authorisation to cancel an MCVideo emergency alert | Y | Y | Y | Y | +| [R-5.1.2.1.2-004] of 3GPP TS 22.281 [3] | Authorisation to modify the video settings of the transmitted video stream of another MCVideo User | Y | Y | Y | Y | +| [R-5.1.2.1.2-006] of 3GPP TS 22.281 [3] | Authorisation to renegotiate a codec during a video transmission. | Y | Y | Y | Y | +| [R-5.1.2.1.2-007] of 3GPP TS 22.281 [3] | Authorisation to remotely control the video capabilities or parameters for a camera on an MCVideo UE | Y | Y | Y | Y | +| [R-5.1.2.2.2-001] of 3GPP TS 22.281 [3] | Authorisation to remotely control the video capabilities or parameters of a remote MCVideo UE | Y | Y | Y | Y | +| [R-5.1.2.2.2-004] of 3GPP TS 22.281 [3] | Authorisation to receive and display the capabilities of a remote MCVideo UE | Y | Y | Y | Y | + +| | | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---| +| [R-5.1.3.1.2-004] of 3GPP TS 22.281 [3] | Authorisation to remotely activate another MCVideo User's camera | Y | Y | Y | Y | +| [R-5.1.9.2.2-002] of 3GPP TS 22.281 [3] | Authorisation to push a video to another MCVideo user . | Y | Y | Y | Y | +| [R-5.1.9.2.2-003] of 3GPP TS 22.281 [3] | Authorisation to enable and to disable the automatic sending of notification to a second MCVideo User that a video is being pushed to a third MCVideo User | Y | Y | Y | Y | +| [R-5.1.9.2.2-004] of 3GPP TS 22.281 [3] | List of MCVideo users for whom to receive notifications about video being pushed to them | Y | Y | Y | Y | +| | > MCVideo IDs | | | | | +| [R-5.1.9.2.2-005] of 3GPP TS 22.281 [3] | List of specific video categories to receive (see NOTE 3) | Y | Y | Y | Y | +| | > Video categories | | | | | +| [R-6.7.3-007] of 3GPP TS 22.280 [2] | List of user(s) who can be called in MCVideo private call | | | | | +| | > MCVideo ID | Y | Y | Y | Y | +| | > Presentation priority relative to other users and groups (see NOTE 4) | Y | Y | Y | Y | +| 3GPP TS 33.180 | > KMSUri for security domain of MCVideo ID (see NOTE 1) | Y | Y | Y | Y | +| [R-5.1.10.2-002] of 3GPP TS 22.281 [3] | List of category tags | Y | Y | Y | Y | +| [R-5.1.10.2-002] of 3GPP TS 22.281 [3] | Authorization to query MCVideo client | Y | Y | Y | Y | +| [R-5.1.3.2.2-004] [R-5.1.10.2-002] of 3GPP TS 22.281 [3] | List of category tags that authorized to query MCVideo client | Y | Y | Y | Y | +| [R-5.1.3.2.2-004] [R-5.1.10.2-002] of 3GPP TS 22.281 [3] | List of geography areas that authorized to query MCVideo client | Y | Y | Y | Y | +| [R-5.1.1.1-015] of 3GPP TS 22.281 [3] | Authorization to perform video adaptation | Y | Y | Y | Y | +| NOTE 1: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [6]. | | | | | | +| NOTE 2: As specified in 3GPP TS 23.280 [6], for each MCVideo user's set of MCVideo user profiles, only one MCVideo user profile shall be indicated as being the pre-selected MCVideo user profile. | | | | | | +| NOTE 3: If this list is blank then this implies that all video categories are acceptable for the MCVideo user. | | | | | | +| NOTE 4: The use of this parameter by the MCVideo UE is outside the scope of the present document. | | | | | | + +**Table A.3-2: MCVideo user profile configuration data (on network)** + +| Reference | Parameter description | MCVideo UE | MCVideo Server | Configuration management server | MCVideo user database | +|---------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|------------|----------------|---------------------------------|-----------------------| +| [R-5.1.5-001],<br>[R-5.1.5-002],<br>[R-5.10-001],<br>[R-6.4.7-002],<br>[R-6.8.1-008],<br>[R-6.7.4-002] of<br>3GPP TS 22.280 [2] | List of on-network MCVideo groups for use by an MCVideo user | | | | | +| | > MCVideo Group ID | Y | Y | Y | Y | +| | > Application plane server identity information of group management server where group is defined | | | | | +| | >> Server URI | Y | N | Y | Y | +| | > Application plane server identity information of identity management server which provides authorization for group (see NOTE 1) | | | | | +| | >> Server URI | Y | N | Y | Y | +| 3GPP TS 33.180 [14] | > KMSUri for security domain of group (see NOTE 4) | Y | Y | Y | Y | +| | > Presentation priority of the group relative to other groups and users (see NOTE 2) | Y | Y | Y | Y | +| Subclause 5.2.5 of<br>3GPP TS 23.280 [6] | List of groups user implicitly affiliates to after MCVideo service authorization for the user | | | | | +| | > MCVideo Group ID | Y | Y | Y | Y | +| [R-6.4.2-006] of<br>3GPP TS 22.280 [2] | Authorisation of an MCVideo user to request a list of which MCVideo groups a user has affiliated to | | Y | Y | Y | +| [R-6.4.6.1-002],<br>[R-6.4.6.1-003] of<br>3GPP TS 22.280 [2] | Authorisation to change affiliated groups of other specified user(s) | | Y | Y | Y | +| [R-6.4.6.2-001],<br>[R-6.4.6.2-002] of<br>3GPP TS 22.280 [2] | Authorisation to recommend to specified user(s) to affiliate to specific group(s) | | Y | Y | Y | +| [R-6.6.1-004] of<br>3GPP TS 22.280 [2] | Authorisation to perform regrouping | Y | Y | Y | Y | +| [R-6.7.2-001] of<br>3GPP TS 22.280 [2] | Presence status is available/not available to other users | Y | Y | Y | Y | +| [R-6.7.1-002],<br>[R-6.7.2-002] of<br>3GPP TS 22.280 [2] | List of MCVideo users that MCVideo user is authorised to obtain presence of | | | | | +| | > MCVideo IDs | Y | Y | Y | Y | +| [R-6.8.7.4.2-001],<br>[R-6.8.7.4.2-002] of<br>3GPP TS 22.280 [2] | Authorisation of a user to cancel an emergency alert on any MCVideo UE of any user | | Y | Y | Y | +| [R-6.13.4-001] of<br>3GPP TS 22.280 [2] | Authorisation for an MCVideo user to enable/disable an MCVideo user | | Y | Y | Y | +| [R-6.13.4-003],<br>[R-6.13.4-005],<br>[R-6.13.4-006],<br>[R-6.13.4-007] of<br>3GPP TS 22.280 [2] | Authorisation for an MCVideo user to (permanently /temporarily) enable/disable a UE | | Y | Y | Y | +| [R-7.14-002],<br>[R-7.14-003] of<br>3GPP TS 22.280 [2] | Authorization for manual switch to off-network while in on-network | Y | Y | Y | Y | +| [R-5.1.5-004] of<br>3GPP TS 22.280 [2] | Limitation of number of affiliations per user (Nc2) | N | Y | Y | Y | +| [R-6.4.6.1-001],<br>[R-6.4.6.1-004] of<br>3GPP TS 22.280 [2] | List of MCVideo users whose selected groups are authorized to be remotely changed | Y | Y | Y | Y | + +| | | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|---|---|---|---| +| [R-5.2.3.2-002], [R-5.2.3.2-003] of 3GPP TS 22.281 [3] | Period after which MCVideo data on a MCVideo UE is to be deleted if no action is taken by an authorized MCVideo user | Y | Y | Y | Y | +| [R-5.2.6.2.2-004] of 3GPP TS 22.281 [3] | Maximum number of simultaneous video streams that can be received (see NOTE 3) | Y | Y | Y | Y | +| [R-5.2.6.2.2-005] of 3GPP TS 22.281 [3] | Authorisation to automatically receive video communications | Y | Y | Y | Y | +| [R-5.2.6.2.2-006] of 3GPP TS 22.281 [3] | Authorisation to automatically receive emergency video streams | Y | Y | Y | Y | +| [R-5.2.6.2.2-007] of 3GPP TS 22.281 [3] | Authorisation to automatically receive imminent peril video streams | Y | Y | Y | Y | +| [R-5.2.6.2.2-008] of 3GPP TS 22.281 [3] | List of MCVideo groups for which video can be automatically/mandatorily received | | | | | +| | > MCVideo group IDs | Y | Y | Y | Y | +| [R-5.2.7.2-001] of 3GPP TS 22.281 [3] | Authorisation to request to override an active MCVideo transmission | Y | Y | Y | Y | +| [R-5.2.7.2-002] of 3GPP TS 22.281 [3] | Authorisation to select MCVideo transmissions that can be overridden | Y | Y | Y | Y | +| [R-5.2.7.2-004] of 3GPP TS 22.281 [3] | Authorisation to allow MCVideo private communications to override or not to override active MCVideo group communications | Y | Y | Y | Y | +| [R-5.2.8-005], [R-5.2.8-006] of 3GPP TS 22.281 [3] | Maximum length of time of a single video transmission | Y | Y | Y | Y | +| Subclause 5.2.9 of 3GPP TS 23.280 [16] | List of partner MCVideo systems in which this profile is valid for use during migration | | | | | +| Subclause 5.2.9 of 3GPP TS 23.280 [16] | > Identity of partner MCVideo system | Y | N | Y | Y | +| Subclause 10.1.1 of 3GPP TS 23.280 [16] | > Access information for partner MCVideo system (see NOTE 5) | Y | N | Y | Y | +| NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [6]. | | | | | | +| NOTE 2: The use of this parameter by the MCVideo UE is outside the scope of the present document. | | | | | | +| NOTE 3: The parameter can be set to an unlimited number of simultaneous streams received that can be received. | | | | | | +| NOTE 4: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [6]. | | | | | | +| NOTE 5: Access information for each partner MCVideo system comprises the list of information required for initial UE configuration to access an MCVideo system, as defined in table A.6-1 of 3GPP TS 23.280 [16] | | | | | | + +**Table A.3-3: MCVideo user profile configuration data (off network)** + +| Reference | Parameter description | MCVideo UE | MCVideo Server | Configuration management server | MCVideo user database | +|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|------------|----------------|---------------------------------|-----------------------| +| [R-7.2-003], [R-7.6-004] of 3GPP TS 22.280 [2] | List of off-network MCVideo groups for use by an MCVideo user | | | | | +| | > MCVideo Group IDs | Y | N | Y | Y | +| | > Application plane server identity information of group management server where group is defined | | | | | +| | >> Server URI | Y | N | Y | Y | +| | > Application plane server identity information of identity management server which provides authorization for group (see NOTE 1) | | | | | +| | >> Server URI | Y | N | Y | Y | +| 3GPP TS 33.180 [14] | > KMSUri for security domain of group (see NOTE 3) | Y | N | Y | Y | +| | > Presentation priority of the group relative to other groups and users (see NOTE 2) | Y | N | Y | Y | +| [R-7.12-002], [R-7.12-003] of 3GPP TS 22.280 [2] | Authorization for off-network services | Y | N | Y | Y | +| Subclause 7.2.3.3 | User info id (as specified in 3GPP TS 23.303 [7]) | Y | N | Y | Y | + +NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [6]. + +NOTE 2: The use of this parameter by the MCVideo UE is outside the scope of the present document. + +NOTE 3: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [6]. + +## A.4 MCVideo related Group configuration data + +The general aspects of group configuration are specified in 3GPP TS 23.280 [6]. + +Parameters specified in table A.4-1 are child parameters of the MCVideo configuration parameter specified in table A.4-1 in 3GPP TS 23.280 [6]. Parameters specified in table A.4-2 are child parameters of the MCVideo configuration parameter specified in table A.4-2 in 3GPP TS 23.280 [6]. Parameters specified in table A.4-3 are child parameters of the MCVideo configuration parameter specified in table A.4-3 in 3GPP TS 23.280 [6]. + +**Table A.4-1: Group configuration data (on and off network)** + +| Reference | Parameter description | MCVideo UE | MCVideo Server | Group management server | +|-----------------------------------------------------------------|---------------------------------------------------------------------------------------------|------------|----------------|-------------------------| +| [R-5.12-001] of 3GPP TS 22.280 [2] | >> Media confidentiality and integrity protection (see NOTE) | Y | Y | Y | +| [R-5.12-001] of 3GPP TS 22.280 [2] | >> Transmission control confidentiality and integrity protection (see NOTE) | Y | Y | Y | +| [R-5.12-001] of 3GPP TS 22.280 [2] | >> Group media protection security material (see NOTE) | Y | N | Y | +| [R-5.1.1.1-010] of 3GPP TS 22.281 [3] | >> List of allowed sets of video codecs and related information in order of preference | | | | +| [R-5.1.1.1-010] of 3GPP TS 22.281 [3] | >>> Video codecs | Y | Y | Y | +| [R-5.1.1.1-010] of 3GPP TS 22.281 [3] | >>> List of allowed video resolution | | | | +| | >>>> Video resolutions | Y | Y | Y | +| [R-5.1.1.1-010] of 3GPP TS 22.281 [3] | >>> List of allowed video frame rates | | | | +| | >>>> Video frame rates | Y | Y | Y | +| [R-5.1.1.3.2-002] of 3GPP TS 22.281 [3] | >> Allowed video modes | | | | +| | >>> Urgent real time mode allowed | N | Y | Y | +| | >>> Non-urgent real time mode allowed | N | Y | Y | +| | >>> Non real time mode allowed | N | Y | Y | +| [R-5.1.1.3.2-002] of 3GPP TS 22.281 [3] | >> Active video mode (urgent real time mode, non urgent real time mode, non real time mode) | Y | Y | Y | +| [R-5.3.2.2-002] of 3GPP TS 22.281 [3] | >> Allowed maximum simultaneous MCVideo transmitting group members | N | Y | Y | +| NOTE: Security mechanisms are specified in 3GPP TS 33.180 [14]. | | | | | + +**Table A.4-2: Group configuration data (on network)** + +| Reference | Parameter description | MCVideo UE | MCVideo Server | Group management server | +|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|------------|----------------|-------------------------| +| [R-6.4.5-001], [R-6.4.5-003] of 3GPP TS 22.280 [2] | >> Authorisation of a user to request a list of affiliated members of a group | Y | Y | Y | +| [R-5.1.7-002], [R-6.2.2-001], [R-6.6.2.2-006], [R-6.8.7.2-003] of 3GPP TS 22.280 [2] | >> Priority of the group | N | Y | Y | + +**Table A.4-3: Group configuration data (off network)** + +| Reference | Parameter description | MCVideo UE | MCVideo Server | Group management server | +|---------------------------------------|----------------------------------------------------------------------------------------------------|------------|----------------|-------------------------| +| Subclause 7.7.2.1 | >> Indication of whether the UE shall use single arbitrator approach or self arbitration approach. | Y | N | Y | +| [R-5.3.2.2-003] of 3GPP TS 22.281 [3] | >> Allowed maximum number of simultaneous transmissions (N9) | Y | Y | Y | +| Subclause 7.1.3 | >> Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values | | | | +| | >>> MCVideo group call signalling | Y | N | Y | +| | >>> MCVideo group call media | Y | N | Y | +| | >>> MCVideo emergency group call signalling | Y | N | Y | +| | >>> MCVideo emergency group call media | Y | N | Y | +| | >>> MCVideo imminent peril group call signalling | Y | N | Y | +| | >>> MCVideo imminent peril group call media | Y | N | Y | + +## A.5 MCVideo service configuration data + +The general aspects of MC service configuration are specified in 3GPP TS 23.280 [6]. The MCVideo service configuration data is stored in the MCVideo server. + +Tables A.5-1 and A.5-2 describe the configuration data required to support the use of on-network MCVideo service. Tables A.5-1 and A.5-3 describe the configuration data required to support the use of off-network MCVideo service. Data in table A.5-1 and table A.5-3 can be configured offline using the CSC-11 reference point. + +**Table A.5-1: MCVideo service configuration data (on and off network)** + +| Reference | Parameter description | MCVideo UE | MCVideo Server | Configuration management server | +|-------------------------------------|-------------------------------------------------------------------------------------------------------|------------|----------------|---------------------------------| +| [R-5.2.2-001] of 3GPP TS 22.280 [2] | Levels of group hierarchy for group-broadcast groups (Bc1) | Y | Y | Y | +| [R-5.2.3-001] of 3GPP TS 22.280 [2] | Levels of user hierarchy for user-broadcast groups (Bc2) | Y | Y | Y | +| [R-5.7-002] of 3GPP TS 22.280 [2] | Minimum length (Nc3) of an alphanumeric identifier (i.e. alias) assigned by an MCVideo administrator. | Y | N | Y | + +**Table A.5-2: MCVideo service configuration data (on network)** + +| Reference | Parameter description | MCVideo UE | MCVideo Server | Configuration management server | +|-----------------------------------------------------------------|------------------------------------------------------------------------|------------|----------------|---------------------------------| +| [R-5.12-001] of 3GPP TS 22.280 [2] | Protect confidentiality of signalling (see NOTE) | Y | Y | Y | +| [R-5.12-001] of 3GPP TS 22.280 [2] | Protect integrity of signalling (see NOTE) | Y | Y | Y | +| [R-5.12-001] of 3GPP TS 22.280 [2] | Use signalling protection between MCVideo servers (see NOTE) | N | Y | Y | +| [R-5.12-001] of 3GPP TS 22.280 [2] | Use transmission control protection between MCVideo servers (see NOTE) | N | Y | Y | +| NOTE: Security mechanisms are specified in 3GPP TS 33.180 [14]. | | | | | + +**Table A.5-3: MCVideo service configuration data (off network)** + +| Reference | Parameter description | MCVideo UE | MCVideo Server | Configuration management server | +|---------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|------------|----------------|---------------------------------| +| [R-7.6-001], [R-7.6-002], [R-7.6-003] of 3GPP TS 22.280 [2] | Default <b>ProSe</b> Per-Packet priority (as specified in 3GPP <b>TS 23.303</b> [7]) values | | | | +| | > MCVideo private call signalling | Y | N | Y | +| | > MCVideo private call media | Y | N | Y | +| | > MCVideo Emergency private call signalling | Y | N | Y | +| | > MCVideo Emergency private call media | Y | N | Y | +| Subclause 7.5.3.3 | Periodicity interval (in seconds) of Capability announcement (see NOTE) | Y | N | Y | +| NOTE: If the value of the periodicity interval is set to zero, the capability announcement is not sent. | | | | | + +# --- Annex B (informative): Change history + +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +|---------|---------|-----------|------|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| 2016-04 | | | | | | Initial version. | 0.0.0 | +| 2016-06 | | | | | | Implemented the following pCRs approved in SA6#11:<br>S6-160535, S6-160536, S6-160589<br>Title aligned with the title in MCVideo WID. | 0.1.0 | +| 2016-08 | | | | | | Implemented the following pCRs approved in SA6#12:<br>S6-160800, S6-160805, S6-160881, S6-160882, S6-160931 | 0.2.0 | +| 2016-10 | | | | | | Implemented the following pCRs approved in SA6#13: S6-161155, S6-161166, S6-161226, S6-161227, S6-161233, S6-161234, S6-161235, S6-161236, S6-161237, S6-161239, S6-161240, S6-161241, S6-161264 | 0.3.0 | +| 2016-11 | | | | | | Implemented the following pCRs approved in SA6#14: S6-161461, S6-161464, S6-161465, S6-161468, S6-161469, S6-161473, S6-161474, S6-161476, S6-161479, S6-161481, S6-161482, S6-161483, S6-161485, S6-161497, S6-161566, S6-161567, S6-161568, S6-161569, S6-161570, S6-161574, S6-161575, S6-161585, S6-161588, S6-161599, S6-161600, S6-161601, S6-161602, S6-161603, S6-161608 | 0.4.0 | +| 2016-11 | SA#74 | SP-160877 | | | | Submitted for Approval at SA#74 | 1.0.0 | +| 2016-12 | SA#74 | SP-160877 | | | | MCC Editorial update for publication after TSG SA approval (SA#74) | 14.0.0 | +| 2017-03 | SA#75 | SP-170070 | 0001 | 1 | F | Alignment of definitions | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0002 | 2 | F | Alignment of group affiliation and de-affiliation requirements | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0003 | 1 | F | Alignment of bearer management | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0004 | 2 | F | Adding descriptive text for several general sections | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0005 | 1 | F | MCVideo call connect and disconnect on MBMS | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0007 | | F | Alignment of business relationships, identities, and application of functional model to deployments | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0008 | 1 | F | Functional model update | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0009 | 1 | F | Location related description alignment | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0010 | 1 | F | Reception control at receiving participant | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0011 | 1 | F | Feedback between reception control and transmission control | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0013 | 1 | F | Activity status sharing | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0014 | 1 | F | Corrections to video push | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0017 | | F | Obsolete editor's notes | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0018 | | F | Response message | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0020 | 1 | F | Clarification on Editor's notes in subclause 7.3.3.2 in MCVideo | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0021 | 1 | F | Clarification on Editor's notes in MCVideo | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0022 | 1 | F | Clarification on transmission control | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0023 | | D | Editorial corrections in MCVideo | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0024 | 2 | F | MCVideo configurations | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0027 | 1 | F | Addition of definition for MCVideo ID | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0028 | 1 | F | Correction of requirement reference for list of implicitly affiliated groups in MCVideo user profile config | 14.1.0 | +| 2017-03 | SA#75 | SP-170070 | 0029 | 3 | F | Off-network transmission arbitration | 14.1.0 | +| 2017-06 | SA#76 | SP-170391 | 0042 | 1 | F | Miscellaneous corrections to configuration | 14.2.0 | +| 2017-06 | SA#76 | SP-170391 | 0043 | 5 | F | Addition of identity management server address per group | 14.2.0 | +| 2017-06 | SA#76 | SP-170391 | 0044 | | F | Clarifications on off-network group call answer response | 14.2.0 | +| 2017-06 | SA#76 | SP-170391 | 0045 | 1 | F | Clarifications on off-network group call procedure descriptions | 14.2.0 | +| 2017-06 | SA#76 | SP-170391 | 0046 | 1 | F | Clarifications on pre-conditions of group communication in off-network | 14.2.0 | +| 2017-06 | SA#76 | SP-170391 | 0048 | | F | Remove Editor's Note on broadcast group communication in 23281 | 14.2.0 | +| 2017-06 | SA#76 | SP-170391 | 0049 | | F | Remove Editor's Note on Video details in Video pull and push in 23281 | 14.2.0 | +| 2017-06 | SA#76 | SP-170391 | 0050 | 2 | F | Remove Editor's Note on Device ID used for Capabilities info request in 23281 | 14.2.0 | +| 2017-06 | SA#76 | SP-170391 | 0051 | 1 | F | Remove Editor's Note on Clarifications for periodic capability announcements in 23281 | 14.2.0 | +| 2017-06 | SA#76 | SP-170391 | 0052 | 1 | F | Some clarifications on off-network group call | 14.2.0 | +| 2017-06 | SA#76 | SP-170391 | 0060 | 1 | F | Editorial correction in chapter Release chat group call of MCVideo | 14.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|--------------------------------------------------------------------------------------|--------| +| 2017-06 | SA#76 | SP-170391 | 0061 | 2 | F | Inclusion of KMSUri to allow multiple security domains | 14.2.0 | +| 2017-06 | SA#76 | SP-170391 | 0062 | | F | Addition of ProSe Per Packet Priority to group configuration | 14.2.0 | +| 2017-06 | SA#76 | SP-170391 | 0063 | 1 | F | Configuration for emergency alerts | 14.2.0 | +| 2017-06 | SA#76 | SP-170391 | 0066 | 1 | F | Video modes usage | 14.2.0 | +| 2017-06 | SA#76 | SP-170391 | 0067 | 2 | F | Communications remote control | 14.2.0 | +| 2017-06 | SA#76 | SP-170391 | 0069 | 3 | F | Alignment of MCVideo user profile configurations | 14.2.0 | +| 2017-06 | SA#76 | SP-170391 | 0071 | | F | Corrections to Group configuration data for all MC services | 14.2.0 | +| 2017-06 | SA#76 | SP-170395 | 0070 | 1 | C | Resource Management in MCVideo | 15.0.0 | +| 2017-09 | SA#77 | SP-170680 | 0072 | 1 | A | CR on MCVideo capabilities information retrieval and remote transmit media end | 15.1.0 | +| 2017-09 | SA#77 | SP-170680 | 0075 | 2 | A | MCVideo call connect | 15.1.0 | +| 2017-09 | SA#77 | SP-170683 | 0077 | 3 | B | Camera query | 15.1.0 | +| 2017-09 | SA#77 | SP-170683 | 0078 | 4 | B | Video capabilities sharing enhancement | 15.1.0 | +| 2017-09 | SA#77 | SP-170683 | 0079 | 1 | B | MCVideo emergency private call | 15.1.0 | +| 2018-01 | SA#78 | SP-170895 | 0080 | 3 | B | Functional model for MCVideo interconnection | 15.2.0 | +| 2018-01 | SA#78 | SP-170888 | 0083 | 1 | A | CR on clarification for MC service group ID | 15.2.0 | +| 2018-01 | SA#78 | SP-170892 | 0084 | 4 | B | Mutual adaption during MCVideo communication | 15.2.0 | +| 2018-01 | SA#78 | SP-170892 | 0085 | 3 | B | Renaming of MCVideo emergency group call cancel and correction to clause 7.1.2.5.1.3 | 15.2.0 | +| 2018-01 | SA#78 | SP-170892 | 0086 | 1 | F | Adding implicit transmit media request IE to MCVideo emergency group call request | 15.2.0 | +| 2018-01 | SA#78 | SP-170892 | 0087 | 1 | F | Renaming of MCVideo "emergency condition" | 15.2.0 | +| 2018-01 | SA#78 | SP-170888 | 0091 | 2 | A | Rejection of group call request | 15.2.0 | +| 2018-01 | SA#78 | SP-170888 | 0093 | 2 | A | MCVideo server PSI configuration | 15.2.0 | +| 2018-01 | SA#78 | SP-170892 | 0095 | 1 | D | Correction of wrong "MCPTT" words | 15.2.0 | +| 2018-01 | SA#78 | SP-170892 | 0097 | 1 | F | Renaming of "MCVideo emergency state cancel" and other corrections | 15.2.0 | +| 2018-04 | SA#79 | SP-180147 | 0099 | 1 | A | Correction of security specification references | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0100 | 2 | B | User profile for MCVideo migration | 15.3.0 | +| 2018-04 | SA#79 | SP-180152 | 0101 | 1 | F | Update of references to stage 1 specifications | 15.3.0 | +| 2018-04 | SA#79 | SP-180154 | 0103 | | B | Definition of MCVideo-3 | 15.3.0 | +| 2018-06 | SA#80 | SP-180366 | 0105 | | A | Clarification for presentation priority in MCVideo UE configuration | 15.4.0 | + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 9 | +| 1 Scope..... | 10 | +| 2 References..... | 10 | +| 3 Definitions, symbols and abbreviations..... | 11 | +| 3.1 Definitions..... | 11 | +| 3.2 Abbreviations ..... | 12 | +| 4 Introduction..... | 13 | +| 5 Architectural requirements..... | 13 | +| 5.1 Transmission control..... | 13 | +| 5.2 Reception control ..... | 13 | +| 5.3 Short Data Service capability..... | 14 | +| 5.4 File distribution capability ..... | 14 | +| 5.5 Data streaming capability..... | 14 | +| 5.6 MCData group affiliation and MCData group de-affiliation ..... | 15 | +| 5.7 Conversation management..... | 15 | +| 5.8 Bearer management..... | 15 | +| 5.8.1 General ..... | 15 | +| 5.8.2 EPS bearer considerations ..... | 15 | +| 5.8.3 EPS unicast bearer considerations for MCData ..... | 15 | +| 5.8.4 MBMS bearer management..... | 16 | +| 5.9 Disposition ..... | 16 | +| 6 Functional model..... | 16 | +| 6.1 General ..... | 16 | +| 6.2 Description of the planes..... | 16 | +| 6.3 Transmission and reception control aspects..... | 16 | +| 6.3.1 General ..... | 16 | +| 6.4 Generic functional model..... | 17 | +| 6.4.1 On-network functional model..... | 17 | +| 6.4.2 Off-network functional model..... | 17 | +| 6.4.3 Functional entities description..... | 17 | +| 6.4.3.1 Application plane..... | 17 | +| 6.4.3.1.1 MCData client ..... | 17 | +| 6.4.3.1.2 MCData server ..... | 17 | +| 6.4.3.1.3 MCData user database..... | 18 | +| 6.4.3.1.4 Interworking function to LMR system..... | 18 | +| 6.4.3.2 Signalling control plane ..... | 18 | +| 6.4.3.3 MCData message store ..... | 18 | +| 6.4.3.4 Message store client..... | 19 | +| 6.4.4 Reference points ..... | 19 | +| 6.4.4.1 Application plane..... | 19 | +| 6.4.4.1.1 General ..... | 19 | +| 6.4.4.1.2 Reference point MCData-2 (between the MCData server and the MCData user database) ..... | 19 | +| 6.4.4.1.3 Reference point MCData-3 (between the MCData server and the MCData server)..... | 19 | +| 6.4.4.1.3A Reference point MCData-5 (between the MCData capability function and the EPS) ..... | 19 | +| 6.4.4.1.4 Reference point MCData-6 (between the MCData server and the EPS) ..... | 20 | +| 6.4.4.1.5 Reference point IWF-2 (between the interworking function to LMR system and the MCData server)..... | 20 | +| 6.4.4.1.6 Reference point MCData-7 (between the Message store client and MCData message store) ..... | 20 | +| 6.4.4.1.7 Reference point MCData-8 (between the MCData message store and MCData server)..... | 20 | +| 6.5 Functional model for short data service ..... | 20 | +| 6.5.1 On-network functional model..... | 20 | +| 6.5.2 Off-network functional model..... | 21 | +| 6.5.3 Functional entities description..... | 21 | +| 6.5.3.1 Application plane..... | 21 | +| 6.5.3.1.1 SDS function ..... | 21 | + +| | | | +|-----------|------------------------------------------------------------------------------------------------------------------------|----| +| 6.5.3.1.2 | SDS distribution function..... | 21 | +| 6.5.3.1.3 | Transmission/Reception control..... | 22 | +| 6.5.3.2 | Signalling control plane ..... | 22 | +| 6.5.4 | Reference points ..... | 22 | +| 6.5.4.1 | Application plane..... | 22 | +| 6.5.4.1.1 | Reference point MCData-SDS-1 (between the SDS distribution function and the SDS function) ..... | 22 | +| 6.5.4.1.2 | Reference point MCData-SDS-2 (unicast between the SDS distribution function and the SDS function) ..... | 22 | +| 6.5.4.1.3 | Reference point MCData-SDS-3 (multicast between the SDS distribution function and the SDS function)..... | 22 | +| 6.5.4.2 | Signalling control plane ..... | 23 | +| 6.6 | Functional model for file distribution ..... | 23 | +| 6.6.1 | On-network functional model..... | 23 | +| 6.6.2 | Off-network functional model..... | 24 | +| 6.6.3 | Functional entities description..... | 24 | +| 6.6.3.1 | Application plane..... | 24 | +| 6.6.3.1.1 | FD function ..... | 24 | +| 6.6.3.1.2 | Media storage client ..... | 25 | +| 6.6.3.1.3 | Transmission/Reception control..... | 25 | +| 6.6.3.1.4 | Media storage function..... | 25 | +| 6.6.3.2 | Signalling control plane ..... | 25 | +| 6.6.4 | Reference points ..... | 25 | +| 6.6.4.1 | Application plane..... | 25 | +| 6.6.4.1.1 | Reference point MCData-FD-1 (between the FD functions of the MCData client and the MCData server)..... | 25 | +| 6.6.4.1.2 | Reference point MCData-FD-2 (unicast between the FD functions of the MCData client and the MCData server)..... | 26 | +| 6.6.4.1.3 | Reference point MCData-FD-3 (multicast between the FD functions of the MCData client and the MCData server) ..... | 26 | +| 6.6.4.1.4 | Reference point MCData-FD-4 (media storage function and media storage client)..... | 26 | +| 6.6.4.1.5 | Reference point MCData-FD-5 (FD function and media storage function) ..... | 26 | +| 6.6.4.2 | Signalling control plane ..... | 26 | +| 6.7 | Functional model for data streaming..... | 26 | +| 6.7.1 | On-network functional model..... | 26 | +| 6.7.2 | Off-network functional model..... | 27 | +| 6.7.3 | Functional entities description..... | 27 | +| 6.7.3.1 | Application plane..... | 27 | +| 6.7.3.1.1 | DS function ..... | 27 | +| 6.7.3.1.2 | Data streaming and distribution function ..... | 27 | +| 6.7.3.1.3 | Transmission/Reception control..... | 28 | +| 6.7.3.2 | Signalling control plane ..... | 28 | +| 6.7.4 | Reference points ..... | 28 | +| 6.7.4.1 | Application plane..... | 28 | +| 6.7.4.1.1 | Reference point MCData-DS-1 (between the data streaming and distribution function and the DS function) ..... | 28 | +| 6.7.4.1.2 | Reference point MCData-DS-2 (unicast between the data streaming and distribution function and the DS function) ..... | 28 | +| 6.7.4.1.3 | Reference point MCData-DS-3 (multicast between the data streaming and distribution function and the DS function) ..... | 29 | +| 6.7.4.2 | Signalling control plane ..... | 29 | +| 7 | Procedures and information flows ..... | 29 | +| 7.1 | MCData service configuration ..... | 29 | +| 7.2 | Affiliation and de-affiliation to/from MCData group(s) ..... | 29 | +| 7.3 | Use of MBMS transmission (on-network)..... | 30 | +| 7.3.1 | Information flows for MBMS Transmission..... | 30 | +| 7.3.2 | Use of pre-established MBMS bearers..... | 30 | +| 7.3.3 | Use of dynamic MBMS bearer establishment..... | 30 | +| 7.3.4 | Switching from MBMS bearer to unicast bearer..... | 30 | +| 7.4 | Short data service ..... | 31 | +| 7.4.1 | General ..... | 31 | + +| | | | +|------------|--------------------------------------------------------------------------------------|----| +| 7.4.2 | Short data service for on-network ..... | 31 | +| 7.4.2.1 | Information flows for short data service..... | 31 | +| 7.4.2.1.1 | MCDData standalone data request..... | 31 | +| 7.4.2.1.2 | MCDData data disposition notification ..... | 31 | +| 7.4.2.1.3 | MCDData standalone session data request ..... | 32 | +| 7.4.2.1.4 | MCDData standalone session data response..... | 32 | +| 7.4.2.1.5 | MCDData session data request ..... | 32 | +| 7.4.2.1.6 | MCDData session data response..... | 33 | +| 7.4.2.1.7 | MCDData group standalone data request (MCDData client – MCDData server)..... | 33 | +| 7.4.2.1.8 | MCDData group standalone data request (MCDData server – MCDData client)..... | 34 | +| 7.4.2.1.9 | MCDData data disposition notification(s) (MCDData server – MCDData client) ..... | 34 | +| 7.4.2.1.10 | MCDData group session standalone data request (MCDData client – MCDData server)..... | 34 | +| 7.4.2.1.11 | MCDData group session standalone data request (MCDData server – MCDData client)..... | 35 | +| 7.4.2.1.12 | MCDData group session standalone data response ..... | 35 | +| 7.4.2.1.13 | MCDData group data request (MCDData client – MCDData server)..... | 36 | +| 7.4.2.1.14 | MCDData group data request (MCDData server – MCDData client)..... | 36 | +| 7.4.2.1.15 | MCDData group data response ..... | 37 | +| 7.4.2.2 | One-to-one standalone short data service using signalling control plane..... | 37 | +| 7.4.2.2.1 | General ..... | 37 | +| 7.4.2.2.2 | Procedure..... | 37 | +| 7.4.2.3 | One-to-one standalone short data service using media plane ..... | 38 | +| 7.4.2.3.1 | General ..... | 38 | +| 7.4.2.3.2 | Procedure..... | 38 | +| 7.4.2.4 | One-to-one short data service session..... | 40 | +| 7.4.2.4.1 | General ..... | 40 | +| 7.4.2.4.2 | Procedure..... | 40 | +| 7.4.2.5 | Group standalone short data service using signalling control plane..... | 41 | +| 7.4.2.5.1 | General ..... | 41 | +| 7.4.2.5.2 | Procedure..... | 41 | +| 7.4.2.6 | Group standalone short data service using media plane ..... | 43 | +| 7.4.2.6.1 | General ..... | 43 | +| 7.4.2.6.2 | Procedure..... | 43 | +| 7.4.2.7 | Group short data service session..... | 44 | +| 7.4.2.7.1 | General ..... | 44 | +| 7.4.2.7.2 | Procedure..... | 44 | +| 7.4.3 | Short data service for off-network..... | 46 | +| 7.4.3.1 | General ..... | 46 | +| 7.4.3.2 | Information flows for short data service..... | 46 | +| 7.4.3.2.1 | MCDData standalone data request..... | 46 | +| 7.4.3.2.2 | MCDData data disposition notification ..... | 46 | +| 7.4.3.2.3 | MCDData group standalone data request ..... | 47 | +| 7.4.3.3 | One-to-one standalone short data service using signalling control plane..... | 47 | +| 7.4.3.3.1 | General ..... | 47 | +| 7.4.3.3.2 | Procedure..... | 47 | +| 7.4.3.4 | Group standalone short data service using signalling control plane..... | 48 | +| 7.4.3.4.1 | General ..... | 48 | +| 7.4.3.4.2 | Procedure..... | 48 | +| 7.5 | File distribution ..... | 49 | +| 7.5.1 | General ..... | 49 | +| 7.5.2 | File distribution for on-network ..... | 50 | +| 7.5.2.1 | Information flows for file distribution ..... | 50 | +| 7.5.2.1.1 | MCDData upload data request..... | 50 | +| 7.5.2.1.2 | MCDData upload data response..... | 50 | +| 7.5.2.1.3 | MCDData download data request..... | 50 | +| 7.5.2.1.4 | MCDData download data response..... | 50 | +| 7.5.2.1.5 | MCDData FD request (using HTTP)..... | 51 | +| 7.5.2.1.6 | MCDData FD response (using HTTP)..... | 51 | +| 7.5.2.1.7 | MCDData download completed report ..... | 51 | +| 7.5.2.1.8 | MCDData FD request (using media plane)..... | 51 | +| 7.5.2.1.9 | MCDData FD response (using media plane)..... | 52 | +| 7.5.2.1.10 | MCDData group standalone FD request (using HTTP)..... | 52 | +| 7.5.2.1.11 | MCDData group standalone FD response (using HTTP) ..... | 52 | + +| | | | +|------------|------------------------------------------------------------------------------------------|----| +| 7.5.2.1.12 | MCDData group standalone FD request (using media plane) ..... | 53 | +| 7.5.2.1.13 | MCDData group standalone FD response (using media plane)..... | 53 | +| 7.5.2.2 | File upload using HTTP..... | 53 | +| 7.5.2.2.1 | General ..... | 53 | +| 7.5.2.2.2 | Procedure..... | 53 | +| 7.5.2.3 | File download using HTTP..... | 54 | +| 7.5.2.3.1 | General ..... | 54 | +| 7.5.2.3.2 | Procedure..... | 54 | +| 7.5.2.4 | One-to-one file distribution using HTTP..... | 55 | +| 7.5.2.4.1 | General ..... | 55 | +| 7.5.2.4.2 | Procedure..... | 55 | +| 7.5.2.5 | One-to-one file distribution using media plane ..... | 56 | +| 7.5.2.5.1 | General ..... | 56 | +| 7.5.2.5.2 | Procedure..... | 56 | +| 7.5.2.6 | Group standalone file distribution using HTTP..... | 58 | +| 7.5.2.6.1 | General ..... | 58 | +| 7.5.2.6.2 | Procedure..... | 58 | +| 7.5.2.7 | Group standalone file distribution using media plane ..... | 59 | +| 7.5.2.7.1 | General ..... | 59 | +| 7.5.2.7.2 | Procedure..... | 59 | +| 7.5.3 | File distribution for off-network..... | 61 | +| 7.5.3.2 | Information flows for file distribution ..... | 61 | +| 7.5.3.2.1 | MCDData FD request (using media plane)..... | 61 | +| 7.5.3.2.2 | MCDData FD response (using media plane) ..... | 61 | +| 7.5.3.2.3 | MCDData download completed report ..... | 62 | +| 7.5.3.2.4 | MCDData group standalone FD request (using media plane) ..... | 62 | +| 7.5.3.2.5 | MCDData group standalone FD response (using media plane)..... | 62 | +| 7.5.3.3 | One-to-one standalone file distribution using media plane ..... | 63 | +| 7.5.3.3.1 | General ..... | 63 | +| 7.5.3.3.2 | Procedure..... | 63 | +| 7.5.3.4 | Group standalone file distribution using media plane ..... | 64 | +| 7.5.3.4.1 | General ..... | 64 | +| 7.5.3.4.2 | Procedure..... | 64 | +| 7.6 | Transmission and reception control ..... | 66 | +| 7.6.1 | General ..... | 66 | +| 7.6.2 | Transmission and reception control for on-network..... | 66 | +| 7.6.2.1 | Information flows for transmission and reception control..... | 66 | +| 7.6.2.1.1 | MCDData control indication..... | 66 | +| 7.6.2.1.2 | MCDData indication ..... | 66 | +| 7.6.2.1.3 | MCDData get deferred list request ..... | 67 | +| 7.6.2.1.4 | MCDData get deferred list response ..... | 67 | +| 7.6.2.2 | Automatic transmission for SDS ..... | 67 | +| 7.6.2.2.1 | General ..... | 67 | +| 7.6.2.2.2 | Procedure..... | 67 | +| 7.6.2.3 | Send data with mandatory download..... | 68 | +| 7.6.2.3.1 | General ..... | 68 | +| 7.6.2.3.2 | Procedure..... | 68 | +| 7.6.2.4 | Send data without mandatory download..... | 69 | +| 7.6.2.4.1 | General ..... | 69 | +| 7.6.2.4.2 | Procedure..... | 69 | +| 7.6.2.5 | Accessing list of deferred data group communications ..... | 71 | +| 7.6.2.5.1 | General ..... | 71 | +| 7.6.2.5.2 | Procedure..... | 71 | +| 7.7 | Communication release ..... | 71 | +| 7.7.1 | General ..... | 71 | +| 7.7.2 | Communication release for on-network..... | 71 | +| 7.7.2.1 | Information flows for communication release..... | 71 | +| 7.7.2.1.1 | MCDData communication release request (one-to-one communication using media plane)..... | 71 | +| 7.7.2.1.2 | MCDData communication release response (one-to-one communication using media plane)..... | 72 | +| 7.7.2.1.3 | MCDData communication release request (group communication using media plane)..... | 72 | +| 7.7.2.1.4 | MCDData communication release response (group communication using media plane) ..... | 72 | +| 7.7.2.1.5 | MCDData communication release request (communication using HTTP) ..... | 73 | + +| | | | +|-------------|---------------------------------------------------------------------------------------------------|----| +| 7.7.2.1.6 | MCData communication release response (communication using HTTP)..... | 73 | +| 7.7.2.1.7 | Data not available control indication ..... | 73 | +| 7.7.2.1.8 | MCData server communication release request (one-to-one communication using media plane)..... | 73 | +| 7.7.2.1.9 | MCData server communication release response (one-to-one communication using media plane)..... | 73 | +| 7.7.2.1.10 | MCData server communication release request (group communication using media plane)..... | 74 | +| 7.7.2.1.11 | MCData server communication release response (group communication using media plane) ..... | 74 | +| 7.7.2.1.12 | MCData server communication release indication (communication using HTTP) ..... | 74 | +| 7.7.2.1.13 | MCData release intent request (one-to-one communication using media plane) ..... | 74 | +| 7.7.2.1.14 | MCData more information response (one-to-one communication using media plane)..... | 75 | +| 7.7.2.1.15 | MCData release intent request (group communication using media plane) ..... | 75 | +| 7.7.2.1.16 | MCData more information response (group communication using media plane)..... | 75 | +| 7.7.2.1.17 | MCData auth user communication release request (one-to-one communication using media plane)..... | 76 | +| 7.7.2.1.18 | MCData auth user communication release response (one-to-one communication using media plane)..... | 76 | +| 7.7.2.1.19 | MCData auth user communication release request (group communication using media plane)..... | 76 | +| 7.7.2.1.20 | MCData auth user communication release response (group communication using media plane)..... | 76 | +| 7.7.2.1.21 | MCData request for extension..... | 77 | +| 7.7.2.1.22 | MCData response for extension ..... | 77 | +| 7.7.2.2 | MCData user initiated communication release..... | 77 | +| 7.7.2.2.1 | General ..... | 77 | +| 7.7.2.2.2 | Release of MCData communication using media plane ..... | 77 | +| 7.7.2.2.2.1 | General ..... | 77 | +| 7.7.2.2.2.2 | Procedure..... | 77 | +| 7.7.2.2.3 | Release of MCData communication using HTTP..... | 78 | +| 7.7.2.2.3.1 | General ..... | 78 | +| 7.7.2.2.3.2 | Procedure..... | 78 | +| 7.7.2.3 | MCData server initiated communication release without prior indication..... | 79 | +| 7.7.2.3.1 | General ..... | 79 | +| 7.7.2.3.2 | Release of MCData communication using media plane ..... | 79 | +| 7.7.2.3.2.1 | General ..... | 79 | +| 7.7.2.3.2.2 | Procedure..... | 80 | +| 7.7.2.3.3 | Release of MCData communication using HTTP..... | 81 | +| 7.7.2.3.3.1 | General ..... | 81 | +| 7.7.2.3.3.2 | Procedure..... | 81 | +| 7.7.2.4 | MCData server initiated communication release with prior indication..... | 82 | +| 7.7.2.4.1 | General ..... | 82 | +| 7.7.2.4.2 | Procedure..... | 82 | +| 7.7.2.5 | Authorized MCData user initiated communication release without prior indication ..... | 83 | +| 7.7.2.5.1 | General ..... | 83 | +| 7.7.2.5.2 | Procedure..... | 83 | +| 7.7.2.6 | Authorized MCData user initiated communication release with prior indication ..... | 84 | +| 7.7.2.6.1 | General ..... | 84 | +| 7.7.2.6.2 | Procedure..... | 84 | +| 7.8 | Conversation management..... | 86 | +| 7.8.1 | General ..... | 86 | +| 7.8.2 | Conversation management for on-network ..... | 86 | +| 7.8.2.1 | Information flows for conversation management..... | 86 | +| 7.8.2.2 | One-to-one conversation management ..... | 86 | +| 7.8.2.2.1 | Procedure..... | 86 | +| 7.8.2.3 | Group conversation management ..... | 87 | +| 7.8.2.3.1 | Procedure..... | 87 | +| 7.8.3 | Conversation management for off-network..... | 87 | +| 7.8.3.1 | One-to-one conversation management ..... | 87 | +| 7.8.3.1.1 | Procedure..... | 87 | +| 7.8.3.2 | Group conversation management ..... | 88 | +| 7.8.3.2.1 | Procedure..... | 88 | +| 7.9 | Enhanced status..... | 89 | +| 7.9.1 | General ..... | 89 | + +7.9.2 Preset values for enhanced status ..... 89 + +7.9.3 Enhanced status for on-network ..... 89 + +7.9.3.1 Sharing enhanced status information..... 89 + +7.9.3.1.1 Procedure..... 89 + +7.9.4 Enhanced status for off-network..... 90 + +7.9.4.1 Sharing enhanced status information..... 90 + +7.9.4.1.1 Procedure..... 90 + +7.10 MCData emergency alert (on-network and off-network) ..... 91 + +7.11 User authentication and authorization for MCData service ..... 91 + +7.12 MCData resource management (on-network)..... 91 + +7.12.1 General ..... 91 + +7.12.2 MCData services not handled by SIP core ..... 91 + +**Annex A (normative): MCData related configuration data..... 93** + +A.1 General..... 93 + +A.2 MCData UE configuration data ..... 94 + +A.3 MCData user profile configuration data ..... 95 + +A.4 MCData related Group configuration data..... 100 + +A.5 MCData service configuration data ..... 102 + +**Annex B (informative): Transmission control for MCData..... 103** + +B.1 Overview of transmission control process ..... 103 + +B.2 Transmission control arbitration ..... 104 + +**Annex C (informative): Secure IP connectivity requirements..... 105** + +Annex D (informative): Change history..... 106 + +--- + +## Foreword + +This Technical Specification has been produced by the 3<sup>rd</sup> 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. + +--- + +# 1 Scope + +This document specifies the functional architecture, procedures and information flows needed to support the Mission Critical Data (MCData) services. MCData is a suite of services which utilizes the common functional architecture defined in 3GPP TS 23.280 [5] to support MC services over **LTE** including the common services core. + +MCData services suite consists of the following sub-services: + +- short data service (SDS); +- file distribution (FD). + +MCData features include: + +- conversation management; +- transmission and reception control; +- communication release; and +- enhanced status. + +The corresponding service requirements are defined in 3GPP TS 22.282 [3] and 3GPP TS 22.280 [2]. + +The present document is applicable primarily to MCData service using **E-UTRAN** access based on the **EPC** architecture defined in 3GPP **TS 23.401** [4]. Certain application functions of the MCData service could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access. + +The MCData service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways. + +--- + +# 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.280: "Mission Critical Common Requirements (MCCoRe); Stage 1". +- [3] 3GPP TS 22.282: "Mission Critical Data services". +- [4] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [5] 3GPP TS 23.280: "Common functional architecture and information flows to support mission critical communication services; Stage 2". +- [6] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [7] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2". +- [8] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE\_LTE); Stage 2". +- [9] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2". + +- [10] 3GPP TS 23.002: "Network Architecture". +- [11] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); stage 2". +- [12] 3GPP TS 29.283: "Diameter data management applications". +- [13] 3GPP TS 33.180: "Security of the Mission Critical Service". +- [14] 3GPP TS 23.203: "Policy and charging control architecture". +- [15] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [16] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE\_LTE); MB2 reference point; Stage 3". +- [17] 3GPP TS 29.214: "Policy and charging control over Rx reference point". +- [18] 3GPP TS 23.283: "Mission Critical Communication Interworking with Land Mobile Radio Systems; Stage 2". + +--- + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Auto-receive:** A mechanism where data smaller than a configured size threshold are delivered to the receiving MCData client(s) from the MCData server i.e. without waiting for the receiving user to indicate a present need for the data. + +**Conversation identifier:** A universally unique identifier that identifies a series of related MCData transactions. + +**Data stream:** A sequence of data that is agnostic to any underlying media (e.g. audio, video, telemetry data), on which processing of data (e.g. semantic, syntactic, save or filter operation) can begin before all the content is received. + +**FD disposition:** is one of "not downloaded" and "download completed". + +**MCData client:** An instance of an MC service client that provides the client application function for the MCData service. + +**MCData group:** An MC service group configured for MCData service. + +**MCData group affiliation:** An MC service group affiliation for MCData. + +**MCData group communication:** A one-to-many communication using an MCData service. + +**MCData group de-affiliation:** An MC service group de-affiliation for MCData. + +**MCData ID:** An instance of an MC service ID within the MCData service. + +**MCData server:** An instance of an MC service server that provides the server application function for the MCData service. + +**MCData service:** A data communication service comprising at least one underlying generic capability (e.g. SDS, file distribution, data streaming) with strong security, high availability, reliability and priority handling to support applications for mission critical organizations and mission critical applications for other businesses and organizations (e.g. utilities, railways). + +**MCData UE:** An MC service UE that can be used to participate in MCData services. + +**MCData user:** An MC service user who is authorized for MCData services suite via an MCData UE. + +**Reception control:** A mechanism that allows the MCData service to regulate data reception to the receiving MCData clients. + +**Reply identifier:** A reference to the original MCData transaction to which the current transaction is a reply. + +**SDS data:** A payload with limited size and variable content type used in SDS transactions. + +**SDS disposition:** is one of "undelivered", "delivered" and "read". + +**Standalone communication:** A unidirectional one-to-one or group data communication completed after one transaction. + +**Transaction identifier:** A unique identifier that identifies a MCData transaction within a conversation. + +**Transmission control:** A mechanism that allows the MCData service to regulate data transmission requests from the sending MCData users, either prior to or after active sending from the MCData UE. + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.280 [2] apply: + +**Mission Critical** + +**Mission Critical Applications** + +**Mission Critical Service** + +**Mission Critical Organization** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.282 [3] apply: + +**MCData system** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.280 [5] apply: + +**MC service client** + +**MC service group** + +**MC service group affiliation** + +**MC service group de-affiliation** + +**MC service ID** + +**MC service server** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.203 [14] apply: + +**Dynamic PCC rule** + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-----------|--------------------------------------| +| DS | Data Streaming | +| E2EE | End to End Encryption | +| FD | File Distribution | +| ITSI | Individual TETRA Subscriber Identity | +| LMR | Land Mobile Radio | +| MC | Mission Critical | +| MCData ID | MCData user identity | +| PCC | Policy and Charging Control | +| PCRF | Policy and Charging Rules Function | +| QCI | QoS Class Identifier | +| RSI | Radio Set Identity | +| SDS | Short Data Service | +| UM | Unacknowledged Mode | + +## 4 Introduction + +The MCData service suite provides a set of generic capabilities and specific services to enable one-to-one and group data communications between MCData users. + +The MCData architecture utilises the common functional architecture to support mission critical services over **LTE** defined in 3GPP TS 23.280 [5] and aspects of the IMS architecture defined in 3GPP TS 23.228 [6], the Proximity-based Services (**ProSe**) architecture defined in 3GPP **TS 23.303** [7], the Group Communication System Enablers for **LTE (GCSE\_LTE)** architecture defined in 3GPP **TS 23.468** [8], the Security of the Mission Critical Service in 3GPP TS 33.180 [13] and the PS-PS access transfer procedures defined in 3GPP TS 23.237 [9] to enable support of the MCData service. + +The MCData UE primarily obtains access to the MCData service via **E-UTRAN**, using the **EPS** architecture defined in 3GPP **TS 23.401** [4]. Certain application functions of MCData service can be accessed using MCData UEs via non-3GPP access networks. + +The MCData system provides the function to support interworking with LMR systems defined in 3GPP TS 23.283 [18]. + +## 5 Architectural requirements + +### 5.1 Transmission control + +The MCData service supports the ability to transmit SDS messages automatically towards the selected recipient user (private communication) or affiliated members of the selected MCData group. The MCData server may still reject the sent message (e.g. if there is no authority to send). + +For MCData types other than SDS, the MCData service invokes a transmission request grant approach before data is permitted to be transmitted. The MCData service provides a configurable limit for the maximum amount of data for FD or time for streamed data that an MCData user can transmit in a single request, which may be configured by the MCData administrator. + +**Editor's note: Additional criteria such as frequency of transmission, category/type of data, etc., for transmission control arbitration is FFS.** + +For congestion control, related to transmission requests, the MCData service may perform the following: + +- reject the data transmission requests and then shall notify the MCData user of the rejection; +- queue the data transmission requests; or +- at any time, withhold the permission to transmit data automatically. + +The MCData service shall notify the transmitting MCData group member if there are no other MCData group members affiliated to the MCData group. + +### 5.2 Reception control + +The MCData service shall support the ability to receive small amounts of data automatically. The MCData service may store data waiting for delivery in a temporary store, and notify availability to the receiving MCData users. The data which is temporarily stored may be configured with "time to live" value, and subsequently, the data may be purged from the temporary store upon expiry of "time to live". + +The recipient individual user (private communication) or affiliated members of the MCData group(s) shall be notified of the list of available data either on request or periodically. + +The MCData service shall provide a mechanism for the MCData user to select data to be downloaded from the list corresponding to the temporary store, subject to limitations such as expiry time and size. + +The MCData service shall support the ability to automatically deliver files with a size less than a configured threshold value (i.e. auto-receive). The data size for auto-receive shall be configured by the MCData administrator. + +## 5.3 Short Data Service capability + +The MCData service shall support SDS capability for one-to-one and group communications. + +The SDS capability shall support messages with a maximum payload of at least 1000 bytes. The supported message types shall include text, binary, or hyperlinks. Multiple message types may be interleaved within in a single message payload. The payload shall support inclusion of location information of the sending MCData user, with or without user or application provided data. + +The MCData service shall support messages to be sent over the signalling plane or the media plane. + +The SDS capability shall allow for multiple related messages to be correlated and sequenced within the MCData service. + +The MCData user shall be able to selectively request read and delivery receipt indication for the sent messages. The message delivery history information should be made available to an authorized MCData user. + +## 5.4 File distribution capability + +The MCData service shall support distribution of files for one-to-one and group communications. + +The MCData service shall allow the MCData user to send a file or a URL of a file to another MCData user. The source of the file can originate either from an MCData client or from a network functional entity. The generated URL shall be a reference to a stored file to allow for subsequent retrieval. The file storage policy may determine the availability of the file to be retrieved, and is subject to expiry time and size limitations. + +When the file delivery request is set by the sending user to mandatory download, the MCData service shall proceed to deliver the file to the recipient when possible. The file distribution mechanisms shall support both unicast and broadcast delivery methods. + +**Editor's note:** Requirements for automatic re-try mechanisms and maximum retry count is FFS. + +The MCData service shall support aggregation of download completion and disposition notification reports when files are distributed to multiple recipients. + +**NOTE:** Requirements for repairing the lost data from MBMS transmission for file distribution are not addressed in the present document. + +## 5.5 Data streaming capability + +The MCData service shall support data streaming capability for one-to-one and group communications. + +The MCData service shall allow the MCData user to send a data stream or a URL of a data stream to another MCData user. The source of the data stream can originate either from an MCData client or from a network functional entity. For a data stream originating at a network functional entity, the data stream may be provided by an MCData user. The data streaming mechanisms shall support both unicast and broadcast delivery methods. + +**Editor's note:** The minimum bitrate support for data streaming is FFS. + +When the data streaming request is set to automatic reception, the MCData service shall not require consent from the receiving MCData user. + +The MCData user shall be able to apply controls (i.e. start, stop, cancel) to the streams, and on a per recipient basis. + +**Editor's note:** The applicability of pause and resume controls to one-to-one communication is FFS + +The stream shall be terminated through an explicit user control (i.e. stop, cancel operation) or by reaching the end of the streamed content. + +## 5.6 MCData group affiliation and MCData group de-affiliation + +MCData groups may be configured with one or more MCData sub-services (e.g. SDS, FD, DS) as specified within the MCData service. When an MCData user affiliates to an MCData group, the MCData user is affiliated to each of those + +MCData sub-services configured in the MCData group. The list of MCData sub-services configured for an MCData group shall be included in the MCData group configuration data. + +MCData group affiliation shall be as specified in clause 5.2.5 of 3GPP TS 23.280 [5]. In addition, the following requirements shall be fulfilled by the MCData service for MCData users affiliated to MCData groups: + +- MCData users receive notifications for participating in MCData sub-services and invitations for their affiliated MCData group(s). +- MCData users select an affiliated MCData group to initiate a new message, file distribution, data stream, etc. +- MCData users receive messages, files, data streams, enhanced status updates, etc, from their affiliated MCData group(s). + +## 5.7 Conversation management + +The conversation management: + +1. shall include a service indication for conversation management in each SDS and FD transaction. +2. may be comprised of SDS transactions or FD transactions or a combination of both. +3. shall include a conversation identifier in each SDS and FD transaction. +4. shall treat conversation between different set of users (either in one-to-one or group) as a separate conversation. +5. shall treat conversation between the same set of users (either in one-to-one or group), but with a different conversation identifier as a separate conversation. + +## 5.8 Bearer management + +### 5.8.1 General + +The MCData UE shall use the **APN**s as defined in subclause 5.2.7.0 and table A.6-1 of 3GPP TS 23.280 [5]. The MCData UE shall use the MC services **APN** as defined in subclause 5.2.7.0 and table A.6-1 of 3GPP TS 23.280 [5] for the SIP-1 reference point. + +### 5.8.2 **EPS** bearer considerations + +The **EPS** bearer considerations specified in subclause 5.2.7.2 of 3GPP TS 23.280 [5] shall apply. + +### 5.8.3 **EPS** unicast bearer considerations for MCData + +For an MCData session request, resources shall be requested utilising interaction with dynamic PCC. The MCData system shall request resources over Rx to a PCRF. The dedicated bearer for MCData media shall utilise the **QCI** value of 70 (as specified in 3GPP **TS 23.203** [14]). The request of resources over Rx shall include an application identifier for MCData in order for the PCRF to evaluate the correct **QCI**. + +The UE is required to support at minimum one UM bearer, which is used for MCData (see annex A in 3GPP **TS 36.331** [15]). + +### 5.8.4 **MBMS** bearer management + +The **MBMS** bearer management for MC services is specified in subclause 5.2.7.1 of 3GPP TS 23.280 [5]. + +## 5.9 Disposition + +Disposition requests and notifications can be sent "in-band" using the same mechanism used for transport of the data, or can be sent "out-of-band" when the mechanism used for transport of the data is no longer available. + +For standalone SDS and FD, the MCData UE shall use the signalling plane for disposition request and disposition notifications. For session SDS, the MCData UE shall use: + +- the media plane for disposition request and disposition notifications; and + +- the signalling plane for disposition notifications when the media plane is no longer available. + +--- + +## 5A Involved business relationships + +The description of the involved business relationships for the MCData service is contained in clause 6 of 3GPP TS 23.280 [5]. + +--- + +## 6 Functional model + +### 6.1 General + +This clause defines the functional model for MCData service. + +The security solution for the MCData service, including end-to-end encryption, is specified in 3GPP TS 33.180 [13]. + +### 6.2 Description of the planes + +The functional model for the support of MCData is defined as a series of planes to allow for the breakdown of the architectural description. + +The description of the planes and the relationship between the planes are contained in the common functional architecture to support MC services in 3GPP TS 23.280 [5]. + +### 6.3 Transmission and reception control aspects + +#### 6.3.1 General + +The transmission and reception control are functions of the MCData server. + +For small data transmissions there is no need for prior grant of request to transmit. The procedures in the present document describe when data is automatically sent. + +For large data transmissions, i.e. large files, the data is transmitted only after request to transmit is granted. The data to be transmitted and/or received may be stored in a data repository associated with the transmission and reception control functions. + +NOTE: An overview of transmission control process and possible arbitration mechanisms is provided in the Annex B. + +### 6.4 Generic functional model + +#### 6.4.1 On-network functional model + +Figure 6.4.1-1 shows the generic application plane functional model. + +![Figure 6.4.1-1: Generic application plane functional model. This block diagram shows the functional architecture of the MCData application plane. On the left, three external entities are connected to a central 'MCData server': 'Other MCData server' via 'MCData-3', 'MCData user database' via 'MCData-2', and 'Interworking function to LMR system' via 'IWF-2'. The 'MCData server' contains a 'Capability functions (SDS, FD, DS)' block. This block connects to an 'MCData UE' on the right via several reference points: 'MCData-cap-1', 'MCData-cap-n', 'MCData-5' (labeled 'Rx'), and 'MCData-6' (labeled 'MB2C'). The 'MCData server' also connects to an 'MCData message store' via 'MCData-8'. The 'MCData message store' connects to the 'MCData UE' via 'MCData-7'. The 'MCData UE' contains two internal blocks: 'MCData client' (with its own 'Capability functions (SDS, FD, DS)') and 'Message store client'. A vertical line labeled 'EPS' at the bottom separates the server-side components from the UE-side components.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Figure 6.4.1-1: Generic application plane functional model. This block diagram shows the functional architecture of the MCData application plane. On the left, three external entities are connected to a central 'MCData server': 'Other MCData server' via 'MCData-3', 'MCData user database' via 'MCData-2', and 'Interworking function to LMR system' via 'IWF-2'. The 'MCData server' contains a 'Capability functions (SDS, FD, DS)' block. This block connects to an 'MCData UE' on the right via several reference points: 'MCData-cap-1', 'MCData-cap-n', 'MCData-5' (labeled 'Rx'), and 'MCData-6' (labeled 'MB2C'). The 'MCData server' also connects to an 'MCData message store' via 'MCData-8'. The 'MCData message store' connects to the 'MCData UE' via 'MCData-7'. The 'MCData UE' contains two internal blocks: 'MCData client' (with its own 'Capability functions (SDS, FD, DS)') and 'Message store client'. A vertical line labeled 'EPS' at the bottom separates the server-side components from the UE-side components. + +**Figure 6.4.1-1: Generic application plane functional model** + +In the model shown in figure 6.4.1-1, capability functions (SDS, FD, DS) of the MCData client and the MCData server along with their reference points (MCData-cap-1 to MCData-cap-n) are described in the respective functional models for each capability. + +**Editor's note:** It is FFS if the "media storage function" and "MCData message store" could be converged into one in the architecture diagram use a set of reference points to support them. + +**NOTE:** The security aspects of new network components (MCData message store and Message store client) and its two new reference points are the responsibility of SA3 and thus outside the scope of the present document. + +## 6.4.2 Off-network functional model + +## 6.4.3 Functional entities description + +**Editor's note:** Combining functional models describing each capability into one functional model is FFS. + +### 6.4.3.1 Application plane + +#### 6.4.3.1.1 MCData client + +The MCData client functional entity acts as the user agent for all MCData application transactions. The client supports SDS, file distribution, data streaming and IP connectivity MCData capabilities utilized by MCData services like conversation management, robots control, enhanced status, database enquiries and secured internet. + +#### 6.4.3.1.2 MCData server + +The MCData server functional entity provides centralised support for MCData services suite. Conversation management, robots, enhanced status, database enquiries and secured internet MCData services requiring one-to-one or group data communication are realized using SDS, file distribution, data streaming and IP connectivity MCData communication capabilities. + +All the MCData clients supporting users belonging to a single group are required to use the same MCData server for that group. An MCData client supporting a user involved in multiple groups can have relationships with multiple MCData servers. + +The MCData server functional entity represents a specific instantiation of the GCS AS described in 3GPP **TS 23.468** [8] to control multicast and unicast operations for group communications. + +The MCData server functional entity is supported by the SIP AS functional entity of the signalling control plane. + +The MCData server shall support the controlling role and the participating role. The MCData server may perform the controlling role for one-to-one and group data communication. The MCData server performing the controlling role for a one-to-one or group data communication may also perform a participating role for the same one-to-one or group data + +communication. For each one-to-one and group data communication, there shall be only one MCData server assuming the controlling role, while one or more MCData servers in participating role may be involved. + +The MCData server performing the controlling role is responsible for: + +- handling transmission and reception control (e.g. policy enforcement for participation in the MCData group communication) towards all the MCData users of the one-to-one and group data communication; +- interfacing with the group management server for group policy and affiliation status information of this MCData server's served affiliated users; and +- managing SDS and FD data distribution during MCData group communication. + +The MCData server performing the participating role is responsible for: + +- handling transmission control (e.g. authorization for participation in the MCData group communication) to MCData users of the one-to-one and group data communication; +- group affiliation support for MCData user, including enforcement of maximum Nc2 number of simultaneous group affiliations by a user; +- interfacing with the group management server for group policy and affiliation status information of this MCData server's served affiliated users; +- relaying the MCData communication messages between the MCData client and the MCData server performing the controlling role; and +- handling reception control (e.g. temporarily storing the data to present to the MCData user as required) to its MCData users of the one-to-one and group data communication. + +NOTE: The MCData server in the controlling role and the MCData server in the participating role can belong to the same MCData system. + +#### 6.4.3.1.3 MCData user database + +This functional entity contains information of the MCData user profile associated with an MCData ID that is held by the MCData service provider at the application plane. The MCData user profile is determined by the mission critical organization, the MCData service provider, and potentially the MCData user. + +#### 6.4.3.1.4 Interworking function to LMR system + +The functional entity is specified in 3GPP TS 23.283 [18]. + +#### 6.4.3.2 Signalling control plane + +The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +#### 6.4.3.3 MCData message store + +The MCData message store is a network base persistent store that allows Mission Critical Organization to configure their MCData service users to permanently store their MCData communications. Once configured a MCData service user will be allocated a secured storage area (i.e. size) in the MCData message store that is only accessible by that configured MCData service user and any authorized users. The MCData service user can manage how and what will be stored in his personal message store with the support of management operations such as creating, deleting and merging folders, moving stored messages and files around and synchronization all used devices to provide the same context view etc. + +**Editor's note:** It is FFS if the MCData message store can also be used to store "group" and "organizational" specific information. + +NOTE: The security aspects of access and management (such as read/write/update/sync etc.) of personal message store are the responsibility of SA3 and thus outside the scope of the present document. + +### 6.4.3.4 Message store client + +The Message store client is used to support MCData client to manage the MCData communication history stored in MCData message store for a particular MCData service user. It supports the secure access to a MCData service user's configured MCData message store area and operations relevant to the stored communication history such as folders management and synchronization to the device local message store. + +## 6.4.4 Reference points + +### 6.4.4.1 Application plane + +#### 6.4.4.1.1 General + +The reference points for the application plane of MCData service are described in the following subclauses. + +#### 6.4.4.1.2 Reference point MCData-2 (between the MCData server and the MCData user database) + +The MCData-2 reference point, which exists between the MCData server and the MCData user database, is used by the MCData server to obtain information about a specific user. The MCData-2 reference point utilises a diameter management application protocol as defined in 3GPP TS 29.283 [12] and shall be intra-network. + +#### 6.4.4.1.3 Reference point MCData-3 (between the MCData server and the MCData server) + +The MCData-3 reference point, which exists between the MCData server and the MCData server for MCData application signalling for establishing MCData sessions, shall use the SIP-2 reference point for transport and routing of signalling. If each MCData server is served by a different SIP core then the MCData-3 reference point shall also use the SIP-3 reference point for transport and routing of signalling. Media is also transferred using the MCData-3 reference point. + +#### 6.4.4.1.3A Reference point MCData-5 (between the MCData capability function and the EPS) + +The MCData-5 reference point, which exists between the MCData capability function and the EPS, is used, subject to the conditions below, by the MCData capability function of the MCData server to obtain unicast bearers with appropriate QoS from the EPS. It utilises the Rx interface of the EPS according to 3GPP TS 23.203 [14]. + +MCData-5 is not used when the MCData service provider and the PLMN operator do not have an operational agreement for QoS control to be provided directly from the MCData service provider domain. + +MCData-5 may be used when the MCData service provider and the PLMN operator have an operational agreement where QoS control is provided directly from the MCData service provider domain. + +NOTE: Any coordination between the P-CSCF use of Rx and the MCData server use of Rx (via MCData-5) from the MCData service provider domain is not specified in this release of this specification. + +#### 6.4.4.1.4 Reference point MCData-6 (between the MCData server and the EPS) + +The MCData-6 reference point, which exists between the MCData server and the EPS, is used to request the allocation and activation of multicast transport resources for MCData application usage. The MCData-6 reference point uses the MB2-C interface as defined in 3GPP TS 29.468 [16]. + +#### 6.4.4.1.5 Reference point IWF-2 (between the interworking function to LMR system and the MCData server) + +The IWF-2 reference point is specified in 3GPP TS 23.283 [18]. + +#### 6.4.4.1.6 Reference point MCData-7 (between the Message store client and MCData message store) + +The MCData-7 reference point, which exists between the Message store client and the MCData message store, is used by the Message store client to manage the information stored in the MCData message store and synchronization between the MCData client and the MCData message store. + +#### 6.4.4.1.7 Reference point MCData-8 (between the MCData message store and McData server) + +The MCData-8 reference point, which exists between the MCData server and the MCData message store, is used by the MCData server to access and manage the MCData message store such as creating MCData user folders and depositing the communications history. + +## 6.5 Functional model for short data service + +### 6.5.1 On-network functional model + +Figure 6.5.1-1 shows the application plane functional model for SDS. + +![Figure 6.5.1-1: Application plane functional model for SDS. The diagram shows the functional components and reference points for the Short Data Service (SDS). On the left, the MCData server contains an SDS distribution function and a Transmission/Reception control. On the right, the MCData UE contains an MCData client with an SDS function and a Message store client. In the center is the MCData Message Store. Reference points are: MCData-SDS-1, MCData-SDS-2, and MCData-SDS-3 between the SDS distribution function and the SDS function; MCData-8 between the MCData server and the MCData Message Store; and MCData-7 between the MCData Message Store and the Message store client. All components are connected to a central EPS (Evolved Packet System) represented by a vertical line.](1a85642ed2356d183ce598f2c8b3ee8b_img.jpg) + +Figure 6.5.1-1: Application plane functional model for SDS. The diagram shows the functional components and reference points for the Short Data Service (SDS). On the left, the MCData server contains an SDS distribution function and a Transmission/Reception control. On the right, the MCData UE contains an MCData client with an SDS function and a Message store client. In the center is the MCData Message Store. Reference points are: MCData-SDS-1, MCData-SDS-2, and MCData-SDS-3 between the SDS distribution function and the SDS function; MCData-8 between the MCData server and the MCData Message Store; and MCData-7 between the MCData Message Store and the Message store client. All components are connected to a central EPS (Evolved Packet System) represented by a vertical line. + +**Figure 6.5.1-1: Application plane functional model for SDS** + +In the model shown in figure 6.5.1-1, the following apply: + +- MCData-SDS-1 reference point is used for uplink and downlink unicast SDS data transaction over signalling control plane by the SDS distribution function of the MCData server and SDS function of the MCData client. This reference point is also used for MCData application signalling during session establishment in support of SDS data transfer. +- MCData-SDS-2 reference point carries uplink and downlink unicast SDS data over media plane between the SDS distribution function of the MCData server and the SDS function of the MCData client. +- MCData-SDS-3 reference point carries downlink multicast SDS data over media plane from the SDS distribution function of the MCData server to the SDS function of the MCData client. + +Examples of SDS data (in the form of text, binary, application data, URL or combinations of these) are: + +- information pertaining to applications e.g. health parameters of MCData user for situational awareness application; +- information pertaining to enhanced status service; +- text or URL data between MCData users; +- application data (e.g. health parameters) to the MCData user; +- location information (independent or along with user or application provided data); +- command instructions to invoke certain operations on the MCData UE e.g. invoking UE specific applications; and +- application plane identities for the MCData user and MCData application. + +## 6.5.2 Off-network functional model + +Figure 6.5.2-1 shows the off-network application plane functional model for SDS. + +![Figure 6.5.2-1: Application plane functional model for SDS. The diagram shows two User Equipment (UE) blocks, UE 1 and UE 2, connected by two horizontal lines labeled 'Media' (green) and 'Signalling' (red). Each UE block contains a top section with 'SDS function' and 'MCData client', a middle section with 'Configuration management client', 'Group management client', and 'Common services core' (all within a dashed box labeled 'Application plane'), and a bottom section with 'Signalling user agent' (within a box labeled 'Signalling control plane').](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg) + +Figure 6.5.2-1: Application plane functional model for SDS. The diagram shows two User Equipment (UE) blocks, UE 1 and UE 2, connected by two horizontal lines labeled 'Media' (green) and 'Signalling' (red). Each UE block contains a top section with 'SDS function' and 'MCData client', a middle section with 'Configuration management client', 'Group management client', and 'Common services core' (all within a dashed box labeled 'Application plane'), and a bottom section with 'Signalling user agent' (within a box labeled 'Signalling control plane'). + +**Figure 6.5.2-1: Application plane functional model for SDS** + +## 6.5.3 Functional entities description + +### 6.5.3.1 Application plane + +#### 6.5.3.1.1 SDS function + +SDS function of the MCData client is responsible to handle SDS capability related requests and responses. + +#### 6.5.3.1.2 SDS distribution function + +The SDS distribution function of the MCData server is responsible for the SDS data transaction to MCData communication participants. The SDS distribution function of the MCData server provides the following functionality: + +- reception of uplink SDS data transaction by means of the MCData-SDS-1 and MCData-SDS-2 reference points; +- replicate the SDS data as needed for distribution to those MCData communication participants using unicast transport; +- distribute downlink data by IP unicast transmission to those MCData communication participants utilizing unicast transport by means of the MCData-SDS-1 and MCData-SDS-2 reference points; and +- distribute downlink SDS data using multicast downlink transport by means of the MCData-SDS-3 reference point. + +#### 6.5.3.1.3 Transmission/Reception control + +This functional entity is responsible for transmission and reception control of MCData SDS data transaction between the sending MCData UE, the MCData server, and the receiving MCData UE. For SDS capability, due to small data size, the SDS messages can be automatically sent. + +### 6.5.3.2 Signalling control plane + +The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +## 6.5.4 Reference points + +### 6.5.4.1 Application plane + +#### 6.5.4.1.1 Reference point MCData-SDS-1 (between the SDS distribution function and the SDS function) + +MCData-SDS-1 reference point is used for uplink and downlink unicast SDS data transaction over signalling control plane by the SDS distribution function of the MCData server and SDS function of the MCData client. This reference point is also used for MCData application signalling during session establishment in support of SDS data transfer. + +The MCData-SDS-1 reference point shall use the SIP-1 and SIP-2 reference points for transport and routing of SIP signalling. MCData-SDS-1 reference point can be used when the SDS payload data size does not exceed the configured maximum payload data size for SDS over signalling control plane, otherwise MCData-SDS-2 and MCData-SDS-3 may be used appropriately. + +Reference point MCData-SDS-1 also provides support to delivered and read requests and notifications as appropriate. + +#### 6.5.4.1.2 Reference point MCData-SDS-2 (unicast between the SDS distribution function and the SDS function) + +The MCData-SDS-2 reference point, which exists between the SDS distribution function and the SDS function of the MCData client, is used unicast SDS data transaction (when the SDS payload data size exceeds the configured maximum payload data size for SDS over signalling control plane) between the MCData server and the MCData client. The MCData-SDS-2 reference point uses the SGi reference point defined in 3GPP TS 23.002 [10]. + +Reference point MCData-SDS-2 also provides support to message thread indication using conversation identifier, delivered and read notifications as appropriate. + +#### 6.5.4.1.3 Reference point MCData-SDS-3 (multicast between the SDS distribution function and the SDS function) + +The MCData-SDS-3 reference point, which exists between the SDS distribution function of the MCData server and the SDS function of the MCData client, is used by the SDS distribution function of the MCData server to send downlink multicast SDS data to the SDS function of the MCData client. The MCData-SDS-3 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [8]. + +### 6.5.4.2 Signalling control plane + +The description of the signalling control plane reference points is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +## 6.6 Functional model for file distribution + +### 6.6.1 On-network functional model + +Figure 6.6.1-1 shows the application plane functional model for file distribution. + +![Figure 6.6.1-1: Application plane functional model for file distribution. The diagram shows the functional architecture for file distribution between an MCData server and an MCData UE. The MCData server contains an FD function, a Transmission/Reception control, and an MCData content server (which includes a Media storage function). The MCData UE contains an MCData client with an FD function, a Media Storage client, and a Message store client. Reference points are defined as follows: MCData-FD-1, MCData-FD-2, and MCData-FD-3 connect the FD functions of the server and UE; MCData-FD-4 connects the Media storage function in the content server to the Media Storage client in the UE; MCData-FD-5 connects the FD function in the server to the Media storage function in the content server; MCData-8 connects the Transmission/Reception control in the server to the MCData message store; and MCData-7 connects the MCData message store to the Message store client in the UE. A central vertical bar labeled EPS represents the network interface.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Figure 6.6.1-1: Application plane functional model for file distribution. The diagram shows the functional architecture for file distribution between an MCData server and an MCData UE. The MCData server contains an FD function, a Transmission/Reception control, and an MCData content server (which includes a Media storage function). The MCData UE contains an MCData client with an FD function, a Media Storage client, and a Message store client. Reference points are defined as follows: MCData-FD-1, MCData-FD-2, and MCData-FD-3 connect the FD functions of the server and UE; MCData-FD-4 connects the Media storage function in the content server to the Media Storage client in the UE; MCData-FD-5 connects the FD function in the server to the Media storage function in the content server; MCData-8 connects the Transmission/Reception control in the server to the MCData message store; and MCData-7 connects the MCData message store to the Message store client in the UE. A central vertical bar labeled EPS represents the network interface. + +**Figure 6.6.1-1: Application plane functional model for file distribution** + +In the model shown in figure 6.6.1-1, the following apply: + +- MCData-FD-1 reference point is used for MCData application signalling for establishing a session in support of MCData file distribution. The bearer is also used for both uplink and downlink unicast data (e.g., URL associated to file, file download completed report). +- MCData-FD-2 reference point carries uplink and downlink unicast file data between the FD functions of the MCData server and the MCData UE. +- MCData-FD-3 reference point carries downlink multicast file data from the FD function of the MCData server to the FD function of the MCData UE. +- MCData-FD-4 reference point carries uplink and downlink unicast file data between the media storage function of the MCData Content server and the media storage client of the MCData UE. +- MCData-FD-5 reference point supports the MCData server to access the stored files in the MCData content server for certain file distribution functions, such as retrieval a file to be distributed through multicast etc. This reference points also supports any necessary operational requirements. + +NOTE: The security aspects of MCData-FD-5 reference point are the responsibility of SA3 and thus outside the scope of the present document. + +**Editor's note:** It is FFS on what the operational requirements (such as QoS control of file upload and download) are needed to be supported by this reference point. + +**Editor's note:** It is FFS if the name of "MCData-FD-5" reference point should be renamed to use a different number (such as MCData-FD-9) to avoid conflicting with the existing MCData base reference points (MCData-1, MCData-2 ...) in numbering. + +- MCData content server is a repository area in the MCData trust domain that allows authorized MCData service user to temporarily store files that are intended to share to other MCData service users. It provides common pool of storage area (i.e. size) to all authorized MCData service users to use, no personal space is allocated. An authorized MCData service user can use the supported operations on the defined reference point to upload shared files and download the files that are shared to him. The MCData server will use the defined reference point to + +access the files stored in the MCData content server and support the necessary operational supports. As part of the file life cycle management the temporarily stored files will be removed periodically based on the Mission Critical service provider policy. + +NOTE: The security aspects of MCData content server and its operational supports are the responsibility of SA3 and thus outside the scope of the present document. + +## 6.6.2 Off-network functional model + +Figure 6.6.2-1 shows the off-network application plane functional model for FD. + +![Figure 6.6.2-1: Application plane functional model for FD. The diagram shows two User Equipment (UE) blocks, UE 1 and UE 2, connected by two horizontal lines labeled 'Media' (green) and 'Signalling' (red). Each UE contains a nested structure: an outer box for the UE, an inner box for the 'Application plane', and a bottom box for the 'Signalling control plane'. The 'Application plane' contains an 'FD function' and 'MCData client' at the top, and a dashed box containing 'Configuration management client', 'Group management client', and 'Common services core' below. The 'Signalling control plane' contains a 'Signalling user agent'.](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +Figure 6.6.2-1: Application plane functional model for FD. The diagram shows two User Equipment (UE) blocks, UE 1 and UE 2, connected by two horizontal lines labeled 'Media' (green) and 'Signalling' (red). Each UE contains a nested structure: an outer box for the UE, an inner box for the 'Application plane', and a bottom box for the 'Signalling control plane'. The 'Application plane' contains an 'FD function' and 'MCData client' at the top, and a dashed box containing 'Configuration management client', 'Group management client', and 'Common services core' below. The 'Signalling control plane' contains a 'Signalling user agent'. + +**Figure 6.6.2-1: Application plane functional model for FD** + +## 6.6.3 Functional entities description + +### 6.6.3.1 Application plane + +#### 6.6.3.1.1 FD function + +FD function of the MCData client and the MCData server is responsible to handle file distribution capability related requests and responses. + +The FD function of the MCData server is responsible for the distribution of file to the MCData communication participants. The FD function of the MCData server provides the following functionality: + +- reception of uplink file data by means of the MCData-FD-2 reference point; +- replicate the file data as needed for distribution to those MCData communication participants using unicast transport; +- distribute downlink file data by IP unicast transmission to those MCData communication participants utilizing unicast transport by means of the MCData-FD-2 reference point; and +- distribute downlink file data using multicast downlink transport by means of the MCData-FD-3 reference point. + +#### 6.6.3.1.2 Media storage client + +The media storage client is used to support FD function of the MCData client for file distribution capability. FD function of the MCData client interacts with media storage client for uploading and downloading file to or from the media storage function of the MCData content server. + +### 6.6.3.1.3 Transmission/Reception control + +This functional entity is responsible for transmission and reception control of MCData file data between the sending MCData UE, the MCData server, and the receiving MCData UE. Transmission and reception control function is used to provide arbitration between multiple data requests and apply the necessary policy to ensure that appropriate data is transmitted between the MCData UE. However, when the file distribution requests are exceeding a certain size, it may be necessary to control the data that is transmitted or received by the MCData UEs. The control is subject to criteria like application level priorities (e.g. user priority, group priority), service type, emergency nature of the communication, etc. + +### 6.6.3.1.4 Media storage function + +The media storage function is responsible for the storing of media uploaded by the media storage client of the MCData UE in case of MCData file distribution. It also supports download of stored media by the MCData UE in case of file distribution via media storage client. + +### 6.6.3.2 Signalling control plane + +The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +## 6.6.4 Reference points + +### 6.6.4.1 Application plane + +#### 6.6.4.1.1 Reference point MCData-FD-1 (between the FD functions of the MCData client and the MCData server) + +MCData-FD-1 reference point is used for MCData application signalling for establishing a session in support of MCData file distribution. The bearer is also used for both uplink and downlink unicast data (e.g., URL associated to file, file download completed report). The MCData-FD-1 reference point shall use the SIP-1 and SIP-2 reference points for transport and routing of SIP signalling. MCData-FD-1 reference point can be used as long as the file size does not exceed the capabilities (e.g. payload or transmission limits) provided by MCData-FD-1. + +Messages supported on this interface include the uplink and the downlink unicast file transaction between the MCData clients in MCData communication via the MCData server for: + +- metadata (file size, type etc.) of the file being distributed; +- URL of the file being distributed; +- sending download completed report; +- small size file; +- conversation identifier for message thread indication; and +- application plane identities for the MCData user and MCData application. + +Messages supported on this interface may also include the MCData client providing the MCData server with + +- MCData application signalling for establishing a file distribution session in support of MCData communication. + +#### 6.6.4.1.2 Reference point MCData-FD-2 (unicast between the FD functions of the MCData client and the MCData server) + +The MCData-FD-2 reference point, which exists between the FD functions of the MCData client and the MCData server, is used for unicast file transaction between MCData server and MCData client. The MCData-FD-2 reference point uses the SGi reference point defined in 3GPP TS 23.002 [10]. + +Reference point MCData-FD-2 supports the following functions: + +- file being distributed from and to the MCData client; +- conversation identifier for message thread indication; and + +- application plane identities for the MCData user and MCData application. + +#### 6.6.4.1.3 Reference point MCData-FD-3 (multicast between the FD functions of the MCData client and the MCData server) + +The MCData-FD-3 reference point, which exists between the FD functions of the MCData client and the MCData server, is used by the FD function of the MCData server to send downlink multicast file data to the FD function of the MCData client. The MCData-FD-3 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [8]. + +#### 6.6.4.1.4 Reference point MCData-FD-4 (media storage function and media storage client) + +The MCData-FD-4 reference point, which exists between the media storage function and the media storage client, is used by the media storage client of MCData UE to upload and download file to the media storage function of the MCData content server. The MCData-FD-4 reference point uses the HTTP reference point. + +#### 6.6.4.1.5 Reference point MCData-FD-5 (FD function and media storage function) + +The MCData-FD-5 reference point, which exists between FD function and the media storage function, is used by the FD function of MCData server to fetch the file in the MCData content server that was uploaded by the media storage client of a MCData UE for multicast delivery using MBMS. It also supports necessary operational functions such as size check for transmission control etc. The MCData-FD-5 reference point uses the HTTP reference point. + +#### 6.6.4.2 Signalling control plane + +The description of the signalling control plane reference points is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +### 6.7 Functional model for data streaming + +#### 6.7.1 On-network functional model + +Figure 6.7.1-1 shows the application plane functional model for data streaming. + +![Figure 6.7.1-1: Application plane functional model for data streaming. The diagram shows the functional architecture for data streaming between an MCData server and an MCData UE. The MCData server contains a 'Data streaming and distribution function' and a 'Transmission / Reception control' function. The MCData UE contains an 'MCData client' with a 'DS function' and a 'Message store client'. A central 'MCData Message store' is also shown. Reference points are labeled: MCData-DS-1, MCData-DS-2, MCData-DS-3, MCData-8, and MCData-7. The EPS (Evolved Packet System) is indicated at the bottom.](62e0e858742d9a9ea4cfdc52e448e8bb_img.jpg) + +``` + +graph LR + subgraph MCData_server [MCData server] + DSF[Data streaming and distribution function] + TRC[Transmission / Reception control] + end + subgraph MCData_UE [MCData UE] + MCData_client[MCData client] + subgraph MCData_client + DSF_UE[DS function] + MSC[Message store client] + end + end + MS[MCData Message store] + EPS((EPS)) + + DSF --- MCData-DS-1 --- DSF_UE + DSF --- MCData-DS-2 --- DSF_UE + DSF --- MCData-DS-3 --- DSF_UE + TRC --- MCData-8 --- MS + MS --- MCData-7 --- MSC + EPS + +``` + +Figure 6.7.1-1: Application plane functional model for data streaming. The diagram shows the functional architecture for data streaming between an MCData server and an MCData UE. The MCData server contains a 'Data streaming and distribution function' and a 'Transmission / Reception control' function. The MCData UE contains an 'MCData client' with a 'DS function' and a 'Message store client'. A central 'MCData Message store' is also shown. Reference points are labeled: MCData-DS-1, MCData-DS-2, MCData-DS-3, MCData-8, and MCData-7. The EPS (Evolved Packet System) is indicated at the bottom. + +**Figure 6.7.1-1: Application plane functional model for data streaming** + +In the model shown in figure 6.7.1-1, the following apply: + +- MCData-DS-1 reference point is used for MCData application signalling for establishing a session in support of MCData data streaming. The bearer is also used for both uplink and downlink unicast stream download reports (e.g. stream start and stop records). +- MCData-DS-2 reference point carries unicast data stream between the data streaming and distribution function of the MCData server and the DS function of the MCData UE. The bearer is used for both uplink and downlink unicast data streaming. + +- MCData-DS-3 reference point carries multicast data stream from the data streaming and distribution function of the MCData server to the DS function of the MCData UE. The bearer is used for downlink multicast data streaming. + +## 6.7.2 Off-network functional model + +## 6.7.3 Functional entities description + +### 6.7.3.1 Application plane + +#### 6.7.3.1.1 DS function + +DS function of the MCData client is responsible to handle DS capability related requests and responses for data streaming. FD function may interact with storage entity for retrieving the locally stored data for data streaming. + +#### 6.7.3.1.2 Data streaming and distribution function + +The data streaming and distribution function is responsible for the distribution of data stream to MCData communication participants. The data streaming and distribution function provides the following functionality: + +- reception of uplink data stream transmission by means of the MCData-DS-2 reference point; +- replicate the data stream as needed for distribution to those MCData communication participants using unicast transport; +- distribute downlink data stream by IP unicast transmission to those MCData communication participants utilizing unicast transport by means of MCData-DS-2 reference point; and +- distribute downlink data stream using multicast downlink transport by means of the MCData-DS-3 reference point. + +#### 6.7.3.1.3 Transmission/Reception control + +This functional entity is responsible for transmission and reception control of data stream between the sending MCData UE, the MCData server, and the receiving MCData UE. Transmission and reception control function is used to provide arbitration between multiple data requests and apply the necessary policy to ensure that appropriate data is transmitted between the MCData UEs. + +### 6.7.3.2 Signalling control plane + +The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +## 6.7.4 Reference points + +### 6.7.4.1 Application plane + +#### 6.7.4.1.1 Reference point MCData-DS-1 (between the data streaming and distribution function and the DS function) + +MCData-DS-1 reference point is used for MCData application signalling for establishing a session in support of MCData data streaming. The bearer is also used for both uplink and downlink unicast stream download reports (e.g., stream start and stop records). The MCData-DS-1 reference point shall use the SIP-1 and SIP-2 reference points for transport and routing of SIP signalling. + +Messages supported on this interface includes the uplink and the downlink unicast data stream between the MCData clients MCData communication via the MCData server for + +- metadata of the data being streamed; +- URL of the data being streamed; +- sending stream download report; +- conversation identifier for message thread indication; and + +- application plane identities for the MCData user and MCData application. + +Messages supported on this interface may also include the MCData client providing the MCData server with + +- MCData application signalling for establishing a UE data streaming session in support of MCData communication. + +#### 6.7.4.1.2 Reference point MCData-DS-2 (unicast between the data streaming and distribution function and the DS function) + +The MCData-DS-2 reference point, which exists between the data streaming and distribution function and the DS function, is used to unicast data stream between the data streaming and distribution function of the MCData server and the DS function of the MCData client. The MCData-DS-2 reference point uses the SGi reference point defined in 3GPP TS 23.002 [10]. + +MCData-DS-2 supports the following functions: + +- stream data from MCData UE; +- stream data from network; +- data stream controls from the authorized MCData UE; +- stream data stream controls from the MCData UE over uplink; +- start and stop data stream from MCData UE over downlink; +- conversation identifier for message thread indication; and +- application plane identities for the MCData user and MCData application. + +#### 6.7.4.1.3 Reference point MCData-DS-3 (multicast between the data streaming and distribution function and the DS function) + +The MCData-DS-3 reference point, which exists between the data streaming and distribution function and the DS function, is used by the data streaming and distribution function of the MCData server to send multicast data stream to the DS function of the MCData client. The MCData-DS-3 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [8]. + +#### 6.7.4.2 Signalling control plane + +The description of the signalling control plane reference points is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +--- + +## 6A Identities + +The MCData service specific identities (e.g. MCData ID, MCData group ID) are described in clause 8 of 3GPP TS 23.280 [5]. + +--- + +## 6B Application of functional model to deployments + +The application of the functional model to deployments, and description of various deployment scenarios for the MCData service, can be found in clause 9 of 3GPP TS 23.280 [5]. + +--- + +## 7 Procedures and information flows + +### 7.1 MCData service configuration + +The MCData service shall support the procedures and related information flows as specified in subclause 10.1 and Annex A of 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; +- The MC service ID is the MCData ID; and +- The MC service user profile index is the MCData user profile index. + +## 7.2 Affiliation and de-affiliation to/from MCData group(s) + +The MCData service shall support the procedures and related information flows as specified in subclause 10.8 of 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; +- The MC service group is the MCData group; +- The MC service ID is the MCData ID; and +- The MC service group ID is the MCData group ID. + +When an MCData user has affiliated to an MCData group then the MCData user can send and receive MCData related media for that MCData group. When an MCData user has de affiliated from an MCData group then the MCData user cannot send and receive MCData related media to and from that MCData group. + +## 7.3 Use of MBMS transmission (on-network) + +### 7.3.1 Information flows for MBMS Transmission + +Information flows for generic MBMS procedures are defined in 3GPP TS 23.280 [5]. + +### 7.3.2 Use of pre-established MBMS bearers + +The MCData service shall support the procedure for using pre-established MBMS bearers as specified in 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; and +- The MC service ID is the MCData ID. + +The MCData service shall use the MCData-6, MCData-SDS-1, MCData-SDS-2, MCData-SDS-3, MCData-FD-1, MCData-FD-3, MCData-DS-1 and MCData-DS-3 reference points for this procedure. + +MCData may use pre-established MBMS bearer for the MCData features short data service, file distribution and data streaming. The MBMS bearer can be used by any group. Depending on the capacity of the MBMS bearer, the bearer can be used to broadcast one or more services in parallel. + +Both the media packets as well as the transmission control messages to the receiving users may be sent on the MBMS bearer. Optionally a separate MBMS bearer could be used for the transmission control messages, due to different bearer characteristic requirements. + +### 7.3.3 Use of dynamic MBMS bearer establishment + +The MCData service shall support the procedure for using pre-established MBMS bearers as specified 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; and +- The MC service ID is the MCData ID. + +The MCData service shall use the MCData-6, MCData-DS-1 and MCData-DS-3 reference points for this procedure. + +MCData may use dynamic **MBMS** bearer for the MCData feature data streaming. The **MBMS** bearer can be used by any group. Depending on the capacity of the **MBMS** bearer, the bearer can be used to broadcast one or more services in parallel. + +For file distribution the use of dynamic **MBMS** bearer is not supported. + +Both the media packets as well as the transmission control messages to the receiving users may be sent on the **MBMS** bearer. Optionally a separate **MBMS** bearer could be used for the transmission control messages, due to different bearer characteristic requirements. + +### 7.3.4 Switching from **MBMS** bearer to unicast bearer + +The MCData service shall support the procedure for switching from **MBMS** bearer to unicast bearer as specified 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; and +- The MC service ID is the MCData ID. + +The MCData service shall use the MCData-SDS-1, MCData-SDS-2, MCData-FD-1, MCData-FD-3, MCData-DS-1 and MCData-DS-3 reference points for this procedure. + +## 7.4 Short data service + +### 7.4.1 General + +There are several procedures how an SDS message can be transported from the sender to the recipient. All of the following factors are used by MCData client for selecting appropriate SDS procedures: + +- Whether the data to transfer is within or outside the SDS data size limit to transport over signalling control plane; +- Whether the MCData user has only one SDS transaction or multiple SDS transactions; +- Whether MCData user is targeting SDS transaction to another MCData user or MCData group; +- Whether MCData UE is on-network or off-network; and +- Security reasons. + +### 7.4.2 Short data service for on-network + +The procedures described in the following subclauses are limited to single MCData system only. + +#### 7.4.2.1 Information flows for short data service + +##### 7.4.2.1.1 MCData standalone data request + +Table 7.4.2.1.1-1 describes the information flow for the MCData standalone data request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.1-1: MCData standalone data request** + +| Information element | Status | Description | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Payload | M | SDS content | +| NOTE: | The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | | + +#### 7.4.2.1.2 MCData data disposition notification + +Table 7.4.2.1.2-1 describes the information flow for the MCData data disposition notification sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.2-1: MCData data disposition notification** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the notification is sent | +| MCData ID | M | The identity of the MCData user sending notification | +| Conversation Identifier | M | Identifies the conversation | +| Disposition association | M | Identity of the original MCData transaction | +| Disposition | M | Disposition which is delivered or read or both | + +#### 7.4.2.1.3 MCData standalone session data request + +Table 7.4.2.1.3-1 describes the information flow for the MCData standalone session data request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.3-1: MCData standalone session data request** + +| Information element | Status | Description | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Standalone transaction | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| SDP offer | M | Media parameters offered | +| NOTE: | The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | + +#### 7.4.2.1.4 MCData standalone session data response + +Table 7.4.2.1.4-1 describes the information flow for the MCData standalone session data response sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.4-1: MCData standalone session data response** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving data | +| MCData ID | M | The identity of the MCData user sent data | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | + +#### 7.4.2.1.5 MCData session data request + +Table 7.4.2.1.5-1 describes the information flow for the MCData session data request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.5-1: MCData session data request** + +| Information element | Status | Description | +|-----------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Session based transactions | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| SDP offer | M | Media parameters offered | +| NOTE: | | The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | + +#### 7.4.2.1.6 MCData session data response + +Table 7.4.2.1.6-1 describes the information flow for the MCData session data response sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.6-1: MCData session data response** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving data | +| MCData ID | M | The identity of the MCData user sent data | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | + +#### 7.4.2.1.7 MCData group standalone data request (MCData client – MCData server) + +Table 7.4.2.1.7-1 describes the information flow for the MCData group standalone data request (in subclause 7.4.2.5.2) sent from the MCData client to the MCData server. + +**Table 7.4.2.1.7-1: MCData group standalone data request (MCData client – MCData server)** + +| Information element | Status | Description | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Payload | M | SDS content | +| NOTE: | The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | + +#### 7.4.2.1.8 MCData group standalone data request (MCData server – MCData client) + +Table 7.4.2.1.8-1 describes the information flow for the MCData group standalone data request (in subclause 7.4.2.5.2) sent from the MCData server to the MCData client. + +**Table 7.4.2.1.8-1: MCData group standalone data request (MCData server – MCData client)** + +| Information element | Status | Description | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Payload | M | SDS content | +| NOTE: | The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | | + +#### 7.4.2.1.9 MCData data disposition notification(s) (MCData server – MCData client) + +Table 7.4.2.1.9-1 describes the information flow for the MCData data disposition notification(s) sent from the MCData server to the MCData client. + +**Table 7.4.2.1.9-1: MCData data disposition notification(s) (MCData server – MCData client)** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the notification is sent | +| MCData ID | M | The identity of the MCData user sending notification | +| Conversation Identifier | M | Identifies the conversation | +| Disposition association | M | Identity of the original MCData transaction | +| Disposition | M | Disposition which is delivered or read or both | + +#### 7.4.2.1.10 MCData group session standalone data request (MCData client – MCData server) + +Table 7.4.2.1.10-1 describes the information flow for the MCData group session standalone data request (in subclause 7.4.2.6.2) sent from the MCData client to the MCData server. + +**Table 7.4.2.1.10-1: MCData group session standalone data request (MCData client – MCData server)** + +| Information element | Status | Description | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Standalone transaction | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| SDP offer | M | Media parameters offered | +| NOTE: | The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | + +#### 7.4.2.1.11 MCData group session standalone data request (MCData server – MCData client) + +Table 7.4.2.1.11-1 describes the information flow for the MCData group session standalone data request (in subclause 7.4.2.6.2) sent from the MCData server to the MCData client. + +**Table 7.4.2.1.11-1: MCData group session standalone data request (MCData server – MCData client)** + +| Information element | Status | Description | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Standalone transaction | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| SDP offer | M | Media parameters offered | +| NOTE: | The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | + +#### 7.4.2.1.12 MCData group session standalone data response + +Table 7.4.2.1.12-1 describes the information flow for the MCData group standalone data response (in subclause 7.4.2.6.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.12-1: MCData group session standalone data response** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user sent data | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | + +#### 7.4.2.1.13 MCData group data request (MCData client – MCData server) + +Table 7.4.2.1.13-1 describes the information flow for the MCData group data request sent from the MCData client to the MCData server. + +**Table 7.4.2.1.13-1: MCData group data request (MCData client – MCData server)** + +| Information element | Status | Description | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Session based transactions | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| SDP offer | M | Media parameters offered | +| NOTE: | The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | + +#### 7.4.2.1.14 MCData group data request (MCData server – MCData client) + +Table 7.4.2.1.14-1 describes the information flow for the MCData group data request sent from the MCData server to the MCData client. + +**Table 7.4.2.1.14-1: MCData group data request (MCData server – MCData client)** + +| Information element | Status | Description | +|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the recipient MCData user | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Session based transactions | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| SDP offer | M | Media parameters offered | +| NOTE: | The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | + +### 7.4.2.1.15 MCData group data response + +Table 7.4.2.1.15-1 describes the information flow for the MCData group data response sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.15-1: MCData group data response** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user sent data | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | + +### 7.4.2.2 One-to-one standalone short data service using signalling control plane + +#### 7.4.2.2.1 General + +A MCData user initiates a standalone SDS data transfer with another MCData user. For the SDS data transfer signalling plane is used. + +#### 7.4.2.2.2 Procedure + +The procedure in figure 7.4.2.2.2-1 describes the case where an MCData user is initiating one-to-one MCData data communication for sending standalone SDS data to other MCData user, with or without disposition request. Standalone refers to sending unidirectional data in one transaction. + +Pre-conditions: + +1. The SDS payload data size is below the configured maximum payload data size for SDS over signalling control plane. +2. MCData users on MCData client 1 and MCData client 2 are already registered for receiving MCData service. +3. MCData client 1 and MCData client 2 belong to the same MCData system. + +![Sequence diagram for one-to-one standalone short data service using signalling control plane. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2. The process starts with client 1 initiating a data request, followed by a standalone data request to the server, which then authorizes and asserts policy. The server then sends a standalone data request to client 2, who processes the payload. Finally, disposition notifications are sent from client 2 to the server, and from the server to client 1.](e038bf4fcea08f51944b4a2dd6e197a5_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData standalone data request + Note right of MCData server: 3. Authorize request and policy assertion + MCData server->>MCData client 2: 4. MCData standalone data request + Note right of MCData client 2: 5. Process payload + MCData client 2-->>MCData server: 6. MCData data disposition notification + MCData server-->>MCData client 1: 7. MCData data disposition notification + MCData client 2-->>MCData server: 8. MCData data disposition notification + MCData server-->>MCData client 1: 9. MCData data disposition notification + +``` + +Sequence diagram for one-to-one standalone short data service using signalling control plane. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2. The process starts with client 1 initiating a data request, followed by a standalone data request to the server, which then authorizes and asserts policy. The server then sends a standalone data request to client 2, who processes the payload. Finally, disposition notifications are sent from client 2 to the server, and from the server to client 1. + +**Figure 7.4.2.2.2-1: One-to-one standalone short data service using signalling control plane** + +1. The user at MCData client 1 initiates an SDS data transfer for the chosen MCData user. + +2. MCData client 1 sends a MCData standalone data request towards the MCData server. The MCData standalone data request contains conversation identifier for message thread indication. The MCData standalone data request may contain disposition request if indicated by the user at MCData client 1. +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData standalone data request. The MCData server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege or affiliation. +4. MCData server initiates the MCData standalone data request towards the MCData user. +5. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData client 2 may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData client 2 shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. +6. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData client initiates a MCData data disposition notification for delivery report. The MCData data disposition notification from MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. +7. MCData data disposition notification is sent to the disposition requesting user at MCData client 1. +8. If the MCData data disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData data disposition notification for read report. The MCData data disposition notification from MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. The MCData data disposition notification from MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. +9. MCData data disposition notification is sent to the disposition requesting user at MCData client 1. + +### 7.4.2.3 One-to-one standalone short data service using media plane + +#### 7.4.2.3.1 General + +A MCData user initiates a standalone SDS data transfer with another MCData user. For the SDS data transfer media plane is used. + +#### 7.4.2.3.2 Procedure + +The procedure in figure 7.4.2.3.2-1 describes the case where an MCData user is initiating one-to-one MCData data communication for sending standalone SDS data to other MCData user, with or without disposition request. Standalone refers to sending unidirectional data in one transaction. The SDS payload data size is assumed to be above the configured maximum payload data size for SDS over signalling control plane. + +Pre-conditions: + +1. MCData users on MCData client 1 and MCData client 2 are already registered for receiving MCData service. +2. MCData client 1 and MCData client 2 belong to the same MCData system. + +![Sequence diagram illustrating the One-to-one standalone short data service using media plane. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2. Steps include: 1. initiate data request (client 1), 2. MCData standalone session data request (client 1 to server), 3. Authorize request and policy assertion (server), 4. MCData standalone session data request (server to client 2), 5. MCData standalone session data response (client 2 to server), 6. MCData standalone session data response (server to client 1), 7. Data transmission (client 1 to client 2), 8. Process payload (client 2), 9. MCData data disposition notification (client 2 to server), 10. MCData data disposition notification (server to client 1), 11. MCData data disposition notification (client 2 to server), 12. MCData data disposition notification (server to client 1).](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData standalone session data request + MCData server->>MCData server: 3. Authorize request and policy assertion + MCData server->>MCData client 2: 4. MCData standalone session data request + MCData client 2->>MCData server: 5. MCData standalone session data response + MCData server->>MCData client 1: 6. MCData standalone session data response + Note over MCData client 1, MCData client 2: 7. Data transmission + MCData client 1->>MCData client 2: Data transmission + Note right of MCData client 2: 8. Process payload + MCData client 2->>MCData server: 9. MCData data disposition notification + MCData server->>MCData client 1: 10. MCData data disposition notification + MCData client 2->>MCData server: 11. MCData data disposition notification + MCData server->>MCData client 1: 12. MCData data disposition notification + +``` + +Sequence diagram illustrating the One-to-one standalone short data service using media plane. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2. Steps include: 1. initiate data request (client 1), 2. MCData standalone session data request (client 1 to server), 3. Authorize request and policy assertion (server), 4. MCData standalone session data request (server to client 2), 5. MCData standalone session data response (client 2 to server), 6. MCData standalone session data response (server to client 1), 7. Data transmission (client 1 to client 2), 8. Process payload (client 2), 9. MCData data disposition notification (client 2 to server), 10. MCData data disposition notification (server to client 1), 11. MCData data disposition notification (client 2 to server), 12. MCData data disposition notification (server to client 1). + +**Figure 7.4.2.3.2-1: One-to-one standalone short data service using media plane** + +1. User at MCData client 1 would like to initiate a SDS data transfer request for the chosen MCData user. +2. MCData client 1 sends a MCData standalone session data request towards the MCData server. The MCData standalone data request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData standalone session data request contains conversation identifier for message thread indication. The MCData data request may contain disposition request if indicated by the user at MCData client 1. +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData standalone session data request. The MCData server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. MCData server determines the eligible MCData user(s) after policy assertion for sending the MCData standalone session data request. +4. MCData server initiates the MCData standalone session data request towards the MCData user. +5. The receiving MCData client 2 automatically accepts the MCData standalone session data request and responds with MCData standalone session data response towards MCData server. +6. MCData server forwards the MCData client 2 accepted response to the MCData user initiating the MCData standalone session data request. +7. MCData client 1 and MCData client 2 have successfully established media plane for data communication and the MCData client 1 transmits the SDS data. +8. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData client 2 may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData client 2 shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. + +- 9. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData client initiates a MCData data disposition notification for delivery report. The MCData data disposition notification from the receiving MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. +- 10. MCData data disposition notification is sent to the disposition requesting user at MCData client 1. +- 11. If the MCData disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData disposition notification for read report. The MCData data disposition notification from the receiving MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. +- 12. MCData data disposition notification is sent to the disposition requesting user at MCData client 1. + +**7.4.2.4 One-to-one short data service session** + +**7.4.2.4.1 General** + +A MCData user triggers an establishment of a MCData session with another MCData user for the exchange of SDS data. + +**7.4.2.4.2 Procedure** + +The procedure in figure 7.4.2.4.2-1 describes the case where an MCData user is initiating data communication session with another MCData user for exchanging at least one SDS data transaction between them, with or without disposition request using MCData-SDS-1 and MCData-SDS-2 or MCData-SDS-3 reference points. + +Pre-conditions: + +- 1. MCData users on MCData client 1 and MCData client 2 are already registered for receiving MCData service. + +![Sequence diagram for One-to-one short data service session. Lifelines: MCData client 1, MCData server, MCData client 2. The sequence starts with client 1 sending a session request to the server, which then forwards it to client 2. Client 2 sends a response back to the server, which then forwards it to client 1. A loop for 'Data transmission and disposition' follows, with client 2 sending notifications to the server and client 1. The session ends with a termination message from client 1 to the server.](f10dc32e3673e1392029a49e958a9d6c_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + + Note left of MCData client 1: 1. initiate session data request + MCData client 1->>MCData server: 2. MCData session data request + Note right of MCData server: 3. Authorize request and policy assertion + MCData server->>MCData client 2: 4. MCData session data request + Note right of MCData client 2: 5. Notify request + MCData client 2->>MCData server: 6. MCData session data response + MCData server->>MCData client 1: 7. MCData session data response + Note right of MCData client 1: 8. Data transmission and disposition + Note right of MCData client 2: 9. Notify data + Note right of MCData client 1: 10. Data transmission and disposition + Note left of MCData client 1: 11. Notify data + Note right of MCData client 1: 12. Session data termination + +``` + +Sequence diagram for One-to-one short data service session. Lifelines: MCData client 1, MCData server, MCData client 2. The sequence starts with client 1 sending a session request to the server, which then forwards it to client 2. Client 2 sends a response back to the server, which then forwards it to client 1. A loop for 'Data transmission and disposition' follows, with client 2 sending notifications to the server and client 1. The session ends with a termination message from client 1 to the server. + +**Figure 7.4.2.4.2-1: One-to-one short data service session** + +- 1. User at MCData client 1 would like to initiate a SDS data communication session request for the chosen MCData user. + +2. MCData client 1 sends a MCData session data request towards the MCData server. The MCData standalone data request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData session data request contains conversation identifier for message thread indication. +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData session data request. The MCData server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. MCData server determines the eligible MCData user(s) after policy assertion for sending the MCData session data request. +4. MCData server initiates the MCData session data request towards the MCData user determined. +5. The receiving MCData client 2 optionally notifies the user about the incoming MCData session data request. +6. The receiving MCData client 2 accepts the MCData session data request and responds with MCData session data response towards MCData server. +7. MCData server forwards the MCData client 2 accepted response to the MCData user initiating the MCData session data request. +8. and 10. MCData client 1 and MCData client 2 have successfully established media plane for data communication and either MCData client can transmit SDS data. The MCData data request may contain disposition request if indicated by the client sending data. If MCData data disposition was requested by the user, then the receiving MCData client initiates a MCData data disposition notification for delivery, read reports to the disposition requesting user. The MCData data disposition notification from MCData user may be stored by the MCData server for disposition history interrogation from authorized users. +9. and 11. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData client 2 may be notified, otherwise the MCData user of MCData client 2 shall not be notified. +12. After SDS data transaction is complete, the established media plane is released. + +#### 7.4.2.5 Group standalone short data service using signalling control plane + +##### 7.4.2.5.1 General + +The initiation of a group standalone SDS to a selected group results in affiliated group members receiving the SDS data. The SDS payload data size is assumed to be below the configured maximum payload data size for SDS over signalling control plane. + +##### 7.4.2.5.2 Procedure + +The procedure in figure 7.4.2.5.2-1 describes the case where an MCData user is initiating group standalone MCData data communication with or without disposition request, to a group. + +Pre-conditions: + +1. MCData users on MCData clients 1 to n belong to the same group and are already registered for receiving MCData service and affiliated. + +![Sequence diagram showing Group standalone SDS using signalling control plane. Lifelines: MCData client 1, MCData server, Group management server, MCData client 2 to n. Steps: 1. initiate group standalone data request, 2. MCData group standalone data request, 3. Resolve group id, 4. MCData group standalone data request, 5. Process payload, 6. MCData data disposition notification, 7. MCData data disposition notification, 8. Aggregate notifications, 9. MCData data disposition notification(s).](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Group management server + participant MCData client 2 to n + + Note left of MCData client 1: 1. initiate group standalone data request + MCData client 1->>MCData server: 2. MCData group standalone data request + MCData server->>Group management server: 3. Resolve group id + MCData server->>MCData client 2 to n: 4. MCData group standalone data request + Note right of MCData client 2 to n: 5. Process payload + MCData client 2 to n-->>MCData server: 6. MCData data disposition notification + MCData client 2 to n-->>MCData server: 7. MCData data disposition notification + Note left of MCData server: 8. Aggregate notifications + MCData server-->>MCData client 1: 9. MCData data disposition notification(s) + +``` + +Sequence diagram showing Group standalone SDS using signalling control plane. Lifelines: MCData client 1, MCData server, Group management server, MCData client 2 to n. Steps: 1. initiate group standalone data request, 2. MCData group standalone data request, 3. Resolve group id, 4. MCData group standalone data request, 5. Process payload, 6. MCData data disposition notification, 7. MCData data disposition notification, 8. Aggregate notifications, 9. MCData data disposition notification(s). + +**Figure 7.4.2.5.2-1: Group standalone SDS using signalling control plane** + +1. The user at MCData client 1 initiates an SDS data transfer to multiple MCData users selecting a pre-configured group (identified by MCData group ID) and optionally particular members from that group. +2. MCData client 1 sends a MCData group standalone data request towards the MCData server. The MCData group data request contains MCData group ID as selected by the user at MCData client 1. The MCData group standalone data request contains conversation identifier for message thread indication. The MCData group standalone data request may contain disposition request if indicated by the user at MCData client 1. +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData group standalone data request. The MCData server resolves the MCData group ID to determine the members of that group and their affiliation status, based on the information from the group management server. The MCData server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege or affiliation. +4. MCData server initiates the MCData group standalone data request towards each MCData client determined in Step 3. +5. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData clients 2 to n may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData clients 2 to n shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. +6. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData client(s) initiates a MCData data disposition notification for delivery report. +7. If the MCData data disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData data disposition notification for read report. +8. The MCData data disposition notification(s) from MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. The MCData data disposition notification(s) from each MCData user may be aggregated. + +- 9. Aggregated or individual MCData data disposition notification(s) is sent to the disposition requesting user at MCData client 1. + +### 7.4.2.6 Group standalone short data service using media plane + +#### 7.4.2.6.1 General + +The initiation of a group standalone SDS to a selected group results in affiliated group members receiving the SDS data. The SDS payload data size is assumed to be above the configured maximum payload data size for SDS over signalling control plane. + +#### 7.4.2.6.2 Procedure + +The procedure in figure 7.4.2.6.2-1 describes the case where an MCData user is initiating group standalone MCData data communication with or without disposition request to a group. + +Pre-conditions: + +- 1. MCData users on MCData client 1 to n belong to the same group and are already registered for receiving MCData service and affiliated. + +![Sequence diagram for Group standalone SDS using media plane. Lifelines: MCData client 1, MCData server, Group management server, MCData client 2 to n. The sequence shows steps from initiating a data request to processing the payload and sending disposition notifications.](4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Group management server + participant MCData client 2 to n + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData group session standalone data request + MCData server->>Group management server: 3. Resolve group id + MCData server->>MCData client 2 to n: 4. MCData group session standalone data request + MCData client 2 to n-->>MCData server: 5. MCData group session standalone data response + MCData server-->>MCData client 1: 6. MCData group session standalone data response + Note right of MCData client 1: 7. Data transmission + Note right of MCData server: 8. Data transmission + Note right of MCData client 2 to n: 9. Process payload + MCData client 2 to n-->>MCData server: 10. MCData data disposition notification + MCData client 2 to n-->>MCData server: 11. MCData data disposition notification + Note right of MCData server: 12. Aggregate notifications + MCData server-->>MCData client 1: 13. MCData data disposition notification(s) + +``` + +Sequence diagram for Group standalone SDS using media plane. Lifelines: MCData client 1, MCData server, Group management server, MCData client 2 to n. The sequence shows steps from initiating a data request to processing the payload and sending disposition notifications. + +Figure 7.4.2.6.2-1: Group standalone SDS using media plane + +- 1. User at MCData client 1 would like to initiate a SDS data transfer request to multiple MCData users selecting a pre-configured group (identified by MCData group ID) and optionally particular members from that group. +- 2. MCData client 1 sends a MCData group session standalone data request towards the MCData server. The MCData group session standalone data request contains target recipient(s) as selected by the user at MCData client 1. The MCData session group standalone data request contains conversation identifier for message thread indication. The MCData session group standalone data request may contain disposition request if indicated by the user at MCData client 1. +- 3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData session group standalone data request. The MCData server resolves the MCData group ID to determine the members of that group and their affiliation status, based on the information from the group management server. The MCData + +server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. + +4. MCData server initiates the MCData group session standalone data request towards each MCData user determined in Step 3. +5. The receiving MCData clients 2 to n automatically accepts the MCData group session standalone data request and responds with MCData group standalone data response towards MCData server. +6. MCData server forwards the MCData clients 2 to n accepted response to the MCData user initiating the MCData group session standalone data request. + +NOTE 1: Step 6 can occur at any time following step 4, and prior to step 7 depending on the conditions to proceed with the data transmission. + +7. MCData client 1 and MCData server have successfully established media plane for data communication and the MCData client 1 transmits the SDS data. +8. MCData server distributes the data received from MCData client 1 to MCData clients 2 to n over the established media plane. After completion of the MCData transfer from MCData client 1, media plane resources associated to the data communication are released. + +NOTE 2: MCData server is not required to wait for the complete reception of SDS data from MCData client 1 prior to initiating transmission to MCData client 2 to n. + +9. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData client 2 to n may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData client 2 to n shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. +10. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData client(s) initiates a MCData data disposition notification for delivery report. +11. If the MCData data disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData data disposition notification for read report. +12. The MCData data disposition notification(s) from MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. The MCData data disposition notification(s) from each MCData user may be aggregated. +13. Aggregated or individual MCData data disposition notification(s) is sent to the disposition requesting user at MCData client 1. + +## 7.4.2.7 Group short data service session + +### 7.4.2.7.1 General + +The initiation of a group SDS to a selected group results in affiliated group members exchanging SDS data. + +### 7.4.2.7.2 Procedure + +The procedure in figure 7.4.2.7.2-1 describes the case where an MCData user is initiating SDS data communication session with an MCData group for exchanging SDS data transactions between the group participants, with or without disposition request, using MCData-SDS-1 and MCData-SDS-2 reference points. + +Pre-conditions: + +1. MCData users on MCData client 1 to n belong to the same group and are already registered for receiving MCData service and affiliated. + +![Sequence diagram for Group SDS session showing interactions between MCData client 1, MCData server, Group management server, and MCData client 2 to n.](32ff77da4286b58c4778033acaa10836_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Group management server + participant MCData client 2 to n + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData group data request + MCData server->>Group management server: 3. Resolve group id + MCData server->>MCData client 2 to n: 4. MCData group data request + Note right of MCData client 2 to n: 5. Notify request + MCData client 2 to n->>MCData server: 6. MCData group data response + MCData server->>MCData client 1: 7. MCData group data response + Note over MCData client 1, MCData server, Group management server, MCData client 2 to n: 8. Data transmission + Note over MCData client 1, MCData server, Group management server, MCData client 2 to n: 9. Disposition notifications + Note over MCData client 1, MCData server, Group management server, MCData client 2 to n: 10. Session data termination + +``` + +Sequence diagram for Group SDS session showing interactions between MCData client 1, MCData server, Group management server, and MCData client 2 to n. + +**Figure 7.4.2.7.2-1: Group SDS session** + +1. User at MCData client 1 would like to initiate a SDS group data transfer request to multiple MCData users selecting a pre-configured group (identified by MCData group ID) and optionally particular members from that group. + 2. MCData client 1 sends a MCData group data request towards the MCData server. The MCData group data request contains MCData group ID as selected by the user at MCData client 1. The MCData session data request contains conversation identifier for message thread indication. + 3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData group data request. The MCData server resolves the MCData group ID to determine the members of that group and their affiliation status, based on the information from the group management server. The MCData server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. + 4. MCData server initiates the MCData group data request towards each MCData user determined in Step 3. + 5. The receiving MCData clients 2 to n optionally notify the user about the incoming MCData session data request. + 6. The receiving MCData client 2 to n accept or reject the MCData group data request and the corresponding result is in the MCData group data response towards MCData server. + 7. MCData server forwards the MCData client 2 accepted response to the MCData user initiating the MCData session data request. +- NOTE: Step 7 can occur at any time following step 4, and prior to step 8 depending on the conditions to proceed with the data transmission. +8. MCData client 1 and the MCData group data request accepted clients have successfully established media plane for data communication and either MCData client can transmit SDS data. The MCData data request may contain disposition request if indicated by the client sending data. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the SDS data receiving MCData users may be notified, otherwise those MCData users shall not be notified. + 9. If MCData data disposition was requested by the user, then the SDS data receiving MCData client initiates a MCData data disposition notification for delivery, read reports to the disposition requesting user. The MCData + +data disposition notification from MCData user may be stored by the MCData server for disposition history interrogation from authorized users. + +10. Based on the MCData user action or conditions to release, the established media plane for SDS data exchange is released. + +### 7.4.3 Short data service for off-network + +#### 7.4.3.1 General + +#### 7.4.3.2 Information flows for short data service + +##### 7.4.3.2.1 MCData standalone data request + +Table 7.4.3.2.1-1 describes the information flow for the MCData standalone data request sent from the MCData client to another MCData client. + +**Table 7.4.3.2.1-1: MCData standalone data request** + +| Information element | Status | Description | +|-----------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Date and Time | M | Date and time of transmission | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Payload | M | SDS content | +| NOTE: | | The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | + +##### 7.4.3.2.2 MCData data disposition notification + +Table 7.4.3.2.2-1 describes the information flow for the MCData data disposition notification sent from the MCData client to another MCData client. + +**Table 7.4.3.2.2-1: MCData data disposition notification** + +| Information element | Status | Description | +|--------------------------|--------|---------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the notification is sent | +| MCData ID | M | The identity of the MCData user sending notification | +| Conversation Identifier | M | Identifies the conversation | +| Reply Identifier | M | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition | M | Disposition which is delivered or read or both | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | + +##### 7.4.3.2.3 MCData group standalone data request + +Table 7.4.3.2.3-1 describes the information flow for the MCData group standalone data request sent from the MCData client to another MCData client. + +Table 7.4.3.2.3-1: MCData group standalone data request + +| Information element | Status | Description | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Date and Time | M | Date and time of transmission | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Payload | M | SDS content | +| NOTE: | The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | | + +### 7.4.3.3 One-to-one standalone short data service using signalling control plane + +#### 7.4.3.3.1 General + +This subclause describes the detailed procedures for the scenario where SDS data is to be sent to MCData user in off-network. + +#### 7.4.3.3.2 Procedure + +Figure 7.4.3.3.2-1 describes procedures for an off-network MCData client 1 initiating one-to-one MCData data communication for sending standalone SDS data to other MCData client, with or without disposition request. Standalone refers to sending unidirectional data in one transaction. The SDS data size is assumed to be pre-configured. + +Pre-conditions: + +1. MCData user 1 has initiated communication for sending standalone SDS data to other MCData user 2. +2. MCData client 1 and MCData client 2 are members of the same **ProSe** Discovery group and are **ProSe** 1:1 direct communication capable. +3. MCData client 1 has discovered MCData client 2 in proximity, associated with MCData user B, using **ProSe** Discovery procedures. + +![Sequence diagram for One-to-one standalone short data service using signalling control plane. The diagram shows two participants: MCData client 1 and MCData client 2. The sequence of messages is: 1. Check authorization (internal to client 1), 2. MCData standalone data request (client 1 to client 2), 3. Assert policy (internal to client 2), 4. Process payload (internal to client 2), 5. MCData data disposition notification (client 2 to client 1), 6. MCData data disposition notification (client 2 to client 1).](4767b6e106f34fe8b63a6838810bf913_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + Note left of MCData client 1: 1. Check authorization + MCData client 1->>MCData client 2: 2. MCData standalone data request + Note right of MCData client 2: 3. Assert policy + Note right of MCData client 2: 4. Process payload + MCData client 2-->>MCData client 1: 5. MCData data disposition notification + MCData client 2-->>MCData client 1: 6. MCData data disposition notification + +``` + +Sequence diagram for One-to-one standalone short data service using signalling control plane. The diagram shows two participants: MCData client 1 and MCData client 2. The sequence of messages is: 1. Check authorization (internal to client 1), 2. MCData standalone data request (client 1 to client 2), 3. Assert policy (internal to client 2), 4. Process payload (internal to client 2), 5. MCData data disposition notification (client 2 to client 1), 6. MCData data disposition notification (client 2 to client 1). + +Figure 7.4.3.3.2-1: One-to-one standalone short data service using signalling control plane + +1. MCData client 1 checks whether the MCData user 1 is authorized to send MCData standalone data request. + +2. If MCData user 1 is authorised MCData client 1 sends a MCData standalone data request towards the MCData client 2. The MCData standalone data request contains conversation identifier for message thread indication. The MCData standalone data request may contain disposition request if indicated by the user at MCData client 1. +3. On receiving a MCData standalone data request, the MCData client 2 checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. +4. If the policy assertion is positive and the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData client 2 may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData client 2 shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. + +NOTE: If the policy assertion was negative, the MCData client 2 sends an appropriate notification to MCData client 1. + +5. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData client 2 initiates a MCData data disposition notification for delivery report. +6. If the MCData data disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData data disposition notification for read report. + +#### 7.4.3.4 Group standalone short data service using signalling control plane + +##### 7.4.3.4.1 General + +The initiation of a group standalone SDS to a selected group results in off-network MCData group members receiving the SDS data. + +##### 7.4.3.4.2 Procedure + +Figure 7.4.3.4.2-1 describes procedures for an off-network MCData client 1 initiating group MCData data communication for sending SDS data to a MCData group, with or without disposition request. The SDS data size limit is pre-configured. + +Pre-conditions: + +1. MCData user 1 has initiated group communication for sending SDS data to the MCData group. +2. Information for **ProSe** direct communications corresponding to the MCData group and its mapping to **ProSe** Layer-2 Group ID are pre-configured in MCData client 1. +3. MCData client 1 to MCData client N are members of the same MCData group. + +![Sequence diagram showing the interaction between multiple MCData clients (1, 2, N) for a group standalone short data service. The process involves authorization, data request, policy assertion, payload processing, and data disposition notifications.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + participant MCData client N + Note left of MCData client 1: 1. Check authorization + MCData client 1->>MCData client 2: 2. MCData group standalone data request + Note right of MCData client 2: 3. Assert policy + Note right of MCData client 2: 4. Process payload + Note right of MCData client N: 3. Assert policy + Note right of MCData client N: 4. Process payload + MCData client 2-->>MCData client 1: 5. MCData data disposition notification + MCData client 2-->>MCData client 1: 6. MCData data disposition notification + MCData client N-->>MCData client 1: 5. MCData data disposition notification + MCData client N-->>MCData client 1: 6. MCData data disposition notification + +``` + +Sequence diagram showing the interaction between multiple MCData clients (1, 2, N) for a group standalone short data service. The process involves authorization, data request, policy assertion, payload processing, and data disposition notifications. + +**Figure 7.4.3.4.2-1: Group standalone short data service using signalling control plane** + +1. MCData client 1 checks whether the MCData user 1 is authorized to send MCData group standalone data request. +2. If MCData user 1 is authorised MCData client 1 sends a MCData group standalone data request towards the MCData group. The MCData group standalone data request contains conversation identifier for message thread indication. The MCData group standalone data request may contain disposition request if indicated by the user at MCData client 1. If MCData group standalone data request contains disposition request, MCData group standalone data request shall also contain the IP address of the MCData client 1. +3. On receiving a MCData group standalone data request, the MCData clients check whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. +4. If the policy assertion is positive and the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. + +NOTE: If the policy assertion was negative, the MCData client sends an appropriate notification to MCData client 1. + +5. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData clients initiate a MCData data disposition notification for delivery report. +6. If the MCData data disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData data disposition notification for read report. + +## 7.5 File distribution + +### 7.5.1 General + +File distribution (mandatory and non-mandatory download) is enabled for both one-to-one and group. + +## 7.5.2 File distribution for on-network + +### 7.5.2.1 Information flows for file distribution + +#### 7.5.2.1.1 MCData upload data request + +Table 7.5.2.1.1-1 describes the information flow for the MCData upload data request sent from the MCData client to the MCData server. + +**Table 7.5.2.1.1-1: MCData upload data request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------| +| MCData ID | M | The identity of the MCData user uploading data | +| Content | M | Content to upload | + +#### 7.5.2.1.2 MCData upload data response + +Table 7.5.2.1.2-1 describes the information flow for the MCData upload data response sent from the MCData server to the MCData client. + +**Table 7.5.2.1.2-1: MCData upload data response** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting to upload data | +| Upload confirmation | M | An indication whether the upload to the content storage is successful or not | +| Content reference | O | URL reference of the content stored (see NOTE). | +| NOTE: Content reference shall be present when the upload confirmation is successful. | | | + +#### 7.5.2.1.3 MCData download data request + +Table 7.5.2.1.3-1 describes the information flow for the MCData download data request sent from the MCData client to the MCData server. + +**Table 7.5.2.1.3-1: MCData download data request** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------| +| MCData ID | M | The identity of the MCData user downloading data | +| Content reference | M | URL reference to the content to download | + +#### 7.5.2.1.4 MCData download data response + +Table 7.5.2.1.4-1 describes the information flow for the MCData download data response sent from the MCData server to the MCData client. + +**Table 7.5.2.1.4-1: MCData download data response** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------|--------|--------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting to download data | +| Content (see NOTE) | O | Requested content to download | +| Result | M | Indicates success or failure of MCData download data request | +| NOTE: Content shall be present when the result of the MCData download data request indicates success. | | | + +#### 7.5.2.1.5 MCData FD request (using HTTP) + +Table 7.5.2.1.5-1 describes the information flow for the MCData FD request (in subclause 7.5.2.4.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.5-1: MCData FD request (using HTTP)** + +| Information element | Status | Description | +|-------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending file | +| MCData ID | M | The identity of the MCData user receiving file | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed reported is expected or not | +| Download indication | O | Indicates mandatory download | +| Content reference | M | URL reference to the content and file metadata information | + +#### 7.5.2.1.6 MCData FD response (using HTTP) + +Table 7.5.2.1.6-1 describes the information flow for the MCData FD response (in subclause 7.5.2.4.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.6-1: MCData FD response (using HTTP)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | + +#### 7.5.2.1.7 MCData download completed report + +Table 7.5.2.1.7-1 describes the information flow for the MCData download completed report sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.7-1: MCData download completed report** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | M | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition confirmation | M | An indication that the client has completed downloading file | + +#### 7.5.2.1.8 MCData FD request (using media plane) + +Table 7.5.2.1.8-1 describes the information flow for the MCData FD request (in subclause 7.5.2.5.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.8-1: MCData FD request (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending file | +| MCData ID | M | The identity of the MCData user receiving file | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed reported is expected or not | +| Download indication | O | Indicates mandatory download | +| SDP offer | M | Media parameters offered | +| Content reference | M | URL reference to the content and file metadata information | + +#### 7.5.2.1.9 MCData FD response (using media plane) + +Table 7.5.2.1.9-1 describes the information flow for the MCData FD response (in subclause 7.5.2.5.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.9-1: MCData FD response (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | + +#### 7.5.2.1.10 MCData group standalone FD request (using HTTP) + +Table 7.5.2.1.10-1 describes the information flow for the MCData group standalone FD request (in subclause 7.5.2.6.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.10-1: MCData group standalone FD request (using HTTP)** + +| Information element | Status | Description | +|-------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending file | +| MCData group ID | M | The MCData group ID to which the file is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed reported is expected or not | +| Download indication | O | Indicates mandatory download | +| Content reference | M | URL reference to the content and file metadata information | + +#### 7.5.2.1.11 MCData group standalone FD response (using HTTP) + +Table 7.5.2.1.11-1 describes the information flow for the MCData group standalone FD response (in subclause 7.5.2.6.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.11-1: MCData group standalone FD response (using HTTP)** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData group ID | M | The MCData group ID to which the file is to be sent | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | + +### 7.5.2.1.12 MCDData group standalone FD request (using media plane) + +Table 7.5.2.1.12-1 describes the information flow for the MCDData group standalone FD request (in subclause 7.5.2.7.2) sent from the MCDData client to the MCDData server and from the MCDData server to another MCDData client. + +**Table 7.5.2.1.12-1: MCDData group standalone FD request (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|--------------------------------------------------------------------------------------------| +| MCDData ID | M | The identity of the MCDData user sending file | +| MCDData group ID | M | The MCDData group ID to which the data is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCDData transaction | +| Reply Identifier | O | Identifies the original MCDData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed reported is expected or not | +| Download indication | O | Indicates mandatory download | +| SDP offer | M | Media parameters offered | +| Content reference | M | URL reference to the content and file metadata information | + +### 7.5.2.1.13 MCDData group standalone FD response (using media plane) + +Table 7.5.2.1.13-1 describes the information flow for the MCDData group standalone FD response (in subclause 7.5.2.7.2) sent from the MCDData client to the MCDData server and from the MCDData server to another MCDData client. + +**Table 7.5.2.1.13-1: MCDData group standalone FD response (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------------| +| MCDData ID | M | The identity of the MCDData user sending FD request | +| MCDData group ID | M | The MCDData group ID to which the file is to be sent | +| MCDData ID | M | The identity of the MCDData user sending response | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | + +## 7.5.2.2 File upload using HTTP + +### 7.5.2.2.1 General + +The MCDData client uses HTTP for a standalone data file upload towards the MCDData server. + +### 7.5.2.2.2 Procedure + +The procedure in figure 7.5.2.2.2-1 describes the case where an MCDData user is uploading file to media storage function of MCDData content server. + +Pre-conditions: + +1. The MCDData user on the MCDData client 1 is registered for receiving MCDData service. + +![Sequence diagram for file upload using HTTP](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData content server + Note left of MCData client 1: 1. initiate upload request + MCData client 1->>MCData content server: 2. MCData upload data request + MCData content server-->>MCData client 1: 3. MCData upload data response +``` + +The diagram illustrates the interaction for file upload. It starts with a note '1. initiate upload request' on the MCData client 1 lifeline. Then, a solid arrow labeled '2. MCData upload data request' points from MCData client 1 to MCData content server. Finally, a dashed arrow labeled '3. MCData upload data response' points from MCData content server back to MCData client 1. + +Sequence diagram for file upload using HTTP + +**Figure 7.5.2.2.2-1: File upload using HTTP** + +1. The user at the MCData client 1 initiates a file upload request of the chosen file and the MCData client 1 verifies that the size of the file is within the maximum data size for FD for the intended MCData FD request (by checking the group configuration for a group FD request and by checking the service configuration for a one-to-one FD request). +2. The file to be uploaded is received by the media storage client at the MCData client 1 and sent to the media storage function on the MCData content server for storing using the MCData upload data request. +3. The MCData content server also applies transmission control policy before storage and provides a MCData upload data response indicating success (along with file URL to the media storage client at the MCData client 1) or failure. + +### 7.5.2.3 File download using HTTP + +#### 7.5.2.3.1 General + +The MCData client uses HTTP for a standalone data file download from the MCData server. + +#### 7.5.2.3.2 Procedure + +The procedure in figure 7.5.2.3.2-1 describes the case where an MCData user is downloading a file from the media storage function of the MCData content server. + +Pre-conditions: + +1. The MCData user on the MCData client 1 is registered for receiving MCData service. + +![Sequence diagram for file download using HTTP](1ca688982d625c3b8a8e382b675de466_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData content server + Note left of MCData client 1: 1. initiate download request + MCData client 1->>MCData content server: 2. MCData download data request + MCData content server-->>MCData client 1: 3. MCData download data response +``` + +The diagram illustrates the interaction for file download. It starts with a note '1. initiate download request' on the MCData client 1 lifeline. Then, a solid arrow labeled '2. MCData download data request' points from MCData client 1 to MCData content server. Finally, a dashed arrow labeled '3. MCData download data response' points from MCData content server back to MCData client 1. + +Sequence diagram for file download using HTTP + +**Figure 7.5.2.3.2-1: File download using HTTP** + +1. The user at the MCData client 1 initiates a file download request available at the indicated URL. +2. The file available at the URL (received in MCData FD request) is requested to be downloaded by the media storage client at the MCData client 1 from the media storage function on the MCData content server using a MCData download data request. + +3. The media storage function applies reception control policy and provides a MCData download data response including the file to the media storage client at MCData client 1. + +#### 7.5.2.4 One-to-one file distribution using HTTP + +##### 7.5.2.4.1 General + +The MCData client uses HTTP for a standalone data file download from another MCData client. The procedure is appropriate for both mandatory and non-mandatory download cases. + +##### 7.5.2.4.2 Procedure + +The procedure in figure 7.5.2.4.2-1 describes the case where an MCData user is initiating one-to-one data communication for sending file to the other MCData user, with or without download completed report request. + +Pre-conditions: + +1. The MCData users on the MCData client 1 and the MCData client 2 are already registered for receiving MCData service. +2. File to be distributed is uploaded to media storage function on MCData content server using the procedures defined in subclause 7.5.2.2. + +![Sequence diagram for One-to-one file distribution using HTTP. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2. The sequence starts with MCData client 1 sending an 'initiate data request' to the server. The server responds with 'MCData FD request' to client 2. Client 2 sends a 'Notify request' to the server. The server then sends 'MCData FD response' to client 2, which in turn sends 'Download file' to client 1. Finally, both clients send 'MCData download completed report' to the server.](62ee64afa2d368d732de66628cf2c841_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData FD request + Note right of MCData server: 3. Authorize request + Note right of MCData server: 4. Transmission/Reception control + MCData server->>MCData client 2: 5. MCData FD request + Note right of MCData client 2: 6. Notify request + MCData client 2->>MCData server: 7. MCData FD response + MCData server->>MCData client 1: 8. MCData FD response + Note right of MCData client 2: 9. Download file + MCData client 2->>MCData server: 10. MCData download completed report + MCData server->>MCData client 1: 11. MCData download completed report + +``` + +Sequence diagram for One-to-one file distribution using HTTP. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2. The sequence starts with MCData client 1 sending an 'initiate data request' to the server. The server responds with 'MCData FD request' to client 2. Client 2 sends a 'Notify request' to the server. The server then sends 'MCData FD response' to client 2, which in turn sends 'Download file' to client 1. Finally, both clients send 'MCData download completed report' to the server. + +**Figure 7.5.2.4.2-1: One-to-one file distribution using HTTP** + +1. The user at the MCData client 1 initiates a file distribution request to the chosen MCData user. +2. The MCData client 1 sends a MCData FD request towards the MCData server. The MCData FD request contains content payload in the form of file URL and may contain the file metadata information. The MCData FD request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData FD request contains conversation identifier for message thread indication. If MCData user at MCData client 1 has requested to mandatory download at the recipient side, then MCData FD request contains mandatory download indication. The MCData FD request may contain download completed report indication if selected by the user at MCData client 1. +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData FD request and that the size of the file is below maximum data size for FD from the service configuration. +4. The MCData server also applies transmission and reception control and the necessary policy to ensure that appropriate data is transmitted between the MCData UEs. +5. MCData server initiates the MCData FD request towards the MCData user. + +6. The receiving MCData client 2 notifies the user about the incoming MCData FD request (including file metadata, if present) which may be either accepted or rejected or ignored. If the request includes mandatory download indication in the MCData FD request an accepted response is assumed. +7. MCData user 2 may provide a response (accept or reject) or not (ignore) to the notification, then MCData client 2 sends the MCData FD response to the MCData server. MCData client 2 automatically sends accepted MCData FD response when the incoming request included mandatory download indication. +8. The MCData server forwards the MCData FD response to the MCData client 1. +9. MCData client 2 downloads the file using the procedures defined in subclause 7.5.2.3, either automatically (for mandatory download) or based upon the MCData user 2 subsequent acceptance. The MCData client 2 records file download completed and notifies MCData user 2. +10. MCData client 2 initiates a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1. +11. The MCData file download completed report from MCData user may be stored by the MCData server for download history interrogation from the authorized MCData users. MCData download completed report is sent by the MCData server to the user at MCData client 1. + +## 7.5.2.5 One-to-one file distribution using media plane + +### 7.5.2.5.1 General + +The MCData client uses the media plane for a standalone data file download from another MCData client. The procedure is appropriate for mandatory download case. + +### 7.5.2.5.2 Procedure + +The procedure in figure 7.5.2.5.2-1 describes the case where an MCData user is initiating one-to-one data communication for sending file to the other MCData user, with or without download completed report request. + +Pre-conditions: + +1. The MCData users on the MCData client 1 and the MCData client 2 are already registered for receiving MCData service. + +![Sequence diagram showing the flow of a one-to-one file distribution between MCData client 1, MCData server, and MCData client 2. Steps include data request initiation, FD requests, authorization, transmission control, FD responses, media plane file distribution, and download completed reports.](daf05db9f13b34fb12da52f007bbfe5b_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCData client 1 + participant S as MCData server + participant C2 as MCData client 2 + + Note over C1: 1. initiate data request + C1->>S: 2. MCData FD request + Note over S: 3. Authorize request + Note over S: 4. Transmission/Reception control + S->>C2: 5. MCData FD request + Note over C2: 6. Notify request + C2->>S: 7. MCData FD response + S->>C1: 8. MCData FD response + Note over C1,S: 9. file distribution over media plane + Note over S,C2: 10. file distribution over media plane + C2->>S: 11. MCData download completed report + S->>C1: 12. MCData download completed report + +``` + +Sequence diagram showing the flow of a one-to-one file distribution between MCData client 1, MCData server, and MCData client 2. Steps include data request initiation, FD requests, authorization, transmission control, FD responses, media plane file distribution, and download completed reports. + +**Figure 7.5.2.5.2-1: One-to-one file distribution using media plane** + +1. The user at the MCData client 1 initiates a file distribution request to the chosen MCData user. + +2. MCData client 1 sends a MCData FD request towards the MCData server. The MCData FD request may contain the file metadata information. The MCData FD request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData FD request contains conversation identifier for message thread indication. MCData FD request may contain mandatory download indication. The MCData FD request may contain download completed report indication if selected by the user at MCData client 1. +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData FD request. +4. The MCData server also applies transmission and reception control and the necessary policy to ensure that appropriate data is transmitted between the MCData UEs. +5. MCData server initiates the MCData FD request towards the MCData user. +6. The receiving MCData client 2 notifies the user about the incoming MCData FD request (including file metadata, if present) which may be either accepted or rejected or ignored. If the request includes mandatory download indication in the MCData FD request an accepted response is assumed. +7. If the target MCData user 2 provides a response (accept or reject) to the notification, then the MCData client 2 sends the MCData FD response to the MCData server. MCData client 2 automatically sends accepted MCData FD response when the incoming request included mandatory download indication. +8. MCData server forwards the MCData FD response from MCData client 2 back to MCData client 1. +9. MCData client 1 distributes the file over the established media plane to MCData server. +10. MCData server distributes the file received from MCData client 1 to MCData client 2 over the established media plane. File download report is shared by the MCData client 2, if requested by the user at MCData client 1. After file transaction is completed, the media plane is released. The MCData client 2 records file download completed and notifies MCData user 2. + +NOTE: MCData server is not required to wait for the complete download of file from MCData client 1 prior to initiating file distribution to MCData client 2. + +11. MCData client 2 initiates a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1. +12. The MCData file download completed report from MCData client may be stored by the MCData server for download history interrogation from the authorized MCData users. MCData download completed report is sent by the MCData server to the user at MCData client 1. + +## 7.5.2.6 Group standalone file distribution using HTTP + +### 7.5.2.6.1 General + +The initiation of a group standalone FD using HTTP to a selected group, results in affiliated group members receiving the file data. + +### 7.5.2.6.2 Procedure + +The procedure in figure 7.5.2.6.2-1 describes the case where an MCData user is initiating group standalone data communication for sending file to multiple MCData users, with or without download completed report request. + +Pre-conditions: + +1. The MCData users on the MCData client 1 to n belong to the same group and are already registered for receiving MCData service and affiliated. +2. File to be distributed is uploaded to media storage function on MCData content server using the procedures defined in subclause 7.5.2.2. + +![Sequence diagram illustrating Group standalone FD using HTTP. Lifelines: MCData client 1, MCData server, Group management server, and MCData client 2 to n. The sequence shows 12 steps: 1. initiate data request (client 1), 2. MCData group standalone FD request (client 1 to server), 3. Resolve group id (server to group management server), 4. Transmission/ Reception control (server), 5. MCData group standalone FD request (server to clients 2 to n), 6. Notify request (clients 2 to n), 7. MCData group standalone FD response (clients 2 to n to server), 8. MCData group standalone FD response (server to client 1), 9. Download file (clients 2 to n), 10. MCData download completed report (clients 2 to n to server), 11. Aggregate download completed report (server), 12. MCData download completed report (server to client 1).](7ed5d5770331f31ade15439a21c31425_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Group management server + participant MCData client 2 to n + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData group standalone FD request + MCData server->>Group management server: 3. Resolve group id + Note right of MCData server: 4. Transmission/ Reception control + MCData server->>MCData client 2 to n: 5. MCData group standalone FD request + Note right of MCData client 2 to n: 6. Notify request + MCData client 2 to n->>MCData server: 7. MCData group standalone FD response + MCData server->>MCData client 1: 8. MCData group standalone FD response + Note right of MCData client 2 to n: 9. Download file + MCData client 2 to n->>MCData server: 10. MCData download completed report + Note right of MCData server: 11. Aggregate download completed report + MCData server->>MCData client 1: 12. MCData download completed report + +``` + +Sequence diagram illustrating Group standalone FD using HTTP. Lifelines: MCData client 1, MCData server, Group management server, and MCData client 2 to n. The sequence shows 12 steps: 1. initiate data request (client 1), 2. MCData group standalone FD request (client 1 to server), 3. Resolve group id (server to group management server), 4. Transmission/ Reception control (server), 5. MCData group standalone FD request (server to clients 2 to n), 6. Notify request (clients 2 to n), 7. MCData group standalone FD response (clients 2 to n to server), 8. MCData group standalone FD response (server to client 1), 9. Download file (clients 2 to n), 10. MCData download completed report (clients 2 to n to server), 11. Aggregate download completed report (server), 12. MCData download completed report (server to client 1). + +**Figure 7.5.2.6.2-1: Group standalone FD using HTTP** + +1. The user at the MCData client 1 initiates a file distribution request to multiple MCData users selecting a pre-configured group (identified by MCData group ID) and optionally particular members from that group. +2. The MCData client 1 sends a MCData group standalone FD request towards the MCData server. The MCData FD request contains content payload in the form of file URL and may contain the file metadata information. The MCData group standalone data request contains target recipient(s) as selected by the user at MCData client 1. The MCData group standalone FD request contains conversation identifier for message thread indication. If MCData user at MCData client 1 has requested to mandatory download at the recipient side, then MCData group standalone FD request contains mandatory download indication. The MCData group standalone FD request may contain download completed report indication if selected by the user at MCData client 1. +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData group standalone FD request and that the size of the file is below maximum data size for FD from the group configuration. The MCData server resolves the MCData group ID to determine the members of that group and their affiliation status, based on the information from the group management server. +4. The MCData server also applies transmission and reception control and the necessary policy to ensure that appropriate data is transmitted between the MCData UEs. +5. MCData server initiates the MCData group standalone FD request towards each MCData user determined in step 3. +6. The receiving MCData clients 2 to n notify the user about the incoming MCData group standalone FD request (including file metadata, if present) which may be either accepted or rejected or ignored. If the request includes mandatory download indication in the MCData group standalone FD request an accepted response is assumed. +7. MCData user on MCData clients 2 to n provides a response (accept or reject or ignore) to the notification, then respective MCData client sends the MCData group standalone FD response to the MCData server. MCData client 2 to n automatically sends accepted MCData group standalone FD response when the incoming request included mandatory download indication. +8. The MCData server forwards the MCData group standalone FD response to the MCData client 1. + +NOTE: Step 8 can occur at any time following step 5, and prior to step 9 depending on the conditions to proceed with the file transmission. + +9. MCData client(s) downloads the file using the procedures defined in subclause 7.5.2.3, either automatically (for mandatory download) or based upon the MCData user subsequent acceptance. The MCData clients successfully receiving the file, records file download completed and notifies MCData user. +10. The MCData client(s), successfully receiving the file, initiate a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1. +11. The MCData file download completed report from MCData client(s) may be stored by the MCData server for download history interrogation from the authorized MCData users. The MCData file download completed report from each MCData user may be aggregated. +12. Aggregated or individual MCData download completed report is sent by the MCData server to the user at MCData client 1. + +### 7.5.2.7 Group standalone file distribution using media plane + +#### 7.5.2.7.1 General + +The initiation of a group standalone FD using media plane to a selected group, results in affiliated group members receiving the file data. + +#### 7.5.2.7.2 Procedure + +The procedure in figure 7.5.2.7.2-1 describes the case where an MCData user is initiating group standalone data communication for sending file to multiple MCData users, with or without download completed report request. + +Pre-conditions: + +1. The MCData users on the MCData client 1 to n belong to the same group and are already registered for receiving MCData service and affiliated. + +![Sequence diagram for Group standalone FD using media plane. Lifelines: MCData client 1, MCData server, Group management server, MCData client 2 to n. The process involves initiating a data request, resolving group ID, sending FD requests, distributing files over the media plane, and aggregating download completed reports.](3263a25e110201638bda790456af2909_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Group management server + participant MCData client 2 to n + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData group standalone FD request + MCData server->>Group management server: 3. Resolve group id + Note right of MCData server: 4. Transmission/ Reception control + MCData server->>MCData client 2 to n: 5. MCData group standalone FD request + Note right of MCData client 2 to n: 6. Notify request + MCData client 2 to n->>MCData server: 7. MCData group standalone FD response + MCData server->>MCData client 1: 8. MCData group standalone FD response + Note left of MCData server: 9. file distribution over media plane + Note right of MCData server: 10. file distribution over media plane + Note right of MCData client 2 to n: 11. Notify data + MCData client 2 to n->>MCData server: 12. MCData download completed report + Note right of MCData server: 13. Aggregate download completed reports + MCData server->>MCData client 1: 14. MCData download completed report + +``` + +Sequence diagram for Group standalone FD using media plane. Lifelines: MCData client 1, MCData server, Group management server, MCData client 2 to n. The process involves initiating a data request, resolving group ID, sending FD requests, distributing files over the media plane, and aggregating download completed reports. + +Figure 7.5.2.7.2-1: Group standalone FD using media plane + +1. The user at the MCData client 1 initiates a file distribution request to multiple MCData users selecting a pre-configured group (identified by MCData group ID) and optionally particular members from that group. +2. MCData client 1 sends a MCData group standalone FD request towards the MCData server. The MCData group standalone FD request may contain the file metadata information. The MCData group standalone data request contains target recipient(s) as selected by the user at MCData client 1. The MCData group standalone FD request contains conversation identifier for message thread indication. MCData group standalone FD request may contain mandatory download indication. The MCData group standalone FD request may contain download completed report indication if selected by the user at MCData client 1. +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData group standalone FD request. The MCData server resolves the MCData group ID to determine the members of that group and their affiliation status, based on the information from the group management server. +4. The MCData server also applies transmission and reception control and the necessary policy to ensure that appropriate data is transmitted between the MCData UEs. +5. MCData server initiates the MCData group standalone FD request towards each MCData user determined in step 3. +6. The receiving MCData clients 2 to n notifies the user about the incoming MCData group standalone FD request (including file metadata if present) which may be either accepted or rejected or ignored. If the request includes mandatory download indication in the MCData group standalone FD request an accepted response is assumed. +7. If the target MCData user on MCData clients 2 to n provides a response (accept or reject) to the notification, then the respective MCData client sends the MCData group standalone FD response to the MCData server. MCData client 2 to n automatically sends accepted MCData group standalone FD response when the incoming request included mandatory download indication. +8. MCData server forwards the MCData group standalone FD response to the MCData client 1. + +NOTE 1: Step 8 can occur at any time following step 5, and prior to step 9 depending on the conditions to proceed with the file transmission. + +9. MCData client 1 and MCData server have successfully established media plane for file transmission and the MCData client 1 transmits the file data. +10. MCData server distributes the file received from MCData client 1 to MCData clients 2 to n over the established media plane. Distribution of file can be via unicast or via MBMS bearer(s). For distribution via MBMS bearer(s), the procedure described in subclause 7.3 Use of MBMS transmission (on-network) is executed. File download report is shared by the receiving MCData clients, if requested by the user at MCData client 1. After file transaction is completed, the media plane is released. + +NOTE 2: MCData server is not required to wait for the complete download of file from MCData client 1 prior to initiating file distribution to MCData client 2. + +11. The MCData clients successfully receiving the file, records file download completed and notifies MCData user. +12. MCData client 2 initiates a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1. +13. The MCData file download completed report from MCData client(s) may be stored by the MCData server for download history interrogation from the authorized MCData users. The MCData file download completed report from each MCData user may be aggregated. +14. Aggregated or individual MCData file download completed report is sent to the disposition requesting user at MCData client 1. + +## 7.5.3 File distribution for off-network + +### 7.5.3.2 Information flows for file distribution + +#### 7.5.3.2.1 MCDATA FD request (using media plane) + +Table 7.5.3.2.1-1 describes the information flow for the MCDATA FD request sent from the MCDATA client to another MCDATA client. + +**Table 7.5.3.2.1-1: MCDATA FD request (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|-------------------------------------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user sending file | +| MCDATA ID | M | The identity of the MCDATA user receiving file | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCDATA transaction | +| Reply Identifier | O | Identifies the original MCDATA transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed reported is expected or not | +| Download indication | O | Indicates mandatory download | +| SDP offer | M | Media parameters offered | +| Content reference | M | URL reference to the content and file metadata information | + +#### 7.5.3.2.2 MCDATA FD response (using media plane) + +Table 7.5.3.2.2-1 describes the information flow for the MCDATA FD response sent from the MCDATA client to another MCDATA client. + +**Table 7.5.3.2.2-1: MCDATA FD response (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user sending FD request | +| MCDATA ID | M | The identity of the MCDATA user sending response | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | +| Acceptance confirmation | M | An indication whether the client has positively accepted the request | + +#### 7.5.3.2.3 MCDATA download completed report + +Table 7.5.3.2.3-1 describes the information flow for the MCDATA download completed report sent from the MCDATA client to another MCDATA client. + +**Table 7.5.3.2.3-1: MCDATA download completed report** + +| Information element | Status | Description | +|--------------------------|--------|--------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user sending FD request | +| MCDATA ID | M | The identity of the MCDATA user sending response | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCDATA transaction | +| Disposition association | M | Identifies the original MCDATA transaction | +| Disposition confirmation | M | An indication that the client has completed downloading file | + +#### 7.5.3.2.4 MCDATA group standalone FD request (using media plane) + +Table 7.5.3.2.4-1 describes the information flow for the MCDATA group standalone FD request sent from the MCDATA client to another MCDATA client. + +**Table 7.5.3.2.4-1: MCData group standalone FD request (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending file | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed reported is expected or not | +| Download indication | O | Indicates mandatory download | +| SDP offer | M | Media parameters offered | +| Content reference | M | URL reference to the content and file metadata information | + +### 7.5.3.2.5 MCData group standalone FD response (using media plane) + +Table 7.5.3.2.5-1 describes the information flow for the MCData group standalone FD response sent from the MCData client to another MCData client. + +**Table 7.5.3.2.5-1: MCData group standalone FD response (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData group ID | M | The MCData group ID to which the file is to be sent | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | +| Acceptance confirmation | M | An indication whether the client has positively accepted the request | + +### 7.5.3.3 One-to-one standalone file distribution using media plane + +#### 7.5.3.3.1 General + +The MCData client uses media plane for a standalone FD download from another MCData client in off-network. + +#### 7.5.3.3.2 Procedure + +Figure 7.5.3.3.2-1 describes procedures for an off-network MCData client 1 initiating one-to-one MCData data communication for sending standalone FD data to other MCData client, with or without download completed report request. + +Pre-conditions: + +1. MCData user 1 has initiated communication for sending standalone FD data to other MCData user 2. +2. MCData client 1 and MCData client 2 are members of the same **ProSe** Discovery group and are **ProSe** 1:1 direct communication capable. +3. MCData client 1 has discovered MCData client 2 in proximity, associated with MCData user 2, using **ProSe** Discovery procedures. + +![Sequence diagram illustrating one-to-one standalone file distribution using media plane between MCData client 1 and MCData client 2.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + Note right of MCData client 2: 2. Assert policy + Note right of MCData client 2: 3. Notify request + MCData client 1->>MCData client 2: 1. MCData FD request + MCData client 2->>MCData client 1: 4. MCData FD response + Note over MCData client 1, MCData client 2: 5. file distribution over media plane + MCData client 2->>MCData client 1: 6. MCData download completed report + +``` + +The diagram shows a sequence of interactions between MCData client 1 and MCData client 2. + 1. MCData client 1 sends an 'MCData FD request' to MCData client 2. + 2. MCData client 2 performs an 'Assert policy' step (shown in a box). + 3. MCData client 2 sends a 'Notify request' (shown in a dashed box). + 4. MCData client 2 sends an 'MCData FD response' back to MCData client 1. + 5. A thick green arrow labeled 'file distribution over media plane' points from MCData client 1 to MCData client 2. + 6. MCData client 2 sends an 'MCData download completed report' back to MCData client 1. + +Sequence diagram illustrating one-to-one standalone file distribution using media plane between MCData client 1 and MCData client 2. + +**Figure 7.5.3.3.2-1: One-to-one standalone file distribution using media plane** + +1. MCData client 1 sends a MCData FD request towards the MCData client 2. The MCData FD request may contain the file metadata information. The MCData FD request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData FD request contains conversation identifier for message thread indication. MCData FD request may contain mandatory download indication. The MCData FD request may contain download completed report indication if selected by the user at MCData client 1. +2. On receiving a MCData FD request, the MCData client 2 checks whether any policy is to be asserted to limit certain types of message or content to certain members, for example, due to location or user privilege. +3. The receiving MCData client 2 notifies the user about the incoming MCData FD request (including file metadata if present) which may be either accepted or rejected or ignored. MCData user may not be sought consent if the request includes mandatory download indication in the MCData FD request and instead only notify the MCData user about file downloading. +4. If the target MCData user 2 provides a response (accept or reject) to the notification, then the MCData client 2 sends the MCData FD response to the MCData client 1. MCData client 2 automatically sends accepted MCData FD response when the incoming request included mandatory download indication. +5. MCData client 1 distributes the file over the established media plane to MCData client 2. +6. The MCData client 2 records file download completed and notifies MCData user 2. MCData client 2 initiates a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1. + +### 7.5.3.4 Group standalone file distribution using media plane + +#### 7.5.3.4.1 General + +The initiation of a group standalone FD to a selected group results in off-network MCData group members receiving the file data. + +#### 7.5.3.4.2 Procedure + +Figure 7.5.3.4.2-1 describes procedures for an off-network MCData client 1 initiating group MCData data communication for sending FD data to a MCData group, with or without download completed report request. + +Pre-conditions: + +1. MCData user 1 has initiated group communication for sending FD data to the MCData group. + +2. Information for ProSe direct communications corresponding to the MCData group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCData client 1. +3. MCData client 1 to MCData client N are members of the same MCData group. + +![Sequence diagram illustrating Group standalone file distribution using media plane. The diagram shows interactions between MCData client 1, MCData client 2, and MCData client N. The process involves: 1. MCData client 1 sends a standalone FD request to the group. 2. Clients 2 to N assert policy. 3. Clients 2 to N send notify requests. 4. Clients 2 to N send standalone FD responses. 5. File distribution occurs over the media plane. 6. Clients 2 to N notify data. 7. Clients 2 to N send download completed reports.](376f80eb8a41369e87da63a0210d173e_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + participant MCData client N + Note right of MCData client 2: 2. Assert policy + Note right of MCData client N: 2. Assert policy + Note right of MCData client 2: 3. Notify request + Note right of MCData client N: 3. Notify request + Note right of MCData client 1: 5. File distribution over media plane + Note right of MCData client 2: 6. Notify data + Note right of MCData client N: 6. Notify data + + MCData client 1->>MCData client N: 1. MCData group standalone FD request + MCData client N->>MCData client 2: 2. Assert policy + MCData client 2->>MCData client N: 2. Assert policy + MCData client N->>MCData client 2: 3. Notify request + MCData client 2->>MCData client N: 3. Notify request + MCData client 2->>MCData client 1: 4. MCData group standalone FD response + MCData client N->>MCData client 1: 4. MCData group standalone FD response + MCData client 1->>MCData client N: 5. File distribution over media plane + MCData client N->>MCData client 2: 6. Notify data + MCData client 2->>MCData client N: 6. Notify data + MCData client N->>MCData client 1: 7. MCData download completed report + MCData client 2->>MCData client 1: 7. MCData download completed report + +``` + +Sequence diagram illustrating Group standalone file distribution using media plane. The diagram shows interactions between MCData client 1, MCData client 2, and MCData client N. The process involves: 1. MCData client 1 sends a standalone FD request to the group. 2. Clients 2 to N assert policy. 3. Clients 2 to N send notify requests. 4. Clients 2 to N send standalone FD responses. 5. File distribution occurs over the media plane. 6. Clients 2 to N notify data. 7. Clients 2 to N send download completed reports. + +**Figure 7.5.3.4.2-1: Group standalone file distribution using media plane** + +1. MCData client 1 sends a MCData FD request towards the MCData group. The MCData group standalone FD request may contain the file metadata information. The MCData group standalone data request contains MCData group ID as selected by the user at MCData client 1. The MCData group standalone FD request contains conversation identifier for message thread indication. MCData group standalone FD request may contain mandatory download indication. The MCData group standalone FD request may contain download completed report indication if selected by the user at MCData client 1. +2. On receiving a MCData FD request, the MCData clients check whether any policy is to be asserted to limit certain types of message or content to certain members, for example, due to location or user privilege. +3. If the policy assertion is positive, the receiving MCData clients 2 to n notifies the user about the incoming MCData group standalone FD request (including file metadata if present) which may be either accepted or rejected or ignored. MCData user may not be sought consent if the request includes mandatory download indication in the MCData group standalone FD request and instead only notify the MCData user about file downloading. +4. If the target MCData user on MCData clients 2 to n provides a response (accept or reject) to the notification, then the respective MCData client sends the MCData group standalone FD response to the MCData client 1. MCData client 2 to n automatically sends accepted MCData group standalone FD response when the incoming request included mandatory download indication. +5. MCData client 1 and MCData client 2 to n have successfully established media plane for file transmission and the MCData client 1 transmits the file data. +6. The MCData client 2 to n successfully receiving the file, records file download completed and notifies MCData users. +7. MCData client 2 to n initiate a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1. + +## 7.6 Transmission and reception control + +### 7.6.1 General + +Based on the configurations (available in MC data user profile, group configuration and service configuration), the MC data transmission and reception control provides a necessary capability for an authorized user of the MC data service to transmit, receive notification messages due to various trigger conditions, advocates reception mode and terminate transmission when there is no longer a need to transmit. The subclauses below describe the transmission and reception control procedures using signalling control plane. + +### 7.6.2 Transmission and reception control for on-network + +#### 7.6.2.1 Information flows for transmission and reception control + +##### 7.6.2.1.1 MCData control indication + +Table 7.6.2.1.1-1 describes the information flow for the MCData control indication sent from the MCData server to the MCData client. + +**Table 7.6.2.1.1-1: MCData control indication** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the control indication is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Control indication type | M | One of the following:<br>- No permission to transmit data<br>- No affiliated members found to the selected MCData group<br>- Rejected due to exceeding data transmit size<br>- Rejected due to exceeding data transmit time<br>- Request to transmit is queued | + +##### 7.6.2.1.2 MCData indication + +Table 7.6.2.1.2-1 describes the information flow for the MCData indication sent from the MCData server to the MCData client. + +**Table 7.6.2.1.2-1: MCData indication** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the control indication is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Control indication type | O | One of the following:<br>- No permission to transmit data<br>- No affiliated members found to the selected MCData group<br>- Rejected due to exceeding data transmit size<br>- Rejected due to exceeding data transmit time<br>- Request to transmit is queued<br>- Data expired and not available to download anymore | +| Deferred data list | O | List of references to deferred data awaiting download | + +##### 7.6.2.1.3 MCData get deferred list request + +Table 7.6.2.1.3-1 describes the information flow for the MCData get deferred list request sent from the MCData client to the MCData server. + +**Table 7.6.2.1.3-1: MCData get deferred list request** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting deferred list | + +#### 7.6.2.1.4 MCData get deferred list response + +Table 7.6.2.1.4-1 describes the information flow for the MCData get deferred list response sent from the MCData server to the MCData client. + +**Table 7.6.2.1.4-1: MCData get deferred list response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting deferred list | +| Deferred data list | M | List of references to deferred data awaiting download | + +#### 7.6.2.2 Automatic transmission for SDS + +##### 7.6.2.2.1 General + +When SDS message is sent, the data is transferred from the sending MCData client to the receiving MCData client without any request/grant procedure or any explicit actions on the part of the receiving MCData client. + +##### 7.6.2.2.2 Procedure + +The procedure in figure 7.6.2.2.2-1 describes the case where MC Data SDS is automatically transmitted to the selected recipient user or affiliated members of the selected MC Data group. + +Pre-conditions: + +1. MCData user is configured with permission to transmit data. + +![Sequence diagram for Automatic transmission for SDS. Lifelines: MCData client 1, MCData server, MCData client 2. Steps: 1. initiate data transmit (client 1 to server), 2. MCData transmission to MCData server (client 1 to server), 3. Authorize request and size check for auto-send (server internal), 4. MCData control indication (server to client 1), 5. MCData delivery to recipient(s) (server to client 2).](d5d5c87be8e612be9d06d406bc894fd5_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. initiate data transmit + MCData client 1->>MCData server: 2. MCData transmission to MCData server + Note right of MCData server: 3. Authorize request and size check for auto-send + MCData server-->>MCData client 1: 4. MCData control indication + Note right of MCData server: 5. MCData delivery to recipient(s) + MCData server->>MCData client 2: + +``` + +Sequence diagram for Automatic transmission for SDS. Lifelines: MCData client 1, MCData server, MCData client 2. Steps: 1. initiate data transmit (client 1 to server), 2. MCData transmission to MCData server (client 1 to server), 3. Authorize request and size check for auto-send (server internal), 4. MCData control indication (server to client 1), 5. MCData delivery to recipient(s) (server to client 2). + +**Figure 7.6.2.2.2-1: Automatic transmission for SDS** + +1. MCData user selects the data to transmit and the recipient MCData user or MCData group. +2. MCData client checks for MCData user's permission to transmit data, and checks if the data size is less than the maximum data size for SDS. MCData client calculates the total transmission request size and determines to select one of the appropriate procedure described in subclause 7.4.2.2, 7.4.2.3, 7.4.2.5 or 7.4.2.6. +3. Transmission control on the server verifies if the MCData user is authorized to transmit and the data size in the received transmission request is less than the maximum data size for SDS. + +4. MCData server may send one of the following MCData control indications: + - a) If the MCData user does not have permission to transmit data to another MC Data user or MC Data group then the "No permission to transmit data" control indication is sent. + - b) If the selected transmission is for a MCData group and there are no affiliated group members, then the transmission control on MCData server sends the "No affiliated members found to the selected MCData group" control indication. +- Otherwise continue with step 5. +5. MCData server automatically transmits the data to the selected MCData user or the affiliated members of the selected MCData group according to the procedures selected in step 2. + +### 7.6.2.3 Send data with mandatory download + +#### 7.6.2.3.1 General + +The mandatory download procedure allows a sending MCData client to send data to a receiving MCData client, where the receiving MCData client is compelled to download the data. + +#### 7.6.2.3.2 Procedure + +The procedure in figure 7.6.2.3.2-1 describes the case where MCData user is using FD. The FD is subjected to transmission control prior to transmitting data to the selected recipient user or affiliated members of the selected MCData group for mandatory download. + +Pre-conditions: + +1. MC Data user is configured with permission to transmit data. +2. MC Data administrator has configured maximum data size for FD. +3. Maximum amount of data that a MC Data user can transmit in a single request is configured. +4. Maximum amount of time that a MC Data user can transmit in a single request is configured. + +![Sequence diagram showing the interaction between MCData client 1, MCData server, and MCData client 2 for a mandatory download. Step 1: MCData client 1 initiates data transmit. Step 2: MCData transmission to MCData server. Step 3: Authorize request and size check for non automatic transmission. Step 4: MCData control indication. Step 5: Mandatory download transmission to recipient(s).](d78e519e9186d30807342196675fd440_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. initiate data transmit + MCData client 1->>MCData server: 2. MCData transmission to MCData server + Note right of MCData server: 3. Authorize request and size check for non automatic transmission + MCData server-->>MCData client 1: 4. MCData control indication + Note right of MCData server: 5. Mandatory download transmission to recipient(s) + +``` + +Sequence diagram showing the interaction between MCData client 1, MCData server, and MCData client 2 for a mandatory download. Step 1: MCData client 1 initiates data transmit. Step 2: MCData transmission to MCData server. Step 3: Authorize request and size check for non automatic transmission. Step 4: MCData control indication. Step 5: Mandatory download transmission to recipient(s). + +Figure 7.6.2.3.2-1: Send data with mandatory download + +1. MCData user selects the data to transmit, the recipient MCData user or MCData group and the indication for mandatory download. +2. MCData client has checked for MCData user's permission to transmit data. MCData client calculates the total transmission request size and determines to select one of the appropriate procedures described in subclause 7.5.2.4, 7.5.2.5, 7.5.2.6 or 7.4.2.7 and including the mandatory download indication. +3. Transmission control on the server verifies if the MCData user is authorized to transmit and the data size in the received transmission request is within the maximum size allowed for FD transmission. +4. MCData server may send one of the following MCData control indications: + +- a) If the MCData user does not have permission to transmit data to another MC Data user or MC Data group then the "No permission to transmit data" control indication is sent. +- b) If the data size requested to be transmitted is more than the maximum amount of data that an MCData user can transmit in a single request, the transmission control on MCData server rejects the data transmission request and sends the rejection control indication "Rejected due to exceeding data transmit size". +- c) If the data transmission time exceeds the maximum amount of time that an MCData user can transmit in a single request, the transmission control on MCData server rejects the data transmission request and sends the rejection control indication "Rejected due to exceeding data transmit time". +- d) If the selected transmission is for a MCData group and there are no affiliated group members, then the transmission control on MCData server sends the "No affiliated members found to the selected MCData group" control indication. +- e) MCData server may queue the data transmit request for later transmission with control indication "Request to transmit is queued". + +Otherwise continue with step 5. + +5. MCData server transmits the data to the selected MCData user or the affiliated members of the selected MCData group according to the procedures selected in step 2 (where the recipient MCData client receives the data automatically). + +#### 7.6.2.4 Send data without mandatory download + +##### 7.6.2.4.1 General + +The send data without mandatory download procedure allows the receiving MCData client to accept download, defer download (i.e. no response) or refuse (e.g. by the user deleting the notification item) the data sent from the sending MCData client. + +##### 7.6.2.4.2 Procedure + +The procedure in figure 7.6.2.4.2-1 describes the case where MCData user selected data is subjected to transmission control prior to transmitting data to the selected recipient user or affiliated members of the selected MCData group for downloading with recipient MCData user consent. + +Pre-conditions: + +1. MCData user is configured with permission to transmit data. +2. Maximum amount of data or time that an MCData user can transmit in a single request is configured. +3. Time limit for the temporarily stored data waiting to be delivered to a receiving user is configured. + +![Sequence diagram for 'Send data without mandatory download' showing interactions between MCData client 1, MCData server, and MCData client 2.](ef8f4838401ece0abd51d63b897fa388_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. initiate data transmit + MCData client 1->>MCData server: 2. MCData transmission to MCData server + Note right of MCData server: 3. Authorize request and size check for non automatic transmission + MCData server-->>MCData client 1: 4. MCData indication + Note right of MCData server: 5. Transmission to recipient(s) for downloading after user consent + MCData server-->>MCData client 2: 6. MCData indication + +``` + +Sequence diagram for 'Send data without mandatory download' showing interactions between MCData client 1, MCData server, and MCData client 2. + +Figure 7.6.2.4.2-1: Send data without mandatory download + +1. MCData user selects the data to transmit and the recipient MCData user or MCData group and does not select the mandatory download indication. + 2. MCData client has checked for MCData user's permission to transmit data and the data size is within the maximum data size allowed. The MCData client calculates the total transmission request size and determines to select procedure described in subclause 7.5.2.4 or 7.5.2.6 and without including the mandatory download indication. + 3. Transmission control on the server verifies if the MCData user is authorized to transmit and the data size in the received transmission request is within the maximum data size allowed. + 4. MCData server sends control indication appropriate to trigger condition: + - a) If the MCData user does not have permission to transmit data to another MC Data user or MC Data group then the "No permission to transmit data" control indication is sent. + - b) If the selected transmission is for a MCData group and there are no affiliated group members, then the transmission control on MCData server sends the "No affiliated members found to the selected MCData group" control indication. + - c) If the data size requested to be transmitted is more than the maximum amount of data that an MCData user can transmit in a single request, the transmission control on MCData server rejects the data transmission requests and sends the rejection control indication "Rejected due to exceeding data transmit size". + - d) If the data transmission time exceeds the maximum amount of time that an MCData user can transmit in a single request (applies to DS only), the transmission control on MCData server rejects the data transmission request and sends the rejection control indication "Rejected due to exceeding data transmit time". + - e) MCData server may queue the data transmit request for later transmission with a control indication "Request to transmit is queued". +- Otherwise, continue with step 5. +5. If the temporarily stored data has not expired, the MCData server transmits the data to the selected MCData user or the affiliated members of the selected MCData group according to the procedures selected in step 2 (where the recipient MCData client may receive the data automatically). + 6. Otherwise, MCData server sends MCData control indication appropriate to trigger condition: + - a) If the timer expired for periodic announcement with the list of available recently invited data group communications, the recipient MCData client waiting to receive the temporarily stored data receives control indication with "List of available temporarily stored data waiting to download". + - b) If the temporarily stored data is expired, the data may be purged from the temporary store and the recipient MCData user is informed with control indication "Data expired and not available to download anymore". + +## 7.6.2.5 Accessing list of deferred data group communications + +### 7.6.2.5.1 General + +This procedure allows an MCData client to obtain a list of deferred data communications. + +### 7.6.2.5.2 Procedure + +The procedure in figure 7.6.2.5.2-1 describes the case where the recipient MCData client receives the list of available temporarily stored data waiting to download for the deferred data group communications. + +Pre-conditions: + +1. MCData server has temporarily stored data for the deferred data group communications e.g. due to recipient MCData client deferred to download. + +![Sequence diagram showing the interaction between an MCData client and an MCData server to access a list of deferred data group communications. The client initiates a request, the server responds, and the client then notifies the user.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + Note left of MCData client 1: 1. Get the list of deferred data group communications + MCData client 1->>MCData server: 2. MCData get deferred list request + MCData server-->>MCData client 1: 3. MCData get deferred list response + Note left of MCData client 1: 4. Notify + +``` + +Sequence diagram showing the interaction between an MCData client and an MCData server to access a list of deferred data group communications. The client initiates a request, the server responds, and the client then notifies the user. + +**Figure 7.6.2.5.2-1: Accessing list of deferred data group communications** + +1. MCData user initiates the request to get the list of temporarily stored data for the deferred data group communications on the MCData server e.g. due to recipient MCData client deferred to download. +2. MCData client sends a MCData get deferred list request to the MCData server. +3. MCData server generates the list of temporarily stored data for the affiliated group(s), available to download for the requesting MCData client and sends the list in the MCData get deferred list response. +4. MCData client notifies the list of temporarily stored data for the deferred data group communications, upon which the MCData user may decide to retrieve the corresponding data. + +## 7.7 Communication release + +### 7.7.1 General + +The subclauses below describe the MCData communication release procedures, which may be initiated either by the sender or the MCData server or the authorized MCData user. + +### 7.7.2 Communication release for on-network + +#### 7.7.2.1 Information flows for communication release + +##### 7.7.2.1.1 MCData communication release request (one-to-one communication using media plane) + +Table 7.7.2.1.1-1 describes the information flow for the MCData communication release request (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.7.2.1.1-1: MCData communication release request (one-to-one communication using media plane)** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------| +| MCData ID | M | The identity of the MCData user uploading data | +| MCData ID | M | MCData ID on which the communication is to be released | + +##### 7.7.2.1.2 MCData communication release response (one-to-one communication using media plane) + +Table 7.7.2.1.2-1 describes the information flow for the MCData communication release response (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.7.2.1.2-1: MCData communication release response (one-to-one communication using media plane)** + +| Information element | Status | Description | +|----------------------|--------|-----------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting to upload data | +| MCData ID | M | MCData ID on which the communication is released | +| Release confirmation | M | Communication released or not indication | + +#### 7.7.2.1.3 MCData communication release request (group communication using media plane) + +Table 7.7.2.1.3-1 describes the information flow for the MCData communication release request (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.7.2.1.3-1: MCData communication release request (group communication using media plane)** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user uploading data | +| MCData group ID | M | MCData group ID on which the communication is to be released | + +#### 7.7.2.1.4 MCData communication release response (group communication using media plane) + +Table 7.7.2.1.4-1 describes the information flow for the MCData communication release response (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.7.2.1.4-1: MCData communication release response (group communication using media plane)** + +| Information element | Status | Description | +|----------------------|--------|-----------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting to upload data | +| MCData group ID | M | MCData group ID on which the communication is released | +| Release confirmation | M | Communication released or not indication | + +#### 7.7.2.1.5 MCData communication release request (communication using HTTP) + +Table 7.7.2.1.5-1 describes the information flow for the MCData communication release request (in subclause 7.7.2.2.3.2) sent from the MCData client to the MCData server. + +**Table 7.7.2.1.5-1: MCData communication release request (communication using HTTP)** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user uploading data | +| URL reference | M | File URL reference on which the communication is to be released | + +#### 7.7.2.1.6 MCData communication release response (communication using HTTP) + +Table 7.7.2.1.6-1 describes the information flow for the MCData communication release response (in subclause 7.7.2.2.3.2) sent from the MCData server to the MCData client. + +**Table 7.7.2.1.6-1: MCData communication release response (communication using HTTP)** + +| Information element | Status | Description | +|----------------------|--------|-----------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting to upload data | +| Release confirmation | M | Communication released or not indication | + +#### 7.7.2.1.7 Data not available control indication + +Table 7.7.2.1.7-1 describes the information flow for the data not available control indication (in subclause 7.7.2.2.3 and 7.7.2.3.3) sent from the MCData server to the MCData client. + +**Table 7.7.2.1.7-1: Data not available control indication** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving file URL reference | +| Conversation Identifier | M | Identifies the conversation | +| URL reference | M | Indicates URL reference of the file that is not available to download | + +#### 7.7.2.1.8 MCData server communication release request (one-to-one communication using media plane) + +Table 7.7.2.1.8-1 describes the information flow for MCData server communication release request (in subclause 7.7.2.3.2.2) sent from the MCData server to the MCData clients involved in one-to-one communication. + +**Table 7.7.2.1.8-1: MCData server communication release request (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|--------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user to which communication is released | +| Conversation Identifier | M | Identifies the conversation | +| Release Reason | M | Indicates reason for the release | + +#### 7.7.2.1.9 MCData server communication release response (one-to-one communication using media plane) + +Table 7.7.2.1.9-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.3.2.2) sent from the MCData client to the MCData server. + +**Table 7.7.2.1.9-1: MCData server communication release response (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|--------------------------------------------------| +| MCData ID | M | MCData ID to which the communication is released | +| Conversation Identifier | M | Identifies the conversation | +| Release confirmation | M | Communication released or not indication | + +#### 7.7.2.1.10 MCData server communication release request (group communication using media plane) + +Table 7.7.2.1.10-1 describes the information flow for MCData server communication release request (in subclause 7.7.2.3.2.2) sent from the MCData server to the MCData clients involved in group communication. + +**Table 7.7.2.1.10-1: MCData server communication release request (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|--------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user to which communication is released | +| MCData group ID | M | MCData group ID on which the communication is released | +| Conversation Identifier | M | Identifies the conversation | +| Release Reason | M | Indicates reason for the release | + +#### 7.7.2.1.11 MCData server communication release response (group communication using media plane) + +Table 7.7.2.1.11-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.3.2.2) sent from the MCData client to the MCData server. + +**Table 7.7.2.1.11-1: MCData server communication release response (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|--------------------------------------------------------| +| MCData ID | M | MCData ID to which the communication is released | +| MCData group ID | M | MCData group ID on which the communication is released | +| Conversation Identifier | M | Identifies the conversation | +| Release confirmation | M | Communication released or not indication | + +#### 7.7.2.1.12 MCData server communication release indication (communication using HTTP) + +Table 7.7.2.1.12-1 describes the information flow for MCData server communication release indication (in subclause 7.7.2.3.3.2) sent from the MCData server to the MCData client uploading the file data. + +**Table 7.7.2.1.12-1: MCData server communication release indication (communication using HTTP)** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user to which communication is released | +| URL reference | M | File URL reference on which the communication is to be released | +| Release Reason | M | Indicates reason for the release | + +#### 7.7.2.1.13 MCData release intent request (one-to-one communication using media plane) + +Table 7.7.2.1.13-1 describes the information flow for MCData release intent request (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData server to the MCData client. + +**Table 7.7.2.1.13-1: MCData release intent request (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user who is originator of the one-to-one communication | +| Conversation Identifier | M | Identifies the conversation | +| Request for more info | O | Indicates what MCData server needs more information (e.g. to know the remaining data volume to transmit) about the communication which has been identified to be released | + +#### 7.7.2.1.14 MCData more information response (one-to-one communication using media plane) + +Table 7.7.2.1.14-1 describes the information flow for MCData more information response (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData client to the MCData server and from MCData server to authorized MCData user. + +**Table 7.7.2.1.14-1: MCData more information response (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user who is originator of the one-to-one communication | +| Conversation Identifier | M | Identifies the conversation | +| More info | M | Information as requested by MCData server | + +#### 7.7.2.1.15 MCData release intent request (group communication using media plane) + +Table 7.7.2.1.15-1 describes the information flow for MCData release intent request (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData server to the MCData client. + +**Table 7.7.2.1.15-1: MCData release intent request (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user who is the originator of the group communication | +| Conversation Identifier | M | Identifies the conversation | +| MCData group ID | M | MCData group ID on which the communication is released | +| Request for more info | O | Indicates what MCData server needs more information about the communication which has been identified to be released | + +#### 7.7.2.1.16 MCData more information response (group communication using media plane) + +Table 7.7.2.1.16-1 describes the information flow for MCData more information response (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData client to the MCData server and from MCData server to authorized MCData user. + +**Table 7.7.2.1.16-1: MCData more information response (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user who is originator of the group communication | +| Conversation Identifier | M | Identifies the conversation | +| MCData group ID | M | MCData group ID on which the communication is released | +| More info | M | Information as requested by MCData server | + +#### 7.7.2.1.17 MCData auth user communication release request (one-to-one communication using media plane) + +Table 7.7.2.1.17-1 describes the information flow for MCData auth user communication release request (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the authorized MCData user to the MCData server. + +**Table 7.7.2.1.17-1: MCData auth user communication release request (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| Request for more info | O | Indicates what MCData server needs more information about the communication which has been identified to be released | +| Release Reason | M | Indicates reason for the release | + +#### 7.7.2.1.18 MCData auth user communication release response (one-to-one communication using media plane) + +Table 7.7.2.1.18-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the MCData server to the authorized MCData user. + +**Table 7.7.2.1.18-1: MCData auth user communication release response (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| Release confirmation | M | Communication released or not indication | + +**7.7.2.1.19 MCData auth user communication release request (group communication using media plane)** + +Table 7.7.2.1.19-1 describes the information flow for MCData auth user communication release request (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the authorized MCData user to the MCData server. + +**Table 7.7.2.1.19-1: MCData auth user communication release request (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| MCData group ID | M | MCData group ID on which the communication is to be released | +| Request for more info | O | Indicates what MCData server needs more information about the communication which has been identified to be released | +| Release Reason | M | Indicates reason for the release | + +**7.7.2.1.20 MCData auth user communication release response (group communication using media plane)** + +Table 7.7.2.1.20-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the MCData server to the authorized MCData user. + +**Table 7.7.2.1.20-1: MCData auth user communication release response (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|--------------------------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| MCData group ID | M | MCData group ID on which the communication is to be released | +| Release confirmation | M | Communication released or not indication | + +**7.7.2.1.21 MCData request for extension** + +Table 7.7.2.1.21-1 describes the information flow for the MCData request for extension (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData client to the MCData server and from MCData server to authorized MCData user. + +**Table 7.7.2.1.21-1: MCData request for extension** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------| +| Conversation Identifier | M | Identifies the conversation | + +**7.7.2.1.22 MCData response for extension** + +Table 7.7.2.1.22-1 describes the information flow for the MCData response for extension (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the authorized MCData user to the MCData server and MCData client to the MCData server and from MCData server to MCData client. + +**Table 7.7.2.1.22-1: MCData response for extension** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| Extension response | M | Indicates whether request for extension has been accepted or not | + +## 7.7.2.2 MCData user initiated communication release + +### 7.7.2.2.1 General + +During MCData communication, a transmitting participant can at any time indicate to stop transmission to the MCData server. + +### 7.7.2.2.2 Release of MCData communication using media plane + +#### 7.7.2.2.2.1 General + +The subclause describes the procedure for MCData user initiated MCData communication release where MCData communication is established as SDS using media plane or SDS session or file distribution using media plane. + +**Editor's note:** Release of MCData communication over MBMS is FFS. + +#### 7.7.2.2.2.2 Procedure + +The procedure in figure 7.7.2.2.2.2-1 describes signalling control plane procedure for the case where MCData communication is ongoing and transmitting participant initiates MCData communication release. The procedure is applicable for one-to-one and group MCData communications. + +Pre-conditions: + +1. MCData users on MCData client 1 and client 2 are already registered for receiving MCData service. +2. MCData communication is established between MCData client 1 and MCData client 2 and MCData client1 is the initiator of the MCData communication. + +![Sequence diagram showing the release of MCData communication using media plane. The diagram involves three lifelines: MCData client 1, MCData server, and MCData client 2. The sequence of messages is: 1. Initiate communication termination (from client 1 to server), 2. MCData communication release request (from client 1 to server), 3. MCData communication release request (from server to client 2), 4. Notify user (from client 2 to server), 5. MCData communication release response (from client 2 to server), 6. MCData communication release response (from server to client 1), 7. Release media plane resources associated with MCData communication (internal server action), 8. Notify user (from server to client 1).](279ae82c0ef66d5fb9a204a4218a78dc_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. Initiate communication termination + MCData client 1->>MCData server: 2. MCData communication release request + MCData server->>MCData client 2: 3. MCData communication release request + Note right of MCData client 2: 4. Notify user + MCData client 2->>MCData server: 5. MCData communication release response + MCData server->>MCData client 1: 6. MCData communication release response + Note over MCData server: 7. Release media plane resources associated with MCData communication + Note left of MCData client 1: 8. Notify user + +``` + +Sequence diagram showing the release of MCData communication using media plane. The diagram involves three lifelines: MCData client 1, MCData server, and MCData client 2. The sequence of messages is: 1. Initiate communication termination (from client 1 to server), 2. MCData communication release request (from client 1 to server), 3. MCData communication release request (from server to client 2), 4. Notify user (from client 2 to server), 5. MCData communication release response (from client 2 to server), 6. MCData communication release response (from server to client 1), 7. Release media plane resources associated with MCData communication (internal server action), 8. Notify user (from server to client 1). + +**Figure 7.7.2.2.2.2-1: Release of MCData communication using media plane** + +1. MCData user at MCData client 1 requests to release ongoing MCData communication. + +2. MCData client 1 sends MCData communication release request towards MCData server, for tearing down the communication with the other MCData client(s). +3. MCData server sends MCData communication release request to all the participants of the MCData communication. +4. Recipient MCData clients notifies respective MCData user about the release of MCData communication. +5. MCData clients receiving the MCData communication release request provide communication release response back towards MCData server. +6. MCData server sends MCData communication release response back to MCData client 1. +7. All participants of the MCData communication have successfully released the media plane resources associated with the MCData communication that is released. +8. MCData client 1 notifies the MCData user about the communication release. + +### 7.7.2.2.3 Release of MCData communication using HTTP + +#### 7.7.2.2.3.1 General + +The subclause describes the procedure for MCData user initiated MCData communication release where MCData communication is established with procedures for file distribution using HTTP. + +#### 7.7.2.2.3.2 Procedure + +The procedure in figure 7.7.2.2.3.2-1 describes signalling control plane procedure for the case where MCData communication is ongoing and transmitting participant initiates MCData communication release. The procedure is applicable for one-to-one and group MCData communications. + +Pre-conditions: + +1. MCData users on MCData client 1 and client 2 are already registered for receiving MCData service +2. MCData client 1 is transmitting file to other MCData client(s). + +![Sequence diagram showing the release of MCData communication using HTTP between MCData client 1, MCData server, and MCData client 2. The steps are: 1. Initiate communication termination (internal to client 1), 2. MCData communication release request (client 1 to server), 3. Remove the file data (internal to server), 4. MCData communication release response (server to client 1), 5. Data not available control indication (server to client 2), 6. Notify user (internal to client 1).](b882c54d92390b4ca523f230e3e07617_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. Initiate communication termination + MCData client 1->>MCData server: 2. MCData communication release request + Note right of MCData server: 3. Remove the file data + MCData server->>MCData client 1: 4. MCData communication release response + MCData server-->>MCData client 2: 5. Data not available control indication + Note left of MCData client 1: 6. Notify user + +``` + +Sequence diagram showing the release of MCData communication using HTTP between MCData client 1, MCData server, and MCData client 2. The steps are: 1. Initiate communication termination (internal to client 1), 2. MCData communication release request (client 1 to server), 3. Remove the file data (internal to server), 4. MCData communication release response (server to client 1), 5. Data not available control indication (server to client 2), 6. Notify user (internal to client 1). + +**Figure 7.7.2.2.3.2-1: Release of MCData communication using HTTP** + +1. MCData user at MCData client 1 requests to release ongoing file transmission. +2. MCData client 1 sends MCData communication release request towards MCData server identifying the HTTP file transmission. + +3. MCData server stops any ongoing file transfer and removes the file data already stored by MCData server. +4. MCData server sends MCData communication release response back to MCData client 1. +5. If file uploading over HTTP is completed and MCData clients have received the file metadata e.g., file URL, then MCData server also sends "data not available" control indication to all the participants receiving file metadata. +6. MCData client 1 notifies the MCData user about the file transmission communication release. + +### 7.7.2.3 MCData server initiated communication release without prior indication + +#### 7.7.2.3.1 General + +MCData server initiates the release of an ongoing MCData communication, since at least one of the communication release conditions are met e.g. lack of bearer capacity, limit for the maximum amount of data or time that a participant transmits from a single request to transmit exceeded. Based on the configuration, MCData server either pre-empts the MCData communication without giving prior indication to MCData client or notifies the intent of release to the MCData client initiating communication. Latter scenario allows the MCData user to request for extension of MCData communication and defer the communication release. + +#### 7.7.2.3.2 Release of MCData communication using media plane + +##### 7.7.2.3.2.1 General + +The subclause describes the procedure for MCData server initiated MCData communication release without prior indication, where MCData communication is established as SDS using media plane or file distribution using media plane. + +**Editor's note:** Release of MCData communication over MBMS is FFS. + +##### 7.7.2.3.2.2 Procedure + +The procedure in figure 7.7.2.3.2.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, based on communication release conditions, MCData server initiates the communication release. The procedure is applicable for one-to-one and group communication. + +Pre-conditions: + +1. MCData users on MCData client 1, client 2 and client 3 are already registered for receiving MCData service. +2. A MCData administrator has configured the limits for the maximum amount of data and time that a participant transmits from a single request to transmit. +3. A MCData communication is ongoing between MCData client 1, client 2 and client 3. + +![Sequence diagram showing the interaction between MCData server and multiple MCData clients (1, 2, 3) for releasing a communication. The process involves the server sending release requests, clients notifying users, and finally releasing media plane resources.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +``` + +sequenceDiagram + participant MCData server + participant MCData client 1 + participant MCData client 2 + participant MCData client 3 + + Note right of MCData server: 1. Release MCData communication + Note right of MCData server: 2. Determine MCData communication participants and generate communication release request + MCData server->>MCData client 1: 3a. MCData server communication release request + MCData server->>MCData client 2: 3b. MCData server communication release request + MCData server->>MCData client 3: 3c. MCData server communication release request + MCData client 1->>MCData client 1: 4a. Notify user + MCData client 2->>MCData client 2: 4b. Notify user + MCData client 3->>MCData client 3: 4c. Notify user + MCData client 1->>MCData server: 5a. MCData server communication release response + MCData client 2->>MCData server: 5b. MCData server communication release response + MCData client 3->>MCData server: 5c. MCData server communication release response + Note over MCData client 1, MCData client 2, MCData client 3: 6. Release media plane resources associated with the MCData communication + +``` + +Sequence diagram showing the interaction between MCData server and multiple MCData clients (1, 2, 3) for releasing a communication. The process involves the server sending release requests, clients notifying users, and finally releasing media plane resources. + +**Figure 7.7.2.3.2.2-1: MCData server initiated release of MCData communication using media plane** + +1. MCData server would like to release the ongoing MCData communication, identified by conversation identifier, since at least one of the release conditions are met e.g. lack of capacity, limit for the maximum amount of data or time that a participant transmits from a single request to transmit exceeded. Based on configuration, MCData server decides to pre-empt the MCData communication without giving prior indication to MCData client 1. +2. MCData server identifies the participants of the ongoing MCData communication and generates communication release request to release ongoing MCData communication. +3. MCData server sends server MCData communication release request towards each participant of the MCData communication. +4. MCData users are notified about the release of the MCData communication. +5. MCData client at each MCData communication participant sends server MCData communication release response towards the MCData server. +6. All participants of the MCData communication have successfully released the media plane resources associated with the MCData communication that is released. + +**7.7.2.3.3 Release of MCData communication using HTTP** + +**7.7.2.3.3.1 General** + +The subclause describes the procedure for MCData server initiated MCData communication release without prior indication, where MCData communication is established with procedures for file distribution using HTTP. + +### 7.7.2.3.3.2 Procedure + +The procedure in figure 7.7.2.3.3.2-1 describes signalling control plane procedure for the case where during ongoing MCData communication, communication release conditions, MCData server initiates the communication release. The procedure is applicable for one-to-one and group communication. + +Pre-conditions: + +1. MCData users on MCData client 1, client 2 and client 3 are already registered for receiving MCData service. +2. A MCData administrator has already configured the limits for the maximum amount of data and time that a participant transmits from a single request to transmit. +3. A MCData communication is ongoing between MCData client 1, client 2 and client 3. MCData client 1 is the initiator of the MCData communication + +![Sequence diagram showing the MCData server initiated release of MCData communication using HTTP. The diagram involves four lifelines: MCData client 1, MCData server, MCData client 2, and MCData client 3. The sequence of messages is: 1. Release MCData communication (from server to server), 2. Remove file data (from server to server), 3. MCData server communication release indication (from server to client 1), 4. Notify user (from client 1 to client 1), 5a. data not available control indication (from server to client 2), 6a. Notify user (from client 2 to client 2), 5b. data not available control indication (from server to client 3), 6b. Notify user (from client 3 to client 3).](18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + participant MCData client 3 + + Note right of MCData server: 1. Release MCData communication + Note right of MCData server: 2. Remove file data + MCData server->>MCData client 1: 3. MCData server communication release indication + Note left of MCData client 1: 4. Notify user + MCData server-->>MCData client 2: 5a. data not available control indication + Note right of MCData client 2: 6a. Notify user + MCData server-->>MCData client 3: 5b. data not available control indication + Note right of MCData client 3: 6b. Notify user + +``` + +Sequence diagram showing the MCData server initiated release of MCData communication using HTTP. The diagram involves four lifelines: MCData client 1, MCData server, MCData client 2, and MCData client 3. The sequence of messages is: 1. Release MCData communication (from server to server), 2. Remove file data (from server to server), 3. MCData server communication release indication (from server to client 1), 4. Notify user (from client 1 to client 1), 5a. data not available control indication (from server to client 2), 6a. Notify user (from client 2 to client 2), 5b. data not available control indication (from server to client 3), 6b. Notify user (from client 3 to client 3). + +**Figure 7.7.2.3.3.2-1: MCData server initiated release of MCData communication using HTTP** + +1. MCData server releases the ongoing MCData communication, identified by the conversation identifier, since at least one of the release conditions are met e.g. lack of capacity, limit for the maximum amount of data or time that a participant transmits from a single request to transmit exceeded. Based on the configuration, MCData server pre-empt's the MCData communication without giving prior indication to MCData client 1. +2. MCData server removes the data stored by MCData server. +3. MCData server sends MCData server communication release indication including the reason for release to MCData client 1. +4. MCData client 1 notifies MCData user about server initiated communication release. +5. If file uploading over HTTP is completed and MCData clients have received the file metadata e.g. file URL, then MCData server also sends "data not available" indication to all the participants receiving file metadata. Otherwise, there is no such indication. +6. MCData users are notified about the release of the MCData communication. + +## 7.7.2.4 MCData server initiated communication release with prior indication + +### 7.7.2.4.1 General + +The subclause describes the procedure for MCData server initiated MCData communication release with prior indication, where MCData communication is established as SDS using media plane or file distribution using media plane or file distribution using HTTP. + +### 7.7.2.4.2 Procedure + +The procedure in figure 7.7.2.4.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, based on communication release conditions, MCData server initiates communication release. As a result of configuration check, MCData server notifies the intent to release MCData communication, optionally requesting for more information (e.g. to know the remaining data volume to transmit) from the MCData client initiating MCData communication. + +Pre-conditions: + +1. MCData user on MCData client 1 is already registered for receiving MCData service. +2. MCData administrator has configured the limits for the maximum amount of data and time that a participant transmits from a single request to transmit. +3. MCData communication may be ongoing between MCData participants and MCData client 1 is the initiator of the communication. +4. MCData administrator has configured the time for which MCData server needs to wait for extension request from the MCData user. + +![Sequence diagram showing the procedure for MCData server initiating communication release with prior indication. The diagram involves three lifelines: MCData client 1, MCData server, and MCData user. The sequence of messages is: 1. Release MCData communication (internal to server), 2. MCData release intent request (server to client), 3. Notify user (client to user), 4. MCData more information response (client to server), 5. Request for extension (user to client), 6. MCData request for extension (client to server), 7. Policy assertion (internal to server), 8. MCData response for extension (server to client).](bd50d56ae2c12a92466ba2aea1a78040_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData user + Note right of MCData server: 1. Release MCData communication + MCData server->>MCData client 1: 2. MCData release intent request + Note left of MCData client 1: 3. Notify user + MCData client 1-->>MCData server: 4. MCData more information response + Note left of MCData client 1: 5. Request for extension + MCData client 1->>MCData server: 6. MCData request for extension + Note right of MCData server: 7. Policy assertion + MCData server->>MCData client 1: 8. MCData response for extension + +``` + +Sequence diagram showing the procedure for MCData server initiating communication release with prior indication. The diagram involves three lifelines: MCData client 1, MCData server, and MCData user. The sequence of messages is: 1. Release MCData communication (internal to server), 2. MCData release intent request (server to client), 3. Notify user (client to user), 4. MCData more information response (client to server), 5. Request for extension (user to client), 6. MCData request for extension (client to server), 7. Policy assertion (internal to server), 8. MCData response for extension (server to client). + +**Figure 7.7.2.4.2-1: MCData server initiates communication release with prior indication** + +1. MCData server releases the ongoing MCData communication, identified by the conversation identifier, since at least one of the release conditions are met e.g. lack of capacity, limit for the maximum amount of data or time that a participant transmits from a single request to transmit exceeded. Based on the configuration, MCData server notifies the intent to release MCData communication. +2. MCData server sends the MCData release intent request towards the communication initiating MCData client 1. MCData server may include request for more information (e.g. to know the remaining data volume to transmit). +3. MCData client 1 informs MCData user about the intent to release communication. +4. If request for more information is included in the received MCData release intent request, MCData client 1 sends MCData more information response including the remaining amount of data to transmit. Upon receiving more information response from MCData client 1, MCData server may wait for the request for extension until the time configured by the MCData administrator. If MCData server does not receive MCData request for extension within the configured timeout, the MCData server releases MCData communication as described in subclause 7.7.2.3. Otherwise, continue with remaining steps. +5. MCData user at MCData client 1 requests for extension of the ongoing MCData communication. + +6. MCData client 1 sends MCData request for extension of the MCData communication. +7. Upon receiving the MCData request for extension of MCData communication from the MCData client 1, MCData server asserts policies to accept or reject the request for extension. +8. MCData server sends MCData response for extension with success or failure result to MCData client 1. MCData communication will continue if MCData server accepted the request for extension from MCData client 1. Otherwise, MCData communication is released according to procedures described in subclause 7.7.2.3. + +## 7.7.2.5 Authorized MCData user initiated communication release without prior indication + +### 7.7.2.5.1 General + +An authorized MCData user at any time during an ongoing MCData communication decides to release communication. The authorized user may decide to release MCData communication without prior indication to the initiator MCData client. + +### 7.7.2.5.2 Procedure + +The procedure in figure 7.7.2.5.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, authorized MCData user initiates MCData communication release without prior indication to the initiator MCData client. An authorized MCData user is part of the ongoing MCData communication. + +Pre-conditions: + +1. An authorized MCData user on MCData client is already registered for receiving MCData service. +2. A MCData communication is ongoing between MCData participants and authorized MCData user is keeping track of which participants are receiving communication e.g. through "message delivered" and/or "message read" indications for the MCData communication. + +![Sequence diagram illustrating the procedure for an authorized MCData user to initiate communication release without prior indication. The diagram shows three lifelines: Authorized MCData client, MCData Server, and MCData client. The sequence of messages is: 1. Release MCData communication (internal to Authorized MCData client), 2. MCData auth user communication release request (from Authorized MCData client to MCData Server), 3. Validate request (internal to MCData Server), 4. Release communication (internal to MCData Server), 5. MCData auth user communication release response (from MCData Server to Authorized MCData client).](04867b54e8cdb31a034edbb472a41162_img.jpg) + +``` +sequenceDiagram + participant AMC as Authorized MCData client + participant MS as MCData Server + participant MC as MCData client + Note left of AMC: 1. Release MCData communication + AMC->>MS: 2. MCData auth user communication release request + Note right of MS: 3. Validate request + Note right of MS: 4. Release communication + MS->>AMC: 5. MCData auth user communication release response +``` + +Sequence diagram illustrating the procedure for an authorized MCData user to initiate communication release without prior indication. The diagram shows three lifelines: Authorized MCData client, MCData Server, and MCData client. The sequence of messages is: 1. Release MCData communication (internal to Authorized MCData client), 2. MCData auth user communication release request (from Authorized MCData client to MCData Server), 3. Validate request (internal to MCData Server), 4. Release communication (internal to MCData Server), 5. MCData auth user communication release response (from MCData Server to Authorized MCData client). + +**Figure 7.7.2.5.2-1: An authorized MCData user initiates communication release without prior indication** + +1. An authorized MCData user requests to release the ongoing MCData communication, without providing prior indication to the initiator of the MCData communication, MCData client 1. +2. An authorized MCData client sends MCData auth user communication release request towards MCData server identifying the MCData communication to release. The request also includes indication to the MCData server to release MCData communication without prior indication to the initiator of the MCData communication, MCData client 1. +3. MCData server validates the user from whom the MCData communication release request is received and checks whether the requesting MCData user is authorized to release communication or not. + +4. If the user is authorized to release communication, then MCData server releases the ongoing MCData communication according to procedures described in subclause 7.7.2.3. +5. MCData server sends MCData auth user communication release response containing the result of MCData communication release back to authorized MCData client 1. + +## 7.7.2.6 Authorized MCData user initiated communication release with prior indication + +### 7.7.2.6.1 General + +An authorized MCData user at any time during an ongoing MCData communication decides to release communication. The authorized user may decide to release MCData communication with prior indication to the initiator MCData client. A prior indication allows initiator MCData client to request for extension for the MCData communication. + +### 7.7.2.6.2 Procedure + +The procedure in figure 7.7.2.6.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, authorized MCData user initiates MCData communication release with prior indication to the initiator MCData client. An authorized MCData user is part of the ongoing MCData communication. An initiator MCData user optionally decides to request for the extension of the ongoing communication. + +Pre-conditions: + +1. An authorized MCData user on MCData client is already registered for receiving MCData service. +2. A MCData communication is ongoing between MCData participants and authorized MCData user is keeping track of which participants are receiving communication e.g. through "message delivered" and/or "message read" indications for the MCData communication +3. MCData client 1 is the initiator of the MCData communication. + +![Sequence diagram illustrating the procedure for an authorized MCData user to initiate communication release with prior indication. The diagram shows interactions between MCData client 1, MCData server, and an Authorized MCData Client. The process involves a release request, validation, intent request, user notification, information exchange, optional extension request, and final release communication.](5152ddc7d77f41ae1eaf931aaac810eb_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Authorized MCData Client + + Note right of Authorized MCData Client: 1. Release MCData communication + Authorized MCData Client->>MCData server: 2. MCData auth user communication release request + MCData server->>MCData server: 3. Validate request + MCData server->>MCData client 1: 4. MCData release intent request + Note left of MCData client 1: 5. Notify user + MCData client 1->>MCData server: 6. MCData more information response + MCData server-->>Authorized MCData Client: 7. MCData more information response + Note left of MCData client 1: 8. Request for extension + MCData client 1->>MCData server: 9. MCData request for extension + MCData server->>Authorized MCData Client: 10. MCData request for extension + Note right of Authorized MCData Client: 11. Notify user + Authorized MCData Client->>MCData server: 12. MCData response for extension request + MCData server->>MCData client 1: 13. MCData response for extension request + Note over MCData client 1, MCData server: 14. Release communication + MCData server->>Authorized MCData Client: 15. MCData auth user communication release response + +``` + +Sequence diagram illustrating the procedure for an authorized MCData user to initiate communication release with prior indication. The diagram shows interactions between MCData client 1, MCData server, and an Authorized MCData Client. The process involves a release request, validation, intent request, user notification, information exchange, optional extension request, and final release communication. + +Figure 7.7.2.6.2-1: An authorized MCData user initiates communication release with prior indication + +1. An authorized MCData user requests to release the ongoing MCData communication by providing prior indication to the initiator of MCData communication, MCData client 1. + 2. An authorized MCData client sends MCData auth user communication release request towards MCData server including the communication identifier identifying the MCData communication to release. Authorized MCData client may include request for more information (e.g. to know the remaining data volume to transmit). The request also includes indication to MCData server to release MCData communication with prior indication to the initiator MCData client. + 3. MCData server validates the user from whom the communication release request is received and checks whether the requesting user is authorized to release communication or not. + 4. If the user is authorized to release communication, then the MCData server sends MCData release intent request, may be including the reason for the release. MCData server may include request for more information as received in the request from the authorized MCData client. + 5. MCData client informs MCData user about the intent to release communication by the authorized MCData user. + 6. If request for more information is included in the received MCData release intent request, MCData client 1 sends MCData more information response including the remaining amount of data to transmit. + 7. MCData server forwards the MCData more information response to the authorized MCData client. +- NOTE: Upon receiving more information response from MCData client 1, MCData server may wait for the request for extension until the time configured by the MCData administrator. If MCData server does not receive request for extension within the configured timeout, the MCData server releases MCData communication as described in subclause 7.7.2.3. Otherwise, continue with remaining steps. +8. MCData user at MCData client 1 decides to request for extension of the ongoing MCData communication. + - 9 and 10. MCData client sends MCData request for extension towards MCData server. And MCData server forwards the MCData request for extension towards the authorized MCData client. + 11. Authorized MCData client notifies the authorized user about the incoming request for extension. An authorized MCData user decides to accept or reject the request for extension. + - 12 and 13. Authorized MCData user decision is sent in MCData response for extension request towards the MCData server. MCData server forwards the MCData response for extension request to MCData client 1. + 14. MCData communication will continue if the authorized user accepted the request for extension from MCData client 1. Otherwise, MCData communication will be released according to procedures described in subclause 7.7.2.3. + 15. After MCData communication is released, MCData server sends the MCData auth user communication release response back to the authorized MCData client. + +## 7.8 Conversation management + +### 7.8.1 General + +Conversation management is a collection of related MCData transmissions for a given activity. Conversation management associates SDS and FD communication transmission and present them as a single thread to the user. + +### 7.8.2 Conversation management for on-network + +#### 7.8.2.1 Information flows for conversation management + +The information flow parameters related to conversation management are as described in the subclauses 7.4.2.1 and subclauses 7.5.2.1.5, 7.5.2.1.6, 7.5.2.1.7, 7.5.2.1.8, 7.5.2.1.9, 7.5.2.1.10, 7.5.2.1.11, 7.5.2.1.12, and 7.5.2.1.13. + +## 7.8.2.2 One-to-one conversation management + +### 7.8.2.2.1 Procedure + +The procedure for an MCData user to associate multiple MCData transmissions between a pair of users for a given activity is illustrated in figure 7.8.2.2.1-1. + +Pre-conditions: + +1. MCData user(s) on MCData client 1 and 2 are registered for receiving MCData service. + +![Sequence diagram for One-to-one conversation management](f52f816ab28ff4b4a9d12c6c94fbd41c_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. Initiate conversation + Note over MCData client 1, MCData client 2: 2. Procedure(s) of one-to-one SDS or one-to-one FD or combination of both +``` + +The diagram is a sequence diagram showing the interaction between MCData client 1, MCData server, and MCData client 2. MCData client 1 initiates the conversation (step 1). The MCData server and MCData client 2 then execute the procedure(s) of one-to-one SDS or one-to-one FD or combination of both (step 2). + +Sequence diagram for One-to-one conversation management + +**Figure 7.8.2.2.1-1: One-to-one conversation management** + +1. The user at MCData client 1 initiates conversation. A universally unique conversation identifier is generated to identify new conversation. Conversation identifier is used in procedures mentioned in step 2. If the intent of the user at MCData client 1 is to transmit within an existing conversation, then corresponding conversation identifier is used in procedures mentioned in step 2. To allow multiple parallel conversations for the same pair of users, different conversation identifier is used for each conversation. The MCData users can view the MCData conversation at any time after the first MCData transaction is initiated within the conversation. +2. The procedure of one-to-one SDS or one-to-one FD or combination of both these procedures can be executed. + +## 7.8.2.3 Group conversation management + +### 7.8.2.3.1 Procedure + +The procedure for an MCData user to associate multiple MCData transmissions between users of a group for a given activity is illustrated in figure 7.8.2.3.1-1. + +Pre-conditions: + +1. MCData user(s) on MCData client 1, 2, and n are registered for receiving MCData service. +2. The MCData users 1, 2 and n are members of the same MCData group and affiliated to the MCData service. + +![Sequence diagram for Group conversation management](3a6bf5d7dd794e6f7fb608b797c92fe7_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + participant MCData client n + Note left of MCData client 1: 1. Initiate conversation + Note over MCData client 1, MCData client n: 2. Procedure(s) of Group SDS or Group FD or combination of both +``` + +The diagram is a sequence diagram showing the interaction between MCData client 1, MCData server, MCData client 2, and MCData client n. MCData client 1 initiates the conversation (step 1). The MCData server and MCData client 2 then execute the procedure(s) of Group SDS or Group FD or combination of both (step 2). + +Sequence diagram for Group conversation management + +**Figure 7.8.2.3.1-1: Group conversation management** + +1. The user at MCData client 1 initiates conversation. A unique conversation identifier is generated to identify new conversation. Conversation identifier is used in procedures mentioned in step 2. If the intent of the user at MCData client 1 is to transmit within an existing conversation, then corresponding conversation identifier is used in procedures mentioned in step 2. To allow multiple parallel conversations for the same group of users, different conversation identifier is used for each conversation. The MCData users can view the MCData conversation at any time after the first MCData transaction is initiated within the conversation. +2. The procedure of group SDS or group FD or combination of both these procedures can be executed. + +### 7.8.3 Conversation management for off-network + +#### 7.8.3.1 One-to-one conversation management + +##### 7.8.3.1.1 Procedure + +The procedure for an MCData user to associate multiple off-network MCData transmissions between a pair of users is illustrated in figure 7.8.3.1.1-1. + +Pre-conditions: + +1. MCData client 1 and MCData client 2 are members of the same **ProSe** Discovery group and are **ProSe** 1:1 direct communication capable. +2. MCData client 1 has discovered MCData client 2 in proximity, associated with MCData user B, using **ProSe** Discovery procedures. + +![Sequence diagram for One-to-one conversation management between MCData client 1 and MCData client 2.](5ec2b6e9c9133bfbb26789d85dc49774_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + Note left of MCData client 1: 1. Initiate conversation + Note right of MCData client 2: 2. Procedure(s) of one-to-one SDS or one-to-one FD or both +``` + +The diagram is a sequence diagram illustrating the interaction between MCData client 1 and MCData client 2. MCData client 1 sends a message labeled '1. Initiate conversation' to MCData client 2. MCData client 2 responds with a message labeled '2. Procedure(s) of one-to-one SDS or one-to-one FD or both'. + +Sequence diagram for One-to-one conversation management between MCData client 1 and MCData client 2. + +**Figure 7.8.3.1.1-1: One-to-one conversation management** + +1. The user at MCData client 1 initiates conversation. A universally unique conversation identifier is generated to identify the new conversation. Conversation identifier is used in the procedures mentioned in step 2. If the intent of the user at MCData client 1 is to transmit within an existing conversation, then corresponding conversation identifier from the existing conversation is used in the procedures mentioned in step 2. To allow multiple parallel conversations for the same pair of users, different conversation identifier is used for each conversation. The MCData users can view the MCData conversation at any time after the first MCData transaction is initiated within the conversation. +2. The procedure of one-to-one SDS or one-to-one FD or a combination of these can be executed. + +#### 7.8.3.2 Group conversation management + +##### 7.8.3.2.1 Procedure + +The procedure for an MCData user to associate multiple off-network MCData transmissions between users of a group is illustrated in figure 7.8.3.2.1-1. + +Pre-conditions: + +1. Information for **ProSe** direct communications corresponding to the MCData group and its mapping to **ProSe** Layer-2 Group ID are pre-configured in MCData client 1. +2. MCData client 1 to MCData client N are members of the same MCData group. + +![Diagram illustrating Group conversation management. Three boxes at the top represent MCData client 1, MCData client 2, and MCData client n. Vertical lines connect each client to a central horizontal bar. From MCData client 1, a box labeled '1. Initiate conversation' points to the central bar. The central bar is labeled '2. Procedure(s) of Group SDS or Group FD or both'.](1c79f31a718d63814feb28ab46f64f19_img.jpg) + +``` + +graph TD + C1[MCData client 1] --- CB[ ] + C2[MCData client 2] --- CB + Cn[MCData client n] --- CB + subgraph CB [ ] + direction TB + S1[1. Initiate conversation] + S2[2. Procedure(s) of Group SDS or Group FD or both] + end + style CB fill:none,stroke:none + +``` + +Diagram illustrating Group conversation management. Three boxes at the top represent MCData client 1, MCData client 2, and MCData client n. Vertical lines connect each client to a central horizontal bar. From MCData client 1, a box labeled '1. Initiate conversation' points to the central bar. The central bar is labeled '2. Procedure(s) of Group SDS or Group FD or both'. + +**Figure 7.8.3.2.1-1: Group conversation management** + +1. The user at MCData client 1 initiates conversation. A universally unique conversation identifier is generated to identify the new conversation. Conversation identifier is used in the procedures mentioned in step 2. If the intent of the user at MCData client 1 is to transmit within an existing conversation, then corresponding conversation identifier from the existing conversation is used in the procedures mentioned in step 2. To allow multiple parallel conversations for the same group of users, different conversation identifier is used for each conversation. The MCData users can view the MCData conversation at any time after the first MCData transaction is initiated within the conversation. +2. The procedure of group SDS or group FD or combination of both can be executed. + +## 7.9 Enhanced status + +### 7.9.1 General + +Enhanced status corresponds to information specific to the activities performed by the mission critical service users during their operation(s) e.g. available, in operation on site, going to the operation site, or just arrived. + +### 7.9.2 Preset values for enhanced status + +The enhanced status information i.e. the set of possible values corresponding to the activities of the MCData user, shall be configured by the MCData administrator. The configuration of status values is applicable on a per-group basis, and therefore shall be part of the MCData group configuration data as described in Annex A.4. + +The configuration mechanism shall allow the MCData administrator to configure a minimum of 32 possible values and allow up to 65536 separate values. The set of values may be divided into a fixed set of values defined by 3GPP standards which are common across all MCData systems, and a set which may be freely configured for any purpose. + +### 7.9.3 Enhanced status for on-network + +#### 7.9.3.1 Sharing enhanced status information + +##### 7.9.3.1.1 Procedure + +The procedure for an MCData user to share the enhanced status information to the members of the selected group is illustrated in figure 7.9.3.1.1-1. + +Pre-conditions: + +1. MCData user(s) on MCData client 1, 2, and n are registered for receiving MCData service. +2. The MCData users 1, 2 and n are members of the same MCData group and affiliated to the MCData service. +3. The MCData group is pre-configured with the possible values for enhanced status information. + +![Sequence diagram illustrating the sharing of enhanced status information. Lifelines: MCData client 1, MCData server, MCData client 2, and MCData client n. Step 1: MCData client 1 sends a message '1. Select enhanced status information' to the MCData server. Step 2: A horizontal bar labeled '2. Procedure of group standalone SDS using signalling control plane' spans across all lifelines. Step 3: From the end of step 2, MCData client 2 and MCData client n each send a message '3. Notify enhanced status information' to the MCData server.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + participant MCData client n + Note left of MCData client 1: 1. Select enhanced status information + Note over MCData client 1, MCData server, MCData client 2, MCData client n: 2. Procedure of group standalone SDS using signalling control plane + Note right of MCData client 2: 3. Notify enhanced status information + Note right of MCData client n: 3. Notify enhanced status information +``` + +Sequence diagram illustrating the sharing of enhanced status information. Lifelines: MCData client 1, MCData server, MCData client 2, and MCData client n. Step 1: MCData client 1 sends a message '1. Select enhanced status information' to the MCData server. Step 2: A horizontal bar labeled '2. Procedure of group standalone SDS using signalling control plane' spans across all lifelines. Step 3: From the end of step 2, MCData client 2 and MCData client n each send a message '3. Notify enhanced status information' to the MCData server. + +**Figure 7.9.3.1.1-1: Sharing enhanced status information** + +1. The user at MCData client 1 selects the MCData group to share the enhanced status information. The user also selects the value of the status information to be shared from the list of pre-configured status values available for the MCData group. +2. The procedure of group standalone SDS using signalling control plane as described in subclause 7.4.2.2, is used to deliver the enhanced status information. +3. The MCData users at MCData client 2 and n are notified of the enhanced status information. + +## 7.9.4 Enhanced status for off-network + +### 7.9.4.1 Sharing enhanced status information + +#### 7.9.4.1.1 Procedure + +The procedure for an MCData user to share the enhanced status information to the members of the selected group is illustrated in figure 7.9.4.1.1-1. + +Pre-conditions: + +1. Information for ProSe direct communications corresponding to the MCData group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCData client 1. +2. MCData client 1, 2 and n are members of the same MCData group. +3. The MCData group is pre-configured with the possible values for enhanced status information. + +![Sequence diagram illustrating the sharing of enhanced status information among multiple MCData clients. The diagram shows three clients: MCData client 1, MCData client 2, and MCData client n. Step 1: MCData client 1 sends a message '1. Select enhanced status information'. Step 2: All clients participate in a 'Procedure of off-network group standalone SDS using signalling control plane'. Step 3: MCData client 2 and MCData client n each receive a message '3. Notify enhanced status information'.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + participant MCData client n + Note left of MCData client 1: 1. Select enhanced status information + Note over MCData client 1, MCData client 2, MCData client n: 2. Procedure of off-network group standalone SDS using signalling control plane + Note right of MCData client 2: 3. Notify enhanced status information + Note right of MCData client n: 3. Notify enhanced status information + +``` + +Sequence diagram illustrating the sharing of enhanced status information among multiple MCData clients. The diagram shows three clients: MCData client 1, MCData client 2, and MCData client n. Step 1: MCData client 1 sends a message '1. Select enhanced status information'. Step 2: All clients participate in a 'Procedure of off-network group standalone SDS using signalling control plane'. Step 3: MCData client 2 and MCData client n each receive a message '3. Notify enhanced status information'. + +**Figure 7.9.4.1.1-1: Sharing enhanced status information** + +1. The user at MCData client 1 selects the MCData group to share the enhanced status information. The user also selects the value of the status information to be shared from the list of pre-configured status values available for the MCData group. +2. The procedure of off-network group standalone SDS using signalling control plane as described in subclause 7.4.3.3, is used to deliver the enhanced status information. +3. The MCData users at MCData client 2 and n are notified of the enhanced status information. + +## 7.10 MCData emergency alert (on-network and off-network) + +The MCData service shall support the procedures and related information flows as specified in subclause 10.10 of 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; +- The MC service group ID is the MCData Group ID; and +- The MC service user profile index is the MCData user profile index. + +## 7.11 User authentication and authorization for MCData service + +**NOTE:** Flow 7.11-1 is a high level user authentication and authorization flow. 3GPP TS 33.180 [13] defines the specific user authentication and authorization architecture required by the MCData service in order to realize the MCData user authentication and authorization requirements as defined in 3GPP TS 22.280 [2]. + +A procedure for user authentication is illustrated in figure 7.11-1. The user authentication is performed based on the procedure specified in subclause 10.6 of 3GPP TS 23.280 [5]. + +![Sequence diagram for MCData user authentication and registration, single domain. Lifelines: MCData client, Identity management client, Signalling user agent, SIP core, Identity management server, MCData server. Step 1: User Authentication is based on the procedure – “General user authentication and authorization for MC services” specified in 3GPP TS 23.280[5]. Step 2: The MCData client performs the service authorization with the MCData server.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +The diagram is a sequence diagram illustrating the interaction for MCData user authentication and registration in a single domain. It features six lifelines: MCData client, Identity management client, Signalling user agent, SIP core, Identity management server, and MCData server. Two numbered steps are shown in rectangular boxes spanning across the lifelines. Step 1, 'User Authentication is based on the procedure – “General user authentication and authorization for MC services” specified in 3GPP TS 23.280[5]', is shown between the Identity management client and the Identity management server. Step 2, 'The MCData client performs the service authorization with the MCData server.', is shown between the MCData client and the MCData server. Vertical lines extend downwards from each lifeline box. + +Sequence diagram for MCData user authentication and registration, single domain. Lifelines: MCData client, Identity management client, Signalling user agent, SIP core, Identity management server, MCData server. Step 1: User Authentication is based on the procedure – “General user authentication and authorization for MC services” specified in 3GPP TS 23.280[5]. Step 2: The MCData client performs the service authorization with the MCData server. + +**Figure 7.11-1: MCData user authentication and registration, single domain** + +- 1. The user authentication is performed as per the general user authentication procedure specified in subclause 10.6 of 3GPP TS 23.280 [5]. +- 2. MCData client performs the MCData service authorization for the user. Step 2 utilizes the results of step 1. + +## 7.12 MCData resource management (on-network) + +### 7.12.1 General + +Procedures for resource management are defined in subclause 10.x of 3GPP TS 23.280 [5]. + +### 7.12.2 MCData services not handled by SIP core + +MCData services that do not utilize the SIP core e.g. IP connectivity, cannot utilize the resource control functionality of the local outbound / inbound proxy. For these types of service, resource management is handled directly by the Rx interface from the MCData server to the PCRF, which is the MCData-5 reference point. The Rx interface is defined in 3GPP TS 29.214 [17]. + +The same types of resource management procedures as defined for SIP based services in 3GPP TS 23.280 [5] may also be applied for non SIP based services. That is: + +- Request for unicast resources at session establishment (in this case service initiation); +- Request for modification of unicast resources; and +- Request for resources with shared priority. + +# Annex A (normative): MCData related configuration data + +## A.1 General + +This Annex provides information about the static data needed for configuration for the MCData service, which belongs to one of the following categories: + +- MCData UE configuration data (see subclause A.2); +- MCData user profile configuration data (see subclause A.3); +- MCData related group configuration data (see subclause A.4); and +- MCData service configuration data (see subclause A.5). + +For each configuration category, data is split between configuration data that is applicable to both on network and off network, configuration data that is applicable to on-network only, and configuration data that is applicable to off-network only. The configuration data in each configuration category corresponds to a single instance of the category type i.e. the MCData UE, MCData group, MCData user and MCData service configuration data refers to the information that will be stored against each MCData UE, MCData group, MCData user and MCData service. This means that the three separate tables (on-network and off-network, on-network only, off-network only) for each configuration category represent the complete set of data for each configuration data category element. + +The columns in the tables have the following meanings: + +- Reference: the reference of the corresponding requirement in 3GPP TS 22.282 [3] or 3GPP TS 22.280 [2] or the corresponding subclause from either the present document or the referenced document. +- Parameter description: A short definition of the semantics of the corresponding item of data, including denotation of the level of the parameter in the configuration hierarchy. + - When it is not clear to which functional entities the parameter is configured, then one or more columns indicating this are provided where the following nomenclature is used: + - "Y" to denote "Yes" i.e. the parameter denoted for the row needs to be configured to the functional entity denoted for the column. + - "N" to denote "No" i.e. the parameter denoted for the row does not need to be configured to the functional entity denoted for the column. + +Parameters within a set of configuration data have a level within a hierarchy that pertains only to that configuration data. The hierarchy of the configuration data is common across all three tables of on-network and off-network, on network only and off network only. The level of a parameter within the hierarchy of the configuration data is denoted by use of the character ">" in the parameter description field within each table, one per level. Parameters that are at the top most level within the hierarchy have no ">" character. Parameters that have one or more ">" characters are child parameters of the first parameter above them that has one less ">" character. Parent parameters are parameters that have one or more child parameters. Parent parameters act solely as a "grouping" of their child parameters and therefore do not contain an actual value themselves i.e. they are just containers for their child parameters. + +Each parameter that can be configured online shall only be configured through one online reference point. Each parameter that can be configured offline shall only be configured through one offline reference point. The most recent configuration data made available to the MCData UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism. + +## A.2 MCData UE configuration data + +The general aspects of UE configuration are specified in 3GPP TS 23.280 [5]. Data in tables A.2-1 and A.2-2 have to be known by the MCData UE after MCData authorization. + +Data in table A.2-1 can be configured offline using the CSC-11 reference point. Table A.2-1 contains the UE configuration required to support the use of off-network MCData service. + +**Table A.2-1: UE configuration data (on and off network)** + +| Reference | Parameter description | +|-------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| | Short data service | +| [R-5.4.2-002] of 3GPP TS 22.280 [2] | > Maximum number of simultaneous SDS transactions (Nc4) | +| [R-5.4.2-004] of 3GPP TS 22.280 [2] | > Requested presentation priority of SDS messages received (see NOTE1) | +| | File distribution | +| [R-5.4.2-002] of 3GPP TS 22.280 [2] | > Maximum number of simultaneous file distribution transactions (Nc4) | +| | Transmission control | +| [R-5.4.2-002] of 3GPP TS 22.280 [2] | > Maximum number of simultaneous data transmissions (Nc4) | +| [R-5.4.2-003] of 3GPP TS 22.280 [2] | > Maximum number of data transmissions (Nc5) in a group | +| | Reception control | +| [R-5.4.2-002] of 3GPP TS 22.280 [2] | > Maximum number of simultaneous data receptions (Nc4) | +| [R-5.4.2-003] of 3GPP TS 22.280 [2] | > Maximum number of data receptions (Nc5) in a group | +| NOTE: | Priority of SDS messages includes enhanced status updates, since enhanced status updates utilise the SDS mechanism. | + +**Table A.2-2: UE configuration data (on network)** + +| Reference | Parameter description | +|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| Subclause 5.2.3 of 3GPP TS 23.280 [6] | Relay service (Y/N) | +| Subclause 5.2.3 of 3GPP TS 23.280 [6] | List of allowed relayed MCData groups and their relay service code (as specified in 3GPP TS 23.303 [7]) (optional) (see NOTE) | +| | > MCData group ID | +| | > Relay service code (as specified in 3GPP TS 23.303 [7]) | +| Subclause 5.7 of 3GPP TS 23.280 [6] | Indication of whether the UE shall use IPv4 or IPv6 for on-network MCData | +| | MCData server | +| | > Server URI | +| NOTE: | When the value of the parameter Relay service is N, this parameter and its child parameters are not needed. | + +## A.3 MCData user profile configuration data + +The general aspects of MC service user profile configuration data are specified in 3GPP TS 23.280 [5]. The MCData user profile configuration data is stored in the MCData user database. The MCData server obtains the MCData user profile configuration data from the MCData user database (MCData-2). + +Tables A.3-1 and A.3-2 contain the MCData user profile configuration required to support the use of on-network MCData service. Tables A.3-1 and A.3-3 contain the MCData user profile configuration required to support the use of off-network MCData service. Data in table A.3-1 and A.3-3 can be configured offline using the CSC-11 reference point. + +**Table A.3-1: MCData user profile configuration data (on and off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | MCData user database | +|-----------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------------|---------------------------------|----------------------| +| Subclause 8.1.2 of 3GPP TS 23.280 [5] | MCData identity (MCData ID) | Y | Y | Y | Y | +| 3GPP TS 33.180 [13] | KMSUri for security domain of MCData ID (see NOTE 1) | Y | Y | Y | Y | +| Subclause 5.2.4 of 3GPP TS 23.280 [5] | Pre-selected MCData user profile indication (see NOTE 2) | Y | Y | Y | Y | +| Subclause 5.2.4 of 3GPP TS 23.280 [5] | MCData user profile index | Y | Y | Y | Y | +| Subclause 5.2.4 of 3GPP TS 23.280 [5] | MCData user profile name | Y | Y | Y | Y | +| [R-5.17-007], [R-6.13.4-002] of 3GPP TS 22.280 [2] | User profile status (enabled/disabled) | | Y | Y | Y | +| [R-5.7-001], [R-6.9-003] of 3GPP TS 22.280 [2] | Authorised to create and delete aliases of an MCData user and its associated user profiles. | | | Y | Y | +| [R-5.7-002], [R-6.9-003] of 3GPP TS 22.280 [2] | Alphanumeric aliases of user | Y | Y | Y | Y | +| [R-5.1.1-005], [R-5.9-001] of 3GPP TS 22.280 [2] | Participant type of the user | Y | Y | Y | Y | +| [R-5.1.8-006], [R-5.3-002], [R-5.9-001], [R-5.16.2-001], [R-5.16.2-002] of 3GPP TS 22.280 [2] | User's Mission Critical Organization (i.e. which organization a user belongs to) | Y | Y | Y | Y | +| [R-5.2.2-003] of 3GPP TS 22.280 [2] | Authorisation to create a group-broadcast group | | | Y | Y | +| [R-5.2.2-003] of 3GPP TS 22.280 [2] | Authorisation to create a user-broadcast group | | | Y | Y | +| [R-5.6.2.4.1-002] of 3GPP TS 22.280 [2] | Authorised to activate MCData emergency alert | Y | Y | Y | Y | +| [R-5.6.2.4.1-004] [R-5.6.2.4.1-008] [R-5.6.2.4.1-012] of 3GPP TS 22.280 [2] | Group / user recipient of an MCData emergency alert (Pre-defined group, currently selected group, pre-defined recipient/ user locally defined recipient/ default if no recipient selected) | Y | Y | Y | Y | +| [R-5.6.2.4.2-002] of 3GPP TS 22.280 [2] | Authorisation to cancel an MCData emergency alert | Y | Y | Y | Y | +| | One-to-one communication | | | | | +| [R-6.3.1.2-007] of 3GPP TS 22.282 [3] and 3GPP TS 33.180 [13] | > List of MCData users this MCData user is authorized to initiate a one-to-one communication | | | | | +| | >> MCData ID | Y | N | Y | Y | +| | >> Discovery Group ID | Y | N | Y | Y | +| | >> User info ID (as specified in 3GPP TS 23.303 [7]) | Y | N | Y | Y | + +| | | | | | | +|-------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---| +| | >> KMSUri for security domain of MCData ID (see NOTE 1) | Y | Y | Y | Y | +| | File distribution | | | | | +| [R-5.3.2-010] of 3GPP TS 22.282 [3] and 3GPP TS 33.180 [13] | > List of MCData users this MCData user is allowed to cancel distribution of files being sent or waiting to be sent | | | | | +| | >> MCData ID | Y | Y | Y | Y | +| | >> KMSUri for security domain of MCData ID (see NOTE 1) | Y | Y | Y | Y | +| | Transmission and reception control | | | | | +| [R-6.2.2.1-001] of 3GPP TS 22.282 [3] | > Whether the MCData user is permitted to transmit data | Y | Y | Y | Y | +| [R-6.2.3-005] of 3GPP TS 22.282 [3] | > Maximum amount of data that the MCData user can transmit in a single request during one-to-one communication | Y | Y | Y | Y | +| [R-6.2.3-005] and [R-6.3.1.2-008] of 3GPP TS 22.282 [3] | > Maximum amount of time that the MCData user can transmit in a single request during one-to-one communication | Y | Y | Y | Y | +| [R-6.2.3-001] of 3GPP TS 22.282 [3] | > List of MCData users this MCData user is allowed to request the release of an ongoing transmission that this MCData user is participating in | | | | | +| | >> MCData ID | Y | Y | Y | Y | + +NOTE 1: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5]. + +NOTE 2: As specified in 3GPP TS 23.280 [5], for each MCData user's set of MCData user profiles, only one MCData user profile shall be indicated as being the pre-selected MCData user profile. + +**Table A.3-2: MCData user profile configuration data (on network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | MCData user database | +|---------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------|---------------|---------------------------------|----------------------| +| [R-5.1.5-001],<br>[R-5.1.5-002],<br>[R-5.10-001],<br>[R-6.4.7-002],<br>[R-6.8.1-008],<br>[R-6.7.4-002] of<br>3GPP TS 22.280 [2] | List of on-network MCData groups for use by an MCData user | | | | | +| | > MCData Group ID | Y | Y | Y | Y | +| | > Application plane server identity information of group management server where group is defined | | | | | +| | >> Server URI | Y | N | Y | Y | +| | > Application plane server identity information of identity management server which provides authorization for group (see NOTE 1) | | | | | +| | >> Server URI | Y | N | Y | Y | +| | > MCData content server where the HTTP FD file is uploaded | | | | | +| | >> Server URI | Y | Y | Y | Y | +| | > MCData message store where the communication history stores | | | | | +| | >> Server URI | Y | Y | Y | Y | +| 3GPP TS 33.180 [13] | > KMSUri for security domain of group (see NOTE 2) | Y | Y | Y | Y | +| | > Presentation priority of the group relative to other groups and users (see NOTE 3) | Y | Y | Y | Y | +| Subclause 5.2.5 of<br>3GPP TS 23.280 [5] | List of groups user implicitly affiliates to after MCData service authorization for the user | | | | | +| | > MCData Group ID | Y | Y | Y | Y | +| [R-6.4.2-006] of<br>3GPP TS 22.280 [2] | Authorisation of an MCData user to request a list of which MCData groups a user has affiliated to | | Y | Y | Y | +| [R-6.4.6.1-002],<br>[R-6.4.6.1-003] of<br>3GPP TS 22.280 [2] | Authorisation to change affiliated groups of other specified user(s) | | Y | Y | Y | +| [R-6.4.6.2-001],<br>[R-6.4.6.2-002] of<br>3GPP TS 22.280 [2] | Authorisation to recommend to specified user(s) to affiliate to specific group(s) | | Y | Y | Y | +| [R-6.6.1-004] of<br>3GPP TS 22.280 [2] | Authorisation to perform regrouping | Y | Y | Y | Y | +| [R-6.7.2-001] of<br>3GPP TS 22.280 [2] | Presence status is available/not available to other users | Y | Y | Y | Y | +| [R-6.7.1-002],<br>[R-6.7.2-002] of<br>3GPP TS 22.280 [2] | List of MCData users that MCData user is authorised to obtain presence of | | | | | +| | > MCData IDs | Y | Y | Y | Y | +| [R-6.8.7.4.2-001],<br>[R-6.8.7.4.2-002] of<br>3GPP TS 22.280 [2] | Authorisation of a user to cancel an emergency alert on any MCData UE of any user | | Y | Y | Y | +| [R-6.13.4-001] of<br>3GPP TS 22.280 [2] | Authorisation for an MCData user to enable/disable an MCData user | | Y | Y | Y | +| [R-6.13.4-003],<br>[R-6.13.4-005],<br>[R-6.13.4-006],<br>[R-6.13.4-007] of<br>3GPP TS 22.280 [2] | Authorisation for an MCData user to (permanently /temporarily) enable/disable a UE | | Y | Y | Y | + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|---|---|---|---| +| [R-7.14-002], [R-7.14-003] of 3GPP TS 22.280 [2] | Authorization for manual switch to off-network while in on-network | Y | Y | Y | Y | +| [R-5.1.5-004] of 3GPP TS 22.280 [2] | Limitation of number of affiliations per user (N2) | N | Y | Y | Y | +| [R-6.4.6.1-001], [R-6.4.6.1-004] of 3GPP TS 22.280 [2] | List of MCData users whose selected groups are authorized to be remotely changed | Y | Y | Y | Y | +| | Conversation management | | | | | +| [R-6.1.1.2-005], [R-6.1.1.2-006], [R-6.1.1.2-007] of 3GPP TS 22.282 [3] | > List of conversation hang times for MCData groups | | | | | +| | >> MCData Group ID | Y | Y | Y | Y | +| | >> Hang time | Y | Y | Y | Y | +| [R-6.1.1.2-009] of 3GPP TS 22.282 [3]. | > List of MCData users to be sent message delivered disposition notifications in addition to the message sender | N | Y | Y | Y | +| [R-6.1.1.2-009] of 3GPP TS 22.282 [3]. | > List of MCData users to be sent message read disposition notifications in addition to the message sender | N | Y | Y | Y | +| 3GPP TS 23.283 [18] | Authorised to use LMR E2EE for interworking | Y | Y | Y | Y | +| 3GPP TS 23.283 [18] | > List of supported LMR technology types | | | | | +| 3GPP TS 23.283 [18] | >> LMR technology type (P25, TETRA etc.) | Y | N | Y | Y | +| 3GPP TS 23.283 [18] | >> URI of LMR key management functional entity (see NOTE 4 ) | Y | N | Y | Y | +| 3GPP TS 23.283 [18] | >> LMR specific identity (RSI for P25 or ITS1 for TETRA) (see NOTE 5) | Y | N | Y | Y | +| 3GPP TS 23.283 [18] | >> LMR specific security information (see NOTE 5) | Y | N | Y | Y | +| NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of TS 23.280 [5]. | | | | | | +| NOTE 2: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5]. | | | | | | +| NOTE 3: The use of this parameter by the MCData UE is outside the scope of the present document. | | | | | | +| NOTE 4: The LMR key management functional entity is part of the LMR system and is outside the scope of the present document. | | | | | | +| NOTE 5: This is an LMR specific parameter with no meaning within MC services. | | | | | | + +**Table A.3-3: MCData user profile configuration data (off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | MCData user database | +|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------|---------------|---------------------------------|----------------------| +| [R-7.2-003], [R-7.6-004] of 3GPP TS 22.280 [2] | List of off-network MCData groups for use by this MCData user | | | | | +| | > MCData Group ID | Y | N | Y | Y | +| | > Application plane server identity information of group management server where group is defined | | | | | +| | >> Server URI | Y | N | Y | Y | +| | > Application plane server identity information of identity management server which provides authorization for group (see NOTE 1) | | | | | +| | >> Server URI | Y | N | Y | Y | +| 3GPP TS 33.180 [13] | > KMSUri for security domain of group (see NOTE 2) | Y | N | Y | Y | +| | > Presentation priority of the group relative to other groups and users (see NOTE 3) | Y | N | Y | Y | +| [R-7.12-002], [R-7.12-003] of 3GPP TS 22.280 [2] | Authorization for off-network services | Y | N | Y | Y | +| Subclause 10.7.2 | User info ID (as specified in 3GPP TS 23.303 [7]) | Y | N | Y | Y | + +NOTE 1: If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of TS 23.280 [5]. + +NOTE 2: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5]. + +NOTE 3: The use of this parameter by the MCData UE is outside the scope of the present document. + +## A.4 MCData related Group configuration data + +The general aspects of group configuration are specified in 3GPP TS 23.280 [5]. + +Parameters specified in table A.4-1 are child parameters of the "MCData configuration" parameter specified in table A.4-1 in 3GPP TS 23.280 [5]. Parameters specified in table A.4-2 are child parameters of the "MCData configuration" parameter specified in table A.4-2 in 3GPP TS 23.280 [5]. Parameters specified in table A.4-3 are child parameters of the "MCData configuration" parameter specified in table A.4-3 in 3GPP TS 23.280 [5]. + +**Editor's note: Further contents of this configuration data are FFS.** + +**Table A.4-1: Group configuration data (on and off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Group management server | +|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-----------|---------------|-------------------------| +| [R-5.12-001] of 3GPP TS 22.280 [2] | >> Media confidentiality and integrity protection (see NOTE) | Y | Y | Y | +| [R-5.12-001] of 3GPP TS 22.280 [2] | >> Transmission control confidentiality and integrity protection (see NOTE) | Y | Y | Y | +| [R-5.12-001] of 3GPP TS 22.280 [2] | >> Group media protection security material (see NOTE) | Y | N | Y | +| Subclause 5 | >> MCData sub-services and features enabled for the group | | | | +| | >>> Short data service enabled | Y | Y | Y | +| | >>> File distribution enabled | Y | Y | Y | +| | >>> Conversation management enabled | Y | Y | Y | +| | >>> Transmission control enabled | Y | Y | Y | +| | >>> Reception control enabled | Y | Y | Y | +| | >>> Enhanced status enabled | Y | Y | Y | +| | >> Transmission and reception control | | | | +| [R-6.2.2.1-001] of 3GPP TS 22.282 [3] | >>> Whether MCData user is permitted to transmit data in the group | Y | Y | Y | +| [R-6.2.3-006] of 3GPP TS 22.282 [3] | >>> Maximum amount of data that the MCData user can transmit in a single request during group communication | Y | Y | Y | +| [R-6.2.3-006] of 3GPP TS 22.282 [3] | >>> Maximum amount of time that the MCData user can transmit in a single request during group communication | Y | Y | Y | +| | >> Enhanced status | | | | +| [R-6.1.3.2-002] of 3GPP TS 22.282 [3] | >>> List of operational status values | Y | N | Y | +| NOTE: Security mechanisms are specified in 3GPP TS 33.180 [13]. | | | | | + +**Table A.4-2: Group configuration data (on network)** + +| Reference | Parameter description | MCData UE | MCData Server | Group management server | +|--------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------|---------------|-------------------------| +| [R-6.4.5-001],<br>[R-6.4.5-003] of<br>3GPP TS 22.280 [2] | >> Authorisation of a user to request a list of affiliated members of a group | Y | Y | Y | +| [R-5.1.7-002],<br>[R-6.2.2-001],<br>[R-6.6.2.2-006],<br>[R-6.8.7.2-003] of<br>3GPP TS 22.280 [2] | >> Priority of the group | N | Y | Y | +| | >> Transmission and reception control | | | | +| | >>> Maximum data size for SDS | Y | Y | Y | +| | >>> Maximum data size for FD | Y | Y | Y | +| [R-6.2.2.1-003] | >>> Maximum data size for auto-receive | N | Y | Y | +| 3GPP TS 23.283 [18] | >> Indication whether use of LMR E2EE is permitted on the MCData group | Y | N | Y | +| 3GPP TS 23.283 [18] | >> LMR specific identity for MCData group (see NOTE) | Y | N | Y | +| 3GPP TS 23.283 [18] | >> Group to key binding (see NOTE) | Y | N | Y | +| NOTE: This is an LMR specific parameter with no meaning within MC services. | | | | | + +**Table A.4-3: Group configuration data (off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Group management server | +|------------------------------------------|------------------------------------------------------------------------------------------------|-----------|---------------|-------------------------| +| Subclause 10.10 of<br>3GPP TS 23.280 [5] | >> Default <b>ProSe</b> Per-Packet priority (as specified in 3GPP <b>TS 23.303</b> [7]) values | | | | +| | >>> MCData group call signalling | Y | N | Y | +| | >>> MCData group call media | Y | N | Y | + +## A.5 MCData service configuration data + +The general aspects of MC service configuration are specified in 3GPP TS 23.280 [5]. The MCData service configuration data is stored in the MCData server. + +Tables A.5-1 and A.5-2 describe the configuration data required to support the use of on-network MCData service. Tables A.5-1 and A.5-3 describe the configuration data required to support the use of off-network MCData service. Data in tables A.5-1 and A.5-3 can be configured offline using the CSC-11 reference point. + +**Table A.5-1: MCData service configuration data (on and off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | +|---------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|-----------|---------------|---------------------------------| +| | Transmission and reception control | | | | +| [R-6.2.2.1-002d],<br>[R-6.2.2.4-003] of<br>3GPP TS 22.282 [3] | > Time limit for the temporarily stored data waiting to be delivered to a receiving user | Y | Y | Y | +| [R-6.2.2.3-001] of<br>3GPP TS 22.282 [3] | > Timer for periodic announcement with the list of available recently invited data group communications | Y | Y | Y | + +**Table A.5-2: MCData service configuration data (on network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | +|-----------------|--------------------------------------------------------------------------|-----------|---------------|---------------------------------| +| | Transmission and reception control | | | | +| | > Maximum data size for SDS | Y | Y | Y | +| | > Maximum payload data size for SDS over signalling control plane (NOTE) | Y | Y | Y | +| | > Maximum data size for FD | Y | Y | Y | +| [R-6.2.2.1-003] | > Maximum data size for auto-receive | N | Y | Y | + +NOTE: The maximum payload data size for SDS over signalling control plane shall be less than or equal to the maximum data size for SDS. + +**Table A.5-3: MCData service configuration data (off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | +|------------------------------------------|----------------------------------------------------------------------------------------------|-----------|---------------|---------------------------------| +| Subclause 10.10 of<br>3GPP TS 23.280 [5] | Default <b>ProSe</b> Per-Packet priority (as specified in 3GPP <b>TS 23.303 [7]</b> ) values | | | | +| | > MCData one-to-one call signalling | Y | N | Y | +| | > MCData one-to-one call media | Y | N | Y | + +## Annex B (informative): Transmission control for MCData + +### B.1 Overview of transmission control process + +The MCData server may receive several simultaneous requests for data transmission, which may be associated with different types of communication e.g. group, private, 1-to-many. For each communication, the how the requests are processed may be different. The requests that are not authorized shall be rejected by the transmission control function. For auto-send requests, the processing should be immediate and is delivered to the recipients either via unicast or broadcast. However, for requests exceeding the auto-send limits, transmission control arbitration (see Annex B.2) will be necessary. Subsequent to transmission control arbitration, and subject to the policy e.g. store and forward, the data is either delivered directly to the recipient MCData user, or stored in the network repository and a corresponding URL is delivered. The end-to-end transmission control process is illustrated in figure B.1-1. + +Editor's note: The aspects related to data streaming and accuracy of the process is FFS. + +![Flowchart of the Transmission control process, showing UE and Network interactions for Private, 1-many, and Group communication.](fc3e2b49a9f850951570e502393b697f_img.jpg) + +``` + +graph TD + subgraph UE + A[MCDATA user interested to Send Data] --> B[Select Data to Send] + B --> C[Select Recipients] + C --> D{Multiple recipients?} + D -- No --> E[Private Communication] + D -- Yes --> F{Group?} + F -- No --> G[1-many Communication] + F -- Yes --> H[Group Communication] + end + subgraph Network + I{Authorized to Send?} -- No --> J[REJECTED] + I -- Yes --> K{Auto-send?} + K -- No --> L[Transmission Control Arbitration] + K -- Yes --> M{Broadcast?} + M -- No --> N[SEND DATA to recipient MCDATA user(s) via Unicast] + M -- Yes --> O[SEND DATA to recipient MCDATA user(s) via Broadcast] + L -- "1-many/Group Communication" --> P{Store and Forward?} + P -- No --> Q[SEND DATA to recipient MCDATA user] + P -- Yes --> R{SEND URL to recipient MCDATA user} + L -- "Private Communication" --> S{Store and Forward?} + S -- No --> T{Broadcast?} + T -- No --> U[SEND DATA to recipient MCDATA users via Unicast] + T -- Yes --> V[SEND DATA to recipient MCDATA users via Broadcast] + S -- Yes --> W{Broadcast?} + W -- No --> X[SEND URL to recipient MCDATA users via Unicast] + W -- Yes --> Y[SEND URL to recipient MCDATA users via Broadcast] + end + H --> I + G --> I + E --> I + N --> I + O --> I + Q --> I + R --> I + U --> I + V --> I + X --> I + Y --> I + +``` + +Flowchart of the Transmission control process, showing UE and Network interactions for Private, 1-many, and Group communication. + +Figure B.1-1: Transmission control process + +## B.2 Transmission control arbitration + +The transmission control arbitration is a central function of transmission control process. In a typical deployment, multiple or simultaneous requests can be received at the transmission control arbitration function. Each of these requests may be categorized into different request types with different queuing priorities, and therefore each request type will be maintained with separate queues. Each request shall not be present in more than one queue at any given time. The queue types and the order of queues may be configured by the MCDATA administrator, as described below. + +- Transmission control queue: It is the primary queue from which the request is processed for transmission e.g. emergency communication requests may result in this queue and processed at the highest priority. +- Communication type queue: This queue may be sorted in the order of the communication type associated with the request. For example, the group communication requests may always take precedence over one-to-many or private communication requests. +- Static attribute queue: This queue may be formed based on the static attributes associated with the request e.g. group priority, user priority, which may be pre-configured by the MCDATA administrator. +- Dynamic attribute queue: This queue may be formed based on the dynamic attributes associated with the request e.g. location of the sending user, content size, etc. + +Editor's note: The queue categories and the order of the queues is FFS. + +## Annex C (informative): Secure IP connectivity requirements + +This annex contains a description of how mission critical organisation may use existing 3GPP solutions to provide a data connection at a fixed defined quality of service level. + +Editor's note: For R14 there is no normative work for MCData secure IP connectivity. Further study in R15 will investigate how to complete compliance with the stage 1 requirements including incoming setup to a UE, UE to UE connection and MCData service control of access. + +An MCData service IP data access **APN** is configured to provide connectivity to reach the required PDN within the MC service provider's control with a defined level of quality of service as defined by **QCI** and ARP. In some instances, the use of the **APN** will be sufficient to provide the required security for the connection. If that is not the case, the MC service provider may use available techniques to further secure parts of the connection through the **EPC**. + +The MCData UE is configured with security policy to identify which IP data traffic is required to use the MCData service IP data access **APN**. + +When the MCData UE requires to access an application to be used with the additional level of security, the local application within the MCData UE commences access. If the policy allows use of the MCData service IP data access **APN**, then the MCData UE establishes connection to the required end point via the PDN provided for the MC service IP data access. + +End to end security is established as required by the local application in the UE and the remote application in the network. + +--- + +## Annex D (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|------|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | R ev | Cat | Subject/Comment | New version | +| 2016-07 | | | | | | Initial version. | 0.0.0 | +| 2016-08 | | | | | | Update following SA6#12 incorporating the following pCRs: S6-160810; S6-160875; S6-160876 | 0.1.0 | +| 2016-10 | | | | | | Update following SA6#13 incorporating the following pCRs: S6-161169; S6-161170; S6-161243; S6-161265; S6-161085; S6-161173; S6-161174; S6-161245; S6-161176; S6-161248; S6-161177; S6-161178; S6-161266; S6-161267; S6-161184 | 0.2.0 | +| 2016-11 | | | | | | Update following SA6#14 incorporating the following pCRs: S6-161316; S6-161586; S6-161609; S6-161587; S6-161589; S6-161506; S6-161576; S6-161507; S6-161326; S6-161508; S6-161577; S6-161511; S6-161512; S6-161616; S6-161514; S6-161515; S6-161516; S6-161580; S6-161581; S6-161519; S6-161498; S6-161642 | 0.3.0 | +| 2016-11 | SA#74 | SP-160878 | | | | Submitted for Approval at SA#74 | 1.0.0 | +| 2016-12 | SA#74 | SP-160878 | | | | MCC Editorial update for publication after TSG SA approval (SA#74) | 14.0.0 | +| 2017-03 | SA#75 | SP-170071 | 0002 | 2 | F | Alignment of definitions | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0003 | 2 | F | Alignment of group affiliation and de-affiliation requirements | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0004 | 1 | F | Alignment of bearer management | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0005 | 2 | D | Adding descriptive text for the FD procedure section | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0006 | 2 | D | Resolving editor's notes for the short data service feature | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0007 | 1 | D | Adding references for the signalling control plane | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0008 | 2 | D | Adding descriptive text for the transmission and reception control section | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0009 | | F | MCData correction of reference | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0010 | | F | Alignment of business relationships, identities, and application of functional model to deployments | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0011 | 3 | F | file download editorials | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0013 | 1 | F | Off-network conversation management | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0014 | 1 | D | Editorial corrections | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0015 | 1 | F | Resolving EN in Scope | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0016 | 5 | F | Resolving EN in Functional model | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0017 | 1 | F | Resolving EN in SDS procedures | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0018 | | F | Referring generic procedures from CFA | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0020 | 2 | F | Conversation management definitions | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0021 | 2 | F | Disposition alignments and corrections in SDS and FD | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0022 | 1 | F | Tx and Rx control procedure corrections | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0025 | 1 | F | MCData functional model alignment | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0027 | 1 | F | Moving configuration data to on-network only | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0028 | 3 | F | Resolve SDS on-network information flows EN | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0030 | 1 | F | Resolve FD information flows EN | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0031 | 2 | F | Adding end-to-end encryption requirements | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0032 | 1 | F | Resolve transmission control information flows EN | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0033 | 2 | F | Resolve conversation management EN | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0034 | 1 | F | Addition of definition for MCData ID | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0035 | | F | Addition of definition for MCData ID | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0036 | 3 | F | Off-network information flows for SDS | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0037 | 1 | F | Resolve communication release information flows EN | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0038 | 1 | F | Conditions for using SDS media plane | 14.1.0 | +| 2017-06 | SA#76 | SP-170392 | 0039 | 2 | F | Correction on MCData reference points when using MBMS | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0048 | | D | Additions to Definition and Abbreviations | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0049 | 2 | F | Clarifications to section 5 Arcitecture requirements | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0051 | 1 | F | Clarifications to section 6.5.1 that SDS Distribution function in MCData server talks to SDS function in MCData client not UE | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0052 | | F | Clarifications to section 6.5.3.1.2 | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0054 | 1 | D | Correct wrong reference in section 7.2 | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0056 | 3 | F | Correct the MCData data disposition notification IEs | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0058 | 1 | D | Consistent use of pre-condition in section 7.4.2.2.2 | 14.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|----------------------------------------------------------------------|--------| +| 2017-06 | SA#76 | SP-170392 | 0059 | 1 | F | Inconsistent use of MCData group ID or list of recipients in request | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 61 | 3 | F | Content reference URL should be a mandatory IE when uploading a file | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 62 | 5 | F | Addition of new configuration and miscellaneous corrections | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 63 | 5 | F | Addition of identity management server address per group | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 64 | | F | Correction on sending data with mandatory download | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 70 | 2 | F | Inclusion of KMSUri to allow multiple security domains | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 71 | 4 | F | Clarification to Auto-send | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 76 | | F | Corrections to Group configuration data for all MC services | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 78 | 2 | F | CR to 23.282 on Auto-receive | 14.2.0 | +| 2017-06 | SA#76 | SP-170394 | 40 | 4 | B | Information flow of File Distribution for off-network | 15.0.0 | +| 2017-06 | SA#76 | SP-170394 | 41 | 1 | B | Functional model of File Distribution for off-network | 15.0.0 | +| 2017-06 | SA#76 | SP-170394 | 75 | 1 | C | Functional model of File Distribution for off-network | 15.0.0 | +| 2017-09 | SA#76 | SP-170682 | 79 | 2 | B | Introduction of SDS application type identifiers | 15.1.0 | +| 2017-09 | SA#76 | SP-170685 | 80 | 1 | B | Addition of IWF and IWF-2 | 15.1.0 | +| 2017-09 | SA#76 | SP-170681 | 83 | 1 | A | File size check for FD | 15.1.0 | +| 2017-09 | SA#76 | SP-170681 | 85 | 1 | A | Correction to configuration for Auto-receive parameter | 15.1.0 | +| 2018-01 | SA#78 | SP-170891 | 87 | 1 | F | SDS location field: Alignment of Stage 2 with Stage 1 & Stage 3 | 15.2.0 | +| 2018-01 | SA#78 | SP-170891 | 88 | 1 | D | Editorial changes to MCData stage 2 | 15.2.0 | +| 2018-01 | SA#78 | SP-170895 | 89 | 1 | F | Adding application identifier in media plane SDSs | 15.2.0 | +| 2018-01 | SA#78 | SP-170891 | 90 | 1 | F | Off-network Conversation Management clarifications | 15.2.0 | +| 2018-01 | SA#78 | SP-170889 | 94 | 2 | A | PSI configuration for MCData service | 15.2.0 | +| 2018-01 | SA#78 | SP-170891 | 95 | 1 | F | Completion of Communication Release | 15.2.0 | +| 2018-01 | SA#78 | SP-170894 | 96 | 1 | F | MBMS packet recovery | 15.2.0 | +| 2018-04 | SA#79 | SP-180148 | 99 | 1 | A | Correction of security specification references | 15.3.0 | +| 2018-04 | SA#79 | SP-180155 | 100 | 3 | B | LMR E2EE user profile and group parameters | 15.3.0 | +| 2018-04 | SA#79 | SP-180148 | 102 | 2 | A | Payload size limit for standalone SDS over signalling control plane | 15.3.0 | +| 2018-04 | SA#79 | SP-180151 | 103 | 1 | F | Update of references to stage 1 specifications | 15.3.0 | +| 2018-04 | SA#79 | SP-180148 | 107 | 1 | A | Duplicated procedure name for MCData Group SDS | 15.3.0 | +| 2018-06 | SA#80 | SP-180367 | 109 | | A | Clarification for presentation priority in MCData UE configuration | 15.4.0 | +| 2018-06 | SA#80 | SP-180370 | 110 | 3 | A | Modify MCData download data response | 15.4.0 | +| 2018-09 | SA#81 | SP-180677 | 111 | 2 | C | Media storage function in the MCData server | 16.0.0 | +| 2018-09 | SA#81 | SP-180677 | 113 | 3 | C | Adding the Network base Message Store | 16.0.0 | + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/marked/Rel-16/23_series/23784/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-16/23_series/23784/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8fb1ac359546500bbf2a24220594dcbc132d53d --- /dev/null +++ b/marked/Rel-16/23_series/23784/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a251153a7d2d726586c5b38fa3f278f5a67572a27e2094cdbeb2bc801cb90ac +size 27336 diff --git a/marked/Rel-16/23_series/23784/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/Rel-16/23_series/23784/16152cf1d84aea10848758f51a91ff6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da810099bf3a763ace7a9d417a6dcf88d407f804 --- /dev/null +++ b/marked/Rel-16/23_series/23784/16152cf1d84aea10848758f51a91ff6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc031065261e27ce4cf40bc00df445e0f616e659888066a22ce466202e09c915 +size 22250 diff --git a/marked/Rel-16/23_series/23784/171115f072e42b379238ed0dd438e9d7_img.jpg b/marked/Rel-16/23_series/23784/171115f072e42b379238ed0dd438e9d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52a87ba02bef9865ff2cc05b12129bf8c2310c35 --- /dev/null +++ b/marked/Rel-16/23_series/23784/171115f072e42b379238ed0dd438e9d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bde88b2e2d9565478b429fe4fa7e4c92d2c4a34a05d121d83dd9c6c5833c8d80 +size 62024 diff --git a/marked/Rel-16/23_series/23784/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg b/marked/Rel-16/23_series/23784/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9ee65c6ee414c2d5e869abe4d258ba0c8a20487 --- /dev/null +++ b/marked/Rel-16/23_series/23784/18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e1e558b1ef6d817556a147f4691da6f1575bc22b65870e374e8cbab593e7612 +size 25384 diff --git a/marked/Rel-16/23_series/23784/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23784/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4b5c0e58054e8251f5ccd66b46839d2147450d9 --- /dev/null +++ b/marked/Rel-16/23_series/23784/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86d57363f5ae5ae9af6e97db49aca946671bb4008c06e654b6f67ef94bedb5be +size 42644 diff --git a/marked/Rel-16/23_series/23784/2834bdd6eb8540277e609decbb924003_img.jpg b/marked/Rel-16/23_series/23784/2834bdd6eb8540277e609decbb924003_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ff9a67fbabdb75112af6f9e38f2c84635d54163 --- /dev/null +++ b/marked/Rel-16/23_series/23784/2834bdd6eb8540277e609decbb924003_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e4f579beaaf5a28e5c088bd57a7e8f782403a512371c18ac12e1903736253d92 +size 16243 diff --git a/marked/Rel-16/23_series/23784/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/Rel-16/23_series/23784/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b77622b3f44950b7bbf8674ba6b945f679fc425 --- /dev/null +++ b/marked/Rel-16/23_series/23784/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b4d6cba8ee04898e66f9c6b92abe18821b18ece0c10363f98f8b622834dd0ba +size 31662 diff --git a/marked/Rel-16/23_series/23784/410562339ce067fdc6fa41940c118658_img.jpg b/marked/Rel-16/23_series/23784/410562339ce067fdc6fa41940c118658_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91f3aad91361bcc5e6dd07fc384fbff6b0163557 --- /dev/null +++ b/marked/Rel-16/23_series/23784/410562339ce067fdc6fa41940c118658_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:68c49a631b771389aeb7789b5b81295df942b8ef503878fc0174d75fb202ade4 +size 29073 diff --git a/marked/Rel-16/23_series/23784/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23784/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7c92fa8ef7039e8517b88cdd81f689bc2d40e84 --- /dev/null +++ b/marked/Rel-16/23_series/23784/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05808f377452180aff32f28ae9fdcc293dd3cf5fffb8f2ea78633ae76950119f +size 73200 diff --git a/marked/Rel-16/23_series/23784/4792a2ccd62226861fadc22117edb7b1_img.jpg b/marked/Rel-16/23_series/23784/4792a2ccd62226861fadc22117edb7b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91b977d170a951cd392b581adb2393a491bfd5b2 --- /dev/null +++ b/marked/Rel-16/23_series/23784/4792a2ccd62226861fadc22117edb7b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2088fec1e881c5815c3c9ee9063412ffa4c5483ccee9ae66882b40c7bfe60009 +size 89879 diff --git a/marked/Rel-16/23_series/23784/4af57aad638888edf2062306f8a54a6c_img.jpg b/marked/Rel-16/23_series/23784/4af57aad638888edf2062306f8a54a6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28da696135ebede230a455d73321e8c5e9965092 --- /dev/null +++ b/marked/Rel-16/23_series/23784/4af57aad638888edf2062306f8a54a6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b928dbff7bb89e757668a1ca42eb644fc111b0b434f26f2a04389d97133fecb2 +size 84203 diff --git a/marked/Rel-16/23_series/23784/5d76c2e9976aaf97001ee189908830fb_img.jpg b/marked/Rel-16/23_series/23784/5d76c2e9976aaf97001ee189908830fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34955aff862d6249407bbe75649478d6ba3cafb9 --- /dev/null +++ b/marked/Rel-16/23_series/23784/5d76c2e9976aaf97001ee189908830fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78d9c611a409f92c2d2c5ee919e9af7fa3a959e7eab77207885982c7566eda58 +size 86982 diff --git a/marked/Rel-16/23_series/23784/6f31cdb576d2f15c35c3f266e5f59211_img.jpg b/marked/Rel-16/23_series/23784/6f31cdb576d2f15c35c3f266e5f59211_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef7e7cb74f1a541688e13c7176a9c4d273d4245f --- /dev/null +++ b/marked/Rel-16/23_series/23784/6f31cdb576d2f15c35c3f266e5f59211_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c02ab729ffe37abc6d61f75006d75b8dd76d1e8e99e58358673b577cf29230d0 +size 62438 diff --git a/marked/Rel-16/23_series/23784/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/Rel-16/23_series/23784/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eede23e834e7a3df2ff22c14ac7a4577d4aff199 --- /dev/null +++ b/marked/Rel-16/23_series/23784/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cbb1461a1dcede77016601d63f4782dff55363fc8d3f1ca002ad04d488370aed +size 16949 diff --git a/marked/Rel-16/23_series/23784/7a1dee155822446f7828dcb055c465c3_img.jpg b/marked/Rel-16/23_series/23784/7a1dee155822446f7828dcb055c465c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b740312498287c683658b496c6e57ef583572d6f --- /dev/null +++ b/marked/Rel-16/23_series/23784/7a1dee155822446f7828dcb055c465c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6688564e06b9f8636d5397113435c67ff43fd843e04861edf32f0af39571b4c9 +size 26468 diff --git a/marked/Rel-16/23_series/23784/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23784/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8e86f62baa2cf25b07c02491d01263849b26f17 --- /dev/null +++ b/marked/Rel-16/23_series/23784/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28ebd07606f40662a31cb2d0f373a6eb6869063986f82c921973e3fabc368f9a +size 22365 diff --git a/marked/Rel-16/23_series/23784/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23784/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..609c44119f7c099288d28c17ebee428deb3f2de6 --- /dev/null +++ b/marked/Rel-16/23_series/23784/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98f3db118f21a7b497cfc136cc7bbb378cf804e3342d70039ca247adebfd459a +size 95136 diff --git a/marked/Rel-16/23_series/23784/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg b/marked/Rel-16/23_series/23784/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f90e9c2731cabcc78eb752a1f06ff3e216bad4c9 --- /dev/null +++ b/marked/Rel-16/23_series/23784/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e328f33a3356bef036015f4a32c6750cd1e65910c1571cc87b9a0586dd3487cf +size 16612 diff --git a/marked/Rel-16/23_series/23784/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/marked/Rel-16/23_series/23784/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..621a946230ee13faa4afc1d61fe536b83f1bc4a3 --- /dev/null +++ b/marked/Rel-16/23_series/23784/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6117b5645f275db704288a76150694f76e82e0f3c1179b5b950d50e2b423e89 +size 28247 diff --git a/marked/Rel-16/23_series/23784/9d70cd4e4cef3f16262b47c8c8f6c642_img.jpg b/marked/Rel-16/23_series/23784/9d70cd4e4cef3f16262b47c8c8f6c642_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c283b5bd7663b0172961ae57c6e164e4b49b813f --- /dev/null +++ b/marked/Rel-16/23_series/23784/9d70cd4e4cef3f16262b47c8c8f6c642_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:653eb1e02ed4c454f50d6de4dcd2356ac8e82c5cfc2783e3aa98d8ba0596245e +size 17505 diff --git a/marked/Rel-16/23_series/23784/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23784/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e27414a97fb2160446906280409cf9586e27fa6 --- /dev/null +++ b/marked/Rel-16/23_series/23784/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a019b2e330053c73580f677b238e3585a28e42108d89a44c42d089572ba3e87 +size 62703 diff --git a/marked/Rel-16/23_series/23784/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Rel-16/23_series/23784/c2fc2621e8206d24427b56bcb2398fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f02d0e90a3fe3b0f1166e938d192e1da847dcccc --- /dev/null +++ b/marked/Rel-16/23_series/23784/c2fc2621e8206d24427b56bcb2398fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a86353f11f789274576be145f4ee7212ea0e95ee56796307d4f3bf28eb1a0c7e +size 35820 diff --git a/marked/Rel-16/23_series/23784/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/marked/Rel-16/23_series/23784/c78c2eefd86269d1740ab85a916f24f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f252296bf5a08670c048228a066aa89bd28af27 --- /dev/null +++ b/marked/Rel-16/23_series/23784/c78c2eefd86269d1740ab85a916f24f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f5a1d79baa18e631fb7de7cf7bfe1493cfb30ee73108fc1cffaf8090f34fde2 +size 17111 diff --git a/marked/Rel-16/23_series/23784/d793cf7c174b89eb024d132f00679787_img.jpg b/marked/Rel-16/23_series/23784/d793cf7c174b89eb024d132f00679787_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..519ee53802739eea8c948614a4824e6cd632d073 --- /dev/null +++ b/marked/Rel-16/23_series/23784/d793cf7c174b89eb024d132f00679787_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c716a6dc25607a71c8bbecb6c5d6cf5ee6c63a1904a40f9db6807b0e6920b31e +size 36985 diff --git a/marked/Rel-16/23_series/23784/dd380ccd5aca1151074fede04826f1a4_img.jpg b/marked/Rel-16/23_series/23784/dd380ccd5aca1151074fede04826f1a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..368fa7000397c03b22f4f3aa88001605ea1741b9 --- /dev/null +++ b/marked/Rel-16/23_series/23784/dd380ccd5aca1151074fede04826f1a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2983f6b0f3ee264f1f83691da46c6fb514467f5ea395980f3bb914799305cfdd +size 80555 diff --git a/marked/Rel-16/23_series/23784/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/Rel-16/23_series/23784/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74a71e6121c9f66901cb94a708306ddc90b3d573 --- /dev/null +++ b/marked/Rel-16/23_series/23784/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa7e18746e60a4ba1de79ff29349b0c2c9eb7558ec867234d715d934814c32de +size 85327 diff --git a/marked/Rel-16/23_series/23784/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-16/23_series/23784/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..43cfa16e5a10945899b4ec4735b922ace9308b16 --- /dev/null +++ b/marked/Rel-16/23_series/23784/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39fda97fc0fa6f890b1188a87fc074ecf35c68d0cdf9a301ee3dd9c6ca5114f1 +size 28027 diff --git a/marked/Rel-16/23_series/23784/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/marked/Rel-16/23_series/23784/e9d825d87c5f85c8dba0664eace96ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..56132daaa145f6d0cdc7a33906898d5a6bad8339 --- /dev/null +++ b/marked/Rel-16/23_series/23784/e9d825d87c5f85c8dba0664eace96ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f624000b5dcc1dd49f6325146ff777c1240d49a0e0973f795142b269808b4b3b +size 43017 diff --git a/marked/Rel-16/23_series/23784/f57a881fcbcaf494a7dedc4f61224991_img.jpg b/marked/Rel-16/23_series/23784/f57a881fcbcaf494a7dedc4f61224991_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cb87c3db475c3d4b1dc4a2f430809dcbd72541b --- /dev/null +++ b/marked/Rel-16/23_series/23784/f57a881fcbcaf494a7dedc4f61224991_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1597198c331e4069e43b46df5c7aa15a85bc834e8b9aa2b842157469d2af2644 +size 33008 diff --git a/marked/Rel-16/23_series/23784/f6e8acf9f931452d01688d311b5c0364_img.jpg b/marked/Rel-16/23_series/23784/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6c9496c93fc78a670cf0f7625987bb323a0c0a3 --- /dev/null +++ b/marked/Rel-16/23_series/23784/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1f23fc2f1cff5e79e8e0604a86d34bee8fc206085e24f60ef0bd040df3b3cb4 +size 40898 diff --git a/marked/Rel-16/23_series/23784/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23784/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb3855ee750f7035afe2889faa0a3ffe84603e80 --- /dev/null +++ b/marked/Rel-16/23_series/23784/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95f413ea917365cbc9dd2d3b7146901e3547303a6bc9007a8fd0b9639b4fedea +size 20084 diff --git a/marked/Rel-16/23_series/23784/raw.md b/marked/Rel-16/23_series/23784/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d0ab516fb34ce9d39f883d64d7e4f812e2638b5c --- /dev/null +++ b/marked/Rel-16/23_series/23784/raw.md @@ -0,0 +1,2337 @@ +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 Scenarios ..... | 8 | +| 4.1 General ..... | 8 | +| 4.2 Scenario 1: Discreet listening of MCPTT and MCVideo private calls..... | 8 | +| 4.2.1 Scenario 1.1: Discreet listening of MCPTT and MCVideo private calls in same MC service server ..... | 8 | +| 4.2.2 Scenario 1.2: Discreet listening of MCPTT and MCVideo private calls with target receiving service from different MC service server ..... | 9 | +| 4.3 Scenario 2: Discreet listening of MCPTT and MCVideo group calls..... | 10 | +| 4.4 Scenario 3: Discreet listening of MCVideo pull ..... | 11 | +| 4.4.1 Scenario 3.1: Discreet listening of one to one MCVideo pull..... | 11 | +| 4.4.2 Scenario 3.2: Discreet listening of one from server MCVideo pull ..... | 12 | +| 4.5 Scenario 4: Discreet listening of MCVideo push..... | 12 | +| 4.5.1 Scenario 4.1: Discreet listening of one to one MCVideo push ..... | 12 | +| 4.5.2 Scenario 4.2: Discreet listening of one to server MCVideo push ..... | 13 | +| 4.5.3 Scenario 4.3: Discreet listening of remotely initiated MCVideo push..... | 13 | +| 4.6 Scenario 5: Discreet listening of MCData SDS ..... | 14 | +| 4.7 Scenario 6: Discreet listening of MCData file distribution..... | 15 | +| 4.7.1 Scenario 6.1: Discreet listening of file upload and file download..... | 15 | +| 4.7.2 Scenario 6.2: Discreet listening of one to one file distribution ..... | 15 | +| 4.8 Scenario 7: Logging scenarios ..... | 16 | +| 4.8.1 General ..... | 16 | +| 4.9 Scenario 8: Limitations on discreet listening due to regulatory constraints and operator security policies .... | 17 | +| 4.9.1 Scenario 8.1: Private communication transmissions..... | 17 | +| 4.9.2 Scenario 8.2: Group communication transmissions ..... | 17 | +| 5 Key Issues ..... | 18 | +| 5.1 Key Issue 1: Selection of MC service for discreet listening ..... | 18 | +| 5.2 Key issue 2: Group membership of authorized MC user for discreet listening ..... | 19 | +| 5.3 Key issue 3: Discreet listening for MCVideo push and pull and MCData file upload and download ..... | 19 | +| 5.4 Key issue 4: Discreet listening of end to end encrypted calls..... | 20 | +| 5.5 Key issue 5: Logging and replay of end to end encrypted calls..... | 20 | +| 5.6 Key issue 6: Source MC service server for discreet listening of user in group call..... | 21 | +| 5.7 Key issue 7: Discreet listening and logging for interconnected MC system ..... | 21 | +| 5.8 Key issue 8: Discreet listening and logging for migrated MC service user ..... | 22 | +| 5.9 Key Issue 9: Discreet listening and logging for user receiving MC service on multiple devices..... | 22 | +| 5.10 Key Issue 10: Logging of MC service users and MC service groups ..... | 23 | +| 5.11 Key Issue 11: Logging of MCData content server and message store services..... | 23 | +| 5.12 Key Issue 12: Discreet listening of MCData content server and message store services ..... | 24 | +| 5.13 Key issue 13: Discreet listening towards an MC service group..... | 24 | +| 5.14 Key Issue 14: Limitations on discreet listening due to regulatory constraints and operator security policies ..... | 24 | +| 6 Solutions..... | 25 | +| 6.1 Solution 1: Functionality for discreet listening ..... | 25 | +| 6.1.1 Description ..... | 25 | +| 6.1.1.1 Functional model ..... | 25 | +| 6.1.1.2 Configuration ..... | 25 | +| 6.1.1.3 Procedures..... | 26 | +| 6.1.1.3.1 General ..... | 26 | +| 6.1.1.3.2 Discreet listening invocation and revocation procedures..... | 26 | +| 6.1.1.3.3 Provision of discreet listening content for private communications ..... | 26 | +| 6.1.1.3.4 Provision of discreet listening content for group communications..... | 27 | + +| | | | +|-----------|----------------------------------------------------------------------------------------|----| +| 6.1.1.3.5 | Information flows for discreet listening ..... | 28 | +| 6.1.2 | Impacts on existing nodes and functionality ..... | 28 | +| 6.1.3 | Solution Evaluation ..... | 28 | +| 6.2 | Solution 2: Discreet listening of MCVideo push and pull ..... | 28 | +| 6.2.1 | Description ..... | 28 | +| 6.2.1.1 | Overview ..... | 28 | +| 6.2.1.2 | Invocation ..... | 29 | +| 6.2.1.3 | MCVideo push discreet listening procedure ..... | 29 | +| 6.2.1.4 | MCVideo pull discreet listening procedure ..... | 30 | +| 6.2.1.5 | Information flows for discreet listening of MCVideo push and pull ..... | 31 | +| 6.2.2 | Impacts on existing nodes and functionality ..... | 31 | +| 6.2.3 | Solution Evaluation ..... | 32 | +| 6.3 | Solution 3: Functionality for on-network logging and replay ..... | 32 | +| 6.3.1 | Description ..... | 32 | +| 6.3.1.1 | Functional model ..... | 32 | +| 6.3.1.2 | Configuration ..... | 34 | +| 6.3.1.3 | Procedures ..... | 35 | +| 6.3.2 | Impacts on existing nodes and functionality ..... | 36 | +| 6.3.3 | Solution Evaluation ..... | 36 | +| 6.4 | Solution 4: On-network logging for interconnection and migration ..... | 37 | +| 6.4.1 | Description ..... | 37 | +| 6.4.1.1 | General ..... | 37 | +| 6.4.1.2 | Functional model ..... | 37 | +| 6.4.1.3 | Configuration ..... | 38 | +| 6.4.1.3.1 | General ..... | 38 | +| 6.4.1.3.2 | Logging of group communications in partner system ..... | 38 | +| 6.4.1.3.3 | Logging of individual communications – option 1 ..... | 39 | +| 6.4.1.3.4 | Logging of individual communications – option 2 ..... | 39 | +| 6.4.1.3.5 | Logging of individual communications – option 3 ..... | 39 | +| 6.4.1.4 | Procedures ..... | 40 | +| 6.4.2 | Impacts on existing nodes and functionality ..... | 40 | +| 6.4.3 | Solution Evaluation ..... | 40 | +| 6.5 | Solution 5: Discreet listening for interconnection and migration ..... | 40 | +| 6.5.1 | Description ..... | 40 | +| 6.5.1.1 | Functional model ..... | 40 | +| 6.5.1.2 | Configuration ..... | 40 | +| 6.5.1.2.1 | General ..... | 40 | +| 6.5.1.2.2 | User profile authorization of discreet listening – option 1 ..... | 41 | +| 6.5.1.2.3 | Sharing the user profile for authorized users – option 2 ..... | 41 | +| 6.5.1.2.4 | New configuration table of authorized users – option 3 ..... | 42 | +| 6.5.1.3 | Procedures ..... | 42 | +| 6.5.2 | Impacts on existing nodes and functionality ..... | 42 | +| 6.5.3 | Solution Evaluation ..... | 42 | +| 6.6 | Solution 6: Discreet listening to an MCPTT group ..... | 43 | +| 6.6.1 | Description ..... | 43 | +| 6.6.1.1 | Overview ..... | 43 | +| 6.6.1.2 | Configuration ..... | 43 | +| 6.6.1.3 | Procedures ..... | 44 | +| 6.6.1.3.1 | Discreet listening activation and deactivation ..... | 44 | +| 6.6.1.3.2 | Provision of discreet listening to groups ..... | 44 | +| 6.6.1.3.3 | Release discreet listening to groups ..... | 45 | +| 6.6.1.4 | Information flows ..... | 46 | +| 6.6.2 | Impacts on existing nodes and functionality ..... | 48 | +| 6.6.3 | Solution Evaluation ..... | 48 | +| 6.7 | Solution 7: Logging of MCData message store and MCData content server ..... | 48 | +| 6.7.1 | Description ..... | 48 | +| 6.7.1.1 | Overview ..... | 48 | +| 6.7.1.2 | Logging of MCData message store services ..... | 48 | +| 6.7.1.3 | Logging of MCData content server transactions ..... | 49 | +| 6.7.2 | Impacts on existing nodes and functionality ..... | 50 | +| 6.7.3 | Solution Evaluation ..... | 50 | +| 6.8 | Solution 8: Discreet listening of MCData message store and MCData content server ..... | 50 | + +| | | | +|------------------------|------------------------------------------------------------------------------------------------------------------|----| +| 6.8.1 | Description ..... | 50 | +| 6.8.1.1 | Overview..... | 50 | +| 6.8.1.2 | Discreet listening of MCData message store services ..... | 50 | +| 6.8.1.3 | Discreet listening of MCData content server transactions..... | 51 | +| 6.8.2 | Impacts on existing nodes and functionality ..... | 52 | +| 6.8.3 | Solution Evaluation ..... | 52 | +| 6.9 | Solution 9: Functionality for discreet listening with regulatory constraints and operator security policies..... | 52 | +| 6.9.1 | Description ..... | 52 | +| 6.9.1.1 | Functional model ..... | 52 | +| 6.9.1.2 | Configuration..... | 53 | +| 6.9.1.3 | Procedures..... | 53 | +| 6.9.1.3.1 | General ..... | 53 | +| 6.9.1.3.2 | Discreet listening invocation and revocation procedures..... | 53 | +| 6.9.1.3.3 | Provision of discreet listening content for private communications ..... | 54 | +| 6.9.1.3.4 | Provision of discreet listening content for group communications..... | 55 | +| 6.9.1.3.5 | Information flows for discreet listening ..... | 55 | +| 6.9.2 | Impacts on existing nodes and functionality ..... | 55 | +| 6.9.3 | Solution Evaluation ..... | 56 | +| 6.10 | Solution 10: Functionality for on-network logging and replay ..... | 56 | +| 6.10.1 | Description ..... | 56 | +| 6.10.1.1 | Functional model ..... | 56 | +| 6.10.1.2 | Configuration..... | 57 | +| 6.10.1.3 | Procedures..... | 57 | +| 6.10.2 | Impacts on existing nodes and functionality ..... | 57 | +| 6.10.3 | Solution Evaluation ..... | 58 | +| 7 | Overall Evaluation ..... | 58 | +| 7.1 | General ..... | 58 | +| 7.2 | Solution evaluation..... | 58 | +| 7.3 | Key issues with security implications ..... | 62 | +| 8 | Conclusions..... | 62 | +| Annex A: | Reproduction of stage 1 requirements ..... | 62 | +| A.1 | Requirements for discreet listening..... | 62 | +| A.2 | Requirements for recording and audit..... | 63 | +| Annex B (informative): | Change history ..... | 64 | + +# --- Foreword + +This Technical Specification has been produced by the 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. + +# --- 1 Scope + +The present document studies solutions to satisfy the requirements for discreet listening and logging for mission critical services. It identifies enhancements to be included in the technical specifications for MCPTT, MCVideo, MCData and in the common functional architecture to support mission critical services. Requirements for this study are taken from the Stage 1 requirements, including 3GPP TS 22.280 [2], and 3GPP TS 22.281 [3]. + +# --- 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe)" +- [3] 3GPP TS 22.281: "Mission Critical Video services" +- [4] 3GPP TS 22.179: "Mission Critical Push To Talk (MCPTT); Stage 1" +- [5] 3GPP TS 22.282: "Mission Critical Data services" +- [6] 3GPP TS 33.180: "Security of the mission critical service" +- [7] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2" +- [8] 3GPP TS 23.281: "Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2". +- [9] 3GPP TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2". +- [10] 3GPP TS 24.379: "Mission Critical Push To Talk (MCPTT) call control; Protocol specification" +- [11] 3GPP TS 24.281: "Mission Critical Video (MCVideo) signalling control; Protocol specification" +- [12] 3GPP TS 24.282: "Mission Critical Data (MCData) signalling control; Protocol specification" + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Discreet listening:** A means for an authorized user to be provided with the communications of a target user, without any unauthorized user in the communications being aware. + +**Migrated MC system:** The partner MC system to which an MC service user has migrated, and in which that migrated MC service user is receiving MC service. + +**Security Domain:** A set of MC users who share common security requirements and policies for their communications. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-----|-------------------------| +| FD | File Distribution | +| GMK | Group Master Key | +| GMS | Group Management Server | +| MC | Mission Critical | +| SDS | Short Data Service | + +# 4 Scenarios + +## 4.1 General + +The following subclauses describe scenarios that will arise from a request from an authorized MC user for discreet listening of the communications of a second MC user within the authority of the authorized MC user. Use cases for MCPTT, MCVideo and MCData are captured. + +In each case, the authorized MC user will be presented with media which has originated from or is destined for the target MC user of the discreet listening request. If this media is protected by encryption and other security measures, the mechanism by which the actual content of the media is revealed to the authorized MC user is outside the scope of the present document. + +## 4.2 Scenario 1: Discreet listening of MCPTT and MCVideo private calls + +### 4.2.1 Scenario 1.1: Discreet listening of MCPTT and MCVideo private calls in same MC service server + +This scenario describes the case where authorized MC user A requests discreet listening for communications involving MC user B where MC user A and MC user B are served by the same MC service server, MC service server A and MC service user B is within the authority of authorized MC user A. The scenario is illustrated in figure 4.2.1-1 below. + +![Diagram illustrating Scenario 1.1: Discreet listening of MCPTT or MCVideo private call in single MC service server. The diagram shows three main components: MC user B (MC service client B) on the left, MC user C (MC service client C) on the right, and MC service server A in the center. MC user B and MC user C are connected to MC service server A via dashed lines. MC service server A is connected to Authorized MC user A (MC service client A) via a dashed line. The diagram illustrates that MC user A is requesting discreet listening of communications involving MC user B, which are being processed by MC service server A.](18f841ac4f2ef28f34a026f1bdc5af9a_img.jpg) + +``` +graph TD; B["MC user B +MC service client B"] -.-> A["MC service server A"]; C["MC user C +MC service client C"] -.-> A; A -.-> D["Authorized MC user A +MC service client A"]; +``` + +Diagram illustrating Scenario 1.1: Discreet listening of MCPTT or MCVideo private call in single MC service server. The diagram shows three main components: MC user B (MC service client B) on the left, MC user C (MC service client C) on the right, and MC service server A in the center. MC user B and MC user C are connected to MC service server A via dashed lines. MC service server A is connected to Authorized MC user A (MC service client A) via a dashed line. The diagram illustrates that MC user A is requesting discreet listening of communications involving MC user B, which are being processed by MC service server A. + +**Figure 4.2.1-1: Discreet listening of MCPTT or MCVideo private call in single MC service server** + +The scenario consists of the following aspects: + +- Authorized MC user A identifies MC user B as the target for discreet listening, and the request for discreet listening is sent by MC service client A to MC service server A, which verifies that MC user A is authorized to perform discreet listening on MC user B. This aspect takes place before any communications involving MC user B can be subject to discreet listening. +- MC user B places or receives an MCPTT or MCVideo private call to or from MC user C. +- MC service server A provides MC service client A with information concerning the initiation of the call, including the identity of MC user C, and also provides the media exchanged between the two parties in the call. +- When the private call completes, the call completion is also conveyed to MC service client A. + +NOTE: The scenario also applies to emergency private calls. + +### 4.2.2 Scenario 1.2: Discreet listening of MCPTT and MCVideo private calls with target receiving service from different MC service server + +This scenario describes the case where authorized MC user A requests discreet listening for communications involving MC user B where MC service user B is within the authority of authorized MC user A and where MC user A and MC user B have different primary MC service servers, MC service servers A and B. The scenario is illustrated in figure 4.2.2-1 below. + +![Diagram illustrating the discreet listening scenario. MC service server A is connected to Authorized MC user A (MC service client A) and MC service server B. MC service server B is connected to MC user B (MC service client B) and MC user C (MC service client C).](0b87abe67b21a93777287649c33e755d_img.jpg) + +The diagram shows three main components: MC service server A, MC service server B, and MC user C (MC service client C). MC service server A is connected to Authorized MC user A (MC service client A) and MC service server B. MC service server B is connected to MC user B (MC service client B) and MC user C (MC service client C). The connections are represented by dashed lines. + +Diagram illustrating the discreet listening scenario. MC service server A is connected to Authorized MC user A (MC service client A) and MC service server B. MC service server B is connected to MC user B (MC service client B) and MC user C (MC service client C). + +**Figure 4.2.2-1: Discreet listening of MCPTT or MCVideo private call with target served by different MC service servers** + +The scenario consists of the following aspects: + +- Authorized MC user A identifies MC user B as the target for discreet listening, and the request for discreet listening is sent by MC service client A to MC service server A, which verifies that MC user A is authorized to perform discreet listening on MC user B. This aspect takes place before any communications involving MC user B can be subject to discreet listening. +- MC service server A identifies MC service server B as the primary MC service server for MC user B. MC service server A requests the discreet listening function from MC service server B. +- MC user B places or receives an MCPTT or MCVideo private call to or from MC user C. +- MC service server A provides MC service client A with information concerning the initiation of the call, including the identity of MC user C, and also provides the media exchanged between the two parties in the call. MC service server B and MC service server A share the relevant information for this to take place. +- When the private call completes, the call completion is also conveyed to MC service client A. + +NOTE 1: The scenario is the same whether MC user C, the other party in the private call, is receiving MC service from MC service server A or MC service server B. + +NOTE 2: The scenario does not imply any requirement for media routing, whether MC user C receives service from MC service server A or MC service server B. + +NOTE 3: The scenario also applies to emergency private calls. + +## 4.3 Scenario 2: Discreet listening of MCPTT and MCVideo group calls + +This scenario describes the case where authorized MC user A requests discreet listening for communications involving MC user B where MC service user B is within the authority of authorized MC user A, where MC user A and MC user B have the same primary MC service server, MC service server A. MC user B is a member of MC service group X together with MC users C to N, and therefore the communications in MC service group X are to be provided to MC user A. The primary MC service server of MC service group X is also MC service server A. The scenario is illustrated in figure 4.3.1-1 below. + +![Diagram illustrating the discreet listening scenario. An oval labeled 'MC service group X' contains 'MC user B' (MC service client B) on the left and 'MC users C-N' (MC service clients C-N) on the right. A central box labeled 'MC service server A' is connected to both the user on the left and the group on the right by dashed lines. Below the oval, 'Authorized MC user A' (MC service client A) is shown with a dashed line connecting to the 'MC service server A'.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +Diagram illustrating the discreet listening scenario. An oval labeled 'MC service group X' contains 'MC user B' (MC service client B) on the left and 'MC users C-N' (MC service clients C-N) on the right. A central box labeled 'MC service server A' is connected to both the user on the left and the group on the right by dashed lines. Below the oval, 'Authorized MC user A' (MC service client A) is shown with a dashed line connecting to the 'MC service server A'. + +**Figure 4.3.1-1: Discreet listening of MCPTT or MCVideo group call** + +The scenario consists of the following aspects: + +- Authorized MC user A identifies MC user B as the target for discreet listening, and the request for discreet listening is sent by MC service client A to MC service server A, which verifies that MC user A is authorized to perform discreet listening on MC user B. This aspect takes place before any communications involving MC user B can be subject to discreet listening. +- MC service server A identifies MC user B as a member of MC service group X +- A group member in MC service group X (one of MC users B or C to N) makes an MCPTT or MCVideo group call. +- MC service server A provides MC service client A with information concerning the initiation of the call, including the identity of the calling MC user, and also provides the media exchanged throughout the group call. +- When the group call completes, the call completion is also conveyed to MC service client A. + +NOTE 1: The scenario does not determine whether authorized MC user A is a member of MC service group X or not. + +NOTE 2: The scenario also applies to other variants of group call, such as emergency group call, imminent peril group call, broadcast group call and calls to temporary groups where MC user B is a group member. + +NOTE 3: If any of MC users B or C to N is receiving MC service from a different MC service server from authorized MC user A, or if the group host MC service server is different from the MC service server serving authorized MC user A, the scenario is similar to that described in subclause 4.2.2 for private call with different MC service servers. + +## 4.4 Scenario 3: Discreet listening of MCVideo pull + +### 4.4.1 Scenario 3.1: Discreet listening of one to one MCVideo pull + +This scenario describes the case where authorized MC user A requests discreet listening for MC user B where MC user B is within the authority of authorized MC user A, and authorized MC user A receives MCVideo pulls where MC user B is the initiator of the MCVideo pull request to a third MC user, or is the recipient of an MCVideo pull request from a third MC user and so provides video as a result of this request. As a one to one MCVideo pull is procedurally identical to an MCVideo private call, the scenarios are the same as those described within the present document in subclause 4.2.1 for MCVideo private call within a single MC service server, and in subclause 4.2.2 where the authorized MC user and target MC user are receiving service from different MC service servers. + +### 4.4.2 Scenario 3.2: Discreet listening of one from server MCVideo pull + +This scenario describes the case where authorized MC user A requests discreet listening for MC user B where MC user B is within the authority of authorized MC user A, and where authorized MC user A receives MCVideo pulls from the MCVideo server initiated by MC user B. In figure 4.4.2-1 below, MC user A and MC user B have the same primary MCVideo server, MCVideo server A. + +![Diagram illustrating the discreet listening of MCVideo pull from server. MC user B (MC service client B) is connected to MCVideo server A. MC user A (MC service client A) is also connected to MCVideo server A. The diagram shows MC user B and MC user A both connected to the same MCVideo server A, indicating that MC user A is receiving MCVideo pulls from MC user B via the server.](c78c2eefd86269d1740ab85a916f24f2_img.jpg) + +``` + +graph TD + subgraph MC_user_B [MC user B +MC service client B] + B[ ] + end + subgraph MC_user_A [Authorized MC user A +MC service client A] + A[ ] + end + subgraph MCVideo_server_A [MCVideo server A] + S[ ] + end + B -.-> S + A -.-> S + +``` + +Diagram illustrating the discreet listening of MCVideo pull from server. MC user B (MC service client B) is connected to MCVideo server A. MC user A (MC service client A) is also connected to MCVideo server A. The diagram shows MC user B and MC user A both connected to the same MCVideo server A, indicating that MC user A is receiving MCVideo pulls from MC user B via the server. + +**Figure 4.4.2-1: Discreet listening of MCVideo pull from server** + +The scenario consists of the following aspects: + +- Authorized MC user A identifies MC user B as the target for discreet listening, and the request for discreet listening is sent by MC service client A to MCVideo server A. This aspect takes place before any communications involving MC user B can be subject to discreet listening. +- MC user B initiates an MCVideo pull from the MCVideo server. +- MCVideo server A provides MC service client A with information concerning the initiation of the MCVideo pull, and provides the MCVideo media sent from the MCVideo server to MC user B. + +NOTE 1: An alternative would be to notify authorized MC user A when MC user B requests to make an MCVideo pull, and allow MC user A to decide whether to receive the video media. + +NOTE 2: Authorized MC user A may receive separate notifications when the MCVideo pull is initiated, and when the MCVideo is provided. + +NOTE 3: The provision of MCVideo media to authorized MC user A may be in real time, or on demand with intermediate storage in the MCVideo server. + +If MC user B receives MC service from a different MCVideo server, MCVideo server A will request the discreet listening function from the serving MCVideo server of MC user B. + +## 4.5 Scenario 4: Discreet listening of MCVideo push + +### 4.5.1 Scenario 4.1: Discreet listening of one to one MCVideo push + +This scenario describes the case where authorized MC user A requests discreet listening for MC user B where MC user B is within the authority of authorized MC user A, and authorized MC user A receives MCVideo pushes initiated or received by MC user B. As a one to one MCVideo push is procedurally identical to an MCVideo private call, the scenarios are the same as those described within the present document in subclause 4.2.1 for MCVideo private call within a single MC service server, and in subclause 4.2.2 where the authorized MC user and target MC user are receiving service from different MC service servers. + +### 4.5.2 Scenario 4.2: Discreet listening of one to server MCVideo push + +This scenario describes the case where authorized MC user A requests discreet listening for MC user B where MC user B is within the authority of authorized MC user A, and where authorized MC user A receives MCVideo pushes to the MCVideo server that have been initiated by MC user B. In figure 4.5.2-1 below, MC user A and MC user B have the same primary MCVideo server, MCVideo server A. + +![Diagram illustrating the discreet listening of MCVideo push to server. MC user B (MC service client B) is connected to MCVideo server A. MC user A (MC service client A) is also connected to MCVideo server A. The diagram shows MC user B and MC user A both connected to the same MCVideo server A, indicating that MC user A is receiving MCVideo pushes from MC user B via the server.](78ffccd66df9bafd96e3e081110d09dd_img.jpg) + +``` + +graph TD + subgraph MC_user_B [MC user B +MC service client B] + B[ ] + end + subgraph MC_user_A [Authorized MC user A +MC service client A] + A[ ] + end + subgraph MCVideo_server_A [MCVideo server A] + S[ ] + end + B -.-> S + A -.-> S + +``` + +Diagram illustrating the discreet listening of MCVideo push to server. MC user B (MC service client B) is connected to MCVideo server A. MC user A (MC service client A) is also connected to MCVideo server A. The diagram shows MC user B and MC user A both connected to the same MCVideo server A, indicating that MC user A is receiving MCVideo pushes from MC user B via the server. + +**Figure 4.5.2-1: Discreet listening of MCVideo push to server** + +The scenario consists of the following aspects: + +- Authorized MC user A identifies MC user B as the target for discreet listening, and the request for discreet listening is sent by MC service client A to MCVideo server A. This aspect takes place before any communications involving MC user B can be subject to discreet listening. +- MC user B initiates an MCVideo push to the MCVideo server. +- MCVideo server A provides MC service client A with information concerning the initiation of the MCVideo push, and provides the MCVideo media sent from MC user B to the MCVideo server. + +NOTE 1: An alternative would be to notify authorized MC user A when MC user B requests to make an MCVideo push, and allow MC user A to decide whether to receive the video media. + +NOTE 2: Authorized MC user A may receive separate notifications when the MCVideo push is initiated, and when the MCVideo is provided. + +NOTE 3: The provision of MCVideo media to authorized MC user A may be in real time, or on demand with intermediate storage in the MCVideo server. This aspect may need an additional requirement on media storage server. + +If MC user B receives MC service from a different MCVideo server, MCVideo server A will request the discreet listening function from the serving MCVideo server of MC user B. + +### 4.5.3 Scenario 4.3: Discreet listening of remotely initiated MCVideo push + +This scenario describes the case where authorized MC user A requests discreet listening for communications involving MC user B where MC user B is within the authority of authorized MC user A, and where MC user C causes a remotely initiated MCVideo push from MC user B to MC user D. The scenario is illustrated in figure 4.5.3-1 below. + +![Diagram illustrating the discreet listening of a remotely initiated MCVideo push. A central MCVideo server A is connected to four entities: MC user B (MC service client B) on the top left, MC user D (MC service client D) on the top right, Authorized MC user A (MC service client A) on the bottom left, and MC user C (MC service client C) on the bottom right. Dashed lines connect the server to each client. The diagram shows the server acting as a central hub for communications between these users.](410562339ce067fdc6fa41940c118658_img.jpg) + +Diagram illustrating the discreet listening of a remotely initiated MCVideo push. A central MCVideo server A is connected to four entities: MC user B (MC service client B) on the top left, MC user D (MC service client D) on the top right, Authorized MC user A (MC service client A) on the bottom left, and MC user C (MC service client C) on the bottom right. Dashed lines connect the server to each client. The diagram shows the server acting as a central hub for communications between these users. + +**Figure 4.5.3-1: Discreet listening of remotely initiated MCVideo push** + +The scenario consists of the following aspects: + +- Authorized MC user A identifies MC user B as the target for discreet listening, and the request for discreet listening is sent by MC service client A to MCVideo server A. This aspect takes place before any communications involving MC user B can be subject to discreet listening. +- MC user C initiates a remotely initiated MCVideo push procedure, wherein MC user B pushes video to MC user D. +- MCVideo server A provides MC service client A with information concerning the initiation of the MCVideo push including the identities of MC users C and D, and provides the MCVideo media sent from MC user B to MC user D. + +NOTE 1: An alternative would be to notify authorized MC user A when MC user B initiates the MCVideo push, and to allow MC user A to decide whether to receive the video media. + +NOTE 2: Authorized MC user A may receive separate notifications when the MCVideo pull is initiated, and when the MCVideo is provided. + +NOTE 3: The provision of MCVideo media to authorized MC user A may be in real time, or on demand with intermediate storage in the MCVideo server. This aspect may need an additional requirement on media storage server. + +NOTE 4: The scenario is the same where MC user C causes MC user D to push MCVideo media towards MC user B; MCVideo server A also sends the pushed video from MC user D to authorized MC user A. + +If MC user B receives MC service from a different MCVideo server, MCVideo server A will request the discreet listening function from the serving MCVideo server of MC user B. + +## 4.6 Scenario 5: Discreet listening of MCData SDS + +This scenario describes the case where authorized MC user A requests discreet listening for communications involving MC user B where MC user B is within the authority of authorized MC user A, and where MC user A and MC user B have the same primary MCData server. The scenario is illustrated in figure 4.6.1-1 below. + +![Diagram illustrating the discreet listening of one-to-one MCData SDS. A central MCData server A is connected to three entities: MC user B (MC service client B) on the left, MC user C (MC service client C) on the right, and Authorized MC user A (MC service client A) below. Dashed lines connect the server to each client.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +graph TD + B["MC user B +MC service client B"] -.-> A["MCData server A"] + C["MC user C +MC service client C"] -.-> A + A -.-> D["Authorized MC user A +MC service client A"] + +``` + +Diagram illustrating the discreet listening of one-to-one MCData SDS. A central MCData server A is connected to three entities: MC user B (MC service client B) on the left, MC user C (MC service client C) on the right, and Authorized MC user A (MC service client A) below. Dashed lines connect the server to each client. + +**Figure 4.6.1-1: Discreet listening of one to one MCData SDS** + +The scenario consists of the following aspects: + +- Authorized MC user A identifies MC user B as the target for discreet listening, and the request for discreet listening is sent by MC service client A to MCData server A. This aspect takes place before any communications involving MC user B can be subject to discreet listening. +- MC user B sends or receives an MCData SDS data request to or from MC user C. +- MCData server A provides MC service client A with the MCData SDS data request, including relevant information such as conversation identifier and transaction identifier. +- If the recipient sends one or more disposition notifications, these are also sent to MC user A. + +NOTE 1: The scenario applies whether the data is sent over the signalling plane or the media plane. + +NOTE 2: The scenario applies whether the data is sent in standalone transactions, or as part of a session. + +NOTE 3: The use applies to enhanced status sent over SDS. + +NOTE 4: If authorized MC user A is receiving MC service from a different MCData server to that of MC user B, the serving MCData server of MC user A communicates with the serving MCData server of MC user B to provide the discreet listening service. This is similar to the case of MCPTT and MCVideo private calls described in subclause 4.2.2. + +NOTE 5: If MC user B is sending or receiving SDS within a group, the scenario is similar to that described in subclause 4.3 for MCPTT and MCVideo group call. + +## 4.7 Scenario 6: Discreet listening of MCData file distribution + +### 4.7.1 Scenario 6.1: Discreet listening of file upload and file download + +This scenario is similar to those for MCVideo push and MCVideo pull from server described in subclauses 4.4.2 and 4.5.2 of the present document. + +### 4.7.2 Scenario 6.2: Discreet listening of one to one file distribution + +This scenario describes the case where authorized MC user A requests discreet listening for communications involving MC user B where MC user B is within the authority of authorized MC user A, and where MC user A and MC user B have the same primary MCData server. The scenario is the same whether the file is distributed over HTTP or over the media plane. The scenario is illustrated in figure 4.7.2-1 below. + +![Diagram illustrating the discreet listening of one-to-one MCData file distribution. A central 'MCData server A' is connected to three entities: 'MC user B / MC service client B' (top left), 'MC user C / MC service client C' (top right), and 'Authorized MC user A / MC service client A' (bottom). The connections are shown as dashed lines forming a star topology around the central server.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +graph TD + B["MC user B +MC service client B"] -.-> A["MCData server A"] + C["MC user C +MC service client C"] -.-> A + A_authorized["Authorized MC user A +MC service client A"] -.-> A + +``` + +Diagram illustrating the discreet listening of one-to-one MCData file distribution. A central 'MCData server A' is connected to three entities: 'MC user B / MC service client B' (top left), 'MC user C / MC service client C' (top right), and 'Authorized MC user A / MC service client A' (bottom). The connections are shown as dashed lines forming a star topology around the central server. + +**Figure 4.7.2-1: Discreet listening of one to one MCData file distribution** + +The scenario consists of the following aspects: + +- Authorized MC user A identifies MC user B as the target for discreet listening, and the request for discreet listening is sent by MC service client A to MCData server A. This aspect takes place before any communications involving MC user B can be subject to discreet listening. +- MC user B sends or receives an MCData file distribution request to or from MC user C. +- MC service server A provides MC service client A with the transferred file, including relevant information such as the identity of MC user C, the conversation identifier and transaction identifier. +- The MCData download completed report is also sent to MC service client A. + +NOTE 1: The scenario applies whether the file is sent over HTTP or the media plane. + +NOTE 2: Authorized MC user A may receive separate notifications when the MCData file transfer is initiated, and when the MCData file is provided. + +NOTE 3: The provision of the MCData file to authorized MC user A may be in real time, or on demand with intermediate storage in the MCData server. + +NOTE 4: If authorized MC user A is receiving MC service on a different MCData server to that of MC user B, the serving MCData server of MC user A communicates with the serving MCData server of MC user B to provide the discreet listening service. This is similar to the case of MCPTT and MCVideo private calls described in subclause 4.2.2. + +## 4.8 Scenario 7: Logging scenarios + +### 4.8.1 General + +According to the requirements for logging in 3GPP TS 22.280 [2] and 3GPP TS 22.281 [3] which are also reproduced in Annex A of the present document, mechanisms are to be provided to log both media and metadata for call related and call unrelated activity of the target MC service users and MC service groups. + +The call related scenarios can be considered to be the same as those described in scenarios 1 to 6 related to discreet listening, except that the recipient of the information is a logging client or interface instead of the authorized user. + +## 4.9 Scenario 8: Limitations on discreet listening due to regulatory constraints and operator security policies + +### 4.9.1 Scenario 8.1: Private communication transmissions + +This scenario describes the case where authorized MC user A requests discreet listening for communications involving MC user B where MC user B is within the authority of authorized MC user A. MC user C can be, but does not have to be within the authority of the authorized MC user A. The MC user C is not the target of the discreet listening request + +executed by the authorized MC user A. The scenario would allow MC user A to be part of the communication coming from MC user B, but not the communication coming from MC user C. The scenario is illustrated in figure 4.9.1-1 below. + +![Diagram of discreet listening with regulatory constraints on private communication transmissions. It shows MC user B and MC user C connected to MC service server A. MC user A is also connected to the server. A dashed line with an 'X' indicates a blocked transmission from MC user C to MC user A.](16152cf1d84aea10848758f51a91ff6a_img.jpg) + +The diagram illustrates a network architecture for discreet listening. At the top, 'MC user B' (MC service client B) and 'MC user C' (MC service client C) are shown as rectangular boxes. Both are connected via dashed lines to a central 'MC service server A' box. Below the server, 'Authorized MC user A' (MC service client A) is shown as a rectangular box, connected to the server by a dashed line. A dashed line extends from 'MC user C' through the server to 'Authorized MC user A', but this line is marked with a large 'X', indicating a blocked or restricted transmission path. + +Diagram of discreet listening with regulatory constraints on private communication transmissions. It shows MC user B and MC user C connected to MC service server A. MC user A is also connected to the server. A dashed line with an 'X' indicates a blocked transmission from MC user C to MC user A. + +**Figure 4.9.1-1: Discreet listening with regulatory constraints on private communication transmissions** + +NOTE 1: As the communication originated from MC user C is restricted, authorized user A is not able to receive the full context of the communications from MC user B which may limit the usefulness of the discreet listening of user B. + +NOTE 2: As authorized user A will know that user B and user C are communicating, and able to receive all conversation from user B, the security of user C is not preserved in this scenario. + +### 4.9.2 Scenario 8.2: Group communication transmissions + +This scenario describes the case where authorized MC user A requests discreet listening for a set of users being part of group communications involving MC user B to MC user D where MC user B to MC user D are within the authority of authorized MC user A. All other participants on these group communications can, but do not have to be within the authority of the authorized MC user A. The scenario would allow MC user A to be part of the communications coming from MC user B to MC user D, but not the communication coming from MC user E. The scenario is illustrated in figure 4.9.2-1 below. + +![Diagram of discreet listening with regulatory constraints on users being part of group communication transmissions. It shows MC user B, C, D, and E connected to MC service server A. MC user A is also connected to the server. Dashed lines with 'X' marks indicate blocked transmissions from MC user C and MC user E to MC user A.](f57a881fcbcaf494a7dedc4f61224991_img.jpg) + +This diagram shows a group communication scenario. A central 'MC service server A' box is connected to five entities via dashed lines: 'MC user B' (MC service client B) at the top left, 'MC user C' (MC service client C) at the top right, 'MC user D' (MC service client D) at the bottom left, 'MC user E' (MC service client E) at the bottom right, and 'Authorized MC user A' (MC service client A) at the bottom center. The connections from 'MC user C' and 'MC user E' to 'Authorized MC user A' are marked with a large 'X', indicating that these specific transmissions are restricted or blocked. The connections from 'MC user B' and 'MC user D' to the server are shown as dashed lines, and their transmissions to 'Authorized MC user A' are shown as dashed lines without an 'X', indicating they are permitted. + +Diagram of discreet listening with regulatory constraints on users being part of group communication transmissions. It shows MC user B, C, D, and E connected to MC service server A. MC user A is also connected to the server. Dashed lines with 'X' marks indicate blocked transmissions from MC user C and MC user E to MC user A. + +**Figure 4.9.2-1: Discreet listening with regulatory constraints on users being part of group communication transmissions** + +The scenario consists of the following aspect: + +- Authorized MC user A is requesting group communication transmissions by identifying the target users being part of group communications. + +NOTE 1: As the communication originated from MC user E is restricted, authorized user A is not able to receive the full context of the communications in the rest of the group which may limit the discreet listening service capability. + +NOTE 2: As authorized user A will know that the other group members are communicating with user E, and able to receive all conversation from the rest of the group, the security of user E is not preserved in this scenario. + +# --- 5 Key Issues + +## 5.1 Key Issue 1: Selection of MC service for discreet listening + +The single requirement for discreet listening [R-6.15.1-001] provided in 3GPP TS 23.280 [2] and reproduced in Annex A of the present document requires that all group or private communication transmissions from the target MC user are to be subject to discreet listening by an authorized MC user. + +In practice, selection at the MC service level will automatically take place, as the MC service clients for each MC service will be used to place the discreet listening requests on behalf of the authorized MC user, for example if the authorized MC user only places the discreet listening request using an MCPTT client, only MCPTT transmissions will be available to the authorized MC user. + +Within each of the MCPTT, MCVideo and MCData services, there are a number of separate services available and it is not clear whether the authorized MC user would wish to automatically receive content involving the target MC user within these separate services; for example whether the authorized MC user would require to receive MCData SDS transmissions but not MCData file upload and downloads. + +NOTE: It is assumed that when discreet listening is invoked by the authorized MC user, the authorized MC user is provided with communications transmitted by the target MC user, and communications received by the target MC user. + +Issues: + +- Whether there should be granularity of discreet listening within each MC service, or whether all services within each MC service should always be provided to the authorized MC user following a request for discreet listening of a target MC user within an MC service. + +## 5.2 Key issue 2: Group membership of authorized MC user for discreet listening + +The target of discreet listening may be a member of an MC service group, and be able to take part in group communications. The authorized MC user will expect to receive all MC service group communication transmissions involving the target MC user, however the authorized MC user might not be defined as an MC service group member of the MC service group in which the target MC user is communicating. + +Issues: + +- Whether the authorized MC user should be a pre-defined member of an MC service group in order to receive group communications in which the target MC user is involved. +- Whether the authorized MC user should be temporarily made an MC service group member in order to receive group communications in which the target MC user is involved. +- Whether, if the authorized MC user is not an MC service group member, there should be any restriction on the communications involving the target MC user that are provided to the authorized MC user, e.g. provision of the target's transmissions to the MC service group, but not transmissions of other MC service group members. +- Whether any restrictions on requiring MC service group membership are different when the MC service group is defined in a different primary MC system to that of the authorized MC user. +- If the authorized MC user affiliates to the MC service group in order to receive the media in group communications, the affiliation of the authorized MC user to the MC service group may be visible to the target MC user and to other members of the MC service group; and the stage 1 requirement is that discreet listening takes place without the knowledge of the target MC user. + +- How the authorized MC user is able to recover the content of communications within the group that are protected by end to end encryption. + +Editor's note: Membership of a group homed in an interworked system is FFS. + +## 5.3 Key issue 3: Discreet listening for MCVideo push and pull and MCData file upload and download + +The MCVideo video push and video pull services each start with a negotiation phase, where information related to the video content to be pushed or pulled such as URL, media characteristics etc is provided and agreed. The MC user can be notified and asked to accept incoming video within a video push. + +Similarly, the MCData file upload and file download services each start with a negotiation phase where information related to the file transfer such as URL is provided and agreed. The MC user can be notified and asked whether to accept an incoming file transfer. + +The discreet listening service could either allow the authorized MC user who is the recipient of the information to accept video or data before that video or data is sent to the authorized MC user, or could be provided with the video or data sent to or from the target MC user of the discreet listening service automatically. + +Issues: + +- Whether the authorized MC user should be notified about the start of video push and pull or file upload or download transactions involving the MC user who is the target of discreet listening and given the choice to accept and receive the information or reject receiving the information; or whether the authorized MC user should always receive the information without any choice being needed. +- Whether the authorized MC user should receive notification both when the file upload or download negotiation phase takes place, and a second notification when the file upload or download takes place. +- Whether the authorized MC user should automatically be presented with the file date if a mandatory download takes place to the target MC user +- Whether the file content should be saved by the MCData server (or another suitable entity) until the authorized MC user decides to retrieve the file, and if so, whether there should be a time limit on this storage. + +## 5.4 Key issue 4: Discreet listening of end to end encrypted calls + +An authorized user may perform discreet listening on end to end encrypted communications, where those communications can be private calls, individual communications with a server (e.g. pull from or push to a server), and group calls where the target of the discreet listening is engaged in group communications. In order to comprehend the communications, the authorized user's MC service client needs to be provided with the end to end encryption key used to encrypt the content of the call. + +NOTE: This key issue assumes that the decryption process is located in the authorized user's MC service client, to avoid violating the stage 1 requirement [R-5.12-009] in 3GPP TS 22.179 [2] for end to end encryption of media traffic. + +For private or individual communications, a session key is used to encrypt the content of the communications, which is protected in transfer between the call participants by an encryption process making use of the identity of the destination party. The mechanism is described in 3GPP TS 33.180 [6]. + +For group communications, a GMK is originated by the GMS and protected in transfer to group members one at a time by an encryption process making use of the identity of each group member. The mechanism is described in 3GPP TS 33.180 [6]. + +According to the requirement in 3GPP TS 22.280 [2] and reproduced in Annex A of the present document, the participants in the call will not be aware of the discreet listening. + +Issues: + +- In order to successfully discreet listen to private or individual communications without violating the requirement for end to end encryption, the authorized user's MC service client needs access to the session key exchanged + +between the parties in the private or individual communication. To fulfil the requirement reproduced in Annex A.1, the parties in the call will not have knowledge of the authorized user possessing the encryption key. + +- In order to successfully discreet listen to group communications without violating the requirement for end to end encryption, the authorized user's MC service client needs access to the GMK for the group. To fulfil the requirement reproduced in Annex A.1, the group members in the call will not have knowledge of the authorized user possessing the encryption key. + +## 5.5 Key issue 5: Logging and replay of end to end encrypted calls + +A logging entity requires to be able to record the content of end to end encrypted private calls, individual communications with a server (e.g. pull from or push to a server) and group calls. In order to permit replay of the content of the recorded calls, the encryption key must be available to provide decryption at some point in the process, either during recording, at some time during storage subsequent to recording, or on playback. + +Issues: + +- Whether the content should be decrypted at the point of recording, at some time during storage, or at the time of playback of the recorded material. +- How the entity performing the decryption obtains the encryption key to enable the decryption of the media content. + +## 5.6 Key issue 6: Source MC service server for discreet listening of user in group call + +An authorized user may perform discreet listening on an MC service user, where that MC service user is taking part in group communications. The primary MC service server of that MC service group may be a different MC service server to the primary MC service server of the target MC service user. + +Issues: + +- Which MC service server should provide the content of group call communications in which the target user takes part: the primary MC service server of the target user or the primary MC service server of the MC service group. +- How the solution prevents the discreet listening service being apparent to the target MC service user, or to other MC service group members. + +## 5.7 Key issue 7: Discreet listening and logging for interconnected MC system + +An authorized user may attempt to perform discreet listening on an MC service user that has a different primary MC system to that of the authorized user, where that target MC service user is taking part in private communications, or in group communications where the MC service group also has a different primary MC system to that of the authorized user. This could raise concerns about eavesdropping on communications in another security domain. The group case is illustrated in figure 5.7-1 below. + +![Figure 5.7-1: Discreet listening for a group entirely in a partner MC system. The diagram shows MC system A and MC system B connected by a dashed line. MC system A is connected to an 'Authorized user DL recipient'. MC system B is connected to an oval containing 'MC service group X' and 'Affiliated MC service group members'.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +The diagram illustrates a scenario where MC system A and MC system B are interconnected. MC system A is connected to an 'Authorized user DL recipient'. MC system B is connected to an oval containing 'MC service group X' and 'Affiliated MC service group members'. A dashed line connects MC system A to the 'MC service group X' within the oval, indicating a discreet listening connection. + +Figure 5.7-1: Discreet listening for a group entirely in a partner MC system. The diagram shows MC system A and MC system B connected by a dashed line. MC system A is connected to an 'Authorized user DL recipient'. MC system B is connected to an oval containing 'MC service group X' and 'Affiliated MC service group members'. + +**Figure 5.7-1: Discreet listening for a group entirely in a partner MC system** + +However, if MC service users in an MC system join an MC service group where that group has a different primary MC system which is connected by interconnection, it is likely that the MC system providing service for those MC service group members would wish to log communications within that group, and likely that an authorized user within that MC system may wish to perform discreet listening on group members who are receiving service in the same MC system as that authorized user. This is illustrated in figure 5.7-2 below. + +![Figure 5.7-2: Discreet listening or logging for group with group members in discreet listening/logging system. The diagram shows MC system A and MC system B connected by a dashed line. MC system A is connected to a 'Discreet listening or logging recipient'. MC system B is connected to an oval containing 'Affiliated MC service group members' and 'MC service group X'. A dashed line connects MC system A to the 'Affiliated MC service group members' within the oval, indicating a discreet listening or logging connection.](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +The diagram illustrates a scenario where MC system A and MC system B are interconnected. MC system A is connected to a 'Discreet listening or logging recipient'. MC system B is connected to an oval containing 'Affiliated MC service group members' and 'MC service group X'. A dashed line connects MC system A to the 'Affiliated MC service group members' within the oval, indicating a discreet listening or logging connection. + +Figure 5.7-2: Discreet listening or logging for group with group members in discreet listening/logging system. The diagram shows MC system A and MC system B connected by a dashed line. MC system A is connected to a 'Discreet listening or logging recipient'. MC system B is connected to an oval containing 'Affiliated MC service group members' and 'MC service group X'. A dashed line connects MC system A to the 'Affiliated MC service group members' within the oval, indicating a discreet listening or logging connection. + +**Figure 5.7-2: Discreet listening or logging for group with group members in discreet listening/logging system** + +Issues: + +- Discreet listening of individual or group communications may need to be restricted to target MC service users with the same primary MC system as the authorized user for discreet listening. +- Logging of individual or group communications may need to be restricted to target MC service users or groups which are receiving service in the same primary MC system as the logging entity. +- If discreet listening or logging of individual communications is permitted where the target is receiving service in an interconnected MC system, both the MC system where the target is receiving service and the MC system where the request for discreet listening or logging originates may need to authorize the discreet listening or logging service. + +## 5.8 Key issue 8: Discreet listening and logging for migrated MC service user + +An MC service user that has migrated to another MC system receives MC service within the security domain of that MC system. + +Issues: + +- The primary MC system of the MC service user and the migrated MC system of the MC service user may both wish to authorize discreet listening and/or logging of the migrated MC service user by the primary MC system of that migrated MC service user. +- The primary MC system of the migrated MC service users and the migrated MC system of the migrated MC service user may both wish to authorize any logging or discreet listening of the migrated MC service user by the migrated MC system. +- There may be a need to restrict the provided content of communications to that which is originated by the migrated MC service user, and not to provide content which originates from other users receiving service within the migrated MC system. +- There may be a need to restrict metadata relating to the communications to hide the identities and other information relating to MC service users and MC service groups whose primary MC system is the migrated MC system of the MC service user who is the target of the discreet listening or logging. + +## 5.9 Key Issue 9: Discreet listening and logging for user receiving MC service on multiple devices + +An MC service user may be service authorized on multiple MC service UEs, and may be receiving the same or different MC services on each of these. It is possible that an MC service user will receive the same communications content on more than one device simultaneously. Both the discreet listening and the logging services target a specific MC service user, and therefore both services will expect to obtain the content of communications and relevant communication related information whichever device the MC service user makes use of. + +Issues: + +- Whether there is any need to identify the MC service UE that was used for each communication, and how such identification of the relevant MC service UE is possible. +- Whether there is any need to capture or to remove duplicated content of the MC service user receives the same communications content on more than one MC service UE. + +## 5.10 Key Issue 10: Logging of MC service users and MC service groups + +An entity is required to perform logging of the communications and communications related information of MC service users and MC service groups. + +Issues: + +- Whether an existing functional entity such as an MC service client can provide the logging function, or whether a new functional entity is required. +- Whether new reference points are needed to support logging. +- Whether there are any explicit protocol transactions and procedures needed to support logging. +- The configuration needed to support logging. +- Whether the logging entity is considered a group member, and whether it requires affiliation to an MC service group, in order to log group communications. +- Whether any aspect of the replay equipment needed to replay recorded communications is in scope of standardization + +## 5.11 Key Issue 11: Logging of MCData content server and message store services + +An MCData user may make use of a content server for upload and download of MCData content. An MCData user may also have the use of a message store where content of MCData transactions can be stored for later retrieval. Logging of + +information stored on the content server or message store could be achieved by storage capabilities of those entities, or could be achieved using a separate MC logging function. + +Issues: + +- Whether logging of transactions to and from an MCData content server is required. +- Whether logging of transactions to and from a message store is required. +- Whether logging of transactions which involve a content server or a message store can be satisfied by the content server or message store providing logging as an intrinsic function without the need for separate MC logging function. +- If a separate MC logging function is required to log transactions to and from a message store or content server, which additional reference points are needed to fulfil the functionality. + +## 5.12 Key Issue 12: Discreet listening of MCData content server and message store services + +An MCData user may make use of a content server for upload and download of MCData content. An MCData user may also have the use of a message store where content of MCData transactions can be stored for later retrieval. An authorized user may require discreet listening of transactions between the MCData user and the the content server or message store. If provided, the authorized user may need access to the content of information exchanged, or may require notification that the information is being exchanged without needing the content. + +Issues: + +- Whether discreet listening of transactions to and from an MCData content server is required. +- Whether discreet listening of transactions to and from a message store is required. +- Whether discreet listening requires notification that transactions are taking place without providing the content, or whether the content itself is also needed. +- Whether the content of transactions needs to follow the same path as notification of the transactions, if both notification and content are required, or whether content can be accessible by the authorized user directly from the message store or content server. +- Whether activation of discreet listening against a target user also gives the authorized user access to previous transactions to or from the target user which have been stored in a content server or message store, or whether access is only possible to transactions in progress. +- Whether activation of discreet listening to a group gives access to transactions (e.g. for group SDS) which have been exchanged prior to that activation. +- Whether discreet listening allows the authorized user to receive synchronization between the message store client of an MCData user and a message store, for example when the MCData client uploads transactions that took place whilst operating in off-network mode. +- Whether discreet listening allows the authorized user access to data content which an MCData user has created and stored in a message store, without that content being sent to or received from another MCData user. + +## 5.13 Key issue 13: Discreet listening towards an MC service group + +The target of discreet listening can be an MC service group specified by the authorized user. The authorized user receives all the group communications of this target group in a real time manner. + +The authorized user (listener) can be within the primary MC system of the target group, or can be in a partner MC system of the target group. + +The following aspects need to be further studied to support group based discreet listening: + +- Procedures and information flows based on the reuse of existing solutions; +- Configurations that are needed for the authorizations for discreet listening. + +## 5.14 Key Issue 14: Limitations on discreet listening due to regulatory constraints and operator security policies + +An authorized MC user has requested discreet listening either on one MC user or a group of MC users. Regulatory constraints and operator security policies can require specifying the exact communication transmissions that are allowed to be part of the discreet listening service, which would result in limitations on discreet listening on all parties in the communication. The communication transmissions from a single target user as well as target users within a group can be listened to by the authorized user while leaving everything else out of scope of the requested discreet listening. The regulatory constraints and operator security policies can have impact on all types of communication transmissions and is therefore mission critical service independent. + +Issues: + +- How only the communication transmissions coming from the target MC user involved in a private communication can be part of discreet listening. +- How only the communication transmissions coming from one target MC user or a group of target MC users involved in a group communication can be part of discreet listening. +- How any other communication transmissions are made unavailable to the authorized MC user, as they are not part of discreet listening requests. +- Whether any of the communication related signalling should be restricted. + +NOTE: There may be security issues relating to the users that are outside the scope of the discreet listening, as the fact that communications are taking place, and the contents of those communications sent to those users is available to the authorized user. + +# 6 Solutions + +## 6.1 Solution 1: Functionality for discreet listening + +### 6.1.1 Description + +#### 6.1.1.1 Functional model + +Discreet listening is carried out by an authorized user, who requests discreet listening for the communications of another user. The authorized user will require a client entity capable of fulfilling the discreet listening request. The functionality required is the same as that of an MC service client, with the addition of the capability to request discreet listening and specify a target MC service user. Therefore the solution is to reuse the MC service client, and make no additions to the functional model. + +This solution addresses aspects of key issue 1, Selection of MC service for discreet listening, and key issue 2, Group membership of authorized user for discreet listening. + +#### 6.1.1.2 Configuration + +The user profiles for MCPTT, MCVideo and MCData which are specified in 3GPP TS 23.379 [7], 3GPP TS 23.281 [8] and 3GPP TS 23.282 [9] will need additional configuration to be added as shown in Table 6.1.1.2-1 below. + +**Table 6.1.1.2-1: Addition to MC service user profiles (on network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Configuration management server | MCPTT user database | +|-----------|---------------------------------------------------------------------|----------|--------------|---------------------------------|---------------------| +| | Authorized to perform discreet listening on another MC service user | Y | Y | Y | Y | +| | List of users upon whom discreet listening can be invoked | | | | | +| | > MC service ID | Y | Y | Y | Y | + +In Table 6.1.1.2-1 'MC service' represents one of MCPTT, MCVideo or MCData. + +#### 6.1.1.3 Procedures + +##### 6.1.1.3.1 General + +New procedures are added to allow the MC service client of the authorized user to invoke and revoke discreet listening of a target MC user, and to allow the MC service server to provide the content of calls in which the target user is involved. + +##### 6.1.1.3.2 Discreet listening invocation and revocation procedures + +The procedure allows the MC service client of the authorized user to request discreet listening of a target MC service user. The procedure is illustrated in figure 6.1.1.3.2-1 below. + +![Sequence diagram showing the discreet listening invocation procedure. It involves two participants: MC service client and MC service server. The client sends a '1. Discreet listening activation request' to the server, and the server responds with a '2. Discreet listening activation response'.](9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg) + +``` + +sequenceDiagram + participant Client as MC service client + participant Server as MC service server + Note left of Client: + Client->>Server: 1. Discreet listening activation request + Note right of Server: + Server-->>Client: 2. Discreet listening activation response + +``` + +Sequence diagram showing the discreet listening invocation procedure. It involves two participants: MC service client and MC service server. The client sends a '1. Discreet listening activation request' to the server, and the server responds with a '2. Discreet listening activation response'. + +**Figure 6.1.1.3.2-1: Discreet listening invocation** + +The information flows needed to support such a procedure are shown in tables 6.1.1.3.2-1 and 6.1.1.3.2-2 below. + +**Table 6.1.1.3.2-1: Discreet listening activation request** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MC service ID | M | MC service ID of the target of the discreet listening request | + +**Table 6.1.1.3.2-2: Discreet listening activation response** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------| +| MC service ID | M | MC service ID of the target of the discreet listening request | +| Result | M | Indicates the success or failure of the discreet listening request | + +Invocation of discreet listening of a target MC service user will result in all communications sent or received to any MC service client on which the target MC service user is receiving MC service being provided to the authorized user. + +A similar procedure, not illustrated here, is required for revocation of the discreet listening function. + +##### 6.1.1.3.3 Provision of discreet listening content for private communications + +When the target user makes or receives a private call or initiates individual communications with a server, the authorized user needs to be informed and provided with the media. Figure 6.1.1.3.3-1 below illustrates a procedure where discreet listening target MC service client 1 sets up a call. + +![Sequence diagram for Figure 6.1.1.3.3-1: Discreet listening of target initiated private call. Lifelines: MC service client 1 (target), MC service server, MC service client 2 (called party), MC service client 3 (authorized user). The sequence shows a private call request from client 1 to client 2 via the server, a discreet listening request from the server to client 3, and subsequent responses leading to media plane establishment.](26d664119ad25250780f554633444e54_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 (target) + participant MC service server + participant MC service client 2 (called party) + participant MC service client 3 (authorized user) + Note left of MC service client 1: Private call request + MC service client 1->>MC service server: 1. Private call request + MC service server->>MC service client 2: 2. Private call request + MC service server->>MC service client 3: 3. Discreet listening call request + MC service client 2->>MC service server: 4. Private call response + MC service client 3->>MC service server: 5. Discreet listening call response + MC service server->>MC service client 1: 6. Private call response + Note right of MC service client 1: 7. Media plane established + +``` + +Sequence diagram for Figure 6.1.1.3.3-1: Discreet listening of target initiated private call. Lifelines: MC service client 1 (target), MC service server, MC service client 2 (called party), MC service client 3 (authorized user). The sequence shows a private call request from client 1 to client 2 via the server, a discreet listening request from the server to client 3, and subsequent responses leading to media plane establishment. + +**Figure 6.1.1.3.3-1: Discreet listening of target initiated private call** + +The procedure is similar if the target of the discreet listening is the recipient of the private call. + +If the target initiated the private call, the discreet listening call request may include the client ID associated with the MC service client on which the target initiates the call. If the target receives a request for a private call, the discreet listening call request may include the client ID(s) of the MC service clients on which the private call request is received. + +**NOTE:** If the MC service server does not receive the 'discreet listening call response' for any reason, the call should still proceed so that the requirement that the call is not affected and the target user is not aware of the discreet listening process is satisfied. + +##### **6.1.1.3.4 Provision of discreet listening content for group communications** + +When the target user makes or receives a group call, the authorized user needs to be informed and provided with the media. Figure 6.1.1.3.4-1 below illustrates a procedure where discreet listening target MC service client 2 is a receiving party in a group call initiated by another affiliated group member. + +![Sequence diagram for Figure 6.1.1.3.4-1: Discreet listening of target initiated group call. Lifelines: MC service client 1 (call initiator), MC service server, MC service client 2 (target), MC service client 3 (authorized user). The sequence shows a group call request from client 1 to client 2 via the server, a discreet listening request from the server to client 3, and subsequent responses leading to media plane establishment.](dd380ccd5aca1151074fede04826f1a4_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 (call initiator) + participant MC service server + participant MC service client 2 (target) + participant MC service client 3 (authorized user) + Note left of MC service client 1: Group call request + MC service client 1->>MC service server: 1. Group call request + MC service server->>MC service client 2: 2. Group call request + MC service server->>MC service client 3: 3. Discreet listening call request + MC service client 2->>MC service server: 4. Group call response + MC service client 3->>MC service server: 5. Discreet listening call response + MC service server->>MC service client 1: 6. Group call response + Note right of MC service client 1: 7. Media plane established + +``` + +Sequence diagram for Figure 6.1.1.3.4-1: Discreet listening of target initiated group call. Lifelines: MC service client 1 (call initiator), MC service server, MC service client 2 (target), MC service client 3 (authorized user). The sequence shows a group call request from client 1 to client 2 via the server, a discreet listening request from the server to client 3, and subsequent responses leading to media plane establishment. + +**Figure 6.1.1.3.4-1: Discreet listening of target initiated group call** + +If the target initiated the group call, the discreet listening call request may include the client ID associated with the MC service client on which the target initiates the call. If the target receives a request for a group call, the discreet listening call request may include the client ID(s) of the MC service clients on which the group call request is received. + +The procedure is similar if the target of the discreet listening is the initiator of the group call. + +**NOTE 1:** If the MC service server does not receive the 'discreet listening call response' for any reason, the call should still proceed so that the requirement that the call is not affected and the target user is not aware of the discreet listening process is satisfied. + +**NOTE 2:** It is irrelevant whether the authorized user is or is not a member of the MC service group. + +##### 6.1.1.3.5 Information flows for discreet listening + +A single pair of information flows can support provision of discreet listening content of individual communications and group communications. Suitable information elements are shown in tables 6.1.1.3.5-1 and 6.1.1.3.5-2 below. + +**Table 6.1.1.3.5-1: Discreet listening call request** + +| Information element | Status | Description | +|--------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | MC service ID of the target of discreet listening | +| MC service client ID list (see NOTE) | O | List of MC service client IDs of the target user on which the call is requested | +| MC service ID | M | MC service ID of the other party in individual call, or MC service ID of talking party in group call | +| Call direction | M | Indicates whether the target or another party initiated the call | +| Call type | M | Indicates the type of communication (private call, group call etc) | +| MC service group ID | O | Provided if the communication is a group call | +| NOTE: | | MC service client ID identifies a specific installation of an MC service client on an MC service UE and is provided to the MC service server at service authorization of the MC service user. It may be equivalent to the client IDs specified in 3GPP TS 24.379 [10], 3GPP TS 24.281 [11] and 3GPP TS 24.282 [12]. | + +**Table 6.1.1.3.5-2: Discreet listening call response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------| +| MC service ID | M | MC service ID of the target of discreet listening | +| Result | M | Indicates the success or failure of the discreet listening call request | + +### 6.1.2 Impacts on existing nodes and functionality + +This solution results in the following impacts on existing entities and reference points: + +- MC service clients and MC service-I reference points: addition of functionality to request discreet listening and to specify a target MC user. +- MC service user configuration: authorization to request discreet listening on a list of target MC service IDs. +- A new procedure to request discreet listening specifying a target MC service user. +- A new procedure to provide the content of discreet listening. + +In each case, MC service is one of MCPTT, MCVideo or MCData. + +### 6.1.3 Solution Evaluation + +This solution allows discreet listening to be achieved with minimal changes to the functional model as it only requires enhancement to existing functional entities and reference points. It also allows discreet listening to be invoked on a service dependent basis as it is achieved as a function of the MC service specific MC service clients. It supports the situations where the MC service user is receiving MC service on multiple MC service clients. + +## 6.2 Solution 2: Discreet listening of MCVideo push and pull + +### 6.2.1 Description + +#### 6.2.1.1 Overview + +This solution addresses the MCVideo aspects of key issue 3 for discreet listening of MCVideo push and pull. + +#### 6.2.1.2 Invocation + +Discreet listening is activated by the MC service client of the authorized user according to the invocation procedures described in subclause 6.1.1.3.2 of the present document. + +#### 6.2.1.3 MCVideo push discreet listening procedure + +The procedure for discreet listening of a one to server push is shown in figure 6.2.1.3-1 below. + +![Sequence diagram for MCVideo push to server discreet listening procedure. The diagram shows interactions between MCVideo client 1, MCVideo server, and MCVideo client 2 (Authorized user).](e29665b8abcea967ef289c6aff07ae4c_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 as MCVideo client 2 Authorized user + + Note left of MCVideo client 1: Steps 1-7: MCVideo push to server + MCVideo client 1->>MCVideo server: 1. MCVideo push to server request + MCVideo server-->>MCVideo client 1: 2. Authorization check + MCVideo server-->>MCVideo client 1: 3. MCVideo push to server response + Note left of MCVideo client 1: 4. Media plane and transmission control established + MCVideo client 1->>MCVideo server: 5. Video stream from MCVideo client 1 + MCVideo client 1->>MCVideo server: 6. MCVideo push to server complete request + MCVideo server-->>MCVideo client 1: 7. MCVideo push to server complete response + + Note right of MCVideo server: Steps 11-17: Discreet listening + MCVideo server->>MCVideo client 2: 11. MCVideo push-pull discreet listening request + Note right of MCVideo client 2: 12. Decision whether to receive video stream + MCVideo client 2->>MCVideo server: 13. MCVideo push-pull discreet listening response + Note right of MCVideo server: 14. Media plane and transmission control established + MCVideo server->>MCVideo client 2: 15. Video stream from MCVideo server + MCVideo server->>MCVideo client 2: 16. MCVideo push-pull discreet listening complete request + MCVideo client 2-->>MCVideo server: 17. MCVideo push-pull discreet listening complete response + +``` + +Sequence diagram for MCVideo push to server discreet listening procedure. The diagram shows interactions between MCVideo client 1, MCVideo server, and MCVideo client 2 (Authorized user). + +**Figure 6.2.1.3-1: MCVideo push to server discreet listening** + +Steps 1 to 7 are described in 3GPP TS 23.281 [3] subclause 7.4.2.4, the procedure for one to server video push. Additional steps to support discreet listening are as follow: + +11. The MCVideo server notifies MCVideo client 2 of the authorized user that MCVideo client 1 has been authorized to push video to the MCVideo server. The notification includes the MCVideo ID of the MCVideo user and may include an MCVideo client ID of the MCVideo client from which the request to push video to the server was made. This step may take place at any time following step 2. +12. The authorized user is notified and decides whether to receive the MCVideo stream, or whether to just remain aware that an MCVideo push is taking place from the target MCVideo user of MCVideo client 1. +13. MCVideo client 2 provides the response to the MCVideo server, indicating whether the authorized user wishes to receive the video stream or not. + +NOTE: Steps 12 and 13 may utilise an automatic process, such that a human user does not need to make a decision at the time that the video stream push commences. + +If the authorized user decides to receive the video stream, steps 14 and 15 establish the media plane and transmission control, and transmit the video to the authorized user. Steps 16 and 17 complete the transaction. + +If step 14 is completed before step 5 occurs, i.e. the media plane is set up to the authorized user but video streaming has not commenced from MCVideo client 1, the video stream sent to MCVideo client 2 of the authorized user in step 15 does not start until the stream in step 5 is received by the MCVideo server. + +If step 14 has not completed before step 5 occurs, i.e. the MCVideo stream from MCVideo client 1 has commenced before the media plane is setup between the MCVideo server and MCVideo client 2 of the authorized user, the video stream in step 15 is either delayed so that the authorized user is able to view the stream from its commencement, or the + +stream is not delayed and so the authorized user receives the stream in real time, but does not receive the start of the video stream. + +**Editor's note:** It is FFS whether the decision to delay or to truncate the start of the video stream sent to the authorized user is determined by configuration or by some other mechanism. + +The same procedure can be followed between the MCVideo server and MCVideo client 2 of the authorized user where the MCVideo push is remotely initiated as described in subclause 7.4.2.5 of 3GPP TS 23.281 [3], and where the MCVideo push is sent to a group as described in subclause 7.4.2.6 of 3GPP TS 23.281 [3]. + +#### 6.2.1.4 MCVideo pull discreet listening procedure + +The procedure for discreet listening of a one from server pull is shown in figure 6.2.1.4-1 below. + +![Sequence diagram for MCVideo pull from server discreet listening. The diagram shows interactions between MCVideo client 1, MCVideo server, and MCVideo client 2 (Authorized user). Steps 1-7 are standard pull steps. Steps 11-17 are discreet listening steps: 11. MCVideo server notifies client 2; 12. client 2 decides; 13. client 2 responds to server; 14. media plane established for client 2; 15. video stream sent to client 2; 16. client 2 sends complete request; 17. client 2 receives complete response.](4af57aad638888edf2062306f8a54a6c_img.jpg) + +``` + +sequenceDiagram + participant MCVideo client 1 + participant MCVideo server + participant MCVideo client 2 as MCVideo client 2 +Authorized user + + Note left of MCVideo client 1: Steps 1 to 7 + MCVideo client 1->>MCVideo server: 1. MCVideo pull from server request + MCVideo server-->>MCVideo client 1: 3. MCVideo pull from server response + Note right of MCVideo server: 2. Authorization check + MCVideo server->>MCVideo client 2: 11. MCVideo push-pull discreet listening request + Note right of MCVideo client 2: 12. Decision whether to receive video stream + MCVideo client 2-->>MCVideo server: 13. MCVideo push-pull discreet listening response + Note right of MCVideo server: 14. Media plane and transmission control established + MCVideo server->>MCVideo client 2: 15. Video stream from MCVideo server + Note left of MCVideo client 1: 5. Video stream from MCVideo server + MCVideo client 1->>MCVideo server: 6. MCVideo pull from server complete request + MCVideo server-->>MCVideo client 1: 7. MCVideo pull from server complete response + MCVideo client 2->>MCVideo server: 16. MCVideo push-pull discreet listening complete request + MCVideo server-->>MCVideo client 2: 17. MCVideo push-pull discreet listening complete response + +``` + +Sequence diagram for MCVideo pull from server discreet listening. The diagram shows interactions between MCVideo client 1, MCVideo server, and MCVideo client 2 (Authorized user). Steps 1-7 are standard pull steps. Steps 11-17 are discreet listening steps: 11. MCVideo server notifies client 2; 12. client 2 decides; 13. client 2 responds to server; 14. media plane established for client 2; 15. video stream sent to client 2; 16. client 2 sends complete request; 17. client 2 receives complete response. + +**Figure 6.2.1.4-1: MCVideo pull from server discreet listening** + +Steps 1 to 7 are described in 3GPP TS 23.281 [3] subclause 7.3.2.4, the procedure for one from server video pull. Additional steps to support discreet listening are as follow: + +11. The MCVideo server notifies MCVideo client 2 of the authorized user that MCVideo client 1 has been authorized to pull video from the MCVideo server. The notification includes the MCVideo ID of the MCVideo user and may include an MCVideo client ID of the MCVideo client from which the request to pull video from the server was made. This step may take place at any time following step 2. +12. The authorized user is notified and decides whether to receive the MCVideo stream, or whether to just remain aware that an MCVideo pull is taking place to the target MCVideo user of MCVideo client 1. +13. MCVideo client 2 provides the response to the MCVideo server, indicating whether the authorized user wishes to receive the video stream or not. + +**NOTE:** Steps 12 and 13 may utilise an automatic process, such that a human user does not need to make a decision at the time that the video stream pull commences. + +If the authorized user decides to receive the video stream, steps 14 and 15 establish the media plane and transmission control, and transmit the video to the authorized user. Steps 16 and 17 complete the transaction. + +If step 14 is completed before step 5 occurs, i.e. the media plane is set up to the authorized user but video streaming has not commenced from the MCVideo server, the video stream sent to MCVideo client 2 of the authorized user in step 15 does not start until the stream in step 5 starts streaming from the MCVideo server. + +If step 14 has not completed before step 5 occurs, i.e. the MCVideo stream from the MCVideo server has commenced before the media plane is setup between the MCVideo server and MCVideo client 2 of the authorized user, the video stream in step 15 is either delayed so that the authorized user is able to view the stream from its commencement, or the stream is not delayed and so the authorized user receives the stream in real time, but does not receive the start of the video stream. + +**Editor's note:** It is FFS whether the decision to delay or to truncate the start of the video stream sent to the authorized user is determined by configuration or by some other mechanism. + +#### 6.2.1.5 Information flows for discreet listening of MCVideo push and pull + +A single pair of information flows can support the request and response for discreet listening of MCVideo push and pull video transfers. Suitable information elements are shown in tables 6.2.1.5-1 and 6.2.1.5-2 below. + +**Table 6.2.1.5-1: MCVideo push-pull discreet listening request** + +| Information element | Status | Description | +|------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCVideo ID | M | MCVideo ID of the target of discreet listening | +| MCVideo client ID (see NOTE) | O | MCVideo client ID of the MCVideo client on which the target user is requesting to push or pull video | +| MCVideo ID | O | MCVideo ID of third party requesting remote MCVideo push, if applicable | +| Push/pull | M | Indicates whether the video is being pushed to or pulled from the target MCVideo client | +| MC service group ID | O | Provided if the communication is a push to an MCVideo push | +| NOTE: | | MCVideo client ID identifies a specific installation of an MCVideo client on an MCVideo UE and is provided to the MCVideo server at service authorization of the MCVideo user. It may be equivalent to the client ID specified in 3GPP TS 24.281 [11]. | + +**Table 6.2.1.5-2: MCVideo push-pull discreet listening response** + +| Information element | Status | Description | +|------------------------|--------|--------------------------------------------------------------------------| +| MCVideo ID | M | MCVideo ID of the target of discreet listening | +| Video stream reception | M | Indicates whether the authorized user wishes to receive the video stream | + +The information elements for MCVideo push-pull discreet listening complete request and response are derived from those employed in steps 6 and 7 of the MCVideo push and pull procedures described in 3GPP TS 23.281 [3], and are illustrated in tables 6.2.1.5-3 and 6.2.1.5-4 below. + +**Table 6.2.1.5-3: MCVideo push-pull discreet listening complete request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------| +| MCVideo ID | M | MCVideo ID of the target of discreet listening | +| Cause | M | End of communication cause | + +**Table 6.2.1.5-4: MCVideo push-pull discreet listening complete response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------| +| MC service ID | M | MC service ID of the target of discreet listening | + +### 6.2.2 Impacts on existing nodes and functionality + +This solution results in the following impacts on existing entities and reference points: + +- MCVideo clients and MCVideo-1 reference points: addition of functionality to offer and accept discreet listening MCVideo push and pull content. +- New procedures to provide discreet listening of MCVideo push and pull transactions. + +- New configuration parameters may be needed to determine whether the MCVideo server truncates or caches video streams forwarded to the authorized user. + +- New configuration parameters may be needed to authorize the discreet listening of MCVideo push and pull transactions. + +### 6.2.3 Solution Evaluation + +This solution allows discreet listening of MCVideo push and pull transactions to be achieved with minimal changes to existing MCVideo functionality, as the provision of discreet listening is based on existing MCVideo push and pull procedures. The solution includes a means of identifying the MCVideo client where an MCVideo user is receiving MCVideo service from multiple MCVideo clients. Additional configuration parameters are likely to be needed to support the service. + +## 6.3 Solution 3: Functionality for on-network logging and replay + +### 6.3.1 Description + +#### 6.3.1.1 Functional model + +To support on-network logging and replay, existing common service core functional entities are reused. The MC logging function makes use of a new MC logging client which has a subset of the functionality of an existing MC service client, in that it can receive communications information and communications content relating to logged users, but cannot set up calls or demand to take part in calls. Provision of call related information and call content is achieved by configuration in the MC service server. The MC logging client uses an MC service ID to allow call related information and call content to be routed to the MC logging client, reusing functionality from existing reference points. + +NOTE 1: An MC logging function may contain multiple MC service clients to allow the separate services MCPTT, MCVideo and MCData to be logged within the same function. However this is out of scope of the description of the functional model. + +Figure 6.3.1.1-1 below illustrates the functional entities and reference points of the common services core in the application plane that are used for logging. + +![Figure 6.3.1.1-1: Common services core functional model for logging. The diagram shows the functional architecture for logging within a Common Services Core (CSC).](4792a2ccd62226861fadc22117edb7b1_img.jpg) + +The diagram illustrates the functional model for logging. On the left, an 'MC service server' is connected to a 'Common services core' (enclosed in a dashed box). The 'Common services core' contains four functional blocks: 'Configuration management server', 'Group management server', 'Identity management server', and 'Key management server'. These servers are connected to various clients on the right via reference points: + + +- The 'Configuration management server' connects to the 'Configuration management client' via reference point CSC-4. +- The 'Group management server' connects to the 'Group management client' via reference point CSC-2. +- The 'Identity management server' connects to the 'Identity management client' via reference point CSC-1. +- The 'Key management server' connects to the 'Key management client' via reference point CSC-8. + + The 'MC service server' also has a connection labeled CSC-9 to the 'Common services core'. On the right side, the clients are grouped into two functional blocks: + + +- The 'MC logging function' block contains the 'MC logging client', 'Logging storage', 'Configuration management client', 'Group management client', 'Identity management client', and 'Key management client'. This block is associated with reference point MCLog-10. +- The 'MC replay equipment' block contains the 'MC replay client', 'Identity management client', and 'Key management client'. This block is connected to the 'MC logging function' via CSC-1 and CSC-8. + +Figure 6.3.1.1-1: Common services core functional model for logging. The diagram shows the functional architecture for logging within a Common Services Core (CSC). + +**Figure 6.3.1.1-1: Common services core functional model for logging** + +In Figure 6.3.1.1-1, the MC logging function is configured with the list of MC service IDs and MC service groups that the logging function will log using reference point CSC-4. The group management client receives configuration for groups that are to be logged. The identity management client allows the logging function to be authorized for logging service using reference point CSC-1, using either security credentials supplied by a user or supplied by the logging application. The key management client obtains keys using reference point CSC-8 to protect signalling information between MC service server and MC service client. Keys may be obtained to protect media if the solution is intended to log communications with any end to end encryption removed. + +NOTE 2: The means of protecting media and communications related information during storage within the MC logging function is outside the scope of this solution. + +The MC replay function receives the necessary security information needed to replay logged communications by CSC-8. A user of the replay function, or an automatic function of the replay function, will perform the necessary authorizations to retrieve logged communications, and CSC-1 will be used to verify the authenticity and authorization of the user or function. + +NOTE 3: Inclusion of the mechanisms for MC service user authentication and authorization for use by the replay function within this solution allows the user organization to require the same security processes to access logged information as the security processes that are used to communicate within the MC service. Alternative solutions are possible, but not considered within this solution. + +The MC logging function and MC replay function are in the same security domain as the MC system for which communications are logged. + +The interface MCLog-10 between the logging recorder and the replay client to retrieve communications is out of scope of this solution. MCLog-10 does not need to use 3GPP access for connectivity. Information relating to the user of the logging replay function and any profile for this replay function user are out of scope of this solution. + +Figure 6.3.1.1-2 below shows the MC service related application plane entities used to log communications. + +![Figure 6.3.1.1-2: MC service related application plane functional model for logging. The diagram shows two main entities: 'MC service server' on the left and 'MC logging function' on the right. The 'MC service server' contains two sub-functions: 'Media distribution function' and 'Media control server'. The 'MC logging function' contains an 'MC logging client' which in turn contains 'Media reception' and 'Media participant'. Three interfaces are shown: MCLog-2 connects 'Media distribution function' to 'Media reception'; MCLog-1 connects 'Media distribution function' to 'Media participant'; and MCLog-3 connects 'Media control server' to 'Media participant'.](7a1dee155822446f7828dcb055c465c3_img.jpg) + +``` + +graph LR + subgraph MC_service_server [MC service server] + MDF[Media distribution function] + MCS[Media control server] + end + subgraph MC_logging_function [MC logging function] + subgraph MC_logging_client [MC logging client] + MR[Media reception] + MP[Media participant] + end + end + MDF -- MCLog-2 --> MR + MDF -- MCLog-1 --> MP + MCS -- MCLog-3 --> MP + +``` + +Figure 6.3.1.1-2: MC service related application plane functional model for logging. The diagram shows two main entities: 'MC service server' on the left and 'MC logging function' on the right. The 'MC service server' contains two sub-functions: 'Media distribution function' and 'Media control server'. The 'MC logging function' contains an 'MC logging client' which in turn contains 'Media reception' and 'Media participant'. Three interfaces are shown: MCLog-2 connects 'Media distribution function' to 'Media reception'; MCLog-1 connects 'Media distribution function' to 'Media participant'; and MCLog-3 connects 'Media control server' to 'Media participant'. + +**Figure 6.3.1.1-2: MC service related application plane functional model for logging** + +In figure 6.3.1.1-2, the MC logging function may comprise MC logging clients dedicated to MCPTT, MCVideo and MCData. Each MC logging client is identified by a service specific identity, namely the MCPTT ID, MCVideo ID or MCData ID of the client. Call related information concerning the targets of logging are sent to the MC logging function via MCLog-1, which is based on the MCservice-1 reference points (i.e. MCPTT-1, MCVideo-1 etc) but does not permit calls to be initiated by the MC logging function. Media plane communications content is provided to the media reception function of the MC logging client via MCLog-2, which is based on unicast media distribution reference points MC service-7 (i.e. MCPTT-7, MCVideo-7 etc), and floor control or media control information provided during calls is provided via MCLog-3. + +*Editor's note: MCData services may require further functionality to be described.* + +#### 6.3.1.2 Configuration + +The MC logging equipment will require configuration to determine which MC service users and which MC service groups are required by that MC logging equipment. Table 6.3.1.2-1 below illustrates the identity specific configuration data applicable to each MC logging equipment. It is expected that the MC logging equipment configuration will not be added into existing MC service user configuration tables, but will have a unique configuration table. + +*Editor's note: It is expected that further configuration information will be needed. This table is intended to contain initial information only.* + +**Table 6.3.1.2-1: MC logging equipment configuration** + +| Reference | Parameter description | MC logging equipment | MC service server | Configuration management server | +|-----------|------------------------------------------|----------------------|-------------------|---------------------------------| +| | MC service identity of MC logging client | Y | Y | Y | +| | List of users to be logged | | | | +| | > MC service ID | Y | Y | Y | +| | List of groups to be logged | | | | +| | > MC service group ID | Y | Y | Y | + +The need to log MC service group calls will require MC service group configuration information to include the list of MC logging equipments. The additions shown in table 6.3.1.2-2 will be made to table A.4-2 (MC service group configuration) in 3GPP TS 23.280 [2]. + +Editor's note: Further configuration information related to logging may be added in addition to the identities listed in table 6.3.1.2-2 below. + +**Table 6.3.1.2-2: Addition to common group configuration data (on network) for logging** + +| Reference | Parameter description | MC service UE | MC service Server | Group management server | +|-----------|---------------------------------------------------|---------------|-------------------|-------------------------| +| | List of logging equipments that log MCPTT calls | | | | +| | >MCPTT ID | | Y | Y | +| | List of logging equipments that log MCVideo calls | | | | +| | >MCVideo ID | | Y | Y | +| | List of logging equipments that log MCData calls | | | | +| | >MCData ID | | Y | Y | + +Additionally, the MC service ID for the logging equipment that is assigned to log the communications of each MC service user will need to be added to the user profiles for MCPTT in 3GPP TS 23.379 [7], for MCVideo in 3GPP TS 23.281 [8] and for MCData in 3GPP TS 23.282 [9]. + +#### 6.3.1.3 Procedures + +To initialise the logging function, the MC logging equipment will perform service authorization to each of the MC service servers following the procedure for authentication and authorization the primary MC system specified in 3GPP TS 23.280 [2] subclause 10.6.1. + +It is not envisaged that any explicit protocol exchange will be carried out in order to start logging communications of identified MC service users and MC service group. Once service authorized, the MC logging equipment will be implicitly affiliated to all its configured MC service groups. However a procedure may be needed to show the interaction between the service authorization of the logging equipment and the implicit authentication of the MC logging client of the MC logging equipment to the logged MC service groups. + +Procedures will need to be defined to illustrate the provision of communications content and communications related information to the MC logging equipment. The functionality of the reference points MCLog-1, MCLog-2 and MCLog-3 that provide this information will need to be defined, derived from existing reference points. + +The MC service server will send the MC logging equipment: + +- Notification of service authorization for each logged MC service user. +- Notification of MC service group affiliations of each member of each logged MC service group, and notifications of group affiliations from each logged MC service user. + +- Notifications of call set up information for each logged MC service user and MC service group +- Notifications of floor control, transmission control and media control information for each MC service user and MC service group +- The content of each media exchange to and from each logged MC service user and within each logged MC service group +- Notifications of end of logged calls + +Each notification will include a timestamp. + +Each notification will include the identity of the MC service user being logged, and may include an MC service client ID or list of MC service client IDs of the MC service client(s) on which the MC service user is sending or receiving media. Where group calls are logged, the MC service ID of the transmitting party is included in the notification, and an MC service client ID relating to the MC service client from which the transmission is being made may also be included. + +**NOTE:** The MC service client ID identifies a specific installation of an MC service client on an MC service UE and is provided to the MC service server at service authorization of the MC service user. It may be equivalent to the client IDs specified in 3GPP TS 24.379 [10], 3GPP TS 24.281 [11] and 3GPP TS 24.282 [12]. + +The MC replay equipment will require authorization of the MC service user making use of the MC replay equipment, following the procedure for authentication and authorization the primary MC system specified in 3GPP TS 23.280 [2] subclause 10.6.1. Configuration and authorization of the user of the MC replay equipment is out of scope of this solution. + +**Editor's note:** It is FFS whether authorization to use MC replay equipment is within the scope of the user profile of an MC service user as defined in the MC service specifications. + +### 6.3.2 Impacts on existing nodes and functionality + +New entities are introduced in this solution, specifically the MC logging equipment and its constituent MC logging client together with MC logging storage and the MC replay equipment containing the MC replay client. The new MC logging client is based on existing MC service clients to maximise reuse of existing functionality and reference points. + +The process for authentication and service authorization use existing functional entities, reference points and procedures. + +New configuration will be introduced to configure logging equipment, and to configure MC service groups with the list of MC logging equipments that will log MC service group communications. + +New procedures for logging call related information and call contents will be required. However these can be based on existing procedures for call setup and floor, transmission and media control within calls. + +Interactions between MC logging client, logging storage and the MC replay client are not specified within this solution and so have no impact on existing nodes and functionality. + +### 6.3.3 Solution Evaluation + +This solution defines new functional entities and reference points to fulfil the on-network logging requirement together with reuse of existing common services core functional entities and reference points. The new functional entities and reference points will be based on the functionality of existing MC service clients and associated reference points. The solution includes a means of identifying the MC service client where an MC service user is receiving MC service from multiple MC service clients. + +A set of procedures will need to be defined to show the invocation of logging functions on logged calls. + +## 6.4 Solution 4: On-network logging for interconnection and migration + +### 6.4.1 Description + +#### 6.4.1.1 General + +This solution builds on solution 3, 'Functionality for on-network logging and replay' to add the case where the logging equipment receives service from its primary MC system, but the target of logging is receiving service in a partner MC system. The target of logging may be receiving MC service in its primary MC system, or may have migrated to that MC system from another MC system. + +#### 6.4.1.2 Functional model + +The functional model in solution 3 is expanded to show the interconnection to a different MC system. This is shown in figure 6.4.1.2-1 below. + +![Functional model diagram showing interconnection between an Other MC system, a Common services core, and MC logging equipment.](5d76c2e9976aaf97001ee189908830fb_img.jpg) + +The diagram illustrates the functional model for logging with interconnection. It consists of three main components: + + +- Other MC system (left):** Contains four servers: MC gateway server, MC service server, Configuration management server, and Group management server. +- Common services core (middle):** Contains five servers: MC service server, Configuration management server, Group management server, Identity management server, and Key management server. +- MC logging equipment (right):** Contains five clients: MC logging client, Logging storage, Configuration management client, Group management client, Identity management client, and Key management client. + + Interconnections are as follows: + + +- The MC gateway server in the Other MC system connects to the MC gateway server in the Common services core via reference point MCX-1. +- The MC service server in the Other MC system connects to the MC service server in the Common services core via reference point MCX-1. +- The Configuration management server in the Other MC system connects to the Configuration management server in the Common services core via reference point CSC-17. +- The Group management server in the Other MC system connects to the Group management server in the Common services core via reference point CSC-16. +- From the Common services core, the servers connect to the clients in the MC logging equipment via the following reference points: + - Configuration management server to Configuration management client via CSC-4. + - Group management server to Group management client via CSC-2. + - Identity management server to Identity management client via CSC-1. + - Key management server to Key management client via CSC-8. + - An additional connection labeled CSC-9 is shown between the MC service server and the Key management server in the Common services core. + +Functional model diagram showing interconnection between an Other MC system, a Common services core, and MC logging equipment. + +Figure 6.4.1.2-1: Common services core functional model for logging with interconnection + +In Figure 6.4.1.2-1, the interaction between the MC logging equipment and the MC replay equipment is not shown and remains according to solution 3. + +The configuration management server in the primary MC system of the MC logging equipment provides the MC logging equipment with the list of MC service users and MC service groups that the MC logging equipment logs. This can include users and groups that receive service in partner MC systems. The list of users and groups receiving service in the partner MC system is shared by the configuration management server in the primary MC system of the MC logging equipment with the configuration management server in the partner MC system using reference point CSC-17, and authorized users or administrators of the partner MC system can locally modify or authorize the list. When this configuration in the partner MC system is provided to the partner MC service server, the partner MC service server can determine which calls should be provided to the primary MC system of the MC logging equipment to allow logging to take place. + +There needs to be interaction between the group management servers in the two MC systems using reference point CSC-16 so that the group management server in the partner MC system can authorize the MC logging equipment to be a member of MC service groups which are hosted in that partner MC system. + +Figure 6.4.1.2-2 below shows the MC service related application plane entities used to log communications originating from a partner MC system. + +![Figure 6.4.1.2-2: MC service related application plane functional model for logging for interconnection. The diagram shows three main components: Partner MC service server, MC service server, and MC logging equipment. The Partner MC service server contains 'Media distribution function' and 'Media control server'. The MC service server contains 'Media distribution function' and 'Media control server'. The MC logging equipment contains 'MC logging client', 'Media reception', and 'Media participant'. Arrows indicate the flow of information: MCLog-4 from Partner MC service server to MC service server; MCLog-2, MCLog-1, and MCLog-3 from MC service server to MC logging equipment.](d793cf7c174b89eb024d132f00679787_img.jpg) + +``` + +graph LR + subgraph PartnerMC [Partner MC service server] + P_MDF[Media distribution function] + P_MCS[Media control server] + end + subgraph MCServer [MC service server] + M_MDF[Media distribution function] + M_MCS[Media control server] + end + subgraph MCLogging [MC logging equipment] + ML_C[MC logging client] + MR[Media reception] + MP[Media participant] + end + P_MDF -- MCLog-4 --> M_MDF + M_MDF -- MCLog-2 --> MR + M_MCS -- MCLog-1 --> MR + M_MCS -- MCLog-3 --> MP + +``` + +Figure 6.4.1.2-2: MC service related application plane functional model for logging for interconnection. The diagram shows three main components: Partner MC service server, MC service server, and MC logging equipment. The Partner MC service server contains 'Media distribution function' and 'Media control server'. The MC service server contains 'Media distribution function' and 'Media control server'. The MC logging equipment contains 'MC logging client', 'Media reception', and 'Media participant'. Arrows indicate the flow of information: MCLog-4 from Partner MC service server to MC service server; MCLog-2, MCLog-1, and MCLog-3 from MC service server to MC logging equipment. + +**Figure 6.4.1.2-2: MC service related application plane functional model for logging for interconnection** + +In figure 6.4.1.2-2, an additional reference point MCLog-4 is added between MC service servers compared with the functional model in solution 3. MCLog-4 carries call related information and call content from the partner MC service server to the primary MC service server, and is based on reference point MCX-1. Compared with MCX-1, MCLog-4 only permits communications information to originate from the partner MC service server and to flow via the primary MC service server to the MC logging equipment, and does not permit calls to be set up in the opposite direction. + +#### 6.4.1.3 Configuration + +##### 6.4.1.3.1 General + +The MC logging equipment configuration outlined in solution 3 remains unchanged for interconnection and migration. The list of users and groups to be logged can include users and groups receiving service in a partner MC system of the MC logging equipment. + +The impact of logging for MC service groups, and a configuration for logging of group communications where the group host is a partner MC system of the MC logging equipment is presented in subclause 6.4.1.3.2. + +The impact of logging for MC service users is presented as three alternative solutions for logging of individual communications in a partner MC system, contained in subclauses 6.4.1.3.3, 6.4.1.3.4 and 6.4.1.3.5. Individual communications include private calls between MC service users and communications between an MC service user and a server. It is necessary for a primary MC system to be provided with the MC service IDs of the MC logging clients of logging equipments which are providing logging service in a partner MC system, and for authorized users or administrators of the primary MC system to be able to authorize this logging from a partner MC system. The three options in the three subclauses provide this information in alternative ways. + +##### 6.4.1.3.2 Logging of group communications in partner system + +No changes are needed to group configuration information. The common group configuration (on-network) includes the MC service IDs of the MC logging clients of the MC logging equipment which is providing the logging service in a partner MC system of the group. + +##### 6.4.1.3.3 Logging of individual communications – option 1 + +In solution 3, the list of MC service IDs to be logged by an MC logging equipment are listed in the configuration of the MC logging equipment, and the MC service IDs relating to the MC logging equipment are not listed in the user profiles of the target MC service users. In the solution described in the present subclause, the user profiles of MC service users are expanded to include the MC service IDs of the responsible MC logging equipment. Thus an on-network MC service user profile will gain the configuration parameters listed in table 6.4.1.3.3-1. + +**Table 6.4.1.3.3-1: Addition to MC service user profile for logging of individual communications** + +| Reference | Parameter description | MCPTT UE | MCPTT server | Configuration management server | MCPTT user database | +|-----------|----------------------------------------------------------------------------|----------|--------------|---------------------------------|---------------------| +| | List of MC logging clients which log communications of the MC service user | | | | | +| | > MC service ID | N | Y | Y | Y | + +In Table 6.4.1.3.3-1 'MC service' represents one of MCPTT, MCVideo or MCData. + +To support interconnection, the MC service IDs of the MC logging clients will include those contained in MC logging equipment that is providing logging service in a partner MC system. In the case of migration, the partner MC system of the migrated MC service user will receive a user profile from the primary MC system of the MC service user which includes the list of MC logging equipment in the primary MC system of the MC service user (and in any other MC systems) which log the communications of that MC service user. + +NOTE: This solution has similarities with the configuration for MC service groups, where the group members are listed in the group configuration information, and the list of groups for each MC service user is listed in the user profile. + +##### 6.4.1.3.4 Logging of individual communications – option 2 + +In this solution, the configuration table of the MC logging equipment and its target MC service users described in solution 3, table 6.3.1.2-1, is provided to the partner MC system. The partner MC system therefore may receive multiple configuration tables from the primary MC system of the MC logging equipment where each configuration table identifies an MC logging equipment and the list of MC service users to be logged. The configuration information will need to be analysed in the partner MC system to determine which MC service servers need to be provided with the information to permit logging based on the list of target MC service users. + +NOTE: The primary MC system of the MC logging equipment may provide the partner MC system with a configuration table relevant to each MC logging equipment where only target MC service users that may receive MC service in the partner MC system are listed (instead of the full set of users that the MC logging equipment logs). + +##### 6.4.1.3.5 Logging of individual communications – option 3 + +In this solution, a single configuration table is provided to the partner MC system that lists the MC service identities of the MC logging equipments which provide logging service in their primary MC system and their set of logged MC service users. Such a configuration table is shown in table 6.4.1.3.5-1. + +**Table 6.4.1.3.5-1: MC logging equipment configuration for provision to partner MC system** + +| Reference | Parameter description | MC service server | Configuration management server | +|-----------|------------------------------------------|-------------------|---------------------------------| +| | MC service identity of MC logging client | | | +| | > MC service ID | Y | Y | +| | > List of users to be logged | | | +| | >> MC service ID | Y | Y | + +The configuration information will need to be analysed in the partner MC system to determine which MC service servers need to be provided with the information to permit logging based on the list of target MC service users. + +NOTE 1: The primary MC system of the MC logging equipment may provide the partner MC system with a configuration table relevant to each MC logging equipment where only target MC service users that may receive MC service in the partner MC system are listed (instead of the full set of users that the MC logging equipment logs). + +NOTE 2: The table could also include a list of MC service groups to be logged for each MC logging equipment. + +#### 6.4.1.4 Procedures + +Solution 3 discusses the need to add procedures to the MC service specifications to illustrate the inclusion of the MC logging equipment in communications. In the case of interconnection, the generic procedures for interconnection described in 3GPP TS 23.280 [2] subclause 10.14 also apply to procedures for logging, allowing the relevant partner MC system to be determined and authorization for the logging to take place by both the primary and partner MC systems. + +### 6.4.2 Impacts on existing nodes and functionality + +An additional reference point is added to the MC service servers, MCLog-4, to allow communication related information and communication content to be passed from the MC service server where the communications are hosted to the primary MC service server of the MC logging equipment. However this is based on existing reference point MCX-1, and can be considered a reduced function set of MCX-1. + +Additional configuration is added beyond that specified in solution 3, to allow MC logging equipment providing logging in one MC system to receive the communications for logging from a partner MC system. + +### 6.4.3 Solution Evaluation + +This solution expands the solution defined in solution 3 to allow logging where the logging equipment is providing logging services in a different MC system to that of the MC logging equipment. + +Three options are provided to provide configuration to a partner MC system to enable logging of individual communications. Of these, option 1 which adds the MC service ID associated with the MC logging equipment to the user profile is preferred as it does not add further configuration tables to be exchanged between primary and partner MC systems to enable interconnection and migration, and does not require any analysis in the partner MC system to determine which MC service servers need to be provided with the information. + +## 6.5 Solution 5: Discreet listening for interconnection and migration + +### 6.5.1 Description + +#### 6.5.1.1 Functional model + +Solution 1 proposes that discreet listening within a single MC system is a functionality available to an authorized user, and therefore no changes are needed to the functional models for MC services. This will also be the case for interconnection and migration. + +#### 6.5.1.2 Configuration + +##### 6.5.1.2.1 General + +The additional authorization to perform discreet listening to the user profiles for MCPTT, MCVideo and MCData which is proposed in solution 1 includes lists of users upon whom discreet listening can be invoked: these can include users that receive service in partner MC systems and therefore no further configuration is needed for interconnection and migration for the authorized user. + +However, an MC system that provides MC service to a target for discreet listening will need to authorize requests for discreet listening that originate from a partner MC system. Three options are provided in the following subclauses as means to provide configuration to another MC system to allow such authorization to take place. + +##### 6.5.1.2.2 User profile authorization of discreet listening – option 1 + +To permit discreet listening from a partner MC system, in this option the user profile of the target for discreet listening is modified to include the list of authorized users that are able to perform discreet listening on that target user. This will entail additions to the user profiles for MC service users as shown in table 6.5.1.2.2-1 below. + +**Table 6.5.1.2.2-1: Addition to MC service user profiles (on network)** + +| Reference | Parameter description | MC service UE | MC service Server | Configuration management server | MC service user database | +|-----------|-------------------------------------------------------------------------------------|---------------|-------------------|---------------------------------|--------------------------| +| | List of authorized users who can perform discreet listening on this MC service user | | | | | +| | > MC service ID | N | Y | Y | Y | + +In Table 6.5.1.2.2-1 'MC service' represents one of MCPTT, MCVide0 or MCData. + +Therefore, if an authorized user in a partner MC system of an MC service user is authorized to perform discreet listening on that MC service user, that authorized user's MC service identity will be configured in the user profile of the target MC service user. When an MC service user migrates to a partner MC system, the user profile for migration provided to the partner MC system of that MC service user will list authorized users permitted to perform discreet listening on that MC service user, including those authorized users who receive MC service in the primary MC system of the migrating MC service user, or in any other MC system. The inclusion of this information in the user profile allows the MC service server in the partner MC system which provides service to the target MC service user to authorize requests for discreet listening when they arise. + +##### 6.5.1.2.3 Sharing the user profile for authorized users – option 2 + +In this option, the primary MC system of the authorized user shares a user profile for the authorized user with any partner MC systems which are providing service to MC service users that are (potential) targets for discreet listening prior to any requests for discreet listening. According to solution 1, the user profile for the authorized user lists the configured target users for that authorized user. Where there are multiple authorized users who need to perform discreet listening on targets in a partner MC system, a separate user profile is provided to the partner MC system for each of those authorized users. The profiles are provided to the MC service servers providing service to the target MC service users, so that requests for discreet listening can be authorized when needed. + +The additional information in the user profile of the authorized user is shown in table 6.5.1.2.3-1 below, and is the same as that shown in Solution 1. + +**Table 6.5.1.2.3-1: Addition to user profile (on network) for authorized user** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Configuration management server | MCPTT user database | +|-----------|---------------------------------------------------------------------|----------|--------------|---------------------------------|---------------------| +| | Authorized to perform discreet listening on another MC service user | Y | Y | Y | Y | +| | List of users upon whom discreet listening can be invoked | | | | | +| | > MC service ID | Y | Y | Y | Y | + +NOTE: The profile shared with the partner MC system only need contain the information about targets for discreet listening that receive MC service in that partner MC system, and need not contain any other configuration information for the authorized user. + +##### 6.5.1.2.4 New configuration table of authorized users – option 3 + +In this option, a new configuration table is defined in the primary MC system of the authorized users who require discreet listening, which lists those authorized users and each of the valid target users on who discreet listening can be performed. This table is shared with the partner MC system prior to discreet listening taking place. The table is provided to the MC service servers in the partner MC system that provide service to the targets of discreet listening to allow discreet listening invoked by the nominated authorized users to be permitted. + +NOTE 1: The MC service server in the primary MC system of the authorized user does not require this table, as the authorization to perform discreet listening and the list of targets is already contained in the user profile for the authorized user. + +The form of the table is shown in table 6.5.1.2.4 below. + +**Table 6.5.1.2.4-1: Table of authorized users for discreet listening for provision to partner MC system** + +| Reference | Parameter description | MC service server | Configuration management server | +|-----------|------------------------------------------------------------|-------------------|---------------------------------| +| | MC service identity of authorized user | | | +| | > MC service ID | Y | Y | +| | > List of users on who discreet listening can be performed | | | +| | >> MC service ID | Y | Y | + +NOTE 2: The primary MC system of the authorized user may provide a configuration table to the partner MC system where only relevant MC service users are listed, i.e. the authorized users that may invoke discreet listening from their primary MC system, and the list of target users that may receive MC service in that partner MC system only. + +#### 6.5.1.3 Procedures + +Solutions 1 and 2 detail procedures to invoke discreet listening in a single MC system. These procedures can be utilized together with the generic procedures for interconnection which are described in 3GPP TS 23.280 [2] subclause 10.14, which allow the relevant partner MC system to be determined and authorization to be carried out by both primary and partner MC systems. + +### 6.5.2 Impacts on existing nodes and functionality + +This solution results in additional configuration to be shared between primary MC system of the authorized user and the partner MC system of the authorized user, where the target of discreet listening is receiving MC service in that partner MC system. The nature of the configuration information is determined by which of the three options in subclause 6.5.1.2 is adopted. Configuration information needs to be provided to the MC service servers providing service to the targets of discreet listening so that requests for discreet listening can be authorized. Options 2 and 3 require some examination of the configuration information in the partner system before it is provided to the MC service servers, as the MC service servers to be provided with the configuration information are determined by the lists of users within the configuration tables. + +### 6.5.3 Solution Evaluation + +This solution expands the solutions 1 and 2 to allow discreet listening where the target is receiving MC service from a different MC system from that of the authorized user performing discreet listening. The three configuration options are evaluated as follow. + +- Option 1 adds the list of authorized users to the user profile of every potential target user. This could be considered sensitive, however the target MC service user would not be provided with this aspect of the user profile via the MC service UE, and the list of permissible authorized users does not provide any information about when the discreet listening service is invoked. This option provides the least additional configuration work, as a partner MC system would be configured with this information as a matter of course for any MC service users for who the partner MC system is their primary MC system, and the partner MC system would receive this information whenever an MC service user migrated to that partner MC system. The provision of configuration to MC service server is according to existing procedures. +- Option 2 requires the primary MC system of the authorized user to share a partial user profile with the partner MC system in advance of the invocation of discreet listening. This would be a new set of information which would need to be shared independently from either call related services or migration. Provision to the MC service server in the partner MC system requires analysis of the configuration information, as the target users are members of a lists. +- Option 3 requires a new configuration table to be created and shared by the primary MC system of the authorized users with the partner system in advance of the invocation of discreet listening. As for option 2, this would be a new set of information which would need to be shared independently from either call related services or migration. Provision to the MC service server in the partner MC system requires analysis of the configuration information, as the target users are members of a lists. + +Therefore of these three options, option 1 is the most consistent with current MC system operation and requires the least additional configuration work, however options 2 and 3 may result in simpler solutions. + +## 6.6 Solution 6: Discreet listening to an MCPTT group + +### 6.6.1 Description + +#### 6.6.1.1 Overview + +This solution serves for the scenario where an authorized user specifies an MCPTT group to be the target of discreet listening. The invocation of discreet listening to a group is based on pre-configured authorizations for the listener and the group members of the target group. The provision of discreet listening of a target group is performed either at the initiation of the group call or during the on-going group call. + +#### 6.6.1.2 Configuration + +In user profile configuration of MCPTT in TS 23.379 clause A.3, two new parameters are added to indicate the authorization of activating discreet listening to a target group and the list of target groups. + +**Table 6.6.1.2-1: Addition to MCPTT user profiles (on network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Configuration management server | MCPTT user database | +|-----------|-----------------------------------------------------------------|----------|--------------|---------------------------------|---------------------| +| | Authorized to perform discreet listening on an MC service group | Y | Y | Y | Y | +| | List of group(s) upon which discreet listening can be invoked | | | | | +| | > MCPTT group ID(s) | Y | Y | Y | Y | + +In group configuration data of MCPTT in TS 23.379 clause A.4, a new parameter is added to indicate the authorization of group members for being discreet listened. + +**Table 6.6.1.2-2: Addition to MCPTT group configuration data (on-network)** + +| Reference | Parameter description | MCPTT UE | MCPTT Server | Group management server | +|-----------|------------------------------------------------------------------------------------|----------|--------------|-------------------------| +| | >> Authorization for being discreet listened in group communications of this group | N | Y | Y | +| | >> List of user(s) who are authorized to perform discreet listening to this group | | | | +| | >>> MCPTT ID(s) | N | Y | Y | + +#### 6.6.1.3 Procedures + +##### 6.6.1.3.1 Discreet listening activation and deactivation + +The procedures for activation and deactivation of discreet listening to groups are shown in figure 6.6.1.3.1-1 and figure 6.6.1.3.1-2 below. + +![Sequence diagram showing discreet listening group activation. A MCPTT client (authorized user) sends a '1. Discreet listening group activation request' to the MCPTT server, which responds with '2. Discreet listening group activation response'.](9d70cd4e4cef3f16262b47c8c8f6c642_img.jpg) + +``` + +sequenceDiagram + participant Client as MCPTT client (authorized user) + participant Server as MCPTT server + Note left of Client: + Client->>Server: 1. Discreet listening group activation request + Note right of Server: + Server-->>Client: 2. Discreet listening group activation response + +``` + +Sequence diagram showing discreet listening group activation. A MCPTT client (authorized user) sends a '1. Discreet listening group activation request' to the MCPTT server, which responds with '2. Discreet listening group activation response'. + +**Figure 6.6.1.3.1-1: Discreet listening group activation** + +![Sequence diagram for Discreet listening group deactivation. It shows two lifelines: 'MCPTT client (authorized user)' and 'MCPTT server'. The client sends a '1. Discreet listening group deactivation request' to the server, and the server responds with '2. Discreet listening group deactivation response'.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` +sequenceDiagram + participant Client as MCPTT client (authorized user) + participant Server as MCPTT server + Client->>Server: 1. Discreet listening group deactivation request + Server-->>Client: 2. Discreet listening group deactivation response +``` + +Sequence diagram for Discreet listening group deactivation. It shows two lifelines: 'MCPTT client (authorized user)' and 'MCPTT server'. The client sends a '1. Discreet listening group deactivation request' to the server, and the server responds with '2. Discreet listening group deactivation response'. + +**Figure 6.6.1.3.1-2: Discreet listening group deactivation** + +##### 6.6.1.3.2 Provision of discreet listening to groups + +The provision of discreet listening can only happen after it is successfully activated. The provision of discreet listening towards a target group is made by inviting the authorized user to the target group call if it is initiated after the activation of discreet listening (as shown in figure 6.6.1.3.2-1), or by transferring the target group call to the authorized user if it is initiated before the activation of discreet listening (as shown in figure 6.6.1.3.2-2). + +Pre-conditions: + +- 1. MCPTT client 3 (authorized user) has activated discreet listening to this specified MCPTT group. + +![Sequence diagram for Discreet listening of MCPTT group call. It features four lifelines: 'MCPTT client 1 (call initiator)', 'MCPTT server', 'MCPTT client 2', and 'MCPTT client 3 (authorized user)'. The sequence starts with a group call request from client 1 to the server, which is then forwarded to client 2 and client 3. Responses are returned from client 2 and client 3 to the server, which then responds to client 1. Finally, a media plane is established for all participants.](e9d825d87c5f85c8dba0664eace96ef4_img.jpg) + +``` +sequenceDiagram + participant Client1 as MCPTT client 1 (call initiator) + participant Server as MCPTT server + participant Client2 as MCPTT client 2 + participant Client3 as MCPTT client 3 (authorized user) + Client1->>Server: 1. Group call request + Server->>Client2: 2. Group call request + Server->>Client3: 3. Discreet listening group call request + Client2-->>Server: 4. Group call response + Client3-->>Server: 5. Discreet listening group call response + Server-->>Client1: 6. Group call response + Note over Client1,Client3: 7. Media plane established +``` + +Sequence diagram for Discreet listening of MCPTT group call. It features four lifelines: 'MCPTT client 1 (call initiator)', 'MCPTT server', 'MCPTT client 2', and 'MCPTT client 3 (authorized user)'. The sequence starts with a group call request from client 1 to the server, which is then forwarded to client 2 and client 3. Responses are returned from client 2 and client 3 to the server, which then responds to client 1. Finally, a media plane is established for all participants. + +**Figure 6.6.1.3.2-1: Discreet listening of MCPTT group call (discreet listening for target group is activated)** + +![Sequence diagram for Figure 6.6.1.3.2-2: Discreet listening of MCPTT group call (discreet listening for target group is not activated).](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant MCPTT 1 (call initiator) + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 (authorized user) + + Note left of MCPTT 1: 1. Group call request + MCPTT 1->>MCPTT server: 1. Group call request + Note right of MCPTT server: 2. Group call request + MCPTT server->>MCPTT client 2: 2. Group call request + Note right of MCPTT client 2: 3. Group call response + MCPTT client 2->>MCPTT server: 3. Group call response + Note right of MCPTT server: 4. Group call response + MCPTT server->>MCPTT 1: 4. Group call response + Note left of MCPTT server: 5. Media plane established + Note right of MCPTT server: 6. Discreet listening group activation request + MCPTT server->>MCPTT client 3: 6. Discreet listening group activation request + Note right of MCPTT client 3: 7. Discreet listening group activation response + MCPTT client 3->>MCPTT server: 7. Discreet listening group activation response + Note right of MCPTT server: 8. Discreet listening group call request + MCPTT server->>MCPTT client 3: 8. Discreet listening group call request + Note right of MCPTT client 3: 9. Discreet listening group call response + MCPTT client 3->>MCPTT server: 9. Discreet listening group call response + Note left of MCPTT server: 10. Media plane established + +``` + +Sequence diagram for Figure 6.6.1.3.2-2: Discreet listening of MCPTT group call (discreet listening for target group is not activated). + +**Figure 6.6.1.3.2-2: Discreet listening of MCPTT group call (discreet listening for target group is not activated)** + +##### 6.6.1.3.3 Release discreet listening to groups + +When the authorized user decides to stop discreet listening to a target group which has no on-going group communications, the discreet listening deactivation procedure is used as defined in subclause 6.6.1.3.1. + +When the authorized user decides to stop discreet listening to a target group which has on-going group communications, the procedure as shown in figure 6.6.1.3.3-1 is used. The group communication is unaffected by the release of discreet listening media to the authorized user. + +![Sequence diagram for Figure 6.6.1.3.3-1: Release discreet listening to group during on-going communication.](f6e8acf9f931452d01688d311b5c0364_img.jpg) + +``` + +sequenceDiagram + participant MCPTT server + participant MCPTT client 3 (authorized user) + + Note left of MCPTT server: 0. Media plane established + Note right of MCPTT client 3: 1. Discreet listening group deactivation request + MCPTT client 3->>MCPTT server: 1. Discreet listening group deactivation request + Note right of MCPTT server: 2. Discreet listening group deactivation response + MCPTT server->>MCPTT client 3: 2. Discreet listening group deactivation response + Note right of MCPTT client 3: 3. Discreet listening group call release request + MCPTT client 3->>MCPTT server: 3. Discreet listening group call release request + Note right of MCPTT server: 4. Discreet listening group call release response + MCPTT server->>MCPTT client 3: 4. Discreet listening group call release response + Note left of MCPTT server: 5. Media plane released + +``` + +Sequence diagram for Figure 6.6.1.3.3-1: Release discreet listening to group during on-going communication. + +**Figure 6.6.1.3.3-1: Release discreet listening to group during on-going communication** + +0. Media plane for discreet listening to the target MCPTT group has been established. +- 1-2. The authorized user at MCPTT client 3 requests discreet listening group deactivation to the MCPTT server to stop the target MCPTT group. +- 3-4. MCPTT server performs discreet listening group call release with the MCPTT client 3. +5. Media plane for discreet listening to the target MCPTT group is released. + +When the group call of the target group is released, the discreet listening to the current call is also released as shown in procedure in figure 6.6.1.3.3-2 below. + +Pre-conditions: + +- The authorized user at MCPTT client 3 is discreet listening to the group call of the target MCPTT group. + +![Sequence diagram showing the release of discreet listening to a current group call. The diagram involves two lifelines: MCPTT server and MCPTT client 3 (authorized user). The sequence of messages is: 0. Release group call (from server to client), 1. Discreet listening group call release request (from server to client), 2. Discreet listening group call release response (from client to server), and 3. Media plane released (from server to client).](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg) + +``` + +sequenceDiagram + participant MCPTT server + participant MCPTT client 3 (authorized user) + Note left of MCPTT server: 0. Release group call + MCPTT server->>MCPTT client 3: 1. Discreet listening group call release request + MCPTT client 3-->>MCPTT server: 2. Discreet listening group call release response + Note right of MCPTT server: 3. Media plane released + +``` + +Sequence diagram showing the release of discreet listening to a current group call. The diagram involves two lifelines: MCPTT server and MCPTT client 3 (authorized user). The sequence of messages is: 0. Release group call (from server to client), 1. Discreet listening group call release request (from server to client), 2. Discreet listening group call release response (from client to server), and 3. Media plane released (from server to client). + +**Figure 6.6.1.3.3-2: Release discreet listening to current group call at group call release** + +0. The group call of the target MCPTT group is released. +- 1-2. MCPTT server performs discreet listening group call release with the MCPTT client 3. +3. Media plane for discreet listening to the target MCPTT group is released. + +#### 6.6.1.4 Information flows + +The information flows in support of procedures for discreet listening to groups are defined as below. + +**Table 6.6.1.4-1: Discreet listening group activation request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------| +| MCPTT group ID | M | MCPTT group ID of the target group for discreet listening | + +**Table 6.6.1.4-2: Discreet listening group activation response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------| +| MCPTT group ID | M | MCPTT group ID of the target group for discreet listening | +| Result | M | Indicates the success or failure of the discreet listening group activation request | + +**Table 6.6.1.4-3: Discreet listening group deactivation request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------| +| MCPTT group ID | M | MCPTT group ID of the target group to be deactivated for discreet listening | + +**Table 6.6.1.4-4: Discreet listening group deactivation response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------------------| +| MCPTT group ID | M | MCPTT group ID of the target group to be deactivated for discreet listening | +| Result | M | Indicates the success or failure of the discreet listening group deactivation request | + +**Table 6.6.1.4-5: Discreet listening group call request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------| +| MCPTT ID | M | MCPTT ID of the authorized user provisioned with discreet listening (the listener) | +| MCPTT group ID | M | MCPTT group ID of the target group for discreet listening | +| SDP offer | M | Media parameters of MCPTT clients | + +**Table 6.6.1.4-6: Discreet listening group call response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------| +| MCPTT ID | M | MCPTT ID of the authorized user provisioned with discreet listening (the listener) | +| MCPTT group ID | M | MCPTT group ID of the target group for discreet listening | +| Result | M | Indicates the success or failure of the discreet listening group call request | + +**Table 6.6.1.4-7: Discreet listening group call release request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------| +| MCPTT ID | M | MCPTT ID of the authorized user provisioned with discreet listening (the listener) | +| MCPTT group ID | M | MCPTT group ID of the target group for discreet listening | + +**Table 6.6.1.4-8: Discreet listening group call release response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------| +| MCPTT ID | M | MCPTT ID of the authorized user provisioned with discreet listening (the listener) | +| MCPTT group ID | M | MCPTT group ID of the target group for discreet listening | + +### 6.6.2 Impacts on existing nodes and functionality + +This solution results in the following impacts on existing entities and reference points: + +- MCPTT servers and MCPTT clients (of authorized users): addition of functionality for activation and deactivation of discreet listening to a specified target MCPTT group; addition of functionality for provision of discreet listening towards a group call to the authorized user without incorporate this authorized user into the group membership. +- MCPTT user configuration (of authorized user): authorization of invoking discreet listening to a target group and the list of target groups. +- MCPTT group configuration: authorization for being discreet listened in group communications of this group. +- MCPTT-1 reference points: addition of new messages in support of new procedures for discreet listening. +- New procedures to request discreet listening specifying a target MCPTT group and provision of discreet listening to the specified target group. + +**Editor's note:** Solutions are FFS for some regrouping scenarios when transmissions from users or groups that are not targets of discreet listening need to be filtered. + +### 6.6.3 Solution Evaluation + +This solution supports discreet listening of a target group by using similar mechanisms of discreet listening of a target user defined in Solution 1. This solution has no impact to the existing function models. + +## 6.7 Solution 7: Logging of MCData message store and MCData content server + +### 6.7.1 Description + +#### 6.7.1.1 Overview + +This solution addresses key issue 11: logging of MCData content server and message store services. + +#### 6.7.1.2 Logging of MCData message store services + +A message store provides a private storage facility for an MCData user, where data that has been transmitted or received can be cached for later retrieval, where a message can be saved prior to sending and where data exchanged in a group while the MCData user was not receiving MCData service can be stored in order to provide lossless communications. + +As any MCData transactions sent or received can be provided to the MC logging function when transferred, it is not necessary to provide additional logging exchanges between the message store and the MC logging function. However, if logging of MCData content stored in the MCData message store is required, this can be provided as an integral function of the MCData message store, and is therefore out of scope of the present document. + +#### 6.7.1.3 Logging of MCData content server transactions + +A file distribution transaction involving an MCData content server allows an MCData user to upload a file to an MCData content server, then initiate file transfer to an MCData user or group by sending the URL of the file to the target user or group, and allowing the user or group members to retrieve the file by downloading from the MCData content server. In this solution, the initial file upload is not sent to the MC logging function, but transactions between MCData users to transfer the file are stored in the MC logging function, and the MC logging function can also optionally retrieve the file being exchanged. + +NOTE 1: If logging of the file is required when uploaded and before distribution to target users and groups, this can be provided by an integral function of the MCData content server. Such functionality is outside the scope of this solution. + +Figure 6.7.1.3-1 illustrates the procedure to log file transfer where an MCData content server is in use. + +![Sequence diagram showing the logging of MCData file distribution using MCData content server. Lifelines: MCData client 1, MCData content server, MCData server FD function, MCData target, and MC logging function. The sequence includes steps: 1. initiate data request, 2. MCData FD request, 3. Authorize request, 4. MCData FD request, 5. MCData FD logging request, 6. MCData FD response, 7. MCData FD logging response, 8. File download, 9. File download, 10. MCData download completed report, 11. MCData download completed logging report.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData content server + participant MCData server FD function + participant MCData target + participant MC logging function + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server FD function: 2. MCData FD request + Note right of MCData server FD function: 3. Authorize request + MCData server FD function->>MCData target: 4. MCData FD request + MCData server FD function->>MC logging function: 5. MCData FD logging request + MCData target->>MCData server FD function: 6. MCData FD response + MCData server FD function->>MC logging function: 7. MCData FD logging response + Note right of MCData content server: 8. File download + MCData content server->>MCData target: 8. File download + Note right of MCData content server: 9. File download + MCData content server-->>MC logging function: 9. File download + MCData target->>MCData server FD function: 10. MCData download completed report + MCData server FD function->>MC logging function: 11. MCData download completed logging report + +``` + +Sequence diagram showing the logging of MCData file distribution using MCData content server. Lifelines: MCData client 1, MCData content server, MCData server FD function, MCData target, and MC logging function. The sequence includes steps: 1. initiate data request, 2. MCData FD request, 3. Authorize request, 4. MCData FD request, 5. MCData FD logging request, 6. MCData FD response, 7. MCData FD logging response, 8. File download, 9. File download, 10. MCData download completed report, 11. MCData download completed logging report. + +**Figure 6.7.1.3-1: Logging of MCData file distribution using MCData content server** + +In figure 6.7.1.3-1, + +- Steps 1, 2, 3, 4, 6, 8 and 11 follow those for file distribution to a single target MCData user or to a target MCData group, as defined in 3GPP TS 22.282 [5]. +- Step 5 alerts the MC logging function to the data transfer following the transmission of the file distribution request to the target users, +- Step 7 informs the MC logging function of the target MCData user or group's response. If the target of the FD operation is a group, a single report message may indicate the responses from multiple group members, and multiple messages may be sent containing the responses from different group members. + +NOTE 2: Step 7 may occur before or after steps 6 and/or 8. It is not expected that step 6 or step 8 will be delayed in case of non-receipt of step 7 by the MCData content server, however an implementation may decide to hold or prevent steps 6 and/or 8 taking place in event of delay or non-receipt of step 7 if system policy requires all transactions to be logged, and the requirement for logging overrules the requirement to provide the target MCData users with the file contents. + +- The MC logging function may decide (according to configuration) to download and log the content of the file in step 9. Step 9 may also be delayed until after step 11 in which the MC logging function is informed of the download completed report, so that the MC logging function may choose not to download the file unless at least one target user has successfully downloaded the file. Alternatively, the MC logging function may be configured to only log the fact that the file transfer has taken place, and not the file itself, in which case step 9 is omitted. +- Step 11 informs the MC logging equipment of the download complete report(s) of the target user(s) if these are sent. As in step 7, if the target of the FD operation is a group, a single report message may indicate the responses from multiple group members, and multiple messages may be sent containing the responses from different group members. + +### 6.7.2 Impacts on existing nodes and functionality + +The MCData server needs to send additional messages to the MC logging equipment when MCData file distribution takes place so that the logging recorder can log requests, responses and reports relating to file distribution transactions. + +The MCData content server needs to be able to receive requests for file content from the MC logging equipment, in addition to those from the targets of the file distribution transaction. + +### 6.7.3 Solution Evaluation + +This solution places logging of content stored in an MCData message store out of scope. + +This solution provides a solution for logging of MCData file distribution where an MCData content server is in use. Additional functionality is required for the MCData server to inform the MC logging function of file distribution transactions; however this is similar to functionality required between an MCData server and an MCData client for file distribution. + +## 6.8 Solution 8: Discreet listening of MCData message store and MCData content server + +### 6.8.1 Description + +#### 6.8.1.1 Overview + +This solution addresses key issue 12: discreet listening of MCData content server and message store services. + +#### 6.8.1.2 Discreet listening of MCData message store services + +A message store provides a private storage facility for an MCData user, where data that has been transmitted or received can be cached for later retrieval, where a message can be saved prior to sending and where data exchanged in a group while the MCData user was not receiving MCData service can be stored in order to provide lossless communications. + +As any MCData transactions sent or received can be provided to the authorized user performing discreet listening when transferred, it is not necessary to provide discreet listening of exchanges between the message store and the MC logging function. However, if discreet listening of MCData content being uploaded to, downloaded from or stored in the MCData message store is required, this can be provided as an integral function of the MCData message store, and is therefore out of scope of the present document. + +#### 6.8.1.3 Discreet listening of MCData content server transactions + +A file distribution transaction involving an MCData content server allows an MCData user to upload a file to an MCData content server, then initiate file transfer to an MCData user or group by sending the URL of the file to the target user or group, and allowing the user or group members to retrieve the file by downloading from the MCData content server. In this solution, the initial file upload is not notified or sent to the authorized user performing discreet listening, but transactions between MCData users to transfer the file are sent to the authorized user, and the authorized user can also optionally retrieve the file being exchanged. + +NOTE 1: If discreet listening of the file is required when uploaded and before distribution to target users and groups, this can be provided by an integral function of the MCData content server. Such functionality is outside the scope of this solution. + +Figure 6.8.1.3-1 illustrates the procedure for discreet listening where an MCData content server is in use. In this procedure, at least one of the sourcing MCData client 1 or the target MCData users or groups are the target for the discreet listening service. The authorized user is making use of MCData client 2 to perform the discreet listening service. + +![Sequence diagram illustrating Discreet listening of MCData file distribution using MCData content server. The diagram shows interactions between MCData client 1, MCData content server, MCData server FD function, MCData target, and MCData client 2 (Authorized user).](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData content server + participant MCData server FD function + participant MCData target + participant MCData client 2 (Authorized user) + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server FD function: 2. MCData FD request + Note right of MCData server FD function: 3. Authorize request + MCData server FD function->>MCData target: 4. MCData FD request + MCData server FD function->>MCData client 2: 5. MCData FD discreet listening request + MCData client 2-->>MCData server FD function: 6. MCData FD discreet listening response + MCData server FD function-->>MCData target: 7. MCData FD response + MCData server FD function->>MCData client 2: 8. MCData FD response discreet listening request + MCData client 2-->>MCData server FD function: 9. MCData FD response discreet listening response + MCData content server->>MCData target: 10. File download + Note right of MCData target: 11. File download + MCData target-->>MCData content server: 12. MCData download completed report + MCData server FD function->>MCData client 2: 13. MCData download completed discreet listening report + MCData client 2-->>MCData server FD function: 14. MCData download completed discreet listening response + +``` + +Sequence diagram illustrating Discreet listening of MCData file distribution using MCData content server. The diagram shows interactions between MCData client 1, MCData content server, MCData server FD function, MCData target, and MCData client 2 (Authorized user). + +**Figure 6.8.1.3-1: Discreet listening of MCData file distribution using MCData content server** + +In figure 6.8.1.3-1, + +- Steps 1, 2, 3, 4, 7, 10 and 12 follow those for file distribution to a single target MCData user or to a target MCData group, as defined in 3GPP TS 22.282 [5]. +- Step 5 alerts the authorized user at MCData client 2 to the request for data transfer sent to the target users, and step 6 contains the response from MCData client 2 informing the MCData server that MCData client 2 received the MCData FD discreet listening request. + +NOTE 2: Step 6 may occur before or after step 7. However, the MCData server should not cause the file download in step 10 to be delayed or impeded if step 7 is not received by the MCData server, to prevent the discreet listening service from causing any perceived change to the MCData FD service to the users taking part in the FD service. + +- Step 8 informs the authorized user at MCData client 2 of the target MCData user or group's response and step 9 contains the response from MCData client 2 confirming receipt of the target user or group's response by MCData client 2. If the target of the FD transfer is a group, a single message may contain the responses of multiple users, and multiple messages may be sent indicating the responses of multiple group members. +- The authorized user may choose to download the specified file contents in step 11. + +NOTE 3: The file needs to be stored in the MCData content server long enough to enable the authorized user to retrieve the file. + +- Step 13 informs the authorized user at MCData client 2 of the download complete report(s) of the target user(s) if these are sent, and step 14 confirms receipt of this to the MCData server. As for step 8, a single discreet listening report sent to MCData client 2 in step 13 may contain reports from multiple target MCData group members, and multiple messages may be sent in step 13. + +NOTE 4: Steps 6, 9 and 14 may utilise an automatic process, such that a human user does not need to make a decision at the time that the file download commences. + +### 6.8.2 Impacts on existing nodes and functionality + +The MCData server needs to send additional messages to the MCData client of the authorized user relating to file distribution transactions. + +The MCData content server needs to be able to and authorized to receive requests for file content from the MCData client of the authorized user, in addition to those from the targets of the file distribution transaction. Such download of content is not visible to the originator of the content, or the target recipients of the content. + +Additional configuration will be needed to achieve this functionality. + +### 6.8.3 Solution Evaluation + +This solution places discreet listening of content stored in an MCData message store out of scope. + +This solution provides a solution for discreet listening of MCData file distribution where an MCData content server is in use. Additional functionality is required for the MCData server to inform the MCData client of the authorized user of file distribution transactions; however this is similar to functionality required between an MCData server and an MCData client for file distribution. + +## 6.9 Solution 9: Functionality for discreet listening with regulatory constraints and operator security policies + +### 6.9.1 Description + +#### 6.9.1.1 Functional model + +Discreet listening is carried out by an authorized user, who requests discreet listening for the communications of another user or several users. There is no differentiation to the type of communication, e.g. individual or group communications. The authorized user will require a client entity capable of fulfilling the discreet listening request. The functionality required is the same as that of an MC service client, with the addition of the capability to request discreet listening and specify an MC service user or several MC service users as target. In contrast to discreet listening with no constraints, discreet listening with regulatory constraints and operator security policies is only applied to an MC service user or several MC service users, which are identified as target MC service user(s). The communications of other MC service users which are not defined as targets are not available to the requested authorized MC service user. + +This solution addresses aspects of key issue 14, Limitations on discreet listening due to regulatory constraints and operator security policies. + +#### 6.9.1.2 Configuration + +The user profiles for MCPTT, MCVideo and MCData which are specified in 3GPP TS 23.379 [7], 3GPP TS 23.281 [8] and 3GPP TS 23.282 [9] will need additional configuration to be added as shown in Table 6.9.1.2-1 below. + +**Table 6.9.1.2-1: Addition to MC service user profiles (on network)** + +| Reference | Parameter description | MC service UE | MC service Server | Configuration management server | MC service user database | +|--------------------------------------|---------------------------------------------------------------------|---------------|-------------------|---------------------------------|--------------------------| +| | Authorized to perform discreet listening on another MC service user | Y | Y | Y | Y | +| [R-6.15.1-003] of 3GPP TS 22.280 [2] | List of users upon whom discreet listening can be invoked | | | | | +| | > MC service ID (see NOTE 1) | Y | Y | Y | Y | +| | > Limited communication (see NOTE 2) | Y | Y | Y | Y | + +NOTE 1: Due to regulatory constraints and operator security policies only MC service IDs are provided, which are identified as targets. +NOTE 2: If applicable, only the originating transmissions of the target MC service ID is available. Otherwise communications from and to the target will be part of discreet listening. + +In Table 6.9.1.2-1 'MC service' represents one of MCPTT, MCVideo or MCData. + +#### 6.9.1.3 Procedures + +##### 6.9.1.3.1 General + +New procedures are added to allow the MC service client of the authorized user to invoke and revoke discreet listening of an MC service user or several MC service users identified as target(s), and to allow the MC service server to provide the content of communications in which the target MC service users are involved. Communications of a MC service user or several MC service users not identified as targets are not available to the requested authorized MC service user. + +##### 6.9.1.3.2 Discreet listening invocation and revocation procedures + +The procedure allows the MC service client of the authorized user to request discreet listening of a target MC service user. The procedure is illustrated in Figure 6.9.1.3.2-1 below. + +![Sequence diagram showing the discreet listening invocation procedure. It consists of two boxes: 'MC service client' on the left and 'MC service server' on the right. A solid arrow labeled '1. Discreet listening activation request' points from the client to the server. A dashed arrow labeled '2. Discreet listening activation response' points from the server back to the client.](2834bdd6eb8540277e609decbb924003_img.jpg) + +``` + +sequenceDiagram + participant Client as MC service client + participant Server as MC service server + Note left of Client: + Client->>Server: 1. Discreet listening activation request + Note right of Server: + Server-->>Client: 2. Discreet listening activation response + +``` + +Sequence diagram showing the discreet listening invocation procedure. It consists of two boxes: 'MC service client' on the left and 'MC service server' on the right. A solid arrow labeled '1. Discreet listening activation request' points from the client to the server. A dashed arrow labeled '2. Discreet listening activation response' points from the server back to the client. + +**Figure 6.9.1.3.2-1: Discreet listening invocation** + +The information flows needed to support such a procedure are shown in tables 6.9.1.3.2-1 and 6.9.1.3.2-2 below. + +**Table 6.9.1.3.2-1: Discreet listening activation request** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------| +| MC service ID (NOTE) | M | MC service ID of the target of the discreet listening request | +| NOTE: Due to regulatory constraints and operator security policies only a MC service ID is provided, which is identified as target. | | | + +**Table 6.9.1.3.2-2: Discreet listening activation response** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------|--------|--------------------------------------------------------------------| +| MC service ID (NOTE) | M | MC service ID of the target of the discreet listening request | +| Result | M | Indicates the success or failure of the discreet listening request | +| NOTE: Due to regulatory constraints and operator security policies only a MC service ID is provided, which is identified as target. | | | + +A similar procedure, not illustrated here, is required for revocation of the discreet listening function. + +##### 6.9.1.3.3 Provision of discreet listening content for private communications + +When the target user makes or receives a private call or initiates individual communications with a server, the authorized user needs to be informed and provided with the media. Figure 6.9.1.3.3-1 below illustrates a procedure where discreet listening target MC service client 1 sets up a call. + +![Sequence diagram illustrating the discreet listening of a target initiated private call. The diagram shows four participants: MC service client 1 (target), MC service server, MC service client 2 (called party), and MC service client 3 (authorized user). The sequence of messages is: 1. Private call request from client 1 to server; 2. Private call request from server to client 2; 3. Discreet listening call request from server to client 3; 4. Private call response from client 2 to server; 5. Discreet listening call response from server to client 3; 6. Private call response from server to client 1; 7. Media plane established (a horizontal bar spanning all participants); 8a. Media transmission from client 1 to server; 8b. Media transmission from server to client 2; 8c. Media transmission from server to client 3; 9a. Media transmission from client 2 to server; 9b. Media transmission from server to client 1.](6f31cdb576d2f15c35c3f266e5f59211_img.jpg) + +Sequence diagram illustrating the discreet listening of a target initiated private call. The diagram shows four participants: MC service client 1 (target), MC service server, MC service client 2 (called party), and MC service client 3 (authorized user). The sequence of messages is: 1. Private call request from client 1 to server; 2. Private call request from server to client 2; 3. Discreet listening call request from server to client 3; 4. Private call response from client 2 to server; 5. Discreet listening call response from server to client 3; 6. Private call response from server to client 1; 7. Media plane established (a horizontal bar spanning all participants); 8a. Media transmission from client 1 to server; 8b. Media transmission from server to client 2; 8c. Media transmission from server to client 3; 9a. Media transmission from client 2 to server; 9b. Media transmission from server to client 1. + +**Figure 6.9.1.3.3-1: Discreet listening of target initiated private call** + +Steps 1 to 7 follow those in solution 1, subclause 6.1.1.3.3. + +When the target MC service client 1 sends media (step 8a) to the called party MC service client 2 (step 8b), the media is also sent to the authorized user MC service client 3 (step 8c) by the MC service server, + +However, when the called party MC service client 2, who is outside the scope of the constrained discreet listening service, sends media (step 9a) to the target MC service client 1 (step 9b), media is not forwarded to the authorized user MC service client 3. + +The procedure is similar if the target of the discreet listening is the recipient of the private call. + +NOTE 1: If the MC service server does not receive the 'discreet listening call response' for any reason, the call should still proceed so that the requirement that the call is not affected and the target user is not aware of the discreet listening process is satisfied. + +NOTE 2: Under certain circumstances, the authorized user may also receive communications of the other party in the communication, e.g. due to imperfect echo cancellation in calls without floor control. + +##### 6.9.1.3.4 Provision of discreet listening content for group communications + +When the target user makes or receives a group call, the authorized user needs to be informed and provided with the media. Figure 6.9.1.3.4-1 below illustrates a procedure where discreet listening target MC service client 2 is a receiving party in a group call initiated by another affiliated group member. + +![Sequence diagram illustrating the provision of discreet listening content for a group call. The diagram shows interactions between MC service client 1 (call initiator), MC service server, MC service client 2 (target), and MC service client 3 (authorized user). The process involves group call requests, discreet listening call requests, and media plane establishment.](171115f072e42b379238ed0dd438e9d7_img.jpg) + +``` + +sequenceDiagram + participant MC service client 1 (call initiator) + participant MC service server + participant MC service client 2 (target) + participant MC service client 3 (authorized user) + + MC service client 1->>MC service server: 1. Group call request + MC service server->>MC service client 2: 2. Group call request + MC service server->>MC service client 3: 3. Discreet listening call request + MC service client 2->>MC service server: 4. Group call response + MC service client 3->>MC service server: 5. Discreet listening call response + MC service server->>MC service client 1: 6. Group call response + Note over all participants: 7. Media plane established + Note over MC service client 1, MC service server: 8a. Media transmission + Note over MC service server, MC service client 2: 8b. Media transmission + Note over MC service client 1, MC service server: 9b. Media transmission + Note over MC service server, MC service client 2: 9a. Media transmission + Note over MC service server, MC service client 3: 9c. Media transmission + +``` + +Sequence diagram illustrating the provision of discreet listening content for a group call. The diagram shows interactions between MC service client 1 (call initiator), MC service server, MC service client 2 (target), and MC service client 3 (authorized user). The process involves group call requests, discreet listening call requests, and media plane establishment. + +**Figure 6.9.1.3.4-1: Discreet listening of target initiated group call** + +The procedure is similar if the target of the discreet listening is the initiator of the group call. + +NOTE 1: If the MC service server does not receive the 'discreet listening call response' for any reason, the call should still proceed so that the requirement that the call is not affected and the target user is not aware of the discreet listening process is satisfied. + +NOTE 2: It is irrelevant whether the authorized user is or is not a member of the MC service group. + +##### 6.9.1.3.5 Information flows for discreet listening + +Identical to solution 1, subclause 6.1.1.3.5. + +### 6.9.2 Impacts on existing nodes and functionality + +This solution results in the following impacts on existing entities and reference points: + +- Similar impacts as described in solution 1, subclause 6.1.3. + +In each case, MC service is one of MCPTT, MCVideo or MCData. + +### 6.9.3 Solution Evaluation + +This solution allows discreet listening with regulatory constraints and applied operator security policies to be achieved with minimal changes to the functional model as it only requires enhancement to existing functional entities and reference points. It also allows discreet listening to be invoked on a service dependent basis as it is achieved as a function of the MC service specific MC service clients. + +## 6.10 Solution 10: Functionality for on-network logging and replay + +### 6.10.1 Description + +#### 6.10.1.1 Functional model + +To support on-network logging and replay, existing common service core functional entities are reused. + +The MC logging function makes use of a new MC logging client which has a subset of the functionality of an existing MC service client, in that it can receive communications information and communications content relating to logged users, but cannot set up calls or demand to take part in calls. Provision of call related information and call content is achieved by configuration in the MC service server. The MC logging client uses an MC service ID to allow call related information and call content to be routed to the MC logging client, reusing functionality from existing reference points. + +NOTE 1: An MC logging function may contain multiple MC service clients to allow the separate services MCPTT, MCVideo and MCData to be logged within the same function. However this is out of scope of the description of the functional model. + +Figure 6.10.1.1-1 below illustrates the functional entities and reference points of the common services core in the application plane that are used for logging. + +![Figure 6.10.1.1-1: Common services core functional model for logging. The diagram shows the functional entities and reference points of the common services core in the application plane. On the left, an MC service server is connected to a dashed box labeled 'Common services core'. Inside this box are four servers: Configuration management server, Group management server, Identity management server, and Key management server. These servers are connected to corresponding clients inside a central box labeled 'MC logging function'. The connections are labeled CSC-4, CSC-2, CSC-1, and CSC-8 respectively. The MC logging function box contains: MC logging client, Logging storage, Configuration management client, Group management client, Identity management client, and Key management client. The MC logging client is connected to an 'MC replay equipment' box on the right via interface MCLog-11. The Logging storage is connected to the MC replay client inside the MC replay equipment box via interface MCLog-10. A line labeled CSC-9 connects the MC service server to the CSC-4 interface.](dd380ccd5aca1151074fede04826f1a4_img.jpg) + +Figure 6.10.1.1-1: Common services core functional model for logging. The diagram shows the functional entities and reference points of the common services core in the application plane. On the left, an MC service server is connected to a dashed box labeled 'Common services core'. Inside this box are four servers: Configuration management server, Group management server, Identity management server, and Key management server. These servers are connected to corresponding clients inside a central box labeled 'MC logging function'. The connections are labeled CSC-4, CSC-2, CSC-1, and CSC-8 respectively. The MC logging function box contains: MC logging client, Logging storage, Configuration management client, Group management client, Identity management client, and Key management client. The MC logging client is connected to an 'MC replay equipment' box on the right via interface MCLog-11. The Logging storage is connected to the MC replay client inside the MC replay equipment box via interface MCLog-10. A line labeled CSC-9 connects the MC service server to the CSC-4 interface. + +**Figure 6.10.1.1-1: Common services core functional model for logging** + +The difference to solution#3 is listed as below: + +1. The MC replay function receives the necessary security information (e.g., keys used to decrypt the signalling information and media if the solution is intended to log communications with any end to end encryption removed) needed to replay logged communications via MCLog-11 from MC Logging function. A user of the replay function, or an automatic function of the replay function, will perform the necessary authorizations to retrieve logged communications, and MCLog-11 will be used to verify the authenticity and authorization of the user or function. +2. The interface MCLog-10 is used for the MC replay client to access logged communications from logging storage in MC logging function. + +3. MCLog-10 and MCLog-11 do not need to use 3GPP access for connectivity, and are outside the scope of this solution. + +Figure 6.10.1.1-2 below shows the MC service related application plane entities used to log communications. + +![Figure 6.10.1.1-2: MC service related application plane functional model for logging. The diagram shows two main functional blocks. The left block is the 'MC service server', which contains two sub-functions: 'Media distribution function' and 'Media control server'. The right block is the 'MC logging function', which contains an 'MC logging client' and two sub-functions: 'Media reception' and 'Media participant'. Three interfaces connect the left block to the right block: 'MCLog-2' connects the 'Media distribution function' to 'Media reception'; 'MCLog-1' connects the 'Media distribution function' to 'Media participant'; and 'MCLog-3' connects the 'Media control server' to 'Media participant'.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +Figure 6.10.1.1-2: MC service related application plane functional model for logging. The diagram shows two main functional blocks. The left block is the 'MC service server', which contains two sub-functions: 'Media distribution function' and 'Media control server'. The right block is the 'MC logging function', which contains an 'MC logging client' and two sub-functions: 'Media reception' and 'Media participant'. Three interfaces connect the left block to the right block: 'MCLog-2' connects the 'Media distribution function' to 'Media reception'; 'MCLog-1' connects the 'Media distribution function' to 'Media participant'; and 'MCLog-3' connects the 'Media control server' to 'Media participant'. + +**Figure 6.10.1.1-2: MC service related application plane functional model for logging** + +The description MC service related application plane functional model for logging is the same as described in solution#3. + +#### 6.10.1.2 Configuration + +The configuration aspect is the same as described in solution#3. + +#### 6.10.1.3 Procedures + +The procedures to enable MC logging function is the same as described in solution#3. + +The MC replay equipment and the interfaces MCLog-10, MCLog-11 are outside scope of this solution. + +### 6.10.2 Impacts on existing nodes and functionality + +New entities are introduced in this solution, specifically the MC logging equipment and its constituent MC logging client together with MC logging storage and the MC replay equipment containing the MC replay client. The new MC logging client is based on existing MC service clients to maximise reuse of existing functionality and reference points. + +The process for authentication and service authorization use existing functional entities, reference points and procedures. + +New configuration will be introduced to configure logging equipment, and to configure MC service groups with the list of MC logging equipment that will log MC service group communications. + +New procedures for logging call related information and call contents will be required. However these can be based on existing procedures for call setup and floor, transmission and media control within calls. + +Interactions between MC logging client, logging storage and the MC replay client are not specified within this solution and so have no impact on existing nodes and functionality. + +### 6.10.3 Solution Evaluation + +This solution defines new functional entities and reference points to fulfil the on-network logging requirement together with reuse of existing common services core functional entities and reference points. The new functional entities and reference points will be based on the functionality of existing MC service clients and associated reference points. + +The interaction between the MC replay client and the MC logging function is outside the scope of the present document. + +A set of procedures will need to be defined to show the invocation of logging functions on logged calls. + +# 7 Overall Evaluation + +## 7.1 General + +The following subclauses contain an overall evaluation of the solutions presented in this technical report, and their applicability to the key issues raised. Subclause 7.2 provides an evaluation of the solutions provided in clause 6, and their impact on other entities and working groups, and shows the mapping of the solutions to the key issues outlined in clause 5. Subclause 7.3 lists the key issues with security implications that will need consideration in 3GPP SA WG3. + +## 7.2 Solution evaluation + +Table 7.2-1 below shows the mapping of key issues to solutions. + +**Table 7.2-1: Mapping of key issues to solutions** + +| Key issue | Solution | +|----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1: Selection of MC service for discreet listening | Solution #1: Functionality for discreet listening | +| 2: Group membership of authorized MC user for discreet listening | Solution #1: Functionality for discreet listening | +| 3: Discreet listening for MCVideo push and pull and MCData file upload and download | Solution #2: Discreet listening of MCVideo push and pull | +| 4: Discreet listening of end to end encrypted calls | Out of scope (see note) | +| 5: Logging and replay of end to end encrypted calls | Out of scope (see note) | +| 6: Source MC service server for discreet listening of user in group call | Solution #1: Functionality for discreet listening | +| 7: Discreet listening and logging for interconnected MC system | Solution #4: On-network logging for interconnection and migration<br>Solution #5: Discreet listening for interconnection and migration | +| 8: Discreet listening and logging for migrated MC service user | Solution #4: On-network logging for interconnection and migration<br>Solution #5: Discreet listening for interconnection and migration | +| 9: Discreet listening and logging for user receiving MC service on multiple devices | Solution #1: Functionality for discreet listening<br>Solution #2: Discreet listening of MCVideo push and pull<br>Solution #3: Functionality for on-network logging and replay | +| 10: Logging of MC service users and MC service groups | Solution #3: Functionality for on-network logging and replay<br>Solution #10: Functionality for on-network logging and replay | +| 11: Logging of MCData content server and message store services | Solution #7: Logging of MCData message store and MCData content server | +| 12: Discreet listening of MCData content server and message store services | Solution #8: Discreet listening of MCData message store and MCData content server | +| 13: Discreet listening towards an MC service group | Solution #6: Discreet listening to an MCPTT group | +| 14: Limitations on discreet listening due to regulatory constraints and operator security policies | Solution #9: Functionality for discreet listening with regulatory constraints and operator security policies | +| NOTE: | Security solutions are within the remit of SA3 | + +The solutions specified in this technical report are described in table 7.2-2, together with the evaluation text for each solution. + +**Table 7.2-2: Solution evaluations** + +| Solution | Applicable key issues | Evaluation | Impact on other entities and working groups | +|------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| +| Solution 1: Functionality for discreet listening | 1: Selection of MC service for discreet listening<br>2: Group membership of authorized MC user for discreet listening<br>6: Source MC service server for discreet listening of user in group call<br>9: Discreet listening and logging for user receiving MC service on multiple devices | This solution allows discreet listening to be achieved with minimal changes to the functional model as it only requires enhancement to existing functional entities and reference points. It also allows discreet listening to be invoked on a service dependent basis as it is achieved as a function of the MC service specific MC service clients. It supports the situations where the MC service user is receiving MC service on multiple MC service clients. | Minor impact on downstream groups to add functionality to existing functional entities and reference points. | +| Solution 2: Discreet listening of MCVideo push and pull | 3: Discreet listening for MCVideo push and pull and MCData file upload and download<br>9: Discreet listening and logging for user receiving MC service on multiple devices | This solution allows discreet listening of MCVideo push and pull transactions to be achieved with minimal changes to existing MCVideo functionality, as the provision of discreet listening is based on existing MCVideo push and pull procedures. The solution includes a means of identifying the MCVideo client where an MCVideo user is receiving MCVideo service from multiple MCVideo clients. Additional configuration parameters are likely to be needed to support the service. | Minor impact on downstream groups to add functionality to existing functional entities and reference points. | +| Solution 3: Functionality for logging and replay | 10: Logging of MC service users and MC service groups<br>9: Discreet listening and logging for user receiving MC service on multiple devices | This solution defines new functional entities and reference points to fulfil the on-network logging requirement together with reuse of existing common services core functional entities and reference points. The new functional entities and reference points will be based on the functionality of existing MC service clients and associated reference points. The solution includes a means of identifying the MC service client where an MC service user is receiving MC service from multiple MC service clients. A set of procedures will need to be defined to show the invocation of logging functions on logged calls. | Impact on downstream groups to add new functionality, based on existing call related functionality. | +| Solution 4: On-network logging for interconnection and migration | 7: Discreet listening and logging for interconnected MC system<br>8: Discreet listening and logging for migrated MC service user | This solution expands the solution defined in solution 3 to allow logging where the logging equipment is providing logging services in a different MC system to that of the MC logging equipment. Three options are provided to provide configuration to a partner MC system to enable logging of individual communications. Of these, option 1 which adds the MC service ID associated with the MC logging equipment to the user profile is preferred as it does not add further configuration tables to be exchanged between primary and partner MC systems to enable interconnection and migration, and does not require any analysis in the partner MC system to determine which MC service servers need to be provided with the information. | Impact on downstream groups to add parameters to configuration tables. | + +| <b>Solution</b> | <b>Applicable key issues</b> | <b>Evaluation</b> | <b>Impact on other entities and working groups</b> | +|-------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------| +| Solution 5: Discreet listening for interconnection and migration | 7: Discreet listening and logging for interconnected MC system<br>8: Discreet listening and logging for migrated MC service user | This solution expands the solutions 1 and 2 to allow discreet listening where the target is receiving MC service from a different MC system from that of the authorized user performing discreet listening. Three configuration options are provided to enable discreet listening. Of these three options, option 1 is the most consistent with current MC system operation and requires the least additional configuration work, however options 2 and 3 may result in simpler solutions. | Impact on downstream groups to add parameters to configuration tables, or to create new configuration tables. | +| Solution 6: Discreet listening to an MCP TT group | 13: Discreet listening towards an MC service group | This solution supports discreet listening of a target group by using similar mechanisms of discreet listening of a target user defined in Solution 1. This solution has no impact to the existing function models. | Minor impact on downstream groups to add functionality to existing functional entities and reference points. | +| Solution 7: Logging of MCData message store and MCData content server | 11: Logging of MCData content server and message store services | This solution provides a solution for logging of MCData file distribution where an MCData content server is in use. Additional functionality is required for the MCData server to inform the MC logging function of file distribution transactions; however this is similar to functionality required between an MCData server and an MCData client for file distribution. | Impact on downstream groups to add new functionality, based on existing MCData server to client functionality. | +| Solution 8: Discreet listening of MCData message store and MCData content server | 12: Discreet listening of MCData content server and message store services | This solution provides a solution for discreet listening of MCData file distribution where an MCData content server is in use. Additional functionality is required for the MCData server to inform the MCData client of the authorized user of file distribution transactions; however this is similar to functionality required between an MCData server and an MCData client for file distribution. | Impact on downstream groups to add new functionality, based on existing MCData server to client functionality. | +| Solution 9: Functionality for discreet listening with regulatory constraints and operator security policies | 14: Limitations on discreet listening due to regulatory constraints and operator security policies | This solution allows discreet listening with regulatory constraints and applied operator security policies to be achieved with minimal changes to the functional model as it only requires enhancement to existing functional entities and reference points. It also allows discreet listening to be invoked on a service dependent basis as it is achieved as a function of the MC service specific MC service clients. | Impact on downstream groups to add new functionality, based on existing call related functionality. | +| Solution 10: Functionality for on-network logging and replay | 10: Logging of MC service users and MC service groups | This solution defines new functional entities and reference points to fulfil the on-network logging requirement together with reuse of existing common services core functional entities and reference points. The new functional entities and reference points will be based on the functionality of existing MC service clients and associated reference points.<br>The interaction between the MC replay client and MC logging function is outside the scope of the present document.<br>A set of procedures will need to be defined to show the invocation of logging functions on logged calls. | Impact on downstream groups to add new functionality, based on existing call related functionality. | + +## 7.3 Key issues with security implications + +The following key issues have security considerations that will need review and possible solutions by SA3: + +- Key issue 4: Discreet listening of end to end encrypted calls; and +- Key issue 5: Logging and replay of end to end encrypted calls. + +# 8 Conclusions + +This technical report presents scenarios, key issues and solutions for discreet listening and logging for MC services. + +All key issues that are addressed by one or more solutions in this Technical Report are presented in subclause 7.2, and those which have security related aspects which are considered to be outside the scope of solutions within this Technical Report are presented in subclause 7.3. + +The set of solutions described in this Technical Report are candidate solutions for normative work. These solutions provide updates to the functional models for MC services that will permit discreet listening and logging to be realised, configuration which will permit discreet listening and logging services to be achieved and describe the essentials of procedures to provide the services themselves. + +Some key issues and some solutions have security considerations. These are identified in clause 7. + +# Annex A: Reproduction of stage 1 requirements + +## A.1 Requirements for discreet listening + +Requirements listed in this subclause are reproduced from the specifications referenced within this subclause. The referenced specifications are the normative source for the requirements and have precedence over the information reproduced within this subclause. + +The requirements in 3GPP TS 22.280 [2] that apply for discreet listening are provided in table A.1-1. They are applied to all services MCPTT, MCVideo and MCData according to the reference tables in Annexes A, B and C of [2]. + +**Table A.1-1: Discreet listening requirement** + +| Requirement | Description | +|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [R-6.15.1-001a] | The MCX Service shall provide discreet listening capabilities without noticeable impact on or knowledge of the target MCX User, or the members of the target MCX Service Group, and all other unauthorized MCX Users. | +| [R-6.15.1-001] | The MCX Service shall provide a mechanism for an authorized MCX User to receive MCX Service Private Communication transmissions to and from a specific target MCX User that is within the authority of the authorized MCX user. | +| [R-6.15.1-002] | The MCX Service shall provide a mechanism for an authorized MCX User to receive MCX Service Group Communication transmissions to and from a specific target MCX User that is within the authority of the authorized MCX User. | +| [R-6.15.1-003] | Subject to regulatory constraints and operator security policies, the MCX Service shall allow to be configured not to provide transmissions from MCX Users who are communicating with the discreet listening target MCX User, and who are not themselves targets of discreet listening. | +| [R-6.15.1-004] | The MCX Service shall provide a mechanism for an authorized MCX User to receive MCX Service Group transmissions from a specific MCX Service Group that is within the authority of the authorized MCX User. | +| NOTE: | Permission to activate discreet listening can include multiple levels of authorization, but this is outside the scope of 3GPP. | + +## A.2 Requirements for recording and audit + +Requirements listed in this subclause are reproduced from the specifications referenced within this subclause. The referenced specifications are the normative source for the requirements and have precedence over the information reproduced within this subclause. + +The following requirements in 3GPP TS 22.280 [2] for recording and audit are listed in table A.2-1. They are applied to all services MCPTT, MCVideo and MCData according to the reference tables in Annexes A, B and C of [2]. + +**Table A.2-1: Requirements for recording and audit** + +| <b>Requirement</b> | <b>Description</b> | +|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [R-6.15.4-001] | The MCX Service shall provide a mechanism for a Mission Critical Organization to log the metadata of the MCX Service Group Communications and MCX Service Private Communications under the organization's authority. | +| [R-6.15.4-002] | Metadata shall be logged for both the transmitting Participant and the receiving Participant(s). | +| [R-6.15.4-003] | The MCX Service shall provide a mechanism for a Mission Critical Organization to record the transmissions of the Group Communications and Private Communications under the organization's authority. | +| [R-6.15.4-004] | The MCX Service shall provide a mechanism for a Mission Critical Organization to log at least the following metadata per communication: depending on service this may include; start time, date, MCX User ID, MCX Group ID, Location information of the transmitting Participant, end time or duration, end reason, type of communication (e.g., MCX Service Emergency, regroup, private). | +| [R-6.15.4-005] | If an MCX Service Group Communication or MCX Service Private Communication uses end-to-end confidentiality, the MCX Service shall provide a mechanism for a Mission Critical Organization to maintain the end-to-end confidentiality when the MCX Service Group Communication or MCX Service Private Communication is logged. | +| [R-6.15.4-006] | The MCX Service shall provide a mechanism for a Mission Critical Organization to log the metadata of non-communication related user activities under the agency's authority. | +| [R-6.15.4-007] | The MCX Service shall provide a mechanism for a Mission Critical Organization to log at least the following non-communication activity types: MCX Service Emergency Alert, MCX Service Emergency Alert cancellation, In-progress Emergency cancellation, registration state change, overridden event, user remote logout, changing another user's affiliations, affiliation change, and change of Selected MCX Service Group. | +| [R-6.15.4-008] | The MCX Service shall provide a mechanism for a Mission Critical Organization to log at least the following metadata per non-communication activity: time, date, MCX Service User identity, and activity type. The following metadata should be logged if applicable to the activity type: MCX Service Group ID, Location information of the MCX User, affiliation list, target MCX Service User ID and success/failure indication. | +| [R-6.15.4-009] | The MCX Service shall provide a mechanism for a Mission Critical Organization to log metadata for all failed authorization attempts (e.g., invalid login password) by an MCX User. | +| [R-6.15.4-010] | The MCX Service shall provide a mechanism to collect metadata for network access events (e.g., pre-emption of EPS bearer, loss of signal, failed registration attempts). | + +The following additional requirement for logging for MCVideo in 3GPP TS 22.281 [3] is provided in table A.2-2: + +**Table A.2-2: MCVideo specific requirement for logging** + +| <b>Requirement</b> | <b>Description</b> | +|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [R-5.1.10.2-008] | The MCVideo service shall be able to provide an integrity protected timestamped detailed log of all performed and attempted activities for each user of the MCVideo Service. | + +# --- Annex B (informative): Change history + +| Change history | | | | | | | | | +|----------------|---------|-----------|----|-----|-----|--------------------------------------------------------------------------------------------------------------|-------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 2018-05 | SA6 #24 | S6-180761 | | | | TR Skeleton | | | +| 2018-06 | SA6 #24 | S6-180913 | | | | Scope & additional references | 0.1.0 | | +| 2018-08 | SA6 #25 | S6-181202 | | | | References and Annex A | 0.2.0 | | +| 2018-08 | SA6 #25 | S6-181203 | | | | Definitions and abbreviation | 0.2.0 | | +| 2018-08 | SA6 #25 | S6-181204 | | | | Use cases/scenarios general subclause | 0.2.0 | | +| 2018-08 | SA6 #25 | S6-181261 | | | | Scenario 1: Discreet listening of MCPTT and MCVideo private calls | 0.2.0 | | +| 2018-08 | SA6 #25 | S6-181262 | | | | Scenario 2: Discreet listening of MCPTT and MCVideo group calls | 0.2.0 | | +| 2018-08 | SA6 #25 | S6-181263 | | | | Scenario 3: Discreet listening MCVideo pull | 0.2.0 | | +| 2018-08 | SA6 #25 | S6-181264 | | | | Scenario 4: Discreet listening MCVideo push | 0.2.0 | | +| 2018-08 | SA6 #25 | S6-181265 | | | | Scenario 5: Discreet listening MCData SDS | 0.2.0 | | +| 2018-08 | SA6 #25 | S6-181266 | | | | Scenario 6: Discreet listening MCData file distribution | 0.2.0 | | +| 2018-08 | SA6 #25 | S6-181211 | | | | Key issue 1: Selection of MC service for discreet listening | 0.2.0 | | +| 2018-08 | SA6 #25 | S6-181252 | | | | Key issue 2: Group membership of authorized MC user for discreet listening | 0.2.0 | | +| 2018-08 | SA6 #25 | S6-181213 | | | | Key issue 3: Discreet listening for MCVideo push and pull and MCData file upload and download | 0.2.0 | | +| 2018-10 | SA6 #26 | S6-181356 | | | | Table titles in Annex A | 0.3.0 | | +| 2018-10 | SA6 #26 | S6-181357 | | | | Scenario implemented as scenario 7: Logging scenarios as in subclause 4.8 | 0.3.0 | | +| 2018-10 | SA6 #26 | S6-181520 | | | | Key issues implemented as key issue 5.4 in subclause 5.4 and key issue 5.5 in subclause 5.5 | 0.3.0 | | +| 2018-10 | SA6 #26 | S6-181521 | | | | Key issue implemented as key issue 6 in subclause 5.6 | 0.3.0 | | +| 2018-10 | SA6 #26 | S6-181522 | | | | Key issues implemented as key issue 7 in subclause 5.7 and key issue 8 in subclause 5.8 | 0.3.0 | | +| 2018-10 | SA6 #26 | S6-181571 | | | | Implemented as solution 1 in subclause 6.1 | 0.3.0 | | +| 2018-12 | SA6 #27 | S6-181799 | | | | Replacement of 'DL' with 'discreet listening' throughout | 0.4.0 | | +| 2018-12 | SA6 #27 | S6-181843 | | | | Implemented as solution 2 in subclause 6.2 | 0.4.0 | | +| 2018-12 | SA6 #27 | S6-181803 | | | | Update to discreet listening definition | 0.4.0 | | +| 2019-01 | SA6 #28 | S6-190122 | | | | Key issue 9 on multiple devices | 0.5.0 | | +| 2019-01 | SA6 #28 | S6-190289 | | | | Overall evaluation | 0.5.0 | | +| 2019-01 | SA6 #28 | S6-190300 | | | | Solution 3 for logging | 0.5.0 | | +| 2019-03 | SA6 #29 | S6-190345 | | | | Key Issue for logging | 0.6.0 | | +| 2019-03 | SA6 #29 | S6-190468 | | | | Key Issue for logging MCData services | 0.6.0 | | +| 2019-03 | SA6 #29 | S6-190469 | | | | Key Issue for discreet listening of MCData services | 0.6.0 | | +| 2019-03 | SA6 #29 | S6-190470 | | | | Group management for logging solution 3 | 0.6.0 | | +| 2019-03 | SA6 #29 | S6-190349 | | | | Solution for interconnection & migration for logging | 0.6.0 | | +| 2019-03 | SA6 #29 | S6-190471 | | | | Solution for interconnection & migration for discreet listening | 0.6.0 | | +| 2019-03 | SA6 #29 | S6-190503 | | | | Key issue for group cased discreet listening | 0.6.0 | | +| 2019-03 | SA6 #29 | S6-190528 | | | | Solution for group based discreet listening | 0.6.0 | | +| 2019-03 | SA6 #29 | S6-190474 | | | | Update to solution evaluation | 0.6.0 | | +| 2019-03 | SA#83 | SP-190061 | | | | Presentation for Information at SA#83 | 1.0.0 | | +| 2019-04 | SA6 #30 | S6-190786 | | | | Scenario 8: Limitations on discreet listening due to regulatory constraints and operator security policies | 1.1.0 | | +| 2019-04 | SA6 #30 | S6-190787 | | | | Key Issue 14: Limitations on discreet listening due to regulatory constraints and operator security policies | 1.1.0 | | +| 2019-04 | SA6 #30 | S6-190564 | | | | Update requirements in Annex A | 1.1.0 | | +| 2019-04 | SA6 #30 | S6-190788 | | | | Solution 7: Logging of MCData message store and MCData content server | 1.1.0 | | +| 2019-04 | SA6 #30 | S6-190789 | | | | Solution 8: Discreet listening of MCData message store and MCData content server | 1.1.0 | | +| 2019-04 | SA6 #30 | S6-190790 | | | | 6.6.1.3.3 Release discreet listening to groups | 1.1.0 | | +| 2019-05 | SA6 #31 | S6-190899 | | | | Update solution 1 for multiple UEs | 1.2.0 | | +| 2019-05 | SA6 #31 | S6-190900 | | | | Update solution 2 for multiple UEs | 1.2.0 | | +| 2019-05 | SA6 #31 | S6-190901 | | | | Update solution 3 for multiple UEs | 1.2.0 | | +| 2019-05 | SA6 #31 | S6-191090 | | | | Conclusions | 1.2.0 | | +| 2019-05 | SA6 #31 | S6-191091 | | | | Solution 9: Functionality for discreet listening with regulatory constraints and operator security policies | 1.2.0 | | +| 2019-05 | SA6 #31 | S6-191201 | | | | Solution 10: Functionality for on-network logging and replay | 1.2.0 | | +| 2019-05 | SA6 #31 | S6-191089 | | | | Update overall evaluation | 1.2.0 | | +| 2019-05 | SA#84 | S6-190471 | | | | Presentation for Approval | 2.0.0 | | + +| | | | | | | | | +|---------|-------|-----------|--|--|--|--------------------------------------------------------------------|--------| +| 2019-06 | SA#84 | S6-190471 | | | | MCC Editorial update for publication after TSG SA approval (SA#84) | 16.0.0 | +|---------|-------|-----------|--|--|--|--------------------------------------------------------------------|--------| \ No newline at end of file diff --git a/marked/Rel-16/23_series/23924/0236eff05bcb8f3a343ea7933aaa306b_img.jpg b/marked/Rel-16/23_series/23924/0236eff05bcb8f3a343ea7933aaa306b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3c360a5987e13f1fa2cbf78d345898c42a16704 --- /dev/null +++ b/marked/Rel-16/23_series/23924/0236eff05bcb8f3a343ea7933aaa306b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6502e70e0a06fa68556d4543595f985c0ef13ad1472b8805006d568433870ce6 +size 28242 diff --git a/marked/Rel-16/23_series/23924/04cefd2bf9de5948b15bea2d0bdc04f4_img.jpg b/marked/Rel-16/23_series/23924/04cefd2bf9de5948b15bea2d0bdc04f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e9918799ae1d25148d8e51ce798293868eb60201 --- /dev/null +++ b/marked/Rel-16/23_series/23924/04cefd2bf9de5948b15bea2d0bdc04f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e053e0bc50b45f5d19c1ff91f75f8a3b17e25a521a3b9b085f1d30e70dbf2e32 +size 38670 diff --git a/marked/Rel-16/23_series/23924/10d81b2cc455e3563e3e562a7f451124_img.jpg b/marked/Rel-16/23_series/23924/10d81b2cc455e3563e3e562a7f451124_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..914965b207b54990a69151f0aad23fb3343390f6 --- /dev/null +++ b/marked/Rel-16/23_series/23924/10d81b2cc455e3563e3e562a7f451124_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6119550b0954e106f23a1b3ccfe90ac8f8876dedd3b70c4bdd324f7ca35ed9d6 +size 30067 diff --git a/marked/Rel-16/23_series/23924/124c6108c63173818afb8ed49521e22d_img.jpg b/marked/Rel-16/23_series/23924/124c6108c63173818afb8ed49521e22d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f11eca8ba2c311a6fd687127a345cb91170d4413 --- /dev/null +++ b/marked/Rel-16/23_series/23924/124c6108c63173818afb8ed49521e22d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1cd692a2a345890bba8e0742c9e806499b3df9daecec28e51074dbe97d77f8cf +size 59379 diff --git a/marked/Rel-16/23_series/23924/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/Rel-16/23_series/23924/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1810229f2f2ea9db5dec3d7bc5d7260a76b73001 --- /dev/null +++ b/marked/Rel-16/23_series/23924/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2876dc7b03a23f476caa99c61d95d3d061050a5894aadf1143954634ecd2306 +size 33077 diff --git a/marked/Rel-16/23_series/23924/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/marked/Rel-16/23_series/23924/19a59d6b53059ebd27b13c98793f88e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..34c63838c4616d5219bc80306995471d58d4b6bc --- /dev/null +++ b/marked/Rel-16/23_series/23924/19a59d6b53059ebd27b13c98793f88e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf252d60e9e97efaec61af0b9dce2bd6290e1aa989015ae57a9786797d85a907 +size 45003 diff --git a/marked/Rel-16/23_series/23924/19a5f0db57a21a0e82a7f326083e96fd_img.jpg b/marked/Rel-16/23_series/23924/19a5f0db57a21a0e82a7f326083e96fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52edb681a012edc72250e5986fd2d5b05e5d84ae --- /dev/null +++ b/marked/Rel-16/23_series/23924/19a5f0db57a21a0e82a7f326083e96fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd12a8715b36ea908b73f7bf759c093c97d4bd249b60c8c7751a02aa370bc81d +size 99599 diff --git a/marked/Rel-16/23_series/23924/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23924/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ab1b00ae31ec5bfdd2cdbba68709aa1a6cf6b4c --- /dev/null +++ b/marked/Rel-16/23_series/23924/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:103392610d11e4b4b3189a3606886d66b2ec6f6cff5789e22acef09cf4922771 +size 65154 diff --git a/marked/Rel-16/23_series/23924/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Rel-16/23_series/23924/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5bc9048055495c7f369b2a8cfbc10c3cfb134e61 --- /dev/null +++ b/marked/Rel-16/23_series/23924/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:378b67ae28624483493fb5fe47fe9f16f1e7362535fcf62a266bf43ae532d764 +size 72164 diff --git a/marked/Rel-16/23_series/23924/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23924/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..718def162e79c7a1b75429241e8e6ec64c38c33f --- /dev/null +++ b/marked/Rel-16/23_series/23924/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18e58cf8eddd05d080ec04bae688e20c22dc2313bdf5a6e5afbd1bd94156f0fe +size 35963 diff --git a/marked/Rel-16/23_series/23924/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/Rel-16/23_series/23924/367926125450c2bc3f4bdca9d59a62ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7df0ba998c2c0f1f0b483a7fd42c886fbc56361 --- /dev/null +++ b/marked/Rel-16/23_series/23924/367926125450c2bc3f4bdca9d59a62ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:91f81cfbea419e246a7677a1d47d4a361c6a94e24ebc1204d37b5765d0b9617c +size 37994 diff --git a/marked/Rel-16/23_series/23924/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/marked/Rel-16/23_series/23924/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b03bc6a115857ee130850c77526d9cf697f41faa --- /dev/null +++ b/marked/Rel-16/23_series/23924/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98f75e744ef439b50d5d2b5042a4ba4f8933184e0999dcadf74ebef2e0d9af97 +size 24788 diff --git a/marked/Rel-16/23_series/23924/474a819357587e34949a3e110ff19b30_img.jpg b/marked/Rel-16/23_series/23924/474a819357587e34949a3e110ff19b30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e22ae5356ebf83ef04b293ddd2a71b5544ff16b --- /dev/null +++ b/marked/Rel-16/23_series/23924/474a819357587e34949a3e110ff19b30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:172872c629fc4ccc27c539ec6b888d7ce6700347ab49e44aa49e076b4be6feb1 +size 55373 diff --git a/marked/Rel-16/23_series/23924/476164b8bdf95c337de4e63f1f82caf3_img.jpg b/marked/Rel-16/23_series/23924/476164b8bdf95c337de4e63f1f82caf3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77c47b8c6975226e522084586b13ba1f62053610 --- /dev/null +++ b/marked/Rel-16/23_series/23924/476164b8bdf95c337de4e63f1f82caf3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fb55dfa1db64f8124581b04647fc30906f11975b4002ca13d82dce6f4adb705 +size 35189 diff --git a/marked/Rel-16/23_series/23924/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/Rel-16/23_series/23924/4b87467ad9642943235f48f7d4b59449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4535e3acb27442b77d3e874125eff56cabe90169 --- /dev/null +++ b/marked/Rel-16/23_series/23924/4b87467ad9642943235f48f7d4b59449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73ddb5365c81c068745132ad699980bac075647cb0f28b47c11c19c72ea3b3dd +size 32607 diff --git a/marked/Rel-16/23_series/23924/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/Rel-16/23_series/23924/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e90e6f59dfd628c23cd38570a3fb38131f5bc136 --- /dev/null +++ b/marked/Rel-16/23_series/23924/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ece74bf94a9dd1018f7c9662b6435fb0c3f3e720e86efbf0a89afe0aaa203da +size 30675 diff --git a/marked/Rel-16/23_series/23924/552ca016af3d6240648ab5a2cad97f60_img.jpg b/marked/Rel-16/23_series/23924/552ca016af3d6240648ab5a2cad97f60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7a6c148ba2af5409899d31e3676095eb669f5aad --- /dev/null +++ b/marked/Rel-16/23_series/23924/552ca016af3d6240648ab5a2cad97f60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2b3dd1865aaa50234d1afbbf97661f1dabed617a3936c0a0a5db3061972e26a8 +size 60904 diff --git a/marked/Rel-16/23_series/23924/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg b/marked/Rel-16/23_series/23924/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..967c8f1da8ab5ac690c4f4835219f4f112ce174e --- /dev/null +++ b/marked/Rel-16/23_series/23924/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7840e4a9cd14f96ec11d0b17139f5ba3b7e8e3c8c9997f426792bb71c75f0818 +size 28348 diff --git a/marked/Rel-16/23_series/23924/68d8089266ace7197304b43dcaf5d08e_img.jpg b/marked/Rel-16/23_series/23924/68d8089266ace7197304b43dcaf5d08e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53020b561dc1aa13bec7724775d81166d8f16dea --- /dev/null +++ b/marked/Rel-16/23_series/23924/68d8089266ace7197304b43dcaf5d08e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88a8f235c041442b2cc6ca136996a807c07d303a6d46722bb5535358ca51020b +size 30098 diff --git a/marked/Rel-16/23_series/23924/731f533b0599c8e42a063f06e4332045_img.jpg b/marked/Rel-16/23_series/23924/731f533b0599c8e42a063f06e4332045_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca8fd7ccf766e0b83229c557d6557345d17497c6 --- /dev/null +++ b/marked/Rel-16/23_series/23924/731f533b0599c8e42a063f06e4332045_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fecadd36a56270b801797406ee4947366c3ad462ce837dbaf5229362f29dfa6 +size 41883 diff --git a/marked/Rel-16/23_series/23924/75e4b78ee25f885d73120e3066a5253e_img.jpg b/marked/Rel-16/23_series/23924/75e4b78ee25f885d73120e3066a5253e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2f82dee3dfe58279065ddfc5b3f79abe38865f93 --- /dev/null +++ b/marked/Rel-16/23_series/23924/75e4b78ee25f885d73120e3066a5253e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:217032e7cbc6022b608346f5287f7f28861eb9ca801826c8039ea26249e68475 +size 53371 diff --git a/marked/Rel-16/23_series/23924/7d2d1d3870cd224c4430d19334557716_img.jpg b/marked/Rel-16/23_series/23924/7d2d1d3870cd224c4430d19334557716_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ce30e4bd83fdd6d453dec56b2b459e0924347e0 --- /dev/null +++ b/marked/Rel-16/23_series/23924/7d2d1d3870cd224c4430d19334557716_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3c368a208d9221395dd04a4e98839021fbf2dc7386f6dc9a22cba62087d4037 +size 22409 diff --git a/marked/Rel-16/23_series/23924/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/Rel-16/23_series/23924/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f5e21eb60d73c5e53604a4acd1df5ba72868d7d --- /dev/null +++ b/marked/Rel-16/23_series/23924/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ad6c48c94980c4aeb75b54a20be6964ec39203c61aac1bf8cfad39c54d7ec9c +size 38852 diff --git a/marked/Rel-16/23_series/23924/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23924/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f04d8a0dd45e6b0e83db3ccc9ed7adda81f84a5a --- /dev/null +++ b/marked/Rel-16/23_series/23924/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4fa1739808748df308f74a05a067ff9d7f41576c6e89be98314b2e16b39e9b0 +size 69872 diff --git a/marked/Rel-16/23_series/23924/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/Rel-16/23_series/23924/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b37861356c314c216c62c9bac1d6cd395f6ac29e --- /dev/null +++ b/marked/Rel-16/23_series/23924/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2031b68e79b894bb6d49a62b4cf2fc69b5a56f4ad7281649eb153891bf8e426d +size 72639 diff --git a/marked/Rel-16/23_series/23924/875c6f4f441fdd3ca7e1908fd1582983_img.jpg b/marked/Rel-16/23_series/23924/875c6f4f441fdd3ca7e1908fd1582983_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfbf0e4499dc74b90ebca29c7428b2716328973e --- /dev/null +++ b/marked/Rel-16/23_series/23924/875c6f4f441fdd3ca7e1908fd1582983_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d3d27c3dbf5682c58db423a41fd9e33ae8735f1a222853569ba9b2c9b84d21e +size 18559 diff --git a/marked/Rel-16/23_series/23924/8d33918c43de10bb6d76f330c4f10e69_img.jpg b/marked/Rel-16/23_series/23924/8d33918c43de10bb6d76f330c4f10e69_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19f87f80af712d47baf2907cc0e1bed13a6fc5d9 --- /dev/null +++ b/marked/Rel-16/23_series/23924/8d33918c43de10bb6d76f330c4f10e69_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d0d810d910a6d4eed7aeb1d73fa1955cd4b367881d162fef3acdaa87f3c9213 +size 21331 diff --git a/marked/Rel-16/23_series/23924/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg b/marked/Rel-16/23_series/23924/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a508a8fe1daf4f7a54294fdf73c51540addcc78 --- /dev/null +++ b/marked/Rel-16/23_series/23924/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:507309ed067e31c958ac1d096705aab7a5802915c254f3d81cc22a38652ca4d1 +size 45222 diff --git a/marked/Rel-16/23_series/23924/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-16/23_series/23924/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d06a1d348fff2c1787a421581f082d631c61a038 --- /dev/null +++ b/marked/Rel-16/23_series/23924/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73812bdf78bab63c1fd7197a6e35a7e2c32bd91547ba6642879a5f1f12688d36 +size 41722 diff --git a/marked/Rel-16/23_series/23924/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23924/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ed7d471b86ba16afd9ce0a6ff7a38a967ed647d --- /dev/null +++ b/marked/Rel-16/23_series/23924/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75f6ac56282297c68b48fdba608bc1af112ba9f2f74c15d7ae308eae192aaa8d +size 109935 diff --git a/marked/Rel-16/23_series/23924/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/Rel-16/23_series/23924/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b628b595c0230ded633bf05b7085b85dc1c5ade3 --- /dev/null +++ b/marked/Rel-16/23_series/23924/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bbefac76909f8f5bd7a9833bd3d6786339c4517c63a263c7b1bc43bcef85211 +size 67889 diff --git a/marked/Rel-16/23_series/23924/ac31fdfebb9751f7f10416dfe33bc872_img.jpg b/marked/Rel-16/23_series/23924/ac31fdfebb9751f7f10416dfe33bc872_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79b131502f5e041356b0380b57bae9089b1c0fa6 --- /dev/null +++ b/marked/Rel-16/23_series/23924/ac31fdfebb9751f7f10416dfe33bc872_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e05a893bb0c2b24fac4b4f6396b8799adcb448e11b10748ff22414eceac954eb +size 104107 diff --git a/marked/Rel-16/23_series/23924/b0211cee4b20034939d883ac0d70f696_img.jpg b/marked/Rel-16/23_series/23924/b0211cee4b20034939d883ac0d70f696_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e36376951f6c706365e0830182bf67c9ddd3a362 --- /dev/null +++ b/marked/Rel-16/23_series/23924/b0211cee4b20034939d883ac0d70f696_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5550a622188dae5ce2c4fd90a0a8f7665e179dc8503f852d63b76d0912d2de11 +size 35423 diff --git a/marked/Rel-16/23_series/23924/b0d4609bc46c2d88a8318706bb5321f7_img.jpg b/marked/Rel-16/23_series/23924/b0d4609bc46c2d88a8318706bb5321f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fde9e82254b92a30e3b4952c911be49326f3985f --- /dev/null +++ b/marked/Rel-16/23_series/23924/b0d4609bc46c2d88a8318706bb5321f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8aa94d8b922ef8f3a649f93b093a63bf8d9dd09211313a43bf3efe6151975a57 +size 42490 diff --git a/marked/Rel-16/23_series/23924/b28af4985cdef1e519e3aaf26561dcb3_img.jpg b/marked/Rel-16/23_series/23924/b28af4985cdef1e519e3aaf26561dcb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26dfc2e83a5b6d15eb3474482d145b6f44d5aa25 --- /dev/null +++ b/marked/Rel-16/23_series/23924/b28af4985cdef1e519e3aaf26561dcb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42986784cee3a5a115df40d86c79dcd44a10cbb7237898da9b17ebab56cc7357 +size 37759 diff --git a/marked/Rel-16/23_series/23924/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/23_series/23924/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28fdc506df726117fc062dcd3799e432b2b6285b --- /dev/null +++ b/marked/Rel-16/23_series/23924/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8922d489e4b20891a2ead11c084cd6613552a1fdd76e186c4f1b43831798e2e0 +size 81175 diff --git a/marked/Rel-16/23_series/23924/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Rel-16/23_series/23924/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a7a4c5214af2d58cbd366ccd1dc38ef50e7e52a --- /dev/null +++ b/marked/Rel-16/23_series/23924/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c094f4e99d147d14461f8e9e145042ddacd095af63b84032d4ef7056262961f6 +size 70971 diff --git a/marked/Rel-16/23_series/23924/bdcc4eb452fcc6ba091949b77546a6d4_img.jpg b/marked/Rel-16/23_series/23924/bdcc4eb452fcc6ba091949b77546a6d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bea3043a9e06b0abcfeadcce4ef9e4ac68514c49 --- /dev/null +++ b/marked/Rel-16/23_series/23924/bdcc4eb452fcc6ba091949b77546a6d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd9ed73f87c8f71354c468fee8bb5026446ba6cbde2ad00a44ef03e4bfc89f30 +size 34696 diff --git a/marked/Rel-16/23_series/23924/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/23_series/23924/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21ac4a5df3a6fa712e39369700f777314a5391c4 --- /dev/null +++ b/marked/Rel-16/23_series/23924/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6a0f904dee9948c29be97fbce5828a4e2ca66822463880b083a75eec69945f2 +size 77762 diff --git a/marked/Rel-16/23_series/23924/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg b/marked/Rel-16/23_series/23924/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca65e47265a25f2541cdeb7a061791d9666d3c53 --- /dev/null +++ b/marked/Rel-16/23_series/23924/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5af2ef63ad83cd9b738a368d084fe1cbe9dc1438b735c0eeb5c22e40f2a11a16 +size 30807 diff --git a/marked/Rel-16/23_series/23924/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-16/23_series/23924/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..da490b3d5fdde1c316ec8f295bd79baee4ad637c --- /dev/null +++ b/marked/Rel-16/23_series/23924/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35b42162301509c4ffb33ab2ae0373c161d424a26425345d23bce49279631c5c +size 56438 diff --git a/marked/Rel-16/23_series/23924/ea4fd10a9a501c602f2bea0f7f711877_img.jpg b/marked/Rel-16/23_series/23924/ea4fd10a9a501c602f2bea0f7f711877_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6aab9c32a60bf46cdb84239034f9fe2675ae366c --- /dev/null +++ b/marked/Rel-16/23_series/23924/ea4fd10a9a501c602f2bea0f7f711877_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb6e324cac5f4d9feb20ffd454dc7e95190ccb299b4fe83814645c0c3e726f3f +size 26309 diff --git a/marked/Rel-16/23_series/23924/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg b/marked/Rel-16/23_series/23924/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ca816a3d55449fe4d4bb6d40e07ddf288c8529c --- /dev/null +++ b/marked/Rel-16/23_series/23924/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d315cf17ab141460c7b7b9d48cadee3e19532586b523a3ee4dffbf360523160 +size 39316 diff --git a/marked/Rel-16/23_series/23924/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg b/marked/Rel-16/23_series/23924/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f30b8960625867a5ee369ac5ccb353172e043b56 --- /dev/null +++ b/marked/Rel-16/23_series/23924/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6e8cfff4b83d7ede78f2416cc349e627f6801286356f541c9603d16bb082fac +size 41840 diff --git a/marked/Rel-16/23_series/23924/raw.md b/marked/Rel-16/23_series/23924/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2b212c397b8e4ba9318db2dc9fdafaaca56091e9 --- /dev/null +++ b/marked/Rel-16/23_series/23924/raw.md @@ -0,0 +1,1515 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| Introduction ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions, symbols and abbreviations..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 General Description ..... | 8 | +| 4.1 Architecture Assumptions..... | 8 | +| 4.2 Overview ..... | 8 | +| 4.2.1 Issues with deploying NNSF in BSC nodes for MSC pool..... | 8 | +| 4.2.1.1 In certain networks some existing BSC/RNC nodes do not support the feature ..... | 8 | +| 4.2.1.2 Mesh TDM circuit connection between BSCs with MSCs is required ..... | 9 | +| 4.2.1.3 Complex O&M ..... | 11 | +| 4.2.2 Implementing SNSF outside of the BSC/RNC nodes ..... | 11 | +| 4.2.3 Issues with deploying NNSF in BSC nodes for SGSN pool ..... | 12 | +| 4.3 Load Balancing ..... | 12 | +| 4.4 Load Re-Distribution..... | 12 | +| 4.5 Mobility Management..... | 12 | +| 4.6 Default CN node..... | 12 | +| 4.7 Support of combined mobility management procedures..... | 12 | +| 4.8 Re-use of A-Interface TDM circuits ..... | 13 | +| 4.9 Redundancy and failover..... | 13 | +| 4.9.1 Redundancy and failover in signalling plane ..... | 13 | +| 4.9.2 Redundancy and failover in user plane..... | 13 | +| 5 Functional Description..... | 13 | +| 5.1 MS function..... | 13 | +| 5.2 RNC Functions..... | 14 | +| 5.3 BSC Functions..... | 14 | +| 5.4 MSC Server Functions ..... | 14 | +| 5.4a MGW Functions..... | 14 | +| 5.5 SGSN Functions..... | 14 | +| 5.6 SNSF Functions..... | 14 | +| 5.6.1 General ..... | 14 | +| 5.6.2 Handling of connection-oriented messages..... | 15 | +| 5.6.2.1 Basic Handling of connection-oriented messages ..... | 15 | +| 5.6.2.2 SCCP Local Reference Based Handling of connection-oriented messages ..... | 16 | +| 5.6.3 Handling of connectionless messages ..... | 17 | +| 5.6.3.1 UTRAN..... | 18 | +| 5.6.3.1.1 Reset..... | 18 | +| 5.6.3.1.2 Overload Control..... | 20 | +| 5.6.3.1.3 Reset Resource ..... | 22 | +| 5.6.3.1.4 ERROR INDICATION..... | 24 | +| 5.6.3.1.5 INFORMATION TRANSFER ..... | 25 | +| 5.6.3.1.6 Direct Information Transfer ..... | 25 | +| 5.6.3.1.7 Uplink Information Exchange..... | 26 | +| 5.6.3.1.8 Paging..... | 27 | +| 5.6.3.2 GSM..... | 28 | +| 5.6.3.2.1 Reset..... | 28 | +| 5.6.3.2.2 Overload..... | 30 | +| 5.6.3.2.3 Reset IP Resource..... | 30 | +| 5.6.3.2.4 Paging..... | 30 | +| 5.6.3.2.5 Resource Request..... | 30 | +| 5.6.3.2.6 Handover Candidate Enquire ..... | 31 | +| 5.6.3.2.7 Confusion ..... | 31 | + +| | | | +|------------|------------------------------------------------------------------------------|----| +| 5.6.3.2.8 | Load Indication ..... | 32 | +| 5.6.3.2.9 | Connectionless Information Transfer ..... | 33 | +| 5.6.3.2.10 | TDM Circuit Management..... | 33 | +| 6 | Interaction with other features ..... | 36 | +| 6.1 | Interaction with Network Sharing ..... | 36 | +| 6.1.1 | Interaction with MOCN..... | 37 | +| 6.1.1.1 | General..... | 37 | +| 6.1.1.2 | RAN selects and distributes messages to CN nodes directly..... | 37 | +| 6.1.1.3 | SNSF node select and distribute messages to CN nodes ..... | 37 | +| 6.1.2 | Interaction with GWCN ..... | 38 | +| 6.1.3 | Conclusion..... | 38 | +| 6.2 | Interaction with A interface over IP ..... | 38 | +| 7 | Compatibility Issues..... | 39 | +| 7.1 | Co-existence of NNSF within BSC/RNC nodes with SNSF above BSC/RNC nodes..... | 39 | +| 8 | Evaluation ..... | 39 | +| 9 | Conclusions..... | 40 | +| Annex A: | Change history..... | 41 | + +# --- Foreword + +This Technical Report has been produced by the 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. + +# --- Introduction + +The solution for support of the Intra Domain Connection of RAN Nodes to Multiple CN Nodes for GSM and UMTS systems in TS 23.236 [2] has some issues for MSC Pool with existing deployments and implementations, e.g. upgrade of existing nodes. This TR studies whether these issues can be resolved by deploying a function above the BSC/RNC nodes which provides similar functions as the NNSF in BSC/RNC nodes that is specified in TS 23.236 [2]. + +# --- 1 Scope + +This Technical Report evaluates the feasibility of implementing a function above the BSC/RNC nodes to provide similar functions as the NNSF function in BSC/RNC nodes that is specified in TS 23.236 [2]. This Technical Report also identifies the impacts on specifications. + +# --- 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes". +- [3] 3GPP TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling". +- [4] 3GPP TS 23.251: "Network sharing; Architecture and functional description". +- [5] 3GPP TS 48.008: "3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC BSS) interface; Layer 3 specification". +- [6] ITU-T Recommendation Q.714: "Specifications of Signalling System No. 7 - Signalling connection control part (SCCP): Signalling connection control part procedures". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Serving Node Selection Function:** A logical function above the BSC/RNC nodes used to assign an MSC Server to serve a mobile station and subsequently route the traffic to the assigned network resource. + +## 3.2 Abbreviations + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and TS 23.236 [2] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1] and TS 23.236 [2]. + +| | | +|------|----------------------------------| +| SNRI | SCCP Network Resource Identifier | +| SNSF | Serving Node Selection Function | + +# 4 General Description + +## 4.1 Architecture Assumptions + +Figure 4.1-1 illustrates the set of network elements related to deploying the SNSF node for MSC Pool. + +![Figure 4.1-1: Network Architecture of deploying SNSF node for MSC Pool. The diagram shows four main components: GERAN, UTRAN, SNSF, and MSC Server. GERAN and UTRAN are on the left, connected to each other by a dashed line labeled 'Iu-CS'. GERAN is connected to SNSF by a dashed line labeled 'A/Iu-CS'. UTRAN is connected to SNSF by a dashed line labeled 'Iu-CS'. SNSF is connected to MSC Server by a dashed line labeled 'A/Iu-CS'. MSC Server is connected to MGW by a solid line labeled '+Mc'. MGW is connected to UTRAN by a solid line labeled 'Iu-CS'. A legend at the bottom indicates that dashed lines represent the Control Plane and solid lines represent the User Plane.](0236eff05bcb8f3a343ea7933aaa306b_img.jpg) + +``` + +graph LR + GERAN[GERAN] + UTRAN[UTRAN] + SNSF[SNSF] + MSC_Server[MSC Server] + MGW[MGW] + + GERAN -.->|A/Iu-CS| SNSF + UTRAN -.->|Iu-CS| SNSF + SNSF -.->|A/Iu-CS| MSC_Server + MSC_Server -->|+Mc| MGW + MGW -->|Iu-CS| UTRAN + GERAN -.->|Iu-CS| UTRAN + +``` + +Figure 4.1-1: Network Architecture of deploying SNSF node for MSC Pool. The diagram shows four main components: GERAN, UTRAN, SNSF, and MSC Server. GERAN and UTRAN are on the left, connected to each other by a dashed line labeled 'Iu-CS'. GERAN is connected to SNSF by a dashed line labeled 'A/Iu-CS'. UTRAN is connected to SNSF by a dashed line labeled 'Iu-CS'. SNSF is connected to MSC Server by a dashed line labeled 'A/Iu-CS'. MSC Server is connected to MGW by a solid line labeled '+Mc'. MGW is connected to UTRAN by a solid line labeled 'Iu-CS'. A legend at the bottom indicates that dashed lines represent the Control Plane and solid lines represent the User Plane. + +**Figure 4.1-1: Network Architecture of deploying SNSF node for MSC Pool** + +Serving Node Selection Function is a newly introduced function which is between the BSC/RNC nodes with the MSC Servers for control plane. As implementation options, SNSF node is a logical function; it may be standalone or co-located with existing nodes. See clause 5.6 for the detail of the SNSF processing. + +To resolve the issues identified from deploying NNSF within the BSC/RNC nodes for MSC pool illustrated in clause 4.2 and to avoid any potential update requirement on existing BSC/RNC equipments, the A/Iu-CS interface is used between BSC/RNC with SNSF. + +## 4.2 Overview + +### 4.2.1 Issues with deploying NNSF in BSC nodes for MSC pool + +In certain networks and with certain implementations, some deployment issues have been identified relative to the deployment of the MSC Pool feature as specified in TS 23.236 [2]. Such issues associated with deploying NNSF in BSC/RNC for MSC pool are described in the following clauses. + +#### 4.2.1.1 In certain networks some existing BSC/RNC nodes do not support the feature + +In certain networks, most of the existing BSC/RNC nodes do not support the feature, and it is not easy to update them to support the feature and to be maintained in the future. New BSC/RNC nodes can be required to support the function, but some of the existing BSC/RNC can not be upgraded. Therefore the advantage of deploying MSC Pool can not be fully exploited within certain networks. + +![Diagram of BSC/RNC nodes connecting to multiple MSS with partial MSC Pool support.](d0abac95583b52a3b35f74a215567334_img.jpg) + +The diagram illustrates a network configuration where three Mobile Switching Stations (MSS) are shown at the top, each within its own oval coverage area. Below the MSS are nine Base Station Controller/Radio Network Controller (BSC/RNC) nodes. Two of these nodes are highlighted in green. The left green node is connected to all three MSS. The right green node is also connected to all three MSS. The other seven BSC/RNC nodes (white) are connected to only one or two MSS. Two text boxes with arrows pointing to the green nodes explain that the MSC Pool feature is supported by these two nodes, while it is not supported by the other seven nodes. + +Diagram of BSC/RNC nodes connecting to multiple MSS with partial MSC Pool support. + +**Figure 4.2.1.1.1: Part of BSC/RNC nodes support connecting to multiple MSS** + +In the real-world example provided in Figure 4.2.1.1.1, nine BSC/RNC nodes do not support MSC Pool feature while two other ones support it. Only for mobile stations moving with the coverage of the 2 BSC/RNC nodes, which support NNSF and where the NNSF function is enabled, the interaction between MSC servers and HLR and inter-MSC handover are reduced, while moving to the coverage of any other BSC/RNC nodes, the interaction and the handover will still be required as if no MSC Pool feature is deployed. And when MS is in the coverage of one of the other 9 BSC/RNC nodes that do not support NNSF, only one MSC server that the BSC/RNC node connects to can serve for the subscriber, thus the resources of the MSC servers in this pool area cannot be shared. Very little advantages could be seen from the feature in such a network configuration. + +#### 4.2.1.2 Mesh TDM circuit connection between BSCs with MSCs is required + +While deployment of AoIP (A interface bearer over IP) removes the mesh TDM connection of BSC nodes with MSC nodes, only TDM connections are supported by the existing BSC, and not all the existing BSC nodes can be updated to IP mode. The mesh TDM circuit connection between BSC nodes with MSC nodes is still a deployment issue in the absence of AoIP, and is described in this clause. + +If the MSC Pool feature is deployed per TS 23.236 [2], the feature enabled BSC will be required to have signaling and bearer connection with all the MSCs in the pool area. Figure 4.2.1.2.1 shows the mesh connection between 3 BSC/RNC nodes and 3 MSCs. + +![Diagram showing a mesh TDM circuit connection between BSC/RNC nodes and MSS in a pool area.](731f533b0599c8e42a063f06e4332045_img.jpg) + +The diagram shows a 'Pool Area' oval containing three Mobile Switching Stations labeled MSS 1, MSS 2, and MSS 3. Below the pool area are three Base Station Controller/Radio Network Controller (BSC) nodes labeled BSC 1, BSC 2, and BSC 3, each in a green box. Every BSC node is connected to every MSS node, creating a complete mesh of connections between the three BSCs and three MSSs. + +Diagram showing a mesh TDM circuit connection between BSC/RNC nodes and MSS in a pool area. + +**Figure 4.2.1.2.1: BSC/RNC connects to each MSS in the pool area** + +That is, the mesh TDM circuit connections between BSC with MSC Servers will be required because each BSC is needed to be able to connect to each MSC server in the pool area, and it will be extremely hard to implement as the + +POOL scale increases. When adding a new MSC into the pool area, the TDM circuit connection between all the BSCs with the new MSC must be installed (either by re-planing the TDM circuits between the BSCs with the MSCs or installing new circuits between the BSCs with the new MSC). + +A physical mesh connection can be avoided by introducing virtual MGWs between BSCs and MSC servers, but the TDM circuit configuration between each pair of BSC and MSC is still required as shown in Figure 4.2.1.2.2. The TDM circuits between each pair of BSC and MSC can not be used by any other pair, e.g. circuits used for the pair BSC 1 and MSC 1 can not be re-used for the pair BSC 1 and MSC 2. Thus, the usage of the TDM circuits (specifically, the circuits in each BSC – virtual MGW pair) is limited by configuration. Any changes in the core network (e.g. adding a new MSC into the pool area) will require the TDM circuits between the BSCs with the virtual MGWs to be re-installed (either by re-planing the TDM circuit configuration between the BSCs with the virtual MGWs or by installing new TDM circuits, i.e. adding new TDM circuits between BSCs with the virtual MGW for the new MSC). + +![Diagram of Figure 4.2.1.2.2: MGW between BSCs and MSC servers used as intermediary node. The diagram shows a 'Pool Area' containing two MSC servers, 'MSS 1' and 'MSS 2'. Below the pool area is a horizontal green line labeled 'Mc'. Below the Mc line is a yellow rectangular block divided into two sections: 'Virtual MGW 1' and 'Virtual MGW 2'. Below this block are two green rectangular blocks labeled 'BSC 1' and 'BSC 2'. Connections are shown as follows: MSS 1 connects to Virtual MGW 1 via a dashed pink line; MSS 2 connects to Virtual MGW 2 via a dashed brown line. BSC 1 connects to Virtual MGW 1 via a solid pink line and to Virtual MGW 2 via a solid red line. BSC 2 connects to Virtual MGW 2 via a solid black line.](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +Diagram of Figure 4.2.1.2.2: MGW between BSCs and MSC servers used as intermediary node. The diagram shows a 'Pool Area' containing two MSC servers, 'MSS 1' and 'MSS 2'. Below the pool area is a horizontal green line labeled 'Mc'. Below the Mc line is a yellow rectangular block divided into two sections: 'Virtual MGW 1' and 'Virtual MGW 2'. Below this block are two green rectangular blocks labeled 'BSC 1' and 'BSC 2'. Connections are shown as follows: MSS 1 connects to Virtual MGW 1 via a dashed pink line; MSS 2 connects to Virtual MGW 2 via a dashed brown line. BSC 1 connects to Virtual MGW 1 via a solid pink line and to Virtual MGW 2 via a solid red line. BSC 2 connects to Virtual MGW 2 via a solid black line. + +**Figure 4.2.1.2.2: MGW between BSCs and MSC servers used as intermediary node** + +But if each BSC/RNC only connects with one or two intermediary nodes, thus keeping the number of intermediary nodes small, it will mitigate the abovementioned need as shown in figure 4.2.1.2.3 that illustrates just a single intermediary node.. + +See clause 4.9.1 for BSC/RNC is connected to several intermediate nodes for the control plane. + +![Diagram of Figure 4.2.1.2.3: BSC and MSS connect to a single intermediary node. The diagram shows a 'Pool Area' containing three MSC servers: 'MSS 1', 'MSS 2', and 'MSS 3'. Below the pool area is a single yellow rectangular block labeled 'Intermediary node'. Below this block are three green rectangular blocks labeled 'BSC 1', 'BSC 2', and 'BSC 3'. Connections are shown as solid lines: MSS 1, MSS 2, and MSS 3 each connect to the 'Intermediary node'. BSC 1, BSC 2, and BSC 3 each connect to the 'Intermediary node'.](b28af4985cdef1e519e3aaf26561dcb3_img.jpg) + +Diagram of Figure 4.2.1.2.3: BSC and MSS connect to a single intermediary node. The diagram shows a 'Pool Area' containing three MSC servers: 'MSS 1', 'MSS 2', and 'MSS 3'. Below the pool area is a single yellow rectangular block labeled 'Intermediary node'. Below this block are three green rectangular blocks labeled 'BSC 1', 'BSC 2', and 'BSC 3'. Connections are shown as solid lines: MSS 1, MSS 2, and MSS 3 each connect to the 'Intermediary node'. BSC 1, BSC 2, and BSC 3 each connect to the 'Intermediary node'. + +**Figure 4.2.1.2.3: BSC and MSS connect to a single intermediary node** + +Furthermore, if the TDM circuits are reused between each pair of BSC and MSC, the likelihood of circuit exhaust will be much less, for example by means of managing the TDM circuits between the intermediary node and BSC nodes as normal resources and managed by the intermediary node itself. + +#### 4.2.1.3 Complex O&M + +When NNSF is deployed within the BSC/RNC, any O&M operation related to NNSF functionality (e.g adding a new MSC into the pool area) will require the O&M centre to interact with each MSC Pool enabled BSC/RNC node individually. As the number of BSC/RNC nodes in a network increases, the complexity of O&M increases in proportion. + +![Diagram illustrating the O&M center sending commands to multiple BSC/RNC nodes and MSSs within a Pool Area.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +The diagram shows a central 'O&M Center' (pink rectangle) on the left. To its right is a large oval labeled 'Pool Area' containing three 'MSS' (Mobile Switching Station) nodes. Below the Pool Area are several 'BSC/RNC' (Base Station Controller/Radio Network Controller) nodes, represented by green rectangles. Arrows indicate connections from the O&M Center to each of the three MSS nodes and to each of the ten BSC/RNC nodes. There are also lines connecting each MSS node to a group of BSC/RNC nodes: MSS 1 connects to the first three, MSS 2 to the next four, and MSS 3 to the last three. An ellipsis (...) is shown between the O&M Center and the first BSC/RNC node. + +Diagram illustrating the O&M center sending commands to multiple BSC/RNC nodes and MSSs within a Pool Area. + +**Figure 4.2.1.3.1: O&M centre send O&M command to all MSC Pool enabled BSCs/RNCs and MSSs** + +But if the NNSF is implemented in a small number of nodes, it will simplify the complexity of O&M. + +### 4.2.2 Implementing SNSF outside of the BSC/RNC nodes + +Deploying NNSF not in the BSC/RNC nodes but instead in standalone intermediary nodes as Serving Node Selection Function (SNSF) or co-locating with some other nodes as illustrated in figure 4.2.2.1, it will be much easier to resolve the problems captured in clause 4.2.1. + +![Diagram illustrating the deployment of the Serving Node Selection Function (SNSF) outside the BSC/RNC nodes.](b0211cee4b20034939d883ac0d70f696_img.jpg) + +The diagram shows a central 'Serving Node Selection Function (SNSF)' (orange rectangle) positioned between a 'Pool Area' and three 'BSC/RNC node 1' nodes. The 'Pool Area' is an oval containing three 'MSS' nodes labeled 'MSS 1', 'MSS 2', and 'MSS 3'. Arrows point from each of the three MSS nodes down to the SNSF. From the SNSF, three arrows point down to the three 'BSC/RNC node 1' nodes, which are represented by green rectangles. + +Diagram illustrating the deployment of the Serving Node Selection Function (SNSF) outside the BSC/RNC nodes. + +**Figure 4.2.2.1: Deploying SNSF outside of the BSC/RNC nodes** + +The NAS Node Selection Function is as specified in TS 23.236 [2] to assign specific network resources (i.e. MSC or SGSN) to serve a mobile station and subsequently route the traffic to the assigned network resource. The NRI identifies the specific CN node. The Serving Node Selection Function (SNSF) is above the BSC/RNC nodes to provide similar functions with NNSF as specified in TS 23.236 [2], has a CN node address configured for the NRI derived from the initial NAS signalling message or from the LLC frame then this message or frame is routed to this address. If no CN node address is configured for the derived NRI or if no NRI can be derived (e.g. the MS indicated an identity which + +contains no NRI) then the Serving Node Selection Function selects an available CN node (e.g. according to load balancing) and routes the message or LLC frame to the selected CN node. + +### 4.2.3 Issues with deploying NNSF in BSC nodes for SGSN pool + +In the progress of this study, there have been no contributions on the topic of SGSN Pool; as such, SGSN Pool is considered as being out of the scope of this feasibility study. + +## 4.3 Load Balancing + +The Serving Node Selection Function balances the signalling load between the available MSC Servers same as specified in clause 4.5 of TS 23.236 [2]. The load-balancing algorithm is implementation specific. + +## 4.4 Load Re-Distribution + +Signalling load re-distribution shall be performed as the procedures defined in clause 4.5a.1 of TS 23.236 [2] that the Serving Node Selection Function performs the same as the NAS Node Selection Function. + +## 4.5 Mobility Management + +No impacts upon mobility management result from the deployment of SNSF. See clause 4.6 of TS 23.236 [2]. + +## 4.6 Default CN node + +No impacts to the default CN node concept result from the deployment of SNSF. See clause 4.7 of TS 23.236 [2]. + +## 4.7 Support of combined mobility management procedures + +No impacts to the support of combined mobility management procedures result from the deployment of SNSF. See clause 4.8 of TS 23.236 [2]. + +The configurations of the Gs interface are illustrated in figure 4.7-2. + +![Diagram illustrating the Gs interface configuration when NNSF is deployed within BSS/RAN nodes. A dashed oval labeled 'MSC Pool' contains three boxes: 'MSS 1', 'MSS 2', and 'MSS 3'. Below the pool is a box labeled 'BSS/RAN + NNSF'. To the right is a box labeled 'SGSN'. Lines connect each of the three MSS boxes to the 'BSS/RAN + NNSF' box. A line labeled 'Gs' connects the 'SGSN' box to the 'BSS/RAN + NNSF' box.](04cefd2bf9de5948b15bea2d0bdc04f4_img.jpg) + +``` +graph TD; subgraph MSC_Pool [MSC Pool]; MSS1[MSS 1]; MSS2[MSS 2]; MSS3[MSS 3]; end; BSSRAN[BSS/RAN + NNSF]; SGSN[SGSN]; MSS1 --- BSSRAN; MSS2 --- BSSRAN; MSS3 --- BSSRAN; SGSN -- Gs --- BSSRAN; +``` + +Diagram illustrating the Gs interface configuration when NNSF is deployed within BSS/RAN nodes. A dashed oval labeled 'MSC Pool' contains three boxes: 'MSS 1', 'MSS 2', and 'MSS 3'. Below the pool is a box labeled 'BSS/RAN + NNSF'. To the right is a box labeled 'SGSN'. Lines connect each of the three MSS boxes to the 'BSS/RAN + NNSF' box. A line labeled 'Gs' connects the 'SGSN' box to the 'BSS/RAN + NNSF' box. + +Deploying NNSF within the BSS/RAN nodes + +![Diagram of Network Model for using the combined mobility management. It shows an MSC Pool containing MSS 1, MSS 2, and MSS 3. These are connected to an SNSF node, which is connected to a BSS/RAN node. A SGSN node is also connected to the SNSF node. A Gs interface is shown between the MSC Pool and the SGSN node.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +graph TD + subgraph MSC_Pool [MSC Pool] + MSS1[MSS 1] + MSS2[MSS 2] + MSS3[MSS 3] + end + MSS1 & MSS2 & MSS3 --> SNSF[SNSF] + SNSF --> BSS_RAN[BSS/RAN] + SNSF --> SGSN[SGSN] + MSC_Pool -.->|Gs| SGSN + +``` + +Diagram of Network Model for using the combined mobility management. It shows an MSC Pool containing MSS 1, MSS 2, and MSS 3. These are connected to an SNSF node, which is connected to a BSS/RAN node. A SGSN node is also connected to the SNSF node. A Gs interface is shown between the MSC Pool and the SGSN node. + +Deploying SNSF above the BSS/RAN nodes + +Figure 4.7-1: Network Model for using the combined mobility management + +## 4.8 Re-use of A-Interface TDM circuits + +The method of managing A-interface TDM circuits is independent with the feasibility study on deploying NNSF above the BSC/RNC nodes. The topic of re-use of A-Interface TDM circuits is considered as being out of the scope of this feasibility study. + +## 4.9 Redundancy and failover + +### 4.9.1 Redundancy and failover in signalling plane + +The resilience of a network that is enabled for MSC Pool by means of the SNSF may be improved by the implementation of nodal redundancy and failover capabilities at the SNSF. Industry standard techniques that are specific to the transport type (e.g. SS7, IP) may be applied in order to achieve the objectives of SNSF redundancy and failover. These techniques typically imply: + +- 1) real-time synchronization of transient data among multiple members of the redundancy set; and +- 2) automatic enabling of a back-up or standby member of the redundancy set when the active member fails. + +The use of such techniques is intended to be transparent to the external nodes that communicate with the redundant node. + +### 4.9.2 Redundancy and failover in user plane + +The deployment of SNSF node above BSC/RNC has only impact on the control plane and has no impact on the redundancy and failover in the user plane. + +# --- 5 Functional Description + +## 5.1 MS function + +The deployment of SNSF has no impact on the MS function. See clause 5.1 of TS 23.236 [2]. + +## 5.2 RNC Functions + +The deployment of SNSF has no impact on the RNC functions, i.e. the RNC function does not provide the NAS Node Selection Function as specified in TS 23.236 [2]. + +## 5.3 BSC Functions + +The deployment of SNSF has no impact on the BSC functions, i.e. the BSC function does not provide the NAS Node Selection Function as specified in clause 5.2 of TS 23.236 [2]. + +## 5.4 MSC Server Functions + +In addition to the functions described in TS 23.236 [2], impacts to MSC Server functions due to the deployment of SNSF are described in clause 5.6 as summarized below: + +- If SCCP Local Reference Based Handling of connection-oriented messages is applied, the MSC Server allocates the local SCCP reference which contains the local SNRI. +- If the solution of SNSF broadcasting TDM Circuit Management messages is applied, the MSC Server handles the received TDM Circuit Management message. + +## 5.4a MGW Functions + +The deployment of SNSF above BSC/RNC places no requirement on the MGW. + +NOTE: As an implementation option, SNSF may be co-located with MGW, and it does not create new requirements on the logical function of MGW. + +## 5.5 SGSN Functions + +The deployment of SNSF above BSC/RNC places no requirement on the SGSN. + +NOTE: SGSN pools as specified in TS 23.236 [2] are not possible as SNSF does not provide the NNSF functionality for PS connections. + +## 5.6 SNSF Functions + +### 5.6.1 General + +The SNSF node is used to select the specific MSC Server to which initial NAS signalling messages or LLC frames are routed. The NRI identifies the specific CN node. If the SNSF node has a CN node address configured for the NRI derived from the initial NAS signalling message, or from the LLC frame, then this message or frame is routed to this address. If no CN node address is configured for the derived NRI, or if no NRI can be derived (e.g. the MS indicated an identity which contains no NRI), then the SNSF node selects an available CN node (e.g. according to load balancing) and routes the message or LLC frame to the selected CN node. + +The SNSF node derives the NRI from the TMSI when the MS is supported in either Iu-CS mode or A interface mode. + +In A/Iu-CS mode, in the event that an MSS/VLR sends a paging-request/paging with IMSI (i.e. the paging message does not contain a TMSI), the SNSF node shall, upon reception, temporarily store the Global-CN-ID of the node that issued the paging-request/paging message. If the SNSF node in A/Iu-CS mode receives a paging-response with an IMSI, then it should check the temporarily stored Global-CN-ID on entries matching this IMSI, and forward the paging-response to the node identified by this Global-CN-ID. + +All message sequence charts in the following clauses are examples and solutions may be implemented using different message sequences from what is illustrated here. + +### 5.6.2 Handling of connection-oriented messages + +#### 5.6.2.1 Basic Handling of connection-oriented messages + +On receipt the SCCP CR message from the BSC/RNC node, the SNSF node extracts the TMSI parameter from the layer-3 message and retrieves the NRI parameters from the TMSI, select and determine the CN node from the NRI parameter as per specified in clause 5.6.1 and distribute the message to the CN node as illustrated in figure 5.6.2.1.1. The layer-3 message in the SCCP CR message may be the Initial MS Message for the A interface mode or the Initial UE Message for the Iu mode. + +![Sequence diagram illustrating the Service Flow for Basic Handling of connection-oriented messages between BSC/RNC, SSNF, and MSS nodes.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant BSC/RNC + participant SSNF + participant MSS + + Note right of SSNF: Select, determine the CN node from the NRI retrieved from the layer-3 message, and send CR message to the CN node. + BSC/RNC->>SSNF: SCCP CR + SSNF->>MSS: SCCP CR + Note right of MSS: Allocate the SCCP local reference for the connection which contains no SNRI. + MSS->>SSNF: SCCP CC + Note right of SSNF: Allocate the SCCP local reference for the connection towards the BSC node and store the combination of the two SCCP connections towards the BSC/RNC and CN nodes. + SSNF->>BSC/RNC: SCCP CC + BSC/RNC->>SSNF: SCCP DT + Note right of SSNF: Distribute the message towards the CN node as per the combination of the two SCCP connections towards the BSC/RNC and towards the CN nodes. + SSNF->>MSS: SCCP DT + +``` + +The diagram shows a sequence of messages between three nodes: BSC/RNC, SSNF, and MSS. + 1. BSC/RNC sends an SCCP CR message to SSNF. + 2. SSNF performs an internal action: 'Select, determine the CN node from the NRI retrieved from the layer-3 message, and send CR message to the CN node.' + 3. SSNF sends an SCCP CR message to MSS. + 4. MSS performs an internal action: 'Allocate the SCCP local reference for the connection which contains no SNRI.' + 5. MSS sends an SCCP CC message back to SSNF. + 6. SSNF performs an internal action: 'Allocate the SCCP local reference for the connection towards the BSC node and store the combination of the two SCCP connections towards the BSC/RNC and CN nodes.' + 7. SSNF sends an SCCP CC message back to BSC/RNC. + 8. BSC/RNC sends an SCCP DT message to SSNF. + 9. SSNF performs an internal action: 'Distribute the message towards the CN node as per the combination of the two SCCP connections towards the BSC/RNC and towards the CN nodes.' + 10. SSNF sends an SCCP DT message to MSS. + +Sequence diagram illustrating the Service Flow for Basic Handling of connection-oriented messages between BSC/RNC, SSNF, and MSS nodes. + +**Figure 5.6.2.1.1: Service Flow for Basic Handling of connection-oriented messages** + +On receipt of the SCCP CC message from the MSS node, the SSNF node creates a local reference for the SCCP connection towards the BSC/RNC node and return SCCP CC message to the BSC/RNC node, and stores the combination of the two SCCP connections, one towards the BSC/RNC and one towards the MSS node. + +For subsequent uplink and downlink messages, the SSNF node distributes the messages as per the combination of the two SCCP connections towards the BSC/RNC and the MSS nodes respectively, as illustrated in figure 5.6.2.1.1. + +The SSNF node should only send SCCP Inactivity Test (IT) message towards the MSC Server on receipt of SCCP Inactivity Test (IT) message from the BSC/RNC node. The SSNF node shall not send SCCP Inactivity Test (IT) message towards the MSC Server if the corresponding SCCP connection towards the BSC/RNC node has been released. The SSNF node should only send SCCP Inactivity Test (IT) message towards the BSC/RNC node on receipt of SCCP Inactivity Test (IT) message from the MSC Server. And the SSNF node shall not send SCCP Inactivity Test (IT) message towards the BSC/RNC node if the corresponding SCCP connection towards the MSC Server has been released. + +NOTE: On failure of receiving SCCP Inactivity Test (IT) message from the peer side (i.e. the SSNF node), the MSC Server and the BSC/RNC node will release the resources related to the SCCP connection. + +#### 5.6.2.2 SCCP Local Reference Based Handling of connection-oriented messages + +Similar with distribute message as per the NRI parameter derived from the TMSI, SCCP Network Resource Identifier (SNRI) may be configured as several digits out of the SCCP local reference for identifying the MSC Server as illustrated in figure 5.6.2.2.1. + +![Sequence diagram illustrating SNRI based distribution of uplink messages. The diagram shows three participants: BSC, SNSF, and MSS. The sequence of messages is: 1. BSC sends SCCP CR to SNSF. 2. SNSF performs internal processing (Select, determine the CN node from the NRI retrieved from the layer-3 message, and distribute the message to the CN node). 3. SNSF sends SCCP CR to MSS. 4. MSS performs internal processing (Allocate the SCCP local reference for the connection which contains the local SNRI). 5. MSS sends SCCP CC to SNSF. 6. SNSF sends SCCP CC to BSC. 7. BSC sends SCCP DT to SNSF. 8. SNSF performs internal processing (Distribute the SCCP message as per the SCCP destination local reference). 9. SNSF sends SCCP DT to MSS.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant BSC + participant SNSF + participant MSS + Note right of SNSF: Select, determine the CN node from the NRI retrieved from the layer-3 message, and distribute the message to the CN node. + BSC->>SNSF: SCCP CR + Note right of MSS: Allocate the SCCP local reference for the connection which contains the local SNRI. + SNSF->>MSS: SCCP CR + MSS->>SNSF: SCCP CC + SNSF->>BSC: SCCP CC + BSC->>SNSF: SCCP DT + Note right of SNSF: Distribute the SCCP message as per the SCCP destination local reference. + SNSF->>MSS: SCCP DT + +``` + +Sequence diagram illustrating SNRI based distribution of uplink messages. The diagram shows three participants: BSC, SNSF, and MSS. The sequence of messages is: 1. BSC sends SCCP CR to SNSF. 2. SNSF performs internal processing (Select, determine the CN node from the NRI retrieved from the layer-3 message, and distribute the message to the CN node). 3. SNSF sends SCCP CR to MSS. 4. MSS performs internal processing (Allocate the SCCP local reference for the connection which contains the local SNRI). 5. MSS sends SCCP CC to SNSF. 6. SNSF sends SCCP CC to BSC. 7. BSC sends SCCP DT to SNSF. 8. SNSF performs internal processing (Distribute the SCCP message as per the SCCP destination local reference). 9. SNSF sends SCCP DT to MSS. + +**Figure 5.6.2.2.1: SNRI based distribution of uplink messages (SCCP connection established by the RAN)** + +On receipt of the initial SCCP CR message, the SNSF retrieves the NRI parameter from the TMSI from the layer 3 message and selects the MSC Server as specified in clause 5.6.1 and distribute the message to the destination MSC Server. The layer-3 message in the SCCP CR message may be the Initial MS Message for the A interface mode or the Initial UE Message for the Iu mode. + +On receipt of the initial SCCP CR message, the MSC Server allocates the SCCP local reference for the connection which contains the local SCCP Network Resource Identifier (SNRI) as configured for the MSC Server, and returns the local reference by the source local reference to the BSC through the SNSF. The SNSF routes the message towards the BSC/RNC node as per the destination signalling point code retrieved from the SCCP CC message. + +For subsequent uplink messages, the SNSF retrieves the SNRI parameter from the destination local reference and distributes the message as per the SNRI parameter. For subsequent downlink messages, the SNSF routes the message towards the BSC/RNC node as per the destination signalling point code retrieved from the SCCP message. + +The SNSF shall not generate SCCP Inactivity Test (IT) messages by its own, but shall route uplink and downlink SCCP Inactivity Test (IT) messages as specified above for subsequent uplink and downlink messages. + +**NOTE:** On failure of receiving SCCP Inactivity Test (IT) message from the peer side (i.e. the SNSF), the MSC Server and the BSC/RNC node will release the resources related to the SCCP connection. + +In this approach, the SNSF does not need to store or handle states of the SCCP connections established between the RAN node and the MSC server. SCCP messages for the same call may be distributed via different SNSFs (e.g. upon the failure of an SNSF). + +The principles specified in this clause for SNRI based distribution of uplink connection oriented messages are also applicable to scenarios where the SCCP connection is established by the MSC Server, e.g. Handover Request procedure. In those scenarios, the MSC Server allocates and includes the SNRI within the SCCP local reference in the SCCP CR message (see figure 5.6.2.2.2). The SNSF distributes the SCCP CC message and subsequent uplink connection oriented messages as per the SCCP destination local reference. + +![Sequence diagram showing SNRI based distribution of uplink messages between BSC, SNSF, and MSS. The diagram shows the flow of SCCP CR, CC, and DT messages with internal processing steps in the SNSF and MSS.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant BSC + participant SNSF + participant MSS + Note right of MSS: Allocate the SCCP local reference +for the connection which contains +the local SNRI. + MSS->>SNSF: SCCP CR + SNSF->>BSC: SCCP CR + BSC->>SNSF: SCCP CC + Note right of SNSF: Distribute the SCCP message as per the +SCCP destination local reference. + SNSF->>MSS: SCCP CC + BSC->>SNSF: SCCP DT + Note right of SNSF: Distribute the SCCP message as per the +SCCP destination local reference. + SNSF->>MSS: SCCP DT + +``` + +Sequence diagram showing SNRI based distribution of uplink messages between BSC, SNSF, and MSS. The diagram shows the flow of SCCP CR, CC, and DT messages with internal processing steps in the SNSF and MSS. + +**Figure 5.6.2.2.2: SNRI based distribution of uplink messages +(SCCP connection established by the MSC Server)** + +##### **Basic configuration needed for one pool:** + +- For an MSC pool, the range of the SNRI bits out of the SCCP local reference shall be the same for SNSFs and MSC Servers. This range shall be configurable in SNSFs and MSC servers. +- The mapping from the SNRI to the MSC Servers shall follow the configuration in the MSC Servers. +- the SNRI should contain at most 5 bits (this allows the pool to contain up to 32 MSC Servers without impacting the maximum number of calls an MSC Server may support). + +A sample of the range of the SNRI bits out of local reference in the CN side is illustrated in figure 5.6.2.2. + +| | | | | | | | | | | | | | | | | | | | | | | | | +|----|----|----|----|------------|----|----|----|----|----|----|----|----|----|---|---|---|---|---|---|---|---|---|---| +| 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 | 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| | | | | SNRI range | | | | | | | | | | | | | | | | | | | | + +**Figure 5.6.2.2: A sample of the range of the SNRI bits out of local reference in the CN side** + +NOTE: The configurations of NRI and SNRI are irrelative. With the nature both NRI and SNRI identifies the MSC Server, the two sets of identifiers may be unified or one set can be map to another one (e.g. several NRI map to one SNRI). + +### 5.6.3 Handling of connectionless messages + +Service flows are described in this clause for the BSSAP/RANAP connectionless messages. + +#### 5.6.3.1 UTRAN + +##### 5.6.3.1.1 Reset + +###### 5.6.3.1.1.1 UTRAN Initiated RESET + +![Sequence diagram for UTRAN Initiated RESET procedure](21ad58fee90f2be50708ff541d225507_img.jpg) + +The diagram illustrates the UTRAN Initiated RESET procedure. It involves four entities: RNC, SNSF, MSS1, and MSS2. The sequence of messages is as follows: 1. The RNC sends a RESET message to the SNSF. 2. The SNSF has a dashed box indicating it forwards the RESET message to all MSC Servers (MSS1 and MSS2) and starts a timer. 3. The SNSF sends a RESET message to MSS1. 4. The SNSF sends a RESET message to MSS2. 5. MSS1 sends a RESET ACKNOWLEDGE message to the SNSF. 6. MSS2 sends a RESET ACKNOWLEDGE message to the SNSF. 7. The SNSF has a dashed box indicating that on receipt of RESET ACKNOWLEDGE messages from all MSC Servers, it sends a RESET ACKNOWLEDGE message to the RNC and stops the timer. 8. The SNSF sends the RESET ACKNOWLEDGE message to the RNC. + +Sequence diagram for UTRAN Initiated RESET procedure + +Figure 5.6.3.1.1.1.1: UTRAN initiated RESET procedure + +In the event of a failure at the UTRAN which has resulted in the loss of transaction reference information, a RESET message shall be sent to all MSC Servers towards which the RNC has Iu signalling connections established. This message is used by the MSC Server to release affected Radio Access Bearers and to erase all affected references for the sending RNC. + +On receipt of the RNC initiated RESET message, the SNSF node forward the RESET message to all the MSC Servers and starts a Timer to waiting for the RESET ACKNOWLEDGE from the MSC Server. On receipt of the RESET ACKNOWLEDGE messages from all the MSC Server, the SNSF node sends a RESET ACKNOWLEDGE message towards the RNC and stops the Timer. If the Timer fires and the SNSF node has not received RESET ACKNOWLEDGE messages from all the MSC Servers, the SNSF node stops the timer and the RNC may re-send the RESET message as defined in clause 8.26.3.2 of TS 25.413 [3]. + +###### 5.6.3.1.1.2 CN Initiated RESET + +![Sequence diagram for CN Initiated RESET procedure](b0d4609bc46c2d88a8318706bb5321f7_img.jpg) + +The diagram illustrates the CN Initiated RESET procedure. It involves four entities: RNC, SNSF, MSS1, and MSS2. The sequence of messages is as follows: 1. The MSS1 sends a RESET message to the SNSF. 2. The SNSF has a dashed box indicating that on receipt of a Reset message from part of the MSC Servers in the pool area, it shall not relay the RESET message and may isolate these MSC Servers for a preconfigured period. 3. The SNSF sends a RESET ACKNOWLEDGE message to the MSS1. + +Sequence diagram for CN Initiated RESET procedure + +Figure 5.6.3.1.1.2.1: RESET procedure initiated from part of the MSC Servers + +According to TS 25.413 [3], in the event of a failure at the CN, which has resulted in the loss of transaction reference information, a RESET message shall be sent to the RNC. On receipt of the RESET message, the UTRAN releases affected Radio Access Bearers and clears all the affected references. + +The RNC should normally have Radio Access Bearers and Iu resources that are handled by other MSC Servers of the pool, and these resources shall not be released while resources handled by the resetting MSC Server should normally be released. + +Based on that, the SNSF shall not relay towards the RNC the RESET message which is received from only part of the MSC Servers, and may isolate the MSC Servers for a preconfigured period. During that period, the SNSF does not transfer any message towards the isolated MSC Server. The affected Radio Access Bearers and the affected references with the isolated MSC Server will be release during the isolation period by some mechanisms, e.g. by the subscriber hanging up the call or by the SCCP Inactivity Test procedure. The SNSF shall then return a RESET ACKNOWLEDGE message to the resetting MSC. + +NOTE 1: ITU-T Recommendation Q.714 [6] defines a range from 11 to 21 minutes for the SCCP T(iar) timer; in practice, all the calls should be released within few tens of seconds by subscribers hanging up the call. + +NOTE 2: Immediately returning a RESET ACKNOWLEDGE message to the MSC Server without any isolation period prevents failure of subsequent mobile terminated calls or signalling (e.g. Short Message), as well as possible unbalanced load distribution on the MSC Servers of the pool. E.g. subscribers affected by the resetting MSC Server will hang up and re-establish a new call immediately, which will lead the SNSF to re-allocate the subscribers to other MSC Servers of the pool if the resetting MSC Server is isolated. + +NOTE 3: Without an isolation period, the MSC Server may allocate to new calls an Iu signalling connection not yet freed in the RNC for earlier calls. This is not a concern if the RNC accepts the new call and releases the old call in that circumstances. + +If the SNSF received RESET messages from all the MSC Servers towards a RNC node within the MSC Pool Area during the period of the isolation, the SNSF may send a RESET message to the destination RNC. On receipt of the RESET ACKNOWLEDGE message from the RNC, the SNSF forwards the RESET ACKNOWLEDGE message to all the MSC Servers. + +![Sequence diagram illustrating the RESET procedure initiated from all the MSC Servers. The diagram shows four lifelines: RNC, SNSF, MSS1, and MSS2. MSS1 and MSS2 send RESET messages to the SNSF. The SNSF waits for a preconfigured period (indicated by a dashed box 'On receipt of Reset message from all the MSC Servers within a preconfigured period'). After the period, the SNSF sends a RESET message to the RNC. The RNC responds with a RESET ACKNOWLEDGE message. The SNSF then forwards the RESET ACKNOWLEDGE message to all the MSC Servers (indicated by a dashed box 'Forward the RESET ACKNOWLEDGE message to all the MSC Servers').](124c6108c63173818afb8ed49521e22d_img.jpg) + +``` +sequenceDiagram + participant RNC + participant SNSF + participant MSS1 + participant MSS2 + Note right of SNSF: On receipt of Reset message from all the MSC Servers within a preconfigured period + MSS1->>SNSF: RESET + MSS2->>SNSF: RESET + Note right of SNSF: Forward the RESET ACKNOWLEDGE message to all the MSC Servers + SNSF->>RNC: RESET + RNC-->>SNSF: RESET ACKNOWLEDGE + SNSF->>MSS1: RESET ACKNOWLEDGE + SNSF->>MSS2: RESET ACKNOWLEDGE +``` + +Sequence diagram illustrating the RESET procedure initiated from all the MSC Servers. The diagram shows four lifelines: RNC, SNSF, MSS1, and MSS2. MSS1 and MSS2 send RESET messages to the SNSF. The SNSF waits for a preconfigured period (indicated by a dashed box 'On receipt of Reset message from all the MSC Servers within a preconfigured period'). After the period, the SNSF sends a RESET message to the RNC. The RNC responds with a RESET ACKNOWLEDGE message. The SNSF then forwards the RESET ACKNOWLEDGE message to all the MSC Servers (indicated by a dashed box 'Forward the RESET ACKNOWLEDGE message to all the MSC Servers'). + +**Figure 5.6.3.1.1.2.2: RESET procedure initiated from all the MSC Servers** + +NOTE 4: If a RNC connects with multiple SNSFs, the MSC Servers shall be configured to one of the SNSFs that the MSC Servers shall send the RESET messages to. The MSC Servers should only send the RESET message to the preconfigured SNSF when the RESET procedure is initiated towards the RNC. + +NOTE 5: Since it is unlikely that all the MSC Servers of the pool reset at the same time (i.e. during the same short period), an SNSF can handle this scenario as it handles RESET initiated by part of the MSC Servers of the pool. + +##### 5.6.3.1.2 Overload Control + +The Overload Control procedure is defined to give some degree of signalling flow control according to TS 25.413 [3]. See clause 8.25 of TS 25.413 [3] for detail of the philosophy and the algorithm used. + +###### 5.6.3.1.2.1 UTRAN Initiated Overload Control + +![Sequence diagram for UTRAN Initiated Overload Control](12de9b926df0384ec07702671827c9cd_img.jpg) + +A sequence diagram showing the interaction between RNC, SNSF, MSS1, and MSS2. The RNC sends an OVERLOAD message to the SNSF. The SNSF then broadcasts this message to all MSC Servers (MSS1 and MSS2) via a dashed box labeled 'Broadcast OVERLOAD message to all the MSC'. The SNSF sends OVERLOAD messages to both MSS1 and MSS2. + +Sequence diagram for UTRAN Initiated Overload Control + +Figure 5.6.3.1.2.1.1: Overload at the UTRAN + +If the UTRAN is overloaded, it will send an OVERLOAD message towards the MSC Servers which the RNC node connects with. On receipt of the RNC initiated OVERLOAD message, the SNSF node should broadcast this message to all the MSC Servers. + +###### 5.6.3.1.2.2 CN Initiated Overload Control + +###### 5.6.3.1.2.2.1 Overload at parts of the MSC Servers + +![Sequence diagram for Overload at parts of the MSC Servers](f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg) + +A sequence diagram showing the interaction between RNC, SNSF, MSS1, and MSS2. MSS1 sends an OVERLOAD message to the SNSF. The SNSF then enters a dashed box labeled 'Receipt of the OVERLOAD message from part of the MSC, the SNSF node discards this message and adjusts load balance arithmetic to reduce the traffic to the overloaded MSC Servers.' The SNSF does not send any message to the RNC or MSS2. + +Sequence diagram for Overload at parts of the MSC Servers + +Figure 5.6.3.1.2.2.1.1: Overload at parts of the MSC Servers + +The MSC Server should indicate to the RNC that it is in a congested state by sending an OVERLOAD message. On reception of the message, the UTRAN should cause reduction of signalling traffic towards the MSC Server. When the SNSF is deployed above the UTRAN, if only part of the MSC Servers are in a congested state, the OVERLOAD message should not be sent to the RNC nodes, otherwise, the RNC will reduce signalling traffic towards all the MSC Servers. The SNSF node should adjust load balance arithmetic to reduce congested MSC Server traffic and add other normal MSC Server traffic. + +###### 5.6.3.1.2.2.2 Overload at all the MSC Servers + +![Sequence diagram for Overload at all the MSC Servers. Lifelines: RNC, SNSF, MSS1, MSS2. MSS1 and MSS2 send OVERLOAD messages to SNSF. A dashed box indicates the receipt of overload messages from all MSCs within a period TIME. SNSF then sends an OVERLOAD message to RNC.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant SNSF + participant MSS1 + participant MSS2 + MSS1->>SNSF: OVERLOAD + MSS2->>SNSF: OVERLOAD + Note over SNSF: Receipt of overload +message from all the MSC +within a period TIME + SNSF->>RNC: OVERLOAD + +``` + +Sequence diagram for Overload at all the MSC Servers. Lifelines: RNC, SNSF, MSS1, MSS2. MSS1 and MSS2 send OVERLOAD messages to SNSF. A dashed box indicates the receipt of overload messages from all MSCs within a period TIME. SNSF then sends an OVERLOAD message to RNC. + +**Figure 5.6.3.1.2.2.2.1: Overload at all of the CN** + +On receipt of all OVERLOAD messages from all the MSC Servers within a period TIMER (the TIMER is configurable with operator's decision), the SNSF node relays one of the received OVERLOAD messages to the destination RNC node. On reception of the message, the UTRAN will reduce signalling traffic towards the CN. + +NOTE: If an RNC node connects with multiple SNSF nodes, the MSC Servers shall be configured to one of the SNSF nodes that the MSC Servers shall send the OVERLOAD messages to. The MSC Servers should only send the OVERLOAD message to the preconfigured SNSF node when the OVERLOAD procedure is initiated towards the RNC. + +##### 5.6.3.1.3 Reset Resource + +###### 5.6.3.1.3.1 UTRAN Initiated Reset Resource + +![Sequence diagram for UTRAN Initiated Reset Resource. Lifelines: RNC, SNSF, MSS1, MSS2. RNC sends RESET RESOURCE to SNSF. SNSF distributes the message to MSS1 and MSS2. MSS1 and MSS2 send RESET RESOURCE ACK to SNSF. SNSF sends RESET RESOURCE ACK to RNC.](552ca016af3d6240648ab5a2cad97f60_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant SNSF + participant MSS1 + participant MSS2 + RNC->>SNSF: RESET RESOURCE + Note over SNSF: For RNC-allocated Iu Signalling Cnx ID, +distribute the message to all CN nodes. + +For CN-allocated Iu Signalling Cnx ID, +distribute the message to all CN nodes or only +to the right CN node(s) as per the SNRI +included in the Iu Signalling Cnx ID + SNSF->>MSS1: RESET RESOURCE + SNSF-->>MSS2: RESET RESOURCE + MSS1->>SNSF: RESET RESOURCE ACK + MSS2-->>SNSF: RESET RESOURCE ACK + SNSF->>RNC: RESET RESOURCE ACK + +``` + +Sequence diagram for UTRAN Initiated Reset Resource. Lifelines: RNC, SNSF, MSS1, MSS2. RNC sends RESET RESOURCE to SNSF. SNSF distributes the message to MSS1 and MSS2. MSS1 and MSS2 send RESET RESOURCE ACK to SNSF. SNSF sends RESET RESOURCE ACK to RNC. + +**Figure 5.6.3.1.1.2.1: UTRAN initiated RESET RESOURCE procedure** + +According to TS 25.413 [3], in the event of an abnormal failure, the RNC may send a RESET RESOURCE message (including the list of Iu Signalling Connection Identifiers) to release the corresponding CN resources. + +The Iu Signalling Connection Identifiers may have been allocated by the RNC or the MSC Server. + +The MSC Server should include the SNRI in the Iu signalling connection ID it allocates. + +Upon receipt of a RESET RESOURCE message from the RNC, the SNSF should broadcast the RESET RESOURCE message including RNC-initiated or/and MSC-initiated Iu Signalling Connection IDs to all MSC Servers. At the expiration of a guard timer, the SNSF returns a RESET RESOURCE ACK to the RNC. + +As an implementation option, the SNSF may distribute a RESET RESOURCE message including only MSC-initiated Iu Signalling Connection Ids only to the right MSC Server(s) using the SRNI contained within the Iu Signalling Connection Ids. + +In this approach, the SNSF does not need to store call related information. + +NOTE: Including the SNRI in an MSC-initiated Iu signalling connection ID enables the SNSF to route the RESET RESOURCE message to the right MSC Server(s), but also the MSC Servers to recognize their own MSC-initiated Iu signalling connection Ids if the RESET RESOURCE message is distributed to all MSC Servers. + +###### 5.6.3.1.3.2 CN Initiated Reset Resource + +###### 5.6.3.1.3.2.1 Alternative 1: Broadcast Based + +![Sequence diagram for MSC Server initiated Reset Resource Procedure (Alternative 1: Broadcast Based).](75e4b78ee25f885d73120e3066a5253e_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant SNSF + participant MSS1 + participant MSS2 + + MSS1->>SNSF: RESET RESOURCE + SNSF->>RNC: RESET RESOURCE + RNC->>SNSF: RESET RESOURCE ACKNOWLEDGE + Note over SNSF, MSS2: Broadcast RESET RESOURCE ACKNOWLEDGE message to all the MSC Servers + SNSF->>MSS1: RESET RESOURCE ACKNOWLEDGE + SNSF->>MSS2: RESET RESOURCE ACKNOWLEDGE + +``` + +The diagram illustrates the sequence of messages for the MSC Server initiated Reset Resource Procedure (Alternative 1: Broadcast Based). It involves four participants: RNC, SNSF, MSS1, and MSS2. The sequence starts with MSS1 sending a RESET RESOURCE message to the SNSF. The SNSF then transfers this message to the RNC. The RNC releases local resources and references and returns a RESET RESOURCE ACKNOWLEDGE message to the SNSF. The SNSF then broadcasts this message to all MSC Servers (MSS1 and MSS2). A dashed box indicates the broadcast action: "Broadcast RESET RESOURCE ACKNOWLEDGE message to all the MSC Servers". + +Sequence diagram for MSC Server initiated Reset Resource Procedure (Alternative 1: Broadcast Based). + +**Figure 5.6.3.1.3.2.1.1: MSC Server initiated Reset Resource Procedure** + +The MSC Server initiates the procedure by sending a RESET RESOURCE message to the RNC. On receipt of the MSC RESET RESOURCE message, the SNSF node transfers this message to the destination RNC. + +On reception of this message the RNC shall release the local resources and references (i.e. radio resources and Iu signalling connection identifiers) associated to the specific MSC Server and Iu signalling connection identifiers indicated in the received message. The RNC shall always return the RESET RESOURCE ACKNOWLEDGE message to the MSC Server when all Iu-related resources and references have been released. On receipt of the RNC RESET RESOURCE ACKNOWLEDGE message, the SNSF node broadcasts this message to all the MSC Servers. The MSC Servers shall ignore the RESET RESOURCE ACKNOWLEDGE message if no corresponding pending RESET RESOURCE procedures are matched locally. + +###### 5.6.3.1.3.2.2 Alternative 2: Mapping RESET to RESET Resource + +For RANAP RESET message from MSC-S, the handling is similar to BSSAP as described in clause 5.6.3.2.1.2.2 but instead of mapping the RESET to RESET Circuit including CIC, the SNSF maps the RESET from MSC-S to RESET Resource message including the Iu Signalling Connection Identifier. + +##### 5.6.3.1.4 ERROR INDICATION + +###### 5.6.3.1.4.1 UTRAN Initiated Error Indication + +![Sequence diagram for UTRAN Initiated Error Indication. Lifelines: RNC, SNSF, MSC1, MSC2. The RNC sends an ERROR INDICATION message to the SNSF. The SNSF then broadcasts this message to all MSC Servers (MSC1 and MSC2) via a dashed box labeled 'Broadcast ERROR INDICATION message to all the MSC Servers'. The SNSF sends an ERROR INDICATION message to MSC1, which in turn sends an ERROR INDICATION message to MSC2.](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +Sequence diagram for UTRAN Initiated Error Indication. Lifelines: RNC, SNSF, MSC1, MSC2. The RNC sends an ERROR INDICATION message to the SNSF. The SNSF then broadcasts this message to all MSC Servers (MSC1 and MSC2) via a dashed box labeled 'Broadcast ERROR INDICATION message to all the MSC Servers'. The SNSF sends an ERROR INDICATION message to MSC1, which in turn sends an ERROR INDICATION message to MSC2. + +Figure 5.6.3.1.4.1.1: Error Indication procedure, RNC originated + +The Error Indication procedure is initiated by an RNC node to report detected errors in one incoming message, provided they cannot be reported by an appropriate failure message. On receipt of the RNC ERROR INDICATION message, the SNSF broadcasts this message to all the MSC Servers in the Pool Area. + +###### 5.6.3.1.4.2 CN Initiated Error Indication + +![Sequence diagram for CN Initiated Error Indication. Lifelines: RNC, SNSF, MSS1, MSS2. The MSS1 sends an ERROR INDICATION message to the SNSF, which then transfers it to the RNC. The MSS2 sends an ERROR INDICATION message to the SNSF, which then transfers it to the RNC.](627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg) + +Sequence diagram for CN Initiated Error Indication. Lifelines: RNC, SNSF, MSS1, MSS2. The MSS1 sends an ERROR INDICATION message to the SNSF, which then transfers it to the RNC. The MSS2 sends an ERROR INDICATION message to the SNSF, which then transfers it to the RNC. + +Figure 5.6.3.1.4.2.1: CN initiated Error Indication procedure + +On receipt of the MSC Server initiated ERROR INDICATION message, the SNSF transfers this message to the destination RNC as per the destination Signalling Point Code received from the MSC Server. + +##### 5.6.3.1.5 INFORMATION TRANSFER + +![Sequence diagram for Information Transfer Procedure. Lifelines: RNC, SNSF, MSC1, MSC2. The procedure starts with MSC1 sending an INFORMATION TRANSFER INDICATION to SNSF. SNSF then sends an INFORMATION TRANSFER INDICATION to RNC. RNC responds with an INFORMATION TRANSFER CONFIRMATION/FAILURE to SNSF. SNSF then broadcasts this message to all MSC Servers (indicated by a dashed box). Finally, SNSF sends an INFORMATION TRANSFER CONFIRMATION/FAILURE to MSC2.](844077b3034f0030b404207db0ad76b4_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant SNSF + participant MSC1 + participant MSC2 + Note right of SNSF: Broadcast INFORMATION TRANSFER CONFIRMATION or INFORMATION TRANSFER FAILURE message to all the MSC Servers + MSC1->>SNSF: INFORMATION TRANSFER INDICATION + SNSF->>RNC: INFORMATION TRANSFER INDICATION + RNC->>SNSF: INFORMATION TRANSFER CONFIRMATION/FAILURE + SNSF->>MSC2: INFORMATION TRANSFER CONFIRMATION/FAILURE + +``` + +Sequence diagram for Information Transfer Procedure. Lifelines: RNC, SNSF, MSC1, MSC2. The procedure starts with MSC1 sending an INFORMATION TRANSFER INDICATION to SNSF. SNSF then sends an INFORMATION TRANSFER INDICATION to RNC. RNC responds with an INFORMATION TRANSFER CONFIRMATION/FAILURE to SNSF. SNSF then broadcasts this message to all MSC Servers (indicated by a dashed box). Finally, SNSF sends an INFORMATION TRANSFER CONFIRMATION/FAILURE to MSC2. + +Figure 5.6.3.1.5.1: Information Transfer Procedure + +On receipt of the MSC INFORMATION TRANSFER INDICATION message, the SNSF transfers this message to the destination RNC. On receipt of INFORMATION TRANSFER CONFIRMATION or INFORMATION TRANSFER FAILURE message from the RNC, the SNSF broadcasts this message to all the MSC Servers in the Pool Area. The MSC Server shall ignore this message if no corresponding pending Information Transfer procedures are matched locally by checking if the *Information Transfer ID* is allocated locally. + +##### 5.6.3.1.6 Direct Information Transfer + +###### 5.6.3.1.6.1 UTRAN Initiated Direct Information Transfer + +![Sequence diagram for UTRAN Initiated Direct Information Transfer. Lifelines: RNC, SNSF, MSS1, MSS2. The procedure starts with RNC sending a DIRECT INFORMATION TRANSFER message to SNSF. SNSF then broadcasts this message to all MSC Servers (indicated by a dashed box). Finally, SNSF sends a DIRECT INFORMATION TRANSFER message to MSS2.](19a59d6b53059ebd27b13c98793f88e0_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant SNSF + participant MSS1 + participant MSS2 + Note right of SNSF: Broadcast DIRECT INFORMATION TRANSFER message to all the MSC Servers + RNC->>SNSF: DIRECT INFORMATION TRANSFER + SNSF->>MSS2: DIRECT INFORMATION TRANSFER + +``` + +Sequence diagram for UTRAN Initiated Direct Information Transfer. Lifelines: RNC, SNSF, MSS1, MSS2. The procedure starts with RNC sending a DIRECT INFORMATION TRANSFER message to SNSF. SNSF then broadcasts this message to all MSC Servers (indicated by a dashed box). Finally, SNSF sends a DIRECT INFORMATION TRANSFER message to MSS2. + +Figure 5.6.3.1.6.1.1: Direct Information Transfer initiated from the RNC + +The purpose of the Direct Information Transfer procedure is to transfer some information from the RNC to the CN. The procedure is initiated with a DIRECT INFORMATION TRANSFER message sent from the RNC to the CN. On receipt of the RNC DIRECT INFORMATION TRANSFER message, the SNSF broadcasts this message to all the MSC Servers in the Pool Area. + +###### 5.6.3.1.6.2 CN Initiated Direct Information Transfer + +![Sequence diagram for CN Initiated Direct Information Transfer. Lifelines: RNC, SNSF, MSS1, MSS2. The sequence starts with a DIRECT INFORMATION TRANSFER message from MSS1 to SNSF. SNSF then sends a DIRECT INFORMATION TRANSFER message to RNC. Next, a DIRECT INFORMATION TRANSFER message is sent from MSS2 to SNSF, which then forwards it to RNC via another DIRECT INFORMATION TRANSFER message.](4b87467ad9642943235f48f7d4b59449_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant SNSF + participant MSS1 + participant MSS2 + Note right of MSS1: DIRECT INFORMATION TRANSFER + MSS1->>SNSF: DIRECT INFORMATION TRANSFER + SNSF->>RNC: DIRECT INFORMATION TRANSFER + Note right of MSS2: DIRECT INFORMATION TRANSFER + MSS2->>SNSF: DIRECT INFORMATION TRANSFER + SNSF->>RNC: DIRECT INFORMATION TRANSFER + +``` + +Sequence diagram for CN Initiated Direct Information Transfer. Lifelines: RNC, SNSF, MSS1, MSS2. The sequence starts with a DIRECT INFORMATION TRANSFER message from MSS1 to SNSF. SNSF then sends a DIRECT INFORMATION TRANSFER message to RNC. Next, a DIRECT INFORMATION TRANSFER message is sent from MSS2 to SNSF, which then forwards it to RNC via another DIRECT INFORMATION TRANSFER message. + +Figure 5.6.3.1.6.2.1: Direct Information Transfer initiated from the CN + +The purpose of the Direct Information Transfer procedure is to transfer some information from the CN to the RNC. The procedure is initiated with a DIRECT INFORMATION TRANSFER message sent from the CN to the RNC. On receipt of the MSC DIRECT INFORMATION TRANSFER message, the SNSF transfers this message to the destination RNC. + +##### 5.6.3.1.7 Uplink Information Exchange + +![Sequence diagram for Uplink Information Exchange procedure. Lifelines: RNC, SNSF, MSS1, MSS2. The sequence starts with an UPLINK INFORMATION EXCHANGE REQUEST from RNC to SNSF. SNSF then broadcasts this request to all MSSes (MSS1 and MSS2). MSS1 and MSS2 respond with UPLINK INFORMATION EXCHANGE FAILURE/RESPONSE messages to SNSF. SNSF then collects these responses within a TIMER period and sends a single UPLINK INFORMATION EXCHANGE FAILURE/RESPONSE message back to RNC.](19a5f0db57a21a0e82a7f326083e96fd_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant SNSF + participant MSS1 + participant MSS2 + RNC->>SNSF: UPLINK INFORMATION EXCHANGE REQUEST + Note right of SNSF: Broadcast UPLINK INFORMATION EXCHANGE REQUEST message to all the MSSes + SNSF->>MSS1: UPLINK INFORMATION EXCHANGE REQUEST + SNSF->>MSS2: UPLINK INFORMATION EXCHANGE REQUEST + MSS1->>SNSF: UPLINK INFORMATION EXCHANGE FAILURE/RESPONSE + MSS2->>SNSF: UPLINK INFORMATION EXCHANGE FAILURE/RESPONSE + Note right of SNSF: Receipt of UPLINK INFORMATION EXCHANGE FAILURE/RESPONSE messages from all the MSC Servers within period TIMER + SNSF->>RNC: UPLINK INFORMATION EXCHANGE FAILURE/RESPONSE + +``` + +Sequence diagram for Uplink Information Exchange procedure. Lifelines: RNC, SNSF, MSS1, MSS2. The sequence starts with an UPLINK INFORMATION EXCHANGE REQUEST from RNC to SNSF. SNSF then broadcasts this request to all MSSes (MSS1 and MSS2). MSS1 and MSS2 respond with UPLINK INFORMATION EXCHANGE FAILURE/RESPONSE messages to SNSF. SNSF then collects these responses within a TIMER period and sends a single UPLINK INFORMATION EXCHANGE FAILURE/RESPONSE message back to RNC. + +Figure 5.6.3.1.7.2: Uplink Information Exchange procedure + +On receipt of the RNC UPLINK INFORMATION EXCHANGE REQUEST message, the SNSF broadcasts the message to all the MSC Servers in the Pool Area. On receipt of an MSC UPLINK INFORMATION EXCHANGE FAILURE/RESPONSE message from all the MSC Servers in the Pool Area within a period TIMER (where TIMER is an operator matter), the SNSF transfers the latest UPLINK INFORMATION EXCHANGE FAILURE/RESPONSE message to the destination RNC. + +##### 5.6.3.1.8 Paging + +###### 5.6.3.1.8.1 Paging when RNC connects with one SNSF node + +![Sequence diagram for Figure 5.6.3.1.8.1.1: Paging procedure. RNC connect with one SNSF node. Lifelines: RNC, SNSF, MSS1, MSS2. A PAGING message is sent from MSS1 to SNSF. A dashed box indicates that the SNSF transfers the PAGING message to the RNC and temporarily stores the mapping between the Global-CN-ID and the IMSI. Finally, a PAGING message is sent from SNSF to RNC.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +``` +sequenceDiagram + participant RNC + participant SNSF + participant MSS1 + participant MSS2 + Note right of SNSF: Transfer the PAGING message to the RNC. If the paging-request/paging with IMSI, the SNSF temporarily stores the mapping between the Global-CN-ID and the IMSI. + MSS1->>SNSF: PAGING + Note right of SNSF: Transfer the PAGING message to the RNC. If the paging-request/paging with IMSI, the SNSF temporarily stores the mapping between the Global-CN-ID and the IMSI. + SNSF->>RNC: PAGING +``` + +Sequence diagram for Figure 5.6.3.1.8.1.1: Paging procedure. RNC connect with one SNSF node. Lifelines: RNC, SNSF, MSS1, MSS2. A PAGING message is sent from MSS1 to SNSF. A dashed box indicates that the SNSF transfers the PAGING message to the RNC and temporarily stores the mapping between the Global-CN-ID and the IMSI. Finally, a PAGING message is sent from SNSF to RNC. + +**Figure 5.6.3.1.8.1.1: Paging procedure. RNC connect with one SNSF node** + +On receipt of the PAGING message, the SNSF node transfers this message to the destination RNC. + +###### 5.6.3.1.8.2 Paging with TMSI when RNC connects with multiple SNSF nodes + +![Sequence diagram for Figure 5.6.3.1.8.2.1: the paging-request/paging with TMSI procedure. RNC connect multiple SNSF nodes. Lifelines: RNC, SNSF 1, SNSF 2, MSS. A PAGING message is sent from MSS to SNSF 1. A dashed box indicates that the SNSF 1 transfers the PAGING message to the RNC. Finally, a PAGING message is sent from SNSF 1 to RNC.](ea4fd10a9a501c602f2bea0f7f711877_img.jpg) + +``` +sequenceDiagram + participant RNC + participant SNSF1 as SNSF 1 + participant SNSF2 as SNSF 2 + participant MSS + Note right of SNSF1: Transfer the PAGING message to the RNC + MSS->>SNSF1: PAGING + Note right of SNSF1: Transfer the PAGING message to the RNC + SNSF1->>RNC: PAGING +``` + +Sequence diagram for Figure 5.6.3.1.8.2.1: the paging-request/paging with TMSI procedure. RNC connect multiple SNSF nodes. Lifelines: RNC, SNSF 1, SNSF 2, MSS. A PAGING message is sent from MSS to SNSF 1. A dashed box indicates that the SNSF 1 transfers the PAGING message to the RNC. Finally, a PAGING message is sent from SNSF 1 to RNC. + +**Figure 5.6.3.1.8.2.1: the paging-request/paging with TMSI procedure. RNC connect multiple SNSF nodes** + +On receipt of the PAGING message, if the paging type is TMSI paging, the SNSF node transfers this message to the destination RNC. + +###### 5.6.3.1.8.3 + +###### Paging with IMSI when RNC connects with multiple SNSF nodes + +![Sequence diagram showing the procedure for paging with IMSI when an RNC connects to multiple SNSF nodes. The diagram involves four entities: RNC, SNSF1, SNSF2, and MSS. The sequence of messages is: 1. MSS sends a PAGING message to SNSF1. 2. SNSF1 sends a PAGING message to the RNC. 3. MSS sends a PAGING IMSI NOTIFY message to SNSF2. 4. SNSF2 sends a PAGING message to the RNC. Two dashed boxes indicate internal actions: the first box shows SNSF1 transferring the PAGING message to the RNC and temporarily storing the mapping between Global-CN-ID and IMSI; the second box shows SNSF2 temporarily storing the mapping between Global-CN-ID and IMSI.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant SNSF1 + participant SNSF2 + participant MSS + + Note right of SNSF1: Transfer the PAGING message to the RNC. If the paging-request contains IMSI, the SNSF temporarily stores the mapping between the Global-CN-ID and the IMSI. + Note right of SNSF2: Temporarily stores the mapping between the Global-CN-ID and the IMSI. + + MSS->>SNSF1: PAGING + SNSF1->>RNC: PAGING + MSS->>SNSF2: PAGING IMSI NOTIFY + SNSF2->>RNC: PAGING + +``` + +Sequence diagram showing the procedure for paging with IMSI when an RNC connects to multiple SNSF nodes. The diagram involves four entities: RNC, SNSF1, SNSF2, and MSS. The sequence of messages is: 1. MSS sends a PAGING message to SNSF1. 2. SNSF1 sends a PAGING message to the RNC. 3. MSS sends a PAGING IMSI NOTIFY message to SNSF2. 4. SNSF2 sends a PAGING message to the RNC. Two dashed boxes indicate internal actions: the first box shows SNSF1 transferring the PAGING message to the RNC and temporarily storing the mapping between Global-CN-ID and IMSI; the second box shows SNSF2 temporarily storing the mapping between Global-CN-ID and IMSI. + +**Figure 5.6.3.1.8.3.1: Procedure for Paging with IMSI (RNC connects to multiple SNSF nodes)** + +On receipt of the PAGING message, the SNSF transfers this message to the destination RNC. In case the PAGING message contains IMSI, the SNSF temporarily stores the mapping between the Global-CN-ID of the node that issued the paging message and the IMSI. + +If the MSS connects with multiple SNSF nodes, the PAGING IMSI NOTIFY message should be sent to the other SNSF nodes in the Pool Area, and all these SNSF nodes should temporarily store the mapping between the Global-CN-ID of the node that issued the paging message and the IMSI. + +NOTE 1: The Paging response message may be reported via an SNSF node other than the one that received the original PAGING request message. To ensure that all SNSF nodes are able to route the PAGING response message correctly, it is proposed to notify the other SNSF nodes by means of the PAGING IMSI NOTIFY message. + +NOTE 2: The PAGING IMSI NOTIFY message may be a RANAP message and an option whether it needs to be sent or not. It is implementation specific how this may be done. + +#### 5.6.3.2 GSM + +##### 5.6.3.2.1 Reset + +###### 5.6.3.2.1.1 GERAN Initiated RESET + +The procedure is similar to the procedure specified in clause 5.6.3.1.1.1, with the following differences according to TS 48.008 [5]: + +- A RESET message is used by the BSS to indicate the MSC Server to release affected calls and erase all affected references and to put all circuits into the idle state; +- Upon receipt of a RESET message from BSS, the MSC Server that does not allocate the circuits send block messages (BLOCK or CIRCUIT GROUP BLOCK) for all circuits that were previously locally blocked on the MSC Server side; + +On receipt of the RESET message from the BSS via the SNSF, the MSC Server will release the affected calls and circuits, and will initiate BLOCK or CIRCUIT GROUP BLOCK procedures for circuits locally blocked on the MSC Server side as per TS 48.008 [5]. + +###### 5.6.3.2.1.2 CN Initiated RESET + +###### 5.6.3.2.1.2.1 Alternative -1: Broadcast Based + +The procedure is similar to the procedure specified in clause 5.6.3.1.1.2, with the following differences: according to TS 48.008 [5], + +- A RESET message is used by the BSS to release affected calls and erase all affected references and to put all circuits into the idle state; +- Upon receipt of a RESET message from the MSC a BSS that does not allocate the circuits send block messages (BLOCK or CIRCUIT GROUP BLOCK) for all circuits that were previously locally blocked on the BSS side; + +Since the SNSF will not pass the RESET message to the BSC (at least when part of the MSC Servers only are resetting), the BSC will not release the affected calls and circuits, and will not initiate any BLOCK or CIRCUIT GROUP BLOCK procedures for circuits locally blocked on the BSS side. + +As a consequence, the BSS may not be able to use the terrestrial resource that the reset MSC Server indicates for subsequent call establishments or handovers: + +- If the MSC indicates a circuit not yet released, the BSC will return an ASSIGNMENT FAILURE or HANDOVER FAILURE message with the cause set to "terrestrial resource already allocated"; +- If the MSC indicates a circuit locally blocked on the BSS side, the BSC will return an ASSIGNMENT FAILURE or HANDOVER FAILURE message with the cause "requested terrestrial resource unavailable" and send a single global BLOCK message for that concerned terrestrial circuit. + +The MSC may initiate a new assignment procedure using a new terrestrial resource. + +NOTE: Without an isolation period, the MSC Server may allocate to new calls an AoIP Call Identifier not yet freed in the BSC for earlier calls. This is not a concern if the BSC accepts the new call and releases the old call in that circumstances. + +###### 5.6.3.2.1.2.2 Alternative -2: Mapping RESET to RESET Circuit + +When a Reset message from an MSC-S is received in the SNSF (which forwards to BSC), this indicates to the BSC that all circuits controlled by that MSC-S have to be reset. However, since all the circuits from the BSC are distributed among the MSC-S's in the pool, the sending of a Reset message to the BSC would cause reset of calls to the other MSC-S's. + +A Reset message received from an MSC-S is mapped to dedicated Reset Circuit messages towards the BSC's, see Figure 5.6.3.2.1.2.2.1 below. + +However the Reset Circuit releases all the sessions which have TDM circuit connected. + +The SNSF has supervision timers in order to supervise the responses from the BSC and the MSC-S, these are required for a fault tolerant implementation. + +![Sequence diagram illustrating the RESET procedure initiated from part of the MSC Servers-Alt 2. The diagram shows five lifelines: BSC 2, BSC 1, SNSF, MSS 1, and MSS 2. The sequence of messages is: 1. MSS 1 sends a RESET message to SNSF. 2. SNSF sends a 'Reset Circuit (CIC)' message to BSC 1. 3. BSC 1 sends a 'Reset Circuit Ack (CIC)' message to SNSF. 4. SNSF sends a 'Reset Circuit (CIC)' message to BSC 2. 5. BSC 2 sends a 'Reset Circuit Ack (CIC)' message to SNSF. 6. SNSF sends a 'RESET ACK' message to MSS 1.](bdcc4eb452fcc6ba091949b77546a6d4_img.jpg) + +``` + +sequenceDiagram + participant MSS1 as MSS 1 + participant SNSF as SNSF + participant BSC1 as BSC 1 + participant BSC2 as BSC 2 + MSS1->>SNSF: RESET + SNSF->>BSC1: Reset Circuit (CIC) + BSC1->>SNSF: Reset Circuit Ack (CIC) + SNSF->>BSC2: Reset Circuit (CIC) + BSC2->>SNSF: Reset Circuit Ack (CIC) + SNSF->>MSS1: RESET ACK + +``` + +Sequence diagram illustrating the RESET procedure initiated from part of the MSC Servers-Alt 2. The diagram shows five lifelines: BSC 2, BSC 1, SNSF, MSS 1, and MSS 2. The sequence of messages is: 1. MSS 1 sends a RESET message to SNSF. 2. SNSF sends a 'Reset Circuit (CIC)' message to BSC 1. 3. BSC 1 sends a 'Reset Circuit Ack (CIC)' message to SNSF. 4. SNSF sends a 'Reset Circuit (CIC)' message to BSC 2. 5. BSC 2 sends a 'Reset Circuit Ack (CIC)' message to SNSF. 6. SNSF sends a 'RESET ACK' message to MSS 1. + +**Figure 5.6.3.2.1.2.2.1:: RESET procedure initiated from part of the MSC Servers-Alt 2** + +NOTE: This solution applies to single SNSF scenario. + +##### 5.6.3.2.2 Overload + +The procedure is similar to the procedure specified in clause 5.6.3.1.2, with the "BSC" replacing the "RNC". + +##### 5.6.3.2.3 Reset IP Resource + +The procedure is similar to the procedure specified in clause 5.6.3.1.3.1, with the "AoIP Call Identifier" replacing the "Iu Signalling Connection Id" and the BSSAP "RESET IP RESOURCE" message replacing the RANAP "RESET RESOURCE" message. + +Since the AoIP Call Identifiers are always allocated by the MSC, the SNSF may distribute the RESET IP RESOURCE messages only to the right MSC Servers. + +##### 5.6.3.2.4 Paging + +Same as Paging procedure for RANAP (See clause 5.6.3.1.8). + +##### 5.6.3.2.5 Resource Request + +![Sequence diagram of the Resource Request Procedure. Lifelines: BSC, SNSF, MSS1, MSS2. The sequence starts with a RESOURCE REQUEST from MSS1 to SNSF. SNSF then sends a RESOURCE REQUEST to BSC. BSC responds with a RESOURCE INDICATION to SNSF. SNSF then broadcasts a RESOURCE INDICATION to all MSSs (indicated by a dashed box). Finally, SNSF sends individual RESOURCE INDICATION messages to MSS1 and MSS2.](9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg) + +``` +sequenceDiagram + participant BSC + participant SNSF + participant MSS1 + participant MSS2 + Note left of BSC: + MSS1->>SNSF: RESOURCE REQUEST + SNSF->>BSC: RESOURCE REQUEST + BSC->>SNSF: RESOURCE INDICATION + Note right of BSC: Broadcast RESOURCE INDICATION message to all the MSSs + SNSF->>MSS1: RESOURCE INDICATION + SNSF->>MSS2: RESOURCE INDICATION +``` + +Sequence diagram of the Resource Request Procedure. Lifelines: BSC, SNSF, MSS1, MSS2. The sequence starts with a RESOURCE REQUEST from MSS1 to SNSF. SNSF then sends a RESOURCE REQUEST to BSC. BSC responds with a RESOURCE INDICATION to SNSF. SNSF then broadcasts a RESOURCE INDICATION to all MSSs (indicated by a dashed box). Finally, SNSF sends individual RESOURCE INDICATION messages to MSS1 and MSS2. + +**Figure 5.6.3.2.5.1: Resource Request Procedure** + +The RESOURCE REQUEST message is sent from the MSC to the BSS and requests the current spare and optionally the total accessible resource on a particular cell. On receipt of the RESOURCE REQUEST message, the SNSF node transfers this message to the destination BSC. + +The RESOURCE INDICATION message is sent from the BSS to the MSC in response to a resource request message, the message includes an explicit indication of the cell concerned. On receipt of the RESOURCE INDICATION message, the SNSF node broadcast the message to all the MSC Servers. The MSC Servers which do not send RESOURCE REQUEST message should ignore RESOURCE INDICATION message. The MSC Servers shall ignore the message if no corresponding pending RESOURCE REQUEST procedures are matched locally. + +##### 5.6.3.2.6 Handover Candidate Enquire + +![Sequence diagram for Handover Candidate Enquire Procedure. Lifelines: BSC, SNSF, MSS1, MSS2. The BSC sends a HANDOVER CANDIDATE ENQUIRE to the SNSF. The SNSF forwards it to MSS1. MSS1 responds with HANDOVER CANDIDATE RESPONSE to the SNSF. The SNSF then broadcasts this response to all MSSs (indicated by a dashed box). Finally, the SNSF sends individual HANDOVER CANDIDATE RESPONSE messages to MSS1 and MSS2.](474a819357587e34949a3e110ff19b30_img.jpg) + +``` + +sequenceDiagram + participant BSC + participant SNSF + participant MSS1 + participant MSS2 + Note right of SNSF: Broadcast HANDOVER CANDIDATE RESPONSE message to all the MSSs + BSC->>SNSF: HANDOVER CANDIDATE ENQUIRE + SNSF->>MSS1: HANDOVER CANDIDATE ENQUIRE + MSS1-->>SNSF: HANDOVER CANDIDATE RESPONSE + Note right of SNSF: Broadcast HANDOVER CANDIDATE RESPONSE message to all the MSSs + SNSF->>MSS1: HANDOVER CANDIDATE RESPONSE + SNSF->>MSS2: HANDOVER CANDIDATE RESPONSE + +``` + +Sequence diagram for Handover Candidate Enquire Procedure. Lifelines: BSC, SNSF, MSS1, MSS2. The BSC sends a HANDOVER CANDIDATE ENQUIRE to the SNSF. The SNSF forwards it to MSS1. MSS1 responds with HANDOVER CANDIDATE RESPONSE to the SNSF. The SNSF then broadcasts this response to all MSSs (indicated by a dashed box). Finally, the SNSF sends individual HANDOVER CANDIDATE RESPONSE messages to MSS1 and MSS2. + +**Figure 5.6.3.2.6.1: Handover Candidate Enquire Procedure** + +The purpose of this procedure is to allow the MSC Server to ascertain if it is possible to handover any MSs that are currently being served by a particular cell to another nominated cell. + +The MSC Server sends a HANDOVER CANDIDATE ENQUIRE message towards a BSS. On receipt of the HANDOVER CANDIDATE ENQUIRE message, the SNSF node transfers this message to the destination BSC. + +On receipt of the HANDOVER CANDIDATE RESPONSE message, the SNSF node broadcasts the response message to all the MSC Servers. Only the MSC Server that sends the HANDOVER CANDIDATE ENQUIRE message will handle the response message. The other MSC Servers in the Pool Area shall ignore the response message per procedures specified in TS 48.008 [5]. + +##### 5.6.3.2.7 Confusion + +This message is sent in either direction in response to a message which cannot be treated correctly for some reason, and for which another failure message cannot substitute. The use of this message may be under operator control. + +###### 5.6.3.2.7.1 Confusion from the BSS + +![Sequence diagram for Confusion procedure, BSC originated. Lifelines: BSC, SNSF, MSS1, MSS2. The BSC sends a CONFUSION message to the SNSF. The SNSF then broadcasts this message to all MSSs (indicated by a dashed box). Finally, the SNSF sends individual CONFUSION messages to MSS1 and MSS2.](68d8089266ace7197304b43dcaf5d08e_img.jpg) + +``` + +sequenceDiagram + participant BSC + participant SNSF + participant MSS1 + participant MSS2 + Note right of SNSF: Broadcast CONFUSION message to all the MSSs. + BSC->>SNSF: CONFUSION + Note right of SNSF: Broadcast CONFUSION message to all the MSSs. + SNSF->>MSS1: CONFUSION + SNSF->>MSS2: CONFUSION + +``` + +Sequence diagram for Confusion procedure, BSC originated. Lifelines: BSC, SNSF, MSS1, MSS2. The BSC sends a CONFUSION message to the SNSF. The SNSF then broadcasts this message to all MSSs (indicated by a dashed box). Finally, the SNSF sends individual CONFUSION messages to MSS1 and MSS2. + +**Figure 5.6.3.2.7.1.1: Confusion procedure, BSC originated** + +The CONFUSION message is sent from the BSC to the MSC Server. On receipt of the BSC CONFUSION message, the SNSF node broadcasts this message to all the MSC Servers. + +###### 5.6.3.2.7.2 + +###### Confusion from the CN + +![Sequence diagram for Confusion procedure, CN originated. Lifelines: BSC, SNSF, MSS1, MSS2. The sequence starts with a CONFUSION message from MSS1 to SNSF. SNSF then sends a CONFUSION message to BSC. BSC sends a CONFUSION message to SNSF. SNSF then sends a CONFUSION message to MSS2.](7d2d1d3870cd224c4430d19334557716_img.jpg) + +``` + +sequenceDiagram + participant BSC + participant SNSF + participant MSS1 + participant MSS2 + Note right of MSS1: CONFUSION + MSS1->>SNSF: CONFUSION + Note right of SNSF: CONFUSION + SNSF->>BSC: CONFUSION + Note right of BSC: CONFUSION + BSC->>SNSF: CONFUSION + Note right of SNSF: CONFUSION + SNSF->>MSS2: CONFUSION + +``` + +Sequence diagram for Confusion procedure, CN originated. Lifelines: BSC, SNSF, MSS1, MSS2. The sequence starts with a CONFUSION message from MSS1 to SNSF. SNSF then sends a CONFUSION message to BSC. BSC sends a CONFUSION message to SNSF. SNSF then sends a CONFUSION message to MSS2. + +Figure 5.6.3.2.7.2.1: Confusion procedure, CN originated + +The CONFUSION message is sent from the MSC to the BSC. On receipt of the MSC Server initiated CONFUSION message, the SNSF node transfers the message to the destination BSC. + +##### 5.6.3.2.8 Load Indication + +The purpose of the load indication procedure is to inform all neighbour BSS's about the traffic situation of a cell. + +The philosophy is to control the incoming handover traffic at the source, i.e. the BSS of the concerned cell informs all its neighbour BSSs about the load situation. This is achieved by sending a LOAD INDICATION message to the neighbour BSSs. On receipt of the LOAD INDICATION message the BSS may analyse the load information and take the traffic load into consideration when deciding a handover. + +The algorithm in which the BSS decides on starting a Load Indication procedure is operator dependent. + +The implementation of the Load Indication procedure shall be regarded as optional, that means, if this procedure is not used, the Load Indication message may be ignored by these network elements. + +###### 5.6.3.2.8.1 + +###### BSS Initiated Load Indication + +![Sequence diagram for Load Indication procedure, BSC originated. Lifelines: BSC, SNSF, MSS1, MSS2. The sequence starts with a LOAD INDICATION message from BSC to SNSF. SNSF then broadcasts the message to all MSC Servers (MSS1 and MSS2).](476164b8bdf95c337de4e63f1f82caf3_img.jpg) + +``` + +sequenceDiagram + participant BSC + participant SNSF + participant MSS1 + participant MSS2 + Note right of BSC: LOAD INDICATION + BSC->>SNSF: LOAD INDICATION + Note right of SNSF: Broadcast LOAD INDICATION message to all the MSC Servers + SNSF->>MSS1: LOAD INDICATION + SNSF->>MSS2: LOAD INDICATION + +``` + +Sequence diagram for Load Indication procedure, BSC originated. Lifelines: BSC, SNSF, MSS1, MSS2. The sequence starts with a LOAD INDICATION message from BSC to SNSF. SNSF then broadcasts the message to all MSC Servers (MSS1 and MSS2). + +Figure 5.6.3.2.8.1.1: Load Indication procedure, BSC originated + +The LOAD INDICATION message is sent from the BSS to the MSC Server. It indicates to the receiving entity that the transmitting BSS has detected a load situation in the concerned cell. On receipt of the BSC LOAD INDICATION message, the SNSF node broadcasts this message to all the MSC. + +###### 5.6.3.2.8.2 + +###### CN Initiated Load Indication + +![Sequence diagram for CN Initiated Load Indication. Lifelines: BSC, SNSF, MSS1, MSS2. MSS1 sends a LOAD INDICATION message to SNSF. SNSF then sends a LOAD INDICATION message to BSC. MSS2 sends a LOAD INDICATION message to SNSF. SNSF then sends a LOAD INDICATION message to BSC.](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg) + +``` + +sequenceDiagram + participant BSC + participant SNSF + participant MSS1 + participant MSS2 + MSS1->>SNSF: LOAD INDICATION + SNSF->>BSC: LOAD INDICATION + MSS2->>SNSF: LOAD INDICATION + SNSF->>BSC: LOAD INDICATION + +``` + +Sequence diagram for CN Initiated Load Indication. Lifelines: BSC, SNSF, MSS1, MSS2. MSS1 sends a LOAD INDICATION message to SNSF. SNSF then sends a LOAD INDICATION message to BSC. MSS2 sends a LOAD INDICATION message to SNSF. SNSF then sends a LOAD INDICATION message to BSC. + +Figure 5.6.3.2.8.2.1: Load Indication procedure, MSC originated + +The LOAD INDICATION message is sent from the MSC Server to the BSC. It indicates to the receiving entity that the transmitting MSS has detected a load situation in the concerned cell. On receipt of the MSC LOAD INDICATION message, the SNSF node transfers this message to the destination BSC node. + +##### 5.6.3.2.9 + +##### Connectionless Information Transfer + +###### 5.6.3.2.9.1 + +###### BSS Initiated Connectionless Information Transfer + +![Sequence diagram for BSS Initiated Connectionless Information Transfer. Lifelines: BSC, SNSF, MSS1, MSS2. BSC sends a CONNECTIONLESS INFORMATION message to SNSF. A dashed box indicates that SNSF transfers the message to any one of the MSC. SNSF then sends a CONNECTIONLESS INFORMATION message to MSS1.](dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg) + +``` + +sequenceDiagram + participant BSC + participant SNSF + participant MSS1 + participant MSS2 + BSC->>SNSF: CONNECTIONLESS INFORMATION + Note right of SNSF: Transfer the message to any one of the MSC + SNSF->>MSS1: CONNECTIONLESS INFORMATION + +``` + +Sequence diagram for BSS Initiated Connectionless Information Transfer. Lifelines: BSC, SNSF, MSS1, MSS2. BSC sends a CONNECTIONLESS INFORMATION message to SNSF. A dashed box indicates that SNSF transfers the message to any one of the MSC. SNSF then sends a CONNECTIONLESS INFORMATION message to MSS1. + +Figure 5.6.3.2.9.1.1: Connectionless Information sent from the BSC + +On receipt of the CONNECTIONLESS INFORMATION message from the BSC, the SNSF node transfers this message to any one of the MSC Servers in the Pool Area. + +###### 5.6.3.2.9.2 + +###### CN Initiated Connectionless Information Transfer + +![Sequence diagram for CN Initiated Connectionless Information Transfer. Lifelines: BSC, SNSF, MSS1, MSS2. MSS1 sends a CONNECTIONLESS INFORMATION message to SNSF. SNSF then sends a CONNECTIONLESS INFORMATION message to BSC.](8d33918c43de10bb6d76f330c4f10e69_img.jpg) + +``` + +sequenceDiagram + participant BSC + participant SNSF + participant MSS1 + participant MSS2 + MSS1->>SNSF: CONNECTIONLESS INFORMATION + SNSF->>BSC: CONNECTIONLESS INFORMATION + +``` + +Sequence diagram for CN Initiated Connectionless Information Transfer. Lifelines: BSC, SNSF, MSS1, MSS2. MSS1 sends a CONNECTIONLESS INFORMATION message to SNSF. SNSF then sends a CONNECTIONLESS INFORMATION message to BSC. + +Figure 5.6.3.2.9.2.1: CN Initiated Connectionless Information + +On receipt of the CONNECTIONLESS INFORMATION message from the MSC Server, the SNSF node transfers this message to the destination BSC. + +##### 5.6.3.2.10 + +##### TDM Circuit Management + +This clause describes message handling procedures at the SNSF for uplink TDM circuit management-related messages. Two alternatives have been captured as summarized below with the corresponding pros and cons: + +- Message distribution based on **circuit mapping data**: in this method, the SNSF determines the destination MSC Server(s) on the basis of the combination of the identity (code) of the affected circuit(s) and the network address of the sending BSC. A configured mapping between this information and the network address of the destination MSC Server(s) is assumed to exist in the SNSF. + +- **Pros:** The circuit mapping data method permits precise identification of the destination MSC Server(s), yet requires the configuration of mapping data in the SNSF. +- **Cons:** If much data configuration is required on the SNSF node together with the MSC Server, any change on the configuration will be very complicated. +- Message distribution based on **broadcast mechanism**: in this method, the SNSF sends the message to each MSC Server in the MSC Pool. + - **Pros:** This alternative requires no configured data in the SNSF or data synchronization between MSC Servers and SNSF nodes, yet its use results in the sending of messages to MSC Servers that do not manage the indicated circuit(s). + - **Cons:** MSC Server may receive TDM circuit management messages to operator circuits which are not locally configured and it is required to discard these messages in these cases. + +The use of the alternatives is implementation specific and there is no recommendation in the present document. + +###### 5.6.3.2.10.1 Message Distribution Based on Circuit Mapping Data + +Optionally, the SNSF may have the configuration data of the mapping from the circuit identity (e.g. Circuit Identity Code and the Signalling Point Code of the BSC) to the MSS node. On receipt of the circuit management messages from the BSC node, the SNSF handle the message as per the message type listed below: + +- On receipt of the BSC initiated (Un)Block or Reset Circuit message, the SNSF determines the MSS node as per the Circuit Identity Code extracted from the received message and the Source Signalling Point Code, and distributes the message to the MSS node. On receipt the (Un)Blocking Acknowledgement or Reset Circuit Acknowledge message, the SNSF relays the message to the BSC as per the destination Signalling Point Code. +- On receipt of the MSS initiated (Un)Block or Reset Circuit message, the SNSF relays the messages towards the BSC as per the destination Signalling Point Code. When received the (Un)Block Acknowledgement or Reset Circuit Acknowledge message, the SNSF determines the MSS node as per the Circuit Identity Code extracted from the received message and the Source Signalling Point Code, and distributes the message to the MSS node. +- On receipt of the BSC initiated Circuit Group (Un)Block message, the SNSF extracts the sub-set of circuits configured for each MSS node and specified in the received message, relays the message with this sub-set circuits towards the MSS node. The MSSs shall (Un)Block the circuits locally configured and return a Circuit Group (Un)Block message by setting the Status Bits with the value of "1" (*(un)blocking acknowledgement*) for the (Un)Blocked circuits. The SNSF will receive multiple Circuit Group (Un)Blocking Acknowledgement messages (one from each MSS node) and the SNSF shall aggregate the Status Bits of this IE with value of "1" (*(un)blocking acknowledgement*) and send the message with the aggregated Status Bits of the Circuit Identity Code List IE to the BSC node. Figure 5.6.3.2.10.1.1 illustrates the procedures for BSC initiated Circuit Group Block messages to block circuits configured to MSS1 and MSS2. + +NOTE 1: As specified in TS 48.008 [5], "*The CIRCUIT GROUP UNBLOCKING ACKNOWLEDGEMENT message is accepted as the appropriate acknowledgement only if the indicated Circuit Identity Code and the returned Range field of the Circuit Identity Code List match the corresponding parameter values of the respective initiating message. Otherwise the message is considered as not expected.*" The MSC Server shall return the acknowledgement messages responding to the Circuit Group (Un)Block message with the same Circuit Identity Code and the same Range Field of the Circuit Identity Code List IE. + +![Sequence diagram illustrating Uplink TDM Circuit Management Message Handling at the SNSF. The diagram shows four lifelines: BSC, SNSF, MSS 1, and MSS 2. The process starts with the BSC sending a CIRCUIT GROUP BLOCK message to the SNSF. The SNSF then performs internal steps: 'Determine the MSS node for each circuit as per Circuit Identity Code, the BSC and local mapping data with MSS node, and CIRCUIT GROUP BLOCK the set of circuits related to each MSS node.' and 'Aggregate the Status Bits with value of "1"'. Next, the SNSF sends CIRCUIT GROUP BLOCK messages to both MSS 1 and MSS 2. MSS 1 and MSS 2 respond with CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages to the SNSF. Finally, the SNSF sends a CIRCUIT GROUP BLOCKING ACKNOWLEDGE message back to the BSC.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +``` + +sequenceDiagram + participant BSC + participant SNSF + participant MSS1 as MSS 1 + participant MSS2 as MSS 2 + Note right of SNSF: Determine the MSS node for each circuit as per Circuit Identity Code, the BSC and local mapping data with MSS node, and CIRCUIT GROUP BLOCK the set of circuits related to each MSS node. + Note right of SNSF: Aggregate the Status Bits with value of "1". + BSC->>SNSF: CIRCUIT GROUP BLOCK + SNSF->>MSS1: CIRCUIT GROUP BLOCK + SNSF->>MSS2: CIRCUIT GROUP BLOCK + MSS1-->>SNSF: CIRCUIT GROUP BLOCKING ACKNOWLEDGE + MSS2-->>SNSF: CIRCUIT GROUP BLOCKING ACKNOWLEDGE + SNSF-->>BSC: CIRCUIT GROUP BLOCKING ACKNOWLEDGE + +``` + +Sequence diagram illustrating Uplink TDM Circuit Management Message Handling at the SNSF. The diagram shows four lifelines: BSC, SNSF, MSS 1, and MSS 2. The process starts with the BSC sending a CIRCUIT GROUP BLOCK message to the SNSF. The SNSF then performs internal steps: 'Determine the MSS node for each circuit as per Circuit Identity Code, the BSC and local mapping data with MSS node, and CIRCUIT GROUP BLOCK the set of circuits related to each MSS node.' and 'Aggregate the Status Bits with value of "1"'. Next, the SNSF sends CIRCUIT GROUP BLOCK messages to both MSS 1 and MSS 2. MSS 1 and MSS 2 respond with CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages to the SNSF. Finally, the SNSF sends a CIRCUIT GROUP BLOCKING ACKNOWLEDGE message back to the BSC. + +**Figure 5.6.3.2.10.1.1: Uplink TDM Circuit Management Message Handling at the SNSF (SNSF distributes the messages as per circuit identity)** + +- On receipt of the MSS initiated Circuit Group (Un)Block message, the SNSF relays the messages towards the BSC as per the destination Signalling Point Code. When received the Circuit Group (Un)Blocking Acknowledgement message (all the circuits will map to the same MSS node), the SNSF distributes the message received from the BSC node to the MSS node as per the Circuit Identity Code extracted from the received message and the Source Signalling Point Code. +- For the BSC initiated Unequipped Circuit message, the SNSF extracts the sub-set of circuits configured for each MSS node and specified in the received message, relays the message with this sub-set circuits towards the MSS nodes. + +NOTE 2: If MSS connects to multiple SNSF nodes, the MSS shall only return the acknowledgement messages towards the SNSF node which the corresponding Reset Circuit, (Un)Block, and Circuit Group (Un)Block received from. + +###### 5.6.3.2.10.2 Message Distribution Based on Broadcast Mechanism + +Alternatively, The SNSF may distribute the uplink message towards to each MSS node. In this approach, the SNSF will no need keep any data related to the mapping from the Circuit Identity to the MSS node. On receipt of the circuit management messages from the BSC node, the SNSF handle the message as per the message type listed below: + +- On receipt of the BSC initiated (Un)Block or Reset Circuit message, the SNSF relay a copy of the message to each MSS node. The MSS shall only handle the message if the circuit is configured locally. On receipt the (Un)Blocking Acknowledgement or Reset Circuit Acknowledge message, the SNSF relays the message to the BSC as per the destination Signalling Point Code. To avoid unnecessary UNEQUIPPED CIRCUIT messages from the MSC Servers, the MSC Servers shall ignore the (Un)Block or Reset Circuit message that the circuit indicated in the message is not configured locally and shall not send an UNEQUIPPED CIRCUIT message in these cases.- On receipt of the MSS initiated (Un)Block or Reset Circuit message, the SNSF relays the messages towards the BSC as per the destination Signalling Point Code. When received the (Un)Block Acknowledgement or Reset Circuit Acknowledge message from the BSC, the SNSF relay a copy of the message to each MSS node. The MSS shall ignore the message if the circuits is not configured locally. +- On receipt of the BSC initiated Circuit Group (Un)Block message, relay a copy of the message to each MSS node. The MSS shall ignore the circuits specified in the message but not configured locally, (Un)Block the circuits locally configured and return a Circuit Group (Un)Block message by setting the Status Bits with the value of "1" (*(un)blocking acknowledgement*) for the (Un)Blocked circuits and with the value of "0" (*no indication*) for the others. The SNSF will receive multiple Circuit Group (Un)Blocking Acknowledgement messages and all the messages shall have the same content with the exception of the Circuit Identity Code List IE. The SNSF shall aggregate the Status Bits of this IE with value of "1" (*(un)blocking acknowledgement*) and + +send the message with the aggregated Status Bits of the Circuit Identity Code List IE to the BSC node. Figure 5.6.3.2.10.2.1 illustrates the procedures for BSC initiated Circuit Group Block messages to block circuits configured to MSS1 and MSS2. To avoid unnecessary UNEQUIPPED CIRCUIT messages from the MSC Servers, the MSC Servers shall not send UNEQUIPPED CIRCUIT messages for the circuits indicated in the Circuit Group (Un)Block message but not locally configured. + +NOTE 1: As specified in TS 48.008 [5], *"The CIRCUIT GROUP UNBLOCKING ACKNOWLEDGEMENT message is accepted as the appropriate acknowledgement only if the indicated Circuit Identity Code and the returned Range field of the Circuit Identity Code List match the corresponding parameter values of the respective initiating message. Otherwise the message is considered as not expected."* The MSC Server shall return the acknowledgement messages responding to the Circuit Group (Un)Block message with the same Circuit Identity Code and the same Range Field of the Circuit Identity Code List IE. + +![Sequence diagram illustrating Uplink TDM Circuit Management Message Handling at the SNSF. The diagram shows four lifelines: BSC, SNSF, MSS 1, and MSS 2. The sequence starts with a CIRCUIT GROUP BLOCK message from BSC to SNSF. A dashed box indicates that SNSF relays a copy of the message to each MSS node. SNSF then sends CIRCUIT GROUP BLOCK messages to both MSS 1 and MSS 2. MSS 1 and MSS 2 respond with CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages to SNSF. A dashed box indicates that SNSF aggregates the Status Bits with a value of '1'. Finally, SNSF sends a CIRCUIT GROUP BLOCKING ACKNOWLEDGE message back to BSC.](a4b963a07cc368283154762c4b156fe7_img.jpg) + +``` + +sequenceDiagram + participant BSC + participant SNSF + participant MSS1 as MSS 1 + participant MSS2 as MSS 2 + Note right of SNSF: Relay a copy of the message to each MSS node. + BSC->>SNSF: CIRCUIT GROUP BLOCK + SNSF->>MSS1: CIRCUIT GROUP BLOCK + SNSF->>MSS2: CIRCUIT GROUP BLOCK + MSS1->>SNSF: CIRCUIT GROUP BLOCKING ACKNOWLEDGE + MSS2->>SNSF: CIRCUIT GROUP BLOCKING ACKNOWLEDGE + Note right of SNSF: Aggregate the Status Bits with value of "1". + SNSF->>BSC: CIRCUIT GROUP BLOCKING ACKNOWLEDGE + +``` + +Sequence diagram illustrating Uplink TDM Circuit Management Message Handling at the SNSF. The diagram shows four lifelines: BSC, SNSF, MSS 1, and MSS 2. The sequence starts with a CIRCUIT GROUP BLOCK message from BSC to SNSF. A dashed box indicates that SNSF relays a copy of the message to each MSS node. SNSF then sends CIRCUIT GROUP BLOCK messages to both MSS 1 and MSS 2. MSS 1 and MSS 2 respond with CIRCUIT GROUP BLOCKING ACKNOWLEDGE messages to SNSF. A dashed box indicates that SNSF aggregates the Status Bits with a value of '1'. Finally, SNSF sends a CIRCUIT GROUP BLOCKING ACKNOWLEDGE message back to BSC. + +**Figure 5.6.3.2.10.2.1: Uplink TDM Circuit Management Message Handling at the SNSF (SNSF Relay the Message to each MSS node a copy)** + +- On receipt of the MSS initiated Circuit Group (Un)Block message, the SNSF relays the messages towards the BSC as per the destination Signalling Point Code. When received the Circuit Group (Un)Blocking Acknowledgement message, the SNSF relay a copy of the message to each MSS node. The MSS shall ignore the message if the circuits specified in the message are not configured locally. +- For the BSC initiated Unequipped Circuit message, the SNSF relays a copy of the message to each MSS node. + +NOTE 2: If MSS connects to multiple SNSF nodes, the MSS shall only return the acknowledgement messages towards the SNSF node which the corresponding Reset Circuit, (Un)Block, and Circuit Group (Un)Block received from. + +# 6 Interaction with other features + +## 6.1 Interaction with Network Sharing + +Network sharing is a way for operators to share the heavy deployment costs for mobile networks, especially in the roll-out phase. Multi-Operator Core Network (MOCN) is a network-sharing configuration in which only the RAN is shared and Gateway Core Network (GWCN) is a network sharing configuration that parts of the core network (MSC Servers or SGSN nodes) are also shared (see TS 23.251 [4]). + +### 6.1.1 Interaction with MOCN + +#### 6.1.1.1 General + +For MOCN network sharing, parts of RAN network are shared. + +In a MOCN configuration without deploying the SNSF node above the RNC node, the RAN node routes the UE's initial access to the shared network to one of the available CN nodes which directly connected with the RAN node as per the PLMN-id and routes subsequent messages to the selected CN nodes as per the NRI parameters extracted from the (P-)TMSI. + +![Diagram of network configurations for only MOCN is deployed. A central RAN node is connected to two separate operators, Operator 1 and Operator 2. Operator 1 contains MSS1, and Operator 2 contains MSS2. Both MSS1 and MSS2 are connected directly to the RAN node.](875c6f4f441fdd3ca7e1908fd1582983_img.jpg) + +``` +graph TD; subgraph Operator1 [Operator 1]; MSS1[MSS1]; end; subgraph Operator2 [Operator 2]; MSS2[MSS2]; end; MSS1 --- RAN[RAN]; MSS2 --- RAN +``` + +Diagram of network configurations for only MOCN is deployed. A central RAN node is connected to two separate operators, Operator 1 and Operator 2. Operator 1 contains MSS1, and Operator 2 contains MSS2. Both MSS1 and MSS2 are connected directly to the RAN node. + +**Figure 6.1.1.1.1: Network configurations for only MOCN is deployed** + +In an MOCN configuration with deploying the SNSF node above the RNC node, the RAN node may be fully configured to select and route the UE's initial access and subsequent messages to an available CN node directly, or the RAN node may be only configured to select and route the UE's initial access and subsequent messages to the SNSF node deployed above the RAN nodes and the SNSF node select and route the UE's initial access and subsequent messages to an available CN node as depicted in the following clauses. + +#### 6.1.1.2 RAN selects and distributes messages to CN nodes directly + +In an MOCN configuration without deploying the SNSF node above the RNC node, the RAN node may be fully configured to select and route the UE's initial access and subsequent messages to an available CN node directly. As no SNSF node is deployed above the RAN nodes, no interaction is detected in this scenario. + +#### 6.1.1.3 SNSF node select and distribute messages to CN nodes + +In a MOCN configuration with deploying the SNSF node above the RNC node, the RAN node may be only configured to select and route the UE's initial access and subsequent messages to the SNSF node deployed above the RAN nodes and the SNSF node select, determine and route the UE's initial access and subsequent messages to an available CN node as specified in clause 5.6 and illustrated in figure 6.1.1.3.1. + +![Diagram of network configurations for MOCN with MSC Pool. A central RAN node is connected to an SNSF node. The SNSF node is connected to three operators: Operator 1 (containing MSS1), Operator 2 (containing MSS2, MSS3, and MSS4), and a third operator (containing MSS5). All MSS nodes are connected to the SNSF node, which in turn is connected to the RAN node.](10d81b2cc455e3563e3e562a7f451124_img.jpg) + +``` +graph TD; subgraph Operator1 [Operator 1]; MSS1[MSS1]; end; subgraph Operator2 [Operator 2]; MSS2[MSS2]; MSS3[MSS3]; MSS4[MSS4]; end; subgraph Operator3 [Operator 3]; MSS5[MSS5]; end; MSS1 --- SNSF[SNSF]; MSS2 --- SNSF; MSS3 --- SNSF; MSS4 --- SNSF; MSS5 --- SNSF; SNSF --- RAN[RAN] +``` + +Diagram of network configurations for MOCN with MSC Pool. A central RAN node is connected to an SNSF node. The SNSF node is connected to three operators: Operator 1 (containing MSS1), Operator 2 (containing MSS2, MSS3, and MSS4), and a third operator (containing MSS5). All MSS nodes are connected to the SNSF node, which in turn is connected to the RAN node. + +**Figure 6.1.1.3.1: Network configurations for MOCN with MSC Pool** + +### 6.1.2 Interaction with GWCN + +For GWCN network sharing, parts of the core network (MSC Servers or SGSN nodes) are also shared. + +In a GWCN configuration without deploying the SNSF node above the RNC node, the RAN node routes the UE's initial access to the shared network to the directly connected CN node. + +In a GWCN configuration with deploying the SNSF node above the RNC node, the RAN node routes the UE's initial access to the SNSF node shared between operators and the SNSF node select, determine and distribute the messages to a correct CN node as specified in clause 5.6 and illustrated in figure 6.1.2.1. + +The network configurations of only GWCN and GWCN with MSC Pool are shown in figure 6.1.2.1. + +![Figure 6.1.2.1: Network configurations for only GWCN and GWCN with MSC Pool. The figure contains two sub-diagrams. Figure 6.1.2-1a shows a 'Only GWCN is configured' setup where two RAN nodes (RAN1, RAN2) are connected to two separate CN nodes (MSS1, MSS2) within a shared CN pool. Figure 6.1.2-1b shows a 'Both GWCN and MSC Pool are configured' setup where the RAN nodes connect to a central SNSF node, which then connects to the shared CN pool containing MSS1 and MSS2.](ac31fdfebb9751f7f10416dfe33bc872_img.jpg) + +**Figure 6.1.2-1a: Only GWCN is configured** + +The diagram shows two RAN nodes, RAN1 and RAN2, connected to two CN nodes, MSS1 and MSS2. The CN nodes are grouped in a dashed oval labeled 'CN shared between Operator 1 with operator 2'. The RAN nodes are grouped in a dashed oval labeled 'RAN shared between Operator 1 with operator 2'. RAN1 is connected to MSS1, and RAN2 is connected to MSS2. + +**Figure 6.1.2-1b: Both GWCN and MSC Pool are configured** + +The diagram shows two RAN nodes, RAN1 and RAN2, connected to a central SNSF node. The SNSF node is connected to two CN nodes, MSS1 and MSS2, which are grouped in a dashed oval labeled 'CN shared between Operator 1 with operator 2'. The RAN nodes are grouped in a dashed oval labeled 'RAN shared between Operator 1 with operator 2'. + +Figure 6.1.2.1: Network configurations for only GWCN and GWCN with MSC Pool. The figure contains two sub-diagrams. Figure 6.1.2-1a shows a 'Only GWCN is configured' setup where two RAN nodes (RAN1, RAN2) are connected to two separate CN nodes (MSS1, MSS2) within a shared CN pool. Figure 6.1.2-1b shows a 'Both GWCN and MSC Pool are configured' setup where the RAN nodes connect to a central SNSF node, which then connects to the shared CN pool containing MSS1 and MSS2. + +**Figure 6.1.2.1: Network configurations for only GWCN and GWCN with MSC Pool** + +### 6.1.3 Conclusion + +Deploying the SNSF node above the BSC/RNC node works well with the deploying of Network Sharing (MOCN or GWCN) feature and no impact on Network Sharing. + +## 6.2 Interaction with A interface over IP + +For the use of A interface control plane over IP with A interface user plane either over TDM or over IP, the A interface signalling is transported over SIGTRAN. With this configuration, the only consideration for the deployment of the SNSF nodes is related to SNSF node redundancy and failover. The procedures for such are described in clause 4.9.1.2. + +# 7 Compatibility Issues + +## 7.1 Co-existence of NNSF within BSC/RNC nodes with SNSF above BSC/RNC nodes + +Using the NNSF within the BSC/RNC nodes has already been defined in TS 23.236 [2]. Deploying SNSF above the BSC/RNC nodes will co-exist with using the NNSF within the BSC/RNC nodes as described below. + +![Diagram illustrating the co-existence of NNSF within BSC/RNC nodes with SNSF above BSC/RNC nodes. A 'Pool Area' contains three MSC Servers (MSS 1, MSS 2, MSS 3). Below the Pool Area is an SNSF node. At the bottom are five RAN nodes: RAN 1, RAN 2, RAN 3, RAN 4 + NNSF, and RAN 5 + NNSF. Dashed lines show connections: RAN 1, 2, and 3 connect to the SNSF node; RAN 4 + NNSF and RAN 5 + NNSF connect directly to the Pool Area; the SNSF node connects to the Pool Area.](fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg) + +``` + +graph TD + subgraph Pool Area + MSS1((MSS 1)) + MSS2((MSS 2)) + MSS3((MSS 3)) + end + SNSF[SNSF] + RAN1[RAN 1] + RAN2[RAN 2] + RAN3[RAN 3] + RAN4[RAN 4 + NNSF] + RAN5[RAN 5 + NNSF] + + RAN1 -.-> SNSF + RAN2 -.-> SNSF + RAN3 -.-> SNSF + RAN4 -.-> Pool Area + RAN5 -.-> Pool Area + SNSF -.-> Pool Area + +``` + +Diagram illustrating the co-existence of NNSF within BSC/RNC nodes with SNSF above BSC/RNC nodes. A 'Pool Area' contains three MSC Servers (MSS 1, MSS 2, MSS 3). Below the Pool Area is an SNSF node. At the bottom are five RAN nodes: RAN 1, RAN 2, RAN 3, RAN 4 + NNSF, and RAN 5 + NNSF. Dashed lines show connections: RAN 1, 2, and 3 connect to the SNSF node; RAN 4 + NNSF and RAN 5 + NNSF connect directly to the Pool Area; the SNSF node connects to the Pool Area. + +**Figure 7.1.1: Co-existence of NNSF within BSC/RNC nodes with SNSF above BSC/RNC nodes** + +As shown in Figure 7.1.1, if part of the BSC/RNC nodes are capable of supporting the NNSF function as described in TS 23.236 [2] (RAN node 4~5) while the others are not (RAN node 1~3), the NNSF capable BSC/RNC nodes assign an MSC Server to serve a mobile station and subsequently route the signalling traffic to the assigned MSC Server whereas non-NNSF capable BSC/RNC nodes connect to SNSF node and the SNSF node is responsible for assigning an MSC Server to serve a mobile station and subsequently routing the signalling traffic to the assigned MSC Server. + +In this situation, the MSC Server interacts with the SNSF node as described in clause 5 of the present document (e.g., allocate the SCCP local reference with SNRI as described in clause 5.6.2.2 if the SCCP Local Reference Based Handling of connection-oriented messages is used), and interacts with BSC/RNC nodes as specified in TS 23.236 [2]. + +# 8 Evaluation + +The technical study verifies that it is feasible to support NNSF functionality above the RAN nodes. This has been studied for the circuit switched core network; the need for support of such function for the packet switched core network was removed during the execution of this study. The value of the SNSF function is based on not impacting 'old' RAN nodes. This also means that SNSF does not impact the existing A and Iu interfaces between the radio network and the CS core network. + +This study has shown that the gain of independence from the RAN nodes requires: + +- Either new standalone SNSF nodes must be introduced into the core network or the SNSF functionality must be collocated with already existing nodes, for example with the MGW. The latter may impact the capacity of the existing node due to the fact that functionality is added. +- It requires more signalling compared to when the NNSF functionality is applied in the RAN nodes, because connection to the SNSF function is forced, which are acting as proxies. +- If the SNSF functionality shall not be a single point of failure then additional complexity is required to realise redundancy mechanisms, including impacts on the MSC Server as well. + +In many cases the SNSF functionality is an SNSF internal handling. For this internal handling it is possible to reuse what has been specified for NNSF in TS 23.236 [2], e.g. load balancing and load re-distribution. Other functionality + +does not impact SNSF at all, for example combined mobility management procedures. The only identified functionality which can't be inherited by existing specifications is the support for redundancy. A potential redundant solution is described in clause 5.6.2.2 of this TR. As vendors had to already cope with these situations early in the operational environment, vendor specific solutions already exist without impacting standards or existing NNSF functions. + +In addition to the above analysis there are also other facts to be considered: + +1. Vendors have already provided products to provide SNSF functionality collocated within MGWs by different means. They may come into conflict with a future normative specification. +2. As far as known, currently those MGWs interfacing the radio network and the MSC Servers are deployed by the same vendor. For these deployment scenarios there is no need for IOT testing. +3. MGW redundancy is also based on vendor specific implementations and is not specified by 3GPP. Specifying SNSF functionality may result into conflicts with already deployed MGW redundancy. + +For the reasons listed above, the present TR concludes without a recommendation for normative specification of SNSF functionality. + +# --- 9 Conclusions + +Through the preceding technical investigation within this technical report, it is concluded that it is feasible to deploy SNSF nodes above the BSC/RNC nodes to provide functions similar to those of the NNSF in BSC/RNC nodes as specified in TS 23.236 [2]. The solution described in this TR is one of the possible solutions to resolve the implementation issues of deploying NNSF within the BSC/RNC nodes for MSC Pool. + +The solutions described in this study may be used as guideline for implementations in cases where operator does not upgrade the radio networks. + +# Annex A: Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|----|-----|---------------------------------------------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2010-03 | SP-47 | SP-100173 | - | - | MCC update to version 2.0.0 for presentation to TSG SA for approval: Requested Upgrade to TR 23.9XX. | 1.2.0 | 2.0.0 | +| 2010-03 | SP-47 | - | - | - | MCC creation of 23.924 version 10.0.0 from 23.823 version 2.0.0 after TSG SA approval with the change of TR number. | 2.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | SP-65 | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2015-12 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | - | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 | +| 2018-06 | SP-80 | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | SP-88E | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23976/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23976/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b6c455251d45de21c44e907a4eb652cc86847bd --- /dev/null +++ b/marked/Rel-16/23_series/23976/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ef35296dd8bed5ac7109dd0de7ac347ea9dc5f78e542221265932301927061b6 +size 103225 diff --git a/marked/Rel-16/23_series/23976/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/Rel-16/23_series/23976/3da1a07cb87051bf616c9876db958cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..827d15dfef1634e1cadab79e09290478cab23702 --- /dev/null +++ b/marked/Rel-16/23_series/23976/3da1a07cb87051bf616c9876db958cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:445f6f15622464d63fa6fafbb3b2e91aceeb6d5fc30ef30f4c8cd5ae8ffc17aa +size 64395 diff --git a/marked/Rel-16/23_series/23976/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23976/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2e105b5414fbf0b059fd4ce38953f9eb8f1f53da --- /dev/null +++ b/marked/Rel-16/23_series/23976/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a66c8b65a92074e96893b0b1d4fd321529d170d42f3df880edf8b3c463610fc +size 42488 diff --git a/marked/Rel-16/23_series/23976/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/marked/Rel-16/23_series/23976/744acfe8d4e31bcf03f95714c2f6e567_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e25c56f01ed79721b3ee8eac0e8ab43bedee534e --- /dev/null +++ b/marked/Rel-16/23_series/23976/744acfe8d4e31bcf03f95714c2f6e567_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:788a252d994715cbb5dab02789e6eda592984601662c2a368180efa84e6b1c68 +size 54028 diff --git a/marked/Rel-16/23_series/23976/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/marked/Rel-16/23_series/23976/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4b8469c4d6440c237b291507c292f58607b02d1f --- /dev/null +++ b/marked/Rel-16/23_series/23976/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a83ca2915a0728f91df87eabb91cf5d9f375ab424e2666c5ee7aa96b736c0ad1 +size 52743 diff --git a/marked/Rel-16/23_series/23976/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/marked/Rel-16/23_series/23976/af6be343f0c0a8f155f965dcf337b8af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7a703e334e3a3b247d3b96b98da94432461f4a6 --- /dev/null +++ b/marked/Rel-16/23_series/23976/af6be343f0c0a8f155f965dcf337b8af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:328e059f244bc088d3d6994092fba89bea0130eb73f618e431557371b148cc36 +size 46495 diff --git a/marked/Rel-16/23_series/23976/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/23_series/23976/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f0829d6532011593f82c252e1d5c109638e9274 --- /dev/null +++ b/marked/Rel-16/23_series/23976/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:517c0683e63c4d647b837fc5051a501818dc362ef21f162094dc0ee1d8cf9a7e +size 109184 diff --git a/marked/Rel-16/23_series/23976/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg b/marked/Rel-16/23_series/23976/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4a1e3bdf22217af37364b3b855af99babbef3cd --- /dev/null +++ b/marked/Rel-16/23_series/23976/e928f4874ed492d3ad4c6fa2d29aedbc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a49dd8077d8078a23b7e78311a590301e02274b7e718fa8bbd537363b67136e +size 49416 diff --git a/marked/Rel-16/23_series/23977/1c953f32bd34345dfd68fddf8a3736d6_img.jpg b/marked/Rel-16/23_series/23977/1c953f32bd34345dfd68fddf8a3736d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..586a9be7e2dfc87f26165a4ba3e7d9b2ebc2f90a --- /dev/null +++ b/marked/Rel-16/23_series/23977/1c953f32bd34345dfd68fddf8a3736d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:273d3d3e686226cc6fcfa3c7ed43b5a0b8176ad0faa8c835b73b10777e54ce8f +size 11847 diff --git a/marked/Rel-16/23_series/23977/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg b/marked/Rel-16/23_series/23977/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0cdadf3ae48fdfb8d3a0ccdb9a7d535f5cdf2d3 --- /dev/null +++ b/marked/Rel-16/23_series/23977/1d27fed9c01eb99f6535283f35fe3bbf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35112aa990e69cf9a3998155fc74c474a6753aca8446237136f475cc23b87d91 +size 102369 diff --git a/marked/Rel-16/23_series/23977/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/marked/Rel-16/23_series/23977/33a8f3f01dfa8bce75d23017855a13c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c886ec022633bb5af5aec0b8b9e3ee733b5e77e --- /dev/null +++ b/marked/Rel-16/23_series/23977/33a8f3f01dfa8bce75d23017855a13c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84cdaf40272ac6768785cf94114a24cb7f1c170e280d1063ef747d1d0c897a35 +size 86198 diff --git a/marked/Rel-16/23_series/23977/47e8c2042061e08a14e012472e9fdbaa_img.jpg b/marked/Rel-16/23_series/23977/47e8c2042061e08a14e012472e9fdbaa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a577df888dcd9304f0a2ff8e16f68bb8b3100828 --- /dev/null +++ b/marked/Rel-16/23_series/23977/47e8c2042061e08a14e012472e9fdbaa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:518253dd18ccc572f6e4baff6d36677570715fc90bcef8becc7bdfbf6af63d2e +size 8249 diff --git a/marked/Rel-16/23_series/23977/54a53f959bb7758332532c1cd5f0ad75_img.jpg b/marked/Rel-16/23_series/23977/54a53f959bb7758332532c1cd5f0ad75_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..08b56d4b1ee40da0322ee7b9e03d2151485dafe5 --- /dev/null +++ b/marked/Rel-16/23_series/23977/54a53f959bb7758332532c1cd5f0ad75_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14af1a5ec36375238dc0855e2a7eec336f19cecceddc01434b4f062e4f42b3b5 +size 37771 diff --git a/marked/Rel-16/23_series/23977/68ca7669d38a3c31f5a2c3a06fa802e3_img.jpg b/marked/Rel-16/23_series/23977/68ca7669d38a3c31f5a2c3a06fa802e3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..336ab50be53218d27228f449424bc5fe5afb76f9 --- /dev/null +++ b/marked/Rel-16/23_series/23977/68ca7669d38a3c31f5a2c3a06fa802e3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ec036542797d2e6962025d27ad7222ac6694f9aa38cadf0103c297b70ff0f33 +size 10042 diff --git a/marked/Rel-16/23_series/23977/70de8885bd7de15723aaad5eb5c5febf_img.jpg b/marked/Rel-16/23_series/23977/70de8885bd7de15723aaad5eb5c5febf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8eeaa4fb4621ce926bd3cd827616e9cf2f5d393 --- /dev/null +++ b/marked/Rel-16/23_series/23977/70de8885bd7de15723aaad5eb5c5febf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ec7a67151abf23db3f8fb2aaf52821d95de08a89c2c41054b567bd012684c29 +size 124762 diff --git a/marked/Rel-16/23_series/23977/768b8ab0d55761b205087c079df1e6e6_img.jpg b/marked/Rel-16/23_series/23977/768b8ab0d55761b205087c079df1e6e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..feba53e3967d0751e939239bc14e9aaa37177b28 --- /dev/null +++ b/marked/Rel-16/23_series/23977/768b8ab0d55761b205087c079df1e6e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae44fcf2cf5612d9583a7d05fbf2897b6e8972798b7f7e9e35354a9a78b39493 +size 122583 diff --git a/marked/Rel-16/23_series/23977/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/marked/Rel-16/23_series/23977/7a0db9703b68b3d06cdaeefc084c0006_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ffe39ec62cf790517edd4bd85aeb7d560b8cc62c --- /dev/null +++ b/marked/Rel-16/23_series/23977/7a0db9703b68b3d06cdaeefc084c0006_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7994dd5637058d112c3fde15d185e112b652e3db1b7f6df941c048e4bc1f10e9 +size 69759 diff --git a/marked/Rel-16/23_series/23977/7a207f7bb5a20f849aee089439e24a84_img.jpg b/marked/Rel-16/23_series/23977/7a207f7bb5a20f849aee089439e24a84_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15972a579ec89bce21dd515ba66de2f0599076a4 --- /dev/null +++ b/marked/Rel-16/23_series/23977/7a207f7bb5a20f849aee089439e24a84_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:522e3037cbdd456cae7bc3c6c5290e2e9a9cf8b5106282075af7ed1592550b11 +size 123240 diff --git a/marked/Rel-16/23_series/23977/895d588a848d9963890c938763de9ecf_img.jpg b/marked/Rel-16/23_series/23977/895d588a848d9963890c938763de9ecf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2b3e20cc1b9636f56c01cb37e076ab036204f75 --- /dev/null +++ b/marked/Rel-16/23_series/23977/895d588a848d9963890c938763de9ecf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e0b88be64b54bcffd6d53ff6aed27a7f089c70584264f33bbc74cbcc94124b9 +size 50048 diff --git a/marked/Rel-16/23_series/23977/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/Rel-16/23_series/23977/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5c290fe1e972bed927bfa2007131ac995407775 --- /dev/null +++ b/marked/Rel-16/23_series/23977/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce343e15bc91809779ba816d2a03e846a207e444ca6c6d1a3862bc12f0953819 +size 91524 diff --git a/marked/Rel-16/23_series/23977/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/Rel-16/23_series/23977/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b83c3022453a510785c93eb66cf178b7197b14d --- /dev/null +++ b/marked/Rel-16/23_series/23977/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:154498c4cbbd8f4194a7de636d722ea26d895cb5a3cbb09e179a0445235b5170 +size 135275 diff --git a/marked/Rel-16/23_series/23977/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/marked/Rel-16/23_series/23977/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ec78dc382fc3594de4ec362f42f47f70c589210 --- /dev/null +++ b/marked/Rel-16/23_series/23977/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38076e623f91999bf4b1fb7429b7fa468d1e20bd4a59ae4631e7eb259887bad2 +size 63812 diff --git a/marked/Rel-16/23_series/23977/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg b/marked/Rel-16/23_series/23977/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1df216c66f741c8c692462778de073e978f5bec --- /dev/null +++ b/marked/Rel-16/23_series/23977/a24e89a6fe9bb70c83f8bf5202baba95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac65dea98b105fb0b089a96218e2a322d956da9e26aed133fd485580416b2437 +size 82153 diff --git a/marked/Rel-16/23_series/23977/a6cf7c02a60c336e0934b5ea40e35b49_img.jpg b/marked/Rel-16/23_series/23977/a6cf7c02a60c336e0934b5ea40e35b49_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40fdaa162f560fb3180629beecab07629a716fc7 --- /dev/null +++ b/marked/Rel-16/23_series/23977/a6cf7c02a60c336e0934b5ea40e35b49_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:36b4077fed86c4ad789dabedd0a94c0a29744b89b77c86f1c6c6cb377f8ab128 +size 18257 diff --git a/marked/Rel-16/23_series/23977/ace13edeb79bdfa129ed84fbb4ac44e5_img.jpg b/marked/Rel-16/23_series/23977/ace13edeb79bdfa129ed84fbb4ac44e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ef9ed522c37e2560b5a4a5d48e3b9e0b96fcf3d --- /dev/null +++ b/marked/Rel-16/23_series/23977/ace13edeb79bdfa129ed84fbb4ac44e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:463a442b12a64a066f0f65d6a601c7a9fd480e2b6ce20b481512328801d3619c +size 2325 diff --git a/marked/Rel-16/23_series/23977/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/marked/Rel-16/23_series/23977/af6be343f0c0a8f155f965dcf337b8af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ce31fee0b731739b4c11cb51140fc2c1d2c8f2b --- /dev/null +++ b/marked/Rel-16/23_series/23977/af6be343f0c0a8f155f965dcf337b8af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8faa693001bdad188b564bb63a86cba419cf90d23d43dd9ddece8618df1bba12 +size 120913 diff --git a/marked/Rel-16/23_series/23977/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Rel-16/23_series/23977/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f5f558001f59939e7ee96a6ddab9cda0ca4ea8a --- /dev/null +++ b/marked/Rel-16/23_series/23977/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ed45587dacf420433b51ab8c794412bfbeb09b405118a199daa30fcccc18a0a +size 120393 diff --git a/marked/Rel-16/23_series/23977/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/marked/Rel-16/23_series/23977/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e548e996a138ee61b0413191340b7d693184d80e --- /dev/null +++ b/marked/Rel-16/23_series/23977/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6fa399c224fb9a93520c3682503296c1724eaa80d532b788a98735a1fc4a429b +size 122498 diff --git a/marked/Rel-16/23_series/23977/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/marked/Rel-16/23_series/23977/c78c2eefd86269d1740ab85a916f24f2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78ef334f49111c2f3d2530a7846c5d0e4b580911 --- /dev/null +++ b/marked/Rel-16/23_series/23977/c78c2eefd86269d1740ab85a916f24f2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:27fad17085f6b42641525c1dcf397f5ec9e6a55a4cfba0b0dbaa541e7086cc54 +size 124273 diff --git a/marked/Rel-16/23_series/23977/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg b/marked/Rel-16/23_series/23977/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1a0dc23dfc136571c2529aa3103a1b93d1bdbe1 --- /dev/null +++ b/marked/Rel-16/23_series/23977/ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de6aa4c17c20275a2ea78f32526657b17eba5c7d3ad49acd91983c9d6cc3da3b +size 14230 diff --git a/marked/Rel-16/23_series/23977/d244183a8ff3d94b0dcf30140f51020d_img.jpg b/marked/Rel-16/23_series/23977/d244183a8ff3d94b0dcf30140f51020d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a79b84e4a11e0646ecca927b32e2797eab024cb7 --- /dev/null +++ b/marked/Rel-16/23_series/23977/d244183a8ff3d94b0dcf30140f51020d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97566a9b2bf52b3b86aedad79886f612ed98d619ff1cfd9338373818c97e1eaa +size 122429 diff --git a/marked/Rel-16/23_series/23977/d62e2e2281009c16f4ee61660e716cd9_img.jpg b/marked/Rel-16/23_series/23977/d62e2e2281009c16f4ee61660e716cd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..557d41417ed11f477055308858dae1fde8c7e1d8 --- /dev/null +++ b/marked/Rel-16/23_series/23977/d62e2e2281009c16f4ee61660e716cd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8a1613001ed770f9727b3eca12371e57fe8f6506bf245248433de3002eac553 +size 42196 diff --git a/marked/Rel-16/23_series/23977/d793cf7c174b89eb024d132f00679787_img.jpg b/marked/Rel-16/23_series/23977/d793cf7c174b89eb024d132f00679787_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c979adfc5a4cc3b01a9caf7e93239012a4fa9631 --- /dev/null +++ b/marked/Rel-16/23_series/23977/d793cf7c174b89eb024d132f00679787_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc59d2c2c2d361f49ebf919263bee4930676159726f514856c94169a2ebede24 +size 9371 diff --git a/marked/Rel-16/23_series/23977/d980a3f9608055996a07f31788baf827_img.jpg b/marked/Rel-16/23_series/23977/d980a3f9608055996a07f31788baf827_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b57502cae3d15b2a2f758d4293eef365664e2667 --- /dev/null +++ b/marked/Rel-16/23_series/23977/d980a3f9608055996a07f31788baf827_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e44cf9f47fd7fe5686d8286f580c0fa9de12e17672189f9bc8aa40ae4078b126 +size 33557 diff --git a/marked/Rel-16/23_series/23977/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/Rel-16/23_series/23977/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19895e5d13e0f8e92effe680a94ce7f36e0c977e --- /dev/null +++ b/marked/Rel-16/23_series/23977/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71eafbfa92604e1672216adf779ae5c444f7ac1f1145e811008669eea3a03ecf +size 135550 diff --git a/marked/Rel-16/23_series/23977/raw.md b/marked/Rel-16/23_series/23977/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..4375f35daf9781893cd213370c38f056ca99a330 --- /dev/null +++ b/marked/Rel-16/23_series/23977/raw.md @@ -0,0 +1,1614 @@ +# Contents + +| | | +|----------------------------------------------------------------------------------|----| +| Contents..... | 3 | +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 Network deployment scenarios to be studied ..... | 8 | +| 4.1 GSM network architecture before Release 4..... | 8 | +| 4.2 UMTS network architecture in Release 99 ..... | 9 | +| 4.3 Packet transport network between MGWs in an A/Iu mode BICN..... | 10 | +| 4.4 TDM transit network between A/Iu mode PLMNs..... | 11 | +| 4.5 Packet transport transit network between PLMNs..... | 12 | +| 5 Call Scenarios to be studied..... | 14 | +| 5.1 Mobile to Mobile call Scenarios ..... | 15 | +| 5.1.1 BSC to RNC call via BICN..... | 15 | +| 5.1.2 BSC to BSC call via BICN..... | 16 | +| 5.1.3 RNC to BSC call via BICN..... | 18 | +| 5.1.4 RNC to RNC call via BICN ..... | 19 | +| 5.2 Mobile to PSTN call scenarios..... | 21 | +| 5.2.1 BSC to PSTN call via BICN ..... | 21 | +| 5.2.2 RNC to PSTN call via BICN..... | 23 | +| 5.3 Roaming and multi-network call scenarios..... | 24 | +| 5.3.1 BSC (HPLMN) to BSC (VPLMN) call..... | 24 | +| 5.3.2 BSC (HPLMN) to RNC (VPLMN) call ..... | 24 | +| 5.3.3 RNC (HPLMN) to BSC (VPLMN) call ..... | 24 | +| 5.3.4 RNC (HPLMN) to RNC (VPLMN) call ..... | 25 | +| 5.4 CS domain to IMS interworking scenario..... | 25 | +| 5.5 A selection of handover scenarios..... | 25 | +| 5.5.1 BSC to BSC call via BICN with Intra GERAN handover AMR-AMR..... | 25 | +| 5.5.2 BSC to BSC call via BICN with Intra GERAN handover to AMR - EFR..... | 27 | +| 5.5.3 BSC to BSC call via BICN: second Handover to EFR – AMR – EFR..... | 28 | +| 5.5.4 BSC to BSC call via BICN: third handover to AMR – EFR – EFR ..... | 29 | +| 5.5.5 RNC to RNC call via BICN with inter-system handover..... | 30 | +| 5.5.6 BSC to RNC call via BICN with second intersystem handover ..... | 31 | +| 6 General requirements for architectural solutions ..... | 31 | +| 6.1 Overall requirements ..... | 31 | +| 6.2 Status of specifications for TFO and TrFO in 3GPP ..... | 32 | +| 6.2.1 Support of codec types in TFO and TrFO on various interfaces..... | 32 | +| 7 Requirements and architectural solutions for Resource Savings ..... | 32 | +| 7.1 AMR-NB configurations..... | 33 | +| 7.2 AMR-WB configurations..... | 33 | +| 8 Requirements and architectural solutions for bandwidth savings..... | 34 | +| 8.1 Background ..... | 34 | +| 8.2 Requirements..... | 34 | +| 8.3 Architectural solutions ..... | 35 | +| 8.3.1 A-ter interface to the MGW..... | 35 | +| 8.3.2 MGW collocated with TRAUs ..... | 36 | +| 9 Requirements and architectural solutions for speech quality Improvements ..... | 36 | +| 9.1 Requirements..... | 36 | +| 9.2 Architectural solutions ..... | 37 | + +| | | | +|-----------------|---------------------------------------------------------------------------------------------------|-----------| +| 9.2.1 | Mobile to mobile calls scenarios: 5.1.1 and 5.1.3 ..... | 37 | +| 9.2.2 | Mobile to PSTN calls: scenarios 5.2.x ..... | 37 | +| 9.3 | Summary ..... | 37 | +| 10 | Requirements and architectural solutions for avoiding duplication in transcoder development ..... | 37 | +| 10.1 | Background and requirements..... | 37 | +| 10.2 | Architectural solutions ..... | 38 | +| 10.2.1 | A-ter interface to the MGW..... | 38 | +| 10.2.1.1 | Description / concept..... | 38 | +| 10.2.1.2 | Difficulties with this concept..... | 38 | +| 10.2.1.3 | Migration aspects..... | 39 | +| 10.2.1.4 | Sample message flow..... | 41 | +| 11 | Conclusions..... | 43 | +| <b>Annex A:</b> | <b>Example for migrating a service to TrFO .....</b> | <b>44</b> | +| A.1 | Service description..... | 44 | +| A.2 | Realization ..... | 44 | +| A.2.1 | Overview ..... | 44 | +| A.2.2 | High level description ..... | 44 | +| A.2.3 | Message flow for a Release 99 network..... | 45 | +| A.2.4 | Message flow with BICC and TrFO ..... | 48 | +| A.2.5 | Message flow with split architecture without TrFO..... | 50 | +| A.2.6 | Message flow with split architecture and TrFO ..... | 52 | +| A.3 | Summary and conclusions ..... | 53 | +| Annex B: | Change history ..... | 54 | + +# --- Foreword + +This Technical Report has been produced by the 3<sup>rd</sup> 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. + +# --- 1 Scope + +The objective of this technical report is to identify the full set of requirements for bandwidth and resource savings and improved speech quality, with specific consideration to networks supporting A/Gb mode and the bearer independent circuit-switched core network (BICN). The different architectural solutions to meet these requirements will be assessed. + +Consideration shall be made to existing architectures and solutions to provide harmony between 2G nodes, UMTS nodes and external networks (PSTN/ISDN). Backward compatibility to existing solutions and ease of network introduction/upgrade shall be given high importance. + +# --- 2 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 TS 23.002: "Network architecture". +- [2] 3GPP TS 23.153: "Out of band transcoder control; Stage 2". +- [3] 3GPP TS 23.053: "Tandem Free Operation (TFO); Service description; Stage 2". +- [4] 3GPP TS 28.062: "Inband Tandem Free Operation (TFO) of speech codecs; Service description; Stage 3". +- [5] 3GPP TS 26.103: "Speech codec list for GSM and UMTS". +- [6] 3GPP TR 26.975: "Performance Characterization of the AMR Speech Codec". +- [7] 3GPP TR 26.976: "Performance characterization of the Adaptive Multi-Rate Wideband (AMR-WB) speech codec". +- [8] 3GPP TS 26.102: "Mandatory speech codec; Adaptive Multi-Rate (AMR) speech codec; Interface to Iu, Uu and Nb". +- [9] Void. +- [10] 3GPP TS 48.060: "In-band control of remote transcoders and rate adaptors for full rate traffic channels". +- [11] 3GPP TS 48.061: "In band control of remote transcoders and rate adaptors for half rate traffic channels". +- [12] 3GPP TS 52.021: "Network Management (NM) procedures and messages on the A-bis interface". +- [13] 3GPP TS 29.163: "Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks". +- [14] ITU-T Recommendation Q.1912.5: "BICC SIP Interworking". +- [15] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [16] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". + +- [17] 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC-BSS) interface; Layer 3 specification". +- [18] 3GPP TS 26.101: "Mandatory speech codec speech processing functions; Adaptive Multi-Rate (AMR) speech codec frame structure". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the definitions in TR 21.905 [15] apply as well as the following terms and definitions. + +**Bearer Independent Core Network :** This term refers to a core network (CN) comprised of MSC Server, CS-MGW and GMSC Server nodes to support MSC and GMSC functionality, as defined in TS 23.002 [1]. + +**Codec Configuration :** The Codec Configuration of a codes type ,like AMR, includes mainly the Active Codec Set, the setting of the OM flag and DTX parameters, etc. + +**MIPS:** Mega (Million) Instructions Per Second. This is a measure for the required DSP capacity. It is here in this context related to the "ETSI-DSP" as defined in 3GPP SA4 for the complexity characterisation of the 3GPP Speech Codec algorithms. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|------|-----------------------------------------------------------------------------------------------------------------------| +| Ater | the reference point internal to the BSC functional entity, between the transcoders and the rest of the BSC functions. | +| Abis | interface between the BTS and the BSC | + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations in TR 21.905 [15] apply as well as the following abbreviations: + +| | | +|-------|---------------------------------| +| BICN | Bearer Independent Core Network | +| BICC | Bearer Independent Call Control | +| DSP | Digital Signal Processor | +| DC | Decoding | +| MSC-S | MSC Server | +| OoBTC | Out of Band Transcoder Control | +| PT | TFO Protocol Termination | +| R | Reframing | +| TC | Transcoding | +| UP | User Plane Termination | + +# 4 Network deployment scenarios to be studied + +## 4.1 GSM network architecture before Release 4 + +![Diagram of GSM Network Architecture before release 4 showing PSTN, PoI A, BSC A, TRAU Trans-Coder A, MSC A, MSC B, TRAU Trans-Coder B, BSC B, and PoI B. It illustrates the flow of call control signalling (dashed lines) and user plane traffic (solid lines) over ISUP, TDM, and Ater interfaces.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +The diagram illustrates the GSM network architecture before Release 4. At the top, two PSTN blocks are shown, connected to the network via Points of Interconnect (PoI A and PoI B). Below the PSTN, the network consists of two Base Station Controllers (BSC A and BSC B) connected to two Mobile Switching Centers (MSC A and MSC B). Each BSC is connected to a TRAU Trans-Coder (TRAU Trans-Coder A and TRAU Trans-Coder B). The TRAU Trans-Coders are connected to the MSCs via the Ater interface. The MSCs are interconnected via ISUP and TDM links. The TDM links are used for speech traffic at 64 kb/s. The legend indicates that dashed lines represent Call Control Signalling, solid lines represent the Ater Interface, and thick solid lines represent the A and TDM Interface at 64 kb/s. + +Diagram of GSM Network Architecture before release 4 showing PSTN, PoI A, BSC A, TRAU Trans-Coder A, MSC A, MSC B, TRAU Trans-Coder B, BSC B, and PoI B. It illustrates the flow of call control signalling (dashed lines) and user plane traffic (solid lines) over ISUP, TDM, and Ater interfaces. + +PoI: Point of Interconnect + +**Figure 4.1-1: GSM Network Architecture before release 4** + +In GSM networks according to releases before release 4 the MSCs are interconnected on the user plane by TDM links (real or virtual) with 64 kb/s for speech traffic. The only speech codec type known between MSCs is G.711 'PCM'. There are typically several Points-of-Interconnect to the underlying PSTN, with 64kb/s for the speech traffic in PCM. The MSCs control and interconnect the BSCs via the A-Interface (user plane and control plane), but they have no direct influence on the Codec Type selected by the BSC on the GSM radio access. The MSC can make a suggestion on the Codec Type, but the BSC decides finally. The MSCs have no means at all to signal the Codec Configuration to the BSCs or between MSCs. This is a drawback. + +The transcoders belong logically to the GSM\_BSS. Speech is transported on the Ater interface in compressed form using the same codec type and configuration as on the radio interface. + +Tandem Free Operation (TFO) is defined on PCM links for all GSM Codec Types. TFO allows by inband signalling to 'tunnel' the compressed speech through the TDM core network. TFO provides the possibility to bypass and omit the encoding functions, saves DSP resources, improves the speech quality in mobile-mobile calls, allows new speech services like wideband speech, but does not provide transmission cost saving. + +## 4.2 UMTS network architecture in Release 99 + +![Diagram of UMTS network architecture in Release 99 showing PSTN, PoI, RNC, and MSC components and their interfaces.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) + +The diagram illustrates the UMTS network architecture in Release 99. It shows two PSTN networks connected via Points of Interconnect (PoI A and PoI B) to a central mobile core network. The core network consists of two MSCs (MSC A and MSC B) interconnected by TDM links. Each MSC is connected to an RNC (RNC A and RNC B) via Iu interfaces. Transcoders are located within each MSC. The legend indicates that dashed lines represent Call Control Signalling (ISUP), thin solid lines represent the Iu Interface, and thick solid lines represent the TDM Interface (64kb/s). + +Diagram of UMTS network architecture in Release 99 showing PSTN, PoI, RNC, and MSC components and their interfaces. + +**PoI: Point of Interconnect** + +**Figure 4.2-1: UMTS network architecture in Release 99** + +In UMTS networks according to release 99 the MSCs are interconnected on the user plane by TDM links (real or virtual) with 64 kb/s for speech traffic. The only speech codec type known between MSCs is G.711 'PCM'. There are typically several Points-of-Interconnect to the underlying PSTN, with 64kb/s for the speech traffic in PCM. + +The MSCs control and interconnect the RNCs via the Iu-Interface (user plane and control plane). + +The MSC selects and commands the Codec Type on the UTRAN radio access and makes a suggestion on the Codec Configuration, but the RNC can select a sub-configuration. + +The Transcoders are located on central places physically and logically 'inside' the mobile core network as integral parts of the MSCs. They are controlled by the MSCs via internal interfaces. But also the RNC controls the transcoder via the Iu interface (Iu\_Init). Speech is transported on the Iu-interface in compressed form using the same codec type and configuration as on the radio interface. + +The MSCs have no means at all to signal the Codec Configuration between MSCs. This is a drawback. + +Tandem Free Operation (TFO) is defined on PCM links for all UMTS Codec Types (there is only UMTS\_AMR and UMTS\_AMR2). TFO allows by inband signalling to 'tunnel' the compressed speech through the TDM core network. TFO provides the possibility to bypass and omit the encoding functions, saves DSP resources, improves the speech quality in mobile-mobile calls, allows new speech services like wideband speech, but does not provide transmission cost saving. It is possible to have a combined GSM/UMTS core network with MSCs supporting both the Iu interface towards RNCs and the A-interface towards BSCs. + +## 4.3 Packet transport network between MGWs in an A/Iu mode BICN + +NOTE: Since we consider only speech telephony services in this TR the Gb interface has no relevance. + +![Diagram of a Bearer Independent Core Network (BICN) architecture showing connections between PSTN, MSC-S, MGW, TRAU, BSC, and RNC components.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +The diagram illustrates a Bearer Independent Core Network (BICN) architecture. At the top, two PSTN blocks are connected via Points of Interconnect (PoI A and PoI B) to MSC-S A and MSC-S B respectively. These MSC-Ss are interconnected by an Nc interface. Below each MSC-S is an MGW (MGW A and MGW B) connected via an Iu interface. The MGWs are also connected to the MSC-Ss via Mc interfaces. Each MGW is connected to a TRAU Trans-Coder (TRAU Trans-Coder A and TRAU Trans-Coder B) via an Ater interface. The TRAUs are connected to BSCs (BSC A and BSC B) via Ater interfaces. Each MGW is also connected to a Trans-Coder (Trans-Coder A' and Trans-Coder B') via an Iu interface. The Trans-Coders are connected to RNCs (RNC A and RNC B) via Iu interfaces. The Trans-Coders are also connected to the MGWs via Nb interfaces. A legend at the bottom defines the interface types: dashed lines for Call Control Signalling, thin solid lines for Ater Interface, thick solid lines for A and TDM Interface: 64kb/s, and medium solid lines for Iu and Nb Interface. PoI is defined as Point of Interconnect. + +Diagram of a Bearer Independent Core Network (BICN) architecture showing connections between PSTN, MSC-S, MGW, TRAU, BSC, and RNC components. + +**Figure 4.3-1: Bearer Independent Core Network with A- and Iu-interfaces from Release 4 onwards** + +The mobile Core Network from release 4 onwards has a layered architecture with BICC and OoBTC/TrFO on the Nc/Nb interface or TFO on the Nb interface and provides the means to transport speech in compressed form on the Nb interface. + +The MSC-Ss know, negotiate and select the speech Codec Types and Configurations on the Iu interfaces. The MSC-Ss also know, negotiate and select speech Codec Types and Configurations on the Nb Interface. + +- This may lead to Transcoder free operation (TrFO) with compressed speech at the Nb interface. +- If the MSC-Ss determine G.711 as the codec used between the MGWs, then the MGWs may afterwards establish TFO at the Nb interface. In this case the transcoders in the MGWs know and negotiate the speech codec configuration on the Nb interface, and they inform the MSC-Server of this configuration indicating that TFO is possible. If the transcoder is in the BSCs, the BSCs know and select the speech codec type and configuration on the A-ter interface to enable TFO operation on the A interface. + +The RNC accepts the commanded Codec Type and Configuration. + +The MSC-Ss suggest also the speech Codec Type to be used on the Ater interface, but the BSC has the final decision and determines the initial Codec Type and Configuration for the GSM radio interface and the Ater interface. The MSC-Ss cannot communicate the preferred Codec Configuration to the BSCs in a direct way. The MSC-Ss can discover the Codec Type and Configuration from the BSCs via the TFO procedures at the corresponding MGW. The MSC-Ss can then direct interworking procedures between TFO on an A interface or other TDM link and either OoBTC or TFO associated with an Nb interface to optimally allocate the speech transcoder functions. + +The MGWs host the transcoding and interworking between compressed speech on Nb or Iu and the legacy 'PCM' with or without TFO on A and TDM interfaces. Points-of-Interconnect to the PSTN are typically provided at every MGW. MGWs may be geographically distributed to minimise the length of the speech path inside the PSTN. + +Bandwidth efficient transmission is always provided on the Ater- and on the Iu-interfaces, where the Iu allows a slightly higher efficiency in DTX due to its packet based transport structure (ATM or IP). + +The bandwidth efficiency on the Nb-Interface depends on the selected Codec Type. It can be as on Iu (when TrFO is used) or it can be 64kb/s for G.711. In the latter case, the bandwidth efficiency on the Nb-interface is always 64kb/s for PCM, even when a compressed Codec Type has been selected by using TFO. This is a drawback. + +OoBTC may lead to a Transcoder free Operation (TrFO) with high bandwidth efficiency on all user planes for UE-to-UE calls. For UE-to-PSTN calls at least the major part of the speech path can be realised in compressed form (TrFO-link, Transcoder at the Edge of the CN). + +For any call transiting the Nb interface, both OoBTC and TFO procedures may apply. Harmonization procedures between OoBTC and TFO provide the necessary interworking, achieving the same speech quality benefits provided separately by either TrFO or TFO. OoBTC and TFO for MS-to-UE and MS-to-MS calls that traverse a packet transport network over Nb may lead to a combination of TrFO/TFO and TFO operation on the Nb and A interface / TDM portions of the speech path, respectively, with high bandwidth efficiency on all but the A interface and TDM portions of the speech path, except when TFO is used over Nb interface. OoBTC and TFO for MS-to-PSTN calls that traverse a packet transport network over Nb may also provide for high bandwidth efficiency on any Ater, Iu and Nb portions of the speech path, except when TFO is used over Nb interface. + +## 4.4 TDM transit network between A/Iu mode PLMNs + +![Diagram of a TDM transit network between two PLMNs (A and B) in A/Iu mode. The diagram shows two mobile Core Networks (BICNs) connected via a TDM link between MGW A2 and MGW B2. Each BICN contains an MSC-S (A1, A2, B2, B1), MGWs (A1, A2, B2, B1), and Transcoders (A'1, A'2, B'2, B'1). The network is connected to PSTN at PoI A and PoI B via ISUP and TDM interfaces. Call control signalling is shown as dashed lines, Ater interfaces as solid lines, and A and TDM interfaces as thick solid lines (64kb/s).](c78c2eefd86269d1740ab85a916f24f2_img.jpg) + +Legend: + +- Call Control Signalling +- Ater Interface +- A and TDM Interface: 64kb/s + +Pol: Point of Interconnect + +Diagram of a TDM transit network between two PLMNs (A and B) in A/Iu mode. The diagram shows two mobile Core Networks (BICNs) connected via a TDM link between MGW A2 and MGW B2. Each BICN contains an MSC-S (A1, A2, B2, B1), MGWs (A1, A2, B2, B1), and Transcoders (A'1, A'2, B'2, B'1). The network is connected to PSTN at PoI A and PoI B via ISUP and TDM interfaces. Call control signalling is shown as dashed lines, Ater interfaces as solid lines, and A and TDM interfaces as thick solid lines (64kb/s). + +**Figure 4.4-1: TDM Transit network between PLMNs from Release 4 onwards** + +This architecture shows two mobile Core Networks (BICNs) of Release 4 or 5 in layered architecture, with BICC and OoBTC on the Nc interface or TFO on the Nb interface and speech in compressed form on the Nb interface, connected by a legacy ISUP signalling and TDM with 64kb/s for speech (G.711). All features as explained above for one BICN are of course valid inside each BICN and are not further reprinted here in all details. + +TFO on the TDM interface between the BICNs (here between MGW A2 and MGW B2) can be used to exchange the compressed speech parameters between both BICNs. By that, end-to-end transcoding free operation is possible in any combination of mobile-to-mobile calls, provided that no In-Path\_Equipment prevents the establishment of TFO on these links. Also "Transcoder at the edge" can be provided in any combination of mobile-to-PSTN calls, regardless whether the Point-of-Interconnect to the PSTN is inside the BICN where the mobile is connected, or in the other BICN. Cost efficient transmission is possible within each BICN, but of course not (directly) on the TDM link between the BICNs, + +except when TFO is used on Nb interface. The resulting speech quality should be identical to the one achievable within one BICN. In all call scenarios the optimal speech quality can be achieved. + +Within each BICN, for TrFO, the MSC-Ss know, negotiate and select the speech Codec Types and Configurations on the Nb and Iu interfaces and suggest also the speech Codec Type to be used on the Ater interface. + +- This may lead to Transcoder free operation (TrFO) with compressed speech at the Nb interface. +- If the MSC-Ss determine G.711 as the codec used between the MGWs, then the MGWs may afterwards establish TFO at the Nb interface. In this case the transcoders in the MGWs know and negotiate the speech codec configuration on the Nb interface, and they inform the MSC-Server of this configuration indicating that TFO is possible. If the transcoder is in the BSCs, the BSCs know and select the speech codec type and configuration on the A-ter interface to enable TFO operation on the A interface. + +For TrFO, the MSC-Ss of one BICN cannot negotiate Speech Codec Type/Configuration directly with the MSC-Ss of the other BICN due to the ISUP connection between them. OoBTC-signalling therefore ends at the border MGWs (here MGW A2 and MGW B2). TFO inband signalling connects both BICNs and provides OoBTC-compatible means to exchange the Codec Lists and to identify the optimal Codec Type and Configuration. In this way a complete end-to-end Codec List negotiation is achieved. + +The main difference between OoBTC- and TFO-signalling is, that one is performed before call setup and the other immediately after call setup. As both Core Networks could select different, incompatible Codec Types/Configurations that TFO cannot in all cases establish immediately. The Codec Mismatch situation and the Optimal Codec Type/Configuration gets known to both BICNs by TFO signalling and then it might be required that one or both BICNs perform an In-Call-Modification of the Codec Type/Configuration to achieve end-to-end transcoding free transport. + +It may be noted here for completeness that also "inside" the ISUP/TDM connection between the shown BICNs another BICN may be "hidden" with TFO capability to the external world. This hidden BICN could have the same OoBTC and Codec Types/Configurations and by that support high bandwidth efficiency on long trunks without any loss of speech quality. + +## 4.5 Packet transport transit network between PLMNs + +![Diagram of packet transport transit network between PLMNs of REL5. The diagram shows two PLMNs (A and B) connected via a transit network. PLMN A includes PSTN (PoI A), BSC A, RNC A, TRAU Trans-Coder A, MGW A1, MGW A2, Trans-Coder A'1, and Trans-Coder A'2. PLMN B includes PSTN (PoI B), BSC B, RNC B, TRAU Trans-Coder B, MGW B1, MGW B2, Trans-Coder B'1, and Trans-Coder B'2. The transit network consists of MSC-S A1, MSC-S A2, MSC-S B2, and MSC-S B1. Connections are labeled with ISUP, TDM, Ater, Nb, Nb FP, Iu, Mc, and Nc. A legend at the bottom defines the line types: dashed for Call Control Signalling, solid for Ater Interface, and thick solid for A and TDM Interface: 64kb/s. PoI is defined as Point of Interconnect.](af6be343f0c0a8f155f965dcf337b8af_img.jpg) + +Legend: + +- Call Control Signalling +- Ater Interface +- A and TDM Interface: 64kb/s + +PoI: Point of Interconnect + +Diagram of packet transport transit network between PLMNs of REL5. The diagram shows two PLMNs (A and B) connected via a transit network. PLMN A includes PSTN (PoI A), BSC A, RNC A, TRAU Trans-Coder A, MGW A1, MGW A2, Trans-Coder A'1, and Trans-Coder A'2. PLMN B includes PSTN (PoI B), BSC B, RNC B, TRAU Trans-Coder B, MGW B1, MGW B2, Trans-Coder B'1, and Trans-Coder B'2. The transit network consists of MSC-S A1, MSC-S A2, MSC-S B2, and MSC-S B1. Connections are labeled with ISUP, TDM, Ater, Nb, Nb FP, Iu, Mc, and Nc. A legend at the bottom defines the line types: dashed for Call Control Signalling, solid for Ater Interface, and thick solid for A and TDM Interface: 64kb/s. PoI is defined as Point of Interconnect. + +Figure 4.5-1: Packet transport transit network between PLMNs of REL5 + +This architecture shows two mobile Core Networks (BICNs) of Release 4 or 5 in layered architecture, with BICC and OoBTC on the Nc interface and speech in compressed form on the Nb interface. They are connected by a packet network, using the signalling and user plane protocols, which are used with the BICNs. All features as explained above for one BICN are of course valid inside each BICN and are not further reprinted here in all details. Indeed, in this scenario all features apply across network borders: OoBTC and TrFO can take place all along the path in the core networks, resulting in compressed speech with high bandwidth efficiency on all user planes for UE-to-UE calls even across PLMN borders. + +The description above indicates that the user plane protocols are used inter- PLMN. The user plane interconnecting the two BICNs may alternately use standard IETF framing protocols when configured over IP transport. TS 29.007 [16] currently does not describe the use of BICC inter-PLMN. + +In the transit network where other protocols than BICC with OoBTC are used (e.g. ISUP), then in some cases OoBTC and TrFO can not apply across network borders and bandwidth efficiency can not be achieved across PLMN borders. To achieve such efficiency would require a mechanism which did not rely on BICC and provided compressed speech still. + +![Figure 4.5-2: Packet transport transit network between PLMNs of REL5, using SIP between PLMNs. The diagram shows two PLMNs, PLMN A and PLMN B, connected via a central packet network. PLMN A includes a PSTN (PoI A) connected to an MSC-S (A1) via ISUP/TDM. MSC-S (A1) is connected to MSC-S (A2) via Nc. MSC-S (A2) is connected to the packet network via SIP. PLMN B includes a PSTN (PoI B) connected to an MSC-S (B1) via ISUP/TDM. MSC-S (B1) is connected to MSC-S (B2) via Nc. MSC-S (B2) is connected to the packet network via SIP. Both PLMNs include BSCs and RNCs connected to MGWs (A1, A2, B1, B2) via Ater and Iu interfaces. MGWs are connected to Trans-Coders (A'1, A'2, B'1, B'2) via Nb interfaces. Trans-Coders are connected to the packet network via Iu interfaces. A legend at the bottom defines the line types: dashed for Call Control Signalling, solid blue for Ater Interface, solid red for Iu, Nb or packet data user plane, and solid dark blue for A and TDM Interface: 64kb/s. PoI is defined as Point of Interconnect.](ddc7460821484f1ae2835c67955c554c_img.jpg) + +Figure 4.5-2: Packet transport transit network between PLMNs of REL5, using SIP between PLMNs. The diagram shows two PLMNs, PLMN A and PLMN B, connected via a central packet network. PLMN A includes a PSTN (PoI A) connected to an MSC-S (A1) via ISUP/TDM. MSC-S (A1) is connected to MSC-S (A2) via Nc. MSC-S (A2) is connected to the packet network via SIP. PLMN B includes a PSTN (PoI B) connected to an MSC-S (B1) via ISUP/TDM. MSC-S (B1) is connected to MSC-S (B2) via Nc. MSC-S (B2) is connected to the packet network via SIP. Both PLMNs include BSCs and RNCs connected to MGWs (A1, A2, B1, B2) via Ater and Iu interfaces. MGWs are connected to Trans-Coders (A'1, A'2, B'1, B'2) via Nb interfaces. Trans-Coders are connected to the packet network via Iu interfaces. A legend at the bottom defines the line types: dashed for Call Control Signalling, solid blue for Ater Interface, solid red for Iu, Nb or packet data user plane, and solid dark blue for A and TDM Interface: 64kb/s. PoI is defined as Point of Interconnect. + +**Figure 4.5-2: Packet transport transit network between PLMNs of REL5, using SIP between PLMNs.** + +The PLMNs may alternately be interconnected using SIP rather than BICC in the signalling plane, see Figure 4.5.2. The user plane interconnecting the two BICNs uses standard IETF framing protocols when configured over IP transport. In this case SIP-to-BICC interworking procedures apply at the border MSCs. See ITU-T Recommendation Q.1912.5 [14], which accommodates the 3GPP SIP profile through its profile A for SIP. ITU-T Recommendation Q.1912.5 [14] can be used with TS 29.163 [13] to enable interworking of OoBTC through the intermediate SIP network. However, TS 29.007 [16] currently does not define the use of SIP inter-PLMN. + +Support for EFR and Half Rate in SDP does not exist. It has not been validated if all current Supplementary Services are supported by the BICC-SIP interworking. Furthermore, the BICC-SIP interworking may have impact to the supported in-call modifications. Further study would be needed to address these issues to ensure BICC-SIP interworking without degradation of the CS call services. + +# 5 Call Scenarios to be studied + +The following call scenarios are those of interest for BARS functionality for the network scenarios detailed in clause 4. For each scenario the resources used in the MGWs and TRAUs and the bandwidths in use are described. They are also + +quantified in relation to each other in terms of Mega Instructions Per Second (MIPS, see definitions). These scenarios apply to initial bearer establishment as well as bearer renegotiation as needed for call forwarding, handover and other situations involving bearer reconfiguration. + +Resource utilisation in MGWs and TRAUs comprises the following aspects: + +- a) **TFO Protocol Termination (PT).** TFO requires the use of TFO-protocol handlers for the inband signalling. This is typically implemented in a DSP, collocated with the Transcoder function. TFO-Protocol Termination requires a small processing power, mainly during the initial search for the first TFO message ( $\leq 1$ MIPS, for simplicity and to be on the safe side counted with 1 MIPS). +- b) **Re-framing (R).** Depending on the scenario, it is necessary to reframe "the same bits of information", for example at transition from TDM (TFO-Frames) to packet (Iu- or Nb-Frames) or vice versa. Reframing is also necessary where transcoding takes place. Reframing requires a comparably tiny processing power ( $\ll 1$ MIPS, this is neglected when it appears together with PT or TC or DC). +- c) **Transcoding (TC) and Decoding (DC).** Transcoding (Encoding and Decoding) is needed to change from AMR (or EFR or AMR-WB...) to G.711 and vice-versa. Only Decoding is needed to restore the PCM signal towards TDM networks at the end of a TrFO link. Transcoding is by far the dominating function in terms of DSP power. The EFR and AMR are characterised with about 15 MIPS, the AMR-WB with about 30 MIPS. In all cases the Encoder is taking the "lions-share" of about 80%, the Decoder only about 20%. For the illustrations below the AMR is assumed (12 MIPS + 3 MIPS) as example. +- d) **User Plane Termination (UP).** Termination of the Iu/Nb User Plane Protocol. Also this function requires a comparably tiny processing power ( $\ll 1$ MIPS, this is neglected when it appears together with PT or TC or DC). + +The figures indicate the resources needed in the MGWs in various scenarios for the case where TFO is used (green) and the case where TrFO is used (blue). In addition to the resource utilisation also the bandwidth used is shown: + +13 kbit/s: + +64 kbit/s: + +![Legend for resource utilization: a green bar represents 13 kbit/s and a blue bar represents 64 kbit/s.](ace13edeb79bdfa129ed84fbb4ac44e5_img.jpg) + +Legend for resource utilization: a green bar represents 13 kbit/s and a blue bar represents 64 kbit/s. + +## 5.1 Mobile to Mobile call Scenarios + +### 5.1.1 BSC to RNC call via BICN + +UE A in the coverage area of a BSC connected via A interface to a MGW, calls UE B which is in the coverage area of a RNC connected via Iu interface to a different MGW. The call between the MGW's is carried via the Nb interface connecting them. + +![Diagram of BSC to RNC call via BICN. The diagram shows two PSTN nodes (PoI A and PoI B) connected to MSC-S A and MSC-S B respectively via ISUP and TDM interfaces. MSC-S A and MSC-S B are connected via Nc interfaces. MSC-S A is connected to MGW A via Iu and Mc interfaces. MGW A is connected to BSC A via Ater and to TRAU Trans-Coder A via A interface. TRAU Trans-Coder A is connected to RNC A via Iu interface. MGW A is also connected to Trans-Coder A' via Nb interface. Trans-Coder A' is connected to RNC B via Iu interface. MGW B is connected to MSC-S B via Iu and Mc interfaces. MGW B is connected to BSC B via Ater and to TRAU Trans-Coder B via A interface. TRAU Trans-Coder B is connected to RNC B via Iu interface. MGW B is also connected to Trans-Coder B' via Nb interface. Trans-Coder B' is connected to RNC B via Iu interface. Call control signalling is shown as dashed lines. Ater interface is shown as a thin blue line. A and TDM interfaces are shown as thick blue lines. Iu and Nb interfaces are shown as thin green lines. The speech path is highlighted in yellow, showing the flow from PoI A through MGW A, Trans-Coder A', Nb interface, Trans-Coder B', and MGW B to PoI B.](70de8885bd7de15723aaad5eb5c5febf_img.jpg) + +----- Call Control Signalling    — Ater Interface    — A and TDM Interface: 64kb/s + ————— Iu and Nb Interface + +PoI: Point of Interconnect + +Diagram of BSC to RNC call via BICN. The diagram shows two PSTN nodes (PoI A and PoI B) connected to MSC-S A and MSC-S B respectively via ISUP and TDM interfaces. MSC-S A and MSC-S B are connected via Nc interfaces. MSC-S A is connected to MGW A via Iu and Mc interfaces. MGW A is connected to BSC A via Ater and to TRAU Trans-Coder A via A interface. TRAU Trans-Coder A is connected to RNC A via Iu interface. MGW A is also connected to Trans-Coder A' via Nb interface. Trans-Coder A' is connected to RNC B via Iu interface. MGW B is connected to MSC-S B via Iu and Mc interfaces. MGW B is connected to BSC B via Ater and to TRAU Trans-Coder B via A interface. TRAU Trans-Coder B is connected to RNC B via Iu interface. MGW B is also connected to Trans-Coder B' via Nb interface. Trans-Coder B' is connected to RNC B via Iu interface. Call control signalling is shown as dashed lines. Ater interface is shown as a thin blue line. A and TDM interfaces are shown as thick blue lines. Iu and Nb interfaces are shown as thin green lines. The speech path is highlighted in yellow, showing the flow from PoI A through MGW A, Trans-Coder A', Nb interface, Trans-Coder B', and MGW B to PoI B. + +Figure 5.1.1-1: BSC to RNC call via BICN + +Harmonized OoBTC/TFO procedures allow for the interworking of TFO procedures on the A interface and OoBTC/TrFO procedures on the Nc/Nb interface to provide for improved voice quality by removing unnecessary transcoding from the voice path, and high bandwidth efficiency on all portions of the speech path except the A interface between Transcoder A and MGW A in the figure. + +1. MSC-S A and MSC-S B use OoBTC to minimize transmission bandwidth and the allocation of codecs on the speech path between MGW A and RNC B, using preferred BSC A Codec Configuration. +2. BSC A and MSC-S A enable TFO in transcoder A and transcoder A'. +3. If TFO is supported but codec mismatch occurs then MSC-S A discovers the Codec Configuration at BSC A via MGW A using the TFO package on the Mc interface, it initiates TrFO/TFO codec negotiation harmonization if necessary, using OoBTC and/or TFO codec modification procedures. + +4. When codec negotiation completes successfully, the Ater, Nb and Iu interfaces all carry compressed speech with high bandwidth efficiency. Transcoders A and A' remain in the speech path to perform necessary TFO protocol tasks and decoding but do not perform transcoding. Transcoder B' is not in the speech path. + +Alternatively, when OoBTC is not available, the MSC-Ss route a 64kbit/s PCM path between the BSC/TRAU and the MGWs. MGW B inserts a transcoder B'. MGW A is configured with PCM on both terminations and does not perform TFO-Protocol handling. TFO is enabled in transcoders A and B'. + +1. When TFO-Negotiation between transcoder A and transcoder B' completes successfully, compressed speech is carried in all portions of the speech path. Transcoders A and B' remain in the speech path to perform necessary TFO protocol tasks and decoding, but do not perform transcoding. + +The bandwidth and resource usage is analogous to clause 5.1.3 below. + +### 5.1.2 BSC to BSC call via BICN + +UE A in the coverage area of a BSC connected via A interface to a MGW, calls UE B which is in the coverage area of a BSC connected via A interface to a different MGW. The call between the MGW's is carried via the Nb interface connecting them. + +![Diagram of BSC to BSC call via BICN showing call control and speech paths between two network elements.](768b8ab0d55761b205087c079df1e6e6_img.jpg) + +The diagram illustrates a BSC to BSC call via BICN. It shows two network elements, MGW A and MGW B, connected via an Nb interface. Each MGW is connected to an MSC-S (MSC-S A and MSC-S B) via an Ater interface. The MSC-Ss are connected to PSTN via ISUP and TDM interfaces at PoI A and PoI B. The MGWs are also connected to BSCs (BSC A and BSC B) via A interfaces. The BSCs are connected to RNCs (RNC A and RNC B) via Iu interfaces. The MGWs are connected to TRAU Transcoders (TRAU Trans-Coder A and TRAU Trans-Coder B) via A interfaces. The TRAU Transcoders are connected to the BSCs via Ater interfaces. The MGWs are also connected to Trans-Coders (Trans-Coder A' and Trans-Coder B') via Iu interfaces. The Trans-Coders are connected to the RNCs via Iu interfaces. The MGWs are connected to each other via an Nb interface. The call control signalling is shown as dashed lines, and the speech path is shown as solid lines. The legend indicates: + + +- Call Control Signalling +- Ater Interface +- A and TDM Interface: 64kb/s +- Iu and Nb Interface + + PoI: Point of Interconnect + +Diagram of BSC to BSC call via BICN showing call control and speech paths between two network elements. + +Figure 5.1.2-1: BSC to BSC call via BICN + +Harmonized OoBTC/TFO procedures allow for the interworking of TFO procedures on the A interfaces and OoBTC/TrFO procedures on the Nc/Nb interface to provide for improved voice quality by removing unnecessary transcoding from the voice path, and high bandwidth efficiency on all portions of the speech path except the A interface between Transcoder A and MGW A and the A interface between MGW B and Transcoder B in the figure. + +1. MSC-S A and MSC-S B use OoBTC to establish compressed speech over Nb between MGW A and MGW B. +2. If TFO is supported but codec mismatch occurs then the MSC-Ss discover the Codec Configurations at the BSCs via the MGWs using the TFO package on the Mc interface, they initiate TrFO/TFO codec negotiation harmonization, using OoBTC and/or TFO codec modification procedures. +3. When codec negotiation completes successfully, the Nb interface carries compressed speech with high bandwidth efficiency. Transcoders A, A', B' and B remain in the speech path to perform necessary TFO protocol tasks and decoding but do not perform transcoding. + +Alternatively, when OoBTC is not available, the MSC-Ss route a 64kbit/s PCM path between the BSC/TRAUs, transparently through the MGWs. Both MGWs are configured with PCM on both terminations and do not perform TFO-Protocol handling. TFO is enabled in transcoders A and B. + +1. When TFO-Negotiation between transcoder A and transcoder B completes successfully, compressed speech is carried in all portions of the speech path. Transcoders A and B remain in the speech path to perform necessary TFO protocol tasks and decoding, but do not perform transcoding. + +Figure 5.1.2-2 shows the bandwidth and resources used in case TFO or TFO-TrFO-TFO are applied. The MIPS values characterize the DSP usage in the steady state, i.e. when TFO is in OPERATION, for AMR. The values in brackets show the DSP usage before TFO is established. Please note that in the upper branch the MGWs are not necessarily aware that TFO is embedded in the G.711 bit stream: + +![Diagram illustrating the bandwidth and resource usage for a BSC to BSC call via BICN. The diagram shows two MGWs connected between two BSC/TRAUs. The top path uses G.711(+TFO) at 64 kbit/s / AAL2, while the bottom path uses TrFO at 13 kbit/s / AAL2. MIPS values are provided for each component, with steady-state values in brackets.](895d588a848d9963890c938763de9ecf_img.jpg) + +The diagram illustrates the network architecture for a BSC to BSC call via BICN. It consists of two MGWs (Media Gateway) connected between two BSC/TRAUs (Base Station Controller/Transceiver Unit). + +**Left BSC/TRAU:** Contains a transcoder labeled "DC, PT (TC, PT)". It has two MIPS values: 4 MIPS (steady state) and 16 MIPS (before TFO is established). It is connected to the first MGW via an "A" interface. The "TFO" (Traffic Flow Optimization) label is present near the interface. + +**First MGW:** Contains two processing blocks. The top block is labeled "R, UP" and has a MIPS value of "<< 1MIPS". The bottom block is labeled "PT, DC (PT, TC)" and "R, UP" and has MIPS values of 4 MIPS (steady state) and 16 MIPS (before TFO is established). The MGW is connected to the second MGW via two parallel paths: + + +- A top path labeled "G.711(+TFO): 64 kbit/s / AAL2". +- A bottom path labeled "TrFO :13 kbit/s / AAL2" and "Nb" (Narrowband). + +**Second MGW:** Contains two processing blocks. The top block is labeled "UP, R" and has a MIPS value of "<< 1MIPS". The bottom block is labeled "DC, PT (TC, PT)" and "UP, R" and has MIPS values of 4 MIPS (steady state) and 16 MIPS (before TFO is established). The MGW is connected to the second BSC/TRAU via an "A" interface. The "TFO" label is present near the interface. + +**Second BSC/TRAU:** Contains a transcoder labeled "PT, DC (PT, TC)". It has two MIPS values: 4 MIPS (steady state) and 16 MIPS (before TFO is established). + +Diagram illustrating the bandwidth and resource usage for a BSC to BSC call via BICN. The diagram shows two MGWs connected between two BSC/TRAUs. The top path uses G.711(+TFO) at 64 kbit/s / AAL2, while the bottom path uses TrFO at 13 kbit/s / AAL2. MIPS values are provided for each component, with steady-state values in brackets. + +Note: The MIPS values in brackets() indicate the DSP-resource usage in the short TFO-setup phase, when TC is used. + +**Figure 5.1.2-2: Bandwidth and resource usage for BSC to BSC call via BICN** + +### 5.1.3 RNC to BSC call via BICN + +UE A in the coverage area of an RNC connected via Iu interface to a MGW, calls UE B which is in the coverage area of a BSC connected via A interface to a different MGW. The call between the MGWs is carried via the Nb interface connecting them. + +![Diagram of RNC to BSC call via BICN showing call control signalling and speech paths between two network elements (A and B) connected via MGWs and MSC-Ss.](d244183a8ff3d94b0dcf30140f51020d_img.jpg) + +The diagram illustrates the network architecture for an RNC to BSC call via BICN. It shows two network elements, A and B, connected via MGWs and MSC-Ss. The call control signalling is shown as dashed blue lines, and the speech path is shown as a solid yellow line. The legend indicates that dashed blue lines represent Call Control Signalling, solid blue lines represent Ater Interface, thick solid blue lines represent A and TDM Interface: 64kb/s, and thin solid blue lines represent Iu and Nb Interface. PoI: Point of Interconnect is also indicated. + +Diagram of RNC to BSC call via BICN showing call control signalling and speech paths between two network elements (A and B) connected via MGWs and MSC-Ss. + +Figure 5.1.3-1: RNC to BSC call via BICN + +Harmonized OoBTC/TFO procedures allow for the interworking of OoBTC/TrFO procedures on the Nc/Nb interface and TFO procedures on the A interfaces to provide for improved voice quality by removing unnecessary transcoding from the voice path, and high bandwidth efficiency on all portions of the speech path except the A interface between MGW B and Transcoder B in the figure. + +1. MSC-S A and MSC-S B use OoBTC to minimize transmission bandwidth and the allocation of codecs on the speech path between RNC A and MGW B, using assumed information about the BSC B Codec Configuration. +2. If TFO is supported but codec mismatch occurs then MSC-S B discovers the Codec Configuration at BSC B via MGW B using the TFO package on the Mc interface, it initiates TrFO/TFO codec negotiation harmonization if necessary, using OoBTC and/or TFO codec modification procedures. +3. MSC-S B establishes TFO operation between MGW B and Transcoder B. +4. When codec negotiation completes successfully, the Ater, Nb and Iu interfaces all carry compressed speech with high bandwidth efficiency. Transcoder A' is not in the speech path. Transcoders B' and B remain in the speech path to perform necessary TFO protocol tasks and decoding but do not perform transcoding. + +Alternatively, when OoBTC is not available, the MSC-Ss route a 64kbit/s PCM path between the BSC/TRAU B and the MGWs. MGW A inserts a transcoder A'. MGW B is configured with PCM on both terminations and does not perform TFO-Protocol handling. TFO is enabled in transcoders A' and B. + +2. When TFO-Negotiation between transcoder A' and transcoder B completes successfully, compressed speech is carried in all portions of the speech path. Transcoders A' and B remain in the speech path to perform necessary TFO protocol tasks and decoding, but do not perform transcoding. + +Figure 5.1.3-2 shows the bandwidth and resources used in case TFO or TFO-TrFO are applied: + +![Diagram of RNC to BSC call via BICN showing MGW components and bandwidth usage.](d62e2e2281009c16f4ee61660e716cd9_img.jpg) + +This diagram illustrates the internal components and data paths of two Media Gateway (MGW) units for an RNC to BSC call via BICN. + +The left MGW contains two main processing blocks: + +1. A top block labeled 'DC, PT R, UP' with a resource usage of '4 MIPS (16 MIPS)'. It is connected to an 'Iu' interface (13 kbit/s / AAL2) and a 'TFO: 64 kbit/s / AAL2' path. + +2. A bottom block labeled 'DC, PT UP, R' with a resource usage of '4 MIPS (16 MIPS)'. It is connected to an 'Nb' interface and a 'TrFO: 13 kbit/s / AAL2' path. + +The right MGW contains similar blocks: + +1. A top block labeled 'UP, R' with a resource usage of '<< 1 MIPS'. It is connected to the 'TFO: 64 kbit/s / AAL2' path and an 'A' interface. + +2. A bottom block labeled 'DC, PT UP, R' with a resource usage of '4 MIPS (16 MIPS)'. It is connected to the 'Nb' interface and the 'A' interface. + +The 'A' interface connects the right MGW to a 'BSC / TRAU' unit, which contains a 'PT, DC' block with a resource usage of '4 MIPS (16 MIPS)'. + +Diagram of RNC to BSC call via BICN showing MGW components and bandwidth usage. + +**Figure 5.1.3-2: Bandwidth and resource usage for RNC to BSC call via BICN** + +Note: the MIPS values in brackets() indicate the DSP-resource usage in the short TFO-setup phase, when TC is used + +### 5.1.4 RNC to RNC call via BICN + +UE A in the coverage area of an RNC connected via Iu interface to a MGW, calls UE B, which is in the coverage area of an RNC connected via Iu interface to a different MGW. The call between the MGWs is carried via the Nb interface connecting them. + +![Network architecture diagram for RNC to RNC call via BICN.](7a207f7bb5a20f849aee089439e24a84_img.jpg) + +This diagram shows the network architecture for an RNC to RNC call via BICN. + +At the top, two PSTN networks are shown, connected via 'PoI A' and 'PoI B'. These connect to 'MSC-S A' and 'MSC-S B' via 'ISUP' and 'TDM' interfaces. + +The MSC-S units are connected to each other via an 'Nc' interface. + +Each MSC-S unit is also connected to an 'MGW' (MGW A and MGW B) via 'Iu' and 'Mc' interfaces. + +The MGWs are interconnected via an 'Nb' interface. + +Each MGW is connected to a 'TRAU Trans-Coder' (TRAU Trans-Coder A and B) via an 'A' interface. + +The TRAU Trans-Coders are connected to 'BSC A' and 'BSC B' via 'Ater' interfaces. + +Each BSC is connected to an 'RNC' (RNC A and RNC B) via an 'Iu' interface. + +The RNCs are also connected to the MGWs via 'Iu' interfaces through 'Trans-Coder A'' and 'Trans-Coder B'' units. + +A thick yellow line highlights the data path between RNC A and RNC B, passing through the Trans-Coder units and the Nb interface between MGW A and MGW B. + +Legend: + +- Dashed blue line: Call Control Signalling + +- Solid blue line: Ater Interface + +- Thick solid blue line: A and TDM Interface: 64kb/s + +- Solid grey line: Iu and Nb Interface + +PoI: Point of Interconnect + +Network architecture diagram for RNC to RNC call via BICN. + +**Figure 5.1.4-1: RNC to RNC call via BICN** + +OoBTC procedures associated with the Nb interface provide for improved voice quality by removing unnecessary transcoding from the voice path, and high bandwidth efficiency on all portions of the speech path in the figure. + +1. MSC-S A and MSC-S B use OoBTC to minimize transmission bandwidth and the allocation of codecs on the speech path between RNC A and RNC B. +2. When codec negotiation completes successfully, the Nb and Iu interfaces all carry compressed speech with high bandwidth efficiency. Neither Transcoder A' nor Transcoder B' remains in the speech path. + +Alternatively, when OoBTC is not available, both MGWs insert transcoders (A' and B'), the MSC-Ss route a 64kbit/s PCM path between the MGWs and enable TFO. + +3. When TFO-Negotiation completes successfully, compressed speech is carried in all portions of the speech path. Transcoders A' and B' remain in the speech path to perform necessary TFO protocol tasks and decoding, but do not perform transcoding. + +Figure 5.1.4-2 shows the bandwidth and resources used in case TFO or TrFO are applied: + +![Diagram of bandwidth and resource usage for RNC to RNC call via BICN. Two MGWs are shown, each with an Iu interface on the left and right. The MGWs are connected by an Nb interface. The TFO path is shown as a green line between the MGWs, labeled 'TFO: 64 kbit/s / AAL2'. The TrFO path is shown as a blue line between the MGWs, labeled 'TrFO: 13 kbit/s / AAL2'. Each MGW contains a DC, PT, R, UP block and a 4 MIPS (16 MIPS) block. The DC, PT, R, UP block is connected to the Iu interface and the Nb interface. The 4 MIPS (16 MIPS) block is connected to the Nb interface.](d980a3f9608055996a07f31788baf827_img.jpg) + +The diagram illustrates the network architecture for an RNC to RNC call via BICN. Two Media Gateway (MGW) units are depicted. Each MGW is connected to an Iu interface (represented by a horizontal line on the left and right sides). The MGWs are interconnected by an Nb interface. Within each MGW, there are two main processing blocks: a 'DC, PT, R, UP' block (top) and a '4 MIPS (16 MIPS)' block (bottom). The 'DC, PT, R, UP' block is connected to the Iu interface and the Nb interface. The '4 MIPS (16 MIPS)' block is also connected to the Nb interface. Two data paths are shown between the MGWs: a green line labeled 'TFO: 64 kbit/s / AAL2' and a blue line labeled 'TrFO: 13 kbit/s / AAL2'. + +Diagram of bandwidth and resource usage for RNC to RNC call via BICN. Two MGWs are shown, each with an Iu interface on the left and right. The MGWs are connected by an Nb interface. The TFO path is shown as a green line between the MGWs, labeled 'TFO: 64 kbit/s / AAL2'. The TrFO path is shown as a blue line between the MGWs, labeled 'TrFO: 13 kbit/s / AAL2'. Each MGW contains a DC, PT, R, UP block and a 4 MIPS (16 MIPS) block. The DC, PT, R, UP block is connected to the Iu interface and the Nb interface. The 4 MIPS (16 MIPS) block is connected to the Nb interface. + +Figure 5.1.4-2: Bandwidth and resource usage for RNC to RNC call via BICN + +Note: the MIPS values in brackets() indicate the DSP-resource usage in the short TFO-setup phase, when TC is used + +## 5.2 Mobile to PSTN call scenarios + +### 5.2.1 BSC to PSTN call via BICN + +UE A in the coverage area of a BSC connected via A interface to a MGW, calls PSTN phone B, which is in a switch connected via a TDM interface to a different MGW. The call between the MGW's is carried via the Nb interface connecting them. + +![Diagram of BSC to PSTN call via BICN showing call control signalling and speech paths between two network elements (A and B) connected via MGWs and MSC-Ss.](1d27fed9c01eb99f6535283f35fe3bbf_img.jpg) + +The diagram illustrates a call scenario between two network elements, A and B, connected via a BICN. The components and interfaces are as follows: + +- Network Elements:** PSTN (Point of Interconnect A and B), MSC-S A and B, MGW A and B, BSC A and B, RNC A and B, TRAU Trans-Coder A and B, and Trans-Coder A' and B'. +- Interfaces:** + - ISUP:** Call control signalling between PSTN and MSC-S. + - TDM:** Interface between PSTN and MGW. + - A:** Interface between BSC and MGW. + - Iu:** Interface between RNC and MGW. + - Nc:** Interface between MSC-S and MGW. + - Mc:** Interface between MSC-S and MGW. + - Nb:** Interface between MGW A and MGW B. + - Ater:** Interface between BSC and TRAU. +- Call Control Signalling:** Represented by dashed blue lines. +- Ater Interface:** Represented by solid blue lines. +- A and TDM Interface: 64kb/s:** Represented by thick solid blue lines. +- Iu and Nb Interface:** Represented by solid yellow lines. + +Diagram of BSC to PSTN call via BICN showing call control signalling and speech paths between two network elements (A and B) connected via MGWs and MSC-Ss. + +----- Call Control Signalling    ——— Ater Interface    ——— A and TDM Interface: 64kb/s + PoI: Point of Interconnect    ——— Iu and Nb Interface + +**Figure 5.2.1-1: BSC to PSTN call via BICN** + +Harmonized OoBTC/TFO procedures allow for the interworking of TFO procedures on the A interface and OoBTC/TrFO procedures on the Nc/Nb interface to provide for high bandwidth efficiency on all portions of the speech path except the A interface between Transcoder A and MGW A and the TDM path to the PSTN in the figure. + +1. MSC-S A and MSC-S B use OoBTC to establish compressed speech over Nb between MGW A and MGW B. +2. If TFO is supported on the A interface but codec mismatch occurs then MSC-S A discovers the Codec Configuration at BSC A via MGW A using the TFO package on the Mc interface, it initiates TrFO/TFO codec negotiation harmonization, using OoBTC and/or TFO codec modification procedures. +3. When codec negotiation completes successfully, the Nb interface carries compressed speech with high bandwidth efficiency. Transcoders A and A' remain in the speech path to perform necessary TFO protocol tasks and decoding but do not perform transcoding. Transcoder B' performs the necessary transcoding to PCM. +4. Often it is not obvious, whether the call terminates in the PSTN or via TDM in another BICN with TFO capability. Transcoder B' is therefore enabled to perform TFO-Negotiation, but this is not successful (in this example) and will terminate after about 5 seconds. + +Alternatively, when OoBTC is not available, the MSC-Ss route a 64kbit/s PCM path between the BSC/TRAU A and the PSTN, through the MGWs and enable TFO. Both MGWs are configured with PCM on both terminations and will therefore not perform TFO-protocol handling. + +1. TFO-Negotiation in transcoder A will start, but will not be successful (the PSTN does not answer) and so will terminate after about 5 seconds. TRAU A will continue to transcode. The MGWs are both transparent and are not aware that TFO was attempted. + +Figure 5.2.1-2 shows the bandwidth and resources used in case TFO-PCM or TFO-TrFO are applied: + +![Diagram illustrating bandwidth and resource usage for BSC to PSTN call via BICN. The diagram shows two MGWs connected by an Nb interface. The left MGW is connected to two BSC/TRAU units. The top unit uses G.711 (15 MIPS (16 MIPS)) and connects to the MGW via an UP. The bottom unit uses TFO (4 MIPS (16 MIPS)) and connects to the MGW via PT, DC, R, UP. The right MGW connects to a PSTN via a TDM interface. The top MGW unit contains a UP. The bottom MGW unit contains TC (PT) UP, R. The bandwidth for G.711 is 64 kbit/s / AAL2, and for TrFO is 13 kbit/s / AAL2.](d793cf7c174b89eb024d132f00679787_img.jpg) + +The diagram illustrates the network architecture for a BSC to PSTN call via BICN. It features two Media Gateway (MGW) units connected by an Nb interface. On the left, two Base Station Controller / Transcoder and Rate Adapter Unit (BSC / TRAU) units are connected to the first MGW. The top BSC / TRAU unit uses G.711 encoding and requires 15 MIPS (with 16 MIPS indicated for the short TFO-setup phase). It connects to the MGW via an UP (User Plane). The bottom BSC / TRAU unit uses TFO encoding and requires 4 MIPS (with 16 MIPS indicated for the short TFO-setup phase). It connects to the MGW via PT, DC, R, UP. The MGW on the left contains a UP for the G.711 path and a PT, DC, R, UP for the TFO path. The MGW on the right contains a UP for the G.711 path and a TC (PT) UP, R for the TFO path. The G.711 path has a bandwidth of 64 kbit/s / AAL2, and the TrFO path has a bandwidth of 13 kbit/s / AAL2. The right MGW connects to the PSTN via a TDM interface. + +Diagram illustrating bandwidth and resource usage for BSC to PSTN call via BICN. The diagram shows two MGWs connected by an Nb interface. The left MGW is connected to two BSC/TRAU units. The top unit uses G.711 (15 MIPS (16 MIPS)) and connects to the MGW via an UP. The bottom unit uses TFO (4 MIPS (16 MIPS)) and connects to the MGW via PT, DC, R, UP. The right MGW connects to a PSTN via a TDM interface. The top MGW unit contains a UP. The bottom MGW unit contains TC (PT) UP, R. The bandwidth for G.711 is 64 kbit/s / AAL2, and for TrFO is 13 kbit/s / AAL2. + +NOTE: The MIPS values in brackets() indicate the DSP-resource usage in the short TFO-setup phase, when TC is used. + +**Figure 5.2.1-2: Bandwidth and resource usage for BSC to PSTN call via BICN** + +### 5.2.2 RNC to PSTN call via BICN + +UE A in the coverage area of an RNC connected via Iu interface to a MGW, calls PSTN phone B, which is in a switch connected via a TDM interface to a different MGW. The call between the MGW's is carried via the Nb interface connecting them. + +![Diagram of RNC to PSTN call via BICN showing call control and speech paths.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) + +The diagram illustrates the network architecture for an RNC to PSTN call via a BICN. At the top, two PSTN networks are shown, each with a Point of Interconnect (PoI) labeled PoI A and PoI B. These PoIs are connected via TDM interfaces to MSC-S A and MSC-S B respectively. MSC-S A and MSC-S B are interconnected via an Nc interface. Below each MSC-S is an MGW (MGW A and MGW B) connected via an Iu interface. MGW A and MGW B are connected via an Nb interface. On the left side, an RNC A is connected to MGW A via an Iu interface. RNC A is also connected to a TRAU Trans-Coder A, which is connected to a BSC A. BSC A is connected to MGW A via an Ater interface. On the right side, a similar setup exists with RNC B, TRAU Trans-Coder B, and BSC B. MGW A contains a transcoder labeled 'Trans-Coder A'' and MGW B contains 'Trans-Coder B''. Call control signalling is shown as dashed blue lines, originating from the PoIs, passing through the MSC-Ss, and reaching the RNCs. The speech path is shown as a solid yellow line, starting from RNC A, passing through MGW A, then MGW B, and finally reaching PoI B. A legend at the bottom defines the line types: dashed blue for Call Control Signalling, solid blue for Ater Interface, solid yellow for A and TDM Interface: 64kb/s, and solid light blue for Iu and Nb Interface. PoI is defined as Point of Interconnect. + +Diagram of RNC to PSTN call via BICN showing call control and speech paths. + +Figure 5.2.2-1: RNC to PSTN call via BICN + +1. OoBTC/TrFO procedures associated with the Nc/Nb interface provide for high bandwidth efficiency on all portions of the speech path except the TDM path to the PSTN in the figure. MSC-S A and MSC-S B use OoBTC to minimize transmission bandwidth and the allocation of codecs on the speech path between RNC A and PSTN B. +2. When codec negotiation completes successfully, the Nb and Iu interfaces carry compressed speech with high bandwidth efficiency. Transcoder A' is not in the speech path. Transcoder B' performs the necessary transcoding to PCM. +3. Often it is not obvious, whether the call terminates in the PSTN or via TDM in another BICN with TFO capability. Transcoder B' is therefore enabled to perform TFO-Negotiation, but this is not successful (in this example) and will terminate after about 5 seconds. + +Alternatively, when OoBTC is not available, the MSC-Ss route a 64kbit/s PCM path between the MGWs and the PSTN, MGW A inserts a transcoder A' and TFO is enabled. MGW B is configured with PCM on both terminations and will therefore not perform TFO-protocol handling. + +1. TFO-Negotiation in transcoder A' will start, but will not be successful (the PSTN does not answer) and so will terminate after about 5 seconds. Transcoder A' will continue to transcode. MGW B is transparent and is not aware that TFO was attempted + +Figure 5.2.2-2 shows the bandwidth and resources used in case G.711 or TrFO are applied: + +![Diagram illustrating bandwidth and resource usage for RNCC to PSTN call via BICN. It shows two MGWs connected via an Nb interface. The left MGW has an Iu interface and contains a TC (R, UP) block. The right MGW contains UP, R and TC (UP, R) blocks. A green line represents G.711: 64 kbit/s / AAL2 traffic from the left TC to the right UP, R. A blue line represents TrFO: 13 kbit/s / AAL2 traffic from the left TC to the right TC. The right MGW is connected to a PSTN via a TDM interface. MIPS values are indicated: 15 MIPS (16 MIPS) for the left TC, << 1 MIPS for the right UP, R, and 15 MIPS (16 MIPS) for the right TC.](54a53f959bb7758332532c1cd5f0ad75_img.jpg) + +Diagram illustrating bandwidth and resource usage for RNCC to PSTN call via BICN. It shows two MGWs connected via an Nb interface. The left MGW has an Iu interface and contains a TC (R, UP) block. The right MGW contains UP, R and TC (UP, R) blocks. A green line represents G.711: 64 kbit/s / AAL2 traffic from the left TC to the right UP, R. A blue line represents TrFO: 13 kbit/s / AAL2 traffic from the left TC to the right TC. The right MGW is connected to a PSTN via a TDM interface. MIPS values are indicated: 15 MIPS (16 MIPS) for the left TC, << 1 MIPS for the right UP, R, and 15 MIPS (16 MIPS) for the right TC. + +NOTE: The MIPS values in brackets() indicate the DSP-resource usage in the short TFO-setup phase, when TC is used. + +**Figure 5.2-2: Bandwidth and resource usage for RNCC to PSTN call via BICN** + +## 5.3 Roaming and multi-network call scenarios + +### 5.3.1 BSC (HPLMN) to BSC (VPLMN) call + +UE A in the coverage area of a BSC connected via A interface to a MGW in the HPLMN, calls UE B which is roaming in the coverage area of a BSC connected via A interface to a MGW on the VPLMN. The call from the HPLMN MGW's is carried via TDM circuits to a Gateway MGW in the UE B's HPLMN and further on to a Gateway MGW in the VPLMN, which then routes the call to the destination MGW (the one connected to the BSC) over the Nb interface. + +The bandwidth and resource usage are analogous to clause 5.2.1 for the HPLMN A and VPLMN. The MGW in HPLMN B does not need to perform Protocol Termination, Transcoding, Re-framing, or User Plane Termination. + +Note: TFO is not applicable in this scenario if the TDM links between networks use DCMEs. + +### 5.3.2 BSC (HPLMN) to RNC (VPLMN) call + +UE A in the coverage area of a BSC connected via A interface to a MGW in the HPLMN, calls UE B which is roaming in the coverage area of a RNC connected via Iu interface to a MGW on the VPLMN. The call from the HPLMN MGW's is carried via TDM circuits to a Gateway MGW in the UE B's HPLMN and further on to a Gateway MGW in the VPLMN, which then routes the call to the destination MGW (the one connected to the RNC) over the Nb interface. + +The bandwidth and resource usage are analogous to clause 5.2.1 for the HPLMN A and to clause 5.2.2 for the VPLMN. The MGW in HPLMN B does not need to perform Protocol Termination, Transcoding, Re-framing, or User Plane Termination. + +NOTE: TFO is not applicable in this scenario if the TDM links between networks use DCMEs. + +### 5.3.3 RNC (HPLMN) to BSC (VPLMN) call + +UE A in the coverage area of a RNC connected via Iu interface to a MGW in the HPLMN, calls UE B which is roaming in the coverage area of a BSC connected via A interface to a MGW on the VPLMN. The call from the HPLMN MGW's is carried via TDM circuits to a Gateway MGW in the UE B's HPLMN and further on to a Gateway MGW in the VPLMN, which then routes the call to the destination MGW (the one connected to the BSC) over the Nb interface. + +The bandwidth and resource usage are analogous to clause 5.2.2 for the HPLMN A and to clause 5.2.1 for the VPLMN. The MGW in HPLMN B does not need to perform Protocol Termination, Transcoding, Re-framing, or User Plane Termination. + +NOTE: TFO is not applicable in this scenario if the TDM links between networks use DCMEs. + +### 5.3.4 RNC (HPLMN) to RNC (VPLMN) call + +UE A in the coverage area of a RNC connected via Iu interface to a MGW in the HPLMN, calls UE B which is roaming in the coverage area of a RNC connected via Iu interface to a MGW on the VPLMN The call from the HPLMN MGW's is carried via TDM circuits to a Gateway MGW in the UE B's HPLMN and further on to a Gateway MGW in the VPLMN, which then routes the call to the destination MGW (the one connected to the RNC) over the Nb interface. + +The bandwidth and resource usage are analogous to clause 5.2.2 for the HPLMN A and for the VPLMN. The MGW in HPLMN B does not need to perform Protocol Termination, Transcoding, Re-framing, or User Plane Termination. + +NOTE: TFO is not applicable in this scenario if the TDM links between networks use DCMEs. + +## 5.4 CS domain to IMS interworking scenario + + + +IMS to CS interworking is being covered by CN3 in TS 29.163 [13]. It is concluded that CN3 are covering the support of OoBTC and it is expected this will be completed by close of Release 6. + +## 5.5 A selection of handover scenarios + +### 5.5.1 BSC to BSC call via BICN with Intra GERAN handover AMR-AMR + +#### **Stable call Situation long before the Handover:** + +UE A in the coverage area of a BSC connected via A interface to a MGW, called UE B, which is in the coverage area of a BSC connected via A interface to a different MGW. The call between the MGWs is carried via the Nb interface connecting them. Both BSCs selected the **FR\_AMR** Codec Type with Codec **Configuration set 12 (10.2 6.7 5.9 4.75)**. The call is established using also FR\_AMR (or UMTS\_AMR\_2) on the Nb interface. TFO-TrFO-TFO interworking applies and end-to-end transcoding free operation is achieved. **See Figure 5.1.2-1 "BSC to BSC call via BICN".** + +Both GSM terminals (UEs) and the GSM base stations (BTSs) monitor their receiving-link quality/capacity and issue regular "Codec Mode Requests" (CMRs) every 40ms on the radio-, Abis- and Ater-interfaces to adapt the net bit rate (the codec mode) to the actual radio link capacity. The GSM TRAUs potentially modify these CMRs, but most of the time just send them along inside the TFO\_Frames on the A-interfaces. The MGW, when receiving these regular Codec Mode Requests, investigate, whether there was a change in the requested bit rate and only if a change occurred, they issue Rate Control Requests (RC\_Req) on the Nb-Interface. These Rate Control Requests are acknowledged by the distant MGW (RC\_Ack) and from then on the distant MGW sends the new, updated CMR to the connected GSM\_BSS via TFO\_Frames. In this way end-to-end Rate Control is achieved, providing the best possible voice quality under the given radio conditions. + +#### **Situation just before Handover:** + +One of the radio interfaces decides that another cell and also another Codec Type has to be used, e.g. for capacity reasons an inter BTS handover has to be performed and the new Codec Type after handover will be **HR\_AMR** with Codec **Configuration set 10 (7.4 6.7 5.9 4.75)**. + +The BSC allocates a new radio channel and a new TRAU device (in this example) and prepares the Handover-Handler. Here we assume that the Handover Handler consists just of a Y-distribution of the downlink PCM signal from the A-Interface to both TRAUs (old and new) and a hard switch (either-or) between both TRAU output PCM streams towards the A-Interface. + +The Handover has still not occurred, but the new BTS and the new TRAU are already interconnected via Abis/Ater and initialised and synchronised to each other. Therefore the new downlink radio channel is already actively sending coded speech, but the mobile station still receives and sends from/to the old BTS. No interruption of the speech path has occurred so far. The TFO-Protocol is still running between old TRAU and distant TFO-Partner (in this case the MGW). The new TRAU gets TFO\_Frames in downlink and starts to send TFO\_Frames in uplink, but so far these contain only frames with classifications "No\_Data" or "Speech\_Bad", because the new BTS does not receive useful data yet. The uplink TFO\_Frames from the new TRAU are anyway ignored by the Handover Handler. + +Optionally the BSC has informed the old BTS (and indirectly or directly the old TRAU) that an handover is expected (Pre-Handover Notification). In this case the old TRAU steers the Rate Control down to the lowest or second lowest mode of the Configuration. This is done in both directions (uplink and downlink) to ensure that the error robustness just before and after handover is maximized, due to the fact that the link quality of new radio channel is still not precisely known. The new TRAU anyway starts to send in lowest or second lowest mode, until the new BTS allows higher rates. If this optional Pre-Handover Notification is not implemented, then there could be a jump in bit rate at handover time. But typically we can assume that the old radio channel is at its performance limits and the rates are anyhow already quite low. + +Now, finally, the UE gets the command to perform the handover. That means: the UE starts receiving and sending from/to the new BTS. The UE starts in uplink also in lowest or second lowest mode. + +#### **Situation just after Handover:** + +Suddenly the old BTS does not get any useful data in uplink, although it still sends speech in downlink. So the old BTS produces TRAU\_Frames on Abis/Ater with classification "No\_Data" or "Speech\_Bad" and the old TRAU relays these further on to the distant TFO\_Partner. The distant UE gets bad speech frames and performs error concealment as usual. Some lost speech frames are often not perceived as such (depends on the speech signal itself). + +Now the new BTS gets the uplink speech and after a short while (40ms) it starts to send TRAU\_Frames in uplink with classification "Speech\_Good". The new TRAU passes these on to the Handover Handler, which – in our example – still discards them, until the new BTS informed the BSC about successful handover and the Handover Handler is commanded to take the new TRAU output. + +In the uplink direction the distant TFO\_Partner gets for a short while "Speech\_Bad" Frames, until the new TFO\_Frames are through-connected. The TFO\_Protocol itself is, however, only very shortly disturbed, just in the switching instant, typically two TFO\_Frames are destroyed, but both TFO\_Partners re-synchronise quickly. + +In the downlink direction the UE always received useful data, either from the old or from the new BTS. But typically two frames are lost due to the break in the interleaving scheme. + +Now – after some 100ms – the estimates on the new radio channel capacities in uplink and downlink are better and better and the UE and the new BTS start to ramp up the bit rate (Codec Mode) to the appropriate level. It should be expected that the radio channel after handover is substantially better than before, so the rate will be quickly up to optimum. + +But what is now the maximally allowed rate? Remember: we have FR\_AMR on the distant side and HR\_AMR now after handover on the local side (where the handover occurred). The new TRAU knows its own Configuration and just does never allow higher rates than 7.4. But 7.4 is not supported by the other configuration! The highest common mode is indeed 6.7. How do the TRAus know this? Well, meanwhile the new BTS and the distant TFO\_Partner have exchanged their full configuration (Codec Type and Configuration, alternative Code List) and the new TRAU has just read and copied that as well. + +#### **Conclusion:** + +Handovers in a TFO-TrFO-TFO connection between FR\_AMR and HR\_AMR (and all combinations of these two) work very smart without noticeable interruptions of the transcoding free operation or the speech path, with reasonably well organised rate control during the handover process. The resource saving in TRAus and MGWs and the bandwidth saving on the Nb interface remain intact all the time. + +Prerequisite: the AMR Configurations on both sides and inside the BICN are compatible! + +### **5.5.2 BSC to BSC call via BICN with Intra GERAN handover to AMR - EFR** + +#### **Stable call Situation long before the Handover:** + +UE A in the coverage area of a BSC connected via A interface to a MGW, called UE B, which is in the coverage area of a BSC connected via A interface to a different MGW. The call between the MGW's is carried via the Nb interface connecting them. Both BSCs selected the **FR\_AMR** Codec Type with Codec **Configuration set 12 (10.2 6.7 5.9 4.75)**. The call is established using also FR\_AMR on the Nb interface. TFO-TrFO-TFO interworking applies and end-to-end transcoding free operation is achieved. See Figure 5.1.2-1 "BSC to BSC call via BICN". + +This is so far exactly as described in the scenario 5.5.1 before. We have now the following constellation: + +| | | | | | | | | | +|--------------|---|-----|---|--------|---|-----|---|--------------| +| FR_AMR | – | TFO | – | FR_AMR | – | TFO | – | FR_AMR | +| UE1 - GERAN1 | – | – | – | BICN | – | – | – | GERAN2 – UE2 | + +The Selected Codec Type is FR\_AMR. The Available Codec List may contain (FR\_AMR, EFR and PCM). + +NOTE: The example works very similar, when EFR is not already here included. + +Both MSC-S prefer the FR\_AMR on the radio legs and within the BICN against any other existing narrowband GERAN Codec Type (such as FR, HR, EFR) and therefore do not offer them to their MGWs for TFO-Negotiation. The TFO-Codec-Lists as sent out by both MGWs to both GERANs contain therefore the FR\_AMR as "Local Used Codec" and as the only alternative Codec Type available. This does, however, not exclude that GERAN may select another Codec Type for radio resource or other reasons later in the call. + +NOTE 1: "Local Used Codec" and "Distant Used Codec" are terms used in the TFO Standard. + +NOTE 2: This claim "FR\_AMR(multi-mode) on GERAN is always better than EFR or any other narrowband GERAN Codec Type, even if transcoding is required" can be derived from the TFO Decision rules in TS 28.062 [4]. + +#### Situation just before Handover: + +One of the radio interfaces (in this example on the "A" side) decides that another cell and also another Codec Type has to be used, e.g. for TRAU resource reasons an inter BTS handover has to be performed and the new Codec Type after handover will be **EFR**. + +BSC A allocates a new radio channel and a new TRAU A<sub>2</sub> device (in this example) and prepares the Handover-Handler. The new BTS A<sub>2</sub> and new TRAU A<sub>2</sub> synchronise to each other and the new TRAU A<sub>2</sub> gets TFO\_Frames from the distant TFO\_Partner via MGW A. It immediately discovers that a Codec Type Mismatch is given and does not enter the TFO Mode, but stays in PCM mode. The received PCM+TFO stream in downlink has some underlying slight white noise, but is well intelligible. Still the old speech path is intact and is working in TFO (TRAU A – MGW A). + +#### Situation just after Handover: + +When the Handover Handler finally connects the new TRAU A' (with EFR) to MGW A (with FR\_AMR) the Codec Type mismatch forces MGW A to fall back to PCM on the A-Interface. The Nb-Interface remains in FR\_AMR, because the TC A' in MGW A starts immediately to ramp up the AMR Encoder. Only a few speech frames are disturbed in both directions. The main effect is most likely the jump in speech path delay by about 40ms in both directions. + +This results now in the following constellation: + +| | | | | | | | | | +|---------------------|---|------------|---|-------------|---|-----|---|---------------------| +| EFR | – | <b>PCM</b> | – | FR_AMR | – | TFO | – | FR_AMR | +| <u>UE1 - GERAN1</u> | – | – | – | <u>BICN</u> | – | – | – | <u>GERAN2 – UE2</u> | + +#### Conclusion: + +Handovers in a TFO-TrFO-TFO connection between AMR (any type) and EFR (or any other non-compatible codec type) forces the local TFO-connection to fall back to PCM and forces the connected MGW to use additional Encoding. The speech path is only marginally interrupted, but the speech path delay increases and the voice quality decreases due to the additional transcoding. The DSP-usage increases substantially. The bandwidth saving on Nb is unaffected. + +**Problem:** What does MSC-S A do, when it is notified by MGW A about the new TFO-Codec-List, the Codec Mismatch situation between BICN and this radio leg and the local TFO decision of the "Optimal Codec Type"? + +#### A) Should it issue a codec modification on BICN to EFR? + +This would result in a less favourable constellation within the BICN (AMR is better and in average needs less bandwidth than EFR), with the transcoding just shifted to the other MGW B and with identical speech quality. This codec modification would also require additional signalling, speech path interruption and DSP resource handling and this should be avoided at this stage. In the worst case the other MSC-S B could reject the codec modification, because it wants to keep the better constellation on Nb, and so the already undertaken codec modification steps would need to be reverted. + +#### B) MSC-S A issues therefore a mid-call codec negotiation with the Codec List (EFR, FR\_AMR, PCM), where the EFR on the first place in the list indicates that this is the "Local Used Codec" Type in use on the radio interface. The distant MSC-S B, when receiving this Codec List, decides to continue with FR\_AMR in the BICN. No codec modification is performed at this stage, which is good, because it avoids further speech path distortions and unnecessary signalling. The distant MSC-S B returns FR\_AMR as the Selected Codec and the Available Codec List (FR\_AMR, EFR, PCM). + +If MSC-S A would have sent the full "Available Codec List" to its MGW A and this would have offered it in the TFO-Negotiation, then the TFO decision rules would have identified the EFR as the "Optimal Codec Type" and this would have been notified to MSC-S A. The TFO Standard then mandates that MSC-S A "shall" change the Codec Type on Nb. For that reason it is assumed that MSC-S A has not offered EFR as alternative in the TFO-Negotiation, but indicated only the better choice: FR\_AMR. But this is not specified in TS 23.153 [2]. + +Alternatively it could be made optional, whether or not the BICN has to follow the TFO Standard to perform a codec modification in BICN to the TFO-selected "Optimal Codec Type". It seems reasonable to give the BICN this freedom, since it has the overall better "global" overview compared to the local TFO decision. The BICN could then always offer the full "Available Codec List" on the TFO interfaces without the risk of being forced to obey the suboptimal TFO decision. + +**Conclusion:** The codec negotiation of the OoBTC Codec List seems to be necessary (should be "mandatory" and not only "optional") to inform the distant side about the changes on the local radio interface. The first Codec Type offered in the OoBTC Codec List for re-negotiation should be interpreted as the new one used on the radio interface. This should not necessarily mean that it has to be selected for the BICN. Not every change of codec type on one radio interface should lead to a change in the BICN. The local TFO selection of the "Optimal Codec Type" should not be binding for the BICN. Some additional text in TS 23.153 [2] and potentially also in TS 28.062 [4] may be helpful to clarify this. + +### 5.5.3 BSC to BSC call via BICN: second Handover to EFR – AMR – EFR + +Let's assume the same call scenario, where the previous clause ended. + +Now the second ("B") radio interface performs a handover, also from FR\_AMR to EFR. Again the same effects: the second A-Interface also falls out of TFO and back into PCM and a second transcoding stage is added. + +The speech quality degrades further, the speech path delay increases and the DSP resource usage is on its worst. We have now: + +| | | | | | | | | | +|---------------------|---|------------|---|-------------|---|------------|---|---------------------| +| EFR | – | <b>PCM</b> | – | FR_AMR | – | <b>PCM</b> | – | EFR | +| <u>UE1 - GERAN1</u> | – | – | – | <u>BICN</u> | – | – | – | <u>GERAN2 – UE2</u> | + +Now also the second MSC-S B issues a mid-call codec-negotiation with the Codec List (EFR, FR\_AMR, PCM). The distant MSC-S A, when receiving this Codec List, decides that it is now time to change to EFR in the BICN, because now the same Codec Type can be used both on the local radio interface and in the CN. Codec modification within BICN is carried out, which is good, because it brings the whole path back into a constellation where end-to-end transcoding free operation is possible: + +| | | | | | | | | | +|---------------------|---|------------|---|-------------|---|------------|---|---------------------| +| EFR | – | <b>PCM</b> | – | EFR | – | <b>PCM</b> | – | EFR | +| <u>UE1 - GERAN1</u> | – | – | – | <u>BICN</u> | – | – | – | <u>GERAN2 – UE2</u> | + +Now EFR is the Selected Codec and the Available Codec List is (EFR, FR\_AMR, PCM). + +But still PCM is used on the A-interfaces. + +**Problem:** It seems reasonable that the MGWs offer this EFR Codec Type immediately now in their TFO-Negotiations. But this is not specified in TS 23.153 [2]. Instead the MSC-S have to inform their MGWs by sending now the TFO\_Package with the TFO-Codec-List to be used on the TFO Interface, otherwise the TFO with EFR could not establish. + +Now, after a short while, TFO Establishment results in: + +EFR                    – **TFO** –            EFR            – **TFO** –                    EFR +UE1 - GERAN1 –            –            BICN            –            –            GERAN2 – UE2. + +**Problem:** TS 23.153 [2] does also not specify what the TFO-Codec-List should be in that situation. + +Alternative 1: again only the Selected Codec Type (EFR) is included. + +Alternative 2: besides the Selected Codec Type (EFR) also the Alternative Codec Types, here FR\_AMR, are included. This has an influence on the potentially following handovers. + +### 5.5.4 BSC to BSC call via BICN: third handover to AMR – EFR – EFR + +A further subsequent handover on one radio leg (here the "A" one) with a change back to FR\_AMR would again result in a re-negotiation. MSC-S A should again use the Codec List (FR\_AMR, EFR, PCM) to indicate that now FR\_AMR is the "Local Used Codec" Type. + +**Issue 1:** TS 23.153 [2] does not specify what the distant MSC-S B shall do in this case, but leaves it open. + +The distant MSC-S B, when receiving the re-negotiation Codec List can either decide to modify the Selected Codec Type in the BICN to FR\_AMR, because this is the "Distant Used Codec" Type and provides a better constellation within the BICN. Or it can decide to keep the Selected Codec Type, which saves signalling capacity and minimises speech path interruptions. The resulting overall speech quality will be in both cases the same. So far this is not dramatic. + +**Issue 2:** If MSC-S A has offered FR\_AMR as alternative in the TFO-Codec-List (see previous clause), then the TFO Standard mandates that the Codec Type within the BICN shall be modified, because the local TFO decision identified FR\_AMR as "Optimal Codec Type". If, however, the distant MSC-S B has kept the EFR, then the mid-call codec negotiation has to be followed by a codec modification, forced by MSC-S A. This is possible, but of course the necessary signalling for re-negotiation and subsequent codec modification seems to be a waste of signalling resources. In the worst case MSC-S B could reject also this codec modification. + +After a forth handover, where both radio legs are back to FR\_AMR (or both back to EFR), the re-negotiation would clearly result again in end-to-end transcoding free operation. + +**Conclusion:** Some clarifications in TS 23.153 [2] would be helpful to avoid different interpretations and implementations of the many options. Inter-vendor interoperability would most likely improve, resulting in lower signalling loads and less speech path disturbances. + +### 5.5.5 RNC to RNC call via BICN with inter-system handover + +Let's assume the call is established ideally transcoding free between two RNCs with UMTS\_AMR\_2 in Codec Configuration set 14 (12.2 7.95 5.9 4.75). The call provides optimal narrowband speech quality with lowest DSP usage at minimal bandwidth within the BICN: very good. + +Let's introduce a short notation "UMTS\_AMR\_2(14)" to define codec type and configuration (in brackets). + +For this scenario the call looks then like: + +UMTS\_AMR\_2(14) - UMTS\_AMR\_2(14) - UMTS\_AMR\_2(14). +UE1 - UTRAN1 -            BICN            - UTRAN2 – UE2 + +The "Selected Codec Type" is UMTS\_AMR\_2(14), of course. The "Available Codec List", as negotiated at call setup, contains exactly this codec type as well (plus PCM), because UE and UTRAN do not support anything else (in this example). Good, so far. + +NOTE: We assume that the MGWs in the BICN support all UTRAN and GERAN Codec types, but that does not matter here. The current TrFO standard defines that only codecs that are supported in UE plus radio leg plus MGW can be included in the codec negotiation. And this is only UMTS\_AMR\_2(14), plus PCM. + +Now one radio leg performs an inter-system handover to GERAN and the new Codec Type here is FR\_AMR with Codec Configuration set 12 (10.2 6.7 5.9 4.75): FR\_AMR(12). TFO between the new TRAU and the MGW is tested, but not established due to incompatible codec configurations. The TRAU transcodes FR\_AMR to PCM; the MGW transcodes PCM to UMTS\_AMR\_2. + +Now the call looks like: + +``` + +FR_AMR(12) - PCM – UMTS_AMR_2(14) - UMTS_AMR_2(14). +UE1 - GERAN1 - - BICN - UTRAN2 – UE2 + +``` + +This results in a waste of DSP resources in TRAU A and MGWA and an audible loss in speech quality. The bandwidth on the Nb interface is still minimal. + +**Problem 1:** Why was in GERAN not FR\_AMR with Codec Configuration set 14 selected? + +Well, set 12 is the default, standardised set for the FR\_AMR; it provides overall the best compromise for GERAN, considering interoperability with HR\_AMR, which cannot use 12.2 and not 7.95. + +And: how should the MSC-S tell the BSC, which configuration to use? The signalling between MSC and BSC does only carry the codec type, but not the configuration. + +**Conclusion 1:** The AMR configurations on UTRAN and GERAN should be harmonised (see chapter 7.1), then this problem would never occur. The alternative, to include the codec configuration on the MSC-BSC signalling link could require extensive changes to the BSSMAP protocol with potential problems in some BSS architectures with TRAU pools. + +**Problem 2:** What is now the "Selected Codec Type"? What is in the "Available Codec List"? Should the MSC-S restart "Mid-call Codec Negotiation"? What would be the result? + +Well, according to the present TrFO standard MSC-S A can only include FR\_AMR(12) in the OoBTC Codec List (plus EFR, plus PCM). + +If MSC-S B only offers UMTS\_AMR\_2(14), both are not compatible and the result could be: PCM in the BICN: + +``` + +FR_AMR(12) – PCM – PCM – UMTS_AMR_2(14) +UE1 - GERAN1 – – BICN – UTRAN2 – UE2. + +``` + +The speech quality would be identical to the one described above, but the bandwidth in the BICN is now 64kbit/s; the DSP usage is identical, although now in another MGW. This is not at all a reasonable result, or? + +Alternatively, MSC-B could select a codec different from the codec that is used on the radio interface B, in this case FR\_AMR(12). Thus, if MSC-A initiates a mid-call codec negotiation, the result would be. + +``` + +FR_AMR(12) – TFO – FR_AMR(12) – PCM – UMTS_AMR_2(14) +UE1 - GERAN1 – – BICN – – UTRAN2 – UE2. + +``` + +with transcoding FR\_AMR(12) – UMTS\_AMR\_2(14) in MGW-B and FR\_AMR compressed speech in the BICN. + +**Conclusion 2:** The OoBTC standard does not describe the MSC-S behaviour in this case. The description of the Codec List handling could be improved. + +### 5.5.6 BSC to RNC call via BICN with second intersystem handover + +Let's continue with the call scenario of the previous clause: + +FR\_AMR(12) – **PCM** – UMTS\_AMR\_2(14) - UMTS\_AMR\_2(14). + +No codec re-negotiation was performed, otherwise – see above – we could have PCM in the BICN. + +Now also the second radio leg performs an inter-system handover from UTRAN to GERAN and to FR\_AMR(12). The second MSC-S may follow the same principle as the first one, again the two approaches above exist. + +If it also does not start codec re-negotiation, then the call looks like + +``` + +FR_AMR(12) – PCM – UMTS_AMR_2(14) – PCM – FR_AMR(12) +UE1 - GERAN1 – – BICN – – GERAN2 – UE2. + +``` + +We get a remarkable loss in quality, and a substantial DSP load, although we can easily see how the solution should be: FR\_AMR(12) - FR\_AMR(12) - FR\_AMR(12), or FR\_AMR(12) - UMTS\_AMR\_2(12) - FR\_AMR(12), which is equivalent in these cases. + +Alternatively, with codec-renegotiation the result is + +| | | | | | | | | | +|---------------------|---|------------|---|-------------|---|------------|---|---------------------| +| FR_AMR(12) | - | <b>TFO</b> | - | FR_AMR(12) | - | <b>TFO</b> | - | FR_AMR(12) | +| <u>UE1 - GERAN1</u> | - | - | - | <u>BICN</u> | - | - | - | <u>GERAN2 - UE2</u> | + +which is optimal in all respects. + +**Conclusion:** The OoBTC standard does not describe this case optimal. The Codec List handling could be improved. + +**NOTE:** With the proposed Harmonisation of AMR Configurations in place: all call combinations with AMR in GERAN and UTRAN and BICN would always be compatible. No transcoding, no mid-call codec negotiation and no codec modifications would be necessary, resulting in best possible speech quality, with minimal DSP usage, minimal delay and minimal bandwidth. + +But this result should not lead to the conclusion that the Codec List handling in OoBTC can stay as is! We have to consider the other codec types as well, especially AMR-WB and all potential future codec types. + +# 6 General requirements for architectural solutions + +## 6.1 Overall requirements + +- Work between PLMNs (where agreements and intervening networks permit). +- Interworking fully defined with existing 3GPP standards (e.g. TrFO, TFO) +- Support for Interworking with IMS +- Backward compatible with existing GSM (R99) Radio Access networks. +- Backward compatible with existing terminals +- Does not require implementation of non-standard interfaces on the Media Gateway (e.g. Ater). +- Support for Local Lawful Intercept requirements +- Provide service and bearer separation for the development of standardised and non-standardised services. + +**NOTE:** Annex A gives a detailed description of an example for migrating a service to TrFO. + +## 6.2 Status of specifications for TFO and TrFO in 3GPP + +### 6.2.1 Support of codec types in TFO and TrFO on various interfaces + +The following table is extracted from TS 26.103 [5] (Codec List in GSM and UMTS) and then modified to include the interfaces: Abis/Ater, A (TFO), Iu, Nb (TrFO), Nc and Mc (OoBTC). This table now gives the overview to which extend which codec type is supported. + +Only the GSM\_FR, GSM\_HR and GSM\_EFR are not fully supported: the framing on Nb is not specified. + +Table 6.1.1-1: Support of codec types in TFO and TrFO + +| | TDMA EFR | UMTS AMR 2 | UMTS AMR | (GSM) HR AMR | (GSM) FR AMR | GSM EFR | GSM HR | GSM FR | +|-------------------------|-----------|------------|----------|--------------|--------------|-----------|--------|--------| +| GERAN GMSK<br>Abis/Ater | no | no | no | yes | yes | yes | yes | yes | +| GERAN 8PSK | no | no | no | no | no | no | no | no | +| UTRAN Iu | yes<br>no | yes | yes | no | no | yes<br>no | no | no | +| TFO | no | yes | yes | yes | yes | yes | yes | yes | +| TrFO (Nb) | no | yes | yes | yes | yes | no* | no | no | +| OoBTC (Nc, Mc) | no | yes | yes | yes | yes | yes | yes | yes | + +| | | | OHR AMR-WB | OFR AMR-WB | OHR AMR | UMTS AMR-WB | FR AMR-WB | PDC EFR | +|-------------------------|----|--|------------|------------|---------|-------------|-----------|-----------| +| GERAN GMSK<br>Abis/Ater | | | no | no | no | no | yes | no | +| GERAN 8PSK | | | yes | yes | yes | no | no | no | +| UTRAN Iu | | | no | no | no | yes | no | yes<br>no | +| TFO | | | yes | yes | yes | yes | yes | no | +| TrFO (Nb) | | | yes | yes | yes | yes | yes | no | +| OoBTC (Nc, Mc) | no | | yes | yes | yes | yes | yes | no | + +\* only the SID-Framing on Nb is missing for the GSM\_EFR. + +# 7 Requirements and architectural solutions for Resource Savings + +- Reduce the total number of transcoding equipment in a A/Gb mode network using R4 core network architecture. This is very important for growing A/Gb mode networks. + +Clauses 4 and 5 include detailed comparisons of the resource savings possible with TrFO and TFO solutions. + +## 7.1 AMR-NB configurations + +The AMR Codec algorithm comprises eight modes. More than hundred combinations of 1, 2, 3 or 4 modes out of 8 are possible, not all are reasonable, only a few are necessary for most applications. TS 28.062 [4] lists the 15 "preferred" AMR Configurations. + +Without further agreements the likelihood is small, that two independent radio legs would chose the same or compatible configurations. With an additional TrFO link in between, which selects the configuration potentially also independently, the situation does by no means improve. + +The TFO-Decision Rules, as formulated in TS 28.062 [4], define preferred configurations for HR\_AMR and for FR\_AMR. With these AMR Configurations it is guaranteed that any combination on both radio access sides and the core network in between does (nearly) always lead to the optimal communication quality under the given restrictions. The Maximum Rate Control Algorithm, integrated into the TFO Handlers, do automatically restrict the rates to the common ones, in case the configurations are different. + +The UTRAN groups preferred a different AMR-NB configuration for UTRAN. + +With this GSM-GSM calls and UTRAN-UTRAN calls would work fine in TFO/TrFO, but GSM-UTRAN calls require at least one unnecessary transcoding, in practise it would mean two transcoders are inserted: + +AMR (config-GSM) – PCM – AMR (config-UTRAN). + +The OoBTC at call setup can not easily decide, which configuration to use inside the CN on the TrFO-link. + +The specified mechanisms to resolve the situation could use an in-call-modification immediately after call setup, when the overall call scenario is known after the TFO Negotiation. But also this can only work, if UTRAN is accepting to be modified to the preferred GSM configurations. So this is not really a nice solution, it costs a substantial amount of additional signalling and speech path disruptions during the (unnecessary) modification. + +Every handover could jeopardise the configuration again. + +Given the importance of GSM-to-UTRAN calls and the expected handovers between GSM and UTRAN in many dual-mode networks this is hardly acceptable. + +### **Conclusion:** + +It is proposed that the 3GPP standardisation groups cooperate to decide upon a common configuration for AMR, to include it into the specifications and to give it a dominant importance. This configuration would be preferred for systems supporting TFO and/or TrFO. + +## **7.2 AMR-WB configurations** + +For the AMR-WB Codec Types one basic, mandatory configuration with the three lowest modes (AMR-WB 6.60 + 8.85 + 12.65 kbit/s) is mandatory for all radio access technologies that offer AMR-WB capability. One of two optional modes may be added: either 15.85 or 23.85 kbit/s. This is described in clause 5.4.0 of TS 26.103 [5] + +With these three different AMR-WB Configurations it is guaranteed that any combination on both radio access sides and the core network in between does (nearly) always lead to the optimal communication quality under the given restrictions. The Maximum Rate Control Algorithms, integrated into the TFO Handlers, do automatically restrict the rates to the common ones, in case the configurations are different. For a pure TrFO connection the Rate Control algorithm should be identical, but it is - so far - not described anywhere. + +### **Conclusion:** + +The configurations for AMR-WB are well suited and no change is necessary + +# --- **8 Requirements and architectural solutions for bandwidth savings** + +## **8.1 Background** + +The 3GPP architecture must support bandwidth usage efficiency on the most highly utilized user plane interfaces in the system. Candidates for optimisation include: + +- The path between RNC and MGW. This is the Iu interface and is already optimised. +- The path between MGWs within a BICN. When this path uses a packet network, it is the Nb interface and is optimised for TrFO. +- The path between BSC and MGW. This is a combination of the Ater and A interfaces via the TRAÜ. The Ater interface is already optimised but the A interface uses 64 kbps facilities on a TDM interface. In this form, the A interface is not a candidate for bandwidth optimisation, but is consistent with TFO. +- The path between MGWs in different PLMNs. This interface is typically TDM and may be consistent with TFO if no DCMEs or other non-TFO IPE (e.g. echo cancellers) are in the path. If a packet transport network is available between the PLMNs, then OoBTC may be applicable. + +Other clauses describe how harmonized OoBTC and TFO procedures enable some combination of TrFO, TFO and transcoding at the edge in various scenarios involving media flow on these paths. The A and TDM interfaces do not yet support the same degree of bandwidth usage efficiency as the Ater, Iu and Nb interfaces. + +If a path between MGWs within a BICN does not already use TrFO over an Nb interface, it can be optimised by doing so. The path between MGWs may used TFO. The path between PLMNs may also support either TFO or TrFO. If a path + +between BSC and MGW is significantly comprised of an A interface, no standard method exists for realizing higher bandwidth usage efficiency on this portion of the path. The next clause includes discussion of two alternative architectures to address this issue. + +## 8.2 Requirements + +- Reduce bandwidth requirements for A/Gb mode traffic in the packet transport network between Media Gateways across Nb interface. +- Enact transcoding at the edge of the network for calls to PSTN or other incompatible networks. + +## 8.3 Architectural solutions + +### 8.3.1 Ater interface to the MGW + +NOTE: Issues related to the signalling aspects have not been studied in this TR. + +**Basic Configuration:** + +![Diagram of Basic Configuration: BSC connected to TRAU, which is connected to MGW via an A interface. The BSC is connected to the TRAU via an Ater interface.](47e8c2042061e08a14e012472e9fdbaa_img.jpg) + +``` +graph LR; BSC[BSC] -- Ater --> TRAU[TRAU]; TRAU -- A --> MGW[MGW]; +``` + +Diagram of Basic Configuration: BSC connected to TRAU, which is connected to MGW via an A interface. The BSC is connected to the TRAU via an Ater interface. + +**Configuration after Ater added to MGW:** + +![Diagram of Configuration after Ater added to MGW: BSC connected to a TRAU which is inside the MGW. The BSC is connected to the TRAU via an Ater interface.](68ca7669d38a3c31f5a2c3a06fa802e3_img.jpg) + +``` +graph LR; BSC[BSC] -- Ater --> TRAU[TRAU]; subgraph MGW [MGW]; TRAU; end; +``` + +Diagram of Configuration after Ater added to MGW: BSC connected to a TRAU which is inside the MGW. The BSC is connected to the TRAU via an Ater interface. + +**Figure 8.3.1-1: BSC to MGW path before and after adding ater interface to MGW** + +Figure 8.3.1-1 depicts the BSC to MGW path as it would appear if an Ater interface is standardized for the MGW, and the TRAU function is performed within the MGW. This corresponds to the functional distribution RNC and MGW across the Iu interface. The advantage of this configuration is that all scenarios described herein using Nb packet transport between MGWs can support end-to-end OoBTC procedures for TrFO or transcoder at the edge since there is no need to perform TFO on any interface. Harmonized OoBTC/TFO procedures support all other scenarios described herein that include this configuration option for the BSC to MGW path, may include Nb packet transport between some MGWs in the path, and include at least one TDM interface between some pair of MGWs in the path, e.g., between PLMNs. But in the case there is TC at the edge of the network with TDM transit network to another TrFO network then TFO on this transit network will improve speech quality. + +### 8.3.2 MGW collocated with TRAU + +#### **Basic Configuration:** + +![Diagram of Basic Configuration: BSC connected to TRAU via Ater interface, and TRAU connected to MGW via A interface.](d793cf7c174b89eb024d132f00679787_img.jpg) + +``` + +graph LR + BSC[BSC] -- Ater --> TRAU[TRAU] + TRAU -- A --> MGW[MGW] + +``` + +Diagram of Basic Configuration: BSC connected to TRAU via Ater interface, and TRAU connected to MGW via A interface. + +#### **Configuration Option 1 after Collocating TRAU with MGW:** + +![Diagram of Configuration Option 1: BSC connected to a dashed box containing TRAU and MGW via the Ater interface. The TRAU and MGW are connected by an A interface.](1c953f32bd34345dfd68fddf8a3736d6_img.jpg) + +``` + +graph LR + BSC[BSC] -- Ater --> DashedBox[ ] + subgraph DashedBox [ ] + TRAU[TRAU] -- A --> MGW[MGW] + end + +``` + +Diagram of Configuration Option 1: BSC connected to a dashed box containing TRAU and MGW via the Ater interface. The TRAU and MGW are connected by an A interface. + +#### **Configuration Option 2 after Collocating MGW with TRAU:** + +![Diagram of Configuration Option 2: BSC connected to a dashed box containing TRAU and MGW via the Ater interface. The TRAU and MGW are connected by an A interface. The MGW is then connected to another MGW via an Nb interface.](ca4d4ff86cf319ed7cc36a1ecda29101_img.jpg) + +``` + +graph LR + BSC[BSC] -- Ater --> DashedBox[ ] + subgraph DashedBox [ ] + TRAU[TRAU] -- A --> MGW1[MGW] + end + MGW1 -- Nb --> MGW2[MGW] + +``` + +Diagram of Configuration Option 2: BSC connected to a dashed box containing TRAU and MGW via the Ater interface. The TRAU and MGW are connected by an A interface. The MGW is then connected to another MGW via an Nb interface. + +**Figure 8.3.2-1: Options for BSC to MGW path after collocating MGW with TRAU** + +Figure 8.3.2-1 depicts two options for how the BSC to MGW path would appear if either the TRAU is moved to be collocated with (in physical proximity to) the MGW, or a new MGW is introduced and collocated with the TRAU. Either approach shortens the portion of the BSC to MGW path comprising an A interface to a negligible portion of the overall path. Harmonized OoBTC/TFO procedures support all scenarios described herein that includes either of these configuration options for the BSC to MGW path. + +# 9 Requirements and architectural solutions for speech quality Improvements + +## 9.1 Requirements + +It is proposed that the TR investigates the requirements for speech quality enhancement features + +The general requirement to ensure maximum speech quality that TrFO and TFO attempt to meet is to prevent unnecessary transcoding on mobile-to-mobile and mobile to fixed network. TSG SA WG4 has studied the degradation to speech quality for mobile to mobile calls with tandeming of speech codecs, and the following is a summary of conclusions from the reports TR 26.975 [6] and TR 26.976 [7]. + +Clause 7 of TR 26.975 [6] shows that tandeming tests were conducted by SA4 in the past and they showed that the degradation in single tandeming compared to TFO between EFR and AMR12.2 is not significant to the user. To quote: "Tandeming with the clean speech error free 12.2 and 10.2 modes of AMR do not significantly degrade the single encoding performances of any of the AMR codec (modes) or existing GSM codecs." Transcoding between FR and AMR, however, does introduce degradation. + +## 9.2 Architectural solutions + +### 9.2.1 Mobile to mobile calls scenarios: 5.1.1 and 5.1.3 + +For mobile to mobile calls between a BSC and an RNC within a PLMN, the call scenarios in clause 5 show that the existing architecture can employ TFO on the A interface supporting AMR-WB / AMR / EFR / FR / HR, and compressed speech (TrFO) on the Iu interface supporting AMR-WB / AMR. If compatible codecs are available, then the network need not perform any transcoding. OoBTC can be used within the BICN and TrFO be established between the MGWs, thus achieving optimal bandwidth saving with optimal voice quality. If compatible codecs are not available, + +a single transcoding point at the MGW then exists between GSM on one side and UTRAN on the other and, therefore, the requirement to prevent unnecessary transcoding in order to not perceptibly degrade the speech quality is fulfilled. Again the BICN can operate in TrFO to achieve optimal bandwidth savings. + +For BSC to BSC calls via a BICN, the network should not need to perform any transcoding when the mobiles share at least one common codec. In some cases, e.g. if only one side supports AMR in multi-mode configuration and the other side supports only single-mode codecs (FR / HR / EFR), it needs to be considered whether to perform a single transcoding in order to gain optimal voice quality. In such cases, the radio error robustness of the AMR may be more important than the TFO connection of a single-mode codec. For details see TS 28.062 [4], clause F.3. + +Whether a transcoding-free link can be established through the BICN (for BSC - BSC or BSC - RNC calls) depends on the codec types used for TFO. If at least one side supports AMR, or AMR-WB or EFR, then optimal bandwidth saving and optimal voice quality can be achieved. Otherwise a 64kbps transparent PCM channel with TFO has to be established through the BICN for optimal voice quality. The reason is that up to 3GPP REL5 no Nb framing is specified for FR and HR. Also, though Nb (and Iu) framing for EFR is supported according to TS 26.103 [5], the specification in TS 26.102 [8] does not seem complete. + +### 9.2.2 Mobile to PSTN calls: scenarios 5.2.x + +For GSM/UMTS mobile to PSTN calls, the existing solutions allow for a single, necessary, transcoding point within the MGW at the edge of the BICN, close to the point of interconnect. + +## 9.3 Summary + +Architectural solutions exist for the common interworking scenarios of mobile to mobile/PTSN calls, which avoid or minimise degradation of speech quality. Optimal Voice Quality together with Optimal Bandwidth Saving is possible for AMR, AMR-WB and EFR. For EFR the Nb (and Iu) framing does not seem completely specified and for FR and HR the optimal bandwidth saving would need the Nb framing for these codec types to be specified. A useful output of this TR would be for these (or at least EFR) be standardised for Nb framing in order for a more optimal voice quality to be accomplished. + +# --- 10 Requirements and architectural solutions for avoiding duplication in transcoder development + +## 10.1 Background and requirements + +The GSM and UMTS systems will co-exist for many years. Most dual-mode operators have currently significantly less UMTS spectrum than they have GSM spectrum, so, these operators have to optimise their utilisation of the combined spectrum pool. Other operators may just have GSM spectrum or just UMTS spectrum. + +One potential operational strategy is that dual mode mobiles may be camped on 3G cells (e.g. to help provide access to fast PS data services), but occasionally (or always) be handed over to 2G for voice calls. However, until the RNC has gathered GSM neighbour cell measurements, the voice call must be handled by the 3G cell and a transcoder is needed in the MGW. Following the handover to 2G, the 2G TRAU will be connected in tandem with the 3G MGW. + +Hence the introduction of a new speech codec (particularly one that is best suited for mobile to mobile calls, like AMR-WB) requires support for that codec in both 2G and 3G coverage areas. + +NOTE: Over GSM's 12 years, 4 new speech coders have been developed (HR, EFR, AMR, AMR-WB). The development of additional codecs in the future probably depends on the uptake of AMR-WB. With the current architectures for GSM and UMTS this requires both TRAUs in the 2G BSS and Transcoders in 3G MSCs (non-layered architecture) and/or Media GateWays (layered architecture) to be developed and installed. + +This has at least the following disadvantages, e.g.: + +- increased development cost; +- increased deployment costs, since the total transcoding capacity is split into TRAU and MGW pools; +- new speech codecs are difficult to use until the slowest of MGW and TRAU development is finished; + +- d) if/when GSM is decommissioned, TRAUs in the BSS will probably have to be discarded; +- e) The requirement for extra DSP power within the TRAUs in the BSS may require other parts of the BSS to have to be replaced. + +Hence it is interesting to consider how a graceful migration of transcoding functionality from BSS to MGW could be achieved and what the potential migration strategies and costs could look like. + +## 10.2 Architectural solutions + +### 10.2.1 A-ter interface to the MGW + +#### 10.2.1.1 Description / concept + +If new transcoders are only implemented on the MGW, then the MGW will need to be able to be connected to GSM BTSes (via the BSC). Given that there is a very large installed base of GSM base stations but only a limited installed base of MGWs, it seems more logical that the MGW adapts itself to handle the existing interface to the BTS rather than the other way round. + +On the user plane, this A-bis/A-ter interface is defined in TS 48.060 [10] and TS 48.061 [11]. Given that multi-vendor interoperability is required for TFO, and the TFO standard (TS 28.062 [4]) is closely related to TS 48.060 [10]/TS 48.061 [11], it seems reasonable to assume that TS 48.060 [10]/TS 48.061 [11] might be made into open standards. + +Many BSS vendors support TRAUs located at the MSC site but with control from the BSS. This control plane, comprising e.g. the selection of the codec type, the allocation of TRAU resources, the handover handling, the fault handling, is currently vendor specific. For O+M purposes remote TRAUs are generally controlled from the BSC. However, if the transcoding would be located within the MGW, then the MGW O+M is used for this task. + +For the A interface control plane, the MSC already controls the allocation of the circuit on the user plane. + +#### 10.2.1.2 Difficulties with this concept + +- a) This approach would introduce legacy design constraints into the MGW and may restrict future development of the MGW. +- b) The complexity of the MGW and the necessary know-how concentration would increase substantially. +- c) Neither GSM-only nor UMTS-only operators would have a gain of that additional functionality and complexity. +- d) The MGW would need to support the functionality described in TS 48.060 [10] and TS 48.061 [11]. This includes support for the TRAU frame structure and for the frame alignment protocol, which is currently running between TRAU and BTS, and provides e.g. procedures for frame synchronisation and time alignment between TRAU and BTS. At least one vendor indicates that there are obvious errors still in TS 48.060 [10], explicitly in the Time Alignment clause. They have not been corrected so far and the only reasonable explanation for that is: every vendor found his own solution to the problem and did not consider it worth the effort to correct the TS 48.060 [10]. A complete standardisation of the Abis/Ater user plane would very likely require a compromise there and an adaptation of existing GSM base stations. + +NOTE 1: It is FFS as to whether this error was corrected during the development of modern codec types, like AMR and AMR-WB. + +NOTE 2: For codecs such as AMR-WB, TFO (or similar) needs to be used in the core network, and, while in TFO mode, the Time Alignment functionality is not required. + +- e) Development effort in the DSP-kernel software might not be saved, because this can be reused also in the existing concept in TRAU and MGW. But extra development on the MGW would be needed for the Input/Output-Interfaces and the Framing protocols. So the saving in development costs would not be as big as originally hoped. Considering that GSM-only operators will exist as well, the development costs would rather increase, because the existing GSM architecture will have to be maintained in parallel. +- f) The introduction of a new Codec Type in GSM requires in any case the upgrade of MSCs, BSCs, BTSs and the signalling interfaces between them. No development costs can be saved here. + +- g) The Operation and Maintenance functions of the BSS need modification (whether new O+M functionality is needed in the BSS, or, whether existing BSS functionality only needs to be disabled is FFS and the impact will be implementation dependent). +- h) It should also be noted that the A interface uses 64 kbit/s channels, while TS 48.060 [10]/TS 48.061 [11] use different data rates, e.g. 16 kbit/s and sometimes 8 and/or 32 kbit/s. The mapping between these two is currently defined BSS internally. For CS data calls with higher bit rates, allocation of up to four 16 kbit/s traffic channels needs to be considered. +- i) For the Mc interface between MSC-Server and MGW protocol extensions would be required. +- j) It is for further study whether the MGW would need to support some of the O+M procedures described in TS 48.060 [10]/TS 48.061 [11] and/or TS 52.021 [12]. However, with the TRAUs in the BSS, the BSS should check that the TRAU is working correctly before it is connected to the BTS. If the TRAU is moved to the MGW, then this check should be performed by the MGW and the need for the BSS to signal O+M commands to the TRAU is unclear, in any case it would be different than today. +- k) For CS data calls the TRAU provides rate adaptation, as described in clause 6.7 of TS 48.060 [10] and clause 6.7 of TS 48.061 [11]. The impact on the MGW in case of Ater to the MGW needs some further study. +- l) some internal handovers may have to be performed as external "intra BSS" handovers, because the location of the transcoder may change from the TRAU into the MGW or vice versa. This causes typically higher signalling load and longer speech path interruptions. +- m) The BSC performs Codec Type and radio resource selection based on its knowledge on the dynamically changing radio situation. This results in the selection of a half rate or full rate radio channel, and, legacy BTSs may further restrict the choice of codec. This may require reallocation of transcoding resources in the MGW or TRAU. This could be achieved by slightly modifying the "switch circuit pool" functionality already specified on the A interface. +- n) Current MGWs have no need to support the basic GSM HR and FR codecs. + +#### 10.2.1.3 Migration aspects + +A large number of existing UEs and base station transceivers support only the early GSM codecs FR, HR. On the other hand, according to TS 26.103 [5], only EFR, AMR and WB-AMR are defined for Iu mode. This implies that MGWs according to 3GPP REL-4 and REL-5 specifications are not mandated to support the legacy codecs FR and HR - and given that all Iu mode UEs support AMR, there is so far little motivation to support EFR. + +Note: EFR is nearly identical to one of the AMR codec modes, and, FR and HR are much less computationally intensive than AMR. Nevertheless the development and verification effort is in a first order approximation similar for all codec types. + +Migration from the existing architecture to the "Ater to the MGW" architecture would thus require one of the following three options: + +1. Terminate the support for HR and FR codecs. This would contradict the desire to use the existing installed base stations including their transceivers - and it will take time until all UEs in the field support at least EFR! The feasibility of this is uncertain. +2. Implement the legacy codecs and related procedures (e.g. TFO) in the MGW. This is possible, but: is it desirable to spend the implementation effort to implement legacy technology? Indeed, disadvantage a) described in clause 10.1 would remain. It is FFS what is the implementation effort to implement legacy codecs in the MGW, however, it should be noted that current mobile devices are capable of implementing FR, HR, EFR and AMR. +3. Support transcoding in the TRAU for legacy codecs and transcoding in the MGW for new codecs at the same time in the same network at both sides of the same A/Ater interface configuration. This seems rather complex and seems to contradict the desire for resource savings. From a technical perspective, at least the following issues would require attention: + - Change of codec during a call, where one codec is supported in the TRAU and the other in the MGW; + - Change between voice and CS data during a call; + - Handover scenarios. + +The MGW would need to support A and Ater user planes. Note that there would still be duplicated implementation effort (disadvantage a) in clause 10.1) in case transcoding related enhancements were introduced in future releases, which are not restricted to a specific voice codec, for example voice quality enhancements (VQE). + +While it is assumed that introduction of a new codec to both UMTS and GSM systems will be easier, once the "Ater to the MGW architecture" is in place, the first new codec requires the implementation of the new architecture; thus the deployment of this codec might be delayed rather than accelerated. + +#### 10.2.1.4 Sample message flow + +A sample message flow for a mobile terminating call with Ater interface going to the MGW is shown below. + +![Sequence diagram showing the message flow for a mobile terminating call with Ater interface going to the MGW. The diagram involves five lifelines: MSC, MGW, BSC, BTS, and UE. The flow starts with an IAM message from an external source to the MSC, followed by a Paging + Security message from the MSC to the BTS. The BSC then sends a SETUP message to the UE. The UE responds with a CALL CONFIRMED message containing a speech codec list. The MSC then sends an Establish bearer for A-ter message to the MGW. The MGW responds with an Ack message. The MSC then sends an ASSIGNMENT REQUEST message to the BSC. The BSC sends a CHANNEL ACTIVATION message to the BTS. The BTS responds with 48.060 frames. The BSC then sends a CHANNEL ACTIVATION ACK message to the MGW. The BSC also sends an ASSIGNMENT COMMAND message to the UE. The UE responds with an ASSIGNMENT COMPLETE message. The BSC then sends an ASSIGNMENT COMPLETE message to the MSC. Finally, the BSC sends an ALERTING message to the UE.](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +``` + +sequenceDiagram + participant External + participant MSC + participant MGW + participant BSC + participant BTS + participant UE + + Note left of MSC: 1 IAM, (distant) Codec List + External->>MSC: 1 IAM, (distant) Codec List + MSC->>BTS: Paging + Security + BSC->>UE: 2 SETUP + UE-->>BSC: 3 CALL CONFIRMED (UE speech codec list) + MSC->>MGW: 4a Establish bearer for A-ter (Circuit ID code, reduced codec list) + MGW-->>MSC: 4b Ack (selected codec type, sub-mux scheme) + MSC->>BSC: 5 ASSIGNMENT REQUEST (Circuit ID Code, Channel type (speech, Full or half rate TCH; permitted speech versions=selected codec, codec config), "TC in MGW", sub-mux scheme) + BSC->>BTS: 6 CHANNEL ACTIVATION (channel mode = selected codec) + BTS-->>BSC: 48.060 frames (frame type = selected codec) + BSC-->>MGW: CHANNEL ACTIVATION ACK + BSC->>UE: ASSIGNMENT COMMAND (channel mode = selected codec) + UE-->>BSC: ASSIGNMENT COMPLETE + BSC-->>MSC: ASSIGNMENT COMPLETE + BSC->>UE: ALERTING + +``` + +Sequence diagram showing the message flow for a mobile terminating call with Ater interface going to the MGW. The diagram involves five lifelines: MSC, MGW, BSC, BTS, and UE. The flow starts with an IAM message from an external source to the MSC, followed by a Paging + Security message from the MSC to the BTS. The BSC then sends a SETUP message to the UE. The UE responds with a CALL CONFIRMED message containing a speech codec list. The MSC then sends an Establish bearer for A-ter message to the MGW. The MGW responds with an Ack message. The MSC then sends an ASSIGNMENT REQUEST message to the BSC. The BSC sends a CHANNEL ACTIVATION message to the BTS. The BTS responds with 48.060 frames. The BSC then sends a CHANNEL ACTIVATION ACK message to the MGW. The BSC also sends an ASSIGNMENT COMMAND message to the UE. The UE responds with an ASSIGNMENT COMPLETE message. The BSC then sends an ASSIGNMENT COMPLETE message to the MSC. Finally, the BSC sends an ALERTING message to the UE. + +NOTE: Some details of this message flow are still for further study. + +**Figure 10.2.1.4-1: Message flow for a mobile terminating call with A-ter interface going to the MGW** + +- 1 The call is routed to the terminating MSC; the Codec List is included + +- 2 The MSC establishes the GSM radio link with the mobile and sends the SETUP message. +- 3 + - a) The mobile indicates what codecs it supports in the CALL CONFIRMED message. + - b) The MSC determines that it wants to use a "new" codec that is supported only by the MGW, but not supported by the TRAUs in the BSS + - c) The MSC selects a sub-set of the codecs (including now only the "new" ones supported by the MGW), allocates the Circuit ID code, and sends an "establish 16 kbit/s bearer for A-ter" message to the MGW. +Comments: extra signalling is needed if 8kbit/s or 32k sub-multiplexing of TDM lines is needed. Use of 16 kbit/s on the A-ter may require extra bandwidth on the BSC-MSC interface. +- 4 The MGW selects transcoding resources, possibly further restricting the sub-set offered by the MSC and associates them with the TDM sub channel indicated by the MSC on the interface to the BSS. +- 5 The MSC copies the CIC and codec information into the Ater interface Assignment Request message. A new IE is added to this message to indicate that the MSC has allocated a TC in the core network and hence that the BSS shall not perform transcoding. +- 6 + - a) The BSC accepts the speech codec type (including all necessary parameters like codec configuration an sub-multiplexing scheme) provided by the MSC and selects the radio channel that the BTS will use. + - b) With the general A-bis architecture, the selection of the radio channel also identifies the A-bis user plane channel that will be used. + - c) The BSC through connects the A-bis user plane channel to the 16 (8, 32) kbps Ater circuit to the MGW, identified by the CIC provided by the MSC. + - d) The BSC commands the BTS to activate the radio channel and to start transmission/reception on the A-bis user plane. + - e) If at step (a) the BSC knows that the BTS cannot support the channel coding for the codec indicated by the MSC, or, for other reasons the assignment fails, then the BSCS sends an ASSIGNMENT FAILURE with the cause "switch circuit pool" and the "circuit pool list" information element. The MSC uses this information to adjust its choice of codec. (see 48.008 [17] clause 3.1.1.2). +- 7 The BTS sends TRAU frames directly to the TC inside the MGW. These TRAU frames carry information on the selected codec type and other details. The MGW responds with TRAU frames and obeys the procedures, e.g. time alignment etc. + +# --- 11 Conclusions + +The extended set of scenarios provided in this Technical Report has enabled a detailed examination of the requirements identified within the report. These scenarios have gone beyond the existing basic set of scenarios provided in the current + +stage 2 documents e.g. TS 23.153 [2]. Some scenarios, e.g. intra UTRAN handover or call forwarding, have not been documented because no further insights were expected to have come from this. + +This Technical Report has also identified that architectural solutions exist for all of the investigated interworking scenarios for 2G and 3G access for mobile-to-mobile and mobile-to-PSTN calls, which + +- maximise the perceived speech quality; +- minimise the core network bandwidth; +- minimise the usage of signal processing devices in the path. + +The study briefly addressed the interworking of CS speech with IMS (see clause 5.4) and triggered the related work ongoing in CN3 in the context of TS 29.163 [13] + +This study has also identified that there are a few issues that could benefit from further standardisation work. These include: + +- Different AMR-NB configurations are preferred for GERAN and UTRAN. A common AMR-NB configuration would improve the situation for GERAN-UTRAN calls (see clause 7.1). Changes would be necessary in TS 26.103 [5] and TS 28.062 [4] and some dependent specifications (e.g. TS 23.153 [2]). +- The standardisation of additional codec framing for EFR over the Nb interface would be of benefit for the GERAN-GERAN calls (see clause 9.3). Changes would be necessary in TS 26.101 [18] and TS 26.102 [8]. +- Some clarifications in the OoBTC could improve inter-vendor interoperability and minimize signalling load (see clause 5.5). Changes would be necessary in TS 23.153 [2]. +- It could be made optional for the MSC-S in OoBTC to follow the local TFO decision on the "Optimal Codec Type" (see clause 5.5.2). Changes would be necessary in TS 23.153 [2] and TS 28.062 [4]. +- Further clarifications on Inter-PLMN signalling could be provided to include in addition to TFO/PCM also BICC and potentially SIP. No problems are expected with using BICC between CS-PLMNs (see clauses 4.4 and 4.5). The gain of using SIP for the interconnection of CS-PLMNs has not been studied in its entirety within this TR (see clause 4.5). + +SA2 recommends that interested companies bring the identified issues forward in the relevant working groups. + +# Annex A: Example for migrating a service to TrFO + +## A.1 Service description + +As an example for a non-standardised service, a "personal ring back tone (PRBT) service" is considered, where the B-party can choose the ringing tone that the A-party will hear, e.g. a song. A media server inserts media (e.g. the song) towards the calling A-party, as long as the B-party is alerted. + +## A.2 Realization + +### A.2.1 Overview + +In clause 2.2 it is described how the service might be realised in the following network scenarios: + +1. A network according to R99 specifications. +2. A network with packet transport, BICC and TrFO/OoBTC with integrated MSC. +3. A network with packet transport, BICC and separation of MSC in MSCS and MGW without TrFO/OoBTC. +4. A network with packet transport, BICC, TrFO/OoBTC and separation of MSC in MSCS and MGW. + +The analysis of all four scenarios allows distinguishing the TrFO/OoBTC specific impact from the impact arising from the separation of call control and bearer. It also illustrates two different migration paths for introduction of TrFO/OoBTC and Rel-4 architecture: $1 \rightarrow 2 \rightarrow 4$ and $1 \rightarrow 3 \rightarrow 4$ . + +NOTE: The descriptions are not intended as a complete service description as this is and should remain a non-standardised service. Thus only the aspects relating to TrFO introduction and the understanding of the underlying assumptions are detailed. + +### A.2.2 High level description + +Once the B party GMSC queries the HLR, it receives an indication that the B-party has subscribed to the PRBT service. Thus, after applying the usual call handling, the B-party GMSC sets-up a connection with a media server, where the ringing tone is stored. The media server inserts the ringing tone. Once the B-party answers the call, the media server is disconnected. + +In all what follows, we assume a mobile-to-mobile call within a network, where the VMSC of the A-party has GMSC functionality. The entities involved in the service are shown in figure A.1. + +![Figure A.1: Functional entities involved in the Service. The diagram shows a central box labeled 'VMSC A GMSC B'. To its left is 'UE A' connected by a horizontal line. To its right is 'VMSC B' connected by a horizontal line, which is further connected to 'UE B' by another horizontal line. Above 'VMSC A GMSC B' is a 'Media Server' connected by a vertical line. Below 'VMSC A GMSC B' is 'HLR B' connected by a vertical line.](a6cf7c02a60c336e0934b5ea40e35b49_img.jpg) + +``` +graph TD; UE_A[UE A] --- VMSC_A_GMSC_B[VMSC A GMSC B]; VMSC_A_GMSC_B --- VMSC_B[VMSC B]; VMSC_B --- UE_B[UE B]; VMSC_A_GMSC_B --- Media_Server[Media Server]; VMSC_A_GMSC_B --- HLR_B[HLR B]; +``` + +Figure A.1: Functional entities involved in the Service. The diagram shows a central box labeled 'VMSC A GMSC B'. To its left is 'UE A' connected by a horizontal line. To its right is 'VMSC B' connected by a horizontal line, which is further connected to 'UE B' by another horizontal line. Above 'VMSC A GMSC B' is a 'Media Server' connected by a vertical line. Below 'VMSC A GMSC B' is 'HLR B' connected by a vertical line. + +Figure A.1: Functional entities involved in the Service + +The GMSC B plays a key role in the service. Therefore in the following VMSC A = GMSC B will often be referred to as MSC for simplicity. + +### A.2.3 Message flow for a Release 99 network + +Figure A.2 shows a possible message flow for a R99 network. TDM transport with G.711 in the core network is assumed. Moreover, it is assumed that TDM transport and G.711 are used between media server and GMSC, and that AMR is used between UE A and VMSC A in Iu mode. + +![Sequence diagram showing message flow in a R99 network between an MSC and a Media Server.](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) + +``` +sequenceDiagram + participant UE + participant MSC + participant HLR + participant Transcoder + participant MediaServer as Media Server + Note left of MSC: Insert Transcoder + Note right of MediaServer: Send Media towards A-party + Note right of MediaServer: Stop Media + + UE->>MSC: 1 SETUP + MSC->>HLR: HLR Interrogation + HLR-->>MSC: + MSC->>MediaServer: 2 IAM + MSC->>UE: 3 RAB Ass Req + Note left of MSC: 4 Bearer Establishment and User Plane Initialisation + MSC->>UE: 5 RAB Ass Resp + MSC->>MediaServer: 6 Continuity + MediaServer-->>MSC: 7 ACM + MSC->>MediaServer: 8 IAM + MediaServer-->>MSC: 9 ACM + MSC->>UE: 10 Alerting + MediaServer-->>MSC: 11 ANM + MSC->>UE: 12 Connect + MSC->>MediaServer: 13 REL + MediaServer-->>MSC: 14 RLC +``` + +The diagram illustrates the message flow for a call in a R99 network. It involves an MSC (Mobile Switching Center) and a Media Server. The flow starts with a SETUP message from the UE to the MSC. The MSC then performs an HLR Interrogation. Upon receiving the response, it sends an IAM (Initial Address Message) to the Media Server. The MSC also sends a RAB Ass Req (Radio Access Bearer Assignment Request) to the UE, followed by a Bearer Establishment and User Plane Initialisation. The MSC then sends a RAB Ass Resp (Radio Access Bearer Assignment Response) to the UE. The Media Server sends a Continuity message to the MSC, which responds with an ACM (Address Complete Message). The MSC then sends an IAM to the Media Server, which responds with an ACM. The MSC sends an Alerting message to the UE. The Media Server sends an ANM (Answer Message) to the MSC. The MSC then sends a Connect message to the UE. The MSC sends a REL (Release) message to the Media Server, which responds with a RLC (Release Complete) message. The Media Server then sends a Stop Media message to the MSC. + +Sequence diagram showing message flow in a R99 network between an MSC and a Media Server. + +**Figure A.2: Message flow in a R99 network** + +1. The MSC receives the initial SETUP message from the UE. It recognises that this is a mobile terminating call and interrogates the HLR. The MSC receives the roaming number and an indication that the B-party has subscribed to the PRBT service. +2. The MSC sends an IAM message to the VMSC B. It applies the usual handling for Iu mode and inserts a transcoder, as it will use G.711 encoded media towards the VMSC of the B-party, but use AMR on the Iu interface towards the UE. + +3. The MSC sends a RAB assignment request towards the RNC. +4. At the Iu interface the Iu bearer is established and the user plane is initialised. +5. The MSC receives the RAB assignment response. +6. The MSC sends a Continuity message indicating a successful continuity check. +7. The MSC receives the acknowledgement for the IAM. +8. The MSC sends an IAM towards the media server, where the ringing tone is stored. +9. The MSC receives the acknowledgement from the media server. +10. The MSC informs the A-party that the B-party is alerted and in-band information is available. + +The media server inserts the ringing tone and the MSC forwards it towards the A-party. The A-party listens to the nice ringing tone selected by the B-party. At some point in time the B-party accepts the call and the message sequence continues. + +11. The MSC receives the answer message from the VMSC B. +12. The MSC sends a CONNECT message towards UE A. +13. The MSC releases the connection with the media server. +14. The media server confirms the release message and stops sending media. + +### A.2.4 Message flow with BICC and TrFO + +In this clause it is assumed that the network has been migrated to support packet transport and BICC with TrFO according to Rel-4 specifications with an integrated MSC. In particular, call and bearer control are now separated. However it is assumed that the media server is still the same, and is still connected via ISUP and using TDM transport with G.711. The message flow might now look as shown in figure A.3. Here and in the following forward bearer establishment is considered. + +![Sequence diagram showing message flow between MSC, HLR, and Media Server for BICC and TrFO.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) + +``` +sequenceDiagram + participant External + participant MSC + participant HLR + participant MediaServer as Media Server + + Note left of MSC: 1 Setup + External->>MSC: 1 Setup + MSC->>HLR: HLR Interrogation + HLR->>MediaServer: 2 IAM + Note right of MediaServer: Bearer and Codec Information + MediaServer-->>HLR: Bearer and Codec Information + Note right of HLR: Bearer Establishment + HLR->>External: 3 RAB Ass Req + Note left of HLR: 4 Bearer Establishment and User Plane Initialisation + Note right of HLR: User Plane Initialisation + HLR->>External: 5 RAB Ass Resp + MSC->>MediaServer: 6 Continuity + MediaServer-->>MSC: 7 ACM + MSC->>MediaServer: 8 IAM + Note left of MSC: Insert Transcoder + MediaServer-->>MSC: 9 ACM + Note left of MSC: 10 Alerting + External-->>MSC: 10 Alerting + MediaServer->>External: Send Media towards A-party + MediaServer-->>MSC: 11 ANM + Note left of MSC: 12 Connect + External-->>MSC: 12 Connect + MSC->>MediaServer: 13 REL + MediaServer-->>MSC: 14 RLC + Note left of MSC: Remove Transcoder + Note right of MediaServer: Stop Media +``` + +The sequence diagram illustrates the message flow for BICC and TrFO in a Rel-4 network. It involves three main entities: an external entity (left), the MSC (top center), and the Media Server (top right). The flow starts with a '1 Setup' message from the external entity to the MSC. The MSC sends an 'HLR Interrogation' to the HLR. The HLR sends a '2 IAM' message to the Media Server. The Media Server responds with 'Bearer and Codec Information' to the HLR. The HLR then initiates 'Bearer Establishment' and 'User Plane Initialisation'. The HLR sends a '3 RAB Ass Req' to the external entity, which responds with '4 Bearer Establishment and User Plane Initialisation'. The HLR sends a '5 RAB Ass Resp' to the external entity. The MSC sends a '6 Continuity' message to the Media Server, which responds with '7 ACM'. The MSC then sends an '8 IAM' message to the Media Server. A 'Transcoder' is inserted at the MSC. The Media Server sends a '9 ACM' message to the MSC. The MSC sends an '10 Alerting' message to the external entity. The Media Server sends 'Send Media towards A-party' to the external entity. The Media Server sends an '11 ANM' message to the MSC. The MSC sends an '12 Connect' message to the external entity. The MSC sends a '13 REL' message to the Media Server, which responds with '14 RLC'. Finally, the 'Transcoder' is removed at the MSC, and the Media Server sends a 'Stop Media' message. + +Sequence diagram showing message flow between MSC, HLR, and Media Server for BICC and TrFO. + +Figure A.3: Message flow with BICC and TrFO in a Rel-4 network + +Compared to the flow for a release 99 architecture in figure A.2, there are the following changes: + +- The IAM message 2 contains codec information. +- As AMR is expected at both Iu and Nb interfaces, at this point there is no need to insert a transcoder. +- The IAM message 2 triggers an additional bearer and codec information message, which contains the necessary information for forward bearer establishment and also codec information in response to the codec information in the IAM. +- Nb bearer establishment takes place. +- The Iu/Nb user plane can be established "through the MSC". +- Once the IAM message 8 is sent to the media server, a transcoder is inserted. Again, this is part of usual call handling: insertion of the transcoder is triggered because the MSC is configured in such a way that it knows that the link to the media server is a TDM link with G.711 encoding (as for other links, e.g. towards the PSTN). +- The transcoder can be removed once the connection to the media server is released. Codec modification is not necessary. + +We conclude that the only added "service specific" actions are the insertion of the transcoder and its removal. Both are triggered by the link information configured in the MSC. Service and bearer separation is possible without added complexity for this example service. + +### A.2.5 Message flow with split architecture without TrFO + +This clause describes an alternative intermediary scenario. It is assumed that the network has been migrated to support packet transport and BICC with the split in call control and bearer according to Rel-4 specifications, but yet without support of TrFO. Thus the MSC is split to MSCS and MGW. However it is assumed that the media server is still the same integrated box, which is connected via ISUP and using TDM transport with G.711. The message flow might now look as shown in figure A.4. + +![Sequence diagram showing message flow with split architecture without TrFO. Lifelines: MSC-S, MGW, Media Server, HLR Interrogation. The diagram illustrates the interaction between these components for call setup, bearer establishment, and call termination.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +``` +sequenceDiagram + participant External + participant MSC-S + participant HLR Interrogation + participant MGW + participant Media Server + + Note left of MSC-S: 1 SETUP + MSC-S->>HLR Interrogation: + HLR Interrogation-->>MSC-S: + MSC-S->>Media Server: 2 IAM + Media Server-->>MSC-S: Bearer Information + MSC-S->>MGW: ADDreq + Note right of MGW: Insert Transcoder + MGW-->>MSC-S: ADDreply + Note right of MGW: Bearer Establishment and User Plane Initialisation + MSC-S->>MGW: ADDreq + MGW-->>MSC-S: ADDreply + MSC-S->>External: 3 RAB Ass Req + Note left of MSC-S: 4 Bearer Establishment and User Plane Initialisation + MSC-S->>MGW: Notify + MGW-->>MSC-S: Notify Ack + MSC-S->>External: 5 RAB Ass Resp + MSC-S->>Media Server: 6 Continuity + Media Server-->>MSC-S: 7 ACM + MSC-S->>MGW: ADDreq + MGW-->>MSC-S: ADDreply + MSC-S->>Media Server: 8 IAM + Media Server-->>MSC-S: 9 ACM + MSC-S->>MGW: MODReq + MGW-->>MSC-S: MODreply + MSC-S->>External: 10 Alerting + Note right of Media Server: Send Media towards A-party + Media Server-->>MSC-S: 11 ANM + MSC-S->>External: 12 Connect + MSC-S->>Media Server: 13 REL + Media Server-->>MSC-S: 14 RLC + MSC-S->>MGW: SUBreq + MGW-->>MSC-S: SUBreply + Note right of Media Server: Stop Media +``` + +Sequence diagram showing message flow with split architecture without TrFO. Lifelines: MSC-S, MGW, Media Server, HLR Interrogation. The diagram illustrates the interaction between these components for call setup, bearer establishment, and call termination. + +Figure A.4: Message flow with split architecture without TrFO + +Compared to the flow for a release 99 architecture in figure A.2, there are the following changes: + +- The functionality of the MSC is now distributed to MSC-Server and MGW. In particular, the transcoder is now located in the MGW. +- H.248 based interactions take place at the Mc interface between MSC-Server and MGW, some of which contain the necessary codec information. +- Nb bearer establishment takes place. +- The Nb user plane is established. As different codecs are used at Iu and Nb, the user planes are established independently. + +We conclude that service and bearer separation is possible without added complexity for this example service. + +### A.2.6 Message flow with split architecture and TrFO + +This clause describes the scenario where network supports all possibilities of the Release 4 architecture, i.e. it is assumed that the network supports packet transport and BICC with the split in call control and bearer according to Rel-4 specifications as well as TrFO/OoBTC. As in the previous clause the MSC is split to MSCs and MGW. However it is assumed that the media server is still the same integrated box, which is connected via ISUP and using TDM transport with G.711. The message flow might now look as shown in figure A.5. + +![Sequence diagram showing message flow between MSC, MGW, and Media Server for split architecture and TrFO.](a24e89a6fe9bb70c83f8bf5202baba95_img.jpg) + +``` +sequenceDiagram + participant External + participant MSC + participant HLR + participant MGW + participant MediaServer as Media Server + + Note left of MSC: 1 SETUP + External->>MSC: 1 SETUP + MSC->>HLR: HLR Interrogation + HLR-->>MSC: Bearer and Codec Information + MSC->>MGW: 2 IAM + MSC->>MGW: ADDreq + MGW-->>MSC: ADDreply + Note right of MGW: Bearer Establishment + MSC->>MGW: ADDreq + MGW-->>MSC: ADDreply + MSC-->>External: 3 RAB Ass Req + Note left of MSC: 4 Bearer Establishment and User Plane Initialisation + MSC->>MGW: Notify + MGW-->>MSC: Notify Ack + Note right of MGW: User Plane Initialisation + MSC-->>External: 5 RAB Ass Resp + MSC->>MGW: 6 Continuity + MGW-->>MSC: 7 ACM + MSC->>MGW: ADDreq + MGW-->>MSC: ADDreply + MSC->>MGW: 8 IAM + MSC->>MGW: MODreq + Note right of MGW: Insert Transcoder + MGW-->>MSC: MODreply + MGW-->>MSC: 9 ACM + Note right of MediaServer: Send Media towards A-party + MSC-->>External: 10 Alerting + MGW-->>MSC: 11 ANM + MSC-->>External: 12 Connect + MGW-->>MSC: 13 REL + MGW-->>MSC: 14 RLC + MSC->>MGW: SUBreq + MGW-->>MSC: SUBreply + Note right of MediaServer: Stop Media + Note right of MGW: Remove Transcoder +``` + +The sequence diagram illustrates the message flow for a call setup and teardown in a split architecture with TrFO. The participants are MSC, MGW, and Media Server. The flow starts with a SETUP message from an external source to the MSC. The MSC then sends an HLR Interrogation to the HLR, which returns Bearer and Codec Information. The MSC sends an IAM message to the MGW, followed by an ADDreq. The MGW responds with an ADDreply. A Bearer Establishment phase occurs between the MGW and Media Server. The MSC sends another ADDreq to the MGW, which responds with an ADDreply. The MSC then sends a RAB Ass Req to the external source. A Bearer Establishment and User Plane Initialisation phase occurs between the MSC and MGW. The MSC sends a Notify message to the MGW, which responds with a Notify Ack. A User Plane Initialisation phase occurs between the MGW and Media Server. The MSC sends a RAB Ass Resp to the external source. The MSC sends a Continuity message to the MGW, which responds with an ACM. The MSC sends an ADDreq to the MGW, which responds with an ADDreply. The MSC sends an IAM message to the MGW. The MSC sends a MODreq to the MGW. An Insert Transcoder phase occurs between the MGW and Media Server. The MGW responds with a MODreply. The MGW sends an ACM message to the MSC. The Media Server sends media towards the A-party. The MSC sends an Alerting message to the external source. The MGW sends an ANM message to the MSC. The MSC sends a Connect message to the external source. The MGW sends a REL message to the MSC. The MGW sends a RLC message to the MSC. The MSC sends a SUBreq to the MGW, which responds with a SUBreply. The Media Server stops media. Finally, a Remove Transcoder phase occurs between the MGW and Media Server. + +Sequence diagram showing message flow between MSC, MGW, and Media Server for split architecture and TrFO. + +Figure A.5 Message flow with split architecture and TrFO + +The flow A.5 can be considered as a combination of the flows A.3 and A.4 in the previous two clauses + +Compared to the message flow A.3, + +- The functionality of the MSC is now distributed to MSC-Server and MGW. In particular, the transcoder is now located in the MGW. +- H.248 based interactions take place at the Mc interface between MSC-Serve and MGW, some of which contain the necessary codec information. + +Compared to the message flow A.4, + +- The IAM message 2 contains codec information. +- As AMR is expected at both Iu and Nb interfaces, at this point there is no need to insert a transcoder between the two. +- As there is codec information in the IAM, codec information is sent together with the bearer information in the response. +- The Iu/Nb user plane can be established "through the MSC". +- Once the IAM message 8 is sent to the media server, the MGW is informed in the ADDreq message that G.711 will be used on this link. Therefore the MGW inserts a transcoder. Again, this is part of usual call handling. +- The transcoder can be removed once the connection to the media server is released. Codec modification is not necessary. + +## --- A.3 Summary and conclusions + +In summary, each time a connection request is sent out, there is a need to consider whether insertion or removal of a transcoder is required. The decision depends on the codecs used on the link and the link which will be connected to it. For this purpose link properties are configured, and the results of a codec negotiation are taken into account. + +For this example service three points in the call flow have been identified, where a transcoder may be added or removed depending on the scenario and configuration: after the initial IAM to the VMSC, after the IAM to the media server and after the release of the connection to the media server. With the split architecture, these points become the establishment and removal of the connections. Now, if the same example service is considered for various scenarios, then the call flows look analogous. In each case the decision for transcoder insertion or removal depends on the scenario. This also holds for scenarios not considered in the previous clauses e.g. for access via A interface instead of Iu (with obvious differences and adjustments), or e.g. for a scenario where the A-party VMSC is different from the B-party GMSC. + +In the same way similar example services would have their dedicated points for transcoder insertion at establishment and release of links and the same logic would apply. + +We conclude that service and bearer separation is possible without added complexity for this example service and similar services. + +# Annex B: Change history + +| Change history | | | | | | | | | | +|----------------|--------|-----------|------|-----|-----|-------------------------------------------|--------|---------------|--| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | Old | New | | +| 2004-06 | SP-24 | SP-040445 | - | - | - | Presented for approval | 1.4.0 | 2.0.0 | | +| 2004-06 | SP-24 | SP-040445 | - | - | - | Raised to v.6.0.0 after approval at SA#24 | 2.0.0 | 6.0.0 | | +| 2004-09 | SP-25 | SP-040529 | 0001 | - | - | Editorials TR 23.977 | 6.0.0 | 6.1.0 | | +| 2007-06 | - | - | - | - | - | Update to Rel-7 version (MCC) | 6.1.0 | 7.0.0 | | +| 2008-06 | SP-42 | - | - | - | - | Update to Rel-8 version (MCC) | 7.0.0 | 8.0.0 | | +| 2009-12 | SP-46 | - | - | - | - | Update to Rel-9 version (MCC) | 8.0.0 | 9.0.0 | | +| 2011-03 | SP-51 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | | +| 2012-09 | - | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | <b>11.0.0</b> | | +| 2014-09 | SP-65 | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | <b>12.0.0</b> | | +| 2015-12 | - | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | <b>13.0.0</b> | | +| 2017-03 | - | - | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | <b>14.0.0</b> | | +| 2018-06 | SP-80 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | <b>15.0.0</b> | | +| 2020-07 | SP-88E | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | <b>16.0.0</b> | | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23979/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/23_series/23979/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77da3494413c6d9045e1bc42bc1bce1b2348d5b8 --- /dev/null +++ b/marked/Rel-16/23_series/23979/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:69a04f4a82698b1463397c02e7584af3e8801952b7aca820f139e6fb79833267 +size 193006 diff --git a/marked/Rel-16/23_series/23979/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-16/23_series/23979/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cdc7304ced30e21411e7671616be8d202fd59c01 --- /dev/null +++ b/marked/Rel-16/23_series/23979/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9db248d7420d94010469fa79929670b2ea097a46fea425560e4e64367aef6da7 +size 36117 diff --git a/marked/Rel-16/23_series/23979/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23979/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d00a3923bd26eb3a896a0bf7f1dba8fe720f30b --- /dev/null +++ b/marked/Rel-16/23_series/23979/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:01062c3bddf007df5e99d795fd18042cf49871cdc2c7945f3d06059f30bee0f6 +size 185597 diff --git a/marked/Rel-16/23_series/23979/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23979/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02513fcb643cd8028d46a713d6ed36bb0d9cfd8d --- /dev/null +++ b/marked/Rel-16/23_series/23979/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3bf32ce34b3ee883979761d1f104f67b8914acf351d3a8134129d2e0e70b2d6f +size 157314 diff --git a/marked/Rel-16/23_series/23979/7d2d1d3870cd224c4430d19334557716_img.jpg b/marked/Rel-16/23_series/23979/7d2d1d3870cd224c4430d19334557716_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..db44c835ccdd59be987eb7c0ab72f2edf1017956 --- /dev/null +++ b/marked/Rel-16/23_series/23979/7d2d1d3870cd224c4430d19334557716_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09da4f6b61fca5d1aef1330a10704ca49b421d6d2a46beb55130f78a5f3743f8 +size 192248 diff --git a/marked/Rel-16/23_series/23979/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23979/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c54f50f0c8b238fb0d36f841d40ee14e8179258 --- /dev/null +++ b/marked/Rel-16/23_series/23979/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aac0c6d586ac3d72bfbb3cd4ff13a2bed4bf711b970629444e40368e7b27aca4 +size 170157 diff --git a/marked/Rel-16/23_series/23979/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23979/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b83ae07050408d4b629e3fcb0bd3295ff3966c5b --- /dev/null +++ b/marked/Rel-16/23_series/23979/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7162e193bd3f1d9b525831cd860a448e7028f8d87eda533d1232b2a7c8bde39 +size 167256 diff --git a/marked/Rel-16/23_series/23979/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/marked/Rel-16/23_series/23979/933ecd14c858bf3fc919222d8e357bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..731221a21649b3a87e7b9513cb5a169d39317564 --- /dev/null +++ b/marked/Rel-16/23_series/23979/933ecd14c858bf3fc919222d8e357bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39448ceb0e97e85ce86de7a24f657b7fd0a814b46a205751cac3e92e471f0f76 +size 206162 diff --git a/marked/Rel-16/23_series/23979/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Rel-16/23_series/23979/c2fc2621e8206d24427b56bcb2398fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63e681d8170e9cf60f1d73f01a7fdf9f0799528b --- /dev/null +++ b/marked/Rel-16/23_series/23979/c2fc2621e8206d24427b56bcb2398fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49e353e9ac7147fec09030c7433d8702c0fe71b7b4ef0dcf484c008f1d1b908d +size 20049 diff --git a/marked/Rel-16/23_series/23979/raw.md b/marked/Rel-16/23_series/23979/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..7310d516212828e48d88de7f45e75b1bada0f4e5 --- /dev/null +++ b/marked/Rel-16/23_series/23979/raw.md @@ -0,0 +1,1207 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------------------|-----------| +| Foreword ..... | 5 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 Architectural Requirements ..... | 8 | +| 4.1 General Requirements ..... | 8 | +| 4.2 PoC specific requirements relevant to 3GPP ..... | 8 | +| 5 Architectural Concept ..... | 9 | +| 5.1 General overview ..... | 9 | +| 5.2 Architecture assumptions ..... | 10 | +| 5.2.1 Charging architecture aspects..... | 10 | +| 5.3 Signalling plane impacts ..... | 11 | +| 5.3.1 General aspects for PoC signalling..... | 11 | +| 5.3.2 On-demand Session..... | 11 | +| 5.3.2.1 On-demand session general ..... | 11 | +| 5.3.2.2 On-demand session with automatic answer..... | 11 | +| 5.3.2.3 On demand session with manual answer ..... | 14 | +| 5.3.3 Pre-established Session ..... | 17 | +| 5.3.3.1 Pre-established session general..... | 17 | +| 5.3.3.2 Pre-established session with automatic answer ..... | 17 | +| 5.3.3.3 Pre-established session with manual answer ..... | 19 | +| 5.4 User plane impacts ..... | 22 | +| 5.4.1 General ..... | 22 | +| 5.4.2 GPRS interactions in relation to PoC ..... | 22 | +| 5.4.2.1 General..... | 22 | +| 5.4.2.2 QoS traffic class considerations..... | 22 | +| 5.4.3 PoC and SBLP/Go functions ..... | 23 | +| 5.5 Notification of Parallel Services ..... | 23 | +| 5.5.1 Notification of incoming CS service during a PoC session ..... | 23 | +| 5.5.2 Notification of PoC Session during an ongoing CS service..... | 23 | +| 5.6 PoC Charging Correlation..... | 23 | +| 6 Conclusions..... | 24 | +| <b>Annex A: Recommended QoS settings and configuration parameters for PoC.....</b> | <b>25</b> | +| A.1 Introduction..... | 25 | +| A.2 QoS attribute settings..... | 25 | +| A.2.1 QoS attribute settings for general purpose PDP context..... | 25 | +| A.2.2 QoS attribute settings when separate PDP contexts are used for signalling and media..... | 26 | + +| | | | +|-----------------|----------------------------------------------------------|-----------| +| A.3 | Radio Network Configuration..... | 28 | +| <b>Annex B:</b> | <b>Delay analysis of PoC session establishment .....</b> | <b>29</b> | +| B.1 | Introduction..... | 29 | +| B.2 | On demand session with manual answer ..... | 30 | +| B.3 | On demand session with automatic answer ..... | 32 | +| B.4 | On pre-established session..... | 33 | +| <b>Annex C:</b> | <b>Required SigComp performance.....</b> | <b>36</b> | +| C.1 | Introduction..... | 36 | +| C.2 | Assumptions..... | 36 | +| C.3 | Estimation of SIP compression ratios ..... | 36 | +| C.4 | SigComp requirements..... | 37 | +| Annex D: | Change history..... | 38 | + +# --- Foreword + +This Technical Report has been produced by the 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. + +# --- Introduction + +Advanced interactive conferencing applications like Push to talk over Cellular (PoC) service enablers are being developed in OMA. It is expected that some enhancements of the 3GPP specifications will be needed in order to use IMS & its capabilities as a base for the PoC services. + +# --- 1 Scope + +The present document studies the architectural requirements in order to enable services like PoC over 3GPP systems. The report looks into aspects of using 3GPP PS domain and radio access technologies (GERAN, UTRAN) for bearer services and IMS for reachability and connectivity for applications like PoC. + +# --- 2 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] Void. +- [2] 3GPP TS 21.905: "Vocabulary for 3GPP Specifications". +- [3] 3GPP TS 23.002: "Network architecture". +- [4] 3GPP TS 23.228: "IP Multimedia (IM) Subsystem; Stage 2." +- [5] 3GPP TS 23.141: "Presence Service; Stage 2". +- [6] OMA-AD-PoC-V1.0: OMA PoC Specification, Architecture Document. +- [7] OMA-RD-PoC-V1\_0: OMA PoC Specification, Requirements Document. +- [8] Void. +- [9] 3GPP TS 23.207: "End-to-end Quality of Service (QoS) concept and architecture". +- [10] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture". +- [11] 3GPP TS 26.071: "AMR speech Codec; General description". +- [12] IETF RFC 3267: (June 2002): "Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs". +- [13] 3GPP TS 23.221: "Architectural requirements". +- [14] IETF RFC 3320: (January 2003): "Signaling Compression (SigComp)". +- [15] 3GPP TS 24.228: "Signalling flows for the IP multimedia call control based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". +- [16] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". +- [17] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles". +- [18] 3GPP TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging". +- [19] 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging applications". + +- [20] IETF RFC 2507: "IP Header Compression". +- [21] IETF RFC 3095: "RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TS 21.905 [2] and the following apply. + +**PoC session:** This is an established connection between PoC users where the users can communicate using voice one at a time. + +**Right to Speak:** In the PoC session establishment, the originating subscriber receives within a pre-determined time, an indication before he can speak, this is known as "Right to Speak (RtS)". + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|--------|--------------------------------| +| AMR | Adaptive Multi-Rate | +| AS | Application Server | +| BER | Bit Error Rate | +| CCF | Charging Collection Function | +| CN | Core Network | +| CS | Circuit Switched | +| CSCF | Call Session Control Function | +| DL | DownLink | +| DTM | Dual Transfer Mode | +| ECF | Event Charging Function | +| FBC | Flow Based Charging | +| GERAN | GSM EDGE Radio Access Network | +| GGSN | Gateway GPRS Support Node | +| GPRS | General Packet Radio Service | +| I-CSCF | Interrogating-CSCF | +| IE | Information Element | +| IM | IP Multimedia | +| IMS | IP Multimedia Subsystem | +| IP | Internet Protocol | +| ISC | IP multimedia Service Control | +| NAS | Non-Access Stratum | +| OCS | Online Charging System | +| OMA | Open Mobile Alliance | +| P-CSCF | Proxy-CSCF | +| PCO | Protocol Configuration Options | +| PDP | Packet Data Protocol | +| PoC | Push to talk over Cellular | +| PS | Packet Switched | +| PSI | Public Service Identity | +| QoS | Quality of Service | +| RAB | Radio Access Bearer | +| RB | Radio Bearer | +| RD | Requirements Document | +| RL | Radio Link | +| RLC | Radio Link Control | +| RRC | Radio Resource Control | +| RTP | Real-Time Transport Protocol | +| RtS | 'right-to-speak' indication | +| S-CSCF | Serving-CSCF | +| SBLP | Service Based Local Policy | + +| | | +|-------|--------------------------------------------| +| SDP | Session Description Protocol | +| SDU | Session Data Unit | +| SGSN | Serving GPRS Support Node | +| SIP | Session Initiation Protocol | +| SMS | State Memory Size | +| TBF | Temporary Block Flow | +| TCP | Transport Control Protocol | +| UDP | User Datagram Protocol | +| UE | User Equipment | +| UMTS | Universal Mobile Telecommunications System | +| UTRAN | UMTS Terrestrial Radio Access Network | +| XDMS | XML Document Management Server | + +# --- 4 Architectural Requirements + +## 4.1 General Requirements + +The 3GPP system shall provide the capabilities to support the PoC service architecture as specified in OMA. + +It is assumed that the PoC architecture makes use of the following IMS capabilities in the 3GPP system, which are described in TS 23.228 [4] and TS 23.141 [5]: + +- Registration; +- IMS routing capabilities, including discovery and address resolution; +- IMS security including authentication and authorization; +- IMS charging; +- SIP compression; +- IMS group management; +- Public service identities; +- Presence Service. + +Commonality and differences with IMS conferencing require further study. + +## 4.2 PoC specific requirements relevant to 3GPP + +In order for 3GPP system to support services like PoC, certain PoC requirements will require additional analysis within 3GPP in order to determine that all necessary architectural support is in place via capabilities provided by the GERAN/UTRAN, GPRS and IMS. + +This clause captures the possible relevant requirements for the purposes of additional evaluation to ensure proper support is in place within 3GPP infrastructure: + +- The PoC service entity may provide the originating user with an early indication to start to speak even before invited users accept the call. +- If the above condition is applied then the initiating PoC subscriber shall receive an indication if no participants receive the talk burst. +- The originating subscriber receives 'right-to-speak' (RtS) indication after certain time depending on the answer mode setting of the target PoC subscriber. +- Depending on the setting by the PoC subscriber, the right-to-speak indication can be given to the originating PoC subscriber before the target PoC subscriber is reached or at least one of the target PoC subscribers has to accept the PoC session before the 'right-to-speak' indication is given to the originating PoC subscriber. + +- During the PoC session, the PoC service entity provides 'right-to-speak' indication to a PoC subscriber requesting to speak. +- In case of a chat group session, the communication between chat group participants shall be possible at the time the PoC chat group session is established, that is at least one participant has joined the chat session. +- The timing requirements for capabilities such as RtS shall be taken into account within 3GPP as specified in OMA PoC RD [7]. +- Charging architecture requirements shall be taken into account as specified in OMA PoC AD [6]. +- The user equipment, depending on its capabilities, shall support notification of incoming CS call during an ongoing PoC session as well as a notification of an incoming PoC session set up during an ongoing CS call. + +# 5 Architectural Concept + +## 5.1 General overview + +PoC service is introduced as an application within the frame of the IP Multimedia Subsystem (IMS). Figure 5.1 below illustrates how the PoC service elements fit into the IMS architecture. + +![Figure 5-1: PoC service elements in the IMS architecture. The diagram shows a User Equipment (UE) connected to an IMS core and a group of application servers. The UE is connected to the IMS core via the Gm interface. The IMS core contains a P-CSCF and an S-CSCF connected by the Mw interface. The S-CSCF is connected to a group of application servers (XDMS, PoC Server, and Presence Server) via the ISC interface. The UE is also connected to the XDMS via the Ut interface. The application servers are enclosed in a dashed box.](0b87abe67b21a93777287649c33e755d_img.jpg) + +``` + +graph TD + UE[UE] -- Gm --> P-CSCF[P-CSCF] + P-CSCF -- Mw --> S-CSCF[S-CSCF] + S-CSCF -- ISC --> PoC_Server[PoC Server] + S-CSCF -- ISC --> XDMS[XDMS] + S-CSCF -- ISC --> Presence_Server[Presence Server] + UE -- Ut --> XDMS + subgraph IMS_core [IMS core] + P-CSCF + S-CSCF + end + subgraph App_Servers [Application Servers] + XDMS + PoC_Server + Presence_Server + end + +``` + +Figure 5-1: PoC service elements in the IMS architecture. The diagram shows a User Equipment (UE) connected to an IMS core and a group of application servers. The UE is connected to the IMS core via the Gm interface. The IMS core contains a P-CSCF and an S-CSCF connected by the Mw interface. The S-CSCF is connected to a group of application servers (XDMS, PoC Server, and Presence Server) via the ISC interface. The UE is also connected to the XDMS via the Ut interface. The application servers are enclosed in a dashed box. + +**Figure 5-1: PoC service elements in the IMS architecture** + +**NOTE:** The I-CSCF is not shown in figure 5-1 for the sake of simplicity. Application servers (XDMS, PoC Server, Presence Server), and interfaces between these application servers shown within the dotted box in figure 5-1 are defined by OMA. + +The OMA PoC architecture specification [6] leverages IMS as the underlying SIP-based IP-core network. To understand the details of how IMS capabilities relate to the overall PoC architecture, there is a need to map the reference points defined in the OMA PoC specification [6], and the reference points defined in TS 23.002 [3] and TS 23.228 [4]. + +The PoC server implementing the application level network functionality for the PoC service is essentially seen as an Application Server from the IMS perspective. Consequently, communications between the IMS core and the PoC server utilize the ISC interface defined in TS 23.228 [4]. + +As defined by OMA PoC AD [6], the XML Document Management Server (XDMS) is used by the PoC users to manage groups and lists (e.g. contact and access lists) that are needed for the PoC service. In the IMS architecture, the Ut interface provides these functions, hence communications between the XDMS and the UE utilize the Ut interface. + +As defined by OMA PoC AD [6], a Presence Server may provide availability information about PoC users to other PoC users. The 3GPP Presence architecture and the Presence Server are defined in TS 23.141 [5]. + +## 5.2 Architecture assumptions + +### 5.2.1 Charging architecture aspects + +TS 32.240 [17] specifies the overall charging architecture for the 3GPP system, including the IMS charging architecture. TS 32.260 [18] and TS 32.299 [19] specify the IMS charging details, including the S-CSCF's interfaces towards the charging nodes used for session charging. + +Based on the IMS charging architecture described in these TSs, and the mapping of IMS and OMA PoC architectures described in clause 5.1, the architecture described in figure 5-2 below shows the charging interfaces around the PoC server: + +![Figure 5-2: Architecture for PoC charging. The diagram shows a PoC Server connected to an Online Charging System (OCS) via the Ro interface, to a Charging Collection Function (CCF) via the Rf interface, and to a Serving CSCF via the ISC interface.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +``` +graph TD; OCS[Online Charging System] ---|Ro| PS[PoC Server]; PS ---|Rf| CCF[Charging Collection Function]; PS ---|ISC| SC[Serving CSCF]; +``` + +Figure 5-2: Architecture for PoC charging. The diagram shows a PoC Server connected to an Online Charging System (OCS) via the Ro interface, to a Charging Collection Function (CCF) via the Rf interface, and to a Serving CSCF via the ISC interface. + +**Figure 5-2: Architecture for PoC charging** + +The Charging Collection Function (CCF) is used for offline charging. It shall be possible for the PoC server to send offline accounting information about PoC-service events to the CCF using the mechanisms described for the Rf interface described in TS 32.260 [18]. Possible additional accounting information to cover PoC charging requirements shall be fulfilled by extending the Rf interface, if needed. + +The address of the CCF to be used by the PoC server for the PoC session is distributed to the PoC server in SIP signalling, as described in TS 24.229 [16]. + +The Online Charging System is used for online charging PoC service-related events. It shall be possible for the PoC server to perform credit control interactions as per the mechanisms defined for the Ro interface. The address of the OCS (same as the address of the ECF) to be used by the PoC server for the PoC session is distributed to the PoC server in SIP signalling. + +## 5.3 Signalling plane impacts + +### 5.3.1 General aspects for PoC signalling + +As described in OMA-AD\_PoC [6] architecture document, there are two mechanisms for session establishment signalling supported. In both scenarios, the session is first established between the PoC user (originating or terminating) and the PoC server serving the user and then the other party is invited to the session. User preferences on how the handled PoC sessions may require special user level interactions are described in the OMA\_RD PoC [7] and OMA\_AD\_PoC [6], but the general principle of the session flows is not affected by such interactions. + +The mechanisms for session set-up as defined by OMA are described in the following clauses in more detail, i.e. those would require changes if changes are performed in the OMA specifications. These procedures have the following functional description of behaviour: + +#### 1. On-Demand Session: + +The On Demand session provides a mechanism to negotiate media parameters such as IP address, ports and codecs, which are used for sending the media and floor control packets between the PoC Client and the home PoC Server when the user wants to actually establish a PoC session. This mechanism allows the PoC Client to invite, via PoC server(s), other PoC clients or receive PoC sessions by using the full session establishment procedure each time the user wants to establish/receive/join a PoC session. Media parameters may be negotiated again in this mechanism. + +#### 2. Pre-established Session: + +The pre-established session provides a mechanism to negotiate media parameters such as IP address, ports and codecs, which are used for sending the media and floor control packets between the PoC Client and the home PoC Server before establishing the PoC session. This mechanism allows the PoC Client to invite other PoC clients or receive PoC sessions without negotiating again the media parameters. After the pre-established session has been set up (once the PoC user has registered), the PoC Client is able to activate media bearer whenever needed: + +- immediately after the general PoC session pre-establishment procedure or; +- when the actual SIP signalling for the PoC media session establishment is initiated. + +### 5.3.2 On-demand Session + +#### 5.3.2.1 On-demand session general + +For an on-demand PoC session set-up all media parameters are negotiated at the same time the PoC session is set-up. Two types of on-demand session set-up procedures are described below. + +#### 5.3.2.2 On-demand session with automatic answer + +A simplified PoC session flow for on-demand session with automatic answer is shown below when using GPRS bearer. The flow shows a general case and relation of PDP context with PoC/IMS session and does not show any special order or requirement of whether separate PDP context is required for the media or not. + +![Sequence diagram for On-demand signalling with automatic answering. Lifelines: PoC user (UE-A), PS Domain (A), IMS Core (A), PoC AS (A) - participating & controlling, PoC AS (B) - participating, IMS Core (B), PS Domain (B), PoC user (UE-B). The diagram shows the interaction between two users (UE-A and UE-B) to establish a PoC session. UE-A initiates the session after IMS registration. The PoC AS (A) evaluates filter criteria and INVITEs PoC AS (B). PoC AS (B) also evaluates filter criteria and performs automatic answering (AUTO-A). The diagram includes steps for PS attach, PDP context establishment, IMS registration, INVITE/ACK/200 OK messages, QoS authorization (SBLP), and media transfer. Dashed boxes indicate optional or conditional steps like 'Talk burst confirm', 'QoS authorization (SBLP)', 'Paging', and 'Establish appropriate PDP context for media'. A large box at the bottom represents the 'Talk burst control and transfer of Media' phase.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +sequenceDiagram + participant UE-A as PoC user (UE-A) + participant PS-A as PS Domain (A) + participant IMS-A as IMS Core (A) + participant AS-A as PoC AS (A) - participating & controlling + participant AS-B as PoC AS (B) - participating + participant IMS-B as IMS Core (B) + participant PS-B as PS Domain (B) + participant UE-B as PoC user (UE-B) + + Note left of UE-A: 1.Power On + UE-A->>PS-A: 2. PS Attach + PS-A->>UE-A: 3. Establish PDP context + UE-A->>IMS-A: 4. Perform IMS Registration + Note left of UE-A: 5. Initiate PoC Session + UE-A->>IMS-A: 6. INVITE + Note right of IMS-A: 7. Evaluation of Initial Filter Criteria + IMS-A->>AS-A: 8. INVITE + AS-A->>IMS-A: 9. INVITE + IMS-A->>IMS-B: 10. INVITE + Note right of IMS-B: 11. Evaluation of Initial Filter Criteria + IMS-B->>AS-B: 12. INVITE + AS-B->>IMS-B: 13a. AUTO-A + IMS-B->>AS-B: 13b. INVITE + AS-B->>IMS-A: 14a. AUTO-ANSWER + Note right of IMS-A: 14b. QoS authorization (SBLP) + IMS-A->>AS-A: 15a. AUTO-A + AS-A->>IMS-A: 16a. 200 OK + Note right of IMS-A: 18a. QoS authorization (SBLP) + IMS-A->>UE-A: 17a. Talk burst confirm + UE-A->>IMS-A: 19a. 200 OK + IMS-A->>AS-A: 20a. ACK + AS-A->>IMS-A: 23a. ACK + UE-A->>IMS-A: 21a. Media + Note right of IMS-A: 22a. Establish appropriate PDP context for media + Note right of AS-A: 24a. Buffering of media packets + AS-A->>IMS-A: 20b. 200 OK + IMS-A->>AS-A: 21b. 200 OK + AS-A->>IMS-A: 27. ACK + IMS-A->>AS-B: 28. ACK + AS-B->>IMS-B: 26. Receiving talk burst + IMS-B->>AS-B: 29. ACK + AS-B->>IMS-B: 30. ACK + IMS-B->>AS-B: 31. ACK + AS-B->>IMS-B: 32. Media + IMS-B->>UE-B: 33. Media + Note right of UE-B: 17b. Establish appropriate PDP context for media + Note right of PS-B: 15b. INVITE + Note right of PS-B: 16b. 200 OK + Note right of PS-B: 15b. INVITE + Note right of PS-B: Paging + Note right of PS-B: 15b. INVITE + Note right of PS-B: 16b. 200 OK + +``` + +Sequence diagram for On-demand signalling with automatic answering. Lifelines: PoC user (UE-A), PS Domain (A), IMS Core (A), PoC AS (A) - participating & controlling, PoC AS (B) - participating, IMS Core (B), PS Domain (B), PoC user (UE-B). The diagram shows the interaction between two users (UE-A and UE-B) to establish a PoC session. UE-A initiates the session after IMS registration. The PoC AS (A) evaluates filter criteria and INVITEs PoC AS (B). PoC AS (B) also evaluates filter criteria and performs automatic answering (AUTO-A). The diagram includes steps for PS attach, PDP context establishment, IMS registration, INVITE/ACK/200 OK messages, QoS authorization (SBLP), and media transfer. Dashed boxes indicate optional or conditional steps like 'Talk burst confirm', 'QoS authorization (SBLP)', 'Paging', and 'Establish appropriate PDP context for media'. A large box at the bottom represents the 'Talk burst control and transfer of Media' phase. + +**Figure 5.3.1: On-demand signalling with automatic answering** + +The simplified steps for establishing PoC communication based upon on demand signalling with auto answering are: + +1. Each UE is powered on. +2. Each UE performs PS attach in order to register to the PS domain. +3. Each UE ensures that a PDP context suitable for IMS related signalling is established and if necessary an additional general-purpose PDP context with the same APN and IP address as the PDP context for IMS related signalling. + +NOTE: This may occur at different times for each terminal. The use of the PDP context bearer(s) depends on how the terminal, network and overall system are configured to operate. Detailed implications of such scenarios will be further analysed in clause 5.4 and clause 6. + +If allowed by the subscription and operator policy (see clause 5.4.3) the QoS of a pre-established PDP context for PoC talk burst control and media is allowed to have a higher QoS than best effort. + +4. Each UE performs the IMS registration + +5. User A presses the push-to-talk indication/button on the terminal A to indicate that he wishes to communicate with the user at UE B. + +Note that step 5 can occur anytime after step 4 has been performed, there is no timing correlation between these steps once steps 1-4 has been performed. + +6. UE-A creates a SIP session for the PoC communication by sending the INVITE request into the IMS Core (A), in this example with UE-B as a destination address (alternatively the destination address could also be a PSI hosted by a PoC server for a PoC group session). The INVITE request contains the PoC service indication and the SDP media parameters indicate the IP address obtained in step 3 and that UE-A is ready to send and receive media, as in this example the UE-A established a non real time PDP context for talk burst control and media at IMS registration time. + +7-8. The IMS core A identifies that the service indication matches ISC filtering information and routes the INVITE request to the PoC AS (A). + +9-10. PoC AS (A) (after determining that the PoC communication should be completed), together with the IMS Core (A), forwards the INVITE request towards the IMS Core (B). + +11-12. The IMS Core (B) identifies that the service indication matches ISC filtering information and routes the INVITE request to the PoC AS (B). + +13a. PoC AS (B) sends AUTO-ANSWER to PoC AS (A) as user B is accepting the session automatically + +13b. The PoC AS (B) forwards the INVITE request to UE-B via IMS Core (B) + +14a-15a. The IMS Core (B) forwards the AUTO-ANSWER message towards the PoC AS (A) via IMS Core (A) + +16a-17a. Based on the AUTO-ANSWER and that the PoC AS (A) supports buffering of media, the PoC AS (A) sends a 200 OK towards the UE-A and at the same time sends a talk burst confirm to UE-A. The talk burst control message is transferred to UE-A on a PDP contexts established in step 3. + +18a-19a. In case Service Based Local Policy is applied in UE A's network, IMS Core (A) generates an authorization token for the session, inserts and delivers the authorization token to the UE-A in the first available reliable SIP response (in this case the 200 OK). + +20a-22a. After the UE-A received both the 200 OK response and the talk burst confirm message, UE-A may send media data to PoC AS (A) using a PDP context established in step 3. The UE-A acknowledges the 200 OK. UE-A may establish an additional PDP context for media and talk burst control exchange with same IP address and APN as of the PDP contexts of step 3, e.g. a PDP context with traffic class streaming and bandwidth required for the negotiated media parameters. If the UE received an authorization token in step 19a, it inserts it in the PDP context signalling. + +23a. The IMS Core (A) forwards the acknowledgement to PoC AS (A) + +24a. The PoC AS (A) buffers the received media until a positive response from UE-B is received + +25a. UE-A continues sending media. If and when the PDP context established in step 22a is available, UE-A uses it. + +14b-15b. In case Service Based Local Policy is applied in UE B's network, IMS Core (B) generates an authorization token for the session, and inserts and delivers the authorization token in the INVITE request to UE-B. + +Typically UE-B needs to be paged before the INVITE request can be transferred. + +NOTE: The INVITE message is transparent to the PS Domain. + +- 16b-17b After receiving the INVITE request, UE (B) accepts the session by returning 200 OK. The media parameters indicate the IP address obtained in step 3. UE B may establish an additional PDP context for media and talk burst control exchange with same IP address and APN as of the context of step 3, e.g. a PDP context with traffic class streaming and bandwidth required for the negotiated media parameters. If the UE received an authorization token in step 15b, it inserts it in the PDP context signalling. +- 18b-21b. IMS Core (B) forwards the 200 OK to the PoC AS (B), which forwards the 200 OK towards the PoC AS (A) via IMS Core (B) and IMS Core (A). +- 26. PoC AS (A) inform the UE-B via the PoC AS (B) that receiving talk bursts from UE-A are on the way. +- 27-29. The PoC AS (A) acknowledges the session set-up, the acknowledgement traverses to PoC AS (B) via IMS Core (A) and IMS Core (B). +- 30-31. The PoC AS (B) acknowledges the session set-up +- 32. The buffered media is transferred from PoC AS (A) to PoC AS (B). +- 33. PoC AS (B) transfer the media to UE-B. If and when the PDP context established in step 17b is available, it is used for this purpose +- 34. Further media and talk burst control messages are transferred between the involved entities. + +#### 5.3.2.3 On demand session with manual answer + +A simplified PoC session flow for on-demand session with manual answer is shown below when using GPRS bearer. The flow shows a general case and relation of PDP context with PoC/IMS session and does not show any special order or requirement of whether separate PDP context is required for the media or not. + +![Sequence diagram for On-demand signalling with manual answer. Lifelines: PoC user (UE-A), PS Domain (A), IMS Core (A), PoC AS (A) - participating & controlling, PoC AS (B) - participating, IMS Core (B), PS Domain (B), PoC user (UE-B). The diagram shows the signaling flow for establishing a PoC session between two users, including power-on, PS attach, PDP context establishment, IMS registration, INVITE messages, filter criteria evaluation, QoS authorization, paging, and media exchange.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant UE-A as PoC user (UE-A) + participant PS-A as PS Domain (A) + participant IMS-A as IMS Core (A) + participant AS-A as PoC AS (A) - participating & controlling + participant AS-B as PoC AS (B) - participating + participant IMS-B as IMS Core (B) + participant PS-B as PS Domain (B) + participant UE-B as PoC user (UE-B) + + Note left of UE-A: 5 Initiate PoC Session + UE-A->>PS-A: 1. Power On + PS-A->>UE-A: 2. PS Attach + PS-A->>IMS-A: 3. Establish PDP context + UE-A->>IMS-A: 4. Perform IMS Registration + Note left of UE-A: 5 Initiate PoC Session + UE-A->>IMS-A: 6. INVITE + IMS-A->>AS-A: 7. Evaluation of Initial Filter Criteria + AS-A->>IMS-A: 8. INVITE + IMS-A->>AS-A: 9. INVITE + AS-A->>IMS-B: 10. INVITE + IMS-B->>AS-B: 11. Evaluation of Initial Filter Criteria + AS-B->>IMS-B: 12. INVITE + IMS-B->>AS-B: 13. INVITE + Note right of IMS-B: 14. QoS authorization (SBLP) + AS-B->>IMS-B: 15. INVITE + Note right of PS-B: Paging + IMS-B->>PS-B: 15. INVITE + PS-B->>UE-B: 15. INVITE + Note right of UE-B: 16 + UE-B->>PS-B: 16. 200 OK + Note right of PS-B: 17. Establish appropriate PDP context for media + PS-B->>IMS-B: 18. 200 OK + IMS-B->>AS-B: 19. 200 OK + AS-B->>IMS-A: 20. 200 OK + IMS-A->>AS-A: 21. 200 OK + AS-A->>IMS-A: 22. 200 OK + IMS-A->>UE-A: 23. Talk burst confirm + Note right of IMS-A: 24. QoS authorization (SBLP) + UE-A->>PS-A: 25. 200 OK + PS-A->>IMS-A: 26. ACK + IMS-A->>AS-A: 29. ACK + AS-A->>IMS-A: 30. ACK + Note right of UE-A: 28. Establish appropriate PDP context for media + UE-A->>IMS-A: 27. Media + IMS-A->>AS-A: 31. ACK + AS-A->>IMS-B: 35. Receiving talk burst + IMS-B->>AS-B: 32. ACK + AS-B->>IMS-B: 33. ACK + IMS-B->>PS-B: 34. ACK + UE-B->>PS-B: 36. Media + PS-B->>IMS-B: 37. Media + IMS-B->>AS-B: 38. Media + +``` + +Sequence diagram for On-demand signalling with manual answer. Lifelines: PoC user (UE-A), PS Domain (A), IMS Core (A), PoC AS (A) - participating & controlling, PoC AS (B) - participating, IMS Core (B), PS Domain (B), PoC user (UE-B). The diagram shows the signaling flow for establishing a PoC session between two users, including power-on, PS attach, PDP context establishment, IMS registration, INVITE messages, filter criteria evaluation, QoS authorization, paging, and media exchange. + +**Figure 5.3.2: On-demand signalling with manual answer** + +The simplified steps for establishing PoC communication based upon on demand signalling with manual answering are: + +1. Each UE is powered on. +2. Each UE performs PS attach in order to register to the PS domain. +3. Each UE ensures that a PDP context suitable for IMS related signalling is established and if necessary an additional general purpose PDP context with the same APN and IP address as the PDP context for IMS related signalling. + +NOTE: This may occur at different times for each terminal. The use of the PDP context bearer(s) depends on how the terminal, network and overall system are configured to operate. Detailed implications of such scenarios will be further analysed in clause 5.4 and clause 6. + +If allowed by the subscription and operator policy (see clause 5.4.3) the QoS of a pre-established PDP context for PoC talk burst control and media is allowed to have a higher QoS than best effort. + +4. Each UE performs the IMS registration. +5. User A presses the push-to-talk indication/button on the UE A to indicate that he wishes to communicate with the user at UE B. + +Note that step 5 can occur anytime after step 4 has been performed, there is no timing correlation between these steps once steps 1-4 has been performed. + +6. UE-A creates a SIP session for the PoC communication by sending the INVITE request into the IMS Core (A), in this example with UE-B as a destination address (alternatively the destination address could also be a PSI hosted by a PoC server for a PoC group session). The INVITE request contains the PoC service indication and the SDP media parameters indicate the IP address obtained in step 3 and that UE-A is ready to send and receive media, as in this example the UE-A established a non real time PDP context for talk burst control and media at IMS registration time. +- 7-8. The IMS Core (A) identifies that the service indication matches ISC filtering information and routes the INVITE request to the PoC AS (A). +- 9-10. PoC AS (A) (after determining that the PoC communication should be completed), together with the IMS Core (A), forwards the INVITE request towards the IMS Core (B). +- 11-12. The IMS Core (B) identifies that the service indication matches ISC filtering information and routes the INVITE request to the PoC AS (B). +13. The PoC AS (B) forwards the INVITE request to UE-B via IMS Core (B) +- 14-15. In case Service Based Local Policy is applied in UE B's network, IMS Core (B) generates an authorization token for the session, and inserts and delivers the authorization token in the INVITE request to UE-B. + +Typically UE-B needs to be paged before the INVITE request can be transferred. + +NOTE: The INVITE message is transparent to the PS domain. + +- 16-17. After receiving the INVITE request, user (B) accepts the session set-up manually and UE-B accepts the session by returning 200 OK. UE-B should send a 180 ringing response when receiving the INVITE request to avoid the INVITE request to be re-sent (not shown in the figure). The media parameters indicate the IP address obtained in step 3. UE B may establish an additional PDP context for media and talk burst control exchange with same IP address and APN as of the context of step 3, e.g. a PDP context with traffic class streaming and bandwidth required for the negotiated media parameters. If the UE-B received an authorization token in step 15, it inserts it in the PDP context signalling. +- 18-21. IMS Core (B) forwards the 200 OK to the PoC AS (B), which forwards the 200 OK towards the PoC AS (A) via IMS Core (B) and IMS Core (A). +- 22-23. PoC AS (A) sends a 200 OK towards the UE-A and at the same time sends a talk burst confirm to UE-A. +- 24-25. In case Service Based Local Policy is applied in UE A's network, IMS Core (A) generates an authorization token for the session, inserts and delivers the authorization token to the UE-A in the first available reliable SIP response (in this case the 200 OK). +- 26-28. After the UE-A received both the 200 OK response and the talk burst confirm message, UE-A may send media data to PoC AS (A) using a PDP context established in step 3. The UE-A acknowledges the 200 OK. UE-A may establish an additional PDP context for media and talk burst control exchange with same IP address and APN as of the PDP contexts of step 3, e.g. a PDP context with traffic class streaming and bandwidth required for the negotiated media parameters. If the UE received an authorization token in step 25, it inserts it in the PDP context signalling. +29. The IMS Core (A) forwards the acknowledgement to PoC AS (A). + +- 30-32. The PoC AS (A) acknowledges the session set-up, the acknowledgement traverses to PoC AS (B) via IMS Core (A) and IMS Core (B). +- 33-34. The PoC AS (B) acknowledges the session set-up. +- 35. PoC AS (A) inform the UE-B via the PoC AS (B) that receiving talk bursts from UE-A are on the way. +- 36. UE-A continues sending media. If and when the PDP context established in step 28 is available, UE-A uses it. +- 37-38. PoC AS (A) transfer the media to UE-B, via PoC AS (B). If and when the PDP context established in step 17 is available, it is used for this purpose. + +### 5.3.3 Pre-established Session + +#### 5.3.3.1 Pre-established session general + +For a pre-established PoC session, media parameters are negotiated at the setup of the pre-established PoC session and during the PoC session is setup the media parameter negotiation can be skipped. Two types of pre-established session set-up procedures are described below. + +#### 5.3.3.2 Pre-established session with automatic answer + +A simplified PoC session flow for the setup of session having pre-established session with automatic answer is shown below when using GPRS bearer. The flow shows a general case and relation of PDP context with PoC/IMS session and does not show any special order or requirement of whether separate PDP context is required for the media or not. This flow assumes (though it is not required for both sides to use the same mechanism) that both originating and terminating PoC user uses the Pre-established session mechanism. + +![Sequence diagram for Figure 5.3.3: Pre-established session signalling with automatic answering.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +The diagram illustrates the signalling flow for a pre-established PoC session with automatic answering between two users, UE-A and UE-B. The entities involved are PoC user (UE-A), PS Domain (A), IMS Core (A), PoC AS (A) - participating & controlling, PoC AS (B) - participating, IMS Core (B), PS Domain (B), and PoC user (UE-B). + +- Steps 1-3:** Both UE-A and UE-B perform Power On, PS Attach, and Establish PDP context. +- Step 4:** Both terminals perform IMS Registration. +- Step 5:** Set up of Pre-established session. This involves an INVITE (5a) from the UE to the IMS Core, Evaluation of Initial Filter Criteria (5b), INVITE (5c) to the PoC AS, and 200 OK responses (5d, 5e) back to the UE. +- Step 6:** UE-A initiates PoC Session. +- Steps 7-16:** Media establishment and session control signalling including Establish media (7, 8), INVITE (9, 10, 11), AUTO-ANSWER (12, 13, 14), and ACCEPT (15, 16). +- Step 17:** Talk burst confirm is sent to UE-A. +- Step 18:** Receiving talk burst is indicated to UE-B. +- Step 19:** Receiving talk burst is acknowledged by UE-B (after Paging). +- Steps 20-24:** Media flow from UE-A to UE-B via PoC AS (A). +- Steps 21 & 25:** Both UEs establish appropriate PDP contexts for media. + +Sequence diagram for Figure 5.3.3: Pre-established session signalling with automatic answering. + +**Figure 5.3.3: Pre-established session signalling with automatic answering** + +The simplified steps for establishing PoC communication based upon pre-established session signalling are: + +- Each terminal is powered on. +- Each terminal performs PS attach in order to authenticate to the PS domain. +- Each UE ensures that a PDP context suitable for IMS related signalling is established and if necessary an additional general purpose PDP context with the same APN and IP address as the PDP context for IMS related signalling. + +**NOTE:** This may occur at different times for each terminal. The use of the PDP context bearer(s) depends on how the terminal, network and overall system are configured to operate. Detailed implications of such scenarios will be further analysed in clause 5.4 and clause 6. + +If allowed by the subscription and operator policy (see clause 5.4.3) QoS of a pre-established PDP context for PoC talk burst control and media is allowed to have a higher QoS than best effort. + +- Each terminal performs the IMS registration +- Each terminal establishes the pre-established session for PoC communication towards the PoC AS (e.g. by using a dedicated PSI). The INVITE request contains the PoC service indication and the SDP media parameters indicate the IP address obtained in step 3; the IMS Core (A) identifies that this service indication matches ISC filtering information and routes the session establishment request to the PoC AS (A). + +In case Service Based Local Policy is applied in the UE(A)'s IMS network, IMS Core (A) generates an authorization token for the session, inserts and delivers the authorization token to the UE-A upon set-up of the pre-established session (in the 200OK response). + +NOTE: This pre-established session set-up may occur at different times for each terminal. Once the session relationship is established, it remains as long as the user wishes to remain connected to the PoC server. Implications of such long established session and its relationship with other IMS functions will require further study. + +6. User A presses the push-to-talk indication/button on the terminal A to indicate that he wishes to communicate to the user at UE (B). + +7-8. UE-A request the establishment of media transfer and sends, for example, a SIP REFER message to the PoC AS (A) via the IMS Core (A), containing the address of the terminating user. + +9-11. PoC AS (A) sends an INVITE request to PoC AS (B) by means of IMS core (A) and IMS Core (B). + +12-14. PoC AS (B) indicates Auto-Answer to PoC AS (A), via IMS Core (B) and IMS Core (A). + +15-17. The PoC AS (A) acknowledges the media establishment request message and at the same time sends a talk burst confirm to UE-A. The talk burst control message is transferred to UE-A on a PDP contexts established in step 3. + +18-19. PoC AS (A) inform the UE-B via the PoC AS (B) that receiving talk bursts from UE-A are on the way. +Typically UE-B needs to be paged before the Receiving talk burst message can be transferred + +NOTE: The Receiving talk burst message is transparent to the PS Domain. + +20-21. After the UE-A received both the acknowledgement for the media establishment request message and the talk burst confirm message, UE-A may send media data to PoC AS (A). UE-A may establish an additional PDP context for media and talk burst control exchange with same IP address and APN as of the PDP contexts of step 3, e.g. a PDP context with traffic class streaming and bandwidth required for the negotiated media parameters. If the UE received an authorization token in step 5, it inserts it in the PDP context signalling. As soon as the PDP context established in step 18 is available, UE-A uses it. + +22-24. UE-A continues sending media. If and when the PDP context established in step 22 is available, UE-A uses it. UE-A sends the media data to PoC AS (A), which sends media data to UE-B, via PoC AS (B). + +25. Having received the receiving talk burst message, UE-B may establish an additional PDP context for media and talk burst control exchange with same IP address and APN as of the context(s) of step 3, e.g. a PDP context with traffic class streaming and bandwidth required for the negotiated media parameters. If the UE received an authorization token in step 5, it inserts it in the PDP context signalling. + +#### 5.3.3.3 Pre-established session with manual answer + +A simplified PoC session flow for the setup of session having pre-established session with manual answer is shown below when using GPRS bearer. The flow shows a general case and relation of PDP context with PoC/IMS session and does not show any special order or requirement of whether separate PDP context is required for the media or not. This flow assumes (though it is not required for both sides to use the same mechanism) that both originating and terminating PoC user uses the Pre-established session mechanism. + +![Sequence diagram for Pre-established session handling with manual answer. The diagram shows the interaction between PoC user (UE-A), PS Domain (A), IMS Core (A), PoC AS (A), PoC AS (B), IMS Core (B), PS Domain (B), and PoC user (UE-B).](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +``` + +sequenceDiagram + participant UEA as PoC user (UE-A) + participant PSA as PS Domain (A) + participant IMSA as IMS Core (A) + participant ASA as PoC AS (A) - participating & controlling + participant ASB as PoC AS (B) - participating + participant IMSB as IMS Core (B) + participant PSB as PS Domain (B) + participant UEB as PoC user (UE-B) + + Note over UEA, PSA: 1. Power On + Note over UEA, PSA: 2. PS Attach + Note over UEA, PSA: 3. Establish PDP context + Note over UEA, IMSA: 4. Perform IMS Registration + + Note over UEB, PSB: 1. Power On + Note over UEB, PSB: 2. PS Attach + Note over UEB, PSB: 3. Establish PDP context + Note over UEB, IMSB: 4. Perform IMS Registration + + rect rgb(255, 255, 255) + Note over IMSA, ASA: 5. Set up of Pre-established session + ASA->>IMSA: 5a. INVITE + Note right of IMSA: 5b. Evaluation of Initial Filter Criteria + IMSA->>ASA: 5c. INVITE + ASA->>IMSA: 5d. 200 OK + IMSA->>ASA: 5e. 200 OK + end + + rect rgb(255, 255, 255) + Note over IMSB, ASB: 5. Set up of Pre-established session + ASB->>IMSB: 5a. INVITE + Note left of IMSB: 5b. Evaluation of Initial Filter Criteria + IMSB->>ASB: 5c. INVITE + ASB->>IMSB: 5d. 200 OK + IMSB->>ASB: 5e. 200 OK + end + + Note left of UEA: 6. Initiate PoC Session + UEA->>IMSA: 7a. Establish media + IMSA->>ASA: 7b. Establish Media + ASA->>IMSA: 8a. INVITE + IMSA->>ASB: 9. INVITE + ASB->>IMSB: 10. INVITE + IMSB->>ASB: 11a. INVITE + ASB->>PSB: 11b. INVITE + Note right of PSB: Paging + PSB->>UEB: 11c. INVITE + Note right of UEB: 12 + UEB->>PSB: 12. 200 OK + PSB->>IMSB: 13. 200 OK + IMSB->>ASB: 14. 200 OK + ASB->>IMSA: 15. 200 OK + IMSA->>ASA: 16. 200 OK + ASA->>UEA: 17. Talk burst confirm + ASA->>ASB: 18. Receiving talk burst + UEA->>ASA: 19. Media + Note over UEA, PSA: 20. Establish appropriate PDP context for media + UEA->>ASA: 21. Media + ASA->>ASB: 22. Media + ASB->>UEB: 23. Media + Note over PSB, UEB: 24. Establish appropriate PDP context for media + +``` + +Sequence diagram for Pre-established session handling with manual answer. The diagram shows the interaction between PoC user (UE-A), PS Domain (A), IMS Core (A), PoC AS (A), PoC AS (B), IMS Core (B), PS Domain (B), and PoC user (UE-B). + +**Figure 5.3.4: Pre-established session handling with manual answer** + +The simplified steps for establishing PoC communication based upon pre-established session signalling are: + +1. Each terminal is powered on. +2. Each terminal performs PS attach in order to authenticate to the PS domain. +3. Each UE ensures that a PDP context suitable for IMS related signalling is established and if necessary an additional general purpose PDP context with the same APN and IP address as the PDP context for IMS related signalling. + +NOTE: This may occur at different times for each terminal. The use of the PDP context bearer(s) depends on how the terminal, network and overall system are configured to operate. Detailed implications of such scenarios will be further analysed in clause 5.4 and clause 6. + +If allowed by the subscription and operator policy (see clause 5.4.3) the QoS of a pre-established PDP context for PoC talk burst control and media is allowed to have a higher QoS than best effort. + +4. Each terminal performs the IMS registration. + +5. Each terminal establishes the pre-established session for PoC communication towards the PoC AS (e.g. by using a dedicated PSI). The INVITE request contains the PoC service indication and the SDP media parameters indicate the IP address obtained in step 3; the IMS Core (A) identifies that this service indication matches ISC filtering information and routes the session establishment request to the PoC AS (A). + +In case Service Based Local Policy is applied in the UE(A)'s IMS network, IMS Core (A) generates an authorization token for the session, inserts and delivers the authorization token to the UE-A upon set-up of the pre-established session (in the 200OK response). + +NOTE: This pre-established session set-up may occur at different times for each terminal. Once the session relationship is established, it remains as long as the user wishes to remain connected to the PoC server. Implications of such long established session and its relationship with other IMS functions will require further study. + +6. User A presses the push-to-talk indication/button on the terminal A to indicate that he wishes to communicate to the user at UE (B). + +- 7a-7b. UE-A requests the establishment of media transfer and sends, for example, a SIP REFER message to the PoC AS (A) via the IMS Core (A), containing the address of the terminating user. + +- 8a-10. PoC AS (A) sends the INVITE message to PoC AS (B) by means of IMS core (A) and IMS Core (B). + +- 8b. PoC AS (A) sends ACCEPT message to UE-A via IMS core (A). + +- 11a-11c. The PoC AS (B) requests the establishment of media transfer and sends a SIP re-INVITE message to the UE (B) via the IMS Core (B). + +Typically UE-B needs to be paged before the SIP re-INVITE message can be transferred. + +NOTE: The re-INVITE message is transparent to the PS Domain. + +12. After receiving the re-INVITE request, user (B) accepts the session set-up manually and UE-B accepts the session by returning 200 OK. UE-B should send a 180 ringing response when receiving the INVITE request to avoid the re-INVITE request to be re-sent (not shown in the figure). The media parameters indicate the IP address obtained in step 3. + +- 13-16. IMS Core (B) forwards the 200 OK to the PoC AS (B), which forwards the 200 OK towards the PoC AS (A) via IMS Core (B) and IMS Core (A). + +17. The PoC AS (A) sends a talk burst confirm to UE-A. The talk burst control message is transferred to UE-A on a PDP contexts established in step 3. + +18. PoC AS (A) informs the UE-B via the PoC AS (B) that receiving talk bursts from UE-A are on the way. + +- 19-20. After the UE-A received both the acknowledgement for the media establishment request message and the talk burst confirm message, UE-A may send media data to PoC AS (A). UE-A may establish an additional PDP context for media and talk burst control exchange with same IP address and APN as of the PDP contexts of step 3, e.g. a PDP context with traffic class streaming and bandwidth required for the negotiated media parameters. If the UE received an authorization token in step 5, it inserts it in the PDP context signalling. As soon as the PDP context established in step 20 is available, UE-A uses it. + +- 21-23. UE-A continues sending media. If and when the PDP context established in step 20 is available, UE-A uses it. UE-A sends the media data to PoC AS (A), which sends media data to UE-B, via PoC AS (B). + +24. Having received the receiving talk burst message, UE-B may establish an additional PDP context for media and talk burst control exchange with same IP address and APN as of the context(s) of step 3, e.g. a PDP context with traffic class streaming and bandwidth required for the negotiated media parameters. If the UE received an authorization token in step 5, it inserts it in the PDP context signalling. + +## 5.4 User plane impacts + +### 5.4.1 General + +The deployment of PoC services over IMS requires some analysis regarding the general IMS as well as the radio, GPRS and terminals. The available QoS and use of specific QoS, codecs etc. may also require analysis or require some guidelines to be provided by 3GPP towards PoC service deployment. + +This clause provides the background material from which the architecture analysis work can draw the necessary conclusions to be captured in clause 6. + +### 5.4.2 GPRS interactions in relation to PoC + +#### 5.4.2.1 General + +It is assumed that additional PDP contexts (within a single APN) to separate signalling and media traffic within IMS is required only when: + +- the QoS need to be different for signalling and media traffic, +- and/or restricted handling of the signalling traffic is required (due to charging (if FBC is not used), policy, policing etc.), +- and/or restricted handling of media traffic is required (due to charging, Service Based Local Policy, policing etc.), +- and/or other GPRS traffic can not use the same PDP context as IMS/PoC. + +It is assumed that any of the following are valid GPRS/PDP contexts usage option for any IMS service, i.e. the options also apply for PoC. However, it is not only up to the PoC client to choose any of the options below as the valid options depends on possible restrictions, e.g. whether the GGSN apply restrictions on the PDP context used for IMS signalling as specified in TS 23.228 [4]. + +1. A Single PDP context is used for both IMS signalling and media traffic; +2. A separate PDP context for media traffic is required, but IMS signalling may share a general purpose PDP context with other GPRS traffic; +3. A separate PDP context is required for IMS signalling traffic, but the media traffic can share a PDP context with other general purpose PDP Context such as IMS session based messaging as described in TS 23.228 [4]; +4. Separate PDP contexts required for IMS signalling, all media share a single PDP context and other GPRS traffic use separate PDP context; +5. Separate PDP contexts required for IMS signalling, all media such as audio, text etc require separate PDP context and other GPRS traffic use separate PDP context. + +How such combinations interact with PoC session establishment mechanism need further analysis. Depending on the mechanism used (on-demand and pre-established), whether existing PDP context can be reused or not, how floor control messages should be treated (as user plane traffic or signalling traffic or both) and whether SBLP/Go function is in use or not, the sessions flows may need to be further verified. + +#### 5.4.2.2 QoS traffic class considerations + +OMA POC AD [6] recommends that when different PDP contexts are used for IMS signalling and media traffic the OMA PoC Clients should separately utilize the QoS traffic class that is best suitable for signalling (e.g., Interactive traffic class) and the QoS traffic class that is best suitable for the media traffic (e.g. Streaming or Conversational traffic classes). + +NOTE: The definitions of the QoS traffic classes used are described in TS 23.107 [10]. + +According to the OMA POC AD [6], when a single PDP context is used for both IMS Signalling and media traffic the PoC Client should utilize the QoS traffic class that is determined to be the best available considering the overall needs of the PoC Service (e.g., Interactive traffic class). + +Recommended QoS settings and radio network configurations for PoC are presented in Annex A. + +### 5.4.3 PoC and SBLP/Go functions + +The signalling procedures being studied within OMA for PoC communication are optimized for session establishment time. Therefore they do not assume that SIP preconditions are used for PoC. However, if SBLP and the Go interface are deployed, they can be used as illustrated in the flows in clause 5.3 as a use-case of the flows in clause 5.7a of TS 23.228 [4]. + +For more information on SBLP/Go functions, see TS 23.228 [4] and TS 23.207 [9]. + +## 5.5 Notification of Parallel Services + +### 5.5.1 Notification of incoming CS service during a PoC session + +PoC is provided as a service in the PS domain. This implies that the existing mechanisms are used for paging and notification of an incoming CS service during a PoC session. + +This means: + +- For a UE in class A mode of operation and Dual Transfer Mode of operation, the CS paging during PS bearer will be applied as defined for UTRAN or class A/B or DTM GERAN. +- For a UE in class B mode of operation, CS paging during PS bearer will be applied as defined for UTRAN or class A/B or DTM GERAN. If the user accepts the CS service, the PS bearer may be suspended or dropped and as a result any PoC session is put on hold or terminated respectively. +- UE in class C mode of operation does not support multiple services, thus the issue does not exist. + +### 5.5.2 Notification of PoC Session during an ongoing CS service. + +PoC is provided as a service in the PS domain. This implies that notification of an incoming PoC sessions during an ongoing CS Service is possible as follows: + +- For UE in Class A mode of operation and Dual Transfer Mode of operation, it is possible to send the initial PoC notification (e.g. the INVITE) to the UE during an ongoing CS Service. +- For UE in Class B mode of operation does not need to monitor GERAN control channels during CS services. CS services have higher priority than PS services. Thus incoming PoC session requests cannot be delivered to the UE during an ongoing CS call. +- UE in class C mode of operation does not support multiple services, thus the issue does not exist. + +## 5.6 PoC Charging Correlation + +PoC is provided as a service over IM CN. This implies that the existing IMS charging correlation information and mechanisms should be reused. + +See TS 24.229 [16] for further information on charging correlation. + +# --- 6 Conclusions + +The TR describes the architectural requirements to support the OMA POC services in clause 4 and the impacts to the architectural concepts in clause 5. This Clause 5 addresses the impacts to the signalling plane by describing the on-demand and pre-established sessions. Also the impacts to the User Plane are described as well. + +The concept of Service Based Local Policies (SBLP) and the Go interface as described in TS 23.228 [4] and TS 23.207 [9] supports the OMA PoC signalling requirements for session establishment, however it is not mandated that these capabilities are to be used for the OMA PoC session establishment. + +PoC will contain the same GPRS/PDP contexts usage options as for any IMS service, i.e. the options also apply for PoC. However, it is not only up to the PoC client to choose any of the GPRS/PDP contexts usage options as the valid + +options depends on possible restrictions, e.g. whether the GGSN apply restrictions on the PDP context used for IMS signalling as specified in TS 23.228 [4]. + +Annex A describes the recommended QoS Attribute settings and the Radio Network Configurations to support OMA PoC services. + +The main issue in supporting PoC services is the session establishment delays. Annex B contains the analysis of the delay for the PoC session establishments based on 'on demand' signalling and based on 'pre-established session' signalling. + +Annex C describes the analyses of the required SigComp performance and gives requirements to support the PoC service. This analysis concludes that IMS provides sufficient SigComp support for the OMA PoC delay requirements. + +The PoC codecs are specified within 3GPP SA4. + +It is concluded that the current 3GPP IMS specifications supports the requirements to deploy PoC services as defined by OMA. + +# Annex A: Recommended QoS settings and configuration parameters for PoC + +## A.1 Introduction + +The Push-to-Talk over Cellular (PoC) application is to be run over PS Domain bearers. The application is characterized by half-duplex voice communication. + +The Annex makes recommendations on QoS attribute settings and radio network configurations. + +## A.2 QoS attribute settings + +The following clauses describe recommended QoS settings by the UE during PDP context activation and modification procedures for the media flow in PoC with only one general purpose PDP context (clause A.2.1) and when separate PDP contexts are used for the media and signalling (clause A.2.2). + +The bandwidth needed for the media flow in PoC is to a large extent dependent on the negotiated speech codec bit rate together with the transport format. In the following it is assumed that AMR speech coding, TS 26.071 [11], together with the RTP payload format for AMR, RFC 3267 [12], is used in the 'octet-aligned mode', without interleaving and without CRCs. It is furthermore assumed that one RTP packet carries ten (10) AMR frames, corresponding to 10\*20 ms of speech (ptime=200). Note that also other packetization schemes are possible. Table A.2-1 shows the required bandwidth for the RTP flow on 'IP level' (i.e. including RTP/UDP/IP overhead) for the different AMR modes: + +**Table A.2-1: Required bandwidth Uplink/Downlink for the RTP traffic for different AMR modes (ptime=200)** + +| AMR Mode | Required bandwidth when IPv4 is used [bits/s] [Note] | Required bandwidth when IPv6 is used [bits/s] | +|----------|--------------------------------------------------------------------|-----------------------------------------------| +| AMR 4.75 | 6840 | 7640 | +| AMR 5.15 | 7240 | 8040 | +| AMR 5.9 | 8040 | 8840 | +| AMR 6.7 | 8840 | 9640 | +| AMR 7.4 | 9640 | 10440 | +| AMR 7.95 | 10040 | 10840 | +| AMR 10.2 | 12440 | 13240 | +| AMR 12.2 | 14440 | 15240 | +| NOTE: | For the usage of IP version in IMS see TS 23.221 [13], clause 5.1. | | + +### A.2.1 QoS attribute settings for general purpose PDP context + +If one general purpose PDP context is used for both media and signalling, the PDP context should be of traffic class Interactive. + +The following QoS parameter values for such PDP context are recommended to be requested by the UE. + +**Table A.2.1-1: Recommended QoS attribute settings for a single general purpose PDP Context for both the PoC control plane and user plane traffic** + +| Traffic class | Interactive class | Notes | +|-----------------------------|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Maximum bitrate (kbps) | See 'Notes' | The value for this parameter is based on the highest speech codec rate negotiated via SDP in the codec mode-set (see table A.2-1) plus appropriate bandwidth for the SIP Signalling traffic to QoS limit the impact on the media flow. | +| Delivery order | No | In sequence delivery of voice samples is not required nor is it desirable since it creates jitter in the media channel. An RTP jitter buffer in the client should re-order packets if needed. | +| Maximum SDU size (octets) | 1500 | Maximum size of IP packets. No PoC specific setting needed. | +| SDU format information | - | Not applicable for traffic class Interactive. | +| Delivery of erroneous SDUs | No | It is sufficient to signal erroneous IP packets to the UE. | +| Residual BER | $10^{-5}$ | Reflects the desire to have a medium level of protection to achieve an acceptable compromise between packet loss rate and voice transport delay and delay variation. | +| SDU error ratio | $10^{-4}$ | See "Residual BER" parameter. | +| Transfer delay (ms) | - | Is not used for the Interactive traffic class. | +| Guaranteed bit rate (kbps) | - | Is not used for the Interactive traffic class. | +| Traffic handling priority | 1 | Specifies the relative importance for handling of all SDUs belonging to the radio access bearer compared to the SDUs of other bearers. Highest importance is recommended for PoC. | +| Source statistic descriptor | - | Not applicable for traffic class Interactive. | +| Signalling indication | No | The PDP context is not used for signalling only | + +### A.2.2 QoS attribute settings when separate PDP contexts are used for signalling and media + +If separate PDP contexts are used for media and signalling, the PDP context for signalling should be of traffic class Interactive. + +The following QoS parameter values for the PDP context are recommended to be requested by the UE for signalling. + +**Table A.2.2-1: Recommended QoS attribute settings for a PDP Context used for the PoC control plane traffic** + +| Traffic class | Interactive class | Notes | +|-----------------------------|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Maximum bitrate (kbps) | 8 | For an Interactive PDP context solely used for signalling, the maximum bit rate should be 8 kbps | +| Delivery order | No | In sequence delivery of voice samples is not required nor is it desirable since it creates jitter in the media channel. An RTP jitter buffer in the client should re-order packets if needed. | +| Maximum SDU size (octets) | 1500 | Maximum size of IP packets. No PoC specific setting needed. | +| SDU format information | - | Not applicable for traffic class Interactive. | +| Delivery of erroneous SDUs | No | It is sufficient to signal erroneous IP packets to the UE. | +| Residual BER | $10^{-5}$ | Reflects the desire to have a medium level of protection to achieve an acceptable compromise between packet loss rate and voice transport delay and delay variation. | +| SDU error ratio | $10^{-4}$ | See "Residual BER" parameter. | +| Transfer delay (ms) | - | Is not used for the Interactive traffic class. | +| Guaranteed bit rate (kbps) | - | Is not used for the Interactive traffic class. | +| Traffic handling priority | 1 | Specifies the relative importance for handling of all SDUs belonging to the radio access bearer compared to the SDUs of other bearers. Highest importance is recommended for PoC. | +| Source statistic descriptor | - | Not applicable for traffic class Interactive. | +| Signalling indication | Yes/No | If set to Yes the operator may require the IMS signalling flag (in the PCO IE) to be set, in that case an additional PDP context to be able to receive early media and talk burst control messages may need to be established. | + +If the underlying access network supports the traffic class streaming and a separate PDP context is used for the media, the additional PDP context to be used for the media (voice) flows of the PoC application is recommended to be of streaming traffic class. + +The following QoS attribute values for such PDP context are recommended to be requested by the UE. + +**Table A.2.2-2: Recommended QoS attribute settings for PDP Contexts for the PoC user plane traffic** + +| <b>Traffic class</b> | <b>Streaming class</b> | <b>Notes</b> | +|-----------------------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Maximum bitrate (kbps) | See 'Notes' | Should be set >= "Guaranteed bit rate". | +| Delivery order | No | In sequence delivery of voice samples is not required nor is it desirable since it creates jitter in the media channel. An RTP jitter buffer in the client should re-order packets if needed. | +| Maximum SDU size (octets) | 1500 | Maximum size of IP packets. No PoC specific setting needed. | +| SDU format information | - | Used in RAB QoS attributes only. Transparent RLC protocol mode is not suggested. | +| Delivery of erroneous SDUs | No | It is sufficient to signal erroneous IP packets to the UE. | +| Residual BER | $10^{-5}$ | Reflects the desire to have a medium level of protection to achieve an acceptable compromise between packet loss rate and voice transport delay and delay variation. | +| SDU error ratio | $10^{-4}$ | See "Residual BER" parameter. | +| Transfer delay (ms) | 650 | | +| Guaranteed bit rate (kbps) | See 'Notes' | The value for this parameter is based on the highest speech codec rate negotiated via SDP in the codec mode-set. See table A.2-1. | +| Traffic handling priority | - | Is not used for the Streaming traffic class. | +| Source statistic descriptor | "Unknown" | Proposed setting is "unknown". "Speech" is to be used when the media stream has speech statistical behaviour only.. | +| Signalling indication | - | Only applicable for Interactive class | + +## --- A.3 Radio Network Configuration + +In addition to QoS, the following configuration means are available to improve the performance of the PoC service: + +- UDP/IP header compression (RFC 2507 [20]) or RTP/UDP/IP header compression (RFC 3095 [21]) can be configured to reduce the required radio link capacity. +- Delayed release of DL Temporary Block Flows (TBFs) and Extended TBF Mode in UL (introduced in 3GPP Release 4, available for GERAN only) can be configured to preserve the TBF over a longer period of time. + +# --- Annex B: Delay analysis of PoC session establishment + +## B.1 Introduction + +This annex contains the analysis of the delay for the PoC session establishments based on 'on demand' signalling and based on 'pre-established session' signalling. + +The session establishment delay can be defined the time delay from the time when a user initiates a PoC session until the user can start to speak after receiving RtS (Talk burst confirm). + +It is assumed that the UTRAN access is used and that the UE is in the UE idle mode. + +## B.2 On demand session with manual answer + +Figure B.1 shows the delay components for the case of the session establishment based on 'on demand session with manual answer' signalling. + +![Sequence diagram illustrating the delay components for an on-demand session with manual answer. The diagram shows the interaction between PoC user (UE-A), PS Domain (A), IMS Core (A), PoC AS (A), PoC AS (B), IMS Core (B), PS Domain (B), and PoC user (UE-B). It details the signaling flow from session initiation to media establishment, highlighting various delay components like signaling transfer and RAB establishment.](7d2d1d3870cd224c4430d19334557716_img.jpg) + +The sequence diagram illustrates the following process: + +- Initial Setup:** Both UE-A and UE-B perform 'Power On', 'PS Attach', and 'Establish PDP context'. UE-A then performs 'IMS Registration' via PS Domain (A) and IMS Core (A). UE-B performs 'IMS Registration' via PS Domain (B) and IMS Core (B). +- Session Initiation:** UE-A sends an 'Initiate PoC Session' to PS Domain (A). + - (1) Set up of Signalling Connection (UE-A to PS Domain (A)). + - (2) Establish RAB (UE-A to PS Domain (A)). + - UE-A sends an **INVITE** to IMS Core (A). + - IMS Core (A) performs 'Evaluation of Initial Filter Criteria' and forwards the **INVITE** to PoC AS (A). + - PoC AS (A) sends an **INVITE** to PoC AS (B). + - PoC AS (B) sends an **INVITE** to IMS Core (B). + - IMS Core (B) performs 'Evaluation of Initial Filter Criteria' and checks 'QoS authorization (SBLP)'. + - (3) Signalling Transfer delay (highlighted in yellow) occurs between IMS Core (A) and IMS Core (B). + - IMS Core (B) sends a **200 OK** back to PoC AS (B), which then forwards it to PoC AS (A) and then to IMS Core (A). + - IMS Core (A) sends a **200 OK** to PS Domain (A), which then sends a 'Talk burst confirm' to UE-A. + - UE-A performs 'QoS authorization (SBLP)' and 'Establish appropriate PDP context for media'. + - UE-A sends an **ACK** to IMS Core (A), which is forwarded through PoC AS (A) and PoC AS (B) to IMS Core (B). + - UE-B receives the 'Receiving talk burst' from PoC AS (B). +- Response and Finalization:** UE-B performs 'Power On', 'PS Attach', and 'Establish PDP context', then 'IMS Registration' via PS Domain (B) and IMS Core (B). + - (4) Set up of Signalling Connection (UE-B to PS Domain (B)). + - (5) Establish RAB (UE-B to PS Domain (B)). + - UE-B sends an **INVITE** to PS Domain (B). + - PS Domain (B) sends a **200 OK** to UE-B and also triggers 'Establish appropriate PDP context for media'. + - (6) Signalling Transfer delay (highlighted in yellow) occurs between PS Domain (B) and IMS Core (B). + - IMS Core (B) sends a **200 OK** to PoC AS (B), which forwards it to PoC AS (A) and then to IMS Core (A). + - IMS Core (A) sends a **200 OK** to PS Domain (A), which then sends a 'Talk burst confirm' to UE-A. + - UE-B sends an **ACK** to PS Domain (B), which is forwarded through IMS Core (B) and PoC AS (B) to PoC AS (A) and then to IMS Core (A). + - UE-B receives the 'Receiving talk burst' from PoC AS (B). +- Total Delay:** A vertical double-headed arrow on the left side, spanning from the 'Initiate PoC Session' to the 'Receiving talk burst' at UE-B, is labeled 'Total Delay'. + +Sequence diagram illustrating the delay components for an on-demand session with manual answer. The diagram shows the interaction between PoC user (UE-A), PS Domain (A), IMS Core (A), PoC AS (A), PoC AS (B), IMS Core (B), PS Domain (B), and PoC user (UE-B). It details the signaling flow from session initiation to media establishment, highlighting various delay components like signaling transfer and RAB establishment. + +Figure B.1: Delay component for the case of on demand session with manual answer + +(1) Set up of Signalling Connection in the UE-A side + +When the User-A initiates a PoC Session, the UE-A shall establish the signalling connection to send the NAS signalling. This includes the RRC Connection Setup procedure, the Service Request procedure and the Security Mode Command procedure. + +The major delay comes from the RRC connection setup procedure, which includes the Random Access procedure, the RL setup procedure and the RB setup procedure. + +→ *The estimated delay is about [700ms~1500ms].* + +### (2) Establish Radio Access Bearer (RAB) in the UE-A side + +RAB should be established for the existing PDP context through which the SIP INVITE message is transmitted by the UE-A. This includes the RAB assignment procedure and the Radio Link (RL) reconfiguration procedure and the Radio Bearer (RB) setup procedure. + +→ *The estimated delay is about [700ms~1500ms].* + +### (3) SIP signalling transfer delay + +When the user plan is ready to send the INVITE message, the UE-A sends it to PoC AS, and then it forwards the INVITE message to PS Domain of UE-B. + +→ *The estimated delay is less than [500ms].* + +### (4) Set up of Signalling Connection in the UE-B side + +When the target SGSN receives the INVITE message, the SGSN shall establish a signalling connection in order to send the NAS signalling message to UE. This includes the Paging procedure, the RRC Connection Setup procedure, the Service Request procedure, and the Security Mode Command procedure. + +The major delay comes from the Paging procedure and the RRC Connection Setup procedure. + +→ *The estimated delay is about [700ms~1500ms].* + +### (5) Set up of RAB in the UE-B side + +The terminating SGSN initiates the RAB Assignment procedure for the PDP Context for the IMS signalling in order to transmit the SIP INVITE message to the UE-B. + +The major delay comes from the RAB assignment procedure which includes the RL reconfiguration procedure and the RB setup procedure. + +→ *The estimated delay is about [700ms~1500ms].* + +### (6) Signalling transfer delay + +The UE-B sends a SIP response message to the PoC AS (B). PoC AS (B) forwards the message to the PoC AS (A) and then the PoC AS (A) sends Talk Burst Confirm to the UE-A and Receiving Talk Burst to the UE-B. + +→ *The estimated delay is less than [500ms].* + +Therefore, the total estimated delay for the PoC session establishment (the time when the User-A initiates the PoC session ~ the time when the User-A can start to speak) is about [3800ms~7000ms]. + +## B.3 On demand session with automatic answer + +Figure B.2 shows the delay components in case of the session establishment based on 'on demand session with automatic answer' signalling. + +![Sequence diagram illustrating the delay components for an on-demand session with automatic answer. The diagram shows the interaction between PoC user (UE-A), PS Domain (A), IMS Core (A), PoC AS (A), PoC AS (B), IMS Core (B), PS Domain (B), and PoC user (UE-B). Key phases include Power On, PS Attach, Establish PDP context, Perform IMS Registration, Initiate PoC Session, (1) Set up of Signalling Connection, (2) Establish RAB, (3) Signalling Transfer delay (Part I), (4) Signalling Transfer delay (Part II), and Talk burst control and transfer of Media. A 'Total Delay' indicator is shown on the left side.](933ecd14c858bf3fc919222d8e357bc8_img.jpg) + +The sequence diagram illustrates the following components and steps: + +- Initial Setup:** Both UE-A and UE-B perform Power On, PS Attach, and Establish PDP context. Both then Perform IMS Registration. +- Initiation:** UE-A initiates the PoC Session. +- Signalling Connection Setup:** (1) Set up of Signalling Connection and (2) Establish RAB occur on the UE-A side. +- Signalling Transfer (Part I):** UE-A sends an INVITE to PS Domain (A), which is processed by IMS Core (A) through Evaluation of Initial Filter Criteria. The INVITE is then transferred through PoC AS (A) and PoC AS (B) to IMS Core (B), where it is processed through another Evaluation of Initial Filter Criteria. +- Signalling Transfer (Part II):** IMS Core (B) sends an INVITE to PS Domain (B). PoC AS (B) performs QoS authorization (SBLP) and sends an AUTO-ANSWER back to PoC AS (A). PoC AS (A) performs its own QoS authorization (SBLP) and sends a 200 OK and ACK back to IMS Core (A). IMS Core (A) sends a Talk burst confirm to UE-A. +- Media Setup:** UE-A receives a 200 OK and ACK from IMS Core (A). It then establishes the appropriate PDP context for media. Media packets are buffered in PoC AS (A). IMS Core (B) performs QoS authorization (SBLP) and sends an INVITE to PS Domain (B), which establishes the appropriate PDP context for media for UE-B. +- Media Transfer:** UE-B receives a 200 OK and ACK from PS Domain (B). Media packets are transferred from PoC AS (A) through IMS Core (B) to UE-B. UE-B receives the talk burst and sends ACKs. The final phase is Talk burst control and transfer of Media. +- Total Delay:** A vertical double-headed arrow on the left indicates the total delay from the initiation of the PoC session to the start of media transfer. + +Sequence diagram illustrating the delay components for an on-demand session with automatic answer. The diagram shows the interaction between PoC user (UE-A), PS Domain (A), IMS Core (A), PoC AS (A), PoC AS (B), IMS Core (B), PS Domain (B), and PoC user (UE-B). Key phases include Power On, PS Attach, Establish PDP context, Perform IMS Registration, Initiate PoC Session, (1) Set up of Signalling Connection, (2) Establish RAB, (3) Signalling Transfer delay (Part I), (4) Signalling Transfer delay (Part II), and Talk burst control and transfer of Media. A 'Total Delay' indicator is shown on the left side. + +Figure B.2: Delay component for the case of on demand session with automatic answer + +(1) Set up of Signalling Connection in the UE-A side + +When the User-A initiates a PoC Session, the UE-A shall establish the signalling connection in order to send the NAS signalling. This includes the RRC Connection Setup procedure, the Service Request procedure and the Security Mode Command procedure. + +This step is the same as that of the session establishment based on 'on demand session with manual answer'. + +→ *The estimated delay is about [700ms~1500ms].* + +### (2) Establish Radio Access Bearer (RAB) in the UE-A side + +RAB should be established for the existing PDP context through which the SIP INVITE message can be transmitted by the UE-A. This includes the RAB assignment procedure and the RL reconfiguration procedure and the RB setup procedure. + +→ *The estimated delay is about [700ms~1500ms].* + +### (3) SIP signalling transfer delay (Part I) + +When the user plan is ready to send INVITE message, the UE-A sends the message to the PoC AS (A) and then PoC AS (A) forwards the message to the PoC AS (B). + +→ *The estimated delay is less than [500ms]* + +### (4) SIP signalling transfer delay (Part II) + +For the Auto-answer mode, when PoC AS (B) receives the INVITE message, the PoC AS (B) sends the AUTO-ANSWER message to the PoC AS (A) without waiting for the response from the UE (B). The PoC AS (A) can send the Talk burst confirm to the UE-A when it receives AUTO-ANSWER message from the PoC AS (B). + +→ *The estimated delay is less than [500ms]* + +Therefore, the total estimated delay for the PoC session establishment (the time when the User-A initiates the PoC session ~ the time when the User-A can start to speak) is about [2400ms~4000ms]. + +Note that the delay of the session establishment using 'on demand session with automatic answer' can be about 2000ms (2 sec) smaller than that of the session establishment using 'on demand session with manual answer'. + +## --- B.4 On pre-established session + +Figure B.3 shows the delay components in case of the session establishment based on 'pre-established session' signalling. + +![Sequence diagram illustrating the delay component for the case of pre-established session between two User Equipment (UE-A and UE-B) via their respective PS Domains and IMS Cores. The diagram shows the flow of SIP messages (INVITE, 200 OK, AUTO-ANSWER, ACCEPT) and media transfer, highlighting delays in signalling and media transfer. Key components include: (1) Set up of Signalling Connection, (2) Establish RAB, (3) Signalling Transfer delay (Part I), and (4) Signalling Transfer delay (Part II).](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +The diagram illustrates the sequence of operations for a PoC session establishment with pre-established sessions. On the UE-A side, the process starts with Power On, PS Attach, Establish PDP context, and Perform IMS Registration. A 'Set up of Pre-established session' involves an INVITE from UE-A to PoC AS (A), followed by an 'Evaluation of Initial Filter Criteria' in the IMS Core (A), leading to a 200 OK response. The PoC Session is initiated, leading to (1) Set up of Signalling Connection and (2) Establish RAB. The 'Establish media' phase follows, with (3) Signalling Transfer delay (Part I) involving INVITE and AUTO-ANSWER messages, and (4) Signalling Transfer delay (Part II) involving ACCEPT and Talk burst confirm messages. Media transfer then occurs, with a note to 'Establish appropriate PDP context for media'. The UE-B side follows a similar sequence: Power On, PS Attach, Establish PDP context, Perform IMS Registration, and 'Set up of Pre-established session' (INVITE, Evaluation of Initial Filter Criteria, 200 OK). The 'Set up of Signalling Connection' and 'Establish RAB' steps occur on the UE-B side, followed by 'Receiving talk burst' and another note to 'Establish appropriate PDP context for media'. + +Sequence diagram illustrating the delay component for the case of pre-established session between two User Equipment (UE-A and UE-B) via their respective PS Domains and IMS Cores. The diagram shows the flow of SIP messages (INVITE, 200 OK, AUTO-ANSWER, ACCEPT) and media transfer, highlighting delays in signalling and media transfer. Key components include: (1) Set up of Signalling Connection, (2) Establish RAB, (3) Signalling Transfer delay (Part I), and (4) Signalling Transfer delay (Part II). + +**Figure B.3: Delay component for the case of pre-established session** + +### (1) Set up of Signalling Connection in the UE-A side + +When the User-A initiates a PoC Session, the UE-A shall establish the signalling connection in order to send the NAS signalling. This includes the RRC Connection Setup procedure, the Service Request procedure and the Security Mode Command procedure. + +This step is the same as that of the session establishment based on 'on demand session'. + +→ The estimated delay is about [700ms~1500ms]. + +### (2) Set up of RAB in the UE-A side + +RAB should be established for the existing PDP context through which the SIP REFER message is transmitted by the UE-A. + +This step is the same as that of the session establishment based on 'on demand session'. + +→ *The estimated delay is about [700ms~1500ms].* + +### (3) SIP signalling transfer delay (Part I) + +When the user plan is ready to send the REFER message, the UE-A sends the message to the PoC AS (A) and then PoC AS (A) sends the INVITE message to the PoC AS (B). + +→ *The estimated delay is less than [500ms].* + +### (4) SIP signalling transfer delay (Part II) + +When it receives the INVITE message, the PoC AS (B) sends the AUTO-ANSWER message to the PoC AS (A) without waiting for the response from the UE-B. It is possible because a 'pre-established session' has been set up beforehand. The PoC AS (A) sends the Talk burst confirm to the UE-A when it receives the AUTO-ANSWER message from the PoC AS (B). + +→ *The estimated delay is less than [500ms].* + +Therefore, the total estimated delay for the PoC session establishment (the time when the User-A initiates a PoC session ~ the time when the User-A can start to speak) is about [2400ms~4000ms]. + +Note that the delay of the session establishment using 'pre-established session' is almost the same as that of the session establishment of 'on demand session with automatic answer'. + +# --- Annex C: Required SigComp performance + +## C.1 Introduction + +It is recognized that the SIP signalling transfer delay is dependent on: + +- Size of the messages sent over the radio link, which is dependent on the performance of the signalling compression algorithm (SigComp, RFC 3320 [14]). +- Available bandwidth over the radio link for signalling, which is dependent on the maximum bit rate attribute settings for the PDP Context used for the PoC control plane traffic. + +This annex contains the analysis of required SigComp performance in order to meet the delay budget for SIP signalling transfer delay presented in Annex B. + +## --- C.2 Assumptions + +The following assumptions have been used: + +- The on demand session using automatic answer is used and the inviting PoC User is given an early "right-to-speak" indication as described in clause 5.3.2.2 and clause B.2. +- A typical SIP INVITE message in an OMA PoC implementation will have approximately the same size as the SIP INVITE message described as message 1 in clause 7.2.2.1 in TS 24.228 [15]. The size of the referred SIP INVITE is 1375 bytes not including UDP (or TCP) and IP overhead, therefore for OMA PoC it is assumed that a SIP INVITE message will be in the order of 1400 bytes including UDP (or TCP) and IP overhead. +- A typical SIP 200 OK message in an OMA PoC implementation will have approximately the same size as the SIP 200 OK message described as message 18 in clause 7.2.2.1 in TS 24.228 [15]. Therefore for OMA PoC it is assumed that a SIP 200 OK message will be in the order of 800 bytes including UDP (or TCP) and IP overhead. +- A SIP 100 Trying message must be sent over the radio link as acknowledgement of the SIP INVITE message. The size of the SIP 100 Trying is 300 bytes including UDP (or TCP) and IP overhead. +- The talk burst confirm message is assumed to be 40 bytes including IP and UDP overhead. +- The processing time in the UE to produce and compress a SIP message is 50 ms. +- The delays imposed by all involved core network elements, including the core network of the radio access network (i.e. SGSN and GGSN) in a message transfer (IMS Core and PoC AS) are 100 ms. +- The duration between the times the inviting PoC User initiates the PoC session and when he receives a "right-to-speak" indication should be less than 2.0 seconds, as required in OMA\_RD PoC [7]. +- All lower estimated delay values presented in clause B.2 apply. + +## --- C.3 Estimation of SIP compression ratios + +The duration between the times the inviting PoC User initiates the PoC session and when he receives a "right-to-speak" indication shall be less than 2.0 seconds (2000 ms) according to OMA\_RD PoC [7]. It is assumed that all lower estimated delay values presented in clause B.2 applies. This means that a total delay budget of less than 2000 ms – 700 ms – 700 ms = 600 ms is assumed for the SIP signalling transfer delay (delay components (3) and (4)). + +Table C.3-1 presents the delay budget given the assumptions presented in C.2. + +**Table C.3-1: Detailed description of the delay budget for SIP signalling transfer delay** + +| Action | Delay | Description | +|---------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| The PoC Client produce and compress a SIP INVITE message<br>The PoC Client transmit the SIP INVITE message to the PoC AS: | 50 ms<br><br>*Radio transport delay of SIP INVITE + 100 ms | <br><br>*Radio transport delay of SIP INVITE = (SIP message size * Compression ratio) / Bit rate of radio link | +| The IMS Core sends a SIP 100 Trying to acknowledge the reception of the SIP INVITE | **Radio transport delay of SIP 100 Trying | **Radio transport delay of SIP 100 Trying = (SIP message size * Compression ratio) / Bit rate of radio link | +| The PoC AS transmits the SIP 200 OK message to the PoC Client: | 100 ms + ***Radio transport delay of SIP 200OK | ***Radio transport delay of SIP 200OK = (SIP message size * Compression ratio) / Bit rate of radio link | +| The PoC AS transmits a talk burst confirmed message to the PoC Client: | ****Radio transport delay of talk burst confirmed message | ****Radio transport delay of talk burst confirmed message = (talk burst confirmed message size) / Bit rate of radio link | +| Total SIP signalling transfer delay: | 50 ms + 100 ms + 100 ms + Radio transport delay of SIP INVITE + Radio transport delay of SIP 100 Trying + Radio transport delay of SIP 200OK + Radio transport delay of talk burst confirmed message < 600 ms | | + +The compression ratios of table C.3-2 is calculated by using the expression for the total SIP signalling transfer delay in table C.3-1, and assuming a bit rate of the radio link used for the PoC control plane traffic + +**Table C.3-2: Compression ratio as a function of Bit rate of the radio link** + +| Bit rate of radio link | Compression ratio | +|------------------------|-------------------| +| 8 kbps | > 8.06:1 | +| 16 kbps | > 3.79:1 | +| 32 kbps | > 1.84:1 | +| 64 kbps | > 0.91:1 | + +## C.4 SigComp requirements + +Given that a low bit rate PS bearer (throughput < 16 kbps) is used for the PoC control plane traffic, SIP signalling compression ratios typically larger than 3:1 is needed to meet the delay requirement stated in OMA\_RD PoC [7]. Therefore it can be concluded that: + +- The decompression byte code should be stored as a state and should not be sent from the transmitting node to the receiving node in every SigComp message. This implies that a SigComp implementation used for PoC should have a state memory size (SMS, see RFC 3320 [14]) larger than zero. +- An SMS that is larger than zero enables stateful compression, which probably is needed to obtain sufficient SIP signalling compression efficiency. +- The initial creation of the SigComp compartment (see RFC 3320 [14]) is done during IMS registration. The exchange and storing of the decompression byte codes is recommended to be performed during the non time critical SIP message exchange of the IMS Registration. This enables the transmission of compressed SIP messages without the overhead of decompression byte codes even in the first PoC Session after IMS Registration. However, the receiver of the byte codes cannot assume that the byte codes are sent only during the IMS registration. + +The IMS support for SigComp is specified in TS 24.229 [16], which fulfils the requirements as stated above. Consequently, IMS provides sufficient SigComp support to fulfil the OMA delay requirements. + +# Annex D: Change history + +| Change history | | | | | | | | | +|----------------|--------|-----------|------|-----|-----|-------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | Old | New | +| 2004-12 | SA#26 | SP-040749 | - | - | - | Creation of version 6.0.0 | 2.0.0 | 6.0.0 | +| 2005-03 | SA#27 | SP-050160 | 0001 | 3 | - | Impact on Charging Correlation | 6.0.0 | 6.1.0 | +| 2005-03 | SA#27 | SP-050160 | 0002 | 1 | - | QoS of pre-established PDP context | 6.0.0 | 6.1.0 | +| 2005-03 | SA#27 | SP-050160 | 0003 | 1 | - | Alignment of 23.979 with OMA architecture | 6.0.0 | 6.1.0 | +| 2005-06 | SA#28 | SP-050343 | 0004 | 1 | - | Correction of OMA PoC references | 6.1.0 | 6.2.0 | +| 2007-06 | - | - | - | - | - | Update to Rel-7 version | 6.2.0 | 7.0.0 | +| 2008-12 | SP-42 | - | - | - | - | Update to Rel-8 version | 7.0.0 | 8.0.0 | +| 2009-12 | SP-46 | - | - | - | - | Update to Rel-9 version | 8.0.0 | 9.0.0 | +| 2011-03 | SP-51 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | <b>11.0.0</b> | +| 2014-09 | SP-65 | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | <b>12.0.0</b> | +| 2015-12 | - | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | <b>13.0.0</b> | +| 2017-03 | - | - | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | <b>14.0.0</b> | +| 2018-06 | SP-80 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | <b>15.0.0</b> | +| 2020-07 | SP-88E | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | <b>16.0.0</b> | \ No newline at end of file